[6138] in Release_7.7_team
I think Release Team should have a debathena representative.
daemon@ATHENA.MIT.EDU (William Cattey)
Mon Dec 22 15:02:27 2008
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2619E4EF-7323-416A-8CDE-284D02047CC5@mit.edu>
Content-Transfer-Encoding: 7bit
From: William Cattey <wdc@MIT.EDU>
Date: Mon, 22 Dec 2008 15:01:05 -0500
To: release-team@mit.edu
X-Spam-Flag: NO
X-Spam-Score: 0.00
Now that IS&T and the SIPB are collaborating in a heavy duty way on
Athena 10, it seems appropriate that there should be debathena
representation on the Release Team.
Back when there were watchmakers, all watchmakers were invited to
Release Team, but they only showed up when there was a topic on the
agenda directly related to something they were doing.
It seems to me that a blanket invitation to the SIPB or to everyone
who is working on debathena is probably not a good way to go.
Instead I propose to email the debathena list, and ask for one or two
designated debathena representatives to join Release Team -- to get
onto the email list and to be invited to Release Team meetings. The
reason why I propose more than one is that I expect class and other
obligations might get in the way of a single person being the
representative.
What do people think?
Should we invite a "debathena representative" to Release Team?
Is one enough, or should we invite two?
-Bill
----
Important: IS&T IT staff will *NEVER* ask you for your password, nor
will MIT send you email requesting your password information. Please
continue to ignore any email messages that claim to require you to
provide such information.
----
William Cattey
Linux Platform Coordinator
MIT Information Services & Technology
N42-040M, 617-253-0140, wdc@mit.edu
http://web.mit.edu/wdc/www/
