Hi!

> What's the threshold of absurdity here?  That we could debate.  However, it 
> is 
> not 0.  (I'd personally put it in the 10-20 range, bearing in mind that not 
> all of them would vote all the time anyway, just like core developers, but 
> others may feel differently.)

I am not sure defining it in numeric terms is the correct approach.
After all, the RFC doesn't say now "20 non-C developers", it says
"PHP-FIG members". We have no control (and no desire to control) what
that means, but we pre-commit to giving all these people, whoever they
are and will be, voting rights now and forever in the future. I'm not
sure that's the right approach.
In fact, I'm also not sure "20 non-C developers" would be the right
approach - why specifically 20? What if we need 21? What if we can't
find even 10 who are really qualified? (all hypothetical of course) That
just sounds so arbitrary.
So I think we need to find something that doesn't look arbitrary and
doesn't look like putting voting eligibility in the project outside of
project members' control.
-- 
Stas Malyshev
smalys...@gmail.com

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to