commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: what's the right way to deal with unlicensed code in sandbox?
Date Thu, 24 Oct 2002 21:30:59 GMT
Isn't the whole point of the sandbox the ability to play? If someone
has not put a copyright on their code while playing, we should not
bother them but let them continue to play undisturbed.

At 22:08 24.10.2002 +0100, you wrote:
>there are files in daemon which appear to be missing license files. this 
>should be fixed.
>
>i'm wondering: what's the right way to do about this?
>
>to me, it doesn't feel right diving in there and changing the code. this 
>may actually make the problem worse since whoever did the modification 
>couldn't be sure that the ASF actually had copyright over the code. it 
>would have to be the original committer.
>
>i suppose there should be an attempt to contact those responsible for the 
>component and ask them either to add the correct copyright notice or 
>remove . what's the right way to do this? post the the commons-dev list? 
>or to the general list? or direct to the the committers themselves?
>
>i suppose the proper thing to do would be to remove the files from cvs. i 
>legal terms, the safest course of action is probably to do the immediately 
>and then let the component committers put them back in once they have 
>proper copyright notices. it would feel a bit rude to remove them before 
>giving the committers a chance to correct matters but it might be the 
>proper course of action.
>
>ideas? opinions?
>
>- robert

--
Ceki

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793



--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message