On Tuesday, March 11, 2003, at 08:21 PM, Costin Manolache wrote:
As with any standard, the "decision making" is based on a group of
people representing different interests. Apache does have a vote ( AFAIK ),
just like Sun or IBM. Projects should be able to participate - and
we should find a way to apply the apache meritocracy and community rules
in our participation to JCP ( for example by a vote by committers who
are affected or by PMCs ).
One way we can do this is for ourselves to do be spec leads for JSR's. Then we can set the rules for the group, and the license. Jetspeed has been around for a while - it was only recently that IBM (and ?) proposed the JSR. We could have done it long before that.
The communication bonds twart collaboration which degrades innovation. The JCP does not encourage innovative processes which Sun or the Spec lead might disagree with.
The spec is approved by a majority vote. I don't think standard goal should
be to "innovate" - but recognize common patterns and practices and set
ground rules.
Well - that's one way to describe it. The other way is that the JCP is how innovations are brought to the platform - the innovation was done before you tried to make a JSR. For example, Jason Hunter is running a JSR for JDOM. JDOM was done, and the benefits of the software clear, before he proposed the JSR....
geir -- Geir Magnusson Jr 203-956-2604(w) Adeptra, Inc. 203-434-2093(m) [EMAIL PROTECTED] 203-247-1713(m)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
