Choosing An Open Source License
When releasing code as open source for the first time, you'll need to choose a license.
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, lazr.config and lazr.delegates, under the LGPLv3 partly because the most related community, Zope, uses a BSD-ish license.
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.
(Note: Canonical employees open-sourcing internal code should also see the internal wiki for the process to follow.)