Skip to content
Lucy Wyman edited this page Oct 7, 2015 · 1 revision

Schedule for DevOps DayCamp:

  • 30 minutes for advanced session, 60 if you have a demo
  • 4 hour long sessions beginner total:
    1. Setup, (Pono, Eli)
    2. CLI/Linux (Lucy, Jordan)
    3. IRC/Help! (Lucy, Eli)
    4. VCS/Text Editors, and Github (Eli, Jordan)

The Schedule:

  • 9-10am: Setup
  • 10-11am: CLI/Linux
  • 11-12pm: IRC/Help!
  • 12-1pm: Lunch
  • 1-2pm: Text Editors
  • 2-2:30: Github
  • 2:30-3pm: Snack
  • 3-4pm: Panel

Speakers for Advanced Track

** Potential invitees

  • Edunham from Mozilla
  • Brandon Philips from Coreos
  • Nibalizer

Panel

  • Trevor (nonprofit)
  • Puppet labs ? (professional)
  • Student from the lab (Jeff and/or Evan) (academia)
  • Jordan (academia)

Bootcamp Stuff

** Choose person to groom to fill lead role.

  • Who will do it:
    • Lucy will default to running it each week
    • Jordan defaults to running it if Lucy isn't there
    • Eli will attend each week but not run it.
    • Pono is interested. And also a bear.
  • Schedule:
    • Doesn't need to span whole year
    • DOBC original for first term, "sequels" for next term.
    • Plan Spring term over winter break (online? Supported)
    • More focused and in-depth: 30 min lecture, 30 min activity. More modular and specific topics (ie. Puppet, as well as configuration Management).
  • Advertising: Keep on keeping on.
  • Metrics:
    • of Attendees per session

    • of same people coming

    • Views on youtube videos?
    • Analytics on the bootcamp site (slide decks and site) to get metrics on that.
    • Badges: Words to use: Quests, Badges for attendance (better word for attendance?), better word than "class" or "lecture" (colloquia, adventure).
    • Certification
    • Trade Quests/Challenges/Assignments for Badges
    • Page on website that is manually updated to have users and badges (basically database)
    • Thanks, Jordan.
  • Topics:
    • Should record Daycamp
    • Assume bootcamp attendees were at Daycamp -- point to video if they weren't.
    • "Learning outcomes":
      • Linux basics
      • Git and text editors
      • IRC
      • Configuration management: (Basics, Coreos, Deploy w/ Ansible (2 weeks?), Docker (close to end))
      • Web applications: (Basics, Databases, Frameworks, Debugging/Testing, Designy stuff, Security, manual deployment (necessary))
      • Speakers: Publicity? But maybe not so much for students. Cost-benefit analysis?
      • One term for each? (c.m and w.a)
  • Weekly meetings (except finals week)
    • 1 hour
  • Unified topic: due by 9/01/2015
  • Website:
    • Current term on front page
    • Archive of old content ('deprecated')

http://imgur.com/a/JuD0u