Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52969
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.199.177.89 as permitted sender)
To: Stas Malyshev <smalyshev@sugarcrm.com>
CC: Pierre Joye <pierre.php@gmail.com>, PHP Internals
	<internals@lists.php.net>
Thread-Topic: Voting Process (was: [PHP-DEV] Re: Voting does not belong on
 the wiki! (Was: [PHP-DEV] 5.4 moving forward))
Thread-Index: Acwju4mMVI/geX/lRt2X0REy1lGzy///0Y4A///FTdA=
Date: Sun, 5 Jun 2011 20:55:54 +0000
Message-ID: <887FE7CFF6F8DE4BB3A9535F53AFD06A4930624C@il-ex2.zend.net>
References: <887FE7CFF6F8DE4BB3A9535F53AFD06A4930609E@il-ex2.zend.net>
 <4DEBE420.50005@sugarcrm.com>
In-Reply-To: <4DEBE420.50005@sugarcrm.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: RE: Voting Process (was: [PHP-DEV] Re: Voting does not belong on
 the wiki! (Was: [PHP-DEV] 5.4 moving forward))
From: zeev@zend.com (Zeev Suraski)

I'm fine if the entire 'Feature selection and development' part goes out of=
 the RFC, but if there's any reference to how features are determined, we'd=
 better get it right.
Making changes once we've approved this RFC is going to be much tougher.  T=
his is big stuff - it's no coincidence we didn't have such guidelines for a=
lmost 15 years.

Honestly there are other parts about the voting process that are much hotte=
r potatoes than the points I brought up - such as who gets to vote, is 50%+=
1 enough or do we need stronger majorities for substantial language changes=
 (67%/75%), can someone who failed passing an RFC just put it up for anothe=
r vote right away or is there some sort of a cool-off period, etc. etc.  I =
think all of these need to be answered before we let this RFC govern how we=
 do feature definition.

Zeev

> -----Original Message-----
> From: Stas Malyshev [mailto:smalyshev@sugarcrm.com]
> Sent: Sunday, June 05, 2011 11:17 PM
> To: Zeev Suraski
> Cc: Pierre Joye; PHP Internals
> Subject: Re: Voting Process (was: [PHP-DEV] Re: Voting does not belong on
> the wiki! (Was: [PHP-DEV] 5.4 moving forward))
>=20
> Hi!
>=20
> > I'd still like to hear from others what they think about my proposal.
> > I'd like to update the Release Process RFC with these suggestions if
> > people like them.
>=20
> I think these voting process additions totally make sense. But I am not s=
ure it
> makes sense to put everything in one release RFC. The reason for that is =
that
> we don't want to endlessly amend and improve the RFC without having it
> actually agreed upon, I would rather prefer to agree on what we agree, ha=
ve
> it as base for the future and then add other stuff. I've noticed a tenden=
cy on
> the list to lose the major goal behind endless amendments and tweaks and =
not
> doing what we agree on because we disagree on some minor detail. So maybe
> it would make sense to have release RFC separate (without spelling out th=
e
> voting process there) and voting RFC separate which would define the voti=
ng
> process?
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227