OperPak
From Afterxwiki
Contents |
Introduction
The "OperPak" is a collection of files and documents designed to aid you in being a good oper (or admin) on the AfterX IRC network, whether you are a complete novice to the oper world and AfterX IRC or if you are an experienced long time AfterX oper. It is useful to all people across the board.
By our definition of "good oper/admin", this means:
1) Respecting and caring for the other members of the AfterX staff.
2) Respecting and abiding by the AfterX Charter.
3) Rrespecting and abiding by the rulings of the AfterX Committees.
4) Contribute to the good spirit of AfterX, perhaps help out with development of AfterX IRCd, maintaining websites, etc.
and last, but not least,
5) Respecting and caring for AfterX's users, regardless of who they are and their history; even if they take the complete piss out of you 24/7.
The original AfterX Operpak was made by Sterri a few years ago. As time went by things changed, we've had to make some updates and changes to it.
Updates
20 November 2006
Massive changes made, added to the AfterX Wiki.
25 September 2003
Documentation for IRCD and services updated.
9 August 2003
A new charter has been added as per forums.xnet.org
30 June 2003
References to mailing lists deleted on the resource pages and link to the forums added. A more thorough updates on the rest of the document to weed out mailing list info will be done shortly
I'd like to thank...
I'd like to thank those who helped with the OperPak since 1998.
Documentation
Introduction
We've tried to gather most of the useful documentation in this section. If there's any documentation you would like to see in addition to what we already have, please e-mail us and we'll take care of it.
Thanks.
Important Links
Below are some important links that contain information that is crucial to being a good, knowledgeable AfterX staff member.
Stress Handling
Stress, n: The confusion caused by one's mind overiding the body's basic desire to choke the living s### out of some arsehole who desperately needs it...
Everyone is going to get stressed at some point and act unprofessionally when all seems to be against them and they feel alone in the world.
This section doesn't really concentrate on any oper commands as such, but is designed to be a guide on dealing with users when we are pissed off.
Due to misconceptions held by normal users about IRCop's conflicts are never going to disappear completely so this section is about:
- How stress affects us - why we react the way we do - What has helped people in the past to deal with their anger when they lose it
Basically it is the scientific explanation why people react the way they do. There are two natural human reactions to any stressful situation. These are Fight and Flee.
As opers on occasion we find ourselves in shoddy moods and then get involved in a situation with a user or another oper, that rubs us the wrong way and we react poorly.
This is the Fight mechanism and it is a 100% normal human reaction. In times such as these it may become necessary to remove yourself from the situation to avoid
1. Making it worse
2. Reacting more strongly than necessary.
We all know that feeling, its like the hairs on the back of your neck are standing straight up, you're red with anger, and you just feel like you want to explode.
In the wild, animals react with a show of force. In society, this does happen as well but it is an unnecessary reaction unless your life is in danger which, by the way, is why human beings have this mechanism.
In a perfect human society however, when placed in a bad situation we would walk away and regroup. This is the Flee mechanism showing itself. It is not a sign of weakness. It is a sign of a responsible and intelligent human being.
It takes a certain measure of intelligence to remove yourself from a confrontational and frustrating situation. Be it something so simple as you confronting yourself.
This little bit of information can also be handy when dealing with the email lists. Because they are basically a forum to inform others of our opinions, we must have the foresight of knowing that not everyone will have the same opinion as we do or see a situation the exactly same way.
We don't have to like what they say, we don't have to like the person saying it, but we should at least respect their right to say it. The Internet is a place of Free Speech. And although this can become frustrating, especially when we see something we so strenuously disagree with, again this fight or flee mechanism will come into play.
So the point to this note is to say, although it may be harder to walk away at the time, in the end, it will prove to be a very wise decision because it may prevent rash behavior, especially when dealing with users, and it may just enable you to see the situation more clearly than you can when your angry and in the midst of it. Because we believe this sort of approach will create a stronger working relationship between opers and users, it is inevitable, that it will create a stronger AfterX.
Services
Introduction
This section is based on the help messages included in IRC Services itself. If you need more info on services, you can find that here.
Nickserv
NickServ allows you to "register" a nickname and prevent others from using it. NickServ is controlled through various commands which allow for registration and maintenance of nicknames. For a list of commands, type /msg NickServ HELP COMMANDS; to use a command, type /msg NickServ command, and for more information on a specific command, type /msg NickServ HELP command. If a registered nickname is not used for 30 days, the registration will expire and the nickname will be available for anyone to use.
For a detailed list of NickServ commands, and descriptions of them, see here
ChanServ
ChanServ allows you to register and control various aspects of channels. ChanServ can often prevent malicious users from "taking over" channels by limiting who is allowed channel operator privileges. Type /msg ChanServ HELP COMMANDS for a list of ChanServ commands; to use a command, type /msg ChanServ command, or for more information on a command, type /msg ChanServ HELP command.
For a detailed list of ChanServ commands, and descriptions of them, see here
MemoServ
MemoServ is a utility allowing IRC users to send short messages to other IRC users, whether they are online at the time or not, or to channels(*). Both the sender's nickname and the target nickname or channel must be registered in order to send a memo. Type /msg MemoServ HELP COMMANDS for a list of MemoServ commands; to use a command, type /msg MemoServ command, or for more information on a command, type /msg MemoServ HELP command.
For a detailed list of MemoServ commands, and descriptions of them, see here
OperServ
OperServ is a service used by operators to help administer an Internet Relay Chat network. It provides IRC operators with functions to help monitor and maintain the network, manage the other services, and deal with problematic users. Type /msg OperServ HELP COMMANDS for a list of OperServ commands; to use a command type /msg OperServ command, or for more information on a command type /msg OperServ HELP command.
For a detailed list of OperServ commands, and descriptions of them, see here
StatServ
StatServ is a utility which displays statistics relating to the network's servers. It provides IRC operators with statistics relating to the network's servers and users. Type /msg StatServ HELP COMMANDS for a list of StatServ commands; to use a command type /msg StatServ command, or for more information on a command type /msg StatServ HELP command.
For a detailed list of StatServ commands, and descriptions of them, see here
Server Commands
Introduction
This section will give you a crash course in the commands and modes available for users/opers and channels as well as some IRCd info and other server related information.
User Modes
Mode |
Description |
r |
Identifies the nick as being registered |
s |
Can listen to server notices |
v |
Receives infected DCC Send Rejection notices |
o |
Global IRC Operator (Set in Oper Block) |
O |
Local IRC Operator (Set in Oper Block) |
B |
Marks you as being a Bot |
b |
Can send and read ChatOps |
i |
Invisible (not shown in /who) |
A |
Server Admin (Set in Oper Block) |
x |
Gives user a hidden hostname |
q |
Only U:Lines can kick you (Services Admins Only) |
a |
Services Admin (Set in Oper Block) |
g |
Can send & read globops and locops |
H |
Hide IRCop Status (IRCop Only) |
S |
Used to protect Services Daemons |
t |
Says you are using a /vhost |
C |
Co-Admin (Set in Oper Block) |
d |
Makes it so you can not receive private messages |
k |
Can see all the /kill commands executed |
N |
Network Administrator (Set in Oper Block) |
w |
Can listen to wallop messages |
h |
Available for help (HelpOp) (Set in OperBlock) |
G |
Filters out all the bad words per configuration |
W |
Lets you see when people do a /whois on you (IRCops Only) |
Channel Modes
Mode |
Description |
A |
Only Administrators may join |
a <nick> |
Goves protection to that user, may not be kicked |
b <nick!user@host> |
Bans the givin user from the channel |
c |
No ANSI color can be sent to the channel |
C |
No CTCP's allowed in the channel |
e <nick!user@host> |
Exception ban – If someone matches this, they can join a channel even if they match an existing ban |
f * <lines:seconds> |
Flood protection, if the * is given a user will kick banned when they send <lines:seconds> if no * they are just kicked |
G |
Makes channel G rated. Checks for words listed in the Bad Word Blocks, and replaces them with the words specified |
M |
A registered nickname (+r) is required to talk |
h <nick> |
Gives half-op status to the user |
i |
Invite required |
K |
/knock is not allowed |
k <key> |
Sets a key needed to join |
l <##> |
Sets max number of users |
L <Chan> |
If the amount set by +l has been reached, users will be sent to this channel |
m |
Moderated channel. Only +v/o/h users may speak |
N |
No nick name changes permitted |
n |
No messages from outside channels |
O |
Only IRCops may join |
o <nick> |
Gives a user channel operator status |
p |
Makes channel private |
q |
Sets channel owner |
Q |
Only U:Lined servers can kick users |
R |
Requires a registered nickname to join |
S |
Strips all incoming colors |
s |
Makes channel secret |
t |
Only chanops can set topic |
u |
Auditorium Makes /names and /who #channel only show channel ops |
V |
/invite is not allowed |
v <nick> |
Gives a voice to users. (May speak in +M Channels |
z |
Only clients on a Secure (SSL) Connection may join |
User and Oper Commands
Command |
Description |
Who |
| nick <newnickname> | Changes your online nick name. Alerts others to the change of your nick |
All |
| whois <nick> | Displays information of user requested. Includes Full Name, Host, Channels
User is in, and Oper Status |
All |
| who <mask> | Who allows you to search for users. Masks
include: nickname, #channel, hostmask (*.attbi.com) |
All |
| whowas <nick> <maxreplys> | Displays information on a nick that has logged off. The <max replies>
field is optional, and limits how many records will be returned. |
All |
| ison <nick1 nick2 nick3 ...> | Allows you to check the online status of a user, or a list of users. Simple
return, best used for scripts |
All |
| join <channel1,channel2, ...> | Allows you to join channels. Using the /join #channel1, #channel2, channel3 will allow you to join more than one channel at a time. The /join 0 command makes you PART | All |
| part <channel1, channel2, ...> | Allows you to part (leave) channels. Using the /part #channel1, #channel2, channel3 will allow you to part more than one channel at a time. | All |
| motd <server> | Displays the servers motd. Adding a server name allows you to view motd’s
on other servers. |
All |
| rules <server> | Displays the ircd.rules of a server. Adding a server name allows you to view rules on other servers | All |
| lusers <server> | Displays current & max user loads, both global and local. Adding a server name allows you to view rules on other servers. |
All |
| map | Displays a network map | All |
| quit <reason> | Causes you to disconnect from the server. If you include a reason, it will be displayed on all channels as you quit | All |
| ping <user> | Sends a PING request to a user. Used for checking connection and lag.
Servers issue pings on a timed basis to determine if users are still connected. |
All |
| version <nick> | Sends a CTCP Version request to the user. If configured to do so, their
client will respond with the client version. |
All |
| links | Displays a list of all servers linked to the network | All |
| Admin <server> | Displays the admin info of a server. If a server name is included it will
display the info of that server. |
All |
| userhost <nick> | Displays the userhost of the nick given. Generally used for scripts |
All |
| topic <channel> <topic> | Topic <channel> will display the current topic of the given channel. Topic
<channel> <topic> will change the topic of the given channel. |
All |
| invite <nick> <channel> | Invites the given user to the given channel. (Must be a channel Op) |
ChanOp |
| kick <channel, channel> <user, user> <reason> | Kicks a user or users out of a channel, or channels. A reason may also
be supplied. |
ChanOp |
| away <reason> | Marks you as being away. A reason may also be supplied. |
All |
| Watch +-<nick> +-<nick> |
Watch is a new notify-type system in UnrealIRCd which is both faster and uses less network resources than any old-style notify system. The server will send you a message when any nickname in your watch list logs on or off. The watch list DOES NOT REMAIN BETWEEN SESSIONS - you (or your script or client) must add the nicknames to your watch list every time you connect to an IRC server. |
All |
| helpop ?<topic> or !<topic> |
HelpOp is a new system of getting IRC Server help. You type either /HELPOP ? <help system topic> or /HELPOP ! <question> The "?" in /HELPOP means query the help system and if you get no response you can choose '!' to send it to the Help Operators online Using neither ? nor ! will mean the command will be first queried within the help system and if no match if found , it will be forwarded to the help operators | All |
| list <search string> | Lists all channels on the network. If a search string is supplied, it will apply that to the search. Wildcards are supported | All |
| quote | If you don't include any options, the default is to send you the entire unfiltered list of channels. Below are the options you can use, and what channels LIST will return when you use them. <number> List channels with more than <number> people.
<number> List channels created between now and &<number> minutes ago. <number> List channels whose topics are newer than <number> minutes.
|
All |
| Knock <channel> <message> |
Allows you to ‘knock’ on an invite only channel and ask for access. Will not work if channel has one of the following modes set: +K +V. Will also not work if you are banned |
All |
| setname | Allows users to change their ‘Real Name’ without reconnecting |
All |
| vhost <login> <password> | Hides your host name by using a vhost provided by the server. |
All |
| mode <chan/nick> <mode> |
Lets you set channel and user modes. Refer to section 5 for lists of modes |
All |
| credits | Lists credits for everyone that has helped create UnrealIRCD |
All |
| license | Displays the GNU License | All |
| time <server> | Displays the servers date and time. Including a server name allows you
to check other servers. |
All |
| botmotd <server> |
Displays the servers bot message of the day. Including a server name allows you to check other servers | All |
| identify <password> | Sends your password to the services system to identify to your nick. |
All |
| identify <channel> <password> | Sends your password to the services system to identify as the founder
of a channel. |
All |
| oper <userid> <password> |
Command to give a user operator status if they match an Oper Block |
IRCop |
| wallop <message> | Sends a message to all users with umode +w | IRCop |
| globops <message> | Sends a message to all IRCops | IRCop |
| chatops <message> | Send a message to all IRCops with umode +c | IRCop |
| locops <message> | Sends a message to all local IRCops | IRCop |
| adchat <message> | Sends a message to all Admins | IRCop |
| nachat <message> | Sends a message to all Net Admins | IRCop |
| kill <nick> <reason> | Kills a user from the network | IRCop |
| kline +-<hostmask> <time to ban> <reason> | Bans the hostmask from the server it is issued on. It is not a global ban. Time to ban is in seconds, or you can use 1d for 1 days. If the hostmask is prefixed with a -, the kline is removed | IRCop |
| zline +-<ip> <time to ban> <reason> | Bans an IP Address from the local server it is issued on. Time to ban is in seconds, or you can use 1d for 1 days. If the ip is prefixed with a - then the zline is removed. |
IRCop |
| gline +-<user@host> <time to ban> :<reason> |
Adds a global ban to anyone that matches. Time to ban is in seconds, or
you can use 1d for 1 days. To remove a gline, put a –user@host |
IRCop |
| shun +-<user@host> <time to shun> :<reason> |
Prevents a user from executing ANY commands on the server, and prevents them from speaking. Time to shun is in seconds, or you can use 1d for 1 days. To remove a shun, put a –user@host. Setting time to 0 makes it permanent.
|
IRCop |
| gzline +-<ip> <time to ban> :<reason> |
Adds a global zline. Time to ban is in seconds, or you can use 1d for 1 days. To remove a gzline, put a –user@host. Setting time to 0 makes it permanent. |
IRCop |
| rehash <server> –<flags> | Rehashes the servers config file. Including a server name allows you to rehash a remote servers config file. Several flags are also available. They include -all - Rehashes all config files | IRCop |
| restart <server> <password> |
Restarts the IRCD Process. Password is required. You may also include
a server name to restart a remote server. |
IRCop |
| die <password> |
Terminates the IRCD Process. Password is required | IRCop |
| lag <server> |
This command is like a Sonar or Traceroute for IRC server. You type in /LAG irc.network.net and it will reply from every server it passes with time and so on. Useful for looking where lag is and optional TS future/past travels |
IRCop |
| sethost <newhost> | Lets you change your vhost to what ever you want it to be. |
IRCop |
| setident <newident> |
Lets you set your ident to what ever you want it to be |
IRCop |
| chghost <nick> <newhost> |
Lets you change the host name of a user currently on the system |
IRCop |
| chgident <nick> <newident> |
Lets you set your ident to what ever you want it to be |
IRCop |
| chgname <nick> <newname> |
Lets you change the realname of a user currently on the system |
IRCop |
| squit <sever> |
Disconnects a server from the network |
IRCop |
| connect <server> <port> <server> | If only one server is givin, it will attempt to connect the server you are ON to the given server. If 2 servers are given, it will attempt to connect the 2 servers together. Put the hub server as the first, and the leaf server as the second. |
IRCop |
| dccdeny <filemask> <reason> |
Adds a DCCDENY for that filemask. Preventing that file from being sent. |
IRCop |
| undccdeny <filemask> |
Removes a DCCDENY | IRCop |
| sajoin <nick> <channel>, <channel> |
Forces a user to join a channel(s). Available to services & network admins only | IRCop |
| sapart <nick> <channel>, <channel> |
Forces a user to part a channel(s). Available to services & network
admins only. |
IRCop |
| samode <channel> <mode> |
Allows Network & Services admins to change modes of a channel without
having ChanOps. |
IRCop |
| rping <servermask> |
Will calculate in milliseconds the lag between servers |
IRCop |
| trace <servermask> |
Will calculate in milliseconds the lag between servers |
IRCop |
| opermotd |
Displays the servers OperMotd File |
IRCop |
| addmotd :<text> |
Will add the given text to the end of the Motd |
IRCop |
| addomotd :<text> |
Will add the given text to the end of the OperMotd |
IRCop |
| sdesc <newdescription> |
Allows server admins to change the description line of their server without
restarting. |
IRCop |
| addline <text> |
Allows you to add lines to the unrealircd.conf |
IRCop |
| mkpasswd <password> |
Will encrypt a clear text password to add it to the unrealircd.conf |
IRCop |
| tsctl offset +/- <time> |
Adjust the IRCD’s Internal clock (Do NOT use if you do not understand
EXACTLY what it does) |
IRCop |
| tsctl time |
Will give a TS Report | IRCop |
| tsctl alltime | Will give a TS Report of ALL servers | IRCop |
| tsctl svstime <timestamp> |
Sets the TS time of all servers (Do NOT use if you do not understand EXACTLY
what it does) |
IRCop |
| htm <option> |
Controls settings related to high traffic mode. High Traffic Mode (HTM) basically disables certain user commands such as: list whois who etc in response to extremely high traffic on the server. Options include: -ON Forces server into HTM |
IRCop |
| stats <option> |
b - Send the badwords list C - Send the link block list |
Admin |
| module |
Lists all loaded modules | IRCop/All |
IRCd Info
As of November 2006 AfterX is using Unreal and we are currently running version Unreal3.2.5. You can find the full manual of the IRCd here and I strongly recommend you to at least look through it.
Server Staffing
Number of irc operators per server:
No AfterX server is allowed more than 6 operators. This limit includes server administrators, global operators and local operators. This limit does not include backup operators. Any server found with more than 6 operators will have two days, from the time the server administrator is notified, to comply with this amendment. After this time period expires, the server violating this amendment may be delinked after a vote of Net-com.
As a server admin, you are entirely responsible for all your opers and it's up to you to see that they are a responsible, mature and helpful opers, otherwise User-com/Net-com may ask you to reconsider your choice of opers on your server.
From time to time, you may like to add new opers or remove opers on your server. There is a limit of how many opers you may have on your server, a total of six IRCops, INCLUDING the server admin and co-admin if you have one, on any one AfterX Server.
You can add anyone you like as a local oper. But if you want to promote someone to a global oper you first have to train this person yourself, then notify Training-com who will test him/her and then they in return will notify Net-com who will give their comments. Upon approval from net-com you may promote the person in question to a global oper and change his/her local o:line to a global O:line. You do not have to inform net-com@afterx.net if you intend to add any local opers, however some server admins do, to keep Net-com up to date.
There is no limit of how long an oper can be in training, it may be days, weeks or months, as long he/she has been trained aquedately as deemed fit by Training-com before becomming Global oper.
You may add backup operators on your server, they will remain the responsibility of their admin. There is no current limit of how many backup operators you may have, but you are responsible for maintaining the backup list of opers on your own servers. In other words, if one of the backup opers on your O:lines list is no longer an oper on the original server, then you should remove him/her or he/she becomes your responsibilty, not the other admin's responsibility. It is important to note that the number of ordinary opers on your server is limited, so be warned you do not exceed this, should you decide to make the backup oper an oper on your server.
Guidelines
Introduction
We have endeavored to put together some guidelines for admins, opers and channels.
Server Administrators
Admins and co-admins are required to be on AfterX (not just idling) and in the channel #afterx a minimum of 10 hours per week. They are also encouraged to spend time actively in #afterx-help and #opers.
Admins are responsible for keeping all issues concerning the IRCd settings up-to-date.
Admins are responsible for the training of their IRCops. Any action taken by an IRCop is the responsibility of the admin.
Admins must follow all rules listed for IRCops. This does not change the 10 hour online requirement for Admins.
IRC Operators
From now on, you are recognised as a representative of AfterX, and your server, even if you are not on active duty, to coin a phrase "a policeman is always on duty". If you have a problem with this please speak to your admin.
IRCops are required to be helpful and attempt to answer any IRC related question asked of them.
IRCops are required to spend a minimum of 1 hour per week in #afterx-help.
IRCops are encouraged to spend time in #opers when they are online as this is a channel to set up where IRC operators and admins can discuss matters concerning the network on a daily basis.
Channel matters
Opers must not interfere with channels or get involved in channel matters,
this includes (but does not exclude other scenarios):
- Setting yourself mode +o or +v on a channel you have no access to
- Joining a channel and demanding a ban to be removed
- The use of /kill upon a channel operator who kicks or bans you from
a channel
However, there are exceptions to where you may need to assist a channel
which is in trouble
- if the founder requests your assistance in removing flooders or other
cause of problem.
- where the founder isn't present, but the majority of channel opers
agree on asking you for assistance
- if there are no active channel opers present and you see the problem
Once the problem is solved you must IMMEDIATELY deop yourself and send a memo or e-mail to the channel founder explaining the situation.
IRCops cannot nuke or otherwise harass users/admins/IRCops of AfterX or any other network they may be visiting at any time for any reason.
Use of kill
Use of /kill should be limited. Acceptable reasons include channel takeovers, constant akick/ban evasion, clone bots, advertising other networks, general nuisance or other similar infractions.
Acceptable reasons for akills include: D.O.S. (denial of service)attacks, akill evasion, damage to servers, major abuse of services, repeated mass advertising of other networks, or other similar infractions.
Training
All AfterX IRC operators must attend training prior to receiving a Global O:line.
Channels
Hate channels
Hate channels, defined as any channel which negatively targets a group of people based on race, religion or culture, are not permitted on AfterX. IRCops who take action regarding a hate channel must inform opers@afterx.net.
Slanderous and/or abusive channel topics or channel names
AfterX does not tolerate slanderous and/or abusive channel topics or channel names. This amendment gives AfterX IRC operators the authority to handle these situations immediately in the following manner:
1. For slanderous/abusive channel topics, the IRC operator will request the channel topic be changed, or the channel be set to mode +s so the topic does not show up in a channel list.
2. For slanderous/abusive channel names, the IRC operator will request that the channel be dropped if registered, or vacated if not registered.
3. If the IRC operator is not successful in 1 and/or 2, the IRC operator has the authority to drop and/or otherwise secure the channel.
4. If a user, after being warned, continues to make slanderous and/or abusive channel topics or channel names, the IRC operator has the authority to set an akill on that user.
If an IRC operator secures or drops a channel as mentioned above, he/she must immediately send an email, including logs and channel information, to opers@afterx.net, net-com@afterx.net and user-com@afterx.net. Either Net-com or User-com has the right to overrule the decision.
Any IRC operator found abusing this authority may be disciplined; up to and including removal of their O:line.
Complaints
Admin
Complaints against an admin should be directed to Net-com.
IRC Operators
Complaints against an operator should be directed to the operator's admin.
Users
Complaints against a user should be directed to User-com.
Channels
Complaints against a channel should be directed to Net-com.
AfterX Information
Introduction
Below is some information regarding AfterX and how it operates, including the various committees which keep AfterX organized.
Net-com
Net-com is represented by 1 admin and 1 co-admin/IRCop per server, giving each server equal representation in the core of the network. Only one vote per server is allowed, though it is recommended that servers with two members on net-com discuss each issue and come up with a joint decision.
Net-com shall promptly and effectivly resolve any issues/complaints sent to it.
Net-com is the core authority of this network.
Net-com Authority
Net-com may propose action without a complaint being filed. In effect, a Net-com member may file a complaint.
Net-com may request action to be taken against an IRCop by his/her admin. The action taken is up to the admin but must be satisfactory to a majority of Net-com. If the action is not satisfactory to a majority of Net-com, Net-com will provide options to the admin that are acceptable. The admin then has 3 days to exercise one of the options provided him or risk action against him and/or his server by Net-com.
Net-com has total authority over the network owned channels. This includes the official administrator/IRCop channel and help channel. Net-com has full authority to remove anyone from those channels for any length of time they feel is necessary, including a permanent ban from the channel.
Net-com may permanently delink any new server during that server's test-link period of two weeks. However, for this to be done at least 51% of the network committee shall approve of that action.
The Net-com committee shall handle complaints and questions about the Channel Service, the Nickname Service and any registered channel. The network committee is permitted to delegate additional IRCops to assist in handling questions and/or problems.
Limitations
When ever possible a network committee member shall attempt to solve any problem that arises without having to bring it before Net-com.
For minor violations, first time or infrequent offenses a warning should be considered rather than punitive action. The network committee is not bound by this, however it's strongly suggested.
Net-com may not make decisions contrary to the spirit of AfterX. At all times decisions must be made using the charter and any pertaining amendments. At no time may decisions be based on personal bias.
If a complaint is filed against a Net-com committee member, that member shall have no voting privileges on that complaint. Other Net-com members must place their friendships aside when handling this type of complaint. Only policy and the benefit of the network as a whole should be considered.
Server application
Net-com will review new link applications and make a decision within 7 days if the server in question should be allowed a test link. The test link should last for 2 weeks and then Net-com will vote on whether the server becomes a permanent link or not. A majority of Net-com needs to vote yes for the server to become a permanent link.
User-com
The makeup of this committee will be determined by a majority vote of User-com within the following rules:
1. Minimum of 7 members.
2. Total membership must be an odd number.
3. A majority of this committee must be users. Users being defined as anyone who is not a server admin, co-admin, or global IRC operator of AfterX.
4. At least 2 global IRCops or admins must be on this committee.
User-com is responsible for making suggestions/comments of the users known to the appropriate party. User complaints will be taken to the offending party first and, if not resolved, taken to the appropriate IRCop, admin, or committee with suggestion(s) as to an appropriate course of action.
Web-com
This committee will determine it's own makeup. Web-com is responsible for keeping the AfterX web site and forums current and accurate.
Training-com
The Net-com elected chairperson of this comittee will determine the makeup. Training-com is responsible for overseeing and managing the training of all opers and admins, and the for the upkeep of Net-com approved training materials, known as the "OperPak". In addition to carrying out any other training requests as directed by Net-com.
Dev-com
The Dev-com chairperson is a voluntary position, approved by Net-com and is reviewed on a regular basis. This person is responsible for keeping services and the ircd up to date, and continually improving it.
This is done by testing the new updates on testnet, for final bug checking, evaluation and importance of commands by anyone on testnet. Then, the Dev-com chairperson or any member of net-com may call an ARV in net-com to approve the changes to be made to AfterX. Any changes to AfterX software must be first done with an entire backup of the current databases and is distributable to the services hub admins, regardless of how small the changes are. Dev-com is an open committee, anyone can work with the coding and submit patches and new features, a more precise committee makeup may be decided by the chairperson if the proposed ideas are accepted by Net-com.
