[Qgis-community-team] 2.18 LTR Documentation

[Yves Jacolin]

Alexandre,

On mercredi 14 juin 2017 23:05:49 CEST Alexandre Neto wrote:
> Harrissou et al.,
> 
> Sorry for the silence, but this threads are so big that I never find time
> to read and answer properly.
> 
> Harrissou, thanks for gathering all that ideas and TODOs. Most of them are
> in fact very important for 3.x (I dare to say 3.2 as I don't think we
> should do an official doc release for 3.0).
> 
> Our biggest problem is (still) not having enough human power. We are barely
> able to keep the User's Manual updated on time. Training manual probably is
> few versions behind and PyQGIS cook book I have no idea. So, IMHO, we
> should focus our efforts on what's more important. And for me it's the User
> manual. Which I consider to be mandatory to deliver. The other two are nice
> to have. For the cook book we need developers to take care of it, and the
> training, we need trainers (people o rely on it to give training) to take
> care of it.
> 
> I say we should not ambiss to change 2.18 structure. Nor to make it
> perfect. I would vote for setting a deadline and release the docs, even if
> something was not completed. July would be ok for me.
> 
> From that point on, we can focus on 3.x users manual and all the
> improvements we would like to do. Planning the docs Restructuring would be
> my top priority as we might not be  able to do it again soon​ (to not break
> help links).
> 
> My second priority would go to update the sphinx / bootstrap etc versions.
> 
> Assuming that all tasks make sense, before even go to the PSC, I would add
> a column with the needed (human) resources for each task. That will
> probably determine what is going forward and what is not.
> 
> I would not rush in converting the tasks into github issues for now. a wiki
> or Google Doc may be more practical as we can see the all picture easily.
> And we can elaborate a final document to send to others.

I agree with all above except this part: I am not sure that a wiki or Google 
doc will give you a nice picture of task to do. We can filter issue easily in 
"project" and/or milestone.

Y.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.osgeo.org/pipermail/qgis-community-team/attachments/20170615/c500203d/attachment.sig>