Category:Create a Tracker Issue (Pathway)

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
(Prerequisites)
 
Line 18: Line 18:
 
* Describe issue trackers and how they are used.
 
* Describe issue trackers and how they are used.
 
* Access the issue tracker with appropriate permissions.
 
* Access the issue tracker with appropriate permissions.
* Read, create, and update issues in a tracker.
 
 
|-
 
|-
 
| Community
 
| Community

Latest revision as of 23:58, 8 March 2017


The contributor will: study and try to create a tracker issue (e.g. a bug report or feature request).

The contribution is: a new tracker issue to improve the project.

Prerequisites

Area The contributor must be able to:
Software Configuration
  • Run the program.
  • Possibly: Download and install the development environment.
Issue Tracker
  • Describe issue trackers and how they are used.
  • Access the issue tracker with appropriate permissions.
Community
  • Describe the community guidelines for management and triage of issues (bug reports and feature requests).

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. Select a issue to create. For example, the issue might be:
a. Suggested by the HFOSS community as appropriate for students.
b. Suggested (and possibly assigned) by the instructor.
c. Created by the student.
You selected an issue.
2. Study the issue details, and identify aspect(s) that should be included.
a. Describe the issue.
i. For a bug report, describe the problem, and how to reproduce it.
ii. For a feature request, describe the benefit, and how it might work.
iii. For a complex issue, consider whether it should be split into several smaller issues.
iv. How many users are affected, and how important is it to them.
b. Describe actual or potential solution(s) to the issue.
i. Actual solution(s) might include a branch, patch, or list of steps.
ii. What code, documentation, database, etc would be changed?
iii. How difficult would these changes be?
iv. For a complex solution, consider whether it should be split into several smaller issues.
You identified one or more aspects to be included.
3. Look for more information.
i. Search for more details - was it discussed in IRC, forums, other issues, etc? Do other projects have similar issues? Summarize what you found.
ii. Ask the reporter(s) or FOSS community for input.
You have provided or asked for more information.
4. Create the issue.
a. Indicate if you plan to start or stop work on the issue e.g. claim or watch the issue, assign it to yourself, etc.
You created an issue in the issue tracker.

Notes for Learning Activities Related to this Pathway

When creating activities:

  1. Use examples to demonstrate concepts to student.
  2. Use screen shots when possible.

This category currently contains no pages or media.

Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox