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 

Help wanted about the license of the theme for building SkyWalking's website.

[peng-yongsheng]

Hello Incubator PMC’ers,

I purchased a WordPress theme from the site of https://themeforest.net, and
this theme's license is a regular license.

This license description is:
1. You are licensed to use the Item to create one single End Product for
yourself or for one client (a “single application”), and the End Product
can be distributed for Free.
2. You can create one End Product for a client, and you can transfer that
single End Product to your client for any fee. This license is then
transferred to your client.


And the ThemeForest say something can't do with the theme:
1. You can’t Sell the End Product, except to one client. (If you or your
client want to Sell the End Product, you will need the Extended License.)
2. You can’t re-distribute the Item as stock, in a tool or template, or
with source files. You can’t do this with an Item either on its own or
bundled with other items, and even if you modify the Item. You can’t
re-distribute or make available the Item as-is or with superficial
modifications. These things are not allowed even if the re-distribution is
for Free
3. You can’t use the Item in any application allowing an end user to
customise a digital or physical product to their specific needs, such as an
“on demand”, “made to order” or “build it yourself” application. You can
use the Item in this way only if you purchase a separate license for each
final product incorporating the Item that is created using the application.
4. Although you can modify the Item and therefore delete unwanted
components before creating your single End Product, you can’t extract and
use a single component of an Item on a stand-alone basis.

The detail of regular license:
https://themeforest.net/licenses/terms/regular/2.2%20(Copy)

*Can we use this theme for building SkyWalking's website?*


*The attachment is the authorization file of the theme.*

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

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

[peng-yongsheng]

The following are the version settings in the releasing step: 
1. The version in sources and binaries to be such as: 5.0.0-beta
2. The tag in Github to be such as: 5.0.0-beta[RC1]

If the vote accepted then create a new tag named 5.0.0-beta or change the tag 
from 5.0.0-beta[RC1] to 5.0.0-beta.
If not, then 
(1) update the sources and binaries, keep version unchanged.
(2) delete the tag 5.0.0-beta[RC1]
(3) create a new tag 5.0.0-beta[RC2] and revote.

So, If we do it as this steps. We can save the version number named 5.0.0-beta 
when vote not accept.

—
Yongsheng Peng
Apache SkyWalking PPMC member



> 在 2018年5月21日，21:23，Stian Soiland-Reyes  写道：
> 
> On Mon, 21 May 2018 15:31:49 +0800, "吴晟 Sheng Wu"  
> wrote:
>> I understand in next time, we should add svn revision number. And do
>> you suggest we should add checksum in the mail? 
> 
> Yes, checksums in the vote email can be good as they are easy to
> cross-check, say if there is an RC2 vote followed by RC1,
> a PMC member who accidentally tests the old one again would not get the
> right checksum.
> 
> 
> Another reason is archival - a checksum sent to the email list, while 
> unencrypted it is archived in multiple distributed archives and so
> becomes a permanent record about the versioned archive the PMC
> (eventually) publish and easy for anyone (say a Debian maintainer) to
> check/hardcode independent of the more origin-centric GPG signature.
> 
> 
> This would also make it easier to detect a 'rogue committer' (or more
> likely a wrong command line) that publish something that was not voted
> on.  In the end the checksum files on the https://www.apache.org/dist/
> should then match a vote email.  
> (AFAIK, nobody has attempted to automate such a check :)
> 
> 
> You have done well switching to secure sha512, but unlike say md5 and
> sha1 these are unfortunately not so email-friendly due to long lines,
> so if you want to try with sha512, sha512224, or fall back to sha1 for
> votes.. I don't know what would be easiest for your project.
> 
> So I would let that be up to the SkyWalking community to decide, but
> IMHO at least one of either either svn revision or checksum should be in
> the email so it's clear what is being voted on. :)
> 
> 
> -- 
> Stian Soiland-Reyes
> The University of Manchester
> https://www.esciencelab.org.uk/
> https://orcid.org/-0001-9842-9718
> 
> 
> -
> 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) version5.0.0-alpha(3rdround)

[peng-yongsheng]

Maybe the source codes tar in github is not pass through this voting process.

—
Yongsheng Peng
Apache SkyWalking PPMC member



