Date:	Fri, 25 Feb 94 10:19:10 JST
From:	Stephen Turnbull <turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp>
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Too many groups? (was: start a news group!)

Many people seem to agree that news groups are a good idea; me too, if
only to get the start a news group traffic out of my inbox ;-)

My two cents on naming:

>   gnu.gcc.djgpp.announce
>   gnu.gcc.djgpp.bugs
>   gnu.gcc.djgpp.help
>   gnu.gcc.djgpp.help.new-user
>   gnu.gcc.djgpp.misc

(combining DJ's and Volker's ideas) is best because (a) MS-DOS is not
an FSF project, whereas DJGPP arguably is; (b) we've been trying for a
while (with fair success) to get people with C/C++/Objective-C
questions to post to C lists, this should encourage the process by the
proximity of the gnu.gcc groups; (c) this is semantically accurate.
    I disagree strongly with people worried about duplicate posts.  If
people post installation and/or newbie questions to "help", send them
flames and copies of "netiquette" and uuencoded TNT.
    Maybe better than "help.new-user" is "help.docs-and-install,"
which is the traffic we really want to avoid in "help.advanced" (who
are we kidding here :).  A similar approach to ".bugs" vs. ".help" is
appropriate.  Anyway, even if *all* bugs are posted to ".help", that's
not so bad.  We just don't see that many true bugs.  (Most traffic is
"start-a-newsgroup"-related ;-)
    I don't know about the exact right name, but a lot of the
"wizardly" traffic on the list concerns gnats in GO32.  I would
suggest a ".djgpp.extender" or ".djgpp.go32-gnats" (that ought to
placate RMS) subgroup.  I think this is appropriate because there are
issues that come up that don't seem to be bugs in GO32 but are
DJGPP-specific.  Maybe this should replace the ".bugs" group.  (Other
bugs really belong in ".gcc.bugs", right?)  Or maybe a cute name is
inappropriate and we should just stick to ".bugs".
    Sorry, what with inflation and all I guess that was 25 cents.
    --Steve

- Raw text -