Re: [VOTE] Accept EventMesh into Apache Incubator
+1 ( binding) -Vinay On Fri, 12 Feb 2021 at 2:21 AM, Dave Fisher wrote: > +1 (binding) > > All The Best, > Dave > > > On Jan 31, 2021, at 10:43 PM, Eason Chen > wrote: > > > > Hi, > > > > After the discussion of EventMesh proposal (discussion thread is > here[1]), > > I would like to call a VOTE to accept it into the Apache Incubator. > > > > Please cast your vote: > > > > [ ] +1, bring EventMesh into Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring EventMesh into Incubator, because... > > > > The vote will open at least for 72 hours and only votes from the > Incubator > > PMC are binding. > > > > The project's proposal is available at [2]. > > > > [1] > > > https://lists.apache.org/thread.html/rcb4bc1e5b4994d377aba4191737ff7c1f7e375fb9044cfbebe236e95%40%3Cgeneral.incubator.apache.org%3E > > [2] > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- -Vinay
Re: [VOTE] Accept EventMesh into Apache Incubator
+1 (binding) All The Best, Dave > On Jan 31, 2021, at 10:43 PM, Eason Chen wrote: > > Hi, > > After the discussion of EventMesh proposal (discussion thread is here[1]), > I would like to call a VOTE to accept it into the Apache Incubator. > > Please cast your vote: > > [ ] +1, bring EventMesh into Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring EventMesh into Incubator, because... > > The vote will open at least for 72 hours and only votes from the Incubator > PMC are binding. > > The project's proposal is available at [2]. > > [1] > https://lists.apache.org/thread.html/rcb4bc1e5b4994d377aba4191737ff7c1f7e375fb9044cfbebe236e95%40%3Cgeneral.incubator.apache.org%3E > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Hi - PODLINGNAMESEARCH-189 for EventMesh has been approved. Regards, Dave > On Feb 2, 2021, at 1:33 AM, Eason Chen wrote: > > Hi, > > "*On one hand we don’t have a policy that say you must have to have done a > name search before becoming a piddling, on the other changing a name does > incur a large community cost and Infra would prefer that podlings don’t > change names. Most podlings do the name search just before graduation. In a > lot of cases it fairly obvious there is not going to be an issue, with a > generic name like this it may be best to wait until the name is approved > before calling the results of the vote.*" > Thanks for Justin's clarification, i also want to add a few words: > > I'm sorry, my words caused unnecessary confusion. I am still following up > on this issue[1]. I must admit that this name is a very serious problem. By > reading Apache’s regulations [2], I found that "*the original Podding > proposal established a working name for the new Podding. During the > election process, there are often discussions and filtering of suitable > names, but the proposed name is not final, just temporary*" > I am tring my best to ensure that it is resolved before the formal > incubation. > > [1]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-188? filter = > -4 = project%20%3D%20PODLINGNAMESEARCH%20order%20by%20created%20DESC > [2]: http://incubator.apache.org/guides/names.html > > > On Tue, Feb 2, 2021 at 5:14 PM Alexander Alten wrote: > >> Hi, >> >> Fully agree with Justin, we from Wayang had the same problem. We >> renamed the project before we submitted the proposal, and we >> documented everything. >> I’d encourage you to find a name which is TM ready in the US, India, >> CN and EU (if possible). You can’t graduate (or better it is unlikely) >> if a project name is not protectable by the ASF. And changing the >> whole INFRA after a podling is voted into the incubator is a huge >> effort. >> >> --alex >> >> On Tue, Feb 2, 2021 at 9:52 AM Justin Mclean >> wrote: >>> >>> Hi, >>> >>> On one hand we don’t have a policy that say you must have to have done a >> name search before becoming a piddling, on the other changing a name does >> incur a large community cost and Infra would prefer that podlings don’t >> change names. Most podlings do the name search just before graduation. In a >> lot of cases it fairly obvious there is not going to be an issue, with a >> generic name like this it may be best to wait until the name is approved >> before calling the results of the vote. >>> >>> 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 >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2
Hi all: I made the following adjustments according to your suggestions: 1. Sorted out and supplemented the LICENSE of each binary dependency package. 2. Delete tubemq-manager and tubemq-web modules related content: In the process of combing, it is found that tubemq-manager contains a dependency package of the GNU GPL V2 LICENSE. This version deletes the module, and then merges it into the official version after finishing the relevant checks for dependency packages. Since more than 60 files of tubemq-web module are not authorized by LICENSE, they will be merged into the mainline version after finishing the LICENSE information checks of the code and dependent packages. 3. Solved the problem of compiling: When compiling with the mvn compile command, the pom dependency of tubemq-docker needs to obtain the dependency package of tubemq from the warehouse instead of locally, so a compilation error occurs; this part should be a pom problem, and solve the problem when the next version is released(does not affect the main line). 4. LICENSE problem of bdb: Through everyone's discussion and confirmation, the 7.3.7 version of berkeleydb-je is authorized under Apache V2 LICENSE, which is explained in detail in the LICENSE file of TubeMQ; subsequent project evolution will consider gradually removing this component. 5. Modify the contents of the CHANGES.md file and add this modification item. Please see if there are any other problems. If OK, we will launch a new round of version release. Thanks! Goson zhang 于2021年2月11日周四 下午2:55写道： > Ok, thanks Daniel! > > > > Daniel Widdis 于2021年2月11日周四 下午2:10写道： > >> To continue to provide clarity: >> >> The current version (7.5.11) still has AL2.0 licensing; I just downloaded >> it to confirm. Any version from 7.3.7 and newer (at this point in time) is >> an acceptable dependency. >> >> If Oracle chooses to change the license again for future releases that >> could pose a problem, but personally I don't think that's likely. >> >> >> On 2/10/21, 9:58 PM, "Goson zhang" wrote: >> >> Yes, restricting the use of its version number in the project is >> still a >> relatively passive solution: if we want to upgrade the version, but >> the >> corresponding version authorization is adjusted, our project still has >> restrictions. >> >> The biggest dependency of replacing this component lies in the >> active/standby switching function: currently we are not considering >> expanding its scope of use, and we are analyzing the new >> active/standby >> switching scheme, and want to temporarily maintain the existing method >> before completing this task, until the real-time active/standby >> switching >> is provided. >> >> I plan to explain this problem in detail in the supplementary binary >> dependency package LICENSE, until the solution is adjusted to >> completely >> solve it. >> >> See if this is OK? >> >> >> Justin Mclean 于2021年2月11日周四 下午1:46写道： >> >> > Hi, >> > >> > > 1. Can we meet the requirements of this open source agreement by >> > > restricting the version of this component to 7.X.Y? >> > > For Berkeley DB JE (Java Edition), this component itself is >> TubeMQ to >> > store >> > > metadata and switch between active and standby. It is not very >> deep, but >> > it >> > > need to take some time to adjust. >> > >> > Possibly if 7.X.Y is clearly Apache licensed, however as time goes >> on you >> > may need to move to a newer version (due to security concerns) and >> what >> > will be become an issue. >> > >> > > 2. Or have to switch to other components? >> > > If so, for this release, do I restore the "WIP" label to >> complete the >> > > version release first? >> > > Then adjust the implementation plan later, and finally remove this >> > > component in the final version. >> > >> > That would be a valid path forward. >> > >> > Thanks, >> > Justin >> >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
Re: [VOTE] Release Apache MXNet (incubating) version 2.0.0.rc2
The Apache Voting Process policy specifies that non-binding votes are only advisory, which would imply they are not included in the count. So my question is addressed. Thanks Leonard On February 11, 2021 10:47:23 AM GMT+01:00, Leonard Lausen wrote: >Hi Justin, > >according to release policy, 'For a release vote to pass, a minimum of three >positive votes and more positive than negative votes MUST be cast. Releases >may not be vetoed. Votes cast by PMC members are binding.' > >There are 3 positive votes including one PPMC vote. Could you provide a >reference to the applicable policy? Or does the formulation of the release >policy need correction? > >Best regards >Leonard > >On February 11, 2021 3:30:34 AM GMT+01:00, Justin Mclean > wrote: >> >>Hi, >> >>-1 (binding) I have not checked dates release but teh vote thread shows only >>one PPMC (and no mentors) vote. Committer votes are not binding on release >>votes. I would suggest you continue with the vote on your dev listuntill you >>have enough PPMC votes and then bright it back here again. >> >>Thanks, >>Justin >>- >>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>For additional commands, e-mail: general-h...@incubator.apache.org >>
Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.3.5
+1 ( binding ) I checked the following. - Incubating in name. - PGP Signatures. - SHA512 Checksums. - DISCLAIMER exists. - LICENSE and NOTICE are fine. - Maven build passes. Regards Kevin On Thu, Feb 11, 2021 at 2:31 PM Furkan KAMACI wrote: > Hi, > > +1 from me (binding). > > I checked: > > - Incubating in name > - DISCLAIMER exists > - LICENSE and NOTICE are fine > - No unexpected binary files > - Checked PGP signatures > - Checked checksums > - Code compiles and tests successfully run > - Apache rat checks are OK > > Kind Regards, > Furkan KAMACI > > On Thu, Feb 11, 2021 at 4:59 AM Sheng Wu > wrote: > > > +1 binding > > > > 1. Compiling passed > > 2. Rat passed > > 3. ASC checked > > 4. sha512 exist. > > 5. LICENSE, NOTICE, and DISCLAIMER exist. > > > > Good luck and happy Chinese New Year. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Kris Calvin 于2021年2月11日周四 上午9:32写道： > > > > > Hello IPMC and DolphinScheduler Community, > > > > > > This is a call for vote to release Apache DolphinScheduler (Incubating) > > > version 1.3.5 > > > > > > We now kindly request the Incubator IPMC members review and vote on > this > > > incubator release. > > > > > > Dolphin Scheduler is a distributed and easy-to-expand visual DAG > workflow > > > scheduling system, > > > dedicated to solving the complex dependencies in data processing, > making > > > the scheduling system out of the box for data processing. > > > > > > DolphinScheduler community vote and result threads: > > > > > > > > > > > > https://lists.apache.org/thread.html/rc63b7590c0cf1c36e5878d8d62ccb9a112e776fe544e4a07eca11bbe%40%3Cdev.dolphinscheduler.apache.org%3E > > > > > > > > > > > > https://lists.apache.org/thread.html/r153bb633f7d7f906386e6f6435a2f3f575f3f883fdec41b3b1904efd%40%3Cdev.dolphinscheduler.apache.org%3E > > > > > > Release changes: > > > https://github.com/apache/incubator-dolphinscheduler/milestone/13 > > > > > > The release candidates: > > > > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/1.3.5 > > > > > > Maven 2 staging repository: > > > > > > > > > https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1052/org/apache/dolphinscheduler/ > > > > > > Git tag for the release: > > > https://github.com/apache/incubator-dolphinscheduler/tree/1.3.5 > > > > > > Release Commit ID: > > > > > > > > > https://github.com/apache/incubator-dolphinscheduler/commit/76e77691f2259c70dd05960e56bae40d5936075e > > > > > > Keys to verify the Release Candidate: > > > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS > > > > > > Look at here for how to verify this release candidate: > > > https://dolphinscheduler.apache.org/en-us/community/release.html > > > > > > 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 > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > > > > [ ] Checksums and PGP signatures are valid. > > > > > > [ ] DISCLAIMER is included. > > > > > > [ ] Source code artifacts have correct names matching the current > > release. > > > > > > [ ] LICENSE and NOTICE files are correct for each DolphinScheduler > repo. > > > > > > [ ] All files have license headers if necessary. > > > > > > [ ] No compiled archives bundled in source archive. > > > > > > More detail checklist please refer: > > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > > > > > > The following votes are carried over from DolphinScheduler dev mailing > > > list: > > > +1 Furkan KAMACI > > > > > > Best wishes！ > > > -- > > > > > > CalvinKirs > > > Committer of Apache DolphinScheduler(Incubator) > > > > > >
Re: [VOTE] Release Apache MXNet (incubating) version 2.0.0.rc2
Hi Justin, according to release policy, 'For a release vote to pass, a minimum of three positive votes and more positive than negative votes MUST be cast. Releases may not be vetoed. Votes cast by PMC members are binding.' There are 3 positive votes including one PPMC vote. Could you provide a reference to the applicable policy? Or does the formulation of the release policy need correction? Best regards Leonard On February 11, 2021 3:30:34 AM GMT+01:00, Justin Mclean wrote: > >Hi, > >-1 (binding) I have not checked dates release but teh vote thread shows only >one PPMC (and no mentors) vote. Committer votes are not binding on release >votes. I would suggest you continue with the vote on your dev listuntill you >have enough PPMC votes and then bright it back here again. > >Thanks, >Justin >- >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.3.5
Hi, +1 from me (binding). I checked: - Incubating in name - DISCLAIMER exists - LICENSE and NOTICE are fine - No unexpected binary files - Checked PGP signatures - Checked checksums - Code compiles and tests successfully run - Apache rat checks are OK Kind Regards, Furkan KAMACI On Thu, Feb 11, 2021 at 4:59 AM Sheng Wu wrote: > +1 binding > > 1. Compiling passed > 2. Rat passed > 3. ASC checked > 4. sha512 exist. > 5. LICENSE, NOTICE, and DISCLAIMER exist. > > Good luck and happy Chinese New Year. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Kris Calvin 于2021年2月11日周四 上午9:32写道： > > > Hello IPMC and DolphinScheduler Community, > > > > This is a call for vote to release Apache DolphinScheduler (Incubating) > > version 1.3.5 > > > > We now kindly request the Incubator IPMC members review and vote on this > > incubator release. > > > > Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow > > scheduling system, > > dedicated to solving the complex dependencies in data processing, making > > the scheduling system out of the box for data processing. > > > > DolphinScheduler community vote and result threads: > > > > > > > https://lists.apache.org/thread.html/rc63b7590c0cf1c36e5878d8d62ccb9a112e776fe544e4a07eca11bbe%40%3Cdev.dolphinscheduler.apache.org%3E > > > > > > > https://lists.apache.org/thread.html/r153bb633f7d7f906386e6f6435a2f3f575f3f883fdec41b3b1904efd%40%3Cdev.dolphinscheduler.apache.org%3E > > > > Release changes: > > https://github.com/apache/incubator-dolphinscheduler/milestone/13 > > > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/1.3.5 > > > > Maven 2 staging repository: > > > > > https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1052/org/apache/dolphinscheduler/ > > > > Git tag for the release: > > https://github.com/apache/incubator-dolphinscheduler/tree/1.3.5 > > > > Release Commit ID: > > > > > https://github.com/apache/incubator-dolphinscheduler/commit/76e77691f2259c70dd05960e56bae40d5936075e > > > > Keys to verify the Release Candidate: > > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS > > > > Look at here for how to verify this release candidate: > > https://dolphinscheduler.apache.org/en-us/community/release.html > > > > 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 > > > > Checklist for reference: > > > > [ ] Download links are valid. > > > > [ ] Checksums and PGP signatures are valid. > > > > [ ] DISCLAIMER is included. > > > > [ ] Source code artifacts have correct names matching the current > release. > > > > [ ] LICENSE and NOTICE files are correct for each DolphinScheduler repo. > > > > [ ] All files have license headers if necessary. > > > > [ ] No compiled archives bundled in source archive. > > > > More detail checklist please refer: > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > > > The following votes are carried over from DolphinScheduler dev mailing > > list: > > +1 Furkan KAMACI > > > > Best wishes！ > > -- > > > > CalvinKirs > > Committer of Apache DolphinScheduler(Incubator) > > >
