Subject: Biz.* Frequently Asked Questions (FAQ)
Date: Fri, 05 Apr 1996 07:52:35 GMT
Summary: Answers to frequently asked questions about biz.* (periodic posting)
Supersedes: <1996Mar05.073948.23069@xenitec.on.ca>

X-Posting-Frequency: bi-monthly
X-Version: 1.05a
X-First-Draft:.Wed Jun 30 22:54:05 EDT 1993
X-Revised:.Fri Apr 04 20:49:11 EST 1996


...      The "biz" FAQ

This "biz" FAQ posting is periodically repeated for the benefit of new
readers, providing an introduction to the biz.* newsgroups and answers
to frequently asked questions (FAQs) about the "biz" hierarchy.

----------------------------------------------------------------------

Notes:.I have trimmed the canonical newsgroup charters in the list
.of valid groups to adhere to the USENET 80 column convention,
.as requested by David C Lawrence <tale@uunet.uu.net> so that
.he can sync his FAQs and the UUNET news files to conform.

.I have added a short paragraph at the end outlining biz
.hierarchy public discussion procedure.

Request:I would like to add (or generate an additional FAQ) containing
.the full text of the actual charters of all valid newsgroups in
.the biz hierarchy.  Anyone having copies of the charters as
.agreed on when the newsgroups were created is encouraged to
.email them to me: edhew@xenitec.on.ca.

Recent major additions:

    Subject: What is the biz "ad" and "SPAM" cancellation policy?
    Subject: Where is the Biz Hierarchy Administrator's authority derived from?

Recent changes to valid newsgroup list:

.Newsgroup(s) status change:
.  biz.clarinet..(Dec  1/95) status changed to moderated
.  biz.clarinet.sample.(Dec  1/95) status changed to moderated

.Newsgroup(s) created: <none>

.Newsgroup(s) removed:
.  biz.mlm..(Apr  4/96) bogus, improper creation procedure
.  biz.americast..(Jan  2/96) removal requested by Americast
.  biz.americast.sample.(Jan  2/96) removal requested by Americast
.  biz.macmillan.announce(Dec  1/95) bogus, improper creation procedure
.  biz.tpm               (Oct 26/95) bogus, improper creation procedure
.  biz.dec..(Apr  1/95) replaced by biz.digital.announce
.  biz.comp.services.(Apr  1/95) replaced by biz.marketplace.*
.  biz.comp.hardware.(Apr  1/95) replaced by biz.marketplace.*
.  biz.comp.software.(Apr  1/95) replaced by biz.marketplace.*
.  biz.misc..(Apr  1/95) replaced by biz.marketplace.*
.  biz.sco.announce.(June 3/95) replaced by comp.unix.sco.announce
.  biz.sco.binaries.(June 3/95) obsoleted by archive sites
.  biz.sco.general.(June 3/95) replaced by comp.unix.sco.misc
.  biz.sco.magazine.(June 3/95) replaced by comp.unix.sco.misc
.  biz.sco.opendesktop.(June 3/95) replaced by comp.unix.sco.misc
.  biz.sco.sources.(June 3/95) obsoleted by archive sites
.  biz.sco.vtcl..(June 3/95) replaced by comp.unix.sco.programmer

----------------------------------------------------------------------

  Subject: Table of Contents:

    Subject: What is the biz hierarchy?
    Subject: Who created biz?
    Subject: What groups already exist on biz?
    Subject: How can I receive a feed of the biz groups?
    Subject: What is the group creation process on biz?
    Subject: What is the charter of biz.config?
    Subject: Is "biz" the right place for a specific newsgroup?
    Subject: What types of groups would be more suitable for biz?
    Subject: What is considered good net.etiquette on biz.*?
    Subject: What is the biz "ad" and "SPAM" cancellation policy?
    Subject: Where is the Biz Hierarchy Administrator's authority derived from?
    Subject: Are the biz groups archived anywhere?
    Subject: Are the biz groups available via mailing lists?
    Subject: What about gopher, wais, mosaic (and the like) servers for biz?
    Subject: Contributions to the biz FAQ.

------------------------------

  Subject: What is the biz hierarchy?

"biz" is a hierarchy of newsgroups that are carried and propagated
by sites interested in the world of business products around them --
in particular, computer products and services.  This includes product
announcements, announcements of fixes and enhancements, product
reviews, postings of demo software, and the resulting discussions.

While not supporting the electronic equivalent of a newspaper ad, the
"biz" hierarchy is specifically intended to carry traffic of a commercial,
factual, and often technical nature.  Thus, some sites that operate under
restrictions against carrying such traffic may not be able to carry the
hierarchy.

------------------------------

  Subject: Who created biz?

Karl Denninger (karl@MCS.COM) formed biz in the late '80s in response to a
rather large net.discussion over the proper place (if indeed there was any
at the time) for people to post things that were blatantly commercial.  To
quote Karl, "I believe it was 87 or 88, but I don't have an exact date".

The result was the creation of biz.*; "ddsw1", the forefather of the
current MCSNet machines (with pieces and parts still in use) was the first
"hub" of distribution.  MCS maintained "free on request" access to anyone
who would poll for a couple of years.  A few people did, and the groups
got picked up by a reasonably large percentage of the net.

There are many sites which do not carry the groups for reasons of AUP-fear
or local politics, or just because they don't want to pay for commercial 
traffic.  Volume is typically low and the information content is reasonably
good.

Subsequent to it's inception, various biz sub-hierarchies have appeared
where content is actually quite strictly regulated and which explicitly
exclude commercial ads (as differentiated from informational postings).

------------------------------

  Subject: What groups already exist on biz?

A number of groups have been created under several sub-classifications.
The original intention of the sub-classifications may have been to
encourage creation of subgroups under (for instance) biz.comp.software.*
and biz.comp.hardware.*.  The second-level tag has since become more
generalized, such as "jobs", or a specific manufacturer's name.  As the
hierarchy continues to evolve, there is some inconsistency.

The valid "biz" newsgroup list, as of Jan. 14, 1996:

biz.books.technical.Technical bookstore & publisher advertising & info.
biz.clarinet..Announcements about ClariNet. (Moderated)
biz.clarinet.sample.Samples of ClariNet newsgroups. (Moderated)
biz.comp.accounting.Dialogue specific to the accounting software industry.
biz.comp.mcs.Macro Computer Solutions, Inc. news and information (Moderated)
biz.comp.telebit.Support of the Telebit modem.
biz.comp.telebit.netblazer.The Telebit Netblazer.
biz.config..Biz Usenet hierarchy configuration and administration.
biz.control..Control information and messages.
biz.digex.announce.Announcements from Digex. (Moderated)
biz.digital.announce.Digital Equipment Corp News & Announcements (Moderated)
biz.digital.articles.DEC Newsletter, Catalog, & Journal Articles (Moderated)
biz.general.Business operations and offerings.  Discussions only.  No ads.
biz.jobs.offered.Position announcements.
biz.marketplace.computers.discussion.Discussion of computer merchandising
biz.marketplace.computers.mac.Macintosh hardware/software
biz.marketplace.computers.other .Other computer hardware/software
biz.marketplace.computers.pc-clone.PC-compatible hardware/software
biz.marketplace.computers.workstation.Computer workstation hardware/software
biz.marketplace.discussion.Discussion of biz.marketplace issues
biz.marketplace.international.International commerce opportunities
biz.marketplace.international.discussion.Discuss international commerce
biz.marketplace.non-computer.Non-computer merchandise
biz.marketplace.services.computers.Computer-related services offered/wanted
biz.marketplace.services.discussion.Discussion of services over newsgroups
biz.marketplace.services.non-computer.Non-computer services offered/wanted
biz.next.newprod.New product announcements for the NeXT.
biz.oreilly.announce.New offerings from O'Reilly and Associates (Moderated)
biz.pagesat..For discussion of the Pagesat Satellite Usenet Newsfeed.
biz.pagesat.weather.Pagesat Satellite Weather Postings
biz.stolen..Postings about stolen merchandise.
biz.tadpole.sparcbook.Discussions on the Sparcbook portable computer.
biz.test..Biz newsgroup test messages.
biz.univel.misc..Discussions and comments on Univel products.
biz.zeos.announce.Zeos Product Announcements. (Moderated)
biz.zeos.general.Zeos technical support and general information.

