Feature: new maintainer role, "no credit"/"light" maintainer

[GudraFree]

Allow a dev to be set as a maintainer of a set, without giving them dev stats credit at all.

This idea comes from the fact that the maintainer role is being used as a replacement for reauthors, which have a strict assignment policy. A "light maintainer" role would allow volunteer devs to take on inactive devs' sets, without the troubles of having to redirect unlocks, and with more facility to change the dev or eliminate the role in cases like the current maintainer quitting or the old dev coming back. This role would be able to be assigned by QA/DevComp/some higher role, but not the devs themselves.

I think this is especially helpful since we may have devs willing to maintain a set for no credit, to keep an eye on highly ticketed sets, and avoiding the "politics" that a reauthor/maintainership (current) implies.

A light maintainer would be treated as the dev of the set only regarding to tickets. In similar concept to #3781 , tickets would show notifications, appear in the dev's ticket list, prevent claims, etc. This would be the set equivalent to this proposal.

[wescopeland]

My understanding is the only difference between this and maintainership is the omission of dev stat awards.

I mean this genuinely from a place of intellectual curiosity: why is that desirable? Is there something cultural or some kind of barrier that would lead a dev to not want those awards granted?

[GudraFree]

Because as of now, maintainership is treated (by DevCompliance) as if it was a replacement to reauthors. That implies very strict conditions to be granted, since some people may abuse it to inflate their dev stats (I assume).

A least strict maintainership is desirable for the sake of the site. If current maintainer role wont be given lightly due to team policies, a new role that only implies the responsibilities would be, ideally, be granted more generously. It all boils down to current maintianer role not being accessible at all.

[wescopeland]

Conceptually, would it make sense for devs to be able to subscribe to all tickets for a game (I'm not sure if this already exists)? Would that be functionally equivalent to this new "maintainer lite" proposed role?

[GudraFree]

The feature exists in the form of sending emails for new tickets, at least.

I personally think this "maintainer lite" role should be granted by some team instead of devs claiming it themselves, which could cause some chaos, since it would ideally be shown somewhere in the UI, maybe equivalent to the current maintainer role, making no difference for the regular user: they would only know the set is currently maintained, not at what level.

[ladynadiad]

I can give one example where it may be good. I requested maintainership on Shining Soul and was denied. I revised the set so I have authored some achievements. Subscribing is actually really annoying because that means I get double notifications for tickets on my achievements there but there is currently no way to subscribe only to tickets on Alfex's achievements. If an issue comes up, I'm the best suited to handle them since I rewrote the achievements to match with the ones I added but DevComp doesn't feel maintainer is appropriate since the set had no issues that required me to do that.