<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="">Very well said Andrea, and I can back this up with very similar experiences from when the OpenLayers project moved to Github.<div class=""><br class=""></div><div class="">That said, if OSGeo considers setting up a Git infrastructure, please keep an alternative in mind: pay for an OSGeo Github account for projects that want to use Git. Will burn some money, but won't burn out volunteers who have to keep OSGeo's own infrastructure up and running. See <a href="https://github.com/locationtech" class="">https://github.com/locationtech</a> as an example.</div><div class=""><br class=""></div><div class="">Andreas.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 18 Oct 2015, at 08:41, Andrea Aime <<a href="mailto:andrea.aime@geo-solutions.it" class="">andrea.aime@geo-solutions.it</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<div class="">just wanted to chime in saying that if OSGeo starts setting said guidelines,</div><div class="">it should also have some benefits comparison so that projects can</div><div class="">see what they might not get by avoiding Github.</div><div class=""><br class=""></div><div class="">In particular, looking at GeoServer experience from the switch, it's rather</div><div class="">evident we got more people contributing right the moment we did the</div><div class="">switch, here is the contributors per month diagram, the red line</div><div class="">is the date we switched from svn to GitHub:</div><div class=""><br class=""></div><div class=""><span id="cid:ii_150799ef0bcc4d5e"><Selezione_095.png></span><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Most of this is due to two factors:</div><div class="">- availability of pull requests (which I believe you can get with other tools too)</div><div class="">- critical mass on the platform (which arguably you will not get an a OsGeo hosting)</div><div class=""><br class=""></div><div class="">There is however a downside of that, most of these contributions are "one time gigs",</div><div class="">people help addressing the particular pitfall concerning them and then they move on:</div><div class="">github did not change the number of core developers, it just increased a lot the</div><div class="">number of other contributors.</div><div class=""><br class=""></div><div class="">There is another benefit of moving to Github, which is build checks on pull requests,</div><div class="">we now have Travis (Linux, OSX) building all pull requests and running the test suite against</div><div class="">them, so we instantly know if the change breaks tests or not, and we planning on adding</div><div class="">test coverage checks (Coveralls, already used by OpenLayers for example) and Windows builds </div><div class="">(already used by MapServer for example).</div><div class=""><br class=""></div><div class="">This kind of automation is also rather beneficial to filter our bad contributions... which is</div><div class="">the dark side of lower contribution barrier, core devs have to spend quite some time evaluating</div><div class="">pull requests... but ending up with a long queue of them gives a bad impression about the project</div><div class="">openness. So yeah, another bit to consider I guess, is the project ready to take on them?</div><div class=""><br class=""></div><div class="">So.... I'm not saying "everybody move to github" but I believe the above should be</div><div class="">part of the many considerations made when evaluating a move to a different version control.</div><div class=""><br class=""></div><div class="">Cheers</div><div class="">Andrea</div><div class=""><br class=""></div><div class="gmail_extra">-- <br class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">==</div><div class="">GeoServer Professional Services from the experts! Visit</div><div class=""><a href="http://goo.gl/it488V" target="_blank" class="">http://goo.gl/it488V</a> for more information.</div><div class=""><span style="font-size:12.8000001907349px" class="">==</span><br class=""></div></div><div class=""><br class=""></div></div><div class="">Ing. Andrea Aime <br class=""></div><div class="">@geowolf</div><div class="">Technical Lead</div><div class=""><br class=""></div><div class="">GeoSolutions S.A.S.</div><div class="">Via Poggio alle Viti 1187</div><div class="">55054 Massarosa (LU)</div><div class="">Italy</div><div class="">phone: <a href="tel:%2B39%200584%20962313" value="+390584962313" target="_blank" class="">+39 0584 962313</a></div><div class="">fax: <a href="tel:%2B39%200584%201660272" value="+3905841660272" target="_blank" class="">+39 0584 1660272</a></div><div class="">mob: <a href="tel:%2B39%20%C2%A0339%208844549" value="+393398844549" target="_blank" class="">+39 339 8844549</a></div><div class=""><br class=""></div><div class=""><a href="http://www.geo-solutions.it/" target="_blank" class="">http://www.geo-solutions.it</a></div><div class=""><a href="http://twitter.com/geosolutions_it" target="_blank" class="">http://twitter.com/geosolutions_it</a></div><div class=""><br class=""></div><div class=""><p class=""><span lang="IT" class=""><font size="1" class=""><b class="">AVVERTENZE AI SENSI DEL D.Lgs. 196/2003</b></font></span></p><p class=""><span lang="IT" class=""><font size="1" class="">Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.</font></span></p><div class=""><span lang="IT" class=""><font size="1" class=""> </font></span><br class="webkit-block-placeholder"></div><p class=""><font size="1" class="">The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.</font></p></div><div class=""><br class=""></div><div class="">-------------------------------------------------------</div></div></div></div></div></div></div></div></div>
</div></div>
_______________________________________________<br class="">Discuss mailing list<br class=""><a href="mailto:Discuss@lists.osgeo.org" class="">Discuss@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/discuss</div></blockquote></div><br class=""></div></body></html>