<div dir="ltr"><div>We can bring it to the qgis-developer mailing list for a broader audience.</div><div><br></div><div>Alex<br> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 17, 2019 at 11:55 AM Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi folks,<br>
On a similar theme, I'm interested to know if this group would like me <br>
to take the draft "Manifesto for QGIS Docs" further?<br>
<br>
<a href="https://docs.google.com/document/d/11N5d1aBgkdQ80I7RKBlt_jx9Uk1RGsvOTeq_TSFeljA/" rel="noreferrer" target="_blank">https://docs.google.com/document/d/11N5d1aBgkdQ80I7RKBlt_jx9Uk1RGsvOTeq_TSFeljA/</a><br>
<br>
I've suggested some actions, and can help a little with setting it up, <br>
but I'm unclear who makes decisions and how decisions are made, and <br>
whether their is a desire to take things further.<br>
<br>
Is there another forum where people are talking? I would have liked to <br>
attend foss4g and met you, but that was out of my budget (considering I <br>
live on the other side of the world to most of you).<br>
<br>
Thoughts?<br>
<br>
<br>
On 17/9/19 2:19 am, Raymond Nijssen wrote:<br>
> Hi Harrissou!<br>
><br>
> How are you? Thanks for the reminder.<br>
><br>
> During the hf I've been working quite some time on the cookbook, to be <br>
> exactly on the vector-layer page I started with in A Coruna. I'm <br>
> halfway now, at the part where "Symbology" starts. Should I put it in <br>
> a branch and share it already? I kind of hope that the symbology part <br>
> will be easier and faster.<br>
><br>
> Kind regards,<br>
> Raymond<br>
><br>
><br>
> On 16-09-19 17:57, DelazJ wrote:<br>
>> Hi all,<br>
>><br>
>> The hackfest has gone for weeks, but QGIS is still there as well as <br>
>> writers and developers. So I wonder if someone had considered the <br>
>> opportunity to give a hand on any of the identified issues.<br>
>><br>
>> /NB: It could not be for the "Spare Time Inc" since we still have <br>
>> unallocated funds (and not "founds" - damn keyboard)./<br>
>><br>
>> Regards,<br>
>> Harrissou<br>
>><br>
>> Le ven. 23 août 2019 à 18:21, DelazJ <<a href="mailto:delazj@gmail.com" target="_blank">delazj@gmail.com</a> <br>
>> <mailto:<a href="mailto:delazj@gmail.com" target="_blank">delazj@gmail.com</a>>> a écrit :<br>
>><br>
>> Hi all,<br>
>><br>
>> With the QGIS Community Meeting beginning, a bunch of developers and<br>
>> writers will meet to brainstorm and improve QGIS. Here are some<br>
>> suggestions of topics (among many others) some documentation<br>
>> contributors would be REALLY interested in having a fix for. We need<br>
>> a developer to address and ease our "life" (sounds tragical enough?<br>
>> :D ). Well.<br>
>><br>
>> In short:<br>
>> 1/ *Improve the automatic creation of screenshots* [1]<br>
>> 2/ *Redirect docs links *and ensure that changing links in docs does<br>
>> *not break the help button* in application [3]<br>
>> 3/ *Document/improve the doctest architecture for PyQGIS Cookbook<br>
>> *(kind of [4])<br>
>><br>
>> For the details:<br>
>> 1/ QGIS is moving fast. Dialogs are changing at every release,<br>
>> making screenshots in the docs obsolete. There was a plan to avoid<br>
>> writers manually take each screenshot, and instead generate them in<br>
>> series, browsing tabs of a specified dialog eg. A work had been<br>
>> initiated in the QgsAppScreenshots class [1]. It could be nice to<br>
>> get more news on it.<br>
>> Incidentally, with such a feature, we can expect more translated<br>
>> screenshots (which may not be good for our server but helpful for<br>
>> non-English readers and translators).<br>
>><br>
>> 2/ Because features are getting bigger, we sometimes need to<br>
>> reorganize the chapters in documentation in order to match how<br>
>> things behave in the application and also avoid very loooong<br>
>> chapters. Moving sections or renaming them (to match their actual<br>
>> scope) breaks the Help button associated to the feature, for at<br>
>> least three releases (the next-to-be LTR and the two previous<br>
>> versions since they point to the same doc). To fix that, doc writers<br>
>> have to update the links in the code and this change only applies to<br>
>> current release(s), not for EOLed one (eg 3.6 could have more not<br>
>> working links than 3.8 or master - we have a script for checks [2]).<br>
>> We need to find a more viable way to address this issue and redirect<br>
>> requested links to their actual place in the corresponding doc.<br>
>> This issue is a long standing one that has been reported/discussed a<br>
>> couple of times already (eg [3] has some suggestions)<br>
>><br>
>> 3/ During the La Coruna hackfest, a doctest infrastructure has been<br>
>> set up to ensure code samples provided for PyQGIS Cookbook are still<br>
>> working. Months later, it looks to me like it's less used than it<br>
>> should:<br>
>> - partly, because we did not make it mandatory,<br>
>> - partly because it does not apply (or we did not figure out how?)<br>
>> in some cases. Eg it seems it does not know about iface [4]. Also<br>
>> there are test projects the system should rely on but nobody uses it<br>
>> and afaics there's no example someone not used to this could follow.<br>
>> It could be nice clarifying the system and help writers adopt it.<br>
>><br>
>> [1] <br>
>> <a href="https://github.com/qgis/QGIS/blob/master/src/app/qgsappscreenshots.h" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS/blob/master/src/app/qgsappscreenshots.h</a><br>
>> [2] <a href="https://github.com/qgis/QGIS/blob/master/scripts/chkdoclink.sh" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS/blob/master/scripts/chkdoclink.sh</a><br>
>> [3]<br>
>> <a href="https://github.com/qgis/QGIS-Documentation/pull/2258#issuecomment-352246124" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS-Documentation/pull/2258#issuecomment-352246124</a><br>
>> [4] <a href="https://github.com/qgis/QGIS-Documentation/issues/3776" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS-Documentation/issues/3776</a><br>
>><br>
>> Et voilà... Sorry to have been long. Looking forward...<br>
>> And for information, docs still have unallocated founds...<br>
>><br>
>> Happy hackfest,<br>
>> Harrissou<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Qgis-community-team mailing list for organizing community resources <br>
>> such as documentation, translation etc..<br>
>> <a href="mailto:Qgis-community-team@lists.osgeo.org" target="_blank">Qgis-community-team@lists.osgeo.org</a><br>
>> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><br>
>><br>
> _______________________________________________<br>
> Qgis-community-team mailing list for organizing community resources <br>
> such as documentation, translation etc..<br>
> <a href="mailto:Qgis-community-team@lists.osgeo.org" target="_blank">Qgis-community-team@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><br>
<br>
-- <br>
Cameron Shorter<br>
Technology Demystifier<br>
Open Technologies and Geospatial Consultant<br>
<br>
M +61 (0) 419 142 254<br>
<br>
_______________________________________________<br>
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..<br>
<a href="mailto:Qgis-community-team@lists.osgeo.org" target="_blank">Qgis-community-team@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a></blockquote></div>