Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96976 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92473 invoked from network); 17 Nov 2016 19:04:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Nov 2016 19:04:27 -0000 Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.214.43 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.214.43 mail-it0-f43.google.com Received: from [209.85.214.43] ([209.85.214.43:32939] helo=mail-it0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6C/23-11917-93FFD285 for ; Thu, 17 Nov 2016 14:04:26 -0500 Received: by mail-it0-f43.google.com with SMTP id c20so47513580itb.0 for ; Thu, 17 Nov 2016 11:04:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pthreads-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hCi6M3aV3DdkLTUs9sNTAKnHH1MquMI5D9W6aePUg9o=; b=VHLqunL4aqnjFS7QtQZ//4lc8uCooy3UxaOSQW+jr26l3Q5BAfvjjxivLMUXN1BTmF DJfF8Qphds09QEFr3d04zYtZokvaDp5bhywo38FGgq5FjHr0ei/npJtBzj59oqvdb2df 9O06FGj5g1ExLb4TpVqTQ9nD19BZWMpao2dfPWrbLv3UibCZKPVnY1YtomxK/S+m3gPZ En7wcHgEWuzLe23JwxKcPZqYafYB7Gu/nruU40UanxC/xq33plJbbqKdiqGwmEp9zgV6 vPRExgPwXfhWrarH/rSzeLQoNlWpXay3bOxzf2GU71/s+jX2hSL6gxWwNZx0Fg6PeyNp /O9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hCi6M3aV3DdkLTUs9sNTAKnHH1MquMI5D9W6aePUg9o=; b=OATpONgYRsiS7KXMMXzKkXS6g0V5fEOaeIj8XPskKpzvVvPIYWhYlW2K6SUCgGv/rc 6v7SxS/Ps4hjqvls0t585NE2b4JALrE9ziCdXAl/j/9GaYMRc1BHm8Jdh2IjxnO5G77m /+xR9lit4mB2IC4pD+GVYjC7QI7hIMqPxkgOgPJOkLsOBbBJVN8ElYvT0pxWsrXZJ/TG V/wENFYwSUcKq8BMCZwr5qg4uowQKjqHiU3p+16+WwN2q+GdUekog5QL0gtawicx8hHw xP/h8lPTxt9ZxOj4KKWU2mysPKc7SqUJeUXFR1YUKCGdx4GBiRXTjmX4751IMlYdeHC6 qN1A== X-Gm-Message-State: ABUngvfQ/MOqFCmNUbQwqdV84ZaqDLQjAYANC6sBRNybFpoigSP6jUYYGLWXeb6xci4cHA9+Pdh6s6cGy06syw== X-Received: by 10.107.147.9 with SMTP id v9mr5231296iod.110.1479409462967; Thu, 17 Nov 2016 11:04:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.102.3 with HTTP; Thu, 17 Nov 2016 11:04:22 -0800 (PST) X-Originating-IP: [109.157.245.230] In-Reply-To: References: <1ff261d9-129e-3b97-adf1-0e3e2aad280b@gmx.de> <8b980bff-8173-a1a3-bed9-1b3b556be6cd@gmail.com> Date: Thu, 17 Nov 2016 19:04:22 +0000 Message-ID: To: Andrea Faulds Cc: PHP internals Content-Type: multipart/alternative; boundary=94eb2c0561628495eb054183db73 Subject: Re: [PHP-DEV] Re: [RFC] Abolish 50%+1 Votes From: pthreads@pthreads.org (Joe Watkins) --94eb2c0561628495eb054183db73 Content-Type: text/plain; charset=UTF-8 Afternoon Andrea, Intention was to just update the voting page, and any other related docs that might exist (maybe rfc template). Cheers Joe On Thu, Nov 17, 2016 at 6:55 PM, Andrea Faulds wrote: > Hi Rowan, > > Rowan Collins wrote: > >> On 17/11/2016 18:03, Joe Watkins wrote: >> >>> Afternoon Chrisoph, >>> >>> The minimum number of votes is going to be the subject of another RFC, >>> let's leave that aside for now. >>> >> >> I'm not sure splitting this into lots of micro-decisions is wise: why >> not discuss a general reform of the voting system, and have a single RFC >> which can then document the agreed system, and supersede >> https://wiki.php.net/rfc/voting? >> > > This might be a good idea, even if we only change the threshold. > > A potential problem with our current system of policy RFCs is I don't > think can we amend existing ones, only pass new ones. This would mean you'd > have to refer to the Voting RFC and the new RFC (as proposed by Joe) to > understand the current policy, rather than it all being in one place. > Worse, if you just read the Voting RFC on its own, you wouldn't know the > threshold it specifies is no longer correct. > > To compare to legal systems for a moment, they don't have to have this > problem. In the UK, we have Acts of Parliament, which pass and become part > of the law. But those acts can amend existing Acts that are already part of > the law, to keep things neat. That makes things simpler, because when you > want to know what the current law is, you only have to refer to the > existing Act as amended, not the existing Act and a new Act which > supplements and possibly overrides it. You can also of course replace > existing Acts entirely, or create new supplementary Acts, but you want to > avoid this when making small changes like the one Joe proposes. > > Creating an RFC which would completely replace the Voting RFC would avoid > people having to refer to two RFCs, one of which overrides the other. > > Alternatively, we could decide to do what the law does, and update the > Voting RFC in place once a new RFC passes, so the wiki page for it would > reflect the amended rules, not the RFC as it originally passed. This is a > wiki, so we do have revision control and could mention on the page that it > had been amended, and link to the original version. (This is, incidentally, > what the UK's legislation website does.) > > Regards. > > -- > Andrea Faulds > https://ajf.me/ > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --94eb2c0561628495eb054183db73--