www-jcp-open mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "robert burrell donkin" <robertburrelldon...@gmail.com>
Subject Re: Are proprietary TCK's compatible with open standards?
Date Sun, 08 Jul 2007 13:10:30 GMT
On 7/6/07, Geir Magnusson Jr. <geir@pobox.com> wrote:
> On Jul 4, 2007, at 7:46 PM, 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.
> That does solve it very neatly.  No muss, no fuss.  I'd just suggest
> that we announce any such policy publicly before acting on it.  We
> will get painted as extremists, though.  Just something to deal with,
> I expect.
> I look forward to see what company leads the charge there.

the FSF have always been better at politics than the ASF. i hope that
the FSF in general (and Dalibor in particular) will take the lead on
these wider issues.

- robert

View raw message