Qt Contributors Summit 2022 - Program/Ghost Maintainers: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(Created page with "Category:QtCS2022 ==Session Summary== There are Qt modules that have maintainers who are largely absent, yet we have no formal process for handling this situation; and [...")
 
(What I can remember of the discussion.)
 
(One intermediate revision by one other user not shown)
Line 11: Line 11:
==Notes==
==Notes==


(Taken by XXX)
We discussed the issue of some maintainers quietly disappearing,
without overtly relinquishing their maintainership.


===Title===
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.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
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.


===Title===
No consensus was reached on a definite conclusion or plan of action.
 
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
 
 
===Title===
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Latest revision as of 14:49, 17 June 2022


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.