FOSS in Courses 2 (Instructors)
m |
(→Background) |
||
(One intermediate revision by one user not shown) | |||
Line 16: | Line 16: | ||
This activity is an extension of [[FOSS in Courses 1 (Instructors)]]. | This activity is an extension of [[FOSS in Courses 1 (Instructors)]]. | ||
− | The goal of this activity is to have | + | The goal of this activity is to have 1-3 topics and/or learning ideas to bring for discussion to the workshop and receive feedback on. |
− | We do not expect that these activities/ideas will be completely fleshed out, but | + | We do not expect that these activities/ideas will be completely fleshed out, but rather provide an initial starting point to think about. |
=== Directions === | === Directions === |
Latest revision as of 18:57, 27 April 2018
Title |
FOSS in Courses 2 |
---|---|
Overview |
Learner will identify 1-3 HFOSS topics and/or learning ideas for a course. |
Prerequisites |
Completion of FOSS in Courses 1 (Instructors) |
Learning Objectives |
After successfully completing this activity, the learner should be able to:
|
Process Skills Practiced |
Background
This activity is an extension of FOSS in Courses 1 (Instructors). The goal of this activity is to have 1-3 topics and/or learning ideas to bring for discussion to the workshop and receive feedback on. We do not expect that these activities/ideas will be completely fleshed out, but rather provide an initial starting point to think about.
Directions
- Recalling your list of activities/topics from FOSS in Courses 1 (Instructors), identify the ways that these FOSS activities/topics can be structured. Possibilities include:
- Lectures
- In-class activity
- Homework
- Stream of related activities
- Project
- List the revised activities on your wiki page. For each activity/topic:
- Identify some possible learning outcomes that should be fulfilled with the activities/task.
- Describe any prerequisite knowledge needed to complete the activity. This does not need to be a complete list.
- Estimate the time required for instructor prep, for student completion and elapsed calendar time. Are you going to have to synchronize your activity with the community or can the activity/topic be covered independent of the HFOSS community schedule.
- Think about possible input required from the HFOSS community. How much input is required and what kind?
- If the result of the activity is contributed back to the HFOSS project, describe the contribution and its usefulness.
- Describe the assessment/grading approach - What will the basis for grading be? Will this be a team activity or individual? Is there a role for the HFOSS community in helping assess student work? For instance, must the work be committed or otherwise accepted by the community?
- List any questions or concerns that you have about the activity/task.
- List any stumbling blocks or barriers to carrying out the activity/task.
Deliverables
POSSE: An entry on your foss2serve user wiki page that includes a list of 1-3 HFOSS topics and/or learning ideas for a course.
Notes for Instructors
The remaining sections of this document are intended for the instructor. They are not part of the learning activity that would be given to students.
Assessment
- How will the activity be graded?
- How will learning will be measured?
- Include sample assessment questions/rubrics.
Criteria | Level 1 (fail) | Level 2 (pass) | Level 3 (good) | Level 4 (exceptional) |
---|---|---|---|---|
Criteria 1 | ||||
Criteria 2 |
Comments
- What should the instructor know before using this activity?
- What are some likely difficulties that an instructor may encounter using this activity?
ACM BoK Area & Unit(s) |
|
---|---|
ACM BoK Topic(s) |
|
Difficulty | |
Estimated Time to Complete |
60-90 minutes |
Environment / Materials |
Access to Internet/Web and web browser. |
Author(s) | |
Source |
None. |
License |
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License |
Suggestions for Open Source Community
Suggestions for an open source community member who is working in conjunction with the instructor.