Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wrong licence in maven central #93

Open
ghdiska opened this issue Apr 11, 2024 · 1 comment
Open

wrong licence in maven central #93

ghdiska opened this issue Apr 11, 2024 · 1 comment
Assignees
Milestone

Comments

@ghdiska
Copy link

ghdiska commented Apr 11, 2024

Hi in mavencentral licence file is wrong https://raw.githubusercontent.com/opengeospatial/geoapi/master/LICENSE.txt

according with geoapi website can be fixed to http://www.apache.org/licenses/LICENSE-2.0.txt ?

@desruisseaux desruisseaux self-assigned this May 3, 2024
@desruisseaux desruisseaux added this to the 3.1 milestone May 3, 2024
@desruisseaux
Copy link
Contributor

At the time when GeoAPI 3.0 was released, OGC used its own license (BSD-like) for software. OGC switched to Apache license only later. The change of license has been applied on GeoAPI 3.1 and 4.0 development branches, and should be in-force if/when those branches will be released. The existing 3.0.1 and 3.0.2 releases on Maven Central were supposed to be releases with only bug fixes or dependency upgrades, so their license has been unchanged. Whether a change of license can be considered as a bug-fix release looks like an open question to me.

Given that the GeoAPI 3.1 development branch is close to completion and a session has been scheduled for the next OGC meeting in Montréal for discussing review and release plan, maybe we can keep the 3.0.x releases as-is and have the license change only in 3.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants