Re: PEAR Meeting Agenda

> Just a reminder to vote for the PEAR meeting agenda. So far only five (5) people > voted. It is important for you to vote even if you do not attend to the meeting. I will be attending on IRC. Unfortunately, I don't have time to make it in person. As I was unable to comment when the topics were discussed, I'll comment on a few here... > Topics are, please put the order of precedence in the square brackets: > > [1] Review of the PEAR Group > > - Future of PEAR > > [5] Roadmap : installer channels > [4] PEARweb : usability, package ratings, bug reporting, orphaned packages (siberia) > [3] Rules and Processes : common method names like toString, toHTML, etc. > [6] Documentation : what to do to improve the situation Rules and processes should to some extent be subject to the QA team. A uniform API is an aspect of quality. I think they are very important to get people to use pear packages. Glad to see it on the program. Roadmap... I'd really like to see this planned out. Of course, it mostly depends on Greg having time ;-) I hope he'll give us an idea of his long-term schedule sometime ;-) > - PEAR QA > [2] Tasks : what will the QA team do ? > [2] Powers : what it can and cannot do > [7] QA-Team : specific members ? It seems that the first to are basically the same thing, and are already hashed out in the RFC. I've listed them together as priority 2 because I think they should be discussed together when the RFC is discussed. Specific members of the QA team may receive mention, but they should be elected as per the RFC, not appointed. Else we'll get a group of people who are too busy to do much (PEAR Group, anyone?). The core team, at least, should be very active and look at each new release for problems, so if you've got too much to do, don't volunteer. Also, as per the RFC, it is very necessary to have the members scattered across the time zones, so let's not cluster everyone in Europe. See you all there! Klaus