[Qgis-community-team] Draft paper discussing QGIS docs

[Régis Haubourg]

Hi Cameron,
this is a tremendously valuable document you submit here. I can't agree
more on most points.
Thank you very much for this effort of putting all your recommendations
along with their context.

One thing came into my mind just now that the hackfest & foss4G sequence is
over. I think that we really need to board in new contributors (technical
writer, senior architect) physically during the next developer meeting.
All the complexity of learning our infrastructure stack and our writing
guidance can be tackled there a lot more easily.

I eared this assertion last week : "Build communities, and then you'll be
able to build project".

In our case, I would recommend that all involved parties come and join.
And again, if some can't make it for financial reasons, QGIS.org and the
OSGEO have travel grant programs.
On the behalf of the French local chapter, I think we can also participate
here.

Best regards,

Régis




Le lun. 2 sept. 2019 à 13:28, Cameron Shorter <cameron.shorter at gmail.com> a
écrit :

> Thanks for all the feedback over the last week or so. I've captured many
> of your comments, gone into deeper analysis, and added specific actions
> and roles.
>
> In what I'm now calling a manifesto I’ve:
>      Raised concerns about the sustainability of QGIS documentation,
>      Collated observations and opinions from a diverse set of contributors,
>      Described my assessment of problems, and
>      Suggested strategies and priorities for moving forward, including:
>          Engaging a community coordinator / evangelist,
>          Defining our vision and roadmap,
>          Implementing an information architecture review,
>          Engaging a trained technical writer,
>          Launch an initiative to target bringing external docs back into
> the core.
>
> Feedback welcomed. I expect to do one last tweak before publishing to my
> blog.
>
> I'm interested to know if you folks in the QGIS doc community wish to
> take this any further?
>
> Doc here:
>
> https://docs.google.com/document/d/11N5d1aBgkdQ80I7RKBlt_jx9Uk1RGsvOTeq_TSFeljA/edit#
>
> On 26/8/19 9:35 pm, Cameron Shorter wrote:
> > For those involved in QGIS docs,
> >
> > After a bit of brainstorming with Matteo about what next for QGIS
> > docs, I offered to put some ideas down into an article to give him
> > something tangible to take to the QGIS Project Steering Committee next
> > week.
> >
> > I feel my thoughts have room to be developed a bit and I'd be keen to
> > hear feedback on them before I copy to my blog at the end of this week.
> >
> >
> https://docs.google.com/document/d/11N5d1aBgkdQ80I7RKBlt_jx9Uk1RGsvOTeq_TSFeljA/edit#
> >
> >
> > Comments are preferred to track changes (which become hard to manage).
> > If you comment, please log in first so I know who said what.
> >
> --
> Cameron Shorter
> Technology Demystifier
> Open Technologies and Geospatial Consultant
>
> M +61 (0) 419 142 254
>
> _______________________________________________
> Qgis-community-team mailing list for organizing community resources such
> as documentation, translation etc..
> Qgis-community-team at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-community-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-community-team/attachments/20190902/2fedf685/attachment-0001.html>