We have a received the following request on the geotools-devel email list.
The code contribution agreement, cited below, clearly allows contributors to continue to reuse and repurpose their own work.
To meet the above request:
- Letter of understanding between the OSGeo board and the Apache Foundation on the acceptance of the above project into incubation
- The request is for a case-by-case selection of files - as such our existing procedure for migrating code between projects will suffice
- Email sent to geotools-devel notifying of the requested file, followed by approval from any PMC member
- Ensure headers carefully track and credit contributors
- To save time we may be able to build a short list contributors who are confident their work can be relicensed outside stewardship of the GeoTools PMC
- Martin Desruisseaux
- Jody Garnett for personal contributions only (cannot speak for former employers)
Discussion on this topic has taken place on several email lists:
- http://lists.osgeo.org/pipermail/board/2012-July/thread.html#9853 OSGeo Board
- http://lists.osgeo.org/pipermail/discuss/2012-July/thread.html#10657 OSGeo Discuss
- http://lists.osgeo.org/pipermail/discuss/2012-July/010683.html Excellent Summary
And the next board meeting:
Related discussion about migrating code between projects and carefully across license changes:
Alternatives shortlisted in email discussion:
- Dual-License (ie this proposal). The OSGeo Foundation has a mandate to promote the development of spatial software, under any OSI approved license. The GeoTools PMC has stwerdship of the codebase including the ability to approve a dual license (using this proposal). As such a dual license approach is feasible under foundation by-laws, and is within the mandate of the PMC.
This proposal offers guidance on how quickly isolate candidate code (using a whitelist of contributors) and how to dual license remaining code of interest (via email request).
- Relicense GeoTools. While this is an option, and would facilitate the above request, we would prefer to consider relicensing more carefully. While we were able to migrate where the developers are with our move to github hosting, migrating license is a more extensive undertaking.
- Case-by-case. Minimal license change approach, asking apache to review files on a case-by-case basis and contact us relicense the final set
This proposal is in DRAFT, review welcome.
Voting has not started yet:
- Andrea Aime
- Ben Caradoc-Davies
- Christian Mueller
- Ian Turton
- Justin Deoliveira
- Jody Garnett +1
- Simone Giannecchini
- Martin Desruisseaux
- add your name here
- Determine what assurances the Apache Foundation needs in order to proceed
- With other projects Compone a letter of understanding, allowing the apache foundation to relicense a subset of the codebase
- Assemble a whitelist of contributors who's work can be dual-licensed without further consultation
- For code falling outside of the above whitelist our existing framework to relicense code should be sufficient.
- An email sent to geotools-devel notifying of the requested file, followed by approval from any PMC member
Apache 2.0 License
AFTER (using wording of current apache license):
This initial request is within the limits of the GeoTools code contribution agreement: GeotoolsAssignmentToOSGeo.pdf as detailed in the following sections:
Section II Assignment of Copyright
Section V. Obligations of the Foundation
The relative section of the above mentioned bylaws is:
Section VII. Assignment of Agreement