On Thursday, January 31, 2002, at 01:11 PM, Sam Ruby wrote:
>
> That addresses the issue for most, but not all jars.  As an example:
> http://www.webgain.com/products/java_cc/usage.html .  Take a look at the
> last time in particular.  Pretty clear, eh?
>
> There are a number of licenses out there that contain restrictions or
> requirements that trigger on distribution.  The GPL and Sun's Binary Code
> License are two.
>
> For those jars, we need to either (1) find alternatives, (2) work with the
> license holder, or (3) require each developer to obtain the code
> themselves.
>

Sorry, you're misunderstanding what the -1 was for. It was just for the 
idea of blindly removing all jars and trying to replace them with a 
technical solution that will take months to implement. I was thinking that 
questionable license jars were already banned from CVS. At least that was 
my understanding from when we donated the Xindice code which was why we 
removed anything under any kind of viral license. I'm not debating whether 
questionable licenses should be allowed or not, just that the idea of 
blindly pulling all jars seems like a rather knee jerk reaction. It's like 
punishing the whole class because one kid did something wrong.

 From looking through the list of jars I didn't see very many that were 
under questionable licenses. This means a better approach is to focus in 
on the ones that are a problem while also clarifying the license and 
source of all the others. That plan made sense to me, pulling all the jars 
doesn't.

> - Sam Ruby
>
>
> ---------------------------------------------------------------------
> In case of troubles, e-mail:     [EMAIL PROTECTED]
> To unsubscribe, e-mail:          [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
Kimbro Staken
XML Database Software, Consulting and Writing
http://www.xmldatabases.org/


---------------------------------------------------------------------
In case of troubles, e-mail:     [EMAIL PROTECTED]
To unsubscribe, e-mail:          [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to