On how to work together
- use PRs for fixes or small features/improvements - no prior issue or disucssion is needed…
- …as the PR itself serves as discussion platform.
- use issues for bugs, and discussion for features…
- …if collaboration or prior feedback is desired; see the contribution guide for when discussion is required
- please follow the contribution guide when collaborating
- for crates you own
- feel free to make any kind of changes to it, including major ones.
- please use
cargo smart-releasefor publishing to crates.io as it will handle dependencies properly.
- for crates you do not own
- for major or architectural changes, open a discussion, issue, or PR to allow participation, and do not merge until there is agreement.
- for minor code changes, feel free to make any kind of change you need.
The workflow can be changed after public discussion - to get started, open a PR.
Please see the development guide for more detailed information on how code and cargo manifests are structured.