Club Penguin Fanon Wiki:Consensus/IRC

''This is the official policy regarding Consensus on the IRC. For the IRC policy, please see IRC. For the policy regarding general Consensus, please go to Project:Consensus.''

''Note: This is written from TS' point of view. It will be written in third person and be edited to look 'professional'.''.

''This policy has been edited heavilly by Leader/Agent Johnson to conform more to conensus as it is known on the wiki. Not all of this reflects TurtleShroom's ideas and order, but it is nonetheless accepted.''

TurtleShroom, Chairman.

"22 Plans fail without good advice.


 * But they succeed when there are many advisers."

- Holy Bible, Proverbs 15:22

IRC Consensus is a Direct consensus RRO (meaning that everyone can take part and that it is governed by a RRO) that takes place on the IRC. It should be used when a dispute is important enough and needs to be settled by a large group of editors (minor issues can be settled on talk pages).

Part of the aftermath of the "Rightsquake" (as it was so aptly named) fell into the IRC. In a flash of brilliance, we managed to fall into line under the criteria of a business meeting. Thus came this idea, adopted and approved on November 30th, 2010.

If we want to get out of this mess alive, we're going to need to compromise ZK/John's Consensus with my Order. The compromise has begun with great vigor, and I've already stepped into the messy world of business meetings, research and all. You will need no experience with business meetings except the ability to speak in turn, listen to others, and follow instructions. This is an EXTREMELY formal but well-known means of conducting business, and over 95% of all organizations use this.

Robert Rule of Order
Robert's Rule of Order (RRO) is a lot like consensus and is also called "parliamentary procedure" (they are synonyms).

According to RRO doctrine, a strict order is followed. (It's already written, so it's not my say.)

Definitions

 * Member: anyone that is a member and can participate in the meeting. In IRC Committee, that's everyone and anyone on the IRC.


 * The Chair: It's not a talking piece of furniture. The Chair (the person is called the Chairman) is the one who presides over the meeting and keeps it in rigid order. His job is to remain silent (yes, that's right, I can't talk outside of my script) and moderate the meeting by repeating things, saying certain required things, and, if need be, command order. The Chair refers to himself as "the chair". In IRC Committee, I am the chair. That also means I have to remain silent.


 * Secretary: A person that reports the minutes, restates things, keeps records, ect. In IRC Committee, I am the secretary and the Chair and everything else to keep people from being confused.


 * Vice President: Second in command to the Chair, he does nothing at all unless the Chair relenquishes for debate.
 * Relenquish the chair: RRO is clear when it says that the chairman can NOT talk outside of his scripted law. Relenquishing the chair is when the chairman places the VP as Chair until he's done talking.
 * To relenquish the Chair, the chairman has to file a motion of relenquishing, and it has to be seconded (read below). This is good thing, because if no one seconds or someone objects, the Chair (me) has to remain silent!


 * AYE: synonym and formal version of "YES". RRO expects the use of "AYE" instead of "yes". You are expected to say "AYE" in formal votes. Varients like "Aye aye" and "Aye aye, captain" will be tolerated.  :)


 * NAY: synonym and formal version of "NO". RRO expects the use of "NAY", but permits "NO" as well, depending on the organization. Both "NAY" and "NO" are considered acceptable in IRC meetings.


 * Seconded/Second: another user agrees that the motion is important. All motions must have at least one second, or the idea is dropped due to insignificance.


 * The Burden: the responsibility of something, and to whom it falls. If the Burden is on the Chair, it's his responsibility or right to do it. If the Burden is on you, it's your responsibility or right to execute or perform the action, and so on.

