Re: RE: [VOTE] Graduate Apache ServiceComb (incubating)
+1 (non-binding) Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Liu Guo <13493...@qq.com> 于2018年9月27日周四 下午10:04写道： > +1 (non-binding) > > > -- Original -- > From: Gangumalla, Uma > Date: Thu,Sep 27,2018 2:44 AM > To: general@incubator.apache.org > Subject: Re: RE: [VOTE] Graduate Apache ServiceComb (incubating) > > > > +1 (binding) > > Regards, > Uma > > -Original Message- > From: Dave Fisher [mailto:dave2w...@comcast.net] > Sent: Wednesday, September 26, 2018 11:31 AM > To: general@incubator.apache.org > Subject: Re: [VOTE] Graduate Apache ServiceComb (incubating) > > +1 (binding) > > > On Sep 26, 2018, at 12:06 AM, Roman Shaposhnik wrote: > > > > Hi! > > > > given that we've got only positive feedback on the DISCUSS thread I'd > > like to start an official VOTE thread now. > > > > Please vote on the resolution pasted below to graduate Apache > > ServiceComb from the incubator to the top level project. > > > > [ ] +1 Graduate Apache ServiceComb from the Incubator. > > [ ] +0 Don't care. > > [ ] -1 Don't graduate Apache ServiceComb from the Incubator because... > > > > This vote will be open for at least 72 hours. > > > > Many thanks to our mentors and everyone else for their support, Roman > > (on behalf of the Apache ServiceComb PPMC). > > > > ## Resolution to create a TLP from graduating Incubator podling > > > > X. Establish the Apache ServiceComb Project > > > > WHEREAS, the Board of Directors deems it to be in the best interests > > of the Foundation and consistent with the Foundation's purpose to > > establish a Project Management Committee charged with the creation and > > maintenance of open-source software, for distribution at no charge to > > the public, related to a microservice framework that provides a set of > > tools and components to make development and deployment of cloud > > applications easier. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > (PMC), to be known as the "Apache ServiceComb Project", be and hereby > > is established pursuant to Bylaws of the Foundation; and be it further > > > > RESOLVED, that the Apache ServiceComb Project be and hereby is > > responsible for the creation and maintenance of software related to a > > microservice framework that provides a set of tools and components to > > make development and deployment of cloud applications easier; and be > > it further > > > > RESOLVED, that the office of "Vice President, Apache ServiceComb" be > > and hereby is created, the person holding such office to serve at the > > direction of the Board of Directors as the chair of the Apache > > ServiceComb Project, and to have primary responsibility for management > > of the projects within the scope of responsibility of the Apache > > ServiceComb Project; and be it further > > > > RESOLVED, that the persons listed immediately below be and hereby are > > appointed to serve as the initial members of the Apache ServiceComb > > Project: > > > > * Aray Chenchu Sukesh > > * Bao Liu > > * Eric Lee > > * Jean-Baptiste Onofré > > * Jimin Wu > > * Linzhinan > > * Mohammad Asif Siddiqui > > * Qi Zhang > > * Roman Shaposhnik > > * Timothy Chen > > * Willem Ning Jiang > > * Yang Bo > > * Yihua Cui > > * Yin Xiang > > * Zheng Feng > > * zhengyangyong > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Willem Ning Jiang be > > appointed to the office of Vice President, Apache ServiceComb, to > > serve in accordance with and subject to the direction of the Board of > > Directors and the Bylaws of the Foundation until death, resignation, > > retirement, removal or disqualification, or until a successor is > > appointed; and be it further > > > > RESOLVED, that the Apache ServiceComb Project be and hereby is tasked > > with the migration and rationalization of the Apache Incubator > > ServiceComb podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > ServiceComb podling encumbered upon the Apache Incubator PMC are > > hereafter discharged. > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Zipkin into the Apache Incubator
+1 non binding Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Von Gosling 于2018年8月27日周一 下午2:07写道： > +1, wish a stable host place for Zipkin :-) > > > Best Regards, > Von Gosling > > > 在 2018年8月27日，11:14，Mick Semb Wever 写道： > > > > After a brief discussion¹ I would like to call a VOTE to accept Zipkin > into the Apache Incubator. > > The full proposal is available on the wiki² and is pasted below in text > 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… > > > > regards, > > Mick > > > > [1] > https://lists.apache.org/thread.html/54798a5059db1d5716ed9910a15c92945509a25ec3b7ccb6b1215c53@%3Cgeneral.incubator.apache.org%3E > > [2] https://wiki.apache.org/incubator/ZipkinProposal > > > > > > > > = Abstract = > > Zipkin is a distributed tracing system. It helps gather timing data > needed to troubleshoot latency problems in microservice architectures. It > manages both the collection and lookup of this data. Zipkin’s design is > based on the Google Dapper paper. > > > > = Proposal = > > Zipkin provides a defined data model and payload type for distributed > trace data collection. It also provides an UI and http api for querying the > data. Its server implements this api and includes abstractions for storage > and transport of trace payloads. The combination of these parts avoid > lock-in to a specific tracing backend. For example, Zipkin includes > integration with different open source storage mechanisms like Apache > Cassandra and Elasticsearch. It also includes bridges to convert collected > data and forward it to service offerings such as Amazon X-Ray and Google > Stackdriver. Ecosystem offering extend this portability further. > > > > While primarily focused on the system, Zipkin also includes tracing > libraries which applications use to report timing information. Zipkin's > core organization includes tracer libraries written in Java, Javascript, > Go, PHP and 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 with 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 outside the core organization than inside it. This is due > to the "OpenZipkin" culture of promoting ecosystem work. > > > > = Background = > > Zipkin began in 2012 at Twitter during a time they were investigating > performance problems underlying the "fail whale" seen by users. The name > Zipkin is from the Turkish word for harpoon: the harpoon that will kill the > failures! Incidentally, Zipkin was not the first tracing system, it had > roots in a former system at Twitter named BigBrotherBird. It is due to > BigBrotherBird 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 > far as it hadn't progressed and often didn't accept pull requests, and the > Cassandra backend was stuck on an unmaintained library. For example, the > Apache Incubator H-Trace project started in some ways as a reaction to the > inability 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 > product. By mid 2015, the community regrouped as OpenZipkin and the > codebase moved from Twitter to an org also named OpenZipkin. This led to > fast progress on concerns including initially a server rewrite and Docker > based deployment. > > > > In 2018, the second version of the data model completed, and along the > way, many new libraries became standard, including javascript, golang and > PHP. The community is dramatically larger than 2015, and Zipkin remains the > most popular tracing system despite heavy competition. > > > > = Rationale = > > 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 > complex communication including asynchronous code and service mesh, > increasing the need for tools that visualize the behavior of requests as > they map across an architecture. > > > >
