Stage 1 Activities

From Foss2Serve
Revision as of 18:25, 26 February 2013 by Stoney.jackson (Talk | contribs)
Jump to: navigation, search

Below is the schedule for the pre-workshop activities. Participants should finish all activities in a timely fashion in order to be reimbursed for travel expenses to the face-to-face portion of the workshop. Please send all comments to Heidi Ellis (ellis@wne.edu).

First Two Weeks - Approximately 5-5.5 hours (Due by May 4th, 2013)

  1. Introduction – 60 minutes
    • Expectations:
    1. Read Cathedral and Bazaar
    2. Talk about being productively lost - We expect you to be lost and we understand that the feeling may be uncomfortable
    3. Expectation is that you will feel overwhelmed, as if you were going to a foreign land.
    4. Pick an HFOSS project from the provided list to "make yours"
    5. More....
  2. Join TOS - 30 minutes
    • Faculty members sign up for TOS list and enter themselves in the "People" area
  3. Introduction to Wikis - 30-45 minutes
    • Activity that describes wikis and has faculty members create their own page and post an introduction
  4. Introduction to IRC - 60-75 minutes
    • Reading(s) about IRC
    • Install an IRC client of choice
    • Walk through actual examples of IRC conversations
    • Prepare expectations: -
    1. Tell faculty to look at the interactions and ignore the technical terms.
    2. Much of the technical content may not be understandable at this point.
    3. Observe the communication patterns.
    4. How to people interact?
    5. What is the pattern of communication?
    • This one step in being productively lost.
    • Lurk in meeting of preferred HFOSS group
      • Have students join a channel for 24 hours –
      • Give students a selection of channels to observe
    • Make an observation on lurking on faculty member’s wiki page
      • Could also be a question about future materials.
  5. IRC Meeting - 60 minutes
    • Introductions
    • Discussion of HFOSS projects
  6. Intro to FOSS Projects and Dynamics - 60 minutes
    • The idea here is to provide an introduction to the landscape of a FOSS project. Introduce major players and define key terms such as releases, packing, upstream and downstream, trackers, tickets, roadmap, etc.
    • First couple of chapters in "Productively Lost" ?
    • Mel has a good overview of some parts in "Roadmap Merge" activity here: http://mchua.fedorapeople.org/posse/POSSE-booklet.pdf

Second Two Weeks - Approximately 4.5-5 hours (Due by May 18th, 2013)

  1. Blogging Activity - 60 minutes
    • Reading on blogs and planets
    • Observe several blogs
      • Provide a selection of blogs to observe
    • Post to wiki about how blogs might be used in classes.
  2. FOSS in Courses - 60 minutes, post your selected activity to your wiki page.
  3. Pads and common editing - 30 minutes
    • Readings
    • Have participants contact someone via IRC and talk about projects using Etherpad to write the notes?
    • Cover how things like Etherpad used in the FOSS community
  4. FOSS Field Trip - 60 minutes, blog on what you learned on your wiki page or blog
  5. Project Evaluation Activity - 60-90 minutes
    • Pared down evaluation of HFOSS project based on the evaluation metric.
    • Post results to wiki

Third Two Weeks - Approximately 5 hours (Due by June 1st, 2013)

  1. IRC Meeting - 60 minutes
    • Discuss progress
    • Guidance for selecting a project
  2. Bug-Tracker Activity - 60 minutes
    • Investigate an existing bug tracker - likely one related to the project that they have chosen
    • HE has a template for this activity, not online anywhere yet.
  3. Source Code Management/Control Activity - 60 minutes
    • Need some content for here. Something that would get the idea of forking and conflict across with low overhead.
  4. Course Integration Activity - 60 minutes
    • Participants identify the course in which they would like to integrate HFOSS
    • Perhaps have them describe this on their wiki page?
    • Identify any learning objectives to be met and scope
      • Talk about plan. Some folks might want to start with a single assignment and grow from there. Others may decide to take on more.
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox