Lukas Kahwe Smith wrote: > Hi, > > I think its painfully obvious that a system to manage the voting is > needed. Like I said, ideally it should also have an email interface. > People should be able to vote from +1 to -1 and be able to add a > comment. Notifications should be send to this list about the start and > final result of the vote. > > Voting itself should be split by people with access to cvs.php.net and > those that do not. This is open source, everybody can voice their > opinions, but the developers of the project should have final say. > However if the end user and developer votes diverge greatly it will > still be an important hint to take into account. That being said, end > user polling imho belongs somewhere else and before the final developer > vote. > > The features of PEPr in PEAR cover all of this quite well, except for > the email interface. I personally would not need that and maybe its too > much of a hassle to get this done in a reliable and secure way.
PEPr, unfortunately, is very tightly bound to the pearweb code, and would be a big hassle to separate as it currently stands. We have been working (by we, I mostly mean Helgi) for over a year now trying to clean up pearweb and still are only about halfway through the codebase, but when PEPr is tackled, I will let you all know. Of course, if there is someone enterprising who wants to assist with that specific part of the cleanup, the code is in cvs at pearweb/. PEPr-specific code is located in pearweb/include/pepr, pearweb/public_html/pepr, and pearweb/cron/pepr.php. Thanks, Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
