Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:61807 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49894 invoked from network); 26 Jul 2012 09:41:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2012 09:41:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 64.22.89.133 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 64.22.89.133 oxmail.registrar-servers.com Linux 2.6 Received: from [64.22.89.133] ([64.22.89.133:48379] helo=oxmail.registrar-servers.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1E/41-41030-ED011105 for ; Thu, 26 Jul 2012 05:41:51 -0400 Received: from [192.168.0.200] (5ad32874.bb.sky.com [90.211.40.116]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oxmail.registrar-servers.com (Postfix) with ESMTPSA id CD0E7C30018; Thu, 26 Jul 2012 05:41:46 -0400 (EDT) Message-ID: <501110C5.1030808@ajf.me> Date: Thu, 26 Jul 2012 10:41:25 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Stefan Marr CC: PHP Internals References: <50105BFC.80900@ajf.me> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFCs and organisation From: ajf@ajf.me (Andrew Faulds) Hi Stefan, I made an RFC page on it. http://wiki.php.net/rfc/howto It's not really an RFC, more a meta-RFC or informational wiki page. It would helpful if you could edit it too. I just want to make an obvious go-to place for info on this. Thanks. On 26/07/12 08:49, Stefan Marr wrote: > 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 > -- Andrew Faulds http://ajf.me/