Re: [VOTE] Release Apache Liminal (incubating) 0.0.1rc4-INCUBATING

[Justin Mclean]

Hi,

> ▶ shasum -c apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512
> shasum: apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512: No such file 
> or directory
>   
> ⍉
> ▶ shasum -a 512  -c apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512
> shasum: apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512: No such file 
> or directory

This may help.

The files may download with .txt extensions you may need to rename them to .sha.

I have a little bash function to do this:

function untxt() {
 find . -name '*.txt' | while read f; do mv "$f" "${f/\.txt/}"; done
}

I generally compare:
shasum -a 512 apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz

with the .sha512 file under nuttx-ing it

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Liminal (incubating) 0.0.1rc4-INCUBATING

[Juan Pan]

Hi,


Here is my checking list,


[x] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[x] LICENSE and NOTICE files are correct (From[1]). 
[x] All files have license headers if necessary.
[x] Install successfully.




PGP signatures are well. However, I got the following exceptions when checksums 
on macOS. 
Did I miss something? 




▶ shasum -c apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512
shasum: apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512: No such file 
or directory
   ⍉
▶ shasum -a 512  -c apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512
shasum: apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512: No such file 
or directory






[1] 
https://github.com/apache/incubator-liminal/commit/8441a3f428982888fe70ce76a89506a80a43845d


 
   Juan Pan (Trista)
 
Senior DBA & PMC of Apache ShardingSphere
E-mail: panj...@apache.org




On 01/28/2021 09:12，Justin Mclean wrote：
Hi,

+1 of the source release, but -1 on the whl file.

For the source release I checked:
- incubating in name
- signatures and hashes are fine
- DISCLAIMER (WIP) exists but still has "List of known issues goes here”. You 
need to mention what issue this release has.
- LICENSE is good
- NOTICE is OK no need for "I. Included Software”
- All source files have ASF headers
- No unexpected binary files

For the whl file, everything is fine as above, and it now does contain the 
LICENSE and NOTICE but is missing a DISCLAIMER file. All releases must contain 
an incubating disclaimer.

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

[Dave Fisher]

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: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

[Goson zhang]

Hi Justin:

Thank you for your prompt reply, I understand. And there is one more
question for help:

- NOTICE is missing information from other Apache licensed NOTICE files.
Information from these  NOTICE files [5][6][7][10] will need to be added.

We did it in the way of [6] [10]. What is the relationship between [5] [7]
and [6] [10]? When do you use the former mode to declare, and when do you
use the concise mode?

Thanks!

Justin Mclean  于2021年1月28日周四 上午11:46写道：

> Hi,
>
> > 1. If the referenced file source has the original version statement, we
> should keep it as it is and cannot replace it with the Apache v2 statement?
>
> Correct.
>
> > 2. If the referenced file source does not have a version statement, but
> the project of the file has a version statement, do we copy the license
> statement of the project to the file header?
>
> I would just leave the file as it is.
>
> > 3. Do we still need to indicate which project the source of the document
> comes from?
> > such as[9]:
> >   /**
> >   * Utility for .ini configure file loading.
> >   * Copied from https://github.com/killme2008/Metamorphosis <
> https://github.com/killme2008/Metamorphosis>">Metamorphosis Project
> >   */
>
> It best to mentioner that in LICENSE, but I see no harm in adding that.
>
> Thanks,
> Justin

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

[Justin Mclean]

Hi,

> 1. If the referenced file source has the original version statement, we 
> should keep it as it is and cannot replace it with the Apache v2 statement?

Correct.

> 2. If the referenced file source does not have a version statement, but the 
> project of the file has a version statement, do we copy the license statement 
> of the project to the file header?

I would just leave the file as it is.

> 3. Do we still need to indicate which project the source of the document 
> comes from? 
> such as[9]:
>   /**
>   * Utility for .ini configure file loading.
>   * Copied from https://github.com/killme2008/Metamorphosis 
> ">Metamorphosis Project
>   */  

It best to mentioner that in LICENSE, but I see no harm in adding that.

Thanks,
Justin

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

[Justin Mclean]

Hi,

> 1. Is it necessary to remove the description of part B in the above 
> screenshot?

I can’t see teh screen shot so not sure what you are asking here sorry.

