PFDR Standing Orders


Revision as of 17:42, 7 August 2016 by Joe Rhimer (talk | contribs)

Below are the standing orders for the Research & Development department, in addition to the standing orders for the Galactic Anthropology Committee, which was absorbed into R&D. These standing orders are currently pending a rewrite in order to fully merge the departments; until such time, the standing order relevant to the area of the R&D department in question shall be used - however the R&D standing orders shall have primacy for any conflicts.

The GAC chair is no longer a PFA position.

Pegasus Fleet Director of Resources Standing Orders

  1. The Pegasus Fleet Director of Resources (PFDR) will create and manage the creation of wiki articles and IFS entries related to Ship Specifications, New Technology, Weapons Systems, Defensive Systems, Alien Race Profiles, Cultural Profiles, Fleet Canon, and other related items.
  2. The PFDR may select two deputies, one for Research & Development activities (Chief of Starfleet Engineering) and Galactic Anthropology related activities (Chairman of the Galactic Anthropology Committee), pending approval of the PFA.

Research & Development Standing Orders

  1. The Research & Development Department (R&D) will have the primary responsibility for researching and developing new technologies for use by the Fleet.
  2. The R&D Team shall be a loosely organized unit whose membership (Excluding the Director) shall be determined at the discretion of the Director of R&D, subject to the laws of Pegasus Fleet. In the case of the Director and Deputy Director, the procedures of the Selection Policy must be followed. This membership will consist of:
    1. Director of Research & Development
    2. Deputy Director of R&D
    3. Tech Team Members
  3. The Development Process is simple and follows this framework:
    1. The new technology (Including Temporary tech on a one mission bases) is sent to The Director of R&D for review, editing and framing into a proposal for review.
    2. Reasonable proposals will not be refused except on the following grounds:
      1. Goes against canon Laws or treaties
      2. Is too powerful for consideration
      3. Reproduces existing technology without significant advantage or reason
    3. Where the idea is a temporary one, the Director of R&D will respond to the request to the CO within 7 days of when the request was made with a Yes, No or modified answer. Unless the idea is something that would benefit the entire Fleet, temporary requests will stop at this step.
    4. The Director of R&D will post the new technology for public review on the Research & Development Forum.
    5. The discussion shall remain open for the greater of 1 week or 3 days after discussion has stopped, but no longer than 2 week's time.
    6. If the discussion does not reach the 2 week time limit, then the new technology will be considered to have passed by "Unanimous Consent"
    7. If the discussion would extend past the 2 week time limit, then the new technology will be presented to the PFA for vote as if it were a "Standing Order"
    8. If a technology is rejected by the PFA, then it will either be completely dropped or revised and reintroduced into the process, at the discretion of the Director of R&D.
    9. Technology that has passed will be entered into the appropriate Fleet IFS Database or Wiki, as well as the discussion topic moved into the Approved Technology Forum.

Issued: June 12th 2010

Galactic Anthropology Committee Standing Orders

Structure

  1. The Galactic Anthropology Chairman.
    1. The GAC Chair shall be a member of the Pegasus Fleet Admiralty
    2. The GAC Chair shall vote on all matters brought before the PFA.
    3. The GAC Chair shall coordinate with other GAC members to prevent ‘overwriting’.
    4. In the event that certain articles need to be written, the GAC Chair shall assign the article to an appropriate GAC member who is capable of doing the article justice.
    5. The GAC Chair shall organize a once-a-month meeting among the members of the GAC.
      1. The GAC monthly meeting shall be on the first Sunday of every month at precisely 6 GMT.
    6. The GAC Chair shall keep all infoboxes in the wiki updated.
    7. The GAC Chair shall keep all forms for various GAC articles updated in the Outer Office forum.
    8. The GAC Chair shall submit a monthly report to the PFA and commanding officers of the fleet no later than the 5th of every month.
    9. The GAC Chair shall encourage the commanding officers to share their unique species, planets, systems, and events.
    10. The GAC Chair shall bring all items proposed for fleet canon to the PFA for a vote.
    11. The GAC Chair shall recruit members of the GAC as necessary.
  2. Galactic Anthropology Committee Assistant Chairman
    1. The GAC Assistant Chair shall be an active member of the GAC
    2. In the event of the GAC Chair being on LOA, the Assistant GAC Chair shall take over the GAC responsibilities of the GAC Chair within the department.
    3. In the event of the GAC Chair being on LOA, the Assistant GAC Chair shall take over the organization of the monthly meeting of the GAC in the chat channel #gac on the DarkMyst server.
  3. Other members of the Galactic Anthropology Committee
    1. Members of the GAC shall be present at monthly meetings unless the GAC Chair is supplied with a reason.
    2. All members of the GAC shall vote on proposed GAC articles within the time frame of seven (7) days.
    3. Members of the GAC shall assist the GAC Chair in creating the fleet canon and GAC articles necessary for fleet story arcs.
    4. Members of the GAC shall assist the GAC Chair in creating the GAC articles for sims to use.
    5. Members of the GAC shall add their entries to the fleet wiki complete with links.
    6. Members of the GAC shall attempt to put as much detail as possible into GAC articles and fleet canon.
    7. All members of the GAC shall encourage members of the fleet to take part in the discussions on the forums.

Fleet Canon and GAC Articles

  1. The GAC articles shall be defined as articles that do not affect the fleet-at-large but also may be used by the fleet.
  2. Sims shall be encouraged to use GAC articles.
  3. Sims shall not be forced to use GAC articles.
  4. It shall be the responsibility of all GAC members to create GAC articles.
  5. Process for GAC article approval.
    1. The GAC member who wrote the article shall place it in the forums.
    2. The discussion shall remain open for the greater of 1week or 3 days after the discussion has stopped, but no longer than 2 weeks’ time.
    3. If the discussion does not reach the 2 week time limit, then the new article will be considered to have passed by "Unanimous Consent".
    4. If the discussion would extend past the 2 week time limit, then the new article will be brought before the GAC for a vote.
  6. Process for Fleet Canon Approval
    1. The article in question is placed in the forum by the GAC member who wrote it.
    2. Seven (7) days after the last comment has been addressed, the GAC Chair shall email the Pegasus Fleet Admiralty for a vote on the article in question.
    3. If the article has passed, the article shall be put into the wiki by the person who created it.
  7. Fleet Canon and GAC articles may be any of the following:
    1. Historical or Current person
    2. Species or culture
    3. Planet
    4. System
    5. Military
    6. Government
    7. Event
    8. Conflict
  8. If a article is rejected by the PFA, then it will either be completely dropped or revised and reintroduced into the process, at the discretion of the Director of the GAC.
  9. Articles that have passed will be entered into the Fleet Wiki, as well as the discussion topic moved into the Approved Articles.

Issue date not known