Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top Level Project' resolution to board

[彭勇升 Peng Yongsheng]

+1 not binding

—
Yongsheng Peng
Apache SkyWalking & ShardingSphere




> 在 2019年3月19日，13:21，Mick Semb Wever  写道：
> 
> 
> After the latest discussion amongst this dev community on this dev mailing 
> list[1],  presenting Sheng Wu as the PMC Chair and the maturity model[2], and 
> then the discussion again on the incubator list[3],  a vote for Apache 
> SkyWalking graduating to a top level project was called and has passed[4]. 
> From the past incubator discussions the PPMC altered the draft graduation 
> proposal, specifically the proposed PMC list: removing some inactive people 
> and adding all the podling Committers. 
> 
> 
> Apache SkyWalking entered the incubator on December of 2017.  SkyWalking has 
> delivered 8 releases so far in total, and now shows a good cadence of 
> successful releases.
> 
> During the podling's time in the Apache Incubator there has been
> 3200+ commits on development of the project,
>  378 Issues tagged as question in GitHub created, 373 resolved,
>  850+ Pull request created and resolved,
>  97 different contributors,
>9 elected new committers, and
>3 elected new PPMC members.
> 
> And the dev ML has had 72 participants: 
> https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019
> 
> Attached is the draft Resolution for the PPMC and IPMC to vote upon.
> 
> Please take a minute to vote on whether or not Apache SkyWalking should
> graduate to a Top Level Project by responding with one of the following:
> 
> [ ] +1 Apache SkyWalking should graduate.
> [ ] +0 No opinion
> [ ] -1 Apache SkyWalking should not graduate (please provide the reason)
> 
> The VOTE is open for a minimum of 72 hours. As there has been previous 
> discussions on past versions of this proposal, I have not preluded the vote 
> with a DISCUSS email. If feedback arises the vote period will be extended in 
> good faith.
> 
> regards,
> Mick
> 
> 
> [1] 
> https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E
> [2] 
> https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking
> [3] 
> https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E
> [4] 
> https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E
> 
> 
> 
> 
> Establish the Apache SkyWalking 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 application performance management and monitoring (APM).
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache SkyWalking Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache SkyWalking Project be and hereby is
> responsible for the creation and maintenance of software related to
> application performance management and monitoring (APM); and 
> be it further
> 
> RESOLVED, that the office of "Vice President, Apache SkyWalking" 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
> SkyWalking Project, and to have primary responsibility for management of
> the projects within the scope of responsibility of the Apache SkyWalking
> 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 SkyWalking
> Project:
> 
>  * Haoyang Liu  (刘浩杨)  
>  * Hongtao Gao  (高洪涛)  
>  * Ignasi Barrera  
>  * Mick Semb Wever 
>  * Sheng Wu  (吴晟)  
>  * Shinn Zhang  (张鑫)   
>  * Willem Ning Jiang  (姜宁)
>  * Yongsheng Peng  (彭勇升)   
>  * DongXue Si (司冬雪)
>  * Jian Tan (谭建)   
>  * Kai Wang (王凯)   
>  * Yang Bai (柏杨)   
>  * Yao Wang (王垚)   
>  * Zhang Kewei (张科伟)  
> * Can Li (李璨)  
> * Jiaqi Lin (林嘉绮)  
> * Jinlin Fu (付金林)  
> * Lang Li (李浪)   
> * Wenbin Wang (王文斌)
> * Yixiong Cao (曹奕雄)
> 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Wu (吴晟) be 
> appointed to the office of Vice President, Apache SkyWalking, 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 

Re: [DISCUSS] Sharding-Sphere incubation proposal

[彭勇升 Peng Yongsheng]

Thanks to Sharding-Sphere team. 


My introduction:

The company I worked for and the company I’m working for are using 
Sharding-Sphere. And the Sharding-Sphere is one of the SkyWalking’s OAP storage 
implementation. 

So, I think I can help so more, whether coding or community. 

—
Yongsheng Peng
Apache SkyWalking PPMC member



