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. Here are some ideas for how to get involved with the project. Some of them don’t even require any coding.
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:
- What kind of deployment model you chose in your company and why.
- How to use Jaeger with hosted storage solutions, such as AWS Elasticsearch.
- What kind of problems you were able to solve with Jaeger in your organization.
- How did you model traces for non-trivial workflows, like async processing.
- Tweet about your blog post at @Jaegertracing and email to
- If your blog is on Medium, reach out to maintainers and we may add it to our official blog.
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.
Help with coding
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 tagged good first issue. Note that the Jaeger project includes many different repositories, covering backend components, Jaeger UI, client libraries, Kubernetes tools, analytics tools, etc. Many of them have the “good first issue” 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.