I write my programs in Python. It's typical to use long comments in source documenting how program interfaces are used (Lisp and Haskell have language-integrated support for such documentation too; something similar is used for Java). There are good tools to make a manual with additional text containing such comments. My program is licensed under the GPL, the manual under FDL.
To do this I need to dual-license all such comments in the source. This prevents me from adapting into the documentation existing comments written by other developers. Most Python programs that I know don't have this issue, since they use the BSD license for both source and documentation: this is not a solution that I want to use. I'm not the only developer having this issue: it was discussed several years ago for libstdc++. (The GNU Coding Standards discourage this practice, IMO maintaining a separate API documentation for a library is too much work and would easily lead into obsolete or missing documentation.) Having a GPL-compatible documentation won't solve this issue completely (it would help reusing documentation in source), using a single GPL-compatible license for both code and documentation does (like copyleft-next).
pgpRCoqVwN8BY.pgp
Description: PGP signature
