Qt Contributors Summit 2022 - Program/Ghost Maintainers

From Qt Wiki
< Qt Contributors Summit 2022 - Program
Revision as of 14:49, 17 June 2022 by EdwardWelbourne (talk | contribs) (What I can remember of the discussion.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.


Session Summary

There are Qt modules that have maintainers who are largely absent, yet we have no formal process for handling this situation; and Maintainers != Gerrit's list.

Session Owners

Andy Nichols, Paul Tvete, Eddy

Notes

We discussed the issue of some maintainers quietly disappearing, without overtly relinquishing their maintainership.

One proposal was to automatically retire any maintainer that failed to either participate in a round of API change review for their module or appoint a deputy to look after that for them. Naturally this would then prompt an effort to recruit a replacement. The status quo is that maybe someone will send an e-mail to such a maintainer's last recorded e-mail address and ask if they'd be willing to step down, optionally nominating a successor in the process; and maybe they get a reply. If the e-mail address is stale or they simply get no reply, there's no process for what to do next, short of the full-blown process of a vote of no confidence in the given maintainer.

No consensus was reached on a definite conclusion or plan of action.

Retrieved from "https://wiki.qt.io/index.php?title=Qt_Contributors_Summit_2022_-_Program/Ghost_Maintainers&oldid=39554"