Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Collaboration Behind your Firewall
Search
Brent Beer
October 16, 2013
0
56
Collaboration Behind your Firewall
Some helpful tips and patterns to help make collaboration within your company on GitHub easier.
Brent Beer
October 16, 2013
Tweet
Share
More Decks by Brent Beer
See All by Brent Beer
How GitHub Does Devops
brntbeer
0
170
Tips and Tricks: Gotta Git Them All
brntbeer
3
500
Pull Request, code review and the GitHub Flow
brntbeer
0
240
Everything I wish I knew when I started using GitHub
brntbeer
1
7.3k
Fast Deployment and Monitoring For HelsinkiJS
brntbeer
1
270
Fast Deployment and Monitoring
brntbeer
1
120
How GitHub Builds Products
brntbeer
2
180
Collaborative Teaching for More Effective Learning
brntbeer
1
180
Featured
See All Featured
Building Adaptive Systems
keathley
38
2.3k
Code Review Best Practice
trishagee
64
17k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
226
22k
Product Roadmaps are Hard
iamctodd
PRO
49
11k
How to train your dragon (web standard)
notwaldorf
88
5.7k
Intergalactic Javascript Robots from Outer Space
tanoku
268
27k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
169
50k
Fontdeck: Realign not Redesign
paulrobertlloyd
82
5.2k
Faster Mobile Websites
deanohume
305
30k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
42
2.2k
Keith and Marios Guide to Fast Websites
keithpitt
409
22k
Unsuck your backbone
ammeep
668
57k
Transcript
Collaboration Behind Your Firewall
@brntbeer Brent Beer
THE BEST WAY TO COLLABORATE
Vision
We like to embrace discoverability
Over Communicate
Explore and Find Interesting Things
Keep Barrier of Entry Low
Talk, A lot
ISSUES
ISSUES ARE SIMPLE
None
ISSUES CAN BE ABOUT ANYTHING FEATURES BUGS
OFFICE STUFF STRATEGY ? QUESTIONS EXAMPLES DISCUSSIONS TODO LISTS
WE USE ISSUES TO: REPORT BUGS
WE USE ISSUES TO: DISCUSS NEW FEATURES
WE USE ISSUES TO: MANAGE TODO LISTS
REFERENCE OTHER ISSUES
CODE REVIEW
USE PULL REQUESTS
PULL REQUESTS ARE HOW WE DO CODE REVIEW
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
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
None
ANATOMY OF PULL REQUESTS TITLE DESCRIPTION DISCUSSION COMMIT COMMIT COMMIT
COMMIT COMMIT DISCUSSION DISCUSSION COMMIT COMMIT COMMIT COMMIT COMMIT DISCUSSION
Current status Where the change is coming from See what
people are saying See all the commits Check out the diff
REASONS PULL REQUESTS ARE AWESOME Asynchronous: No meetings. Notifications: Let
GitHub email you. Accessible: Let everyone work together. Historical: Preserve the record.
@mentions
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?”
@mention TEAMS @jch @shayfrendt @chrishunt @achiu @demonbane @ericgerhardt @danishkhan @dsorkin
@jessla @sachinr @leereilly
emoji are words too! :+1: :SHIPIT: :FIRE: I like it!
:HEART: Ready to merge Kill it Feelings
Don't Make It Hard, Talk it Out
Explore
SEARCH
Find whatever it is you are looking for
Real Big Microscopes
REGULAR SEARCH
REGULAR SEARCH
ADVANCE SEARCH
ADVANCE SEARCH
HELP WANTED Creating a help wanted repository can help
people find things to work on
HELP WANTED
TRENDING
RENDER
None
None
Sean Bryant (@sbryant) was able to look around at the
tools
None
Ben Balter (@benbalter) also stumbled upon Render
None
None
None
None
None
None
Make Projects Discoverable, and Go Looking
Make Geing Started Easy
README
Welcome Mat
None
None
None
None
None
SCRIPTS
Quick Steps
How do you share?
culture-tools
culture-tools
culture-tools
But wait, there's one more thing
BOXEN
Boxen
boxen rails
boxen rails boxen github
boxen rails boxen github boxen training
What is a Boxen?
None
None
None
None
MANIFESTS
MANIFESTS
MANIFESTS
Why Boxen At All?
Why Boxen At All?
boxen.github.com #boxen on irc
If It's Easy To Get Started, Many People Will Help
Your Vision
Talk to people, stay open
Take A Look Around
Lower The Friction
Start Collaborating Thanks Brent Beer
[email protected]
@brntbeer
Resources hp://tomayko.com/writings/adopt-an- open-source-process-constraints hp://tom.preston-werner.com/ 2011/11/22/open-source-everything.html hp://tomayko.com/writings/ management-style