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

Tue Aug 8 17:38:43 PDT 2017

I think you are overrating the discomfort of having to handle pull requests from github (as a mirror vs. being our official) if everything isn't there and forgetting that you are forcing people who don't have github accounts to create one.

There are 3 kinds of contributors I think are important

1)      End users reporting bugs – many of these don't have github accounts so forcing them to create an osgeo instead of github sounds better. You can argue creating a github account is easier these days.

2)      Developers who are on github – we take pull requests from them whether I do it from github/gogs/svn doesn't matter to me.  The conversation if changes need to be made is better on github or gogs.

To me after it's committed that's all noise I don't really need in final commit or on ticket.

If a dev becomes a serious contributor e.g. Dan Baston or Björn Harrtell then I'd really like them to have an OSGeo account.

>From what I presume from both, they just want to work with a git repo and less sensitive to where the official is.

Sandro is already struggling with svn so I know he prefers git.

So my reason for wanting the git move is to make it easier for those with commit access already and future.

3)      Developers/users who don't have a github account or don't like committing to github for political reasons.  We lose all these people if they are forced to create a github accounts before they can exchange with us.

So I'm still +1 for GIT OSGeo and okay with tickets moving from trac to gogs.

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
Sent: Tuesday, August 08, 2017 7:46 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

The point isn't features, it's developer density. I don't see any great advantage to gogs if we still have PRs and work managing the github mirror. Might as well continue on w/ trac/svn, since gogs shares the main drawback; forcing folks to get new accounts / logins before they can start engaging.

I'm sure gogs is technically wunderbar, but it's not where the persons are.

P.

On Tue, Aug 8, 2017 at 4:38 PM, Regina Obe <lr at pcorp.us <mailto:lr at pcorp.us> > wrote:

Nice.

1) So gogs with the pull and the lazy editing feature (I can edit via the web interface which I have done) has everything github has and appeases my emotional side too
2) appeases my need to be able to know I can access via SQLif I really really wanted to which I got from this:
https://git.osgeo.org/gogs/postgis/postgis/pulls/9#issuecomment-3040

 :)

3) I'm okay with trac eventually moving to gogs.  It would be sweet if we change the r... to the actual git hash.  That seems like a simple r.. map to git hash UPDATE  statement if we have a table that maps svn revision numbers to git which I assume we might be able to generate via the mirror.

That's a minor thing for me though.

Thanks,
Regina

-----Original Message-----
From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org <mailto:postgis-devel-bounces at lists.osgeo.org> ] On Behalf Of Sandro Santilli
Sent: Tuesday, August 08, 2017 6:34 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> >
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

On Tue, Aug 08, 2017 at 06:22:35PM -0400, Regina Obe wrote:
> But OSGEo trac is on postgresql now :) I'm sure if I am given a
> postgresql backup I can figure out how to get data out of it much
> easier than using a github api :)

An XSLT recipe ? :P

I'm speaking as the one who made `Trac -> Gogs` tool based on PostgreSQL queries.
See example results: https://git.osgeo.org/gogs/strk/geos-migration-test/issues
Code: http://strk.kbt.io/projects/go/trac2gogs/

--strk;

_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/postgis-devel

_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto: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/462c9c40/attachment.html>