> 在 2018年11月2日，23:35，吴晟 Sheng Wu  写道：
> 
> Based inside project discussion, a volunteer and new initial committer, 
> Yongsheng Peng added to the proposal.
> 
> 
> --
> Sheng Wu
> Apache SkyWalking 
> 
> 
> 
> 
> 
> 
> 
> -- Original --
> From:  "吴晟 Sheng Wu";
> Date:  Mon, Oct 29, 2018 08:25 PM
> To:  "general";
> 
> Subject:  Re: [DISCUSS] Sharding-Sphere incubation proposal
> 
> 
> 
> +1 no-binding
> 
> 
> Welcome Sharding-Sphere, a wild used sql proxy(in/out of process) project 
> join the Apache Incubator. 
> The status of project is good. The community is diversity, contributors from 
> different companies or as individuals.
> 
> 
> --
> Sheng Wu
> Apache SkyWalking 
> 
> 
> 
> 
> 
> 
> 
> -- Original --
> From:  "zhangli...@apache.org";
> Date:  Mon, Oct 29, 2018 05:27 PM
> To:  "general";
> 
> Subject:  [DISCUSS] Sharding-Sphere incubation proposal
> 
> 
> 
> Dear Apache Incubator Community,
> 
> I would like to start a discussion about the incubation of Sharding-Sphere
> at Apache.
> 
> Please accept the Sharding-Sphere podling into the Incubator.
> 
> We have 4 mentors, also we are welcome other volunteers to mentor us.
> 
> The proposal can be found at
> https://wiki.apache.org/incubator/ShardingSphereProposal . Here is the text
> of it:
> 
> 
> = Abstract =
> Sharding-Sphere is an ecosystem of transparent distributed database
> middleware, focusing on data sharding, distributed transaction and database
> orchestration. It provides maximum compatibility for applications through
> Sharding-JDBC (a driver to implement JDBC) or Sharding-Proxy (a proxy to
> implement database protocol).
> 
> = Proposal =
> With a large number of end users, Sharding-Sphere has a fairly huge
> community in China. It is also widely adopted by many [[
> http://shardingsphere.io/community/en/company/|companies and
> organizations]] as a solution to process their massive amounts of data.
> 
> We believe that bringing Sharding-Sphere into Apache Software Foundation
> could advance development of a stronger and more diverse open source
> community.
> 
> Dangdang submits this proposal to donate Sharding-Sphere's source codes and
> all related documentations to Apache Software Foundation. The codes are
> already under Apache License Version 2.0.
> 
>  * Code base: https://github.com/sharding-sphere/sharding-sphere
> 
>  * Web site: http://shardingsphere.io/
> 
>  * Documentations: http://shardingsphere.io/document/current/
> 
>  * Community: http://shardingsphere.io/community/
> 
> = Background =
> 
> Relational database hardly supports such huge amounts of data any more
> which has increased rapidly in recent years, but for reason of technique
> maturity, developers and DBAs still want to use it to persist core data.
> 
> Sharding-Sphere was open sourced on Github in 2016. At the very beginning,
> Sharding-Sphere is just a JDBC driver for data sharding (name as
> Sharding-JDBC) at Dangdang internal framework; now it offers data sharding,
> distributed transaction and database orchestration. Besides JDBC, proxy to
> implement MySQL database protocol is also supported at present.
> Furthermore, our roadmap includes Proxy for PostgreSQL protocol, Sidecar
> model, data repica and elastic data scalability function as well.
> 
> Due to the extension of project, we provide proxy model and sidecar model
> in addition to JDBC model. Therefore, we rename it to Sharding-Sphere by [[
> https://github.com/sharding-sphere/sharding-sphere/issues/788|a public
> vote]], which refers to a sharding ecosphere with Sharding-JDBC,
> Sharding-Proxy and Sharding Sidecar as its three sub-projects.
> 
> Sharding-JDBC has won the [[http://www.oschina.net/project/top_cn_2016|TOP
> 20 most popular open source projects in China 2016]].
> 
> = Rationale =
> 
> Relational database still plays a very important role on current
> application system. The maturity of products and surrounding ecosystem, the
> friendliness of its data query and developers' and DBAs' mastery of it,
> cannot be completely replaced with other types of database in the near
> future. However, current relational database cannot support cloud native
> very well and it is not friendly to distributed system.
> 
> It is the ultimate goal of Sharding-Sphere, which manages the databases
> scattering around the system, to make user use distributed databases as
> simply as using a single one.
> 
> Without extra cost, Sharding-JDBC directly connects database with Java
> application to get the best performance.
> 
> Sharding-Proxy is deployed as a stateless server 

Re: [DISCUSS] Sharding-Sphere incubation proposal

[彭勇升 Peng Yongsheng]

Hi, ZhangLiang:
This project looks so interesting, I wana to join. 

—
Yongsheng Peng
Apache SkyWalking PPMC member



> 在 2018年10月29日，17:27，zhangli...@apache.org 写道：
> 
> Dear Apache Incubator Community,
> 
> I would like to start a discussion about the incubation of Sharding-Sphere
> at Apache.
> 
> Please accept the Sharding-Sphere podling into the Incubator.
> 
> We have 4 mentors, also we are welcome other volunteers to mentor us.
> 
> The proposal can be found at
> https://wiki.apache.org/incubator/ShardingSphereProposal . Here is the text
> of it:
> 
> 
> = Abstract =
> Sharding-Sphere is an ecosystem of transparent distributed database
> middleware, focusing on data sharding, distributed transaction and database
> orchestration. It provides maximum compatibility for applications through
> Sharding-JDBC (a driver to implement JDBC) or Sharding-Proxy (a proxy to
> implement database protocol).
> 
> = Proposal =
> With a large number of end users, Sharding-Sphere has a fairly huge
> community in China. It is also widely adopted by many [[
> http://shardingsphere.io/community/en/company/|companies and
> organizations]] as a solution to process their massive amounts of data.
> 
> We believe that bringing Sharding-Sphere into Apache Software Foundation
> could advance development of a stronger and more diverse open source
> community.
> 
> Dangdang submits this proposal to donate Sharding-Sphere's source codes and
> all related documentations to Apache Software Foundation. The codes are
> already under Apache License Version 2.0.
> 
>  * Code base: https://github.com/sharding-sphere/sharding-sphere
> 
>  * Web site: http://shardingsphere.io/
> 
>  * Documentations: http://shardingsphere.io/document/current/
> 
>  * Community: http://shardingsphere.io/community/
> 
> = Background =
> 
> Relational database hardly supports such huge amounts of data any more
> which has increased rapidly in recent years, but for reason of technique
> maturity, developers and DBAs still want to use it to persist core data.
> 
> Sharding-Sphere was open sourced on Github in 2016. At the very beginning,
> Sharding-Sphere is just a JDBC driver for data sharding (name as
> Sharding-JDBC) at Dangdang internal framework; now it offers data sharding,
> distributed transaction and database orchestration. Besides JDBC, proxy to
> implement MySQL database protocol is also supported at present.
> Furthermore, our roadmap includes Proxy for PostgreSQL protocol, Sidecar
> model, data repica and elastic data scalability function as well.
> 
> Due to the extension of project, we provide proxy model and sidecar model
> in addition to JDBC model. Therefore, we rename it to Sharding-Sphere by [[
> https://github.com/sharding-sphere/sharding-sphere/issues/788|a public
> vote]], which refers to a sharding ecosphere with Sharding-JDBC,
> Sharding-Proxy and Sharding Sidecar as its three sub-projects.
> 
> Sharding-JDBC has won the [[http://www.oschina.net/project/top_cn_2016|TOP
> 20 most popular open source projects in China 2016]].
> 
> = Rationale =
> 
> Relational database still plays a very important role on current
> application system. The maturity of products and surrounding ecosystem, the
> friendliness of its data query and developers' and DBAs' mastery of it,
> cannot be completely replaced with other types of database in the near
> future. However, current relational database cannot support cloud native
> very well and it is not friendly to distributed system.
> 
> It is the ultimate goal of Sharding-Sphere, which manages the databases
> scattering around the system, to make user use distributed databases as
> simply as using a single one.
> 
> Without extra cost, Sharding-JDBC directly connects database with Java
> application to get the best performance.
> 
> Sharding-Proxy is deployed as a stateless server and supports MySQL
> protocol at present. In the paper [[
> https://db.cs.cmu.edu/papers/2016/pavlo-newsql-sigmodrec2016.pdf|What’s
> Really New with NewSQL?]], three types of NewSQL are introduced, among
> which Sharding-Proxy is a Transparent Sharding Middleware.
> 
> Sharding-Sidecar can be understood as a data panel in Service Mesh. The
> interaction between the application and the database provides a mesh layer.
> The concept of Database Mesh is similar to Service Mesh, and it focuses on
> how to connect data access applications to the database. Database Mesh will
> set up a huge grid system between applications and databases. Applications
> and databases need be placed in the grid system. They are all objects
> managed by the meshing layer.
> 
> = Current Status =
> == Meritocracy ==
> Sharding-Sphere was incubated at Dangdang in 2015 and open sourced on
> GitHub in 2016. In 2017, JingDong recognized its value and determined to
> sponsor this project. Sharding-Sphere has contributors and users from many
> companies; we have set up the PMC Team and Committer Team. New contributors
> are guided and reviewed 

Re: [VOTE] Accept Zipkin into the Apache Incubator

[彭勇升 Peng Yongsheng]

+1 (non-binding)


—
Yongsheng Peng
Apache SkyWalking PPMC member



> 在 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.
> 
> Zipkin's server is focused only on distributed tracing. It is meant to be 
> used alongside existing logging and metrics systems. Generally, the community 
> optimizes brown field concerns such as interop over breaking changes such as 
> experimental features. The combination of code and community make Zipkin a 
> safe and easier choice for various sites to introduce or grow their 
> observability practice.
> 
> = Initial Goals =
> The initial goals are to mature OpenZipkin's community process. For example, 
> while OpenZipkin has a good collaborative process, it lacks formality around 
> project management functions 

