[35] in Kakapo Windows Team
Re: Kakapo Thursday July 17th, W20-PDR3 1:00
daemon@ATHENA.MIT.EDU (Kerem B Limon)
Thu Jul 17 12:39:38 2003
Message-Id: <5.2.0.9.2.20030717122949.090b0d60@hesiod>
Date: Thu, 17 Jul 2003 12:39:34 -0400
To: Brian Murphy <bmurphy@mit.edu>
From: Kerem B Limon <kerem.limon@MIT.EDU>
Cc: kakapo@mit.edu
In-Reply-To: <5.0.2.1.2.20030716173337.01a627b0@po12.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Given the timing, these are not per the agenda today, but for continued
discussion. I will raise the issues within the meeting as well...
I believe we are meeting in PDR3, not 400, according to your Subject and
earlier e-mail about scheduling rooms.
At 03/07/16 17:35 Wednesday, Brian Murphy wrote:
>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')
Thank you for including these items and hearing my concerns. However, this
alone is a large topic and it is a very full agenda. I suggest we spend the
first few minutes pacing ourselves for the next hour/hour and a half.
>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?
Yes, I would like to participate in this testing, and have a machine ready.
Paul and Tom made some brief suggestions last week, but I would much rather
participate in and/or lead a coordinated effort into this.
>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.
I am anxious to get this resolved and this sounds like the beginnings of a
reasonable proposal. I, however, am also interested in making sure Jonathon
Weiss' and his team has a chance to argue and present their viewpoint. The
relative urgency to resolve this issue and Jonathon's being away seem to
conspire against it, so may I suggest that we provide a good summary of the
discussion points to which he can respond, or perhaps even assign the
action item to one of us to speak with him and ensure his view are
accurately represented.
>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
I met with Wael today to pool what we have. I will combine what we have (2
- 3 all divergent and not up-to-date) documents for Windows 2000 RIS/join,
and Windows XP join if it works by Friday. IS internal migrators demand
that ASAP. The document Tom referenced in his e-mail is among those.
> c) DART Process steps - concise graphical or enumerated summary
I have added kakapo to the ACL for the Windows Server portal pages we have
been previewing; please try
https://web.mit.edu/windows-delivery/www/dontindex/server/
Comments are *most* welcome and should go to windows-delivery-www, and
CC:'d to Kakapo as you desire, of course.
Under https://web.mit.edu/windows-delivery/www/dontindex/server/dart/,
there is the kind of information you seek, that is also being updated as we
continue. I also have the CaseTracker queues for DART requests created and
as soon as I am able to verify the request forms and the queues work
tonight, we will begin end-to-end testing with OSP, Facilities, etc.
> d) MSI development guidelines for win.mit.edu
>
>We need to develop a common document with the roles,
>responsibilities for Container Admins.
I would be willing to commit resources from the Delivery Team to assist
with this.
>5. Standing items:
>
>New Container Requests
> Win.mit.edu domain transition updates (status; critical issues;
> dependencies; expected accomplishments for the coming week).
Ditto the one from Biology Tom quoted.
>If there are any other items please let me know and I'll add them to the
>agenda.
>
>-Brian
Kerem
