<div dir="ltr">Sorry Cameron two many small changes for a prompt email reply.<div><br></div><div>In general several additions appear to be setting the bar higher (for a given concern) rather then simply clarifying. Open 2b has been tweaked with more requirements about sustainability, this is a bit off topic as we cover that later do we not?<br><div><div><br></div><div>There is also examples of overlap (some overlap between 1c and 2c).</div></div></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div>Jody Garnett</div></div></div></div>
<br><div class="gmail_quote">On Sat, Nov 29, 2014 at 4:49 PM, Cameron Shorter <span dir="ltr"><<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Ok, proposed changes are now in place. Additions in style=red,
deletions in <strike> font.<br>
Hopefully style will by forwarded through the email list, otherwise
follow the links to the wiki page.<br>
<br>
<a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist" target="_blank">http://wiki.osgeo.org/wiki/Project_Graduation_Checklist</a><br>
<h1 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.1em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:24px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none">Project
Graduation Checklist</h1>
<br>
<h2 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.6em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:19px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none rgb(255,255,255)"><span>Open</span></h2>
<p style="margin:0.4em 0px 0.5em;line-height:19.0499992370605px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">The project has
demonstrated that it has an open, active and healthy user and
developer community:</p>
<ol style="line-height:19.0499992370605px;margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<li style="margin-bottom:0.1em"><span>[open.1]</span><span> </span>Open: projects are
expected to function in an open and public manner and include:
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span>[open.1a]</span><span> </span>Open source
license(s),</li>
<li style="margin-bottom:0.1em"><span>[open.1b]</span><span> </span>Open communication
channels,</li>
<li style="margin-bottom:0.1em"><span>[open.1c]</span><span> </span>Open decision making
process,</li>
</ul>
</li>
<li style="margin-bottom:0.1em"><span>[open.2]</span><span> </span>Active and healthy
community:
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span>[open.2a]</span><span> </span>The project should
have a community of developers and users who actively
collaborate and support each other in a healthy way.<span> </span><br>
<i>Eg. collaboration on project activities such as testing,
release and feature development.</i></li>
<li style="margin-bottom:0.1em"><span>[open.2b]</span><span> </span>Long term viability
of the project is demonstrated by showing participation,<span> </span><span style="color:red">support</span><span> </span>and
direction from multiple developers,<span> </span><span style="color:red">power users, and/or sponsors</span>, who come from
multiple organisations.<span> </span><br>
<i>Eg. The project is resilient enough to sustain loss of a
developer or supporting organisation, often referred to as
having a high<span> </span><a href="http://en.wikipedia.org/wiki/Bus_factor" rel="nofollow" style="text-decoration:none;color:rgb(51,102,187);padding-right:13px;background:url(http://wiki.osgeo.org/skins/monobook/external.png) 100% 50% no-repeat" target="_blank">bus factor</a>.</i></li>
<li style="margin-bottom:0.1em"><span>[open.2c]
Decisions are made openly instead of behind closed doors,
which empowers all developers to take ownership of the
project and facilitates spreading of knowledge between
current and future team members.</span></li>
<li style="margin-bottom:0.1em"><span style="color:red">[open.2d] Users are supported and
encouraged, via an email list or similar.</span></li>
</ul>
</li>
</ol>
<h2 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.6em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:19px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none rgb(255,255,255)"><span>Copyright
and License</span></h2>
<p style="margin:0.4em 0px 0.5em;line-height:19.0499992370605px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">We need to ensure that the
project owns or otherwise has obtained the ability to release the
project code by completing the following steps:</p>
<ol style="line-height:19.0499992370605px;margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<li style="margin-bottom:0.1em"><span>[copyright.1]</span><span> </span>All project source code
is available under an Open Source license.</li>
<li style="margin-bottom:0.1em"><span>[copyright.2]</span><span> </span>Project documentation is
available under an open license, such as Creative Commons.</li>
<li style="margin-bottom:0.1em"><span>[copyright.3]</span><span> </span><span>[copyright.1]</span><span> </span>The project code,
documentation and data has been adequately vetted to assure it
is all properly licensed, and a copyright notice included, as
per a<span> </span><a href="http://www.osgeo.org/incubator/process/codereview.html" rel="nofollow" style="text-decoration:none;color:rgb(51,102,187);padding-right:13px;background:url(http://wiki.osgeo.org/skins/monobook/external.png) 100% 50% no-repeat" target="_blank">Provenance Review</a>.</li>
<li style="margin-bottom:0.1em"><span>[copyright.4]</span><span> </span>The project maintains a
list of all copyright holders identified in the Provenance
Review Document.</li>
<li style="margin-bottom:0.1em"><span>[copyright.5]</span><span> </span>All code contributors
have agreed to abide by the project's license policy, and this
agreement has been documented and archived.</li>
</ol>
<h2 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.6em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:19px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none rgb(255,255,255)"><span>Processes</span></h2>
<ol style="line-height:19.0499992370605px;margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<li style="margin-bottom:0.1em"><span>[processes.1]</span><span> </span>The project has code
under configuration management.<span> </span><br>
<i>Eg, subversion, git.</i></li>
<li style="margin-bottom:0.1em"><span>[processes.2]</span><span> </span>The project uses an
issue tracker and keeps the status of the issue tracker up to
date.</li>
<li style="margin-bottom:0.1em"><span>[processes.3]</span><span> </span>The project has
documented<span> </span><span style="color:red">and follows</span><span> </span>its management
processes.<span> </span><br>
<i>This is typically done within a Developers Guide or Project
Management Plan.</i>
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span>[processes.2a]</span><span> </span>The project has a
suitable open governance policy ensuring decisions are made,
documented and adhered to in a public manner.<span> </span><br>
<i>This typically means a Project Management Committee has
been established with a process for adding new members. A
robust Project Management Committee will typically draw
upon developers, users and key stakeholders from multiple
organisations as there will be a greater variety of
technical visions and the project is more resilient to a
sponsor leaving.</i></li>
<li style="margin-bottom:0.1em"><span>[processes.2b]</span><span> </span>The project uses
public communication channels for decision making to
maintain transparency.<br>
<i>E.g. archived email list(s), archived IRC channel(s),
public issue tracker.</i></li>
</ul>
</li>
</ol>
<h2 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.6em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:19px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none rgb(255,255,255)"><span>Documentation</span></h2>
<ol style="line-height:19.0499992370605px;margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<li style="margin-bottom:0.1em"><span>[documentation.1]</span><span> </span>The project has user
documentation:
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span>[documentation.1a]</span><span> </span>Including sufficient
detail to guide a new user through performing the core
functionality provided by the application.</li>
</ul>
</li>
<li style="margin-bottom:0.1em"><span>[documentation.2]</span><span> </span>The project has
developer documentation:
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span>[documentation.2a]</span><span> </span>Including checkout
and build instructions.</li>
<li style="margin-bottom:0.1em"><span>[documentation.2b]</span><span> </span>Including commented
code, ideally published for developer use.<span> </span><br>
<i>Examples: javadocs for Java applications, or Sphinx
documentation for Python applications.</i></li>
<li style="margin-bottom:0.1em"><span>[documentation.2c]</span><span> </span>Providing sufficient
detail for an experience programmer to contribute patches or
a new module in accordance with the project's programming
conventions.</li>
</ul>
</li>
<li style="margin-bottom:0.1em"><span style="color:red">[documentation.3] The project has
deployment documentation:</span>
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span style="color:red">[documentation.3a] Including, where
appropriate, how to deploy, configure and optimise the
application.</span></li>
</ul>
</li>
</ol>
<h2 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.6em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:19px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none rgb(255,255,255)"><span>Release
Procedure</span></h2>
<p style="margin:0.4em 0px 0.5em;line-height:19.0499992370605px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">In order to maintain a
consistent level of quality, the project should follow defined
release and testing processes.</p>
<ol style="line-height:19.0499992370605px;margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<li style="margin-bottom:0.1em"><span>[release.1]</span><span> </span>The project follows a
defined release process:
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span style="color:red">[release.1a] Which supports both
stable and development releases.</span></li>
<li style="margin-bottom:0.1em"><span>[release.1b]</span><span> </span>Which includes
execution of the testing process before releasing a stable
release.</li>
</ul>
</li>
<li style="margin-bottom:0.1em"><span>[release.2]</span><span> </span>The project follows a
documented testing process.
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span>[release.2a]</span><span> </span><i>Ideally, this
includes both automated and manual testing.</i></li>
<li style="margin-bottom:0.1em"><span>[release.2b]</span><span> </span><i>Ideally this
includes documented conformance to set quality goals, such
as reporting Percentage Code Coverage of Unit Tests.</i></li>
</ul>
</li>
<li style="margin-bottom:0.1em"><span>[release.3]</span><span> </span>Release and testing
processes provide sufficient detail for an experienced
programmer to follow.</li>
<li style="margin-bottom:0.1em"><span style="color:red">[release.4] The project has released
stable, feature complete releases.
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><i>Ideally this is
demonstrated by describing risk adverse organisations
who have deployed releases into production systems.</i></li>
</ul>
</span></li>
</ol>
<h1 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.6em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:24px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none rgb(255,255,255)"><span>OSGeo Committees and
Community</span></h1>
<p style="margin:0.4em 0px 0.5em;line-height:19.0499992370605px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">The OSGeo Foundation is
made up of a number of committees, projects and local chapters.
This section gathers up information these groups have requested
from OSGeo projects. These expectations are not mandatory
requirements before graduation, but a project should be prepared
to address them in order to be considered a good OSGeo citizen.</p>
<h2 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.6em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:19px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none rgb(255,255,255)"><span>Board</span></h2>
<p style="margin:0.4em 0px 0.5em;line-height:19.0499992370605px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">The OSGeo<span> </span><a href="http://wiki.osgeo.org/wiki/Board" title="Board" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Board</a><span> </span>holds ultimate
responsibility for all OSGeo activities. The Board requests:</p>
<ol style="line-height:19.0499992370605px;margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<li style="margin-bottom:0.1em"><span>[board.1]</span><span> </span>A project provide a
Project Officer as a contract point:
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em">The Project Officer should
be listed at:<span> </span><a href="http://wiki.osgeo.org/wiki/Contacts#Software_Projects" title="Contacts" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project Officer</a></li>
<li style="margin-bottom:0.1em">This person is established
when the incubation committee recommends the project for
graduation</li>
<li style="margin-bottom:0.1em">Your community can change
the project officer as needed (just add an agenda item to
the next board meeting so they can recognise the change of
officer).</li>
</ul>
</li>
</ol>
<h2 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.6em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:19px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none rgb(255,255,255)"><span>Marketing</span></h2>
<p style="margin:0.4em 0px 0.5em;line-height:19.0499992370605px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">Access to OSGeo's<span> </span><a href="http://wiki.osgeo.org/wiki/Marketing_Committee" title="Marketing Committee" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Marketing_Committee</a><span> </span>and associated<span> </span><a href="http://wiki.osgeo.org/wiki/Marketing_Pipeline" title="Marketing Pipeline" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Marketing_Pipeline</a><span> </span>is one of the key benefits
of joining the OSGeo foundation. The Marketing Committee requests:</p>
<ol style="line-height:19.0499992370605px;margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<li style="margin-bottom:0.1em"><span>[marketing.1]</span><span> </span>Marketing artefacts have
been created about the project in line with the incubation
criteria listed in the OSGeo Marketing Committee's<span> </span><a href="http://wiki.osgeo.org/wiki/Marketing_Artefacts" rel="nofollow" style="text-decoration:none;color:rgb(51,102,187);padding-right:13px;background:url(http://wiki.osgeo.org/skins/monobook/external.png) 100% 50% no-repeat" target="_blank">Marketing Artefacts</a>. This lists the
documentation requirements for<span> </span><a href="http://live.osgeo.org/" rel="nofollow" style="text-decoration:none;color:rgb(51,102,187);padding-right:13px;background:url(http://wiki.osgeo.org/skins/monobook/external.png) 100% 50% no-repeat" target="_blank">OSGeo-Live</a>. Marketing Artefacts include:
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span>[marketing.1a]</span><span> </span>Application Overview</li>
<li style="margin-bottom:0.1em"><span>[marketing.1b]</span><span> </span>Application Quick
Start</li>
<li style="margin-bottom:0.1em"><span>[marketing.1c]</span><span> </span>Logo</li>
<li style="margin-bottom:0.1em"><span>[marketing.1d]</span><span> </span>Graphical Image</li>
</ul>
</li>
<li style="margin-bottom:0.1em"><span>[marketing.2]</span><span> </span>Ideally, stable
version(s) of executable applications are bundled with
appropriate distributions.<br>
<i>In most cases, this will at least include<span> </span><a href="http://live.osgeo.org/" rel="nofollow" style="text-decoration:none;color:rgb(51,102,187);padding-right:13px;background:url(http://wiki.osgeo.org/skins/monobook/external.png) 100% 50% no-repeat" target="_blank">OSGeo-Live</a>, but may also include<span> </span><a href="http://wiki.debian.org/DebianGis" rel="nofollow" style="text-decoration:none;color:rgb(51,102,187);padding-right:13px;background:url(http://wiki.osgeo.org/skins/monobook/external.png) 100% 50% no-repeat" target="_blank">DebianGIS</a>,<span> </span><a href="https://wiki.ubuntu.com/UbuntuGIS" rel="nofollow" style="text-decoration:none;color:rgb(51,102,187);padding-right:16px;background:url(http://wiki.osgeo.org/skins/monobook/lock_icon.gif) 100% 50% no-repeat" target="_blank">UbuntuGIS</a>, and/or<span> </span><a href="http://trac.osgeo.org/osgeo4w/" rel="nofollow" style="text-decoration:none;color:rgb(51,102,187);padding-right:13px;background:url(http://wiki.osgeo.org/skins/monobook/external.png) 100% 50% no-repeat" target="_blank">osgeo4w</a><span> </span><a href="http://www.maptools.org/ms4w/" rel="nofollow" style="text-decoration:none;color:rgb(51,102,187);padding-right:13px;background:url(http://wiki.osgeo.org/skins/monobook/external.png) 100% 50% no-repeat" target="_blank">ms4w</a>, etc.)</i></li>
<li style="margin-bottom:0.1em"><span style="color:red">[marketing.3] The project incorporates
OSGeo branding, such as including an OSGeo logo on its
website.</span></li>
<li style="margin-bottom:0.1em"><span style="color:red">[marketing.4] The project has been
registered with Open HUB, and Open HUB has been updated to
reference the correct code repository(s) for the project.<span> </span><a href="https://www.openhub.net/" rel="nofollow" style="text-decoration:none;color:rgb(51,102,187);padding-right:16px;background:url(http://wiki.osgeo.org/skins/monobook/lock_icon.gif) 100% 50% no-repeat" target="_blank">Open HUB</a><span> </span>provides metrics to
help assess the health of a project.</span></li>
</ol>
<h2 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.6em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:19px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none rgb(255,255,255)"><span>Projects</span></h2>
<ol style="line-height:19.0499992370605px;margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<li style="margin-bottom:0.1em"><span>[projects.1]</span><span> </span>Projects do not exist in
isolation; and are expected to communicate and collaborate on
key issues.<span> </span><br>
<i>As an example, the PostGIS release procedure asks that the
release be checked with MapServer, GeoServer and others.</i></li>
<li style="margin-bottom:0.1em"><span style="color:red">[projects.2] Where applicable, projects
are expected to interoperate effectively with other
applications.</span>
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span style="color:red">[projects.2a] Interoperability is
preferably achieved by supporting relevant Open Standards.</span></li>
<li style="margin-bottom:0.1em"><span style="color:red">[projects.2b] Where applicable,
standards compliance is verified by executing compliance
tests, such as provided by OGC CITE testing.</span></li>
</ul>
</li>
</ol>
<br>
<div><a href="http://wiki.osgeo.org/wiki/Incubator_Application_Questionnaire" target="_blank">http://wiki.osgeo.org/wiki/Incubator_Application_Questionnaire</a><br>
<h1 style="color:rgb(0,0,0);font-weight:normal;margin:0px 0px 0.1em;padding-top:0.5em;padding-bottom:0.17em;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(170,170,170);font-size:24px;font-family:sans-serif;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:19.0499992370605px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background:none">Incubator
Application Questionnaire</h1>
<br>
<ol style="line-height:19.0499992370605px;margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<li style="margin-bottom:0.1em">Please describe your Project.
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span style="color:red">What
is its name?</span></li>
<li style="margin-bottom:0.1em"><span style="color:red">What
is the home page URL?</span></li>
<li style="margin-bottom:0.1em">What does the application
do and how does it add value to the GeoSpatial stack of
software?</li>
<li style="margin-bottom:0.1em">Does the application make
use of OGC standards? Which standards? You may wish to add
comments about how standards are used.</li>
<li style="margin-bottom:0.1em">What language(s) are used
in this project? (C/Java/perl/etc)</li>
<li style="margin-bottom:0.1em">What is the dominant
written language (i.e. English, French, Spanish, German,
etc) of the core developers?</li>
<li style="margin-bottom:0.1em">What type of application
does this project represent(client, server, standalone,
library, etc.)</li>
<li style="margin-bottom:0.1em">Please provide the name
and email address of the principal Project Owner. Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#board.1" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#board.1</a></li>
</ul>
</li>
<li style="margin-bottom:0.1em"><span style="color:red">Do
you anticipate your project will encounter issues addressing
the criteria of the<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist</a>?
Please explain what areas need to be addressed in order to
meet this criteria.</span>
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><strike>Please provide the
names and emails of co-project owners (if any).</strike></li>
<li style="margin-bottom:0.1em"><strike>Please provide the
names, emails and entity affiliation of all official
committers. Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#open.2b" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#open.2b</a></strike></li>
</ul>
</li>
<li style="margin-bottom:0.1em"><strike>Why is OSGeo
Incubation good for your project?</strike></li>
<li style="margin-bottom:0.1em">Please describe any
relationships to other open source projects. Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#Projects" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#Projects</a></li>
<li style="margin-bottom:0.1em">Please describe any
relationships with commercial companies or products. Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#open.2b" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#open.2b</a></li>
<li style="margin-bottom:0.1em"><strike>Please explain how
your project will use an open governance policy, ensuring
decisions are made, documented and adhered to in a public
manner. Ref:<a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#processes.2a" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#processes.2a</a></strike></li>
<li style="margin-bottom:0.1em"><strike>Which open source
license(s) will the source code be released under? Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#open.1a" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#open.1a</a></strike></li>
<li style="margin-bottom:0.1em">Please describe the maturity
and history of your project. For instance,
<ul style="line-height:1.5em;list-style-type:square;margin:0.3em 0px 0px 1.5em;padding:0px">
<li style="margin-bottom:0.1em"><span style="color:red">How
long has your project been producing stable releases?</span></li>
<li style="margin-bottom:0.1em">What is the origin of your
project (commercial, experimental, thesis or other higher
education, government, or some other source)?</li>
<li style="margin-bottom:0.1em">How many people actively
contribute (code, documentation, other?) to the project at
this time? Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#open.2b" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#open.2b</a></li>
<li style="margin-bottom:0.1em">How many people have
commit access to the source code repository? Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#open.2b" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#open.2b</a></li>
<li style="margin-bottom:0.1em">Approximately how many
users are currently using this project?</li>
<li style="margin-bottom:0.1em">What type of users does
your project attract (government, commercial, hobby,
academic research, etc. )?</li>
</ul>
</li>
<li style="margin-bottom:0.1em"><strike>Do you wish to host
any portion of this project using the OSGeo infrastructure?
If so, what? Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#SAC" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#SAC</a></strike></li>
<li style="margin-bottom:0.1em"><strike>Does the project
support open standards? Which ones and to what extent? (OGC,
w3c, etc.) Has the software been certified to any standard
(CITE for example)? If not, is it the intention of the
project owners to seek certification at some point? Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#projects.2" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#projects.2</a></strike></li>
<li style="margin-bottom:0.1em"><strike>Is the code free of
patents, trademarks, and do you control the copyright? Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#Project_Graduation_Checklist.23Copyright_and_License" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#Project_Graduation_Checklist#Copyright_and_License</a></strike></li>
<li style="margin-bottom:0.1em"><strike>Does the project
include an automated build and test? Ref:<span> </span><a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#release.2" title="Project Graduation Checklist" style="text-decoration:none;color:rgb(90,54,150);background:none" target="_blank">Project_Graduation_Checklist#release.2</a></strike></li>
<li style="margin-bottom:0.1em"><strike>What is the
(estimated) size of a full release of this project? How many
users do you expect to download the project when it is
released?</strike></li>
<li style="margin-bottom:0.1em">Do you already have an OSGeo
Mentor to guide you through the incubation process?</li>
</ol>
<br>
Deprecate:<br>
<a href="http://wiki.osgeo.org/wiki/General_Principles_of_Incubation" target="_blank">http://wiki.osgeo.org/wiki/General_Principles_of_Incubation</a><div><div class="h5"><br>
<br>
On 30/11/2014 3:36 am, Jody Garnett wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">Merging docs is a good idea, looks like we end up
with one "initial application" document, and one "graduation /
checklist" document.
<div><br>
</div>
<div>While merging please keep the checklist feel, we do have a
FAQ page which can be used if you feel more discussion is
warranted. Questions such as "appropriate standards" are
difficult, since we would like to encourage projects to
explore and work in areas that have not yet been
standardized. </div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div>
<div dir="ltr">
<div>Jody Garnett</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Sat, Nov 29, 2014 at 5:49 AM,
Cameron Shorter <span dir="ltr"><<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
As I start considering taking OSGeo-Live into OSGeo
Incubation, I've audited our Incubation documents which have
significant overlap.<br>
<br>
In particular, I think our Project Graduation Checklist is
now quite comprehensive.<br>
<br>
I believe the General Principles of Incubation document can
be retired, as material in it is covered by the Checklist.<br>
<br>
I think we probably should also retire the Incubation
Application Questionnaire, moving a few project specific
questions into the Project Graduation Checklist.<br>
<br>
To show the level of duplication between documents, I've
inserted cross references into:<br>
<a href="http://wiki.osgeo.org/wiki/General_Principles_of_Incubation" target="_blank">http://wiki.osgeo.org/wiki/General_Principles_of_Incubation</a><br>
<a href="http://wiki.osgeo.org/wiki/Incubator_Application_Questionnaire#Questions" target="_blank">http://wiki.osgeo.org/wiki/Incubator_Application_Questionnaire#Questions</a><br>
<br>
These link to points in: <a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist" target="_blank">http://wiki.osgeo.org/wiki/Project_Graduation_Checklist</a><br>
<br>
In doing this, I've also picked up some limitations with
Graduation Checklist:<br>
<br>
1. There is no question to see if there is feature complete,
mature code, with at least one stable release.<br>
<br>
2. There is no question to see if appropriate standards are
being used.<br>
<br>
3. While there are questions about developer and their
affiliations, there isn't a question about the size of the
user base.<br>
<br>
4. We should move some of the "About this project" questions
into the Checklist, to keep them in the same place.<br>
<br>
I'm interested to hear comment on whether merging docs into
one is a good idea. If there is rough consensus that it is
good, I'll put a proposal forward for a v3 Graduation
Checklist.<br>
<br>
-- <br>
Cameron Shorter,<br>
Software and Data Solutions Manager<br>
LISAsoft<br>
Suite 112, Jones Bay Wharf,<br>
26 - 32 Pirrama Rd, Pyrmont NSW 2009<br>
<br>
P <a href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank">+61 2 9009 5000</a>, W <a href="http://www.lisasoft.com" target="_blank">www.lisasoft.com</a>, F <a href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank">+61 2 9009 5099</a><br>
<br>
_______________________________________________<br>
Incubator mailing list<br>
<a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/incubator" target="_blank">http://lists.osgeo.org/mailman/listinfo/incubator</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre cols="72">--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009
P <a href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank">+61 2 9009 5000</a>, W <a href="http://www.lisasoft.com" target="_blank">www.lisasoft.com</a>, F <a href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank">+61 2 9009 5099</a></pre>
</div></div></div>
</blockquote></div><br></div>