Juno Fleet :: Star Trek Roleplay
(Rules and Regulations - Revised 2008)
Revised and Edited by Fleet Admiral Robert W. Cornwall and Vice Admiral Andrew Smith

CONTENTS:

Article 1. - Mission Statement
Article 2. - Fleet Structure
Section 2.1 - Simms
Section 2.2 - Task Groups
Section 2.3 - Task Forces
Section 2.4 - Juno Fleet Admiralty
Article 3. - Rights and Responcibility
Section 3.1 General Members



Article 1 - Mission Statement

Following in the legacy of the brilliant story created by Gene Roddenberry's Star Trek, Juno Fleet endeavors to recreate and go beyond what Roddenberry had started and open ourselves up to whats out their in the Star Trek universe by providing a fun and creative atmosphere for internet users to fullfill their fantesy of living in a Star Trek universe. Juno Fleet does this by creating Simming environments at which to let lose the imagination in all of us and bodly go where no one has gone before.

Juno Fleet :: Star Trek Roleplay acknowledges that the Copyright for Star Trek, Star Trek: The Next Generation, Star Trek: Deep Space Nine, Star Trek: Voyager and Star Trek Enterprise and all associated trademarks are the property of Paramount Pictures and are used here in a non-profit manner. Copyright infringement is not intended in anyway and merely for the enjoyment of our members.

Article 2 - Fleet Stucture

As with all organizations, Juno Fleet cannot function without some form of organization. Juno Fleet is set up in the following manner. Every SIMM (commonly known as a ship or starbase) is assigned to a Task Group which is further assigned to a Task Force. The overall operations and the fleet is run by Juno Fleet Admiralty.

The main timeline in Juno Fleet is situated in the year 2421 after all of the Star Trek tv shows and movies. All of the ship, starbases, uniforms and other things pertaining to Juno Fleet have been updated to show evolution of time and thus many things have changed to suit the era. A simm can roleplay in a different era only by permission from the Admiralty.

Section 2.1 - Simms

1. A Simm is a site run by a commanding officer that administers the site. The simm is usually a ship, starbase or ground base where people roleplay their characters in.

2. All simms must be assigned to a Task Group unless deemed Independant.

3. The chain of command for a simm is as follows: Commanding Officer, Executive Officer and Second Officer.

Section 2.2 - Task Group

1. A Task Group is generally comprised of five to seven simms and the size is determined by Admiralty.

2. Every Task Group must have a Task Group Commanding Officer and a Task Group Executive officer if deemed necessary by the Admiralty and the TFCO and if there is more than one task group in the said Task Group.

3. A Task Group Executive officer may not be from the same simm as of that of the Task Group Commanding Officer.

4. The Admiralty can appoint any commanding officer from any task group to be TGCO or TGXO of a Task Group.

5. A TGCO may recruit extra staff for the operations of his/her task group by approval by the TFCO or Admiralty.

6. A TGCO can give out missions to the simms in his/her task group as long as it does not conflict with Juno Fleet's main timeline and general storyline. However, it is highly recommended that the TGCO speak to the COs of those simms to make sure it does not conflict with their own storylines.

7. Any TGCO can be removed without explanation or reason if the person has been proven inactive(see glossary) for over three months by TFCO or Admiralty if the person has not sent a LOA or ELOA status message to his/her TFCO or Admiralty.

Section 2.3 - Task Forces

1. A Task Force is comprised of up to five to seven Task Groups and the size is determined by Admiralty.

2. Every Task Force must have a Task Force Commanding Officer and a Task Force Executive Officer if deemed necessary by the Admiralty and the TFCO and if there is more than one task group in the said Task Group.

3. A Task Force Executive officer may not be from the same simm as of that of the Task Force Commanding Officer except under special circumstances determined by the Admiralty.

4. The Admiralty can appoint any commanding officer from any task group or task force to be TFCO or TFXO of a Task Force.

5. A TFCO may recruit extra staff for the operations of his/her task force by approval by the Admiralty.

6. A TFCO can give out missions to the task groups in his/her task force as long as it does not conflict with Juno Fleet's main timeline and general storyline. [b]However, it is highly recommended that the TFCO speak to the COs of those simms to make sure it does not conflict with their own storylines.

7. Any TGCO can be removed without explanation or reason if the person has been proven inactive(see glossary) for over three months by TFCO or Admiralty if the person has not sent a LOA or ELOA status message to his/her TFCO or Admiralty.

Section 2.4 - Juno Fleet Admiralty

1. The operations of Juno Fleet run by a team of members known as the Juno Fleet Admiralty

2. The Admiralty shall discuss matters of other fleet members regarding promotion, demotions, ban, recommendation and awardship among themselves and shall not consult another member in the fleet that is not of the Admiralty on these matter unless it is released to all members of Juno Fleet.

3. Any decisions made by the Admiralty may be countermanded by the Commander-in-Chief.

4. Each member of the Admiralty may recruit staff for his/her to help in the operations of his/her department if they so choose.

5. If the Admiralty would like to countermand the Commander-in-Chief's decision on a matter it must be an unanimous agreement amongst the entire admiralty.

6. The Admiralty reserve the right to change or revise any part of the Juno Fleet Rules and Regulations with or without the consent of its members.

