Collaboration Behind your Firewall

Some helpful tips and patterns to help make collaboration within your company on GitHub easier.

Transcript

1.  Collaboration Behind Your Firewall
2. @brntbeer Brent Beer
3. THE BEST WAY TO COLLABORATE
4. Vision 
5. We like to embrace discoverability
6. Over Communicate
7. Explore and Find Interesting Things
8. Keep Barrier of Entry Low
9. Talk, A lot    
10. ISSUES
11. ISSUES ARE SIMPLE
13. ISSUES CAN BE ABOUT ANYTHING  FEATURES  BUGS  OFFICE STUFF  STRATEGY ? QUESTIONS  EXAMPLES  DISCUSSIONS  TODO LISTS
14. WE USE ISSUES TO: REPORT BUGS
15. WE USE ISSUES TO: DISCUSS NEW FEATURES
16. WE USE ISSUES TO: MANAGE TODO LISTS
17. REFERENCE OTHER ISSUES
18. CODE REVIEW
19. USE PULL REQUESTS 
20. PULL REQUESTS ARE HOW WE DO CODE REVIEW
21. Code Discussion Strategy Discussion Features Discussion Discussion Discussion Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Discussion n Discussion Dis Discussion n Discussion Dis Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis
22. Discussion Discussion Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Discussion n Discussion Dis Discussion n Discussion Dis Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Discussion Discussion Discussion n Discussion Dis Review Diffs Reference Issues Write Comments
24. ANATOMY OF PULL REQUESTS TITLE DESCRIPTION DISCUSSION COMMIT COMMIT COMMIT COMMIT COMMIT DISCUSSION DISCUSSION COMMIT COMMIT COMMIT COMMIT COMMIT DISCUSSION
25. Current status Where the change is coming from See what people are saying See all the commits Check out the diff
26. REASONS PULL REQUESTS ARE AWESOME Asynchronous: No meetings. Notifications: Let GitHub email you. Accessible: Let everyone work together. Historical: Preserve the record.
27. @mentions
28. WE USE @mentions ALL THE TIME “Look at my Pull Request.” “You’re the expert on this.” “I need another opinion.” “Did you break this?”
29. @mention TEAMS @jch @shayfrendt @chrishunt @achiu @demonbane @ericgerhardt @danishkhan @dsorkin @jessla @sachinr @leereilly
30. emoji are words too! :+1: :SHIPIT: :FIRE: I like it! :HEART: Ready to merge Kill it Feelings
31. Don't Make It Hard, Talk it Out
32. Explore 
33. SEARCH
34. Find whatever it is you are looking for
35. Real Big Microscopes
36.  REGULAR SEARCH
37.  REGULAR SEARCH
38.  ADVANCE SEARCH
39.  ADVANCE SEARCH
40.  HELP WANTED Creating a help wanted repository can help people find things to work on
41.  HELP WANTED
42. TRENDING
43. RENDER
46. Sean Bryant (@sbryant) was able to look around at the tools
48. Ben Balter (@benbalter) also stumbled upon Render
55. Make Projects Discoverable, and Go Looking
56. Make Geing Started Easy 
57. README
58. Welcome Mat
64. SCRIPTS
65. Quick Steps
66. How do you share?
67. culture-tools
68. culture-tools
69. culture-tools
70. But wait, there's one more thing
71. BOXEN
72. Boxen
73. boxen rails
74. boxen rails boxen github
75. boxen rails boxen github boxen training
76. What is a Boxen?
81. MANIFESTS
82. MANIFESTS
83. MANIFESTS
84. Why Boxen At All?
85. Why Boxen At All?
86. boxen.github.com #boxen on irc
87. If It's Easy To Get Started, Many People Will Help
88. Your Vision 
89. Talk to people, stay open
90. Take A Look Around
91. Lower The Friction
92. Start Collaborating Thanks Brent Beer brent@github.com @brntbeer
93. Resources hp://tomayko.com/writings/adopt-an- open-source-process-constraints hp://tom.preston-werner.com/ 2011/11/22/open-source-everything.html hp://tomayko.com/writings/ management-style