Pecha Kucha Storyboard

[SOLV-Code]

Specs

• 12 slides
• 20 s each (2-3 sentences)
• this link has some slide templates with timers that count down 20 seconds

General

• put link on all slides (github.com/SOLV-Code/Githubbing)

Part 1: Theory

• 1 WHat is git
  • focus = Collaborate on Code & Data
  • synch between WG members
  • track everything
  • can backtrack / reconstruct any changes
• 2 What is github?
  • slide with logos (word, access/xls, proj mgmt post its, facebook/twitter, code -> guthub, markdown, Rstudio)
• 3 Communication / Project Management:
  • Issue: tasks, bugs, but also bulletin board, mtg notes etc (Searchable!, tag people)
  • ReadMe
  • Wiki
  • Basic Markdown (task list example)
• 4 Automated Documents
  • whenever the data/calc changes, rerun the doc, and have the latest version of plots and tables.
    "Markdown plus" -> "bookdown"

Part 2: Practice

• 5 Personal Journey
  • July 29, 2017 -> now
  • Fisheries Science != Computer Science
  • not primarily software dev
  • diverse WG, end-users (Excel 2003 in 2016)
• 6 Current Status
  • Use it for all projects (check github before e-mail)
  • give a "github crash course" at the beginning of each project
  • Then they each evolve differently
• 7 Organization Tools != Organized
  • Multiplying repositories
• 8 We've got issues, lots of issues
  • Avalanche of issue
• 9 Collaboration Tools != Collaboration
  • learning curve / uptake
  • Project Mgmt: task lists and discussion threads yes, but most of the advanced features not used (except AMH and Antonio)
• 10 Automated != Effortless
  • Reports / Collective Editing
  • Issues, Wiki: :-)
  • Reports: :-) -> :-( -> :-)

Taku Sk MR review : markdown -> word -> google docs -> markdown -> word -> google docs
Fraser Sockeye Recovery Potential Assessment:

• body of doc: word / google docs
• appendix with figures and tables: automatically generated (no specific links)
  formatting etc

• 11 Big Data = Big Problem
  • github deals with text, csv files
  • doesn't like xls, pdf, doc (ignore those, share separately): MRP, nuSEDS
• 12 Pain Now or Pain Later?
  • Up Front Effort vs. Later Savings
  • Setting up gets easier after you've done a few and found your own workflow
  • the rest depends on the nature of the project and the WG
  • even if only 1 actively using the code tracking and issue threads, it still helps with switching between projects, and reducing the number of post-its in my office.