Re: Interested to contributing for SkyWalk

[彭勇升 Peng Yongsheng]

Welcome, join our team.

—
Yongsheng Peng
Apache SkyWalking PPMC member



> 在 2018年7月11日，22:59，Kumar Nishant  写道：
> 
> Hi,
> I am interested in contributing to Skywalk project since it is from the
> scratch. Would it be possible if I can work under any individual or team
> and contribute? This will help me learn something new and provide my
> contribution to the community.
> 
> Please let me know if possible.
> 
> Reards
> Nishant

Re: [ANN] Please welcome Justin Mclean as the new Incubator PMC chair!

[彭勇升 Peng Yongsheng]

Congratulations!
Thanks very much for our first incubator version release.  Our project retry 
three times by this version release. Justin checked it very patiently and 
helped us to fixed the issues.

—
Yongsheng Peng
Apache SkyWalking PPMC member



> 在 2018年6月4日，18:12，Bertrand Delacretaz  写道：
> 
> Hi,
> 
> John D. Ament recently announced his desire to step down from the
> Incubator PMC chair role. Thank you so much John for your efficient
> service here, "retiring" from that is certainly well deserved!
> 
> The Incubator PMC had the difficult task of choosing between a handful
> of excellent candidates and has selected Justin as our new chair. The
> ASF's Board of Directors has ratified this choice at our May meeting.
> 
> Please join me in welcoming Jusin as our new PMC chair! Justin's been
> very active in the Incubator in the last few years, it's great to see
> him step up to this role.
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [ANN] Please welcome Justin Mclean as the new Incubator PMC chair!

[彭勇升 Peng Yongsheng]

Congratulations!
Thanks very much for our first incubator version release.  Our project retry 
three times by this version release. Justin checked it very patiently and 
helped us to fixed the issues.

—
Yongsheng Peng
Apache SkyWalking PPMC member



> 在 2018年6月4日，22:34，Juan P  写道：
> 
> Congratulations and thanks, Justin!
> Thanks Jhon for the effort!!
> 
> On 4 June 2018 at 16:17, Makoto Yui  wrote:
> 
>> Congratulations Justin! Happy to have a very active chair.
>> And, thank you for John for the hard work you have done.
>> 
>> Makoto
>> 2018年6月4日(月) 22:49 Geertjan Wielenga :
>>> 
>>> Congratulations and thanks for your great work and support of the Apache
>>> NetBeans (incubating) project, looking forward to even more interactions
>>> with you.
>>> 
>>> Gj
>>> 
>>> On Mon, Jun 4, 2018 at 3:10 PM, Sharan Foga  wrote:
>>> 
 Congratulations Justin and thanks John for all the hard work you have
>> done!
 
 On 2018/06/04 10:12:21, Bertrand Delacretaz 
 wrote:
> Hi,
> 
> John D. Ament recently announced his desire to step down from the
> Incubator PMC chair role. Thank you so much John for your efficient
> service here, "retiring" from that is certainly well deserved!
> 
> The Incubator PMC had the difficult task of choosing between a
>> handful
> of excellent candidates and has selected Justin as our new chair. The
> ASF's Board of Directors has ratified this choice at our May meeting.
> 
> Please join me in welcoming Jusin as our new PMC chair! Justin's been
> very active in the Incubator in the last few years, it's great to see
> him step up to this role.
> 
> -Bertrand
> 
> 
>> -
> 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
 
 
>> 
>> --
>> Makoto YUI 
>> Research Engineer, Treasure Data, Inc.
>> http://myui.github.io/
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta

[彭勇升 Peng Yongsheng]

Hi all,

The vote for releasing Apache SkyWalking 5.0.0-beta (incubating) is closed, now.

Vote result:
3 (+1 binding) (st...@apache.org , m...@apache.org 
 and willem.ji...@gmail.com 
)
No -1.

Thank you everyone for taking the time to review the release and help us. 

I will procedd to publish the release and send ANNOUNCE.

—
Yongsheng Peng
Apache SkyWalking PPMC member


—
Yongsheng Peng
Apache SkyWalking PPMC member

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta

[彭勇升 Peng Yongsheng]

> - Peng Yongsheng, please remember to keep your english (ascii) name in the 
> email from field along with your real name: 彭勇升 
> When you sent the mail to IPMC there was no english name accompanying your 
> chinese name. Sheng is consistent in this practice, so is a good example. 
> I know it's unfortunate, but those of us that can't speak chinese simply find 
> it too difficult to distinguish and remember the chinese characters and names.
> This will also hinder you from getting responses and votes.

Thanks mck. I changed it.

—
Yongsheng Peng
Apache SkyWalking PPMC member