Is Bazaar's document distributed under GPL?

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> I think the next steps here are:
> 
>  - Regardless of what we do in the future, it is desirable that our
> documents be clearly labeled with the terms that pertain to them now,
> which is GPL.  If someone would like to update it, that would be good.
> 
>  - Is a CC licence better than GPL, especially with regard to
> encouraging more documentation, translation or redistribution?  It
> seems possibly so, but I'd like to know from Inada or others whether
> it appeals to translators?
> 
>  - Canonical's policy states a preference for CC-BY-SA (sharealike, ie
> a kind of copyleft iiuc) -- is that better or worse for our purposes
> than CC-BY?
> 
>  - Should we move all our docs to be CC-BY-SA or CC-BY?  Consistency
> seems good.  There may be some questions about docs autogenerated from
> code etc but they should be soluble.
> 
>  - Should/can it be dual CC/GPL?  Is that even possible?
> 

I'm pretty sure you can license the same stuff under as many licenses as
you want, as long as you are the copyright holder. (And we've generally
been good about making everything (c) Canonical).

>  - What is the FSF's opinion?
> 
>  - What is Canonical's opinion?
> 
> "All docs are CC-BY-SA and GPL, all code is GPL" is fairly clear and simple.
...

> 
> Meaning the code and documentation?  I see your point but that seems
> to lock us to GPL, since a non-copyleft licence for the code is not on
> the cards.
> 

Sure, but that may be the most reasonable way forward.

I can understand where something like CC would be a better fit for docs,
but especially given incompatibilities with GPL I would just go GPL...

And I do think we have a high chance of stuff in doc migrating to a help
topic, etc.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq27aMACgkQJdeBCYSNAAMCQQCfV1rn6As0a0Tjjnn+mMVh7zJg
Ds8AnjCz72cTcG2WYLG+lW1tzWFuW3mY
=2dUO
-----END PGP SIGNATURE-----