I thought I sent this to you earlier this week... I'm not sure
what happened..


Steve,

Here is my input.

Rich.

Performance
O: Ship 4.0G, 5.0A, and 5.1 versions of APX
   without disrupting T64 schedule
M: Quantitative, measured at appropriate time
> I have Contributed little to these releases in 2000, except
for the LDAP support which was done for the most part in 1999
for Zulu.

O; Contribute towwards deliverables in the "Yankee"
release.
M: Quantitative, progress checked at weekly meeting
> I have submitted both my "Yankee" projects - to the
> wildcat release. These are the lpc check facility for
> lpd and the APX integration sysman.

O: Product quality
M: Quantitative: meet T64 UNIX release Q/A metrics.
> I've submitted and answered a few QARs. The lpc check
> facility was also conceived as a way to improve the
> perceived quality fo the lpd software, as it allows
> customers to more easily identify and fix their own
> configuration problems.

O: Provide timely review of plans, specs, and code.
M: Quantitative, meet T64 UNIX release Q/A metrics.
> I have reviewed many specs and code changes. Mark and
> I make it a rule to always review each others submits
> and we have done that.

M: Perform level-3 (i.e. IPMT bug fixes) support as required.
O: Quantitative: discuss with PL
> I have fixes a few bugs, as needed.

M: Become more familiar with APX internals; become able to
fix bugs within environment.
O: Qualtitative, ask Rich.
> I have learned about the APX build process as well as the
> installation tools. I am reasonably comfortable using the
> APX build environment and I can find my way around the
> tree.

M: Continue technical currancy.
O: Take a class in some new technology.
> I took the class on planning and managing projects.

M: Industry awareness
O: Monitory PWG activities and keep the group informed.
> I did not attend any PWG meetings in 2000, but I have
> been following the email and internet postings of the
> group.

Other: I have always been interested in software develop
processes and the tools use to manage and support software
development. I have participated (by email only so far)
with discussion of software development issues in the
UBPG.


-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to