4 ms·
The approach I'm trying to take with the community I'm involved in is to keep the effort required spread out -- so for instance I manage mainline releases but s
by pm215 11y ago
The approach I'm trying to take with the community I'm involved in is to keep the effort required spread out -- so for instance I manage mainline releases but somebody else deals with stable branches and point releases, and a third person does the "pick up otherwise orphaned patches from the mailing list and get them applied" work. If I was trying to do all those jobs at once I'd never find time to do any of the things I actually find interesting!
- bonzini 11y agoAs (I think) the third person you mention above, I totally agree---and thanks for the great work keeping the tree in good state.
- ethbro 11y agoThis is probably one of the issues with being a the aforementioned super-smart / super-productive leader: they can take all of that load if needed. Should they? God no. No one can run that workload as a volunteer for a decade+. But I can see how the default reality probably bends towards "Well, someone left and we need this job filled" -> "I'll just temporarily add that job to my workload" -> "It'd be more effort to move that job's responsibility to someone else, so I'll just keep doing it."