User:Tharvey/b4activity
From Foss2Serve
< User:Tharvey(Difference between revisions)
(Created page with " {| class="wikitable" style="width:100%;" |- ! Lesson ! URL ! style="width:60%;" | comments/changes |- | Bug gardening | http://foss2serve.org/index.php/Bug_Gardening | select...") |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 23: | Line 23: | ||
|} | |} | ||
| − | + | #Make a small contribution: see https://www.ushahidi.com/support/add-code-to-ushahidi | |
| − | + | ##read project "how to contribute" | |
| + | ##find project volunteer coordinator | ||
| + | ##tracker: marked "easy/beginner"? | ||
| + | ##understand code base | ||
| + | ##plan solution | ||
| + | ##claim | ||
| + | |||
| + | |||
| + | #Bug Gardening | ||
| + | #Identify some possible learning outcomes that should be fulfilled with the activities/task. | ||
| + | ## small is still productive | ||
| + | ## bug life cycle | ||
| + | ## projects have triage rules/guidelines | ||
| + | #Describe any prerequisite knowledge needed to complete the activity. This does not need to be a complete list. | ||
| + | ## HFOSS intro | ||
| + | ## Bug Tracking | ||
| + | # 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. | ||
| + | ## 1 HR identify some bugs ahead of time for students who will have trouble | ||
| + | ## 1 HR Notify/request/schedule the project that students will be gardening | ||
| + | #Think about possible input required from the HFOSS community. How much input is required and what kind? | ||
| + | ## Notify/request/schedule the project that students will be gardening | ||
| + | ## Ask for the assistance of someone on the project for live IRC assistance | ||
| + | #If the result of the activity is contributed back to the HFOSS project, describe the contribution and its usefulness. | ||
| + | ## Removes dead bugs that take space and attention. Can mark as resolved, or update with requirements to show this is still worth attention. | ||
| + | #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? | ||
| + | ## I would do this in teams with me assisting. My first time I would ideally have an experienced project person helping via IRC. | ||
| + | #List any questions or concerns that you have about the activity/task. | ||
| + | ## I have to do this myself a few times to get comfortable before running this in a classroom. | ||
| + | #List any stumbling blocks or barriers to carrying out the activity/task. | ||
| + | ## see previous | ||
Latest revision as of 20:44, 18 June 2019
| Lesson | URL | comments/changes |
|---|---|---|
| Bug gardening | http://foss2serve.org/index.php/Bug_Gardening | select one triage guide; initial is "validation" in OpenMRS, no triage doc there |
| Interactive Visualization with Git | http://foss2serve.org/index.php/Interactive_Visualization_with_Git | do this after Git lab - see other pre-activites listed |
| Code Base Understanding | http://foss2serve.org/index.php/Code_Base_Understanding | josh will add?; this is tough for new SEs; maybe SE2? try it myself |
| Comparable interface | http://foss2serve.org/index.php/Comparable_Interface_-_Code_Reading-Activity | for Java programming course, nice questions |
- Make a small contribution: see https://www.ushahidi.com/support/add-code-to-ushahidi
- read project "how to contribute"
- find project volunteer coordinator
- tracker: marked "easy/beginner"?
- understand code base
- plan solution
- claim
- Bug Gardening
- Identify some possible learning outcomes that should be fulfilled with the activities/task.
- small is still productive
- bug life cycle
- projects have triage rules/guidelines
- Describe any prerequisite knowledge needed to complete the activity. This does not need to be a complete list.
- HFOSS intro
- Bug Tracking
- 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.
- 1 HR identify some bugs ahead of time for students who will have trouble
- 1 HR Notify/request/schedule the project that students will be gardening
- Think about possible input required from the HFOSS community. How much input is required and what kind?
- Notify/request/schedule the project that students will be gardening
- Ask for the assistance of someone on the project for live IRC assistance
- If the result of the activity is contributed back to the HFOSS project, describe the contribution and its usefulness.
- Removes dead bugs that take space and attention. Can mark as resolved, or update with requirements to show this is still worth attention.
- 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?
- I would do this in teams with me assisting. My first time I would ideally have an experienced project person helping via IRC.
- List any questions or concerns that you have about the activity/task.
- I have to do this myself a few times to get comfortable before running this in a classroom.
- List any stumbling blocks or barriers to carrying out the activity/task.
- see previous
