Summary: | bugs.kde.org repeatedly refers to all issues (including feature requests) as "bugs" (terminology) | ||
---|---|---|---|
Product: | [Websites] bugs.kde.org | Reporter: | Philippe Cloutier <chealer> |
Component: | general | Assignee: | KDE sysadmins <sysadmin> |
Status: | CLOSED UPSTREAM | ||
Severity: | normal | CC: | nate, sheedy, teamtesting66 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | All | ||
URL: | http://community.kde.org | ||
Latest Commit: | Version Fixed In: |
Description
Philippe Cloutier
2019-07-27 16:08:00 UTC
bugs.kde.org is definitely intended to be used for both bugs and feature requests. That's why there's a "wishlist" classification. You're not wrong about any of this though. We often use the word "bug" to refer to Bugzilla tickets, regardless of whether they track a bug or a feature request. I have updated the documentation to use the more generic terms "Issue" and "Bugzilla ticket" instead. Hopefully that should clear this up. See https://community.kde.org/Get_Involved/Issue_Reporting and https://community.kde.org/Get_Involved#Issue_Reporting. Thank you very much Nate. I am re-titling to clarify that, assuming that comment 1 is correct, bugs.kde.org needs fixing. I am afraid there may be lots of place which need to be switched to proper terms. Without pretending to be exhaustive, all of the following places are currently incoherent: # Site title "KDE Bugtracking System", which could read "KDE Issue Tracking System", or - more succinctly - "KDE Issue Tracker". # The homepage only offers to "File a Bug", and doing that brings to an "Enter Bug" page. # The ticket visualization/edition controller presents all issues as "bugs", even those with importance "wishlist" (see https://bugs.kde.org/show_bug.cgi?id=9055 for example) # To my knowledge, the site only has subdomain "bugs.kde.org", which - while not necessarily a bug, is at least misleading. It would be much clearer to at least support access through a representative subdomain, such as "issues.kde.org". There is still some work needed on community.kde.org, at least on https://community.kde.org/Get_Involved/Issue_Reporting. For example, the name of step #1 ("Step 1: Make sure it's a valid bug or feature request") currently doesn't allow requests for improvements other than feature additions and bug-fixes. Looking at https://bugs.kde.org/show_bug.cgi?id=409930 I am afraid that statuses need fixing too. It is currently possible for tickets with importance "wishlist" to be set to status RESOLVED NOT A BUG. This status should probably become INVALID. There's a certain amount of this that's not really resolvable, and people will just need to interpret things accordingly. That said I do think the proposed changes to bugs.kde.org are reasonable. This also needs changing the Importance field's name from current "Severity" to "Importance", when filing a ticket. Also, this may exceed this ticket's scope, but either the default value for Severity should be undetermined, or there should be none. (In reply to Nate Graham from comment #4) > There's a certain amount of this that's not really resolvable, and people > will just need to interpret things accordingly. Can you clarify which amount or which part is not really resolvable? > [...] Could you explain your latest changes to this ticket? Do you want the part about community.kde.org to be tracked in a different ticket? Please upgrade this ticket's importance to at least major. We could change the subdomain to "issues" and add a redirect to the "bugs" subdomain, but ultimately the "bug" terminology is all over Bugzilla itself, as a matter of its original design. As such, real improvements here would need to be implemented upstream in Bugzilla itself; please report there if it's something you're still interested in. Thanks! |