If you are interested in contributing, please have a look at our Newbie Tutorial.
Any development on features is done in "devel/" feature branches in the NeoMutt repository. Once development is complete, the work will be merged into the "neomutt" branch.
Finally, some automatic checking is done on commits and pull-requests for NeoMutt. It benefits from two free services (free for Open Source). They are triggered on every commit to GitHub.
|Architectures||List of supported architectures / operating systems|
|Branch Names||List of Branches in the NeoMutt Repo|
|Bug-Fix Week||A Period of Stabilisation|
|Building NeoMutt||How to build NeoMutt from the Source Code|
|Coding Style||The preferred style for code committed to NeoMutt|
|Debugging NeoMutt||How to Debug NeoMutt|
|Discussions||Closed Discussions on GitHub|
|Docs Rebuild||(Re-)Building the Documentation|
|Documentation||Description of Neomutt's documentation process.|
|Doxygen||Formatted Comment Blocks|
|Hard Problems||A list of problems we really need help for|
|Issue Labels||Labelling of GitHub Issues|
|Making NeoMutt||How NeoMutt Assembles the Source|
|Newbie Tutorial||Things every Newbie Should Know|
|Obsolescence||A list of old projects that can be forgotten|
|Releases||Releases of NeoMutt and Mutt|
|List of Repos||List of GitHub Repositories|
|Signing Code / Releases||Be Sure You're Getting the Real Thing|
|Translating Code||How to make the code translatable|
|Translating Strings||How to Translate Strings|
NeoMutt also has a couple of speculative ideas: