See also: ssbc/patchbay#268

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

Reproduced by @cblgh just now :P

Powersource assigned hermes-bot and unassigned Powersource 44 minutes ago

?

Idk, to pin it but make it clear no one in particular is taking it on

(FWIW I'd personally like to avoid pinning issues that don't have anyone taking responsibility for them, but I won't stop you from doing it.)

I just reread my above message and it had kind of a stern tone. Hmm. I meant it in a playful "not my style, but we don't have to have the same style" kind of way. Hope that's more clear and not a weird "you have violated my sacred preferences" kinda way.

TEXT IS HARD

For e.g. this issue no one is really 'taking responsibility' for it (and I think that probably applies to most of the issues with someone assigned to them), but for me this felt like enough of a bug that I wouldn't want stalebot to sweep it away.

But my opinion here isn't super strong, was mostly trying to clean up old issues.

Maybe "taking responsibility" is the wrong vibe. My preference is to assign myself to issues that I want open, that way there's no ambiguity about who is insisting on keeping the issue open. I don't like "pinned" because in 5 years it will remain open and unless we have a conversation like this, it's unclear whether someone actually wants it to remain open for 5 years or whether someone was annoyed with stalebot and labeled "pinned".

My issue management philosophy is that open issues should be active, and that 'closed' is more like "no longer active". 🤷 GitHub issue management isn't ideal at all.