------------------------------

  Subject: How can I receive a feed of the biz groups?

NNTP feeds of "biz" may be obtained from, among others:

  dpcdev.dpcsys.com.<dan@dpcsys.com>..(Dan Busarow)
  hookup.net..<newsadm@hookup.net>..(Murray S. Kucherawy)
  news.kei.com..<usenet@kei.com>..(Christopher Davis)
  news.mcs.com..<info.mcs.com>...(Karl Denninger)
  openage.com..<paul@openage.com>..(Paul Fischer)
  rain.psg.com..<randy@psg.com>...(Randy Bush)
  s.ms.uky.edu  .<usenet@ms.uky.edu>..(Kenneth Herron)
  uunet.ca..<support@uunet.ca>..(Lyn Fincham)
  uunet.uu.net..<help@uunet.uu.net>..(UUNET Customer Liaison)
  xenitec.on.ca..<edhew@xenitec.on.ca>..(Ed Hew)

UUCP feeds of "biz" may be obtained from, among others:

  dpcdev.dpcsys.com.<dan@dpcsys.com>..(Dan Busarow)
  excelsior.com..<tim@excelsior.com>..(Tim Tyhurst)
  news.mcs.com..<info.mcs.com>...(Karl Denninger)
  telly.on.ca..<evan@telly.on.ca>..(Evan Leibovitch)
  uunet.ca..<support@uunet.ca>..(Lyn Fincham)
  uunet.uu.net..<help@uunet.uu.net>..(UUNET Customer Liaison)
  xenitec.on.ca..<edhew@xenitec.on.ca>..(Ed Hew)

Propagation of the hierarchy isn't quite as widespread as the mainstream
USENET, but it is growing.  The news admins listed above have made and
continue to make a concerted effort to enhance global biz propagation
and to reduce its geographic fragmentation.  An inquiry to the appropriate
news admin is suggested, as feed availability may vary from time to time
and from host to host.  Note that commercial service providers and others
may charge a fee for service and connectivity -- again, ask.

Those having difficulty getting biz feeds, especially outside of North
America, are encouraged to write to either the undersigned or the
contacts listed above, so that we can help you get a feed.

Those willing and in a position to *offer* feeds are encouraged to
write to the biz FAQ maintainer providing the appropriate information.
Additions to this biz provider list are most welcome.

------------------------------

  Subject: What is the group creation process on biz?

The group creation process on biz is somewhat looser than the "standard"
hierarchy.  To some extent this reflects that fact that biz is an ongoing
and maturing experiment-in-process.

[...in response to the question...]
>Uh, I don't pretend to be a USENET know-it-all, but don't you need to
>make this an RFD, then hold a CFV, then a final ACK, then do the
>newgroup?  Or is the biz. hierarchy like alt. in that anyone can
>create a new newsgroup?

Neither.  The biz hierarchy has its own peculiar set of rules, which
have evolved from necessity and common sense over the years.

In theory, anyone can issue a newgroup message on a whim.  However, that
doesn't necessarily mean that it will be either widely honored, or that
the new newsgroup will actually be propagated to any useful degree!

In practice, creation of new 'biz' newsgroups is normally handled as follows:

0. Is someone else already in charge of your desired discussion area?

   Some biz sub-hierarchies are historically managed.  Creation of new
   newsgroups within them requires the agreement and support of the
   respective responsible party (eg, biz.digital.* or the old biz.sco.*
   sub-hierarchy).  Check the FAQ for the sub-hierarchy, locate and
   contact the authoritative individual, and ask them to follow the
   biz creation process on your behalf.

..- otherwise -

