Diff for "ChoosingALicense"

Not logged in - Log In / Register

Differences between revisions 4 and 5
Revision 4 as of 2009-03-06 14:21:57
Size: 1030
Editor: kfogel
Comment: Refer awkwardly to internal wiki for now, to avoid redundancy.
Revision 5 as of 2011-07-27 23:34:56
Size: 1025
Editor: lifeless
Comment: streamline
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Don't try to do it alone. Instead, please mail the appropriate development list and ask -- the licensing of related projects may be relevant, due to license compatibility issues. For example, we released two LAZR packages, [[http://pypi.python.org/pypi/lazr.config|lazr.config]] and [[http://pypi.python.org/pypi/lazr.delegates|lazr.delegates]], under the [[http://www.fsf.org/licensing/licenses/lgpl-3.0.html|LGPLv3]] partly because the most related community, Zope, uses a BSD-ish license. /!\ If releasing previously proprietary code Canonical staff must follow the internal process specific to that situation.

|| Situation || License || (For Canonical Launchpad developers) Is management signoff needed ||
|| Server side specific code || [[http://www.fsf.org/licensing/licenses/agpl-3.0.html|AGPLv3]] '3.0 only' || No ||
|| Client side or general purpose code || [[http://www.fsf.org/licensing/licenses/gpl-3.0.html|GPLv3]] '3.0 only' || Yes ||
|| Code that needs to integrate tightly into some external project / has compatibility constraints || Discuss on the launchpad-dev list || Yes ||
Line 8: Line 13:

(Note: Canonical employees open-sourcing internal code should also see the internal wiki for the process to follow.)

Choosing An Open Source License

When releasing code as open source for the first time, you'll need to choose a license.

/!\ If releasing previously proprietary code Canonical staff must follow the internal process specific to that situation.

Situation

License

(For Canonical Launchpad developers) Is management signoff needed

Server side specific code

AGPLv3 '3.0 only'

No

Client side or general purpose code

GPLv3 '3.0 only'

Yes

Code that needs to integrate tightly into some external project / has compatibility constraints

Discuss on the launchpad-dev list

Yes

That said, generally we use AGPLv3 if it's server-side code, and GPLv3 for anything else. Never the or later versions, just an exact version number of the license.

ChoosingALicense (last edited 2011-07-27 23:37:47 by lifeless)