Ian Hickson | cf2fba7 | 2018-11-06 13:41:09 -0800 | [diff] [blame] | 1 | # Code of conduct |
| 2 | |
| 3 | We expect Flutter's contributors to act professionally and respectfully, and |
| 4 | we expect our social spaces to be safe and dignified environments. |
| 5 | |
| 6 | Specifically: |
| 7 | |
| 8 | * Respect people, their identities, their culture, and their work. |
| 9 | * Be kind. Be courteous. Be welcoming. |
| 10 | * Listen. Consider and acknowledge people's points before responding. |
| 11 | |
| 12 | Should you experience anything that makes you feel unwelcome in Flutter's |
Ian Hickson | 8fe7643 | 2019-08-25 10:46:02 -0700 | [diff] [blame] | 13 | community, please contact [conduct@flutter.dev](mailto:conduct@flutter.dev) |
| 14 | or, if you prefer, directly contact someone on the team, for instance |
| 15 | [Hixie](mailto:ian@hixie.ch) or [Tim](mailto:timsneath@google.com). We will |
Phil Quitslund | 919f457 | 2019-01-03 12:51:45 -0800 | [diff] [blame] | 16 | not tolerate harassment from anyone in Flutter's community, even outside |
Ian Hickson | cf2fba7 | 2018-11-06 13:41:09 -0800 | [diff] [blame] | 17 | of Flutter's public communication channels. |
| 18 | |
| 19 | ## Conflict resolution |
| 20 | |
| 21 | When multiple contributors disagree on the direction for a particular |
| 22 | patch or the general direction of the project, the conflict should be |
| 23 | resolved by communication. The people who disagree should get |
| 24 | together, try to understand each other's points of view, and work to |
| 25 | find a design that addresses everyone's concerns. |
| 26 | |
| 27 | This is usually sufficient to resolve issues. If you cannot come to an |
| 28 | agreement, ask for the advice of a more senior member of the team. |
| 29 | |
| 30 | Be wary of agreement by attrition, where one person argues a point |
| 31 | repeatedly until other participants give up in the interests of moving |
| 32 | on. This is not conflict resolution, as it does not address everyone's |
| 33 | concerns. Be wary of agreement by compromise, where two good competing |
| 34 | solutions are merged into one mediocre solution. A conflict is |
| 35 | addressed when the participants agree that the final solution is |
| 36 | _better_ than all the conflicting proposals. Sometimes the solution is |
| 37 | more work than either of the proposals. [Embrace the yak |
| 38 | shave](https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#lazy-programming). |
| 39 | |
| 40 | ## Questions |
| 41 | |
Todd Volkert | 8470b4a | 2018-11-20 22:25:03 -0800 | [diff] [blame] | 42 | It's always ok to ask questions. Our systems are large, and nobody will be |
Ian Hickson | cf2fba7 | 2018-11-06 13:41:09 -0800 | [diff] [blame] | 43 | an expert in all the systems. Once you find the answer, document it in |
| 44 | the first place you looked. That way, the next person will be brought |
| 45 | up to speed even quicker. |
| 46 | |
Yazeed Al-Khalaf | d41b1fb | 2020-07-23 04:23:47 +0300 | [diff] [blame] | 47 |  |
Ian Hickson | e833a58 | 2019-08-20 11:00:21 -0700 | [diff] [blame] | 48 | |
| 49 | Source: _[xkcd, May 2012](https://xkcd.com/1053/)_ |