Mass-removing myself from cc; search for 12b9dfe4-ece3-40dc-8d23-60e179f64ac1 or any reasonable part thereof, to mass-delete these notifications (and sorry!)

The severity field for this bug is relatively low, S3. However, the bug has 20 votes.
:tnikkel, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Please stop generating bug mail for votes of all things.

We are working on it, this was triggered by the severity migration which updated the last change time for many old bugs.

There shouldn't be a rule for votes at all! Doesn't matter what the last change time was, votes shouldn't waste our precious time with bugmail. Can we try to look for opportunities to not waste our time by default instead of looking for make work projects for bots?

(In reply to Timothy Nikkel (:tnikkel) from comment #5)

There shouldn't be a rule for votes at all! Doesn't matter what the last change time was, votes shouldn't waste our precious time with bugmail. Can we try to look for opportunities to not waste our time by default instead of looking for make work projects for bots?

You can file issues for any suggestion you might have on https://github.com/mozilla/relman-auto-nag, we are always happy to adjust the rules and queries the bot is using.
Note these needinfos were the result of a bug/coincidence, they were not added on purpose.

(In reply to Marco Castelluccio [:marco] from comment #6)

(In reply to Timothy Nikkel (:tnikkel) from comment #5)

There shouldn't be a rule for votes at all! Doesn't matter what the last change time was, votes shouldn't waste our precious time with bugmail. Can we try to look for opportunities to not waste our time by default instead of looking for make work projects for bots?

You can file issues for any suggestion you might have on https://github.com/mozilla/relman-auto-nag, we are always happy to adjust the rules and queries the bot is using.
Note these needinfos were the result of a bug/coincidence, they were not added on purpose.

Yes I understand it was a bug but votes exist so that there is a way to advocate for a bug without wasting dev time with bugmail. So this rule seems to be completely against that. ni for visibility.

Also, how does one get to have input on rules before they are created? Trying to change things after they have already been decided upon is like pushing a rock uphill.

(In reply to Timothy Nikkel (:tnikkel) from comment #8)

Also, how does one get to have input on rules before they are created? Trying to change things after they have already been decided upon is like pushing a rock uphill.

:tnikkel, thank you for filing issues in the autonag repository. We will follow up on them.

We send emails to the dev-platform and firefox-dev mailing lists before enabling any new tool/rule and ask for feedback.

Examples:

• https://groups.google.com/a/mozilla.org/g/dev-platform/c/LIgLh9QcBj8/m/-6WGSvw4BwAJ
• https://groups.google.com/a/mozilla.org/g/dev-platform/c/OQPzdxV6_SQ/m/CmfF7cImBwAJ

Also, you can have visibility over the planned work in the autonag improvement project: https://github.com/mozilla/relman-auto-nag/projects/1. If you want to participate more closely, we could invite you to some of the bot triage meetings.

(In reply to Suhaib Mujahid [:suhaib] from comment #9)

(In reply to Timothy Nikkel (:tnikkel) from comment #8)

Also, how does one get to have input on rules before they are created? Trying to change things after they have already been decided upon is like pushing a rock uphill.

:tnikkel, thank you for filing issues in the autonag repository. We will follow up on them.

We send emails to the dev-platform and firefox-dev mailing lists before enabling any new tool/rule and ask for feedback.

Examples:

• https://groups.google.com/a/mozilla.org/g/dev-platform/c/LIgLh9QcBj8/m/-6WGSvw4BwAJ
• https://groups.google.com/a/mozilla.org/g/dev-platform/c/OQPzdxV6_SQ/m/CmfF7cImBwAJ

The rule is already created at that point. So if someone replied to that they would be applying stop energy to the situation. So that is not what I asked for.

(In reply to Timothy Nikkel (:tnikkel) from comment #10)

The rule is already created at that point. So if someone replied to that they would be applying stop energy to the situation. So that is not what I asked for.

We are always happy to incorporate feedback even if the rule is already created.

For tools/rules with wider impact, we even go through a purpose process to collect feedback/approvals before starting the work; examples:

• https://docs.google.com/document/d/1U17fEx9D1lRjJMfjNrGPjjbQCOy1qQjjuj9gufsXW9c
• https://docs.google.com/document/d/1bL7EZePIgORTiwTNTmaJOaYRpnRHEy3OvLlsbDzA7dk

(In reply to Timothy Nikkel (:tnikkel) from comment #8)

Also, how does one get to have input on rules before they are created? Trying to change things after they have already been decided upon is like pushing a rock uphill.

Indeed, the tool doesn't notify on any new vote, it only notifies when the severity of the bug is low and the number of votes have substantially increased, which might warrant a re-triage.

(In reply to Timothy Nikkel (:tnikkel) from comment #10)

The rule is already created at that point. So if someone replied to that they would be applying stop energy to the situation. So that is not what I asked for.

The rule is created but not enabled, that's on purpose so we can incorporate feedback and make necessary changes (or even decide not to enable the tool, if we find nobody agrees with it).
Feel free to reply to the dev-platform emails that we send when you have thoughts, we will take them into account.

My thoughts are generally "don't run the rule". You don't seem open to this kind of feedback.

You seem to be operating from the perspective that all these changes are good things and haven't been able to see a perspective different from that.

Timothy, there seems to be a miscommunication issue between us. I said "or even decide not to enable the tool, if we find nobody agrees with it".
Anyway, we are polluting this bug with an off-topic discussion, feel free to contact me on Matrix/Slack or schedule a call with me to talk about this.