<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Jürgen<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 12 Apr 2020, at 00:29, Jürgen E. Fischer <<a href="mailto:jef@norbit.de" class="">jef@norbit.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Tim,<br class=""><br class="">On Sat, 11. Apr 2020 at 00:09:45 +0100, Tim Sutton wrote:<br class=""><blockquote type="cite" class="">Rationale: Free software should be the first choice for all the tools we use.<br class="">We should choose proprietary alternatives only when it is proven that free<br class="">software fails to provide a reasonable solution. The PSC should vote in case<br class="">a proprietary solution is suggested.<br class=""><br class="">With<br class=""><br class="">Proposal: As a matter of policy when deploying software tools to manage the<br class=""><a href="http://QGIS.org" class="">QGIS.org</a> project, we should consider licensing, functionality, convenience,<br class="">effort, cost, time, available volunteers, security, privacy, how much effort<br class="">is required to maintain the solution. Given two solutions that appear<br class="">satisfactory with regards to these requirements, one being FOSS and one being<br class="">proprietary, we should of make use of the FOSS solution in preference to the<br class="">proprietary solution.<br class=""></blockquote><br class=""><blockquote type="cite" class="">---<br class=""></blockquote><br class=""><blockquote type="cite" class="">Please vote here if you are OK with these proposed changes and I will be<br class="">happy to submit a pull request.<br class=""></blockquote><br class="">-1 I believe the point of the resolution is to emphasize that using free<br class=""> software should be the rule and using proprietary software should be an<br class=""> exception.<br class=""><br class=""> But I think "it is proven" is too strong as it suggests big effort<br class=""> and could be replaced with "we agree".<br class=""><br class=""> All other points and more are IMHO covered by "reasonable solution".<br class=""><br class=""> Also not sure if that mandatory PSC vote is required as that would also<br class=""> require voting in case there obviously is no free alternative to some<br class=""> proprietary tool we want to use.<br class=""><br class=""></div></div></blockquote><div><br class=""></div><div>Thanks for your reply Jürgen!</div><div><br class=""></div><div>Well the reason I raised this it that I don’t think we all share the same definition of what a ‘reasonable solution’ is - IMHO it is better to be explicit rather than implicit. I actually don’t think my proposed update to the motion goes far enough in terms of being explicit:</div><div><br class=""></div><div>It would be reassuring to know that this is not a pre-cursor to a major disruption to the infrastructure of the project, where we land up running around spending a lot of time, project funds and effort trying to replace tools that already work for us with new things. And if that is the plan (as appears to be the case from Paolo’s list of replacement candidates) who will do the migrations to the new platform and manage the transition smoothly, and at what cost?</div><div><br class=""></div><div>Another concern I have is what we consider acceptable FOSS licenses here. From prior discussions on this list there are different outlooks on what acceptable licenses are - will we accept BSD? MIT? GPL with amendments, dual licensed software? Hosted buy third party versus self-hosted? Hosted FOSS by third party with a cost (e.g. Loomio, Wordpress). </div><div><br class=""></div><div>For me the proposal is still half-baked until these things are all well defined. Let me stress finally that I have absolutely no objection to using FOSS for our infrastructure, I have objection to taking our project funds and energies and putting them into this migrating stuff over to FOSS when the current solution already works well for us, instead of using our time and funds for actually useful stuff like supporting bug fixes, getting QGIS in front of more users etc. So let’s make the plan clear, the responsibilities clear, the process non-disruptive, the licensing requirements as to what licenses and hosting arrangements clear, the cost implications clear, and then I am "on-team" too.</div><div><br class=""></div><div>Regards</div><div><br class=""></div><div>Tim</div><div><br class=""></div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">Jürgen<br class=""><br class="">-- <br class="">Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31<br class="">Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50<br class="">Software Engineer D-26506 Norden <a href="https://www.norbit.de" class="">https://www.norbit.de</a><br class="">QGIS release manager (PSC) Germany IRC: jef on FreeNode<br class="">_______________________________________________<br class="">Qgis-psc mailing list<br class=""><a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/qgis-psc</div></div></blockquote></div><br class=""><div class="">
<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none; font-size: 18px;"> </span><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;"><span><img apple-inline="yes" id="6B2B8DE6-FEBC-4B29-900A-26BD2A209DCD" src="cid:B67F6A36-B856-4FD5-91BC-5BDE8990D373" class=""></span><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><br class="Apple-interchange-newline"><br class="Apple-interchange-newline"><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">---</div><div style="font-weight: normal;" class=""><br class=""></div><div class=""><b class="">Tim Sutton</b></div><div style="font-weight: normal;" class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div style="font-weight: normal;" class=""><br class=""></div></div><br class="Apple-interchange-newline" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal;"><br class="Apple-interchange-newline" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;">
</span></div>
<br class=""></body></html>