CocoaPods strongly values contributors from anywhere, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. As a result, the CocoaPods team has agreed to and enforces this code of conduct in order to provide a harassment-free experience for everyone who participates in the development of CocoaPods.
Harassment in code and discussion or violation of physical boundaries is completely unacceptable anywhere in CocoaPods’ codebases, issue trackers, Slack, Campfire, mailing lists, meetups, and other events. Violators will be warned and then blocked or banned by the core team at or before the 3rd violation.
Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, sexual images, deliberate intimidation, stalking, sustained disruption, and unwelcome sexual attention.
Individuals asked to stop any harassing behavior are expected to comply immediately.
Maintainers, including the core team, are also subject to the anti-harassment policy.
If anyone engages in harassing behavior, including maintainers, we may take appropriate action, up to and including warning the offender, deletion of comments, removal from the project’s codebase and communication systems, and escalation to Github support.
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of the core team or email the core team immediately.
We expect everyone to follow these rules anywhere in the CocoaPods project’s codebases, issue trackers, IRC channel, group chat, and mailing lists.
This code of conduct applies both within project spaces and in public spaces when an individual is actively representing the project or its community. Due to their strong association with the project, core contributors are always seen as actively representing it.
Finally, don't forget that it is human to make mistakes! We all do. Let’s work together to help each other, resolve issues, and learn from the mistakes that we will all inevitably make from time to time.
Thanks to the Bundler Code of Conduct, JSConf Code of Conduct, Fedora Code of Conduct, and Contributor Covenant, version 1.2.0 for inspiration and ideas.