> 2. If the file source itself does not have a LICENSE authorization statement, 
> but the top level of the project is Apache V2 or other authorization 
> agreements, should we add the corresponding authorization statement in the 
> header of this file?

I wold leave the file as it is, 3rd party files shouldn't have ASF headers on 
them.

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

[Justin Mclean]

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: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc3

[Justin Mclean]

Hi,

+1 (binding) but only because of WIP DISCLAIMER. LICENSE is not correct and 
source release contains Category B licensed bits.

I checked:
- incubating in name
- signatures and hashes are fine
- DISCLAIMER (WIP) exist but information has not been updated in it
- LICENSE looks OK but I’ve not checked everything and there looks like there 
been a lot  of changes since the last release. It missing some 3rd party 
licenses.
- NOTICE has incorrect year
- The source include a font under the OFL license In general this can't be 
included in a source release. [1] This should be mention in the DISCLAIMER. 
Also [4] and [7] are under the OFL license I believe.
- It would be good to see more description in the rat exclusions file (and have 
it at the top level)
- No unexpected binary files. However I did seem some binary files that should 
be mentioned in LICENSE. [2][3][4][5][6][7]
- It also unclear how [2] is licensed and may be category X
-  I didn’t try to compile from source

Thanks,
Justin


1 https://www.apache.org/legal/resolved.html#weak-copyleft-licenses
2. ./3rdparty/mkldnn/doc/assets/fonts/fontawesome-webfont*
3. ./3rdparty/mkldnn/doc/assets/fonts/lato*
4. ./3rdparty/mkldnn/doc/assets/mathjax/fonts/HTML-CSS/Asana-Math/otf*
5. ./3rdparty/mkldnn/doc/assets/mathjax/fonts/HTML-CSS/*/*/MathJax*
6. 
./docs/python_docs/themes/mx-theme/mxtheme/static/material-design-icons-3.0.1/iconfont/*
7. /docs/python_docs/themes/mx-theme/mxtheme/static/webfonts/fa-solid*


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

[Goson zhang]

Hi Justin,

Regarding the point 3, I have questions:

1. If the referenced file source has the original version statement, we
should keep it as it is and cannot replace it with the Apache v2 statement?

2. If the referenced file source does not have a version statement, but the
project of the file has a version statement, do we copy the license
statement of the project to the file header?

3. Do we still need to indicate which project the source of the document
comes from?
such as[9]:

>   /**
>   * Utility for .ini configure file loading.
>   * Copied from  href="https://github.com/killme2008/Metamorphosis;>Metamorphosis
> Project
>   */
>


9. Is this declaration in the
tubemq-server/src/main/java/org/apache/tubemq/server/tools/ToolUtils.java

Thanks!

Goson zhang  于2021年1月28日周四 上午11:19写道：

> [image: image.png]
>
> Hi Justin:
>
> Regarding the third point, I don’t quite understand. Regarding [3] [4] [9]:
>
> 1. Is it necessary to remove the description of part B in the above
> screenshot?
>
> 2. If the file source itself does not have a LICENSE authorization
> statement, but the top level of the project is Apache V2 or other
> authorization agreements, should we add the corresponding authorization
> statement in the header of this file?
>
>
> 3. ./tubemq-client-twins/tubemq-client-cpp/src/any.h
> 4. ./tubemq-client-twins/tubemq-client-cpp/src/buffer.h
> 8.
> tubemq-core/src/main/java/org/apache/tubemq/corebase/utils/TStringUtils.java
> 9.
> tubemq-server/src/main/java/org/apache/tubemq/server/tools/ToolUtils.java
>
> Justin Mclean  于2021年1月28日周四 上午11:10写道：
>
>> Hi,
>>
>> > - These files seem to have incorrect headers [1][2][3][4][8][9]. ASF
>> headers should include a copyright line and 3rd part headers need to be
>> kept unchanged.
>>
>> Sorry that should be "ASF headers should NOT include a copyright line”
>>
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

[Goson zhang]

[image: image.png]

Hi Justin:

Regarding the third point, I don’t quite understand. Regarding [3] [4] [9]:

1. Is it necessary to remove the description of part B in the above
screenshot?

