<div dir="auto">Would be nice if we could create a project for the next release and put the prioritary issues there. That could be our way of planning, but I wasn't able to find a way to do it.<div dir="auto"><br></div><div dir="auto">I will try on my own repo or something.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">A sexta, 27/09/2019, 15:46, DelazJ <<a href="mailto:delazj@gmail.com">delazj@gmail.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Alex, OK you are referring to <a href="https://github.com/qgis/QGIS-Documentation/projects/1" target="_blank" rel="noreferrer">https://github.com/qgis/QGIS-Documentation/projects/1</a>. This is some completely different project. You'll find the rationale at <a href="https://github.com/qgis/QGIS-Documentation/pull/4237#issuecomment-530794557" target="_blank" rel="noreferrer">https://github.com/qgis/QGIS-Documentation/pull/4237#issuecomment-530794557</a> (in short, these are notes to remember what needs to be done when creating a new branch in docs. According to the notes context menu, they can be turned into issue reports; to do only at release time to avoid people trying to tackle them when unnecessary)</div><div><br></div><div>From what I saw in GH we can create as many projects as we want and GH also provides the Todo/In Progress/Done structure. The question is what to put in and how do we organise the items (by manuals, by chapters, by main components of the application?) I don't quite see the right way to do, yet! and i'm less confident with blindly play with the shared repo. ;) And is it worth it?<br></div><div><br></div><div>Harrissou<br></div><div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le ven. 27 sept. 2019 à 12:41, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank" rel="noreferrer">cameron.shorter@gmail.com</a>> a écrit :<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 bgcolor="#FFFFFF">
<p>Hi Harrissou,</p>
<p>For OSGeoLive, we apply "docs not complete - package not
included". For QGIS, your unit might be a module or feature.</p>
<p>We started small and expanded. First, we just asked for a package
installer, then a Project Overview, then a Quickstart.</p>
<p>We make it clear that a we expect quality and we expect the
projects to provide their own volunteers to reach our quality
criteria. Projects without a maintainer are removed. This is a
principle which you might want to customise for QGIS modules.</p>
<p>Eg: <a href="https://wiki.osgeo.org/wiki/OSGeoLive_AddProject#What_gets_into_OSGeoLive.3F" target="_blank" rel="noreferrer">https://wiki.osgeo.org/wiki/OSGeoLive_AddProject#What_gets_into_OSGeoLive.3F</a></p>
<p>We also keep track of the status of each project in a publicly
visible table, and often reference it to project maintainers. Eg:
See doc review column for v11.0 release:</p>
<p><a href="https://docs.google.com/spreadsheets/d/1Q5BaEgQtgw4O1bXyeWMlM8XtAOhUgcjZ7Y2O0FZc2H0/edit?hl=en_GB#gid=2014800150" target="_blank" rel="noreferrer">https://docs.google.com/spreadsheets/d/1Q5BaEgQtgw4O1bXyeWMlM8XtAOhUgcjZ7Y2O0FZc2H0/edit?hl=en_GB#gid=2014800150</a></p>
<p><br>
</p>
<div>On 27/9/19 8:17 am, DelazJ wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi,</div>
<div><br>
</div>
<div>Cameron, the idea is to put in actions some affordable
items that were pointed in the recent discussion you raised,
while "waiting" for some more political (in the honourable
sense) moves.</div>
<div class="gmail_quote">Yes, we'll indeed need to find key
dates/events that would help us structure the timeline up to
the release date (thanks for the pointers). But since we are a
single project, it'd be hard to apply the "not complete - not
included" rule you apply (or I did misunderstand you?).<br>
<div dir="auto"><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">A domingo, 22/09/2019,
09:28, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank" rel="noreferrer">cameron.shorter@gmail.com</a>>
escreveu:<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 bgcolor="#FFFFFF">
<p>Hi Harrissou,</p>
<p>Great ideas here around setting a documentation
generation schedule. You might want to borrow from
the countdown schedule we use for OSGeoLive, which
has key milestones for docs included. We align our
schedule with the international FOSS4G. <br>
</p>
<p><a href="https://docs.google.com/spreadsheets/d/1kO6zzmLFfprZGgp5x7Sjwi-EVN6NTGDR4KXvFVtNpR0/edit?hl=en_GB&hl=en_GB#gid=0" rel="noreferrer noreferrer" target="_blank">https://docs.google.com/spreadsheets/d/1kO6zzmLFfprZGgp5x7Sjwi-EVN6NTGDR4KXvFVtNpR0/edit?hl=en_GB&hl=en_GB#gid=0</a></p>
<p>We go one step further in that we state that if a
project's documentation is not complete, then it is
not included. (We occasionally bend this rule, and
let a project be included, but if it's docs are not
linked in, then people can't find the project.)</p>
<p>Cheers, Cameron</p>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
<pre cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</div>
</blockquote></div>
</blockquote></div>