Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107478
To: "'PHP Internals'" <internals@lists.php.net>
References: <67911D3D-CBC1-4847-9F4B-3C895EF84741@newclarity.net> <4ed1fb31-a8e4-bff7-54f5-c66c95c692c4@alec.pl> <CAG9XoMTU+X1zTjdZekjHE6b0nDnckxryLKhbNumWa_d45B6tqw@mail.gmail.com> <CAPKYkKyKGHyDL4_VkvKDHBofZ_hkB7Bmcbx8Bik4x2nE9ANcLw@mail.gmail.com> <CAG9XoMQQJb_ggFMzZ-nU05+ju0GCXD5-FALmN3uD_B9OJ7AWKA@mail.gmail.com>
In-Reply-To: <CAG9XoMQQJb_ggFMzZ-nU05+ju0GCXD5-FALmN3uD_B9OJ7AWKA@mail.gmail.com>
Date: Thu, 10 Oct 2019 21:47:44 +0300
Message-ID: <000301d57f9b$33bed320$9b3c7960$@roze.lv>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQISnFxyQeCclhmHsfM8J1nbGX9vQwKZlyhLAiPm504AsbOAbQHOwouQpqAJVxA=
Content-Language: lv
Subject: RE: [PHP-DEV] Constraints and userland@
From: r@roze.lv ("Reinis Rozitis")

> -----Original Message-----
> From: Benjamin Morel [mailto:benjamin.morel@gmail.com]
>
>
> And we could change the RFC process to either:
>=20
> - require a 2/3 majority of votes *in each category*
> - *or *require a 2/3 majority in the *average of all three categories*
> - *or *give a weight to each category (like 50% to core members, 30% =
to OSS
> developers and 20% to the rest of the world) and calculate the result
> accordingly
> - *or even* something like require a 2/3 majority in at least 2 of =
these
> categories
>=20
> ... or any other rule we could think of.
>=20
> I quite like this idea of splitting voters into 3 categories, where =
each category
> has a weight that does not depend on the number of people who voted =
inside
> it.
>=20
> Something like this would seem fair to me. Thoughts?


The problem in this is that - what good is a vote/RFC if no one is there =
to implement it?

Like you could get and overwhelming majority/weight in all the =
non-developer groups but what then? Are you then forcing someone to =
write the code? Pick someone from the group(s) who voted for or pay =
someone to do it (quite valid though)?

IMO even now all the discussion in the internals@ (hence the name) for =
the developer (RFC author) is just to see if any other code contributor =
has something to say about his idea. The rest can voice their concerns =
but as long you don't really contribute yourself I doubt you get to =
choose in the end..

rr