[pgrouting-dev] Idea: new Github repository for organizational issues and documents

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[pgrouting-dev] Idea: new Github repository for organizational issues and documents

dkastl
Hi Vicky and Steve,

I'm currently helping to re-organize another Open Source project on Github, and we found it a good idea to have a separate "org" Github repository for organizational issues and documents.

Such a repository helps to keep unrelated issues away from source repositories. Also templates, contributor guidelines and other documents, that may be shared between multiple projects, could be stored there.

If you don't disagree, I will create such a repository in the next weeks and fill it with content in parallel with the other Open Source project.

Best regards,
Daniel

 

--
Georepublic UG & Georepublic Japan
eMail: [hidden email]
Web: https://georepublic.info




_______________________________________________
pgrouting-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/pgrouting-dev
Reply | Threaded
Open this post in threaded view
|

Re: [pgrouting-dev] Idea: new Github repository for organizational issues and documents

Vicky Vergara-2
👍
Setting a place where administrative issues can be set looks fine.
I use my forks to keep issues so I don't forget, or issues for the GSoC students.
But as an organization everything is tight together.
Sub issues on the individual projects can be derived from the administration issues.





On Wed, Jul 12, 2017 at 10:30 AM, Daniel Kastl <[hidden email]> wrote:
Hi Vicky and Steve,

I'm currently helping to re-organize another Open Source project on Github, and we found it a good idea to have a separate "org" Github repository for organizational issues and documents.

Such a repository helps to keep unrelated issues away from source repositories. Also templates, contributor guidelines and other documents, that may be shared between multiple projects, could be stored there.

If you don't disagree, I will create such a repository in the next weeks and fill it with content in parallel with the other Open Source project.

Best regards,
Daniel

 

--
Georepublic UG & Georepublic Japan
eMail: [hidden email]
Web: https://georepublic.info




_______________________________________________
pgrouting-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/pgrouting-dev



--
Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44, 
81739 München, Germany

Vicky Vergara
Operations Research

eMail: vicky@georepublic.de
Web: https://georepublic.info

Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9

Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl


_______________________________________________
pgrouting-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/pgrouting-dev
Reply | Threaded
Open this post in threaded view
|

Re: [pgrouting-dev] Idea: new Github repository for organizational issues and documents

Stephen Woodbridge
In reply to this post by dkastl
I'm not a fan of this, but wouldn't stop it if you want to do this. For
transparency of the project and provenience I think it is better to keep
it all in one place.

I look at mapserver which has been around for years or PostGIS, etc and
they have not taken this approach.

If you need to track administrative or PSC tasks, create a ticket and
tag it as such. It is easy to filter queries based on tags.


On 7/12/2017 11:30 AM, Daniel Kastl wrote:

> Hi Vicky and Steve,
>
> I'm currently helping to re-organize another Open Source project on
> Github, and we found it a good idea to have a separate "org" Github
> repository for organizational issues and documents.
>
> Such a repository helps to keep unrelated issues away from source
> repositories. Also templates, contributor guidelines and other
> documents, that may be shared between multiple projects, could be stored
> there.

I don't think we should do it just because some other project decided to
do it. Part of the provenience of the software is the management of the
project. We could easily make an admin folder for all this stuff. I
don't think there is much value in sharing between multiple projects, it
is easy enough to copy the information and personalize it to the
project. And I would not want one project changing the documents for my
project without my approval. This just opens a rats nest IMHO.

> If you don't disagree, I will create such a repository in the next weeks
> and fill it with content in parallel with the other Open Source project.

As I said, I'm not a fan of this idea. But as you and Vicky are doing
most of the work these days. I'll leave this to you to decide, but I
hope you give my concerns some serious consideration.

-Steve


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

_______________________________________________
pgrouting-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/pgrouting-dev