<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 22/4/17 8:45 am, Jody Garnett wrote:<br>
</div>
<blockquote
cite="mid:CAOhbgAmSHh1AY8QNwx++B68bFc7iRefb6ri_nZ3hn-o6SR-V_A@mail.gmail.com"
type="cite">
<div class="moz-text-html" lang="x-unicode">
<div dir="ltr"><br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
2. In/exclude projects<br>
Given the fact that OSGeo Live serves as an
introduction, I think the libraries are far less
important to include.<br>
</blockquote>
<div><br>
</div>
<div>I think the libraries are in use by the other
applications (example GeoTools, GDAL/OGR). Having some
documentation about the libraries does no harm.</div>
</div>
</div>
</div>
</div>
</blockquote>
Jody, The cost of including documentation for libraries (and other
projects) is that with each release someone needs to verify that the
documentation hasn't become dated, and update where required, then
trigger translators to update their pages.<br>
The question is, do we have the volunteer capacity to do this task
for each release, for each library? (At the moment our current
volunteer base is struggling to keep up).<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
M +61 419 142 254</pre>
</body>
</html>