Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60567
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4FB0AE18.1060902@sugarcrm.com>
References: <CAF+90c-Xfs0n-E=+s3g9GE=UZHGvPYdagCho0ma65u6YB+0Tgg@mail.gmail.com>
	<CAF+90c-_78TufE8+L8UNfuXLwPW9QgrSWyQaHvS8TOjj40-_cQ@mail.gmail.com>
	<op.wd8z16uqidpuyk@damnation.mshome.net>
	<CAEZPtU7BvZEHh4wQErQh2E+=REV0W=RXx-iPxUAiesTS39neRg@mail.gmail.com>
	<CAF+90c-N1Sj9TwT8WFdsrjCbY32g5NJnLzQcaUzfJocd1Nmn0Q@mail.gmail.com>
	<CAEZPtU7B=kj9YVzV4pH4yWRs9t3VfEAF4HeMnjkT+tWqqOSR5g@mail.gmail.com>
	<4FB0AE18.1060902@sugarcrm.com>
Date: Mon, 14 May 2012 10:33:56 +0200
Message-ID: <CAEZPtU4GWAPSxvB4vHZZgELf2j9tcivo-BkeHR9KoWXH6oXkew@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Nikita Popov <nikita.ppv@googlemail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Re: [VOTE] Vote change for empty() RFC
From: pierre.php@gmail.com (Pierre Joye)

hi Stas,

On Mon, May 14, 2012 at 9:02 AM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> As Stas suggested earlier, it would help if you can convince one
>> person having voted none or both to choose the empty only option, then
>> you should be good. It is not that good in general, but for 1/3 of a
>> voice for something like that ... :)
>
> AFAIK 2 of the people voting "both" (myself included) already said they
> are OK with "empty only".

If the other one can raise his voice, then we are good.


> But in general, what is happening now is exactly what I was concerned
> about when we have started this voting thing - that decision becomes
> matter of formal incidents having nothing to do... well, with anything
> on the merits of the proposal.

Partially correct but mostly wrong too. Let me explain it below.

> Support we lack one vote and do not
> implement it - then we didn't implement a feature because somebody who
> could add one crucial vote was on vacation or too busy or missed the
> email.

Right now, one has one month to vote. Yes, the voting vote is only two
weeks but he can always say his opinion before leaving. As of those
being too busy during one month to read a RFC and vote, then that's
bad for them and for php.

However, the issue we are suffering is not about people being busy or
being in vacation. The issue is that we are a very few amount of
active developers. I'd to say maximum 5 for daily to weekly active,
maximum (and I am very optimist here) 10 for monthly. And last but not
least, most of the historical contributors are not active anymore, no
matter how. This is the problem, not the voting.

So the key is to get more active contributors and we are doing well
again. Most of the top 5 contributors for this year are new
contributors (except you and me :). We have to improve that too. But
we can't stop to move and organize our next releases because some
legacy developers have moved to other interesting projects (with all
due respects).

That being said, I was thinking to send notification emails when a RFC
is proposed and when it enters the voting phase. A one time email for
everyone then each developer has to opt out if he does not want these
notifications. That should help to get some active devs voting while
they are totally not interested to follow internals (bad but their
choices).

> I don't think it's a good situation.

me neither, but I have a different view on it.

Cheers,
-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org