Re: [deegree-devel] incubation for FOSS4G?
OSGeo project deegree
Brought to you by:
deegreesfadmin,
tfr
From: Jody G. <jod...@gm...> - 2009-10-14 00:36:05
|
On Wed, Oct 14, 2009 at 4:21 AM, Markus Schneider <sch...@la...> wrote: > Hi Jody, > > we finished the code provenance review for all relevant SVN modules! See > http://wiki.deegree.org/deegreeWiki/OSGeoIncubationCodeProvenanceReviewReport > That is great news! Congratulations. > However, there are still a few open issues that we analyzed, but were not able to resolve yet: That is fine; the point is to find the issues (you can fix them on your own time - even after graduation). That said I will try and provide some comments. Just please keep in mind this is friendly advise and the decision rests in the hands of the PSC - and resolving these issues is not required for graduation. Thank you for all the hard work; can we have a shared Skype or IRC session and go over the graduation requirements and ensure you are happy? The next step is for me to nominate you and for us to play Q&A with the incubation list. Jody > = deegree 2 (base) = > > http://wiki.deegree.org/deegreeWiki/OSGeoIncubationCodeProvenanceBase > Could you please comment on issues 2 and 3? Issue 2 matches GeoAPI interfaces (such as CodeList). This code is released under its own license (so you will need to refer to that in the header for these files; and include the license in the zip. >From the GeoAPI website: ----- GeoAPI is free software. GeoAPI may be used, modified and redistributed by anyone for any purpose requring only maintaining the copyright and license terms on the source code and derivative files. See the OGC legal page for details. The copyright to the GeoAPI interfaces is held by the Open Geospatial Consortium. ----- (with a link to http://www.opengeospatial.org/ogc/legal) Issue 3 is an interesting one - You reference the correct (c) 2003 in your header; that provides a history others can review to establish ownership. You may also talk to to the author directly; since 2003 many books have tightened up their language making it clear that you can use their work as a starting point. Until then you are providing credit where credit is due. There does not appear to be a problem here. > = deegree 2 (igeoportal) = > > http://wiki.deegree.org/deegreeWiki/OSGeoIncubationCodeProvenance_iGeoPortal > Could you please comment on the open issues here as well? > > = deegree 2 (owswatch) = > > http://wiki.deegree.org/deegreeWiki/OSGeoIncubationCodeProvenance_owsWatch > The story you tell here is fine; tell that story in the header; and try and contact the author. The idea with the header is to communicate what is know right now. So short term I would make a header consisting of exactly your summary on that page. > = External libraries in our SVN = > > http://wiki.deegree.org/deegreeWiki/OSGeoIncubationCodeProvenanceReviewReport#Module.27base.27 > Can you share your thoughts on the libraries that still have a question mark? In general you are distributing these libraries in accordance with their license. In cases where you have your own fork - say commons-httpclient-2.0.2-deegreeversion.jar you actually have an interesting issue. You need to be sure that the code is available for others (and whatever else Apache License asks). And you are taking responsibility for shipping that fork of httpclient as a distinct artifact. In my case I usually submit a patch back to the original project; and consider the source code published as a result. You can link to the bug report w/ patch in your providence review ... Other then that I am not always sure why there is a ? for some of these libraries. mysql-connector-java-5.1.7-bin.jar is always a trouble since what does it mean for a jdbc-driver to be GPL? |