Pathways Model Workshop 2016

Revision as of 14:58, 23 January 2016

Pathways Model Workshop

Overview: This workshop will bring together members of Humanitarian Free and Open Source Software (HFOSS) project communities and faculty members to review a draft model of learning pathways for student involvement in HFOSS. The model defines and sequences student learning activities that prepare students for successful HFOSS participation. Workshop attendees will focus on refining this model, including identification of entry-level knowledge, establishment of knowledge and skills required for HFOSS participation, and definition of learning outcomes that can move a student from entry-level knowledge to HFOSS participation.

Location: Nassau Community College, Garden City, NY.

Date and Time: 5:00 p.m. Thursday February 4th through lunchtime Saturday February 6th

Goals

The goals of this workshop include:

1. Review assumptions about entry knowledge of students
2. Refine the definition of knowledge and skills required for HFOSS participation
3. Verify the existing draft model
   • Is the structure of the approach appropriate?
   • Are there alternative implementations of the model?
   • Is the model:
     • Understandable
     • Usable
     • Reflective of reality
4. Refine the list of paths through the model
   • Which paths are most approachable by students?
   • Which paths are most valuable to the HFOSS community?
   • What are the strengths and weaknesses of the model?
5. Identify the existing resources to support learning
   • Are there activities that can map to paths or steps in a path?

Agenda

Tasks/Questions:

• What infrastructure are we using?
  • Dropbox?
  • Wiki - other than this overview?
  • Titanpad?
• What materials need to be prepared?
  • Need an evaluation form for pathways
  • Need a template in which to create pathways. Is this the Use Case format that Stoney presented in Verify Bug2 V0.1?
  • Somehow we need a way to capture the paths and steps in a common space so that we can flesh out the model jointly.
• Is the set of tasks identified in the Team Meeting Notes sufficient?
• Should we put that set of tasks in a separate location?