Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug, feature request, or question? #3629

mwjames opened this issue Jan 19, 2019 · 2 comments

Bug, feature request, or question? #3629

mwjames opened this issue Jan 19, 2019 · 2 comments


Copy link

@mwjames mwjames commented Jan 19, 2019

The CONTRIBUTION guideline already makes an attempt to distinguish between bug and feature request, and the following tries to extend guidance of how project members interact and interpret tickets posted on the Github issue tracker.

Issue list

To clarify, the issue list is a working list allowing developers (and other community members) to easily navigate and review open issues. There are divided into two main groups, bugs and feature requests with both impacting the software, its development, and the release cycle.

  • Issues labelled with newcomer are selected issues that should be picked by users wanting to make a difference or contribute directly to the project by improving the software


A bug is the occurrence of an unintended or unanticipated behaviour that causes a vulnerability or fatal error.

An issue classified as “bug” will most certainly solicit a response from a core developer or project member to request further details or share information on the described circumstances and observations. Yet, developers may express different interpretations of how to proceed or manage individual issues.

Feature request (or enhancement)

A feature request is a new, or altered behaviour of an existing functionality, it can also express a wish for an entire new functionality.

  • Issues (especially features request without a sponsor) that are not actively worked on and have been open for longer than 90 days without a significant activity will be closed and moved to the Enhancements and features project
  • Resurrecting issues from the Enhancements and features project is possible but should come with a clear sign of sponsorship (see [0])

Moving a request to the Enhancements and features project isn't a sign of dishonoring the request or its importance (especially to the requesting party) but a managerial action to keep the issue list a working list by employing a rule of thumb [1].


An issue that has not been classified as bug or future request and intents to clarify an observation is a question by which the requesting party implores on the assistance of a developer or community member.


[0] A sponsor or sponsorship is understood as a person or entity that keeps track of related activities and/or implements aspects of it in order to have it reviewed and merged.
[1] After 90 days of inactivity it is assumed that the likelihood for an implementation has greatly diminished and sponsorship is unlikely to happen in near future.

@mwjames mwjames pinned this issue Jan 19, 2019
@kghbln kghbln added this to Documentation in Documentation Jan 19, 2019
Copy link

@kghbln kghbln commented Jan 19, 2019

Referenced here and there on the wiki. Moreover added to the "General" section of the "Documentation" project.

@kghbln kghbln closed this Jan 19, 2019
Copy link
Contributor Author

@mwjames mwjames commented Feb 23, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants