Bug reports & issues: help us help you. #767
Pinned
aurelienpierre
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Bad quality bug reports are unacceptable given the currently available workforce, because they take too much time and energy to understand, going back and forth with their authors to understand WTF they mean.
Issues should be actionnable
We have a project management board that allows to track where we are at for the upcoming release: what remains to do, what has been done but still needs validation. Issues are meant to end on this board.
Unlike Darktable, a stable release will be published when the todo list of the corresponding milestone will be cleared (it's revolutionnary, I know).
Anything that doesn't belong in the todo list doesn't belong to issues at all, and will only trigger cognitive overload ([1] [2]) and information fatigue from those who have to actually fix the code.
Your best interest as users is to protect the mental health and sanity of those who will work on your issue. Having to carry the burden of 15 years of code legacy written in C (the worst programming language ever) is enough work and pressure.
Questions / Is it normal ? / I don't understand
Those are not bugs and don't belong to issues. You have:
Respect the issue form
The form is meant to guide you through filling the relevant info, don't skim or bypass it.
All reactions