The present document serves as a guideline. Reading is greatly encouraged, as it may ensure that everyone within the Discord server is on the same page. This policy may be subject to change at any given time if Management finds it fitting to do so. Also, some 'rules' can always be bent, but if it happens, special circumstances need to be met, and this needs to be done fairly in regards to other members of the community.

Overview

Who are we? Ravenbound is a Gaming community that focuses on Star Citizen with an emphasis on Large Group Combined-Arms Gameplay. We have players that enjoy all facets of the game, and strive to ensure we maintain a constructive, friendly, and overall positive environment with everyone we associate with.

COMMUNITY EXPECTATIONS

As a member of the Ravenbound Discord Server, you are effectively a member of the Org as a whole and have the ability to join on RSI as a Citizen/Affiliate. https://robertsspaceindustries.com/orgs/RABD

We ask our Citizens to follow these rules:

• Your discord nickname should match your RSI name for the ease of adding you to a party.
• We are all on the same team. We greatly value the ability to trust and rely on our members to play as part of a team-based environment, and although we acknowledge individual skill, we put trust at a higher level of importance. Be a team player and have good sportsmanship with everyone both in and out of the Org.
• Don't be a dick! If you have issues with something or someone, act like an adult and try to remedy the situation. If you require further assistance, contact Management to mediate.
• Real life comes first! We're just a bunch of nerds playing an unreleased space game on the internet. We ask that if issues arise, that you communicate with Management about anything of concern.
• Try to be active! We are taking lengths to ensure that the server remains active. If inactive for longer than 90 days, you will be removed!

AFFILIATION

We have a number of ORGs that we affiliate with and are working to frequently run events alongside. Points of contact will be given the Envoy tag and listed in the player list. If you have a friend or yourself that wishes to be an envoy for another org, please contact anyone from Ravenbound Management to become that role for your org.

Management has decided to clearly define the different "leadership" roles that will go into managing the org as a whole. The positions have been better defined for RABD's Growth in mind. Positions may change as the needs of the Org evolve.

Ravenbound Management

• Ravenbound Management oversees the entire Org and are meant to operate as equals among a council with no one person having more voting power than another.
• Each Management Member oversees a section of the Org as a Head of a Corps (TSC Director, Racing Corps Head, Freelancer Commissioner, Academy Dean) and are limited to being the Head of one Corps each to negate burnout. These heads are meant to create policies regarding each Division and related sub-sections along with assistance of voluntary leads.
• Management maintains 7 members in total. Any member of management may step down at any time, and a new manager would be voted into the vacant space. Otherwise, management members will need to be voted out of management by a unanimous vote by the remaining management members.
• Becoming a Battlegroup Role Commander does not equate becoming a member of Management as some Management members may relieve themselves of a Role Commander position in the future.

Battlegroup Leadership

• The Battlegroup Role Commander role is designated for those that are in command of a specific combat role within the Battlegroup. New Commander roles will be created as new features are developed.
• All members of Battlegroup Leadership (Commanders) have equal voting power on all subjects that are relevant to the Battlefield during Org Meetings (Public or Private).
• Battlegroup Leadership will vote in who will become a new Role Commander as a group when a seat is vacant or if a new role is created. Important factors for Leadership Candidates include: Availability, Sense of Responsibility, Ability to Teach, and Teamwork Mentality.
• As a Battlegroup Role begins to grow, Role Commanders may choose Captains/Mentors (Staff NCO) to help facilitate trainings and content for their respective roles. Staff NCOs do not have voting power but are meant to be a voice for the members of their respective squads/elements.
• During Combined Arms Operations, Combat Leadership follows this chain of command:
  • Battlegroup Role Commander
  • Captains/Mentors (Staff NCO)
  • Battlegroup Member

Section/Division Staff

• Like a Battlegroup NCO, the Section/Division Staff role is for those who are chosen by Corps Heads that wish to help facilitate content for their specific Section/Division.
• Designed for Voluntary Individuals, their goal is to create and moderate events that abide by the policies of their Division (Academy Registrar, TSC Commerce Staff, TSC Logistics Staff, Racing Lead, Freelancer RP Lead)
• Section/Division Leads do not have voting power during Org-wide meetings.
• There may be multiple leads per division. Each Corps Head may decide the number of leads required for their respective divisions. Contact the associated Corps Head to volunteer.

Town Hall Meetings

• Management will attempt to hold Town Hall Meetings once per quarter that will take place in the public section of the Discord to talk about the state of the Org and any changes affecting the Org as a whole
• There will be an open-comment period at the end of each meeting for all Citizens to be able to voice their opinions or any future topics to be brought up.