Step in – here may be more than just consuming

What's going on?

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.

Travis CI automatically build projects on every commit (Continuous Integration). Coverity performs static analysis on the code looking for potential problems.

travis status coverity status Backlog In Progress Ready

Development docs

Title Description
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
Closed Discussions Closed and stalled discussions on GitHub
Code Libraries Sharing to untangle NeoMutt's code
Coding Style The preferred style for code committed to NeoMutt
Debugging NeoMutt How to Debug NeoMutt
Docs Rebuild (Re-)Building the Documentation
Documentation Description of NeoMutt's documentation process
Doxygen Comments Formatted Comment Blocks
Glossary A collection of abbreviations/acronyms
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

Blue sky

NeoMutt also has a couple of speculative ideas:

Note: These are just toys (for now).

Search by Algolia