|
|
| Line 4: |
Line 4: |
| | ** freenode.net | | ** freenode.net |
| | ** irc.gnome.org | | ** irc.gnome.org |
| − |
| |
| − | == Exercise 2.6 Planning for HFOSS involvement ==
| |
| − | # What course(s) are you targeting?
| |
| − | ## CS1: CSIT 102 - Intro. Programming (python)
| |
| − | # What learning outcomes would you like the students to achieve?
| |
| − | ## Able to use common open-source tools (forge, IRC, etherpad, tracker, etc.).
| |
| − | ## Able to articulate the distinguishing characteristics of FOSS development (adv./disav.).
| |
| − | # 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.
| |
| − | ## Have students create an account with github or bitbucket (probably bitbucket).
| |
| − | ## Have students collaborate through bitbucket.
| |
| − | ## Have students coordinate with IRC.
| |
| − | ## Code review.
| |
| − | # What HFOSS project will you use?
| |
| − | ## The tools I'll be introducing are not HFOSS specific, but are needed by the HFOSS community.
| |
| − | # What are the benefits of this project for this particular context (course & activity)?
| |
| − | ## Students will be better prepared to participate in H/FOSS projects.
| |
| − | # What are potential stumbling blocks?
| |
| − | ## Time. CS1 curriculum is tight.
| |
| − | # How do you want your students to interact with the community (if at all)?
| |
| − | ## To get help using tools.
| |
| − | # What tools will your students have to learn (if any)?
| |
| − | ## forge, tracker, IRC, pastebin
| |
| − | # Do you currently have the environment for this project to run (ie. is the hardware/OS available at your institution)?
| |
| − | ## yes.. a web-browser
| |
| − | # What type of materials/background do you think you will need to provide to the students?
| |
| − | ## links to tools
| |
| − | ## links to instructions to download and install various tools
| |
| − | ## class specific instructions for using tools (like naming conventions)
| |
| − | # What would you like the students to do during this activity?
| |
| − | ## Use FOSS to complete programming assignments
| |
| − | # How long do you expect the activity to take?
| |
| − | ## All semester :)
| |
| − | # What will the students hand in?
| |
| − | ## IRC logs (meetbot)
| |
| − | ## Link to repository (code in a repository)
| |
| − | ## Link to pastebins
| |
| − | ## Blog links
| |
| − | ## WIki links
| |
| − | ## Tracker link
| |
| − | # How will you assess what students have learned from this activity?
| |
| − | ## Rubric for use of tools.
| |
