the best way to build and ship software Communicating with Issues How GitHub uses GitHub

the best way to build and ship software 2 Cynthia Rich @crichID, Manager of Training

the best way to build and ship software A few logistics 3 ▸ 40 minutes presentation, 10 minutes Q&A ▸ Please ask questions in the GoToWebinar Q&A panel ▸ Recording ▸ Yes, we are! It will be sent via email after the presentation. ▸ Additional Questions ▸ services@github.com

the best way to build and ship software In this session, we will focus on the communication patterns we use here at GitHub. This includes: ▸ Organizing people and projects ▸ Organizing Issues and Pull Requests ▸ Optimizing your written communication ▸ Providing visual structure to support your ideas 4 Our goals

the best way to build and ship software 5 How we communicate

the best way to build and ship software 6 Organizing people

the best way to build and ship software How we think about teams ... 7 Organizational Teams services services-engineering services-tools services-training services-operations Project Teams project-lily-spider Affinity Teams blacktocats Location Teams emea north-carolina }

the best way to build and ship software Liberal @ mentions 8 ▸ Filtering emails is an art form ▸ Direct mention vs. team mention ▸ We unsubscribe

the best way to build and ship software Organizing projects 9

the best way to build and ship software Key ingredients of a project 10 ▸ README.md ▸ CONTRIBUTING.md ▸ ROADMAP.md ▸ ISSUE_TEMPLATE.md ▸ PULL_REQUEST_TEMPLATE.md

the best way to build and ship software 11 Flexible project boards

the best way to build and ship software 12 Organizing issues and pull requests

the best way to build and ship software Using assignees 13 ▸ Assignees are used to indicate who is responsible for the next step. ▸ Changes to assignees are documented in the Issue or Pull Request ▸ Every discussion has an assignee

the best way to build and ship software 14 Another benefit of assignees

the best way to build and ship software Labels should fit the needs of your project 15 Your perfect set of labels

the best way to build and ship software 16 The power of the written word

the best way to build and ship software We write A LOT 17 GitHubbers communicate differently: ▸ We focus on inclusive communication ▸ We rely heavily on async communication ▸ We believe in crafting communication for our future selves

the best way to build and ship software 18

the best way to build and ship software What are you trying to accomplish? 19 Three questions ...

the best way to build and ship software Who are you trying to reach? 20 Three questions ...

the best way to build and ship software What action do you want taken? 21 Three questions ...

the best way to build and ship software ▸ Perception ▸ Investment ▸ Support 22 Always consider your reader

the best way to build and ship software ▸ BLUF ▸ tl;dr ▸ RACI ▸ SCIPAB 23 Useful Techniques

the best way to build and ship software 24 BLUF

the best way to build and ship software 25 tl;dr tl;dr is an acronym for Too Long, Didn’t Read. It is typically used at the beginning or end of a long post to provide a summary for the reader to gauge the level of investment they have in the long form content.

the best way to build and ship software 26 RACI Code RACI Summary Details R Responsible “The doer” The individual who actually completed the task. This is person is responsible for action/implementation of the deliverable. A Accountable “The buck stops here” The individual who is ultimately accountable for the correct and thorough completion of the deliverable. C Consult “In the loop” The individual(s) to be consulted prior to a final decision or action. This is two-way communication. I Inform “Keep in the picture” The individual(s) who need to be informed after a decision or action is taken. This is one-way communication.

the best way to build and ship software 27 SCIPAB

the best way to build and ship software 28

the best way to build and ship software 29 # markdown

the best way to build and ship software 30 Our favorite markdown features ▸ Links & cross references ▸ Tables ▸ Headers ▸ Bold & italics ▸ Quotes ▸ Images ▸ Code blocks ▸ Task lists ▸ Dropdowns

the best way to build and ship software 31 Cross references and links

the best way to build and ship software 32 Tables

the best way to build and ship software 33 Basic formatting

the best way to build and ship software 34 Quoting text

the best way to build and ship software 35 Images

the best way to build and ship software 36 Code blocks

the best way to build and ship software 37 Task lists

the best way to build and ship software 38 Simple dropdowns

the best way to build and ship software The Ultimate Guide to Markdown 39

the best way to build and ship software 40 A few more helpful tips

the best way to build and ship software 41 Reactions and emoji voting

the best way to build and ship software 42 Indicating the scope of the ship

the best way to build and ship software 43 A whole new level

the best way to build and ship software ▸ July 25: Communicating with issues ▸ August 22: Communicating with remote teams ▸ September 26: Managing your teams ▸ October 24: Managing your projects ▸ November 28: Writing documentation for your projects Sign up at services.github.com 44 How GitHub Uses GitHub

the best way to build and ship software Questions? 45