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

[Regina Obe]

Okay sound like it's doable but not trivial.

 

I imagine going to github is also doable but not trivial.

 

So I'm beginning to lean on the side of do nothing since so many people are
against switching to just git.

And I see my life harder dealing with github tickets.

 

 

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf
Of Even Rouault
Sent: Wednesday, August 09, 2017 10:19 AM
To: postgis-devel at lists.osgeo.org
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay
on SVN

 

On mardi 8 août 2017 14:39:44 CEST Paul Ramsey wrote:

> 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

> 

> 

 

 

Linked to that, I found

https://github.com/josegonzalez/python-github-backup

 

which can backup code, issues, pull requests, etc.. using the github API

 

Quickly tested it on their own repo. Seems to work (although a bit slow:
requires 2 GET per issue / pull request to retrieve extra details that are
not retrieved by the global request you showed above)

 

Even

 

-- 

Spatialys - Geospatial professional services

http://www.spatialys.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20170809/57b1a29e/attachment.html>