• Plan for the day
• Welcome to Raleigh and Red Hat
• Introducing everyone
• Workshop overview and schedule

• 50 Ways to be a FOSSer
• Examples of actual student contributions
• Exercise 1.2 - Sample HFOSS Assignment

1.3 Project Evaluation Activity

• Compare notes from stage 1.B.2 activity
• Review critical criteria for a chosen project
• Go through secondary criteria for chosen project (if time permits)

1.4 Project Intros and Typical Workflow Activity

• In groups, review the major features of the project
• Walk through the workflow for the project
  • Clone out code for "test" project
  • Fix a small bug in "test" project

• Perspective on a few example HFOSS communities
  • Basic information: contact person, guide to getting started, Project Selection evaluation summary
  • Understanding the community landscape and process
  • Becoming a participant: lurking, joining the community, being visible, finding things to do
• Background: Results of Stage 1.B.1 learning activity

2.2 HFOSS in the Curriculum

• Discussion of options for getting started
• Example: A single HFOSS assignment in a course
• Example: HFOSS in a project course
• Example: HFOSS as a course
• HFOSS beyond the curriculum
• Trying to find the right size student project
• Evaluating student work
• Instructional style: mentoring vs. lecturing; instructor as co-learner

• Small Group Discussion
• Form groups around HFOSS projects
• Identify possible courses and possible contributions
• Plan a first HFOSS activity at your institution
• Make use of assignment ideas generated by participants in Stage 1 B.4 and C.4
• Exercise:
  • Questions for OpenMRS group
  • Questions for Ushahidi group
  • Questions for GNOME group
  • Questions for Sahana group

2.4 Understanding POSSE Stage 3

• Overview of Stage 3 group activities over the past year for: OpenMRS, Mousetrap, Ushahidi
• Evaluation in Stage 3
• Group Informatics

2.5 Planning for POSSE Stage 3

• Some experience reports from Stage 3
• Small Group Discussion - discuss the following:
  • List at least one modification to the Stage 3 process that you think would improve instructor support.
  • Are there other examples/ideas for improving communication and instructor support?
  • How will our group communicate and support each other?
  • Can/how will we create joint activities?
  • Report back on the group answers to the above questions

2.6 Group Hands-on Work

• Completing project set up in groups

• How tools fit and support HFOSS culture
• Upstream Adoption
  • Version control - role in a FOSS project
  • How to get a change committed.
• FERPA
• Licensing and Intellectual Property

3.2 Sharing HFOSS Learning Activities

• Goal: to create a shared set of HFOSS learning activities
• Standard information to define each learning activity
• Existing learning activities and places to share new ones
  • foss2serve.org, teachingopensource.org, swenet.org, computingportal.org

• Identify kinds of contributions students can make
• Brainstorming session
  • Talk about how you would create student deliverables
  • Now using the template, start to create the activity whose development began in 2.3
    • Make sure to make a copy of the template for each activity

• Groups report back on work done before lunch (early 3.2)

• What will the group do together?
• Plan some initial activities (faculty only or faculty and students)
• Discuss group communication

• Evaluation form
• Open discussion
• Closing remarks