mirror of https://github.com/poanetwork/quorum.git
37 lines
1.5 KiB
Markdown
37 lines
1.5 KiB
Markdown
# Contributing
|
|
|
|
Thank you for your interest in contributing to Quorum!
|
|
We welcome contributions from anyone on the internet, and are grateful for even the
|
|
smallest of fixes!
|
|
|
|
If you'd like to contribute to go-ethereum please fork, fix, commit and
|
|
send a pull request. Commits which do not comply with the coding standards
|
|
are ignored.
|
|
|
|
## Coding guidelines
|
|
|
|
Please make sure your contributions adhere to our coding guidelines:
|
|
|
|
* Code must adhere to the official Go
|
|
[formatting](https://golang.org/doc/effective_go.html#formatting) guidelines
|
|
(i.e. uses [gofmt](https://golang.org/cmd/gofmt/)).
|
|
* Code must be documented adhering to the official Go
|
|
[commentary](https://golang.org/doc/effective_go.html#commentary) guidelines.
|
|
* Pull requests need to be based on and opened against the `master` branch.
|
|
* Commit messages should be prefixed with the package(s) they modify.
|
|
* E.g. "eth, rpc: make trace configs optional"
|
|
|
|
## Can I have feature X
|
|
|
|
Before you submit a feature request, please check and make sure that it isn't
|
|
possible through some other means. The JavaScript-enabled console is a powerful
|
|
feature in the right hands. Please check our
|
|
[Wiki page](https://github.com/ethereum/go-ethereum/wiki) for more info
|
|
and help.
|
|
|
|
## Configuration, dependencies, and tests
|
|
|
|
Please see the [Developers' Guide](https://github.com/ethereum/go-ethereum/wiki/Developers'-Guide)
|
|
for more details on configuring your environment, managing project dependencies
|
|
and testing procedures.
|