Step in - here may be more than just consuming
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 main 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.
| Title | Description |
|---|---|
| Actions | GitHub Actions |
| Analysis | Ways to Analyze NeoMutt’s code |
| Bug-Fix Week | A Period of Stabilisation |
| Build | Building NeoMutt |
| Code Style | The preferred style for code committed to NeoMutt |
| Config System | How Config Variables are handled |
| Deployment using Actions | Update the website when certain builds succeed |
| Docs Rebuild | (Re-)Building the Documentation |
| Documentation | Description of NeoMutt’s documentation process |
| Doxygen Comments | Formatted Comment Blocks |
| Easy Tasks | A Great Way to get started in Open Source |
| GitHub | How the Project uses GitHub |
| Glossary | A collection of abbreviations/acronyms |
| Newbie Tutorial | Things every Newbie Should Know |
| Obsolescence | A list of old projects that can be forgotten |
| Roadmap | The Future of NeoMutt |
| Signing Code / Releases | Be Sure You’re Getting the Real Thing |
| Support | List of supported architectures / operating systems |
| Translating Strings | How to Translate Strings |
NeoMutt also has a couple of speculative ideas:
Note: These are just toys (for now).
