Final project
For this project, you will explore and correct an issue in an open source project. This project will be done in groups of 3-4.
Forming a team
You can form a team of 3-4 people. It is best if you have a good balance of skills and you get along with your teammates.
The groups have been formed as this:
-
A : huangf1 sheffeit zhengj2
1819c-debug-A
moonmask
pyrsistent
anycvs
carbon -
B : proctem johnsor2 clonintl graziodj
1819c-debug-B
MusicBot
MusicBot2
Evolve1
Evolve2
Evolve3 -
C : fengy3 wangc6 xiey2
1819c-debug-C
teammates -
D : shenx liur5 wangy18
1819c-debug-D
openoffice -
E : hilliara shaferw mckownqa
1819c-debug-E
Cataclysm -
F : calarejf neessc chenj10 schluncg
1819c-debug-F
Craft -
G : mongovsp paytonzk petrisjj
1819c-debug-G
javascript-tetris
Selecting an issue
You will need to select a project and bug to investigate. You should look for these qualities in the project you select:
- Reasonable build process
- Reasonable sized codebase
- Has issue tracking system of some kind
- Has source control system of some kind
You should look for these qualities in the issue you select:
- Has not been known for long period of time
- Is not assigned to an active developer
- Is reproducible
You must submit the project and bug to your instructor for approval.
Solving the issue
To complete the assignment, you will need to submit the following:
- A report with:
- A brief description of the project and your reasons for selecting it.
- A description of the issue and your reasons for selecting it.
- A log of your bug investigation
- The changeset that correct the issue
- A link to your pull request or correction submission for the issue
Final presentation
Each team will briefly present their bug and how they solved it to the class. This presentation will be very informal, but you need to make sure the class understands the issue and how you arrived at the solution.
Rubric
Bug selection
- Possible bug list (5)
- Bug selection (5)
Status 1
- Sufficient work last week (5)
- Good plan for next week (5)
Status 2
- Sufficient work last week (5)
- Good plan for next week (5)
Status 3
- Sufficient work last week (5)
- Good plan for next week (5)
Presentation
- Explain bug (5)
- Explain solution (5)
Debugging process
- Log documents hypotheses, implementation, results (25)
- Summary document of bug solving process (10)
- Repo shows all team members contributing (10)
- Group evaluation completed (5)