I am tired of endlessly going around the same boat, trying to be understanding, trying to come to a workable solution, and not being able to. All the issues and viewpoints are on the table. I believe our committers have the ability to make a rational decision, and that we ALL will abide by that decision. The only way to move forward at this time is a simple vote. What the committers decide is what the Avalon community will do--no exceptions.
1) Vote to work with the "meta-info" package as is [ ] +1 I am fine with @avalon.extension and @avalon.stage [ ] -1 I am not fine with those attributes or I don't like the library [ ] 0 I don't care
2) Vote to work with the "meta-info" package, but moving the "extension" and "stage" attributes in the "lifecycle" namespace [ ] +1 I would like @lifecycle.extension and @lifecycle.stage [ ] -1 I am not fine with those attributes or I don't like the library [ ] 0 I don't care
3) Scrap the library completely, but preserve the attributes already agreed upon. A new library will be created and all Avalon containers will support it. [ ] +1 I don't like the library as defined, or it has become too contentious [ ] -1 The existing library is fine [ ] 0 I don't care
The result of this vote will help us move forward and get past this stupid debate.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
