<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi All<div class=""><br class=""></div><div class=""><br class=""></div><div class="">A couple of notes from me from the meeting to add to Andreas and Richard's comments:</div><div class=""><br class=""></div><div class="">* We looked at the GitLab issue tracker - the functionality seems close to GitHub's tracker so no category support. This is a blocker for some.</div><div class="">* Until someone has complete and working migration to GitHub or GitLab, the option should be considered off the table since losing our history was considered a blocker.</div><div class=""><br class=""></div><div class="">Please consider the Redmine upgrade an interim solution which gives us:</div><div class=""><br class=""></div><div class="">* Redmine updated to the latest version with improved functionality</div><div class="">* Getting ourselves off the OSGEO authentication framework so we can get rid of the mantra etc. experience</div><div class="">* Hosting on a new server with SSD drives etc and hosted in europe will make the site much more responsive</div><div class="">* Using oauth authentication means you should be able to log in with your existing credentials from GitHub</div><div class=""><br class=""></div><div class="">In the process we are also streamlining things to get rid of the WIKI and other hosted projects on redmine so that when we do eventually do a complete migration we don't have anything to deal with.</div><div class=""><br class=""></div><div class="">In summary it is a step forward, maybe not the step we all wanted, but it is pragmatic and paves the way for full migration into a unified platform (GitHub or GitLab) later when someone has stepped up to the plate to support doing a complete migration.</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><blockquote type="cite" class="">On 27 Aug 2016, at 2:31 PM, Richard Duivenvoorde <<a href="mailto:rdmailings@duif.net" class="">rdmailings@duif.net</a>> wrote:<br class=""><br class="">On 26-08-16 23:03, Denis Rouzaud wrote:<br class=""><blockquote type="cite" class="">Hi all,<br class=""><br class="">Being part of the unhappy, I would like to ask if you have considered<br class="">running our own gitlab instance or using a gitlab service?<br class=""><br class="">To me integrated solution should be a hard requirement.<br class=""><br class="">If we have to maintain something like Redmine, why not gitlab. It seems<br class="">you can categorize issues.<br class=""></blockquote><br class="">To add some extra info:<br class=""><br class="">- we put effort in porting the existing issues to github (given the<br class="">precondition we want to keep full history with such a move, and not<br class="">loose information). But failed both in time and complexity, and<br class="">everybody was 'waiting' on a move ...<br class=""><br class="">- also administration/updating the running service was an issue in this.<br class="">Because of the old version of the OS it was not so easy to update<br class="">Redmine, because of the old verson of Redmine we have a security issue<br class="">AND the redmine2github scripts that we found on internet did not work<br class="">with this older redmine version...<br class=""><br class="">So having a fast and uptodate OS now, with a Redmine that is easily<br class="">updatable (apt-get update) we think this is the best step for now.<br class="">Github Integration I think is doable with the plugins, webhooks we use now.<br class=""><br class="">As Gitlab is not in the repo's we would have to install our own, AND we<br class="">also were not able to recover the issues.<br class=""><br class="">Now that it looks that we can at least move all our issues + info to an<br class="">up to date OS/Redmine version, maybe somebody can do some testing to see<br class="">if he/she is able to use newer 'export/import' scripts available... But<br class="">note that you VERY early hit in Github throtteling issues....<br class=""><br class="">So: please bear with us for now, and if we have the new Redmine running<br class="">(it is at least very fast!), we can always see if there is another<br class="">alternative, given the precondition that we want to pull all info over<br class="">to another 'system'... we 'just' need somebody to do it :-)<br class=""><br class="">Regards,<br class=""><br class="">Richard<br class=""><br class=""><br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">Qgis-developer mailing list<br class=""><a href="mailto:Qgis-developer@lists.osgeo.org" class="">Qgis-developer@lists.osgeo.org</a><br class="">List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer<br class="">Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer<br class=""></blockquote><br class=""><div class=""><span><img height="65" width="59" apple-inline="yes" id="0B73A515-2C79-4167-8D3D-120C409E3113" apple-width="yes" apple-height="yes" src="cid:879A6E78-CA46-47B2-AA0E-1810BD833229" class=""></span><br class=""><br class=""><br class="">---<br class=""><br class="">Tim Sutton<br class="">QGIS Project Steering Committee Chair<br class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a><br class=""><br class=""><br class=""><br class=""></div><br class=""></div></body></html>