<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 10 Mar 2016, at 12:37, Denis Rouzaud <<a href="mailto:denis.rouzaud@gmail.com" class="">denis.rouzaud@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
<font size="-1" class=""><font face="Verdana" class="">I believe it would require a
final approval of moving to github.<br class="">
There were some voices (not mine ;) ) against it!<br class="">
<br class=""></font></font></div></div></blockquote><div><br class=""></div><div>The only reason I can see that people might have for not moving to GitHub is that the GitHub platform is not FOSS. Personally I don’t think that is enough reason not to take advantage of the platform that GitHub provides. While of course it would be nicer if it was FOSS, I think the benefits provided by GitHub outweigh the cons. Were there any other noteworthy reasons?</div><div><br class=""></div><div>Regards</div><div><br class=""></div><div>Tim</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class=""><font size="-1" class=""><font face="Verdana" class="">
From my understanding in Las Palmas, the idea was<br class="">
* move to github if we can port<br class="">
* updagre redmine otherwise<br class="">
<br class="">
Moving the whole code hosting was discouraged because many
plugins are hosted on github, people have their account there
and so on.<br class=""></font></font></div></div></blockquote><div><br class=""></div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class=""><font size="-1" class=""><font face="Verdana" class="">
<br class="">
<br class="">
<br class="">
<br class="">
</font></font>
<div class="moz-cite-prefix">On 03/10/2016 11:28 AM, Luigi Pirelli
wrote:<br class="">
</div>
<blockquote cite="mid:CAFO80_oCRCkygcYYMcSYJ04kD4m2XFC8gWchd=cm6YTSpd_o+w@mail.gmail.com" type="cite" class="">
<pre wrap="" class="">Can be porting a GSoC proposal?
Luigi Pirelli
**************************************************************************************************
* Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com
* LinkedIn: <a class="moz-txt-link-freetext" href="https://www.linkedin.com/in/luigipirelli">https://www.linkedin.com/in/luigipirelli</a>
* Stackexchange: <a class="moz-txt-link-freetext" href="http://gis.stackexchange.com/users/19667/luigi-pirelli">http://gis.stackexchange.com/users/19667/luigi-pirelli</a>
* GitHub: <a class="moz-txt-link-freetext" href="https://github.com/luipir">https://github.com/luipir</a>
* Mastering QGIS:
<a class="moz-txt-link-freetext" href="https://www.packtpub.com/application-development/mastering-qgis">https://www.packtpub.com/application-development/mastering-qgis</a>
**************************************************************************************************
On 10 March 2016 at 09:55, Denis Rouzaud <a class="moz-txt-link-rfc2396E" href="mailto:denis.rouzaud@gmail.com"><denis.rouzaud@gmail.com></a> wrote:
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">
On 03/10/2016 09:25 AM, Vincent Picavet (ml) wrote:
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">Hello,
On 09/03/2016 19:50, Tim Sutton wrote:
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">Hi
</pre>
</blockquote>
<pre wrap="" class="">[...]
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">Yes really great news! +1 for moving to GitHub issues ASAP.
</pre>
</blockquote>
<pre wrap="" class="">Do we have a plan to try not breaking tickets references in commit
entries ? Any idea on how to handle this issue ?
</pre>
</blockquote>
<pre wrap="" class="">Some were proposing to use github API to port all the issues to github
using the same order.
Since github uses the same increment for issues and PR, we would only
miss references to the first 3000 issues (which would point to existing
PRs).
Hence, the idea would be to port issues from number_of_github_PR + 1.
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">Vincent
_______________________________________________
Qgis-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
</pre>
</blockquote>
<pre wrap="" class="">_______________________________________________
Qgis-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
</pre>
</blockquote>
</blockquote>
<br class="">
</div>
_______________________________________________<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</div></blockquote></div><br class=""><div class="">
<span><img height="60" width="60" apple-inline="yes" id="E3884C0D-5B0D-4E0E-A4D4-FBD69A6C93E6" apple-width="yes" apple-height="yes" src="cid:DDEF9B12-67C3-4498-BD7D-EC3563CC35A4" class=""></span><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class="Apple-interchange-newline"><br class=""></div><div class="">Tim Sutton</div><div class="">QGIS Project Steering Committee Member</div><div class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div class=""><br class=""></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class="Apple-interchange-newline">
</div>
<br class=""></div></body></html>