Here are some best practices if you want to contribute to this project. Please note that this is a personal project that I maintain in my free time. I will do my best to review contributions and ship new features within a reasonable time.
Feel free to pick any open issue and start working on it. If you need help or guidance, leave a comment on the issue.
If you want to start contributing to the project, beginner-friendly issues are tagged with the "contributor friendly" label.
If there are no issues you want to pick, check the project kanban. Everything I'd like to implement that I haven't created a plan/issue for it are there as draft (just ideas, nothing concrete) - if you want to do them or want talk about it, let's chat at #dexchat.
Remember: contributing to a project doesn't mean only creating Pull Requests. You can contribute by helping users, discussing about things, etc.
If you have a new idea, please open a discussion before opening a pull request. The idea is to agree on what will be implemented so everyone can discuss the change and provide feedback. Discussions are also a good place to find new features to implement. Once a proposal has been discussed, you can open a Feature Request.
If you couldn't find a similar issue, feel free to open a bug report.
In this case, you can open a Q&A discussion or join the #dexchat IRC channel on libera.
Pull requests for non-trivial changes should address an existing issue. Small documentation fixes and typo corrections may be submitted directly.
- For new features, start with a Discussion so we can agree on the scope and proposed behavior. Once the proposal is accepted, open a feature request and link it to the Discussion.
- For bug fixes, link the corresponding bug report in the pull request.
Note
Pull requests are NOT the place to discuss the feature itself. That should be done in Discussions. They are the place to discuss the code being implemented, though.
For commit messages, please use conventional commits to make it easier to generate release notes.