Your SlideShare is downloading. ×
Collaboration Behind Your Firewall - Brent Beer (GitHub)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Collaboration Behind Your Firewall - Brent Beer (GitHub)

385
views

Published on

Presented at JAX London 2013 …

Presented at JAX London 2013

Many people think that because they have a full time job they won't be able to work on any open source projects. Open source works through similarly-aligned teams and individuals, so why do you think of your job and open source as two different things? Treating your internal projects as if they were open source allows more freedom in how you work. Maybe you are looking for a way to spend a few days a week on one internal tool, and the rest on another. Do you know of a project that is missing instructions on how to get started? Fix that!

Published in: Technology, News & Politics

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
385
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
10
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1.  Collaboration Behind Your Firewall
  • 2. Brent Beer @brntbeer
  • 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
  • 12. ISSUES CAN BE ABOUT ANYTHING    ? TODO LISTS OFFICE STUFF BUGS QUESTIONS  EXAMPLES  STRATEGY  DISCUSSIONS  FEATURES
  • 13. WE USE ISSUES TO: REPORT BUGS
  • 14. WE USE ISSUES TO: DISCUSS NEW FEATURES
  • 15. WE USE ISSUES TO: MANAGE TODO LISTS
  • 16. REFERENCE OTHER ISSUES
  • 17. CODE REVIEW
  • 18.  USE PULL REQUESTS
  • 19. PULL REQUESTS ARE HOW WE DO CODE REVIEW
  • 20. n n n n n n n n n n Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Code Discussion Discussion Strategy Discussion Discussion Features Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Dis Dis Dis Dis Dis Dis Dis Dis Dis Dis
  • 21. n n n n n n n n n n Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Review Diffs Reference Issues Write Comments Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Discussion Dis Dis Dis Dis Dis Dis Dis Dis Dis Dis
  • 22. ANATOMY OF PULL REQUESTS TITLE DESCRIPTION COMMIT COMMIT COMMIT COMMIT COMMIT DISCUSSION DISCUSSION DISCUSSION COMMIT COMMIT COMMIT COMMIT COMMIT DISCUSSION
  • 23. Current status Where the change is coming from See what people are saying See all the commits Check out the diff
  • 24. REASONS PULL REQUESTS ARE AWESOME Asynchronous: No meetings. Accessible: Let everyone work together. Notifications: Let GitHub email you. Historical: Preserve the record.
  • 25. @mentions
  • 26. 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?”
  • 27. @mention TEAMS @jch @shayfrendt @chrishunt @achiu @leereilly @demonbane @ericgerhardt @danishkhan @dsorkin @jessla @sachinr
  • 28. emoji are words too! :+1: :SHIPIT: :FIRE: :HEART: I like it! Ready to merge Kill it Feelings
  • 29. Don't Make It Hard, Talk it Out
  • 30.  Explore
  • 31. SEARCH
  • 32. Find whatever it is you are looking for
  • 33. Real Big Microscopes
  • 34.  REGULAR SEARCH
  • 35.  REGULAR SEARCH
  • 36.  ADVANCE SEARCH
  • 37.  ADVANCE SEARCH
  • 38.  HELP WANTED Creating a help wanted repository can help people find things to work on
  • 39.  HELP WANTED
  • 40. TRENDING
  • 41. RENDER
  • 42. Sean Bryant (@sbryant) was able to look around at the tools
  • 43. Ben Balter (@benbalter) also stumbled upon Render
  • 44. Make Projects Discoverable, and Go Looking
  • 45.  Make Geing Started Easy
  • 46. README
  • 47. Welcome Mat
  • 48. SCRIPTS
  • 49. Quick Steps
  • 50. How do you share?
  • 51. culture-tools
  • 52. culture-tools
  • 53. culture-tools
  • 54. But wait, there's one more thing
  • 55. BOXEN
  • 56. Boxen
  • 57. boxen rails
  • 58. boxen rails boxen github
  • 59. boxen rails boxen github boxen training
  • 60. What is a Boxen?
  • 61. MANIFESTS
  • 62. MANIFESTS
  • 63. MANIFESTS
  • 64. Why Boxen At All?
  • 65. Why Boxen At All?
  • 66. boxen.github.com #boxen on irc
  • 67. If It's Easy To Get Started, Many People Will Help
  • 68.  Your Vision
  • 69. Talk to people, stay open
  • 70. Take A Look Around
  • 71. Lower The Friction
  • 72. Start Collaborating Thanks Brent Beer brent@github.com @brntbeer
  • 73. Resources hp://tomayko.com/writings/ management-style hp://tomayko.com/writings/adopt-anopen-source-process-constraints hp://tom.preston-werner.com/ 2011/11/22/open-source-everything.html