Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:35796 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25680 invoked by uid 1010); 25 Feb 2008 16:20:13 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 25665 invoked from network); 25 Feb 2008 16:20:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Feb 2008 16:20:13 -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 82.96.83.42 cause and error) X-PHP-List-Original-Sender: php@stefan-marr.de X-Host-Fingerprint: 82.96.83.42 serv6.servweb.de Linux 2.4/2.6 Received: from [82.96.83.42] ([82.96.83.42:39889] helo=serv6.servweb.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F0/5A-07350-CBAE2C74 for ; Mon, 25 Feb 2008 11:20:13 -0500 Received: from [172.16.16.90] (toolslave.net [85.88.12.247]) by serv6.servweb.de (Postfix) with ESMTP id 7C79B590029; Mon, 25 Feb 2008 17:21:45 +0100 (CET) Message-ID: <47C2EAC2.20106@stefan-marr.de> Date: Mon, 25 Feb 2008 17:20:18 +0100 Reply-To: php@stefan-marr.de User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Pierre Joye Cc: Derick Rethans , Lukas Kahwe Smith , PHP Developers Mailing List References: <0F1A0758-D3AF-4B1C-B2E0-7BEEEE1ED2C6@pooteeweet.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Redirected: By TestProxy Subject: Re: [PHP-DEV] RFC: documentation collaboration toolchain From: php@stefan-marr.de (Stefan Marr) Pierre Joye schrieb: > Limiting the RFC to existing php.net's member sound like a bad idea > and create CVS accounts only for a RFC does not sound any better. > > I would rather use the wiki for the complete process. Once a RFC > reached a "stable" status, we can add it to a RFC repository. > Would agree on this. For me at would have been a burden to get such an account upfront. Since I'm not part of the core dev team. Kind Regards Stefan