Striking Gold: Building software better, together

Transcript

1. 1.

   Building Software Better, Together Brian Doll @briandoll Striking Gold!

2. 2.

   California Gold Rush

3. 3.

   Gold Ru Technology Gold Rush

4. 4.

   Every company is a software company

5. 5.

   FTP CVS Perforce Subversion Git GitHub ’95 ’99 ’01 ’03

   ’08 ’08 My personal journey through software repositories...
6. 6.

   "organizations which design systems ... are constrained to produce designs

   which are copies of the communication structures of these organizations" Conway’s Law:
7. 7.

   The GitHub Way

8. 8.

   The GitHub Way run your company like an open source

   project
9. 9.

   collaboration without coordination The GitHub Way

10. 10.

    electronic The GitHub Way

11. 11.

    available via URL The GitHub Way

12. 12.

    asynchronous The GitHub Way

13. 13.

    lock free The GitHub Way

14. 14.

    The best software is made by happy people working together

15. 15.

    Process vs. Vision

16. 16.

    Process

17. 17.

    Vision

18. 18.

    Important to GitHub My Interests My Skills What I work

    on
19. 19.

    None
20. 20.

    issues / features don’t get worked on? What happens when...

21. 21.

    a day in the life...

22. 22.

    everyone ships, all the time

23. 23.

    Chris (new employee): How much is the ideal githubber expected

    to ship when operating at full awesomeness?
24. 24.

    Chris (new employee): How much is the ideal githubber expected

    to ship when operating at full awesomeness? Lee: Whatever makes you feel good, man
25. 25.

    The best software is made by happy people working together

26. 26.

    GitHub API : developer.github.com GitHub Archive : githubarchive.org GitHub data

    on Google BigQuery Questions: data@github.com Mining GitHub Data
27. 27.

    Team / Discussions •CommitCommentEvent •PullRequestEvent •PullRequestReviewCommentEvent •MemberEvent Development activities •

    CreateEvent • DeleteEvent • DownloadEvent • ForkEvent • ForkApplyEvent • GistEvent • GollumEvent • PublicEvent • PushEvent Social activities •FollowEvent •IssueCommentEvent •IssuesEvent •TeamAddEvent •WatchEvent Events on GitHub
28. 28.

    Our internal social graph by Derek Greentree, GitHub

29. 29.

    Our internal social graph 688 repositories 169 people

30. 30.

    Interactions were counted between two users when: • One user

    @mentions another in a pull request, issue, or commit comment • A user comments on another's pull request or issue Our internal social graph
31. 31.

    None
32. 32.

    • 25%: 6 • 50%: 25.5 • 75%: 59.25 Quantiles

    Team size at GitHub
33. 33.

    GitHub Data Challenge

34. 34.

    Source of commits. The more commits come from pull requests,

    the more open the project process. Percentage of issue comments and commenters coming from the project community (i.e. users with no commit rights to the main repo) Dr. Georgios Gousios, GHTorrent
35. 35.

    Dr. Georgios Gousios, http://ghtorrent.org/netviz/

36. 36.

    Huang Liang, Programming Language Activity Trends

37. 37.

    JeongHoon Byun , http://sideeffect.kr/popularconvention

38. 38.

    bbaudry/GitWorks

39. 39.

    Eduarda Mendes Rodrigues, http://zoom.it/kCsU#full

40. 40.

    Matthew Willson, mjwillson/ProgLangVisualise

41. 41.

    None
42. 42.

    Jean-Noël Avila, fork to pull request latency

43. 43.

    Geeksta, http://bit.ly/geeksta : Anger in commit messages

44. 44.

    Geeksta, http://bit.ly/geeksta : joy in commit messages

45. 45.

    None
46. 46.

    Software is eating the world. Let’s eat it faster!