Mission, Roles and Behavior code (By-laws)

“Let’s Do This!” – Leroy Jenkins

MISSION STATEMENT: It is the core mission of <Enduring Dawn> to create a positive, supportive gaming environment for Reasonable Adults.

This By-Laws Document is going to cover This Stuff:

  • List of Documents – The Charter is The Document. It’s like … okay, the Charter is the One Ring to Rule Them All, but we also gave some rings to the Elves, yeah? This By-Laws document is one document of several that makes up The Specific <Enduring Dawn> Rules.
  • Leadership Positions – A definition of what the leadership postions are, what their responsibilities are, what their authority is, and other stuff like that. This part is a Must Read if you are considering taking on a leadership position, because it’s going to tell you what your job is if you take on that position.
  • Membership – This section goes over the Behavior Code and stuff like that.
  • Policies and Procedures – This is the nitty-gritty stuff, like how we handle Behavior Code violations, and how we do other stuff that’s not outlined in The Charter. This part, more than anything, is The Rule Book. This section is broken out into three sub-sections.
    -Corrective Action for Behavior Code Violations
    -Altering/Amending the Charter
    -Altering/Amending Non-Charter Documents
    -Performance Review Policies

SECTION THE FIRST: LIST OF DOCUMENTS

“So much paperwork to read! So much paperwork to push away! So much paperwork to pretend he hadn’t received and that might have been eaten by gargoyles.” – Terry Pratchett, Snuff

  • Charter: The Charter is HERE. It is THE Document. There are other documents (listed below) and those are important, too, but they’re simpler to change than the Charter is, so they’re in their own documents. Also, the Charter is really, really long, so breaking this stuff out into separate documents makes peoples eyes bleed less. But this is important: anytime the Charter and these other documents overlap or conflict, the Charter Wins.
  • By-Laws: You’re reading that now. Grats on finding it!
  • Rank Requirements: This document outlines what the ranks are and how to achieve them, and other rank-related information, like what qualifies as a Guild Event, etc. blah-blah. This is considered a guild-wide document and follows the guild-wide document amendment/alteration policies and procedures.
  • RP Guidelines: Yup … it’s guidelines … for RP. This is a guild-wide document and follows the guild-wide document amendment/alteration polices and procedures.
  • Section Documents: That’s the uniform code and Honor Groups for each Section. These are section-specific documents and follow the section-secific document amendment/alteration policies and procedures.
  • Officer Policies and Procedures: This is the “how to be an Officer” stuff. It’s published on the Officer Boards, so no, it’s not missing if you’re not an officer and you don’t see it. This is a guild-wide document and follows the guild-wide document amendment/alteration policies and procedures. Performance Review Forms are included in the Officer Policies And Procedures.

SECTION THE SECOND: LEADERSHIP POSITIONS

“If we could just find out who’s in charge, we could kill him.” – George Carlin

This section covers Definitions, Responsibilities, Areas of Authority, Requirements, Restrictions and Term Length. The mechanism by which any person in a leadership position can be removed from office is also described in the Policies and Procedures section of the By-Laws.

I. Community Coordinator

  • Definition:
    The Community Coordinator is the in-game guild owner of <Enduring Dawn> and any associated future community guild(s). This is a hybrid position composed of both administrative work and in-game responsibilities.
  • Responsibilities:
    Coordinating community-wide efforts, being a positive and fun member, maintenance and alteration of the in-game guild(s) including approved changes to in-game rank and ship unlocks, /gkicking people who need /gkicking, invading chosen planet for conquest every Tuesday morning, scheduling and chairing periodic Section Lead meetings for status updates and discussion of on-going guild business, bugging people about their deadlines, and generally keeping this train a’rollin’. Does not have formal event-running responsibilities, but frequent availability to be online and in TS is a big plus for this position, and the Community Coordinator should run events geared towards creative (fun) fundraising, ship/stronghold unlocks and cross-section/cross-faction as available.
  • Areas of Authority:
    The Community Coordinator has the authority to call meetings, assign tasks to Section Leads regarding on-going guild business, delegate any tasks that don’t require in-game guild owner permissions, and set deadlines. In the event an assigned or delegated task is not completed by the deadline, the Community Coordinator is empowered to reassign the task and record non-completion on official Performance Review (See: Policies and Procedures)
  • Requirements:
    Only members who have served a term as a Section Lead are eligible to serve as Community Coordinator.
  • Restrictions:
    The Community Coordinator is prohibited from also being the Website Owner or the TeamSpeak Owner. The Community Coordinator may not serve two consecutive terms unless there are no applicants who meet the requirement.
  • Term Length:
    There are two 6-month terms for Community Coordinator, October 1st – March 31st and April 1st – September 30th.