1. Demonstrate its viability:

   Ongoing dialogue in existing newsgroups and private discussion between
   interested parties to the resolution that the new newsgroup has a
   likelihood of success may suggest it's creation.  Where no existing
   newsgroup appears appropriate for initial discussions of a new "biz"
   topic, postings should be directed to biz.general, specifically
   chartered for this purpose.

."biz.general provides an un-moderated newsgroup for general
.dialogue of, or related to, business operations and offerings.
.Commercial ads are prohibited."

   Over a reasonable period of time, sometimes as long as several months,
   it will be fairly evident from the volume of existing topical discussion
   whether a new newsgroup is warranted.

2. Issue a biz newsgroup PROPOSAL, a "Request for Discussion".

   When participants agree that longevity, intensity, and sheer volume
   of existing dialogue suggests consideration of biz.<whatever>, barring
   strenuous or widespread objections, the proponent should post a formal
   proposal to biz.config including the following:
.- Name of the proposed new newsgroup,
.- Charter,
.- Canonical newsgroups file entry,
.- Status (moderated or unmoderated)
.  (if moderated, provide the name and email address of the moderator),
.- Background for the newsgroup,
.- Supporting information and justification for creation,
.- Invitation to discussion of at least two weeks duration,
.- Date the newgroup control message request will be issued.

   Feel free to clone a previously successful proposal.  Include the
   information you feel important in influencing others to agree that
   your proposal is sound!

   Optionally, for a wider audience, folks sometimes choose to cross-post
   these discussions to USENET group news.groups and perhaps other groups
   relevant to the proposal.  Since other newsgroups aren't necessarily
   monitored by those you most wish to influence, please set the
   "Followup-To:" header line to biz.config _only_.  

   On occasion, objections are made that should be taken under advisement,
   generally for naming reasons (i.e. consistency with existing groups
   either in biz or USENET), unnecessary duplication with other groups,
   or perhaps that the preceding criteria haven't been met.  Advice may
   often be offered by those who have supported the biz hierarchy for years
   and know something about it, or by the biz news admins who actually pay
   the cost of moving biz articles between the far corners of the planet.
   Such advice is honorably offered and should be heeded.

   It is good practice to enlist, via biz.config, the support of the key
   news admins who handle the vast majority of biz propagation, particularly
   those who control the NNTP links that bring disparate chunks of geographic
   biz propagation together.  This will ensure that your proposed newsgroup
   will be indeed be propagated.  Convert those who post opposition to a
   position of tacit agreement at minimum; if you can't do that, consider
   going back to step 1.

3. Wait the balance of your announced discussion period.  If there is no
   (further) substantiated objection, the newsgroup has successfully passed
   the tests for inclusion in the biz hierarchy.  If the newsgroup will be
   within a sub-hierarchy under the auspices of a given individual, ask the
   party responsible to ask the "biz authority" to issue the newgroup control
   message.  Otherwise, place the request directly.  In either case, outline
   the justification for it's creation according to the above guidelines,
   to be presented to the biz newsadmins.

   The "biz authority" maintains the valid "biz" newsgroups list and issues
   the newgroup control messages for the biz hierarchy so that the new
   newsgroup is honored and propagated by the biz backbone news admins.
   Currently, these duties reside with Ed Hew <edhew@xenitec.on.ca>, who
   at this time also maintains this FAQ.  A valid newgroup control message,
   including a request that the biz backbone news admins support your
   newgroup with their own newgroup messages, will usually be issued
   within 7 days.

4. Send email to the maintainer of this FAQ to ensure that your new
   biz newsgroup is listed!  (They may not always be the same person.)

------------------------------

  Subject: What is the charter of biz.config?

"biz.config is to serve as the controlling newsgroup for discussion of
 new biz groups, connectivity, propagation, policy, and the like."

The biz.config canonical newsgroups entry is:

biz.config..Biz Usenet configuration and administration.

