To view parent comment, click here.
To read all comments associated with this story, please click here.
JCP is a big money play. You can join up all you want, you won't be able to have a say on what Sun does with their code, or any of other comanies who've sunk money into staking out their licensing claims via JSRs. That's the community the "C" in JCP really means, not individual developers.
Unless one has a few million dollars to put on the table, all an individual at the JCP can do is pretend to have some influence.
The JCP is no third party, it's ran by Sun exclusively. Sure, there is an EC, but it has no real power, as Roy Fielding from ASF has explained on Apache's legal-discuss mailing list: http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200604.m...
"Sun legal currently has complete authority to prevent publication
on jcp.org of any specification that doesn't meet Sun legal's
requirements (which are determined by Sun at their own discretion).
As such, the EC is entirely irrelevant to the actual policy and
procedures imposed on spec leads. I suggest that the EC might want
to address that issue in a revision of the JSPA, since the actual
publication process occurs behind the scenes and allows Sun to
control the content of a JSR *before* it is presented to the EC
for a final ballot."
There you go, from someone who knows the inner workings of the 'third party' JCP.






Member since:
2006-04-30
Open-Sourcing the Reference Implementation isn't relevant. If you want the fate of Java to be completly free, you got to free the specification and turn it to some 3rd Party Consortium/Foundation such as the W3C or Apache
The Java specifications has already been turned over to a 3rd party. It is called JCP, and you are free to join yourself and have your say how to open source java.