d41b1fbb50
* 🐛 Fix Spelling Issues in Main README.md * 🐛 Fix spelling issues in dev README.md * 🐛 Fix spelling issues in complex_layout README.md * 🐛 Fix spelling issues in macrobenchmarks README.md * 🐛 Fix spelling issues in platform_views_layout README.md * 🐛 Fix spelling issues in test_Apps/stocks README.md * 🐛 Fix spelling issues in bots README.md * ✒ Spell Check dev/ci README.md * ✒ Spell Check dev/ci/docker_linux README.md * ✒ Spell Check dev/devicelab README.md * ✒ Spell Check dev/docs README.md * ✒ Spell Check dev/snippets README.md * ✒ Spell Check dev/snippets/config/templates README.md * ✒ Spell Check dev/tools/gen_keycodes README.md * ✒ Spell Check dev/tools/vitool README.md * ✒ Spell Check examples/catalog README.md * ✒ Spell Check examples/flutter_view README.md * ✒ Spell Check examples/image_list README.md * ✒ Spell Check examples/layers README.md * ✒ Spell Check examples/platform_channel README.md * ✒ Spell Check examples/platform_channel_swift README.md * ✒ Spell Check examples/platform_view README.md * ✒ Spell Check packages/_flutter_web_build_script README.md * ✒ Spell Check packages/flutter_localizations README.md * ✒ Spell Check packages/flutter_tools README.md * ✒ Spell Check CODE_OF_CONDUCT.md * ✒ Spell Check dev/integration_test/android_splash_screens/splash_Screen_load_rotate README.md * ✒ Spell Check dev/integration_test/android_views README.md * ✒ Spell Check dev/integration_tests/flutter_driver_screenshot_test README.md * ✒ Spell Check dev/integration_tests/flutter_gallery README.md * ✒ Spell Check dev/integration_tests/gradle_deprecated_settings README.md * ✒ Spell Check dev/integration_tests/ios_add2app_life_cycle README.md * ✒ Spell Check dev/integration_tests/ios_host_app README.md * ✒ Spell Check dev/integration_tests/ios_platform_view_tests README.md * ✒ Spell Check dev/automated_tests/flutter_test README.md * ✒ Spell Check .github/PULL_REQUEST_TEMPLATE.md * ✒ Spell Check .hithub/ISSUE_TEMPLATE/ACTIVATION.md * ✒ Spell Check .github/ISSUE_TEMPLATE/BUG.md * ✒ Spell Check .github/ISSUE_TEMPLATE/feature_request.md * ✒ Spell Check .github/ISSUE_TEMPLATE/performance_others.md * ✒ Spell Check .github/ISSUE_TEMPLATE/performance_speed.md * ✒ Spell Check packages/flutter_tools/doc/daemon.md * ✒ Spell Check packages/flutter_tools/fuchsia_enrtypoint_shim/README.md * ✒ Minimize line to 80 columns * ✒ Minimize line to 80 columns * ✒ Fix Typo * ✒ Chnaged numbers to 1 for testing purposes * ✒ Changed numbers to 1 for testing purposes * ❌ Remove 'a' which is a typo * ✒ Change a sentence to be better * ✒ Remove 'a' which is a typo * ✒ Fix small issue * ✒ Fix small typo * ✒ Fix some typos * ❌ Remove trailing space * ❌ Remove trailing space * 🐛 Fix small typo * ✒ Fix Typo * 🐛 Fix small bug
50 lines
2.7 KiB
Markdown
50 lines
2.7 KiB
Markdown
# Code of conduct
|
|
|
|
We expect Flutter's contributors to act professionally and respectfully, and
|
|
we expect our social spaces to be safe and dignified environments.
|
|
|
|
Specifically:
|
|
|
|
* Respect people, their identities, their culture, and their work.
|
|
* Be kind. Be courteous. Be welcoming.
|
|
* Listen. Consider and acknowledge people's points before responding.
|
|
|
|
Should you experience anything that makes you feel unwelcome in Flutter's
|
|
community, please contact [conduct@flutter.dev](mailto:conduct@flutter.dev)
|
|
or, if you prefer, directly contact someone on the team, for instance
|
|
[Hixie](mailto:ian@hixie.ch) or [Tim](mailto:timsneath@google.com). We will
|
|
not tolerate harassment from anyone in Flutter's community, even outside
|
|
of Flutter's public communication channels.
|
|
|
|
## Conflict resolution
|
|
|
|
When multiple contributors disagree on the direction for a particular
|
|
patch or the general direction of the project, the conflict should be
|
|
resolved by communication. The people who disagree should get
|
|
together, try to understand each other's points of view, and work to
|
|
find a design that addresses everyone's concerns.
|
|
|
|
This is usually sufficient to resolve issues. If you cannot come to an
|
|
agreement, ask for the advice of a more senior member of the team.
|
|
|
|
Be wary of agreement by attrition, where one person argues a point
|
|
repeatedly until other participants give up in the interests of moving
|
|
on. This is not conflict resolution, as it does not address everyone's
|
|
concerns. Be wary of agreement by compromise, where two good competing
|
|
solutions are merged into one mediocre solution. A conflict is
|
|
addressed when the participants agree that the final solution is
|
|
_better_ than all the conflicting proposals. Sometimes the solution is
|
|
more work than either of the proposals. [Embrace the yak
|
|
shave](https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#lazy-programming).
|
|
|
|
## Questions
|
|
|
|
It's always ok to ask questions. Our systems are large, and nobody will be
|
|
an expert in all the systems. Once you find the answer, document it in
|
|
the first place you looked. That way, the next person will be brought
|
|
up to speed even quicker.
|
|
|
|
|
|
|
|
Source: _[xkcd, May 2012](https://xkcd.com/1053/)_
|