[17:49] <Laibsch> rbasak: Can we please encourage the Christopher to stop his unhelpful, robot-like "triaging"?  Here is another example of the nonsense: bug 1395003
[17:49] <Laibsch> The information given is about as close to a patch as it gets.
[17:49] <Laibsch> yet, the penalv-bot runs his scrips to keep people busy needlessly
[17:56] <Laibsch> unrelated question: is it OK to set a bug that has a debdiff waiting for sponsorship from the sponsors team to "In progress"?
[17:56] <rbasak> Laibsch: I think it would be more appropriate to resolve this in private.
[17:56] <Laibsch> rbasak: impossible
[17:56] <Laibsch> I've tried many times before
[17:56] <Laibsch> quite many reporters have simply left, especially after dealing with his abuse in kernel bugs
[17:57] <rbasak> I would leave something in the sponsorship queue as Triaged in In Progress depending on whether someone's actively driving it or not, as opposed to queue status.
[17:58] <Laibsch> in the case of bug 1564778 I have prepared the debdiff and subscribed sponsors
[17:58] <Laibsch> I wonder if setting to "in progress" might make the sponsors assume somebody else is doing the sponsoring which I can not do
[18:07] <rbasak> I'm not sure.
[21:40] <Vej> Can someone please set bug #1657440 to Triaged and set the Importance? This bug contains sufficient information and had already been fixed Upstream. I would set the Importance to Medium because it "has a moderate impact on a core application".