<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 06/16/2014 02:14 AM, Bruce Bannerman
wrote:<br>
</div>
<blockquote
cite="mid:CAG=9HVKH=RLTSSczXJyKyu3wcE8fvtfD+P0LdCHUE-POnU7X=Q@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>
<div>
<div>
<div>Can we move on from this discussion please? The
criteria has been defined and accepted by the Incubation
Committee.<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
hm, clarification I understood as being part of the open process.<br>
<br>
<blockquote
cite="mid:CAG=9HVKH=RLTSSczXJyKyu3wcE8fvtfD+P0LdCHUE-POnU7X=Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div><br>
</div>
<div>I personally find that version 2 [1] of the OSGeo
graduation checklist is much easier to work with than
version 1 [2] and allows a stronger case to be made for
the project that is seeking graduation.<br>
</div>
<div><br>
A quick compare between what the Rasdaman community
already have in their checklist and the current OSGeo
Project Graduation Checklist will show very little
difference. I have identified these issues already in my
earlier email [3].<br>
</div>
<br>
The main difference that I found is about 'openness'. If
this is the sticking point, please say so and we can move
forward. I would not have thought that this was a problem
for the Rasdaman Open Source Community though.<br>
<br>
</div>
I'm personally very short on volunteer time and would rather
spend that on working through Rasdaman graduation issues. I
have no doubt that I'm not the only person in this position.<br>
</div>
</div>
</div>
</blockquote>
<br>
same here - incubation is consuming substantial effort in addition
to all our obligations. Hence, we are interested in converging in a
way that is efficient for all sides.<br>
<br>
cheers,<br>
Peter<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAG=9HVKH=RLTSSczXJyKyu3wcE8fvtfD+P0LdCHUE-POnU7X=Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div><br>
<br>
</div>
</div>
Bruce<br>
<br>
[1] <a moz-do-not-send="true"
href="http://www.osgeo.org/incubator/process/project_graduation_checklist.html">http://www.osgeo.org/incubator/process/project_graduation_checklist.html</a>
<br>
<br>
[2] <a moz-do-not-send="true"
href="http://www.osgeo.org/incubator/process/project_graduation_checklist_v1.html">http://www.osgeo.org/incubator/process/project_graduation_checklist_v1.html</a><br>
<br>
[3] <a moz-do-not-send="true"
href="http://lists.osgeo.org/pipermail/incubator/2014-June/002436.html">http://lists.osgeo.org/pipermail/incubator/2014-June/002436.html</a>
<br>
<br>
<br>
<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
On Mon, Jun 16, 2014 at 9:13 AM, Cameron Shorter <span
dir="ltr"><<a moz-do-not-send="true"
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 bgcolor="#FFFFFF" text="#000000"> Peter, yes in an
ideal world with unlimited volunteer energy, it would be
good to have someone write a changes doc. In reality, I
don't expect someone will write it, unless you do.<br>
However, I think the best you are going to get is a diff
between versions of the doc, which can probably be
constructed from:<br>
<a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist"
target="_blank">http://wiki.osgeo.org/wiki/Project_Graduation_Checklist</a><br>
<br>
Probably easier would be to visually compare 1.0 and 2.0,
and look for the differences. <br>
<div>
<div class="h5"> <br>
<div>On 15/06/2014 6:43 pm, Peter Baumann wrote:<br>
</div>
<blockquote type="cite">
<div>thanks for your insights, Cameron! Indeed,
adjusting to new versions binds extra resources.<br>
In that respect, may I suggest that OSGeo provides
a change list for new versions so that projects
can quickly grasp what has been altered, hence
what to look at. This is common, eg, in OGC
standards updates (where I had to write the Change
Notes for a couple of specifications myself).<br>
<br>
thanks for considering,<br>
Peter<br>
<br>
<br>
On 06/15/2014 02:03 AM, Cameron Shorter wrote:<br>
</div>
<blockquote type="cite"> Peter,<br>
As far as I'm aware, the incubation committee has
not discussed what to do when the graduation
document that a project is working from is
updated.<br>
My personal suggestion is that you keep the
template you started with, but look over the new
template, and incorporate any major things from
the new template which may have been missed from
the first.<br>
<br>
Our graduation template represents a level of
quality for our OSGeo projects, and it should be
expected that all projects should meet OSGeo's
current definition of quality at the time of
graduation.<br>
<br>
<div>On 14/06/2014 11:22 pm, Peter Baumann wrote:<br>
</div>
<blockquote type="cite">
<div>Hi Jody, Cameron, & incubation
organizers,<br>
<br>
does an incubating project need to update its
documents whenever a new version of the
incubation checklist is issued?<br>
How is this meant for graduating and graduated
projects?<br>
My concern is the extra burden put on
projects.<br>
<br>
thanks for your advice,<br>
Peter<br>
<br>
<br>
<br>
On 06/14/2014 04:23 AM, <a
moz-do-not-send="true"
href="mailto:bruce.bannerman.osgeo@gmail.com"
target="_blank">bruce.bannerman.osgeo@gmail.com</a>
wrote:<br>
</div>
<blockquote type="cite">
<div>Peter,</div>
<div><br>
</div>
<div>See <a moz-do-not-send="true"
href="http://lists.osgeo.org/pipermail/incubator/2014-May/002404.html"
target="_blank">http://lists.osgeo.org/pipermail/incubator/2014-May/002404.html</a></div>
<div><br>
</div>
<div>Please use the incubation graduation
checklist that I referred to below.</div>
<div><br>
</div>
<div>Bruce</div>
<div><br>
</div>
<br>
</blockquote>
</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 moz-do-not-send="true" href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank">+61 2 9009 5000</a>, W <a moz-do-not-send="true" href="http://www.lisasoft.com" target="_blank">www.lisasoft.com</a>, F <a moz-do-not-send="true" href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank">+61 2 9009 5099</a></pre>
</blockquote>
<br>
<pre cols="80">--
Dr. Peter Baumann
- Professor of Computer Science, Jacobs University Bremen
<a moz-do-not-send="true" href="http://www.faculty.jacobs-university.de/pbaumann" target="_blank">www.faculty.jacobs-university.de/pbaumann</a>
mail: <a moz-do-not-send="true" href="mailto:p.baumann@jacobs-university.de" target="_blank">p.baumann@jacobs-university.de</a>
tel: <a moz-do-not-send="true" href="tel:%2B49-421-200-3178" value="+494212003178" target="_blank">+49-421-200-3178</a>, fax: <a moz-do-not-send="true" href="tel:%2B49-421-200-493178" value="+49421200493178" target="_blank">+49-421-200-493178</a>
- Executive Director, rasdaman GmbH Bremen (HRB 26793)
<a moz-do-not-send="true" href="http://www.rasdaman.com" target="_blank">www.rasdaman.com</a>, mail: <a moz-do-not-send="true" href="mailto:baumann@rasdaman.com" target="_blank">baumann@rasdaman.com</a>
tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: <a moz-do-not-send="true" href="tel:%2B49-173-5837882" value="+491735837882" target="_blank">+49-173-5837882</a>
"Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata." (mail disclaimer, AD 1083)
</pre>
</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 moz-do-not-send="true" href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank">+61 2 9009 5000</a>, W <a moz-do-not-send="true" href="http://www.lisasoft.com" target="_blank">www.lisasoft.com</a>, F <a moz-do-not-send="true" href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank">+61 2 9009 5099</a></pre>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="80">--
Dr. Peter Baumann
- Professor of Computer Science, Jacobs University Bremen
<a class="moz-txt-link-abbreviated" href="http://www.faculty.jacobs-university.de/pbaumann">www.faculty.jacobs-university.de/pbaumann</a>
mail: <a class="moz-txt-link-abbreviated" href="mailto:p.baumann@jacobs-university.de">p.baumann@jacobs-university.de</a>
tel: +49-421-200-3178, fax: +49-421-200-493178
- Executive Director, rasdaman GmbH Bremen (HRB 26793)
<a class="moz-txt-link-abbreviated" href="http://www.rasdaman.com">www.rasdaman.com</a>, mail: <a class="moz-txt-link-abbreviated" href="mailto:baumann@rasdaman.com">baumann@rasdaman.com</a>
tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata." (mail disclaimer, AD 1083)
</pre>
</body>
</html>