#48032 change C code license to GPLv3
Closed: wontfix None Opened 7 years ago by rmeggins.

In order to be future proof, the license should change to GPLv3. This includes 389 (389-ds-base), adminutil, admin server, and dsgw. This includes all headers in all files, LICENSE* files, documentation, wiki, and any other places that refer to the license.

Is this going to be GPLv3 or rather GPLv3 '''or later'''?

Replying to [comment:2 mkosek]:

Is this going to be GPLv3 or rather GPLv3 '''or later'''?

GPLv3 or later.

git patch file (master) -- Each source file refers the LICENSE file.

Thanks to Nathan for pointing out the first patch did not include the new LICENSE.openssl and LICENSE.GPLv3+. I've recreated the patch including them.

Copyright (C) 2015 Red Hat
2 see files 'LICENSE.GPLv3+' and 'LICENSE.openssl' for use and warranty
3 information

Richard Fontana (legal) said 'In the file LICENSE, I would delete "for use and warranty information"
(if only because no warranty is being given). The rest is okay.'

So maybe just say "See files 'LICENSE.GPLv3+' and 'LICENSE.openssl' for more information."

Otherwise, ack

git patch file (master) -- LICENSE LICENSE.GPLv3+ LICENSE.openssl (deleting EXCEPTION)

Thank you, Rich!! Replaced the line with:
See files 'LICENSE.GPLv3+' and 'LICENSE.openssl' for more information.

Pushed to master:
ac43090..817bc41 master -> master
commit 88cae40
commit 817bc41

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone:

5 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1363

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. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

2 years ago

Login to comment on this ticket.