Hi Lukas, Am Dienstag, den 19.02.2008, 20:09 +0100 schrieb Lukas Kahwe Smith: [...] > 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.
I agree. > 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. > > 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? I think more important than the technical implementation details is the concrete RFC template and the process how to work with such RFCs. We should have one to show a submitter what we expect to know about a new feature. I've tried to create one from Stefan great RFC and added a few points I felt was missing (http://lars.schokokeks.org/php/php-rfc.txt). To the process: First of all, someone authors an RFC. As long as the RFC is in not ready, there is a "not ready for review"-comment in the proposal. Once the author feels the proposal is ready, he sends a mail to internals. Once the mail has been reached internals, an RFC number is assigned to the proposal (by one of the wiki administrators or whoever maintains the numbers). The discussion takes place on internals, and two results may raise. Accepted and declined. The last one is definite, while there might be "accepted but change x, y and z" responses. cu, Lars -- Lars Strojny Senior Software Developer MediaVentures GmbH (http://mediaventures.de)
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
