Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Description

We have a received the following request on the a request on geotools-devel email list.

Panel

Hello all

I'm Martin Desruisseaux, a former GeoTools 2 contributor and now a developer of the Geotoolkit.org project (http://www.geotoolkit.org).
In our search for a community, we had a recent discussion with members of the Apache Spatial Information System project (http://incubator.apache.org/sis/), which is in incubation. A small email exchange gave me the feeling that our design goals could be in phase. We would like to offer them the Geotoolkit.org code. In order to make that possible, we need OSGeo permission to re-license Geotoolkit.org from its current LGPL 2.1 license to the more permissive Apache license. The proposal is not to transfer the totality of Geotoolkit.org to Apache SIS, but to allow them to review the code and pick-up whatever they wish on a case-by-case basis. The transition to Apache SIS would probably be slow and very progressive.

Geotoolkit.org is a fork of GeoTools 2.6 followed by 4 years of developments. The project contains two parts: "core" and "pending". Our proposal is to begin with the "core" part, which include material derived from the following GeoTools 2.6 modules:
* utilities
* metadata
* referencing
* core of coverage (excluding I/O)
* many (but not all) Swing widgets

In 2008 those modules were written (according SVN history) at 95% by myself, Geomatys or IRD institute. The remaining 5% were written by other GeoTools contributors. To my knowledge, everyone signed the copyright assignment on http://download.osgeo.org/osgeo/legal/ which grants copyright to OSGeo. However because the GeoTools community may have vested interest in this re-licensing decision, I wish to ask on this mailing list.

I would like to emphases that this is not a demand for relicensing current GeoTools, but only relicensing of the GeoTools 2.6 code from which "Geotidy" (the Geotoolkit.org precursor) is derived, which is 4 years old. If the community accepts to grant us the permission to relicense 100% of Geotoolkit.org "core", that would be truly appreciated. But in case of bjection, we are willing to rewrite the 5% of "core" code which was not written by myself, Geomatys or IRD.

It the community accepts re-licensing, this would allows Apache SIS to gain services they are currently missing, allows Geotoolkit.org code base to gain a community, and possibly allows the GeoTools project to gain a metadata and referencing library maintained by a trusted foundation, which could complete or replace the current referencing module as GeoTools wish. The Geotk referencing module got 4 years of extensive development since our departure, and has capabilities which are - to my knowledge - unique in the open source world.

Regards,
Martin Desruisseaux

The to relicense a subset of the codebase under the apache license to facilitate collaboration with the apache sis-dev community.

The code contribution agreement, cited below, clearly allows contributors to continue to reuse and repurpose their own work. As such this proposal is strictly focused on establishing a working relationship with the Apache foundation to facilitate making a subset of the codebase available under a dual license.

...

...

Panel

VII. Assignment of Agreement

In the event the Foundation assigns to a third party any of the rights in or to the Submissions that were assigned to the Foundation by Contributor hereunder, Foundation shall also assign the obligations of this Agreement with respect to such Submissions.

Request

Initial Request:

Anchor
request
request

Panel

Hello all

I'm Martin Desruisseaux, a former GeoTools 2 contributor and now a developer of the Geotoolkit.org project (http://www.geotoolkit.org).
In our search for a community, we had a recent discussion with members of the Apache Spatial Information System project (http://incubator.apache.org/sis/), which is in incubation. A small email exchange gave me the feeling that our design goals could be in phase. We would like to offer them the Geotoolkit.org code. In order to make that possible, we need OSGeo permission to re-license Geotoolkit.org from its current LGPL 2.1 license to the more permissive Apache license. The proposal is not to transfer the totality of Geotoolkit.org to Apache SIS, but to allow them to review the code and pick-up whatever they wish on a case-by-case basis. The transition to Apache SIS would probably be slow and very progressive.

Geotoolkit.org is a fork of GeoTools 2.6 followed by 4 years of developments. The project contains two parts: "core" and "pending". Our proposal is to begin with the "core" part, which include material derived from the following GeoTools 2.6 modules:
* utilities
* metadata
* referencing
* core of coverage (excluding I/O)
* many (but not all) Swing widgets

In 2008 those modules were written (according SVN history) at 95% by myself, Geomatys or IRD institute. The remaining 5% were written by other GeoTools contributors. To my knowledge, everyone signed the copyright assignment on http://download.osgeo.org/osgeo/legal/ which grants copyright to OSGeo. However because the GeoTools community may have vested interest in this re-licensing decision, I wish to ask on this mailing list.

I would like to emphases that this is not a demand for relicensing current GeoTools, but only relicensing of the GeoTools 2.6 code from which "Geotidy" (the Geotoolkit.org precursor) is derived, which is 4 years old. If the community accepts to grant us the permission to relicense 100% of Geotoolkit.org "core", that would be truly appreciated. But in case of bjection, we are willing to rewrite the 5% of "core" code which was not written by myself, Geomatys or IRD.

It the community accepts re-licensing, this would allows Apache SIS to gain services they are currently missing, allows Geotoolkit.org code base to gain a community, and possibly allows the GeoTools project to gain a metadata and referencing library maintained by a trusted foundation, which could complete or replace the current referencing module as GeoTools wish. The Geotk referencing module got 4 years of extensive development since our departure, and has capabilities which are - to my knowledge - unique in the open source world.

Regards,
Martin Desruisseaux

Request withdrawn:

Panel

Hello all

Two weeks ago, we posted a request to the GeoTools PMC asking permission to re-license portions of GeoTools 2.6. However since that time, we reformulated our demand as a request to the OSGeo board to state whatever the Contributor's rights, which is granted "perpetual, irrevocable, worldwide, royalty­free, license to use, copy, prepare derivative works of, publicly display or perform, and distribute the Submission", include the right to re-license his own code. Adrian Custer, who wrote the Copyright Assignment together with a Lawyer, confirmed us very clearly that the intend was to give unrestricted rights to the contributor over his own code, including re-licensing, providing that all other contributions are removed. This is also the right of those who signed the Contributor Agreement instead than the Copyright Assignment.

The OSGeo board is expected to take a decision in their meeting scheduled August 9. If the OSGeo vote is positive, then we would like to withdrawn our request to the GeoTools PMC. We decided to re-license only the code that we wrote, with all other contributions omitted or rolled back. Of course the procedure can continue if the GeoTools community still wants to examine the question, but it could be driven as a procedure independent of our current request.

Regards,

Martin