Xref: utzoo news.groups:9773 news.admin:5799
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!phavl!rob
From: rob@phavl.UUCP (Robert Ransbottom)
Newsgroups: news.groups,news.admin
Subject: CALL FOR DISCUSSION:  Creation of news.groups.d
Summary: A vote will be called!
Message-ID: <240@phavl.UUCP>
Date: 24 May 89 04:21:06 GMT
References: <2017@internal.Apple.COM> <61490@yale-celray.yale.UUCP>
Organization: General Supply & Metals, Inc., New Bedford, MA
Lines: 36

In article <61490@yale-celray.yale.UUCP>, Ram-Ashwin@cs.yale.edu (Ashwin Ram) writes:
>    [ cites a small piece of the flamefest ]
> 
> NONE OF THESE MESSAGES BELONG IN NEWS.GROUPS!
> 
> News.groups is for discussing the proposed newsgroup, not about all these issues
> I find news.groups harder and harder to keep up with.  This is one group that
> most USENET readers should be encouraged to read, but with this kind of
> discussion going on I'm afraid all we'll do is encourage people to unsubscribe.
> 
> We need more organization in news.groups.  One possibility is to create a
> news.groups.d for followup discussions.  But though this will be an improvement,
> I think news.groups.d will suffer from the same problem.

> [ ... self-proclaimed off the wall idea deleted ... ]

IMHO your idea is to complex to pass.  


This is a simple call for discussion.  This idea has come up 3 times in
the last 6 months.  As one correspondent stated:  it requires little
discussion.  

The only discussion I see needed is if news.groups needs to become moderated.
I move that we leave news.groups unmoderated in the interest of getting 
news.groups.d made.

The ramifications as I see them:
 - A post to news.groups still serves as "official notice".
 - News.groups becomes a "readable" group (newsadmins take note).
 - People can skip news.group.d unless there is an issue they'd wish to see.

The call for votes will be issued on June 6, 1989.

-- 
 ...!uunet!phavl!rob              Robert Ransbottom