pva cODE OF cONDUCT AND bYLAWS

 Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, the administration team pledges to make participation in our project 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.

Our Standards

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 behavior 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

Our Responsibilities

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.

Scope

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.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the administration team at admin@vspirit.io or via 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.

Attribution

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.

 Bylaws

Article I. Name and Objects

Section 1.01 This organization is named “Piedmont Virtual Airlines Historical Group”, usually to be stylized as “PVA” or “PVA-HG”, a non-incorporated, non-registered, fully voluntary group.

Section 1.02 “Piedmont Virtual Airlines Historical Group” is not affiliated with Piedmont Airlines, American Airlines, or any other ‘real’ airline/aviation companies or their affiliates.

Section 1.03 All flight and aeronautical information found through membership in the club is for entertainment use only. For any real-world flight operations consult your appropriate procedures and regulations as determined by your local regulatory body.

Section 1.04 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.05 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.

Article II. Membership

Section 2.01 Membership is open to any adult or minor above the age of 16 by either invitation or by application.

Section 2.02 Membership is fully voluntary.

Section 2.03 Membership is at the sole discretion of the PVA 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 PVA 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 Piedmont Virtual Airlines Historical Group requires one (1) flight to be completed with a PIREP filed via Pegasus within 10 days of joining, and one (1) flight and PIREP filed via Pegasus every 90 days thereafter, with a ten-day grace period before the user will be automatically marked as inactive.

Section 2.09 If removed per Section 2.09 you may be eligible to rejoin in the future by requesting that the administration team reactivates your account.

Article III. Administration Team

Section 3.01 The administration team of the organization is composed of Mike Gold, Chase Burrell, Alex Dunbar, and Timothy Long.

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

Section 3.03 All PVA-HG websites and memberships are currently owned and administered by Mike Gold. Should he leave PVA-HG in the future he will be responsible to migrate those accounts to another appropriate member of the administration team.

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.06 and 2.07.

Section 3.06 The administration team will take decisions wherever possible by unanimous consent. When a disagreement over a decision cannot be resolved, the administration team will vote. In the event of a tie, the question may be put to a vote by the entire membership if the tie cannot be resolved internally within the administration team.

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

Section 3.08 As required, from time to time, the administration team may delegate some tasks to certain members as is appropriate. These members will be designated as comprising the Staff Team and their duties will be documented in the future when and if needed.

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.

Article IV. Privacy

Section 4.01 Piedmont Virtual Airlines Historical Group does not retain any Personally Identifiable Information (PII) outside of what is collected when you sign up for vAMSYS. Please refer to the vAMSYS privacy policy (https://vamsys.io/legal/privacy) for further information on how your information may be collected and used.