Infrastructure Licensing

In developing applications for Fedora Infrastructure we have to worry about how the licenses we use in various bits of code we write interact with each other. This page is to help formulate a plan of action for hw we are going to license works we generate in Fedora Infrastructure to make optimal use of our work.

Goals

• Be able to share code among the various pieces we write.
• Not have our libraries force a specific license on the apps that we write.
• Not have conflicting licenses between our apps and our libraries
• Have a clear understanding of the steps we must take whenever we want to move code from an application under one license to a library under a different one.
• Protect the code we write from being taken proprietary (note, this is not the same for every author, MM for instance is under the MIT/X11 License).

Questions

We need to understand how our licensing choices help or hinder accomplishing our goals in order to come up with a plan of action.

• Can he authors of a work (especially Red Hat employees) relicense their code at will?
• Can Fedora relicense code under the CLA?
• GPLv2 and AGPLv3/GPLv3 are incompatible for combining and linking in compiled languages. How does that work in dynamic languages? Especially python.