[comp.emacs] How about comp.org.fsf or comp.os.gnu ?

page@ulowell.UUCP (03/28/87)

With the recent announcement of the GNU C compiler, comp.emacs has
become comp.os.gnu, or comp.org.fsf, depending on how you look at
it.  The GNU/Free Software Foundation stuff has been floating
around comp.emacs for a long time now, presumably because it has
no other home.  Recently comp.os.minix was created, and for a while
much of the traffic *there* was about GNU/FSF/Stallman.

While it may be premature to create a newsgroup devoted to an
operating system that does not yet exist (in public form, anyway),
there is a need to get the GNU/FSF stuff into its own newsgroup
(and out of comp.emacs).

So - I'd like to see something like comp.org.fsf or comp.os.gnu.
I don't really care what it's called - you know my motivations.

Followups should go to news.groups.

..Bob
-- 
Bob Page, U of Lowell CS Dept.   page@ulowell.{uucp,edu,csnet}    617/452-5000

tower@mit-eddie.UUCP (04/04/87)

There are several sections to this message headed by lines starting
with "* " (try outline-mode in GNU Emacs).  The one about comp.os.gnu
is last.  The other sections are in response to issues raised in
previous articles on this topic in newsgroup news.groups


* gnu@prep.ai.mit.edu

This address will get you answers to Project GNU related questions.
Including a description of GNU's electronic mailing lists.

Via UUCP:  ..!ucbvax!prep.ai.mit.edu!gnu or ..!mit-eddie!mit-prep!gnu


* electronic mailing list about GNU

There is an electronic mailing list used for progress reports on the
GNU project in general, and for requests for people to help.  To join
it, send your address to: info-gnu-request@prep.ai.mit.edu

If several users at your site or local network would like to read this
list, the GNU project would prefer if you would set up one address
that redistributes locally.  This reduces overhead on our machine,
your gateway machine, and the network(s) used to transport the mail
from us to you.


* use comp.sources.d to discuss freed or public domain software.

The group comp.software.free isn't needed.  If USENET really wants to,
perhaps comp.sources.d.freed.  Note the use of "freed" instead of
"free", freed software need not be no-cost free software.


* if you must, use comp.os.gnu

If USENET decides it must have this group now, name it comp.os.gnu .
comp.org.fsf is a bad name, the focus should be on the GNU operating
system, not the organization.


* Don't create comp.os.gnu now.

** It's still premature.

The only GNU software in full release is: gdb, bison and GNU Emacs.
(FSF is also distributing MIT C Scheme and hack.)  There isn't enough
to talk about.  The GNU mailing lists on prep have been handling the
distribution of the small amount of needed information well.  Wait for
GNU to be finished, then create the newsgroup.

** comp.os.gnu won't stop flaming in comp.emacs

Most of the objectionable GNU related articles in comp.emacs have been
"flames" (in the USENET use of the word) about things related to GNU
Emacs (e.g. sex.1).  This kind of comp.emacs posting will not stop
just because comp.os.gnu is created.  It will only add flaming in
comp.os.gnu, and USENET does not need more flaming to add to its
traffic load.

gdb and gcc have been announced on comp.emacs because many of it's
readers are interested.  Further discussion of them on comp.emacs
isn't appropriate.  These occasional technical and substantial
articles on gdb or gcc aren't worth another group, and aren't a major
bother to comp.emacs readers.



Thanx and enjoy -len
-- 
Len Tower, Project GNU of the Free Software Foundation
	1000 Mass. Ave., Cambridge, MA  02138, USA   +1 (617) 876-3296
HOME: 36 Porter Street, Somerville, MA  02143, USA   +1 (617) 623-7739
UUCP: {}!mit-eddie!mit-prep!tower	INTERNET:   tower@prep.ai.mit.edu