> 在 2018年4月1日，21:18，吴晟 Sheng Wu  写道：
> 
> Hi Sebb
> 
> 
>> Also, when GitHub is used to grab the code as a Zip, it does not
>> include the submodules.
>> Maybe there is a setting that can tell GitHub to adjust the Zip
>> contents as well.
> 
> Actually I don't know the way to do so. Even there is, Apache may more prefer 
> to use their own source codes tar ball than the github, right?
> 
> 
> --
> Sheng Wu
> Apache SkyWalking original creator and PPMC member
> 
> 
> 
> 
> 
> 
> 
> -- Original --
> From:  "sebb";
> Date:  Sun, Apr 1, 2018 09:12 PM
> To:  "general";
> 
> Subject:  Re: [VOTE] Release Apache SkyWalking (incubating) 
> version5.0.0-alpha(3rdround)
> 
> 
> 
> On 1 April 2018 at 14:03, John D. Ament  wrote:
>> From reading through this, I think I understand the confusion faced.
>> 
>> Typically when we see a source release, its tied to a single git repo.
>> Generating the source release in this case involves a special type of git
>> checkout, which IMHO is just fine.
>> 
>> It just needs to be documented that when you clone the repo, it's using the
>> --recurse-submodules flag.  This should result in
>> 
>> Cloning into 'incubator-skywalking'...
>> remote: Counting objects: 114594, done.
>> remote: Compressing objects: 100% (38/38), done.
>> remote: Total 114594 (delta 10), reused 29 (delta 2), pack-reused 114539
>> Receiving objects: 100% (114594/114594), 134.38 MiB | 4.55 MiB/s, done.
>> Resolving deltas: 100% (44254/44254), done.
>> Submodule 'apm-protocol/apm-network/src/main/proto' (
>> https://github.com/apache/incubator-skywalking-data-collect-protocol.git)
>> registered for path 'apm-protocol/apm-network/src/main/proto'
>> Submodule 'skywalking-ui' (https://github.com/apache/incubator-skywalking-ui)
>> registered for path 'skywalking-ui'
>> Cloning into
>> '/Users/johnament/src/apache/incubator-skywalking/apm-protocol/apm-network/src/main/proto'...
>> remote: Counting objects: 52, done.
>> remote: Compressing objects: 100% (44/44), done.
>> remote: Total 52 (delta 34), reused 10 (delta 8), pack-reused 0
>> Cloning into
>> '/Users/johnament/src/apache/incubator-skywalking/skywalking-ui'...
>> remote: Counting objects: 4374, done.
>> remote: Compressing objects: 100% (84/84), done.
>> remote: Total 4374 (delta 38), reused 51 (delta 17), pack-reused 4268
>> 
>> Receiving objects: 100% (4374/4374), 3.56 MiB | 6.15 MiB/s, done.
>> Resolving deltas: 100% (2107/2107), done.
>> Submodule path 'apm-protocol/apm-network/src/main/proto': checked out
>> 'c02c12af12116121e25155d1f3fca0fadee5f2e9'
>> Submodule path 'skywalking-ui': checked out
>> '922c012efd0c385e3c502d06d2730c73452f779d'
>> 
>> 
>> and then the checks that Sebb is trying should work.
>> 
>> Sheng, do you know if this checkout is documented somewhere?
> 
> Also, when GitHub is used to grab the code as a Zip, it does not
> include the submodules.
> 
> Maybe there is a setting that can tell GitHub to adjust the Zip
> contents as well.
> 
>> John
>> 
>> On Sun, Apr 1, 2018 at 8:49 AM sebb  wrote:
>> 
>>> On 1 April 2018 at 01:43, 吴晟 Sheng Wu  wrote:
 Hi sebb,
 
 
 I see your point, that is why we provide the build document[1] if you
>>> want to build from GitHub tag. Git submodules are used in our project for
>>> binding multi repos. The source codes tar is provided by running some
>>> source code release process, by following project document[2] and script
>>> [3].
>>> 
>>> I see.
>>> So cloning the Git repo is not sufficient to get all the code (unless
>>> there is an option to automatically include submodules that I have
>>> missed).
>>> 
 
 And for `dependency-reduced-pom.xml`, it is generated in building the
>>> project, when we run build and tar source code. If you think we should not
>>> include it, I think we can add an exclusion in next release.
>>> 
>>> That would be a good idea.
>>> 
 
 Is that good enough for you?
>>> 
>>> I think there is a problem with the build process, because the source
>>> artifact contains other items that are not in Git.
>>> 
>>> $ diff -r incubator-skywalking/
>>> apache-skywalking-apm-incubating-5.0.0-alpha
>>> Only in incubator-skywalking/: .git
>>> Only in incubator-skywalking/: .github
>>> Only in incubator-skywalking/: .gitignore
>>> Only in incubator-skywalking/: .travis.yml
>>> Only in incubator-skywalking/apm-protocol/apm-network/src/main/proto: .git
>>> Only in apache-skywalking-apm-incubating-5.0.0-alpha/apm-sniffer/apm-agent:
>>> dependency-reduced-pom.xml
>>> Only in
>>> apache-skywalking-apm-incubating-5.0.0-alpha/apm-sniffer/apm-agent-core:
>>> dependency-reduced-pom.xml
>>> Only in
>>> 

Re: [VOTE] Release Apache SkyWalking (incubating) version5.0.0-alpha(2ndround)

[peng-yongsheng]

From this site:  http://mvnrepository.com/artifact/net.java.dev.jna/jna/4.4.0 
, 
The license of this jna-4.4.0 is LGPL 2.1 and Apache 2.0.


But from the Github home page: https://github.com/java-native-access/jna 
,
At the end of README document,  they said: " (from version 4.0 onward) the 
Apache Software License, version 2.0”.

We used the 4.4.0 version. So, can we use this component in our product?


> 在 2018年3月26日，04:35，sebb  写道：
> 
> On 25 March 2018 at 21:23, Justin Mclean  wrote:
>> Hi,
>> 
>> If it is bundled and under a ALv2 license you can list it in LICENSE if you 
>> want to but it’s not required.
> 
> The document also says:
> 
> "However, for completeness it is useful to list the products and their
> versions, as is done for products under other licenses."
> 
> This makes it easier for consumers (and developers) to determine what
> licenses apply to the bundled bits.
> Otherwise it's not clear whether there is no entry in LICENSE because
> it has been overlooked.
> 
>> Thanks,
>> Justin
>> -
>> 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] Release Apache SkyWalking (incubating) version5.0.0-alpha(2ndround)

[peng-yongsheng]

 
BUNDLING AN APACHE-2.0-LICENSED DEPENDENCY 

Assuming once again that that the bundled dependency itself contains no bundled 
subcomponents under other licenses and thus the ALv2 applies uniformly to all 
files, there is no need to modify LICENSE. However, for completeness it is 
useful to list the products and their versions, as is done for products under 
other licenses.

If the dependency supplies a NOTICE file, its contents must be analyzed and the 
relevant portions bubbled up into the top-level NOTICE file.



I think this section means: List the apache-2.0 licensed dependency is not 
necessary. 


> 在 2018年3月25日，21:45，吴晟 Sheng Wu  写道：
> 
> When I recheck our release, we are using Apache HTTPComponent, should its 
> license list in our distribution licenses?
> 
> 
> --
> Sheng Wu
> Apache SkyWalking original creator and PPMC member
> 
> 
> 
> 
> 
> 
> 
> -- Original --
> From:  "Matt Sicker";
> Date:  Sun, Mar 25, 2018 01:47 AM
> To:  "general";
> 
> Subject:  Re: [VOTE] Release Apache SkyWalking (incubating) 
> version5.0.0-alpha(2ndround)
> 
> 
> 
> I’ve primarily used excludes in rat to exclude files that can’t include a
> license header or that does have one but rat doesn’t recognize it (I’ve
> seen this problem with a minified version of jquery for example).
> 
> On Sat, Mar 24, 2018 at 03:31, 吴晟 Sheng Wu  wrote:
> 
>> Justin
>> 
>> 
>> Thanks for helping.
>> 
>> 
>> Sheng Wu
>> 
>> 
>> 
>> ---Original---
>> From: "Justin Mclean"
>> Date: Sat, Mar 24, 2018 16:21 PM
>> To: "general";
>> Subject: Re: [VOTE] Release Apache SkyWalking (incubating)
>> version5.0.0-alpha(2nd round)
>> 
>> 
>> Hi,
>> 
>>> Right now, I updated our rat exclude config as following, is this
>> allowed?
>> 
>> Rat is just a tool, so anything is allowed. It’s up to you to check it
>> complies with ASF policy.
>> 
>>> The concern may about JSON file for our test cases data and frontend/UI
>> dependency descriptions, but JSON format is not allowed to add the header.
>> 
>> You can’t add headers to JSON files so that’s fine.
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> -- 
> Matt Sicker 

Re: [VOTE] Release Apache SkyWalking (Incubating) 5.0.0-alpha

[peng-yongsheng]

OK, we got it: 
don't try to publish .sha256, .sha512 files ; it doesn't work
.md5's in dist.apache.org/repos/dist/release/ must be removed manually.



> 在 2018年3月18日，15:19，Henk P. Penning  写道：
> 
> On Sat, 17 Mar 2018, John D. Ament wrote:
> 
>> Date: Sat, 17 Mar 2018 14:21:47 +0100
>> From: John D. Ament 
>> To: general@incubator.apache.org
>> Cc: dev 
>> Subject: Re: [VOTE] Release Apache SkyWalking (Incubating) 5.0.0-alpha
> 
>> I would recommend you review the release policy and release distribution
>> policy
>> 
>> http://www.apache.org/legal/release-policy.html
>> http://www.apache.org/dev/release-distribution.html
> 
>  In view of policy : please remove the .md5's from 5.0.0-alpha/
> 
>  Thanks ; regards,
> 
>  Henk Penning
> 
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/