This project is governed by a Code of Conduct.
First, before writing any code, please open an issue, let's have a discussion about any features or ideas that you may have.
Once the feature or idea is fleshed out, let's hack!
- Fork it
- Branch it
- Hack it
- Save it
- Commit it
- Push it
- Pull-request it
The above is respectively taken from the Clearwater framework repository.
Kudos to Jamie Gaskins for framing the guidelines so succinctly.
Further reading, I've been thinking a lot about Jeff Geerling's post "Why I close PRs (OSS project maintainer notes)" lately. If you do submit a PR and feel that I'm closing it down, this is probably the rationale behind it.