Home » By-Laws

By-Laws

Last Updated: 21 April 2021

Navigation


By-Law #1 – Divisions

The 22nd Fleet shall operate with the following Divisions:

  1. A division operating in the Firefly universe;
  2. A division operating in the Star Trek universe;
  3. A division operating in the Star Wars universe; and
  4. A division, called “Miscellaneous,” which contains all sims not connected to any other division.

By-Law #2 – Membership Duties

Members

  1. Unless permitted by the Game Manager, all players have the responsibility to create original characters that are:
    1. Not established characters or relatives thereof in their own setting’s canon;
    2. Not in relation or familiar of other characters on the sim; and
    3. Not an already created character in any of the 22nd Fleet without the permission and consent of the character’s original creator.
  2. All players shall refrain from the unsolicited recruitment of and to any sim outside of the Fleet.
  3. All players who wish to resign must do so by informing the Game Manager of the sim(s) the player participates in. This resignation must be handled in a private forum between the player and the Game Manager.
  4. All players will try to resolve disputes with other players and the Game Manager in a respectful manner before proceeding to the Grievance process outlined in the Charter.

Game Managers

  1. Game Managers shall have the duty to determine the minimum post quantity and quality for their players on their sims, as long as they are within the Fleet activity thresholds established in these by-laws.
  2. Game Managers will be responsible to design, maintain, and operate the website for their sim.
  3. Game Managers shall have the sole responsibility to recruit members for their sim.
  4. Game Managers are free to resign their command to their Division Head, and then rescind that resignation within 48 hours without penalty.
  5. Game Managers will regularly maintain and update their sim’s page on the Fleet’s website.
  6. Game Managers will submit a report to the Fleet at the end of every quarter that outlines the stories written on their game and other activity of note during the quarter.

Officers

  1. Officers shall be held accountable to the GM Council by way of publicly posted reports. These shall be filed within the 10th to 15th days of the first month of each quarter. 
  2. All reports shall contain the following, where applicable:
    1. New and departing Sims
    2. A summary of the stories created on Member Sims
    3. An overview of the prior quarter’s happenings
    4. Plans for the current quarter’s operations
  3. The Chairperson & Vice-Chairperson’s report shall also include, in addition to the above:
    1. A record of all major Officer activity
    2. GM Council and Officer voting records and decisions
  4. The Chairperson shall also maintain a public docket, where all matters under Officer and Council attention shall be listed.

By-Law #3 – Canon

  1. Game Managers are free to determine what is or what will not be canon for their simulation(s) and/or game(s).
  2. Members and Game Managers from multiple simulations may work together to create shared canon amongst each other.
    1. Any such developments will remain unique to those player(s) and/or simulation(s) and may not be reused without proper permission and accreditation.
    2. Should a sim wish to withdraw from the shared canon group, it will not need to forfeit any shared canon developments. It may continue moving forward as long as it maintains the proper accreditation.

By-Law #4 – Sim Activity Thresholds

Simulations in the 22nd Fleet shall be assigned one of three activity designations, which shall be utilized at the discretion of the appropriate Division Head. The Division Head can make exceptions to these statuses as needed to accommodate different sim writing styles.

Active Status

To be granted active status a sim/GM will:

  1. Publish at least 2 posts per month (at least 500 words each); and
  2. Have four active players; and
  3. Create and maintain a website; and
  4. Maintain the sims page on the fleet website; and
  5. Submit a quarterly report before the 5th of the first month of each quarter.

Provisional Status

To be granted provisional status a sim/GM will:

  1. Be newly established in the 22nd Fleet; or
  2. Produce less than 2 posts per month; or
  3. Have less than four active players; or
  4. Fail to maintain the sims page on the fleet website; and/or
  5. Fail to submit a quarterly report.

Inactive Status

To be granted inactive status a sim/GM will:

  1. Not publish any posts in a two month period; or
  2. Be in provisional status for two consecutive quarters; or
  3. Fail to submit a quarterly report for two consecutive quarters; and/or
  4. Fail to respond to communications from their Division Head within a seven-day period.

While a sim is in “inactive” status, the GM will be considered to be “inactive” as well. The GM may still participate in Council discussions, proposals, votes, and other business; and retain all rights and privileges; but the number of votes required for quorum will automatically be reduced by 1 per inactive GM.

By-Law #5 – CO Removal and Sim Closure

Division Heads have the authority to remove a simulation game manager and/or close a simulation under the following set of conditions:

  1. A GM resigns;
  2. Fails to adhere to core values of the fleet as identified in the fleet’s Charter and By-Laws;
  3. A simulation is classed as inactive according to By-Law #4;
  4. A minimum one-month period has elapsed since inactive status was assigned;
  5. A Division Head has activated a seven day notice of closure; and
  6. The Division Head has granted an additional seven day period for the commanding officer to reach out and discuss the situation

By-Law #6 – Sim Ratings

  1. All 22nd Fleet simulations must have a rating image clearly displayed on their site’s main page.
  2. Ratings should be created at http://rpgrating.com/
  3. Game Managers in the 22nd Fleet are free to assign a rating of their choice, upto and including a 333 rating.

Any simulation with a 333 rating must:

  1. Not accept any player below the age of 18;
  2. Restrict all visible post content from public view

The 22nd Fleet does not endorse the use or discussion of graphic sexual or violent content. Due to the nature of the content, any simulation wishing to portray either shall be required to hold a 333 rating, have restricted from public access to anyone not a member of the simulation, and only people who have been verified to be aged 18 or older shall be permitted to join said simulations. Any simulation found to be in violation of these provisions, shall be subject to termination by the GM Council.

By-Law #7 – Requirements for new and additional games

A player seeking to open a new game in the 22nd Fleet must:

  1. Have four months verifiable experience in the 22nd fleet or six months in another fleet; and
  2. Must be a Member in good standing.

Existing Game Managers who wish to start an additional simulation must:

  1. Have at least three consecutive months of active status with their most recent sim(s) in the 22nd Fleet.

By-Law #8 – Approval of New GM’s

The approval of all new Game Managers rests with the Division Head and their authorized deputies.

To open a game in the 22nd Fleet, a prospective GM must complete all the following steps:

  1. Agree to abide by the Fleet Charter, By-Laws, and Code of Conduct
  2. Submit a game proposal to the appropriate division through the GM application form
  3. Consult with the Division Head and/or their designee to refine or expound a proposal if necessary
  4. Create and publish a website for the game to a level of completeness to permit the recruitment of players
  5. Draft the game entry post for the 22nd Fleet Website
  6. Receive final approval by the Division Head/or their designee who shall then officially announce the addition of a new game and list the game on the 22nd Fleet website.

By-Law #9 – Leaves of Absence

There are three statuses other than active that may be applied to players and leadership that are not currently performing their assigned game or fleet roles:

LOA or ELOA

A Leave of Absence (LOA) is a brief leave from the fleet for a specified period of time, with a fixed return date.

An Extended Leave of Absence (ELOA) is any leave over two weeks or a leave that does not have a specified end date due to extraordinary circumstances in the life of the player. Extraordinary circumstances could include personal illness, illness of a family member, natural disaster or military deployment.

  • Both LOAs and ELOAs must be agreed between the person taking the leave and, should they be a GM, their Division Head. Players should always talk to their GM.
  • Should a natural disaster strike an area of the planet known to be home to one or more of the fleet’s members, said members are automatically granted an ELOA in absentia until their status can be ascertained.

AWOL

A player can be declared Absent Without Leave (AWOL) for absences without an approved LOA or ELOA, by not returning within the specified return date of an LOA, or if an ELOA has continued, without any contact from the player, for significantly longer than anticipated.

  • If any player is declared AWOL, and all attempts to contact then have been unsuccessful, after a reasonable amount of time, one week minimum, they may be removed from their positions and subsequent appropriate actions taken.
  • Any player who wishes to claim unfair removal from their position while on leave must provide, to their Division Head, the acknowledgment of their leave notification/request to show that the LOA request was received and that the date the player returned was on or prior to the agreed date. The complaint can then be processed through the Chain of Command as necessary.

Game Managers, Council Members, Division Heads and Fleet Chairperson

  • Game Managers taking leave must specify to the Division head an Acting Game Manager in their stead along with their contact information.
  • All Division Heads have the right to take leaves of absences for up to 14 days.
  • Any period greater than 14 days (ELOA) requires notice to be given to the Fleet Chair in advance.
  • If possible, GM and Officer LOAs should be posted in the LOA channel on the Fleet Discord server.
  • Should a Division Head take a leave of absence, their authorized deputy shall take over as acting Division Head, having all charges and responsibilities, save for accepting new simulations into the Division.
  • Should the Fleet Chairperson be required to take an LOA/ELOA, their duties would fall to the Vice Chair until their return.

By-Law #10 – Privacy

  1. The 22nd Fleet shall maintain a privacy policy in open record in order to maintain compliance with the applicable laws instituted by the nations of the Earth.
  2. All sims on the 22nd Fleet roster shall be required to post and maintain a privacy policy in open record in order to maintain compliance with the applicable laws instituted by the nations of the Earth.
    1. All sims shall have two weeks to become compliant following the activation of their website(s).
    2. Should a sim not become compliant within the first two weeks, the Division Head will issue a warning (first strike) via an official email.
    3. Should a sim still not become compliant two weeks after the Division Head issues the first strike, the Division Head shall issue a second strike via an official email.
    4. Should the sim still not become compliant for two weeks following the second strike, the third strike shall be issued and the sim immediately removed from the fleet. If this sim is the GM’s only sim in the fleet, then the GM will forfeit their seat on the Council as well.

By-Law #11 – Supplemental Offices and Officers

  1. Pursuant to the Charter, the GM Council has authorized the following officers:
    1. The Fleet Development Officer who will be charged with public relations, recruitment of players and new sims alike, and enriching our community with resources.
      1. The Fleet Development Officer will develop training and similar resources for new and developing players and Game Managers.
      2. The Fleet Development Officer will be able to build a support committee around itself to manage the duties charged to the office, such as the management of social media channels.
      3. In addition to the support committee, the Fleet Development Officer shall be able to appoint a deputy who shall be able to fully operate as FDO should the FDO need to be temporarily absent.
    2. The Operations Officer who will act as a Division Head for the Misc Division, and all Divisions with three (3) games or less.
      1. The Operations Officer must be a GM, but will not be required to have a sim in any of the Divisions they oversee.
      2. The Operations Officer will focus on cultivating these smaller Divisions, helping them grow into an official capacity.
      3. The Operations Officer shall be able to appoint deputies based upon the same guidelines for Assistant Division Heads per the Charter.
      4. Should there not be any Divisions under the Operations Officer’s purview, the office will remain filled and the position will function as an Assistant to the Chair and Vice Chair.

By-Law #12 – Nomination and Election of Officers

  1. Scheduling Annual Elections
    1. Annual elections for Officers will begin with the nomination period beginning on 1 NOVEMBER and continuing until 30 NOVEMBER.
    2. The voting period for the annual officer elections shall take place 1 DECEMBER to 7 DECEMBER.
  2. Vacant Offices
    1. Vacant Offices occur when an Officer position is first created, the Officer holding the Office decides to resign before the term has ended, or the Officer holding the Office has been removed by vote.
    2. The process to fill the Vacant Office will begin with a discussion period lasting a minimum of 48 hours, and will be followed by a vote lasting no less than 72 hours.
  3. Nominations
    1. Any Game Manager or member meeting the requirements for an Officer position may be nominated by any member of the GM Council, including themselves.
    2. The Chairperson, or other appropriate Officer, will confirm if a Nominee is eligible and provide proof of that eligibility if necessary.
    3. Nominations must be accepted by the nominee prior to the start of voting or will not be placed on the ballot.
    4. Members may accept nomination for as many positions that they are nominated for.
  4. Voting
    1. If there is only a single member nominated for a position the nomination shall be considered unanimous and a single ballot shall be cast by the Vice-Chairperson for that member.
    2. If there are two members nominated for a position, then a traditional runoff vote will be held.
    3. If there are three or more members nominated for a position then Rank Choice Voting (RCV) shall be used.
      1. Voters rank the candidates for a given office by preference on their ballots.
      2. If a candidate wins an outright majority of first-preference votes (i.e., majority of votes cast by the Council), he or she will be declared the winner.
      3. If, on the other hand, no candidates win an outright majority of first-preference votes, the candidate with the fewest first-preference votes is eliminated.
      4. All first-preference votes for the failed candidate are eliminated, lifting the second-preference choices indicated on those ballots.
      5. A new tally is conducted to determine whether any candidate has won an outright majority of the adjusted voters.
      6. The process is repeated until a candidate wins a majority of votes cast.
        The following link shall be used as official reference: https://ballotpedia.org/Ranked-choice_voting_%28RCV%29

By-law #13 – Committees

The GM Council shall, at its discretion, organize committees to handle various tasks and projects based upon the needs of the 22nd Fleet at large.

  1. All committees shall be authorized by a simple majority of the Council.
  2. All committees shall report to a designated person or group, whether that be a select Officer, or the GM Council at large.
  3. Unless otherwise specified or required by the Council, the Chairperson shall appoint a person to head the committee. The appointee will not be subject to a confirmation vote by the Council, but the Council may choose to veto the appointment.
  4. The following committees are hereby authorized:
    1. The Awards Committee which reports to the Fleet Development Officer. This committee may contain GMs and Players on a volunteer basis in order to create, review, and give awards to members of the community.
    2. A Mentorship Committee which reports to the Chairperson. This committee may contain GMs who are willing to mentor other GMs within the 22nd Fleet in running successful sims.

By-Law #14 – Fleet Infrastructure

In order to maintain the infrastructure of the fleet the infrastructure committee will be made up of three members appointed by resolution of the Game Manager Council. Infrastructure will include, but not be limited to, items such as web hosting accounts, the website administrator account, discord owner account, and administrative access to social media accounts.

  1. Membership to the council will be required to be approved once per year in the Month of August.
  2. The committee shall consist of no less than three members who partake in fiscal responsibility for the fleet.
  3. The committee chairperson will be the primary contact for infrastructure matters.
  4. If the chairman does not also serve as the webmaster for the fleet, one may be appointed.
  5. All members of the committee will have appropriate knowledge and access to fleet accounts.

The committee shall:

  1. Submit a report of activities quarterly to the fleet along with officer reports or combined with the chairman’s report at the discretion of the committee chairperson and fleet’s Chairperson.
  2. Vote on all fiscal matters to approve purchase or to discontinue infrastructure.
  3. Monitor appropriate security access to the fleet’s infrastructure and ensure proper transition between administrations.
  4. Maintain a google account that will include the official email to use for official communications with web hosts and other vendors, log access to administrative accounts by committee members, and to hold a log of all access information for committee members.

Current Hosting Resolution (1)

The current infrastructure committee shall consist of Stephen (Chairperson/Webmaster), Sprite, and Teix. This will require renew no later than August of 2022.