Re: Meritocracy, initial contributors and (Incubator) Proposals
Hi, > For straight-to-TLP projects, like your Training proposal, I think the > initial PMC should consist only of Apache Members. While that seem like a good idea it’s not been the case with all PMC members on previous TLP. It’s really up to the board to decide if they accept a straight to TLP our not. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache ECharts 4.2.1 (release candidate 1)
I am pleased to be calling this vote for the release of Apache ECharts 4.2.1 (release candidate 1). Apache ECharts community has voted and approved the release. Vote thread: https://lists.apache.org/thread.html/30a097ec4cc086e91ee3dee2b6b10ae53da76fee7115dd263ea0120d@%3Cdev.echarts.apache.org%3E Results thread: https://lists.apache.org/thread.html/8c9c2b1a464acc6aa353ac6429075cf3c864ed518d66bf04f36e71ed@%3Cdev.echarts.apache.org%3E The release candidate to be voted over is available at: https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.1/ The release candidate is signed with a GPG key available at: https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS The Git commit for this release is: https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=9234f03 The Release Note is available in: https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.1/RELEASE_NOTE.txt Some shell commands for validating the release: ```shell # Download the release: curl https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.1/apache-echarts-4.2.1-rc.1-incubating-src.zip -o apache-echarts-4.2.1-rc.1-incubating-src.zip unzip apache-echarts-4.2.1-rc.1-incubating-src.zip -d apache-echarts-4.2.1-rc.1-incubating-src > /dev/null # Rebuild the project (Node.js environment is required): cd "apache-echarts-4.2.1-rc.1-incubating-src" && npm install && cd .. node "apache-echarts-4.2.1-rc.1-incubating-src/build/build.js" --release # (See help: `node "apache-echarts-4.2.1-rc.1-incubating-src/build/build.js" --help`) ``` Please vote on releasing this package as: Apache ECharts 4.2.1 (release candidate 1) by "2019-02-01T07:39:41.921Z". [ ] +1 Release this package [ ] 0 I don't feel strongly about it, but don't object [ ] -1 Do not release this package because... Anyone can participate in testing and voting, not just committers, please feel free to try out the release candidate and provide your votes. -- Zhang Wenli http://zhangwenli.com
Re: [VOTE] Release Apache Dubbo (Incubating) 2.7.0 [RC2]
+1. Checked the github tag with the source code. Checked the signed key and can build from the source. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Jan 24, 2019 at 10:28 PM Huxing Zhang wrote: > > Hello Incubator Community, > > The Apache Dubbo community has voted on and approved a proposal to release > Apache Dubbo (Incubating) version 2.7.0. > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > Apache Dubbo™ (incubating) is a high-performance, java based, open source > RPC framework. Dubbo offers three key functionalities, which include > interface based remote call, fault tolerance & load balancing, and > automatic service registration & discovery. > > Dubbo community vote and result thread: > https://lists.apache.org/thread.html/60b3ef868d8acd127c18584968d98dd6191c41dd3a426f98703f68f6@%3Cdev.dubbo.apache.org%3E > > The release candidates (RC2): > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.7.0 > > The staging repo: > https://repository.apache.org/content/repositories/orgapachedubbo-1005 > > Git tag for the release (RC2): > https://github.com/apache/incubator-dubbo/tree/dubbo-2.7.0 > > Hash for the release tag: > 614bcebc01336ee5047a98f96b28915680c0399c > > Release Notes: > https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md > > The artifacts have been signed with Key : > AF1B3C2AC648B9E8C9AC6F26CD69F886A620E8EC, which can be > found in the keys file: > https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > The Apache Dubbo (Incubating) Team > > - > 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 Dubbo (Incubating) 2.7.0 [RC2]
Hi community, Dubbo 2.7.0 RC2 is still waiting for 1 more binding vote to get it passed. Would you please help to review and vote for the candidate? Any help is greatly appreciated! On Thu, Jan 24, 2019 at 10:28 PM Huxing Zhang wrote: > > Hello Incubator Community, > > The Apache Dubbo community has voted on and approved a proposal to release > Apache Dubbo (Incubating) version 2.7.0. > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > Apache Dubbo™ (incubating) is a high-performance, java based, open source > RPC framework. Dubbo offers three key functionalities, which include > interface based remote call, fault tolerance & load balancing, and > automatic service registration & discovery. > > Dubbo community vote and result thread: > https://lists.apache.org/thread.html/60b3ef868d8acd127c18584968d98dd6191c41dd3a426f98703f68f6@%3Cdev.dubbo.apache.org%3E > > The release candidates (RC2): > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.7.0 > > The staging repo: > https://repository.apache.org/content/repositories/orgapachedubbo-1005 > > Git tag for the release (RC2): > https://github.com/apache/incubator-dubbo/tree/dubbo-2.7.0 > > Hash for the release tag: > 614bcebc01336ee5047a98f96b28915680c0399c > > Release Notes: > https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md > > The artifacts have been signed with Key : > AF1B3C2AC648B9E8C9AC6F26CD69F886A620E8EC, which can be > found in the keys file: > https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > The Apache Dubbo (Incubating) Team -- Best Regards！ Huxing - 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 6.0.0-GA
+1 I checked : + the signature + the sha512 + the license + compiled successfully Thanks, William On Mon, Jan 28, 2019 at 10:46 PM Willem Jiang wrote: > Carrying my +1 vote in the dev@skywalking.a.o here. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sat, Jan 26, 2019 at 4:49 PM 吴晟 Sheng Wu wrote: > > > > Hi All, > > This is a call for vote to release Apache SkyWalking (Incubating) > version 6.0.0-GA. > > > > > > The Apache SkyWalking community has tested, voted and approved the > proposed > > release of Apache SkyWalking (Incubating) 6.0.0-GA > > > > > > We now kindly request the Incubator PMC members review and vote on this > > incubator release. > > > > > > SkyWalking: APM (application performance monitor) tool for distributed > systems, > > especially designed for microservices, cloud native and container-based > (Docker, Kubernetes, Mesos) architectures. > > Underlying technology is a distributed tracing system. > > > > > > Vote Thread: > >* > https://lists.apache.org/thread.html/5ee4634d3cc72449082f527952ab5b135cb0d171f2eb3bfa2caf664f@%3Cdev.skywalking.apache.org%3E > > > > > > Release notes: > > > > > > > > > >* > https://github.com/apache/incubator-skywalking/blob/master/CHANGES.md#600-ga > > > > > > > > > > Release Candidate: > > > > > > > > > >* > https://dist.apache.org/repos/dist/dev/incubator/skywalking/6.0.0-GA/ > >* sha512 checksums > > - > 6e07c174a0473af245c05869e485a4ddc1f4b7b1ba1d55c65b81d5ed37041f632985f6c5d3e13773fc5940917b71940131580b4f9fbd1853521e906c7b60f11d > apache-skywalking-apm-incubating-6.0.0-GA-src.tgz > > - > a19a24b790f41b1d7f93547104fbfc70a1dc208d855026b0c4696d1991518a952d031b62a76bfa923394042757dc92aa87e6cac6502d015f30258e9959e393bf > apache-skywalking-apm-incubating-6.0.0-GA.tar.gz > > - > 4f0bff2bf2edb207f9b209abdc8c5433d3f7a0f1f24d515344204dac6a3a4aa2e2ebb9354f3725e75b47e7d3bee52e0a9a454136b410df29034db0d478b60164 > apache-skywalking-apm-incubating-6.0.0-GA.zip > > > > > > > > > > Maven 2 staging repository: > > > > > > > > > >* > https://repository.apache.org/content/repositories/orgapacheskywalking-1028/org/apache/skywalking > > > > > > > > > > Release Tag : > > > > > > > > > >* (Git Tag) v6.0.0-GA > > > > > > > > > > Release CommitID : > > > > > > > > > >* > https://github.com/apache/incubator-skywalking/tree/8b638258bb9ae9d512f946b5622fb65948a937e8 > >* Git submodule > > * skywalking-ui: > https://github.com/apache/incubator-skywalking-ui/tree/c44642f73b9f73a54b0d716cade5094304e1a67b > > * apm-protocol/apm-network/src/main/proto: > https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/b66fa070fd647662f06497e4ed3657eb258cb6e9 > > * > oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol > > https://github.com/apache/incubator-skywalking-query-protocol/tree/c65a23bd6b9bba8d1df30d4de261624952df2b7b > > > > > > > > > > Keys to verify the Release Candidate : > > > > > > > > > >* > https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS > corresponding to wush...@apache.org > > > > > > > > > > Guide to build the release from source : > > > > > > > > > >* > https://github.com/apache/incubator-skywalking/blob/v6.0.0-GA/docs/en/guides/How-to-build.md > >* docs/en/guides/How-to-build.md in source tar. > > > > > > Voting will start now (Jan. 26th 2019) and will remain open for at > least 72 hours, Request IPMC to give their vote. > >[ ] +1 Release this package. > >[ ] +0 No opinion. > >[ ] -1 Do not release this package because > > > > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > - > 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 6.0.0-GA
Carrying my +1 vote in the dev@skywalking.a.o here. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, Jan 26, 2019 at 4:49 PM 吴晟 Sheng Wu wrote: > > Hi All, > This is a call for vote to release Apache SkyWalking (Incubating) version > 6.0.0-GA. > > > The Apache SkyWalking community has tested, voted and approved the proposed > release of Apache SkyWalking (Incubating) 6.0.0-GA > > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > > SkyWalking: APM (application performance monitor) tool for distributed > systems, > especially designed for microservices, cloud native and container-based > (Docker, Kubernetes, Mesos) architectures. > Underlying technology is a distributed tracing system. > > > Vote Thread: >* > https://lists.apache.org/thread.html/5ee4634d3cc72449082f527952ab5b135cb0d171f2eb3bfa2caf664f@%3Cdev.skywalking.apache.org%3E > > > Release notes: > > > > >* > https://github.com/apache/incubator-skywalking/blob/master/CHANGES.md#600-ga > > > > > Release Candidate: > > > > >* https://dist.apache.org/repos/dist/dev/incubator/skywalking/6.0.0-GA/ >* sha512 checksums > - > 6e07c174a0473af245c05869e485a4ddc1f4b7b1ba1d55c65b81d5ed37041f632985f6c5d3e13773fc5940917b71940131580b4f9fbd1853521e906c7b60f11d > apache-skywalking-apm-incubating-6.0.0-GA-src.tgz > - > a19a24b790f41b1d7f93547104fbfc70a1dc208d855026b0c4696d1991518a952d031b62a76bfa923394042757dc92aa87e6cac6502d015f30258e9959e393bf > apache-skywalking-apm-incubating-6.0.0-GA.tar.gz > - > 4f0bff2bf2edb207f9b209abdc8c5433d3f7a0f1f24d515344204dac6a3a4aa2e2ebb9354f3725e75b47e7d3bee52e0a9a454136b410df29034db0d478b60164 > apache-skywalking-apm-incubating-6.0.0-GA.zip > > > > > Maven 2 staging repository: > > > > >* > https://repository.apache.org/content/repositories/orgapacheskywalking-1028/org/apache/skywalking > > > > > Release Tag : > > > > >* (Git Tag) v6.0.0-GA > > > > > Release CommitID : > > > > >* > https://github.com/apache/incubator-skywalking/tree/8b638258bb9ae9d512f946b5622fb65948a937e8 >* Git submodule > * skywalking-ui: > https://github.com/apache/incubator-skywalking-ui/tree/c44642f73b9f73a54b0d716cade5094304e1a67b > * apm-protocol/apm-network/src/main/proto: > https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/b66fa070fd647662f06497e4ed3657eb258cb6e9 > * > oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol > > https://github.com/apache/incubator-skywalking-query-protocol/tree/c65a23bd6b9bba8d1df30d4de261624952df2b7b > > > > > Keys to verify the Release Candidate : > > > > >* https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS > corresponding to wush...@apache.org > > > > > Guide to build the release from source : > > > > >* > https://github.com/apache/incubator-skywalking/blob/v6.0.0-GA/docs/en/guides/How-to-build.md >* docs/en/guides/How-to-build.md in source tar. > > > Voting will start now (Jan. 26th 2019) and will remain open for at least 72 > hours, Request IPMC to give their vote. >[ ] +1 Release this package. >[ ] +0 No opinion. >[ ] -1 Do not release this package because > > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Training (incubating) Proposal
I've been going back and forth on the topic of TLP vs. Incubator podling. I don't really have a strong opinion but I'm leaning slightly in favor of "straight to TLP" and the past discussion (linked in previous mail) did also have more voices in favor of TLP. But of course there are arguments to be made for both sides. I've been wondering if anyone here has opinions on this part of the proposal? In a related thread I asked about how to proceed in terms of choosing members for a PMC and one suggestion was to make it depend on the route: * Incubator: On graduation ask and assess current PMC members and see if everyone has proven their merit and is willing to continue * TLP: Start with a PMC consisting of only ASF members (plus additional committers) and then accept additional members for the PMC on a "normal" basis Cheers, Lars On Fri, Jan 25, 2019 at 1:49 PM Lars Francke wrote: > Hello everyone, > > this is the result of the discussion I started in December 2018[1]. > > I would like to start this thread to get feedback on a proposal we've been > working on for a project focused on developing training material for Apache > & 3rd party projects. > > The full proposal can be found here < > https://wiki.apache.org/incubator/TrainingProposal> > > Disclaimer: It is a bit different than most other proposals as it > basically starts at zero. > > Our main goals for this discussion are: > * Finding mentors and interested contributors > * Discuss whether this should be a Incubator project, straight to TLP or a > Central Service > * Sharpen the scope of the project > > While I personally have a relatively long history as a contributor, > committer etc. at Apache I've never been a mentor before so we would love > for some experienced people to help us out. > > We're looking forward to all kinds of feedback. > > Cheers, > Lars > > [1] < > https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E > > >
Re: Meritocracy, initial contributors and (Incubator) Proposals
Thanks for the feedback everyone. The general outline makes sense to me and it is reassuring that I didn't miss anything too obvious. I'll wait to see if a discussion is going to develop on the exact form this is going to happen in. Cheers, Lars On Mon, Jan 28, 2019 at 11:14 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > Hi Lars, > > On Sat, Jan 26, 2019 at 5:35 PM Lars Francke > wrote: > > ...Proposals (and this especially) are a way to be granted something > that you > > usually have to work for (prove merit) > > I agree that being listed as an initial committer on podling proposals > is a way to get committership without necessarily demonstrating merit > in the ASF. > > And that might lead people to becoming PMC members once their podling > graduate. > > In podlings what I've been mentoring I have often asked for the list > of PMC members to be reviewed before graduation, to verify that those > people have earned their role by providing value to the podling. I > think that's a good filter to avoid the problem the you mention. > > For straight-to-TLP projects, like your Training proposal, I think the > initial PMC should consist only of Apache Members. We haven't had many > of those so far so I don't think we have a rule for that but that > seems reasonable, as there's no guidance outside of the PMC for a > straight-toTLP project. > > Once the project is created the PMC can elect committers as quickly as > it wants, and decide who can also join the PMC. > > I think saying "The initial PMC of a straight-to-TLP project consists > of Apache Members only" gives you a simple rule to accept candidates, > is reassuring for the Board when it accepts creating the project and > doesn't block quick project growth in any way. I recommend using that > rule for your Training project if it aims to go straight to TLP. > > Interested people can still be listed somewhere but the best way for > them to demonstrate interest is to join the project's lists once > created. > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Training (incubating) Proposal
Sharan, great! I've added you to the Wiki. Cheers, Lars On Sun, Jan 27, 2019 at 10:51 PM Sharan Foga wrote: > Hi Lars > > I'd like to be a part of this, not only from a ComDev perspective, as this > project and its resources would be a great asset for the community > development effort (internally and externally), but also because I have an > real interest in developing documentation and training material. > > So I'd be happy to be involved. > > Thanks > Sharan > > On 2019/01/25 12:49:01, Lars Francke wrote: > > Hello everyone, > > > > this is the result of the discussion I started in December 2018[1]. > > > > I would like to start this thread to get feedback on a proposal we've > been > > working on for a project focused on developing training material for > Apache > > & 3rd party projects. > > > > The full proposal can be found here < > > https://wiki.apache.org/incubator/TrainingProposal> > > > > Disclaimer: It is a bit different than most other proposals as it > basically > > starts at zero. > > > > Our main goals for this discussion are: > > * Finding mentors and interested contributors > > * Discuss whether this should be a Incubator project, straight to TLP or > a > > Central Service > > * Sharpen the scope of the project > > > > While I personally have a relatively long history as a contributor, > > committer etc. at Apache I've never been a mentor before so we would love > > for some experienced people to help us out. > > > > We're looking forward to all kinds of feedback. > > > > Cheers, > > Lars > > > > [1] < > > > https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Meritocracy, initial contributors and (Incubator) Proposals
Hi Lars, On Sat, Jan 26, 2019 at 5:35 PM Lars Francke wrote: > ...Proposals (and this especially) are a way to be granted something that you > usually have to work for (prove merit) I agree that being listed as an initial committer on podling proposals is a way to get committership without necessarily demonstrating merit in the ASF. And that might lead people to becoming PMC members once their podling graduate. In podlings what I've been mentoring I have often asked for the list of PMC members to be reviewed before graduation, to verify that those people have earned their role by providing value to the podling. I think that's a good filter to avoid the problem the you mention. For straight-to-TLP projects, like your Training proposal, I think the initial PMC should consist only of Apache Members. We haven't had many of those so far so I don't think we have a rule for that but that seems reasonable, as there's no guidance outside of the PMC for a straight-toTLP project. Once the project is created the PMC can elect committers as quickly as it wants, and decide who can also join the PMC. I think saying "The initial PMC of a straight-to-TLP project consists of Apache Members only" gives you a simple rule to accept candidates, is reassuring for the Board when it accepts creating the project and doesn't block quick project growth in any way. I recommend using that rule for your Training project if it aims to go straight to TLP. Interested people can still be listed somewhere but the best way for them to demonstrate interest is to join the project's lists once created. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
