<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Guys<div class=""><br class=""></div><div class="">Could you give me a little update on the current status so that I can report back at the next meeting in 1.5 weeks time?</div><div class=""><br class=""></div><div class="">Thanks!</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim<br class=""><div><blockquote type="cite" class=""><div class="">On 14 Mar 2016, at 09:49, Martin Dobias <<a href="mailto:martin.dobias@lutraconsulting.co.uk" class="">martin.dobias@lutraconsulting.co.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Hi all<br class="">
<br class="">
Sorry for the delayed reply, I have been offline until yesterday.<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">On 9.3.2016 05:39, Tim Sutton wrote:<br class="">
</div>
<blockquote cite="mid:439C54FE-E35D-4551-8E49-83D27E03F8E4@qgis.org" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div class="">Thanks for your patience. I’m copying you all in so
that you can virtually ‘meet’ each other. I met with the PSC
last night and the way forward is agreed. My proposal is that we
share the work between the three of you (with the possibility of
pulling in two other applicants if they are willing and we need
more help). <br class="">
</div>
</blockquote>
Thanks Tim for bringing up your proposal to PSC to get the project
going!<br class="">
<br class="">
<blockquote cite="mid:439C54FE-E35D-4551-8E49-83D27E03F8E4@qgis.org" type="cite" class="">
<div class="">The idea is that we form a small team (the four of
us for now). The first priority would be to establish the main
workflows for what we want to build which Martin would do with
some input from the rest of us as needed. Martin has been
looking at the possibility of using Breath[1] Then Martin would
step back a bit and Wes and Francisco could start wading with
the actual documentation work. How does that sound for all of
you?</div>
</blockquote>
Sounds good!<br class="">
<br class="">
I would like to finish the research on Breathe, possibly
contributing to it for the bits we will find necessary. For those
who have not heard about Breathe - it acts as a bridge between
Doxygen and Sphinx - if everything will work well, we should be able
to get the best of both worlds - comprehensive API docs generated
from source code with the power and look of Sphinx docs used for the
rest of QGIS documentation, allowing a complete blend of API docs
with the python cookbook.<br class="">
<br class="">
<blockquote cite="mid:439C54FE-E35D-4551-8E49-83D27E03F8E4@qgis.org" type="cite" class="">Assuming we are agreed, we can get started, first with
Martin designing the standard approach. The PSC has earmarked 5000
EURO of QGIS funds for the API documentation work which is not a
huge fortune, but if we make a success of it I think we will be
able to access further funding (e.g. via a funding drive) further
down the line. I would expect the funding split to be somewhere
along the lines of 1000 EUR for the initial pilot work and then
4000 EURO for the writing API documentation.</blockquote>
Cool!<br class="">
<br class="">
<blockquote cite="mid:439C54FE-E35D-4551-8E49-83D27E03F8E4@qgis.org" type="cite" class="">
<div class="">I also do need to sensitise you to the fact that the
API is going to undergo some big revisions for QGIS 3.0 so you
will need to work closely with the dev community to ensure that
your work is focussed on areas of the code that are not going to
e.g. get axed in the near future.</div>
</blockquote>
I think the best would be if we make a list of important classes
missing good docs and keep an eye as we progress on those which are
likely to change significantly in the run towards 3.0.<br class="">
<br class="">
<br class="">
I shall be able to fit in the work on docs starting from April.<br class="">
<br class="">
For Wes and Francisco - as of now I am (mostly) in GMT+8 timezone,
which is a bit of difference from yours, but that should not be an
issue for the collaboration :-)<br class="">
<br class="">
Cheers<br class="">
Martin<br class="">
<br class="">
<br class="">
<br class="">
<hr class=""><p style="font-family:arial,sans-serif; font-size:10px; color:#999;" class="">This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.</p><p style="font-family:arial,sans-serif; font-size:10px; color:#999;" class="">Whilst reasonable care has been taken to avoid virus transmission, no responsibility for viruses is taken and it is your responsibility to carry out such checks as you feel appropriate.</p><p style="font-family:arial,sans-serif; font-size:10px; color:#999;" class="">If this email contains a quote or offer to sell products, carry out work or perform services then our <a href="http://www.lutraconsulting.co.uk/downloads/Lutra%20Consulting%20Standard%20Terms%20and%20Conditions.pdf" class="">standard terms and conditions</a> shall apply unless explicitly stated otherwise.</p><p style="font-family:arial,sans-serif; font-size:10px; color:#999;" class="">Saber Razmjooei and Peter Wells trading as Lutra Consulting.</p>
<br class="">
<br class="">
</div>
</div></blockquote></div><br class=""><div class="">
<span><img height="65" width="59" apple-inline="yes" id="28E86A90-91B4-4DF3-A7C5-19E7A11DE7BC" apple-width="yes" apple-height="yes" src="cid:879A6E78-CA46-47B2-AA0E-1810BD833229" class=""></span><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; 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; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">---</div><div style="font-weight: normal;" class=""><br class=""></div><div class=""><b class="">Tim Sutton</b></div><div style="font-weight: normal;" class="">QGIS Project Steering Committee Chair</div><div style="font-weight: normal;" class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div style="font-weight: normal;" class=""><br class=""></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; 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; line-height: normal;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; 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;">
</div>
<br class=""></div></body></html>