Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85398 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46678 invoked from network); 22 Mar 2015 08:45:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Mar 2015 08:45:41 -0000 Authentication-Results: pb1.pair.com header.from=leight@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=leight@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.46 as permitted sender) X-PHP-List-Original-Sender: leight@gmail.com X-Host-Fingerprint: 209.85.213.46 mail-yh0-f46.google.com Received: from [209.85.213.46] ([209.85.213.46:35201] helo=mail-yh0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 06/75-00828-4318E055 for ; Sun, 22 Mar 2015 03:45:40 -0500 Received: by yhim52 with SMTP id m52so28336213yhi.2 for ; Sun, 22 Mar 2015 01:45:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VfHWBfLlDoSXRj3fl6MT0rorz3GJPfsf7czZrBgkm4I=; b=tGe/fsd/MzQbaXld2sMzfiEsv+/JH2DVVpivDatMcgHVB5x/MtjyeQjxTh75EbAcH6 EE+utXLK3q2+JSRc7ioD3pmJjApvT7xJZUEmtamNsV9YTguYc/V1Dvmb+8dpNWoO/7ym VEaoD7Tf6mTunCH5+U785P4mzgEvNNL8CDG7stcDTaPqF7QbrOjvGqBOEbExS3JXQURm VOl7RzMlUmP8GyuVE280fOsRoDuPE5dnWyIvgtyyUSqIv1cQpTe/nfliG7UKq0VTszM8 WV3r3nuTBXPH35p2FpXq1lp/6apBNTY9GjyCN0sa+NKaz7+Umfye9uKWHbeJ7TPZqDSq ecVA== MIME-Version: 1.0 X-Received: by 10.52.166.134 with SMTP id zg6mr25594030vdb.38.1427013937416; Sun, 22 Mar 2015 01:45:37 -0700 (PDT) Received: by 10.52.177.7 with HTTP; Sun, 22 Mar 2015 01:45:37 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Mar 2015 08:45:37 +0000 Message-ID: To: Patrick Schaaf Cc: Peter Cowburn , internals Content-Type: multipart/alternative; boundary=089e01633ec4d450340511dc92ba Subject: =?UTF-8?B?UmU6IFtQSFAtREVWXSBUbyBSRkMgb3IgTm90IFRvIFJGQyBbd2FzIFJlOiBbUEhQLURFVg==?= =?UTF-8?B?XSDlm57lpI3vvJogW1JGQ11bRElTQ1VTU0lPTl0gQWRkIHByZWdfcmVwbGFjZV9jYWxsYmFja19hcnJh?= =?UTF-8?B?eSBmdW5jdGlvbl0=?= From: leight@gmail.com (Leigh) --089e01633ec4d450340511dc92ba Content-Type: text/plain; charset=UTF-8 On 22 March 2015 at 07:00, Patrick Schaaf wrote: > > Hmm. Is that really the line to be drawn? An RFC, by itself, provides a > good point to spell out a change clearly, and anchor it for reference in > discussion. Discussion on internals itself cannot provide that, it is too > scattered, and POC code provides it at the code layer only. Thinking about > documentation, for example. > Sure, I can agree on RFC all the things. > So, maybe the line is better drawn at what needs a vote, and what does not? > > Just an idea: as soon as an RFC goes up / leaves draft state, could it > have a "needs a vote?" prevoting section? And if a certain minimum opts for > "needs a vote" (within a minimum discussion period after leaving draft), > one must be held? (thinking about a one week period and three or five > needs-a-vote calls, or something similar) > I suppose this could be part of the discussion on list when it is not obvious, then we at least have some documented opinions on the decision, rather than the assumptions of individuals. --089e01633ec4d450340511dc92ba--