2. If the file source itself does not have a LICENSE authorization
statement, but the top level of the project is Apache V2 or other
authorization agreements, should we add the corresponding authorization
statement in the header of this file?


3. ./tubemq-client-twins/tubemq-client-cpp/src/any.h
4. ./tubemq-client-twins/tubemq-client-cpp/src/buffer.h
8.
tubemq-core/src/main/java/org/apache/tubemq/corebase/utils/TStringUtils.java
9. tubemq-server/src/main/java/org/apache/tubemq/server/tools/ToolUtils.java

Justin Mclean  于2021年1月28日周四 上午11:10写道：

> Hi,
>
> > - These files seem to have incorrect headers [1][2][3][4][8][9]. ASF
> headers should include a copyright line and 3rd part headers need to be
> kept unchanged.
>
> Sorry that should be "ASF headers should NOT include a copyright line”
>
> 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]

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=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: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

[Justin Mclean]

Hi,

> - These files seem to have incorrect headers [1][2][3][4][8][9]. ASF headers 
> should include a copyright line and 3rd part headers need to be kept 
> unchanged.

Sorry that should be "ASF headers should NOT include a copyright line”

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

[Yuanbo Liu]

Hi, Justin
 Thanks for your check, we will go through your comments and create jira
correspondingly.

On Thu, Jan 28, 2021 at 10:43 AM Goson zhang  wrote:

