Rocket Science On Github
summary
A university rocket project with about 50 to 100 contributors moves its code and docs onto GitHub, consolidating 45 repositories and using read the docs and Travis CI for automated docs and tests. The 12–13 foot rocket reaches roughly 5 kilometers in 30 seconds and just breaks Mach 1, so tracking firmware, boards and test data matters. Major pain points are binary CAD and board files from SolidWorks and Eagle that lack useful diffs, and large binary test data blobs that bloat repos.
AI-written summary · about
chapters (12)
- 0:00ROCKET SCIENCE ON GITHUB
- 3:02WHY ROCKETS
- 4:22PLAN OF ATTACK
- 12:51INITIAL REACTIONS
- 14:12READ THE DOCS
- 14:59CAPSTONES
- 21:45TEST DATA
- 26:59RISE OF THE ISSUE TRACKER
- 34:27LAUNCHES!
- 38:02SECRET WEAPONS
- 40:23MISSING PIECES
- 43:06META
related talks
43mHow Rocket Science Can Help You Build Your App
57mOpen Source at commercial organisations
23mSimplify Challenging Software Problems with Rocket Science
42mHow Github (No Longer) Works
01h 06mHow GitHub delivers GitHub using GitHub
46mBuilding Developer Community One Pull Request at a Time
01mIdan Gazit, GitHub, ETLS Vegas (07)
43mOpen Source Robotics Where we are and where we are heading