On Wed, Nov 9, 2011 at 9:04 PM, Stas Malyshev <smalys...@sugarcrm.com> wrote:
>> To summarize: The technical viability of a feature should always be
>> determined
>> through discussion before voting even starts.
> It doesn't matter too much when it happens, as the purpose of the vote is to
> see if the feature is needed/desired in the form that is proposed. That
> doesn't mean it will actually be implemented - there are other conditions
> for that, such as technical viability, willingness to contribute/support,
> etc. It would be best if they would be closed before voting in order to not
> waste time, but one should always realize they are necessary in any case,
> voting or not.
That's what I was trying to say. That implementability isn't much of a
factor for voting,
as it is determined by the discussion, not the vote. By that argument
voting should not
require that you know all Zend API calls by heart (a basic
understanding of PHP internals
might be helpful though), so a restriction to php-src isn't necessary
from that point of view.

>> So, I don't really know. In some way it does make sense to give php-src
>> more
>> voting rights, after all they do know internals better and are more
>> engaged than
>> other contributors. On the other hand it also is kind of unfair for
>> everybody else
> I'm not sure what you mean by "fair" here. PHP project is not some limited
> resource that is in common ownership and should be fairly distributed
> between owners. I think decisions in PHP should be taken by people that have
> the most ability to take correct decisions that would make PHP more usable,
> and it has nothing to do with fairness.
I borrowed the term "fair" from Tyrael's response, though retrospectively it was
a bad aspect to consider, as fairness or such isn't a precondition for
good descisions.
What I should have said is that in my eyes - as outlined in my other replies -
I don't see any compelling reasons why one should distinguish between php-src
contributors and the others.

Nikita

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

Reply via email to