mirror of
https://github.com/jlengrand/helidon.git
synced 2026-03-10 08:21:17 +00:00
43 lines
1.5 KiB
Markdown
43 lines
1.5 KiB
Markdown
|
|
# Contributing to Project Helidon
|
|
|
|
We welcome your contributions! There are multiple ways to contribute.
|
|
|
|
## Discussion
|
|
|
|
Join us at [#helidon-users](https://join.slack.com/t/helidon/shared_invite/enQtNDM1NjU3MjkyNDg2LTFkZTM4NmI3OWUyNjUxYWQ5Njc0NGNiMzY3MTZiZmMwNzAxYmI4YzUzOWNkNzNlZTEwNDRkZGU4YzMzZjhkNTE) and participate in discussions.
|
|
|
|
## Issues
|
|
|
|
If you hit a bug or have an enhancement request then file a [GitHub issue](https://github.com/oracle/helidon/issues).
|
|
When filing a bug remember that the better written the bug is, the more likely it is
|
|
to be fixed. Please include:
|
|
|
|
1. Version of Helidon
|
|
2. Whether you are writing a Helidon SE or MP application
|
|
3. OS
|
|
4. Version of Docker or Kubernetes or other software if it's relevant to your issue
|
|
5. Steps to reproduce
|
|
|
|
## Code
|
|
|
|
We welcome code contributions, but we need the contributor to sign the
|
|
[Oracle Contributor Agreement (OCA)](https://www.oracle.com/technetwork/community/oca-486395.html)
|
|
first.
|
|
|
|
The process:
|
|
|
|
0. Sign the [OCA](https://www.oracle.com/technetwork/community/oca-486395.html)
|
|
1. Fork the repo
|
|
2. Fix an issue or create an issue and fix it
|
|
3. Create a Pull Request that fixes the issue
|
|
4. Watch your PR for pipeline results. If there are failures then fix them.
|
|
5. We will review your PR and merge as appropriate.
|
|
|
|
## Code of Conduct
|
|
|
|
Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If
|
|
you'd like more specific guidelines see the
|
|
[Contributor Covenant Code of Conduct](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html)
|
|
|