<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Victor,<div><br></div><div>I have created labels in the QGIS-Documentation issue tracker for organising the issues. Unfortunately, the labels on each issue might pile up quite quickly, but I can’t see a more efficient way of doing it within the confines of the GitHub issue tracker.</div><div><br></div><div>There’s a Training Manual label, a label for each chapter, then a label for Text, Screenshots, Translation and Sample Data. Also an In Progress label.</div><div><br></div><div>This might seem like a lot (it is), but this will mean that any contributor can quickly establish whether the Text for Ch 1 is already being worked on/assigned. Or whether the screenshots for Ch 8 are already done. </div><div><br></div><div>I think we should keep the issues at as high a level as possible and use the comments and to define/discuss/notify of subtasks (e.g. typos in Ch 2). We can use GitHub’s - [ ] markdown to add subtasks to the issue’s description as subtasks are identified in the comments.</div><div><br></div><div>I hope that makes sense? Please do suggest alternatives if not.</div><div><br></div><div>George</div><div><br></div><div><br></div><div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><b>George Irwin</b><br>Project and Client Manager<br>Linfiniti Consulting</div><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><a href="http://www.linfiniti.com">http://www.linfiniti.com</a><br>+27 (0)76 013 6355<br>Skype: georgeirwin22<br><br></div></div>
</div>
<br><div><div>On 26 Nov 2013, at 09:46 , Victor Olaya <<a href="mailto:volayaf@gmail.com">volayaf@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">George<br><br>Do you plan on using anythin for organizing the work and assigning<br>tasks? Like, let's says that I want to start now to rewrite chapter 1<br>or re-do screenshots in chapter 2. How do I let others know? That<br>would be good to avoid repeated work and, specially, to know what is<br>left an what is already done.<br><br>I think we could use git hub issues in the QGIS-doc repo. I can<br>volunteer to create a list of issues with all the (many) things to do.<br><br>Cheers<br><br>2013/11/26 George Irwin <<a href="mailto:george@linfiniti.com">george@linfiniti.com</a>>:<br><blockquote type="cite">Good morning Paolo,<br><br>Thanks for the suggestion - it seems like a very good one to me (and Tim). That way we can take advantage of the Sphinx setup/theme from the word go (quite apart from the other advantages). If no-one has any objections, I think that’s what we should do?<br><br>I’ll plan to work on a branch of QGIS-Documentation - I see there is already a training_manual branch last authored a year ago by Alex Bruy. Alex - do you still have something in mind for that branch or can we replace/update?<br><br>George<br><br><br><br>On 25 Nov 2013, at 17:11 , Paolo Cavallini <<a href="mailto:cavallini@faunalia.it">cavallini@faunalia.it</a>> wrote:<br><br><blockquote type="cite">-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>Il 25/11/2013 11:19, George Irwin ha scritto:<br><br><blockquote type="cite">My first task is to start work on porting the QGIS Training Manual to QGIS 2.0.<br></blockquote><br><blockquote type="cite">As an aside, I plan to work in a branch of the<br>repository on github, with nightly builds pushed to an accessible server - advice<br>on this front also welcome!<br></blockquote><br>IMHO better to put it in<br><a href="https://github.com/qgis/QGIS-Documentation">https://github.com/qgis/QGIS-Documentation</a><br>or some branch of it, from the beginning.<br>better integrating it earlier than later (which often translates into "never").<br>I'll be glad of collaborating, thiugh my time is severely limited.<br>all the best.<br>- --<br>Paolo Cavallini - www.faunalia.eu<br>Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html<br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.15 (GNU/Linux)<br>Comment: Using GnuPG with Icedove - http://www.enigmail.net/<br><br>iEYEARECAAYFAlKTaLgACgkQ/NedwLUzIr7MtwCeKYV6xztlw+z8kHq2BIBWCfSL<br>KNYAn0UDL8olEq00v9lSGOxnCcUreDNu<br>=ccEs<br>-----END PGP SIGNATURE-----<br>_______________________________________________<br>Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..<br>Qgis-community-team@lists.osgeo.org<br>http://lists.osgeo.org/mailman/listinfo/qgis-community-team<br></blockquote><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">Qgis-community-team@lists.osgeo.org</a><br>http://lists.osgeo.org/mailman/listinfo/qgis-community-team<br></blockquote></blockquote></div><br></div></body></html>