#1503 Licensing Guidelines for apps we write
Closed: Fixed None Opened 14 years ago by toshio.

Discuss and approve these Infrastructure Licensing Guidelines.

https://fedoraproject.org/wiki/Infrastructure_Licensing

The aim is to:

  1. List the problems that can be encountered in licensing
  2. List the things that canbe done WRT relicensing
  3. Give a default for licensing of applications that will work well with each other

Tickets for the apps we have. I'm planning on starting with python-fedora since we need to relicense that to LGPLv2+ no matter what. I think mdomsch will close the MirrorManager ticket soon as it's already MIT and that should be fine.

https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assigned&status=reopened&keywords=~LICENSE

python-fedora has been relicensed. notes:
* Most time is spent waiting for contributors to respond that it is fine to relicense.
* bzr stats or the equivalent in your VCS may make it easier to see who has contributed code but transifex submissions may obfuscate that.
* VCS annotate is the best way I found to find who actually committed what code.
* Since it is possible to relicense when no license was given when the code was contributed, you mostly have to worry about people who added new files and who put license headers on the files. However, it's very nice to get consent from all of the large contributors.
*A graphicaldiff tool (meld) seemed to work the best for actually updating the code.

Complete details:
https://fedorahosted.org/fedora-infrastructure/ticket/1507

It was decided to go with GPLv2+ for all applications instead of GPLv2+ for non-web apps and AGPLv3+ for web apps. Licensing Policy updated:
https://fedoraproject.org/wiki/Infrastructure_Licensing

Seems this is resolved. Closing.

Login to comment on this ticket.

Metadata