Re: [pear-webmaster] Re: cvs: pearweb /public_html/trackback trackback-admin.php

Hello Pierre, From Saturday, October 22, 2005, 12:20:24 PM, you wrote: >> 1) if you haven't tested the code, don't commit it >> 2) if you can't test it, post a patch to pear-webmaster >> 3) if you've tested it, commit it >> 4) if it's obvious you haven't tested it, you get a warning. On the >> second commit of obviously untested code, your cvs karma is revoked >> for 4 weeks, minimum. P> 5) if you have no idea about the reasons, ignore or ask P> I'm not going to test each single page to see if one did his work P> correctly or not. A security reason (very critical) made me set P> register globals to off. I tested 7-80% of the site and it works. You've done everything right. The only effort, that should be done by somebody else who is afraid of dark PR against PEAR is to place a notice on the main page with explanations about major security patch was made to register_globals and provide a link to http://pear.php.net/status/ to track site outages and report possible problems. I didn't mention people, who use pearweb code for they own projects. I guess somebody from QA team should put a public notice if they care for them. P> It was more time efficient to do it this way, and the only 2 complaints P> are fine with me. If you (all together) have nothing else to do that P> shooting at the sherif, please do, but I doubt it helps in any way to P> make this code base better or safer. True. The most we can do for now is to start learning project management and begin requirements collecting for requrements collecting system. After that the progress to resolve overall PEAR problems can be moved onto next stage. -- anatoly