Re: [VOTE] Accept EventMesh into Apache Incubator
+1(non-binding) Good luck! Best, tison. ShannonDing 于2021年2月2日周二 上午9:58写道： > +1， > > > Thanks, > ShannonDing > On 02/1/2021 14:43，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 >
Re: [DISCUSS] Graduate Apache DolphinScheduler (incubating) as a TLP
+1 Many times I recommend to my friends that DolphinScheduler is a passionate, rapidly growing, and friendly community. Glad to see it's moving to graduate! Happy new year! Best, tison. Ming Wen 于2021年2月6日周六 上午8:33写道： > +1 binding > > Congratulations, the community has grown very well > > Paul King 于2021年2月6日 周六上午7:08写道： > > > +1 (binding) > > > > Cheers, Paul. > > > > On Fri, Feb 5, 2021 at 9:36 PM Gang Li wrote: > > > > > Hi all, > > > After discussion with the community [1] and [2], and a positive vote > > > result [3]. > > > We'd like to bring this to a discussing at the IPMC. > > > > > > Please see the proposed resolution below and let us know what do you > > think. > > > > > > A few status to help with the discussion: > > > > > > - Released 8 Apache releases, through 5 different release managers > > > - Invited 14 new committers (all accepted) > > > - Invited 2 new PPMC members (all accepted) > > > - Apache DolphinScheduler name search has been approved [4] > > > - Finished the Podling Maturity Assessment for DolphinScheduler [5], > all > > > items are passed > > > - There are 169 contributors for now > > > - There are 1904 emails sent by 197 people in dev mailing-list excepted > > > GitBox forwarded > > > - Resolved 1500+ issues and 2000+ pull requests during ASF incubating > > > > > > We've resolved all branding issues which include Logo, GitHub repo, > > > document, website and others. > > > > > > [1] > > > > > > https://lists.apache.org/thread.html/rbef0779035c61d02ef9fa63e55175fd5896fc513258d1b2537b51604%40%3Cdev.dolphinscheduler.apache.org%3E > > > [2] > > > > > > https://lists.apache.org/thread.html/r79381a3fd38d112b5ccb0be67675547e187497135853b0fe999f813a%40%3Cdev.dolphinscheduler.apache.org%3E > > > [3] > > > > > > https://lists.apache.org/thread.html/raa78e55fc511b479cae1c4faefb8ae2cb31b4fb9143a1a958ac577f0%40%3Cdev.dolphinscheduler.apache.org%3E > > > [4] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-186 > > > [5] > > > > > > https://cwiki.apache.org/confluence/display/DOLPHINSCHEDULER/Podling+Maturity+Assessment+for+DolphinScheduler > > > > > > > - > > > > > > Establish the Apache DolphinScheduler Project > > > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > > the Foundation and consistent with the Foundation's purpose to > establish > > > a Project Management Committee charged with the creation and > maintenance > > > of open-source software, for distribution at no charge to the public, > > > related to a distributed and extensible workflow scheduler platform > with > > > powerful DAG visual interfaces. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > (PMC), to be known as the "Apache DolphinScheduler Project", be and > > > hereby is established pursuant to Bylaws of the Foundation; and be it > > > further > > > > > > RESOLVED, that the Apache DolphinScheduler Project be and hereby is > > > responsible for the creation and maintenance of software related to a > > > distributed and extensible workflow scheduler platform with powerful > DAG > > > visual interfaces.; and be it further > > > > > > RESOLVED, that the office of "Vice President, Apache DolphinScheduler" > > > 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 > > > DolphinScheduler Project, and to have primary responsibility for > > > management of the projects within the scope of responsibility of the > > > Apache DolphinScheduler 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 > DolphinScheduler > > > Project: > > > > > > * Furkan Kamaci > > > * Gang Li > > > * Guo Jiwei > > > * Guo William > > > * Jun Gao > > > * Kevin Ratnasekera > > > * Leon Bao > > > * Liang Chen > > > * Lidong Dai > > > * Qiao Zhanwei > > > * Shao Feng Shi > > >
Re: subscibe
I guess you should send to the -subscribe address instead. Best, tison. Aloys Zhang 于2021年9月8日周三 下午7:22写道： > subscribe > -- > Best, > Aloys. >
Re: [RESULT] [VOTE] Release Apache InLong(Incubating) 0.11.0-incubating Candidate 0
Congrats! Best, tison. Aloys Zhang 于2021年11月4日周四 下午7:29写道： > Hi all, > Thanks for reviewing and voting for Apache InLong(Incubating) > 0.11.0-incubating RC0 release. > The vote has passed with 3 +1 binding votes, no +0 or -1 votes. > Binding votes are from IPMC > >- Xun Liu >- Justin Mclean >- Jean-Baptiste Onofre > > The voting thread is: > https://lists.apache.org/thread/xv90mynkppsoy6hz2ngyms4g8qy2v2t9 > > Many thanks for all our mentors helping us with the release procedure and > all IPMC helped us to review and vote for Apache InLong(Incubating) > release. > We will proceed with publishing the approved artifacts and sending out the > announcements in the coming days. > > Thanks > On behalf of Apache InLong(Incubating) community > -- > Best, > Aloys. >
Re: Chunjun Proposal
Hi, I have two questions here: 1. How should I name you in this thread? Apache is a community of peers. I can't image I'm talking to the whole Chunjun community or "Apache" expect its your name. 2. What's your expectations on going into the incubator? Among the whole proposal it's almost about what the current state of Chunjun and the only statement about your expectations is: > we seek to further prosper the community with the aid of Apache Could you elaborate a bit the motivation here? What help are you seeking? Also I second to Sheng's comment that it's confused about your expressions of contributors and initial committers. If your community continuously promote contributors , why the initial committer list is quite a bit limited? Best, tison. Sheng Wu 于2022年2月22日周二 20:54写道： > I think this description is incorrect. > > > Our initial committers will submit iCLA(s), SGA, and CCLA(s). > > Committers are individuals, who should only submit ICLA, their > employers are recommended to submit CCLA, the owner of the project > should sign the SGA. > ___ > > Also, I noticed a conflict in your description > On one side, you mentioned `The initial committers are employees of > DTStack.` with only 5 initial committers, and on the other hand, you > gave a very long vendor list and core contributors list. > So, which is an accurate description? If you have those contributors, > why were all of them invited as PPMC members? Do you have any public > discussion about this decision? > Such as GitHub ID(demotto) is the #8 in the contributor list, and also > listed in the core contributor list, but can't find it in the initial > committer list. > > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > Lidong Dai 于2022年2月22日周二 20:41写道： > > > > I am curious that Chunjun(was Flinkx) is built on the Flink CDC, so what > is > > its innovation? > > > > BTW, you shouldn't use the mail(apa...@dtstack.com) as your user > account, > > apache is a registered trademark of ASF > > > > > > > > Best Regards > > > > > > > > --- > > Apache DolphinScheduler PMC Chair > > Lidong Dai > > lidong...@apache.org > > Linkedin: https://www.linkedin.com/in/dailidong > > Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy> > > > > --- > > > > > > On Tue, Feb 22, 2022 at 3:10 PM Jean-Baptiste Onofré > > wrote: > > > > > By the way, if you need a mentor, you can ping me. > > > > > > Regards > > > JB > > > > > > On Tue, Feb 22, 2022 at 8:08 AM Jean-Baptiste Onofré > > > wrote: > > > > > > > > Hi, > > > > > > > > It looks interesting. Quick questions about the current state of the > > > > project/roadmap: how the users implement the ETL pipeline ? Is it > > > > using a kind of SDK/DSL or do you plan an UI ? > > > > Is it very coupled to Flink or the runtime is "pluggable" ? Do you > > > > plan to have some kind of optional storage, similar to Apache Druid, > > > > ... ? > > > > > > > > Regards > > > > JB > > > > > > > > On Tue, Feb 22, 2022 at 7:41 AM Apache wrote: > > > > > > > > > > > > > > > Dear Apache Incubator Community, > > > > > We propose to contribute Chunjun as an Apache Incubator project. > > > > > We are still looking for possible Champion and Mentors if anyone > would > > > like to volunteer. Thanks a lot. > > > > > Best Regards, > > > > > Real-time computing engine team of DTStack. > > > > > > > > > > #Chunjun Proposal > > > > > > > > > > ##Abstract > > > > > Chunjun is a distributed ETL tool and distributed data integration > > > tool. Currently Chunjun is based on Apache Flink. It was initially > known as > > > FlinkX and renamed Chunjun on February 22, 2022. > > > > > - Chunjun codebase: https://github.com/DTStack/chunjun > > > > > > > > > > ##Proposal > > > > > We propose to contribute the Chunjun codebase to the Apache > Software > > > Foundation with the intent of forming a productive, meritocratic and > open > > > community around Chunjun’s continued development, according to the > 'Apache > > > Way'. The Chunjun's source code is already under the Apache License > Version > > > 2.0. > > > > > > > > > > ##Backgroun
Re: [DISCUSSION] Incubating proposal of Kvrocks
+1 I learned Kvrocks for a few months ago and read their previous report like this one[1]. I believe its people can be good citizens of the Apache community. Two coins from my side: 1. The proposal writes that Kvrocks aims to become a distributed multi-model NoSQL database. My personal feeling is that it's often stability and efficiency instead of more features users adopt a software or solution. I'd suggest you guys to connect to the wide ecosystem and to bring more user cases instead of becoming a software to do everything. 2. The proposal writs: > If Kvrocks accepted for incubation, the primary initial goal is to build a large community. > We really trust that Kvrocks will become a good NoSQL database, we hope to grow the > base of contributors by inviting all those who offer contributions through The Apache Way. I don't get it well and want to see more elaborations. For example, you cannot grow contributors "by inviting all those who offer contributions", which sounds like we grow contributors when they are contributors. If you can write down some contributor stories, real or unreal, it will shape your thoughts. 3. The proposal wants to run this podling with 5 IPMCs, but about a week after the proposal submitted, only the champion and one mentor participant the thread. Are other mentors be aware of this proposal? Anyway, it would be nice to accept Kvrocks to the incubator and we can build a healthy and storage community. Best, tison. [1] https://mp.weixin.qq.com/s/FhVjCq8jSk7atWpnR9Xrsg Xiaoqiao He 于2022年4月10日周日 22:42写道： > +1. > > Thanks for starting this thread, Liang! > > I'm very glad to be the mentor of this project. I've connected with > the core team online several times, and was attracted by their > contributions, collaborations and willingness. > Hope this project could be accepted by the incubator, and push forward > healthily to build up a better community! > > Best Regards, > - He Xiaoqiao > > On Sat, Apr 9, 2022 at 4:18 PM Liang Chen wrote: > > > > Hi all > > > > We would like to propose Kvrocks [1] as a new apache incubator project, > you > > can find the proposal [2] of Kvrocks for more detail. > > > > Kvrocks is a distributed key-value NoSQL database, supporting the rich > data > > structure and be widely used by many internet business for example, the > > recommendation service can use hashes to store user characteristics and > the > > sorted set to sort them. For supporting more users, Kvrocks also have > good > > integration and ecosystem compatibility with other NoSQL database API and > > script. > > In comparison to current open source NoSQL database like Redis, which > also > > has rich data structure, Kvrocks data be stored in disk storage, but the > > redis data be stored in memory, it means the cost is higher and the > > capacity is limited when compare to disk storage solution, this is why we > > created Kvrocks project to solve the cost and capacity issues by using > disk > > storage solution, the following are key features of Kvrocks: > > > >- Compatibly support Redis protocol and data structures > >(String/List/Hash/Set/Sorted-set/Bitmap/GEO/Sorted-Int) > >- Disk-Based, all data and updates always persist on the disk > >- Proxyless centralized cluster > >- Stored procedures based on Lua script > >- Transaction(no strict ACID) > >- Publish-Subscribe > >- Tunable consistency(In-Progress) > > > > > > Kvrocks was designed to decrease the cost of memory and increase the > > capacity while compared to Redis. Also, Kvrocks aims to become a > > distributed multi-model NoSQL database in the future. We will provide > more > > features to expand its usage scenarios but all data structures on disk. > > Kvrocks is fully compatible with Redis in term of protocol. > > > > We believe that the Kvrocks project will provide the diversity value for > > community if Kvrocks is introduced into the Apache incubator. > > > > > > I will help this project as champion and many thanks to 4 mentors : > > Jean-Baptiste > > Onofre [jbono...@apache.org], Xiaoqiao He [hexiaoq...@apache.org], Xun > Liu[ > > liu...@apache.org], Von Gosling[vongosl...@apache.org]. > > > > > > [1] https://github.com/KvrocksLabs/kvrocks > > > > [2] > https://cwiki.apache.org/confluence/display/INCUBATOR/KvrocksProposal > > > > > > Regards > > > > Liang > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSSION] Incubating proposal of Kvrocks
@hulk Thanks for your reply! That sounds good to me. Learned from @Liang Chen I've submitted an application[1] for being an IPMC member and willing to be a mentor of this proposed podling. Looking forward to further cooperation. Best, tison. [1] https://lists.apache.org/thread/h0d7rxhzzmnbspzsmjocwng3cd2mzg5l hulk 于2022年4月15日周五 18:18写道： > Thanks for your comment. We will update the Kvrocks proposal accordingly to > it. > > For multi-model, we also agree that we should not become a software to do > everything. > We would mainly focus on data structures that are frequently used and fit > the underlying storage. > > On Fri, Apr 15, 2022 at 11:28 AM tison wrote: > > > +1 > > > > I learned Kvrocks for a few months ago and read their previous report > like > > this one[1]. I believe its people can be good citizens of the Apache > > community. > > > > Two coins from my side: > > > > 1. The proposal writes that Kvrocks aims to become a distributed > > multi-model > > NoSQL database. My personal feeling is that it's often stability and > > efficiency > > instead of more features users adopt a software or solution. I'd suggest > > you > > guys to connect to the wide ecosystem and to bring more user cases > instead > > of becoming a software to do everything. > > > > 2. The proposal writs: > > > > > If Kvrocks accepted for incubation, the primary initial goal is to > build > > a large community. > > > We really trust that Kvrocks will become a good NoSQL database, we hope > > to grow the > > > base of contributors by inviting all those who offer contributions > > through The Apache Way. > > > > I don't get it well and want to see more elaborations. For example, you > > cannot grow contributors > > "by inviting all those who offer contributions", which sounds like we > grow > > contributors when they > > are contributors. If you can write down some contributor stories, real > > or unreal, it will shape your > > thoughts. > > > > 3. The proposal wants to run this podling with 5 IPMCs, but about a week > > after the proposal > > submitted, only the champion and one mentor participant the thread. Are > > other mentors be aware > > of this proposal? > > > > Anyway, it would be nice to accept Kvrocks to the incubator and we can > > build > > a healthy and storage community. > > > > Best, > > tison. > > > > [1] https://mp.weixin.qq.com/s/FhVjCq8jSk7atWpnR9Xrsg > > > > > > Xiaoqiao He 于2022年4月10日周日 22:42写道： > > > > > +1. > > > > > > Thanks for starting this thread, Liang! > > > > > > I'm very glad to be the mentor of this project. I've connected with > > > the core team online several times, and was attracted by their > > > contributions, collaborations and willingness. > > > Hope this project could be accepted by the incubator, and push forward > > > healthily to build up a better community! > > > > > > Best Regards, > > > - He Xiaoqiao > > > > > > On Sat, Apr 9, 2022 at 4:18 PM Liang Chen > > wrote: > > > > > > > > Hi all > > > > > > > > We would like to propose Kvrocks [1] as a new apache incubator > project, > > > you > > > > can find the proposal [2] of Kvrocks for more detail. > > > > > > > > Kvrocks is a distributed key-value NoSQL database, supporting the > rich > > > data > > > > structure and be widely used by many internet business for example, > the > > > > recommendation service can use hashes to store user characteristics > and > > > the > > > > sorted set to sort them. For supporting more users, Kvrocks also have > > > good > > > > integration and ecosystem compatibility with other NoSQL database API > > and > > > > script. > > > > In comparison to current open source NoSQL database like Redis, which > > > also > > > > has rich data structure, Kvrocks data be stored in disk storage, but > > the > > > > redis data be stored in memory, it means the cost is higher and the > > > > capacity is limited when compare to disk storage solution, this is > why > > we > > > > created Kvrocks project to solve the cost and capacity issues by > using > > > disk > > > > storage solution, the following are key features of Kvrocks: > > > > > > > >- Compatibly sup
Re: [VOTE] Accept Kvrocks into the Apache Incubator
+1 (binding) Best, tison. Xiaoqiao He 于2022年4月20日周三 11:17写道： > +1 (binding) > > Regards, > - He Xiaoqiao > > On Wed, Apr 20, 2022 at 11:04 AM hulk wrote: > > > > +1 > > > > Regards, > > Hulk > > > > On Wed, Apr 20, 2022 at 7:49 AM Uma gangumalla > wrote: > > > > > +1 (binding) > > > > > > Regards, > > > Uma > > > > > > On Tue, Apr 19, 2022 at 4:18 PM Liang Chen > > > wrote: > > > > > > > Hi all, > > > > > > > > Following up the [DISCUSS] thread on Kvrocks[1], I would like to > > > > call a VOTE to accept Kvrocks into the Apache Incubator, please > check out > > > > the Kvrocks Proposal from the incubator wiki[2]. > > > > > > > > Please cast your vote: > > > > > > > > [ ] +1, bring Kvrocks into the Incubator > > > > [ ] +0, I don't care either way > > > > [ ] -1, do not bring Kvrocks into the Incubator, because... > > > > > > > > The vote will open at least for 72 hours, and only votes from the > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > [1] https://lists.apache.org/thread/bdtmvbmvzrgjd1kj7mdrp9tkqrhg3d31 > > > > [2] > > > https://cwiki.apache.org/confluence/display/INCUBATOR/KvrocksProposal > > > > > > > > Regards > > > > Liang > > > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] graduate Apache Doris (Incubating) as a Top Level Project
+1 binding Good luck :) Best, tison. Ming Wen 于2022年4月24日周日 13:58写道： > +1 binding > good luck > > Thanks, > Ming Wen, Apache APISIX PMC Chair > Twitter: _WenMing > > > Wang Weibing 于2022年4月24日周日 13:54写道： > > > +1 (non binding) > > > > I think the Doris Community have done a good job! > > > > Weibing Wang > > from Apache bRPC Community > > > > On 2022/04/24 02:25:46 陈明雨 wrote: > > > Dear Incubator Community, > > > > > > After having the discussion in Doris community[1][2], we have passed > the > > community vote[3]. > > > > > > And then made a discussion in general@incubator[4]. We got a lot of > > positive responses. > > > > > > And have responded and addressed all suggestions and comments raised. > > > > > > > > > > > > > > > I would like to start this voting thread to request graduating the > Doris > > project from the incubator as a TLP. > > > > > > Please provide your vote as one of the following options: > > > > > > > > > > > > > > > [ ] +1 - Recommend graduation of Apache Doris as a TLP > > > > > > [ ] 0 - I don't feel strongly about it, but don't object > > > > > > [ ] -1 - Do not recommend the graduation of Apache Doris because… > > > > > > > > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > > > > > > > > The following is a brief overview of the progress of the Doris project > > and community since entering the incubator: > > > > > > 1. Community > > > > > > - 9 new PPMC members were added, from five different companies, > bringing > > the total number of PPMC members to 22. > > > > > > - 20 new Committers were added (including the new PPMC members), > > bringing the total number of Committers to 33. > > > > > > - The number of Contributors is now 305 and growing[5]. > > > > > > - The dev@doris mailing list currently has 328 subscribers, and all > > major project discussions are happening in the dev@doris. > > > > > > > > > > > > > > > 2. Project > > > > > > - 7 releases by 6 release managers. All compliance issues have been > > resolved. > > > > > > - Doris official website[6] is compliant with Apache Foundation > > requirements[7]. > > > > > > - Project maturity model is detailed in [8]. > > > > > > - See Doris Project Incubation Status[9] for more info. > > > > > > > > > > > > > > > [1] https://lists.apache.org/thread/90fd2pd3r6wgn4hnfdo3rd0wqkv23cgr > > > > > > [2] https://lists.apache.org/thread/xc5qj7m2k1ph0mc97otj0nf8vskdfrzv > > > > > > [3] https://lists.apache.org/thread/9yklv4vbp39jhrzbcx3qgpcs1osk3lyf > > > > > > [4] https://lists.apache.org/thread/nbncjl8fdq0bcjop6l4747c8x9c06q00 > > > > > > [5] https://github.com/apache/incubator-doris > > > > > > [6] http://doris.incubator.apache.org/ > > > > > > [7] https://whimsy.apache.org/pods/project/doris > > > > > > [8] > > > https://cwiki.apache.org/confluence/display/DORIS/Maturity+Assessment+for+Doris > > > > > > [9] https://incubator.apache.org/projects/doris.html > > > > > > > > > > > > > > > > > > == > > > > > > Establish the Apache Doris Project > > > > > > > > > > > > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > > > > > the Foundation and consistent with the Foundation's purpose to > establish > > > > > > a Project Management Committee charged with the creation and > maintenance > > > > > > of open-source software, for distribution at no charge to the public, > > > > > > related to a MPP-based interactive SQL data warehousing for reporting > > > > > > and analysis. > > > > > > > > > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > > > > (PMC), to be known as the "Apache Doris Project", be and hereby is > > > > > > established pursuant to Bylaws of the Foundation; and be it furt
Multiple entities of software grant agreement
Hi IPMCs, Recently we voted and accepted Kvrocks to the Incubator[1]. While the IPMCs and PPMCs preparing the SGA, we meet an issue that the original entity sign a SGA but explicit limit the agreement on code from 2018 to 2020. Its lawyer said that code contributions from then on belong to the Kvrocks community. The issue is that since the original entity sign such a SGA and all core contributors sign ICLAs, is there other agreements should be signed for podling IP Clearance? Best, tison. [1] https://lists.apache.org/thread/shxcg56j3x36t75x63voj82s6hhdtrcv
Re: Multiple entities of software grant agreement
Thanks for your inputs. Try to summarize the discussion: * Apache requires a SGA from the *current* copyright holder of the software to grant permission for ASF. * If the current copyright holder is Meitu, then they should sign a grant with Exhibit A barely "Kvrocks". However, if the current copyright holder is "Kvrocks contributors", since it's a virtual entity, a certain contributor on behalf of the community should sign the SGA. Did I get it right? Is there some other proposal that got into the incubator without a SGA from a certain "company". Best, tison. Sheng Wu 于2022年4月25日周一 15:42写道： > > but I think it's right that meitu should claim clearly about the > copyright > date since the > > Do you mean there is no single Meitu employee(s) was > working/contributed to that project ever since? > Because the org is virtual on GitHub, and meitu can't sign CCLA or SGA > to that virtual group back then, I think one way or another, Meitu > still need to prove the SGA from the transfer date to now. > It is better for meitu to sign the SGA to declare all > contributions(from beginning to now), others(individuals) would submit > their ICLA(or other companies' SGA) for some codes after the transfer. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > hulk 于2022年4月25日周一 15:06写道： > > > > Thanks for junping reply. > > > > Yes, we also agree that should grant the whole source code repository > for > > ASF, > > but I think it's right that meitu should claim clearly about the > copyright > > date since the > > the repository was moved to another organization after then. > > > > So our question is should we need to sign extra other agreements for > > podling IP Clearance? > > > > > > > > On Mon, Apr 25, 2022 at 2:57 PM 俊平堵 wrote: > > > > > I think SGA here should be the same as other project. > > > As Craig mentioned above, it is code’s copyright owner ( a legal > entity or > > > natural human) to grant permission for ASF. If only for code during > certain > > > period, that means some code is not get permitted for Apache which is > very > > > weird. :( > > > > > > hulk 于2022年4月25日 周一上午11:52写道： > > > > > > > Thanks all, > > > > > > > > From the meitu side, they think should claim the date clearly > instead of > > > > implicitly, > > > > so I'm not sure whether is ok to add this clarification on SGA or > not? > > > > If not, are there other agreements that should be signed for podling > IP > > > > Clearance? > > > > > > > > On Mon, Apr 25, 2022 at 11:13 AM Sheng Wu > > > > > wrote: > > > > > > > > > Please check the SGA template of ASF, like Craig mentioned, > usually, > > > > > there is no date/timestamp included. > > > > > The foundation just needs legal approval that the company granted > to > > > > > move codes to the foundation, others(like individuals) should > submit > > > > > ICLA(s) > > > > > > > > > > Sheng Wu 吴晟 > > > > > Twitter, wusheng1108 > > > > > > > > > > hulk 于2022年4月25日周一 10:19写道： > > > > > > > > > > > > > I think the key is how they make this conclusion. Was the > project > > > > > > > moving to a 3rd party repository, and changing the owner from a > > > > > > > license perspective? > > > > > > > > > > > > Kvrocks has transferred from the meitu to the KvrocksLabs > > > organization > > > > > and claimed the copyright belongs to the Kvrocks community. > > > > > > > > > > > > > Is there a place/way to track this event? > > > > > > > > > > > > We didn't track this event in a public place. The lawyer thinks > they > > > > can > > > > > only grant the copyright when all of the contributors are their > > > employees > > > > > (before 2020.3.23). After that, the copyright should belong to the > > > > Kvrocks > > > > > community. > > > > > > > > > > > > On Mon, Apr 25, 2022 at 8:29 AM Sheng Wu < > wu.sheng.841...@gmail.com> > > > > > wrote: > > > > > >> > > > > > >> > While the IPMCs and PPMCs preparing the SGA > > > > > >> > > > > > >> I think IPMC don&
Re: terminology (was: [DISCUSSION] Incubating proposal of Kvrocks)
Hi Greg, Thanks for pointing that out. Is "5 IPMC members" correct also? "5 members of the IPMC" is a bit wordy, though. Best, tison. Greg Stein 于2022年4月27日周三 10:52写道： > I have a problem with the terminology some people are using: > > On Thu, Apr 14, 2022 at 10:28 PM tison wrote: > >... > > > 3. The proposal wants to run this podling with 5 IPMCs, > > > There is ONLY ONE IPMC. aka the Incubator Project Management Committee. > > ONE. > > IPMC refers to the committee. > > The use of "IPMC" to refer to a *MEMBER* of the IPMC is erroneous. The > correct phrase is "5 members of the IPMC". > > NOTE: I have seen this elsewhere. A "PMC" is a committee. It is NOT A > PERSON. > > -g >
Setting up project website
Hi, On Apache Kvrocks (Incubating) project, I just set up the website repo (main and asf-site branch)[1] and it seems the asf-site branch is properly configured and static site staff published. However, the homepage https://kvrocks.apache.org/ still returns 404 NOT FOUND. I don't know whether it takes some time to deploy or the setting is wrong which needs more polishing. Best, tison. [1] https://github.com/apache/incubator-kvrocks-website/tree/asf-site
Re: Setting up project website
https://github.com/apache/incubator-kvrocks-website/blob/main/.asf.yaml .asf.yaml is also present on main branch. Best, tison. Sheng Wu 于2022年5月15日周日 20:58写道： > I remember you need this > > https://github.com/apache/skywalking-website/blob/master/.asf.yaml > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > tison 于2022年5月15日周日 20:50写道： > > > > Hi, > > > > On Apache Kvrocks (Incubating) project, I just set up the website repo > > (main and asf-site branch)[1] and it seems the asf-site branch is > properly > > configured and static site staff published. > > > > However, the homepage https://kvrocks.apache.org/ still returns 404 NOT > > FOUND. I don't know whether it takes some time to deploy or the setting > is > > wrong which needs more polishing. > > > > Best, > > tison. > > > > [1] https://github.com/apache/incubator-kvrocks-website/tree/asf-site >
Re: Setting up project website
Thank you. It seems that the website is online and the problem is that initializing the website takes some time. Best, tison. Calvin Kirs 于2022年5月15日周日 21:20写道： > HI, > > FYI [1]: Website deployment service for Git repositories. > > btw. I recommend that the mentor guide PPMC do such a thing, rather > than the mentor doing it himself. > > [1] > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories > > tison 于2022年5月15日周日 21:07写道： > > > > https://github.com/apache/incubator-kvrocks-website/blob/main/.asf.yaml > > > > .asf.yaml is also present on main branch. > > > > Best, > > tison. > > > > > > Sheng Wu 于2022年5月15日周日 20:58写道： > > > > > I remember you need this > > > > > > https://github.com/apache/skywalking-website/blob/master/.asf.yaml > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > tison 于2022年5月15日周日 20:50写道： > > > > > > > > Hi, > > > > > > > > On Apache Kvrocks (Incubating) project, I just set up the website > repo > > > > (main and asf-site branch)[1] and it seems the asf-site branch is > > > properly > > > > configured and static site staff published. > > > > > > > > However, the homepage https://kvrocks.apache.org/ still returns 404 > NOT > > > > FOUND. I don't know whether it takes some time to deploy or the > setting > > > is > > > > wrong which needs more polishing. > > > > > > > > Best, > > > > tison. > > > > > > > > [1] > https://github.com/apache/incubator-kvrocks-website/tree/asf-site > > > > > > > -- > Best wishes！ > CalvinKirs > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Is it possible to install GitHub App on apache repos?
Hi, Supposed that I'd like to use semantic-pull-requests[1] app for validating PRs on GitHub. But it requires people with maintain permissions to enable. I'm unsure about our policy whether it's possible to file an issue on INFRA JIRA project to perform such actions (of course, with a PMC voting result). Best, tison. [1] https://github.com/apps/semantic-pull-requests
Re: Is it possible to install GitHub App on apache repos?
Hi Gavin, Thank you! Could you share some examples I can refer to? Best, tison. Gavin McDonald 于2022年5月15日周日 23:11写道： > INFRA Jira is fine , it is already enabled for other repositories. > > On Sun, May 15, 2022 at 4:50 PM tison wrote: > >> Hi, >> >> Supposed that I'd like to use semantic-pull-requests[1] app for >> validating PRs on GitHub. But it requires people with maintain permissions >> to enable. I'm unsure about our policy whether it's possible to file an >> issue on INFRA JIRA project to perform such actions (of course, with a PMC >> voting result). >> >> Best, >> tison. >> >> [1] https://github.com/apps/semantic-pull-requests >> > > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
Re: Is it possible to install GitHub App on apache repos?
Thanks again :) Best, tison. Gavin McDonald 于2022年5月15日周日 23:22写道： > Sure, https://issues.apache.org/jira/browse/INFRA-21904 > > > > On Sun, May 15, 2022 at 5:14 PM tison wrote: > > > Hi Gavin, > > > > Thank you! Could you share some examples I can refer to? > > > > Best, > > tison. > > > > > > Gavin McDonald 于2022年5月15日周日 23:11写道： > > > >> INFRA Jira is fine , it is already enabled for other repositories. > >> > >> On Sun, May 15, 2022 at 4:50 PM tison wrote: > >> > >>> Hi, > >>> > >>> Supposed that I'd like to use semantic-pull-requests[1] app for > >>> validating PRs on GitHub. But it requires people with maintain > permissions > >>> to enable. I'm unsure about our policy whether it's possible to file an > >>> issue on INFRA JIRA project to perform such actions (of course, with a > PMC > >>> voting result). > >>> > >>> Best, > >>> tison. > >>> > >>> [1] https://github.com/apps/semantic-pull-requests > >>> > >> > >> > >> -- > >> > >> *Gavin McDonald* > >> Systems Administrator > >> ASF Infrastructure Team > >> > > > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP
gt; > > > > > > > > > > > > > > > > WHEREAS, the Board of Directors deems it to be in the best > > > interests of > > > > > > > > > > > > > > > > the Foundation and consistent with the Foundation's purpose > to > > > establish > > > > > > > > > > > > > > > > a Project Management Committee charged with the creation and > > > maintenance > > > > > > > > > > > > > > > > of open-source software, for distribution at no charge to the > > > public, > > > > > > > > > > > > > > > > related to a one-stop data integration framework that > provides > > > > > > > > > > > > > > > > automatic, secure, and reliable data transmission > capabilities. > > > InLong > > > > > > > > > > > > > > > > supports both batch and stream data processing at the same > > time, > > > which > > > > > > > > > > > > > > > > offers great power to build data analysis, modeling, and > other > > > real-time > > > > > > > > > > > > > > > > applications based on streaming data. > > > > > > > > > > > > > > > > > > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > > Committee > > > > > > > > > > > > > > > > (PMC), to be known as the "Apache InLong Project", be and > > hereby > > > is > > > > > > > > > > > > > > > > established pursuant to Bylaws of the Foundation; and be it > > > further > > > > > > > > > > > > > > > > > > > > > > > > RESOLVED, that the Apache InLong Project be and hereby is > > > responsible > > > > > > > > > > > > > > > > for the creation and maintenance of software related to a > > > one-stop data > > > > > > > > > > > > > > > > integration framework that provides automatic, secure, and > > > reliable data > > > > > > > > > > > > > > > > transmission capabilities. InLong supports both batch and > > stream > > > data > > > > > > > > > > > > > > > > processing at the same time, which offers great power to > build > > > data > > > > > > > > > > > > > > > > analysis, modeling, and other real-time applications based on > > > streaming > > > > > > > > > > > > > > > > data; and be it further > > > > > > > > > > > > > > > > > > > > > > > > RESOLVED, that the office of "Vice President, Apache InLong" > 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 > > > InLong > > > > > > > > > > > > > > > > Project, and to have primary responsibility for management of > > the > > > > > > > > > > > > > > > > projects within the scope of responsibility of the Apache > > InLong > > > > > > > > > > > > > > > > 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 > InLong > > > Project: > > > > > > > > > > > > > > > > > > > > > > > > * Aloys Zhang > > > > > > > > > > > > > > > > * Charles Zhang > > > > > > > > > > > > > > > > * Guangxu Cheng > > > > > > > > > > > > > > > > * Guocheng Zhang > > > > > > > > > > > > > > > > * Heal Chow > > > > > > > > > > > > > > > > * Jean-Baptiste Onofré > > > > > > > > > > > > > > > > * Jerry Shao > > > > > > > > > > > > > > > > * Junjie Chen > > > > > > > > > > > > > > > > * Junping Du > > > > > > > > > > > > > > > > * Justin Mclean > > > > > > > > > > > > > > > > * Lamber Liu > > > > > > > > > > > > > > > > * Osgoo Li > > > > > > > > > > > > > > > > * Peng Chen > > > > > > > > > > > > > > > > * Zak Wu > > > > > > > > > > > > > > > > * ZhongBo Wu > > > > > > > > > > > > > > > > * Zili Chen > > > > > > > > > > > > > > > > * Daniel Li > > > > > > > > > > > > > > > > * Guo Jiwei > > > > > > > > > > > > > > > > * Haiji Li > > > > > > > > > > > > > > > > * Lizhen > > > > > > > > > > > > > > > > * Yuanbo Liu > > > > > > > > > > > > > > > > * Yuanhao Ji > > > > > > > > > > > > > > > > * Zijie Lu > > > > > > > > > > > > > > > > * Zirui Peng > > > > > > > > > > > > > > > > > > > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Charles Zhang be > > > appointed > > > > > > > > > > > > > > > > to the office of Vice President, Apache InLong, to serve in > > > accordance > > > > > > > > > > > > > > > > with and subject to the direction of the Board of Directors > and > > > the > > > > > > > > > > > > > > > > Bylaws of the Foundation until death, resignation, > retirement, > > > removal > > > > > > > > > > > > > > > > or disqualification, or until a successor is appointed; and > be > > it > > > > > > > > > > > > > > > > further > > > > > > > > > > > > > > > > > > > > > > > > RESOLVED, that the Apache InLong Project be and hereby is > > tasked > > > with > > > > > > > > > > > > > > > > the migration and rationalization of the Apache Incubator > > InLong > > > > > > > > > > > > > > > > podling; and be it further > > > > > > > > > > > > > > > > > > > > > > > > RESOLVED, that all responsibilities pertaining to the Apache > > > Incubator > > > > > > > > > > > > > > > > InLong podling encumbered upon the Apache Incubator PMC are > > > hereafter > > > > > > > > > > > > > > > > discharged. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Best wishes, > > > > > > > > Charles Zhang > > > > > > > > > > > > > > > > > - > > > > > > > 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 > > > > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > -- Best, tison.
Re: [DISCUSSION] Incubating Proposal of Uniffle
+1 (binding) An interesting project. Good luck! Best, tison. Jungtaek Lim 于2022年5月25日周三 14:22写道： > +1 (non-binding) > > Good luck! > > On Wed, May 25, 2022 at 2:42 PM Daniel Widdis wrote: > > > This was stated in the other thread: Unified/Universal Shuffle > > > > On 5/24/22, 10:04 PM, "XiaoYu" wrote: > > > > Hi > > > > Uniffle as a project name， What does he mean~ > > > > thanks > > > > Weiwei Yang 于2022年5月25日周三 12:57写道： > > > > > > +1 (binding) > > > Good luck! > > > > > > On Tue, May 24, 2022 at 8:49 PM Ye Xianjin > > wrote: > > > > > > > +1 (non-binding). > > > > > > > > Sent from my iPhone > > > > > > > > > On May 25, 2022, at 9:59 AM, Goson zhang < > gosonzh...@apache.org> > > wrote: > > > > > > > > > > +1 (non-binding) > > > > > > > > > > Good luck! > > > > > > > > > > Daniel Widdis 于2022年5月25日周三 09:53写道： > > > > > > > > > >> +1 (non-binding) from me! Good luck! > > > > >> > > > > >> On 5/24/22, 9:05 AM, "Jerry Shao" wrote: > > > > >> > > > > >>Hi all, > > > > >> > > > > >>Due to the name issue in thread ( > > > > >> > > https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f), > > > > we > > > > >>figured out a new project name "Uniffle" and created a new > > Thread. > > > > >> Please > > > > >>help to discuss. > > > > >> > > > > >>We would like to propose Uniffle[1] as a new Apache > incubator > > > > project, > > > > >> you > > > > >>can find the proposal here [2] for more details. > > > > >> > > > > >>Uniffle is a high performance, general purpose Remote > > Shuffle Service > > > > >> for > > > > >>distributed compute engines like Apache Spark > > > > >><https://spark.apache.org/>, Apache > > > > >>Hadoop MapReduce <https://hadoop.apache.org/>, Apache > Flink > > > > >><https://flink.apache.org/> and so on. We are aiming to > make > > > > >> Firestorm a > > > > >>universal shuffle service for distributed compute engines. > > > > >> > > > > >>Shuffle is the key part for a distributed compute engine to > > exchange > > > > >> the > > > > >>data between distributed tasks, the performance and > > stability of > > > > >> shuffle > > > > >>will directly affect the whole job. Current “local file > > pull-like > > > > >> shuffle > > > > >>style” has several limitations: > > > > >> > > > > >> 1. Current shuffle is hard to support super large > > workloads, > > > > >> especially > > > > >> in a high load environment, the major problem is IO > > problem > > > > (random > > > > >> disk IO > > > > >> issue, network congestion and timeout). > > > > >> 2. Current shuffle is hard to deploy on the > disaggregated > > compute > > > > >> storage environment, as disk capacity is quite limited > on > > compute > > > > >> nodes. > > > > >> 3. The constraint of storing shuffle data locally makes > > it hard to > > > > >> scale > > > > >> elastically. > > > > >> > > > > >>Remote Shuffle Service is the key technology for > enterprises > > to build > > > > >> big > > > > >>data platforms, to expand big data applications to > > disaggregated, > > > > >>online-offline hybrid environments, and to solve above > > problems. > > > > >> > > > > >>The impl
Re: [VOTE] Graduate Apache InLong(Incubating) as a TLP
+1 (binding) Good luck! Best, tison. Jerry Shao 于2022年5月25日周三 16:12写道： > +1 (binding). > > Good luck to Inlong. > > Best > Jerry > > 俊平堵 于2022年5月25日周三 14:50写道： > > > +1, good luck to InLong.:) > > > > Charles Zhang 于2022年5月25日 周三下午2:34写道： > > > > > Dear Apache Incubator Community, > > > > > > > > > The InLong community has a discussion thread [1], passed the community > > vote > > > [2], and the vote result is published [3]. We have discussed the > > graduation > > > for InLong in the Incubator Community [4], where no issues were raised > > and > > > lots of positive responses were received. > > > > > > > > > I would like to start this voting thread to request graduating Apache > > > InLong (incubating) from the incubator as a TLP. Please provide your > vote > > > as one of the following options: > > > > > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator. > > > > > > [ ] +0 No opinion. > > > > > > [ ] -1 No, the InLong project is not ready to graduate, because ... > > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > > Since incubating in ASF, the project itself has become more mature and > > > > > > stable. The following is a brief summary of the project and community > > > > > > during the incubation: > > > > > > > > > - 11 versions were released by 6 different release managers, of which 5 > > > > > > versions are the original TubeMQ, and 6 versions are after the name was > > > > > > changed to InLong. The release cadence is about 2 months [5]. > > > > > > > > > - 10 new Committers and 3 PPMCs were added during incubating, they are > > from > > > > > > 4 different organizations. All PPMCs and Committers are spread across 8 > > > > > > different organizations [6]. > > > > > > > > > - 101 unique code developers [7]. > > > > > > > > > - Closed more than 2200 issues, with an average of 200 issues per > version > > > > > > [8]. > > > > > > > > > - All the dependencies were reviewed and ensured they do not bring any > > > > > > license issues [9]. > > > > > > > > > - Evaluated the InLong project and self-checked the InLong maturity > model > > > > > > [10] and the pre-graduation Check [11]. > > > > > > > > > - Well and Complete documentation for contributors and users [12]. > > > > > > > > > - Created channels like Email, Slack, Twitter, WeChat, and GitHub > > > > > > Discussions to communicate, with more than 650 subscribers. > > > > > > > > > - Actively participated in or held more than 15 meetups to increase > > > > > > community influence. > > > > > > > > > Please see the proposed board resolution below and let us know what you > > > > > > think. The initial PMC members were passed by the discussion and > > invitation > > > > > > [13]. > > > > > > > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro > > > > > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20 > > > > > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9 > > > > > > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t > > > > > > [5] https://inlong.apache.org/download/main/ > > > > > > [6] https://whimsy.apache.org/roster/ppmc/inlong > > > > > > [7] https://github.com/apache/incubator-inlong/graphs/contributors > > > > > > [8] > > > > > > > > > https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed > > > > > > [9] https://github.com/apache/incubator-inlong/tree/master/licenses > > > > > > [10] > > > > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG&title=Maturity+Assessment+for+InLong > > > > > > [11] > > > > > > > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List > > > > > > [12] https://inlong.apache.org/docs/next/introduction > > > > > > [13] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfq
Re: [VOTE] Accept Uniffle into the Apache Incubator
+1 (binding) Best, tison. Jerry Shao 于2022年5月31日周二 09:37写道： > Hi all, > > Following up the [DISCUSS] thread on Uniffle[1] and Firestorm[2], I would > like to > call a VOTE to accept Uniffle into the Apache Incubator, please check out > the Uniffle Proposal from the incubator wiki[3]. > > Please cast your vote: > > [ ] +1, bring Uniffle into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring Uniffle into the Incubator, because... > > The vote will open at least for 72 hours, and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > [1] https://lists.apache.org/thread/fyyhkjvhzl4hpzr52hd64csh5lt2wm6h > [2] https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f > [3] https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal > > Best regards, > Jerry >
Re: [DISCUSS] Graduate Apache ShenYu(Incubating) as Apache TLP
Hi, ShenYu is born to be open-source and the experience it grows the community in both users perspective and developers perspective looks attractive. Its diversity and maturity to make Apache release, as well as the behavior of PPMC members are good fit in the Apache way. I'm glad to see such a project become an Apache top level project. Good luck. Best, tison. XiaoYu 于2022年6月13日周一 13:35写道： > Dear Apache Incubator Community, > > Apache ShenYu has been incubating since 2021-05-03. For over a year, the > Apache ShenYu community has made great progress and grown rapidly under the > guidance of our mentors. We believe the Apache ShenYu project has met the > conditions for graduation. Summary statistics on the state of the > community are listed below. Please feel free to participate in the > discussion and give more feedback. > > The Apache ShenYu community has a discussion thread [1], passed the > community vote > [2], and the vote result is published [3]. Our assessment is that Apache > ShenYu(Incubating) is ready to graduate as a Apache TLP. We would like to > raise > the discussion to IPMC and collect more feedback towards graduation. > > ** Community ** > > - 6 new PPMC members were added, bringing the total number of PPMC > members to 30 from at least 15+ different organizations. > > - 7 new Committers were added, bringing the total number of Committers > 37. > > - 110+ new contributors participate in the community. The number > of contributors is now 274 and growing. > > - The dev@shenyu.a.o mailing list currently has 357 subscribers, > and all major project discussions are happening in the dev@shenyu.a.o. > > - 26 Bi-weekly online meetings were held between committers, > contributors and users. The meeting minutes are recorded on the > mailing list [4]. > > - 1100+ pull requests merged [5], and 700+ issues closed [6] after > into the apache incubator. > > ** Project ** > > - 4 releases by 4 release managers. > > - ShenYu official website [7] is compliant with Apache Foundation > requirements [8]. > > - Project maturity model is detailed in [9]. > > - See ShenYu Project Incubation Status [10] for more info. > > ** Brands ,License, and Copyright ** > > - We submitted an application for the brand[11] and it has been > reviewed and approved. > - Apache ShenYu community maintains project code on GitHub, and all > modules > code is under Apache 2.0 license. We have reviewed all the > dependencies and ensured they do not bring any license issues [12]. All > the status files, license headers, and copyright are up to date. > > ** PMC members ** > >- Please see the proposed board resolution below and let us know what > you > think. The initial PMC members were passed by the discussion and invitation > [13]. > > The discussion will remain open for at least 72 hours, looking forward to > your feedback. > > [1] https://lists.apache.org/thread/lc1xr9gjf1t2lbk8070thf1bgt3sq1v3 > [2] https://lists.apache.org/thread/0fo3f3whl7bb5r7bhoh85czlgjdn7rog > [3] https://lists.apache.org/thread/jdh2dcs4qd97t1mjjl8hp62sso470wc7 > [4] https://lists.apache.org/list.html?d...@shenyu.apache.org > [5] > https://github.com/apache/incubator-shenyu/pulls?q=is%3Apr+merged%3A%3E%3D2021-05-03+ > [6] > https://github.com/apache/incubator-shenyu/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-05-03 > [7] https://shenyu.incubator.apache.org/ > [8] https://whimsy.apache.org/pods/project/shenyu > [9] https://github.com/apache/incubator-shenyu/blob/master/MATURITY.md > [10] https://incubator.apache.org/projects/shenyu.html > [11] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-197 > [12] https://github.com/apache/incubator-shenyu/blob/master/LICENSE > [13] https://lists.apache.org/thread/gp1bnjflz7ysgopxk515l9clswgrvnko > > > -- > > Establish the Apache ShenYu 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 Apache ShenYu is a high performance Microservices API gateway > in Java ecosystem, compatible with a variety of mainstream framework > systems, supports hot plug. Users can write their own plugin meet the > current requirement and future needs in a variety of scenarios, > especially in large-scale scenes. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be
Re: [VOTE] Graduate Apache ShenYu(Incubating) as a TLP
+1 binding WenYu Dai 于2022年6月18日 周六10:17写道： > + 1 (non-binding) > > On 2022/06/18 02:13:37 Goson zhang wrote: > > + 1 (non-binding) > > > > Good luck!! > > > > Liu Ted 于2022年6月18日周六 10:04写道： > > > > > +1 (binding) with the best wishes. > > > Ted Liu > > > > > > 2022 年 6 月 18 日周六 9:47，TaiShi Hu 写道： + 1 > > > (non-binding) > > > > > > On 2022/06/18 01:35:55 qicz wrote: > > > > + 1 (non-binding) > > > > > > > > On Saturday, June 18, 2022, Sheng Wu > wrote: > > > > > > > > > +1 binding. > > > > > > > > > > Good luck for your next journey. > > > > > > > > > > Justin Mclean 于2022年6月18日 周六09:12写道： > > > > > > > > > > > HI, > > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > Kind Regards, > > > > > > Justin > > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > > > For additional commands, e-mail: > general-h...@incubator.apache.org > > > > > > > > > > > > -- > > > > > Sheng Wu 吴晟 > > > > > > > > > > Apache SkyWalking > > > > > Apache Incubator > > > > > Apache ShardingSphere, ECharts, DolphinScheduler podlings > > > > > Zipkin > > > > > Twitter, wusheng1108 > > > > > > > > > > > > > > > - > > > 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 > > -- Best, tison.
Create a new directory for podling
Hi, After a new podling joined the incubator, when an Apache release prepared, it seems that I should create a new directory under both: * https://dist.apache.org/repos/dist/dev/incubator * https://dist.apache.org/repos/dist/release/incubator and then push a KEYS file to hold PMC members' keys. Is there an instruction manual for these steps? Best, tison.
Re: [VOTE] Graduate Apache ShenYu(Incubating) as a TLP [ROUND 2]
+1 (binding) Best, tison. Liming Deng 于2022年6月22日周三 15:04写道： > +1 (non-binding) > > > On 2022/06/22 06:42:42 XiaoYu wrote: > > Dear Apache Incubator Community, > > > > In the previous vote[1] thread, > > > > I only described the functionality of the project and not the scope of > > the project in the resolution template.It doesn't fit the standard > > template. so I initiate cancel the vote thread[2]. > > > > Under the guidance of our mentors, I refactor the project description > > in this resolution template. > > > > The Apache ShenYu community has a discussion thread [3], > > passed the community vote[4], and the vote result is published [5]. > > We have discussed the graduation for ShenYu in the Incubator Community > [6], > > where no issues were raised and lots of positive responses were received. > > > > I would like to start this voting thread to request graduating Apache > > ShenYu (incubating) from the incubator as a TLP. Please provide your vote > > as one of the following options: > > > > [ ] +1 Yes, I support ShenYu to graduate from the Apache incubator. > > > > [ ] +0 No opinion. > > > > [ ] -1 No, the ShenYu project is not ready to graduate, because ... > > > > The VOTE will remain open for at least 72 hours. > > > > > > ** Community ** > > > > - 6 new PPMC members were added, bringing the total number of PPMC > > members to 30 from at least 15+ different organizations. > > > > - 7 new Committers were added, bringing the total number of > Committers 37. > > > > - 110+ new contributors participate in the community. The number > > of contributors is now 270+ and growing. > > > > - The dev@shenyu.a.o mailing list currently has 350+ subscribers, > > and all major project discussions are happening in the dev@shenyu.a.o. > > > > - 26 Bi-weekly online meetings were held between committers, > > contributors and users. The meeting minutes are recorded on the > > mailing list [7]. > > > > - 1100+ pull requests merged [8], and 700+ issues closed [9] after > > into the apache incubator. > > > > ** Project ** > > > > - 4 releases by 4 release managers. > > > > - ShenYu official website [10] is compliant with Apache Foundation > > requirements [11]. > > > > - Project maturity model is detailed in [12]. > > > > - See ShenYu Project Incubation Status [13] for more info. > > > > ** Brands ,License, and Copyright ** > > > > - We submitted an application for the brand[14] and it has been > > reviewed and approved. > > - Apache ShenYu community maintains project code on GitHub, and all > modules > > code is under Apache 2.0 license. We have reviewed all the > > dependencies and ensured they do not bring any license issues [15]. All > > the status files, license headers, and copyright are up to date. > > > > ** PMC members ** > > > >- Please see the proposed board resolution below and let us know what > you > > think. The initial PMC members were passed by the discussion and > invitation > > [16]. > > > > [1] https://lists.apache.org/thread/yk6kjx3j2mh9c5xzfojcln5dtrzt87yf > > [2] https://lists.apache.org/thread/53rj96r63sf2vxcdbfqbqbl27r4v9j0c > > [3] https://lists.apache.org/thread/lc1xr9gjf1t2lbk8070thf1bgt3sq1v3 > > [4] https://lists.apache.org/thread/0fo3f3whl7bb5r7bhoh85czlgjdn7rog > > [5] https://lists.apache.org/thread/jdh2dcs4qd97t1mjjl8hp62sso470wc7 > > [6] https://lists.apache.org/thread/cc2myvso0pbyl39yv26bdmzml8jjvpt2 > > [7] https://lists.apache.org/list.html?d...@shenyu.apache.org > > [8] > https://github.com/apache/incubator-shenyu/pulls?q=is%3Apr+merged%3A%3E%3D2021-05-03+ > > [9] > https://github.com/apache/incubator-shenyu/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-05-03 > > [10] https://shenyu.incubator.apache.org/ > > [11] https://whimsy.apache.org/pods/project/shenyu > > [12] https://github.com/apache/incubator-shenyu/blob/master/MATURITY.md > > [13] https://incubator.apache.org/projects/shenyu.html > > [14] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-197 > > [15] https://github.com/apache/incubator-shenyu/blob/master/LICENSE > > [16] https://lists.apache.org/thread/gp1bnjflz7ysgopxk515l9clswgrvnko > > > > > -- > > > > Establish the Apache ShenYu Project > > > > WHEREAS, the Board of Directors de
Queuing solution for merging patches
Hi, There're several solutions around GitHub ecosystem to queuing patches passed reviews and waiting for merged, especially in case to avoid semantic conflict; e.g., Mergify or Bors-NG. After enabled branch must be up-to-date with main branch, it introduces an issue that multiple patches can race each other and cause unnecessary CI tasks rerun - two patches can be verified simultaneously, after one merged, the other should rerun, which generally cause O(n^2) task instance while with queuing only O(n) is required. Given that there're existing solutions, I'd like to ask what the best practice for Apache projects host developments on GitHub on this topic. Or what support does INFRA provide for the certain case. Best, tison.
Re: Queuing solution for merging patches
Hi Sheng, Yes. I do _not_ ask INFRA to support it, but to see if there is existing practice. Best, tison. Sheng Wu 于2022年6月29日周三 19:33写道： > Hi Tison > > I think there is no hard requirement from infra or Apache perspective. The > PMC could decide what they like, and ask Infra team to set them up. > > tison 于2022年6月29日 周三19:25写道： > > > Hi, > > > > There're several solutions around GitHub ecosystem to queuing patches > > passed reviews and waiting for merged, especially in case to avoid > semantic > > conflict; e.g., Mergify or Bors-NG. > > > > After enabled branch must be up-to-date with main branch, it introduces > an > > issue that multiple patches can race each other and cause unnecessary CI > > tasks rerun - two patches can be verified simultaneously, after one > merged, > > the other should rerun, which generally cause O(n^2) task instance while > > with queuing only O(n) is required. > > > > Given that there're existing solutions, I'd like to ask what the best > > practice for Apache projects host developments on GitHub on this topic. > Or > > what support does INFRA provide for the certain case. > > > > Best, > > tison. > > > -- > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 >
Re: Queuing solution for merging patches
Hi Sheng, I think you're right that I can remove 'required_status_checks.strict' in .asf.yaml to disable up-to-date requirements and then find other way to resolve logic conflict issue. At least the committers should be aware of which case should merge main branch. Hi Martinjn, Good to know that you meet similar requirements and those previous discussions. I think one possible way is finding a sponsored bors-ng deployment and ask INFRA to setup webhook, or ask INFRA to enable bors-ng / mergify app on the repo. I don't know whether it's a good fit but some thoughts. BTW, GitHub provides an option to always show "Update Branch" but not require to be up-to-date. I'll ask INFRA whether there's an option to configure. See also https://issues.apache.org/jira/browse/INFRA-23432. Best, tison. Martijn Visser 于2022年6月29日周三 21:13写道： > Hi Tison, > > I asked a couple of months ago [1] if Infra could enable Github's Merge > Queue Functionality [2]. That was rejected unfortunately. I'm also curious > if others think of a solution that would be compliant with the ASF rules. > > Best regards, > > Martijn > > [1] https://issues.apache.org/jira/browse/INFRA-22804 > [2] > > https://github.blog/changelog/2021-10-27-pull-request-merge-queue-limited-beta/ > > Op wo 29 jun. 2022 om 13:53 schreef Sheng Wu : > > > Hi > > > > I think the key is you set up to date for main branch, which makes CI has > > to rerun. > > > > tison 于2022年6月29日 周三19:39写道： > > > >> Hi Sheng, > >> > >> Yes. I do _not_ ask INFRA to support it, but to see if there is existing > >> practice. > >> > >> Best, > >> tison. > >> > >> > >> Sheng Wu 于2022年6月29日周三 19:33写道： > >> > >> > Hi Tison > >> > > >> > I think there is no hard requirement from infra or Apache perspective. > >> The > >> > PMC could decide what they like, and ask Infra team to set them up. > >> > > >> > tison 于2022年6月29日 周三19:25写道： > >> > > >> > > Hi, > >> > > > >> > > There're several solutions around GitHub ecosystem to queuing > patches > >> > > passed reviews and waiting for merged, especially in case to avoid > >> > semantic > >> > > conflict; e.g., Mergify or Bors-NG. > >> > > > >> > > After enabled branch must be up-to-date with main branch, it > >> introduces > >> > an > >> > > issue that multiple patches can race each other and cause > unnecessary > >> CI > >> > > tasks rerun - two patches can be verified simultaneously, after one > >> > merged, > >> > > the other should rerun, which generally cause O(n^2) task instance > >> while > >> > > with queuing only O(n) is required. > >> > > > >> > > Given that there're existing solutions, I'd like to ask what the > best > >> > > practice for Apache projects host developments on GitHub on this > >> topic. > >> > Or > >> > > what support does INFRA provide for the certain case. > >> > > > >> > > Best, > >> > > tison. > >> > > > >> > -- > >> > Sheng Wu 吴晟 > >> > > >> > Apache SkyWalking > >> > Apache Incubator > >> > Apache ShardingSphere, ECharts, DolphinScheduler podlings > >> > Zipkin > >> > Twitter, wusheng1108 > >> > > >> > > -- > > Sheng Wu 吴晟 > > > > Apache SkyWalking > > Apache Incubator > > Apache ShardingSphere, ECharts, DolphinScheduler podlings > > Zipkin > > Twitter, wusheng1108 > > >
Re: [VOTE] Release Apache Kvrocks(incubating) 2.1.0
Carry on my vote in the dev@ thread: +1 binding + Checksum and GPG sign correct + LICENSE, NOTICE and DISCLAIMER files exist + Build from source via `./x.py build` + Communicate kvrocks with redis-cli and all things fine. + No binary files bundled. + Version info correct (2.1.0) Best, tison. hulk 于2022年7月30日周六 18:13写道： > Hello IPMC, > > The Apache Kvrocks community has voted and approved the release of Apache > Kvrocks(incubating) 2.1.0. We now kindly request the IPMC members > review and vote for this release. > > Kvrocks is a distributed key value NoSQL database that uses RocksDB as the > storage engine > and is compatible with Redis protocol. The current release provides the > first official > package, resolves all of the license issues, many improvements and fixes > many bugs. > > Kvrocks community vote thread: > > https://lists.apache.org/thread/b6hdnsq7fw2tnqlfo1h1yzqhbrxjkyg4 > > Vote result thread: > > https://lists.apache.org/thread/rw0s8m72f5kp0pohs2xc75xsvk6wyw44 > > **Vote Results**: > No 0 or -1 votes. > > 7 (+1) Binding Vote: > > - Yuan Wang > - tison > - hulk > - Liang Chen > - Jean-Baptiste Onofré > - Xiaoqiao He > - donghui liu > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.1.0 > > This release has been signed with a PGP available here: > > https://downloads.apache.org/incubator/kvrocks/KEYS > > Git tag for the release: > > https://github.com/apache/incubator-kvrocks/releases/tag/v2.1.0 > > Build guide can be found at: > > https://github.com/apache/incubator-kvrocks#build > > The vote will be open for at least 72 hours or until the necessary number > of votes is reached. > > Please vote accordingly: > [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.1.0 > [ ] +0 > [ ] -1 Do not approve (please specify the reason) > > Best Regards, > hulk > Apache Kvrocks (incubating) > > -- > Best Regards, > - *Hulk Lin* >
[DISCUSS] Incubating Proposal for StreamPark
Hi all, I would like to propose StreamPark[1] as a new apache incubator project, you can find the proposal[2] of StreamPark for more detail. StreamPark is a streaming application development platform. Aimed at ease building and managing streaming applications, StreamPark provides scaffolding for writing streaming process logic with Apache Flink and Apache Spark. Also, StreamPark provides a dashboard for controlling and monitoring streaming tasks. It was initially known as StreamX and renamed to StreamPark in August 2022. StreamPark abstracts the environment and program parameters of task development and deployment in a convention over configuration manner for low code development. It initializes a runtime environment and context and combines it with a series of connectors to simplify development. From the aspect of a task management platform, StreamPark is a streaming data management platform based on the JVM platform. So far, StreamPark has accumulated a few users, and the accrued download time is over 5,000. The representative users are Baidu, China Unicom, Ziroom, Yonghui Supermarket, InMobi, YTO Express, and so on. StreamPark has built an open-source community with 52 developers and released over ten versions in the past year. The proposed initial committers are interested in joining ASF to increase the connections in the open-source world. Based on extensive collaboration, it is possible to build a community of developers and committers that live longer than the founder. Also, the Apache Brand can help encourage more organizations to use StreamPark more confidently. We believe that the StreamPark project will provide diversity value for the community if StreamPark is introduced into the Apache incubator. I (@tison) will help this project as the champion and many thanks to four other mentors: * Willem Ning Jiang [ningji...@apache.org] * Stephan Ewen [se...@apache.org] * Thomas Weise [t...@apache.org] * Duo Zhang [zhang...@apache.org] Best, tison. [1] https://github.com/streamxhub/streamx [2] https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal
Re: [DISCUSS] Incubating Proposal for StreamPark
Hi Sheng, Thanks for your comments. I write the proposal just following the template. Please specify exactly which section is in the wrong format or missing. Best, tison. Sheng Wu 于2022年8月17日周三 10:26写道： > Hi, > > Could you reformat this proposal to follow the proposal template? There is > something like project owner, dependencies, initial committers, experienced > developers etc. are not clear right now. > > tison 于2022年8月17日 周三09:15写道： > > > Hi all, > > > > I would like to propose StreamPark[1] as a new apache incubator project, > > you can find the proposal[2] of StreamPark for more detail. > > > > StreamPark is a streaming application development platform. Aimed at ease > > building and managing streaming applications, StreamPark provides > > scaffolding for writing streaming process logic with Apache Flink and > > Apache Spark. Also, StreamPark provides a dashboard for controlling and > > monitoring streaming tasks. It was initially known as StreamX and renamed > > to StreamPark in August 2022. > > > > StreamPark abstracts the environment and program parameters of task > > development and deployment in a convention over configuration manner for > > low code development. It initializes a runtime environment and context > and > > combines it with a series of connectors to simplify development. From the > > aspect of a task management platform, StreamPark is a streaming data > > management platform based on the JVM platform. > > > > So far, StreamPark has accumulated a few users, and the accrued download > > time is over 5,000. The representative users are Baidu, China Unicom, > > Ziroom, Yonghui Supermarket, InMobi, YTO Express, and so on. StreamPark > has > > built an open-source community with 52 developers and released over ten > > versions in the past year. > > > > The proposed initial committers are interested in joining ASF to increase > > the connections in the open-source world. Based on extensive > collaboration, > > it is possible to build a community of developers and committers that > live > > longer than the founder. Also, the Apache Brand can help encourage more > > organizations to use StreamPark more confidently. > > > > We believe that the StreamPark project will provide diversity value for > the > > community if StreamPark is introduced into the Apache incubator. > > > > I (@tison) will help this project as the champion and many thanks to four > > other mentors: > > > > * Willem Ning Jiang [ningji...@apache.org] > > * Stephan Ewen [se...@apache.org] > > * Thomas Weise [t...@apache.org] > > * Duo Zhang [zhang...@apache.org] > > > > Best, > > tison. > > > > [1] https://github.com/streamxhub/streamx > > [2] > > > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal > > > -- > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 >
Re: [DISCUSS] Incubating Proposal for StreamPark
I follow a previous proposal (Kvrocks) to send a digest to general@ while linking the complete proposal to https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal >_< Best, tison. tison 于2022年8月17日周三 10:34写道： > Hi Sheng, > > Thanks for your comments. I write the proposal just following the > template. Please specify exactly which section is in the wrong format or > missing. > > Best, > tison. > > > Sheng Wu 于2022年8月17日周三 10:26写道： > >> Hi, >> >> Could you reformat this proposal to follow the proposal template? There is >> something like project owner, dependencies, initial committers, >> experienced >> developers etc. are not clear right now. >> >> tison 于2022年8月17日 周三09:15写道： >> >> > Hi all, >> > >> > I would like to propose StreamPark[1] as a new apache incubator project, >> > you can find the proposal[2] of StreamPark for more detail. >> > >> > StreamPark is a streaming application development platform. Aimed at >> ease >> > building and managing streaming applications, StreamPark provides >> > scaffolding for writing streaming process logic with Apache Flink and >> > Apache Spark. Also, StreamPark provides a dashboard for controlling and >> > monitoring streaming tasks. It was initially known as StreamX and >> renamed >> > to StreamPark in August 2022. >> > >> > StreamPark abstracts the environment and program parameters of task >> > development and deployment in a convention over configuration manner for >> > low code development. It initializes a runtime environment and context >> and >> > combines it with a series of connectors to simplify development. From >> the >> > aspect of a task management platform, StreamPark is a streaming data >> > management platform based on the JVM platform. >> > >> > So far, StreamPark has accumulated a few users, and the accrued download >> > time is over 5,000. The representative users are Baidu, China Unicom, >> > Ziroom, Yonghui Supermarket, InMobi, YTO Express, and so on. StreamPark >> has >> > built an open-source community with 52 developers and released over ten >> > versions in the past year. >> > >> > The proposed initial committers are interested in joining ASF to >> increase >> > the connections in the open-source world. Based on extensive >> collaboration, >> > it is possible to build a community of developers and committers that >> live >> > longer than the founder. Also, the Apache Brand can help encourage more >> > organizations to use StreamPark more confidently. >> > >> > We believe that the StreamPark project will provide diversity value for >> the >> > community if StreamPark is introduced into the Apache incubator. >> > >> > I (@tison) will help this project as the champion and many thanks to >> four >> > other mentors: >> > >> > * Willem Ning Jiang [ningji...@apache.org] >> > * Stephan Ewen [se...@apache.org] >> > * Thomas Weise [t...@apache.org] >> > * Duo Zhang [zhang...@apache.org] >> > >> > Best, >> > tison. >> > >> > [1] https://github.com/streamxhub/streamx >> > [2] >> > >> https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal >> > >> -- >> Sheng Wu 吴晟 >> >> Apache SkyWalking >> Apache Incubator >> Apache ShardingSphere, ECharts, DolphinScheduler podlings >> Zipkin >> Twitter, wusheng1108 >> >
Re: Re: [DISCUSS] Incubating Proposal for StreamPark
Thanks for your feedback! I'm going to keep the discussion for a while and start a vote the next week. Best, tison. Mingyu Chen 于2022年8月18日周四 20:23写道： > +1 (non-binding) > Good to see StreamPark to join the Incubator. > > > > > -- > > 此致！Best Regards > 陈明雨 Mingyu Chen > > Email: > morning...@apache.org > > > > > > 在 2022-08-18 15:27:26，"Jark Wu" 写道： > >+1 (non-binding) > > > >StreamPark is a nice name. Good luck! > > > >Best, > >Jark Wu > > > >On 2022/08/18 01:50:10 Willem Jiang wrote: > >> It's my pleasure to be the mentor of StreamPark. > >> Please check out the proposal in the incubator wiki page and give your > >> feedback. > >> > >> Willem Jiang > >> > >> Twitter: willemjiang > >> Weibo: 姜宁willem > >> > >> On Wed, Aug 17, 2022 at 11:05 AM tison wrote: > >> > > >> > I follow a previous proposal (Kvrocks) to send a digest to general@ > while > >> > linking the complete proposal to > >> > > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal > >> > >_< > >> > > >> > Best, > >> > tison. > >> > > >> > > >> > >> - > >> 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: Re: [DISCUSS] Incubating Proposal for StreamPark
FYI, > 2. List initial committers with their GitHub accounts. It's updated in the proposal. Pick here: * [benjobs](https://github.com/wolfboys) [benj...@apache.org] * [Al-assad](https://github.com/Al-assad) [assad@outlook.com] * [xinzhuxiansheng](https://github.com/xinzhuxiansheng) [ xinzhuxianshen...@gmail.com] * [MonsterChenzhuo](https://github.com/MonsterChenzhuo) [ monster.zhuoyuc...@gmail.com] * [lvshaokang](https://github.com/lvshaokang) [lvshaoka...@gmail.com] * [monrg](https://github.com/monrg) [wangmo...@gmail.com] * [tamer.ning](https://github.com/GuoNingNing) [tamer.n...@gmail.com] Best, tison. Sheng Wu 于2022年8月19日周五 08:54写道： > Thanks for updating. I recommend to > 1. Fix headers > 2. List initial committers with their GitHub accounts. > 3. Add words about you have checked with major contributors, only the > listed ppl want to join the initial committer team, if you don't have > an open discussion(You just mentioned you asked, so I guess they are > all not public) > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > huajie wang 于2022年8月18日周四 23:30写道： > > > > Hi, Sheng. I'm benjobs the author of the StreamPark project. about the > > questions you mentioned: > > > > 1. Copyright statement problem, we will fix it. > > > > 2. About the initial committer: Currently there are 59 contributors. I > have > > tried to contact these 59 contributors. At present, only the 7 > contributors > > who are willing to become a committer have been contacted, and their code > > submission times, code volume and contribution value are ranked high > > > > 3. About ICLA: I have contacted all the top 20 contributors and will sign > > ICLA. Other contributors will try to contact. > > > > Sheng Wu 于2022年8月18日周四 22:16写道： > > > > > Several questions > > > > > > 1. Many source codes in the repository declare `Licensed to the Apache > > > Software Foundation (ASF)`[1], which is wrong. As an out-of-foundation > > > project, `licensed to the ASF`. Could you correct this? > > > The correct header should be like this > > > ``` > > > /* > > > * Copyright 2018 x > > > * > > > * Licensed under the Apache License, Version 2.0 (the "License"); > > > * you may not use this file except in compliance with the License. > > > * You may obtain a copy of the License at > > > * > > > * http://www.apache.org/licenses/LICENSE-2.0 > > > * > > > * Unless required by applicable law or agreed to in writing, software > > > * distributed under the License is distributed on an "AS IS" BASIS, > > > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or > implied. > > > * See the License for the specific language governing permissions and > > > * limitations under the License. > > > */ > > > ``` > > > 2. `com.streamxhub` is used for the package of source codes, as well > > > as `https://streamxhub.com/` <https://streamxhub.com/> < > https://streamxhub.com/> is used for > > > project website. Is > > > streamxhub a company/legal entity? Who or which company owns this > > > project? `.com` usually means a company. We may need an SGA in the > > > donation process. > > > 3. I can't see the initial committers' GitHub accounts, could you make > > > them clear in the proposal? > > > 4. I can see at least 59 GitHub accounts/contributors contributed to > > > this project, and the initial committer team has 7 members, how about > > > the other 52? Such as GitHub ID(xxyykkxx) #14 on the contributor list. > > > He/she has over 12k LOC. Would ppl like him/her to submit ICLA? > > > 5. How does this community/entity/org determine the initial committer > > > candidate? Would others be happy with the current candidate list? > > > Would others like to join the initial team? > > > > > > > > > > > > [1] > > > > https://github.com/streamxhub/streamx/blob/v1.0.0-beta.1/streamx-flink/streamx-flink-core/src/main/java/com/streamxhub/streamx/flink/core/java/function/HBaseQueryFunction.java#L4 > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > Sherlock Homles 于2022年8月18日周四 21:34写道： > > > > > > > > +1 (non-binding) > > > > > > > > StreamPark is a very great project. I have used it for a long time. > > > > > > > > tison 于2022年8月18日周四 21:15写道： > > > > > > > > > > Thanks for your feedback! I'm goin
Re: Re: [DISCUSS] Incubating Proposal for StreamPark
> Add words about you have checked with major contributors Added words in the "Initial Committers" section based on @benjobs's comment. Best, tison. tison 于2022年8月19日周五 08:59写道： > FYI, > > > 2. List initial committers with their GitHub accounts. > > It's updated in the proposal. Pick here: > > * [benjobs](https://github.com/wolfboys) [benj...@apache.org] > * [Al-assad](https://github.com/Al-assad) [assad@outlook.com] > * [xinzhuxiansheng](https://github.com/xinzhuxiansheng) [ > xinzhuxianshen...@gmail.com] > * [MonsterChenzhuo](https://github.com/MonsterChenzhuo) [ > monster.zhuoyuc...@gmail.com] > * [lvshaokang](https://github.com/lvshaokang) [lvshaoka...@gmail.com] > * [monrg](https://github.com/monrg) [wangmo...@gmail.com] > * [tamer.ning](https://github.com/GuoNingNing) [tamer.n...@gmail.com] > > Best, > tison. > > > Sheng Wu 于2022年8月19日周五 08:54写道： > >> Thanks for updating. I recommend to >> 1. Fix headers >> 2. List initial committers with their GitHub accounts. >> 3. Add words about you have checked with major contributors, only the >> listed ppl want to join the initial committer team, if you don't have >> an open discussion(You just mentioned you asked, so I guess they are >> all not public) >> >> Sheng Wu 吴晟 >> Twitter, wusheng1108 >> >> huajie wang 于2022年8月18日周四 23:30写道： >> > >> > Hi, Sheng. I'm benjobs the author of the StreamPark project. about the >> > questions you mentioned: >> > >> > 1. Copyright statement problem, we will fix it. >> > >> > 2. About the initial committer: Currently there are 59 contributors. I >> have >> > tried to contact these 59 contributors. At present, only the 7 >> contributors >> > who are willing to become a committer have been contacted, and their >> code >> > submission times, code volume and contribution value are ranked high >> > >> > 3. About ICLA: I have contacted all the top 20 contributors and will >> sign >> > ICLA. Other contributors will try to contact. >> > >> > Sheng Wu 于2022年8月18日周四 22:16写道： >> > >> > > Several questions >> > > >> > > 1. Many source codes in the repository declare `Licensed to the Apache >> > > Software Foundation (ASF)`[1], which is wrong. As an out-of-foundation >> > > project, `licensed to the ASF`. Could you correct this? >> > > The correct header should be like this >> > > ``` >> > > /* >> > > * Copyright 2018 x >> > > * >> > > * Licensed under the Apache License, Version 2.0 (the "License"); >> > > * you may not use this file except in compliance with the License. >> > > * You may obtain a copy of the License at >> > > * >> > > * http://www.apache.org/licenses/LICENSE-2.0 >> > > * >> > > * Unless required by applicable law or agreed to in writing, software >> > > * distributed under the License is distributed on an "AS IS" BASIS, >> > > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or >> implied. >> > > * See the License for the specific language governing permissions and >> > > * limitations under the License. >> > > */ >> > > ``` >> > > 2. `com.streamxhub` is used for the package of source codes, as well >> > > as `https://streamxhub.com/` <https://streamxhub.com/> < >> https://streamxhub.com/> is used for >> > > project website. Is >> > > streamxhub a company/legal entity? Who or which company owns this >> > > project? `.com` usually means a company. We may need an SGA in the >> > > donation process. >> > > 3. I can't see the initial committers' GitHub accounts, could you make >> > > them clear in the proposal? >> > > 4. I can see at least 59 GitHub accounts/contributors contributed to >> > > this project, and the initial committer team has 7 members, how about >> > > the other 52? Such as GitHub ID(xxyykkxx) #14 on the contributor list. >> > > He/she has over 12k LOC. Would ppl like him/her to submit ICLA? >> > > 5. How does this community/entity/org determine the initial committer >> > > candidate? Would others be happy with the current candidate list? >> > > Would others like to join the initial team? >> > > >> > > >> > > >> > > [1] >> > > >> https://github.com/strea
Re: Re: [DISCUSS] Incubating Proposal for StreamPark
Hi Chris, I checked out the official site of Apache StreamPipe (Incubator) whose slogan writes: > A self-service (Industrial) IoT toolbox to enable non-technical users to connect, analyze and explore IoT data streams. Basically, StreamPark is for technical users and it does not specifically focus on IoT scenarios. It's a streaming application development and management platform mainly supporting Flink & Spark streaming applications. Best, tison. Sheng Wu 于2022年8月19日周五 20:16写道： > Thanks for the update. My <1> - <5> should have been resolved. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > tison 于2022年8月19日周五 09:40写道： > > > > > Add words about you have checked with major contributors > > > > Added words in the "Initial Committers" section based on @benjobs's > comment. > > > > Best, > > tison. > > > > > > tison 于2022年8月19日周五 08:59写道： > > > > > FYI, > > > > > > > 2. List initial committers with their GitHub accounts. > > > > > > It's updated in the proposal. Pick here: > > > > > > * [benjobs](https://github.com/wolfboys) [benj...@apache.org] > > > * [Al-assad](https://github.com/Al-assad) [assad@outlook.com] > > > * [xinzhuxiansheng](https://github.com/xinzhuxiansheng) [ > > > xinzhuxianshen...@gmail.com] > > > * [MonsterChenzhuo](https://github.com/MonsterChenzhuo) [ > > > monster.zhuoyuc...@gmail.com] > > > * [lvshaokang](https://github.com/lvshaokang) [lvshaoka...@gmail.com] > > > * [monrg](https://github.com/monrg) [wangmo...@gmail.com] > > > * [tamer.ning](https://github.com/GuoNingNing) [tamer.n...@gmail.com] > > > > > > Best, > > > tison. > > > > > > > > > Sheng Wu 于2022年8月19日周五 08:54写道： > > > > > >> Thanks for updating. I recommend to > > >> 1. Fix headers > > >> 2. List initial committers with their GitHub accounts. > > >> 3. Add words about you have checked with major contributors, only the > > >> listed ppl want to join the initial committer team, if you don't have > > >> an open discussion(You just mentioned you asked, so I guess they are > > >> all not public) > > >> > > >> Sheng Wu 吴晟 > > >> Twitter, wusheng1108 > > >> > > >> huajie wang 于2022年8月18日周四 23:30写道： > > >> > > > >> > Hi, Sheng. I'm benjobs the author of the StreamPark project. about > the > > >> > questions you mentioned: > > >> > > > >> > 1. Copyright statement problem, we will fix it. > > >> > > > >> > 2. About the initial committer: Currently there are 59 > contributors. I > > >> have > > >> > tried to contact these 59 contributors. At present, only the 7 > > >> contributors > > >> > who are willing to become a committer have been contacted, and their > > >> code > > >> > submission times, code volume and contribution value are ranked high > > >> > > > >> > 3. About ICLA: I have contacted all the top 20 contributors and will > > >> sign > > >> > ICLA. Other contributors will try to contact. > > >> > > > >> > Sheng Wu 于2022年8月18日周四 22:16写道： > > >> > > > >> > > Several questions > > >> > > > > >> > > 1. Many source codes in the repository declare `Licensed to the > Apache > > >> > > Software Foundation (ASF)`[1], which is wrong. As an > out-of-foundation > > >> > > project, `licensed to the ASF`. Could you correct this? > > >> > > The correct header should be like this > > >> > > ``` > > >> > > /* > > >> > > * Copyright 2018 x > > >> > > * > > >> > > * Licensed under the Apache License, Version 2.0 (the "License"); > > >> > > * you may not use this file except in compliance with the > License. > > >> > > * You may obtain a copy of the License at > > >> > > * > > >> > > * http://www.apache.org/licenses/LICENSE-2.0 > > >> > > * > > >> > > * Unless required by applicable law or agreed to in writing, > software > > >> > > * distributed under the License is distributed on an "AS IS" > BASIS, > > >> > > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
Re: Re: [DISCUSS] Incubating Proposal for StreamPark
Thanks for your participation! I'll start a vote now. Best, tison. Goson zhang 于2022年8月24日周三 09:40写道： > +1 (non-binding), good luck! > > david zollo 于2022年8月23日周二 23:20写道： > > > if CCLA is signed, my problem is solved. > > > > > > > > Best Regards > > > > --- > > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC > > David > > Linkedin: https://www.linkedin.com/in/davidzollo > > Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy> > > --- > > > > > > On Mon, Aug 22, 2022 at 10:55 PM huajie wang wrote: > > > > > related notes: > > > > > > 1. StreamPark is my learning project in the early stage, Not a > > company-led > > > project and No company employees are involved > > > 2. StreamPark is open-sourced on GitHub on my behalf, no company is > > > associated with it > > > 3. I contacted the initial committers and contributors, they are all > > happy > > > to donate the project to asf, and agreed to sign the iCLA > > > 4. I will contact the companies to come forward and sign the CCLA > > > > > > > > > To sum up, the StreamPark project will be donated in the name of > > > individuals. StreamPark has been learning and practicing the Apache Way > > > since it was open-sourced. > > > We have built a small community, have a group of users, and are very > > > willing to donate StreamPark to the Apache foundation. > > > We are looking forward to building a more prosperous community by > > following > > > the Apache Way. Contribute to the development of the software. > > > > > > > > > Best, > > > benjobs > > > > > > > > > david zollo 于2022年8月21日周日 19:35写道： > > > > > > > I want to know about how do you understand no organization? If you > work > > > for > > > > a company, do you need to prove that this project is not > > company-related? > > > > > > > > > > > > > > > > Best Regards > > > > > > > > --- > > > > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC & Apache > > > > Incubator Mentor > > > > David > > > > Linkedin: https://www.linkedin.com/in/davidzollo > > > > Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy> > > > > --- > > > > > > > > > > > > On Thu, Aug 18, 2022 at 10:22 PM Sheng Wu > > > > > wrote: > > > > > > > > > Sheng Wu 于2022年8月18日周四 22:15写道： > > > > > > > > > > > > Several questions > > > > > > > > > > > > 1. Many source codes in the repository declare `Licensed to the > > > Apache > > > > > > Software Foundation (ASF)`[1], which is wrong. As an > > > out-of-foundation > > > > > > project, `licensed to the ASF`. Could you correct this? > > > > > > The correct header should be like this > > > > > > ``` > > > > > > /* > > > > > > * Copyright 2018 x > > > > > > * > > > > > > * Licensed under the Apache License, Version 2.0 (the > "License"); > > > > > > * you may not use this file except in compliance with the > License. > > > > > > * You may obtain a copy of the License at > > > > > > * > > > > > > * http://www.apache.org/licenses/LICENSE-2.0 > > > > > > * > > > > > > * Unless required by applicable law or agreed to in writing, > > > software > > > > > > * distributed under the License is distributed on an "AS IS" > > BASIS, > > > > > > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express > or > > > > > implied. > > > > > > * See the License for the specific language governing > permissions > > > and > > > > > > * limitations under the License. > > > > > > */ > > > > > > ``` > > > > > > 2. `com.streamxhub` is used for the package of source codes, as > > well > > > > > > as `https://streamxhub.com/` <https://streamxhub.com/> < > https://streamxhub.com/> < > > https://streamxhub.com/> < > > > https://streamxhub.com/> < > > > > https://
[VOTE] Accept StreamPark into the Apache Incubator
Hi all, Following up on the [DISCUSS] thread on StreamPark[1], I would like to call a VOTE to accept StreamPark into the Apache Incubator, please check out the StreamPark Proposal from the incubator wiki[2]. Please cast your vote: [ ] +1, bring StreamPark into the Incubator [ ] +0, I don't care either way [ ] -1, do not bring StreamPark into the Incubator, because... The vote will open at least for 72 hours, and only votes from the Incubator PMC are binding, but votes from everyone are welcome. Best, tison. [1] https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3 [2] https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal
Re: Re: [DISCUSS] Incubating Proposal for StreamPark
Please vote in the thread: https://lists.apache.org/thread/dowk7mtw26vg74qcpx4ttjvn9tkwt5qk Best, tison. tison 于2022年8月24日周三 11:49写道： > Thanks for your participation! I'll start a vote now. > > Best, > tison. > > > Goson zhang 于2022年8月24日周三 09:40写道： > >> +1 (non-binding), good luck! >> >> david zollo 于2022年8月23日周二 23:20写道： >> >> > if CCLA is signed, my problem is solved. >> > >> > >> > >> > Best Regards >> > >> > --- >> > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC >> > David >> > Linkedin: https://www.linkedin.com/in/davidzollo >> > Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy> >> > --- >> > >> > >> > On Mon, Aug 22, 2022 at 10:55 PM huajie wang wrote: >> > >> > > related notes: >> > > >> > > 1. StreamPark is my learning project in the early stage, Not a >> > company-led >> > > project and No company employees are involved >> > > 2. StreamPark is open-sourced on GitHub on my behalf, no company is >> > > associated with it >> > > 3. I contacted the initial committers and contributors, they are all >> > happy >> > > to donate the project to asf, and agreed to sign the iCLA >> > > 4. I will contact the companies to come forward and sign the CCLA >> > > >> > > >> > > To sum up, the StreamPark project will be donated in the name of >> > > individuals. StreamPark has been learning and practicing the Apache >> Way >> > > since it was open-sourced. >> > > We have built a small community, have a group of users, and are very >> > > willing to donate StreamPark to the Apache foundation. >> > > We are looking forward to building a more prosperous community by >> > following >> > > the Apache Way. Contribute to the development of the software. >> > > >> > > >> > > Best, >> > > benjobs >> > > >> > > >> > > david zollo 于2022年8月21日周日 19:35写道： >> > > >> > > > I want to know about how do you understand no organization? If you >> work >> > > for >> > > > a company, do you need to prove that this project is not >> > company-related? >> > > > >> > > > >> > > > >> > > > Best Regards >> > > > >> > > > --- >> > > > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC & Apache >> > > > Incubator Mentor >> > > > David >> > > > Linkedin: https://www.linkedin.com/in/davidzollo >> > > > Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy> >> > > > --- >> > > > >> > > > >> > > > On Thu, Aug 18, 2022 at 10:22 PM Sheng Wu < >> wu.sheng.841...@gmail.com> >> > > > wrote: >> > > > >> > > > > Sheng Wu 于2022年8月18日周四 22:15写道： >> > > > > > >> > > > > > Several questions >> > > > > > >> > > > > > 1. Many source codes in the repository declare `Licensed to the >> > > Apache >> > > > > > Software Foundation (ASF)`[1], which is wrong. As an >> > > out-of-foundation >> > > > > > project, `licensed to the ASF`. Could you correct this? >> > > > > > The correct header should be like this >> > > > > > ``` >> > > > > > /* >> > > > > > * Copyright 2018 x >> > > > > > * >> > > > > > * Licensed under the Apache License, Version 2.0 (the >> "License"); >> > > > > > * you may not use this file except in compliance with the >> License. >> > > > > > * You may obtain a copy of the License at >> > > > > > * >> > > > > > * http://www.apache.org/licenses/LICENSE-2.0 >> > > > > > * >> > > > > > * Unless required by applicable law or agreed to in writing, >> > > software >> > > > > > * distributed under the License is distributed on an "AS IS" >> > BASIS, >> > > > > > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express >> or >> > > > > impl
Re: [VOTE] Accept StreamPark into the Apache Incubator
Hi, I already replied to the comment about StreamPipe in the discussion thread: > Hi Chris, > > I checked out the official site of Apache StreamPipe (Incubator) whose slogan writes: > >> A self-service (Industrial) IoT toolbox to enable non-technical users to connect, analyze and explore IoT data streams. > > Basically, StreamPark is for technical users and it does not specifically focus on IoT scenarios. It's a streaming application development and management platform mainly supporting Flink & Spark streaming applications. > Do you need to prove that this project is not company-related? I think this topic was also answered in the discussion thread. Please read through it: https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3 Best, tison. tksonjk tk 于2022年8月24日周三 12:26写道： > -1, (non-binding) > > Hmmm how does it differentiate to what StreamPipes does? Can you explain in > detail, thanks. and if you work for > a company, do you need to prove that this project is not company-related? > > On 2022/08/24 03:55:26 tison wrote: > > Hi all, > > > > Following up on the [DISCUSS] thread on StreamPark[1], I would like to > call > > a VOTE to accept StreamPark into the Apache Incubator, please check out > the > > StreamPark Proposal from the incubator wiki[2]. > > > > Please cast your vote: > > > > [ ] +1, bring StreamPark into the Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring StreamPark into the Incubator, because... > > > > The vote will open at least for 72 hours, and only votes from the > Incubator > > PMC are binding, but votes from everyone are welcome. > > > > Best, > > tison. > > > > [1] https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3 > > [2] > > > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal > > >
Re: [DISCUSS] Incubating Proposal for StreamPark
Hi JB, With Beam: Beam provides a unified programming model (dataflow), while StreamPark is a platform to package, deploy and operate streaming applications. I'm not quite familiar with Wayang and NiFi, though. Best, tison. Jean-Baptiste Onofré 于2022年8月25日周四 13:26写道： > Hi, > > Interesting proposal. How do you compare StreamPark with Apache Beam, > Wayang, NiFI ? > > Thanks > > Regards > JB > > On Wed, Aug 17, 2022 at 3:13 AM tison wrote: > > > > Hi all, > > > > I would like to propose StreamPark[1] as a new apache incubator project, > > you can find the proposal[2] of StreamPark for more detail. > > > > StreamPark is a streaming application development platform. Aimed at ease > > building and managing streaming applications, StreamPark provides > > scaffolding for writing streaming process logic with Apache Flink and > > Apache Spark. Also, StreamPark provides a dashboard for controlling and > > monitoring streaming tasks. It was initially known as StreamX and renamed > > to StreamPark in August 2022. > > > > StreamPark abstracts the environment and program parameters of task > > development and deployment in a convention over configuration manner for > > low code development. It initializes a runtime environment and context > and > > combines it with a series of connectors to simplify development. From the > > aspect of a task management platform, StreamPark is a streaming data > > management platform based on the JVM platform. > > > > So far, StreamPark has accumulated a few users, and the accrued download > > time is over 5,000. The representative users are Baidu, China Unicom, > > Ziroom, Yonghui Supermarket, InMobi, YTO Express, and so on. StreamPark > has > > built an open-source community with 52 developers and released over ten > > versions in the past year. > > > > The proposed initial committers are interested in joining ASF to increase > > the connections in the open-source world. Based on extensive > collaboration, > > it is possible to build a community of developers and committers that > live > > longer than the founder. Also, the Apache Brand can help encourage more > > organizations to use StreamPark more confidently. > > > > We believe that the StreamPark project will provide diversity value for > the > > community if StreamPark is introduced into the Apache incubator. > > > > I (@tison) will help this project as the champion and many thanks to four > > other mentors: > > > > * Willem Ning Jiang [ningji...@apache.org] > > * Stephan Ewen [se...@apache.org] > > * Thomas Weise [t...@apache.org] > > * Duo Zhang [zhang...@apache.org] > > > > Best, > > tison. > > > > [1] https://github.com/streamxhub/streamx > > [2] > > > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Incubating Proposal for StreamPark
> How about simply changing to Postgres? There is an ongoing issue as mentioned above https://github.com/streamxhub/streampark/issues/1447. @Cheng Pan If you'd like to discuss more on dependencies policy, you can start a dedicated thread. @Justin & @Calvin Please note that Cheng Pan's comment is their own question, which isn't associated with StreamPark's situation. As @benjobs replied in https://lists.apache.org/thread/ql5k7j72p2s6hrw6clgpbwp4kmznj1b8, is the category X issue resolved? I can see that MySQL isn't a hard dependency to deliver the platform. Best, tison. Christofer Dutz 于2022年8月25日周四 16:40写道： > How about simply changing to Postgres? > I wouldn't expect StreamPark to depend on some MySQL special features. > Simply changing to Postgres should probably resolve the problem, right? > > Chris > > On 25.08.22, 08:43, "Calvin Kirs" wrote: > > Yes, this is consistent with what Justin said. If he is optional, then > OK. I misunderstood what you meant by 1 :( > But if the software does not work without mysql, even if you remove it > (mysql) when you distribute it, and then leave it to users to add it > themselves. > that's not okay either > > Cheng Pan 于2022年8月25日周四 14:33写道： > > > > > 1. the project hardly depends on mysql-connector, w/o > mysql-connector, > > > the project can not work totally. > > > 2. some optional functionalities of the project require > > > mysql-connector, w/o mysql-connector, the project still works. > > > 3. the project use mysql-connector for testing-only purpose, > > > mysql-connector is not required in runtime at all, e.g. the project > > > implements MySQL transport protocol, it uses mysql-connector for > > > testing to ensure compatibility. > > > > Thanks Calvin, from my understanding of [1], 2 and 3 are allowed, > but 1 is not. > > > > [1] https://apache.org/legal/resolved.html#optional > > > > Thanks, > > Cheng Pan > > > > On Thu, Aug 25, 2022 at 2:04 PM tison wrote: > > > > > > Hi JB, > > > > > > With Beam: Beam provides a unified programming model (dataflow), > while > > > StreamPark is a platform to package, deploy and operate streaming > > > applications. > > > > > > I'm not quite familiar with Wayang and NiFi, though. > > > > > > Best, > > > tison. > > > > > > > > > Jean-Baptiste Onofré 于2022年8月25日周四 13:26写道： > > > > > > > Hi, > > > > > > > > Interesting proposal. How do you compare StreamPark with Apache > Beam, > > > > Wayang, NiFI ? > > > > > > > > Thanks > > > > > > > > Regards > > > > JB > > > > > > > > On Wed, Aug 17, 2022 at 3:13 AM tison > wrote: > > > > > > > > > > Hi all, > > > > > > > > > > I would like to propose StreamPark[1] as a new apache > incubator project, > > > > > you can find the proposal[2] of StreamPark for more detail. > > > > > > > > > > StreamPark is a streaming application development platform. > Aimed at ease > > > > > building and managing streaming applications, StreamPark > provides > > > > > scaffolding for writing streaming process logic with Apache > Flink and > > > > > Apache Spark. Also, StreamPark provides a dashboard for > controlling and > > > > > monitoring streaming tasks. It was initially known as StreamX > and renamed > > > > > to StreamPark in August 2022. > > > > > > > > > > StreamPark abstracts the environment and program parameters of > task > > > > > development and deployment in a convention over configuration > manner for > > > > > low code development. It initializes a runtime environment and > context > > > > and > > > > > combines it with a series of connectors to simplify > development. From the > > > > > aspect of a task management platform, StreamPark is a > streaming data > > > > > management platform based on the JVM platform. > > > > > > > > > > So far, StreamPark has accumulated a few users, and the > accrued download > > &
Re: [DISCUSS] Incubating Proposal for StreamPark
Hi @Sheng @Justin @Cheng @Clavin, Thanks for your comments so far. If there's no more concern from your point of view, you're welcome to vote in the vote thread[1]. Best, tison. [1] https://lists.apache.org/thread/dowk7mtw26vg74qcpx4ttjvn9tkwt5qk
Re: [VOTE] Accept StreamPark into the Apache Incubator
Thanks for your reply :) I second what Julian and Dave said. IIRC in the Uniffle proposal, Justin had a similar statement[1]. StreamPark has its own users and the developers want to build a better community around it under sponsoring and mentoring of the Apache Incubator. This is good and why convinces me to act as the champion. I don't recognize the -1s for why not merge to project X, but let me talk about some technology here: 1. For StreamPipes, I replied several times that StreamPark doesn't focus on IoT scenarios and for technical people, while StreamPipes clearly writes that it's optimal for IoT scenario and for non-technical people. 2. For InLong, I'm one of the PMC members of InLong since the first day when it joined the Incubator. InLong describes itself as a one-stop integration framework for massive data. It's aimed at a good scenario while StreamPark provides a platform for packaging, deploying, and monitoring streaming applications. InLong is previously TubeMQ, I suggest you read the original proposal thread and especially the part of comparation of other messaging queues/streaming systems[2]. Softwares do have some overlaps with different focuses. I like JB's comment asking about the difference between StreamPark with other related projects and helping people to understand the project better. It's not a reason to object to the incubator proposal, though. To @Julian & @Dave: You're welcome to comment on the discussion thread about anything that is still a concern from accepting the proposal. You're welcome to vote in the voting thread. Best, tison. [1] https://lists.apache.org/thread/747tdt8hfmtzcpwqhll27l8k5n8pdhrl [2] https://lists.apache.org/thread/2o8zygdtg6nm56ld9kf3hlqtbnzjx3gj Dave Fisher 于2022年8月29日周一 05:00写道： > Hi Julian, > > This is very true. I’m also dismayed by -1 votes based on not yet having > explicit plans on removing LGPL/GPL dependencies. Following Apache Release > policy is a to do to learn during Incubation. The real question is if the > community accepts that their release cycle will be slowed. > > Best, > Dave > > Sent from my iPhone > > > On Aug 28, 2022, at 1:45 PM, Julian Hyde wrote: > > > > A few people on this thread are voting -1 with the rationale that > > StreamPark is similar to existing projects. This is not a valid > > reason. Apache does not try to ensure that projects don't overlap. > > > > The 'community over code' mantra holds true: Apache does not pick > > technologies, it builds communities. There are many examples of > > 'overlapping' projects that have built their own communities and > > flourished (HTTP Server vs Tomcat, Spark vs Flink, Druid vs Pinot, ORC > > vs Parquet). > > > > Julian > > > > > >> On Sun, Aug 28, 2022 at 12:17 PM Zur Aviem wrote: > >> > >> -1, > >> > >> Apache InLong[1] is a one-stop integration framework for massive data > that > >> provides automatic, secure and reliable data transmission capabilities. > >> InLong supports both batch and stream data processing at the same time, > >> which offers great power to build data analysis, modeling and other > >> real-time applications based on streaming data. > >> > >> The streamxhub[2] aims to make stream processing easier! easy-to-use > stream > >> processing application development framework and one-stop stream > processing > >> operation platform. > >> > >> From my side, the planning and design of Apache Inlong and streamxhub > >> projetc is consistent. Is it necessary to create a new project? > >> > >> And there are still many problems that have not been solved in the > >> discussion email[3]. > >> > >> Kind Regards, > >> Beam, Aviem Zur > >> > >> [1] https://inlong.apache.org/ > >> [2] https://github.com/streamxhub/streampark > >> [3] https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3 > >> > >>> On 2022/08/24 03:55:26 tison wrote: > >>> Hi all, > >>> > >>> Following up on the [DISCUSS] thread on StreamPark[1], I would like to > >> call > >>> a VOTE to accept StreamPark into the Apache Incubator, please check out > >> the > >>> StreamPark Proposal from the incubator wiki[2]. > >>> > >>> Please cast your vote: > >>> > >>> [ ] +1, bring StreamPark into the Incubator > >>> [ ] +0, I don't care either way > >>> [ ] -1, do not bring StreamPark into the Incubator, because... > >>> > >>> The vote will open at least for 72 hour
Re: [VOTE] Accept StreamPark into the Apache Incubator
Hi Zhuoyu, The mailing list cannot render images embedded. You can attach the file or send a link to CDN for images. If it's a screenshot for some content, you can just paste the content which is better for reading and (partial) referencing. Best, tison. 陈卓宇 于2022年8月29日周一 11:27写道： > The Streampark development community reacted quickly to the compliance > issues and now looks to have converged on completion, which is something we > should see. > [image: 图片.png] > > > Justin Mclean 于2022年8月29日周一 10:45写道： > >> Hi, >> >> There is no issue in having a project that does something similar as >> another project, that in itself is no reason to vote -1. It is useful to >> discuss overlap and perhaps work out were projects could complement each >> other or even if possible reuse code. >> >> Kind Regards, >> Justin >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
Re: Re: [VOTE] Accept StreamPark into the Apache Incubator
+1 (binding) Best, tison. Liu Ted 于2022年8月24日周三 23:08写道： > +1 (binding) > Best regards,, > > Ted Liu > > 2022 年 8 月 24 日周三 21:12，Thomas Weise 写道： +1 (binding) > > Thanks, > Thomas > > > On Wed, Aug 24, 2022 at 3:08 AM Kelu Tao wrote: > > > +1 (non-binding) > > > > Good Luck! > > > > On 2022/08/24 03:55:26 tison wrote: > > > Hi all, > > > > > > Following up on the [DISCUSS] thread on StreamPark[1], I would like to > > call > > > a VOTE to accept StreamPark into the Apache Incubator, please check out > > the > > > StreamPark Proposal from the incubator wiki[2]. > > > > > > Please cast your vote: > > > > > > [ ] +1, bring StreamPark into the Incubator > > > [ ] +0, I don't care either way > > > [ ] -1, do not bring StreamPark into the Incubator, because... > > > > > > The vote will open at least for 72 hours, and only votes from the > > Incubator > > > PMC are binding, but votes from everyone are welcome. > > > > > > Best, > > > tison. > > > > > > [1] https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3 > > > [2] > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > >
Re: Re: [VOTE] Accept StreamPark into the Apache Incubator
The voting thread looks fragmented in some mail clients (like Gmail). I'd like to make a summary of the current state so that we don't deadlock here: +1 bindings: Thomas Weise Ted Liu +1 non-bindings: Zhuoyu Chen Qingrong wang shaokang lv benjobs Sherlock Homles hulk Jiafeng.Zhang 郭宁 Kelu Tao -1 bindings: Justin Mclean -1 non-bindings: tksonjk tk Zur Aviem All concerns thrown by -1s are answered. I'd like to learn if there're still some blockers. Also, cc the nominated mentors to help with voting in this thread. Best, tison. tison 于2022年8月30日周二 10:37写道： > +1 (binding) > > Best, > tison. > > > Liu Ted 于2022年8月24日周三 23:08写道： > >> +1 (binding) >> Best regards,, >> >> Ted Liu >> >> 2022 年 8 月 24 日周三 21:12，Thomas Weise 写道： +1 (binding) >> >> Thanks, >> Thomas >> >> >> On Wed, Aug 24, 2022 at 3:08 AM Kelu Tao wrote: >> >> > +1 (non-binding) >> > >> > Good Luck! >> > >> > On 2022/08/24 03:55:26 tison wrote: >> > > Hi all, >> > > >> > > Following up on the [DISCUSS] thread on StreamPark[1], I would like to >> > call >> > > a VOTE to accept StreamPark into the Apache Incubator, please check >> out >> > the >> > > StreamPark Proposal from the incubator wiki[2]. >> > > >> > > Please cast your vote: >> > > >> > > [ ] +1, bring StreamPark into the Incubator >> > > [ ] +0, I don't care either way >> > > [ ] -1, do not bring StreamPark into the Incubator, because... >> > > >> > > The vote will open at least for 72 hours, and only votes from the >> > Incubator >> > > PMC are binding, but votes from everyone are welcome. >> > > >> > > Best, >> > > tison. >> > > >> > > [1] https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3 >> > > [2] >> > > >> > >> https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal >> > > >> > >> > - >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> > For additional commands, e-mail: general-h...@incubator.apache.org >> > >> > >> >>
Re: [VOTE] Accept StreamPark into the Apache Incubator
Thanks for your participation! I'm closing this voting thread now and summarizing the result. Best, tison. Jiafeng.Zhang 于2022年8月31日周三 22:12写道： > +1 (non-binding) > Good luck! > > Jiafeng.Zhang > Email: jiafengzh...@apache.org > > Jia Fan 于2022年8月31日 周三18:38写道： > > > +1 (non-binding) > > Good luck! > > > > hulk 于2022年8月31日周三 16:28写道： > > > > > +1 (non-binding) > > > > > > Good luck! > > > > > > On Wed, 31 Aug 2022 at 16:26, Stephan Ewen wrote: > > > > > > > +1 (binding) > > > > > > > > Thank you for kicking off this interesting project! > > > > > > > > Best of luck with the project! > > > > > > > > On 2022/08/24 03:55:26 tison wrote: > > > > > Hi all, > > > > > > > > > > Following up on the [DISCUSS] thread on StreamPark[1], I would like > > to > > > > call > > > > > a VOTE to accept StreamPark into the Apache Incubator, please check > > out > > > > the > > > > > StreamPark Proposal from the incubator wiki[2]. > > > > > > > > > > Please cast your vote: > > > > > > > > > > [ ] +1, bring StreamPark into the Incubator > > > > > [ ] +0, I don't care either way > > > > > [ ] -1, do not bring StreamPark into the Incubator, because... > > > > > > > > > > The vote will open at least for 72 hours, and only votes from the > > > > Incubator > > > > > PMC are binding, but votes from everyone are welcome. > > > > > > > > > > Best, > > > > > tison. > > > > > > > > > > [1] > https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3 > > > > > [2] > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > > -- > > > Best Regards, > > > - *Hulk Lin* > > > > > > -- > 张家峰 >
[RESULT][VOTE] Accept StreamPark into the Apache Incubator
Hi all, Thanks to everyone who participated in the vote. The voting is now closed and it has passed with 8 binding +1, 12 non-binding +1, and no 0 or -1 bindings votes. two -1 non-binding votes are answered. +1 bindings: Thomas Weise Ted Liu tison Justin Mclean Willem Jiang Duo Zhang Junping Du Stephan Ewen +1 non-bindings: Zhuoyu Chen Qingrong wang shaokang lv benjobs Sherlock Homles hulk 郭宁 Kelu Tao Xiao Yu Dominik Riemer Jia Fan Jiafeng Zhang -1 non-bindings: tksonjk tk Zur Aviem Best, tison.
Re: [VOTE] Graduate Apache MXNet to a TLP
+1 (binding) Best, tison. david zollo 于2022年9月1日周四 00:25写道： > +1 (binding) > > > Best Regards > > --- > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC > David > Linkedin: https://www.linkedin.com/in/davidzollo > Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy> > --- > > > On Thu, Aug 25, 2022 at 1:27 PM Jean-Baptiste Onofré > wrote: > > > +1 (binding) > > > > Regards > > JB > > > > On Wed, Aug 17, 2022 at 4:40 PM Joe Evans > wrote: > > > > > > Hi Apache Incubator community, > > > > > > The Apache MXNet (incubating) community has discussed[1] graduating to > a > > > top level project and passed a community vote[2][3]. We have also > > > discussed[4] graduating in the Incubator community. > > > > > > In the incubator discussion, some branding issues[5] were brought up. > We > > > have fixed the issues[6] we were able to and discussed the others with > > > trademarks@. This work is ongoing. In addition, a few website > issues[7] > > > were brought up which were subsequently resolved[8]. > > > > > > Based on the positive feedback from the incubator discussion, we would > > like > > > to start a vote on graduating Apache MXNet (incubating) to a top level > > > project. > > > > > > Please cast your vote as one of the following options: > > > > > > [ ] +1 Yes, I support Apache MXNet (incubating) graduating from the > > Apache > > > Incubator to a top level project. > > > > > > [ ] +0 No opinion. > > > > > > [ ] -1 No, the Apache MXNet (incubating) project is not ready to > > graduate, > > > because ... > > > > > > This vote will remain open for at least 72 hours. > > > > > > Here is a brief overview of the progress of the Apache MXNet > (incubating) > > > project and community since entering the incubator: > > > > > > Community > > > > > >- > > > > > >38 new PPMC members were added, bringing the total number of PPMC > > >members to 51 > > >- > > > > > >56 new committers were added (which include new PPMC members), > > bringing > > >the total number of committers to 87 > > >- > > > > > >The total number of contributors is now 870 and growing. > > > > > > Project > > > > > >- > > > > > >18 releases by 13 different release managers. All compliance issues > > have > > >been resolved with the 1.9.0 and 2.0.beta releases. > > >- > > > > > >MXNet website is now compliant with Apache Project Website > > requirements > > >- > > > > > >MXNet has completed the project maturity self assessment[9] > > > > > > > > > References: > > > > > > [1] https://lists.apache.org/thread/l9h2qgb2vqs2y0cm46wh83sgomr9w190 > > > > > > [2] https://lists.apache.org/thread/py1nw6whov78sch5kkm1gcg7cv3zb2sv > > > > > > [3] https://lists.apache.org/thread/b8bngc6qcb33n0jo6m1rw0ylwlqzkmgx > > > > > > [4] https://lists.apache.org/thread/3rxzjcmo2y457y6r8ohz1j4qv49joyo6 > > > > > > [5] https://lists.apache.org/thread/6brq4jg1x3hnt0sr3phboh2vwoo33db1 > > > > > > [6] https://github.com/apache/incubator-mxnet/issues/21036 > > > > > > [7] https://lists.apache.org/thread/j29jcv0zdkvx7vyy701qnfhnj09fzv8o > > > > > > [8] https://github.com/apache/incubator-mxnet/issues/21054 > > > > > > [9] > > > > > > https://cwiki.apache.org/confluence/display/MXNET/Apache+Maturity+Model+Assessment+for+MXNet > > > > > > > > > Here is the proposed resolution: > > > > > > —-- > > > > > > Establish the Apache MXNet Project > > > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > > > > > the Foundation and consistent with the Foundation's purpose to > establish > > > > > > a Project Management Committee charged with the creation and > maintenance > > > > > > of open-source software, for distribution at no charge to the public, > > > > > > related to a flexible and efficient library for Deep Learning. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Proje
Re: [DISCUSS] Incubating Proposal for Datark
Hi Gabriel, > Datark became a popular remote shuffle service in the past few years and > I'm very glad to see it will be one of us soon. Out of curiosity, I can see the history of this project starts from Dec. 2021. How can it be a popular solution for years? Best, tison. Yu Li 于2022年9月27日周二 14:05写道： > Hi BLAST and Kaijie, > > Yes, we've done quite some work on merging the two rss projects (or more > accurately, try to extract the high-level architecture and interfaces to > form a more general framework) but still not fully completed. However, on > second thought, we feel incubating the project first and involving more > community forces to discuss and complete the work together might be a > better idea. I believe more information on this topic will be shared in the > community, and further discussion and the incubation process won't block > each other. Wdyt? > > @Gon > Apache Nemo is an interesting project and we will further investigate and > search for the cooperation between the two projects (smile). > > Best Regards, > Yu > > > On Tue, 27 Sept 2022 at 10:45, Kaijie Chen wrote: > > > Hi Yu, > > > > You mentioned you will merge RemoteShuffleService and > flink-remote-shuffle > > previously in this thread: > > > > https://lists.apache.org/thread/1w74z5f0pb7bhslhzcl5x7rdj9s9objz > > > > > Our proposal is still not fully prepared because the merge of the two > > projects > > > is still in progress > > > > Have you done the merge? Or is there a plan to merge them later? > > I just checked the github repositories, seems there is no mention of the > > merge > > and both project are still being actively developed. > > > > Best, > > Kaijie > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [DISCUSS] Incubating Proposal for Datark
Hi Gabriel, Thanks for your explanation! Best, tison. Gabriel Lee 于2022年9月27日周二 16:25写道： > Hi Tison, > > Thanks for your curiosity. > > To be clear, as I know, RSS[1] was born in 2019 and has grown rapidly from > then. RSS was open-sourced in Dec, 2021 [2]. But before this, RSS has > already become a commercialized product on Alibaba Cloud EMR and attracts > lots of attention from cloud customers. You can refer to [3] for more > details if you want. > > Best, > Gabriel > > [1] https://www.alibabacloud.com/help/en/e-mapreduce/latest/rss-new > [2] https://github.com/alibaba/RemoteShuffleService > [3] https://www.51cto.com/article/699346.html > > On Tue, 27 Sept 2022 at 15:45, tison wrote: > > > Hi Gabriel, > > > > > Datark became a popular remote shuffle service in the past few years > and > > > I'm very glad to see it will be one of us soon. > > > > Out of curiosity, I can see the history of this project starts from Dec. > > 2021. How can it be a popular solution for years? > > > > Best, > > tison. > > > > > > Yu Li 于2022年9月27日周二 14:05写道： > > > > > Hi BLAST and Kaijie, > > > > > > Yes, we've done quite some work on merging the two rss projects (or > more > > > accurately, try to extract the high-level architecture and interfaces > to > > > form a more general framework) but still not fully completed. However, > on > > > second thought, we feel incubating the project first and involving more > > > community forces to discuss and complete the work together might be a > > > better idea. I believe more information on this topic will be shared in > > the > > > community, and further discussion and the incubation process won't > block > > > each other. Wdyt? > > > > > > @Gon > > > Apache Nemo is an interesting project and we will further investigate > and > > > search for the cooperation between the two projects (smile). > > > > > > Best Regards, > > > Yu > > > > > > > > > On Tue, 27 Sept 2022 at 10:45, Kaijie Chen wrote: > > > > > > > Hi Yu, > > > > > > > > You mentioned you will merge RemoteShuffleService and > > > flink-remote-shuffle > > > > previously in this thread: > > > > > > > > https://lists.apache.org/thread/1w74z5f0pb7bhslhzcl5x7rdj9s9objz > > > > > > > > > Our proposal is still not fully prepared because the merge of the > two > > > > projects > > > > > is still in progress > > > > > > > > Have you done the merge? Or is there a plan to merge them later? > > > > I just checked the github repositories, seems there is no mention of > > the > > > > merge > > > > and both project are still being actively developed. > > > > > > > > Best, > > > > Kaijie > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > >
Re: possible interest in forming a community fork of akka
Hi PJ, Thanks for driving this discussion! As mentioned above, Lightbend switched the license from upstream and we simply _cannot_ backport code from there any longer. However, it's reasonable to me that we start a new project based on the latest APL-2.0 licensed version (forked) to save users depending on Akka open-source ecosystem to get further bugfixes and new features. Given that there're a number of volunteers for this initiative, I believe it is worth a try to revive the open-source project: 1. We need a new name here. IIUC "akka" will cause legal issues. 2. The aim of this project should be declared in the first place, especially about new features and breaking changes. TrinoDB forked from PrestoDB can be a good pioneer to learn from. > "hostile forks" The answer of the second question listed above should answer this question also. My perspective is that the initial purpose of this project is to save users depending on Akka open-source ecosystem and it's community driven. > If anyone else in the Incubator PMC would like to get involved, that > would be great. The same as Roman :) Count me in. I'd like to be involved all the way in this effort. Best, tison. PJ Fanning 于2022年9月27日周二 17:39写道： > Thanks Ralph for looking at this. > > It is early days but a number of people have expressed an interest in > joining the new community. > > https://github.com/mdedetrich/akka-apache-project/discussions/3 > > There are some former Lightbend employees and some very active > contributors. Most of the people appear to have contributed to akka or > to related projects. > > So far, it looks like quite a diverse group with no company or > interest group having too great a say. > > There are other discussions, including ones about goals and release > plans at https://github.com/mdedetrich/akka-apache-project/discussions > > On Mon, 26 Sept 2022 at 23:25, Ralph Goers > wrote: > > > > Before going too far with this I would be interested to know: > > 1. Who the initial committers/PMC members would be. > > 2. How much familiarity the proposed people already have with the code > base. > > 3. How diverse the community is from an employment point of view. > > > > In other words, I would be concerned if this is pushed by just 3 or 4 > people, > > none of which have ever spent much time in the code, and who all work for > > the same employer. > > > > Ralph > > > > > On Sep 26, 2022, at 11:11 AM, PJ Fanning wrote: > > > > > > Hi everyone, > > > > > > Apologies if this is not the right mailing list. If it is not, please > > > let me know and I'll switch the thread to the right list. > > > > > > Lighbend [1], the company that maintains the popular open source > > > framework, Akka [2], recently announced they are moving Akka to a > > > non-OSS commercial license [3]. > > > > > > There is interest in the OSS community in forking Akka under a new > > > name and maintaining it as an ASF project [4]. > > > > > > It is early days yet but there is some discussion online [5]. > > > > > > Reading the incubator cookbook, a new podling would need to have > > > champions and mentors from within the Incubator PMC [6]. > > > > > > I would like to put my name forward for such a role, as an existing > > > ASF member [7]. > > > > > > If anyone else in the Incubator PMC would like to get involved, that > > > would be great. > > > > > > Regards, > > > PJ > > > > > > [1] https://www.lightbend.com/ > > > [2] https://akka.io/ > > > [3] https://www.lightbend.com/akka/license-faq > > > [4] https://github.com/mdedetrich/akka-apache-project > > > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 > > > [6] > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator > > > [7] https://whimsy.apache.org/roster/committer/fanningpj > > > > > > - > > > 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: [DISCUSS] Incubating Proposal for Pekko
Hi Claude, Thanks for starting this discussion! +1 to this proposal. It answers my previous questions on https://lists.apache.org/thread/hdknoyvr9c0d4j70xqw6t2t7gnbzc7nq a new name + a clear goal. I'm interested to act as a mentor to help with this podling's growth. w.r.t the membership, I notice that Claude Warren and PJ Fanning are listed on both initial committers and mentors, while other mentors don't. Perhaps you should check what's the intention here. Also, Claude Warren (you) and PJ Fanning are Apache members who can become IPMC members with a notice, but it still needs to go through the process[1][2]. Best, tison. [1] https://incubator.apache.org/guides/roles_and_responsibilities.html#incubator_project_management_committee_ipmc [2] https://lists.apache.org/thread/t6k3mg97pyshzoxzjg4c62n166l3crcw Jean-Baptiste Onofré 于2022年9月29日周四 23:36写道： > Hi Claude > > Very interesting. I would be more than happy to mentor this podling (if > accepted of course). > > I will take a deeper look on the proposal wiki page. > > Thanks ! > > Regards > JB > > Le jeu. 29 sept. 2022 à 16:57, Claude Warren, Jr > a écrit : > > > Greetings, > > > > I would like to propose Pekko [1] as a new Apache Incubator project. > > > > Pekko is a toolkit that brings the actor model (popularised by Erlang) to > > the JVM, providing the basis for building both locally and distributed > > concurrency. On top of this Pekko provides a rich set of libraries built > on > > top of Actors to solve modern problems, including: > > > > > >- Streams: Fully bi-directional backpressured streams following the > >Reactive manifesto > >- HTTP: A fully streamed HTTP client/server built on top of streams > that > >also provides expected tools (such as connection pooling) necessary > for > >highly available web services > >- connectors: A rich set of connectors for various databases, > messaging, > >persistent services built on top of streams > >- grpc: A gRPC server/client > >- projection: Provides abstractions necessary for CQRS pattern such as > >envelope, necessary for systems such as Kafka. > > > > > > > > Controversially Pekko is a fork of the Akka project just prior to its > > licence changed from Apache 2 to Business Source License 1.1. > > > > I look forward to your feedback and discussions, > > > > Thank you, > > Claude Warren > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal > > >
Re: [DISCUSS] Incubating Proposal for Pekko
Hi PJ, I think it's now in progress: 1. https://lists.apache.org/thread/clrd9dctv34981rcvr7w1j39kblj4lj4 2. https://lists.apache.org/thread/qxyj9xxbwdqy82ps4qq1vo8ghrng63zm Best, tison. Willem Jiang 于2022年9月30日周五 08:52写道： > Please send an IPMC member request mail to priv...@incubator.apache.org. > Then, it will be taken care of. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Sep 30, 2022 at 5:07 AM PJ Fanning wrote: > > > > Thanks Tison, > > Would you be in a position to do the notice email for Charles and me > > (to the board mailing list)? > > > > Regards, > > PJ > > > > > > > > On Thu, 29 Sept 2022 at 18:26, tison wrote: > > > > > > Hi Claude, > > > > > > Thanks for starting this discussion! +1 to this proposal. > > > > > > It answers my previous questions on > > > https://lists.apache.org/thread/hdknoyvr9c0d4j70xqw6t2t7gnbzc7nq a new > > > name + a clear goal. > > > > > > I'm interested to act as a mentor to help with this podling's growth. > > > > > > w.r.t the membership, I notice that Claude Warren and PJ Fanning are > listed > > > on both initial committers and mentors, while other mentors don't. > Perhaps > > > you should check what's the intention here. > > > > > > Also, Claude Warren (you) and PJ Fanning are Apache members who can > become > > > IPMC members with a notice, but it still needs to go through the > > > process[1][2]. > > > > > > Best, > > > tison. > > > > > > [1] > > > > https://incubator.apache.org/guides/roles_and_responsibilities.html#incubator_project_management_committee_ipmc > > > [2] https://lists.apache.org/thread/t6k3mg97pyshzoxzjg4c62n166l3crcw > > > > > > > > > > > > Jean-Baptiste Onofré 于2022年9月29日周四 23:36写道： > > > > > > > Hi Claude > > > > > > > > Very interesting. I would be more than happy to mentor this podling > (if > > > > accepted of course). > > > > > > > > I will take a deeper look on the proposal wiki page. > > > > > > > > Thanks ! > > > > > > > > Regards > > > > JB > > > > > > > > Le jeu. 29 sept. 2022 à 16:57, Claude Warren, Jr > > > > a écrit : > > > > > > > > > Greetings, > > > > > > > > > > I would like to propose Pekko [1] as a new Apache Incubator > project. > > > > > > > > > > Pekko is a toolkit that brings the actor model (popularised by > Erlang) to > > > > > the JVM, providing the basis for building both locally and > distributed > > > > > concurrency. On top of this Pekko provides a rich set of libraries > built > > > > on > > > > > top of Actors to solve modern problems, including: > > > > > > > > > > > > > > >- Streams: Fully bi-directional backpressured streams following > the > > > > >Reactive manifesto > > > > >- HTTP: A fully streamed HTTP client/server built on top of > streams > > > > that > > > > >also provides expected tools (such as connection pooling) > necessary > > > > for > > > > >highly available web services > > > > >- connectors: A rich set of connectors for various databases, > > > > messaging, > > > > >persistent services built on top of streams > > > > >- grpc: A gRPC server/client > > > > >- projection: Provides abstractions necessary for CQRS pattern > such as > > > > >envelope, necessary for systems such as Kafka. > > > > > > > > > > > > > > > > > > > > Controversially Pekko is a fork of the Akka project just prior to > its > > > > > licence changed from Apache 2 to Business Source License 1.1. > > > > > > > > > > I look forward to your feedback and discussions, > > > > > > > > > > Thank you, > > > > > Claude Warren > > > > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal > > > > > > > > > > > > > - > > 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: package names (pekko related)
One point from the technical perspective: I remember that akka's config use akka. prefix and it causes several issues prevent you shaded it. That is, Maven Shaded Plugin cannot distinguish a string literal starts with akka. a config key or package name. >From this perspective, if possible, I tend to use org.apache.pekko in package name and use pekko. in the config name (or even akka? lol). Best, tison. Sheng Wu 于2022年10月11日周二 20:22写道： > Hi > > I am not sure about Kafka and Netbeans cases, as I was not working > inside the foundation back there. > For the recent years' new podlings, `org.apache.*` is preferred by the > incubator. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > PJ Fanning 于2022年10月11日周二 20:14写道： > > > > Hi everyone, > > > > I'm creating a new thread to avoid filling the Pekko thread with emails > that are only partially related to the proposal. > > > > The current Akka code uses packages that start with 'akka.' and a lot of > the people involved with Pekko seem to prefer to keep the use 'pekko.' > instead of 'org.apache.pekko.' when we rename the Akka packages. > > > > Kafka and Netbeans are examples of Apache projects that don't use > 'org.apache' prefix in their package names. > > > > Is 'pekko.' a viable option or is there a strong preference within the > ASF and the Incubator PMC for 'org.apache.pekko.'? > > > > Regards, > > PJ > > > > - > > 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: [DISCUSS] Remove 72 hour waiting time to add PPMC members.
+1 to keep the NOTICE and remove 72 hours requirement. One reminder here is that we should update the description on https://whimsy.apache.org/ when adding new members also. Currently, it writes: > To add existing committers to the PPMC, please cancel this dialog. Select the committer from the list and use the Modify button. That can be read as neither NOTICE nor 72 hours requirement is needed. Best, tison. Josh Fischer 于2022年10月14日周五 09:52写道： > +1 (non binding) > > On Thu, Oct 13, 2022 at 7:51 PM Sheng Wu > wrote: > > > +1 to keep the NOTICE and remove 72 hours waiting. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > Calvin Kirs 于2022年10月14日周五 08:37写道： > > > > > > On Fri, Oct 14, 2022 at 6:57 AM Dave Fisher > > wrote: > > > > > > > > > > > > > > > > Sent from my iPhone > > > > > > > > > On Oct 13, 2022, at 3:46 PM, Justin Mclean < > jus...@classsoftware.com> > > wrote: > > > > > > > > > > Hi, > > > > > > > > > > The board recently changed the 72-hour waiting time to add a PMC > > member to a top level project. We have the same 72-hour waiting time to > add > > PPMC members to a podling. > > > > > > > > > > Do we want to consider removing this 72-hour waiting time and just > > require a PMC to notify the IPMC that they want to add someone? > > > > > > > > Let’s just require that they notify that a PPMC member has been > added. > > > +1 > > > > > > > > > > Kind Regards, > > > > > 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 > > > > > > > > > > > > > -- > > > Best wishes！ > > > CalvinKirs > > > > > > - > > > 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 > > > > -- > Sent from A Mobile Device >
Re: Request to have me added as an IPMC Member
I noticed that Justin has sent a NOTICE: https://lists.apache.org/thread/8ftfqgmq1tztdb6fwvmg9obckp7nbpbo Generally, you will be added to the IPMC in three days. Best, tison. larry mccay 于2022年10月19日周三 00:51写道： > Hi - > > It has come to my attention that I don't seem to be an IPMC member > (anymore?) and I would like to officially Mentor the reboot of Livy. > > thanks! > > --larry >
Re: Request to have me added as an IPMC Member
Good to know :) Best, tison. Justin Mclean 于2022年10月19日周三 09:46写道： > There is no need for the 3 day wait anymore > > On Tue, 18 Oct 2022, 6:14 pm tison, wrote: > > > I noticed that Justin has sent a NOTICE: > > https://lists.apache.org/thread/8ftfqgmq1tztdb6fwvmg9obckp7nbpbo > > > > Generally, you will be added to the IPMC in three days. > > > > Best, > > tison. > > > > > > larry mccay 于2022年10月19日周三 00:51写道： > > > > > Hi - > > > > > > It has come to my attention that I don't seem to be an IPMC member > > > (anymore?) and I would like to officially Mentor the reboot of Livy. > > > > > > thanks! > > > > > > --larry > > > > > >
Re: [VOTE] Accept Pekko into the Apache Incubator
+1 (binding) Best, tison. Yu Xiao 于2022年10月19日周三 18:00写道： > + 1 （non-binding） > > Best wishes! > > Yu Xiao > Apache ShenYu > > Calvin Kirs 于2022年10月19日周三 17:51写道： > > > > +1 binding > > Good luck. > > > > On Wed, Oct 19, 2022 at 5:37 PM Sheng Wu > wrote: > > > > > > +1 binding > > > > > > Welcome > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > PJ Fanning 于2022年10月19日周三 17:32写道： > > > > > > > > Thanks Claude and Ryan for putting together the proposal. > > > > > > > > +1 binding > > > > > > > > On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr > > > > wrote: > > > > > > > > > > I'll even kick off the voting: > > > > > > > > > > +1 binding > > > > > > > > > > On Wed, Oct 19, 2022 at 9:04 AM Claude Warren, Jr < > claude.war...@aiven.io> > > > > > wrote: > > > > > > > > > > > After reviewing the [DISCUSS] threads concerning bringing Pekko > into the > > > > > > incubator [1][2], and finding that there is no further comment, > I am > > > > > > calling for a VOTE to accept Pekko into the Apache Incubator. > The text of > > > > > > the proposal is included below for convenience, final and > definitive text > > > > > > is in the Pekko Proposal from the Incubator wiki.[3] . > > > > > > > > > > > > Thank you for your time and consideration, > > > > > > Claude > > > > > > > > > > > > [1] > https://lists.apache.org/thread/1t0x6d815td9dgjxhck51b5txcjm28rr > > > > > > [2] > https://lists.apache.org/thread/cjo86gdwvqlqslq68gd0c8hxq6ds6yrz > > > > > > [3] > https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal > > > > > > > > > > > > *Pekko Proposal* > > > > > > > > > > > > *Abstract* > > > > > > > > > > > > Pekko is a toolkit and an ecosystem for building highly > concurrent, > > > > > > distributed, reactive and resilient applications for Java and > Scala. > > > > > > > > > > > > *Proposal* > > > > > > > > > > > > Pekko is a toolkit that brings the actor model (popularised by > Erlang) to > > > > > > the JVM, providing the basis for building both locally and > distributed > > > > > > concurrency. On top of this Pekko provides a rich set of > libraries built on > > > > > > top of Actors to solve modern problems, including: > > > > > > > > > > > >- Streams: Fully bi-directional backpressured streams > following the > > > > > >Reactive manifesto > > > > > >- HTTP: A fully streamed HTTP client/server built on top of > streams > > > > > >that also provides expected tools (such as connection > pooling) necessary > > > > > >for highly available web services > > > > > >- connectors: A rich set of connectors for various databases, > > > > > >messaging, persistent services built on top of streams > > > > > >- grpc: A gRPC server/client > > > > > >- projection: Provides abstractions necessary for CQRS > pattern such as > > > > > >envelope, necessary for systems such as Kafka. > > > > > > > > > > > > *Background* > > > > > > > > > > > > Pekko is a fork of the Akka project just before its licence > changed from > > > > > > Apache 2 to Business Source License 1.1. The project provides a > set of > > > > > > tools and frameworks that covers the complex problem space of > distributed > > > > > > concurrent systems. It is designed to support the design > principles of the > > > > > > Reactive Manifesto by providing components to efficiently scale > up systems > > > > > > within a server or scale out across multiple servers, are high > performance, > > > > > > resilient to failure, distributed systems without a single point > of failure. > > > > > > > > > > > > *Rationale* > > > > > > > > > > > > There is a large cohort of applications and lib
Re: [VOTE] Graduate Apache MXNet to a TLP
Hi Joe, Reminded of this thread - do we have a result mail and moving forward the graduation? I read that MXNet is still under incubating when exploring https://incubator.apache.org/clutch/ today. Best, tison. li gang 于2022年9月5日周一 19:22写道： > +1 (non-binding) > Good luck! > > Joe Evans 于2022年8月17日周三 22:41写道： > > > Hi Apache Incubator community, > > > > The Apache MXNet (incubating) community has discussed[1] graduating to a > > top level project and passed a community vote[2][3]. We have also > > discussed[4] graduating in the Incubator community. > > > > In the incubator discussion, some branding issues[5] were brought up. We > > have fixed the issues[6] we were able to and discussed the others with > > trademarks@. This work is ongoing. In addition, a few website issues[7] > > were brought up which were subsequently resolved[8]. > > > > Based on the positive feedback from the incubator discussion, we would > like > > to start a vote on graduating Apache MXNet (incubating) to a top level > > project. > > > > Please cast your vote as one of the following options: > > > > [ ] +1 Yes, I support Apache MXNet (incubating) graduating from the > Apache > > Incubator to a top level project. > > > > [ ] +0 No opinion. > > > > [ ] -1 No, the Apache MXNet (incubating) project is not ready to > graduate, > > because ... > > > > This vote will remain open for at least 72 hours. > > > > Here is a brief overview of the progress of the Apache MXNet (incubating) > > project and community since entering the incubator: > > > > Community > > > >- > > > >38 new PPMC members were added, bringing the total number of PPMC > >members to 51 > >- > > > >56 new committers were added (which include new PPMC members), > bringing > >the total number of committers to 87 > >- > > > >The total number of contributors is now 870 and growing. > > > > Project > > > >- > > > >18 releases by 13 different release managers. All compliance issues > have > >been resolved with the 1.9.0 and 2.0.beta releases. > >- > > > >MXNet website is now compliant with Apache Project Website > requirements > >- > > > >MXNet has completed the project maturity self assessment[9] > > > > > > References: > > > > [1] https://lists.apache.org/thread/l9h2qgb2vqs2y0cm46wh83sgomr9w190 > > > > [2] https://lists.apache.org/thread/py1nw6whov78sch5kkm1gcg7cv3zb2sv > > > > [3] https://lists.apache.org/thread/b8bngc6qcb33n0jo6m1rw0ylwlqzkmgx > > > > [4] https://lists.apache.org/thread/3rxzjcmo2y457y6r8ohz1j4qv49joyo6 > > > > [5] https://lists.apache.org/thread/6brq4jg1x3hnt0sr3phboh2vwoo33db1 > > > > [6] https://github.com/apache/incubator-mxnet/issues/21036 > > > > [7] https://lists.apache.org/thread/j29jcv0zdkvx7vyy701qnfhnj09fzv8o > > > > [8] https://github.com/apache/incubator-mxnet/issues/21054 > > > > [9] > > > > > https://cwiki.apache.org/confluence/display/MXNET/Apache+Maturity+Model+Assessment+for+MXNet > > > > > > Here is the proposed resolution: > > > > —-- > > > > Establish the Apache MXNet Project > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > > > the Foundation and consistent with the Foundation's purpose to establish > > > > a Project Management Committee charged with the creation and maintenance > > > > of open-source software, for distribution at no charge to the public, > > > > related to a flexible and efficient library for Deep Learning. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > > (PMC), to be known as the "Apache MXNet Project", be and hereby is > > > > established pursuant to Bylaws of the Foundation; and be it further > > > > RESOLVED, that the Apache MXNet Project be and hereby is responsible for > > > > the creation and maintenance of software related to a flexible and > > > > efficient library for Deep Learning; and be it further > > > > RESOLVED, that the office of "Vice President, Apache MXNet" 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 MXNet > > > > Project, and to have primary responsibility for managemen
Re: [VOTE] Release Apache Kvrocks (incubating) 2.2.0
+1 (binding) I checked: * LICENSE/NOTICE/DISCLAIMER files exist. * Dependencies are clean. * GPG sign is valid. * Checksum is valid. * Build from source with `./x.py build --ninja' * Simple interactions. Best, tison. Twice Pragma 于2022年11月15日周二 10:48写道： > Thanks for your kind reminder! > > Although these two file are same at this moment. > > Best, > Twice > > From: Kent Yao > Sent: Tuesday, November 15, 2022 10:12:36 AM > To: general@incubator.apache.org > Subject: Re: [VOTE] Release Apache Kvrocks (incubating) 2.2.0 > > Hi Twice > > You should provide [1] instead of [2] for signatures. > > Kent > > [1] https://downloads.apache.org/incubator/kvrocks/KEYS > [2] https://dist.apache.org/repos/dist/dev/incubator/kvrocks/KEYS > > On 2022/11/14 13:20:59 Twice wrote: > > Hello IPMC, > > > > The Apache Kvrocks (incubating) community has voted and approved the > > release of Apache > > Kvrocks(incubating) 2.2.0. We now kindly request the IPMC members > > review and vote for this release. > > > > Kvrocks is a distributed key value NoSQL database that uses RocksDB as > the > > storage engine > > and is compatible with Redis protocol. The current release provides many > > new features, > > improvements to existing features and bug fixes. > > > > Kvrocks community vote thread: > > > > https://lists.apache.org/thread/10bxhgdd4nlk6dt039b4zxh2k4c3xncb > > > > Vote result thread: > > > > https://lists.apache.org/thread/djtoc1lgy56wtchtsl0r4jy6r8lhbv3l > > > > The release candidate: > > > > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.2.0 > > > > This release has been signed with a PGP available here: > > > > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/KEYS > > > > Git tag for the release: > > > > https://github.com/apache/incubator-kvrocks/tree/v2.2.0 > > > > Build guide can be found at: > > > > https://github.com/apache/incubator-kvrocks#build > > > > The vote will be open for at least 72 hours or until the necessary number > > of votes is reached. > > > > Please vote accordingly: > > [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.2.0 > > [ ] +0 > > [ ] -1 Do not approve (please specify the reason) > > > > Thanks! > > > > Best wishes, > > Twice > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Graduate Kyuubi from Apache Incubator as a Top Level Project
+1 (binding) Good luck! I like the report on the Apache Maturity Model :) Best, tison. Xun Liu 于2022年11月16日周三 11:04写道： > +1 (binding) for me, > > Thank you to the community for the great work. > A special thanks to Kent for all the preparation and great work. > > Best Regards, > Xun Liu > > On Wed, Nov 16, 2022 at 11:01 AM Yikun Jiang wrote: > > > Big +1 (non-binding). > > > > I am very happy to see Kyuubi's graduation vote email. In addition to > what > > Kent wrote in the mail, I also like to share some of my feelings: > > > > - I also participated in some of Kyuubi's groups and offline activities > in > > China. Users can quickly get responses from the community when they > > encounter problems. > > > > - The project operation is very standardized and professional, with good > > documentation, guide and license. > > > > - Some developer tools like Jetbrains are also actively helping to build > > Kyuubi's ecology. > > > https://blog.jetbrains.com/big-data-tools/2022/05/19/data-engineering-annotated-monthly-april-2022/ > > > > - Some operating system communities like openEuler are also actively > > helping him improve the experience platform: > > https://mp.weixin.qq.com/s/IRFOEQ9LddyhSqLnmP0_Hg > > > > - In the Kyuubi community, there are many users who use Spark and Flink, > > and students in the Kyuubi community are also very happy to answer > > questions about these Apache projects. > > > > So, in my mind, it has already become a graduation project. > > > > On 2022/11/15 03:57:27 Kent Yao wrote: > > > Hello, Incubator community and IMPC-ers, > > > > > > Following the discussion[0], I'd like to call a vote to graduate Kyuubi > > from > > > Apache Incubator as a Top-Level Project. > > > > > > Please vote accordingly: > > > [ ] +1 it is ready to graduate from the Apache Incubator to a TLP. > > > [ ] +0 No opinion. > > > [ ] -1 it is not ready to graduate (please state reasons) > > > > > > Thank you for participating in the vote. This vote will stay open for > at > > > least 72 hours. > > > > > > Best Regards, > > > Kent Yao > > > > > > > > > Kyuubi has been an incubating project since 2021-06-21 after the > > > proposal[1] was accepted. During the incubation, the Kyuubi project > > > and community developed stably and continuously following the Apache > > > Way. By sorting out and self-checking the Kyuubi maturity model[2], > > > we believe that the Kyuubi project is ready for graduating as a Top > > > Level Project. Meanwhile, corresponding threads for both discussions[3] > > > and vote[4][5] have been finished in the kyuubi@dev mailing list with > > > positive results. Please refer to the Kyuubi project incubation > > status[15] > > > for more information. > > > > > > Here is a brief overview of the progress of the Apache > Kyuubi(incubating) > > > project and community since entering the incubator: > > > > > > ** Community ** > > > > > > - 3 new PPMC members were added, bringing the total number to 12. > > > The community strives to be meritocratic and diverse, the current > > > PPMC(mentors excluded) consists of individuals from different > > organizations[16], > > > China Mobile(1), Ctrip(1), eBay(1), NetEase(4), and T3(1). > > > - 8 new committers were added, bringing the total number to 17. The > newly > > > added committers(PPMC excluded) are also from different organizations, > > > AsiaInfo(1), Bilibili(1), Dingxiangyuan(1), iQiYi(1), and NetEase(1). > > > - 60+ new contributors participate in the community. The number of > > > contributors are now 99 and still growing. > > > - The dev@kyuubi mailing list currently has 89 subscribers, and all > > major > > > project discussions happen there. The GitHub discussions page is also > > being > > > actively used for user questions, feature requests, story sharing, etc. > > > - Held 3 meetups by our community, and participated in 20+ events, such > > as > > > ApacheCon, to promote the Kyuubi project. > > > - All PPMC members are willing to join the Kyuubi PMC membership after > > > graduation[6][7]. > > > - Kent Yao(y...@apache.org) was voted as Vice President[8]. > > > > > > ** Project ** > > > > > > - 8 releases[9] by 8 different release managers. > > > - 1400+ pull requests merged[10], and 900+ issue
Re: [VOTE] Release Apache StreamPark 2.0.0-RC1
+1 (binding) I verified: + Dist artifacts valid and downloadable. + 3 released tarball has correct sign and checksum. + Do not found binary files in the source release. + LICENSE, NOTICE and DISCLAIM are present in each release. + JAR files contain DEPENDENCIES file to show dependencies' license information + Build from source by ./build.sh with detach mode + scala 2.12 + jdk 1.8, and later run pnpm install & build to build the front end. - I cannot build the library with mixed mode due to multiple network issues. But this seems not be a blocker. nit: The release validation process has some typos and indent issues. I made https://github.com/apache/incubator-streampark-website/commit/0b04e3a8bd34eebb9306fb2f1f7f0db4250559a2 to fix. Best, tison. Huajie Wang 于2022年12月25日周日 08:01写道： > Hello Incubator Community: > > The Apache StreamPark community has voted on and approved a proposal to > release, Apache StreamPark version 2.0.0-RC1, We now kindly request the > Incubator PMC members review and vote on this incubator release. > > Apache StreamPark, Make stream processing easier! easy-to-use streaming > application development framework and operation platform. > > > StreamPark community vote thread: > https://lists.apache.org/thread/8683w7pwf24qg852px4ngwnorhqz27n1 > > Vote result thread: > https://lists.apache.org/thread/4qqw8vpw13ngtc4y2340o37crbf7oqjz > > The release candidate: > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC1/ > > Git tag for the release: > https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc1 > > Maven artifacts are available in a staging repository at: > > https://repository.apache.org/content/repositories/orgapachestreampark-1004/ > > > The artifacts signed with PGP key [5AE01B8E], corresponding to [ > benj...@apache.org], that can be found in keys file: > https://downloads.apache.org/incubator/streampark/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 > > Best, > Huajie Wang >
Re: Looking for a champion: HyperIoT
> I'm an ASF Member, I could also help here for writing the proposal but I'm > not a PMC member for the Incubator project, I'm a committer for my past > incubation experience related to Apache ManifoldCF. FYI, as an ASF Member, you can request to become a IPMC member anytime: > Individuals may be nominated to join the IPMC after a vote which passes. Individuals may choose to bring themselves or others to the attention of the IPMC. Additionally, any Member of the Apache Software Foundation may join the IPMC by request. ... from https://incubator.apache.org/guides/roles_and_responsibilities.html . Best, tison. Piergiorgio Lucidi 于2023年1月12日周四 16:06写道： > Hi folks, > > ACSoftware contacted me because they would like to donate their platform > named HyperIoT to the Foundation. I'm searching for a champion to build the > incubation proposal. > > I'm an ASF Member, I could also help here for writing the proposal but I'm > not a PMC member for the Incubator project, I'm a committer for my past > incubation experience related to Apache ManifoldCF. > > They currently published only the backend services on their GitHub account > but they are going to also share all the UI modules: > https://github.com/ACSoftwareTeam/HyperIoT-Platform > > You can find more information and some screenshots here: > https://hyperiot.cloud/ > > Below is an overview of this platform. > > HyperIoT is an OpenSource Cloud Native platform entirely based on Apache > Technologies for managing big data from any IoT network. > The platform captures the information sent from any source by managing data > compression, running statistics or machine/deep learning algorithms, > presenting data to the end user in realtime and offline mode (saved data). > > It consists of the following macro-components (entirely built on top of > Apache Technologies): > > - Realtime and Enrichments (Kafka and Storm): Realtime configuration and > visualization of data coming from sources with the possibility of defining > enrichment rules on incoming data > > - Events and Alarm Management (Storm): Data are analyzed in real time with > the possibility of reporting any alarms by sending timely notifications > either to the device or using other channels such as email > > - Persistence (HBase and Hadoop) : Data is saved in a secure mode > > - Statistics and Machine Learning (Apache Spark): It is possible to run > periodically, on the saved data, machine learning algorithms or generic > statistics presenting the results of these computations in the user's > dashboard. > > HyperIoT cloud infrastructure constitutes a generic server-side > architecture suitable for cross-cutting applications in various > manufacturing sectors. The infrastructure allows a user, without the > intervention of external developers, to be able to: > > - Configure communication between the IoT network and the cloud (without > writing code but following graphically guided processes) > - Have a set of predefined statistics for the data being processed > - Upload your own analytics algorithms (for more technical users) > - Access an intuitive web interface for configurations and access to > real-time and historical data via different graphical widgets > - Share the information collected > > The easy use of the platform through graphically guided processes allows it > to be used even by personnel who do not have specific knowledge about IoT > topics, data streaming, big data, etc... > > This will help spread the benefits of IoT and Industry 4.0 technologies > even to personnel who are not exactly experts. > > Thank you for your support. > > Cheers, > PJ > > -- > Piergiorgio >
Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC4
I suggest you create a release-2.0 branch and make only release related changes so that the artifacts get converged during RCs. Currently, I see that you create RC always from the dev branch and thus includes unexpected changes. This approach introduces extra exceptions and only slows the release. Best, tison. Huajie Wang 于2023年2月5日周日 11:26写道： > hi Willem: > > Thanks for your review and feedback, this vote is closed, We will fix these > issues and start a new vote process. > > > Best, > Huajie Wang > > > > Willem Jiang 于2023年2月5日周日 11:16写道： > > > -1, we need to start a new vote with the tag of rc5. > > I just found out that the rc4 tag[1] was created on Feb 3th, it has > > some new changes[2] after the vote in the stream park dev on Feb 1st. > > Please keep in mind, if we made some changes on the voting release > > kit, we need to start a new vote, otherwise the vote is invalid. > > We need to include the last commit hash within the voting mail next time. > > > > [1]https://github.com/apache/incubator-streampark/tree/v2.0.0-rc4 > > [2]https://github.com/apache/incubator-streampark/commits/v2.0.0-rc4 > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Sat, Feb 4, 2023 at 7:22 PM Huajie Wang wrote: > > > > > > Hello Incubator Community: > > > > > > This is a call for a vote to release Apache StreamPark(Incubating) > > > version 2.0.0-RC4 > > > > > > The Apache StreamPark community has voted on and approved a proposal to > > > release > > > Apache StreamPark(Incubating) version 2.0.0-RC4 > > > > > > We now kindly request the Incubator PMC members review and vote on this > > > incubator release. > > > > > > Apache StreamPark, Make stream processing easier! easy-to-use streaming > > > application development framework and operation platform. > > > > > > In this release we fixed some license issues[1]. > > > > > > StreamPark community vote thread: > > > https://lists.apache.org/thread/gxdc5d9posbbc3lmbstyw9sr350tthgm > > > > > > Vote result thread: > > > https://lists.apache.org/thread/v3gc6p9xdsohg2xn80ydbtf6tbm1t13n > > > > > > The release candidate: > > > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC4/ > > > > > > Git tag for the release: > > > https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc4 > > > > > > Release notes: > > > https://streampark.apache.org/download/release-note/2.0.0/ > > > > > > Maven artifacts are available in a staging repository at: > > > > > > https://repository.apache.org/content/repositories/orgapachestreampark-1008/ > > > > > > The artifacts signed with PGP key [5AE01B8E], corresponding to [ > > > benj...@apache.org], that can be found in keys file: > > > https://downloads.apache.org/incubator/streampark/KEYS > > > > > > The vote will be open for at least 72 hours or until the necessary > number > > > of votes are reached. > > > > > > Please vote accordingly: > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > More detailed checklist please refer: > > > • > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > > > Steps to validate the release， Please refer to: > > > • https://www.apache.org/info/verification.html > > > • https://streampark.apache.org/community/release/how-to-verify > > > > > > > > > How to Build: > > > > > > 1) clone source code: > > > > git clone -b v2.0.0-rc4 g...@github.com: > apache/incubator-streampark.git > > > > > > 2) build project: > > > > cd incubator-streampark && sh ./build.sh > > > > > > > > > Thanks, > > > > > > On behalf of Apache StreamPark(Incubating) community > > > > > > [1] https://github.com/apache/incubator-streampark/pull/2294 > > > > > > > > > Best, > > > Huajie Wang > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC4
BTW, RCs don't need a branch but a tag, although this is a practice instead of requirement :) Best, tison. tison 于2023年2月5日周日 11:57写道： > I suggest you create a release-2.0 branch and make only release related > changes so that the artifacts get converged during RCs. > > Currently, I see that you create RC always from the dev branch and thus > includes unexpected changes. This approach introduces extra exceptions and > only slows the release. > > Best, > tison. > > > Huajie Wang 于2023年2月5日周日 11:26写道： > >> hi Willem: >> >> Thanks for your review and feedback, this vote is closed, We will fix >> these >> issues and start a new vote process. >> >> >> Best, >> Huajie Wang >> >> >> >> Willem Jiang 于2023年2月5日周日 11:16写道： >> >> > -1, we need to start a new vote with the tag of rc5. >> > I just found out that the rc4 tag[1] was created on Feb 3th, it has >> > some new changes[2] after the vote in the stream park dev on Feb 1st. >> > Please keep in mind, if we made some changes on the voting release >> > kit, we need to start a new vote, otherwise the vote is invalid. >> > We need to include the last commit hash within the voting mail next >> time. >> > >> > [1]https://github.com/apache/incubator-streampark/tree/v2.0.0-rc4 >> > [2]https://github.com/apache/incubator-streampark/commits/v2.0.0-rc4 >> > >> > >> > Willem Jiang >> > >> > Twitter: willemjiang >> > Weibo: 姜宁willem >> > >> > On Sat, Feb 4, 2023 at 7:22 PM Huajie Wang wrote: >> > > >> > > Hello Incubator Community: >> > > >> > > This is a call for a vote to release Apache StreamPark(Incubating) >> > > version 2.0.0-RC4 >> > > >> > > The Apache StreamPark community has voted on and approved a proposal >> to >> > > release >> > > Apache StreamPark(Incubating) version 2.0.0-RC4 >> > > >> > > We now kindly request the Incubator PMC members review and vote on >> this >> > > incubator release. >> > > >> > > Apache StreamPark, Make stream processing easier! easy-to-use >> streaming >> > > application development framework and operation platform. >> > > >> > > In this release we fixed some license issues[1]. >> > > >> > > StreamPark community vote thread: >> > > https://lists.apache.org/thread/gxdc5d9posbbc3lmbstyw9sr350tthgm >> > > >> > > Vote result thread: >> > > https://lists.apache.org/thread/v3gc6p9xdsohg2xn80ydbtf6tbm1t13n >> > > >> > > The release candidate: >> > > >> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC4/ >> > > >> > > Git tag for the release: >> > > >> https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc4 >> > > >> > > Release notes: >> > > https://streampark.apache.org/download/release-note/2.0.0/ >> > > >> > > Maven artifacts are available in a staging repository at: >> > > >> > >> https://repository.apache.org/content/repositories/orgapachestreampark-1008/ >> > > >> > > The artifacts signed with PGP key [5AE01B8E], corresponding to [ >> > > benj...@apache.org], that can be found in keys file: >> > > https://downloads.apache.org/incubator/streampark/KEYS >> > > >> > > The vote will be open for at least 72 hours or until the necessary >> number >> > > of votes are reached. >> > > >> > > Please vote accordingly: >> > > [ ] +1 approve >> > > [ ] +0 no opinion >> > > [ ] -1 disapprove with the reason >> > > >> > > More detailed checklist please refer: >> > > • >> > > >> > >> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist >> > > >> > > Steps to validate the release， Please refer to: >> > > • https://www.apache.org/info/verification.html >> > > • https://streampark.apache.org/community/release/how-to-verify >> > > >> > > >> > > How to Build: >> > > >> > > 1) clone source code: >> > > > git clone -b v2.0.0-rc4 g...@github.com: >> apache/incubator-streampark.git >> > > >> > > 2) build project: >> > > > cd incubator-streampark && sh ./build.sh >> > > >> > > >> > > Thanks, >> > > >> > > On behalf of Apache StreamPark(Incubating) community >> > > >> > > [1] https://github.com/apache/incubator-streampark/pull/2294 >> > > >> > > >> > > Best, >> > > Huajie Wang >> > >> > - >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> > For additional commands, e-mail: general-h...@incubator.apache.org >> > >> > >> >
Re: [CANCEL][VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC4
I don't see license issues here but a process issue. What license issues do you spot? Best, tison. Huajie Wang 于2023年2月5日周日 11:29写道： > Hello Incubator Community, > > I'm cancelling this vote: > > https://lists.apache.org/thread/680qq5jggwbqxmwfq5yztp4tzmz4l2ys > > due to licenses issues. I'll fix them and start a new vote process. > > > Thanks a lot for all your help. > > > Best, > Huajie Wang >
Re: [QUESTION] are binary distributions/releases required?
Hi PJ, Only source releases are required. Apache Kvrocks (Incubating) release 2.1.0 (the first Apache release) with sources only, although there's a following vote for Docker release due to user's requirement :) You may refer to: https://lists.apache.org/thread/v63xyr8rw5o7h0flt3fx3mrn9vxsyskm https://lists.apache.org/thread/k744nbjf6vhvwkf8fb02t4l08rjxo7n7 I agree to release only sources helps the podling getting started with the new process, while please keep collecting users feedback :) Best, tison. PJ Fanning 于2023年2月8日周三 22:33写道： > Hi everyone, > The release management guide [1] only mentions 'source releases'. Every > Apache project that I am familiar with also does binary releases. For > applications, this makes sense - having a zip/tgz file that you can > download and extract - that you can then readily start the application > using a shell script. For libs, I'm sure these binary releases can be > useful too but I'm wondering if they are strictly required. > > Apache Pekko is a set of libraries as opposed to an application. Our build > uses the sbt build tool and there isn't anything that I've come across that > would produce something like the binary releases that other Apache projects > release. This means we'd likely have to roll our own solution. > > In terms of prioritising work towards a v1.0.0 release, it's useful to > know if we have items that could be de-prioritised. > > If we do need to create binary releases, are there any guidelines to > follow - or do we just look at other Apache libs and use their binary > releases as a guide? > > Regards, > PJ > > [1] https://incubator.apache.org/guides/releasemanagement.html > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)
+1 (binding) Verified: - [X] Download links are valid. - [X] Checksums and PGP signatures are valid. - [X] Source code artifacts have correct names matching the current release. - [X] LICENSE, NOTICE and DISCLAIMER are correct for the repository. - [X] All files have license headers if necessary. - [X] No compiled archives bundled in the source archive. - [X] Building is OK with: ./x.py build --ninja --ghproxy - [X] Stage docker image runs and serves properly Best, tison. Chao Zhang 于2023年2月12日周日 18:33写道： > Hi, > > +1 (non-binding) from me. I have checked: > > 1. All the above links are correct; > 2. The signature and checksum are correct; > 3. LICENSE and NOTICE files exist; > > Best regards > Chao Zhang > > https://github.com/tokers > > On Sat, Feb 11, 2023 at 10:44 PM Myth wrote: > > > > Hello Incubator PMC, > > > > The Apache Kvrocks community has voted and approved the release of Apache > > Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members review > > and vote for this release. > > > > This is the second call for a vote. The first call for a vote, which is > > cancelled: > > *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt > > <https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt>* > > > > Kvrocks is a distributed key value NoSQL database that uses RocksDB as > the > > storage engine and is compatible with Redis protocol. The current release > > provides many new features, many improvements and fixes many bugs. > > > > Kvrocks community vote thread: > > https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2 > > > > Vote result thread: > > https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw > > > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/ > > > > This release has been signed with a PGP available here: > > https://downloads.apache.org/incubator/kvrocks/KEYS > > > > Git tag for the release: > > https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0 > > > > Docker image: > > > https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807 > > > > Build guide can be found at: > > https://github.com/apache/incubator-kvrocks#build > > > > The vote will be open for at least 72 hours or until the necessary number > > of votes is reached. > > > > Please vote accordingly: > > [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.3.0 > > [ ] +0 > > [ ] -1 Do not approve (please specify the reason) > > > > Thanks > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)
> you believe the original authors agree that the modifications > are significant and can be relicensed, then I'm totally OK > to add ASF license headers there Hi zhenxu, This is the case for Kvrocks. Kvrocks contributors port the file to cpp and the original license is BSD 3-Clause which allows the recipient to relicense. Best, tison. kezhenxu94 于2023年2月13日周一 17:15写道： > Hi, > > When it comes to human feelings there is no quantifiable standard, > if the original authors granted you to relicense the file, or, > you believe the original authors agree that the modifications > are significant and can be relicensed, then I'm totally OK > to add ASF license headers there. > > If that's neither the case, I'd be conservative to keep the original > license header. > > I also remember there was a discussion already in this mailing list, > but can't recall the link at the moment, anyone else can find > and share would be appreciated. > > > On Feb 13, 2023, at 16:51, Twice wrote: > > > > Hi @kezhenxu94, > > > > Thank you for taking the time to vote and for your valuable input. > > > > However, I would like to point out that > > - You can see the changes we have made to these files in the commit log, > > and I have included some links [1-2] for your convenience. > > - I cannot find an official description of the inclusion of the ASF > header > > to the modified third-party code: i.e. > > how many changes can be described as not being "mostly the same"? Is > > there a quantifiable standard for this? > > > > [1] > > > https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc > > [2] > > > https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc > > > > Best, > > Twice > > > > > > On Mon, Feb 13, 2023 at 4:07 PM kezhenxu94 > wrote: > > > >> Hi sorry -1 (binding) due to license issue, the following files [1] have > >> ASF license headers along with the original license header, > >> I saw you mentioned it's a conversion from C to C++ from Redis project, > >> but from my comparison they look to > >> be mostly the same so you might want to remove the ASF license header > from > >> those files. > >> > >> Other files [2] might be controversial whether we should have dual > license > >> headers, but I won't vote -1 on those files if [1] are resolved. > >> > >> [1] - apache/incubator-kvrocks/src/types/geohash.cc < > http://geohash.cc/> > >> - apache/incubator-kvrocks/src/common/sha1.cc <http://sha1.cc/> > >> > >> [2] - src/common/rand.cc src/common/rand.h > >>- src/storage/scripting.* > >> > >>> On Feb 11, 2023, at 22:43, Myth wrote: > >>> > >>> Hello Incubator PMC, > >>> > >>> The Apache Kvrocks community has voted and approved the release of > Apache > >>> Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members > review > >>> and vote for this release. > >>> > >>> This is the second call for a vote. The first call for a vote, which > is > >>> cancelled: > >>> *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt > >>> <https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt>* > >>> > >>> Kvrocks is a distributed key value NoSQL database that uses RocksDB as > >> the > >>> storage engine and is compatible with Redis protocol. The current > release > >>> provides many new features, many improvements and fixes many bugs. > >>> > >>> Kvrocks community vote thread: > >>> https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2 > >>> > >>> Vote result thread: > >>> https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw > >>> > >>> The release candidate: > >>> https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/ > >>> > >>> This release has been signed with a PGP available here: > >>> https://downloads.apache.org/incubator/kvrocks/KEYS > >>> > >>> Git tag for the release: > >>> https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0 > >>> > >>> Docker image: > >>> > >> > https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807 > >>> > >>> Build guide can be found at: > >>> https://github.com/apache/incubator-kvrocks#build > >>> > >>> The vote will be open for at least 72 hours or until the necessary > number > >>> of votes is reached. > >>> > >>> Please vote accordingly: > >>> [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.3.0 > >>> [ ] +0 > >>> [ ] -1 Do not approve (please specify the reason) > >>> > >>> Thanks > >> > >> > >> - > >> 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 Kvrocks(incubating) 2.3.0(NEW VOTE)
Hi Justin, It can be a case of The Ship of Theseus. When you take a look at the issued files[1][2], you may find a commit history touching them and modifying them. Anyway, it's not an identical copy or one-shot translation. And we keep the origin comments. Even a one-shot translation, if it's done by humans, generally modification will be applied. But if you insist on "keep the original license header and don't add the ASF header" with an existing documented guideline, the Kvrocks contributors would be glad to change it. Best, tison. [1] https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc [2] https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc Justin Mclean 于2023年2月14日周二 05:39写道： > Hi, > > In general porting a file from one language to another would not change > the original license. > > Kind Regards, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)
Hi zhenxu, When you look at the header, it writes: SHA-1 in C By Steve Reid 100% Public Domain Zhenxu Ke 于2023年2月14日 周二10:00写道： > Hi, sorry the mailer-dae...@apache.org just says it can't deliver my > email, which should be sent out last night (2023/02/13 22:49), here is my > reply: > > Hi, now I would continue to vote -1 and I believe this should be fixed > ASAP, because you might copy the file[1] from Redis, but the file is not > originated from Redis either, it’s copied from yet another project > valgrind[2], which is GPL licensed[3]. > > [1] incubator-kvrocks/src/common/sha1.cc > [2] https://github.com/danos/valgrind/blob/master/none/tests/sha1_test.c > [3] https://github.com/danos/valgrind/blob/master/COPYING > > On 2023/02/14 00:43:19 tison wrote: > > Hi Justin, > > > > It can be a case of The Ship of Theseus. When you take a look at the > issued > > files[1][2], you may find a commit history touching them and modifying > > them. Anyway, it's not an identical copy or one-shot translation. And we > > keep the origin comments. > > > > Even a one-shot translation, if it's done by humans, generally > modification > > will be applied. > > > > But if you insist on "keep the original license header and don't add the > > ASF header" with an existing documented guideline, the Kvrocks > contributors > > would be glad to change it. > > > > Best, > > tison. > > > > [1] > > > https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc > > [2] > > > https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc > > > > > > Justin Mclean 于2023年2月14日周二 05:39写道： > > > > > Hi, > > > > > > In general porting a file from one language to another would not change > > > the original license. > > > > > > Kind Regards, > > > 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 > > -- Best, tison.
Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)
Thanks for your confirmation. Then I agree the content should be updated to avoid risk. kezhenxu94 于2023年2月14日 周二10:43写道： > But at the same time, the file header has `/* from valgrind tests */`, > I assumed you ported the variation of Valgrind. > > A good practice is not to add more license information than you > actually do, i.e., don't declare it's from valgrind tests if you > believe you are using the original Public Domain sha1.c file, > confusions arise like this. > > > On Feb 14, 2023, at 10:22, tison wrote: > > > > Hi zhenxu, > > > > When you look at the header, it writes: > > > > SHA-1 in C > > By Steve Reid > > 100% Public Domain > > > > Zhenxu Ke 于2023年2月14日 周二10:00写道： > > > >> Hi, sorry the mailer-dae...@apache.org just says it can't deliver my > >> email, which should be sent out last night (2023/02/13 22:49), here is > my > >> reply: > >> > >> Hi, now I would continue to vote -1 and I believe this should be fixed > >> ASAP, because you might copy the file[1] from Redis, but the file is not > >> originated from Redis either, it’s copied from yet another project > >> valgrind[2], which is GPL licensed[3]. > >> > >> [1] incubator-kvrocks/src/common/sha1.cc > >> [2] > https://github.com/danos/valgrind/blob/master/none/tests/sha1_test.c > >> [3] https://github.com/danos/valgrind/blob/master/COPYING > >> > >> On 2023/02/14 00:43:19 tison wrote: > >>> Hi Justin, > >>> > >>> It can be a case of The Ship of Theseus. When you take a look at the > >> issued > >>> files[1][2], you may find a commit history touching them and modifying > >>> them. Anyway, it's not an identical copy or one-shot translation. And > we > >>> keep the origin comments. > >>> > >>> Even a one-shot translation, if it's done by humans, generally > >> modification > >>> will be applied. > >>> > >>> But if you insist on "keep the original license header and don't add > the > >>> ASF header" with an existing documented guideline, the Kvrocks > >> contributors > >>> would be glad to change it. > >>> > >>> Best, > >>> tison. > >>> > >>> [1] > >>> > >> > https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc > >>> [2] > >>> > >> > https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc > >>> > >>> > >>> Justin Mclean 于2023年2月14日周二 05:39写道： > >>> > >>>> Hi, > >>>> > >>>> In general porting a file from one language to another would not > change > >>>> the original license. > >>>> > >>>> Kind Regards, > >>>> 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 > >> > >> -- > > Best, > > tison. > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best, tison.
Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)
I submit a patch: https://github.com/apache/incubator-kvrocks/pull/1259 @zhenxu you're welcome to help verify if it fixes your concerns. ... and -1 (binding) @Myth I think we need a new release candidate :) Best, tison. tison 于2023年2月14日周二 10:47写道： > Thanks for your confirmation. Then I agree the content should be updated > to avoid risk. > > kezhenxu94 于2023年2月14日 周二10:43写道： > >> But at the same time, the file header has `/* from valgrind tests */`, >> I assumed you ported the variation of Valgrind. >> >> A good practice is not to add more license information than you >> actually do, i.e., don't declare it's from valgrind tests if you >> believe you are using the original Public Domain sha1.c file, >> confusions arise like this. >> >> > On Feb 14, 2023, at 10:22, tison wrote: >> > >> > Hi zhenxu, >> > >> > When you look at the header, it writes: >> > >> > SHA-1 in C >> > By Steve Reid >> > 100% Public Domain >> > >> > Zhenxu Ke 于2023年2月14日 周二10:00写道： >> > >> >> Hi, sorry the mailer-dae...@apache.org just says it can't deliver my >> >> email, which should be sent out last night (2023/02/13 22:49), here is >> my >> >> reply: >> >> >> >> Hi, now I would continue to vote -1 and I believe this should be fixed >> >> ASAP, because you might copy the file[1] from Redis, but the file is >> not >> >> originated from Redis either, it’s copied from yet another project >> >> valgrind[2], which is GPL licensed[3]. >> >> >> >> [1] incubator-kvrocks/src/common/sha1.cc >> >> [2] >> https://github.com/danos/valgrind/blob/master/none/tests/sha1_test.c >> >> [3] https://github.com/danos/valgrind/blob/master/COPYING >> >> >> >> On 2023/02/14 00:43:19 tison wrote: >> >>> Hi Justin, >> >>> >> >>> It can be a case of The Ship of Theseus. When you take a look at the >> >> issued >> >>> files[1][2], you may find a commit history touching them and modifying >> >>> them. Anyway, it's not an identical copy or one-shot translation. And >> we >> >>> keep the origin comments. >> >>> >> >>> Even a one-shot translation, if it's done by humans, generally >> >> modification >> >>> will be applied. >> >>> >> >>> But if you insist on "keep the original license header and don't add >> the >> >>> ASF header" with an existing documented guideline, the Kvrocks >> >> contributors >> >>> would be glad to change it. >> >>> >> >>> Best, >> >>> tison. >> >>> >> >>> [1] >> >>> >> >> >> https://github.com/apache/incubator-kvrocks/commits/unstable/src/types/geohash.cc >> >>> [2] >> >>> >> >> >> https://github.com/apache/incubator-kvrocks/commits/unstable/src/common/sha1.cc >> >>> >> >>> >> >>> Justin Mclean 于2023年2月14日周二 05:39写道： >> >>> >> >>>> Hi, >> >>>> >> >>>> In general porting a file from one language to another would not >> change >> >>>> the original license. >> >>>> >> >>>> Kind Regards, >> >>>> 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 >> >> >> >> -- >> > Best, >> > tison. >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> -- > Best, > tison. >
Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)
Hi Justin, Thanks for your information! I made this patch https://github.com/apache/incubator-kvrocks/pull/1259 to resolve the license issue. Since we're going to make a new RC with only this change, could you take a look at the patch whether there still remains some concerns? Then we can avoid another round of failed vote. Best, tison. Justin Mclean 于2023年2月14日 周二15:59写道： > Hi, > > > It can be a case of The Ship of Theseus. When you take a look at the > issued > > files[1][2], you may find a commit history touching them and modifying > > them. Anyway, it's not an identical copy or one-shot translation. > > This has been discussed many times on various lists, translating an > algorithm from one language to another does not change its license. > > > And we keep the origin comments. > > Which is also an IP issue. > > Kinds Regards, > Justin > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best, tison.
[DISCUSS] Incubating Proposal for OpenDAL
Hi IPMC, I would like to propose OpenDAL[1] as a new apache incubator project, you can find the proposal[2] of OpenDAL for more detail. [1] https://github.com/datafuselabs/opendal [2] https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal Best, tison. Full text of the proposal below: ## Abstract OpenDAL means “Open Data Access Layer”. It’s a Rust library that helps developers access data freely, painlessly, and efficiently over multiple services, including AWS S3, HDFS, POSIX-compatible file systems, and so on. ## Proposal OpenDAL provides the following features to support developers accessing data freely, painlessly, and efficiently: - Freely - Access different storage services in the same way - Behavior tests for all services - Cross-language/project bindings (working in progress) - Painlessly - **100%** of documents covered - Powerful [Layers]( https://opendal.databend.rs/opendal/layers/index.html) - Automatic [retry]( https://opendal.databend.rs/opendal/layers/struct.RetryLayer.html) support - Full observability support: [logging]( https://opendal.databend.rs/opendal/layers/struct.LoggingLayer.html ), [tracing]( https://opendal.databend.rs/opendal/layers/struct.TracingLayer.html), and [metrics]( https://opendal.databend.rs/opendal/layers/struct.MetricsLayer.html). - Native chaos testing - Native service-side encryption support - Efficiently - Zero cost: mapping to underlying API calls directly - Best effort: auto-pick the best `read`/`seek`/`next` implementations based on services - [Auto metadata reuse]( https://opendal.databend.rs/rfcs/0561-list-metadata-reuse.html): avoid extra `metadata` calls OpenDAL was originally designed to be used by the Databend project but is now being used by Mozilla's sccache, DeepETH's mars, and several database startups. We believe that the OpenDAL project will provide diversity value to the community if OpenDAL is brought into the Apache incubator. ## Background OpenDAL is being developed by an open-source community from day one and is owned by DatafuseLabs. The project has been launched in February 2022. ## Rationale OpenDAL provides a unified storage abstraction layer that simplifies the interfacing of different storage services. In addition, OpenDAL provides further advanced storage encapsulation, enabling enhancements such as automatic retry, request optimization, and observability. OpenDAL makes it possible to develop once and run on any storage service. ## Initial Goals By transferring ownership of the project to the ASF, OpenDAL expects to ensure its neutrality and further encourage and facilitate the adoption of OpenDAL by the community. Some of the areas we would like to focus on during the Apache incubation phase include: - A healthier community: more maintainers and contributors will be able to participate in OpenDAL and own different modules. - Wider adoption: OpenDAL can be adopted by more open source/commercial projects, which in turn drives its own functionality. - Richer integration: OpenDAL enables greater integration of storage services and offers a wider range of language bindings. ## Current Status ### Meritocracy We intend to radically expand the initial developer and user community by running the project the 'Apache way'. Users and new contributors will be respected and welcomed. They will earn credit by participating in the community and providing quality patches/support to move the project forward. They will also be encouraged to provide non-code contributions (documentation, events, community management, etc.) and will be rewarded accordingly. Those with a proven track record of support and quality will be encouraged to become committers. ### Community Contributors: 37 Users: - Databend: A cloud data warehouse - GreptimeDB: A time-series database - Sccache: ccache with cloud storage - RisingWave: A Distributed SQL Database for Stream Processing ### Core Developers The core developers are all experienced open-source developers. They have been running the OpenDAL community for 1 year. ### Alignment ## Known Risks ### Project Name We have checked and believe that the name is appropriate and that the project has legal permission to continue using its current name. There are no other projects with this name found in a Google search. ### Orphan Products ### Inexperience with Open Source OpenDAL's core developers are all experienced open source contributors, and its main maintainer Xuanwo has 10 years of open source experience, having worked on a number of open source projects including Hexo, TiDB, TiKV, Databend, Sccache, and others. ### Length of Incubation Expect to enter incubation in two months and graduate in about two years. ### Homogenous Developers OpenDAL developers come from a variety of backgrounds and contribute to the OpenDAL project for different usage scenarios. ### Reliance on Salaried Developers Most dev
Re: [DISCUSS] Incubating Proposal for OpenDAL
Thanks for your feedbacks! @Willem Thanks for your reply. I've added you to the mentor list. AFAIK an incubating project needs up to 5 mentors :) For the bus factor concern, I agree that it's an issue that to be resolved during the incubating process. As OpenDAL attracts more and more adoptions in the Rust ecosystem, I'm not quite concern about it. Best, tison. Willem Jiang 于2023年2月17日周五 21:13写道： > +1, it's an interesting project. I'd like to be a mentor of this project. > BTW, even though there are 37 contributors, I found Xuanwo did most > of the development, which is not a good bus factor[1] of this project. > We can make it better during the incubating process. > > [1]https://en.wikipedia.org/wiki/Bus_factor > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Feb 17, 2023 at 7:22 AM tison wrote: > > > > Hi IPMC, > > > > I would like to propose OpenDAL[1] as a new apache incubator project, you > > can find the proposal[2] of OpenDAL for more detail. > > > > [1] https://github.com/datafuselabs/opendal > > [2] > https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal > > > > Best, > > tison. > > > > Full text of the proposal below: > > > > ## Abstract > > > > OpenDAL means “Open Data Access Layer”. It’s a Rust library that helps > > developers access data freely, painlessly, and efficiently over multiple > > services, including AWS S3, HDFS, POSIX-compatible file systems, and so > on. > > > > ## Proposal > > > > OpenDAL provides the following features to support developers accessing > > data freely, painlessly, and efficiently: > > > > - Freely > > - Access different storage services in the same way > > - Behavior tests for all services > > - Cross-language/project bindings (working in progress) > > - Painlessly > > - **100%** of documents covered > > - Powerful [Layers]( > > https://opendal.databend.rs/opendal/layers/index.html) > > - Automatic [retry]( > > https://opendal.databend.rs/opendal/layers/struct.RetryLayer.html) > support > > - Full observability support: [logging]( > > https://opendal.databend.rs/opendal/layers/struct.LoggingLayer.html > > ), [tracing]( > > https://opendal.databend.rs/opendal/layers/struct.TracingLayer.html), > and > > [metrics]( > > https://opendal.databend.rs/opendal/layers/struct.MetricsLayer.html). > > - Native chaos testing > > - Native service-side encryption support > > - Efficiently > > - Zero cost: mapping to underlying API calls directly > > - Best effort: auto-pick the best `read`/`seek`/`next` > implementations > > based on services > > - [Auto metadata reuse]( > > https://opendal.databend.rs/rfcs/0561-list-metadata-reuse.html): avoid > > extra `metadata` calls > > > > OpenDAL was originally designed to be used by the Databend project but is > > now being used by Mozilla's sccache, DeepETH's mars, and several database > > startups. > > > > We believe that the OpenDAL project will provide diversity value to the > > community if OpenDAL is brought into the Apache incubator. > > > > ## Background > > > > OpenDAL is being developed by an open-source community from day one and > is > > owned by DatafuseLabs. The project has been launched in February 2022. > > > > ## Rationale > > > > OpenDAL provides a unified storage abstraction layer that simplifies the > > interfacing of different storage services. In addition, OpenDAL provides > > further advanced storage encapsulation, enabling enhancements such as > > automatic retry, request optimization, and observability. OpenDAL makes > it > > possible to develop once and run on any storage service. > > > > ## Initial Goals > > > > By transferring ownership of the project to the ASF, OpenDAL expects to > > ensure its neutrality and further encourage and facilitate the adoption > of > > OpenDAL by the community. > > > > Some of the areas we would like to focus on during the Apache incubation > > phase include: > > > > - A healthier community: more maintainers and contributors will be able > to > > participate in OpenDAL and own different modules. > > - Wider adoption: OpenDAL can be adopted by more open source/commercial > > projects, which in turn drives its own functionality. > > - Richer integration: OpenDAL enables greater integration of storage > > services and offers a wider range of language bindings. >
Re: [DISCUSS] Incubating Proposal for OpenDAL
@Xuanwo: Updated. Best, tison. Xuanwo 于2023年2月19日周日 08:54写道： > @Kimm King, thanks for pointing this out! > > I did a double check on all the deps marked as Apache 2.0 with the LLVM > exception. The result is that io-lifetimes,linux-raw-sys,rustix,wasi are > all triple-licensed under Apache 2.0 with the LLVM Exception, Apache 2.0 > and MIT terms. I think they should be OK to use them as Apache 2.0. > > @tison, can you help update the proposal to change all deps under Apache > 2.0 with the LLVM exception to Apache 2.0? > > On Sun, Feb 19, 2023, at 00:17, KimmKing wrote: > > +1, it is a "delicious" project. > > > > > > BTW: "Apache-2.0 WITH LLVM-exception (5)" should be modified/removed in > future? > > > > > > > > > > > > > > -- > > > > Kimm King(kimmk...@apache.org/kimmk...@163.com) > > Apache Dubbo&ShardingSphere PMC Member > > github&twitter: kimmking > > > > > > > > > > > > At 2023-02-17 21:12:59, "Willem Jiang" wrote: > >>+1, it's an interesting project. I'd like to be a mentor of this project. > >>BTW, even though there are 37 contributors, I found Xuanwo did most > >>of the development, which is not a good bus factor[1] of this project. > >>We can make it better during the incubating process. > >> > >>[1]https://en.wikipedia.org/wiki/Bus_factor > >> > >> > >>Willem Jiang > >> > >>Twitter: willemjiang > >>Weibo: 姜宁willem > >> > >>On Fri, Feb 17, 2023 at 7:22 AM tison wrote: > >>> > >>> Hi IPMC, > >>> > >>> I would like to propose OpenDAL[1] as a new apache incubator project, > you > >>> can find the proposal[2] of OpenDAL for more detail. > >>> > >>> [1] https://github.com/datafuselabs/opendal > >>> [2] > https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal > >>> > >>> Best, > >>> tison. > >>> > >>> Full text of the proposal below: > >>> > >>> ## Abstract > >>> > >>> OpenDAL means “Open Data Access Layer”. It’s a Rust library that helps > >>> developers access data freely, painlessly, and efficiently over > multiple > >>> services, including AWS S3, HDFS, POSIX-compatible file systems, and > so on. > >>> > >>> ## Proposal > >>> > >>> OpenDAL provides the following features to support developers accessing > >>> data freely, painlessly, and efficiently: > >>> > >>> - Freely > >>> - Access different storage services in the same way > >>> - Behavior tests for all services > >>> - Cross-language/project bindings (working in progress) > >>> - Painlessly > >>> - **100%** of documents covered > >>> - Powerful [Layers]( > >>> https://opendal.databend.rs/opendal/layers/index.html) > >>> - Automatic [retry]( > >>> https://opendal.databend.rs/opendal/layers/struct.RetryLayer.html) > support > >>> - Full observability support: [logging]( > >>> https://opendal.databend.rs/opendal/layers/struct.LoggingLayer.html > >>> ), [tracing]( > >>> https://opendal.databend.rs/opendal/layers/struct.TracingLayer.html), > and > >>> [metrics]( > >>> https://opendal.databend.rs/opendal/layers/struct.MetricsLayer.html). > >>> - Native chaos testing > >>> - Native service-side encryption support > >>> - Efficiently > >>> - Zero cost: mapping to underlying API calls directly > >>> - Best effort: auto-pick the best `read`/`seek`/`next` > implementations > >>> based on services > >>> - [Auto metadata reuse]( > >>> https://opendal.databend.rs/rfcs/0561-list-metadata-reuse.html): avoid > >>> extra `metadata` calls > >>> > >>> OpenDAL was originally designed to be used by the Databend project but > is > >>> now being used by Mozilla's sccache, DeepETH's mars, and several > database > >>> startups. > >>> > >>> We believe that the OpenDAL project will provide diversity value to the > >>> community if OpenDAL is brought into the Apache incubator. > >>> > >>> ## Background > >>> > >>> OpenDAL is being developed by an open-source community from day one > and is > >>>
Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0-rc2
+1 (binding) Verified: - [X] Download links are valid. - [X] Checksums and PGP signatures are valid. - [X] Source code artifacts have correct names matching the current release. - [X] LICENSE, NOTICE and DISCLAIMER are correct for the repository. - [X] All files have license headers if necessary. - [X] No compiled archives bundled in the source archive. - [X] Building is OK with: ./x.py build --ninja --ghproxy - [X] Stage docker image runs and serves properly Best, tison. Pengbo Cai 于2023年2月19日周日 15:24写道： > Hello Incubator PMC, > > The Apache Kvrocks community has voted and approved the release of Apache > Kvrocks(incubating) 2.3.0-rc2. We now kindly request the IPMC members > review and vote for this release. > > We modified some of the issues about license that were raised in the rc1 > vote, please refer to rc1 thread: > https://lists.apache.org/thread/q11wxgg3hdw694w5csf43trgv7yvj2jt > > Kvrocks is a distributed key value NoSQL database that uses RocksDB as the > storage engine and is compatible with Redis protocol. The current release > provides many new features, many improvements and fixes many bugs. > > Kvrocks community vote thread: > *https://lists.apache.org/thread/n2tv349f3w31yshofktgsx3drc1svc9r > <https://lists.apache.org/thread/n2tv349f3w31yshofktgsx3drc1svc9r>* > > Kvrocks community vote result thread: > *https://lists.apache.org/thread/nm9ythpw3txqwyg6r538h7rlqszw17dh > <https://lists.apache.org/thread/nm9ythpw3txqwyg6r538h7rlqszw17dh>* > > The release candidate: > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/ > > This release has been signed with a PGP available here: > https://downloads.apache.org/incubator/kvrocks/KEYS > > Git tag for the release: > *https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0-rc2 > <https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0-rc2>* > > Docker image: > https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256- > 5e75345ae8193619cb7d92daea180f1d89c2024662f4858ec38adc02b49131b0 > <https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-5e75345ae8193619cb7d92daea180f1d89c2024662f4858ec38adc02b49131b0> > > Build guide can be found at: > https://github.com/apache/incubator-kvrocks#build > > The vote will be open for at least 72 hours or until the necessary number > of votes is reached. > > Please vote accordingly: > [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.3.0-rc2 > [ ] +0 > [ ] -1 Do not approve (please specify the reason) > > > Thanks, > Pengbo Cai >
[VOTE] Accept OpenDAL into the Apache Incubator
Hi all, Following up on the [DISCUSS] thread on OpenDAL[1], I would like to call a VOTE to accept OpenDAL into the Apache Incubator, please check out the OpenDAL Proposal from the incubator wiki[2]. Please cast your vote: [ ] +1, bring OpenDAL into the Incubator [ ] +0, I don't care either way [ ] -1, do not bring OpenDAL into the Incubator, because... The vote will open at least for 72 hours, and only votes from the Incubator PMC members are binding, but votes from everyone are welcome. [1] https://lists.apache.org/thread/px7wjcjy3rd4s59d4d3ll1x6y11d240r [2] https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal Best, tison.
Re: [DISCUSS] Incubating Proposal for OpenDAL
I have started a VOTE thread for accepting OpenDAL on https://lists.apache.org/thread/3v9g2nk734m2zplrq1fgozc7xt169bgt. Welcome to vote in the dedicated thread :) Best, tison. Xiaoqiao He 于2023年2月20日周一 00:41写道： > +1. Good luck! > > Thanks for starting this thread, tison! > > I'm glad to be one mentor of this project. > Hope this interesting project could be accepted by apache incubator, and > push forward more > healthily and build a better community! > > Best Regards, > - He Xiaoqiao > > On Sun, Feb 19, 2023 at 21:58 Xin Wang wrote: > > > +1 > > Thanks for the interesting proposal! > > OpenDAL reduces the complexity of users' use of cloud storage services. > And > > look forward to a growing and healthy community during the incubation > > period. > > > > Sheng Wu 于2023年2月19日周日 17:06写道： > > > > > It is good to see you make the preparation ready so quickly. > > > Hope you woenjobe benefit of joining the ASF for.building a more > diverse > > > and bigger community. > > > > > > hulk 于2023年2月19日 周日16:42写道： > > > > > > > +1, good luck. > > > > > > > > On Sun, 19 Feb 2023 at 10:18, tison wrote: > > > > > > > > > > @Xuanwo: Updated. > > > > > > > > > > Best, > > > > > tison. > > > > > > > > > > > > > > > Xuanwo 于2023年2月19日周日 08:54写道： > > > > > > > > > > > @Kimm King, thanks for pointing this out! > > > > > > > > > > > > I did a double check on all the deps marked as Apache 2.0 with > the > > > LLVM > > > > > > exception. The result is that > > io-lifetimes,linux-raw-sys,rustix,wasi > > > > are > > > > > > all triple-licensed under Apache 2.0 with the LLVM Exception, > > Apache > > > > 2.0 > > > > > > and MIT terms. I think they should be OK to use them as Apache > 2.0. > > > > > > > > > > > > @tison, can you help update the proposal to change all deps under > > > > Apache > > > > > > 2.0 with the LLVM exception to Apache 2.0? > > > > > > > > > > > > On Sun, Feb 19, 2023, at 00:17, KimmKing wrote: > > > > > > > +1, it is a "delicious" project. > > > > > > > > > > > > > > > > > > > > > BTW: "Apache-2.0 WITH LLVM-exception (5)" should be > > > > modified/removed in > > > > > > future? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > Kimm King(kimmk...@apache.org/kimmk...@163.com) > > > > > > > Apache Dubbo&ShardingSphere PMC Member > > > > > > > github&twitter: kimmking > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > At 2023-02-17 21:12:59, "Willem Jiang" > > > > > wrote: > > > > > > >>+1, it's an interesting project. I'd like to be a mentor of > this > > > > project. > > > > > > >>BTW, even though there are 37 contributors, I found Xuanwo did > > > most > > > > > > >>of the development, which is not a good bus factor[1] of this > > > > project. > > > > > > >>We can make it better during the incubating process. > > > > > > >> > > > > > > >>[1]https://en.wikipedia.org/wiki/Bus_factor > > > > > > >> > > > > > > >> > > > > > > >>Willem Jiang > > > > > > >> > > > > > > >>Twitter: willemjiang > > > > > > >>Weibo: 姜宁willem > > > > > > >> > > > > > > >>On Fri, Feb 17, 2023 at 7:22 AM tison > > > wrote: > > > > > > >>> > > > > > > >>> Hi IPMC, > > > > > > >>> > > > > > > >>> I would like to propose OpenDAL[1] as a new apache incubator > > > > project, > > > > > > you >
Re: [VOTE] Accept OpenDAL into the Apache Incubator
+1 (binding) Thanks for your participation! I'll call a result soon. Best, tison. Eason Chen 于2023年2月24日周五 14:25写道： > +1 non-binding > > Good Luck! > > Eason Chen > Apache EventMesh > > On Fri, Feb 24, 2023 at 1:21 PM Furkan KAMACI > wrote: > > > > Hi, > > > > +1 (binding) > > > > Kind regards, > > Furkan Kamaci > > > > On Thu, Feb 23, 2023 at 2:47 PM Yu Xiao wrote: > > > > > +1 non-binding > > > > > > Best wishes! > > > > > > Yu Xiao > > > Apache ShenYu > > > > > > Charles Zhang 于2023年2月23日周四 18:33写道： > > > > > > > > +1 (non-binding) > > > > Good luck. > > > > > > > > Best wishes, > > > > Charles Zhang > > > > from Apache InLong > > > > > > > > > > > > Kaijie Chen 于2023年2月23日周四 17:56写道： > > > > > > > > > +1 (non-binding) > > > > > Good luck. > > > > > > > > > > Kaijie > > > > > > > > > > On 2023/02/23 07:47:24 Enrico Olivelli wrote: > > > > > > +1 (non binding) > > > > > > > > > > > > In the future maybe this project may add some java bindings and > work > > > as a > > > > > > replacement for the retiring JClouds project > > > > > > > > > > > > Enrico > > > > > > > > > > > > Il Gio 23 Feb 2023, 06:14 li gang ha > scritto: > > > > > > > > > > > > > +1 (binding) > > > > > > > Good luck. > > > > > > > > > > > > > > tison 于2023年2月21日周二 21:24写道： > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > Following up on the [DISCUSS] thread on OpenDAL[1], I would > like > > > to > > > > > call > > > > > > > a > > > > > > > > VOTE to accept OpenDAL into the Apache Incubator, please > check > > > out > > > > > the > > > > > > > > OpenDAL Proposal from the incubator wiki[2]. > > > > > > > > > > > > > > > > Please cast your vote: > > > > > > > > > > > > > > > > [ ] +1, bring OpenDAL into the Incubator > > > > > > > > [ ] +0, I don't care either way > > > > > > > > [ ] -1, do not bring OpenDAL into the Incubator, because... > > > > > > > > > > > > > > > > The vote will open at least for 72 hours, and only votes > from the > > > > > > > Incubator > > > > > > > > PMC members are binding, but votes from everyone are welcome. > > > > > > > > > > > > > > > > [1] > > > https://lists.apache.org/thread/px7wjcjy3rd4s59d4d3ll1x6y11d240r > > > > > > > > [2] > > > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal > > > > > > > > > > > > > > > > Best, > > > > > > > > tison. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Best Regards > > > > > > > > > > > > > > DolphinScheduler PMC > > > > > > > Gang Li 李岗 > > > > > > > > > > > > > > lgcar...@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 > > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[RESULT][VOTE] Accept OpenDAL into the Apache Incubator
Hi all, Thanks to everyone who participated in the vote! The voting is now closed and it has passed with 8 binding +1, 14 non-binding +1, and no 0 or -1 votes. +1 bindings: PJ Fanning Willem Jiang Xiaoqiao He Sheng Wu Gordon li gang Furkan KAMACI tison +1 non-bindings: Twice Cheng Pan Huajie Wang Xin Wang Xinyi Zhou Mengyang Tang Zhang Yonglun Keyong Zhou Jialin Qiao Enrico Olivelli Kaijie Chen Charles Zhang Yu Xiao Eason Chen Best, tison.
Re: [VOTE] Accept Paimon into the Apache Incubator
+1 (binding) Nice to meet Paimon :) Best, tison. Cheng Pan 于2023年3月6日周一 16:38写道： > +1 (non-binding), good luck > > Thanks, > Cheng Pan > > > On Mar 6, 2023 at 16:29:24, Nicholas Jiang > wrote: > > > Hi Guys, > > > > +1(not-binding). > > > > Regards, > > Nicholas Jiang > > > > On 2023/03/06 08:08:14 Calvin Kirs wrote: > > > > Hi, > > > > +1(binding). > > > > Enjoy your trip to the incubator :) > > > > > > On Mon, Mar 6, 2023 at 3:59 PM Yu Li wrote: > > > > > > > > > > Hi All, > > > > > > > > > > Following up on the [DISCUSS] thread on Paimon [1], I would like to > call > > > > > a VOTE to accept Paimon into the Apache Incubator, please check out > > > > > the Paimon Proposal from the incubator wiki [2]. > > > > > > > > > > > > > > > Please cast your vote: > > > > > > > > > > > > > > > [ ] +1, bring Paimon into the Incubator > > > > > > > > > > [ ] +0, I don't care either way > > > > > > > > > > [ ] -1, do not bring Paimon into the Incubator, because... > > > > > > > > > > > > > > > The vote will open at least for 72 hours, and only votes from the > > Incubator > > > > > PMC are binding, but votes from everyone are welcome. > > > > > > > > > > Best Regards, > > > > > Yu > > > > > > > > > > [1] https://lists.apache.org/thread/hr3d7tpw02w6ybrnnlf3hcbhfxotwpvn > > > > > [2] > https://cwiki.apache.org/confluence/display/INCUBATOR/PaimonProposal > > > > > > > > > > -- > > > > Best wishes！ > > > > CalvinKirs > > > > > > - > > > > 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 > > > > >
Confluence wiki page gives "Unknown macro: markdown"
For example, https://cwiki.apache.org/confluence/display/INCUBATOR/March2023 I found some possible debugging info, but I don't have permission to try it: https://community.atlassian.com/t5/Confluence-questions/Unknown-macro-code/qaq-p/820495 Any confluence space maintainer may take a look? Best, tison.
Re: [VOTE] Release Apache Kvrocks(incubating) 2.4.0-rc1
+1 (binding) * LICENSE / NOTICE / DISCLAIMER exist * GPG sign and checksum match * Build from source successfully and run some simple commands Best, tison. Xiaoqiao He 于2023年5月3日周三 00:04写道： > +1(binding) > > Best Regards, > - He Xiaoqiao > > On Mon, May 1, 2023 at 7:44 PM Liang Chen wrote: > > > +1(binding) > > > > Regards > > Liang > > > > > > Twice 于 2023年4月29日周六 10:17写道： > > > > > +1 (non-binding) > > > > > > Best, > > > Twice > > > > > > > > > On Fri, Apr 28, 2023 at 7:19 PM hulk wrote: > > > > > > > > Carry my +1 vote from the community. > > > > > > > > On Fri, 28 Apr 2023 at 15:37, xiaobiao zhao < > zhaoxiaobia...@gmail.com> > > > > wrote: > > > > > > > > > Hello Incubator PMC, > > > > > > > > > > The Apache Kvrocks community has voted and approved the release of > > > Apache > > > > > Kvrocks(incubating) 2.4.0-rc1. We now kindly request the IPMC > members > > > > > review and vote for this release. > > > > > > > > > > Kvrocks is a distributed key value NoSQL database that uses RocksDB > > as > > > the > > > > > storage engine > > > > > and is compatible with Redis protocol. The current release provides > > > many > > > > > new features, many improvements and fixes many bugs. > > > > > > > > > > Kvrocks community vote thread: > > > > > > > > > > https://lists.apache.org/thread/rchh8fqq6syzptlx28mfq2yt2f61zmp8 > > > > > > > > > > Vote result thread: > > > > > > > > > > https://lists.apache.org/thread/21wwvf7y8p2dsgrvt5dcwpot925kkoqs > > > > > > > > > > The release candidate: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.4.0 > > > > > > > > > > This release has been signed with a PGP available here: > > > > > > > > > > https://downloads.apache.org/incubator/kvrocks/KEYS > > > > > > > > > > Git tag for the release: > > > > > > > > > > > https://github.com/apache/incubator-kvrocks/releases/tag/v2.4.0-rc1 > > > > > > > > > > Docker image: > > > > > > > > > > > > > > > > https://hub.docker.com/layers/zhaoxiaobiao/kvrocks/2.4.0/images/sha256-6f04c9fd3f60ddc88177c80f5dcbd41320e81de1d41347a1281fe87da98133c6 > > > > > > > > > > > > > > > Build guide can be found at: > > > > > > > > > > https://github.com/apache/incubator-kvrocks#build > > > > > > > > > > The vote will be open for at least 72 hours or until the necessary > > > number > > > > > of votes is reached. > > > > > Please vote accordingly: > > > > > [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.4.0-rc1 > > > > > [ ] +0 > > > > > [ ] -1 Do not approve (please specify the reason) > > > > > > > > > > To learn more about apache kvrocks, please see > > > > > https://kvrocks.apache.org/ > > > > > > > > > > Checklist for reference: > > > > > > > > > > [ ] Download links are valid. > > > > > [ ] Checksums and signatures. > > > > > [ ] LICENSE/NOTICE files exist > > > > > [ ] No unexpected binary files > > > > > [ ] All source files have ASF headers > > > > > [ ] Can compile from source > > > > > [ ] All Tests Passed > > > > > [ ] Docker image with right version > > > > > [ ] Docker image contains license files > > > > > [ ] Docker image can work well > > > > > > > > > > More detailed checklist please refer to: > > > > > > > https://kvrocks.apache.org/community/verify-a-release-candidate > > > > > > > > > > Thanks > > > > > > > > > > > > > > > > > -- > > > > Best Regards, > > > > - *Hulk Lin* > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > >
Re: [VOTE] Release Apache StreamPark(Incubating) 2.1.0-rc1
+1 (binding) - LICENSE and NOTICE present - DISCLAIMER present - GPG sign is correct "muchunjin (for apache StreamPark release create at 20230501) " - Checksum 512 match - Build with JDK 8 & Scala 2.12 on macOS M1 - No binary files in the source release Best, tison. Willem Jiang 于2023年5月7日周日 15:01写道： > +1, > I just ran the script with JDK11 to build the release kit from the > source with the command without any error. > Here is what I checked: > - The checksums and signatures are validated. > - The LICENSE and NOTICE files look good to me. > - There is DISCLAIMER-WIP > - No binary files in the source release > - I can build the binary from the source kit. > > Thanks, > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > On Sat, May 6, 2023 at 7:57 PM Chunjin Mu wrote: > > > > Hello mentor, please see line 182 in the build.sh script, the latest > > compilation command is as follows > > > > mvn -Pscala-2.11,shaded,webapp,dist -DskipTests clean install > > mvn -Pscala-2.12,shaded,webapp,dist -DskipTests clean install > > > > Best, > > ChunJin Mu > > > > > > Willem Jiang 于2023年5月6日周六 19:13写道： > > > > > When I tried to build the artifact from the source, I got the below > > > error. I cannot find > > > org.apache.streampark:streampark-shaded-slf4j:jar:1.0.0 from the maven > > > central repo. > > > > > > Failed to execute goal on project streampark-common_2.12: Could not > > > resolve dependencies for project > > > org.apache.streampark:streampark-common_2.12:jar:2.1.0: The following > > > artifacts could not be resolved: > > > org.apache.streampark:streampark-shaded-slf4j:jar:1.0.0, > > > org.apache.streampark:streampark-shaded-jackson:jar:1.0.0: > > > org.apache.streampark:streampark-shaded-slf4j:jar:1.0.0 was not found > > > in https://repo.maven.apache.org/maven2 during a previous attempt. > > > > > > Did I miss something? > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Fri, May 5, 2023 at 11:47 PM Chunjin Mu > wrote: > > > > > > > > Hello Incubator Community: > > > > > > > > This is a call for a vote to release Apache StreamPark(Incubating) > > > version 2.1.0-RC1. > > > > The Apache StreamPark community has voted on and approved a proposal > to > > > release Apache StreamPark(Incubating) version 2.1.0-RC1. > > > > We now kindly request the Incubator PMC members review and vote on > this > > > incubator release. > > > > Apache StreamPark, Make stream processing easier! easy-to-use > streaming > > > application development framework and operation platform. > > > > > > > > StreamPark community vote thread: > > > > https://lists.apache.org/thread/t01b2lbtqzyt7j4dsbdp5qjc3gngjsdq > > > > > > > > Vote result thread: > > > > https://lists.apache.org/thread/t5z58mvrs1drgzfyc48c9lhmd8skswn7 > > > > > > > > The release candidate: > > > > > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.1.0-RC1/ > > > > > > > > Git tag for the release: > > > > > https://github.com/apache/incubator-streampark/releases/tag/v2.1.0-rc1 > > > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > > https://repository.apache.org/content/repositories/orgapachestreampark-1012/ > > > > > > > > The artifacts signed with PGP key [05016886], corresponding to [ > > > muchun...@apache.org], that can be found in keys file: > > > > https://downloads.apache.org/incubator/streampark/KEYS > > > > > > > > The vote will be open for at least 72 hours or until the necessary > > > number of votes are reached. > > > > > > > > Please vote accordingly: > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > > > > > More detailed checklist please refer: > > > > • > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > > > > > Steps to validate the release， Please refer to: > > > > • https://www.apache.org/info/verification.html > > > > • https://streampark.apache.org/community/release/how-to-verify > > > > > > > > > > > > How to Build: > > > > > > > > 1) clone source code: > > > > > git clone -b v2.1.0-rc1 g...@github.com: > apache/incubator-streampark.git > > > > > > > > 2) build project: > > > > > cd incubator-streampark && sh ./build.sh > > > > > > > > > > > > Thanks, > > > > > > > > On behalf of Apache StreamPark(Incubating) community > > > > > > > > > > > > Best, > > > > ChunJin Mu > > > >
Re: [VOTE] Graduate Apache Kvrocks(incubating) as a TLP
+1 (binding) Kvrocks has a strong community with diversity in users, developers, and release managers. I'm confident in its sustainability. Best, tison. PJ Fanning 于2023年5月13日周六 17:32写道： > +1 (binding) > > Kvrocks project seems to be in a very healthy position to move forward as > a TLP. > > On Sat, 13 May 2023 at 09:43, Yuan Wang wrote: > > > > +1 (non-binding) > > > > We already used it for several years in production environment, very glad > > to see this happen, good luck! > > > > Best Regards > > Yuan Wang > > > > peacewong 于2023年5月13日周六 13:55写道： > > > > > +1 (non-binding) > > > > > > Good Luck! > > > > > > Best regards, > > > Peace Wong > > > Liang Chen 于2023年5月13日周六 13:50写道： > > > > > > > +1(binding) > > > > > > > > Regards > > > > Liang > > > > > > > > hulk 于2023年5月12日周五 05:55写道： > > > > > > > > > Hello all, > > > > > > > > > > We've got positive feedback on the DISCUSS thread[1], I'd like to > start > > > > an > > > > > official VOTE thread now. > > > > > > > > > > Please vote on the resolution pasted below to graduate Apache > Kvrocks > > > > from > > > > > the incubator to the Top Level Project. > > > > > > > > > > [ ] +1 Graduate Apache Kvrocks from the Incubator. > > > > > [ ] +0 No opinion. > > > > > [ ] -1 Don't graduate Apache Kvrocks from the Incubator because ... > > > > > > > > > > This vote will open for at least 72 hours. > > > > > > > > > > Many thanks to our mentors and everyone else for their support. > > > > > > > > > > [1] > https://lists.apache.org/thread/ld8x1wvh1n745j96ksy0pmy92gwn2t06 > > > > > > > > > > --- > > > > > > > > > > Establish the Apache Kvrocks Project > > > > > > > > > > WHEREAS, the Board of Directors deems it to be in the best > interests of > > > > > the Foundation and consistent with the Foundation's purpose to > > > establish > > > > > a Project Management Committee charged with the creation and > > > maintenance > > > > > of open-source software, for distribution at no charge to the > public, > > > > > related to a distributed key-value NoSQL database, supporting the > rich > > > > > data structure. > > > > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > > > (PMC), to be known as the "Apache Kvrocks Project", be and hereby > is > > > > > established pursuant to Bylaws of the Foundation; and be it further > > > > > > > > > > RESOLVED, that the Apache Kvrocks Project be and hereby is > responsible > > > > > for the creation and maintenance of software related to a > distributed > > > > > key-value NoSQL database, supporting the rich data structure; and > be it > > > > > further > > > > > > > > > > RESOLVED, that the office of "Vice President, Apache Kvrocks" 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 > Kvrocks > > > > > Project, and to have primary responsibility for management of the > > > > > projects within the scope of responsibility of the Apache Kvrocks > > > > > 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 Kvrocks > > > Project: > > > > > > > > > > * Alfejik Liu > > > > > * Hulk Lin > > > > > * Jean-Baptiste Onofré > > > > > * Liang Chen > > > > > * Mingyang Liu > > > > > * Von Gosling > > > > > * Xiaoqiao He > > > > > * Yaroslav Stepanchuk > > > > > * Yuan Wang > > > > > * Zili Chen > > > > > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hulk Lin be appointed > to > > > > > the office of Vice President, Apache Kvrocks, to serve in > accordance > > > > > with and subject to the direction of the Board of Directors and the > > > > > Bylaws of the Foundation until death, resignation, retirement, > removal > > > > > or disqualification, or until a successor is appointed; and be it > > > > > further > > > > > > > > > > RESOLVED, that the Apache Kvrocks Project be and hereby is tasked > with > > > > > the migration and rationalization of the Apache Incubator Kvrocks > > > > > podling; and be it further > > > > > > > > > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator > > > > > Kvrocks podling encumbered upon the Apache Incubator PMC are > hereafter > > > > > discharged. > > > > > > > > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache OpenDAL(incubating) 0.34.0-rc1
+1 (binding) I checked: + Download links are valid. + Checksums and signatures - although the SIGNING KEY has multiple entries, it contains xua...@apache.org so I think it's OK. + LICENSE/NOTICE files exist + DISCLAIMER files exist + No unexpected binary files + All source files have ASF headers + Can compile from source on macOS M1 with "cargo build" Best, tison. Xuanwo 于2023年5月17日周三 12:14写道： > Hello Incubator PMC, > > The Apache OpenDAL community has voted and approved the release of Apache > OpenDAL(incubating) 0.34.0-rc1. We now kindly request the IPMC members > review and vote for this release. > > OpenDAL is a data access layer that allows users to easily and efficiently > retrieve data from various storage services in a unified way. > > OpenDAL community vote thread: > > https://lists.apache.org/thread/nh80zh9y11frx7ls9fn4dvj1hdh2n4pb > > Vote result thread: > > https://lists.apache.org/thread/hjkxdvqr1dsrq71cr6j7ltjxvwmn0jg2 > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.34.0-rc1/ > > This release has been signed with a PGP available here: > > https://downloads.apache.org/incubator/opendal/KEYS > > Git branch for the release: > > https://github.com/apache/incubator-opendal/tree/release-0.34.0-rc1 > > Please download, verify, and test. > > The VOTE will pass after got 3 binding approve. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > To learn more about apache opendal, please see https://opendal.apache.org/ > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and signatures. > [ ] LICENSE/NOTICE files exist > [ ] No unexpected binary files > [ ] All source files have ASF headers > [ ] Can compile from source > > More detailed checklist please refer to: > https://github.com/apache/incubator-opendal/tree/main/scripts > > To compile from source, please refer to: > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md > > Thanks > > Xuanwo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache OpenDAL(incubating) 0.34.0-rc1
>These License information should be put into the License file. Any requirement for this statement? In ASF projects I involve, I always put dependencies info in the NOTICE file and leave the LICENSE file AS IS from https://apache.org/licenses/LICENSE-2.0.txt. Best, tison. Willem Jiang 于2023年5月19日周五 22:03写道： > I checked the NOTICE file, it includs the third-party dependencies > license information. > These License information should be put into the License file. > Some third-party dependency Licenses are Apache or MIT, we can choose > Apache License by default. > > I cannot find how to build from the README.md file in the root > directory. Did I miss something? > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, May 17, 2023 at 12:14 PM Xuanwo wrote: > > > > Hello Incubator PMC, > > > > The Apache OpenDAL community has voted and approved the release of Apache > > OpenDAL(incubating) 0.34.0-rc1. We now kindly request the IPMC members > > review and vote for this release. > > > > OpenDAL is a data access layer that allows users to easily and > efficiently > > retrieve data from various storage services in a unified way. > > > > OpenDAL community vote thread: > > > > https://lists.apache.org/thread/nh80zh9y11frx7ls9fn4dvj1hdh2n4pb > > > > Vote result thread: > > > > https://lists.apache.org/thread/hjkxdvqr1dsrq71cr6j7ltjxvwmn0jg2 > > > > The release candidate: > > > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.34.0-rc1/ > > > > This release has been signed with a PGP available here: > > > > https://downloads.apache.org/incubator/opendal/KEYS > > > > Git branch for the release: > > > > https://github.com/apache/incubator-opendal/tree/release-0.34.0-rc1 > > > > Please download, verify, and test. > > > > The VOTE will pass after got 3 binding approve. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > To learn more about apache opendal, please see > https://opendal.apache.org/ > > > > Checklist for reference: > > > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist > > [ ] No unexpected binary files > > [ ] All source files have ASF headers > > [ ] Can compile from source > > > > More detailed checklist please refer to: > > https://github.com/apache/incubator-opendal/tree/main/scripts > > > > To compile from source, please refer to: > > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md > > > > Thanks > > > > Xuanwo > > > > - > > 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 OpenDAL(incubating) 0.34.0-rc1
You may use apache-opendal-incubating-0.34.0-src.tag.gz instead. Best, tison. Xuanwo 于2023年5月23日周二 13:06写道： > Oh, my mistake, thank you all! > > On Tue, May 23, 2023, at 13:02, Justin Mclean wrote: > > HI, > > > >>> - “incubating" is not in the release name > >> > >> Could you please explain the phrase "not in the release name"? Our > release includes the term "incubating," such as > "apache-incubator-opendal-0.34.0-src.tar.gz.” > > > > That's “incubator” not “incubating”. > > > > Kind Regards, > > Justin > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > -- > Xuanwo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Graduate Apache DataLab (Incubating) as a Top Level Project
Hi, Thanks for bringing this topic here! Apart from the last elected committer and PPMC member part, the last commit of the project except dependabot happened on Nov 10, 2022. Can you provide a bit more information about the project status on its development and users? For example, is it mature enough to be updated infrequently? What is the diversity of its developer and known users? Best, tison. Denys Yankiv 于2023年5月22日周一 20:17写道： > Hi Justin, > > I'm happy to let you know that we have successfully resolved the issues > you mentioned earlier. > All PPMC members are now subscribed to the private mailing list, > and you can find the ongoing discussion about DataLab naming by following > this link: > https://lists.apache.org/thread/7rz5w9ocq13mjn99nxck19n6mh884lk5 > > Apologies for the delayed response. > Now, I'd like to inquire if we can proceed with the voting process. > > Best regards, > Denys Yankiv > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
ASF Maven credential in a project-wise token?
Hi, I'm configuring tokens for automatically deploying artifacts to the ASF snapshot repository[1]. It requires configuring a user token to auth to the repository. Although I'm wondering if I must use my personal token or if there is some project-wise token to use. Even asking for an INFRA member to help configure, passing over a personal token to another one increases the risk. Best, tison. [1] https://github.com/tisonkun/opendal/actions/runs/5090173050/workflow#L129
Re: ASF Maven credential in a project-wise token?
Hi Christofer, Thanks for your reply! Two questions here: 1. Are there instructions to set up such Jenkins workflow? I remember that the last few time I try to set up a hello-world workflow for another ASF project but fail to get it right. I read some of the INFRA pages but still I don't know how to create a project and how to properly configure the workflow. > the credentials are there 2. Who's credentials? Best, tison. Christofer Dutz 于2023年5月27日周六 05:08写道： > If you run the build on asf Jenkins the credentials are there. You just > need to inherit from the latest apache pom and it should work. > > Chris > > Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> > ____ > From: tison > Sent: Friday, May 26, 2023 1:33:29 PM > To: Maven Developers List ; Incubator < > general@incubator.apache.org> > Subject: ASF Maven credential in a project-wise token? > > Hi, > > I'm configuring tokens for automatically deploying artifacts to the ASF > snapshot repository[1]. > > It requires configuring a user token to auth to the repository. Although > I'm wondering if I must use my personal token or if there is some > project-wise token to use. Even asking for an INFRA member to help > configure, passing over a personal token to another one increases the risk. > > Best, > tison. > > [1] > https://github.com/tisonkun/opendal/actions/runs/5090173050/workflow#L129 >
Re: [VOTE] Release Apache OpenDAL(incubating) 0.35.0-rc1
+1 (binding) I checked - [x] Download links are valid. [x] Checksums and signatures. [x] + incubating in artifacts name [x] LICENSE/NOTICE files exist + DISCLAIMER exists [x] No unexpected binary files [x] All source files have ASF headers [x] Can compile from source Best, tison. Xuanwo 于2023年5月25日周四 14:58写道： > Hello Incubator PMC, > > The Apache OpenDAL community has voted and approved the release of Apache > OpenDAL(incubating) 0.35.0-rc1. We now kindly request the IPMC members > review and vote for this release. > > OpenDAL is a data access layer that allows users to easily and efficiently > retrieve data from various storage services in a unified way. > > OpenDAL community vote thread: > > https://lists.apache.org/thread/lxn4ssg4tsvgvfwmcfv3h9wzqtprpjdf > > Vote result thread: > > https://lists.apache.org/thread/ygcyxsoy71zh2gyjh2kyr4qjf2ohd0or > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.35.0-rc1/ > > This release has been signed with a PGP available here: > > https://downloads.apache.org/incubator/opendal/KEYS > > Git branch for the release: > > https://github.com/apache/incubator-opendal/tree/release-0.35.0-rc1 > > Please download, verify, and test. > > The VOTE will pass after got 3 binding approve. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > To learn more about apache opendal, please see https://opendal.apache.org/ > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and signatures. > [ ] LICENSE/NOTICE files exist > [ ] No unexpected binary files > [ ] All source files have ASF headers > [ ] Can compile from source > > More detailed checklist please refer to: > https://github.com/apache/incubator-opendal/tree/main/scripts > > To compile from source, please refer to: > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md > > Thanks > > > Xuanwo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: ASF Maven credential in a project-wise token?
Thanks for your reference, Martin!
cc dev@opendal.a.o - I'm going to open a branch on the upstream repo to
verify this setting when I find some time.
Best,
tison.
Martin Grigorov 于2023年5月29日周一 16:21写道：
> Hi,
>
> Here is a setup using username and password provided by the Infra team -
>
> https://github.com/apache/avro/blob/0be01a58bd7586982953dda45d53ac3551c7b6c4/.github/workflows/java-publish-snapshot.yml#L56-L62
>
> - name: Deploy Maven snapshots
> env:
> ASF_USERNAME: ${{ secrets.NEXUS_USER }}
> ASF_PASSWORD: ${{ secrets.NEXUS_PW }}
> run: |
> echo
>
> "apache.snapshots.https$ASF_USERNAME$ASF_PASSWORD"
> > settings.xml
> mvn --settings settings.xml -U -B -e -fae -ntp -DskipTests deploy
>
> I am not sure whether those are available per project or globally for the
> 'apache' Github organization.
> Try it and if it fails then contact the Infra team to add them for your
> project.
>
> On Sat, May 27, 2023 at 6:19 AM tison wrote:
>
> > Hi Christofer,
> >
> > Thanks for your reply! Two questions here:
> >
> > 1. Are there instructions to set up such Jenkins workflow? I remember
> that
> > the last few time I try to set up a hello-world workflow for another ASF
> > project but fail to get it right. I read some of the INFRA pages but
> still
> > I don't know how to create a project and how to properly configure the
> > workflow.
> >
> > > the credentials are there
> >
> > 2. Who's credentials?
> >
> > Best,
> > tison.
> >
> >
> > Christofer Dutz 于2023年5月27日周六 05:08写道：
> >
> > > If you run the build on asf Jenkins the credentials are there. You just
> > > need to inherit from the latest apache pom and it should work.
> > >
> > > Chris
> > >
> > > Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
> > >
> > > From: tison
> > > Sent: Friday, May 26, 2023 1:33:29 PM
> > > To: Maven Developers List ; Incubator <
> > > general@incubator.apache.org>
> > > Subject: ASF Maven credential in a project-wise token?
> > >
> > > Hi,
> > >
> > > I'm configuring tokens for automatically deploying artifacts to the ASF
> > > snapshot repository[1].
> > >
> > > It requires configuring a user token to auth to the repository.
> Although
> > > I'm wondering if I must use my personal token or if there is some
> > > project-wise token to use. Even asking for an INFRA member to help
> > > configure, passing over a personal token to another one increases the
> > risk.
> > >
> > > Best,
> > > tison.
> > >
> > > [1]
> > >
> >
> https://github.com/tisonkun/opendal/actions/runs/5090173050/workflow#L129
> > >
> >
>
Re: [VOTE] Release Apache OpenDAL(incubating) 0.36.0-rc1
+1 (binding) I checked - [x] Download links are valid. [x] Checksums and signatures. [x] + incubating in artifacts name [x] LICENSE/NOTICE files exist + DISCLAIMER exists [x] No unexpected binary files [x] All source files have ASF headers [x] Can compile from source - with `cargo build' Best, tison. Xuanwo 于2023年6月1日周四 10:34写道： > Hello Incubator PMC, > > The Apache OpenDAL community has voted and approved the release of Apache > OpenDAL(incubating) 0.36.0-rc1. We now kindly request the IPMC members > review and vote for this release. > > OpenDAL is a data access layer that allows users to easily and efficiently > retrieve data from various storage services in a unified way. > > OpenDAL community vote thread: > > https://lists.apache.org/thread/c211gqq2yl15jbxqk4rcnq1bdqltjm5l > > Vote result thread: > > https://lists.apache.org/thread/xk5myl10mztcfotn59oo59s4ckvojds6 > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.36.0-rc1/ > > This release has been signed with a PGP available here: > > https://downloads.apache.org/incubator/opendal/KEYS > > Git branch for the release: > > https://github.com/apache/incubator-opendal/tree/release-0.36.0-rc1 > > Please download, verify, and test. > > The VOTE will pass after got 3 binding approve. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > To learn more about apache opendal, please see https://opendal.apache.org/ > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and signatures. > [ ] LICENSE/NOTICE files exist > [ ] No unexpected binary files > [ ] All source files have ASF headers > [ ] Can compile from source > > More detailed checklist please refer to: > https://github.com/apache/incubator-opendal/tree/main/scripts > > To compile from source, please refer to: > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md > > Thanks > > Xuanwo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache OpenDAL (incubating) 0.36.0-rc1 (Round 2)
+1 (binding) I checked - [x] Download links are valid. [x] Checksums and signatures. [x] + incubating in artifacts name [x] LICENSE/NOTICE files exist + DISCLAIMER exists [x] No unexpected binary files [x] All source files have ASF headers [x] Can compile from source - with `cargo build' Best, tison. Xuanwo 于2023年6月3日周六 19:50写道： > Hello Incubator PMC, > > The Apache OpenDAL community has voted and approved the release of Apache > OpenDAL(incubating) 0.36.0-rc1. We now kindly request the IPMC members > review and vote for this release. > > OpenDAL is a data access layer that allows users to easily and efficiently > retrieve data from various storage services in a unified way. > > OpenDAL community vote thread: > > https://lists.apache.org/thread/c211gqq2yl15jbxqk4rcnq1bdqltjm5l > > Vote result thread: > > https://lists.apache.org/thread/xk5myl10mztcfotn59oo59s4ckvojds6 > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.36.0-rc1/ > > This release has been signed with a PGP available here: > > https://downloads.apache.org/incubator/opendal/KEYS > > Git branch for the release: > > https://github.com/apache/incubator-opendal/tree/release-0.36.0-rc1 > > Please download, verify, and test. > > The VOTE will pass after got 3 binding approve. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > To learn more about apache opendal, please see https://opendal.apache.org/ > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and signatures. > [ ] LICENSE/NOTICE files exist > [ ] No unexpected binary files > [ ] All source files have ASF headers > [ ] Can compile from source > > More detailed checklist please refer to: > https://github.com/apache/incubator-opendal/tree/main/scripts > > To compile from source, please refer to: > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md > > Thanks > > Xuanwo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
