www-jcp-open mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <Ralph.Go...@dslextreme.com>
Subject Re: Are proprietary TCK's compatible with open standards?
Date Thu, 05 Jul 2007 07:55:45 GMT
Sam Ruby wrote:
> We need to find a way forward, a way that breaks the JCP loose from 
> the "corrupting"[1] influences that so evidently drive it today.  So 
> in the spirit of brainstorming, I'm forwarding on to this mailing list 
> a notion expressed by Dalibor Topic[2]:
>
>     "Proprietary software should not be allowed to be tied in as a
>     fundamental part of an open standard in any form."
>
>     "It doesn't matter if such software comes from IBM, Sun, Oracle,
>     BEA, Red Hat, Google, Nokia, or someone else. It doesn't really
>     matter what the restrictions are, either."
>
>     "If the TCK is proprietary, a JSR needs to be voted down, until it
>     is resubmitted with that bug fixed."
>
> My initial thoughts: is this step necessary?  No, not if there are 
> viable other alternatives.  Is this sufficient?  Actually, yes.  It 
> would neatly solve both the FOU and NDA issues.  It has the added 
> benefit of addressing the behavior as opposed to the person.
>
> So, given that pretty much every idea is being shot down, I for one 
> could support a policy built around such this notion.
>
> What do others think? 
I totally agree. Whether it will be sufficient to change Sun's (or 
anyone else's) behavior remains to be seen. I also don't see how it will 
influence anything that Apache is not part of, such as Open XML.

Ralph


Mime
View raw message