III. Section Leads

  • Definition:
    There are four “Sections” to <Enduring Dawn> and any associated future guilds broken down by class/RP. In <Enduring Dawn> these sections are Troopers, Smuggler, Knights and Consulars. The Section Lead is the primary leadership officer of each section. This is an administrative position.
  • Responsibilities:
    Section Leads are responsible for processing rank-up applications and updating website tags, in-game rank, and in-game member notes. Section Leads are also responsible for processing the Honor Group applications for their section and distributing rewards. Section Leads make up the bulk of the Leadership Council and are expected to be active and engaged on the Officer Board of the forums where the majority of guild-wide business will be discussed, and are responsible for writing formal proposals and chairing committees as assigned by the Community Coordinator and voting on formal proposals via forum in a timely manner. Finally, Section Leads are responsible for maintenance and administration of all concerns regarding their section, including but not limited to uniform code and Honor Group.
  • Areas of Authority:
    Section Leads are mini-Community-Coordinators when it comes to their Section. They can assign tasks to Section Officers regarding on-going section business, delegate tasks, and set deadlines. In the event an assigned or delegated task is not completed by the deadline, the Section Lead is empowered to reassign the task and record non-completion on official Performance Review (See: Policies and Procedures)
  • Requirements:
    Beginning May 1st 2016, only members who have earned Steward Rank are eligible to be Section Leads. These By-Laws are pre-approved to be edited to reflect this change on May 1st 2016. The current requirement will be Marshal Rank or higher because earning Steward Rank is not possible until there have been two full leadership terms.
  • Restrictions:
    A Section Lead may not serve as a Section Officer in another Section.
  • Term Length:
    Section Leads serve 4-month terms beginning January 1st, 2016. Terms are January 1st – April 30th, May 1st – August 31st, September 1st – December 31st.

IV. Section Officers

  • Definition:
    A Section Officer is a guild officer assigned to a section whose primary responsibility is defined by their officer “type”. Section Officers serve under Section Leaders, and neither outrank nor are outranked-by Community Officers. While this position may have some administrative tasks, it is primarily an in-game event-running position rather than an administrative position.
  • Responsibilities:
    All Section Officers are voting officers for any formal proposals regarding their section, including but not limited to alterations of the uniform code and Honor Group.
    -PvP Officer Responsibilities: There will be no more than four PvP Officers, one for each section, and they are responsible for coordinating with each other to have an Official Weekly Event for max-level PvP Premades, spreading the duty around so each officer runs the event once or twice per month. PvP Officers may also, as per their interest, schedule and run lowbie, midbie, and/or ranked PvP events.
    -PvE Officer Responsibilities: There will be no more than four PvE Officers, one for each section, and they are responsible for coordinating with each other to have an Official Weekly Event for an Open Raid Team, spreading the duty around so each officer runs the event once or twice per month. PvE Officers may also, per their interest, schedule and run flashpoints, zergs, commander runs, etc.
    -Rover: This is a “Discretionary Officer” position which will be filled or not filled per interest and requirement at the discretion of the Section Lead. One example as to why a Section Lead might want to fill this seat is selecting a single officer who is specifically delegated Honor Group tasks, like administrating the group, distributing awards, and hosting events that help our members achieve their honor group qualifications. This officer would also serve as a “back up” for the other two officer positions and is available to be assigned/delegated administrative tasks per Section Lead requirements.
  • Areas of Authority:
    Section Officers are empowered to schedule and run events, as well as post and oversee events for members ranking up per rank-up requirements. They are voting members for all matters specifically pertaining to their Section.
  • Requirements:
    Marshal Rank is required. Section Leads may, at their discretion, open applications to Warden Rank members in the event there are no Marshal Rank members applying. If there are also no Warden Rank members, the seat will not be filled.
  • Term Length:
    Section Officers serve 4-month terms beginning January 1st, 2016. Terms are January 1st – April 30th, May 1st – August 31st, September 1st – December 31st.

V. Community Officers

  • Definition:
    A Community Officer is a guild officer not assigned to a section whose primary responsibility is defined by their officer “type”. Community Officers serve under the Community Coordinator, and neither outrank nor are outranked-by Section Officers. While this position may have some administrative tasks, it is primarily an in-game event-running position rather than an administrative position.
  • Responsibilities:
    Community Officers are not voting officers in any Section or guild-wide, and their sole responsibility is defined by their “type”.
    -RP Officer Responsibilities: The RP Officer is the Keeper of Guild Canon and is responsible for keeping and maintaining on-going Guild Continuity (See: RP Guidelines Document). The RP Officer may, at their discretion, hand-pick members to participate in a “Writer’s Room” to delegate generating on-going write-ups of Canon RP. The “Writer’s Room” may also work closely with the Web Owner to assist in generating website content when a member of the “Writer’s Room” is willing to accept the delegation of the task. Members of the “Writer’s Room” are not official leadership, and serving in the “Writer’s Room” does not confer completion of a leadership term in regards to Steward rank, but “Writer’s Room” experience should be taken into account during the selection process for officers (See: Policies and Procedures). The RP officer serves under the Community Coordinator in regards to tying on-going guild continuity to Conquest Objectives and community-wide initiatives, but will be given deadlines by the Web Owner for weekly submissions to communicate those objectives via website. When deadlines are not met or there is no RP Officer, the Web Owner assumes these duties.
    -GSF Officer: The GSF Officer is responsible for running periodic GSF premades and administrating/maintaining the GSF Honor Group. The four Section Leads are the voting officers for any proposed changes to the GSF Honor Group.
    -Assistant Coordinator: The Community Coordinator may, at their discretion, select an Assistant Coordinator to assist in the Communitor Coordinator duties as per powers of the Community Coordinator outlined in The Charter.
  • Areas of Authority:
    The RP Officer is the final authority of all matters related to Guild Continuity, but needs to keep in mind they can be removed from office per Charter if this authority causes severe cray-cray and they start being a megalomaniacal dickhead. The GSF Officer has no additional authority beyond scheduling events and administrating the GSF Honor Group. The Assistant Coordinator has no authority beyond completing assigned tasks from the Community Coordinator.
  • Requirements:
    Marshal Rank is required. Section Leads may, at their discretion, open applications to Warden Rank members in the event there are no Marshal Rank members applying. If there are also no Warden Rank members, the seat will not be filled.
  • Term Length:
    Community Officers serve 4-month terms beginning January 1st, 2016. Terms are January 1st – April 30th, May 1st – August 31st, September 1st – December 31st.

SECTION THE THIRD: TERMS OF MEMBERSHIP

“Careful now … Would you kindly lower that weapon for a moment?” – Atlas, Bioshock

I. Eligibility

Anyone over the age of 18 may join <Enduring Dawn> or other affiliated guild(s). Members who are parents may secure a guild invite for their kids, though the kids may not be on TS without their gamer-parent. All individual toons (not players) join at “Survivor” rank and have a period of 30 days to rank-up to “Citizen” rank or the toon will be removed from the guild. “Survivor” is a placeholder rank and should only include toons that meet the following conditions 1) New Players 2) Players on Probation 3) Alts of Existing Players Who Are Still Within Their 30 Days to Rank-Up Period.

II. Behavior Code

By joining Enduring Dawn, members agree to not troll, grief, harrass or use slurs of any kind. This is not limited to intra-guild communication, but also all platforms upon which the guild communicates, included (but not limited to) all in-game chat channels, Enjin website, TeamSpeak. This includes behaving badly towards members of other guilds/communities or any individual in-game, on Enjin, or in TeamSpeak. For example, if we are sent a screenshot of any of our members exhibiting behavior we prohibit in any player-made custom chat channel like /gsf, they will be banned, even though that is not our chat channel. This also applies to the game-owned channels, like General and PvP.

Prohibited Behaviors Include But Are Not Limited To:

  • Trolling: Purposefully and willfully behaving in such a way as to disrupt other people’s playtime with the intent to be disruptive, including but not limited to “baiting” people with inflammatory statements in various chats, and “crashing” RP events and being obnoxious by streaking or dancing, “crashing” any guild event and purposefully being disruptive, etc.
  • Harassment: A pattern of on-going targeted comments meant to intimidate, bother, annoy, vent anger, and/or otherwise be unpleasant
  • Skeeziness: Specifically, Sexual Harassment. Also totally not allowed.
  • Raging: A one-time incident that would be considered harassment if it became an on-going pattern, usually involving very loudly and unpleasantly expressing anger.
  • Griefing: Killing the same poor guy (or gal) over and over again in Open World PvP. It is not considered Griefing if the same person attacks you over and over and you successfully defend yourself each time, but if you’ve killed the same guy (or gal) once or twice, don’t start the fight.
  • Ninja’ing: That totally dick move where you go in and take a chest or an open-world multi-person quest objective while someone else is fighting the mobs in front of it.
  • Guild Wars: No, we don’t mean the MMO – we mean smack-talking other guilds. We don’t want drama IN our guild, and we don’t want drama with OTHER guilds, either. We get that our members might have ended up in <Enduring Dawn> because something about their old guild made them unhappy or angry or something, but we don’t want any gossip/complaints/airing-of-grievances about other guilds or their leadership here.

We expect all of our members to abide by Wheaton’s Law which states “Don’t Be A Dick”. People who enjoy MMO’s because of the wide array of opportunities to mess with other people and ruin their good time are not a good fit for <Enduring Dawn> and should consider finding one of those guilds where this kind of behavior is acceptable – it’s totally not acceptable here.

III. Violation of Behavior Code

In the event of a violation of this behavior code, the Section Leads, Community Coordinator, and Web Admin will be tasked with reviewing and weighing the severity of the offense and issuing appropriate corrective action ranging from verbal warning to ban. In the event the offender is a member of Leadership, they will not be included in the process for determining fault and punishment. Further details in Policies and Procedures.

SECTION THE FOURTH: POLICIES AND PROCEDURES

“Ah! Yeah. It’s just we’re putting new coversheets on all the TPS reports before they go out now. So if you could go ahead and try to remember to do that from now on, that’d be great. All right!” -Office Space

Corrective Action for Behavior Code Violations

  • All Behavior Code Violations will be reviewed by Leadership Council.
  • If documented behavior is found to be a Behavior Code Violation, the offending party will receive a private verbal warning; however, the verbal warning will be documented on the Officer Board for tracking.
  • In the event of a second behavior code violation after a verbal warning, the second violation will result in a temporary removal of guild rank for the offending party. The offending party will be required to re-take the Welcome Class before guild rank will be restored, and this must occur within 30 days or the offending party will be banned. Rank suspension will also be documented on the Officer Board.
  • In the event of a third behavior code violation after temporary suspension of guild rank, the offending party will be banned.
  • If the first behavior code violation is considered trolling as defined in the behavior code, this will earn an insta-ban. Really extreme, really douche-y behavior of other kinds, like harassment or use of offensive slurs may also result in an insta-ban at the discretion of Leadership Council.
  • If a sitting officer is found to have committed a second behavior code violation earning a temporary removal of guild rank, they will be immediately removed from their officer position and their position will be filled per the mid-term replacement procedures.
  • After 90 days from the date of documentation on the officer board with no new behavior code violations, the “demerit” is removed. For example, if someone is issued a verbal warning, corrects the behavior and has no further violations after 90 days, that first violation doesn’t count anymore. A new violation of behavior code would then result in a step-one verbal warning instead of a step-two temporary removal of guild rank.

Altering/Amending the Charter

  • The process for Altering/Amending the Charter is outlined in The Charter. No changes to other documents may be proposed or passed that contradict the Charter without first amending/altering the Charter.

Altering/Amending Non-Charter (guild-wide) Documents

  • Any proposed changes to guild-wide documents (not including the Charter) will be passed with a simple majority vote of Leadership Council.
  • Any proposed changes to section-specific documents will be passed with a simple majority vote of Section Officers, including Section Lead. In the event of a tie, the proposed change does not pass.
  • Changes to Honor Groups, specifically, will be presented to all current Leadership Council for the possibility of veto. Leadership Council may veto a proposed change to Honor Group Requirements or awards with a 3/5ths majority.
  • Any changes to the Officer Policies and Procedures Document may be vetoed by the Web Owner. The Web Owner is responsible for data collection and approval scripts, and the majority of the policies and procedures outlined in this document exist to create data standards to support the Web Owner in this effort. Because changes to this document directly affects the Web Owner’s data duties, the Web Owner has veto power over alterations.

Performance Review Policies

  • One month into each term, every reviewer must supply a “How It’s Going So Far” preliminary performance review to each reviewee. This should specifically identify any areas of concern that, if unaddressed, would result in a bad performance review at end-of-term, giving the officer the information they need in a timely manner to improve their performance before the final review.
  • Final review should be submitted and recorded one week prior to end-of-term.
  • Exact format and categories for Performance Review are in the Officer Policies and Procedures document.

“We are so glad you came. Bye-bye. Bye-bye. Bye-bye. Bye-bye now. Bye. Bye-bye. Remember, please discard all candy wrappers and popcorn containers in the nearest trash receptacle. Thank you. Okay, bye-bye now. Bye-bye. Bye. Okay. Are they all gone? Is every — is everybody gone? Huh? Good. Oh, my gosh, my cheeks are killing me. I can’t keep smiling like this anymore. I am exhausted. I think I need a break. A little break?” -Tour Guide Barbie, Toy Story 2