Stephen McConnell wrote:

<snip/>


Berin:


There are no technical issues in your email.

Correct, they are management issues. (Management in the sense of code management, not in the sense of personell management).

Instead what you have said is that you are:

(a) opposed to introducing something into the Avalon namespace that you don't understand

Correction: that all the committers don't understand (which happens to include me).

(b) feel that a broader base of developer knowledge is needed

On this ONE issue.


(c) that more user experience is needed

On this ONE issue.


All of these points I can understand. However, your vote does not say this - in fact it calls up people to make a decision on a subject that is directly linked to a question concerning extension management that you yourself do not feel competent to address at this time.

It is a question of putting it in an alternative namespace until the time we are on the same page. I.e. managing the change to the API.


I think that some time and experience with a released Merlin will go a long way towards addressing all three of the points you have raised. It would ensure a broader knowledge base, greater experience, and as a consequence, future actions can be taken with full knowledge and responsibility as to the actions we propose, the votes that we take, and the implications of those decisions.

We are on the same page on 90% of the issues. Everything not related to lifecycle extension is good to go.

I want to publish the 90%, with the hopes that we come to 100% over time.
Instead of removing the tags altogether, I proposed to put them into an
alternative namespace for the immediate release, with the possibility that
they (or something similar to them) will be incorporated later.

That is all I am asking us to agree to. We can't blindly be all or nothing.

--

"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]



Reply via email to