Re: New maintainer

[Przemysław Wojnowski]

> Maintainers tend to burn out and eventually cease their contribution as
> developers.
IMHO this is very important issue to address, because with them Emacs
looses active developers and a lot of knowledge.

What can be changed in this role to not burn out people?

IMHO one problem might be that, due to lack of roadmap and clear
priorities, a lot of different things are developed at the same time,
which springs even more topics on emacs-devel. Going through this flood
and deciding on them must be tiring. Selecting top 10 (X) from the
roadmap would constrain topics range and make it simpler to manage.
Also it would clarify for developers what to focus on.

Another thing is that a maintainer doesn't have to code review every
single change (search for "the cost of perfectionism"). It's enough if
some other developer would do that.
A developer that wrote a feature can just write tests and send an email
to emacs-devel "XXX - ready for Code Review".

I don't have experience as Emacs maintainer, so I may be wrong. But I
do have some experience as a team lead and have to deal with similar
issues.