Nan:2006-10-16-ms-windows-binaries-lcc

From Usenet Big-8 Management Board
Revision as of 13:52, 10 July 2010 by Moleski (talk | contribs) (Created page with '<pre> From: board@big-8.org (The Big-8 Management Board) Subject: 2nd RFD: remove comp.binaries.ms-windows moderated (LAST CALL FOR COMMENTS) Newsgroups: news.announce.newgroups,…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
From: board@big-8.org (The Big-8 Management Board)
Subject: 2nd RFD: remove comp.binaries.ms-windows moderated (LAST CALL FOR COMMENTS)
Newsgroups: news.announce.newgroups, news.groups, comp.binaries.ms-windows,
 comp.os.ms-windows.announce, comp.os.ms-windows.apps.misc,
 comp.os.ms-windows.misc
Followup-To: news.groups
Date: Mon, 16 Oct 2006 12:31:13 -0700

                      REQUEST FOR DISCUSSION (RFD)
                    remove comp.binaries.ms-windows

This is a formal Request For Discussion (RFD) to remove the moderated
newsgroup comp.binaries.ms-windows.


PROCEDURE:

The B8MB plans to begin voting on this proposal after five days.  Please
offer any final discussion or comments before the end of this waiting
period.  Voting may take up to one week (7 days); a result will be posted
following the end of the voting period.

All discussion of this proposal should be posted to news.groups.

The full group removal procedure is documented here:

  http://www.big-8.org/dokuwiki/doku.php?id=policies:rmgroup


SUMMARY OF DISCUSSION:

No comments were received.


RATIONALE: remove comp.binaries.ms-windows

There have been no approved messages since August 1996.

Distribution of binary programs via Usenet, and in particular the Big
8 comp.binaries.* groups is no longer particularly useful or viable.
The binaries groups were created before there was widespread access to
the Internet, so that propagation of binaries via Usenet was a viable
alternative to distribution via floppies or other removal storage
media sent by mail.

Binaries newsgroups typically have very short expiration periods, so
someone interested in acquiring programs would have to constantly
monitor a newsgroup, or hope that the programs were archived so that
they can be accessed via the internet (such as by FTP).  But if the
programs can be sent via internet, there is no need for the Usenet
alternative.

Google does not archive binaries in newsgroups.  So even though they
maintain archives of the comp.binaries.* groups, they do not archive
most of the content (the reason for existence of the group in the
first place).

Over the years, programs have generally become larger and more
complex.  When transmitted by Usenet this may require the programs be
distributed in many parts, some of which may be lost.  Again,
transmission via FTP is more reliable.

The moderators of binaries newsgroups may be legally responsible for
the reliability of software, whether it is legal to distribute, and
whether it is free of viruses and trojans.  Many may not be willing to
assume that responsibility, and unmoderated binaries groups are not
acceptable in the Big 8.

This proposal is one of several that will removal all groups in the
comp.binaries.* hierarchy except comp.binaries.cbm.


HISTORY: 

The newsgroup comp.binaries.ms-windows was created in January 1993.


DISTRIBUTION:

This document has been posted to the following newsgroups:

  news.announce.newgroups
  news.groups
  comp.binaries.ms-windows
  comp.os.ms-windows.announce
  comp.os.ms-windows.apps.misc
  comp.os.ms-windows.misc


CHARTER:

The newsgroup line is:

comp.binaries.ms-windows	Binary programs for Microsoft Windows.

The charter (from the CFV):

Distribution of applications and device drivers for the Microsoft
Windows operating system, including Windows 3.x, Windows for
Workgroups, Windows NT and Pen Windows.  Drivers, product patches,
shareware, demos and binaries containing source code may be posted if
they are, in the judgement of the moderator, beneficial to the
audience of the newsgroup and do not appear to violate copyright laws.


PROPONENT: 

Jim Riley <jimrtex@pipeline.com>


CHANGE HISTORY: 

2006-10-05     1st RFD
2006-10-16     2nd RFD/LCC