Re: CS fixes
| From: | Lukas Smith | Date: | Wed, 25 Feb 2004 13:26:15 +0000 |
| Subject: | Re: CS fixes | ||
| References: | 1 2 3 4 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-657@lists.php.net to get a copy of this message | ||
Klaus Guenther wrote:
Lukas Smith wrote:+1 Yes we should start a new subsection on pear.php.net where we provide information about how to help, what we do, how we do it, why we do it etc. I also think that sometime down the line we should be able to add information on each package homepage where we can comment on the stability or even just the fact that we actively monitor the package (sort of QA having adopted this package). Pierre: we really need to come up with a gameplan for pearweb's future .. but that is a topic for another list :-) regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07Tobias Schlitt wrote:sets upHi all!I will maintain a current list of maintainers that have agreed to this and will make it available online.That are the issues I wanted to avoid by getting up a QA group whichisan official annoncement of QA's tasks and powers. IMHO the list solutionthenot very comfortable for QA. It's a better way to tell people "That'syouway to go, if someone has objections scream now" instead of "Scream ifI 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. 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. 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.accept the way to go"...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.