7. The Admiralty may ban or remove any member with out express explanation of the following matters: posting vulgar and pornographic materials on any site in connection with Juno Fleet, is inactive for over three months without LOA or ELOA and racial slurs or derogatory statements.

Article 3 - Rights and Responsibilties

Section 3.1 - General Members

1. All members have the right to have an unresolved dispute mediated by the Judge Advocate General and or by Admiralty.

2. All members must create original characters and may not in anyway be established Star Trek characters or relatives thereof, or previously created Juno Fleet characters or relatives without the permission of the creator of the Juno Fleet character.

3. No member shall create a active character(this being that a member can create a non-playable character if the CO of the simm the member is on agrees) belonging to the following species without the Admiralty's consent:

The Q
Species 8472
The Borg
Breen
Jem'Hadar
Changling
Android

4. Members are expected to post at least once a week unless they are on leave of absence or extended leave of absence or if the CO of the simm has said otherwise.

5. Unless clearly specified all simms in Juno Fleet are rated PG-13. Any overly explicit content, vulgar or racial language will not be tolerated. It is the responsibility of the CO and XO to enforce this rule.

6. The chain of command is instrumental in ensuring that the fleet runs smoothly. All questions or complaints should be directed to your direct superior in the chain of command. If a question or complaint is regarding your direct superior you may go to the next person on the chain of command or discuss it with the JAG officer.

7. All members will respect the role of a commanding officer and should not start a new mission or significantly alter the plot of the simm they are playing on without the permission or direction of the CO. Exceptions are possible under extenuating circumstances.

8. All members will recognize the limitations of Star Trek and Juno Fleet canon and will not create unsual or different classes of ships, types of weapons or alien creatures with out the approval of the Director of Research and Development or the Admiralty.

9. All members shall refrain from recruiting members from another simm/fleet within or outside of Juno Fleet.

10. A member in Juno Fleet is allowed to be an active member of no more than three simms in Juno Fleet. The member can have a more than one character on a simm by the discretion of the CO. Certain exceptions may be granted on a limited basis by the Admiralty.

11. No member may have more than one CO position in Juno Fleet. Two XO positions are allowed by the discretion of the TFCO or by the Admiralty, except in the case of Academy or Admiralty position.

12. All members shall show respect for the characters of other members and shall not use them in a fashion that would be considered by or has not been approved by the member controlling the character in question.

13. Any member wishing to resign from a simm or Admiralty position must inform their CO, TFCO, Admiralty, or post it on the Juno Fleet forum.

14. All member shall try and resolve any disputes with other members in a respectful manner and should try to resolve the matter first with the other player and their direct superior before submitting a complaint with the Judge Advocate General.

15. All member have the right to take leave of absence(LOA) from their simm(s) and or position(s) without fear of loss of rank when they have real life committments to which they must attend.

16. All members shall leave the detemination of the rank of their character to their CO of their simm or the Admiralty.

17. Should a member wish to enroll in Juno Fleet Academy they must send a request to the Academy staff who will see to their enrollment.

18. All members should participate in Juno Fleet with the purpose of having fun.

19. All members must comply to the terms of the Juno Fleet Rules and Regulations and as such shall simm within the limitations and rights laid out by this document.

Section 3.2 - Commanding Officers
1. Any person wishing to be a CO must take a command course before being assigned a simm. Unless the person has six months of command experience in another fleet or has been roleplaying for over a year. Exceptions may be granted by the admiralty on case-by-case basis and subject to approval of the CinC.

2. A CO has the right to run their simm as they see fit so long as they do not violate any of the terms in the Juno Fleet Rules and Regulations. This includes the right to demote, promote, or remove players from his/her simm and to create missions and storylines for their simm.

3. A CO must report any demotion of rank of his/her members to the Judge Advocate General, except for those demotions which were taken voluntarily by the member in question.

4. A CO has the right to promote any member of his/her simm, up to the rank directly under themself. They cannot in noway promote a member higher than their rank. JAG may override the CO's decision to promote a member however, if the member in question is under punishment.

5. CO's shall not destroy, change the class of or specifications of their class as defined by Juno Fleet without the approval of their TFCO or Admiralty.

6. It is the CO's duty to recruit members for his/her simm, unless that duty has been expressly delegated to another member.

7. No member shall command more than one ship, starbase or ground base. Exceptions may be made by the CinC.

8. In order to receive a command position, all CO's must read and fully understand the Juno Fleet Rules and Regulations and agrees to comply to them.

9. A CO has the right to run his simm as either a play-by-forum or play-by-email format. If the CO wishes to change the format of his/her simm they must get approval from the Admiralty.

10. No CO shall have a joint-simm-mission with another simm in Juno Fleet without the permission of the Admiralty and after getting permission and compliance of the CO with which he/she would like to joint-simm with.

11. A CO that resigns from his/her position(s) may not take another command in Juno Fleet for 90 days and it is still at the discretion of the Admiralty to allow the CO to return to active duty.

12. A CO may recommend his XO or Second officer for a Command postion to the TFCO or the Admiralty.

13. A CO may not switch his ship to another TG or TF without the permission of his/her TFCO or the Admiralty.

14. All CO's must post a report by the 9th of every month, in the form set by the Admiralty.

Section 3.3 - Task Group CO's

Section 3.4 - Task Group & Force Staff

Section 3.5 - Task Force CO & XO's