Xref: utzoo news.groups:8014 comp.windows.x:8680
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!srcsip!csd4.milw.wisc.edu!bionet!agate!eris.berkeley.edu!mellon
From: mellon@eris.berkeley.edu (Ted Lemon)
Newsgroups: news.groups,comp.windows.x
Subject: Re: CALL FOR DISCUSSION -- splitting comp.windows.x
Message-ID: <21650@agate.BERKELEY.EDU>
Date: 15 Mar 89 09:49:33 GMT
References: <14051@bellcore.bellcore.com> <829@hydra.cs.Helsinki.FI> <14717@bellcore.bellcore.com> <564@peritek.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 29

dave@peritek.uucp suggests splitting comp.windows.x up into cwx.server,
cwx.client and cwx.misc (where cwx stands for comp.windows.x).   Another
person suggested having a group called cwx.bugs.

I am generally in favour of these ideas - bandwidth on comp.windows.x is
too high, and too scattered, to make reading it anything but a chore.
I'd like to add a few suggestions to the list, though, since the groups
suggested above don't seem satisfactory to me.   Here's how I'd like to
see it divided:

comp.windows.x			General X discussion.
comp.windows.x.announce		Announcements from athena or other
				X contributors.   Should be moderated.
comp.windows.x.toolkits		Discussion about various toolkits.
				The idea of going down yet another
				level in this tree is enticing.
comp.windows.x.clients		Discussion about client implementation.
comp.windows.x.server		Discussion about server implementation.
comp.windows.x.distrib		Discussion about the MIT X Distribution,
				such as ``why doesn't this build?''

This way, people who are only interested in hearing about bug fixes,
new releases of software, and similar items can read cwx.announce
without having to read a bunch of stuff about HP toolkits, or whatever
the current discussion happens to be about.

As always, please flame by EMail.

				_MelloN_