From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Artem S. Tashkinov" <aros@gmx.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org
Date: Mon, 08 Nov 2021 15:00:02 +0200 [thread overview]
Message-ID: <871r3q950t.fsf@intel.com> (raw)
In-Reply-To: <0b78b74e-5c72-1258-8373-5385d5709a6c@gmx.com>
On Mon, 08 Nov 2021, "Artem S. Tashkinov" <aros@gmx.com> wrote:
> It does *not* help one bit that we have different bug trackers and
> mailing lists for a *single* component which is the kernel. No other
> software project under the sun makes the user rack their head trying to
> understand how and where to post bug reports.
I suppose the kernel is a single component only from a fairly narrow
user centric view. Sure, it would be nice, from a user perspective, to
have a single bug tracker for everything. But behind the scenes, the
kernel development community is so broad and fragmented it's basically
impossible to get people to agree on a tracker that would suit everyone
and that everyone would use. Furthermore, there are users that insist on
reporting bugs on their own terms anyway, refusing to sign up to any
trackers.
Arguably "the single bug tracker" most users should report their kernel
problems for triage first is their distro bug tracker.
> Can we shut down bugzilla.kernel.org completely? In its current form
> it's nothing but disgrace.
Works for me, ymmv.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2021-11-08 13:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 12:10 [PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org Thorsten Leemhuis
2021-01-11 18:14 ` Randy Dunlap
2021-01-11 18:55 ` Thorsten Leemhuis
2021-01-11 23:42 ` Randy Dunlap
2021-01-12 17:34 ` Thorsten Leemhuis
2021-01-11 19:48 ` Konstantin Ryabitsev
2021-01-12 19:09 ` Thorsten Leemhuis
2021-01-13 11:17 ` Jani Nikula
2021-01-14 19:18 ` Konstantin Ryabitsev
2021-11-05 14:36 ` Artem S. Tashkinov
2021-11-05 14:42 ` Matthew Wilcox
2021-11-05 14:59 ` Artem S. Tashkinov
2021-11-08 11:43 ` Jani Nikula
2021-11-08 12:03 ` Artem S. Tashkinov
2021-11-08 13:00 ` Jani Nikula [this message]
2021-11-08 13:17 ` Artem S. Tashkinov
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=871r3q950t.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=aros@gmx.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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 NNTP newsgroup(s).