Thanks Martin, will try and find the correct wiki page after work today.
> Jody Garnett a écrit :
>> Will find a wiki to post this shortly .... wanting to have "module/*"
>> done for tonights meeting (4 hours away). If someone wants to start
>> at the bottom of the list I could use a hand :-)
> org.geotools.referencing
> ------------------------
> * Most files have dual copyright (Geotools PMC first, IRD second).
> Some files
> have "Fishery and Ocean Canada" as third copyright holder.
>
> * It may be possible for me to get IRD to officially donate the code
> to OSGeo (not sure, but I
> could try). Maybe we should change "(C) Geotools PMC" to "(C) OSGeo"
> first, and then I negotiate
> with IRD in order to get the legal papers signed? However I already
> know the question they are
> going to ask me: how can IRD get their contribution (as hours of
> paid work) be recognized? They
> are basically just asking for some raisonably visible place where
> their contribution is mentionned
> (don't know how visible it must be, but a deep corner in some obscur
> wiki page may not be enough).
I think they (c) with the date stays on the header ... at least from
last nights IRC meeting that was the indication. I am running around
adding (c) 2005 Refractions Research, Inc. to some donated uDig code
right now ...
> * Note sure I can join anyone at "Fishery and Ocean Canada" for doing
> the same there,
> but I could check after IRD.
>
> * Some files contains code from Proj4 (all of them are in
> ...referencing.operation.projection
> package). The Proj4 copyright header is already copied below the
> Geotools copyright header
> in the source files. We need (maybe by a layer) to verify if the
> Proj4 license conflict with
> the LGPL license (Proj4 license is opensource, but do we need to
> distribute the projection
> files under an other license than LGPL?). Frank Warmerdam could
> probably answer since he is
> the Proj4 maintainer :).
Ug, I would prefer not to mix licenses if we can avoid it.
> * The GeodeticCalculator class contains code from NOAA, which is an US
> government agency I
> believe. The NOAA code is already flagged by comments in the source
> file (with the FTP adress
> where is come from). I have been unable to find a license on NOAA
> web site, other than a sentence
> saying that the code is in the public domain.
>
> * Referencing-3D would contains code from
> http://earth-info.nima.mil/GandG/wgs84/gravitymod/.
> The only "license-like" info I found up to date is the sentence
> "Both the EGM96 and the WGS 84
> geoid height files and coefficient files have associated software
> and documents. They are
> available for unlimited distribution" in the above-cited page. If
> anyone as suggestion about
> how I should work the LICENSE.txt file in the referencing-3D module,
> it would be appreciated.
>
> * Some javadoc sentences are adapted from GeoAPI javadoc.
> org.geotools.coverage
> ---------------------
> * Contains dual copyright ("IRD" after "(C) Geotools", something
> "Fishery and Ocean Canada" in
> addition) like the referencing module. I may try to get the code
> donated together with the
> one from the referencing module.
>
> * Some javadoc sentences are adapted from GeoAPI javadoc.
>
> * No other IP issues I can think right now. The situation may be more
> complex after the
> coverage branch merge.
>
> Martin.
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
