[kde] [Bug 410284] bugs.kde.org and community.kde.org inconsistent about reporting KDE issues other than defects on bugs.kde.org

[Filipus Klutiero]

https://bugs.kde.org/show_bug.cgi?id=410284

Filipus Klutiero <chealer at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---
     Ever confirmed|0                           |1
            Summary|community.kde.org (and      |bugs.kde.org and
                   |bugs.kde.org) inconsistent  |community.kde.org
                   |about reporting KDE issues  |inconsistent about
                   |other than defects on       |reporting KDE issues other
                   |bugs.kde.org                |than defects on
                   |                            |bugs.kde.org

--- Comment #2 from Filipus Klutiero <chealer at gmail.com> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.