From general-return-65447-archive-asf-public=cust-asf.ponee.io@incubator.apache.org Mon Aug 27 05:26:42 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7A7DC180672 for ; Mon, 27 Aug 2018 05:26:41 +0200 (CEST) Received: (qmail 59861 invoked by uid 500); 27 Aug 2018 03:26:39 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 59848 invoked by uid 99); 27 Aug 2018 03:26:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2018 03:26:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 636141804D2 for ; Mon, 27 Aug 2018 03:26:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.111 X-Spam-Level: X-Spam-Status: No, score=-0.111 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 28ThrQRzb5aC for ; Mon, 27 Aug 2018 03:26:35 +0000 (UTC) Received: from mail-pl1-f175.google.com (mail-pl1-f175.google.com [209.85.214.175]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 7D7555F543 for ; Mon, 27 Aug 2018 03:26:34 +0000 (UTC) Received: by mail-pl1-f175.google.com with SMTP id x6-v6so3500975plv.10 for ; Sun, 26 Aug 2018 20:26:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=w0w7MVDle3XByyFc7PfDp/WishrRh9XG2cEE9ixqG5o=; b=CVKg4Xwp3CtWNFTbVxmlyE84tg9UqSjUnyupDZNgWYdB8+3+gXQ+47t719qrEDMxkP Ce1DuXpW8dkwhOhPuL2vlUdEEFtkNNqA+w8IQMXhCrno/qk+1Gq6bKJLq71si6Y42mW9 GAYlLO1rf+xX1qM87pT20dcFguIS0xc+Vq+fiK0YGEtVIcgJtADTYDYkWwRsAQ4n59dB uy4xrg+ltQ1soGdQN8hKQpCC6n6LrNn8/MnSQQTnmDfiCbXzDHpVWRK8eOwOaW+aPkgs cFofKSm+r1p0gok0YcFcfYpZiuTGOlCxJ0wyKqJSLKnS3LwXHms5ssx5FVN8DFDqFRdO O+Tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=w0w7MVDle3XByyFc7PfDp/WishrRh9XG2cEE9ixqG5o=; b=kKDnxoUA7a91G5j/3eOP1d6Z0T1jmeggWRH0+ecwpmmkhjxjibGz6wV04UrvLvbtau Up67WDiNvxVoP4XWOw+HqtY+WAjpZNDonGFcTcJT427tDAKLBeHmjt/coyR2dvyN6ayH ZdjsqaAxtLNdUKY9pdwmu7IM+YNxKBqgHi73ZX5ebJdmoXhGtdnST76aKUvXvimwtQms 5/0iPr1d1u4qXr0CIZDRMj9WuK/lEqrQ690uFi4B5oq2YdgbBRaocnKdTmVXtKih5l7H n7o/rFJlHymIOJyXfyosFd8Mxlj616yQ8cZEcfExk86wN2kCufOaw6J+CkUwGqE/qpva 0UcA== X-Gm-Message-State: APzg51DBTwM63x1mVPs/+gSwBzhcAEDzy51QNC8UlB90FyaFCatX/Zkp d1E5vkKJXOaWLJ/LYgUMY8bxFjsDVTHfh8RK45QrCefZ X-Google-Smtp-Source: ANB0VdacBbEReVa4VdTwRjuf0nZyWLHI/A+Ggq5NEfwdzoOAqN72zjnF1PufmtkJSTh7da3U+TT4rFts0ZXXjJqXoqE= X-Received: by 2002:a17:902:3041:: with SMTP id u59-v6mr11081272plb.99.1535340392442; Sun, 26 Aug 2018 20:26:32 -0700 (PDT) MIME-Version: 1.0 References: <1535339658.3334760.1487003256.1BC04858@webmail.messagingengine.com> In-Reply-To: <1535339658.3334760.1487003256.1BC04858@webmail.messagingengine.com> From: Adrian Cole Date: Mon, 27 Aug 2018 10:26:21 +0700 Message-ID: Subject: Re: [VOTE] Accept Zipkin into the Apache Incubator To: general@incubator.apache.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable +1 Accept Zipkin (non binding) On Mon, Aug 27, 2018 at 10:14 AM Mick Semb Wever wrote: > > After a brief discussion=C2=B9 I would like to call a VOTE to accept Zipk= in into the Apache Incubator. > The full proposal is available on the wiki=C2=B2 and is pasted below in t= ext form as well. > > This vote will run at least 72 hours. Please VOTE as follows: > > [ ] +1 Accept Zipkin into the Apache Incubator > [ ] +0 No opinion > [ ] -1 Do not accept Zipkin into the Apache Incubator because=E2=80=A6 > > regards, > Mick > > [1] https://lists.apache.org/thread.html/54798a5059db1d5716ed9910a15c9294= 5509a25ec3b7ccb6b1215c53@%3Cgeneral.incubator.apache.org%3E > [2] https://wiki.apache.org/incubator/ZipkinProposal > > > > =3D Abstract =3D > Zipkin is a distributed tracing system. It helps gather timing data neede= d to troubleshoot latency problems in microservice architectures. It manage= s both the collection and lookup of this data. Zipkin=E2=80=99s design is b= ased on the Google Dapper paper. > > =3D Proposal =3D > Zipkin provides a defined data model and payload type for distributed tra= ce data collection. It also provides an UI and http api for querying the da= ta. Its server implements this api and includes abstractions for storage an= d transport of trace payloads. The combination of these parts avoid lock-in= to a specific tracing backend. For example, Zipkin includes integration wi= th different open source storage mechanisms like Apache Cassandra and Elast= icsearch. It also includes bridges to convert collected data and forward it= to service offerings such as Amazon X-Ray and Google Stackdriver. Ecosyste= m offering extend this portability further. > > While primarily focused on the system, Zipkin also includes tracing libra= ries which applications use to report timing information. Zipkin's core org= anization includes tracer libraries written in Java, Javascript, Go, PHP an= d Ruby. These libraries use the formats mentioned above to report data, as = well "B3" which is a header format needed to send trace identifiers along w= ith production requests. Many Zipkin libraries can also send data directly = to other services such as Amazon X-Ray and Google Stackdriver, skipping any= Zipkin infrastructure. There are also more Zipkin tracing libraries outsid= e the core organization than inside it. This is due to the "OpenZipkin" cul= ture of promoting ecosystem work. > > =3D Background =3D > Zipkin began in 2012 at Twitter during a time they were investigating per= formance problems underlying the "fail whale" seen by users. The name Zipki= n is from the Turkish word for harpoon: the harpoon that will kill the fail= ures! Incidentally, Zipkin was not the first tracing system, it had roots i= n a former system at Twitter named BigBrotherBird. It is due to BigBrotherB= ird that the de-facto tracing headers we still use today include the prefix= "X-B3". > > In 2015, a community of users noticed the project was not healthy in so f= ar as it hadn't progressed and often didn't accept pull requests, and the C= assandra backend was stuck on an unmaintained library. For example, the Apa= che Incubator H-Trace project started in some ways as a reaction to the ina= bility to customize the code. The root cause of this was Twitter moving to = internal storage (Manhattan) and also the project not being managed as a pr= oduct. By mid 2015, the community regrouped as OpenZipkin and the codebase = moved from Twitter to an org also named OpenZipkin. This led to fast progre= ss on concerns including initially a server rewrite and Docker based deploy= ment. > > In 2018, the second version of the data model completed, and along the wa= y, many new libraries became standard, including javascript, golang and PHP= . The community is dramatically larger than 2015, and Zipkin remains the mo= st popular tracing system despite heavy competition. > > =3D Rationale =3D > Zipkin is a de-facto distributed tracing system, which is more important = as architectures become more fine grained due to popularity of microservice= or even serverless architectures. Applications transition to use more comp= lex communication including asynchronous code and service mesh, increasing = the need for tools that visualize the behavior of requests as they map acro= ss an architecture. > > Zipkin's server is focused only on distributed tracing. It is meant to be= used alongside existing logging and metrics systems. Generally, the commun= ity optimizes brown field concerns such as interop over breaking changes su= ch as experimental features. The combination of code and community make Zip= kin a safe and easier choice for various sites to introduce or grow their o= bservability practice. > > =3D Initial Goals =3D > The initial goals are to mature OpenZipkin's community process. For examp= le, while OpenZipkin has a good collaborative process, it lacks formality a= round project management functions defined in the Apache Software Foundatio= n (ASF). We also seek out help with brand abuse which is becoming common pr= actice in the competitive landscape, yet demotivates volunteers. Towards vo= lunteers, help with on boarding summer of code and funding for those who ca= nnot afford to get to conferences on their own would be nice. Finally, we o= ccasionally have organizations who are constrained to only work with founda= tion projects: ASF is often mentioned, and being in the ASF removes this co= llaboration roadblock. > > Zipkin will not move all existing code into Apache. In fact, most Zipkin = ecosystem exists outside our org! The goal is to start with the data format= s and server code. Possibly the java client-side libraries can move initial= ly as well, depending on community feedback. > > =3D Current Status =3D > =3D=3D Meritocracy =3D=3D > Zipkin is an active community of contributors who are encouraged to becom= e committers. A Zipkin committer understands the importance of seeking comm= unity feedback, and the gravity of brown field concerns. Committers express= diverse interest by contributing beyond their sites immediate needs and ac= knowledging features require diverse need before being merged into the core= repositories. A camaraderie between committers and not yet committers exis= ts and is re-inforced with face to face meetups where possible. We expect t= his to continue and build with incubation and ideally acceptance into the A= pache Software Foundation (ASF). > > Zipkin encourages involvement from its community members, and the issues = are open and available to any developers who wish to contribute to the proj= ect. The Zipkin team currently seeks help and asks for suggestions utilizin= g zipkin-user and zipkin-dev Google groups and Gitter chat on https://gitte= r.im/openzipkin/zipkin. While all contributions are reviewed, generally a "= rule of three" policy on diverse need must be met before a feature is consi= dered standard. > > =3D=3D Community =3D=3D > Zipkin has a highly active and growing community of users and developers.= The community is currently fostered on chat https://gitter.im/openzipkin/z= ipkin and issues in their respective GitHub repositories, notably the main = server: https://github.com/openzipkin/zipkin > > There are well over 1000 users in the chat room and hundreds who contribu= ted code to code in the main OpenZipkin GitHub org. Interest metrics have g= rown dramatically: For example, in three years and a month from when Zipkin= began until the time OpenZipkin formed, its main repository accumulated 24= 00 GitHub stars. In the same time after, it accumulated over 6700. Other me= trics such as blog count and community meetings have similarly gone way up.= We expect further growth as more learn about Zipkin and can engage with Zi= pkin through the guidance of the Apache Software Foundation (ASF). > > =3D=3D Core Developers =3D=3D > The core contributors are a diverse group comprised of both unaffiliated = developers and those hailing from small to large companies. They are scatte= red geographically, and some are highly experienced industry as well as ope= n source developers. Though their backgrounds may be diverse, the contribut= ors are united in their belief in community driven software development. > > More detailed information on the core developers and contributors in gene= ral can be found under the section on homogeneous developers. > > =3D=3D Alignment =3D=3D > Zipkin adoption is growing, and it is no longer feasible for it to remain= as an isolated project. Apache is experienced in dealing with software tha= t is very widely accepted and has a growing audience. The proposers believe= that the Zipkin team can benefit from the ASF's experience and its broad a= rray of users and developers. > > Zipkin supports several Apache projects and options exist for integration= with others. Apache CXF, Apache Camel, Apache Incubator SkyWalking and Apa= che Incubator HTrace all utilize Zipkin APIs in their core repositories. Ma= ny more do via community extensions. Apache Maven is primarily use by Zipki= n, and can be used by projects who build upon Zipkin projects. > > =3D=3D Known Risks =3D=3D > =3D=3D=3D Orphaned products =3D=3D=3D > Zipkin is already being utilized at multiple companies that are actively = participating in improving the code. The thriving community centered around= Zipkin has seen steady growth, and the project is gaining traction with de= velopers. The risks of the code being abandoned are minimal. > > =3D=3D=3D Inexperience with Open Source =3D=3D=3D > Zipkin rebooted its community in July 2015 and grown there for over three= years. Additionally, many of the committers have extensive experience with= other open source projects. Zipkin fosters a collaborative and community-d= riven environment. > > In the interest of openly sharing technology and attracting more communit= y members, several of our developers also regularly attend conferences in N= orth America and Europe to give talks about Zipkin. Zipkin meetups are also= planned every few months for developers and community members to come toge= ther in person and discuss ideas. > > =3D=3D=3D Homogenous Developers =3D=3D=3D > At the time of the writing, OpenZipkin's core 12 developers all work at d= ifferent companies around the globe. Most operate their own tracing sites, = but some no longer operate sites at all: staying for the community we've bu= ilt. Our ASF champion, Mick Semb Wever, is both a committer and an experien= ced ASF member. > > The Zipkin developers thrive upon the diversity of the community. The Zip= kin gitter channel is always active, and the developers often collaborate o= n fixes and changes in the code. They are always happy to answer users' que= stions as well. > > Zipkin is interested in continuing to expand and strengthen its network o= f developers and community members through the ASF. > > =3D=3D=3D Reliance on Salaried Developers =3D=3D=3D > Zipkin has one full time salaried developer, Adrian Cole. Though some of = the developers are paid by their employer to contribute to Zipkin, many Zip= kin developers contribute code and documentation on their own time and have= done so for a lengthy period. Given the current stream of development requ= ests and the committers' sense of ownership of the Zipkin code, this arrang= ement is expected to continue with Zipkin' induction into the ASF. > > =3D=3D=3D Relationships with Other Apache Products =3D=3D=3D > Zipkin, Apache Incubator Skywalking and Apache Incubator HTrace address s= imiliar use cases. Most similarities are between Zipkin and HTrace: Zipkin = hopes to help serve the community formerly served by HTrace, but understand= s the data services focus of HTrace may require different tooling. SkyWalki= ng addresses more feature surface than Zipkin. For example, metrics collect= ion is not a goal of Zipkin, yet it is a goal of SkyWalking. SkyWalking acc= epts Zipkin formats and can be used as a replacement server. SkyWalking PPM= C member, Sheng Wu, has been a routine member of Zipkin design discussions = and has offered to help Zipkin through ASF process. > > While Zipkin does not directly rely upon any Apache project, zipkin suppo= rts several Apache projects. Apache CXF, Apache Camel, Apache Incubator Sky= Walking, Apache Incubator Dubbo, Apache Incubator ServiceComb and Apache In= cubator HTrace all utilize Zipkin APIs in their core repositories. Many mor= e do via community extensions. Apache Maven is primarily use by Zipkin, and= can be used by projects who build upon Zipkin projects. > > =3D=3D=3D A Excessive Fascination with the Apache Brand =3D=3D=3D > Zipkin recognizes the fortitude of the Apache brand, but the motivation f= or becoming an Apache project is to strengthen and expand the Zipkin commun= ity and its user base. While the Zipkin community has seen steady growth ov= er the past several years, association with the ASF is expected to expedite= this pattern of growth. Development is expected to continue on Zipkin unde= r the Apache license whether or not it is supported by the ASF. > > =3D=3D Documentation =3D=3D > The Zipkin project documentation is publicly available at the following s= ites: > > * https://zipkin.io: project overview > * http://zipkin.io/zipkin-api/#/: swagger specification > * https://github.com/openzipkin/b3-propagation: header formats > * https://zipkin.io/zipkin/: Javadocs for the Zipkin server > > =3D=3D Initial Source =3D=3D > The initial source is located on GitHub in the following repositories: > > * git://github.com/OpenZipkin/zipkin.git > * git://github.com/OpenZipkin/zipkin-dependencies.git > * git://github.com/OpenZipkin/zipkin-api.git > * git://github.com/OpenZipkin/b3-propagation.git > * git://github.com/OpenZipkin/docker-zipkin.git > * git://github.com/OpenZipkin/docker-zipkin-dependencies.git > * git://github.com/openzipkin/zipkin-reporter-java > * git://github.com/openzipkin/brave > * git://github.com/openzipkin/zipkin-aws > * git://github.com/openzipkin/docker-zipkin-aws > * git://github.com/openzipkin/zipkin-azure > * git://github.com/openzipkin/docker-zipkin-azure > * git://github.com/openzipkin/zipkin-gcp > * git://github.com/openzipkin/docker-zipkin-gcp > * git://github.com/openzipkin/brave-cassandra > * git://github.com/openzipkin/docker-jre-full > * git://github.com/openzipkin/brave-karaf > > Depending on community progress, other repositories may be moved as well > > =3D=3D Source and Intellectual Property Submission Plan =3D=3D > Zipkin's initial source is licensed under the Apache License, Version 2.0= . https://github.com/openzipkin/zipkin/blob/master/LICENSE > > All source code is copyrighted to 'The OpenZipkin Authors', to which the = existing core community(members list in Initial Committers) has the rights = to re-assign to the ASF. > > =3D=3D External Dependencies =3D=3D > This is a listing of Maven coordinates for all of the external dependenci= es Zipkin uses. All of the dependencies are in Sonatype and their licenses = should be accessible. > > =3D=3D Cryptography =3D=3D > Zipkin contains no cryptographic algorithms. > > =3D Required Resources =3D > =3D=3D Mailing Lists =3D=3D > * Zipkin-dev: for development discussions > * Zipkin-user: for community discussions > * Zipkin-private: for PPMC discussions > * Zipkin-commits: for code changes > > =3D=3D Git Repositories =3D=3D > The Zipkin team is experienced in git and requests to transfer GitHub rep= ositories(list in Initial Source) to Apache. > > =3D=3D Issue Tracking =3D=3D > The community would like to continue using GitHub Issues. > > =3D Initial Committers =3D > * Zolt=C3=A1n Nagy > * Adrian Cole, Pivotal > * Bas van Beek > * Brian Devins > * Eirik Sletteberg > * Jeanneret Pierre-Hugues > * Jordi Polo Carres > * Jos=C3=A9 Carlos Ch=C3=A1vez > * Kristof Adriaenssens > * Lance Linder > * Mick Semb Wever, > * Tommy Ludwig > > =3D Champion =3D > * Michael Semb Wever, mck@apache.org > > =3D Mentors =3D > * Michael Semb Wever, mck@apache.org > * Andriy Redko, reta@apache.org > * John D. Ament, johndament@apache.org > * Willem Ning Jiang, ningjiang@apache.org > > =3D Sponsoring Entity =3D > We are requesting the Apache Incubator to sponsor this project. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org > For additional commands, e-mail: general-help@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org