<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>A lot of what instigated this conversation is what PostGIS should do? stick with SVN/Trac, get rid of SVN and just move everything to GitHub, or have an OSGeo GIT and a GitHub mirror and still keep trac.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I don't think it makes sense for us to completely ditch github, but then I also think there is a downside to having github as our official repo.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Right now PostGIS is mirroring our svn repo to GitHub and we get enough pull requests from users, sometimes even big patches. So I think having a mirror on GitHub takes care of that. It's a bit extra effort to accept the pulls, but that may be a good thing as it forces us to scrutinize more. So we get the benefit of travis testing etc already.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>However I also care about package maintainers since to me they are the life and blood of PostGIS. They insure that new users have an easy time installing postgresql / postgis.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Many of them would prefer OSGEO hosting (and preferably git over svn) because why force someone to get a github account just to put in a bug report or submit a patch. If they should be forced to create an account with a faceless organization, it should be OSGeo </span><span style='font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>, not github.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Relevant notes from Package maintainers:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><a href="https://lists.osgeo.org/pipermail/postgis-devel/2015-October/025361.html">https://lists.osgeo.org/pipermail/postgis-devel/2015-October/025361.html</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><a href="https://lists.osgeo.org/pipermail/postgis-devel/2015-October/025359.html">https://lists.osgeo.org/pipermail/postgis-devel/2015-October/025359.html</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>We also have a lot of users who just report bugs. I'm not so sure they have github accounts or care to. Bug reports are more important to me than new contributions as every new contribution requires some level of stress testing.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Regina Obe<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>PostGIS PSC member<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Windows PostGIS Stackbuilder Maintainer<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Discuss [mailto:discuss-bounces@lists.osgeo.org] <b>On Behalf Of </b>Andreas Hocevar<br><b>Sent:</b> Sunday, October 18, 2015 3:08 AM<br><b>To:</b> OSGeo Discussions <discuss@lists.osgeo.org><br><b>Subject:</b> Re: [OSGeo-Discuss] OSGeo guidelines for code hosting ?<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'>Very well said Andrea, and I can back this up with very similar experiences from when the OpenLayers project moved to Github.<o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>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">https://github.com/locationtech</a> as an example.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Andreas.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-left:.5in'>On 18 Oct 2015, at 08:41, Andrea Aime <<a href="mailto:andrea.aime@geo-solutions.it">andrea.aime@geo-solutions.it</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-left:.5in'>Hi,<o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'>just wanted to chime in saying that if OSGeo starts setting said guidelines,<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>it should also have some benefits comparison so that projects can<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>see what they might not get by avoiding Github.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>In particular, looking at GeoServer experience from the switch, it's rather<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>evident we got more people contributing right the moment we did the<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>switch, here is the contributors per month diagram, the red line<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>is the date we switched from svn to GitHub:<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><Selezione_095.png><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Most of this is due to two factors:<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>- availability of pull requests (which I believe you can get with other tools too)<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>- critical mass on the platform (which arguably you will not get an a OsGeo hosting)<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>There is however a downside of that, most of these contributions are "one time gigs",<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>people help addressing the particular pitfall concerning them and then they move on:<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>github did not change the number of core developers, it just increased a lot the<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>number of other contributors.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>There is another benefit of moving to Github, which is build checks on pull requests,<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>we now have Travis (Linux, OSX) building all pull requests and running the test suite against<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>them, so we instantly know if the change breaks tests or not, and we planning on adding<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>test coverage checks (Coveralls, already used by OpenLayers for example) and Windows builds <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>(already used by MapServer for example).<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>This kind of automation is also rather beneficial to filter our bad contributions... which is<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>the dark side of lower contribution barrier, core devs have to spend quite some time evaluating<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>pull requests... but ending up with a long queue of them gives a bad impression about the project<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>openness. So yeah, another bit to consider I guess, is the project ready to take on them?<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>So.... I'm not saying "everybody move to github" but I believe the above should be<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>part of the many considerations made when evaluating a move to a different version control.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Cheers<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Andrea<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>-- <o:p></o:p></p><div><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal style='margin-left:.5in'>==<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>GeoServer Professional Services from the experts! Visit<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><a href="http://goo.gl/it488V" target="_blank">http://goo.gl/it488V</a> for more information.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:9.5pt'>==</span><o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div></div><div><p class=MsoNormal style='margin-left:.5in'>Ing. Andrea Aime <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>@geowolf<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Technical Lead<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>GeoSolutions S.A.S.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Via Poggio alle Viti 1187<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>55054 Massarosa (LU)<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Italy<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>phone: <a href="tel:%2B39%200584%20962313" target="_blank">+39 0584 962313</a><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>fax: <a href="tel:%2B39%200584%201660272" target="_blank">+39 0584 1660272</a><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>mob: <a href="tel:%2B39%20%C2%A0339%208844549" target="_blank">+39 339 8844549</a><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><a href="http://www.geo-solutions.it/" target="_blank">http://www.geo-solutions.it</a><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><a href="http://twitter.com/geosolutions_it" target="_blank">http://twitter.com/geosolutions_it</a><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><b><span lang=IT style='font-size:7.5pt'>AVVERTENZE AI SENSI DEL D.Lgs. 196/2003</span></b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=IT style='font-size:7.5pt'>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.</span><o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'><span lang=IT style='font-size:7.5pt'> </span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span style='font-size:7.5pt'>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.</span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>-------------------------------------------------------<o:p></o:p></p></div></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal style='margin-left:.5in'>_______________________________________________<br>Discuss mailing list<br><a href="mailto:Discuss@lists.osgeo.org">Discuss@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/discuss">http://lists.osgeo.org/mailman/listinfo/discuss</a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div></div></body></html>