+0. I'm tentitively in favour of migrating to a better track system, but
would fist like to be comfortable with:
* What new tracker will we use and will it integrate with our current
workflow?
* Can we migrate old issues?
* Can we exit from the new system if we need to (as per Ben's comments)?
Cameron
On 13/10/17 8:09 am, Even Rouault wrote:
On vendredi 13 octobre 2017 10:02:29 CEST Ben Caradoc-Davies wrote:
> We control our trac instances. Even before comparing features, is there
> any mechanism for migrating issues from GitHub to another system should
> we need to do so? I am still smarting from the Codehaus shutdown and its
> impact on GeoTools and GeoServer.
>
Ben,
Never tried it but gitlab has apparently an import module (rather
expected given they directly compete):
https://docs.gitlab.com/ce/user/project/import/github.html
There are also ways to backup github tickets through their REST API
with gitthub-backup (which I tried)
For example:
1) pip install github-backup
2) in github UI, create a personnal access token, so as to be able to
use authenticated
requests to github API, to bypass the rate limit of unauthenticated
requests (you can use it even for repositories that you don't own)
3) github-backup -i -R python-github-backup josegonzalez --issues
--issue-comments --issue-events --pulls --pull-comments --pull-commits
-t ${your_github_token}
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
Live-demo mailing list
Live-demo@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
_______________________________________________
Live-demo mailing list
Live-demo@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
