>> enough time on maintenance (we're all spread a lot thinner than we >> used to be, I think, and I don't see that changing in the short >> term). We know it's a big problem. We need more maintainers (not just >> patch writers), but we're doing a terrible job of encouraging people
> I think there's the fairly obvious step of asking people directly > > There's also the matter of road map, which I think the various > ALSO had a (perhaps optional) GUI with additional functionality that's > but in practice IMO forks are bad: They divide the effort, and cause Mutt's pretty cool for years. And email spec is stable so it's more important to fix bugs and refine current features than new features (which add more bugs and refinement needs) when staff is slim. Really the only major feature mutt could have to be 'current' would be html renderer, for those 'only html' emails that come in. Even if just spawn elinks for it. Just encourage advertise for developers, why mutt is cool, etc. And it is better for current maintaners to step up and say, ok we're passing on the history, than to fork, or fight, or rot. Mutt excels at text based and is it's sole reason to exist, there is no place for any gui mutt. Otherwise just use thunderbird like masses.
