[1325] in athena10
Re: Metapackage rename
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Fri Mar 6 16:50:20 2009
Cc: debathena@mit.edu
Message-Id: <11CF34BC-5139-4042-B645-6249C4DF0F34@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: Evan Broder <broder@mit.edu>
In-Reply-To: <49B18DAA.8070402@mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 6 Mar 2009 16:46:47 -0500
Off the top of my head, I'll suggest the following:
debathena-standard -> debathena-basic
"Standard" implies a "reference point against which other things can
be judged" or "something established by general consent as a model".
While it's true that debathena-standard fits this definition for
Debathena users, it doesn't necessarily fit for other portions of the
community. I like "basic" here, because it provides a basic level of
functionality, or to continue being pedantic, "constituting or serving
as the basis or starting point". This package will be the starting
point of Debathena for 95% of the user community (the other 5% would
likely start with -locker, -clients, or similar).
debathena-login -> debathena-login
I kind of like "login" here. What it adds to -standard is in fact the
ability for people without local accounts to log in. The only things
it has that aren't immediately concerned with that are fingerd-config
and athinfod. I can't, at the moment think of a good one-word way to
refer to those.
debathena-workstation -> debathena-graphical-login
I think this best describes what it does - it makes graphical logins
for Athena users suck less.
debathena-managed -> debathena-workstation
I like this idea best, assuming we can manage the transition for
current -workstation users. "Private workstation" is really stuck in
the minds of lots of people (along with things like "I/S", "The
Graphic Arts Building", and "R/O"), and it would be nice to not have
to re-educate everyone. I think we still haven't 100% ironed out
what does and does not go in here, but that's a separate thread.
If we go with debathena-graphical-login, we could in theory rename
debathena-login to debathena-tty-login (yes, I know it's not
technically true, but...)
-Jon
On Mar 6, 2009, at 3:55 PM, Evan Broder wrote:
> I'd like to move forward with the idea of trying to rename our
> metapackages, or at least some of them, to something that's a little
> more inherently understandable.
>
> The one that I think is obvious is renaming debathena-workstation to
> debathena-graphical, which would eventually leave the name
> "debathena-workstation" open to be what we're currently calling
> "debathena-managed"
>
> I think that both -login and -standard could also benefit from better
> names, but damned if I know what they are.
>
> If the goal is to reuse the name debathena-workstation, we'll have to
> execute the transition slowly so that people don't get
> "debathena-workstation" changed out from under them.
>
> Do people have ideas for more descriptive names for -standard or
> -workstation?
>
> Do people have objections to workstation -> graphical?
>
> - Evan
