On Fri, Apr 05, 2013 at 12:35:13PM -0700, Kevin J. McCarthy wrote:
I understand. More patches just means more work. The people who know
how to do things are too busy to do them, none-the-less mentor new
people. There certainly isn't an easy solution to this problem.
I would encourage mutt developers to start a thread and just list the
things they wish someone would do, that would enable them to get other
pressing things done. Then create a page or list, and post it somewhere
visible, or periodically email the list out to mutt-dev. [Yes, I am
happy to volunteer.]
The bug reporting system of full of open issues:
http://dev.mutt.org/trac/report/1
The problem is that it isn't very much fun to fix bugs, but
writing a new feature that you would like is, so the few people
who do submit patches tend to focus on that.
I don't know how many committers there are for mutt. It may be
worth considering appointing a few trusted people keep their own
hg repositories to vet and refine patches, which you and the other
committers could pull from. (The Linux "trusted lieutenants" model.)
I understand the desire to keep mutt lean and fast, but patches are the
lifeblood of a project. Having a process for dealing with them is one
of the best ways to keep the project membership healthy and growing.
Don't feel so bad, I've posted many patches myself in the past few
years that got a uniform negative reaction. The culture of this
mailing list is pretty negative toward any new functionality.