Note the somewhat ambiguous use of "Usenet" in this description.  In
this FAQ, the usage USENET means the comp/misc/news/rec/sci/soc/talk
hierarchies, aka "mainstream USENET".  Many people, including whoever
originally wrote the description line, use "Usenet" to loosely mean,
"interconnected newsgroup hierarchies and/or distributions propagated
via B News compatible mechanisms.", and now encompassing a multitude of
NTAs (News Transport Agents) within the "greater internet".  One goal
of this FAQ is to clarify in people's minds the distinction between the
transport mechanism and the sets of networks (plural) carried over them.
To summarize, the description should probably just refer to the "biz net."

------------------------------

  Subject: Is "biz" the right place for a specific newsgroup?

Not if it only deals with local concerns!  Subjects that would be of
interest to relatively restricted portions of the planet are always
better served in a newsgroup under a more local or regional hierarchy.
For example, if you're going to discuss "business activities in the
Kitchener-Waterloo area", it definitely doesn't belong under "biz",
but perhaps may be a candidate for "kw.biz".  Never consider inflicting
a newsgroup on the global readership for postings restricted to a
geographic area most of the readers have never even heard of.

Topics of global interest may already be well served in existing biz
newsgroups.  Familiarize yourself with the charters and monitor their
content before proposing a possibly redundant newsgroup.

Expand your search beyond the "biz" hierarchy.  Your topic may already
be properly and adequately subsumed in one or more newsgroups under
other hierarchies within the "Big 7" or under "alt" or "ads".  If the
nature of your intended newsgroup is more appropriate under another
hierarchy then it should be proposed there instead.  Do your homework.

------------------------------

  Subject: What types of groups would be more suitable for biz?

Any group that intends to include specifically commercial announcements
to the global community from businesses concerning their main products
or focus would more properly fit the charter of the biz newsgroups.
Examples are the biz.*.announce newsgroups, often with related
discussion newsgroups.

Expert technical content from a specific vendor's staff is also most
appropriate within biz, noting that some in the "mainstream USENET"
frown upon anything that might be considered tainted by vendor
participation even for the informational aspect provided.  This has
proven to free many who have the knowledge, to post valuable insight
into the products they develop and work with.

Reorganization of the most commercial part of the "biz" hierarchy
in early 1995 into "biz.marketplace.*" provides a home for certain
forms of charter-specific advertising.  Read their FAQs and check
their charters for more specific information.

------------------------------

  Subject: What is considered good net.etiquette on biz.*?

Here are some etiquette reminders that will help us all to make the
hierarchy an ever-friendlier place:

 -- Please, before posting, ensure that you've read the basic USENET
    etiquette guide in news.announce.newusers.  Ensure that you are
    also familiar with the newsgroup charter and acceptable content.

 -- Is your posting so blatantly an advertisement that it goes beyond
    the bounds of being "informational", and hence may cause many users
    or sites to restrict their participation in "biz"?  If so, tone it
    down!  Keep it factual.  Edit out the hype.  Product and service
    announcements are welcome within specific biz "announce" newsgroups.
    Check the newsgroup charter, and the availability of an appropriate
    "announce" newsgroup before posting.

 -- "So, where do I place my blatant commercial ads?"  From time to time,
    an "ads" hierarchy has been proposed.  If you need such, create it!

    Certain biz newsgroups may tolerate private or public ads to some
    extent - monitor them, check and respect their charters.  Ads are
    specifically permitted in some of the biz.marketplace newsgroups.
    Don't post ads to newsgroups that don't tolerate them.  Never
    blindly crosspost to every biz newsgroup in sight or you will
    certainly draw the ire of many net folks upon yourself.
 
 -- Remember that biz isn't the mainstream USENET.  The rules of the
    comp/misc/news/rec/sci/soc/talk hierarchies do not necessarily apply
    here.  However, those guidelines that are mostly net.common.sense
    should probably always be taken to heart.

 -- Remember that biz is a volunteer network.  All the code, maintenance,
    and question-answering are maintained by folks who freely give their
    time to help the net.  Please consider this and treat them accordingly.
    Be as precise as possible so that overworked knowledgeable people will
    not waste time trying to solve the wrong problem when trying to help you.

------------------------------

  Subject: What is the biz "ad" and "SPAM" cancellation policy?

