<div dir="ltr">
<div>Hi all,</div><div><br></div><div>Matteo, you were quicker than me.
Since I won't be at the hackfest, i was preparing a kind of wishlist;
They are not necessarily things to discuss (some of them have been long
standing and sometimes longly debated) but I hope most of them get done.
HF is unfortunately the single moment where many people will get
involved in docs improvement so let's take that advantage to fix things
that complicate doc writers life.</div><div><br></div><div>
#. Fix the help button in QGIS being broken each time the link in the
doc has moved or changed a bit, with nobody noticing it: see [0] with
all the links that mention it, as places it has been rediscussed<br></div><div>
#. Review the doc site look (template, css, ) - see from [1]</div><div>
<div>#. Review the doc build instructions in the readme file of the
repository and ensure they work for all platforms (I personally abandon
doc building on Windows though it's my working env - I don't think that
travis should be the place to check our changes)<br></div><div>
<div>#. Fix script to clean the repo from obsolete/unused image files (
see [2] and some of the other backend tagged issue reports [3])<br></div><div>#. Fix automatic screenshot generation [4]</div><div>#. and, a bit aside though related to writing, Add translation guidelines for desktop translators and make them
accessible to all as a welcome message on Transifex, or in the
signature of the translation group. see [5] and a quick tip at [6] <br></div><div>#. Close 2.16 and 2.18 milestones issues<br></div><div><br></div><div>I'd
also like to react on the stale bot activation. I really don't
understand what it's needed for, if I understood the discussion that was
held at the time:</div><div>- if the PR is from a person with commit
rights, if not reviewed and IF he reminds the others but failed to get
their review (did we ever get to this?), he/she simply has to merge, no
need for a bot</div><div>- if the PR is from any other contributor,
closing it because none of the reviewers has time will simply make
people frustrated. What would have resolved the closure of the PR? What
should it resolve actually? Most of the PR allow maintainers to push
changes to them so if it's a good but abandoned PR, better keep it along
and complete and merge it when a maintainer feels interested.</div><div>For me, the problem of the queue in doc repo is not in the Pull request tab but in the Issues one.</div><div>Of
course I don't want to hijack this thread with that issue, simply
wanted to express my opinion regarding this imho risky decision.<br></div>
</div>
</div><div><br></div><div>[0] <a href="https://github.com/qgis/QGIS-Documentation/pull/2258#issuecomment-352246124">https://github.com/qgis/QGIS-Documentation/pull/2258#issuecomment-352246124</a></div><div>[1] <a href="https://github.com/qgis/QGIS-Documentation/pull/3112#issuecomment-436201322">https://github.com/qgis/QGIS-Documentation/pull/3112#issuecomment-436201322</a></div><div>[2] <a href="https://github.com/qgis/QGIS-Documentation/issues/3205">https://github.com/qgis/QGIS-Documentation/issues/3205</a><br></div><div>[3] <a href="https://github.com/qgis/QGIS-Documentation/labels/Backend">https://github.com/qgis/QGIS-Documentation/labels/Backend</a></div><div>[4] <a href="https://github.com/qgis/QGIS/pull/8041">https://github.com/qgis/QGIS/pull/8041</a></div><div>
[5] <a href="https://github.com/qgis/QGIS-Website/issues/592">https://github.com/qgis/QGIS-Website/issues/592</a><br></div><div>[6] <a href="https://github.com/qgis/QGIS/pull/9331">https://github.com/qgis/QGIS/pull/9331</a></div><div><br></div><div>Have a nice QGIS week,</div><div>Harrissou</div>
</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 5 mars 2019 à 12:30, Richard Duivenvoorde <<a href="mailto:rdmailings@duif.net">rdmailings@duif.net</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 05/03/2019 10.58, matteo wrote:<br>
> Hi guys,<br>
> <br>
> I want to propose the doc writer and contributors have a meeting during<br>
> the hackfest. Several topics to discuss, here a short list on my mind:<br>
> <br>
> * branching the new LTR release<br>
> * direct integration of transifex and github [0]<br>
> * PR cue (stale bot...)<br>
> * helping new contributors<br>
> * cleaning issues list<br>
> * pyqgis cookboox (integration of pyqgis samples of Thomas Gratier [1]<br>
> <br>
> Other ideas?<br>
> <br>
> Who is coming to the Hackfest?<br>
<br>
Hi Mattea,<br>
<br>
I am, and I'm in the workshop area now.<br>
<br>
Yep, let's just plan a meeting, maybe Thursday morning?<br>
<br>
After showing somebody the trick to write some docs I'm even more<br>
convinced that we REALLY REALLY need the help of developers.<br>
I do not want to point to somebody, but just open some of the doc<br>
writer issues:<br>
<br>
<a href="https://github.com/qgis/QGIS-Documentation/milestone/10" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS-Documentation/milestone/10</a><br>
<br>
then try to place yourself in the shoes of a (less technical) doc writer<br>
and try to figure out what is meant by the short sentence OR what<br>
exactly is build... OR how to create a quick screenshot (without the<br>
sometimes specially prepared data the developer had).<br>
<br>
I do not want to sound negative, but I think it's almost not doable.<br>
<br>
Doc writer really need more help/information/screenshots to get going.<br>
<br>
But let's discuss in the meeting (but I hope also some devs read this :-) )<br>
<br>
Regards,<br>
<br>
Richard Duivenvoorde<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>