Re: A complete summary of doc.keliglia.com status

> * RFC: > From my experience, when an RFC (Request For Comments) is published, the > only way to provide comments is to answer with an mail. Some comments > get lost > in the archives.. Sometimes the RFC slowly dies without bringing anything. > I've sent an RFCs for this website 6 or 7 months ago, for the user > notes system > a year ago.. nothing was done until today, and I'm not sure to be able > to provide > all the comments that I've collected since then. > > I asked Yannick to make a simple RFC reader/comment system on the website. > It's a basic stuff, and it's online, waiting for your comments. > > Maybe we can create an RFC dir in each documentation repository to discuss > the particular topics (restructuring the install part for phpdoc, using > phpdocumentor for peardoc, ..), and an RFC dir in the website CVS > module to > discuss some global issues (how do we document a class ? I know Steph has > been waiting for an official and global answer since ... too much time). As a note you might want to have a look at PePr, it's the system PEAR uses to manage package proposals and RFCs. It's in pearweb cvs module, you can see it in action at http://pear.php.net/pepr/pepr-overview.php Arnaud.