On Mon, 4 Dec 2000 15:27:28 -0500, "Bryan C. Warnock" <[EMAIL PROTECTED]> wrote:
> Apprentice Tasks
>
> Any task vaguely Perl related can be apprenticed out. Here is a sample
> list:
>
> - Documentation, both internal and external, including, for instance,
> programming guides, DDDs, user documentation, API documentation, coding
> standards, etc.
>
> - Writing weekly summaries of the groups and other stuff the list chair
> is currently doing (or should be doing).
>
> - Q&A or "Help Desk" between working groups, or between a working group
> and a public forum.
>
> - Writing test code, both internal and external.
>
> - Fleshing out simple stub code.
>
> - Research and prototyping.
>
> - Mananging new apprenctices, or the program itself.
Testing, plain.
i.e. I'm now pretty involved in p5p, and cannot spare time for p6, though I'm
following most of it. What I could offer is testing the `current state' (what's
now bleadperl for p5p) on several non-linux machines (see sig), and maybe put
some useful comments next to test results.
Just download/rsync the latest state. Start the test. Report the test results.
> Dan then pings on one of the group apprentices to grab the code and run the
> tests.
Nothing to do with apprenticeships. If I'm no apprentice, I can do this. Nick
and Dan would be happy.
--
H.Merijn Brand Amsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.005.03, 5.6.0, 5.7.1 & 620 on HP-UX 10.20 & 11.00, AIX 4.2 & 4.3,
DEC OSF/1 4.0 and WinNT 4.0 SP-6a, often with Tk800.022 and/or DBD-Unify
ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
