[25] in Kakapo Windows Team
Meeting tomorrow, I presume? + Agenda suggestions
daemon@ATHENA.MIT.EDU (Kerem B Limon)
Wed Jul 9 13:23:57 2003
Message-Id: <5.2.0.9.2.20030709131338.07c1d250@hesiod>
Date: Wed, 09 Jul 2003 13:23:52 -0400
To: Kakapos at MIT <kakapo@mit.edu>
From: Kerem B Limon <kerem.limon@MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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
