Hello,
This is a question on how to post online documentaion and code changes to a software package that is covered under GPL v2.

I want to post some documentation and code changes to some software that falls under GPL v2. Since I want it to remain in public domain how do I do this. I' am using docbook format and will be converting to html to publish.

I've looked at copyleft that says to put this in your documentation:

(http://www.gnu.org/copyleft/fdl.html#SEC4)

Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled "GNU
Free Documentation License".

and GPL v2

(http://www.gnu.org/copyleft/gpl-howto.html)

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA

Thanks

Kent N

Please note that documentation and software covered by the GPL is not public domain. It is covered by a licence. The licence forbids it entering public domain.

Anyway - what do you mean by "post". You want to start a thread in LQ on your documentation? Put it in the wiki? Or do you mean "publish"? If so - where and how? Publishing companies usually have their own rules....snip...So what is your problem?

If the software has a maintainer, you should contact them and let them know what you are up to. They may want the source (or a patch). Similarily with the documentation. Anyway, it's polite.

(The previous developer/author should be in the original documentation.)

Thanks, I've contacted the responsible parties and inquired about documentation.

Kent
N