Suggestion: give everyone "triage" right on helpdesk repo

[lemeurherve]

if someone incorrectly closes an issue, then someone else can reopen it.
if someone incorrectly reopens an issue, you can reclose it.
If it becomes a problem, then it can get addressed.
Like I said, jenkins has always tried to be open and letting anyone that wants to contribute to help contribute.

Ref: https://issues.jenkins.io/browse/INFRA-3175?focusedCommentId=417701

[timja]

Not really do-able on GitHub via permissions, you can have a team of people that is 'everybody' in your org but you have to manage that and add people to the org.

imo this was just a feature that Jira had that isn't really needed.
(Of course we can add more teams here with triage or setup a specific team for it)

Also triage doesn't give you much permission it just lets you update labels and close / open issues.
It doesn't let you update descriptions

And labels and issue opening / closing are just as easy to do via GitHub actions.
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/.github/workflows/hosting-comment-checker.yml#L12

[lemeurherve]

This is a general discussion I though it had to be open after seeing Gavin's comments in the linked Jira issue, nothing definitive, just throwing the idea.

Not really do-able on GitHub via permissions, you can have a team of people that is 'everybody' in your org but you have to manage that and add people to the org.

Maybe via GHA? Idk, thinking out loud here.

I've also though about managing it via chatops like you suggested too.

[timja]

Yeah comment ops would be fine to add some things if we see a need.

But generally I don't really see it being a problem.
I've managed lots of projects on GitHub issues for years and hasn't been an issue. 😄

[lemeurherve]

Is this goal of allowing more open management of these issues a priority one in your opinion or can it be delayed a little bit?

[timja]

I think this one would be more useful: #12

[lemeurherve]

Closed in favor of #12