Closed rfdoell closed 5 years ago
I'm curious as to what depth we should go into here. My gut says our contribution guide would be pretty simple?
cargo clippy
and cargo fmt
on code prior to issuing a pull request.Is there anything else that people think I might be missing? @Alex-Addy any thoughts?
Keep it simple. Just a few bullet points should be sufficient to set expectations. We can make a more complicated guide if we ever try to open up development.
Added as part of #30.
A contribution guide should be created and documented in the project so that new developers know how best to provide code to the comms-rs project.
Acceptance: