[kde] [Bug 410284] New: community.kde.org (and bugs.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

            Bug ID: 410284
           Summary: community.kde.org (and bugs.kde.org) inconsistent
                    about reporting KDE issues other than defects on
                    bugs.kde.org
           Product: kde
           Version: unspecified
          Platform: Other
               URL: http://community.kde.org
                OS: All
            Status: REPORTED
          Severity: grave
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: chealer at gmail.com
  Target Milestone: ---

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.

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