First off, thank you for considering contributing to The Deed Protocol. It's people like you that make this platform great.
There are many ways you can directly contribute to the project:
- Report bugs and file issues. Our project uses GitHub issues to track public bugs.
- Suggest new features and improvements.
- Write and help us improve our documentation.
- Submit pull requests. If you're fixing a bug, describe the bug in detail and provide a descriptive title for the PR.
By participating in this project, you are expected to uphold our Code of Conduct.
- git
- Node v18+
- Yarn v3+
- VSCode (recomanded) / WebStorm / Any web IDE
- Clone the repo
- Open a terminal and run
yarn install
- Open the project workspace in your IDE (VSCode recomanded)
- Open a terminal in Frontend (or packages/nextjs) and run
yarn start
- To debug the backend, open
run and debug
in VSCode and selectNextJS: debug server side
from the dropdown. - To debug the frontend, use the browser dev tools. (vscode task doesn't work yet)
- Ensure the bug was not already reported by searching on GitHub under Issues.
- If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
- Open a new issue. Use the correct template for feature request issues. Be sure to include a detailed description of the feature, why this feature is needed, and how it can be used.
- Fill in the required template
- Follow the coding style of the project
- Separate unrelated changes into multiple pull requests
Please read the Pull Request Guidelines before submitting your pull request.
- Please use the
.eslintrc
configuration file in the project for the code style settings.
By contributing to The Deed Protocol, you agree that your contributions will be licensed under its AGPL-3.0 License.
If you have further questions, you can check out the FAQ, ask a question on the GitHub Discussions page, or join our community on Discord.