I commited to the trunk a new directory, "licenses", wich contains the license
files in HTML format
for some of our dependencies. Having all licenses in a common directories have
the following advantages:
* Different modules can point to the same license file. For example
there is more than one module using the PostgreSQL JDBC driver.
* Provide a single place where to update the licenses, if needed.
* Provide a single place where we can look for all license used
by Geotools dependencies.
I have commited only the licenses for the main dependencies in the modules that
I maintain. I
suggest that other module maintainers add the license files for the
dependencies in their own
modules. I suggest to adopt the following formatting rules:
* Header copyright sentence in bold
* Conditions in <blockquote>
* Source cited at the end (right alignment inside the <blockquote> section).
Example: http://svn.geotools.org/geotools/trunk/gt/licenses/PostgreSQL.html
The easiest approach may be to copy this file and modify it.
In addition, a LICENSE.html file should be provided in each module, in
replacement of the old
LICENSE.txt file. This LICENSE.html should contains the Geotools license only
(not dependencies). A
model is provided in the "licenses" directory, which should be copied using the
"svn copy" command
in order to make it easier to track the changes done for a particular module:
svn copy licenses/Geotools.html <your module>/LICENSE.html
The LICENSE.html file in each module shall be modified in order to list all
conjoint copyright
holders, if any. Example:
http://svn.geotools.org/geotools/trunk/gt/ext/go/LICENSE.html
Finally, the pom.xml file in every module should be updated with a <licenses>
section, just below
the <description> section, enumerating all applicable licenses. The Geotools
license should be first
and without comment. All other licenses (if any) should have a <comments>
section explaining how
this license apply to this module. The example below is copied from
plugin/epsg-hsql/pom.xml:
<licenses>
<license>
<name>Lesser General Public License (LGPL)</name>
<url>http://svn.geotools.org/geotools/trunk/gt/plugin/epsg-hsql/LICENSE.html</url>
<distribution>repo</distribution>
</license>
<license>
<name>EPSG database distribution license</name>
<url>http://svn.geotools.org/geotools/trunk/gt/licenses/EPSG.html</url>
<distribution>repo</distribution>
<comments>
This Geotools module is bundled with a copy of the EPSG database. The
data may be copied and distributed subject to the EPSG conditions.
</comments>
</license>
<license>
<name>BSD License for HSQL</name>
<url>http://svn.geotools.org/geotools/trunk/gt/licenses/HSQL.html</url>
<distribution>repo</distribution>
<comments>
This Geotools module requires the HSQL database engine, which is
bundled
with the binary distribution only (there is no HSQL derived work in the
Java source code).
</comments>
</license>
</licenses>
Note that the URL point toward the public SVN server, not to a local directory.
This is needed
because the Maven generated reports will publish this URL. Note also that if we
are not allowed to
distribute a dependency, we can write "manual" in the <distribution> section.
This means that users
need to download that dependency themself.
One more note: according Maven website, the above should list only the licenses
applicable to the
project, not the dependencies. We are using it in a more paranoiac way by
listing dependency
licenses as well.
Finally, when all the above are setup, the Maven generated page looks like this
one:
http://maven.geotools.fr/reports/epsg-hsql/license.html
I suggest that when a module has reached the point where Maven generates a page
like the above one,
we consider the IP review for that module as completed.
Does it sound like a good approach? Any proposed changes?
Martin.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
