The Sims Wiki:Requests for IRC Channel operator

IRC Channel operator requests are almost always open on.

Minimum requirements
If you feel that you are a valuable member of the IRC channel and you think you would benefit from channel operator flags, this is where to apply. The minimum requirements are:
 * An account on irc.freenode.net
 * Fair knowledge of operating an IRC channel.
 * Being highly active in the channel
 * Applying for this should not be the first thing you do after joining IRC for the first time.


 * Understandable, (almost 100%) correct English all the time.
 * If u talk liek dis, ur not rdy 2 bcome chanop.


 * A record of civil behavior
 * If you're constantly being told not to mess around then you're not ready for this.


 * Prerequisites — before you can become an Op, you must already be a HalfOp. Before you can become a SuperOp, you must already be an Op.

Please be sure you read The Sims Wiki:IRC Channel Operators in order to understand the different tiers of channel operators on The Sims Wiki before applying.

Stage 1: Nominating

 * Users may nominate themselves or other users for IRC operator rights.
 * Multiple requests at one time are allowed.
 * Operator candidates that are not given any additional privileges are ineligible to be nominated or to nominate themselves for at least a month.

Stage 2: Discussion

 * A period of discussion shall last at least five days.
 * If a request will clearly not achieve a favorable consensus (i.e. there is absolutely no support for promotion) - in other words, the request doesn't have a "snowball's chance" of passage - it may be closed early.


 * After five days of discussion, it shall be determined whether a consensus is in favor of a user being given operator rights. If there is a consensus, rights will be awarded. If there is clearly no consensus for a user to be promoted, the discussion is ended and rights will not be awarded.
 * In cases where consensus is not clear after five days, discussion will continue for three additional days.
 * If, after this time, there is no clear consensus for promotion, the nomination will end and the nominee will not be promoted. This will occur even if a consensus against promotion does not exist.

Note
Administrators, bureaucrats, and other channel operators may moderate discussions and votes and determine consensus, but only SuperOps may award rights to successful nominees. Administrators, bureaucrats, and channel operators may participate in discussions and vote, but must be impartial when moderating, determining consensus, and awarding rights.

Guidelines for discussion and consensus

 * All registered users may participate in a nomination for IRC channel operator; however, more weight will be given to arguments made by users who frequent the IRC channel.
 * Points of discussion should be focused on assessing the ability of a nominee to perform their duties. Discussion should avoid sweeping praise or generalizations (e.g. "he/she is a good editor" or "he/she deserves it"), and focus instead on specific reasons why a user is or is not a good fit for the position.
 * Users engaged in discussion may contradict the points raised by another user, but should remain respectful at all times. Back-and-forth arguments between two users should be avoided.
 * Generally, consensus in a request can be determined by answering these questions:
 * Are there major and specific problems raised by multiple users regarding the nominee?
 * Is there a lack of agreement between users over whether a nominee is qualified, capable of serving or a good fit for the role?
 * If the answer to these questions is 'no', there likely exists a consensus for the nomination.

Ben/MrC/MrBenC
So, I was recently promoted to Op not even two weeks ago. Ordinarily I wouldn't attempt to move up yet again this quickly. However, the circumstances justify this. As of this writing, there are only two SuperOps, one who is marked inactive and the other marked as semi-active. The potential candidate list is very short, and any other potential candidates would have to go through the Op nomination process first.

Not sure if there's really much more that needs to be said, that I didn't say in my original Op nomination request. Ben (talk) 04:29, July 3, 2016 (UTC)

Ben/MrC/MrBenC
So, guess I'll start this off. The differences are small, since if this request is successful, I'd just gain the ability to change the topic. Back when I used to run the channel statistics web page, this would have been useful if I had to move it from one server to another, so a different URL. However, this is for a different reason. Since the new rules have been implemented, it has been proposed as part of the reform process that some users have their flags removed, due to limited IRC knowledge. One of these users occupy the SuperOp (formerly Bureaucrat) tier, while another who formerly had that tier has resigned from that role. While time will tell, if this entire proposal goes through, it would mean the only people with SuperOp abilities will be the contact, and one user who hasn't been very active lately.

Under the new rules, this is a prerequisite to SuperOp and no provision exists to leap-frog or skip tiers. In the event those users listed in the proposal are dropped, I want to be in a position to apply for SuperOp later on.

Hopefully, my record, knowledge, experience, and reputation speak for themselves. Ben (talk) 01:43, June 18, 2016 (UTC)


 * Knowing Ben from other IRC networks, he is clearly competent with using IRC and definitely a trusted channel member. This system is still fairly new so there are definitely kinks that will be worked out over time, but I have no doubt that Ben's expertise will benefit the channel. — k6ka  🍁 ( Talk ·  Contributions ) 01:47, June 18, 2016 (UTC)


 * Ben is very skilled in IRC and is very active in the channel. I have no hesitation whatsoever to giving him more powers in the channel --  LiR talk • blog  •  contribs 16:35, June 18, 2016 (UTC)

Well there is clear support for the promotion, so ✅ Flags added. — k6ka  🍁 ( Talk ·  Contributions ) 19:40, June 23, 2016 (UTC)