Re[2]: [PEAR-DEV] PEAR/PHP CVS karma solution

Hello Pierre, From Friday, September 9, 2005, 2:30:47 PM, you wrote: PJ> http://news.php.net/php.cvs/33869 PJ> End of the karma discussions. Then kill the "CVS Access" field for developers profile and cvs_acls tables in pearweb database. If not now - it will never be used. I can't understand why don't you want to automate PHP.NET a bit more and add ability for package maintainers to allow/deny CVS access to their source code base subtrees for *existing accounts* without all this bereaucracity. Ready solution to make PHP.NET more developer-friendly and community-oriented and nobody even reviewed the concept. I'm disappointed. It is not that I'm spend whole day making the patches, but the overall lack of visibility of PHP progress. No roadmap about upcoming features and release dates, no visible project planning, sometimes there is a kind of feeling that complex bugs and issues are being skipped, there is no accessible feature requests and enchantment interface with user votings/suggestions/history and _overall_ statistics, rather poor and insecure (in terms of network security - not PHP code, of course) developers interface. I welcome trend to hide excessive developers information and obscure features from users, but for development process I'd like to see something more convenient than a tons of useless letters and search button. PHP.NET encompasses a lot of projects, but users have hard times trying to figure out what these PEAR/PHPDOC/LIVEDOCS and other means. I really want to see some kind of PHP.NET project map with their status, developers, themes and roadmaps. This map along with project goals and guidelines would improve the way for new developers to quickly connect to the process and help with development. PJ> For new accounts, one still has to do a cvs account request, this is a PJ> normal and understable process. t --