Order of meeting

 * The minutes of the last are repeated. (In IRC, they're simply linked.)
 * Folks adopt the minutes (just say "AYE" when asked to do it, it's just procedure).


 * A "secretary" repeats what the Board/those on the Committee did last session that is important but not in the minutes.


 * The chairman of any existing committee summaraizes what their committee has done since last meeting. (Existing committees don't run on RRO, they run like you want them to run.)


 * Unfinished business since last meeting is brought up. ("Old business" is stuff that was begun prior and still going.)


 * New business is proposed.


 * The meeting is adjourned.

(I have personally sat through a RRO meeting, and it lasted less than fifteen minutes when nothing was proposed.)

Motions
When it's time for "new business", people in the meeting can perform motion. That is defined as "a formal proposal for action made [in a meeting] for discussion and vote".


 * A member (AKA anyone on the IRC) proposes a motion.
 * You just have to be the first to say it. The book says to word it like this: "I move that [specific statement of following action]."
 * Chair says "The chair acknowledges the gentleman (or lady)", and for IRC sake, since we're not able to see each other like RL, he'll follow it with "Mister (or Miss) [USERNAME]".
 * The chair responds with "Is there a second to the motion?"


 * Another member seconds it. Failure to second it stops the motion and moves on.


 * The chair repeats the motion, and it is "officially placed on the assembly". That means DEBATE/CONSENSUS TIME.


 * The motion is debated by consensus. (Bonus! The Chair can not debate unless he has someone else take his place while he debates, relenguishing the chair. That means silent TS !!!)
 * Only the Chair (me) has to be formal during this time. You are free to use down-to-earth language until you've decided amongst yourselves what the motion is. After a long pause, the chair will move the motion to a vote, or you can tell him you're ready.
 * When you're ready, ask the Chair for a motion to close debate ("I move to close debate on this motion."). Get a guy to second it, and off to vote.


 * The chair restates the motion and the measure is voted on. The chair repeats who won and the motion is adopted or defeated.


 * The chair moves the meeting to next business, if any.

That's it.

Post-meeting procedure
After the meeting, the minutes will be posted on the forums. Any motions adopted in the meeting will be posted here for the community to vote on. Votes will last for 3 days, and the plurality wins.

Rough Consensus
See Also: Rough consensus

Rough consensus is where an agreement can't be reach. This is where someone requests for a rough consensus. This is when the supermajority wins the argument. Unanimity is hard to reach so this is used as an alternative. To request it, anyone must make a "motion for rough consensus" to the Chair and have it seconded. It is then the Chair's discretion if rough consensus has been achieved. It is generally accepted that anything over 70% (two-thirds) or that number is a rough consensus. Remember, 51% doesn't qualify as rough consensus and 99% is always better.

No Consensus
''See Also: No consensus

In any discussion on IRC Consensus, there are two possible outcomes: consensus, for some course of action, and no consensus. When there is no consensus on the proposal, the current status quo prevails. In the event where no consensus is achieved, it becomes the responsibility of the dissenting editor(s) to modify the original proposal if they wish to. However, it is also possible for the proponents to come up with an alternative proposal which addresses the concerns raised by the dissenters.

It is important to note that a few vocal dissenters do not create "no consensus".

Closure
''See Also: Consensus closure A Consensus discussion is to be closed when:


 * The topic has unanimous or near unanimous support or opposes and discussion has ran for at least three/four meetings.
 * The topic's arguments have been refuted and there is general consensus on which is the better and more accepted option.
 * The topic has been open for a long period of time and the discussion has reached a standstill with no sign of consensus forming. The topic should be closed, on a basis of no consensus.
 * The topic is meant to be in another area of the wiki, such as the forums.

Anyone can request closure and it's the Chair's discretion to close it. If you disagree or feel uncomfortable with a proposal or its alleged repercussions, the Burden is on you to say so.

It is impractical to wait forever for affirmation: in the meantime, it is best to assume that silence implies consensus. Users can continue to hold that assumption (hopefully safely) until someone comes along and voices their concerns. The more visible the statement, and the longer it stands unchallenged, the stronger the implication of consensus is.

To close a consensus, one must file a motion to close debate and move to vote. When you're ready, ask the Chair for a motion to close debate ("I move to close debate on this motion."). Get a guy to second it.

Rules of etiquette
The book says:


 * 1) "Do not get off topic."
 * 2) It also says that the Chair is charged with keeping all on topic.
 * 3) "Refrain from attacking a member's motives."
 * 4) "The chair is expected to control the meeting."
 * 5) "The Chair is not to use other member's [user]names."
 * 6) In this case, I'll make an exception because that's all we have.
 * 7) "When finished with an issue, let it go, so the meeting can move to other business."
 * 8) It can be brought up again in the next Meeting or informally anytime by normal means.
 * 9) "Refrain from disturning the meeting."

Positions

 * The Chair: TurtleShroom. (You are to call me Chairman TurtleShroom, or some other snappy name.)
 * Secretary: TurtleShroom.
 * Vice President: Andrew, John, or someone willing to read a quick link on RRO.


 * Members that can act and vote, ect.
 * Everyone

Unanimous Consent
Sometimes, something is so obviousor so routine that it's a waste of time to second it. Reading the minutes, for example, or linking to something in debate. In this case, Silence Implies Consent. In UC cases, the mere silence will have the Chair say "without objection", so ordered.

"Sometimes, Unanimous Consent can be assumed if the chair perceives that no one would raise an objection if he formally asked. For instance, if it is obvious that the members of an assembly are absorbed in listening to a speaker who has exceeded the time limits on debate, but is about to conclude his remarks, the chair may allow him to continue without interruption."

- Wikipedia

Duties
TurtleShroom is vested with maintaining all formality, order, rules, and leading the meeting, as well as keeping silent. You don't have to worry about formaility. You just come, discuss and vote.

What to say for things
As said before, you have no formal duties at all. Come, discuss, vote.

However, as this is RRO and not your mom's kitchen, there ARE certain words and phrases to initate things. No way around it.

Unlike TurtleShroom, your duties are easy and barely relevant. Robert's Rules of Order were designed for Noobs to get.

REMEMBER THAT TURTLESHROOM WILL HANDLE ALL FORMALITIES.

Voting and motions (the stuff you need to know to properly participate in RRO)
The easiest way is to just copy and paste this. A table has been provided for that very reason!

Advanced (placed here because All Members are Equal and can use all powers given to them in RRO if needed)
Most people will never need this, but in the interest of fairness and because All Members are Equal, here are all of the powers at your disposal as a voter.

External links (for TS only)

 * The COMPLETE IDIOT's Guide to Robert's Rules of Order
 * Nancy Sylverster's RRO site for total morons
 * The ORDER of procession in RRO meetings
 * Chairman's script (do not deviate)
 * TurtleShroom's opinion and response to calls for orderless consensus
 * All means of Parliamentary Procedure known to man

Thank you.

-- † TurtleShroom™! Jesus Loves You and Died for You!! †    :)  :)  Dubya dubya dubya dot...       †          †       As I always say...    ――–    ―――――      02:33, 1 December 2010 (UTC)