_brian_d_foy writes: > furthermore, if you truly want to transfer rights, then you > have an entirely different headache involving attorneys, > paperwork, and other bookkeeping.
My feeling is that this can be done as a kind of shrink-wrap license around submitting patches. By submitting a patch, you agree to .... There's precedent for this not being a clusterfuck. Apache and others manage to have contributors assign copyright to a central entity. If it works for them, it will work for us. > a single source that can grant permission can also deny it. an > author should not have to ask permission to use his own work. The author should if the author gives it away. This is unlikely to be a big problem, either. Very little of the FAQ went literally into the Cookbook--most of it was original text and code. We were the authors of both works, which were ostensibly quite similar. If it wouldn't have been a headache there, it shouldn't be a headache anywhere else. It's think it's ridiculous to keep copyright with individual authors in a joint document like this. If I write something, do you have to seek my permission to make a change to improve the grammar? You are, after all, creating a derived work. Nat
