[31] in Kakapo Windows Team
Kakapo Thursday July 17th, W20-PDR3 1:00
daemon@ATHENA.MIT.EDU (Brian Murphy)
Wed Jul 16 18:22:23 2003
Message-Id: <5.0.2.1.2.20030716173337.01a627b0@po12.mit.edu>
Date: Wed, 16 Jul 2003 17:35:11 -0400
To: kakapo@mit.edu
From: Brian Murphy <bmurphy@MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Greetings,
We will be meeting this week on Thursday at 1:00 in W20-400
The Agenda is as follows:
Developing a shared communication process that will
1) identify deadlines, deliverables, and those responsible for them for
major activities relevant to delivering Windows services.
2) describe the communications process by which this information will be
distributed, updated and maintained.
3) identify the alert process when a deadline or other critical piece of
information needs to be communicated across the community (analogous to the
'snow chain')
2. Adding Laptops into the win.mit.edu Specifically The Laptop Loaner Pool
Tom/Chad - If this is already possible can we get a demo? Or, when do you
estimate it being ready?
3. Container Requests - We need to reach agreement on how these requests
will be
handled and commit to having the Kakapo team be the offical body which
sanctions these requests. (Secondarily, Casetracker as a tool for tracking
requests) Alternately - Container requests - proposed process
add Kakapo mail list to the container request form
All such requests will go before the Kakapo group for advice and
consent UNLESS there is a critical time dependency. In that case, the
request will be brought to TR and PDL for a decision. Regardless all
container requests will be brought to Kakapo at the next scheduled meeting,
including those handled by the alternate path through TR and PDL, for
information sharing.
A tracking mechanism must be adopted that allows for any member of
Kakapo to look up and see the status of any given container request. By
default, the proposal here is to use Casetracker. An alternate tools is
fine IF it permits inquiries by members of the team and allows the status
of the work to be seen by the inquirer, and comments and updates to it by
any in the group.
4. Documentation - We need documentation for the following shared with this
group:
a) container administrators
b) instructions to join a machine to win.mit.edu
c) DART Process steps - concise graphical or enumerated summary
d) MSI development guidelines for win.mit.edu
We need to develop a common document with the roles,
responsibilities for Container Admins.
5. Standing items:
New Container Requests
Win.mit.edu domain transition updates (status; critical issues;
dependencies; expected accomplishments for the coming week).
If there are any other items please let me know and I'll add them to the
agenda.
-Brian
