The Frontier Fleet Charter
Our motto has always been and always will be, 'for players, by players'. To keep being that quality game we always have strived to be and will keep striving to be, the time has now come to formalize our core essence and make our set-up even more democratic. That foundation, defining our core essence, is what this document is for.
Section 1: Fundamental Rights
1. All members of Frontier Fleet are equal. Discrimination is not allowed.
2. Members are allowed their privacy, but are to give true information.
3.a. All members are allowed to vote and can be voted upon, respecting restrictions made in further acts.
3.b. A member is excluded from the pool of members as meant under a, when that member has not been active for at least half a year. The sitting Gamemasters are allowed to lift this restriction in specific cases for specific persons.
4. All members are allowed to put requests forward to the Council.
Section 2: Game structure
a. Game Founder: founder of the game who still has a connection with the game.
b. Council: the executive body, a body of 3 elected persons responsible for the fleetwide day-to-day running of the game.
c. Gamemasters: the sitting Council combined with the Game Founder.
d. Command: all command teams of Frontier Fleet's dutystations, the Academy Commandant, the Webmaster and the head of Public Relations (PR) head.
e. Act: set of rules or guidelines as defined by the Gamemasters.
f. JAG: person who in disputes objectively has to look at righteousness of the procedures, acts and decisions.
g. Councilor: member of the Council.
h. Command Team: a dutystation's Commanding Officer (CO), First Officer (FO) and Second Officer (2O) and all other Command-level players of official FF dutystations.
2.a. The status of game owner, in the context of this constitution, is granted to Guido Dorssers, who has run the game from mid-2000 to early-2006 and is still arranging the hosting of the game.
2.b. The Council cannot take away the status of ownership.
2.c. Abdication of game ownership, handing over or dividing ownership will be arranged by act.
3.a. A game owner can also temporarily abdicate from ownership to later on pick up game ownership. In this case a special act will have to be made to formalize this.
3.b. In the meantime, for altering or revoking the special made act itself or altering this constitution, the temporary abdication of game ownership does not apply.
4.a. The councilors are appointed by the game owner.
4.b. All appointed councilors together form the Council.
4.c. The game owner is inviolable, the Council is responsible.
5.a. After each new composition of the Council, the duties of the respective councilors will be defined by way of act.
5.b. Councilors are allowed to delegate the duties they are responsible for, it will however stay their end-responsibility.
6.a. The Gamemasters are responsible for ensuring there is an act that set up a procedure for members to directly or indirectly vote for the councilors to be appointed.
6.b. The period that councilors can serve is a maximum of 3 years.
7.a. Command represents the full complement of all members in the regular behind-the-scenes running of the game. Only current command team members can be part of command.
7.b. The period for people to serve in a command position, and thereby be part of Command, is unlimited, respecting restrictions set in other acts.
8.a. By way of act a schedule will be created for public IRC meetings of the Council.
8.b. These meeting will at least be held quarterly.
8.c. The act will define what kind of items will be handled in public and in what way, if at all, members present are allowed to speak their mind.
9.a. Command has the right to ask the Council for explanations of their actions. 9.b. Command members cannot be demoted, thrown out of the game, or otherwise be handled in a negative way for using this right.
10.a. A JAG will be chosen by way of voting conform a procedure to be described in an act.
10.b. The JAG has to be an experienced member, but cannot be part of the Council and is preferably also not part of Command.
10.c. A candidate for the JAG will have to be put forward by at least two members of Command.
10.d. By an equal amount of votes the difference in endorsements will define the JAG to be appointed, if this is also equal, the Council of Gamemasters will pick the JAG of their choice.
10.e. The JAG will be protected from being demoted, thrown out of the game, or otherwise be handled in a negative way for being in the position of JAG.
11.a. The JAG is directly responsible to the game owner, but does not take orders from the game owner.
11.b. The JAG is responsible for objectively looking at the Frontier Fleet Acts and state if a decision, including acts, made by the Gamemasters, the Council, a member of Command or the behavior among members is consistent with the active Frontier Fleet acts.
Section 3: Running of the game
1.a. Acts are created by the Gamemasters.
1.b. Acts are only valid after they have been published on the website and announced to all members by way of either the NRPG-list or the mailing function of the website.
2.a. Executive decisions about the fleetwide running of the game are the responsibility of the Council. The Council also oversees all game functions.
2.b. Executive decisions include the following non-limited list of decisions:
- Frontier Fleet Canon.
- Giving permission for dutystation missions.
- Handling promotion requests to Lt. Cmdr. and higher.
- Deciding on promotions to Command team positions after discussion with the Command.
2.c. Executive decisions exclude the following non-limited list of decisions:
- Creating acts
- Changing the structure of the game
- Creating and/or cancelling dutystations
- Adding dutystations
2.d. Overseeing all game functions as under a includes the following non-limited list of tasks:
- Handling requests for new biographies.
- Handling requests for a transfer (in communication with the Commanding Officers of both the dutystations tranferred from and to). - Dealing with small straightforward questions about Frontier Fleet canon - Setting deadlines for discussions in Command.
- Giving out summaries about these discussions to Command, when the deadlines have passed.
- Organise the voting for those discussions to determine the majority's stance.
- Giving out fleet-wide summaries monthly to Game Founder and Command about what the Council has been doing and a summary of the discussions at Command.
- Dealing with Cadet assignments in the Fleet, and monitoring dutystation activity (and dealing with it as necessary; although individual dutystation commanders should take initiative on that matter).
- Monitoring the Frontier Fleet timeline (where dutystations are at, time-wise, in relation to each other).
- Keeping the playerbase informed about significant decisions/discussions at Command or Council.
- Monitor the Public Relations, Newspaper, and Academy Commandant positions. Find replacements as necessary in consultation with Command.
- Arbitrate disputes between dutystations and discuss these with Command as deemed necessary.
- Command as well as invidiual players may send questions and concerns to the Council as they see fit; the Council will address/redirect their concerns appropriately.
3.a. Frontier Fleet Canon exists of the Star Trek series and movies, the Star Trek books and Star Trek books.
3.b. Series and movies have priority when defining canoness.
3.c. Books are considered canon unless conflicting with series or movies.
3.d. When a conflict about canoness comes up the Council handles it and does it's best to keep the canonness of series, movies and books intact as much as possibile.
4.a. Command will handle the less frequent, more significant issues regarding game continuity, etcetera.
4.b. On each of these issues, Command's majority view is considered to be a strong but non-binding recommendation, which the Council must take into account.
4.c. If the Council does not adopt Command's recommendation, the Council must provide specific justification for rejecting the recommendation.
4.d. These issues meant under a include the following non-limited list of tasks:
- Discuss and vote about larger Frontier Fleet canon issues, such as adding a species to Frontier Fleet or questions about the TV series.
- Discuss and about filling in Frontier Fleet history: what happened to the Talaxians since the end of the series, what happened to the Breen, etcetera.
- Discuss and vote about the Frontier Fleet fleetwide storyline.
- Discuss and vote about the Frontier Fleet fleetwide feeling, and how to improve that.
- Bring fleetwide problems to discussion.
- Conduct votes for councilors and/or other positions as necessary.
- To discuss and fill vacancies in the Command Teams, be it for individual dutystations or in the other positions involved in running Frontier Fleet (Public Relations, etcetera).
- Discussing alterations of the Game Rules.
- Any serious discussion regarding the reassignment or dissolving of a dutystation.
- Discussing command team vacancies, and potential candidates to fill them.
5.a. The Council is responsible for the game.
5.b. The Game Founder is responsible for the website.
5.c. The Webmaster is answerable to the Game Founder, yet the website must support the game. The Council will support the Webteam in providing contents for the website.
5.d. Public Relations is answerable to the Council and responsible for advertising the game in order to attract new members.
5.e. The Chief Editor of the Newspaper is answerable to the head of Public Relations.
5.f. The Newspaper is for both internal and external receivers.
5.g. The Academy Commandant is answerable to the Council and responsible for training new applicants in using our posting format and our posting style.
6.a. Dutystations are run by a Command Teams, consisting of a Commanding Officer (CO), a First Officer (FO), a Second Officer (2O) and all other official command-level players.
6.b. The Command Team in-game consists of PC characters.
6.c. The Command Team should discuss their dutystation's running among them.
6.d. While the Command Team has a requirement to discuss, the Commanding Officer has the ultimate say.
6.e. While the Commanding Officer has the ultimate say on his/her dutystation, he/she can be overruled by the Council.
6.f. The Commanding Officer reports to the Council.
6.g. The First Officer reports to the Commanding Officer.
6.h. The Second Officer reports to the Commanding Officer and the First Officer.
7. In order to know who is interested in a Command position or otherwise helping out behind the scenes, the Council will arrange for a questionaire to be held half-yearly.
8.a. Command Teams have to write monthly status report which are to be send to the Command.
8.b. A full status report includes (in this order):
• The (current) stardate the dutystation is on.
• The (current) location of the dutystation (if applicable since a starbase will not move...).
• A summary of the most important events of the past month.
• A list of current vacancies.
• A list of current players.
• After these five items other optionalities are allowed to follow.
Section 4: Council Articles
1. The council will be made up of rotating members. At minimum yearly one current member is to be replaced by voting in a new member.
2. Accepting the role of councilor means committing to serve a minimum of a three year term. Although at their discretion the council may choose to exempt a councilor from this commitment if they are in unanimous agreement (i.e. someone wants to step away after two years).
3. If any councilor has to step down, then a special election is held to replace that councilor at the time of stepping down.
4.a. After three consecutive years on council, if a councilor wishes to continue to serve they must stand for re-election with other members seeking election.
4.b. Assuming they are elected and they serve a fourth year they must thereafter step down for a minimum of one year. After one year, the member may run for election again when called.
5. The council will never be made up with all members of the same dutystation.
6.a. Voting on the council is exclusive to the appointed councilors at that time.
6.b. All councilors have an equal vote.
7.a. In the case of a stalemate being reached on any particular issue, the vote will be turned over to the Command List for further consultation.
7.b. If the issue is still not settled, the vote of the Game Founder will be the deciding vote between the options currently stalemated.
Section 5: Council Election Articles
1. Minimal requirements to be eligible for election to the council are the rank of Lieutenant, current active membership and continuous membership in Frontier Fleet for at least one year.
2. The minimal rank and continuous membership can be lowered on a case by case basis at the Gamemasters' discretion (for example, if the applicant has been a member of Frontier Fleet before).
3.a. Election for the FF council are held in the month September of each year. 3.b. Candidates for a Council position will be drawn gamewide.
3.c. Any eligible candidate may stand for election when one is called.
3.d. Two weeks before planned election, requests for nominations will be called by way of a member-wide mailing.
4.a. Candidates will send their nomination request to Command.
4.b.i. A candidate's nomination must be endorsed by two members of the Command list before accepted.
4.b.ii. Command members may hand out only one endorsement per election.
4.c. One week before the election the candidate list will be finalised by an announcement from the council. All members endorsed by at least 2 command members will be taken forward as candidates in the election.
5.a. Command will have a closed voting where Command will vote by sending an email to the Gamemasters. Alternatively the Gamemasters can agree to chosen scrutinizers as determined necessary/practical by Command.
5.b. Candidates standing for election are not eligible to vote.
5.c. Voting will be announced one (1) week in advance and immediatly before the voting period starts.
5.d. Voting will be four (4) days. The election will not be ended until the voting period has passed or until all eligible Command members have voted.
5.e. A minimum of fifty percent (50%) of eligible Command members must have voted for the election to become official.
5.f. In the case of a tied vote, the vote of the Game Founder will be the deciding vote between the options currently stalemated.
6.a. For either the Game Founder or a member of Command to remove a councilor, he/she needs to call a vote for impeachment.
6.b. Either the votes of the other two (2) councilors or fifty percent (50%) of the votes of Command (excluding the Councilors) is required for the hearing to go forward.
6.c. Voting will be three (3) days.
7.a. A hearing as called per article 6 will exist of a discussion period of two weeks.
7.b. After the hearing a private vote will be held over three (3) days to determine whether the councior will stay on or not. Command, Council and Game Founder will send their votes to the JAG.
7.c. The following vote results are required to remove a council member: - option 1: fifty percent (50%) of the gamemasters and fifty percent (50%) of command (non-council);
- option 2: twenty-five percent (25%) of the gamemasters and sixty-six (66%) of command (non-council);
- option 3: zero percent (0%) of the gamemasters 88% of command (non-council).
Section 1: Fundamental Rights
1. Normal respective behavior is expected from all members.
2. The essence of the internet allows one to hide and create his/her own virtual identity. While we can of course not verify this, we allow everyone to hold back information they are not willing to give, but require everyone to give true information when giving information. An internet community like Frontier Fleet can online survive by putting trust into eachother, trust that of course needs to be earned, but cannot be earned by giving false information.
3. Basically all members are equal and are allowed to vote and can be voted upon. However, further acts can also state restrictions. Possibilities are for example allowing members to chose command members and have command members chose the council. Or the other way around, have the council be chosen by all members and have the council pick the command members.
Section 2: Game structure
1.a. Currently one of the original founders, Guido Dorssers, is still around and interested in the game, taking care of it's hosting and giving active input when possible for as much as his time restrictions allow. He is also the one currently responsible for arranging the hosting, including the mailing lists, and holds the domains. Even though he does not have time any more to be an active day-to-day part of running the game, he is still around behind the scenes and granted the role of game owner. In the future it is not unthinkable that the role of game owner will be merged with the role of council. It will however be up to the game owner to abdicate ownership.
1.c. When the Gamemasters will be referred to, they are referred to as a single body who need to act in unison. The persons who are together former the Gamemasters have no seperate powers.
1.d. The dutystations meant are to be PC dutystations. SPC or NPC dutystations, like for example the Academy do not count for these definitions. Keep in mind that the Academy Commandant nonetheless holds a special position.
1.e. Usually the acts will be prepared by or in order of the Council after which the approval of the Council of Gamemasters will grant them their status of act.
2.a. New circumstances might in the future lead to a new version of this constitution where this will need to be replaced by something else. For example when there is a new hosting of the website, mailinglists and domains, the Council of Gamemasters might decided to include the person responsible also as a game owner.
Section 3: Running of the game
2.b&c. The lists being non-limited means that is here as an example, decisions which are comparable also fall in this category.
2.d. Copied from the proposed charter section 3.0 Council/Command Duties, article 1.1.
- Small straightforward questions about Frontier Fleet canon are questions like "Can I join you with a Betazoid?" or "Is it okay for me to make my Jem'Hadar telepathic?".
- Monitoring the timeline means guarding the timeline and keeping all dutystations on the right track. The idea will be that all missions will span multiple days. The Council will set an in-game month in which all dutystations will play and will also set an out-of-game timespan in which these missions are to be ended. The in-game months given by the Council will normally consist of timejumps of approximately 4 to 6 months. In these months a dutystation will usually roleplay about 1-2 weeks. The remainder of the time is not roleplayed, but can be used for flashbacks in a following mission. A middleway should tried to be found for keeping timejumps as short as possible, while they also should try to refrain from being too short which might cause officers to go from Ensign to Commander in one month gametime.
7. To be able to create a list of candidates for command positions, a questionnaire will be held half-yearly. This questionnaire can contain public relations related questions, mission related questions, etc. They will in each case also hold questions about command, whether a person likes to get in command someday, how he/she would handle a command position, why he/she thinks he/she would be a real asset, etc. The Commanding Officers of the dutystations will compile this information and add notes based on their command teams' opinions. They will sent the compiled questionnaires to the Council who will then be able to use them when needed.
8.b. A script is available on the website to copy&paste the crew aboard a dutystation, for example <http://www.frontierfleet.com/vessels/roster.text.php?id=3>.
Section 4: Council articles
4. This is to encourage the use of the rotational system.
5. The council, ideally, will be made up of members from different duty stations. Should this not be possible, then trust is placed in the council to remain true to the best interests of the fleet, and not their individual ship. The council will however never be made up of all members of the same dutystation.
Section 5: Council election articles
6. A council member should not be removed unless under extreme circumstances, but in the case that a member of command feels it is necessary to do so, they can call a vote for an impeachment.