License for Extracted API Documentation

[Toshio Kuratomi <a.badger@xxxxxxxxx>]

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

If a package has API Documentation extracted from source via doxygen,
gtk-doc, or similar, can the documentation have a separate license from
the code-source?  In the particular case I'm looking at (qof) the source
is currently under the GPLv2+ and the doxygen main page lists GFDL as
the license for the documentation.  The code in question has multiple
contributors but I don't know whether the inline documentation was all
created by a single person (who could dual license) or not.  I can ask
if that's important but would like to understand whether I need to or
not first.

- -Toshio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGx2RnX6yAic2E7kgRAtLDAKCZ/VDFKl0uZv0JqJbkhIZli6RTJQCfbdGQ
cgjwn/CpHOgq9sksVt1YgA8=
=iete
-----END PGP SIGNATURE-----

--
Fedora-maintainers mailing list
Fedora-maintainers@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers

--
Fedora-maintainers-readonly mailing list
Fedora-maintainers-readonly@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly