Please introduce yourself in the #talk channel. Feel free to ask questions in #howto, or any other channel. Events like WWDC and Google I/O can be discussed before, during and after in #events. The #design and #code channels can be used for design and programming related topics respectively. We’re a friendly bunch, and we’ll do what we can to help.
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in the Aligned Pixels Slack team and related projects 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 behaviour that contributes to creating a positive environment include:
Examples of unacceptable behaviour by participants include:
Project maintainers are responsible for clarifying the standards of acceptable behaviour and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behaviour.
Project maintainers 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 Code of Conduct, or to ban temporarily or permanently any contributor for other behaviours that they deem inappropriate, threatening, offensive, or harmful.
This Code of Conduct applies both within project spaces and in public spaces when an individual is 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. Representation of a project may be further defined and clarified by project maintainers.
Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported by contacting Marc Edwards (@marcedwards) or Matt Kelsh (@matt) via public or private message. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
Project maintainers 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 contributor-covenant.org/version/1/4/code-of-conduct.html. For answers to common questions about this code of conduct, see contributor-covenant.org/faq.