Link to Update feedback guidelines directly from Bodhi's feedback form #915

Open
opened 2026-07-17 08:08:33 +00:00 by kparal · 1 comment
Owner

In Bodhi, people very often give -1 karma for problems which are not regressions, but already exist in stable. We have it documented in https://fedoraproject.org/wiki/QA:Update_feedback_guidelines , but obviously, most people don't know about that document. Here's the an example.

It occurred to me that the most straightforward way to make more people familiar with the guidelines is to link to it directly from the Bodhi's feedback form.

In the "Karma: Is the update generally functional?" question we could make "generally functional" a link to https://fedoraproject.org/wiki/QA:Update_feedback_guidelines (or even https://fedoraproject.org/wiki/QA:Update_feedback_guidelines#update-functional ). Or add "(feedback guidelines)" link after the question, or similar.

I've defined anchors for each section of the document (see the wiki source), we could even link from each specific question to the right section.

The point of this ticket is to go through the document and make sure it's up-to-date. Possibly polish it a bit (maybe shorten the introduction - nobody's going to read long instructions), add some bold highlights, etc.

Then submit a patch to Bodhi to add links to this document (or document sections) to the feedback form. That shouldn't be a very difficult patch.

Btw, the guidelines could be linked from the question mark popup in the top right corner. I wouldn't do that, people won't find it there.

PS: The guide talks about "Does the system's basic functionality continue to work after this update?" question in Bodhi. I don't see in Bodhi. Maybe they removed it? Let's figure it out and update the guidelines accordingly.

Checklist:

  • Polish the guidelines
  • Submit a Bodhi patch
In Bodhi, people very often give -1 karma for problems which are not regressions, but already exist in stable. We have it documented in https://fedoraproject.org/wiki/QA:Update_feedback_guidelines , but obviously, most people don't know about that document. Here's the [an example](https://bodhi.fedoraproject.org/updates/FEDORA-2026-e8e294a7fa#comment-4704754). It occurred to me that the most straightforward way to make more people familiar with the guidelines is to link to it directly from the Bodhi's feedback form. In the "_Karma: Is the update generally functional?_" question we could make "generally functional" a link to https://fedoraproject.org/wiki/QA:Update_feedback_guidelines (or even https://fedoraproject.org/wiki/QA:Update_feedback_guidelines#update-functional ). Or add "_(feedback guidelines)_" link after the question, or similar. I've defined anchors for each section of the document (see the wiki source), we could even link from each specific question to the right section. The point of this ticket is to go through the document and make sure it's up-to-date. Possibly polish it a bit (maybe shorten the introduction - nobody's going to read long instructions), add some bold highlights, etc. Then submit a patch to Bodhi to add links to this document (or document sections) to the feedback form. That shouldn't be a very difficult patch. Btw, the guidelines could be linked from the question mark popup in the top right corner. I wouldn't do that, people won't find it there. PS: The guide talks about "_Does the system's basic functionality continue to work after this update?_" question in Bodhi. I don't see in Bodhi. Maybe they removed it? Let's figure it out and update the guidelines accordingly. **Checklist:** - [ ] Polish the guidelines - [ ] Submit a Bodhi patch
Author
Owner

Btw if somebody wants to only take the Bodhi patch part, but doesn't feel knowledgeable enough for polishing the guidelines document, I'm happy to take the document part and do just that.

Btw if somebody wants to only take the Bodhi patch part, but doesn't feel knowledgeable enough for polishing the guidelines document, I'm happy to take the document part and do just that.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
quality/tickets#915
No description provided.