Contributing to the crnk project, and to any open-source project for that matter, can be a rewarding experience both in terms of the way you can help yourself and projects you are working on, as well as the countless number of others you may help with your contribution.
Before you raise a new issue you must be able to narrow it down to a minimal test case against a clean code base that can be used for reproduction when submitting the issue. And, naturally, to make sure it's not an "undiscovered feature" on your side :). Once you have a reproducable case in a clean code base please check the list of project issues. There may already be a discussion in progress that you can contribute to or at least follow for a resolution. You should also ask in gitter first. However, if you have discovered an issue then please follow these rules:
- Include version of crnk you are using
- Use labels to tell us in which module problem occurs
- Wait for feedback from our developers in response to your issue. We are volunteers so please be patient.
- Make a coffee and feel proud of yourself (or tea, or whatever the hot relaxing beverage in your part of the world is)!
So you have added a feature to a library or you have created something new. Maybe you just have some bit of code that you use all the time in your projects and now you want to give that to the community and let them enjoy the same benefits you have? Great! This is how open source projects begin, grow, thrive and reach new users. Here is how to proceed with a pull request:
- Fork crnk-framework repository
- Implement your new feature or fix on dedicated branch
- Don't forget to update or add unit tests and ensure they are passing
- Submit a pull request to be merged into
master. In your PR please refer to the issue number. Remember, enhancements are "issues" too. - Your code will be reviewed by at least two people from our developers community
- Wait for feedback and in next release you may see your code working on production
Crnk gives you a number of ways to discuss features, express concerns or just chat about the project with other people just like you. Feel free to chat with us on gitter or if your question is strictly involving usage of crnk create new question on StackOverflow
You don't necessarily have to write code to contribute. Telling someone in an effective way what a project is for and how to use it is just as important as providing the code for them to use. And it doesn't end there. From helping to maintain infrastructure to event planning, projects need help in many areas beyond the code.
Open source projects are small communities of like-minded individuals coming together over a common interest or skill set. As with any community, there are appropriate ways to conduct yourself when interacting with other members of that group. Treating others with respect is not just courteous, but it helps encourage new people that may have important contributions to feel comfortable enough to put themselves out there and take that first step toward getting involved.
Whether you're answering questions in a forum, chatting with someone at a conference or commenting on a section of someone's code, keep in mind that your words and your actions have real consequences. Treat others how you would like to be treated and keep in mind that we were all beginners at some point. When you encounter a community member that doesn't follow or understand the mores, just remember that someone once helped you and pass on the kindness.
- Crbj 3.x uses Java 8.
- Code style. we use the default Intellij settings.