On Thu, Jan 31, 2019 at 4:55 PM Nikita Popov <nikita....@gmail.com> wrote:

> I agree with Joe here that we should handle the question of voting margins
> separately. Your RFC is a much more comprehensive reform, which contains a
> number of points that look highly controversial to me (such as the eligible
> voter changes). It may take a long time until we reach a satisfactory
> consensus there.
>
> On the other hand, this RFC is very simple and at least to me a complete
> no-brainer. I already use 2/3 majority for all my votes, because I very
> strongly believe that changes to PHP need to be held to a much higher
> standard than a simple majority. It is outright shameful that functionality
> can be added to PHP if 21 vote in favor and 20 against. That's not a
> consensus, that's a complete disagreement.
>
> It's not necessary to decide all questions regarding the RFC process at
> once. Voting threshold is a very self-contained issue and we can decide it
> separately from other controversial changes.


Well, I think there are several issues here.

One - while the passing threshold is probably one of the most painful
issues with the current Voting RFC, it's hardly the only one.  Given it's
taken us many years to start tackling this, I think it's safe to say that
as a rule, we lack the motivation to tackle these issues.  I think it's
pretty clear that if we solve the threshold issue independently, it would
likely be years before we tackle the other issues, if ever.

Secondly - the threshold and voting eligibility are not, in any way,
independent.  They're two fundamental aspects of the same topic - how votes
take place.  A 2/3 majority out of a subset of ~200-300 people is very
different from a 2/3 majority out of a potential group of several thousand
people

Thirdly - implementation issues - that the original Voting RFC did NOT
intend to cover, later became covered by it by virtue of assumption.  I
think that implementation issues (implementing the same functionality that
we have right now in a better way) should not be subject to a vote, and
moving the threshold to 2/3 makes the current situation even worse than it
currently is, and should be for the most part up to the maintainers of the
code.

So no, I don't think we can simply 'abolish narrow margins' without
thinking about the implications as well as tackling the other shortcomings
of the 2011 Voting RFC.  With due respect, it reminds me of the hasty
approach we took back then, and that wasn't good.

Unless I'm missing something, we're currently in absolutely no hurry - we
just released 7.3, we can spend as much time as needed (to a reason) on
hashing out updated voting rules.  I'm speaking on behalf of myself, and
maybe Dmitry thinks differently - but I'm certainly fine waiting with that
RFC for several weeks or even a couple of months if needed.

Zeev

Reply via email to