[71] in Kakapo Windows Team

home help back first fref pref prev next nref lref last post

Windows Server Documentation Workflow

daemon@ATHENA.MIT.EDU (Robert Ferrara)
Wed Aug 20 09:01:48 2003

Message-Id: <5.1.0.14.2.20030818105039.00bcce58@po9.mit.edu>
Date: Wed, 20 Aug 2003 09:01:32 -0400
To: kakapo@mit.edu, kirilisa@mit.edu, itlt@mit.edu, timb@mit.edu
From: Robert Ferrara <rferrara@MIT.EDU>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_676943==.ALT"

--=====================_676943==.ALT
Content-Type: text/plain; charset="us-ascii"

Hello all, 

In response to requests for a more formal process for documentation updates to the site http://web.mit.edu/windows/server Kerem and I prepared the following proposal. It was reviewed and modified slightly at last Friday’s ITLT meeting on our Windows commitments. Currently, the documentation material is being collected at http://web.mit.edu/windows-delivery/web/ but should be moving to the final site soon. 

Windows Server Documentation Workflow

1. The initiator sends the draft of the proposed documentation update (or new content) kakapo@MIT.EDU with a copy to Elise Riordan at kirilisa@MIT.EDU. The message should include information on where it is linked in documentation hierarchy. 

2. If there are no comments from Kakapo members after five business days, Elise (or the responsible pubs person) may post it to the site. In cases where it is not obvious who should be reviewing the updated documentation, Brian Murphy will coordinate a response and may ask for an extension.  

Kerem has developed a proposed Windows Server site map, or documentation hierarchy. By the conclusion of the Windows 2000 Domains, Workgroups, and Servers Delivery Project  a few short weeks from now - upkeep of this document should transition to Tim Brennan, who may ask for help from the Kakapo group as it needs to evolve.  Also, as part of the transition to Tim, Kerem will assign the likely “owner” (e.g. Windows Development, SWRT, ASO, etc) for each documentation area. Once again, the Kakapos can provide maintenance oversight and help on appropriate ownership. 

Cheers, Bob Ferrara 

--=====================_676943==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
Hello all, <br><br>
In response to requests for a more formal process for documentation
updates to the site
<a href="http://web.mit.edu/windows/server" eudora="autourl"><font color="#0000FF"><u>http://web.mit.edu/windows/server</a></u></font>
Kerem and I prepared the following proposal. It was reviewed and modified slightly at last Friday’s ITLT meeting on our Windows commitments. Currently, the documentation material is being collected at <a href="http://web.mit.edu/windows-delivery/web/" eudora="autourl"><font color="#0000FF"><u>http://web.mit.edu/windows-delivery/web/</a></u></font> but should be moving to the final site soon. <br><br>
Windows Server Documentation Workflow<br><br>
1. The initiator sends the draft of the proposed documentation update (or new content) <font color="#0000FF"><u>kakapo@MIT.EDU</u></font> with a copy to Elise Riordan at <font color="#0000FF"><u>kirilisa@MIT.EDU</u></font>. The message should include information on where it is linked in documentation hierarchy. <br><br>
2. If there are no comments from Kakapo members after five business days, Elise (or the responsible pubs person) may post it to the site. In cases where it is not obvious who should be reviewing the updated documentation, Brian Murphy will coordinate a response and may ask for an extension.&nbsp; <br><br>
Kerem has developed a proposed Windows Server site map, or documentation hierarchy. By the conclusion of the Windows 2000 Domains, Workgroups, and Servers Delivery Project&nbsp; a few short weeks from now - upkeep of this document should transition to Tim Brennan, who may ask for help from the Kakapo group as it needs to evolve.&nbsp; Also, as part of the transition to Tim, Kerem will assign the likely “owner” (e.g. Windows Development, SWRT, ASO, etc) for each documentation area. Once again, the Kakapos can provide maintenance oversight and help on appropriate ownership. <br><br>
Cheers, Bob Ferrara <br>
</body>
</html>

--=====================_676943==.ALT--


home help back first fref pref prev next nref lref last post