linux-kernel - Re: [PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0b78b74e-5c72-1258-8373-5385d5709a6c@gmx.com>
Date:   Mon, 8 Nov 2021 12:03:20 +0000
From:   "Artem S. Tashkinov" <aros@....com>
To:     Jani Nikula <jani.nikula@...ux.intel.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH v1 (RFC)] docs: discourage users from using
 bugzilla.kernel.org



On 11/8/21 11:43, Jani Nikula wrote:
> On Fri, 05 Nov 2021, "Artem S. Tashkinov" <aros@....com> wrote:
>> Let me continue.
>>
>> Here's something which is really bad for bugzilla.kernel.org:
>>
>> People _continue_ to file bug reports for graphics drivers in Linux and
>> we don't even have proper components for it, only
>>
>> Video (AGP) - What? AGP has been dead for a decade.
>> Video (DRI - Non Intel)  - what? Isn't it an X.org's feature, not kernel's?
>> Video (Other)
>>
>> This is a complete and total clusterjoy.
>
> FWIW, for Intel graphics (i915) we don't want any bug reports at
> bugzilla.kernel.org. We've migrated away more than five years ago. The
> "Video (DRI - Intel)" component was closed for new bugs around that


 From my initial message:


---
2.6 You're under the impression that users will read this wonderful
document (reporting-bugs.rst). They will *not*, they will google for
"report bug linux kernel" and find bugzilla.kernel.org

2) To integrate the first three with https://gitlab.freedesktop.org/drm/
and automatically crosspost over there.
---


It does *not* help one bit that we have different bug trackers and
mailing lists for a *single* component which is the kernel. No other
software project under the sun makes the user rack their head trying to
understand how and where to post bug reports.

And then like I've mentioned earlier:


---
2.1 Tons of messages in various kernel related mailing lists have zero
replies and are not acted upon in any way or shape

2.2 There's no sense of accountability, no way to see what are the
current issues, what's resolved or not

2.3 Users have an extremely hard time looking for bug reports which are
spread along God knows where

2.4 It's impossible to follow up on such messages except when you were
subscribed to the original mailing list, IOW just impossible

2.5 It's extremely difficult to collaborate since e-mail totally sucks
when it comes to long discussions.
---


The Linux kernel bug reporting process is a complete clusterfuck and it
looks like no one cares at all. The consensus is "the harder it is, the
better" since unreported bugs means less work, accountability and
responsibility.

The fact that no one from FSF has replied to any of my messages is a
further confirmation. Budget ~$2 million in FY 2019. I guess two million
bucks are not enough to take proper care of the most important FSF project.

Can we shut down bugzilla.kernel.org completely? In its current form
it's nothing but disgrace.

> time, the description points at freedesktop.org as does MAINTAINERS:
>
> INTEL DRM DRIVERS (excluding Poulsbo, Moorestown and derivative chipsets)
> B:	https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
>
>
> BR,
> Jani.
>
>