<div dir="ltr">I agre seems that nothing is changed... just changed propriety of a closed platform. We should only have a plan B in case they decide to change licences and politics,</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">Luigi Pirelli<br><br>**************************************************************************************************<br>* LinkedIn: <a href="https://www.linkedin.com/in/luigipirelli" target="_blank">https://www.linkedin.com/in/luigipirelli</a><br>* Stackexchange: <a href="http://gis.stackexchange.com/users/19667/luigi-pirelli" target="_blank">http://gis.stackexchange.com/users/19667/luigi-pirelli</a><br>* GitHub: <a href="https://github.com/luipir" 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" target="_blank">https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition</a><br>* Hire me: <a href="http://goo.gl/BYRQKg" target="_blank">http://goo.gl/BYRQKg</a><br>**************************************************************************************************</div></div>
<br><div class="gmail_quote">On 5 June 2018 at 09:37, Régis Haubourg <span dir="ltr"><<a href="mailto:regis.haubourg@gmail.com" target="_blank">regis.haubourg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi all, <br></div><div> +1 with all that. <br></div><div><br></div><div><br></div><div>The most pragmatic issue with Github is that issue management is stored in their servers only, and extracting them properly is not so easy if you need to keep all references, history of comments, authors and so on. <br></div><div><br></div><div>That is one of the strong reasons not to migrate issues to GitHub in a hurry. The only mature alternative, and allowing us to keep the ownership and hosting of our issues would be Gitlab, besides continuing with redmine of course. <br></div><div><br></div><div>Moving to gitlab is a big task for sure, we need to keep users, issues, pull request history, issue referencing and last but not the least, Continuous integration. <br></div><div><br></div><div>Gitlab has it all, but the migration process needs to be totally clean before we jump into it. I like the idea of having a way out of Github in case things go wrong. They are already wrong to me concerning the issue management in fact. <br></div><div><br></div><div>So no hurry at all clearly. But let's keep trying to tackle all migration obstacles. We submitted a grant application to make a true prototype, that would help a lot. <br></div><div><br></div><div>Best regards</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Régis<br></div><div><br></div><div><br></div><div><br></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2018-06-05 9:16 GMT+02:00 Richard Duivenvoorde <span dir="ltr"><<a href="mailto:rdmailings@duif.net" target="_blank">rdmailings@duif.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Please, no panic, no stress :-)<br>
<br>
Nobody is forcing us to move, and until something changes in a very<br>
negative way, we are not moving (for what I understand from our PSC<br>
meeting)...<br>
<br>
As some more context: the reason that 'we' (as a community) are/were<br>
looking into Gitlab, is actually because some members had problems with<br>
our issue-tracker/Redmine earlier.... not so much because we wanted our<br>
code to move!<br>
<br>
We also concluded that currently our Redmine instance is<br>
behaving/performing OK, so the urge to move to another issue tracker is<br>
not as high anymore.<br>
<br>
Some community members had very good experience with Gitlab, AND<br>
invested time into creating scripts to move our issues from Redmine to<br>
Gitlab. To also be able to use Gitlab CI it was easiest to also move code.<br>
<br>
The wiki page (in my view) is not so much a 'Migration *plan*', but more<br>
created to do a thorough investigation of what we have to move/do IF we<br>
decide to do such a move (to whatever service)... So a thorough write up<br>
+ research, instead of just yelling 'there are import scripts online<br>
available to move issues/code/CI/Webhooks/Wiki/* ....'<br>
<br>
My conclusions:<br>
- nothing will change in a short term now, unless Github is changing in<br>
a negative way<br>
- it is wise to keep doing research/experiments to alternative services<br>
- if something is missing in the wiki page: add it<br>
- it is wise to keep the use of (free) services modular, so moving<br>
(parts of) our infrastructure to other/own services stays feasible<br>
- we have a good running (rather complex) infrastructure currently.<br>
Changing it will cost a lot of development time, which then is not going<br>
to be used in debugging/coding/features).<br>
<br>
Happy coding/debugging/QGISsing!<br>
<br>
Regards,<br>
<br>
Richard Duivenvoorde<br>
<span><br>
<br>
<br>
<br>
<br>
On 05-06-18 03:04, Nathan Woodrow wrote:<br>
> Remember also moving to another platform leaves some of the community<br>
> behind, so anything like this is a long term plan with migration not<br>
> just a quick over night becacuse GitHub changed ownership.<br>
> <br>
> On Tue, Jun 5, 2018 at 10:57 AM, Nyall Dawson <<a href="mailto:nyall.dawson@gmail.com" target="_blank">nyall.dawson@gmail.com</a><br>
</span><span>> <mailto:<a href="mailto:nyall.dawson@gmail.com" target="_blank">nyall.dawson@gmail.com</a><wbr>>> wrote:<br>
> <br>
> On 5 June 2018 at 10:49, Denis Rouzaud <<a href="mailto:denis.rouzaud@gmail.com" target="_blank">denis.rouzaud@gmail.com</a><br>
</span><div><div class="m_3100870232434058110h5">> <mailto:<a href="mailto:denis.rouzaud@gmail.com" target="_blank">denis.rouzaud@gmail.c<wbr>om</a>>> wrote:<br>
> > Hi all,<br>
> ><br>
> > Just to bring a bit more context to our project...<br>
> ><br>
> > Decision has been taken during Madeira HF to move to Gitlab.<br>
> <br>
> I realise that, and am happy to go along with this group decision<br>
> *when it's all proven possible and is ready to go*. But the ownership<br>
> of GitHub should have no bearing whatsoever on this discussion. We<br>
> move when (and if) we can without any regressions, and not on an<br>
> accelerated timeline because of this news.<br>
> <br>
> > Original reason was the move of the tbug tracker from Redmine to Github.<br>
> > Many raised their voices for Gitlab and decision was taken to see if it is<br>
> > feasible and reasonnable to move everything at once to Gitlab (code,<br>
> > tracker, CI).<br>
> > Vincent proposed to establish a wiki page for listing all the issues<br>
> > <a href="https://github.com/qgis/QGIS/wiki/QGIS-Platform-migration-plan" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS/w<wbr>iki/QGIS-Platform-migration-pl<wbr>an</a><br>
> <<a href="https://github.com/qgis/QGIS/wiki/QGIS-Platform-migration-plan" rel="noreferrer" target="_blank">https://github.com/qgis/<wbr>QGIS/wiki/QGIS-Platform-<wbr>migration-plan</a>><br>
> > There is a proposal in the grant program for doing the migration, but it is<br>
> > not really clear to me if this also integrate the CI (or only the code/bug<br>
> > tracker) part which might be very tedious.<br>
> <br>
> (My understanding is that the proposal is for prototyping this change<br>
> -- not implementing the actual change itself. Oslandia staff can<br>
> clarify here.)<br>
> <br>
> But I agree... porting the CI would be a HUGE effort. It's thanks<br>
> mostly to your and Matthias' tireless efforts that we have the<br>
> mostly-great CI setup we have today. I can't even begin to estimate<br>
> the number of volunteer weeks of development you both have sunk into<br>
> this, but my continued, wholehearted thanks are extended to you both<br>
> because of it!<br>
> <br>
> Nyall<br>
> <br>
> ><br>
> > I don't think today's news is affecting our situation, despite our<br>
> personnal<br>
> > relation with MS ;)<br>
> ><br>
> > Best wishes,<br>
> > Denis<br>
> ><br>
> > Le lun. 4 juin 2018 à 20:26, Nathan Woodrow <<a href="mailto:madmanwoo@gmail.com" target="_blank">madmanwoo@gmail.com</a><br>
</div></div>> <mailto:<a href="mailto:madmanwoo@gmail.com" target="_blank">madmanwoo@gmail.com</a>>> a écrit :<br>
<span>> >><br>
> >> Hey,<br>
> >><br>
> >> IMO that would be a silly move for no added benefit and a lot of<br>
> pain. MS<br>
> >> now is not the MS of old, they are not the open source haters of<br>
> the Ballmer<br>
> >> years like they used to be. I strongly suggest we stay where we<br>
> are and not<br>
> >> react like that for this. I trust MS over most companies that<br>
> could have<br>
> >> bought it (if it was Oracle you would have had my support) and I<br>
> suspect it<br>
> >> will lead to a lot of good things in the future.<br>
> >><br>
> >> I am ok to move to other platforms in future if we need but<br>
> jumping ship<br>
> >> just because MS now own it is not a good reason to move.<br>
> >><br>
> >> - Nathan<br>
> >><br>
> >> On Tue, Jun 5, 2018 at 10:19 AM, Paolo Cavallini<br>
</span>> <<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a> <mailto:<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a>><wbr>><br>
<span>> >> wrote:<br>
> >>><br>
> >>> Hi all.<br>
> >>> Just read about ms buying GH. Maybe we should react reasonably fast?<br>
> >>> I'd be in favour of migrating to gitlab, preferably on our server.<br>
> >>> Opinions?<br>
> >>> Cheers.<br>
> >>> --<br>
> >>> Sorry for being short<br>
> >>> ______________________________<wbr>_________________<br>
> >>> Qgis-psc mailing list<br>
</span>> >>> <a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.org</a> <mailto:<a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.o<wbr>rg</a>><br>
> >>> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-psc</a><br>
<span>> <<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mail<wbr>man/listinfo/qgis-psc</a>><br>
> >><br>
> >><br>
> >> ______________________________<wbr>_________________<br>
> >> Qgis-psc mailing list<br>
</span>> >> <a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.org</a> <mailto:<a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.o<wbr>rg</a>><br>
> >> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-psc</a><br>
<span>> <<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mail<wbr>man/listinfo/qgis-psc</a>><br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Qgis-psc mailing list<br>
</span>> > <a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.org</a> <mailto:<a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.o<wbr>rg</a>><br>
> > <a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-psc</a><br>
<div class="m_3100870232434058110HOEnZb"><div class="m_3100870232434058110h5">> <<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mail<wbr>man/listinfo/qgis-psc</a>><br>
> <br>
> <br>
> <br>
> <br>
> ______________________________<wbr>_________________<br>
> Qgis-psc mailing list<br>
> <a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-psc</a><br>
> <br>
<br>
______________________________<wbr>_________________<br>
Qgis-psc mailing list<br>
<a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-psc</a></div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
Qgis-psc mailing list<br>
<a href="mailto:Qgis-psc@lists.osgeo.org">Qgis-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-psc</a><br></blockquote></div><br></div>