>  Thanks Justin, very complete and detailed guidance, thank you!!
>
> The BDB download problem, if the third-party warehouse cannot let everyone
> compile, we will make adjustments.
>
> Thanks
>
> Justin Mclean  于2021年1月28日周四 上午10:01写道：
>
> > Hi,
> >
> > -1 (binding) due to license and notice issues and possible inclusion of
> > Category X software
> >
> > It unclear to me if the berkeleydb-je licensing issue has been resolved.
> I
> > can’t find any discussion of it on your mailing list. Can someone tell me
> > what the outcome of this was?
> >
> > I checked:
> > - incubating in name
> > - signatures and hashes all good
> > - LICENSE has a few issues. There is need to have the Apache license text
> > twice. The 3rd party license text in not being included correctly for MIT
> > and BSD licenses as these licenses includes a copyright line.
> > - NOTICE has incorrect year
> > - NOTICE is missing information from other Apache licensed NOTICE files.
> > Information from these  NOTICE files [5][6][7][10] will need to be added.
> > - These files seem to have incorrect headers [1][2][3][4][8][9]. ASF
> > headers should include a copyright line and 3rd part headers need to be
> > kept unchanged.
> > - This file [8] doesn’t seem to be under an Apache license and may be
> > Category X.
> > - It’s unclear how these files are licensed [11]
> > - No unexpected binary files
> > - Can’t compile from source
> > [ERROR] Failed to execute goal on project tubemq-all: Could not resolve
> > dependencies for project
> org.apache.tubemq:tubemq-all:pom:0.8.0-incubating:
> > Could not find artifact
> > org.apache.tubemq:tubemq-server:tar.gz:bin:0.8.0-incubating in
> > berkeleydb-je (
> https://download.dcache.org/nexus/repository/berkeleydb-je/)
> > -> [Help 1]
> >
> > Some of these issue were noted on previous releases.
> >
> > Thanks,
> > Justin
> >
> > 1.
> ./tubemq-client-twins/tubemq-client-python/src/python/tubemq/client.conf
> > 2. ./tubemq-client-twins/tubemq-client-cpp/conf/client.conf
> > 3. ./tubemq-client-twins/tubemq-client-cpp/src/any.h
> > 4. ./tubemq-client-twins/tubemq-client-cpp/src/buffer.h
> > 5. https://github.com/apache/hbase/blob/master/NOTICE.txt
> > 6. https://github.com/apache/mina/blob/trunk/NOTICE
> > 7. https://github.com/apache/avro/blob/master/NOTICE.txt
> > 8.
> >
> tubemq-core/src/main/java/org/apache/tubemq/corebase/utils/TStringUtils.java
> > 9.
> > tubemq-server/src/main/java/org/apache/tubemq/server/tools/ToolUtils.java
> > 10 https://github.com/apache/pulsar/blob/master/NOTICE
> > 11. ./resources/assets/public/css/fonts/icon.*
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

[Goson zhang]

 Thanks Justin, very complete and detailed guidance, thank you!!

The BDB download problem, if the third-party warehouse cannot let everyone
compile, we will make adjustments.

Thanks

Justin Mclean  于2021年1月28日周四 上午10:01写道：

> Hi,
>
> -1 (binding) due to license and notice issues and possible inclusion of
> Category X software
>
> It unclear to me if the berkeleydb-je licensing issue has been resolved. I
> can’t find any discussion of it on your mailing list. Can someone tell me
> what the outcome of this was?
>
> I checked:
> - incubating in name
> - signatures and hashes all good
> - LICENSE has a few issues. There is need to have the Apache license text
> twice. The 3rd party license text in not being included correctly for MIT
> and BSD licenses as these licenses includes a copyright line.
> - NOTICE has incorrect year
> - NOTICE is missing information from other Apache licensed NOTICE files.
> Information from these  NOTICE files [5][6][7][10] will need to be added.
> - These files seem to have incorrect headers [1][2][3][4][8][9]. ASF
> headers should include a copyright line and 3rd part headers need to be
> kept unchanged.
> - This file [8] doesn’t seem to be under an Apache license and may be
> Category X.
> - It’s unclear how these files are licensed [11]
> - No unexpected binary files
> - Can’t compile from source
> [ERROR] Failed to execute goal on project tubemq-all: Could not resolve
> dependencies for project org.apache.tubemq:tubemq-all:pom:0.8.0-incubating:
> Could not find artifact
> org.apache.tubemq:tubemq-server:tar.gz:bin:0.8.0-incubating in
> berkeleydb-je (https://download.dcache.org/nexus/repository/berkeleydb-je/)
> -> [Help 1]
>
> Some of these issue were noted on previous releases.
>
> Thanks,
> Justin
>
> 1. ./tubemq-client-twins/tubemq-client-python/src/python/tubemq/client.conf
> 2. ./tubemq-client-twins/tubemq-client-cpp/conf/client.conf
> 3. ./tubemq-client-twins/tubemq-client-cpp/src/any.h
> 4. ./tubemq-client-twins/tubemq-client-cpp/src/buffer.h
> 5. https://github.com/apache/hbase/blob/master/NOTICE.txt
> 6. https://github.com/apache/mina/blob/trunk/NOTICE
> 7. https://github.com/apache/avro/blob/master/NOTICE.txt
> 8.
> tubemq-core/src/main/java/org/apache/tubemq/corebase/utils/TStringUtils.java
> 9.
> tubemq-server/src/main/java/org/apache/tubemq/server/tools/ToolUtils.java
> 10 https://github.com/apache/pulsar/blob/master/NOTICE
> 11. ./resources/assets/public/css/fonts/icon.*
>
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC1

[Justin Mclean]

Hi,

-1 (binding) due to license and notice issues and possible inclusion of 
Category X software

It unclear to me if the berkeleydb-je licensing issue has been resolved. I 
can’t find any discussion of it on your mailing list. Can someone tell me what 
the outcome of this was?

I checked:
- incubating in name
- signatures and hashes all good
- LICENSE has a few issues. There is need to have the Apache license text 
twice. The 3rd party license text in not being included correctly for MIT and 
BSD licenses as these licenses includes a copyright line.
- NOTICE has incorrect year
- NOTICE is missing information from other Apache licensed NOTICE files. 
Information from these  NOTICE files [5][6][7][10] will need to be added.
- These files seem to have incorrect headers [1][2][3][4][8][9]. ASF headers 
should include a copyright line and 3rd part headers need to be kept unchanged.
- This file [8] doesn’t seem to be under an Apache license and may be Category 
X.
- It’s unclear how these files are licensed [11]
- No unexpected binary files
- Can’t compile from source
[ERROR] Failed to execute goal on project tubemq-all: Could not resolve 
dependencies for project org.apache.tubemq:tubemq-all:pom:0.8.0-incubating: 
Could not find artifact 
org.apache.tubemq:tubemq-server:tar.gz:bin:0.8.0-incubating in berkeleydb-je 
(https://download.dcache.org/nexus/repository/berkeleydb-je/) -> [Help 1]

Some of these issue were noted on previous releases.

Thanks,
Justin

1. ./tubemq-client-twins/tubemq-client-python/src/python/tubemq/client.conf
2. ./tubemq-client-twins/tubemq-client-cpp/conf/client.conf
3. ./tubemq-client-twins/tubemq-client-cpp/src/any.h
4. ./tubemq-client-twins/tubemq-client-cpp/src/buffer.h
5. https://github.com/apache/hbase/blob/master/NOTICE.txt
6. https://github.com/apache/mina/blob/trunk/NOTICE
7. https://github.com/apache/avro/blob/master/NOTICE.txt
8. tubemq-core/src/main/java/org/apache/tubemq/corebase/utils/TStringUtils.java
9. tubemq-server/src/main/java/org/apache/tubemq/server/tools/ToolUtils.java
10 https://github.com/apache/pulsar/blob/master/NOTICE
11. ./resources/assets/public/css/fonts/icon.*





-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] EventMesh Proposal

[Dave Fisher]

> 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=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: [VOTE] Release Apache Liminal (incubating) 0.0.1rc4-INCUBATING

[Justin Mclean]

Hi,

+1 of the source release, but -1 on the whl file.

For the source release I checked:
- incubating in name
- signatures and hashes are fine
- DISCLAIMER (WIP) exists but still has "List of known issues goes here”. You 
need to mention what issue this release has.
- LICENSE is good
- NOTICE is OK no need for "I. Included Software”
- All source files have ASF headers
- No unexpected binary files

For the whl file, everything is fine as above, and it now does contain the 
LICENSE and NOTICE but is missing a DISCLAIMER file. All releases must contain 
an incubating disclaimer.

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

[vongosling]

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=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 

Re: [DISCUSS] EventMesh Proposal

[Dave Fisher]

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=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

[Matt Sicker]

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=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 

Re: [DISCUSS] EventMesh Proposal

[Sheng Wu]

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=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

[Eason Chen]

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 

Re: [DISCUSS] EventMesh Proposal

[ShannonDing]

I would like to make a comments about this serious problem too,
In order not to cause unnecessary trouble in the future, we also request the 
infra member from apache to help check whether this name is appropriate[1]. 
For us, we have used the name EventMesh for a long time, and we want to keep it 
so that users can get better product positioning from this name. 
According to this document[2], we also searched in the US Patent Office[3] and 
found no non-compliance.


[1] https://issues.apache.org/jira/browse/INFRA-21353
[2] https://incubator.apache.org/guides/names.html
[3] https://www.uspto.gov/trademark




On 01/27/2021 21:11，Eason Chen wrote：
@Sheng Wu
thank you for your kindly reminder. I would like to clarify this concerns.

As @Duane Pauls  clarified this before:
“*I work for Solace and have consulted internally to confirm that we do not
have any copyright or trademark on the term “Event Mesh”. It’s true it is
something our products are closely aligned with。 Solace does not oppose the
term being used in other applicable products or projects.*”
Solace do not  have any copyright or trademark on the term “Event Mesh”.

On Wed, Jan 27, 2021 at 5:17 PM Sheng Wu  wrote:

Hi

I want to send a reminder for your project name chosen.
Event Mesh is widely used as a concept and term, you could find it through
Google search, https://www.google.com/search?q=event+mesh=event+mesh

Sheng Wu 吴晟
Twitter, wusheng1108


 于2021年1月27日周三 下午5:12写道：

Hi,

Yes, it looks very promising.

I will be very happy to help in the incubation process and integrate the
project into Karaf with JB ;)

regards,

François
fpa...@apache.org

Le 27/01/2021 à 10:07, vongosling a écrit :
Hi,

This is a very young but promising project. The team attached great
importance to this project according to the feedback given by
communities.
Through the efforts of the last five months, I am glad to see positive
changes in the project and community.

@Jean-Baptiste Onofré   EventMesh really need
to improve its lighter plugin modules, karaf may be a good optional

Best Regards,
Von Gosling

Jean-Baptiste Onofre  于2021年1月27日周三 下午4:43写道：

Hi Eason,

That’s an interesting proposal, indeed.

I would rewrite some part of the proposal, but overall good.

I will check if the EventMesh architecture is "pluggable", meaning
that
we
"could" replace RocketMQ with another messaging/async provider.

Anyway, if you need some help on the project, please let me know, it’s
interesting and could be a good extend to Apache Karaf for instance.

Regards
JB

Le 27 janv. 2021 à 09:32, Eason Chen  a
écrit :
Good time of the time to all!

I'd like to bring this new interesting project for the discussion,
comments
and feedback with the aim of starting a formal [VOTE] of its
acceptance
into Incubator.

People behind this project aren't new to Apache: some of them were
behind
the Apache RocketMQ, which I consider a huge success(especially in
China)
as the community is literally thriving almost 5 years after the
graduation.
I have been involved a little bit with this project when it just
started
in
WeBank a few years ago. And I'd like to emphasize that the community
however small it might look so far, has been aligned with Apache ways
of
doing things. Von Gosling is very instrumental in tirelessly helping
this
group to learn what it means to be a truly open source project.

The code is already under ALv2 and is publicly available. As you will
see
it has a lot of dependency connections with the rest of Apache
ecosystem
and IMO will fit very well here and continue to grow the community.

By the way, we still need 1 to 2 mentors, please let me know if you
are
interested.

With best regards,

The project's proposal is available at [1].

Thank you very much for the feedback you're willing to provide!

Eason Chen

[1]



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] EventMesh Proposal