Commercial ads may be permitted in specific newsgroups.  Ensure that
the newsgroup(s) you select for posting will tolerate the ad and it's
specific type and content before you post.

Due to the nature of news software, articles crossposted to inappropriate
newsgroups will defacto be removed from all crossposted newsgroups when
canceled, thus posters should be very careful not to crosspost to a
newsgroup which might result in cancellation of the article throughout
USENET.

Ads posted to inappropriate biz newsgroups may be canceled by the
individual (or their delegates) responsible for administering that
newsgroup.  It is recommended that accepted "cyberspam" conventions
be followed as well as the specific biz "adcancel" convention, and
that the canceling party be properly identified.

Excessively Multi-Posted articles (aka SPAM) may be canceled by the
appropriate USENET authorities with that responsibility.

------------------------------

  Subject: Where is the Biz Hierarchy Administrator's authority derived from?

Extensive discussions were held in biz.config during 1993-1994, where
the biz newsadmins responsible for propagation of the biz hierarchy
agreed on the set of regulations for the biz newsgroup hierarchy.  This
set, as amended by discussion and agreement in biz.config from time to
time, is reflected in this FAQ, and is to be enforced by the current
Biz Hierarchy Administrator, often referred to as the "Biz Authority",
or "Biz Newsgroup Authority".

Questions and suggestions on biz hierarchy administration and policy
should be discussed in biz.config.  Before doing so, please check the
biz.config archives to ensure the issue has not already been dealt
with.  If appropriate, queries may be addressed privately to the
current Biz Authority.

The "Biz Authority" position is currently delegated to Ed Hew
<edhew@xenitec.on.ca>, who has gone on record as hoping that another
responsible, respected, knowledgeable and qualified individual will
come along to assume this position in future.  Transfer of authority
would require the consent of the biz newsadmins who granted it in the
first place.

------------------------------

  Subject: Are the biz groups archived anywhere?

Selective biz newsgroup archives are maintained at various publicly
accessible archive sites, not necessarily limited to:

.telly.on.ca..<evan@telly.on.ca>.(Evan Liebovitch)
.ftp.xenitec.on.ca.<edhew@xenitec.on.ca>.(Ed Hew)
.wimsey.com..<sl@wimsey.com>..(Stuart Lynn)

------------------------------

  Subject: Are the biz groups available via mailing lists?

Selectively, yes.  Check current FAQs in respective biz newsgroups
for further information.  

.** note: biz.sco.* was replaced by comp.unix.sco.*, check the
.   FAQ there for information on their current mailing lists.

------------------------------

  Subject: What about gopher, wais, mosaic (and the like) servers for biz
.   newsgroup archives?

A number of servers are under construction and will be listed as they
become operational.  They respectively archive specific portions of
the biz hierarchy.  Currently operational:

WWW (mosaic) URL:  http://www.xenitec.on.ca/..(biz.sco,biz.config)

.** note: while biz.sco.* was replaced by comp.unix.sco.*
.   in Apr/95, the old (and new) archives are still in place.

------------------------------

  Subject: Contributions to the biz FAQ.

Many thanks to the following for their contributions:

    Karl Denninger <karl@mcs.com>
    Kenneth Herron <kherron@ms.uky.edu>
    David C Lawrence <tale@uunet.uu.net>
    Mark Linimon <linimon@nominil.lonesome.com>
    Murray S. Kucherawy <mskucher@nic.hookup.net>
    Catherine E. Stanton <cat@uunet.uu.net>
    Tim Tyhurst <tim@excelsior.com>
    Randy Bush <randy@psg.com>

This posting, like much of net.land, is maintained on a purely volunteer
basis.  I welcome reactions, additions, and corrections, via email.

Public discussions on biz hierarchy policy, procedures, and newsgroup
proposals should be posted in biz.config, crossposted to a minimal
list of other possibly affected newsgroups, with "Followup-To:" set
to biz.config only.
--
  Ed. A. Hew <edhew@xenitec.on.ca>
  biz FAQ maintainer, biz newsgroup authority, various other hats
