Re: [DISCUSS] EventMesh Proposal
Hi - PODLINGNAMESEARCH-189 for EventMesh has been approved. Regards, Dave > On Feb 2, 2021, at 1:33 AM, Eason Chen wrote: > > Hi, > > "*On one hand we don’t have a policy that say you must have to have done a > name search before becoming a piddling, on the other changing a name does > incur a large community cost and Infra would prefer that podlings don’t > change names. Most podlings do the name search just before graduation. In a > lot of cases it fairly obvious there is not going to be an issue, with a > generic name like this it may be best to wait until the name is approved > before calling the results of the vote.*" > Thanks for Justin's clarification, i also want to add a few words: > > I'm sorry, my words caused unnecessary confusion. I am still following up > on this issue[1]. I must admit that this name is a very serious problem. By > reading Apache’s regulations [2], I found that "*the original Podding > proposal established a working name for the new Podding. During the > election process, there are often discussions and filtering of suitable > names, but the proposed name is not final, just temporary*" > I am tring my best to ensure that it is resolved before the formal > incubation. > > [1]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-188? filter = > -4&jql = project%20%3D%20PODLINGNAMESEARCH%20order%20by%20created%20DESC > [2]: http://incubator.apache.org/guides/names.html > > > On Tue, Feb 2, 2021 at 5:14 PM Alexander Alten wrote: > >> Hi, >> >> Fully agree with Justin, we from Wayang had the same problem. We >> renamed the project before we submitted the proposal, and we >> documented everything. >> I’d encourage you to find a name which is TM ready in the US, India, >> CN and EU (if possible). You can’t graduate (or better it is unlikely) >> if a project name is not protectable by the ASF. And changing the >> whole INFRA after a podling is voted into the incubator is a huge >> effort. >> >> --alex >> >> On Tue, Feb 2, 2021 at 9:52 AM Justin Mclean >> wrote: >>> >>> Hi, >>> >>> On one hand we don’t have a policy that say you must have to have done a >> name search before becoming a piddling, on the other changing a name does >> incur a large community cost and Infra would prefer that podlings don’t >> change names. Most podlings do the name search just before graduation. In a >> lot of cases it fairly obvious there is not going to be an issue, with a >> generic name like this it may be best to wait until the name is approved >> before calling the results of the vote. >>> >>> Thanks, >>> Justin >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Hi, "*On one hand we don’t have a policy that say you must have to have done a name search before becoming a piddling, on the other changing a name does incur a large community cost and Infra would prefer that podlings don’t change names. Most podlings do the name search just before graduation. In a lot of cases it fairly obvious there is not going to be an issue, with a generic name like this it may be best to wait until the name is approved before calling the results of the vote.*" Thanks for Justin's clarification, i also want to add a few words: I'm sorry, my words caused unnecessary confusion. I am still following up on this issue[1]. I must admit that this name is a very serious problem. By reading Apache’s regulations [2], I found that "*the original Podding proposal established a working name for the new Podding. During the election process, there are often discussions and filtering of suitable names, but the proposed name is not final, just temporary*" I am tring my best to ensure that it is resolved before the formal incubation. [1]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-188? filter = -4&jql = project%20%3D%20PODLINGNAMESEARCH%20order%20by%20created%20DESC [2]: http://incubator.apache.org/guides/names.html On Tue, Feb 2, 2021 at 5:14 PM Alexander Alten wrote: > Hi, > > Fully agree with Justin, we from Wayang had the same problem. We > renamed the project before we submitted the proposal, and we > documented everything. > I’d encourage you to find a name which is TM ready in the US, India, > CN and EU (if possible). You can’t graduate (or better it is unlikely) > if a project name is not protectable by the ASF. And changing the > whole INFRA after a podling is voted into the incubator is a huge > effort. > > --alex > > On Tue, Feb 2, 2021 at 9:52 AM Justin Mclean > wrote: > > > > Hi, > > > > On one hand we don’t have a policy that say you must have to have done a > name search before becoming a piddling, on the other changing a name does > incur a large community cost and Infra would prefer that podlings don’t > change names. Most podlings do the name search just before graduation. In a > lot of cases it fairly obvious there is not going to be an issue, with a > generic name like this it may be best to wait until the name is approved > before calling the results of the vote. > > > > Thanks, > > Justin > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] EventMesh Proposal
Hi, Fully agree with Justin, we from Wayang had the same problem. We renamed the project before we submitted the proposal, and we documented everything. I’d encourage you to find a name which is TM ready in the US, India, CN and EU (if possible). You can’t graduate (or better it is unlikely) if a project name is not protectable by the ASF. And changing the whole INFRA after a podling is voted into the incubator is a huge effort. --alex On Tue, Feb 2, 2021 at 9:52 AM Justin Mclean wrote: > > Hi, > > On one hand we don’t have a policy that say you must have to have done a name > search before becoming a piddling, on the other changing a name does incur a > large community cost and Infra would prefer that podlings don’t change names. > Most podlings do the name search just before graduation. In a lot of cases it > fairly obvious there is not going to be an issue, with a generic name like > this it may be best to wait until the name is approved before calling the > results of the vote. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Hi, On one hand we don’t have a policy that say you must have to have done a name search before becoming a piddling, on the other changing a name does incur a large community cost and Infra would prefer that podlings don’t change names. Most podlings do the name search just before graduation. In a lot of cases it fairly obvious there is not going to be an issue, with a generic name like this it may be best to wait until the name is approved before calling the results of the vote. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Hi - A Name Search was started but not completed. I’m surprised that a vote was started while that was still active. Regards, Dave Sent from my iPhone > On Jan 31, 2021, at 7:19 PM, Eason Chen wrote: > > All problems and risks seem to be well clarified and resolved. Next, I will > initiate a vote, thank you for your attention and continued participation. > > Regards, > Eason > >> On Thu, Jan 28, 2021 at 1:00 PM Dave Fisher wrote: >> >> Exactly. Here’s a link - >> https://www.apache.org/foundation/marks/naming.html#namesearch >> >> It’s available from here - >> https://incubator.apache.org/guides/names.html#podling_suitable_name_search >> >> Regards, >> Dave >> >> Sent from my iPhone >> >>> On Jan 27, 2021, at 7:42 PM, Justin Mclean >> wrote: >>> >>> Hi, >>> >>> To help trademarks it would bee best if you provided them with some >> search results as described here. [1] Have a look at a couple of the other >> recent polling name search JIRAs to get a good idea of what is needed. >>> >>> Thanks, >>> Justin >>> >>> 1. http://incubator.apache.org/guides/names.html >>> - >>> 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] EventMesh Proposal
All problems and risks seem to be well clarified and resolved. Next, I will initiate a vote, thank you for your attention and continued participation. Regards, Eason On Thu, Jan 28, 2021 at 1:00 PM Dave Fisher wrote: > Exactly. Here’s a link - > https://www.apache.org/foundation/marks/naming.html#namesearch > > It’s available from here - > https://incubator.apache.org/guides/names.html#podling_suitable_name_search > > Regards, > Dave > > Sent from my iPhone > > > On Jan 27, 2021, at 7:42 PM, Justin Mclean > wrote: > > > > Hi, > > > > To help trademarks it would bee best if you provided them with some > search results as described here. [1] Have a look at a couple of the other > recent polling name search JIRAs to get a good idea of what is needed. > > > > Thanks, > > Justin > > > > 1. http://incubator.apache.org/guides/names.html > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > >
Re: [DISCUSS] EventMesh Proposal
Exactly. Here’s a link - https://www.apache.org/foundation/marks/naming.html#namesearch It’s available from here - https://incubator.apache.org/guides/names.html#podling_suitable_name_search Regards, Dave Sent from my iPhone > On Jan 27, 2021, at 7:42 PM, Justin Mclean wrote: > > Hi, > > To help trademarks it would bee best if you provided them with some search > results as described here. [1] Have a look at a couple of the other recent > polling name search JIRAs to get a good idea of what is needed. > > Thanks, > Justin > > 1. http://incubator.apache.org/guides/names.html > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [DISCUSS] EventMesh Proposal
Hi, To help trademarks it would bee best if you provided them with some search results as described here. [1] Have a look at a couple of the other recent polling name search JIRAs to get a good idea of what is needed. Thanks, Justin 1. http://incubator.apache.org/guides/names.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Thank you for your correction, a PODLINGNAMESEARCH issue has been created and followed up. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-188 On Thu, Jan 28, 2021 at 9:21 AM Dave Fisher wrote: > > > > On Jan 27, 2021, at 4:58 PM, vongosling wrote: > > > > Agree to raise this issue, even before podling starts. Initial teams > need > > to follow up on this potential problem[1]. Let's see how things go :-) > > > > [1] https://issues.apache.org/jira/browse/INFRA-21353 > > No! Naming is not an INFRA issue. Please see my other note. > > > > > Matt Sicker 于2021年1月28日周四 上午12:35写道: > > > >> It's typically a good idea to figure out your project name early on. > >> If you have to change the name before graduation in order to get a > >> trademark, then that wastes the momentum gathered under the old name. > >> That can always happen after the podling boots up, though. > >> > >>> On Wed, 27 Jan 2021 at 07:44, Sheng Wu > wrote: > >>> > >>> This is just a reminder, not an instruction. > >>> The naming search and approval will officially happen when you are > >> powerful > >>> enough to graduate. > >>> Personally, I would like to see this as a potential risk, not just > >>> regarding Solace. > >>> > >>> Of course, this is your option. you should know, if you can't get > >> approval > >>> in the future, you will have a much bigger branding hurt. > >>> (You don't need to convince me) > >>> > >>> Sheng Wu 吴晟 > >>> Twitter, wusheng1108 > >>> > >>> > >>> ShannonDing 于2021年1月27日周三 下午9:23写道: > >>> > > > 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&oq=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 > >>
Re: [DISCUSS] EventMesh Proposal
> On Jan 27, 2021, at 4:58 PM, vongosling wrote: > > Agree to raise this issue, even before podling starts. Initial teams need > to follow up on this potential problem[1]. Let's see how things go :-) > > [1] https://issues.apache.org/jira/browse/INFRA-21353 No! Naming is not an INFRA issue. Please see my other note. > > Matt Sicker 于2021年1月28日周四 上午12:35写道: > >> It's typically a good idea to figure out your project name early on. >> If you have to change the name before graduation in order to get a >> trademark, then that wastes the momentum gathered under the old name. >> That can always happen after the podling boots up, though. >> >>> On Wed, 27 Jan 2021 at 07:44, Sheng Wu wrote: >>> >>> This is just a reminder, not an instruction. >>> The naming search and approval will officially happen when you are >> powerful >>> enough to graduate. >>> Personally, I would like to see this as a potential risk, not just >>> regarding Solace. >>> >>> Of course, this is your option. you should know, if you can't get >> approval >>> in the future, you will have a much bigger branding hurt. >>> (You don't need to convince me) >>> >>> Sheng Wu 吴晟 >>> Twitter, wusheng1108 >>> >>> >>> ShannonDing 于2021年1月27日周三 下午9:23写道: >>> 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&oq=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
Re: [DISCUSS] EventMesh Proposal
Agree to raise this issue, even before podling starts. Initial teams need to follow up on this potential problem[1]. Let's see how things go :-) [1] https://issues.apache.org/jira/browse/INFRA-21353 Matt Sicker 于2021年1月28日周四 上午12:35写道: > It's typically a good idea to figure out your project name early on. > If you have to change the name before graduation in order to get a > trademark, then that wastes the momentum gathered under the old name. > That can always happen after the podling boots up, though. > > On Wed, 27 Jan 2021 at 07:44, Sheng Wu wrote: > > > > This is just a reminder, not an instruction. > > The naming search and approval will officially happen when you are > powerful > > enough to graduate. > > Personally, I would like to see this as a potential risk, not just > > regarding Solace. > > > > Of course, this is your option. you should know, if you can't get > approval > > in the future, you will have a much bigger branding hurt. > > (You don't need to convince me) > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > ShannonDing 于2021年1月27日周三 下午9:23写道: > > > > > > > > > > > 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&oq=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 thin
Re: [DISCUSS] EventMesh Proposal
If you want to do the name search before being accepted then please submit a JIRA here: https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/ You then provide the results of your search in the issue. The trademark committee / VP, Brand will review. This might take a few weeks. It is up to you whether you want to gate this proposal on name approval. Otherwise it’s as Sheng Wu wrote. Regards, Dave Sent from my iPhone > On Jan 27, 2021, at 5:44 AM, Sheng Wu wrote: > > This is just a reminder, not an instruction. > The naming search and approval will officially happen when you are powerful > enough to graduate. > Personally, I would like to see this as a potential risk, not just > regarding Solace. > > Of course, this is your option. you should know, if you can't get approval > in the future, you will have a much bigger branding hurt. > (You don't need to convince me) > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > ShannonDing 于2021年1月27日周三 下午9:23写道: > >> >> >> 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&oq=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 >
Re: [DISCUSS] EventMesh Proposal
It's typically a good idea to figure out your project name early on. If you have to change the name before graduation in order to get a trademark, then that wastes the momentum gathered under the old name. That can always happen after the podling boots up, though. On Wed, 27 Jan 2021 at 07:44, Sheng Wu wrote: > > This is just a reminder, not an instruction. > The naming search and approval will officially happen when you are powerful > enough to graduate. > Personally, I would like to see this as a potential risk, not just > regarding Solace. > > Of course, this is your option. you should know, if you can't get approval > in the future, you will have a much bigger branding hurt. > (You don't need to convince me) > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > ShannonDing 于2021年1月27日周三 下午9:23写道: > > > > > > > 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&oq=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 ava
Re: [DISCUSS] EventMesh Proposal
This is just a reminder, not an instruction. The naming search and approval will officially happen when you are powerful enough to graduate. Personally, I would like to see this as a potential risk, not just regarding Solace. Of course, this is your option. you should know, if you can't get approval in the future, you will have a much bigger branding hurt. (You don't need to convince me) Sheng Wu 吴晟 Twitter, wusheng1108 ShannonDing 于2021年1月27日周三 下午9:23写道: > > > 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&oq=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 > > > >
Re: [DISCUSS] EventMesh Proposal
Hi, I am honored that JB and François are willing to help the eventmesh project. I will soon initiate a discussion on evaluating Karaf 5 in the community. regards, Eason Chen On Wed, Jan 27, 2021 at 8:54 PM wrote: > +1 for me to be mentor on the project :) > > regards, > > François > fpa...@apache.org > > Le 27/01/2021 à 13:50, Jean-Baptiste Onofre a écrit : > > If you are open to evaluate/PoC EventMesh with Karaf (especially, Karaf > 5 would be a prefect candidate), you can count on me ! > > > > I would be more than happy to be mentor on EventMesh if you think it > would be helpful. > > > > Thanks ! > > Regards > > JB > > > >> Le 27 janv. 2021 à 13:47, Eason Chen a > écrit : > >> > >> Thanks to the attention of @JB and @François, > >> I have to admit that Karaf's lightweight operating environment, hot > >> deployment, dynamic configuration, and safe and rich management > functions > >> are indeed very helpful to help developers and users deploy applications > >> more flexibly. We will further investigate the feasibility of Karaf > >> becoming EventMesh's runtime container and look forward to the > integration > >> of the two products. By the way, I would like to know if @JB and > @François > >> are interested in becoming EventMesh mentors to help the project develop > >> better? > >> > >> On Wed, Jan 27, 2021 at 5:12 PM wrote: > >> > >>> 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 > >>> > >>> > > > > - > > 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 comm
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&oq=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
Re: [DISCUSS] EventMesh Proposal
@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&oq=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 > > > > >
Re: [DISCUSS] EventMesh Proposal
+1 for me to be mentor on the project :) regards, François fpa...@apache.org Le 27/01/2021 à 13:50, Jean-Baptiste Onofre a écrit : > If you are open to evaluate/PoC EventMesh with Karaf (especially, Karaf 5 > would be a prefect candidate), you can count on me ! > > I would be more than happy to be mentor on EventMesh if you think it would be > helpful. > > Thanks ! > Regards > JB > >> Le 27 janv. 2021 à 13:47, Eason Chen a écrit : >> >> Thanks to the attention of @JB and @François, >> I have to admit that Karaf's lightweight operating environment, hot >> deployment, dynamic configuration, and safe and rich management functions >> are indeed very helpful to help developers and users deploy applications >> more flexibly. We will further investigate the feasibility of Karaf >> becoming EventMesh's runtime container and look forward to the integration >> of the two products. By the way, I would like to know if @JB and @François >> are interested in becoming EventMesh mentors to help the project develop >> better? >> >> On Wed, Jan 27, 2021 at 5:12 PM wrote: >> >>> 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 >>> >>> > > - > 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] EventMesh Proposal
If you are open to evaluate/PoC EventMesh with Karaf (especially, Karaf 5 would be a prefect candidate), you can count on me ! I would be more than happy to be mentor on EventMesh if you think it would be helpful. Thanks ! Regards JB > Le 27 janv. 2021 à 13:47, Eason Chen a écrit : > > Thanks to the attention of @JB and @François, > I have to admit that Karaf's lightweight operating environment, hot > deployment, dynamic configuration, and safe and rich management functions > are indeed very helpful to help developers and users deploy applications > more flexibly. We will further investigate the feasibility of Karaf > becoming EventMesh's runtime container and look forward to the integration > of the two products. By the way, I would like to know if @JB and @François > are interested in becoming EventMesh mentors to help the project develop > better? > > On Wed, Jan 27, 2021 at 5:12 PM wrote: > >> 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 >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Thanks to the attention of @JB and @François, I have to admit that Karaf's lightweight operating environment, hot deployment, dynamic configuration, and safe and rich management functions are indeed very helpful to help developers and users deploy applications more flexibly. We will further investigate the feasibility of Karaf becoming EventMesh's runtime container and look forward to the integration of the two products. By the way, I would like to know if @JB and @François are interested in becoming EventMesh mentors to help the project develop better? On Wed, Jan 27, 2021 at 5:12 PM wrote: > 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 > >
Re: [DISCUSS] EventMesh Proposal
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&oq=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 > >
Re: [DISCUSS] EventMesh Proposal
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
Re: [DISCUSS] EventMesh Proposal
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] > > > -- Nothing is impossible
Re: [DISCUSS] EventMesh Proposal
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
Re: [DISCUSS] EventMesh Proposal
Hi, All code of the project will be donated to ASF. There were some inconsistencies when the project was just open source, but now it is developed based on the github version. Thanks, Eason -- Original -- From: "general"
Re: [DISCUSS] EventMesh Proposal
We need to build the community around the project once we open source the code. It's quite important for the health of the project. Even the project is accepted as a podling of incubator, you still need to keep building the community. >From the information we got through the Github project, I cannot get the conclusion that you are building the community here[1]. I don't know you plan of the internal version and the open source version, if there are two different version projects why are you so urge to contribute the project which is not in active development to Apache? I think Sheng Wu already expressed the same concern as I did. Please think about it carefully, and make process to address our concerns. [1]https://github.com/WeBankFinTech/EventMesh Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, Aug 15, 2020 at 9:09 AM Eason Chen wrote: > > Hi, > > > After the project was open sourced, we did not conduct evangelism, and the > internal version iterations were not synchronized in time. Many of these > issues and prs were raised by many of our partners, and many of them were not > reflected on github. Some document changes were also requested by them, It is > not very irregular at present, but we will run the standardized mechanism > later. > > > Thanks, > Eason > > > > > -- 原始邮件 -- > 发件人: > "general" > > 发送时间: 2020年8月14日(星期五) 晚上9:37 > 收件人: "Incubator General" > 主题: Re: [DISCUSS] EventMesh Proposal > > > > Hi, > > I just spent some time on the issues of EventMesh[1], it looks like > there are a bunch of people interested about this project, but > unfortunately the recent replied issue is about three weeks ago. > It's quite strange for me that the project maintainers are not keen to > answer the issues if they want to build the community from the > scratch. > > I also checked the commit logs, I can only find some small > documentation fixes which were done through the Github web interface. > I cannot find any new feature development commits after went through > the commits. > I'm not sure if WeBankFinTech guys do regular development on this repo. > > BTW, There is still an open issue asking if all the features are open > sourced[2]. > > [1]https://github.com/WeBankFinTech/EventMesh/issues > [2]https://github.com/WeBankFinTech/EventMesh/issues/5 > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
HI, > After the project was open sourced, we did not conduct evangelism, and the > internal version iterations were not synchronized in time. Does that mean a different version to what in that GitHub will be donated to ASF? That may complicate things a little as we would need to know who the contributors were. Thanks, Justin
Re: [DISCUSS] EventMesh Proposal
Willem Jiang 于2020年8月14日周五 下午9:38写道: > Hi, > > I just spent some time on the issues of EventMesh[1], it looks like > there are a bunch of people interested about this project, but > unfortunately the recent replied issue is about three weeks ago. > It's quite strange for me that the project maintainers are not keen to > answer the issues if they want to build the community from the > scratch. > Hi Willem Thanks for taking a look at this too. That is why I am concerned from day one I saw this proposal. Joining the ASF incubator is about learning how to build the community and make it better, rather than all things that should happen after the movement like this is a condition for the project to begin to run? Even issues opened for months, the proposal has been sent out for 10 days, and I had pointed out the concerns for 7 days. Still, no one cares about GitHub issues. Is that normal for a community? Why don't the initial PPMC members care about the project in these so many days? I love the ASF's Community Over Codes, so my all interests are focusing on the people who maintain the projects. My concerns are still there. Sheng Wu 吴晟 Twitter, wusheng1108 > > I also checked the commit logs, I can only find some small > documentation fixes which were done through the Github web interface. > I cannot find any new feature development commits after went through > the commits. > I'm not sure if WeBankFinTech guys do regular development on this repo. > > BTW, There is still an open issue asking if all the features are open > sourced[2]. > > [1]https://github.com/WeBankFinTech/EventMesh/issues > [2]https://github.com/WeBankFinTech/EventMesh/issues/5 > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Aug 14, 2020 at 7:42 PM Eason Chen wrote: > > > > Thanks Justin, and can not agree more. > > > > > > Thanks everyone for your attention to this project and your valuable > comments. > > > > > > If everyone has no problems, i will initiate the voting processs later. > > > > > > Thanks, > > Eason > > > > > > -- 原始邮件 -- > > 发件人: > "general" > < > jus...@classsoftware.com>; > > 发送时间: 2020年8月14日(星期五) 下午4:57 > > 收件人: "general" > > > 主题: Re: [DISCUSS] EventMesh Proposal > > > > > > > > Hi, > > > > The incubator prefers that a project comes with a community around it > but it’s not essential. Not having one may possibly make graduation harder, > as long as the project is aware of that I don’t see any issues. > > > > Thanks, > > Justin > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] EventMesh Proposal
Hi, I just spent some time on the issues of EventMesh[1], it looks like there are a bunch of people interested about this project, but unfortunately the recent replied issue is about three weeks ago. It's quite strange for me that the project maintainers are not keen to answer the issues if they want to build the community from the scratch. I also checked the commit logs, I can only find some small documentation fixes which were done through the Github web interface. I cannot find any new feature development commits after went through the commits. I'm not sure if WeBankFinTech guys do regular development on this repo. BTW, There is still an open issue asking if all the features are open sourced[2]. [1]https://github.com/WeBankFinTech/EventMesh/issues [2]https://github.com/WeBankFinTech/EventMesh/issues/5 Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Aug 14, 2020 at 7:42 PM Eason Chen wrote: > > Thanks Justin, and can not agree more. > > > Thanks everyone for your attention to this project and your valuable comments. > > > If everyone has no problems, i will initiate the voting processs later. > > > Thanks, > Eason > > > -- 原始邮件 -- > 发件人: > "general" > > 发送时间: 2020年8月14日(星期五) 下午4:57 > 收件人: "general" > 主题: Re: [DISCUSS] EventMesh Proposal > > > > Hi, > > The incubator prefers that a project comes with a community around it but > it’s not essential. Not having one may possibly make graduation harder, as > long as the project is aware of that I don’t see any issues. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
I will leave that up to your mentors. I think my feeling is already very clear for you. Sheng Wu 吴晟 Twitter, wusheng1108 Eason Chen 于2020年8月14日周五 下午7:55写道: > Thanks for your continued attention. > As i mentened before in my first discuss "And I'd like to emphasize that > the community however small it might look so far", if there are > seemingly inaccurate descriptions in the proposal, I can modify it as > needed. > > > > > -- 原始邮件 -- > 发件人: > "general" > < > wu.sheng.841...@gmail.com>; > 发送时间: 2020年8月14日(星期五) 下午4:46 > 收件人: "Incubator" > 主题: Re: [DISCUSS] EventMesh Proposal > > > > Eason Chen > > Hi, > > Maybe a bit misunderstood, what I am trying to explain is that even > if the > > project is really in its infancy, it does not prevent the building > under > > apache way. In fact, many apache projects are built from 0. And > mentors > > also don't think this is a big problem. > > > > I don't think this is a problem either. > That is why I keep saying, the only thing I want, is to adjust the proposal > to state the fact. Currently, the proposal looks like, you have an active > community already. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > > > > > > Thanks, > > Eason > > > > > > -- 原始邮件 -- > > 发件人: > > > "general" > > > < > > wu.sheng.841...@gmail.com>; > > 发送时间: 2020年8月14日(星期五) 下午4:02 > > 收件人: "Incubator" > > > 主题: Re: [DISCUSS] EventMesh Proposal > > > > > > > > Why are you arguing this with me? > > > > I am not saying anything about the future, or nothing about whether > this > > project is good or not. > > > > The risk and challenges are only things that could happen based on the > > current status, community-level only. > > And it is higher than some projects had a larger or more active > community. > > That is a factor, isn't it? > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Eason Chen > > > > &gt;1. Just open-sourced > > > &gt;3. Community development would be a challenge > > > > > > > > > As mentioned earlier, the project is still in its infancy. I > also > > asked > > > the mentors how to build the community. I believe that with > the help > > of > > > apache way and the mentors, we have reasons and confidence > to make > > products > > > more diversified and build a healthy internationalization > community. > > > > > > > > > &gt;2. Have a risk of being an orphaned project > > > > > > > > > > > > Event is a huge ecosystem, and especially eventmesh will be > a very > > > promising direction,currently such products are scarce, but > the > > demand will > > > be greater > > > > > > > > > > > > > > > -- 原始邮件 -- > > > 发件人: > > > > > > "general" > > > > &a
Re: [DISCUSS] EventMesh Proposal
Hi, The incubator prefers that a project comes with a community around it but it’s not essential. Not having one may possibly make graduation harder, as long as the project is aware of that I don’t see any issues. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Eason Chen 于2020年8月14日周五 下午4:25写道: > Hi, > Maybe a bit misunderstood, what I am trying to explain is that even if the > project is really in its infancy, it does not prevent the building under > apache way. In fact, many apache projects are built from 0. And mentors > also don't think this is a big problem. > I don't think this is a problem either. That is why I keep saying, the only thing I want, is to adjust the proposal to state the fact. Currently, the proposal looks like, you have an active community already. Sheng Wu 吴晟 Twitter, wusheng1108 > > > Thanks, > Eason > > > -- 原始邮件 -- > 发件人: > "general" > < > wu.sheng.841...@gmail.com>; > 发送时间: 2020年8月14日(星期五) 下午4:02 > 收件人: "Incubator" > 主题: Re: [DISCUSS] EventMesh Proposal > > > > Why are you arguing this with me? > > I am not saying anything about the future, or nothing about whether this > project is good or not. > > The risk and challenges are only things that could happen based on the > current status, community-level only. > And it is higher than some projects had a larger or more active community. > That is a factor, isn't it? > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Eason Chen > > >1. Just open-sourced > > >3. Community development would be a challenge > > > > > > As mentioned earlier, the project is still in its infancy. I also > asked > > the mentors how to build the community. I believe that with the help > of > > apache way and the mentors, we have reasons and confidence to make > products > > more diversified and build a healthy internationalization community. > > > > > > >2. Have a risk of being an orphaned project > > > > > > > > Event is a huge ecosystem, and especially eventmesh will be a very > > promising direction,currently such products are scarce, but the > demand will > > be greater > > > > > > > > > > ---------- 原始邮件 -- > > 发件人: > > > "general" > > > < > > wu.sheng.841...@gmail.com>; > > 发送时间: 2020年8月14日(星期五) 下午3:01 > > 收件人: "Incubator" > > > 主题: Re: [DISCUSS] EventMesh Proposal > > > > > > > > Eason Chen > > > > Our product has actually received a lot of attention from > people. We > > have > > > conducted communication with many people and collected their > > opinions. We > > > plan to abstract eventmesh more independently, make product > > positioning > > > clearer, and make it easier for everyone to participate. We > will > > invest > > > more time and energy to build the community. > > > > > > > I think you misunderstand Ming's and my points, > > We are not saying you have to have a large community, for now, we are > > asking you to make sure, your statement/proposal is matching your > current > > status. > > > > Do you mean, the project community is more active than I found? > > If so, I would like to ask for more materials(including open > discussion, > > news, blogs, issue, pull requests) to prove your points, EN and CN > are both > > fine for me. > > > > I hope the status could be clear before any formal vote. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > > > > > --&nbsp;原始邮件&nbsp;-- > > > 发件人: > > > > > > "general" > > > > &a
Re: [DISCUSS] EventMesh Proposal
Why are you arguing this with me? I am not saying anything about the future, or nothing about whether this project is good or not. The risk and challenges are only things that could happen based on the current status, community-level only. And it is higher than some projects had a larger or more active community. That is a factor, isn't it? Sheng Wu 吴晟 Twitter, wusheng1108 Eason Chen 于2020年8月14日周五 下午3:51写道: > >1. Just open-sourced > >3. Community development would be a challenge > > > As mentioned earlier, the project is still in its infancy. I also asked > the mentors how to build the community. I believe that with the help of > apache way and the mentors, we have reasons and confidence to make products > more diversified and build a healthy internationalization community. > > > >2. Have a risk of being an orphaned project > > > > Event is a huge ecosystem, and especially eventmesh will be a very > promising direction,currently such products are scarce, but the demand will > be greater > > > > > -- 原始邮件 -- > 发件人: > "general" > < > wu.sheng.841...@gmail.com>; > 发送时间: 2020年8月14日(星期五) 下午3:01 > 收件人: "Incubator" > 主题: Re: [DISCUSS] EventMesh Proposal > > > > Eason Chen > > Our product has actually received a lot of attention from people. We > have > > conducted communication with many people and collected their > opinions. We > > plan to abstract eventmesh more independently, make product > positioning > > clearer, and make it easier for everyone to participate. We will > invest > > more time and energy to build the community. > > > > I think you misunderstand Ming's and my points, > We are not saying you have to have a large community, for now, we are > asking you to make sure, your statement/proposal is matching your current > status. > > Do you mean, the project community is more active than I found? > If so, I would like to ask for more materials(including open discussion, > news, blogs, issue, pull requests) to prove your points, EN and CN are both > fine for me. > > I hope the status could be clear before any formal vote. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > > > > > > > > > > -- 原始邮件 -- > > 发件人: > > > "general" > > > < > > wenm...@apache.org>; > > 发送时间: 2020年8月14日(星期五) 中午11:35 > > 收件人: "general" > 抄送: "legal-discuss" > 主题: Re: [DISCUSS] EventMesh Proposal > > > > > > > > > Thanks for the honesty, I prefer you should adjust the > proposal to > > match > > > the reality. Such as > > > 1. Just open-sourced > > > 2. Have a risk of being an orphaned project > > > 3. Community development would be a challenge > > > > As mentioned in wusheng’s previous email, the challenge should be > stated in > > the proposal. > > > > Thanks, > > Ming Wen, Apache APISIX & Apache SkyWalking > > Twitter: _WenMing > > > > > > Eason Chen > > > > Thanks for your help and answers @Duane, i will initiate the > voting > > > processs later if you have no other questions. > > > > > > > > > > > > > > > > --&nbsp;原始邮件&nbsp;-- > > > 发件人: > > > > > > "general" > > > > &
Re: [DISCUSS] EventMesh Proposal
Thanks for @Duane's reply. Duane Pauls 于2020年8月11日周二 上午12:25写道: > 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, but it is an industry term > that has been adopted by Gartner and is gaining traction in the industry. > Solace does not oppose the term being used in other applicable products or > projects. > > +1 (non-binding) on the idea. > > Cheers, > Duane > > On Thu, Aug 6, 2020 at 11:51 AM heng du wrote: > > > Hi @Michael > > > > Thanks for your advice. As far as I know, Solace doesn't have a product > > called Eventmesh, They're just using that name to promote their PubSub > > platform. > > > > But in order not to cause trouble in the future, I also ask guys of > Apache > > Brand to help check whether this name is appropriate. For us, we've been > > using the name EventMesh for a long time, and we want to keep it so that > > users can get better product positioning from the name. > > > > And base on this document[1], we searched in the U.S. Patent Office[2] > and > > found nothing inappropriate. > > > > [1] https://incubator.apache.org/guides/names.html > > [2] https://www.uspto.gov/trademark > > > > Thanks > > Henry > > > > Michael André Pearce 于2020年8月6日周四 > > 下午3:33写道: > > > >> Hi > >> > >> Im PMC member from ActiveMQ project. > >> I like the idea, nice. +1 on it as a project idea. > >> > >> I am though a little -1 on the name of the project, I would recommend > >> that an alternative name for the project is found as there maybe a > conflict > >> in rights ability to copyright and trademark to it. > >> > >> I’m aware there is a commercial vendor messaging company called Solace, > >> where they use and market their product with heavy use of the name Event > >> Mesh, you can see this just googling event mesh, brings back many hits > to > >> their products, marketing material and other records, so they may hold a > >> heavy claim to this name. > >> > >> Best > >> Michael > >> > >> > On 4 Aug 2020, at 18:33, Kevin Ratnasekera > >> wrote: > >> > > >> > Hi Easen, > >> > > >> > +1, Having worked in a similar domain so far, I have to say this is an > >> > interesting project. If you are seeking new mentors, please consider > >> adding > >> > me as a mentor to the project. > >> > > >> > Regards > >> > Kevin > >> > > >> > On Tue, Aug 4, 2020 at 3:34 PM Eason Chen wrote: > >> > > >> >> 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 3 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. Heng Du (from RocketMQ PMC) 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. > >> >> > >> >> > >> >> The project's proposal is available at [1]. > >> >> > >> >> > >> >> Thank you very much for the feedback you're willing to provide! > >> >> > >> >> > >> >> With best regards, > >> >> > >> >> Eason Chen > >> >> > >> >> > >> >> > >> >> [1] > >> >> > >> https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal > >> > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> >
Re: [DISCUSS] EventMesh Proposal
Eason Chen 于2020年8月14日周五 下午2:43写道: > Our product has actually received a lot of attention from people. We have > conducted communication with many people and collected their opinions. We > plan to abstract eventmesh more independently, make product positioning > clearer, and make it easier for everyone to participate. We will invest > more time and energy to build the community. > I think you misunderstand Ming's and my points, We are not saying you have to have a large community, for now, we are asking you to make sure, your statement/proposal is matching your current status. Do you mean, the project community is more active than I found? If so, I would like to ask for more materials(including open discussion, news, blogs, issue, pull requests) to prove your points, EN and CN are both fine for me. I hope the status could be clear before any formal vote. Sheng Wu 吴晟 Twitter, wusheng1108 > > > > > -- 原始邮件 -- > 发件人: > "general" > < > wenm...@apache.org>; > 发送时间: 2020年8月14日(星期五) 中午11:35 > 收件人: "general" 抄送: "legal-discuss" 主题: Re: [DISCUSS] EventMesh Proposal > > > > > Thanks for the honesty, I prefer you should adjust the proposal to > match > > the reality. Such as > > 1. Just open-sourced > > 2. Have a risk of being an orphaned project > > 3. Community development would be a challenge > > As mentioned in wusheng’s previous email, the challenge should be stated in > the proposal. > > Thanks, > Ming Wen, Apache APISIX & Apache SkyWalking > Twitter: _WenMing > > > Eason Chen > > Thanks for your help and answers @Duane, i will initiate the voting > > processs later if you have no other questions. > > > > > > > > > > -- 原始邮件 -- > > 发件人: > > > "general" > > > < > > duane.pa...@gmail.com>; > > 发送时间: 2020年8月11日(星期二) 凌晨0:16 > > 收件人: "legal-discuss" > 抄送: "general" > 主题: Re: [DISCUSS] EventMesh Proposal > > > > > > > > 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, but it is an > industry term > > that has been adopted by Gartner and is gaining traction in the > industry. > > Solace does not oppose the term being used in other applicable > products or > > projects. > > > > +1 (non-binding) on the idea. > > > > Cheers, > > Duane > > > > On Thu, Aug 6, 2020 at 11:51 AM heng du > > > wrote: > > > > > Hi @Michael > > > > > > Thanks for your advice. As far as I know, Solace doesn't > have a > > product > > > called Eventmesh, They're just using that name to promote > their PubSub > > > platform. > > > > > > But in order not to cause trouble in the future, I also ask > guys of > > Apache > > > Brand to help check whether this name is appropriate. For > us, we've > > been > > > using the name EventMesh for a long time, and we want to > keep it so > > that > > > users can get better product positioning from the name. > > > > > > And base on this document[1], we searched in the U.S. Patent > > Office[2] and > > > found nothing inappropriate. > > > > > > [1] https://incubator.apache.org/guides/names.html > > > [2] https://www.uspto.gov/trademark > > > > > > Thanks > > > Henry > > > > > > Michael André Pearce .invalid> > > 于2020年8月6日周四 > > > 下午3:33写道: > > > > > >> Hi > > >> > > >> Im PMC member from ActiveMQ project. > > >> I like the idea, nice. +1 on it as a project idea. > > >> > > >> I am though a little -1 on the name of the project, > I would > > recommend > > >> that an alternative name for the project is found as > there maybe > > a conflict > > >> in rights ability to copyright and trademark to it. > > >> > > &g
Re: [DISCUSS] EventMesh Proposal
> Thanks for the honesty, I prefer you should adjust the proposal to match > the reality. Such as > 1. Just open-sourced > 2. Have a risk of being an orphaned project > 3. Community development would be a challenge As mentioned in wusheng’s previous email, the challenge should be stated in the proposal. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Eason Chen 于2020年8月14日周五 上午10:52写道: > Thanks for your help and answers @Duane, i will initiate the voting > processs later if you have no other questions. > > > > > -- 原始邮件 -- > 发件人: > "general" > < > duane.pa...@gmail.com>; > 发送时间: 2020年8月11日(星期二) 凌晨0:16 > 收件人: "legal-discuss" 抄送: "general" 主题: Re: [DISCUSS] EventMesh Proposal > > > > 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, but it is an industry term > that has been adopted by Gartner and is gaining traction in the industry. > Solace does not oppose the term being used in other applicable products or > projects. > > +1 (non-binding) on the idea. > > Cheers, > Duane > > On Thu, Aug 6, 2020 at 11:51 AM heng du wrote: > > > Hi @Michael > > > > Thanks for your advice. As far as I know, Solace doesn't have a > product > > called Eventmesh, They're just using that name to promote their PubSub > > platform. > > > > But in order not to cause trouble in the future, I also ask guys of > Apache > > Brand to help check whether this name is appropriate. For us, we've > been > > using the name EventMesh for a long time, and we want to keep it so > that > > users can get better product positioning from the name. > > > > And base on this document[1], we searched in the U.S. Patent > Office[2] and > > found nothing inappropriate. > > > > [1] https://incubator.apache.org/guides/names.html > > [2] https://www.uspto.gov/trademark > > > > Thanks > > Henry > > > > Michael André Pearce 于2020年8月6日周四 > > 下午3:33写道: > > > >> Hi > >> > >> Im PMC member from ActiveMQ project. > >> I like the idea, nice. +1 on it as a project idea. > >> > >> I am though a little -1 on the name of the project, I would > recommend > >> that an alternative name for the project is found as there maybe > a conflict > >> in rights ability to copyright and trademark to it. > >> > >> I’m aware there is a commercial vendor messaging company called > Solace, > >> where they use and market their product with heavy use of the > name Event > >> Mesh, you can see this just googling event mesh, brings back many > hits to > >> their products, marketing material and other records, so they may > hold a > >> heavy claim to this name. > >> > >> Best > >> Michael > >> > >> > On 4 Aug 2020, at 18:33, Kevin Ratnasekera < > djkevincr1...@gmail.com> > >> wrote: > >> > > >> > Hi Easen, > >> > > >> > +1, Having worked in a similar domain so far, I have to say > this is an > >> > interesting project. If you are seeking new mentors, please > consider > >> adding > >> > me as a mentor to the project. > >> > > >> > Regards > >> > Kevin > >> > > >> > On Tue, Aug 4, 2020 at 3:34 PM Eason Chen < > daerduoc...@qq.com> wrote: > >> > > >> >> 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 3 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
Re: [DISCUSS] EventMesh Proposal
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, but it is an industry term that has been adopted by Gartner and is gaining traction in the industry. Solace does not oppose the term being used in other applicable products or projects. +1 (non-binding) on the idea. Cheers, Duane On Thu, Aug 6, 2020 at 11:51 AM heng du wrote: > Hi @Michael > > Thanks for your advice. As far as I know, Solace doesn't have a product > called Eventmesh, They're just using that name to promote their PubSub > platform. > > But in order not to cause trouble in the future, I also ask guys of Apache > Brand to help check whether this name is appropriate. For us, we've been > using the name EventMesh for a long time, and we want to keep it so that > users can get better product positioning from the name. > > And base on this document[1], we searched in the U.S. Patent Office[2] and > found nothing inappropriate. > > [1] https://incubator.apache.org/guides/names.html > [2] https://www.uspto.gov/trademark > > Thanks > Henry > > Michael André Pearce 于2020年8月6日周四 > 下午3:33写道: > >> Hi >> >> Im PMC member from ActiveMQ project. >> I like the idea, nice. +1 on it as a project idea. >> >> I am though a little -1 on the name of the project, I would recommend >> that an alternative name for the project is found as there maybe a conflict >> in rights ability to copyright and trademark to it. >> >> I’m aware there is a commercial vendor messaging company called Solace, >> where they use and market their product with heavy use of the name Event >> Mesh, you can see this just googling event mesh, brings back many hits to >> their products, marketing material and other records, so they may hold a >> heavy claim to this name. >> >> Best >> Michael >> >> > On 4 Aug 2020, at 18:33, Kevin Ratnasekera >> wrote: >> > >> > Hi Easen, >> > >> > +1, Having worked in a similar domain so far, I have to say this is an >> > interesting project. If you are seeking new mentors, please consider >> adding >> > me as a mentor to the project. >> > >> > Regards >> > Kevin >> > >> > On Tue, Aug 4, 2020 at 3:34 PM Eason Chen wrote: >> > >> >> 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 3 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. Heng Du (from RocketMQ PMC) 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. >> >> >> >> >> >> The project's proposal is available at [1]. >> >> >> >> >> >> Thank you very much for the feedback you're willing to provide! >> >> >> >> >> >> With best regards, >> >> >> >> Eason Chen >> >> >> >> >> >> >> >> [1] >> >> >> https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
Re: [DISCUSS] EventMesh Proposal
What are the similarities and differences from Camel? (I'm not making an argument in any way..just trying to understand it) On Thu, Aug 6, 2020 at 11:51 AM Clebert Suconic wrote: > > If you make it generic enough that runs on other messaging solutions > (Kafka, Artemis, ActiveMQ, RocketMQ), you have less risk of being > orphaned. > > however if it's tight coupled with RocketMQ mentioned.. it becomes > more like a sub project of your broker than a separate project. > > What are the plans? > > On Thu, Aug 6, 2020 at 8:58 AM Sheng Wu wrote: > > > > Eason Chen 于2020年8月6日周四 下午6:17写道: > > > > > Hi, > > > > > > > > > We do not deny that the community is not really big and active, we share > > > our best practices and look forward to getting more people's attention and > > > help, at the same time can help our colleagues .we believe that as > > > long as we find the right method and organization such as the apache way, > > > the community will become stronger and stronger. > > > > > > > Hi > > > > Thanks for the honesty, I prefer you should adjust the proposal to match > > the reality. Such as > > 1. Just open-sourced > > 2. Have a risk of being an orphaned project > > 3. Community development would be a challenge > > > > I hope you could understand, a project open-sourced from the company, and > > not widely adopted, these are just the fact, don't need to hide them. > > The incubator is welcome this kind of project, once you have enough active > > mentors and initial committers. > > > > - > > Personally only, not from an IPMC member perspective > > - > > The concerns I raised, are from the perspective of protecting the project, > > a very young community will face heavy loads of joining the ASF incubator > > directly. > > And from my personal experiences, people(especially in China) will > > challenge the qualification of the project. I have seen this happened > > before. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > > > > > > > > In addition, I want to clarify that these codes are submitted by the > > > entire team within our company, but I open sourced them, as you see some > > > components are not yet open source, we are reviewing and reforming > > > internally, and will open source soon. > > > > > > > > > > > > > > > -- 原始邮件 -- > > > 发件人: > > > "general" > > > < > > > wu.sheng.841...@gmail.com>; > > > 发送时间: 2020年8月6日(星期四) 下午5:42 > > > 收件人: "Incubator" > > > > > 主题: Re: [DISCUSS] EventMesh Proposal > > > > > > > > > > > > Hi > > > > > > Noticed this a little late. > > > > > > I have some questions about the status of the project, especially about > > > the > > > `Orphaned Products` and the activity of the community. > > > > > > With a project open-sourced since September 2019, this doesn't seem like > > > the status you said in the proposal. > > > 1. If the EventMesh repo is the only code repo, AFAIK, there is only one > > > contributor who has submitted the codes over 110 lines, most are just < 50 > > > lines. https://github.com/WeBankFinTech/EventMesh/graphs/contributors > > > 2. Only have 35 issues opened on the GitHub. > > > https://github.com/WeBankFinTech/EventMesh/issues > > > 3. The issues(since issue #21) since 21 days ago have no comment any all. > > > > > > From my understanding, this project is only limited maintained by one and > > > only one for now. > > > > > > To the project community, could you respond what is the real status now? > > > And why there is a gap between your proposal and GitHub open statistics? > > > > > > Personally, I have concerns about the activity and support of the > > > community, or a little more, whether the basic community has been > > > established. > > > I think the incubator should notice the status, in case, it will be hard > > > to > > > make consensus and release soon in the incubating stage. > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > > > > Ming Wen > > > > > > Hi, Eason, > > > > It
Re: [DISCUSS] EventMesh Proposal
Hi @Michael Thanks for your advice. As far as I know, Solace doesn't have a product called Eventmesh, They're just using that name to promote their PubSub platform. But in order not to cause trouble in the future, I also ask guys of Apache Brand to help check whether this name is appropriate. For us, we've been using the name EventMesh for a long time, and we want to keep it so that users can get better product positioning from the name. And base on this document[1], we searched in the U.S. Patent Office[2] and found nothing inappropriate. [1] https://incubator.apache.org/guides/names.html [2] https://www.uspto.gov/trademark Thanks Henry Michael André Pearce 于2020年8月6日周四 下午3:33写道: > Hi > > Im PMC member from ActiveMQ project. > I like the idea, nice. +1 on it as a project idea. > > I am though a little -1 on the name of the project, I would recommend that > an alternative name for the project is found as there maybe a conflict in > rights ability to copyright and trademark to it. > > I’m aware there is a commercial vendor messaging company called Solace, > where they use and market their product with heavy use of the name Event > Mesh, you can see this just googling event mesh, brings back many hits to > their products, marketing material and other records, so they may hold a > heavy claim to this name. > > Best > Michael > > > On 4 Aug 2020, at 18:33, Kevin Ratnasekera > wrote: > > > > Hi Easen, > > > > +1, Having worked in a similar domain so far, I have to say this is an > > interesting project. If you are seeking new mentors, please consider > adding > > me as a mentor to the project. > > > > Regards > > Kevin > > > > On Tue, Aug 4, 2020 at 3:34 PM Eason Chen wrote: > > > >> 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 3 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. Heng Du (from RocketMQ PMC) 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. > >> > >> > >> The project's proposal is available at [1]. > >> > >> > >> Thank you very much for the feedback you're willing to provide! > >> > >> > >> With best regards, > >> > >> Eason Chen > >> > >> > >> > >> [1] > >> https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] EventMesh Proposal
If you make it generic enough that runs on other messaging solutions (Kafka, Artemis, ActiveMQ, RocketMQ), you have less risk of being orphaned. however if it's tight coupled with RocketMQ mentioned.. it becomes more like a sub project of your broker than a separate project. What are the plans? On Thu, Aug 6, 2020 at 8:58 AM Sheng Wu wrote: > > Eason Chen 于2020年8月6日周四 下午6:17写道: > > > Hi, > > > > > > We do not deny that the community is not really big and active, we share > > our best practices and look forward to getting more people's attention and > > help, at the same time can help our colleagues .we believe that as > > long as we find the right method and organization such as the apache way, > > the community will become stronger and stronger. > > > > Hi > > Thanks for the honesty, I prefer you should adjust the proposal to match > the reality. Such as > 1. Just open-sourced > 2. Have a risk of being an orphaned project > 3. Community development would be a challenge > > I hope you could understand, a project open-sourced from the company, and > not widely adopted, these are just the fact, don't need to hide them. > The incubator is welcome this kind of project, once you have enough active > mentors and initial committers. > > - > Personally only, not from an IPMC member perspective > - > The concerns I raised, are from the perspective of protecting the project, > a very young community will face heavy loads of joining the ASF incubator > directly. > And from my personal experiences, people(especially in China) will > challenge the qualification of the project. I have seen this happened > before. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > > > > > > In addition, I want to clarify that these codes are submitted by the > > entire team within our company, but I open sourced them, as you see some > > components are not yet open source, we are reviewing and reforming > > internally, and will open source soon. > > > > > > > > > > -- 原始邮件 -- > > 发件人: > > "general" > > < > > wu.sheng.841...@gmail.com>; > > 发送时间: 2020年8月6日(星期四) 下午5:42 > > 收件人: "Incubator" > > > 主题: Re: [DISCUSS] EventMesh Proposal > > > > > > > > Hi > > > > Noticed this a little late. > > > > I have some questions about the status of the project, especially about the > > `Orphaned Products` and the activity of the community. > > > > With a project open-sourced since September 2019, this doesn't seem like > > the status you said in the proposal. > > 1. If the EventMesh repo is the only code repo, AFAIK, there is only one > > contributor who has submitted the codes over 110 lines, most are just < 50 > > lines. https://github.com/WeBankFinTech/EventMesh/graphs/contributors > > 2. Only have 35 issues opened on the GitHub. > > https://github.com/WeBankFinTech/EventMesh/issues > > 3. The issues(since issue #21) since 21 days ago have no comment any all. > > > > From my understanding, this project is only limited maintained by one and > > only one for now. > > > > To the project community, could you respond what is the real status now? > > And why there is a gap between your proposal and GitHub open statistics? > > > > Personally, I have concerns about the activity and support of the > > community, or a little more, whether the basic community has been > > established. > > I think the incubator should notice the status, in case, it will be hard to > > make consensus and release soon in the incubating stage. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Ming Wen > > > > Hi, Eason, > > > It's an interesting project. And I have a few questions and > > > it would be great if you could help: > > > 1. According to github's statistics[1], most of the code was > > contributed by > > > yourself. > > > So if you're on vacation, this project will not easy to move forward. > > > 2. An external dependency `logback` is LGPL license, which is > > Category X. > > > Can this dependency be removed? > > > > > > [1] https://github.com/WeBankFinTech/EventMesh/graphs/contributors > > > <https://github.com/WeBankFinTech/EventMesh/graphs/contributors>>; > > > Thanks, > > > Ming Wen, Apache APISIX & Apache SkyWalking > &
Re: [DISCUSS] EventMesh Proposal
Eason Chen 于2020年8月6日周四 下午6:17写道: > Hi, > > > We do not deny that the community is not really big and active, we share > our best practices and look forward to getting more people's attention and > help, at the same time can help our colleagues .we believe that as > long as we find the right method and organization such as the apache way, > the community will become stronger and stronger. > Hi Thanks for the honesty, I prefer you should adjust the proposal to match the reality. Such as 1. Just open-sourced 2. Have a risk of being an orphaned project 3. Community development would be a challenge I hope you could understand, a project open-sourced from the company, and not widely adopted, these are just the fact, don't need to hide them. The incubator is welcome this kind of project, once you have enough active mentors and initial committers. - Personally only, not from an IPMC member perspective - The concerns I raised, are from the perspective of protecting the project, a very young community will face heavy loads of joining the ASF incubator directly. And from my personal experiences, people(especially in China) will challenge the qualification of the project. I have seen this happened before. Sheng Wu 吴晟 Twitter, wusheng1108 > > > In addition, I want to clarify that these codes are submitted by the > entire team within our company, but I open sourced them, as you see some > components are not yet open source, we are reviewing and reforming > internally, and will open source soon. > > > > > -- 原始邮件 -- > 发件人: > "general" > < > wu.sheng.841...@gmail.com>; > 发送时间: 2020年8月6日(星期四) 下午5:42 > 收件人: "Incubator" > 主题: Re: [DISCUSS] EventMesh Proposal > > > > Hi > > Noticed this a little late. > > I have some questions about the status of the project, especially about the > `Orphaned Products` and the activity of the community. > > With a project open-sourced since September 2019, this doesn't seem like > the status you said in the proposal. > 1. If the EventMesh repo is the only code repo, AFAIK, there is only one > contributor who has submitted the codes over 110 lines, most are just < 50 > lines. https://github.com/WeBankFinTech/EventMesh/graphs/contributors > 2. Only have 35 issues opened on the GitHub. > https://github.com/WeBankFinTech/EventMesh/issues > 3. The issues(since issue #21) since 21 days ago have no comment any all. > > From my understanding, this project is only limited maintained by one and > only one for now. > > To the project community, could you respond what is the real status now? > And why there is a gap between your proposal and GitHub open statistics? > > Personally, I have concerns about the activity and support of the > community, or a little more, whether the basic community has been > established. > I think the incubator should notice the status, in case, it will be hard to > make consensus and release soon in the incubating stage. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Ming Wen > > Hi, Eason, > > It's an interesting project. And I have a few questions and > > it would be great if you could help: > > 1. According to github's statistics[1], most of the code was > contributed by > > yourself. > > So if you're on vacation, this project will not easy to move forward. > > 2. An external dependency `logback` is LGPL license, which is > Category X. > > Can this dependency be removed? > > > > [1] https://github.com/WeBankFinTech/EventMesh/graphs/contributors > > <https://github.com/WeBankFinTech/EventMesh/graphs/contributors>>; > > Thanks, > > Ming Wen, Apache APISIX & Apache SkyWalking > > Twitter: _WenMing > > > > > > Eason Chen > > > > 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 3 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 th
Re: [DISCUSS] EventMesh Proposal
There are now 10 contributors of this project, but seven of them started the first commit in July. That's a little strange. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Eason Chen 于2020年8月6日周四 下午5:44写道: > Hi, wenming > 1. I believe more people will join in the future ;) > 2. Sure > > > > > -- 原始邮件 -- > 发件人: > "general" > < > wenm...@apache.org>; > 发送时间: 2020年8月6日(星期四) 下午5:23 > 收件人: "general" > 主题: Re: [DISCUSS] EventMesh Proposal > > > > Hi, Eason, > It's an interesting project. And I have a few questions and > it would be great if you could help: > 1. According to github's statistics[1], most of the code was contributed by > yourself. > So if you're on vacation, this project will not easy to move forward. > 2. An external dependency `logback` is LGPL license, which is Category X. > Can this dependency be removed? > > [1] https://github.com/WeBankFinTech/EventMesh/graphs/contributors > > Thanks, > Ming Wen, Apache APISIX & Apache SkyWalking > Twitter: _WenMing > > > Eason Chen > > 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 3 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. Heng Du (from RocketMQ PMC) 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. > > > > > > The project's proposal is available at [1]. > > > > > > Thank you very much for the feedback you're willing to provide! > > > > > > With best regards, > > > > Eason Chen > > > > > > > > [1] > > > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
Re: [DISCUSS] EventMesh Proposal
Hi Noticed this a little late. I have some questions about the status of the project, especially about the `Orphaned Products` and the activity of the community. With a project open-sourced since September 2019, this doesn't seem like the status you said in the proposal. 1. If the EventMesh repo is the only code repo, AFAIK, there is only one contributor who has submitted the codes over 110 lines, most are just < 50 lines. https://github.com/WeBankFinTech/EventMesh/graphs/contributors 2. Only have 35 issues opened on the GitHub. https://github.com/WeBankFinTech/EventMesh/issues 3. The issues(since issue #21) since 21 days ago have no comment any all. >From my understanding, this project is only limited maintained by one and only one for now. To the project community, could you respond what is the real status now? And why there is a gap between your proposal and GitHub open statistics? Personally, I have concerns about the activity and support of the community, or a little more, whether the basic community has been established. I think the incubator should notice the status, in case, it will be hard to make consensus and release soon in the incubating stage. Sheng Wu 吴晟 Twitter, wusheng1108 Ming Wen 于2020年8月6日周四 下午5:24写道: > Hi, Eason, > It's an interesting project. And I have a few questions and > it would be great if you could help: > 1. According to github's statistics[1], most of the code was contributed by > yourself. > So if you're on vacation, this project will not easy to move forward. > 2. An external dependency `logback` is LGPL license, which is Category X. > Can this dependency be removed? > > [1] https://github.com/WeBankFinTech/EventMesh/graphs/contributors > > Thanks, > Ming Wen, Apache APISIX & Apache SkyWalking > Twitter: _WenMing > > > Eason Chen 于2020年8月4日周二 下午6:04写道: > > > 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 3 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. Heng Du (from RocketMQ PMC) 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. > > > > > > The project's proposal is available at [1]. > > > > > > Thank you very much for the feedback you're willing to provide! > > > > > > With best regards, > > > > Eason Chen > > > > > > > > [1] > > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal >
Re: [DISCUSS] EventMesh Proposal
Hi, Eason, It's an interesting project. And I have a few questions and it would be great if you could help: 1. According to github's statistics[1], most of the code was contributed by yourself. So if you're on vacation, this project will not easy to move forward. 2. An external dependency `logback` is LGPL license, which is Category X. Can this dependency be removed? [1] https://github.com/WeBankFinTech/EventMesh/graphs/contributors Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Eason Chen 于2020年8月4日周二 下午6:04写道: > 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 3 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. Heng Du (from RocketMQ PMC) 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. > > > The project's proposal is available at [1]. > > > Thank you very much for the feedback you're willing to provide! > > > With best regards, > > Eason Chen > > > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
Re: [DISCUSS] EventMesh Proposal
Hi Im PMC member from ActiveMQ project. I like the idea, nice. +1 on it as a project idea. I am though a little -1 on the name of the project, I would recommend that an alternative name for the project is found as there maybe a conflict in rights ability to copyright and trademark to it. I’m aware there is a commercial vendor messaging company called Solace, where they use and market their product with heavy use of the name Event Mesh, you can see this just googling event mesh, brings back many hits to their products, marketing material and other records, so they may hold a heavy claim to this name. Best Michael > On 4 Aug 2020, at 18:33, Kevin Ratnasekera wrote: > > Hi Easen, > > +1, Having worked in a similar domain so far, I have to say this is an > interesting project. If you are seeking new mentors, please consider adding > me as a mentor to the project. > > Regards > Kevin > > On Tue, Aug 4, 2020 at 3:34 PM Eason Chen wrote: > >> 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 3 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. Heng Du (from RocketMQ PMC) 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. >> >> >> The project's proposal is available at [1]. >> >> >> Thank you very much for the feedback you're willing to provide! >> >> >> With best regards, >> >> Eason Chen >> >> >> >> [1] >> https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Hi, +1, I'm also interesting by this project and I would be happy to help as mentor if needed. regards, François fpa...@apache.org Le 04/08/2020 à 19:33, Kevin Ratnasekera a écrit : > Hi Easen, > > +1, Having worked in a similar domain so far, I have to say this is an > interesting project. If you are seeking new mentors, please consider adding > me as a mentor to the project. > > Regards > Kevin > > On Tue, Aug 4, 2020 at 3:34 PM Eason Chen wrote: > >> 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 3 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. Heng Du (from RocketMQ PMC) 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. >> >> >> The project's proposal is available at [1]. >> >> >> Thank you very much for the feedback you're willing to provide! >> >> >> With best regards, >> >> Eason Chen >> >> >> >> [1] >> https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Hi Easen, +1, Having worked in a similar domain so far, I have to say this is an interesting project. If you are seeking new mentors, please consider adding me as a mentor to the project. Regards Kevin On Tue, Aug 4, 2020 at 3:34 PM Eason Chen wrote: > 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 3 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. Heng Du (from RocketMQ PMC) 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. > > > The project's proposal is available at [1]. > > > Thank you very much for the feedback you're willing to provide! > > > With best regards, > > Eason Chen > > > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal