Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:35794 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 10745 invoked by uid 1010); 25 Feb 2008 16:04:51 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 10730 invoked from network); 25 Feb 2008 16:04:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Feb 2008 16:04:51 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.162.179 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.162.179 el-out-1112.google.com Linux 2.4/2.6 Received: from [209.85.162.179] ([209.85.162.179:22935] helo=el-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 33/37-07350-127E2C74 for ; Mon, 25 Feb 2008 11:04:49 -0500 Received: by el-out-1112.google.com with SMTP id n30so1424874elf.17 for ; Mon, 25 Feb 2008 08:04:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=uas06arZf/oXaQDdhJsPoIXtfGB7iVyRuy7FW8XwvlU=; b=dIg/h712FgIel97/mZekV3YXD/IbVoif+YvAFYbS0qDNputXBwXDtMKhG+Z8YgQ63GcaBDVkyqs4fmUUo1SuzV6rtvR+oPXjvQMHRd5acZEIHClKvXkv+B7P7A7iFqo1lweXr2lTCtERuQDfzTkznebQom3VraEI/i+HcjeUej8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hR7OBXSatvOIXR+sx5OVTZ6kYSBM5D5zlER6ULVaelC8XGQotDLmfUBhz2XhR0FOoS111Vv0wJ0QCCsKtWyucgDHVK/vOsXp0qgZlR7zuoS5/MXk39hiMC7SsE9GzlLHt5BJ1bV49ruJ89GqLC3KaoNVeLXFeCmnckAt8EMV3/k= Received: by 10.140.191.14 with SMTP id o14mr2232604rvf.247.1203955485675; Mon, 25 Feb 2008 08:04:45 -0800 (PST) Received: by 10.141.116.12 with HTTP; Mon, 25 Feb 2008 08:04:45 -0800 (PST) Message-ID: Date: Mon, 25 Feb 2008 17:04:45 +0100 To: "Derick Rethans" Cc: "Lukas Kahwe Smith" , "PHP Developers Mailing List" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <0F1A0758-D3AF-4B1C-B2E0-7BEEEE1ED2C6@pooteeweet.org> Subject: Re: [PHP-DEV] RFC: documentation collaboration toolchain From: pierre.php@gmail.com ("Pierre Joye") On Mon, Feb 25, 2008 at 3:59 PM, Derick Rethans wrote: > On Sat, 23 Feb 2008, Lukas Kahwe Smith wrote: > > > Personally I prefer going with a wiki, because I do not have much affection > > with CVS for these kinds of documents (actually I do think that the README's > > should be in CVS, which is why I worked with Hannes on creating the current > > php.net/reST interface). I have put this document up on my wiki [12], and I > > will keep it uptodate. > > I'd go for RFC in CVS/Rest, and the todo's in a wiki. 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. VC are perfect for source codes and relatively static contents but nor for documents edition like what we need for RFC, todos or other similar documents (no source code). Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org