#1547 Update 'tpsclient' license from LGPL v2.1 to GPL 3
Closed: migrated by dmoluguw. Opened by mharmsen.

The 'pki-tps' package contains the original 'tpsclient' which is based upon software which required the LGPL license (as it is comprised of native-based code related to the original pki-tps Apache plug-in), and a newly rewritten java-based Tomcat implementation of 'pki-tps'.

  • Do we need to carry both the LGPL license for 'tpsclient' as well as the GPL license for 'pki-tps'?

To which legal responded:

It doesn't matter too much but I guess for simplification I would suggest updating
the license of tpsclient to GPL. LGPLv2.1 explicitly contemplates that such license
migration from LGPL to GPL may be done.

Per CS/DS Meeting of 08/10/2015 - 10.3

Changed subject from "LGPL v2.1 to GPL2" to "LGPL v2.1 to GPL 3" since we will not change it in the 10.2.6 timeframe.

Metadata Update from @mharmsen:
- Issue set to the milestone: UNTRIAGED

Metadata Update from @edewata:
- Custom field feature adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None
- Issue set to the milestone: 10.6 (was: UNTRIAGED)

The whole license probably should be changed to GPLv3:
https://www.gnu.org/licenses/rms-why-gplv3.en.html

This is needed by ticket #2978.

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2106

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

Metadata