[30] in Kakapo Windows Team
Re: Meeting tomorrow, I presume? + Agenda suggestions
daemon@ATHENA.MIT.EDU (Jean Foster)
Fri Jul 11 09:23:12 2003
Message-ID: <000401c347af$8fa8f750$71029812@thira>
From: "Jean Foster" <jfoster@MIT.EDU>
To: "Kakapos at MIT" <kakapo@mit.edu>, "Kerem B Limon" <kerem.limon@mit.edu>
Date: Wed, 9 Jul 2003 16:16:14 -0400
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
I won't be able to make the kakapo meeting tomorrow since I'll be at the
Altilab meeting until mid-afternoon.
-jean-
----- Original Message -----
From: "Kerem B Limon" <kerem.limon@MIT.EDU>
To: "Kakapos at MIT" <kakapo@mit.edu>
Sent: Wednesday, July 09, 2003 1:23 PM
Subject: Meeting tomorrow, I presume? + Agenda suggestions
> It's probably wise to drop a reminder that we are scheduled to meet
> tomorrow, in W20-400 according to Brian's latest e-mail:
>
> > July 10, W20-400 1:00-2:30
>
> I would like to propose two agenda topics.
>
> 1) On handling container requests and tracking them: We had a short
> discussion on this last time we met, and there was some discussion as to
> whether Ops would/could use CaseTracker, which seems to be the tool of
> choice from the win.mit.edu and DART side. I would like to vote for
> CaseTracker, however, I'd also like to understand and be mindful of
> Jonathon's team and their procedures, since this task seems to be shifting
> to their area.
>
> If we do use CaseTracker, I would propose the following:
>
> o The current form continues to e-mail the list container-request.
> o The list includes those people whom we think should see requests that go
by.
> o The list also includes the feed to CaseTracker. Each submitted request
is
> assigned an auto-generated case, an ack is sent to the submitter.
> o For requests coming from "known" bodies, such as DITR, forwarded over
> from DART, etc., including existing container admins (who will maintain
> list?) are processed, unless there is something apparently wrong (e.g.
> weird naming schemes, request for 100 new containers from the same person,
> etc.)
> o For requests coming from "newbies", there is a n business day grace
> period during which all who have seen the request via the list
> container-request can respond to object/correct. If no objections arrive
by
> then, the request is processed.
>
> 2) Regardless of where the container requests are tracked, where other
> requests are logged. We will have to track DART consultation requests and
> DNS subdomain delegation requests for independent AD domains. I would like
> to propose these go to CaseTracker, in a fashion similar to the above,
> especially for the latter. The question is, where (in what category) these
> should go in CaseTracker.
>
> I propose creating a top-level "Windows Server" category in CaseTracker
> where 'DART'' and 'independent domains' are subcategories/queues for
> tracking the above requests only.
>
> Flames, comments, suggestions welcome.
>
> Kerem
>
>
>
