<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Jody, thanks for the feedback. You've made some good comments.</p>
<p>My responses and actions inserted below.<br>
</p>
<br>
<div class="moz-cite-prefix">On 6/09/2016 12:23 PM, Jody Garnett
wrote:<br>
</div>
<blockquote
cite="mid:CAOhbgAnBUSoaAoby0uUJvBeNJZFfLYNMcT+z7zx-VKrEGrA2eQ@mail.gmail.com"
type="cite">
<div dir="ltr">grabbing this out into a seperate thread (rather
than make things complicated).
<div><br>
</div>
<div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">While
not approved by the incubation committee, I have added
suggestions for a next version of the incubation list here:<br>
<a moz-do-not-send="true"
href="https://wiki.osgeo.org/wiki/Project_Graduation_Checklist">https://wiki.osgeo.org/wiki/Project_Graduation_Checklist</a><br>
While nothing on this list should prevent current
incubation, I suggest running your eye over it and see if
there is anything else worth addressing.<br>
In particular, I suggest that somewhere in your processes
you link to the OSGeo code of condu</blockquote>
<div>
<div class="gmail_signature">
<div dir="ltr">
<div dir="ltr">
<div><br>
</div>
<div>Going through the stuff in red, which I assume is
your most recent additions:</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
Yes, stuff in red is differences between the last version 2.0
incubation document, and proposed new version.<br>
<blockquote
cite="mid:CAOhbgAnBUSoaAoby0uUJvBeNJZFfLYNMcT+z7zx-VKrEGrA2eQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div class="gmail_signature">
<div dir="ltr">
<div dir="ltr">
<div><br>
</div>
<div>[open.2d] Users are supported and encouraged, via
an email list or similar.<br>
</div>
<div>- I had assumed that "[open.2a] The project
should have a community of developers and users who
actively collaborate and support each other in a
healthy way. " would cover this?</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
Valid comment. I've struck out this line, with intent that it should
be removed in the final version.<br>
<blockquote
cite="mid:CAOhbgAnBUSoaAoby0uUJvBeNJZFfLYNMcT+z7zx-VKrEGrA2eQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div class="gmail_signature">
<div dir="ltr">
<div dir="ltr">
<div><br>
</div>
<div>
<div>[processes.4] The project has a Code of
Conduct. This may be a reference to the OSGeo Code
of Conduct.</div>
</div>
<div>- I wonder if this belongs under "open" rather
than process?</div>
<div>- I also recognize that a code of conduct is one
tool out of many for a project to work on being
inclusive?</div>
<div>- I have not seen the osgeo code of conduct
discussed much at the project level? I kind of
viewed he OSGeo code of conduct as applicable to all
committees, mailing lists and projects (and thus not
a subject for incubation as you have outlined here?)</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
I agree that Code of Conduct aligns better with the
<meta charset="utf-8">
<span id="open.2" style="color: rgb(37, 37, 37); font-family:
sans-serif; font-size: 14px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255);">"[open.2]</span><span style="color: rgb(37, 37, 37);
font-family: sans-serif; font-size: 14px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); display: inline !important; float: none;"><span
class="Apple-converted-space"> </span>Active and healthy
community", and have moved as suggested.<br>
With regards to further questioning about whether projects should
reference a Code of Conduct. I think they should and it should be
an incubation criteria. Healthy communities are built on mutual
respect, and a Code of Conduct helps confirm an understanding of
mutual respect.<br>
<br>
</span>
<blockquote
cite="mid:CAOhbgAnBUSoaAoby0uUJvBeNJZFfLYNMcT+z7zx-VKrEGrA2eQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div class="gmail_signature">
<div dir="ltr">
<div dir="ltr">
<div><br>
</div>
<div>
<div>[documentation.3] The project has deployment
documentation:</div>
<div>[documentation.3a] Including, where
appropriate, how to deploy, configure and optimise
the application.</div>
</div>
<div>- I find this covered under "[documentation.1]
The project has user documentation:" - for a server
application the user documentation would be directed
at the system administrator. I know the language is
confusing with a sys admin being responsible for
standing up a service which is made available to
"users".</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
I mildly disagree with you here. I'd be interested to hear thoughts
from others. If others also think this extra line should be removed,
then I'm ok with that.<br>
<blockquote
cite="mid:CAOhbgAnBUSoaAoby0uUJvBeNJZFfLYNMcT+z7zx-VKrEGrA2eQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div class="gmail_signature">
<div dir="ltr">
<div dir="ltr">
<div><br>
</div>
<div>[release.1a] Which supports both stable and
development releases.<br>
</div>
<div>
<div>[release.4] The project has released stable,
feature complete releases.</div>
<div>- this is getting too much, asking that a
project make releases is one thing, asking that a
team maintain multiple concurrent versions
suitable for public consumption is a bit too far</div>
</div>
<div>- making the source code available, and
instructions for how to build, are enough for any
party interested in trying our the latest
development</div>
<div>- (nightly build is preferable to development
releases anyways so that the community can benifit
from rapid feedback)</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
I think your logic about expecting concurrent releases are valid.
I've struck out [release.1a].<br>
However, I can't see any reasoning for removing: [release.4] The
project has released stable, feature complete releases.
<blockquote
cite="mid:CAOhbgAnBUSoaAoby0uUJvBeNJZFfLYNMcT+z7zx-VKrEGrA2eQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div class="gmail_signature">
<div dir="ltr">
<div dir="ltr">
<div><br>
</div>
<div>I am leaving off the other items as they require
collaboration with the respective committees.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>--</div>
<div>Jody Garnett</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
M +61 419 142 254</pre>
</body>
</html>