Skip to content

Instantly share code, notes, and snippets.

@nexdrew

nexdrew/what-makes-open-source-work.md

Last active January 13, 2016 19:09
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save nexdrew/aac73190a02fa956a8c3 to your computer and use it in GitHub Desktop.
Save nexdrew/aac73190a02fa956a8c3 to your computer and use it in GitHub Desktop.
Download ZIP
Ideas that could be organized into a talk/prez
Raw
what-makes-open-source-work.md

What Makes OSS Work

GH, npm, Travis, Coveralls

Source code that is... "open"

  • Find/view source code (GitHub website)
  • Duplicate/download source code (git clone)
  • Sandbox/isolate changes (git checkout -b)
  • Capture changes (git add && git commit)
  • Share changes (git push)
  • Review changes before acceptance (GitHub Pull Request)
  • Accept changes (merge PR)

Requires a "generally accepted" or "standard" process/workflow:

  1. Fork + clone
  2. Branch
  3. Change
  4. Test
  5. Commit
  6. Push
  7. PR
  8. Review + iterate
  9. Merge

We could "reverse engineer" the needs for these steps, starting with Change.

A way to make the source code open

GitHub

The find/view/share aspects from above

A way to change the source code

git

The capture aspects from above

A way to test changes and guard against regression

Travis CI, Coveralls

A way to release and install the software

npm

Differences from Agile

  • Async by nature
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment