launchpad development|
Size: 1025
Comment: streamline
|
← Revision 6 as of 2011-07-27 23:37:47 ⇥
Size: 1024
Comment: misread my email
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| || Client side or general purpose code || [[http://www.fsf.org/licensing/licenses/gpl-3.0.html|GPLv3]] '3.0 only' || Yes || | || Client side or general purpose code || [[http://www.fsf.org/licensing/licenses/gpl-3.0.html|GPLv3]] '3.0 only' || No || |
Choosing An Open Source License
When releasing code as open source for the first time, you'll need to choose a license.
![/!\](/moin_static198/lp20/img/alert.png "/!\"){kind=small}
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' |
No |
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.
