You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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 ?
The text was updated successfully, but these errors were encountered: