HOME > Guides & Information > Group Information > FSF Charter

FSF Charter

ARTICLE 1: Preamble

We, the members of the Federation Sim Fleet, have set forth to provide an entertaining gaming atmosphere. Our main and most important goal is to appeal to the online gamer, not the entire simming, or gaming, community.

The Administration, Fleet Command, the Hosts, and the Members are all dedicated to the proposition that all people in the simming world are equal and deserve equal and positive treatment. As a group, we have the following basic goals:

  • To supply a fun and safe environment for all our members.
  • To provide conditions of friendship and mutual respect for all.
  • To ensure an organization that is completely financially free for general membership (excluding a personal home service.)

Therefore, in compliance with the above goals, we have formed an online simulation group called the Federation Sim Fleet (FSF).

For the purposes of this document, a majority vote in Fleet Command is considered when half of the total number of active fleets votes together. If there are six fleets, it requires at least three fleets to vote their approval to pass a vote.

ARTICLE 2: Purpose of Document

SECTION 1: To provide everyone, without regard to race, color, ancestry, age, sex, or any other consideration, membership to this group.

SECTION 2: To ensure availability of fun, fair and entertaining online games to all members.

SECTION 3: To present a gaming forum free from complication, injustice, bias and oppressive and burdening bureaucracy.

SECTION 4: To maintain the idea that peaceful cooperation is the basis for continued growth and development of a gaming organization.

ARTICLE 3: Government

SECTION 1: The FSF, from the time that this charter is approved, will follow the official FSF Government System. This document will be posted in public view, and sent to any member or outside group that requests it.

SECTION 2a: The Government of the FSF consists of two separate governing bodies: the Administration and Fleet Command. Fleet Command handles all simming policies, while the Administration handles group-wide policies and the enforcement of all policies.

SECTION 2b: The Administration consists of the FSF Commanding Officer, the FSF Executive Officer, the Chief of Operations and all members of the Personnel Department in Director Positions. The FSF Commanding Officer runs the Administration, and decision-making authority within the Administration can be delegated on a case-by-case basis.

SECTION 3a: Fleet Command shall vote to create or remove any sub-fleets as needed. Once created, the Administration shall designate two hosts, once approved to be on Fleet Command by Fleet Command, to act as Fleet Commanding Officer and Fleet Executive Officer, of said sub-fleet.

SECTION 3b: Sub-fleets may draft sub-charters of the FSF Charter that further explain policies and rules for that specific sub-fleet, as long as said sub-charters, fleet rules and fleet policies do not contradict established FSF policies, outlined in this and related documents.

SECTION 4a: Each simulation in the FSF is assigned to a fleet of simulations, consisting no more than eight simulations. Each fleet has a Commanding Officer and an Executive Officer, both of which vote together on Fleet Command.

SECTION 4b: Fleet Command will hold regular monthly meetings, via chat room or mailing list. In order to pass a vote, a majority is required. If there is a tie in the vote, the FSF Executive Officer may vote to break this tie.

SECTION 4c: The FSF Executive Officer proposes votes and collects vote tallies through email from the fleets. Each vote runs one week. Once a vote has finished, the FSF Executive Officer has up to a week to present the results to Fleet Command and the Administration.

SECTION 4d. New members of Fleet Command must be voted into Fleet Command by Fleet Command by a majority vote. They must meet the following qualifications: be a host for at least three months in good standing and must host in the fleet they will represent within two months of appointment.

SECTION 4e: Each Fleet gets one vote on Fleet Command. The Fleet CO and Fleet XO of each fleet must vote together. If they disagree on their fleet's vote, they must vote to abstain.

SECTION 4f: Any member of Fleet Command may get a vote proposed through the FSF Executive Officer. They are required to retrieve one co-signer from another member of Fleet Command in a separate fleet from their own. The FSF Executive Officer is required to propose this vote within seven days of receipt (not necessarily from when it was sent).

SECTION 5: Members of Fleet Command report to the FSF Commanding Officer. Members of the Administration report to the FSF Commanding Officer. Fleet Commanding Officers supervise the hosts in their fleet for the positions they host in their fleet. Once a host has been assigned to a Fleet Commanding Officer, he or she is required to assign and remove said hosts in their fleets to active simulations in their fleets.

SECTION 5a: The Chief of Operations position is filled by a member of Fleet Command. Fleet Command shall appoint the person for a one-year term through normal voting procedures described above. The person appointed to this position must remain active in Fleet Command during their tenure.

SECTION 6: A Fleet Executive Officer is chosen to assist the Fleet Commanding Officer in their duties to run the fleet to which they are assigned. Fleet Commanding Officers can recommend a Fleet Executive Officer if the position is vacant in their fleet. The FSF Commanding Officer assigns Fleet Executive Officers to fleets after Fleet Command approves them.

SECTION 7: The FSF Commanding Officer may remove any member of Fleet Command or the Administration. Any reversal of this decision requires a majority approval in Fleet Command.

SECTION 8: The FSF Administration and Fleet Command may vote to change their duties, this charter, and policies relating to the operation of the group by a majority vote in Fleet Command. Any policies and procedures written by Fleet Command or the Administration, approved as outlined above, shall be added to an official handbook on FSF Policy & Procedure, available to all members and hosts.

ARTICLE 4: Membership

SECTION 1: All people of the universe are free to join the FSF if they have no prior negative history with the group.

SECTION 2: All potential members must agree to the rules of membership before their membership begins.

SECTION 3: Members are free to be in whatever sim they would like, per approval from the simulation's hosts, given they have completed any requirements for that simulation. Members can move in and out of fleets with no restrictions.

SECTION 4: Members can join up to three simulations per email address. The Personnel Director, on a case-by-case basis, may approve additional simulations per email address.

SECTION 5: Members are free to resign at any time. Members must remove themselves from the Account Management System (AMS) to be removed from the group.

SECTION 6: Members may contact the Personnel Director, FSF Executive Officer or the FSF Commanding Officer to appeal any membership decisions.

SECTION 7: Members may also join any other simulation groups without penalty in the FSF.

SECTION 8: Members are under a thirty-day evaluation from when they sign up initially to the FSF. During these 30 days, their performance can be evaluated. If after 30 days, the player is not qualified to sim on an Advanced Simulation, they may be removed and reassigned to receive training.

SECTION 9: Members may only miss six weeks of simming within six months. If a simmer misses more than six unexcused sim weeks within these six months, they can be penalized, removed from their assigned simulation or removed from the FSF. Only simulation hosts may enact this section for members of their simulations. A sim week is characterized as chat simming for a specific week or email or message board simming for a week.

SECTION 10: A fleet's Fleet Commanding Officer may ban a member from their individual fleet. A member may be banned from the FSF through a vote in Fleet Command with which at least half of the active fleets in the FSF approve. Fleet banishments may be overturned by the Administration. Group banishments can only be overturned by a majority vote in Fleet Command.

ARTICLE 5: Hosting

SECTION 1: The FSF Commanding Officer may train and empower volunteers to host activities in the FSF. These activities can range from chat games, email games, message board games, or other related activities.

SECTION 2: All current members of the FSF may apply to be a host. Any player with less than six consecutive months of current active membership must have at least one host recommendation, one Fleet Command Recommendation, and Administration approval. Any player under 18 years of age must have two host recommendations and Administration approval. No player under 16 may be hired for hosting. The Administration may require proof of age before an interview is granted.

SECTION 3: All people interested in becoming a host must fill out an application and be interviewed before being hired to host. If hired, all hosts must agree to the Host Code of Conduct and fill out the host biography form before officially hosting any activity.

SECTION 4: The Code of Conduct must be available to all hosts at all times. Any changes to the Code of Conduct must be approved by Fleet Command, and once approved, immediately sent to all FSF hosts for their notification.

SECTION 5: Any infractions of the Code of Conduct may result in disciplinary action by their superior officer, including but not limited to, restriction and/or reduction of hosting duties, probationary LOA, or termination of hosting status.

SECTION 6: Multiple hosts of simulations share responsibility for the simulation. Hosts report to their direct Supervisor, the fleet's Fleet Commanding Officer to which their sim is assigned. Hosts for other related activities report to the FSF Executive Officer.

ARTICLE 6: Simulations

SECTION 1: FSF has no authority to change a simulation's concept, roster, or plan of action by hosts or players. FSF has the authority to remove a simulation's hosts from their hosting position(s) in regard to the policies in the Code of Conduct.

SECTION 2: Hosts looking to create a new simulation in the FSF may propose a concept, which includes a website, roster, cohosts, game type and plot plan, to the FSF Commanding Officer and FSF Executive Officer. If approved, the simulation is then added to the FSF under a sixty-day probationary period.

SECTION 3: A simulation may be added to the group, from outside the group, with a majority vote in Fleet Command. Simulations are required to have a website with links to the FSF, a roster size of at least eight unique players, two active hosts, and have been simming continuously for six months. If approved, the simulation is then added to the FSF under a sixty-day probationary period. This simulation may be removed or request removal from the group, at any time during these sixty days.

SECTION 4: The FSF Commanding Officer may remove a simulation from the group for major infractions by the host(s) of the simulation, inactivity by the simulation, or other such related problems. This decision can be reversed by a majority vote in Fleet Command.

SECTION 5: A simulation must have at least two hosts, but in special circumstances a Fleet Commanding Officer may request Administration approval to assign a third host. Simulation Admissions may be granted exemptions to this limit on a case by case basis, requiring Administration approval and a Fleet Command majority vote. All hosts share responsibility for the simulation and may face disciplinary action if the simulation does not remain active with all related activity factors (website, roster, etc.). Hosts must adhere to the list of responsibilities in the official Staff Duties & Responsibilities information packet.

SECTION 6: Each simulation in the FSF must maintain and update: a game Website and Message Boards (which must be located on the main FSF server), the Account System for this simulation (ranks, positions, open positions, promotions, removals, etc.), a roster with current mailstring, and a simulation information package (which should include a welcome, plot information, roster, mailstring, FSF data, and simming information).

ARTICLE 7: Rules & Policy

SECTION 1: A single set of membership rules will apply to all members of the group. Fleet Command must approve any changes to these rules.

  • All members must agree to the group rules upon joining, and will forfeit to the decisions of the group if they break any of these rules.
  • All rules must be accessible at all times to all members. Changes to rules must be announced to all members.

SECTION 2: Policies are created and continually changed to work for the current system of operations. Most of these policies will be in the above articles, but any policies that need to be expanded upon, or edited, may be done so via separate documents. These policies, just as the rules, must be accessible to public view via the webpage, and a separate email to all affected for notification of the change.

SECTION 3: Sub-fleet policies and rules, established in fleet sub-charters, shall be enforced by Fleet Commanding Officers, with appropriate punishments for all members and hosts, with consultation with the Administration.

SECTION 4: Any member that has broken a rule or has gone against policy will be dealt with on a case by case basis (no decisions can be made on a group of members). Members have the right to defend their side and appeal to the FSF Executive Officer.

  • For small infractions, the hosts of the simulation have the right to discipline the member. This may include a warning, restriction on characters, and banning from their sim. When a player is banned from the sim, the Personnel Director is notified.
  • A host may request further action, outside their sim, to be taken against the member. They may make such a request to the FSF Commanding Officer.

ARTICLE 8: Intergroup Relations

SECTION 1: The FSF may set up agreements with other groups for cooperation and prosperity. These must be approved by Fleet Command & administered by the Administration.

SECTION 2: The FSF can at no time use methods to disrupt other simulation group's sovereignty.

SECTION 3: The FSF cannot admit a simulation that is a member of another group. The sim must be independent before the FSF can vote on its admission.

SECTION 4: The FSF may enter into a large group alliance to represent its interests in the simming community. Fleet Command must approve or deny the membership of the FSF in such an alliance and shall at any time vote to disengage the FSF from such an alliance.

SECTION 5: If groups outside the FSF request admission into the FSF, the FSF Commanding Officer or FSF Executive Officer may gather information about this group and propose a vote to Fleet Command. The group may be admitted into the FSF with a majority in Fleet Command. Once admitted, such a group will no longer run as a group, but as individual simulations in the FSF.

SECTION 6: The FSF cannot declare war on people or sim groups at any time. The FSF cannot participate in any wars on the Internet and cannot supply aide to any groups that are violating the ideals of this charter.

SECTION 7: A majority in Fleet Command must approve Joint Activities with other sim groups.

SECTION 8: The FSF may not recruit in or on other sim group chat rooms or message boards. Any kind of disruption by a member with a clear association with the FSF in any other sim group activity will result in disciplinary action on said member, which may include termination of membership.

SECTION 9: The FSF can nominate a person to act as Ambassador to other sim groups. This person must be an FSF host and must have at least three months of hosting experience. This person would be included on the FSF Administration in the Personnel Department.

Keyword: FSF Charter