POSSE Survey

From Teaching Open Source

Jump to: navigation, search

THIS IS A DRAFT!

Purpose[edit]

The purpose of this survey is to measure the return on investment that open source communities have gotten from the first POSSE session.

Questions[edit]

POSSE is a substantial portion of building the TOS community, from which existing open source communities will be getting...

  • Labor
  • Recruiting
  • Mindshare

This survey will largely focus on the first one, "Labor," using Chris Grams's progression of open source community involvement.

Consume[edit]

This is what POSSE focuses on the least - our focus is not in getting more open source "seats" into classrooms, so we aren't concerned about software usage except inasmuch as it enables contribution (because using open source is a prerequisite to contributing to open source). We will not be measuring usage in this survey.

Participate[edit]

This is something we will measure ourselves by tracking your student contributions to our projects.

  • Please give us the Fedora Account System (FAS) usernames of all your students.
  • Please give us the Mozilla usernames of all your students.
  • Did your students participate in any other open source projects this semester? If yes, please list the homepages of those projects.
  • Please give us links to the blogs of all your students (or the planet where their blogs are aggregated).
  • Please give us links to public mailing lists your students participated in for their projects this semester.
  • Please list IRC channels your students will be doing project work in this semester.

We will use this to track things like...

  • IRC meeting participation
  • Mailing list discussions
  • Blog discussions
  • Bug reports submitted (particularly those leading to closure)
  • Bug triaging work done
  • Tickets closed
  • Documentation work contributed (wiki edits, etc)
  • Packages created and maintained

We're also interested in who you participated with.

  • Who are the community members (outside your class) that your class has worked with?
    • For Fedora or Mozilla community members: please send us their FAS or Mozilla usernames.
    • For members of other communities, please send us their name and the project they are from, and (if possible) a way for us to contact them.

We'll be asking these community members to tell their stories about what it was like to work with a POSSE classroom.

Contribute[edit]

(end of the semester)

This is something we would like qualitative data on. Tell us stories about...

  • Are there any individual students that stood out for you this semester? What have they been doing, and how can we encourage them?
  • Success stories. What went right? What can we learn from this, and what can we do to help you go even further in the future? We're interested in both project and learning success stories - for instance, if a project isn't feature-complete by the end of the semester but students learned a valuable lesson about scope, or if a collaboration conflict arises and students are able to successfully resolve it, these are also success stories we can learn from.
  • Failure stories. What went wrong? What can we learn from this, and what can we do to help you improve things in the future? We're interested in both project and learning failure stories - for instance, if a project was technically successful, but the students involved didn't take risks and instead built what they already knew how to build, that's an area for improvement in terms of student learning.

Lead[edit]

This is where POSSE's unique value shines.

For each question, we need to ask professor before/after and students before/after, with yes/no for both.

  • Know what open source is
  • (Optional) How would you describe it (before/after)?
  • Use IRC for open source project communication
  • Use a wiki for open source project communication
  • Use a mailing list for open source project communication
  • Use blogs/Planets for open source project communication
  • Create and/or maintain a piece of open source software (code)
  • Create and/or maintain a package
  • Make a patch
  • Do a code review
  • Report a bug
  • Debug a piece of open source code
  • Do open source outreach

Also leave a free text area for comments on any of the above.

Plain Old Metrics[edit]

  • Where can we find your class website?
  • Where can we find your class syllabus?
  • How many students were in your class?
  • (Optional) Did you collect any metrics on class demographics - major, year, gender, nontraditional students, etc? If so, we'd love to see them.
  • How many hours total, throughout the semester, would a single student be expected to spend on coursework for your class (including attending class)?

Other[edit]

  • what else should we have asked?