[Eason Chen]

@Sheng Wu
thank you for your kindly reminder. I would like to clarify this concerns.

As @Duane Pauls  clarified this before:
“*I work for Solace and have consulted internally to confirm that we do not
 have any copyright or trademark on the term “Event Mesh”. It’s true it is
something our products are closely aligned with。 Solace does not oppose the
term being used in other applicable products or projects.*”
>> Solace do not  have any copyright or trademark on the term “Event Mesh”.

On Wed, Jan 27, 2021 at 5:17 PM Sheng Wu  wrote:

> Hi
>
> I want to send a reminder for your project name chosen.
> Event Mesh is widely used as a concept and term, you could find it through
> Google search, https://www.google.com/search?q=event+mesh=event+mesh
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
>  于2021年1月27日周三 下午5:12写道：
>
> > Hi,
> >
> > Yes, it looks very promising.
> >
> > I will be very happy to help in the incubation process and integrate the
> > project into Karaf with JB ;)
> >
> > regards,
> >
> > François
> > fpa...@apache.org
> >
> > Le 27/01/2021 à 10:07, vongosling a écrit :
> > > Hi,
> > >
> > > This is a very young but promising project. The team attached great
> > > importance to this project according to the feedback given by
> > communities.
> > > Through the efforts of the last five months, I am glad to see positive
> > > changes in the project and community.
> > >
> > > @Jean-Baptiste Onofré   EventMesh really need
> > > to improve its lighter plugin modules, karaf may be a good optional
> > >
> > > Best Regards,
> > > Von Gosling
> > >
> > > Jean-Baptiste Onofre  于2021年1月27日周三 下午4:43写道：
> > >
> > >> Hi Eason,
> > >>
> > >> That’s an interesting proposal, indeed.
> > >>
> > >> I would rewrite some part of the proposal, but overall good.
> > >>
> > >> I will check if the EventMesh architecture is "pluggable", meaning
> that
> > we
> > >> "could" replace RocketMQ with another messaging/async provider.
> > >>
> > >> Anyway, if you need some help on the project, please let me know, it’s
> > >> interesting and could be a good extend to Apache Karaf for instance.
> > >>
> > >> Regards
> > >> JB
> > >>
> > >>> Le 27 janv. 2021 à 09:32, Eason Chen  a
> > >> écrit :
> > >>> Good time of the time to all!
> > >>>
> > >>> I'd like to bring this new interesting project for the discussion,
> > >> comments
> > >>> and feedback with the aim of starting a formal [VOTE] of its
> acceptance
> > >>> into Incubator.
> > >>>
> > >>> People behind this project aren't new to Apache: some of them were
> > behind
> > >>> the Apache RocketMQ, which I consider a huge success(especially in
> > China)
> > >>> as the community is literally thriving almost 5 years after the
> > >> graduation.
> > >>> I have been involved a little bit with this project when it just
> > started
> > >> in
> > >>> WeBank a few years ago. And I'd like to emphasize that the community
> > >>> however small it might look so far, has been aligned with Apache ways
> > of
> > >>> doing things. Von Gosling is very instrumental in tirelessly helping
> > this
> > >>> group to learn what it means to be a truly open source project.
> > >>>
> > >>> The code is already under ALv2 and is publicly available. As you will
> > see
> > >>> it has a lot of dependency connections with the rest of Apache
> > ecosystem
> > >>> and IMO will fit very well here and continue to grow the community.
> > >>>
> > >>> By the way, we still need 1 to 2 mentors, please let me know if you
> are
> > >>> interested.
> > >>>
> > >>> With best regards,
> > >>>
> > >>> The project's proposal is available at [1].
> > >>>
> > >>> Thank you very much for the feedback you're willing to provide!
> > >>>
> > >>> Eason Chen
> > >>>
> > >>> [1]
> > >>
> > >>
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] EventMesh Proposal

