Code Monkey home page Code Monkey logo

code-of-conduct's Introduction

CakePHP Contributor Code of Conduct

See CODE_OF_CONDUCT.md.

This code of conduct applies to all of the projects under the CakePHP organization on GitHub and the CakePHP community at large (IRC, mailing lists, Google+, Twitter, etc.).

See the contributing guidelines and the CakePHP Cookbook for technical details of contributing to CakePHP or its related projects.

Events

If you are running a CakePHP meetup, conference, user group, or other type of event, we encourage you to adopt and provide an appropriate code of conduct. The confcodeofconduct.com template is a good starting point. You should also provide contact information for attendees to get help or report a violation.

For more on adopting a code of conduct, see Ashe Dryden's FAQ.

Credits

Based on the Contributor Covenant by Coraline Ada Ehmke.

If you have suggestions to improve this code of conduct, please submit an issue or PR.

code-of-conduct's People

Contributors

beporter avatar phpnut avatar tuffz avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

code-of-conduct's Issues

RFC: Context

I'd like to make the context a bit more specific.

  • 1st suggestion: A code of conduct taken seriously (and I do) should only govern community. What you do in your private matters is something else.
  • 2nd change: Spelling correction (harrassment => harassment).
  • 3rd suggestion: "other unprofessional conduct" is very unspecific. There are two ways to fix this. Add similar instead of other. By doing so you define unprofessional conduct as being similar to personal attacks, trolling, public or private harassment. "Other unprofessional" conduct may be for instance posting cat pictures (I am even annoyed but you are free to do so!) while "similar unprofessional conduct" would not include cat pictures.

Suggested changes in bold/strike-through:

As contributors and maintainers of the CakePHP project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities related to this community.

Communication through any of CakePHP's channels (GitHub, IRC, mailing lists, Google+, Twitter, etc.) must be constructive and never resort to personal attacks, trolling, public or private harrassment, insults, or other similar unprofessional conduct.

We promise to extend courtesy and respect to everyone involved in this project regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to the CakePHP project to do the same.

If any member of the community violates this code of conduct, the maintainers of the CakePHP project may take action, removing issues, comments, and PRs or blocking accounts as deemed appropriate.

If you are subject to or witness unacceptable behavior, or have any other concerns, please email us at [email protected].```

RFC: Add language as a discrimination factor

Helloes,

language is a big problem and also a discrimination factor.
Some CoCs specify language:

I'd like to see twofold:

  • An official stance on language, e.g. that all support channels, source code documentation and the book is only offering English as guaranteed but...
  • That other languages are respected on XY
  • That no discrimination should happen because of language barriers. As this DID IMHO happen a few month ago I see this as a case.

So there needs to be a concise sentence in essence saying: Development and communication is primarily English (practicability) but other languages are respected and discrimination because of weak English is not okay.

The implications are that the core team should not be obligated to translate docs but for instance there should be done as much as possible to include non native speakers for instance at conferences, through subtitles in videos, by welcoming their chatting in the official channel and on google groups (TBD) etc.

This is a hard issue because it is a hard problem because de facto discrimination and practicability go hand in hand.

I am not strongly pushing this, because it is hard to solve as a concise and precise don't do rule, maybe it should be a sentence in the preamble adding to the spirit of our CoC instead... but see it as a primary exclusion factor and problem.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.