Ross Ridge writes:
> Years ago, I was asked to sign one of these documents for some public
> domain code I wrote that I never intended to become part of a FSF project.
> Someone wanted to turn it a regular GNU project with a GPL license,
> configure scripts, a cute acronym and all that stuff. I said no.
> It's public domain, take it or leave it. Why I should I sign some
> legally binding document for some code I had in effect already donated
> to the public?
Richard Kenner writes:
> Because that's the only way to PUT something in the public domain!
That's absurd and beside the point.
>> How would you feel if some charity you donated money to came back
>> with a piece of paper for you to sign?
>
>A closer analogy: a charity receives an unsolicited script for a play from
>you.
No, that's not a closer analogy. As I said, I never intended for my
code to become part of an FSF project. I didn't send them anything
unsolicited.
I'm contributing to this thread solely to answer the question asked.
Either take the time to read what I've written and use it try to
understand why I don't and others might not contribute to GCC, or please
just ignore it. Your unsubstantiated and irrelevent legal opinions
aren't helping.
Ross Ridge
