Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53083 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91294 invoked from network); 6 Jun 2011 21:29:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jun 2011 21:29:48 -0000 Authentication-Results: pb1.pair.com header.from=chadfulton@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=chadfulton@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: chadfulton@gmail.com X-Host-Fingerprint: 209.85.218.42 mail-yi0-f42.google.com Received: from [209.85.218.42] ([209.85.218.42:33841] helo=mail-yi0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 39/F1-23189-5A64DED4 for ; Mon, 06 Jun 2011 17:29:39 -0400 Received: by yie16 with SMTP id 16so586642yie.29 for ; Mon, 06 Jun 2011 14:28:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type:content-transfer-encoding; bh=lNKL7mlrLiZSgcIORuJZ30f12ADt0LSeeBZ9i5S4lY8=; b=U0m6GxnoUV1FxL1C40BmH3QG3ZWLwypJQAuqH7gh1pQSs08xvx6j0NqZvkc4b8370H 7LtFNCPZFLyeal8eAnkGm85InCbfCEy+CNqKWES3V973cqdx5mKCjiSq9wxd29pXGGwd DZUZgYee+Yl0APjwTKcpy46Jp+JpC7bBzoLrk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=qj61bIqF/zjBX51vWt1MFrBI9AA30Z0yWvFARrY2oEjJNRzHIveZOXe9Gr8kQwS3lq 9y5yFWk4YPXxyBGPvcEzQe4uoCw/osh8ZYhw/UJ/B9E3mSXRcCAZdMZtHpkdN2ubBhOf U9uKkqils0IYKQU0uaqmt66hrGdSNu3rgV5Wg= Received: by 10.90.66.12 with SMTP id o12mr4834241aga.116.1307395725194; Mon, 06 Jun 2011 14:28:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.90.89.4 with HTTP; Mon, 6 Jun 2011 14:28:25 -0700 (PDT) In-Reply-To: References: <887FE7CFF6F8DE4BB3A9535F53AFD06A4930609E@il-ex2.zend.net> <4DEBE420.50005@sugarcrm.com> <887FE7CFF6F8DE4BB3A9535F53AFD06A4930624C@il-ex2.zend.net> Date: Mon, 6 Jun 2011 14:28:25 -0700 Message-ID: To: dukeofgaming , PHP Internals Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: Voting Process (was: [PHP-DEV] Re: Voting does not belong on the wiki! (Was: [PHP-DEV] 5.4 moving forward)) From: chadfulton@gmail.com (Chad Fulton) On Mon, Jun 6, 2011 at 12:27 PM, dukeofgaming wrot= e: > > I have a little proposition here. > > I'm not =97at least currently=97 known for any app or framework, but I'd = like my > voice to count, that is, if and only if the rest of the community thinks = I > make sane arguments that are worth considering. > > I'm perfectly aware that the fame one could gain from taking production c= ode > to visible success should be an indicator of an educated opinion, however= , I > think this might lead to a closed group who can vote, and I like the > openness of this community, even if the general process is chaotic, it st= ill > gets the warm and fuzzy feeling of an open source community. > > OTOH, if a completely open group's votes were all considered, the final > decision could just end up being a matter of numbers outnumbering other > numbers. If I get it right, this is the current problem. > > So my proposal is that the voting privilege could be given on the basis o= f a > *web of trust*, and if I'm not mistaken this is a little like what the > concept of karma works here (I'm fairly new here). Not sure if there shou= ld > be a voting to elect voters or if it could/should be something more lax, = but > I don't think the requirement to vote should be fame. I'm similarly placed (as are many here I think), in the sense that I have not done any internals work and I am not one of the lead devs for a well-known project. Much as I think my opinions are great, I don't believe we should have a vote or, if we do, that it shouldn't count for as much as others', for the following reasons: - Long-term commitment: we want people voting who (1) know the history of past PHP discussions on topics and why they were rejected or postponed, (2) understand the "PHP way", and (3) have shown commitment to *maintaining* PHP - Perspective: developing *with* PHP is not the same as developing *for* PHP internals. Feasibility, interoperability, maintenance concerns, and more are things that, as long as I've read the list, are often misunderstood or downplayed by people who develop *with* PHP and want a shiny new feature (including me). - Unified vision: we want people who are taking the whole PHP picture into account to be the ones doing the voting. Much of the volume on the list is very narrowly focused - this is a good thing for discussion of specific features, but a bad thing for picking which features to include in PHP. So, I would advocate a "white list" of core devs for formal voting (of which, for example, I would not be a member). I think this mailing list has grown sufficiently that "public opinion" can be gauged from here: everyone can write their opinion without giving them voting privileges. If you haven't already, I recommend you read the (incredibly long) discussions from last summer on type-hinting. They convinced me that sometimes a feature that sounds good is simply not a good fit for PHP for reasons which many did not (still do not?) understand. Chad Fulton