Amsterdam meeting agenda

Hi, I think we could take the opportunity of the PEAR Amsterdam meeting to discuss further the topics that recently raised on the list. IIRC we have already setup an agenda but maybe we could add some points to it. For example, I am thinking about the following : - Future of PEAR ---------------- Decide whether we want PEAR more open and how to reflect this new openness both in the way we communicate (slogan, banners, PR) and the tools we provide: think about how to improve PEPr. - Online documentation system ----------------------------- I am thinking about some sort of automatic inline doc extractor that would create the API documentation, using PHPDocumentor, and add it to PEARDoc automatically. All this would be done on PEAR web. The process will be the same as with the new release upload. Actually, it could even be made at the same time. I think we also need some sort of CMS for the documentation system so that we could easily add tutorials and class description. And the process should also be possible in the other way, I mean you provide your class and the API doc is copied from the PEAR site to your class. You get a fully commented and updated class back. The goal is to get rid as much as possible of Docbook, which is in my opinion the biggest mistake made by PEAR. I think we should also discuss the adoption of another format like reSt to replace it. Docbook is a barrier to proper doc for PEAR, let's admit it now. I could maybe take care of developing that in July or August if nobody is voluntary, and if I am allowed to use my own frameworks/tools. - Method names -------------- It might also be needed to create a list of common methods we use in PEAR and put it online in the CS docs. I am thinking of toString(), toArray(), display() or show() , toHtml() or get()... - Package ratings ----------------- Can they be trusted, will they really be useful, how to implement them successfully ? - Where to find the source, online ? ------------------------------------------------------------ I hate it when the package I am interested in doesn't have its source in PEAR CVS. I have to download it, untar it, read the source in an IDE. I suggest that every packages should be available for browsing in CVS or Subversion repositories with online access. Or at least as .phps. Feel free to add topics... For the meeting, it will also be nice to have some sort of voting system online where people not present at the meeting could express their vote too using a web interface and their pear account. Or we can totalize votes in IRC. Bertrand Mansion Mamasam