dryhurst / code-of-conduct

code of conduct for all phpfmt projects

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Phpfmt Bylaw

In the interest of fostering an open and welcoming environment, we, the members of this project, pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, personal discreet beliefs, race, religion, or sexual identity and orientation.

Membership

Membership of this project are reserved for:

    1. Person who has publicly declared the decision to join the project as Member; and
    1. Person who has contributed with source code, with accepted pull requests or provided support to users in support channels (Github Issues);

Persons are considered Senior Members if they are one of the owners of source code repository account (Github).

Persons who are neither Member nor Senior Member are considered Aliens.

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
  • Being discreet and avoid confrotation on controversial personal beliefs

Examples of unacceptable behavior by Members and Aliens 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
  • Derailing the harmony of the project and its relationships through off-topic debates in any space
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Responsibilities

Members are 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.

Members have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Bylaw, or to ban temporarily or permanently any Alien for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Bylaw applies both within project spaces and in public spaces when an Alien or a Member are representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Members at this Bylaw support service (Github Issues). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Complaints confidentiality is guaranteed as long as it is not required by complainer the impeachment of one or any project members.

Impeachment

Aliens cannot propose an Impeachment of a Member.

Proposition for Member Impeachment must be proposed by a Member, in capacity of Reporter of Impeachment, and with approval of the simple majority of Senior Members.

Propositions for Member Impeachment must be made public, and all identities disclosed and publicly confirmed by the Reporter of Impeachment.

All parties cited in an Proposition for Member Impeachment have the right to present, at once, Evidences and Arguments to all Members in the date set by Reporter of Impeachment.

Reporter of Impeachment must define the date of delivery of Evidences and Arguments no later than 14 days counting from approval of Proposition for Member Impeachment.

Reporter of Impeachment must define the date of Voting of Impeachment no later than 7 days counting from the date of delivery of Evidences and Arguments.

Reporter of Impeachment must write and make public the Terms of Impeachment which content must state: Members to be impeached, violations, facts, evidences and arguments.

If the proposed Terms of Impeachment lacks any of its mandatory elements, it is deemed null and the Impeachment is nulled, in favor of the Member to be impeached.

The Quorum for Voting of Impeachment comprises all Senior Members, except those, if any, whose Impeachment is being sought after.

The object of Voting of Impeachment is the Terms of Impeachment.

The Voting of Impeachment question must be: "Do you vote for the Impeachment as stated by the presented Terms of Impeachment?".

The Voting of Impeachment responses must be Yes or No.

The Voting of Impeachment is secret, and its results are public.

The Voting of Impeachment will result in an Impeached Member if, and only if, the Quorum for Voting of Impeachment vote unanimously for Yes.

Absent Members in Voting of Impeachment do not count for establishing unanimity, nor as No votes.

Senior Members must validate the result of Voting of Impeachment and notify the Member about the result of the Impeachment.

Impeachment means the loss of the state of Member.

All Impeachment information, documents and vote results must be publicized by Reporter of Impeachment in source code repository for this Bylaw.

Amending

Amendments to this Bylaw must be proposed by Senior Members and unanimously approved by Senior Members.

Senior Members must not deliberate about or seek voting for Amendments which diminish the powers of Senior Members.

Senior Members must not deliberate about or seek voting for Amendments which change the rules of Impeachment.

All approved Amendments must be publicized in source code repository for this Code of Conduct, along with the votes of the Senior Members.

Ratification

This Code of Conduct is valid from the day it is published by the creator of the phpfmt, Carlos Cirello.

Attribution

This Bylaw is based on the Contributor Covenant, version 1.4.

About

code of conduct for all phpfmt projects