Re: QA category
| From: | Lukas Kahwe Smith | Date: | Mon, 23 Oct 2006 21:06:33 +0000 |
| Subject: | Re: QA category | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-4003@lists.php.net to get a copy of this message | ||
Joshua Eichorn wrote:
Lukas Kahwe Smith wrote:Doesnt this piece of code for the first time validate the usefulness of docbook atleast to some extend? I did not look at the code, but I assume he is using some of the markup of docbook in the parsing. regards, LukasArnaud Limbourg wrote:Thats true, Peardoc_Coverage just seems pretty Pear specific for me. Plus I hope no one else follows our lead in doing docbook documentation, its hard enough to get good docs with the low bar of entry a wiki provides, once you raise the bar to docbook its hard to want to spend the time to write any at all.Joshua Eichorn wrote:Well considering that we are sort of a role model and all our infrastructure is open source based, I think that even if this is very specialized for PEAR infrastructure, I could still see other projects using our QA tools. regards, LukasArnaud Limbourg wrote:You have a point. It may look like pear is providing qa tools to the public whereas the aim is to have qa tools for pear itself.Christian Weiske wrote:A top level QA category that is specific to PEAR sounds kinda confusing, why not do something like PEAR_QA_Peardoc_Coverage, so its clear this is a PEAR specific QA tool not a general purpose one?Hello all, I asked on pear-dev which category my QA_Peardoc_Coverage tool should be put in, and common sense was that a new "QA" package category should be created and tools put in there. Perhaps PEAR alone is enough if not more QA tools come. Could you please decide and add the group so I can add the package?Creating a QA category might give incentive to get more tools in :) Arnaud.