Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #93797
| From | Yunseong Kim <ysk@kzalloc.com> |
|---|---|
| Newsgroups | linux.debian.kernel |
| Subject | Re: Agenda items for kernel-team meeting on 2026-08-19 |
| Date | 2026-08-19 17:20 +0200 |
| Message-ID | <NtQf8-bUnP-13@gated-at.bofh.it> (permalink) |
| References | <NtOZH-bTCD-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Ben,
On 19/08/2026 3:56 pm, Ben Hutchings wrote:
> This week's meeting will happen today (2026-08-19) at 21:00 CEST = 19:00
> UTC. This time it will be on Jitsi if possible, otherwise we will fall
> back to IRC.
>
> The agenda is here:
> https://salsa.debian.org/kernel-team/meetings/-/wikis/20260819
>
> I will attempt to add summaries of each bug's status before the meeting.
>
> Please reply to this message if you want to add items.
Recently, I started drafting some guidance on avoiding unhelpful or
harmful AI-generated kernel bug reports, including reports submitted
without using reportbug.
Do you think it would be worthwhile to add a section to the kernel
handbook [1], extend the DebianKernelReportingBugs wiki page [2], or
perhaps create a dedicated page covering this topic?
A rough draft is below:
---
= Debian Kernel Bug Reporting Etiquette: AI-Generated Reports =
AI tools can be useful for improving writing quality, but they should
not replace the factual information needed for diagnosing kernel issues.
Submitting unverified AI-generated output to the bug tracker or kernel
mailing lists is not a substitute for a proper bug report. Maintainers
and developers volunteer significant amounts of time to investigate
reported issues, and providing fabricated, guessed, or AI-invented
technical details wastes that effort.
When reporting kernel bugs, please provide real observations, actual
logs, reproduction steps, and system information.
Better yet, Please run: {{{
$ reportbug kernel }}}
The scripts in /usr/share/bug/linux-base/ and
/usr/share/bug/linux-image-*/ automatically collect information that
maintainers frequently need, including kernel taint status
(/proc/sys/kernel/tainted), loaded modules (lsmod), hardware details
(lspci -knn), and other diagnostic data [3].
If you are asking others to spend their time investigating a problem,
please provide accurate information gathered from the affected system.
Honest diagnostic data is far more valuable than unverifiable
AI-generated text.
= References =
[1] https://salsa.debian.org/kernel-team/kernel-handbook
[2] https://wiki.debian.org/DebianKernelReportingBugs
[3] https://kernel-team.pages.debian.net/kernel-handbook/ch-bugs.html#s9.1.1
---
> Ben.
>
Best regards,
Yunseong
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Agenda items for kernel-team meeting on 2026-08-19 Ben Hutchings <ben@decadent.org.uk> - 2026-08-19 16:00 +0200
Re: Agenda items for kernel-team meeting on 2026-08-19 Yunseong Kim <ysk@kzalloc.com> - 2026-08-19 17:20 +0200
[Question] Guidance on LLM-assisted bug reporting in Debian Yunseong Kim <ysk@kzalloc.com> - 2026-09-03 16:40 +0200
csiph-web