Re: CS fixes

From: Date: Wed, 25 Feb 2004 13:42:50 +0000
Subject: Re: CS fixes
References: 1 2 3 4  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-661@lists.php.net to get a copy of this message
<quote who="Klaus Guenther"> >> I dont think it is feasible to have QA commit whitespace fixes if the >> maintainers dont want this to happen. The internals people are having >> frequent flame wars about this topic and I want to evade it by making >> this an optional service instead of a PITA. > I agree that this should be optional, but I also agree with Toby that the > list should be maintained by QA and the rules as to what is permissible, > etc. should also be handled by QA. What if the maintainer is working on the > code and someone submits CS changes? It's generally a lot nicer to provide a > patch to the maintainer. However, if the code hasn't been touched for a > number of weeks, then I can understand committing directly. I guess a simple announcement on pear-dev like "Dear package maintainers,... CS are a fixed guideline of PEAR... if your code is not fully CS compatible until xx.yy.2004, the QA team will commit fixes to it on xx.yy.2004..." would have done the thing (if we had previously announced to force people to take CS seriously). QA is a service for developers on the one site, but the greater part it's like ass-kicking... > By the way, why not include this information in the pear package database? > How about automatically asking the question the next time a release is > uploaded? Once that has been done, the list can be automatically generated. > If a maintainer later decides to opt out, he could do that on a special > "Package properties" panel that could be accessed directly from the package > page -- just like the form for adding and removing developers. Mmmhhh... I guess the effor is to high to implement this, as to do it by hand. Nevertheless, IMHO this "list" stuff is the complete wrong way. People do not have to explicitly agree with QA actions, but may complain against them. With or without a QA group: Let's set up clear definitions, what QA is for, what it does and which powers it owns! > I think it's getting time to have a QA section of the website, with > instructions for testing, the list proposed in this thread, etc. +1, but what exactly should be written there? Regards, Toby -- Tobias Schlitt a passion for php http://www.schlitt.info

« previous php.pear.qa (#661) next »