<div dir="ltr">I have a bunch of svn based scripts that I use daily, but I would be happily trash my current work flow for github. <div><br></div><div>I would prefer option 3, but option 2 would be okay too.</div><div><br></div><div>I think that the utility of github pull requests is just too valuable to go with option 1.</div><div><br></div><div>I really need to rewatch the classic "Git for Ages 4 and up"... <a href="https://www.youtube.com/watch?v=1ffBJ4sVUb4">https://www.youtube.com/watch?v=1ffBJ4sVUb4</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 6, 2017 at 1:26 PM, Luigi Pirelli <span dir="ltr"><<a href="mailto:luipir@gmail.com" target="_blank">luipir@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">FYI in QGIS dev world we still not have found a clear and complete way<br>
to migrate tracker from redmine to GH or GitLab.<br>
More info and details can be asked to the key people that investigated<br>
the problem... just asking in Dev list.<br>
<br>
FYI we are still in a new updated redmine :/<br>
Luigi Pirelli<br>
<br>
******************************<wbr>******************************<wbr>******************************<wbr>********<br>
* Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com<br>
* LinkedIn: <a href="https://www.linkedin.com/in/luigipirelli" rel="noreferrer" target="_blank">https://www.linkedin.com/in/<wbr>luigipirelli</a><br>
* Stackexchange: <a href="http://gis.stackexchange.com/users/19667/luigi-pirelli" rel="noreferrer" target="_blank">http://gis.stackexchange.com/<wbr>users/19667/luigi-pirelli</a><br>
* GitHub: <a href="https://github.com/luipir" rel="noreferrer" target="_blank">https://github.com/luipir</a><br>
* Mastering QGIS 2nd Edition:<br>
* <a href="https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition" rel="noreferrer" target="_blank">https://www.packtpub.com/big-<wbr>data-and-business-<wbr>intelligence/mastering-qgis-<wbr>second-edition</a><br>
******************************<wbr>******************************<wbr>******************************<wbr>********<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On 6 September 2017 at 20:36, Mateusz Loskot <<a href="mailto:mateusz@loskot.net">mateusz@loskot.net</a>> wrote:<br>
> On 6 September 2017 at 15:14, Even Rouault <<a href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a>> wrote:<br>
>> Hi,<br>
>><br>
>> I've heard a few voices speaking/asking/begging for a git/github migration.<br>
>> At some point we'll certainly have to do it, as SVN vs git is beginning to<br>
>> feel more and more like CVS vs SVN 15 years ago.<br>
>><br>
>> I can see different options :<br>
>> [...]<br>
>><br>
>> 3) migrate code and tickets to github. I guess this would match most<br>
>> (especially occasional) contributor wishes regarding the "social" aspect.<br>
>> What would be needed is Trac -> github ticket migration. Thomas Bonfort did<br>
>> it for MapServer at some point, but he lost the script if I remember well (I<br>
>> can see in<br>
>> <a href="https://stackoverflow.com/questions/6671584/how-to-export-trac-to-github-issues" rel="noreferrer" target="_blank">https://stackoverflow.com/<wbr>questions/6671584/how-to-<wbr>export-trac-to-github-issues</a><br>
>> a number of possibilities listed). One issue also is we have numbers taken<br>
>> by existing github pull requests, so there would be collisions on import (we<br>
>> could decide either to sacrifice colliding Trac tickets, as there are really<br>
>> old, currently the colision appear for tickets older than 2003, or move them<br>
>> to an available github ticket number. Or to sacrifice existing PR, but there<br>
>> are a few pending ones)<br>
>><br>
>> There's also the valid concern about being tied with <a href="http://github.com" rel="noreferrer" target="_blank">github.com</a> regarding<br>
>> tickets. Recently I found<br>
>> <a href="https://github.com/josegonzalez/python-github-backup" rel="noreferrer" target="_blank">https://github.com/<wbr>josegonzalez/python-github-<wbr>backup</a><br>
>><br>
>> which can backup code, issues, pull requests, etc.. using the github API.<br>
>><br>
>><br>
>> My synthetic view of the situation:<br>
>> [...]<br>
>> 3) offers probably the best contributor experience. We loose a bit of<br>
>> control, but a backup(*) strategy exists (at least for now). I'd tend to<br>
>> favor this approach.<br>
><br>
><br>
> As member of the development team, I'm very much support this motion<br>
> and move to GitHub.<br>
><br>
><br>
>> So this email is mostly to say I'm open to the idea, but I'd appreciate if<br>
>> someone else could take the lead on this. I'd be happy to help. A RFC to<br>
>> formalize the move would be needed.<br>
><br>
> If no one offers her/him-self to do it earlier, I am willing to offer myself to<br>
> migrate GDAL to GitHub in mid October.<br>
><br>
> Then, I will prepare RFC, ask for comments and voting,<br>
> develop Trac to GitHub workflow using existing tools and/or custom<br>
> scripting in Python,<br>
> test with sandbox mirror and push final migration.<br>
><br>
> Best regards,<br>
> --<br>
> Mateusz Loskot, <a href="http://mateusz.loskot.net" rel="noreferrer" target="_blank">http://mateusz.loskot.net</a><br>
> ______________________________<wbr>_________________<br>
> gdal-dev mailing list<br>
> <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/gdal-dev</a><br>
______________________________<wbr>_________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/gdal-dev</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">--<div><a href="http://schwehr.org" target="_blank">http://schwehr.org</a></div></div>
</div>