For your newsgroups file:

dfw.[newsgroup]

template charter for dfw.* groups

CHARTER

Area of Coverage of dfw.[newsgroup]

This section contains verbiage about what the group should cover. The verbiage may be multiple paragraphs

Intended Use of dfw.[newsgroup]

A more detailed description of the intended use of this newsgroup.

Hopefully, the description is sufficiently enough detailed to allow ISP's to determine charter violations for disciplining their users.

The charter for dfw.internet.providers is an excellent example.

Cross-posting guidelines for dfw.[newsgroup]

Detailed cross posting guidelines for the newsgroup. Outlines limitations on cross posting into and out of this newsgroup. May also describe appropriate or inappropriate reasons for cross posting, as well as in/appropriate groups for cross posts.

Once again, the charter for dfw.internet.providers is an excellent example.

Article Format

1. Articles posted to dfw.[newsgroup] MUST be flat-ASCII. This means:
   1. No Binary postings, uuencoded or base64.
   2. No MIME encoded messages. Posts SHOULD be readable by the simplest text-only newsreader.
   3. No HTML, although HTML-like emoticons are acceptable.
   4. No characters with a value greater than 127 in any part of the post.

2. Posts SHOULD be shorter than 30K in size. Longer items SHOULD be made available for FTP or HTTP download and a pointer to that file posted.

3. Posts MUST contain a valid From address, unless the ".invalid" domain is used (see RFC 1036). Spam blocks are acceptable. By definition USENET newsgroups are a broadcast medium. If you have a post that needs to be anonymous, it is not a valid topic for dfw.[newsgroup]. Post this material elsewhere.

4. ROT13 encoding SHOULD NOT be used on any field in the headers. Nor should any attempts, except minimal spam blocks, be made to obscure the origins of the posting.

5. Posts MUST contain a "Abuse-Reports-To:" or "X-Complaints-To:" header with a valid email address. When RFC1036 is updated, this line SHOULD be adjusted to comply with the latest specifications. Adding or replacing this header is the responsibility of the news server where the article was injected.

Failing to follow the above formatting requirements could result in an article being canceled instantly and without warning by an authorized moderation device (human or otherwise) for the group in question. Articles cross-posted to other groups and dfw.[newsgroup] must still follow the criteria of dfw.[newsgroup] and be subject to these rules.