Get Involved | Jaeger

Jaeger is an open source project with open governance. We welcome contributions from the community, and we’d love your help to improve and extend the project. Below you will find some ideas for how to get involved with the project. Some of them don’t even require any coding. There is also a good CNCF guide on how to start contributing to open source and figure out where to begin.
In order to understand the project better and come up with reasonable solutions, it’s always helpful to become familiar with Jaeger and its code base. We strongly recommend these steps:
Join the online chat room and help answering questions from the rest of the community.
Join our bi-weekly video calls to discuss issues, large initiatives, or present case studies.
Help documenting answers to common questions, either in Jaeger documentation or Stackoverflow.
Help improving Jaeger documentation, especially if you yourself run into issues where something is not clear or not working.
Publish blog posts or tutorials about Jaeger, for example:
Advocate for deploying Jaeger in your company.
Propose designs for building new capabilities in Jaeger.
Organize local meetups to explain the benefits of Jaeger and distributed tracing.
Of course, there’s also no shortage of opportunities to help with the actual development of Jaeger. The easiest way to start is with issues labeled as good-first-issue. Note that the Jaeger project includes many different repositories, covering backend components, Jaeger UI, Kubernetes tools, analytics tools, etc. Many of them have these tickets, so pick whichever area interests you the most.
Another label to look for is help-wanted, which we use to tag tickets that involve features that maintainers consider promising / useful, but which are not on the immediate roadmap (after all, we all have day jobs with different priorities).
Please refer to the Contributing Guidelines on how to make code contributions. And make sure to follow the CNCF Code of Conduct.
If the issue is open and labeled as help-wanted there is a very high probability it is still relevant. Only if it is very old (e.g. more than two years) it may no longer be needed and it’s ok to comment on it and confirm.
We have a policy of not explicitly assigning the issues to anyone. It is always a good etiquette to verify if someone is already working on the issue:
It’s always a good idea to include the text Resolves #{issue number} in the PR so that GitHub can link it to the issue and to close the issue once the PR is merged. If this is done, you will be able to see the PR number and icon right under the issue description. Alternatively, you can look through the issue comment history and you will also find the links to the PRs that mention the issue (although they may not necessarily be solving that issue, so look deeper).
The Jaeger project regularly participates in mentorship programs via CNCF. See Mentorships.