Return-Path: <y@MIT.EDU>
Received: from pacific-carrier-annex.mit.edu by po11.mit.edu (8.9.2/4.7) id NAA08052; Fri, 7 Sep 2001 13:23:42 -0400 (EDT)
Received: from egon.jenwa.org (h002078cfb834.ne.mediaone.net [24.147.19.145])
	by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id NAA28115
	for <windowmgr@mit.edu>; Fri, 7 Sep 2001 13:23:41 -0400 (EDT)
Received: from egon.jenwa.org (y@localhost)
	by egon.jenwa.org (8.11.2/8.11.2) with ESMTP id f87HMGs01103;
	Fri, 7 Sep 2001 13:22:16 -0400
Message-Id: <200109071722.f87HMGs01103@egon.jenwa.org>
To: Jesse Pavel <jpavel@alum.mit.edu>
cc: windowmgr@mit.edu
Subject: Re: Windowmaker 0.65 
In-Reply-To: Message from Jesse Pavel <jpavel@alum.mit.edu> 
   of "Fri, 07 Sep 2001 12:17:10 EDT." <Pine.GSO.4.30L.0109071214470.8026-100000@m38-370-19.mit.edu> 
Date: Fri, 07 Sep 2001 13:22:15 -0400
From: chad <y@MIT.EDU>


Hello, Jesse.

Sorry about the lack of response.  We're in a bit of a tight spot,
unfortunately.  There are two basic issues involved.

One: `old-style' window managers were pretty solitary beasts.  They
had very specific functionality that changed very infrequently and
used parts of the X apis with similar characteristics.  By contrast,
modern window managers are a serious PITA to maintain.  Generally
they're written for a very specific set of platforms (i.e. `Linux with
glibc6 and glib greater than 1.2.3'), and usually involve a passel of
shared libraries.  As a single `product', the window manager
installation becomes very fragile; any changes must be built and
tested for a large variety of platforms.  Often local changes are
required to make a window manager installation fit well into the
athena environment (many wm's assume that they'll be installed
directly in the default X bin directory of every workstation), which
makes upgrades somewhat painful.  Once the added effort of
frequently-updated wm's in included, it becomes much more tempting to
simply stay at a functioning version.

Two: while most of the above factors are true of many modern programs,
the wm really does occupy a special place for almost every user.  In
particular, while a user might be inconvenienced if, say, exmh were to
suddenly break, they could continue about their business relatively
simply.  On the other hand, a very typical failure mode for window
managers is to either abort the user's login or leave the login in a
state that's unusable to most users.  We've found that a large
percentage (probably a large majority) of the people who use a window
manager other than the default did not make the change themselves, but
instead had it done for them, and they usually do not understand the
problem beyond ``I can't log in.''.  

These two factors make the windowmanagers locker a very tricky beast.

In this particular case, the person who normally maintains WindowMaker
has moved away, and, while he's still `in touch', he can't really
adequately support the athena locker installation anymore.  Because of
the frailty and the annoying failure mode, we are usually much more
picky about giving out access to windowmanagers than we are about
other lockers -- there is a much greater potential for someone to `try
something out' and accidentally cause a large number of people to be
unable to log in.

What should we do about this?  Well, honestly, I was hoping that one
of the existing locker maintainers would volunteer to handle
WindowMaker.  Since that doesn't seem to be the case, I'm going to
attempt to get a new locker created for `beta' windowmanagers, and
I'll give you access to that.  Unless there's a problem, most likely
we (that is, the existing wm locker maintainers and you) will
eventually decide that you should move the newer WindowMaker
installation over into the `non-beta' locker, and go from there.

If anyone has an alternative suggestion, I'm happy to hear it.

chad

