Category:Add a Feature (Pathway)
(Difference between revisions)
(→Pathway Steps, Outcomes, & Learning Activities) |
(→Pathway Steps, Outcomes, & Learning Activities) |
||
| Line 49: | Line 49: | ||
* [[Requirements_Analysis|Requirements analysis]] | * [[Requirements_Analysis|Requirements analysis]] | ||
* TBD: identify feature to be implemented | * TBD: identify feature to be implemented | ||
| + | * [[Code_Base_Understanding|Code base understanding]] | ||
|- | |- | ||
| 2. Claim the ticket for the feature. | | 2. Claim the ticket for the feature. | ||
Revision as of 19:29, 8 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. | ||
| 5. Complete process to close ticket. | Ticket for feature is closed. |
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.
