🚀 go-pugleaf

                          BACKGROUND: co.config 

The charter below was approved by consensus in co.config on
Friday, May, 28, 1999, following established procedures for new group
creation in the co.* hierarchy.  This charter will be posted twice
monthly.

CHARTER:  co.config is an unmoderated newsgroup for the discussion 
of ways and means of creating a viable national Usenet hierarchy
for the State of Colorado.  Topics may include, but not be limited 
to, newsgroup creation and removal; hierarchy rules and their
enforcement; propagation in the State of Colorado and beyond; 
the creation of a committee to manage the future growth and 
development of the co.* hierarchy; and monitoring traffic in
the groups.

POSTING RULES:  The posting rules of the co.* hierarchy are
incorporated into this charter by reference.  Some highlights:

Direct advertising is not permitted, but occasional announcements
of new software, newsletters, and/or web sites are acceptable 
provided they are done in a tasteful manner.  Posters who wish 
to advertise their business or profession should create a 4-6 line 
signature file to append to each article they post.

Make Money Fast chain letters, pyramid schemes, and other types 
of scams or spams are not permitted, either.

All articles must be written in plain text.  Except for PGP
signatures, non-standard formats should not be used.  This prohibition
includes binaries, HTML, v-cards, and other types of 'fancy' posts.
If you do have a binary you want people to see, put it on your web
page and post a pointer to the group telling people where to find it.

Please set your horizontal line length to 75 characters so as to make
it easier for others to read and respond to your articles.

The co.* hierarchy has a 5-group limit on crossposts to help keep 
the noise level down and reduce the chances of articles being 
cancelled by other hierarchies which enforce their own crosspost 
limits.  If you see an article crossposted to more than 5 groups, 
please trim the Newsgroups: line to comply with this rule.  And 
when you post yourself, be sure to select only the 5 most relevant 
groups.

Violations of this charter or the hierarchy rules may be reported 
to the co.* hierarchy administation, your Internet Service Provider,
and/or legal authorities in appropriate situations.  This applies
especially to illegal chain letters, forgeries, unauthorized use of
registered domains, newsgroup "spamming", and/or the constant
harassment of other posters.

NEWSGROUP HOST:  This charter will be posted twice a month by the
Newsgroup Host. The host will also keep an eye on the group, and
report serious violations of the posting rules to the co.* hierarchy
administration.  Further action, including cancellation of an
offending post, is at the discretion of the co.* hierarchy
administration.

If for any reason, the host is unable or unwilling to continue
monitoring the group, the co.* hierarchy administration shall post a
notice asking for volunteers or nominations from the group.  If there
is no contest, a sole volunteer or nominee may be appointed directly
by the co.* hierarchy administration.  But if there are more
candidates, a poll will be conducted to determine the wishes of the
group.  The final decision then rests with the co.* hierarchy
administration.

ANNUAL REVIEW

On or about the first anniversary of the adoption of this charter, the

co.* hierarchy administration shall post a Call For Discussion on 
the status of the group in accordance with the procedures outlined 
in the co.* hierarchy newsgroup creation rules.  The discussion 
period shall be at least two weeks.  If at the end of two weeks, no 
problems have been identified or the problems identified have been
satisfactorily resolved, the newsgroup will remain as is until the
next evaluation.  Buf if major changes are desired, a new RFD must be 
posted for full discussion in co.config in accordance with the co.* 
hierarchy newsgroup creation rules.

END CHARTER