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

[Regina Obe]

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] On Behalf Of Sandro Santilli
Sent: Tuesday, August 08, 2017 6:34 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

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
https://lists.osgeo.org/mailman/listinfo/postgis-devel