[postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

[Paul Ramsey]

The mapserver github migration seems to have also retained "patch view"
which I assume Regina means the r999 notation links to diffs.

https://github.com/mapserver/mapserver/issues/2002



On Tue, Aug 8, 2017 at 2:07 PM, Paul Ramsey <pramsey at cleverelephant.ca>
wrote:

> The practical aspects of "going where the people are" leads me to advocate
> for going all over to github. Code, tickets, etc. Mapserver managed to go
> there with all their history, so there's prior art and folks we can talk to
> about it.
>
> https://github.com/mapserver/mapserver/issues/42
>
> P.
>
>
> On Tue, Aug 8, 2017 at 1:56 PM, Regina Obe <lr at pcorp.us> wrote:
>
>> Here is my understanding of situation
>>
>> Everyone wants GIT of some sort (Sandro, Mateusz, Dan Baston etc.)
>> Most people want Github (Mateusz, Paul Ramsey, Dan Baston etc.)
>> Some people want Github as the official repo to simplify the process
>> (Mateusz and Paul Ramsey)
>>
>> We've already got postgis website, buidbot repo on OSGeo git.
>>
>> I want my tickets and comments preserved cause I still remember the mess
>> getting off of google code.
>>
>> I like svn more than git just cause git provides me nothing of value I can
>> appreciate at the moment, but I'm willing to let go of that in spirit of
>> doing what's best for all.
>>
>> Github has a community so we'll always need at least a mirror there.
>>
>> Having github as anything but a mirror seems pretty pointless (aside from
>> Gitea upkeep) to me unless the tickets are there as well which brings up
>> the
>> question of how to push our existing tickets there,
>> How to export our tickets and comments should github decide to become evil
>> or we just want to get off for some other reason.
>>
>> Some staunch Free Software advocates - Sandro, Sebastien, Linus, and I
>> think
>> a lot of PostgreSQL devs don't like their primary source control being a
>> proprietary thing.
>> I feel somewhat in that camp but feel it might be an illogical / emotional
>> gut feeling drive thing that I might need to learn to let go.
>>
>> That said my vote is for:
>>
>> Gitea (OSGeo Git) / OSGeo Trac / mirror GitHub - ditch SVN
>>
>> Reason being is if for some reason Gitea doesn't work out, I think it's
>> far
>> easier to move from Gitea to GitHub
>> It also means tickets don't need moving (though having the seamless patch
>> view would be gone and I'd have to settle for a link to a git pull).
>> Until we get tracgit working.
>>
>> It also means I don't have to worry about exporting tickets and comments
>> out
>> of github should something go wrong with github or we decide github is no
>> longer the solution for us.
>>
>> If we decide to change, I was thinking we can do it after PostGIS 2.4
>> release and start with PostGIS 2.5.
>>
>> Other people feel free to chime in with your thoughts.
>>
>>
>> Thanks,
>> Regina
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20170808/797fd545/attachment.html>