Thank you for considering contribution to Noe Core. As a potential contributor, your changes and ideas are always welcome. Please do not ever hesitate to ask a question or send a Pull Request.
If you come across what seems to be a bug, please use the Github issue tracker and file an issue. An issue can also be used for discussions.
Documentation is crucial for success of any project. If you feel like there is lack of documentation in some area, feel free to file an issue. If you want to contribute documentation, feel free to open a PR with your changes. Your contribution may or may not be changed with stylistic and grammatical corrections; do not expect to see your changes ad verbum in the code.
To limit wasted effort and time, before contributing code, please open up an issue where you describe your desired change in Noe Core. After a debate and review of the idea, follow the Contribution Workflow section to get your patch accepted.
Noe Core uses the standard Github's Pull Request workflow. In addition, we expect you to:
- Adhere to the review provided within the pull request. If you disagree, we are always open to a debate.
- Adhere to the Apache software Foundation's Code of Conduct.
- Provide integration and unit test where applicable.
- Provide full documentation for your changes where applicable.
- Provide reasonable commit messages.
- Adhere to our codestyle.
We use the same coding style as Wildfly with the following exceptions:
- Indentation size is 2 spaces.
- Contined indentation is 4 spaces.
- Maximum line length is 160 chars.
Are you missing something? Is something confusing? Is something unreasonable? Please let us know!