On 19/03/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
You have to be kidding me..
The only problem I see is that people are all caught up in policies /
processes but I've yet to hear what the actual root "problem" is. I'm
sure it's intended to somehow prevent something nasty that has
happened in the past but these policies don't have any logic that I'm
able to follow. Why does the ASF need to dictate how we vote on
releases?
I don't have the references to hand, but I believe it is something to
do with providing some form of legal protection. There may be other
reasons as well.
Maybe I'm just having a bad morning, but for some reason this really
rubs me the wrong way and feels extremely inefficient.
As far as I know, only one formal vote is actually required by the
ASF; this must be by the PMC on the release itself.
On 3/19/07, sebb <[EMAIL PROTECTED]> wrote:
<snipped>
> The problem here seems to be that it is not possible to use one vote
> to do both; therefore it seems to me that the sensible thing to do is
> to have two votes.
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
