[PEPr] Comment on QA::Core_Team_Vote
| From: | PEPr | Date: | Sat, 05 Jun 2004 16:28:43 +0000 |
| Subject: | [PEPr] Comment on QA::Core_Team_Vote | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-29987@lists.php.net to get a copy of this message | ||
Stephan Schmidt (http://pear.php.net/user/schst) has commented on the proposal for
QA::Core_Team_Vote.
Comment:
OK, lets do some stat('schst');
I'm living in Karlsruhe/Germany, so I'm located in the same timezone as Lukas and German
is my mother tongue, too. I've been studying English, so I'm quite fluent in written and
spoken English.
I'm developing PHP since 1999, and I'm spending approx. 10 hours a day coding PHP.
I joined PEAR in July 2003 and currently maintain 11 packages as lead developer and contribute to
one package as developer. Besides PEAR I'm lead developer of http://www.php-tools.net, where I release stuff that does not
fit into PEAR, like my templating engine, a user-management package, my own version of
XML_Transformer (older than XML_Transformer and thus really buggy...) and some other packages.
I'm a regular contributor to the German PHP Magazin, but I also did some articles for php|a. I
attended several PHP conferences (as a speaker, including PHPCon (New York, SF), PHP Conference,
Linuxtag and I will be doing a PEAR talk at the O'Reilly Open Source Con in July.
In my everyday work I do a lot of stuff for Europe's largest webhoster (www.1und1.de,
www.1and1.com), so I'm used to working with new technologies and large-scale web-sites.
Currently I'm also working on an extension that I'd like to see included in pecl.
I'm especially interested in XML (I maintain 8 XML_* packages) and the PEAR manual, I set up a
testing enviroment at http://pear.php-tools.net/peardoc/ I read my mails
within one hour during worktime and I'll answer PEAR related stuff within 24 hours.
I'm subscribed to pear-dev, pear-doc, pear-qa as well as PHP internals. I try to take part in
as many discussions as possible. My previous QA-actions have been some patches and advices to
developers (mostly XML related) and I adopted two orphaned packages (Tomas' XML_Parser and
XML_DTD).
I think the QA team should help developers create unit tests as well as set up a automatic testing
environment, which is able to run unit-tests for new releases as well as current CVS versions. I
developed a small script for http://snaps.php-tools.net/
which creates PEAR packages for some of my non-PEAR projects from CVS. This allows users to test
versions before they are released and as every snapshot has a unique version number, bug reports can
be accurate. I guess, this could be useful for PEAR as well.
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