cakephp / code-of-conduct

Contributor Code of Conduct

CakePHP is a rapid development framework for PHP which uses commonly known design patterns like Associative Data Mapping, Front Controller, and MVC. Our primary goal is to provide a structured framework that enables PHP users at all levels to rapidly develop robust web applications, without any loss to flexibility.

Installing CakePHP via Composer

You can install CakePHP into your project using Composer. If you're starting a new project, we recommend using the app skeleton as a starting point. For existing applications you can run the following:

composer require cakephp/cakephp

For details on the (minimum/maximum) PHP version see version map.

Running Tests

Assuming you have PHPUnit installed system wide using one of the methods stated here, you can run the tests for CakePHP by doing the following:

1. Copy phpunit.xml.dist to phpunit.xml.
2. Add the relevant database credentials to your phpunit.xml if you want to run tests against a non-SQLite datasource.
3. Run phpunit.

Some Handy Links

• CakePHP - The rapid development PHP framework.
• CookBook - The CakePHP user documentation; start learning here!
• API - A reference to CakePHP's classes.
• Awesome CakePHP - A list of featured resources around the framework.
• Plugins - A repository of extensions to the framework.
• The Bakery - Tips, tutorials and articles.
• Community Center - A source for everything community related.
• Training - Join a live session and get skilled with the framework.
• CakeFest - Don't miss our annual CakePHP conference.
• Cake Software Foundation - Promoting development related to CakePHP.

Get Support!

• Slack - Join us on Slack.
• Discord - Join us on Discord.
• #cakephp on irc.freenode.net - Come chat with us, we have cake.
• Forum - Official CakePHP forum.
• GitHub Issues - Got issues? Please tell us!
• Roadmaps - Want to contribute? Get involved!

Contributing

• CONTRIBUTING.md - Quick pointers for contributing to the CakePHP project.
• CookBook "Contributing" Section - Details about contributing to the project.

Security

If you’ve found a security issue in CakePHP, please use the procedure described in SECURITY.md.

code-of-conduct's Issues

Translations of our CoC

What about those?

In case there are none(?) I am willing to contribute the German one.

RFC: Add language as a discrimination factor

Helloes,

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

• http://todogroup.org/opencodeofconduct/

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.

CakeFest - Code of Conduct

I'll just leave this here... http://cakefest.org/conduct

🍰 👍

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].```