SECOND CALL FOR DISCUSSION: Reorganization of comp.unix.*

[Chip Salzenberg]

[ Document created: $Date: 90/07/20 19:37:27 $ ]

This article is a SECOND CALL FOR DISCUSSION on a reorganization
of the comp.unix.* hierarchy.  This reorganization will add
various "obvious" missing groups and rename several groups which
have misleading names.

THIS ARTICLE IS **NOT** A CALL FOR VOTES.
PLEASE EXAMINE THE ENTIRE PROPOSAL BEFORE COMMENTING ON IT.

All discussion regarding this proposal will take place in
news.groups ONLY.  If you post articles elsewhere, I might
read them, but I might not.  Comments intended for me
personally should be sent by E-Mail to <chip at tct.uucp> or
<uunet!pdn!tct!chip> or <chip%tct at pdn.com>.

+----------+
| PROPOSAL |
+----------+

Create:
  comp.unix.admin           UNIX system administration.
  comp.unix.msdos           MS-DOS running under UNIX by whatever means.
  comp.unix.large           UNIX on mainframes and in large networks.
  comp.unix.misc            General discussions regarding UNIX.
  comp.unix.programmer      UNIX programming.
  comp.unix.shell           UNIX shell usage and programming.
  comp.unix.xenix.sco       XENIX versions from the Santa Cruz Operation. [*]

[*] NOTE: If comp.unix.xenix.sco passes, then comp.unix.xenix will be
          renamed to comp.unix.xenix.misc, since its charter will have
          changed to cover only non-SCO versions of XENIX.  I didn't
          want to make two changes based on one vote, but in this case
          I think it's necessary.  Experience teaches that parent
          groups frequently draw inappropriate crossposting from their
          children.  Peer groups are better insulated from each other.

Rename:
 comp.unix.microport -->
  comp.unix.sysv286         UNIX System V (not XENIX) on the '286.
 comp.unix.i386 -->
  comp.unix.sysv386         UNIX System V (not XENIX) on the '386.
 comp.unix.wizards -->
  comp.unix.internals       UNIX internals: kernel hacking, etc.

For completeness, here is a list of comp.unix groups for which NO change
is proposed:

  comp.unix		Discussion of UNIX* features and bugs. (Moderated)
  comp.unix.aix		IBM's version of UNIX.
  comp.unix.aux		The version of UNIX for Apple Macintosh II computers.
  comp.unix.cray	Cray computers and their operating systems.
  comp.unix.questions   Questions and answers about UNIX.
  comp.unix.ultrix	Discussion about DEC's Ultrix.

+---------------+
| VOTING METHOD |
+---------------+

THIS ARTICLE IS **NOT** A CALL FOR VOTES.
PLEASE EXAMINE THE ENTIRE PROPOSAL BEFORE COMMENTING ON IT.

I will collect votes on my machine, "tct", which is two
Trailblazer hops away from uunet.

A valid vote will include a "yes", "no" or "abstain" for EACH
proposed change.  Each proposed newsgroup creation or renaming
will stand on its own.  Why?  First, it fits better with the
spirit of the current guidelines.  Second, I don't want the
whole proposal going down the tubes because of one unpopular
change.

I will use a Perl script to tabulate well-formed votes.  I will
examine each vote rejected by the Perl script.  If it is
complete and its meaning is obvious, I will fix it.  Otherwise,
I will reply to the voter with a form message that explains how
to cast a valid vote.

+----------+
| SCHEDULE |
+----------+

  1. Discussion:
     The official discussion period began on July 1.  It will end
     on Thursday, July 26.  Patience, please; we'll get it done.

  2. Voting:
     I will issue a Call For Votes on Friday, July 27.  The vote
     will run for 21 days from the time the Call For Votes
     appears in news.announce.newgroups.

     I will post a second Call For Votes, and possibly a list of
     unreachable return addresses, during the voting period.  When
     the vote is over, I will post the final results.

 3.  Waiting Period:
     I will observe the normal waiting period of five days from the
     time that the final results appear in news.announce.newgroups.
     During this time, people may report lost votes and/or impugn
     the fairness of the vote taker.  :-)

 4.  Consummation:
     After the waiting period, I will issue the appropriate control
     messages to create all new groups and/or new names for renamed
     groups.  About one week later, I will re-issue the creation
     control messages, and also issue removal control messages for
     old names of renamed groups.

If all goes as planned, whatever parts of the reorganization that
pass will take effect by the end of August.
-- 
Chip, the new t.b answer man      <chip at tct.uucp>, <uunet!ateng!tct!chip>