Craig L Russell wrote:
> This is an interesting turn. The Jini web site doesn't currently say  
> anything like this. It talks about "the specification" and "the  
> implementation" as separable pieces.

They are "separable", and I'm not suggesting that change.  At the same
time, they have not been that "separated", and I'm not suggesting that
change either. :)  Almost all of the specs and code that are proposed
as a starting point for the ASF project have been developed by a single
team at Sun (with varying degrees of community input).  With successful
incubation at ASF, that should turn into a more diverse team, but I
don't see a necessity to separate. The notion of public interface with
multiple private implementations is a core part of Jini architecture, and
a core design tenet of the Sun team, to be instilled as necessary when
mentoring new committers. I don't see that separability disappearing easily.
What I'm suggesting goes away is not "spec vs impl", but the broad-based
formal approval process for deciding that a spec is a "standard".

> I wonder if others in the Jini community have this same objective?

There are definitely people in the community that want to see the
existing Jini community process maintained for approving standards.
I used to be one of them.  But, when we've looked for volunteers
committed to running that process, there are very few takers.

> Would it make sense to update the jini.org web site once consensus is  
> achieved?

To my mind, consensus as such will be demonstrated when we have an
ASF project that successfully exits incubation.

> This is a pretty important step, probably equally important as your  
> decision to use the Apache License for Jini. I don't want to impose  
> any arbitrary barriers to acceptance into the Apache incubator, but  
> I'd like to see a wider discussion of abandoning the "standard".

To my mind the wider discussions have already taken place within
the Jini community.  At some point, I stop wishing for what could be
in theory, and start executing on what I think can be in practice.

- Bob

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to