[PEPr] Comment on QA::Core_Team_Vote
| From: | PEPr | Date: | Sat, 05 Jun 2004 15:19:56 +0000 |
| Subject: | [PEPr] Comment on QA::Core_Team_Vote | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-29985@lists.php.net to get a copy of this message | ||
Lukas Smith (http://pear.php.net/user/lsmith) has commented on the proposal for QA::Core_Team_Vote.
Comment:
Actually I think its a good idea that everybody again give a bit information about themselves. Maybe
we should better do so on a wiki?
Anyways I am based in Berlin (that means I fall into CET timezone). I usually read all mails within
10 hours or so and reply within 24 hours. To dispell a common myth I am german and my mother tongue
is german as well.
I have been with PEAR since 2002 maintaining MDB[2] and LiveUser. I have been on pear-qa@ since its
creation and actively take part in all discussions. I read all PEAR mailinglists (except for
pear-webmasters@) actively. I try to visit atleast 2-3 PHP related conferences a year. I am also a
member of the PEAR group :-)
I use PEAR professionally inside my companies development framework. Beyond that I spend a fair
share of my free time on PEAR.
Generally I tend to be in the formal regulation camp, but I do think that alot of things are too
hard to put into formal rules and instead common sense and trust should reign in those situations. I
think PEAR QA should offer services to PEAR Dev but it needs to balance what it can actually sustain
and where educating the the actual developers makes more long term sense. I think we should try to
automate everything we manage to put into written regulations (like version naming etc) but we
shouldnt apply automatic ways to determine relative quality (like bug count, meantime to fix, CVS
commits, etc).
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=77
--
Sent by PEPr, the automatic proposal system at http://pear.php.net