Section 1.01    This organization is named "vspirit".

Section 1.02    This organization is not affiliated with Spirit Airlines or any other airline/aviation companies. All information and resources provided to our members is intended for hobby use only and should not be used for real world flight operations. Our resources have been compiled from publicly available documents found online and by compiling information collected from speaking to subject matter experts within the larger flight simulation community. None of the information or resources that we provide have been vetted by regulatory officials, the relevant equipment manufacturers, any airline or air carrier, or engineers. Attempting to utilize any information or resources provided by us could be catastrophic, involving potential revocation of licensure, injury, or death.

Section 1.03    This organization is not formally organized and shall not be operated for any financial gain or profit, nor will any service or item purchased for the group be used for any business activity.

Section 1.04    The purpose of this organization is primarily a social one: to gather likeminded aviation enthusiasts who enjoy enriching their flight simulation hobby through simulating the operations of a real-world airline.

Section 2.01    Membership in vspirit is open to any adult over the age of 18 by either invitation or by application. This age limit matches the age limit of vAMSYS, our service provider. We do not accept parental permission as an exception to the age limit. A link to the vAMSYS Terms and Conditions can be found in Section 2.05 (a).

(a) The minimum age for membership was updated on 16 March 2022 and was previously 16 years of age. Existing members as of that date are grandfathered in and not subject to removal from vspirit.

Section 2.02    Membership is fully voluntary.

Section 2.03    Membership is at the sole discretion of the vspirit administration team.

Section 2.04    All members are expected to abide by these bylaws and by all rules, codes of conduct, and/or community guidelines posted in any vspirit websites, chat servers, forums, etc.

Section 2.05    All members are expected to follow whatever posted rules, codes of conduct, and/or community guidelines are found on all vAMSYS websites, chat servers, forums, etc.

(a) https://vamsys.io/legal/tc

(b) https://vamsys.io/legal/privacy

(c) https://vamsys.io/legal/cookies

Section 2.06    All members are expected to follow whatever posted rules, codes of conduct, and/or community guidelines are found on all VATSIM, IVAO, and PilotEdge websites, chat servers, forums, etc.

Section 2.07    Breach of any of the above may result in immediate termination of membership in the organization at the sole discretion of the administration team.

Section 2.08    vspirit requires each member to file one (1) PIREP via our automatic flight tracking software, Pegasus, at least once every 90 days with a 10-day grace period. Failing to meet this requirement will result in the users account being deactivated, but not removed.

Section 2.09    New members are required to file one (1) PIREP in their first ten (10) days after joining. Failing to meet this requirement will result in the user's account being deactivated, but not removed.

Section 2.10    If removed per Section 2.08 you may rejoin in the future by requesting that your account be reactivated. Please contact the administration team via email, Discord, or the Contact Us page with a hyperlink to Contact Us to request reactivation. Do NOT create a new account as your old account was not deleted.

Section 3.01    The vspirit is led by a five person administration team.

Section 3.02    The administration team will, wherever possible, share equally the duties of running the organization, as well as the financial obligations.

Section 3.03    [Redacted]

Section 3.04    The duties of the administration team are ad hoc and are coordinated internally and do not consist of any specifically set roles.

Section 3.05    The administration team has the final say on all operational matters within the organization except where constrained by any external requirements from the organizations in Section 2.05 and 2.06.

Section 3.06    The administration team will take decisions wherever possible by unanimous consent. When a disagreement over a decision cannot be resolved, each of the five members will have one vote on the matter and the majority opinion will be the decision.

Section 3.07    Each administration team member can individually enforce our bylaws and community guidelines on any vspirit websites, chat servers, forums, etc. without consulting the other four admins, up to and including banning from membership any offending party.

Section 3.08    The administration team is supported by a staff team and a volunteer team. These members are appointed and removed at the discretion of the administration team and are tasked with both specific and ad hoc roles.

Section 3.09    Should a vacancy become available on the administration team, the filling of it will be at the sole discretion of the currently serving administration team.

Section 4.01    vAMSYS retains certain Personal Identifiable Information (PII) from users when they sign up for an account. This information is stored in vAMSYS databases to which vspirit has limited access.

Section 4.02    Please refer to the vAMSYS privacy policy (https://vamsys.io/legal/privacy) for further information on how your information may be collected, used, and removed.

Section 4.03    vAMSYS is the data controller of data input to vAMSYS systems; vspirit is a data processor.

Section 4.04    If a user wants to exercise their rights with regards to vAMSYS data, they must contact vAMSYS via email at hello@vamsys.co.uk.

In the interest of fostering an open and welcoming environment, the administration team pledges to make participation in vspirit and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio- economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Examples of behavior that contributes to creating a positive environment include:

• Using welcoming and inclusive language
• Being respectful of differing viewpoints and experiences
• Gracefully accepting constructive criticism
• Focusing on what is best for the community
• Showing empathy towards other community members
  
  

Examples of unacceptable behavioir by participants include:

• The use of sexualized language or imagery and unwelcome sexual attention or advances
• Trolling, insulting/derogatory comments, and personal or political attacks
• Public or private harassment
• Publishing others’ private information, such as a physical or electronic address, without explicit permission
• Other conduct which could reasonably be considered inappropriate in a professional setting
  
  

The administration team is responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

The administration team has the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representation include posting in other forums or Discord channels related to our hobby, flying on an online ATC platform such as VATSIM, IVAO, or PilotEdge, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by the administration team.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the administration team via email or Discord direct message. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The administration team is obligated to maintain confidentiality regarding the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Members who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.

This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html.

For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq.