Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:35606 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76470 invoked by uid 1010); 19 Feb 2008 19:34:32 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 76452 invoked from network); 19 Feb 2008 19:34:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Feb 2008 19:34:32 -0000 Authentication-Results: pb1.pair.com smtp.mail=david.coallier@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=david.coallier@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.184.224 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: david.coallier@gmail.com X-Host-Fingerprint: 64.233.184.224 wr-out-0506.google.com Linux 2.4/2.6 Received: from [64.233.184.224] ([64.233.184.224:48741] helo=wr-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/41-55225-54F2BB74 for ; Tue, 19 Feb 2008 14:34:31 -0500 Received: by wr-out-0506.google.com with SMTP id c38so2224249wra.17 for ; Tue, 19 Feb 2008 11:34:26 -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:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=Rg+qQZ6jDg3Ryfw8AtzMBBh5oFeskkdewGA5zxqqmuw=; b=ooFIaqsVGp24FgR5TE7HMtjMSq3dBGUQKZ1Vx4t2pkbaN8+1s5QproqYPEcygUqdsQiJWx0Os39Ajh8JFjs9vKNkJiAFWSQjHBTeQ8xkpuJXsZ966eE5+nIE0Jqs4w9MZK3NIHMg5RpZ+HFETzBCIFX9mdROSMBA+lqCDRnzvAQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=rbsD/X1zYDuTqkiGWp9KgiWY5qpWCP+Sy0qwuSpXw70lsRdoyoDnH7I0w+95YNNF3D3B8FEO37+TsDJmUP48Anp6QKG+tRBYkC/81adgcc/OMcrwv71pNBJgBIq407lS3ryc3Ceyvv9OPGSp05C5bkS5GRTsVBSRwHtuqjzk4Xw= Received: by 10.114.106.1 with SMTP id e1mr6716343wac.95.1203449665279; Tue, 19 Feb 2008 11:34:25 -0800 (PST) Received: by 10.114.13.11 with HTTP; Tue, 19 Feb 2008 11:34:25 -0800 (PST) Message-ID: Date: Tue, 19 Feb 2008 14:34:25 -0500 Sender: david.coallier@gmail.com To: "Lukas Kahwe Smith" Cc: "Stefan Marr" , "PHP Developers Mailing List" In-Reply-To: <744ABBE0-17C0-4AB7-8BB1-E5CFC0573A7F@pooteeweet.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <744ABBE0-17C0-4AB7-8BB1-E5CFC0573A7F@pooteeweet.org> X-Google-Sender-Auth: 92f258679f799f4d Subject: Re: [PHP-DEV] Role model RFC From: davidc@php.net ("David Coallier") On Feb 19, 2008 2:09 PM, Lukas Kahwe Smith wrote: > Hi, > > I really like what Stefan did here with his traits RFC. Very solid > work, even if there are still some people not convinced if they want > this feature in, I have seen little complaints about the way this > proposal was made. Quite the contrary actually. I would like this kind > of detailed thought to become more the norm. Even if at the very > beginning of an idea this quality may not be immediately attainable, > it should be the goal. So for every idea we should have at least > someone who tries to bring the proposal to this kind of level as the > discussions progress. Most definitely, thanks to Stefan for this. I have rarely seen such RFC in PHP lately. This is.. wow, from simple example to a bit more complex and real life examples, simple texts, the reason why we need this and a bit more about MI. The external links to further readings on the subject are great and the thesis is even better (A bit long but very interesting). I think this can make a lot of good to PHP's RFC process if handled correctly. Let's just hope we do it correctly :) > > For this proposal I would hope that it would be put on some host we > can trust to not disappear and be updated with the feedback. I am > still dreaming of a php.net wiki for this kind of stuff. If interested > I do of course offer wiki.pooteeweet.org to host these RFC's for the > time being. Using php.net/reST has the draw back of requiring > cvs.php.net karma for maintenance, which would be problematic for new > comers, unless we can do karma on a per file level for this? Wiki is such a great idea, what were the (political?) reasons for not having it ? No one to maintain it ? > > regards, > Lukas > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- David, Re-read what you are replying.