-
Ensure the bug was not already reported by searching on GitHub under Issues.
-
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
-
Please use the issue template to create the issue.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
-
Please use the PR template to create the new PR.
-
Please ensure that you validate your changes by running our basic test case tests/basic.t
-
Please help with steps to test your changes and/or add a simple test case.
-
Suggest your change in the gluster-devel mailing list and wait for acknowledgement from the maintainer[s].
-
Alternatively you can use github issue for proposing the idea or design.
-
Once the design/idea is approved, you can start writing the code (or choose to get this done by others)
-
Please follow submitting new PR guide when your code is ready for review.
- Ask any question about how to use gluster-block in the gluster-users mailing list.
- Please walk through our documentation here gluster documentation and gluster-block documentation
We encourage you to pitch in and join the team!
Thanks! ❤️ ❤️ ❤️
Gluster-block Team!