This file lists the duties of the moderators in PIN conferences. Rules for the network as a whole are listed in the rules.txt file that is included in the is packet. What is a moderator? --------------------- In a network mail conference, a moderator is a user of the network who has volunteered to monitor the message traffic of one of the conferences. The job of the moderators in Politically Incorrect Net is two fold. The first, and most important is to stimulate messages that are within the topic guidelines of the conference, as listed in CONF.LST. The second duty of the moderator is to inform users of inappropriate behavior in the message areas, and let the admin and users sysop know of this. Being heavy handed is NOT in the job discription, nor will it ever be. A moderator should keep messages on track, and topic with gentle reminders, not threats or flames. Moderators messages are monitored by the admin, and inappropriate treatment of users will be noted and corrected. Hopefully this won't happen. In The Politicallly Incorrect Net, the system administrator will act as the moderator for the following conferences. PIN_SYSMOD PIN_ADMIN PIN_SUGGESTION How do I become a moderator? ---------------------------- This is an easy question. Volunteer! Moderators will be selected from net users who volunteer for the job. They needn't be sysops (though they can), they don't have to be a "friend of the admin", or anything else. They should be a mature message user, who knows how to effectively deal with people without stepping on their toes. To voluteer to be a moderator, leave a message to BOB BELLER in the PIN_SUGGESTIONS conference. In the message include the conference you'd like to moderate, and why you think you could do a good job. Moderator Responsibilities. -------------------------- 1. Post the rules of your conference at least once a month. Conference rules should follow as close as possible the network rules listed in Rules.Txt. Your posting doesn't have to include everything in that file, (nor should it) but instead a one or two paragraph sysopsis of the rules, and a paragraph on what the conference is about. You can elaborate on the short listing in conf.lst, and expand what you will except as "on topic posts" in your conference. Keep in mind that making one conference all inclusive will draw users from other conferences. Try to avoid this. Post this message to ALL and use a subject line that will let them know what it is. Any major deviation from the rules in Rules.txt must be approved by the admin. Post a message in PIN_ADMIN listing what you'd like to change for your conference, and why. It will be responed to as quick as possible. 2. Stimulate message posting... The purpose of the net is to transfer mail back and forth, if no one is posting, there won't be much mail to transfer. When things get slow, post a message or two on different topics that fit the conference, and see what happens. 3. Notify users of inappropriate behavior. If it is just a case of an off topic post or two, a gentle reminder of the correct conference for the messages should be all that is needed. When a user becomes a "problem child", and is violating more sacred rules, such as use of vulgar language, cross posting messages to the whole net (Spamming), or flaming other users do the following: a. Post a message to the user (quoting a small amount of the original) explaining why what they did is wrong. b. Post a message in PIN_ADMIN to BOB BELLER (or current administrator) with the subject PROBLEM USER. Quote back the entire problem message. Carbon Copy the message (cc:) to the sysop of the board where the message originated. Most offline readers will allow cc: messages. This is the only case where sending carbon copies is acceptable. If this is a first offense, it will be noted, however, no action will be taken. If the behavior doesn't change after a moderator warning, then the user may be asked to leave the conference for a short while. (see rules.txt for lengths of vacations). Notify the sysop and admin of any continued problems with the particular user. If the behavior changes, no problem, live and let live. If it doesn't, let the admin handle it. 4. NEVER!!! Argue about your moderating with a user in your conference. This can only lead to problems (for you). If the user isn't happy with what you did, explain to them that rules.txt outlines how to appeal a net suspension, or conference vacation. In fact, cut that part out of Rules.Txt and leave it to them in the message. HELPFUL HINTS. -------------- While it would be great that every situation would fit this set of guidelines, it won't happen. It never does. I know that since I left one thing out that could happen, it will! (Murphy writes his laws based on what I forget to include in things). 1. Use an offline mail reader. It's nearly impossible to keep up with all message traffic "online". Don't try to, unless you are a speed reader. A few good mail readers for DOS are OLX-TD.EXE (olx ver 2.1) from Mustang Software, and Speed200 (Speed Read ver 2.0). UniQwk, OLXWIN, and Cmpqwk are all good windows readers. KWQ is a good OS/2 reader. Freddie works well on Macs. 2. Read the mail in your conference at least 3 times a week. That way problems don't get past you. Plus it keeps you current on what's going on, and who's new in the conference. 3. Post a welcome message to a user who you notice for the first time. This helps new users feel welcome in your conference, and makes them more likely to post to it. 4. Use the PIN_SYSMOD conference to talk to the other moderators and sysops about general (non official) business, and say hi to each other. You are part of the group that makes the work in network. 5. Don't get discouraged if you have a slow week or two of mail. It happens, and things will pick up. 6. Feel free to send me mail suggesting changes to the rules, etc. I am only one guy, and things get past me occasionally. When they do, let me know, and I'll see if I can fix the problem. 7. If you are getting burnt out, or bored, resign. There is no disgrace in saying you are having a hard time with the job. We ain't paying you to do this, and there are times when this can't be the priority, or even close. Thanks for volunteering. Modified 01/05/96