Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <c828f525-8fdf-186a-2d18-582f534ecb61@gmx.com>
Date:   Mon, 3 Oct 2022 07:49:38 +0000
MIME-Version: 1.0
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla
 blues"
To:     Geert Uytterhoeven <geert@linux-m68k.org>
Cc:     Willy Tarreau <w@1wt.eu>,
        Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
        Theodore Ts'o <tytso@mit.edu>,
        Thorsten Leemhuis <linux@leemhuis.info>,
        Greg KH <gregkh@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>
References: <83f6dd2b-784a-e6d3-ebaf-6ad9cfe4eefe@gmx.com>
 <a676e5cf-c67b-7946-ce73-8fb8d63a5a0a@leemhuis.info>
 <Yzg7pHspc72I7TAb@mit.edu> <e98597e8-9ddb-bbf0-7652-691327186a92@gmx.com>
 <YzmBjgXq9geMnL1B@mit.edu> <79bb605a-dab8-972d-aa4a-a5e5ee49387c@gmx.com>
 <20221002150522.ul4nbtfawqjhnsag@meerkat.local>
 <b594681b-6b8c-ffb7-f526-3da847d160a8@gmx.com>
 <20221002205430.GC22129@1wt.eu>
 <d1f99826-2a66-c2d5-c9cd-d2fadd35eca4@gmx.com>
 <20221002213235.GA22532@1wt.eu>
 <867b35b7-da2b-fed0-1f75-b2021d9be499@gmx.com>
 <CAMuHMdVkFdXiqV-k2X8yDh5VkR3cv0a4z78z+uCF_PfgHgGx=Q@mail.gmail.com>
From:   "Artem S. Tashkinov" <aros@gmx.com>
In-Reply-To: <CAMuHMdVkFdXiqV-k2X8yDh5VkR3cv0a4z78z+uCF_PfgHgGx=Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Precedence: bulk


On 10/3/22 06:37, Geert Uytterhoeven wrote:
> Hi Artem,
>
> On Sun, Oct 2, 2022 at 11:54 PM Artem S. Tashkinov <aros@gmx.com> wrote:
>> It's easy to join an existing bug report. Tell me how can I join an
>> existing email thread without being first subscribed to it? I certainly
>> can, absolute most people will not be able to.
>
> lore.kernel.org
>
>> What about sending large dump files? Should everyone on the mailing lis=
t
>> receive it?
>
> post a link
>
>> A bug report is a simple plain list of messages in a single place which
>> could be read with a web browser. An email thread is anything but.
>
> lore.kernel.org
>
>> Searching through many emails at once? Good luck with that.
>
> lore.kernel.org
>
>> Replying to a particular email? Good luck with that.
>
> lore.kernel.org
>
>> It looks like you're under the impression that every Linux user who is
>> willing to ever use Linux must:
>>
>> 1) Subscribe to _all_ the existing mailing lists (just in case - what i=
f
>> you need to work on something which was started by someone else)
>
> lore.kernel.org
>
>> 2) Know the email etiquette
>
> Just Be Polite
>
>> 3) Learn to be persistent and resend (an unknown number of times) your
>> concerns hoping they will eventually be addressed.
>>
>> Bugzilla: sign up once. Follow up. If you file a dupe, hopefully it wil=
l
>> be marked as a dupe. Everyone's happy. No particular skills, email
>> clients, formatting, referencing, etc. etc. etc.
>
> Having at last the skill to provide a good rebug port would be nice...
>
> Now, back to work. The merge window has opened, so there will be
> bugs to report and/or fix...

Lore looks alien to me and in my life I've worked with a dozen bug tracker=
s.

* Where are open "issues"?
* Which issues are now resolved?
* What's the status of the "issue"?
* Which kernel subsystem is responsible for this or that "bug report"?
* How to change the assignee? How to know the new assignee has been
notified?

This thing looks interesting to discuss patches and merge requests
between developers who know each other and even at that it's not exactly
super intuitive. Again, you're not thinking about users who have no idea
how the kernel is developed.

If you remove bugzilla I'll never use lore.kernel.org, I promise. I'm
frightened by it.

Regards,
Artem