POSSE Worcester State planning

From Teaching Open Source

Jump to: navigation, search

Contents

[edit] Curriculum

[edit] Todo

Mel:

  • make sure SoaS is set up
  • make Remix, sticks
  • get student project examples
  • get readings out

Walter:

  • Activity development environment
  • Activity modification experience
  • Code deep-dive prep
  • Drum up examples of pedagogical thinking

[edit] Notes

[edit] Current draft

Meeting summary

[edit] Monday

  • Goal: Learn how to use the communication tools the community uses.
  • accounts to create: SL trac, gitorious, FAS, RHBZ, aslo, freenode nick registration, SL wiki
  • each attendee should be set up with a blog
  • ACTION: mchua make account-creation instructions and send them out beforehand so professors can arrive with accounts already made (and then just learn to use them)
  • ACTION: mchua test jhbuild setup
  • ACTION: make remix with git, jhbuild, inkscape
  • ACTION: reading list
    • get ssh key
    • flossmanuals
    • how to write activities

Mel:

  • Fedora setup
  • history
  • communication tools

Walter:

  • Sugar Labs history
  • SL dev setup
  • professor context

[edit] Tuesday

  • Goal: Learn how to find what code is available, get that code, and begin modifying it
  • tools: git, some sort of editor/IDE
  • social: asking questions and finding people on IRC, mailing lists, wikis - scoping a project
  • IDEA: Goal for the week: get an Activity that isn't included in SoaS, up to standards and included in SoaS.
  • IDEA: RPM packaging will be the extra-evening-bonus-sessions, in the evenings in the hotel lobby
  • ACTION: mchua finalize SoaS inclusion criteria, get general community consensus on them for v.4.0
  • ACTION: sdziallas gear up for "how to package Activities" sessions (make resources, etc.)
  • AGREED: no jhbuild! but tell them what it is and how to learn more if they're interested after POSSE week.
  • IDEA: SoaS Activity reviews can be done by Sebastian, Peter, and Mel for v.4.0 (for inclusion in SoaS, separate from packaging in Fedora - though that's one of the criteria)
  • Activity: pick an Activity
  • Activity: learn about inclusion criteria
  • Activity: use stick to download and install Activity from aslo to test it
  • make sure we have "intro to SoaS" time on Monday (for basic Sugar usage)
  • ACTION: mchua make sure all attendees have a computer that can boot a stick (bring extra netbooks if possible)
  • Activity: intro to git/gitorious (check out Activity code)
  • Activity: python 101
  • Activity: modifying an Activity (perhaps changing a toolbar icon temporarily) - tools to learn: some IDE, code search tools/strategies like ack/grep
  • Activity: finding active bugs for an Activity - tools to learn: trac
  • make sure attendees know what RPM packaging is and how they could learn it (evening sessions, etc) but it will *not* be part of the day's curriculum
  • packaging party (optional) Tuesday night

Mel:

  • git intro
  • SoaS Activity inclusion criteria and workflow

Walter:

  • gitorious and view source, ASLO
  • intro to basic Sugar usage

[edit] Wednesday

  • Activity: Answer questions from the previous day, ask people who in the community they've been engaging with
  • Activity: working with bug reports - how to read them, how to write them, how to get your bug fixed
  • Activity: creating and submitting patches
  • Activity: merge requests - basically, "getting your code upstream"
  • LINK: Bug Reports: http://wiki.sugarlabs.org/go/BugSquad/Bug_Report
  • Activity: "talking about the work you're doing" - everyone should be blogging, posting to lists, etc
  • to be continued tomorrow - we left off partway through Wednesday's curriculum

[edit] Budget

  • Sebastian's plane ticket is nonrefundable, so it looks like we're just going to have to eat $650.
  • Peter's travel arrangements are last-minute, so we're going to go over budget - which is ok, since our hard limit is actually $7000.
Description Budget Spent
Instructor stipend $2000 $2000
Instructor travel $40 (gas) $100 (approx)
Instructor lodging $0 (local) $0
Instructor expenses $360 ($30/day * 2 people * 6 days) $360 (approx)
Tech guru travel $700 $912.12
Tech guru lodging $800 $1125.04
Tech guru expenses $180 ($30/day * 6 days) $180 (approx)
Tech guru summit pass/lodging (in lieu of stipend）
Opening night dinner $300 $100 (approx)
Graduation night dinner $600 $600 (approx)
Total $4980 $5400 (approx)

Sebastian's plane was $642.49, need to convert to credit for a later flight.

Retrieved from "http://teachingopensource.org/index.php/POSSE_Worcester_State_planning"