Zipkin is a tracing system originally created by Twitter and is currently run by the OpenZipkin volunteer organization.
OpenZipkin is the OSS organization that stewards Zipkin code, docs, specs and support. It includes github projects, this web site, google groups - mailing list, Twitter and gitter.
Follow @zipkinproject on Twitter for news including release announcements and community events. You can also ask on gitter about something specific. If you are working on code, you can also follow projects like the server or an instrumentation you use.
OpenZipkin is primarily volunteers, and there are a lot of ways to help. Once you are on gitter, you might notice others asking questions you once asked. A great way to give-back is to help others who are just starting. We are at a number of events, and these are a great way to meet others you collaborate with. You can also host your own Zipkin meetup, similar to how our Tokyo user group started. If you notice something interesting on Twitter, tag it with #zipkin so that others can see it. Last, but not least, you can get involved with the code, docs and project maintenance.
Most OpenZipkin efforts start as localized experiments, then progressively build traction before becoming a feature. Before you start a large effort, be it docs or a test framework or a feature, check with one of the above channels. Someone may already have worked on this in the past and might join your effort. Sometimes, features are intentionally absent, usually with rationale documented in an issue. Regardless, the best advice is to join the community before proposing change, and read one of our HACKING files which explains important aspects of change culture.
This guide will help you to use Zipkin logo with its brand colors, and symbol. You can get original image files(.svg, .png) at below link.