User:Stoney.jackson

• Organization: Western New England University
• Email: dr.stoney@gmail.com
• Stoney or StoneyJackson on IRC networks:
  • freenode.net
  • irc.gnome.org

Exercise 2.6 Planning for HFOSS involvement

1. What course(s) are you targeting?
   1. CS1: CSIT 102 - Intro. Programming (python)
2. What learning outcomes would you like the students to achieve?
   1. Able to use common open-source tools (forge, IRC, etherpad, tracker, etc.).
   2. Able to articulate the distinguishing characteristics of FOSS development (adv./disav.).
3. What type of activity do you want to incorporate? Sample activities could be HFOSS field trips, installing, documenting, testing, or code development. See http://xcitegroup.org/softhum/doku.php?id=f:50ways for more ideas.
   1. Have students create an account with github or bitbucket (probably bitbucket).
   2. Have students collaborate through bitbucket.
   3. Have students coordinate with IRC.
   4. Code review.
4. What HFOSS project will you use?
   1. The tools I'll be introducing are not HFOSS specific, but are needed by the HFOSS community.
5. What are the benefits of this project for this particular context (course & activity)?
   1. Students will be better prepared to participate in H/FOSS projects.
6. What are potential stumbling blocks?
   1. Time. CS1 curriculum is tight.
7. How do you want your students to interact with the community (if at all)?
   1. To get help using tools.
8. What tools will your students have to learn (if any)?
   1. forge, tracker, IRC, pastebin
9. Do you currently have the environment for this project to run (ie. is the hardware/OS available at your institution)?
   1. yes.. a web-browser
10. What type of materials/background do you think you will need to provide to the students?
    1. links to tools
    2. links to instructions to download and install various tools
    3. class specific instructions for using tools (like naming conventions)
11. What would you like the students to do during this activity?
    1. Use FOSS to complete programming assignments
12. How long do you expect the activity to take?
    1. All semester :)
13. What will the students hand in?
    1. IRC logs (meetbot)
    2. Link to repository (code in a repository)
    3. Link to pastebins
    4. Blog links
    5. WIki links
    6. Tracker link
14. How will you assess what students have learned from this activity?
    1. Rubric for use of tools.