[Qgis-community-team] QGIS 2.8 Documentation update - use git issues for tasks?

[Yves Jacolin]

Larissa,

The proposition was to create issue for each commit in this way we 
(documentors) can be assigned to a ticket and work on this. We can add a link 
between the issue and the pull resquest, have a proof review, etc.

Currently, taks are still in the wiki which give you some work and is not easy 
to used (slow and it is difficult to see how task are done). We can keep this 
way for the QGIS 2.8 documentation.

I am pretty sure that using git issue will improve the process. Unfortunately 
I have no skills to to the automatic magic script to add a new issue when a 
commit is done with flags [FEATURE], etc. So I can't help for this last step.

Regards,

Y.


On Thursday, February 12, 2015 15:04:30 Larissa Junek wrote:
> Hello Alexandre,
> 
> I have some ressources for contributing to the new user manual. I found
> a new list on the Manual Tasks site and completed it. Are you talking
> about git log messages (= issues in documentation)?
> 
> Just tell me if there is a new procedure for writing the manual.
> Otherwise I just go on with my work and start to include the new
> information.
> 
> Kind regards,
> Larissa
> 
> Am Thu, 22 Jan 2015 10:42:56 +0000
> 
> schrieb Alexandre Neto <senhor.neto at gmail.com>:
> > Hello all,
> > 
> > With the feature freeze near by, we will enter in documentation update
> > phase again (this time LTS :)).
> > 
> > Following Yves recommendation, will we be using git issues to track
> > tasks this time?
> > 
> > Is there a way to transform [Feature] and [gui] tags in issues in
> > documentation?
> > 
> > Thanks,
> > 
> > Alexandre Neto
> 
> _______________________________________________
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team