Step 1. 

Decide if you *really* need to create a new hierarchy, there are
currently hundreds of existing hierarchies out there that deal with
thousands of topics. Employ the options of using an existing hierarchy
such as alt.* before you go through the process of creating a new one.

Step 2.

Do you want to distribute the hierarchy to just a few or many sites? If
you wish to limit the sites than be VERY careful about sending out control
messages. It is very easy to have these being sent to every site on
Usenet. If you are having these groups created on just a few sites it is
probably a better idea to have the admins of each manually add them. Some
sites will also add group where they receive messages so it you have to
take care that those sites don't send articles from your hierarchy to
other sites.

In summary ensuring that a group is restricted to more than a small number
of sites is difficult and sooner or later some messages will leak out.

Step 3.

Decide on the name of the hierarchy, you should check the Master List to
see if it has already been taken. Having the same name as an existing
hierarchy causes problems for both and is best avoided. Also don't use a
name that is likely to be used by someone else. ie if your organisation is
the University of Hereville don't create hereville.* if the local area
might want to use it.

Step 4.

Work out the rules for the hierarchy, if it is for your organisation then
an official policy should be created and a position allocated for
controlling creating and distribution of any groups. If you are widely
distributing the hierarchy you should consult with interested parties
about rules for the groups and possible names. Take a look at the rules
for the uk.*, nz.* and other hierarchies to get an idea of what you
might like to use. 

At this stage you should plan what the hierarchy is going to look like in
the future. If the hierarchy becomes popular then you may need to add on
new groups to cover expanded and new topics. The design of the hierarchy
should be such that these groups can be easily accommodated. 

Some groups are common among most hierarchies. 

A test group (usually called *.test ). 
A group for discussing creating new groups ( *.config or *.net.admin ).
A general discussion group ( *.misc or *.general ).
An announcement groups ( *.announce ).
A group for non-commercial advertising ( *.forsale , *.wanted )

Step 5.

Create an alias for sending out control messages for the group, don't use
your own name since your address might change. Remember that once people
start accepting this alias they might take years to update it so make sure
this is as permanent. You should also create a new PGP key (see the
sections above) for signing control messages. If need be your should also
have an alias for moderated groups.

Step 6.

You should inform me and tale@isc.org of all the information about the
hierarchy we need for our lists. You should then post to
news.admin.hierarchies with similar information. You should look at
creating a FAQ for the hierarchy that you can crosspost to the admin group
and news.admin.hierarchies.

Step 7.

Start sending out newgroup messages for the groups. You should sign these
with the PGP Key and make sure you include a description line for the
group. You should also duplicate the information about the hierarchy
including the PGP Key and the Admin Email alias so that News-administrators
can automate your hierarchy if they wish.

Step 8.

Keep posting you FAQ, Send out booster control messages every year or so
and make sure you add and remove groups according to the rules.

© 2008 FAQS.ORG. All rights reserved.