<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></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 01 Feb 2017, at 1:02 PM, Matthias Kuhn <<a href="mailto:matthias@opengis.ch" class="">matthias@opengis.ch</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi all,<br class=""><br class="">I am not a member of the PSC and was mostly just a spectator in the<br class="">thread linked below. Please let me share my thoughts nonetheless.<br class=""></div></div></blockquote><div><br class=""></div><div>Just to emphasize again that anyone is welcome to post here, so thanks for sharing your thoughts.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">I think the whole "issue" is based on a series of misunderstandings and<br class="">I would be very glad if we could flatten the waves and take this<br class="">decision based on arguments instead of escalating it by requesting a PSC<br class="">decision.<br class=""></div></div></blockquote><div><br class=""></div>I'm ok with anyone asking the PSC for input if they feel the need for it. Generally I think the PSC is not the place to discuss technical details so I won't raise the pro's and cons of having the Resource Sharing Plugin in core. </div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">First off, as far as I could see, everybody liked the outcome of the<br class="">GSOC and everyone is happy with the outcome. I don't think the plugin or<br class="">the project is at risk wherever it may live, be it in core or as a<br class="">separate plugin. The job done by Akbar and Alesandro is of great<br class="">importance and it's going to be even more important the more resources<br class="">are in there. Thank you very much for the amazing job!<br class=""><br class="">Apparently, the clearance to 1) port this to a core plugin and 2) which<br class="">parts of it and 3) the future of core plugins per se has not been<br class="">understood the same way by all parties. A merge which was done in an<br class="">unfortunately quick timeframe caused different parties to react just as<br class="">quickly.</div></div></blockquote><br class=""><div>I do think that a lot of the discussion around this merge could have been avoided if we follow more strict peer review processes: Require a pull request for each new feature and require third party peer review approval for each pull request. I would argue also that for larger features we should also expect a large enough time window that others can test out the new functionality before it gets merged.That will ensure that others in the developer community have a fair chance to review incoming code, and make their arguments for or against its inclusion. GitHub already includes very nice code review tools so my proposal is that we just enable them and prevent similar issues occurring in the future. We do also have code maintainers (we need more!)[1] that should be given an opportunity to review changes to the parts of the code base they maintain. </div><div><br class=""></div><div><br class=""></div><div>I will take the question about the enabling of GitHub code reviews over to the dev list....</div><div><br class=""></div><div>Regards</div><div><br class=""></div><div>Tim</div><div><br class=""></div><div>[1] <a href="https://www.qgis.org/en/site/getinvolved/governance/governance.html#code-maintainers" class="">https://www.qgis.org/en/site/getinvolved/governance/governance.html#code-maintainers</a></div><div><br class=""></div><div><br class=""></div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">All the best<br class="">Matthias<br class=""><br class=""><br class="">On 02/01/2017 11:30 AM, ElPaso wrote:<br class=""><blockquote type="cite" class="">Hi,<br class=""><br class="">I've always been convinced that this plugin for "sharing" was a<br class="">fundamental feature to share symbology assets (and not only them!!!), so<br class="">fundamental that having it as a core plugin was taken for granted.<br class=""><br class="">If the problem is the lack of quality of the plugin, well I can take it<br class="">and admit that we've failed the GSOC. No problems with that.<br class=""><br class=""><br class="">But now I start thinking that I might have completely misunderstood the<br class="">importance of the plugin in the first place.<br class=""><br class=""><br class="">Can I ask the PSC to take (or confirm) position on this topic?<br class=""><br class="">See: <a href="https://github.com/qgis/QGIS/pull/4087" class="">https://github.com/qgis/QGIS/pull/4087</a><br class=""><br class="">There is already enough nonsense in that thread that I don't want to<br class="">reply more, but of course it's not a +34000 lines of code PR, well, it<br class="">is if you count jquery.js, *.css, *.html and all Python ext-libs and tests.<br class=""><br class="">As for the responsibility: I take it for granted that if you commit a<br class="">feature you also "commit" to maintain it, but we are a community and we<br class="">agree to work together for the good of the project, this means that we<br class="">also agree to cooperate and help each other if needed.<br class=""><br class=""><br class="">Thanks!<br class=""><br class=""></blockquote>_______________________________________________<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><img apple-inline="yes" id="ED671F60-F289-473D-856E-9D1672C2A83F" src="cid:879A6E78-CA46-47B2-AA0E-1810BD833229" 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; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><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="">QGIS Project Steering Committee Chair</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="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: 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-stroke-width: 0px; line-height: normal;"><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; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
</div>
<br class=""></div></body></html>