RE: [PEAR-DEV] Plans for pear.php.net

What I think is important: we need to ensure that people can easily read up on 1) how to propose 2) when a package is accepted 3) what to do when a package has been accepted we also need to make sure that anyone can do all of the above. Especially 3) has been problematic lately. I can see that a webpage might help in making this process more transparent. But there is also the danger that this will separate ML discussions from what is going on at this web page. However it would be nice to be able to follow projects submissions without having to read pear-dev all the time nor forcing everyone to check both the ML and this webpage to stay uptodate. So a solution that link both would best optimal but a bit unrealistic (that would require somehow being able to determine what packages relate to the package proposal - that would be doable with a unique id in the subject - and then parse that mail for relevant conent - not so realistic). So basically I would say that we need to make the process a little more transparent with written guidelines. So that the package developer can ensure that the process moves forwards because he knows how the process is supposed to go. Finally we need to ensure that someone with enough power and time is around to grant CVS access for new developers whos packages have been accepted. One final thing: Lately most of the packages that stayed or remained in "limbo" were packages where a correct name could not be found quickly. Lets write a good guideline for that as well, so that discussions such as this don’t drag on forever. Regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de