[2264] in Enterprise Print Delivery Team
Re: followup to yesterday's meeting
daemon@ATHENA.MIT.EDU (Rocklyn E. Clarke)
Thu Feb 7 21:14:00 2002
Mime-Version: 1.0
Message-Id: <p05010400b888e28a4e38@[192.168.1.101]>
In-Reply-To: <200202062032.PAA16000@brad-majors.mit.edu>
Date: Thu, 7 Feb 2002 21:13:57 -0500
To: Garry Zacheiss <zacheiss@MIT.EDU>
From: "Rocklyn E. Clarke" <rclarke@MIT.EDU>
Cc: Enterprise Printing Delivery Team <PRINTDEL@MIT.EDU>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Hi Garry,
Thanks! With regard to "maintain", we want the latter: we want
Athena Server Ops to be responsible for deploying new binaries on
these machines when necessary. Naturally I understand that this
needs to be discussed with the rest of the team. If there are any
budgetary obstacles to Athena Server Ops taking this on, I am fully
prepared to lobby Roger and Jim to make the appropriate resources
available (presumably some additional fraction of an EFT). I will
await the outcome of your deliberations.
Rocklyn
-------
At 3:32 PM -0500 2/6/02, Garry Zacheiss wrote:
> >> I will be out of the office for the rest of this week, so I would
>>> like to plan for this to be done next week (i.e. the week of
>>> 2/11/2001) if possible.
>
> That should be fine.
>
>>> The Enterprise Printing team has decided that the installation of
>>> zephyr and update server should be done after the project wraps
>>> (hopefully this month). I will therefore be in touch with you about
>>> these two tasks sometime in March (assuming we wrap on time).
>
> That should also be fine.
>
>>> The bigger picture here is that we want Athena Server Operations to
>>> be responsible for maintaining these pieces of code (i.e. LPrng,
>>> zephyr, update_server) on the test and production servers.
>
> Could you expand on "maintain" here? Do you want us to provide
>source trees, or also be responsible for deploying new binaries on these
>machines when bug fixes/new feature requests make this necessary? This
>is likely possible, but we'll need some more information, and I'll need
>to involve the rest of the team in some of the discussion.
>
>Garry
