commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@multitask.com.au
Subject Re: what's the right way to deal with unlicensed code in sandbox?
Date Fri, 25 Oct 2002 01:04:49 GMT
robert burrell donkin <robertburrelldonkin@blueyonder.co.uk> wrote on 
25/10/2002 07:08:58 AM:

> 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?

+1 on contacting the committers with a timeout option for removal.
--
dIon Gillard, Multitask Consulting
Work:      http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers




--
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