2005-05-20-01
Minutes |
B. Foster gave a report of his latest meeting with M. Paivinen:
- 31 machine inventory: M. Paivinen still working on this, B. Foster
asked for list of physical hardware so environmental planning can start,
list of operational tasks of each machine can follow later
- knowledge preservation (source code review): B. Foster got 6-15-05
review date set; 7-1-05 networking; 7-15-05 databases; there are three
key areas that will break up for source code review project; there are
about 200 add-on processes, on 7-15-05 HP will select a subset for review
- PSA: none yet, B. Foster will push to place this higher on M. Paivinen's
list, P. Edwards pointed out it has been more than 1 year now since
HP said they would give money to OpenMPE
- ss_config: no way it will be released outside HP, M. Paivinen making
sure process exists for system down and will evaluate quality and time
of process for improvements; discussion that this needs to include system
cpu upgrades, etc. and that HP needs to make a public statement of
turnaround times, escalation procedures and contacts
- support tools: vCSY looking at what support tools and processes it
owns and can turn over, what belongs to other divisions they can't turn
over
- "thiscpu2": vendors to use for license management, will
work with vendor community
- 9x7 running 7.0/7.5: M. Paivinen asks are they really for migration
or test work, units can be purchased on ebay for ~$400; if 9x9's are
not cheaply available, let B. Foster know so he can get with M. Paivinen;
a question was raised: when HP turns over MPE will the receiver be required
to maintain non-9x7 issue and speed crippling issue? Note: M. Perdue
will post to -L and OpenMPE list a message with follow-up of the 9x7/7.0,7.5
issue, mention the HP customer survey (maybe do a write-in vote) also
talk about HP support: HP may investigate so have your paperwork ready
if a review takes place
- "big disk" patch has been back-ported to 6.5, HP will make
announcement question: can announcement be jointly made? (would help
with OpenMPE public perception in the community)
|