Workflows Archive on lore.kernel.org
 help / color / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ksummit-discuss@lists.linuxfoundation.org,
	workflows@vger.kernel.org,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [Ksummit-discuss] RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions
Date: Mon, 22 Mar 2021 20:49:52 +0100
Message-ID: <4dcc2b8e-719e-e171-f236-9b28c8c0bae9@leemhuis.info> (raw)
In-Reply-To: <CAKXUXMw7kHBPov23kF1HUBrW9DL+huqAG8ZRLJwGgU67nCOPeg@mail.gmail.com>

On 22.03.21 17:55, Lukas Bulwahn wrote:
> On Mon, Mar 22, 2021 at 4:38 PM Thorsten Leemhuis <linux@leemhuis.info> wrote:
>> Lo! I want to provide users with an easier way to search our multitude
>> of mailing lists for reports about issues (aka bugs), as reporting the
>> same kernel problem multiple times has known downsides for everyone
>> involved. That's why I propose to create this new mailing list:
>>
>> linux-issues@lists.linux.dev
>>
>> Developers and users reporting or handling issues then can CC it or
>> search it via lore. But this will only fly if the idea has buy-in from
>> at least the core kernel maintainers, to make sure they and the
>> developers actually use it. That's why I'm looking for feedback with
>> this mail and also CCed ksummit-discuss, as that's the easiest way to
>> make sure maintainers get aware of this idea and can raise their voice.
>>
>>
>> Note, there is a second reason why ksummit-discuss is CCed: another
>> reason why I want to create this new list is making it easier to find
>> and track regressions reported to our various mailing lists (often
>> without LKML in CC, as for some subsystems it's seems to be custom to
>> not CC it). Back on the maintainers summit in 2017 it was agreed to
>> create a dedicated list for this purpose
>> (https://lwn.net/Articles/738216/). I even requested a
>> "linux-regressions@vger.kernel.org" a while later, but didn't hear
>> anything back; and, sadly, about the same time I started having trouble
>> finding spare time for working on regression tracking. :-/
>>
>> But I soon will get back into that area:
>> https://linux-regtracking.leemhuis.info/post/hello-world/ Hence it's a
>> good time to prepare some groundwork for that. But these days I think
>> having something like linux-regressions@lists.linux.dev might be over
>> engineered, at least for now: a linux-issues@lists.linux.dev with a
>> simple "[regressions]" in the subject will suffice, as that tag is
>> something a lot of people are used to already. And if we think we need
>> that list we can still create it in the future. Or what do you folks
>> think about it?
> 
> Thorsten, I generally support this initiative. I am just wondering:
> 
> What is the definition of an issue for you?

Good question, but that is up to us. But FWIW, here is my stance:

> Just four examples that come to my mind:
> 
> - all the warnings that Stephen Rothwell reports on linux-next, such
> as https://lore.kernel.org/linux-next/20210322170452.726525e8@canb.auug.org.au/
> or https://lore.kernel.org/linux-next/20210322075108.3967d5d1@canb.auug.org.au/?

I'd have no problem with those, but those are more devel internal issues
and nothing users would face, so I'm don't think it will buy us anything.

> - all the issues that the kernel test robot reports?

I'd say so, at least those that are regressions, as I want to track them ;-)

> - all the errors and warnings that kernel ci reports? Basically, each
> "issue" that is already aggregated in this email,
> https://lore.kernel.org/linux-next/6058787c.1c69fb81.d3f10.8c6d@mx.google.com/?
> - all the syzbot reports?
>
> Are you including all those automatic testing and checking efforts as
> reporting valid "issues"?

Well, the purpose of that list would be "make it easier to find existing
reports". Too much noise works against that, so we should try to limit
it, so maybe those are better left out, unless it's something we known
users might face.

> Or would you like to keep this list only for
> reports from single individual human users that need to detect the
> "issue" without using one of the tools above?

Guess something like that might be best strategy.

Ciao, Thorsten

  reply index

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 15:18 Thorsten Leemhuis
2021-03-22 16:55 ` [Ksummit-discuss] " Lukas Bulwahn
2021-03-22 19:49   ` Thorsten Leemhuis [this message]
2021-03-22 17:16 ` Konstantin Ryabitsev
2021-03-22 17:57   ` [Ksummit-discuss] " James Bottomley
2021-03-22 18:34     ` Eric Wong
2021-03-22 18:55       ` Thorsten Leemhuis
2021-03-22 19:20         ` Konstantin Ryabitsev
2021-03-22 18:32 ` Linus Torvalds
2021-03-22 19:25   ` Thorsten Leemhuis
2021-03-22 21:56     ` [Ksummit-discuss] " Theodore Ts'o
2021-03-23  8:57       ` Thorsten Leemhuis
2021-03-23 15:01         ` Konstantin Ryabitsev
2021-03-23 19:09           ` Thorsten Leemhuis
2021-03-23 18:11         ` Theodore Ts'o
2021-03-23 18:51           ` Thorsten Leemhuis
2021-03-23 14:57     ` Luis Chamberlain
2021-03-23 16:20     ` Steven Rostedt
2021-03-23 16:30       ` [Ksummit-discuss] " James Bottomley
2021-03-23 21:43         ` Konstantin Ryabitsev
2021-03-23 23:11           ` Eric Wong
2021-03-23 18:07       ` Theodore Ts'o

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=4dcc2b8e-719e-e171-f236-9b28c8c0bae9@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=gregkh@linuxfoundation.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --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

Workflows Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/workflows/0 workflows/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 workflows workflows/ https://lore.kernel.org/workflows \
		workflows@vger.kernel.org
	public-inbox-index workflows

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.workflows


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git