Responsive Feedback¶
Target competencyHas the ability to describe a software issue in a meaningful way for developers to act on.
Why it matters¶
Giving feedback to the developers of language technology tools is an important skill for improving these tools.
Progression¶
Each rung is a level a learner is at; its activities are what carries them to the next one. How to read these levels
General¶
-
0No Competency
Learn what should be included in a bug report.Carries a learner to 1 — Has Knowledge
-
1Has Knowledge
Submit a well-defined bug report or a new feature request for developers to act upon. Follow the report or request through the process.Carries a learner to 2 — With Assistance
-
2With Assistance
Actively participate as a beta tester for a language technology tool.Carries a learner to 3 — Independent
-
3Independent
Represent the user community on software development prioritization committees, UX design, or in championing new products.Carries a learner to 4 — Expert
Description¶
Knowledge to describe a software issue in a meaningful way for developers to act on.
Further Information¶
- How to write good bug report?Guide · musescore.orgMuseScore guide on how to write a good bug report, useful when reporting software problems to developers.
- What makes a good bug report?Guide · boxuk.comArticle on the parts of a good bug report: title, description, steps to reproduce, screenshots and severity.
- A Humorous but true article on Bug Reporting (Simon Tatham)Guide · chiark.greenend.org.ukSimon Tatham's essay on how to report bugs effectively, for learning what developers need in a bug report.
- Github IssuesGuide · guides.github.comGitHub documentation on issues, for tracking bugs and feature requests in a GitHub repository.
More in the resource library.