https://community.kde.org/Get_Involved#Getting_in_touch_and_working_together claims it is possible to report KDE issues other than defects on bugs.kde.org: > The KDE Bugzilla bug tracker is intended for user-to-developer communication and tracks simple bug reports and feature requests. However, a different page on the same site says before reporting a problem, one should "make sure" that it is a real bug: > Step 1: Make sure it's a real bug That page is titled "Bug Reporting", but appears to cover issue reporting in general. As for bugs.kde.org, when one follows the "New" link, one lands on a page titled "Enter Bug", which starts with: > First, you must pick a product on which to enter a bug: And then, at least 1 KDE developer claims that "entries in bugs.kde.org are bugs, not tickets": https://bugs.kde.org/show_bug.cgi?id=409930#c1 I cannot determine what the bug is, so I will merely report inconsistency here, but either: 1. there is a huge terminological flaw on both bugs.kde.org and other sites which refers to all issues as "bugs" 2. or bugs.kde.org's sole purpose is to track bugs, in which case community.kde.org should point reporters of issues other than defects elsewhere. There should urgently be a project decision taken to confirm the way to go. In any case, bugs.kde.org definitely has lots of tickets which do not report bugs, and trying to stick to bugs would mean: 1. lots of work getting rid of tickets which request mere enhancements 2. the need for another system for other tickets, which would cause much duplication of work for infrastructure maintainers and inefficiency for contributors Looking at https://www.bugzilla.org/about/ I think we can conclude the problem was initially terminological. According to that, Bugzilla was initially a bug tracking system. The following sentence alone demonstrates Bugzilla has a acute language problem: > Defect-tracking systems allow teams of developers to keep track of outstanding bugs, problems, issues, enhancement and other change requests in their products effectively. In my opinion, KDE has developed a terminological problem due to Bugzilla's, and this terminological problem has transformed into an actual understanding problem for a minority of contributors. By the way, there is visibly no other way to report an issue in community.kde.org than to report against the kde product.
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!