This document describes how to contribute to Bee.
We encourage everyone with knowledge of IOTA technology to contribute.
Do you have a question :question:
If you have a general or technical question, you can use one of the following resources instead of submitting an issue:
- Developer documentation: For official information about developing with IOTA technology
- Discord: For real-time chats with the developers and community members
- IOTA cafe: For technical discussions with the Research and Development Department at the IOTA Foundation
- StackExchange: For technical and troubleshooting questions
Ways to contribute :mag:
To contribute to Bee on GitHub, you can:
- Report a bug
- Suggest a new feature
- Build a new feature
- Join the Bee Initiative
Report a bug :bug:
This section guides you through reporting a bug. Following these guidelines helps maintainers and the community understand the bug, reproduce the behavior, and find related bugs.
Please check the following list:
Ensure the bug was not already reported by searching on GitHub under Issues. If the bug has already been reported and the issue is still open, add a comment to the existing issue instead of opening a new one.
Note: If you find a Closed issue that seems similar to what you're experiencing, open a new issue and include a link to the original issue in the body of your new one.
To report a bug, open a new issue, and be sure to include as many details as possible, using the template.
Note: Minor changes such as fixing a typo can but do not need an open issue.
If you also want to fix the bug, submit a pull request and reference the issue.
Suggest a new feature :bulb:
This section guides you through suggesting a new feature. Following these guidelines helps maintainers and the community collaborate to find the best possible way forward with your suggestion.
Ensure the feature has not already been suggested by searching on GitHub under Issues.
To suggest a new feature, talk to the IOTA community and IOTA Foundation members in the #bee-discussion channel on Discord.
Or, you can submit an official Request for Comments (RFC).
Build a new feature :hammer:
This section guides you through building a new feature. Following these guidelines helps give your feature the best chance of being approved and merged.
Make sure to discuss the feature in the #bee-discussion channel on Discord.
Otherwise, your feature may not be approved at all.
To build a new feature, check out a new branch based on the
master branch, and be sure to document any public-facing APIs, using Rust code comments.
Join the Bee Initiative :deciduous_tree:
The Bee Initiative is a collaborative effort to improve the Bee developer experience by focussing on the following goals:
- Quality Assurance and Quality Control
- Node usability
- Improvements to modules and libraries
You can invest as much or as little time as you want into the initiative.
In return for your time, not only do you get to be a part of the future of IOTA technology, you will also be given a badge on Discord to show others that you're a valuable member of the IOTA community.
If you're interested in joining, chat to us in the #experience channel on Discord.
Pull requests :mega:
This section guides you through submitting a pull request (PR). Following these guidelines helps give your PR the best chance of being approved and merged.
Before submitting a pull request, please follow these steps to have your contribution considered by the maintainers:
A pull request should have exactly one concern (for example one feature or one bug). If a PR addresses more than one concern, it should be split into two or more PRs.
A pull request can be merged only if it references an open issue
Note: You don't need to open an issue for minor changes such as typos, but you can if you want.
All public interfaces should have descriptive documentation, including an example that compiles and passes documentation tests
All instances of
unsafeshould have a comment that explains why its use was unavoidable
All code should be well tested, using unit tests and integration tests
Code must compile and pass our continuous integration tests
To be compatible with the guidelines of the Eclipse foundation, all code must be licensed under the Apache License, Version 2.0. This license must be referenced in every crate of the workspace (add [
./LICENSE] to the crate's top level directory). For Rust crates, every
Cargo.tomlmust contain the line
license = "Apache-2.0".
The following is a typical workflow for submitting a new pull request:
- Fork this repository
- Create a new branch based on your fork. For example,
git checkout -b fix/my-fixor
git checkout -b feat/my-feature.
- Run the
rustfmtcommand to make sure your code is well formatted
- Commit changes and push them to your fork
- Target your pull request to be merged with
If all status checks pass, and the maintainer approves the PR, it will be merged.
Note: Reviewers may ask you to complete additional work, tests, or other changes before your pull request can be approved and merged.
Code of Conduct :clipboard:
This project and everyone participating in it is governed by the IOTA Code of Conduct.