[fpapon]

+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

[Jean-Baptiste Onofre]

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

[Eason Chen]

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

[Sheng Wu]

Hi

I want to send a reminder for your project name chosen.
Event Mesh is widely used as a concept and term, you could find it through
Google search, https://www.google.com/search?q=event+mesh=event+mesh

Sheng Wu 吴晟
Twitter, wusheng1108


 于2021年1月27日周三 下午5:12写道：

> Hi,
>
> Yes, it looks very promising.
>
> I will be very happy to help in the incubation process and integrate the
> project into Karaf with JB ;)
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 27/01/2021 à 10:07, vongosling a écrit :
> > Hi,
> >
> > This is a very young but promising project. The team attached great
> > importance to this project according to the feedback given by
> communities.
> > Through the efforts of the last five months, I am glad to see positive
> > changes in the project and community.
> >
> > @Jean-Baptiste Onofré   EventMesh really need
> > to improve its lighter plugin modules, karaf may be a good optional
> >
> > Best Regards,
> > Von Gosling
> >
> > Jean-Baptiste Onofre  于2021年1月27日周三 下午4:43写道：
> >
> >> Hi Eason,
> >>
> >> That’s an interesting proposal, indeed.
> >>
> >> I would rewrite some part of the proposal, but overall good.
> >>
> >> I will check if the EventMesh architecture is "pluggable", meaning that
> we
> >> "could" replace RocketMQ with another messaging/async provider.
> >>
> >> Anyway, if you need some help on the project, please let me know, it’s
> >> interesting and could be a good extend to Apache Karaf for instance.
> >>
> >> Regards
> >> JB
> >>
> >>> Le 27 janv. 2021 à 09:32, Eason Chen  a
> >> écrit :
> >>> Good time of the time to all!
> >>>
> >>> I'd like to bring this new interesting project for the discussion,
> >> comments
> >>> and feedback with the aim of starting a formal [VOTE] of its acceptance
> >>> into Incubator.
> >>>
> >>> People behind this project aren't new to Apache: some of them were
> behind
> >>> the Apache RocketMQ, which I consider a huge success(especially in
> China)
> >>> as the community is literally thriving almost 5 years after the
> >> graduation.
> >>> I have been involved a little bit with this project when it just
> started
> >> in
> >>> WeBank a few years ago. And I'd like to emphasize that the community
> >>> however small it might look so far, has been aligned with Apache ways
> of
> >>> doing things. Von Gosling is very instrumental in tirelessly helping
> this
> >>> group to learn what it means to be a truly open source project.
> >>>
> >>> The code is already under ALv2 and is publicly available. As you will
> see
> >>> it has a lot of dependency connections with the rest of Apache
> ecosystem
> >>> and IMO will fit very well here and continue to grow the community.
> >>>
> >>> By the way, we still need 1 to 2 mentors, please let me know if you are
> >>> interested.
> >>>
> >>> With best regards,
> >>>
> >>> The project's proposal is available at [1].
> >>>
> >>> Thank you very much for the feedback you're willing to provide!
> >>>
> >>> Eason Chen
> >>>
> >>> [1]
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] EventMesh Proposal

[fpapon]

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

[vongosling]

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

[Jean-Baptiste Onofre]

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

[DISCUSS] EventMesh Proposal

[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 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] https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal