<div dir="ltr"><div><div><div>@Cameron,<br><br></div><div>Thanks for your comments and for taking the time to review the wealth of material available.<br></div><div><br><br>@Incubation Committee<br><br></div><div>Is there anything else that you'd like addressed?<br><br><br></div><div>@Peter,<br></div><div><br></div>Could you please arrange for a project member to address Cameron's comments in the first instance? This is in line with my email of the 21st May [1].<br><br></div>If required, I'll then add specific comments / observations as the project mentor.<br><br></div><div>Bruce<br></div><div><br><br>[1] <a href="http://lists.osgeo.org/pipermail/incubator/2014-May/002423.html">http://lists.osgeo.org/pipermail/incubator/2014-May/002423.html</a> <br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Oct 19, 2014 at 8:30 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">
<div bgcolor="#FFFFFF" text="#000000">
Hi Peter and Bruce,<br>
I've reviewed the incubation documentation provided, and provided a
few spot reviews of the referenced documentation.<br>
Overall, I think the documentation is in good shape, but missing
explanations, particularly around licenses and testing.<br>
<br>
<br>
Below are a few things that I'd like to see looked into before final
sign off:<br>
<br>
Looking at: <a href="http://rasdaman.org/wiki/OSGeoIncubationChecklist" target="_blank">http://rasdaman.org/wiki/OSGeoIncubationChecklist</a> which
provides the summary about how the project is ready to complete
graduation.<br>
<br>
* For each statement that you are addressing, please add a brief
sentence explaining HOW you are addressing the statement, possibly
also with an OPINION.<br>
For instance, currently for: "Open communication channels", you have
"see MailingLists".<br>
In reviewing, I can see that a mailing list has been set up. In
looking at the list, I see users are asked questions on the user
list and there are answers. I can see that auto-patch messages are
being pumped into the developers list. In my quick scan, I can't see
discussions between developers about a new feature, and discussions
about a design idea. So I'd suggest describing how communication is
happening. Maybe:<br>
"See MailingLists <URL>. User questions are typically
addressed on the user email list. Development is currently mostly
happening at Jacobs University, and discussions about development
typically happen in person, and the results of such conversations
are summarised onto the developer email list (or ...)."<br>
<br>
* For "Open Source License": I'd be hoping to see a statement about
the dual license, including a comment about the enterprise license.
I'm ok with the dual license concept which I think fits with OSGeo
principles. Further, from the material and links provided, it seems
plausible that the GPL license terms are broken by LGPL and
enterprise licensed products being distributed.<br>
I feel there needs to be an explanation of the enterprise license,
and then about how LGPL products and enterprise products don't need
to be GPL (because they don't link in any GPL libraries?).<br>
<br>
* "<i>Long term viability</i>": <br>
Sentence needed here discussing roughly how many contributors you
have, (as well as existing reference to patchmanager).<br>
<br>
*
<i>Project documentation is available under an open license, as
documented here: Legal</i>: <br>
The referenced "Legal" link doesn't talk about Documentation. Please
reference correct documentation license link.<br>
<br>
* <i><a href="http://rasdaman.org/wiki/Legal" target="_blank">http://rasdaman.org/wiki/Legal</a></i> : <br>
Remove references to "... blah-blah ..."<br>
<br>
* "
<i>Which includes execution of the testing process before releasing
a stable release: <a href="http://212.201.49.21:35000/" target="_blank">http://212.201.49.21:35000/</a>"</i> :<br>
Link requires user log in. A sentence explaining testing will help
here.<br>
<br>
* "<i>All patches submitted to the repository undergo review before
being applied to the code base:
<a href="http://www.rasdaman.org/patchmanager" target="_blank">http://www.rasdaman.org/patchmanager</a></i>" : <br>
This doesn't confirm that patches are reviewed (by a person), only
that you use patchmanager.<br>
<br>
* "<i>Systemtests are to be run by developers before submitting
patches: <a href="http://www.rasdaman.org/wiki/CodeGuide" target="_blank">http://www.rasdaman.org/wiki/CodeGuide</a></i>" : <br>
This code guide is good, but on my first pass, I can't see any
reference to testing processes. How do you verify that all code is
tested? Ideally reference continual integration or similar.<br>
<br>
* Link to <i><a href="http://rasdaman.org/browser/systemtest" target="_blank">http://rasdaman.org/browser/systemtest</a></i> is
broken. I'm looking for evidence of testing processes, including
unit testing, continuous integration, and a system testing plan
which is executed. <br><div><div class="h5">
<br>
<br>
<br>
<div>On 16/10/2014 4:25 pm, Bruce Bannerman
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div><br>
Project: Rasdaman <br>
<br>
</div>
Project Contact: Peter Baumann<br>
<br>
Project Mentor: Bruce Bannerman<br>
<br>
<br>
Recommendation: Rasdaman to Graduate from OSGeo Incubation<br>
<br>
<br>
<div>Incubation Checklist: <a href="http://rasdaman.org/wiki/OSGeoIncubationChecklist" target="_blank">http://rasdaman.org/wiki/OSGeoIncubationChecklist</a>
<div style="width:16px;min-height:16px;display:inline-block"> </div>
<br>
</div>
<div><br>
<br>
</div>
Comments:<br>
<br>
I have been monitoring and participating in the Rasdaman
Community developer and user email lists for over four years. I
plan to continue to participate within the community.<br>
<br>
It has been pleasing to see how the community has evolved over
this time to develop effective, open and robust processes. <br>
<br>
I recommend to other FOSS4G communities to review what has been
done, as you may well find that Rasdaman offers a compelling
solution for the management of multi-dimensional array or
gridded data that your project may be able to capitalise on.<br>
<br>
<div>A summary of community activity may be found at: <a href="https://www.openhub.net/p/rasdaman" target="_blank">https://www.openhub.net/p/rasdaman</a>
<br>
</div>
<div><br>
</div>
Key project members are active within both OSGeo and the OGC.<br>
<br>
Within the OGC they have successfully guided a range of
standards to support mutltidimensional array (gridded) data
which have culminated (currently) in Web Coverage Service
version 2.0 and a suite of extensions, see: <a href="http://www.opengeospatial.org/standards/wcs" target="_blank">http://www.opengeospatial.org/standards/wcs</a><br>
<br>
The project's principal, Professor Peter Baumann was also
recently awarded OGC's prestigious Kenneth D Gardels award for
his contributions to OGC.<br>
<br>
<br>
<br>
<div>After having participated within the community for four
years and having reviewed their OSGeo Project Graduation
Checklist, I believe that Rasdaman Community have fulfilled
the requirements of OSGeo Incubation and are eligible to
graduate as an OSGeo Project.<br>
</div>
<div><br>
<br>
</div>
The only reservation that I have is over the dual licensing
model that is used by the sponsoring company, Rasdaman GmbH.
See: <a href="http://www.rasdaman.com/Product/commercial+free.php" target="_blank">http://www.rasdaman.com/Product/commercial+free.php</a>
<div style="width:16px;min-height:16px;display:inline-block"> </div>
<br>
<br>
There are two versions: Community (GPL and LGPL) and Enterprise
(free from GPL constraints).<br>
<br>
The main difference between the two versions is summarised at: <a href="http://www.rasdaman.org/wiki/Features" target="_blank">http://www.rasdaman.org/wiki/Features</a>
<div style="width:16px;min-height:16px;display:inline-block"> </div>
<br>
<br>
This dual licensing may create a problem for the Rasdaman
Community in the future should Rasdaman GmbH decide to sell its
stake in the Rasdaman Enterprise version of the software. We
have already seen a similar situation arise after the sale of
MySQL which was similarly licensed. <br>
<br>
However as the community edition of the software is released
under open source licenses, I expect that the main impact would
be to the continuity of the Rasdaman Community in its current
form. In the event of a sale, we may see the software forked, as
happened with MySQL.<br>
<div><br>
</div>
<div>For consideration and vote.
<div>
<div><img src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif"></div>
</div>
<span><font color="#888888"><br>
</font></span></div>
<span><font color="#888888">
<div>Bruce<br>
</div>
</font></span></div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Incubator mailing list
<a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/incubator" target="_blank">http://lists.osgeo.org/mailman/listinfo/incubator</a></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<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>
</font></span></div>
</blockquote></div><br></div>