Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77474
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2e56d0ee-978b-4b64-9410-b3127272c197@email.android.com>
References: <8DEFB90E-0F7F-4876-890D-D4AD1C655D87@ajf.me>
	<alpine.DEB.2.11.1409221231540.4267@whisky.home.derickrethans.nl>
	<D32F58E1-EA5F-4888-B569-502FFC043542@ajf.me>
	<CAPhkiZzPj8HbaVXp7SrhN2BaX6EYQGuWZwtT6A+HKoyKV4w+QA@mail.gmail.com>
	<alpine.DEB.2.11.1409221428570.4267@whisky.home.derickrethans.nl>
	<CAEZPtU6gpYdDaCU5E1PdzXWahDY9tAmkb7-rAbFNuZxXDJSNww@mail.gmail.com>
	<CA+S5htPxeGdTmZZNaJvkChUOUfYrP=0sq+9UzZ2zSs0O3ZiA+Q@mail.gmail.com>
	<2e56d0ee-978b-4b64-9410-b3127272c197@email.android.com>
Date: Mon, 22 Sep 2014 18:08:30 +0200
Message-ID: <CAEZPtU55o0Ao3OFYsH_svp-jH8wcgazSeF2grsjhwcHTXhm7Wg@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: Rafael Kassner <kassner@php.net>, Derick Rethans <derick@php.net>, 
	PHP internals <internals@lists.php.net>, Andrea Faulds <ajf@ajf.me>, Andrey Andreev <narf@devilix.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Is it fair that people with no karma can vote on RFCs?
From: pierre.php@gmail.com (Pierre Joye)

On Mon, Sep 22, 2014 at 5:38 PM, Johannes Schl=C3=BCter
<johannes@schlueters.de> wrote:

> Slightly provocative:  Why should I be forced to maintain code by people =
who
> don't want to maintain it themselves? Probably even due to votes by peopl=
e
> about whom I don't know anything? Mind that most maintenance work by
> most contributors happens in free time on a voluntarily base.

The same applies to many new codes. Even more for my team as we have
to take care of many issues where only a few actually takes care of.


> And no open source doesn't mean democracy as governing model. The
> democratic part is that people who don't like it can fork the project and
> eventually receive a higher traction. But no, "one man one vote" and full
> equality doesn't work out. (i.e. if a modules primary maintainer vetos a
> change I have to mind that [which doesn't mean I have to agree in the
> end])

Primary maintainers doing only maintenance but not having actually
designed/implemented an extension fits in this description. That
sounds pretty awkward to me, for anything landing in the core. Landed
in the core? Dictartorship goes away.

>>Using separated voting count isn't an option? Like only internal
>>changes
>>are voted only by people with karma and features/changes/small BC
>>breaks
>>that affects userland are allowed to anyone. This way I believe is easy
>>to
>>say if either internals and community agrees with the proposed change
>>and
>>community people are making their opinion count.
>
> There are no plans (and enough people who'd veto such plans) to close
> the mailing list. Everybody might state their opinion and we are happy to
> receive (constructive) feedback and ideas here. And yes, this can be a bi=
t
> painful due to different forms of "trolling" but leads to better results =
respecting
> more opinions than a yes/no vote.

Never worked before and it will suddenly work? I am open to know how
one can make it works. Unless you mean to go back to individual
deciding everything for a given area or ext.


Cheers,
--=20
Pierre

@pierrejoye | http://www.libgd.org