From: "Artem S. Tashkinov" <aros@gmx.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Steven Rostedt <rostedt@goodmis.org>,
Theodore Ts'o <tytso@mit.edu>,
Thorsten Leemhuis <linux@leemhuis.info>,
Greg KH <gregkh@linuxfoundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
workflows@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
ksummit@lists.linux.dev,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues"
Date: Mon, 3 Oct 2022 09:16:06 +0000 [thread overview]
Message-ID: <251201be-9552-3a51-749c-3daf4d181250@gmx.com> (raw)
In-Reply-To: <YzqjfU66alRlGk5y@kernel.org>
On 10/3/22 08:55, Mike Rapoport wrote:
> On Mon, Oct 03, 2022 at 07:41:08AM +0000, Artem S. Tashkinov wrote:
>>
>>
>> On 10/2/22 23:04, Al Viro wrote:
>>> On Sun, Oct 02, 2022 at 10:20:40PM +0000, Artem S. Tashkinov wrote:
>>>
>>>> Bugzilla hasn't been updated in a very long time so it's missing both
>>>> mailing lists and individual kernel developers.
>>>>
>>>> AFAIK, some pieces of kernel have no appropriate mailing lists at all.
>>>> What about that? I've no clue.
>>>
>>> There's that file, right in the root of the source tree. Called "MAINTAINERS",
>>> in all-caps... Could have something to do with locating maintainers, could it not?
>>>
>>>> Opt-in will work, except I've no idea how to make it work. Mass email
>>>> all the kernel developers and politely invite them to sign up? Most will
>>>> simply ignore it.
>>>
>>> Sigh... You really don't seem to appreciate just how deep a septic
>>> tank you've jumped into with your combination of "it should be opt-out"
>>> and "but unsubscribing takes just a minute, what are you unhappy about?!?"
>>>
>>> Maybe you are not using email a lot, but for just about everyone who does...
>>> We have heard that. Many, many times. From many sources - spammers,
>>> "legitimate" companies' marketing departments, etc.
>>>
>>> And you keep moving along the same track - the usual reaction of some
>>> company after having pulled back a bloody stump and enjoyed the pile of
>>> explanations of the reasons why opt-out is *NOT* *ACCEPTABLE*, *EVER*
>>> is along the lines of "OK, we'll just spam everyone in our database once
>>> and ask them to opt-in - that must be OK, right?"
>>
>> Being on bugzilla does _not_ mean you'll receive a single email unless
>> someone _specifically_ CC's you.
>
> If I'm not mistaken, bugzilla lets CC people explicitly. How the database
> of emails in bugzilla would help choosing the right people to CC better
> than MAINTAINERS?
>
> You repeated multiple times that bug reports sent to the mailing lists are
> ignored, but what will make emails from bugzilla different from those bug
> reports? Why do you think they will get more attention?
Maybe because they are specific? Maybe because they are not part of a
high volume mailing list such as LKML? Maybe because lots of developers
are _not_ on any mailing lists?
>
>> Anyways, Bugzilla is bad but it surely works. Let's have 100+ more
>> interchanges inventing something most users (for whom Bugzilla exists -
>> which people here keep forgetting all the time) will a have hard time
>> working with.
>
> You keep repeating that bugzilla is better then email, but the major point
> here is not the tools, but the lack of resources to deal with initial
> triage of the bugs and holding users' hand to get a meaningful report.
> Until that changes, there is no point in trying to add more people CC'ed on
> bugzilla reports. They won't be handled unless somebody would want to take
> care of them and forcing people to receive these reports won't make anybody
> more willing to help.
The initial conversation started with the fact that Bugzilla is old,
semi-deprecated, requires MySQL [no idea what's bad about it, Bugzilla
can work with MariaDB and Percona as well] and its components along with
the respective emails are extremely outdated. If I remember correctly
triaging bugs was raised much later in the discussion and is orthogonal
to the topic.
Triaging bugs could be and should be done by the people who are willing
to help [for free]. There's no problem with bugs filed under "Other" if
the reporter has no idea where to file them as long as they are visible
and searchable.
Imagine instead you send your issue to a random mailing list. What is
the chance another person with a similar issue will even find it?
Vanishingly low. The net result? Work and time wasted and no one is aware.
Again the volume of bug reports is relatively low, fewer than two dozen
a week.
Everything about Bugzilla so far has been completely blown out of
proportions:
* The insane number of emails it ostensibly sends: "OMG so much SPAM,
save me from it!"
* The privacy "issue" despite git commits and respective email addresses
being public
* The amount of work required to keep its components and email addresses
up to date - could be done maybe every 12-24 months
* The triaging "issue" which is outside the scope of this conversation
At the same time:
* Multiple reporters can perfectly find the people who have made bad
commits or who are responsible for certain drivers - it's safer to CC
them _via_ Bugzilla than to email them _privately_ or via mailing lists
which entails multiple issues including trust, SPAM, formatting,
English, net etiquette, etc. etc. etc.
You don't like Bugzilla? Fine, never touch it, never visit the website.
Never get emails from it.
Regards,
Artem
next prev parent reply other threads:[~2022-10-03 9:16 UTC|newest]
Thread overview: 155+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aa876027-1038-3e4a-b16a-c144f674c0b0@leemhuis.info>
2022-09-29 11:33 ` Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues" Thorsten Leemhuis
2022-09-29 12:22 ` Artem S. Tashkinov
2022-09-29 12:52 ` Greg KH
2022-09-29 13:09 ` Artem S. Tashkinov
2022-09-29 13:21 ` Greg KH
2022-09-29 13:23 ` Konstantin Ryabitsev
2022-09-29 13:04 ` Konstantin Ryabitsev
2022-09-29 13:31 ` Artem S. Tashkinov
2022-09-29 13:43 ` Greg KH
2022-09-29 13:53 ` Konstantin Ryabitsev
2022-09-29 14:22 ` Artem S. Tashkinov
2022-09-29 14:54 ` Slade Watkins
2022-09-29 16:42 ` Laurent Pinchart
2022-09-29 19:00 ` Slade Watkins
2022-09-30 9:35 ` Thorsten Leemhuis
2022-09-30 13:23 ` Laurent Pinchart
2022-09-30 16:19 ` Bird, Tim
2022-09-30 16:34 ` Artem S. Tashkinov
2022-09-30 16:47 ` Laurent Pinchart
2022-10-01 1:18 ` Theodore Ts'o
2022-10-01 2:47 ` Slade Watkins
2022-10-01 7:57 ` Bagas Sanjaya
2022-10-01 13:01 ` Theodore Ts'o
2022-10-03 6:55 ` Christoph Hellwig
2022-09-30 17:36 ` Slade Watkins
2022-09-30 16:36 ` Laurent Pinchart
2022-09-30 17:28 ` Luck, Tony
2022-09-30 17:49 ` Slade Watkins
2022-09-30 20:04 ` Randy Dunlap
2022-09-30 20:29 ` Thorsten Leemhuis
2022-09-29 15:31 ` Konstantin Ryabitsev
2022-09-29 15:39 ` Slade Watkins
2022-09-29 16:06 ` Artem S. Tashkinov
2022-09-29 20:26 ` Slade Watkins
2022-09-30 8:47 ` Thorsten Leemhuis
2022-09-30 9:03 ` Artem S. Tashkinov
2022-09-30 10:37 ` Slade Watkins
2022-09-30 15:32 ` Laurent Pinchart
2022-10-03 11:44 ` Jani Nikula
2022-09-29 15:26 ` James Bottomley
2022-09-30 8:52 ` Artem S. Tashkinov
2022-09-29 13:47 ` Steven Rostedt
2022-09-29 14:02 ` Thorsten Leemhuis
2022-09-29 14:12 ` Steven Rostedt
2022-10-01 10:30 ` Artem S. Tashkinov
2022-10-01 10:39 ` Greg KH
2022-10-01 10:47 ` Artem S. Tashkinov
2022-10-01 10:57 ` Thorsten Leemhuis
2022-10-01 11:21 ` Artem S. Tashkinov
2022-10-01 11:34 ` Thorsten Leemhuis
2022-10-01 13:07 ` Theodore Ts'o
2022-10-01 14:58 ` Artem S. Tashkinov
2022-10-02 12:18 ` Theodore Ts'o
2022-10-02 12:49 ` Artem S. Tashkinov
2022-10-02 14:35 ` Greg KH
2022-10-02 19:27 ` Artem S. Tashkinov
2022-10-02 20:46 ` Linus Torvalds
2022-10-02 20:56 ` Artem S. Tashkinov
2022-10-02 21:07 ` Linus Torvalds
2022-10-02 21:27 ` Artem S. Tashkinov
2022-10-02 21:40 ` Willy Tarreau
2022-10-02 21:57 ` Artem S. Tashkinov
2022-10-02 14:48 ` Slade Watkins
2022-10-02 19:37 ` Artem S. Tashkinov
2022-10-02 21:11 ` Laurent Pinchart
2022-10-02 21:38 ` Artem S. Tashkinov
2022-10-02 15:05 ` Konstantin Ryabitsev
2022-10-02 19:43 ` Artem S. Tashkinov
2022-10-02 20:54 ` Willy Tarreau
2022-10-02 21:07 ` Artem S. Tashkinov
2022-10-02 21:32 ` Willy Tarreau
2022-10-02 21:53 ` Artem S. Tashkinov
2022-10-03 6:37 ` Geert Uytterhoeven
2022-10-03 7:49 ` Artem S. Tashkinov
2022-10-03 10:04 ` Willy Tarreau
2022-10-02 15:56 ` Al Viro
2022-10-02 17:22 ` Slade Watkins
2022-10-02 16:08 ` Geert Uytterhoeven
2022-10-02 16:10 ` Geert Uytterhoeven
2022-10-02 16:32 ` Joe Perches
2022-10-02 18:56 ` Joe Perches
2022-10-02 19:46 ` Artem S. Tashkinov
2022-10-02 17:57 ` Willy Tarreau
2022-10-02 19:55 ` Artem S. Tashkinov
2022-10-02 20:40 ` Willy Tarreau
2022-10-02 18:13 ` Steven Rostedt
2022-10-02 20:14 ` Artem S. Tashkinov
2022-10-02 22:08 ` Steven Rostedt
2022-10-02 22:20 ` Artem S. Tashkinov
2022-10-02 22:28 ` Steven Rostedt
2022-10-02 23:04 ` Al Viro
2022-10-02 23:21 ` Steven Rostedt
2022-10-03 7:41 ` Artem S. Tashkinov
2022-10-03 8:55 ` Mike Rapoport
2022-10-03 9:15 ` David Laight
2022-10-03 9:16 ` Artem S. Tashkinov [this message]
2022-10-03 9:26 ` Geert Uytterhoeven
2022-10-03 9:40 ` Artem S. Tashkinov
2022-10-03 10:26 ` Mike Rapoport
2022-10-03 14:20 ` Steven Rostedt
2022-10-03 18:24 ` Al Viro
2022-10-03 19:07 ` Steven Rostedt
2022-10-03 20:28 ` Slade Watkins
2022-10-04 12:16 ` Artem S. Tashkinov
2022-10-04 12:32 ` Geert Uytterhoeven
2022-10-04 22:45 ` Steven Rostedt
2022-10-03 14:22 ` Konstantin Ryabitsev
2022-10-04 12:21 ` Artem S. Tashkinov
2022-10-04 14:20 ` Konstantin Ryabitsev
2022-10-03 15:37 ` Konstantin Ryabitsev
2022-10-04 7:37 ` Thorsten Leemhuis
2022-10-04 7:56 ` Conor Dooley
2022-10-04 12:24 ` Artem S. Tashkinov
2022-10-04 14:48 ` Konstantin Ryabitsev
2022-10-02 20:41 ` Slade Watkins
2022-10-02 20:52 ` Slade Watkins
2022-10-02 21:06 ` Laurent Pinchart
2022-10-02 22:18 ` Steven Rostedt
2022-10-02 22:41 ` Laurent Pinchart
2022-10-02 23:59 ` Slade Watkins
2022-10-02 18:17 ` Geert Uytterhoeven
2022-10-02 20:17 ` Artem S. Tashkinov
2022-10-02 20:48 ` Willy Tarreau
2022-10-02 19:59 ` Laurent Pinchart
2022-10-02 20:19 ` Artem S. Tashkinov
2022-10-02 20:26 ` Laurent Pinchart
2022-10-02 13:25 ` Slade Watkins
2022-10-02 9:03 ` Geert Uytterhoeven
2022-10-02 9:06 ` Artem S. Tashkinov
2022-10-02 9:25 ` Geert Uytterhoeven
2022-10-02 7:37 ` Takashi Iwai
2022-10-02 8:23 ` Artem S. Tashkinov
2022-10-02 8:53 ` Geert Uytterhoeven
2022-10-02 9:14 ` Takashi Iwai
2022-10-03 10:10 ` Thorsten Leemhuis
2022-10-03 11:18 ` Slade Watkins
2022-10-03 12:59 ` Thorsten Leemhuis
2022-10-03 15:26 ` Steven Rostedt
2022-10-03 15:44 ` Laurent Pinchart
2022-10-03 15:51 ` Steven Rostedt
2022-10-03 15:59 ` Laurent Pinchart
2022-10-03 16:03 ` Steven Rostedt
2022-10-04 8:41 ` Thorsten Leemhuis
2022-10-04 9:20 ` Geert Uytterhoeven
2022-10-04 10:16 ` Thorsten Leemhuis
2022-10-04 10:45 ` Geert Uytterhoeven
[not found] ` <20221004175354.bfvg3vhfqch35ib5@meerkat.local>
[not found] ` <Yzx1T05Ut0of55KY@kroah.com>
2022-10-04 18:13 ` Konstantin Ryabitsev
[not found] ` <87fsg3s8co.fsf@intel.com>
2022-10-04 19:24 ` Konstantin Ryabitsev
[not found] ` <c74d9d75-4428-e22d-1adb-334b1173d871@leemhuis.info>
2022-10-04 20:25 ` Konstantin Ryabitsev
2022-10-05 9:00 ` Thorsten Leemhuis
2022-10-05 9:57 ` Hans de Goede
2022-10-12 16:12 ` Thorsten Leemhuis
2022-10-17 13:57 ` Thorsten Leemhuis
2022-10-17 20:47 ` Konstantin Ryabitsev
2022-10-18 16:24 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=251201be-9552-3a51-749c-3daf4d181250@gmx.com \
--to=aros@gmx.com \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mario.limonciello@amd.com \
--cc=regressions@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).