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

[Regina Obe]

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 :)

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
Sent: Tuesday, August 08, 2017 5:40 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

 

Getting issues out of github is pretty straightforward, particularly compared to trac, 

 

https://api.github.com/repos/mapserver/mapserver/issues?page=1 <https://api.github.com/repos/mapserver/mapserver/issues?page=1&per_page=10> &per_page=10

 

 

 

P.

 

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

Because there is no point of moving to github unless we move the whole thing that means trac too.
The main benefit of moving to GitHub would be lower maintenance which means getting rid of trac and any need for any other git mirror.

To Paul's point I'm more concerned about getting out of github than getting into it.
Though would be interesting to know how much effort they put into the migration of all their tickets to github.

Maintaining an OSGeo git and trac does take some maintenance.
 Is it worth keeping or not is the question in my mind absence of any emotional argument.

I would say probably still, but strk you are the one doing most of the work keeping things running so I don't know.





-----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 5:13 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 04:56:47PM -0400, Regina Obe wrote:

> That said my vote is for:
>
> Gitea (OSGeo Git) / OSGeo Trac / mirror GitHub - ditch SVN

This motion is a bit confusing, but assuming it is about moving the code repository from OSGeo/SVN to OSGeo/GIT my vote is a +1

> 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.

I don't understand this statement: "patch view would be gone".
If we keep using trac for tickets why would you loose "patch view" ?

--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/859a712b/attachment.html>