<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>
<div>I agree with this also.</div><div><br></div><div>Y.</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:88%;color:#364f67" dir="auto">Envoyé depuis mon appareil Samsung</div></div><br><br>-------- Message d'origine --------<br>De : Paolo Cavallini <cavallini@faunalia.it> <br>Date : 07/03/2017 07:52 (GMT+01:00) <br>À : qgis-developer@lists.osgeo.org <br>Objet : Re: [Qgis-developer] 3.0 Documentation and branching <br><br>Il 07/03/2017 05:58, Nyall Dawson ha scritto:<br><br>> I think a better solution is to hook into the current<br>> [FEATURE]/[NEEDS-DOCS] hooks which auto-open issues on the<br>> documentation repo. We could *require* that all developers who push a<br>> new feature commit have to post on the corresponding documentation<br>> auto-opened issue with at least very rough notes about how the feature<br>> is supposed to work. The documentation team could then polish these<br>> up, add screenshots, etc (and merge when the timing is right for the<br>> team). This would also keep things as easy as possible for devs so<br>> that they (*cough*... i mean me *cough*) have no excuse not to do it!<br><br>Agreed fully.<br>Thanks Nyall.<br>-- <br>Paolo Cavallini - www.faunalia.eu<br>QGIS & PostGIS courses: http://www.faunalia.eu/training.html<br>https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis<br>_______________________________________________<br>Qgis-developer mailing list<br>Qgis-developer@lists.osgeo.org<br>List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer<br>Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer</body></html>