| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Wed, 29 Oct 2003 16:08:15 -0500 (EST) From: Cana Lynn McCoy <cana@MIT.EDU> To: <kakapo@mit.edu> Message-ID: <Pine.LNX.4.30L.0310291558000.800-100000@boeing-vertol.mit.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have concerns about the container requests being sent to hesreq@mit.edu, and I'm sending this mail to kakapo to make sure I'm managing to communicate this to the appropriate people. Currently, container-request consists of: dongq dtanner jcalz pbh redelson tregan LIST:ops container-request-mtg@menelaus.mit.edu (a pointer to an archival discuss meeting I started to track the container requests) It is certainly fine if the container-requests go to only a subset of ops, but I am concerned about the non-ops people currently reading container-request. Have they all decided that they do longer need to see any container requests? Alternatively, is it thought that they will all be added to hesreq@mit.edu? If so, they will be flooded with a fair amount of mail completely unrelated to the WinAthena project - namely, the other request functions of the hesreq list. I can't imagine that they'd like this. Additionally, as the primary person who reads, responds to, and tracks hesreq@mit.edu, I'd greatly appreciate having the unrelated WinAthena container requests directed to a separate discuss archive (and thus, separate mailing list), where they can be tracked separately. Discuss is cumbersome as a request-tracking system already, and I'd like to at least keep these disjoint batches of requests tracked separately. --Cana McCoy Athena Server Operations
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |