<html><head></head><body>Agreed, better make it explicit.<br>Thanks Nyall!<br><br><div class="gmail_quote">On 10 March 2020 23:55:05 CET, Nyall Dawson <nyall.dawson@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Wed, 11 Mar 2020 at 03:31, Alessandro Pasotti <apasotti@gmail.com> wrote:<br>><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">I've always felt it was an implicit agreement, but I totally agree<br>that making it explicit is a good idea.<br></blockquote><br>Yep, it's been more or less "understood" practice for some time, but<br>I'd like it to be official so there's no room for misunderstand.<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Where exactly would you suggest to add that kind of statements?<br></blockquote><br>I'd put it in a new section under<br><a href="https://docs.qgis.org/testing/en/docs/developers_guide/">https://docs.qgis.org/testing/en/docs/developers_guide/</a> Maybe<br>something like "development policies"?<br><br>We could word it something like:<br><br>"While new feature submissions are always highly appreciated, every<br>feature added to QGIS comes with an associated maintenance burden for<br>the project. Accordingly, some policies exist to avoid placing this<br>burden on the existing QGIS development team:<br>- Following any new feature development, it is the original<br>developer's (or organisations) SOLE responsibility to proactively<br>monitor and implement bug fixes relating to the new feature (or<br>regressions to other parts of QGIS which have resulted from its<br>development). This extends up to the next major QGIS release following<br>the feature being merged*. It is NOT acceptable to use QGIS.org<br>sponsored bug fixing efforts to implement these fixes. Failure to<br>provide fixes to all reasonable bug reports raised for a<br>new feature may lead to that feature being reverted prior to release.<br>- After this major release, the developer is still expected to monitor<br>the bug tracker for issues relating to their work and implement<br>reasonable fixes at their own expense.<br>"<br><br>Nyall<br><br><br>><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><br> --<br> Alessandro Pasotti<br> w3: www.itopen.it<br></blockquote><hr>QGIS-Developer mailing list<br>QGIS-Developer@lists.osgeo.org<br>List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre></blockquote></div><br>-- <br>Please excuse my brevity.</body></html>