In that case, be sure to use a license that correctly states your requirements. The GPL is not such a license (unless, of course, you consider your copyright statement to be adequate notice) [1]. By releasing code under the GPL, you're _explicitly_ saying that the copyright notice is _all_ the credit you require. You can't then change your mind and add further restrictions in a random mailing list post.
Well, the copyright notice may well constitute sufficient acknowledgement, especially if my package is one of dozens that make up the derivative product. I'm certainly not going to insist on a whole paragraph for one minor library function, for example.
While the GPL may not explicitly *require* any acknowledgement beyond the copyright statement, nothing says that you can't ask for a more elaborate, voluntary credit in the back of a user manual as a simple matter of professional courtesy and good will. I think that would be especially appropriate if one particular GPL package were to make up the bulk of the derivative work, as appears to be the case with Slimserver and MP3Beamer. If I were a contributor to such a package, I know I'd be more inclined to provide a little free technical assistance to someone willing to go beyond the letter of the agreement.
--Phil _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
