Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Allow me to highlight Andrew C. Oliver's blog story
that covers Sun's latest Java Cartel Process (JCP)
This title follows the normal path of declaring
everything a non-problem even if it is known to still
have issues. Are we there yet: no, of course not and
you bloody well know it. The real question is once you
get there will anyone still care?
1. Eliminate all use of NDAs in the JCP process.
Nothing can ever be fair and equitable or even appear
that way without sunlight. If I don't know what is
going on, I assume its shady cigar smoking boardroom
stuff. All PR will go bad for you until you swallow
2. License TCKs under an OSI-approved open source
3. Upgrade ALL JSRs to JCP 2.6 without pulling
another JSR-168. It didn't even work for you.
4. Allow companies willing to produce a revenue
report which is below $100,000/yr to join under the
same rules as individuals (this would allow
individuals to incorporate and LLC thus limiting their
personal liability for participation. Presently Sun
could exercise a great deal of control over
individuals by threatening suit). This would obviously
not apply to JBoss and would questionably apply to
SuperLink (won't know till the taxes are done).
5. Allow third party administration of TCK
6. Give up your "right of origin" veto, etc. I
don't give a damn if you haven't used it. It isn't
fair, it isn't equitable and you damn well know it.
Community my butt so long as you've got the biggest
bat and everyone knows it.
7. Require prior implementation and that all
specifications be driven by a Reference Implementation
(RI) wherever possible. Design by committee without
code to prove it is just stupid and produces dumb
things like Remote Entity Beans. Set standards for
this including unit tests proving RI conformance and
cross ref the unit tests to the spec.
That and take IBM up on their offer in a fair and
equitable non-shady honest way (no fake open source),
stop playing both sides of the open source fence and
we'll be there. Quite simply it is not a logical
argument that an open source compliant and official
JDK implementation means the forking of Java. You own
the trademark, can still require TCK compliance to use
it, etc. Microsoft has ALREADY forked Java. Quit
screwing around with perception games (from what I
hear, the JCP birthday at the Apachecon was a big hit
until you implied it was better than open source, give
me a break). Do "it" and be proud or learn how to do
the "big bad guy" thing the right way. You Decide.
Full story @