- Notifications
You must be signed in to change notification settings - Fork67
A community version of the "common API" for how the GitHub Engineering organization communicates
License
github/how-engineering-communicates
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
As a company that's been remote-first since day one, GitHub Engineering has learned a lot about how to communicate effectively across time zones, teams, and tools. We've distilled our experience into a set of guidelines that we call "How we communicate". We hope that by sharing our communication practices publicly, we can help other organizations that are embracing remote work or want to improve their collaboration culture.
For more about how we use GitHub to build GitHub, how we turned our guiding communications principles into prescriptive practices to manage our internal communications signal-to-noise ratio, and how you can contribute to the ongoing conversation, check outthis blog post.
This documentation is released underCC-BY-4.0.
About
A community version of the "common API" for how the GitHub Engineering organization communicates
Resources
License
Code of conduct
Security policy
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Uh oh!
There was an error while loading.Please reload this page.
Contributors4
Uh oh!
There was an error while loading.Please reload this page.