[6583] in Release_7.7_team
Re: dialup churn in process
daemon@ATHENA.MIT.EDU (Mark W. Manley)
Wed Dec 30 12:32:38 2009
Date: Wed, 30 Dec 2009 12:32:29 -0500 (EST)
From: "Mark W. Manley" <mmanley@MIT.EDU>
To: Jonathan Reed <jdreed@mit.edu>
cc: Oliver Thomas <othomas@mit.edu>, ops@mit.edu, release-team@mit.edu
In-Reply-To: <F449FA0E-2070-4158-AA46-94A1BFED4863@mit.edu>
Message-ID: <alpine.DEB.2.00.0912301229350.6950@green-arrow.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Flag: NO
X-Spam-Score: 0.00
Answers below.
On Wed, 30 Dec 2009, Jonathan Reed wrote:
> I'm fine with a linux.dialup.mit.edu pool, provided the MOTD sufficiently
> explains the difference (and has sufficiently different formatting compared
> to the current one such that users won't just skim over it).
Totes.
>
> Can you give an approximate date for this (for planning purposes), since I'll
> need to make sure our docs are updated accordingly?
End of January.
>
> I assume we'll have a sun.dialup.mit.edu pool for explicit access to those?
That is a truth fact.
> I wonder if we need to think harder about outreach to the community or
> something. I don't know of a good way to do that. Maybe update the current
> dialup MOTDs now to at least make people aware of the upcoming transition?
> I'm primarily concerned that we'll see a significant number of people who
> gave up on Debathena for whatever reason and fellback to the dialups instead,
> and now will be forced to actually report their problem.
>
I'll leave that to your collective user support wisdom. My past
experiences with these kinds of migrations is that you are correct and
notthing, even a laser light show and full-on parade announcing the
change, will get some users' attention.
-MM
