17 Matching Annotations
  1. Apr 2026
    1. Section 3 — Scope (a) This Bylaw applies to playable canon races — species that members may use to create characters. (b) It does not apply to temporary NPC races created for plot purposes, which commanding officers may introduce at their discretion. Section 4 — Process (a) A proposal for a new race is submitted to the Captains Council with supporting documentation (species profile, biology, culture, etc.). (b) The CC votes under the standard procedures in Bylaw 1. The proposal passes by simple majority. (c) Approved races are added to the community’s official species registry.

      I'd like some clarity around what happens with species when they are created as NPC races initially and then tagged with a TBD / Non-Reviewed Species tag for the ILI.

      Is the process to go from a species introduced in our game's canon (for NPCs), to TBD / Non-Reviewed, to anything else (e.g. Permitted, Restricted, Forbidden) the one outlined here?

      What about the process for a canon (from the shows) species to go from TBD / Non-Reviewed to, say, Restricted or Forbidden - does that go through this same voting process?

      Finally, should we not perhaps codify in the bylaws our species review process (i.e. proposal, 7 day wait, if no veto it's approved, etc)?

    2. No member of any rank may use community resources — email lists, forums, Discord, or any other official channel — to recruit members for other organizations

      I'd like to suggest explicitly including Wiki content and Image Collective works to this

    3. Demands, personal attacks, and bad-faith argumentation are not tolerated.

      While I heartily agree with this statement, should we perhaps clarify somewhat further what constitutes bad behaviour within the CC context and what the consequences / mechanisms are there?

    4. The EC may require enhanced reporting from new commanding officers (through the end of their practical and first year of command) and from reinstated commanding officers (for up to six months after relaunch). Enhanced reporting follows a format determined by the EC and is intended to support the CO, not to penalize.

      Where is this defined? Or is this essentially a "we reserve the right to do this" and the details will be determined if/when it happens?

    5. The following officer ranks are recognized in StarBase 118 PBEM RPG, listed from entry to highest:

      It may be worth clarifying that these ranks are recognized OOC, though other rank structures may be used for IC purposes (e.g. Marine ranks, civilian 'ranks' for the FDC, Enlisted officers, etc).

    6. (c) To maintain CC participation rights, administrative members must meet the same 60% vote participation standard as other non-vessel members.

      Should this be clarified that this applies only to those with voting rights (or is this clear enough as is, given the definitions provided previously in the CON?)

    7. Built in Administrative Membership. Rather than bolting it on later, admin membership is a first-class concept throughout.

      I've commented on the relevant bylaw section overview this membership class (BL3) below, but in short, it was not assumed that this pilot would automatically become part of the CON / Bylaws after 1 year but requires a follow-up decision by the CC.

    8. (b) Administrative Member. New A member who is not actively simming but is contributing through out-of-character administrative work. Eligibility, oversight, rights, and limitations are defined in the Bylaws.

      I've commented on the relevant bylaw section overview this membership class (BL3) below, but in short, it was not assumed that this pilot would automatically become part of the CON / Bylaws after 1 year but requires a follow-up decision by the CC.

    9. Bylaw 3: Administrative Membership New SCA Proposal (2025) Entirely new Bylaw. Eligibility: Lt. Commander+ with 1 year service. EC application describing intended work. EC liaison assigned. Annual review. Retains CC rights at rank tier with 60% vote participation. Cannot command a ship, serve as FO, or be promoted while in admin status. 90-day AWOL provision. Voluntary return to active status at any time. Implements the SCA proposal concept with the lightest possible structure: liaison model (not sponsorship), annual review (not term limits).

      Per the Pilot Program's wording, as it was voted in:

      After the trial period the membership will have the option to permanently adopt the program, to modify it as necessary, or to end the pilot without restriction.

      I do not believe there has been a subsequent vote on whether or not to permanently adopt the program, to modify it, or to end it. I think before this is codified into a bylaw it ought, therefore, to go through a process to determine whether or not the CC actually wants to move forward with this program.

      TLDR: It was not assumed that this pilot would automatically become part of the CON / Bylaws after 1 year but requires a follow-up decision by the CC.

    10. (d) Once appointed, an EC member serves until they retire or are removed through the disciplinary process.

      What about EC members who are put on suspension without the typical disciplinary processes taking place? I understand this is sort of an "elephant in the room" - but this did take place in the past year. Yes, that member eventually retired, but in cases such as this is the expectation that the suspended member (who was not removed from the EC via the disciplinary process) would return after X amount of time (e.g. 6 months) back into the previously-held EC position? Would that position remain vacant for the duration of that time?

      I think, considering this has happened it may be worth clarifying what is expected for EC members who are suspended (or disciplined, etc) but not removed from the EC via the disciplinary process.

    11. reasonable time

      What does this mean? Can we be more clear about what constitutes a "reasonable time"? Is that a week? Two weeks? A month? etc

    12. At a minimum, members must participate in at least 60% of CC votes.

      How/when is this measured? At what point is it determined that someone has failed to meet this criterion for continued participation in the CC?

      Looking into the bylaws, I see that it is Quarterly. Perhaps it's worth noting that the measurement of this % is established in the bylaws.

    13. Decisions pass by simple majority (51%+)

      A majority of the Yes / No votes, right? Abstentions should not count as votes in this % tally, otherwise they will always be treated as no votes since they are not Yes.

    14. The founder provision is role-based and self-terminating — it does not create an inheritable class.

      Is it worth baking into this section that it should automatically be removed from the constitution, without need for an amendment, if the Founder permanently departs? Twenty years from now (god or whatever willing) we may well no longer have a need for this Section in the CON. Might be nice to have that housekeeping anticipated.

    15. (b) Regardless of active simming status, the founder retains: full EC and CC voting membership; all authority of their rank; recognition as a contributing member in good standing.

      It may be worth noting their role in the "Emergency Authority" structure since Wolf has been explicitly removed from that listing in favour of role-based terminology. Just for clarity.

    16. This section applies only to the individual who founded the community and ceases to have effect if that individual permanently departs.

      Considering we are only referring to one person here, what is the value in being vague in the language and saying "the person who founded the community" instead of just identifying the specific individual we're talking about? I think that would be more clear especially for newer members who may not know who this is.