From: Markus Armbruster <armbru@redhat.com>
To: Mark Cave-Ayland <mark.caveayland@nutanix.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [qemu-web PATCH] contribute: define clear limits on bug report volume
Date: Fri, 02 Oct 2026 13:20:53 +0200 [thread overview]
Message-ID: <874if42vsa.fsf@pond.sub.org> (raw)
In-Reply-To: <1362570a-8bb8-4303-88aa-418eb55b9ef9@nutanix.com> (Mark Cave-Ayland's message of "Fri, 2 Oct 2026 11:57:33 +0100")
Mark Cave-Ayland <mark.caveayland@nutanix.com> writes:
> On 24/09/2026 14:56, Daniel P. Berrangé wrote:
[...]
>> + Ignoring any of the above rules may lead to the bugs being
>> + mass closed without further triage, even if valid reports.
>> + In cases where the filing limits are grossly exceeded,
>> + the reporter's GitLab account may be reported for abuse
>> + (spam), potentially leading to termination.
>
> Do we know if people are doing this purely for the recognition? Perhaps we could suggest that if these rules are broken, all bug reports submitted by the reporter will remain private (to reporters) on GitLab: if a maintainer decides to fix a reported bug at their discretion, the original reporter will not be credited in the commit message.
Reducing the reward might be a possible partial replacement for
friction.
However, to not give credit for a bug we first need to fix the bug.
This has turned out to be pretty much infeasible in the cases covered by
the proposed policy.
[...]
prev parent reply other threads:[~2026-10-02 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:56 [qemu-web PATCH] contribute: define clear limits on bug report volume Daniel P. Berrangé
2026-09-24 15:12 ` Alex Bennée
2026-09-24 15:29 ` Daniel P. Berrangé
2026-10-02 11:12 ` Markus Armbruster
2026-09-25 7:51 ` Thomas Huth
2026-09-25 16:08 ` Richard Henderson
2026-09-30 8:57 ` Thomas Huth
2026-10-02 10:46 ` Markus Armbruster
2026-10-02 10:57 ` Mark Cave-Ayland
2026-10-02 11:20 ` Markus Armbruster [this message]
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=874if42vsa.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=mark.caveayland@nutanix.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.