Category:Add a Feature (Pathway)
(Difference between revisions)
| Line 78: | Line 78: | ||
* [[Unit_Test_With_GoogleTest_Activity|Unit testing with GoogleTest]] | * [[Unit_Test_With_GoogleTest_Activity|Unit testing with GoogleTest]] | ||
* [[Examine_Branch_Test_Coverage_(Activity)|Examine branch test coverage]] | * [[Examine_Branch_Test_Coverage_(Activity)|Examine branch test coverage]] | ||
| + | * [[UML_a_project]|UML a project] | ||
|- | |- | ||
| 4. Submit changes to community. | | 4. Submit changes to community. | ||
Revision as of 00:18, 9 March 2017
The contributor will: contribute code to implement a requested feature.
The contribution is: code accepted into the project's codebase to implement a requested feature.
Prerequisites
| Area | The contributor must be able to: |
|---|---|
| Tools |
|
| Software Configuration |
|
| Issue Tracker |
|
| 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. Identify feature to be coded.
|
Feature identified. |
| |
2. Claim the ticket for the feature.
|
Ticket for feature is claimed. | ||
| 3. Implement feature. | Code to implement feature is complete.
|
||
| 4. Submit changes to community. | Code to implement the feature is accepted into the project’s codebase, or the feature is abandoned. Note: There may need to be several iterations of this process until resolution one way or another is reached. | ||
| 5. Complete process to close ticket. | Ticket for feature is closed either by the participant or by a maintainer. |
Notes for Learning Activities Related to this Pathway
When creating activities:
- Identify reasonable features to be implemented. This can reduce student time searching for issues, and reduce the chances of choosing a feature that is too difficult or too easy.
This category currently contains no pages or media.
