Re:[VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project
+1 At 2023-02-10 10:31:56, "Eason Chen" wrote: >Dear Apache Incubator Community and IPMC members, > >After having the graduation discussion in the EventMesh community [1], >we passed the vote within the EventMesh community [2] and the vote >result was published[3]. >We then discussed the graduation for EventMesh in the Apache Incubator >Community [4], where no issues were raised and positive replies were >received. > >I would like to start this voting thread to request graduating Apache >EventMesh(incubating) from Apache Incubator as a Top Level Project. > >Please provide your vote accordingly: >[ ] +1 Yes, I support the EventMesh project to graduate from the >Apache Incubator. >[ ] +0 No opinion. >[ ] -1 No, the EventMesh project is not ready to graduate, because... > >Thank you for participating in the vote. This vote will stay open for >at least 72 hours. > >Here is an overview of the Apache EventMesh(incubating) to help with the vote. > >*Community* > >● 5 new PPMC members were added, bringing the total number of PPMC >members to 14 from at least 9 different organizations. >● 20 new Committers were added, bringing the total number of >committers to 42 from at least 30 different organizations. >● 220+ new contributors participate in the community. The number of >contributors is now 250+ and growing. >● 20 Bi-weekly online meetings were held among the committers, >contributors, and users. The meeting minutes are recorded on the >mailing list[5] and cwiki [6]. >● The dev@eventmesh mailing list currently has 117 subscribers. >● We've confirmed the VP, PMC, and Committers in the preparation >discussion at private@eventmesh [7]. Eason >Chen(chenguangsh...@apache.org) was recommended as Vice President. > >*Project* > >● Apache EventMesh(incubating) builds a fully serverless platform for >distributed event-driven applications. >● Project maturity model is detailed in [8]. >● EventMesh has been incubating [9] since 2021-02-18 for over 23 months. >● EventMesh community released a total of 7 Apache releases [10] by 6 >different release managers from 5 different organizations. >● 1300+ issues created, and 1100+ issues closed [11]. >● 1600+ pull requests created, and 1600+ pull requests closed [12], >2500+ commits added. >● The release cadence is about 3 months, with an average of 180+ >issues and 230+ pull requests per release. >● Please refer to the EventMesh project incubation status [13][14] for >more information. > >*Brands, License, and Copyright* > >● We applied the brand [15], which has been reviewed and approved. >● EventMesh 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 [16]. >All the status files, license headers, and copyright are up to date. >● EventMesh official website [17] is compliant with Apache Foundation >requirements[18]. > >- >BEGINNING OF DRAFT RESOLUTION >- > >Establish the Apache EventMesh 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 fully serverless platform used to build distributed >event-driven applications. > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee >(PMC), to be known as the "Apache EventMesh Project", be and hereby is >established pursuant to Bylaws of the Foundation; and be it further > >RESOLVED, that the Apache EventMesh Project be and hereby is responsible >for the creation and maintenance of software related to a fully >serverless platform used to build distributed event-driven applications; >and be it further > >RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh >Project, and to have primary responsibility for management of the >projects within the scope of responsibility of the Apache EventMesh >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 EventMesh >Project: > > * Alex Luo > * Du Heng > * Eason Chen > * Francois Papon > * Jean-Baptiste Onofré > * Junping Du > * Justi
Re:[VOTE] Accept EventMesh into Apache Incubator
+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] EventMesh Proposal
I would like to make a comments about this serious problem too, In order not to cause unnecessary trouble in the future, we also request the infra member from apache to help check whether this name is appropriate[1]. For us, we have used the name EventMesh for a long time, and we want to keep it so that users can get better product positioning from this name. According to this document[2], we also searched in the US Patent Office[3] and found no non-compliance. [1] https://issues.apache.org/jira/browse/INFRA-21353 [2] https://incubator.apache.org/guides/names.html [3] https://www.uspto.gov/trademark On 01/27/2021 21:11，Eason Chen wrote： @Sheng Wu thank you for your kindly reminder. I would like to clarify this concerns. As @Duane Pauls clarified this before: “*I work for Solace and have consulted internally to confirm that we do not have any copyright or trademark on the term “Event Mesh”. It’s true it is something our products are closely aligned with。 Solace does not oppose the term being used in other applicable products or projects.*” Solace do not have any copyright or trademark on the term “Event Mesh”. On Wed, Jan 27, 2021 at 5:17 PM Sheng Wu wrote: Hi I want to send a reminder for your project name chosen. Event Mesh is widely used as a concept and term, you could find it through Google search, https://www.google.com/search?q=event+mesh=event+mesh Sheng Wu 吴晟 Twitter, wusheng1108 于2021年1月27日周三 下午5:12写道： Hi, Yes, it looks very promising. I will be very happy to help in the incubation process and integrate the project into Karaf with JB ;) regards, François fpa...@apache.org Le 27/01/2021 à 10:07, vongosling a écrit : Hi, This is a very young but promising project. The team attached great importance to this project according to the feedback given by communities. Through the efforts of the last five months, I am glad to see positive changes in the project and community. @Jean-Baptiste Onofré EventMesh really need to improve its lighter plugin modules, karaf may be a good optional Best Regards, Von Gosling Jean-Baptiste Onofre 于2021年1月27日周三 下午4:43写道： Hi Eason, That’s an interesting proposal, indeed. I would rewrite some part of the proposal, but overall good. I will check if the EventMesh architecture is "pluggable", meaning that we "could" replace RocketMQ with another messaging/async provider. Anyway, if you need some help on the project, please let me know, it’s interesting and could be a good extend to Apache Karaf for instance. Regards JB Le 27 janv. 2021 à 09:32, Eason Chen a écrit : Good time of the time to all! I'd like to bring this new interesting project for the discussion, comments and feedback with the aim of starting a formal [VOTE] of its acceptance into Incubator. People behind this project aren't new to Apache: some of them were behind the Apache RocketMQ, which I consider a huge success(especially in China) as the community is literally thriving almost 5 years after the graduation. I have been involved a little bit with this project when it just started in WeBank a few years ago. And I'd like to emphasize that the community however small it might look so far, has been aligned with Apache ways of doing things. Von Gosling is very instrumental in tirelessly helping this group to learn what it means to be a truly open source project. The code is already under ALv2 and is publicly available. As you will see it has a lot of dependency connections with the rest of Apache ecosystem and IMO will fit very well here and continue to grow the community. By the way, we still need 1 to 2 mentors, please let me know if you are interested. With best regards, The project's proposal is available at [1]. Thank you very much for the feedback you're willing to provide! Eason Chen [1] - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
