Category:Add a Feature (Pathway)
(Difference between revisions)
(→Prerequisites) |
(→Prerequisites) |
||
| Line 28: | Line 28: | ||
| | | | ||
* Contact community members for help and identify the person responsible for committing changes. | * Contact community members for help and identify the person responsible for committing changes. | ||
| − | * Describe community policy on testing and submitting patches, understand issue solving/triaging process. | + | * Describe community policy on testing and submitting patches/code, understand issue solving/triaging process. |
* Participate in a community which is open to code contributions. | * Participate in a community which is open to code contributions. | ||
* Time a contribution within the project's release cycle. | * Time a contribution within the project's release cycle. | ||
Revision as of 19:07, 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. Set up development environment. | Development environment installed and project and its tests run. | ||
2. Identify feature to be coded.
|
Feature identified. | ||
3. Claim the ticket for the feature.
|
Ticket for feature is claimed. | ||
| 4. Implement feature. | Code to implement feature is complete.
|
||
| 5. Submit changes to community. | Code to implement the feature is accepted into the project’s codebase, or the feature is abandoned. | ||
| 6. 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.
