Category:Fix a Bug (Pathway)
From Foss2Serve
(Difference between revisions)
m (→Pathway Steps, Outcomes, & Learning Activities) |
|||
| (17 intermediate revisions by 3 users not shown) | |||
| Line 18: | Line 18: | ||
* Access the issue tracker with appropriate permissions. | * Access the issue tracker with appropriate permissions. | ||
* Read, create, and update issues in a tracker. | * Read, create, and update issues in a tracker. | ||
| + | |- | ||
| + | | [[:Category:Git|Git]] | ||
| + | | | ||
| + | * Understand how to find repository | ||
| + | * Fork the repository to your github account | ||
| + | * Clone the repository to your local github | ||
|- | |- | ||
| Community | | Community | ||
| Line 45: | Line 51: | ||
* [[:Category:Written Communication|Writ Comm]] | * [[:Category:Written Communication|Writ Comm]] | ||
| | | | ||
| − | :[[ | + | :[[Intro to Bug Trackers (Activity)]] |
|- | |- | ||
| − | | 3. | + | | 3. Find the buggy code |
| − | : | + | | Specific lines of code in program identified |
| − | + | | | |
| − | + | * [[:Category:Problem Solving|Prob Solv]] | |
| − | | | + | * [[:Category:Written Communication|Writ Comm]] |
| + | | | ||
| + | :[[Finding the Code Responsible for Behavior]] | ||
| + | |- | ||
| + | | 4. Write and test code that attempts to solve the problem | ||
| + | | Code written and tested for patch | ||
| | | | ||
* [[:Category:Problem Solving|Prob Solv]] | * [[:Category:Problem Solving|Prob Solv]] | ||
* [[:Category:Written Communication|Writ Comm]] | * [[:Category:Written Communication|Writ Comm]] | ||
| − | |||
| | | | ||
| − | :[ | + | :[[Solving A Bug]] (Java specific) |
| − | :[[ | + | :[[Document Code with Meaningful Comments (Activity)]] |
| + | :[[:Category:Quality and Testing]] | ||
| + | |- | ||
| + | | 5. Submit patch to the community following community norms.(If patch is rejected, go back to step 4.) | ||
| + | | Patch submitted to community | ||
| + | | | ||
| + | * [[:Category:Problem Solving|Prob Solv]] | ||
| + | * [[:Category:Written Communication|Writ Comm]] | ||
| + | | | ||
|- | |- | ||
| − | | | + | | 6. Once accepted or abandoned verify that the issue is updated appropriately |
| Issue updated in issue tracker | | Issue updated in issue tracker | ||
| | | | ||
Latest revision as of 18:37, 11 March 2017
The contributor will: fix a bug by submitting a patch and updating the issue tracker.
The contribution is: a patch for the bug and updated information in the issue tracker.
Prerequisites
| Area | The contributor must be able to: |
|---|---|
| Software Configuration |
|
| Issue Tracker |
|
| Git |
|
| Community |
|
Pathway Steps, Outcomes, & Learning Activities
Follow the project’s policies and practices to complete the steps below.
| Pathway Step | Step Outcome | Process Skills Focus | Related Learning Activities |
|---|---|---|---|
| 1. Verify bug (see Verify a Bug (Pathway)) | Bug reproduced | ||
| 2. Claim issue on issue tracker | Issue tracker updated | ||
| 3. Find the buggy code | Specific lines of code in program identified | ||
| 4. Write and test code that attempts to solve the problem | Code written and tested for patch | ||
| 5. Submit patch to the community following community norms.(If patch is rejected, go back to step 4.) | Patch submitted to community | ||
| 6. Once accepted or abandoned verify that the issue is updated appropriately | Issue updated in issue tracker |
Notes for Learning Activities Related to this Pathway
When creating activities:
- Indicate the level of programming experience needed.
This category currently contains no pages or media.
