> -----Original Message----- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > > In conclusion - where is the Avalon team today in this trust model? > Clearly a team needs to feel in control and masters of their own assets. > I think this could have happened if the same approach were applied to > the developers here as was applied to the Excalibur team. The remaining > question is one of identity. Should the team start with a new identity > around which it creates its own community as it sees fit - or should the > team rebuild the Avalon identity? > > I think a new identity is in the best interests of everyone.
And just about everyone agrees a "new identity" is a good idea. Look, let's step back for a moment. A week ago the Board issued a set of comments and recommendations to both Avalon and the Metro team. For those who have it, it would be worth while to re-read that message. Also re-read Brian Behlendorf's response. There were a series of concerns, one of which was the need for three projects (Metro, Avalon, Excalibur). When we began to discuss the idea of only two projects (Metro and Excalibur) we got an initially favorable response from several Board members. However, since that time the discussion has turned to arguing over community styles, transparency and rehashing a lot of old issues. This has left many wondering if Metro really belongs in the ASF at all. We are further away from a TLP today than we were a week ago. Much further away. If Metro is interested in an ASF future it will require the Metro team to seriously review and consider the concerns of the Board as raised in the original response. Unless the minds of quite a few officers and board members can be changed, it will also require Incubation. Merlin will most likely not be allowed to simply stay in Avalon either. Therefore, the Metro team must begin evaluating the recommendations given to them and determine the course of action they would like to take. Otherwise, the decisions will be made for them. J. Aaron Farr SONY ELECTRONICS STP SYSTEMS (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
