So get active on the codebase - get voted in as a committer after demonstrating commitment and ability to work with the community - and get yourself onto the PMC - and from there influence the decisions that are made. In the meantime - decisions have been made and Avalon is moving forward. The question is not if we moving forward - the question is how to deal with the pragmatics of migration and user transitioning.
I have sent in Fortress patches previously, I will continue to do so; I am certainly very active in and committed to creating Avalon components that the entire community can use. Having said that, given that very capable developers (no, let me state it, the *ORIGINAL AUTHORS OF AVALON AND MOST OF THE CONTAINERS*) who are already committers cannot do this because of the veto that you would give to everything that is non-Merlin, there is hardly a chance that little, old me could do anything to influence decisions.
I love the words "ability to work with the community"! Indeed!
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
