Excited about Gloo and want to help make it better?
At Solo we strive to make the world of microservices, serverless and service mesh available to everyone. If you want to help but don’t know where to start, let us know, and we’ll find something for you.
If you haven’t already, make sure you sign up for the Solo Slack.
Here are some of the ways you can contribute:
If you encounter a bug, please file an issue on GitHub. If an issue you have is already reported, please add additional information or add a 👍 reaction to indicate your agreement.
Improving the documentation, adding examples or use cases can be the easiest way to contribute to Gloo. If you see a piece of content that can be better, open a PR with an improvement, it doesn’t matter how small!
If your bug fix is small (around 20 lines of code) just open a pull request. We will try to merge it as soon as possible, just make sure that you include a test that verifies the bug you are fixing.
For significant changes to the repository, it’s important to settle on a design before starting on the implementation. Reaching out to us early will help minimize the amount of possible wasted effort and will ensure that major improvements are given enough attention.
wipto start getting feedback.
It’s important that every piece of code in Gloo is reviewed by at least one Solo team member familiar with that codebase.
/teston your PR.
To see coverage, run your tests in the package like so
ginkgo -cover && go tool cover -html *.coverprofile