<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi<br>
</p>
<div class="moz-cite-prefix">On 26.09.19 09:39, Anita Graser wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFFV8Fhme7AwaiF44APK9j1r2FqYdvHtMdv54iQOKLmECo-ZzA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default" style="font-size:small"><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Sep 26, 2019 at 8:29
AM Andreas Neumann <<a href="mailto:a.neumann@carto.net"
moz-do-not-send="true">a.neumann@carto.net</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div
style="font-size:10pt;font-family:Verdana,Geneva,sans-serif">
<p>Hi,</p>
<p>Hm - We always had a separate budget for documentation
- totally separate from the grants.</p>
</div>
</blockquote>
<div class="gmail_default" style="font-size:small">According
to our budget sheet, there's still money in the
documentation pot, right?</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div
style="font-size:10pt;font-family:Verdana,Geneva,sans-serif">
<p>Personally, I would prefer if we could find a pragmatic
solution so that work, that wasn't planned ahead, can
still be financed. Grants are only issued once a year -
for one-time work - not for repeated maintenance work.</p>
<p>I think our Python devs would appreciate a complete API
documentation. This seems to be repeating work - isn't
the API constantly changing a bit? Mainly for major
releases, but also some additions, fixes,
clarifications, etc. in betweeen?</p>
<p>I think, in the future, we should declare API
documentation as part of the documentation budget and
increase the documentation funds accordingly.</p>
</div>
</blockquote>
<div>
<div class="gmail_default" style="font-size:small">Can't we
just do that now. I don't see a huge difference. <br>
</div>
</div>
</div>
</div>
</blockquote>
Completely agree.<br>
<blockquote type="cite"
cite="mid:CAFFV8Fhme7AwaiF44APK9j1r2FqYdvHtMdv54iQOKLmECo-ZzA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">We could
also ask OSGeo if we don't have the funds. (Or have we
asked them for anything else this year yet?)</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">Regards,</div>
<div class="gmail_default" style="font-size:small">Anita</div>
</div>
</div>
</div>
</blockquote>
<p>Ciao <br>
</p>
<p>Marco<br>
</p>
<blockquote type="cite"
cite="mid:CAFFV8Fhme7AwaiF44APK9j1r2FqYdvHtMdv54iQOKLmECo-ZzA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div class="gmail_default" style="font-size:small"><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Qgis-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-psc@lists.osgeo.org">Qgis-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-psc">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a></pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Marco Bernasocchi
QGIS.org Co-chair
<a class="moz-txt-link-freetext" href="http://berna.io">http://berna.io</a></pre>
</body>
</html>