Hello,

Could you work like we do for QEP? i.e Write the text in a ticket, ask for 
comment and label it as finished (or to be integrated in the documentation).

I will be happy to do it (assign the ticket to me) if everybody agree with 
this process!

Pros:
* lower the barrier
* easy to comment for a (small) chapter even if this is better and easier in a 
PR for bigger chapter though
* easy also to improve some part of an existing chapter (typos, missing 
informations)

Cons:
* make sure to finalized it :)

Y.
On samedi 18 mars 2017 15:55:34 CET Richard Duivenvoorde wrote:
> And can I add the constant hard fight against fake user accounts adding
> wiki spam? (see osgeo wiki).
> 
> The workflow we have now is translatable, can be build to pdf's, is
> versioned and is continuously tested/rebuild.
> 
> Regards,
> 
> Richard
> 
> On 18-03-17 13:40, Nathan Woodrow wrote:
> > The wiki information got outdated very fast, and was also not
> > translatable easily.
> > A decision was made a while ago for official documentation should be
> > done int the same workflow
> > as the website in order to streamline that process and make sure
> > everyone is using the same tools.
> > 
> > - Nathan
> > 
> > 
> > On Sat, Mar 18, 2017 at 10:18 PM, John Hawkinson <jh...@mit.edu
> > 
> > <mailto:jh...@mit.edu>> wrote:
> >     I'm new here, so I'll ask the obvious question:
> >     
> >     Wikis are great because they lower the bar to collaboration. It's
> >     really
> >     easy to make edits and you don't have to worry about them getting
> >     approved
> >     and that's awesome. Really easy workflow, more so than github pull
> >     requests.
> >     New and potential contributors don't get discouraged.
> >     
> >     What's the reason for putting up barriers to documentation like this?
> >     
> >     Problems with spam or low quality edits? Can I find a robust
> >     discussion
> >     of the tradeoffs in the list archives?
> >     
> >     --jh...@mit.edu <mailto:jh...@mit.edu>
> >     
> >       John Hawkinson
> >     
> >     _______________________________________________
> >     Qgis-developer mailing list
> >     Qgis-developer@lists.osgeo.org <mailto:Qgis-developer@lists.osgeo.org>
> >     List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >     <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
> >     Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >     <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
> > 
> > _______________________________________________
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to