Bug Gardening

From Foss2Serve
Revision as of 14:23, 16 June 2015 by Glikins (Talk | contribs)
Jump to: navigation, search
Title Bug Gardening
Overview Most projects have a backlog of bugs that need to be periodically “gardened.” Sometimes there are even old bugs that may have already been fixed that just haven’t been closed in the system. This module familiarizes students with bug gardening (/bug gardening) techniques, *and* helps the community by doing some of that gardening.
Prerequisite Knowledge Students should be familiar with how bug trackers work -- see [Bug Tracker Activity]
Learning Objectives What should the student be able to do after completing completed this activity?

Background:

Is there background reading material?

Are there other activities the student should have done first?

What is the rational for this activity?

Include helpful hints to faculty here.

Directions:

What should the student do?

Deliverables:

What will the student hand in?

Assessment:

How will the activity be graded?

How will learning will be measured?

Include sample assessment questions/rubrics.

Comments:

What should the instructor know before using this activity?

What are some likely difficulties that an instructor may encounter using this activity?

Additional Information:

Knowledge Area/Knowledge Unit What ACM Computing Curricula 2013 knowledge area and units does this activity cover? ACM_Body_of_Knowledge
Topic What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf
Level of Difficulty Is this activity easy, medium or challenging?
Estimated Time to Completion How long should it take for the student to complete the activity?
Materials/Environment What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?
Author Who wrote this activity?
Source [ways to contribute to open source without being a programming genius or a rock star
License Under which license is this material made available? (http://creativecommons.org/licenses/)

Suggestions for the Open Source Project:

Your community should have specific expectations around [support] that are published [somewhere]. For example, if your code will only work on Fedora versions newer than 19, then specify that.

If there are a set of bugs that it would be more helpful to have someone verify, then marking those in some way would help the instructor.



This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License

CC license.png

Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox