Hello.
I am very encouraged by the recent discussions. I think we are starting
to build a consensus, to establish dialogs and lay the foundation for an
exciting future. In an effort to capitalize on this momentum, I'm
starting the following, simple, vote:
Avalon as a single platform
Now, I don't like formalities, so I was initially hesitant to issue this
vote, but I feel that given the context this vote will consolidate our
community. Language can be tricky sometimes, so I'll try to clarify:
Single Platform = a single specification, single container, single
architecture.
This means Avalon components will work in any Avalon compliant container
according to some yet-to-be TCK. This is not a vote on WHAT the
specification will be, or WHAT the container exactly will look like.
We'll work on those thing step by step (though I believe we're well on
our way with things like Merlin and Leo's Aspects idea).
Voting Rules:
YES (+1) = I will to work on a single Avalon Platform
NO (-1) = No, I'm opposed to a single platform
ABSTAIN (0) = I'm abstaining.
If this vote passes, we will begin effort to redesign the website, start
on the TCK, start hashing out these tougher issues of specifications and
handle legacy management. Each of these will be accompanied by the
appropriate proposal and vote process.
I'm really excited for this!
--
jaaron <http://jadetower.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
