Ok, this is the first entry for me, so I'll attempt to bring
everyone up to speed on whatever I can.

First off, I would like to appologize for not posting a UI
Summary yet. The reason I haven't done this is because we
haven't finished anything yet, and the entire thing would be
a bunch of links to Eazel, Inc. resources and articles. I
would like to get at least two news items before posting a
new summary, so that's that.

Somewhat related to the first item, I did send out Proposal
#2 (Improving The GNOME-Core Interface) to the other members
of the Hit Squad. All that's left is for them to vote on it,
me to HTML-ize it, mix it with the redesign screenshots I've
already done, and announce it to the world (at which time, I
will post the URL).

And as a little teaser to get you all flipping out (:-)),
I'm planning on learning GNOME/GTK+ programming so I can
code a GNOME System Administrator application. The basic
idea is that I steal the Control Center 2.0 code (the next
gen codebase), change a few labels, and write some sample
capplets. And what do these capplets do? Simple. Configure
system services! That's right, a gnomecc-style interface for
setting up Runlevels, httpd, nfs, exim, samba, etc. And
since it uses capplets, service authors can (read: should)
write their own capplets which handle the intricasies of
their service. A Roxen capplet could ship with Roxen, an
Apache capplet with Apache, etc. This way nobody has to keep
track of every config file format under creation, just the
few that the sample capplets I'll provide handle (I plan on
doing capplets for the current OSS Linux versions of all the
major services: NFS, Apache, Samba, Exim, and a Runlevel
editor). So after this is finished, pester your favorite
vendor to write a capplet for their setup.

If you are already working on such an app, please contact me
immediately so I don't waste my time, thanks ;-)