Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:61806 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43167 invoked from network); 26 Jul 2012 07:49:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2012 07:49:31 -0000 Authentication-Results: pb1.pair.com header.from=php@stefan-marr.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=php@stefan-marr.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain stefan-marr.de from 81.20.134.149 cause and error) X-PHP-List-Original-Sender: php@stefan-marr.de X-Host-Fingerprint: 81.20.134.149 vps-1012701-4512.united-hoster.de Received: from [81.20.134.149] ([81.20.134.149:45152] helo=vps-1012701-4512.united-hoster.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A6/40-41030-986F0105 for ; Thu, 26 Jul 2012 03:49:30 -0400 Received: from soft83.vub.ac.be ([134.184.43.183]) by vps-1012701-4512.united-hoster.de with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1SuIp2-0005qg-P8; Thu, 26 Jul 2012 09:49:25 +0200 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii In-Reply-To: <50105BFC.80900@ajf.me> Date: Thu, 26 Jul 2012 09:49:19 +0200 Cc: PHP Internals Content-Transfer-Encoding: quoted-printable Message-ID: References: <50105BFC.80900@ajf.me> To: Andrew Faulds X-Mailer: Apple Mail (2.1084) Subject: Re: [PHP-DEV] RFCs and organisation From: php@stefan-marr.de (Stefan Marr) Hi Andrew: On 25 Jul 2012, at 22:50, Andrew Faulds wrote: > I think someone (perhaps me) should write an RFC on how to write an = RFC Note that a new page create on the wiki in the RFC namespace comes with = a template that gives some guidance on how to write an RFC. Lukas based it on my original Traits RFC, since that one was considered = to be a nice example. At least it was kind of complete with regard to = the essential parts of an RFC: - intro - motivation - full description (up-to-date following the discussions) of the = proposed feature - with examples and use cases - summary of semantics - a patch And then based on discussion: - FAQ or common misconceptions - alternative proposals - rejected features - change log Best regards Stefan --=20 Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525