Jody Garnett a écrit :
Talking to a few guys here and they have not been running Jalopy for
fear of mangling headers, my understanding is that:
a) geotools code gets a geotools header (code donated by a company can
be credited in the class description - which is more public anyways),
A credit in the class description may be too much; I would prefer to
focus class descriptions on what developper care about, i.e. what the
class do.
At the very least, the first copyright owner in the header should be the
Geotools PMC. It should be the case in every classes I wrote. I'm not
sure what to do for the next ones when there is more than one owner. In
my understanding, having multicopyright owners means that the license
can not change without the agreement of all parties, which means that
Geotools code is safe as long as the Geotools PMC is listed in the
copyright owners.
An alternative may be to create some credit page on the web site (I
would prefer that rather than javadoc).
Martin.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
