Policy:Operator AUP
From #LinuxWiki
 |
Contents |
Mission
This is your mission, if you choose to accept it..
You will be participating in the maintenance of the IRCnet channel #linux. This guide will help you cope with the other ops and with the users, this guide will also make certain guidelines of how to behave and what has been decided about the channel maintenance.
This is not a definite guide, these are just guidelines how to behave and what is expected from you by other ops.
Good luck, Jim The simple rules
Simple Rules
- No auto-opping: The bots are currently quite capable of opping each other and other ops, do not enable any sort of auto-ops when on the channel. and if you have auto-ops on on some other channel, make sure that they don't affect #linux in any way. Better yet, don't use any: They are bad policy in any case.
- All automated functions need to be disabled while AFK (except the ones explicitly mentioned) There has been situations where ops have been kicked from the channel while deopping clone-bots, please remove ALL of these functions to protect the channel, the bots are fully capable of handling attacks, and if they can't handle them, it wouldn't have done any good anyways =)
- Trust your fellow-ops to do the right thing. This also means:
- Respect actions by your fellow ops.
- Unless there is an immediate threat to the channel, never undo actions by your fellow ops without discussing with them first.
- Do not take any offensive actions against your fellow ops. This includes kicks and bans, but also..
- Channel operators should not be found fighting or bickering in the channel. If you have something to discuss with a fellow operator, take it off-channel immediately, unless of course the discussion is on-topic.
- Operator rights are granted to allow for assisting in channel maintenance, and for no other reason.
Some Recommendations
- Turn on your auto re-join: unlike normal users, it is good for the channel if the ops rejoin the channel when kicked from it. it is up to you how you set up the auto re-join, i prefer a timed rejoin, 10 sec delay should be enough for everyone (have i heard something like this before)
- Keep track of your messages: It would be good if other ops can get a hold of you, if you are in IRC, log your messages so that you can read them later. (other means include the linux-ops list)
- Nicknames should be static: please, don't change your nickname too often, it will cause confusion. It is OK to change your nickname to avoid killing or something alike, but the nickname change should be temporary. This will make it easier for everyone else to know who you are.
Kicks
The idea of a kick is to remove someone from the channel who is breaking one, some, many or all of the established rules of the channel. The idea of a kick is NOT to entertain you when you've nothing better to do.
The following list is not complete and all sorts of scripts to automate the kick messages are appreciated. Kick reasons with suggested kick messages are as follows:
- ALL kick reasons shall be descriptive and include a link to http://linux-irc.net/why/ to help the user see why he was banned.
- Bot bans must be set on the channel and must always expire::
- Use this template: .+ban *!*@*.some.lame.host.eu #Linux %180d REASON - http://linux-irc.net/why/
On these rules
Breaking these rules will result in a warning, and if the rules are broken again, it will result in a removal of the ops. (No, you cannot complain about this!)
When someone is being accused of breaking of these rules, a log MUST be provided of the events that happened. The log should be absolutely complete, nothing should be cut out of it even it will result in a LONG log.
Please note once again, these are not definite rules, there shouldn't be any sort of bickering about this. There has to be a good reason. and i hope the logs will prove your point.
Hierarchy
There is no operator hierarchy on the channel. It doesn't matter if you are operator, bot-master, bot owner, or if you have been an operator for 500 years already: You still have to act according to these basic rules.
