• erika owens:
  My very proto documentation on journalism hack days, includes links to great reportbacks, guides, tips. #tcamp13

@erika_owens curious about your using GitHub to host this. Blog post sometime?

• erika owens:
  @jeffporten hmm…sure. It was mostly to aid in collaboration and to worry less about formatting, ha.

@erika_owens Right, I just haven’t seen GitHub used for text collaboration before. Adv/disadvantages over wiki/GDocs?

@erika_owens I know some writers who use SVN for personal version tracking, but otherwise haven’t heard much about check-in for non-coding.

• erika owens:
  @jeffporten got the nudge from @veltman‘s kick ass learning lunches on github https://github.com/veltman/learninglunches …

@erika_owens Thanks, *another* thing you’ve put on my to-look-at to do list. You’re running the risk of becoming your own category.

• Noah Veltman:
  @erika_owens @jeffporten I chose github for a few reasons: 1. easy for others to contribute in a structured way (contra Google Docs)

• Noah Veltman:
  @erika_owens @jeffporten 2. Limits of Markdown force me to focus on content and not nitpick the presentation

• Noah Veltman:
  @erika_owens @jeffporten 3. it’s good general practice for Git workflow and Markdown syntax

• erika owens:
  @veltman @jeffporten Grateful you lead the way. Worrying about formatting drives me nuts and git time is quality time.

@erika_owens @veltman Nearly all my writing starts in Markdown these days. Agreed that formatting is generally a waste of time.

@erika_owens @veltman still wrapping my head around using Git as a collaborative documentation space.