Our bylaws and code of conduct in full: how FDXvirtual operates, what we expect from members and how we handle conduct issues.
Section 1.01 This organization is named FDXvirtual, sometimes shortened to FDXv.
Section 1.02 This organization is not affiliated with Federal Express (FedEx Express) or any of their subsidiaries, nor with any other airline or aviation companies. All flight and aeronautical information found through membership in the club is for entertainment use only. For any real-world flight operations consult the appropriate procedures and regulations as approved by your local regulatory body.
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 like-minded aviation enthusiasts who enjoy enriching their flight simulation hobby through simulating the operations of a real-world airline.
Section 2.01 Membership in FDXvirtual is open to any adult aged 18 or older 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).
Section 2.02 Membership is fully voluntary.
Section 2.03 Membership is at the sole discretion of the FDXvirtual administration team.
Section 2.04 All members are expected to abide by these bylaws and by all rules, codes of conduct and community guidelines posted in any FDXvirtual websites, chat servers, forums and other community spaces.
Section 2.05 All members are expected to follow whatever posted rules, codes of conduct and community guidelines are found on all vAMSYS websites, chat servers, forums and other community spaces.
Section 2.06 All members are expected to follow whatever posted rules, codes of conduct and community guidelines are found on all VATSIM, IVAO and PilotEdge websites, chat servers, forums and other community spaces.
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 FDXvirtual requires each member to file 1 PIREP via our automatic flight tracking software, Pegasus, at least once every 120 days with a 10-day grace period. New members are required to file 1 PIREP in their first 10 days after joining. Failing to meet these requirements will result in the user’s account being deactivated, but not removed.
Section 2.09 If your account is deactivated under Section 2.08, you may rejoin in the future by reactivating your account or by contacting the admin team and requesting that you be reactivated.
Section 3.01 The administration team of the organization is composed of five members.
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 The duties of the administration team are ad hoc and are coordinated internally and do not consist of any specifically set roles.
Section 3.04 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 Sections 2.05 and 2.06.
Section 3.05 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.06 Each administration team member can individually enforce our bylaws and community guidelines on any FDXvirtual websites, chat servers, forums and other community spaces, without waiting for the other four admins, up to and including banning from membership any offending party.
Section 3.07 As required, from time to time, the administration team may delegate some tasks to certain members as is appropriate. These duties will be documented in the future when and if needed.
Section 3.08 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 Personally Identifiable Information (PII) from users when they sign up for an account. This information is stored in vAMSYS databases to which FDXvirtual has limited access. Please refer to the vAMSYS privacy policy for further information on how your information may be collected, used and removed. vAMSYS is the data controller of data input to vAMSYS systems; FDXvirtual is a data processor. If a user wants to exercise their rights with regard 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 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.
Examples of behavior that contributes to creating a positive environment include:
Examples of unacceptable behavior by participants include:
The administration team is responsible for clarifying the standards of acceptable behavior and is 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, and to ban, temporarily or permanently, any contributor for 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.
For answers to common questions about this code of conduct, see the Contributor Covenant FAQ.