[Qgis-community-team] 2.18 LTR Documentation

[Yves Jacolin]

Hello,

On lundi 1 mai 2017 13:55:10 CEST Alexandre Neto wrote:
> Hello Yves,
> 
> Thanks for all your work this weekend. I tried to keep up and do some work,
> but it was a family tagged weekend :-)
:))
 
> I will try to put some more work this week into solving 2.16 and 2.18
> issues.
great! 

> Do we have a hard deadline for 2.18 documentation? I would say we can keep
> work on it until 2.18 becomes LTR (June?).

No hard deadline but I am available this week and probably next week-end (May 
6-7) . So I would like to give a strong push to finalize it and start thinking 
QGIS 3.0 documentation. Even if there is some new ticket for 2.18, we can make 
the changes when they come.

Harrissou sent an email last week and I have also some concern for the 3.0, 
and I guess you have some ideas.

I will probably triggers a meeting (in june?) to discuss this topic. One 
example of work we need to focus on is the "Add layer" refactoring which will 
lead to a strong changes in the structure of the doc. So if we want to not 
have any problem on doc contribution (like conflicts), we need to plan this.

Y.


> Thanks
> 
> Alex Neto
> 
> Yves Jacolin <yjacolin at free.fr> escreveu no dia segunda, 1/05/2017 às 14:40:
> > Hello doc contributors,
> > 
> > Finishing the hackfest we are close to release the 2.18 release of the
> > QGIS
> > Documentation.
> > 
> > I planned to work on this all the week to finish my PR waiting to be
> > merged and
> > backporting to master/release_2_18, reviewing PR.
> > 
> > Are people available to help reviewing and merging PR? Are you ok to focus
> > on
> > issue in 2.16 and 2.18 milestone for this week?
> > 
> > A side note when reviewing, could you use github tools with the following:
> > 
> > 1. if you add one comment (even really smal) note the Pr as "changes
> > needed "
> > 2. if the PR is ok (not any comment) mark it as "Approved"
> > 3. if you start a review, assign the ticket to you as a reviewer and keep
> > the
> > work going as soon as the PR is merged.
> > 
> > Finally, we have 10 open issues in 2.16 and 2 in 2.18 about python
> > cookbook. I
> > am in favor to migrate them to milestone 3.0 except someone can take care
> > of
> > it soon.
> > 
> > We had also 3 ticket in 2.18 that I can take care of: #1353, #1835 and
> > #1579.
> > If you want to help working on this ticket, fell free to ask!
> > 
> > Thanks all for your help for the documentation!
> > 
> > Y._______________________________________________
> > 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 --------------
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/20170501/2308844d/attachment.sig>