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;
Content-Type: text/plain;
        charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla
 blues"
From:   Slade Watkins <srw@sladewatkins.net>
In-Reply-To: <SJ1PR11MB60836F8B9E045C5542D01ADAFC569@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date:   Fri, 30 Sep 2022 13:49:01 -0400
Cc:     "Bird, Tim" <Tim.Bird@sony.com>,
        Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
        Thorsten Leemhuis <linux@leemhuis.info>,
        "Artem S. Tashkinov" <aros@gmx.com>,
        Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
        "workflows@vger.kernel.org" <workflows@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
        "ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A947768-A4CC-4BE8-AFF3-056CAE266674@sladewatkins.net>
References: <aa876027-1038-3e4a-b16a-c144f674c0b0@leemhuis.info>
 <05d149a0-e3de-8b09-ecc0-3ea73e080be3@leemhuis.info>
 <93a37d72-9a88-2eec-5125-9db3d67f5b65@gmx.com>
 <20220929130410.hxtmwmoogzkwcey7@meerkat.local>
 <7b427b41-9446-063d-3161-e43eb2e353f9@gmx.com>
 <20220929135325.4riz4ijva2vc7q5p@meerkat.local>
 <95c3384b-53d0-fd6c-6ec5-a7e03fdeddfc@gmx.com>
 <F300ED64-5E8E-4060-89DC-C98BC5FF08E6@sladewatkins.net>
 <YzXK6Px+BrNuuMZH@pendragon.ideasonboard.com>
 <a86adc6d-05db-ec2e-c5de-d280aad9fb8a@leemhuis.info>
 <Yzbtuz6L1jlDCf9/@pendragon.ideasonboard.com>
 <BYAPR13MB250377AAFCC43AC34E244795FD569@BYAPR13MB2503.namprd13.prod.outlook.com>
 <SJ1PR11MB60836F8B9E045C5542D01ADAFC569@SJ1PR11MB6083.namprd11.prod.outlook.com>
To:     "Luck, Tony" <tony.luck@intel.com>
Precedence: bulk

Hey:

> On Sep 30, 2022, at 1:28 PM, Luck, Tony <tony.luck@intel.com> wrote:
>=20
>> E-mails sent from a web interface could have as much structure as =
you'd like.
>> So one avenue would be to set up a nice interface for bug reporting, =
that just
>> delivered the form data in e-mail format to the proposed =
bug-receiving mail list.
>=20
> Web interfaces have the advantage that they can be full of boxes which =
indicate
> useful details to supply. Like what kernel version? Did this work on =
an older version,
> is so, which one? Which CPU vendor/model are you using? Is there an =
error message?
> Are there warnings in the console log before the error? Can you upload =
a full console log?
> Does this happen repeatably? What are the steps to reproduce?

Not to mention, they have the advantage of being faster, in a lot of =
cases. (Sometimes, just a few keystrokes and an issue is filed. Saves =
everyone time.)

> Sometimes it takes a few round trips by e-mail to establish the =
baseline facts.

+1 to this, it=E2=80=99s much easier to have that information =
immediately at hand. It helps no one when you have to wait for it all to =
trickle via email taking days if not weeks. Waste of everyone=E2=80=99s =
time, in my mind.

As I=E2=80=99ve said=E2=80=94my opinion is that email is good for =
discussions, but  is not great for bug reports (at least, the initial =
ones that have all the base information.)=20

-srw