Re: [IP CLEARANCE] Dubbo Getty project contribution

2020-08-06 Thread Jun Liu
Hi, 

With no -1 votes being cast, I will consider this IP clearance vote as passed 
by lazy consensus. I will ask the infra team to do the transfer now[1]

1. https://issues.apache.org/jira/browse/DUBBO-43

Jun

> On Jul 24, 2020, at 6:54 PM, Jun Liu  wrote:
> 
> Hi Incubator PMC,
> 
> The Apache Dubbo has been donated code for Getty[1] being referred
> to as `Getty`.
> 
> This is the formal request for IP clearance to be checked as per [2]. The
> transfer task is recorded in here [3] .
> 
> Please check the ip-clearance filed here[4] for more information. The PMC
> has voted and passed to accept this donation[5]. The ICLA of contributors
> have been filed. Secretary has confirmed that SGA is received[6].
> 
> Please vote to approve this contribution.
> 
> This majority vote is open for at least 72 hours and as usual lazy
> consensus applies.
> 
> [1] https://github.com/dubbogo/getty
> [2] 
> https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling
> [3] https://issues.apache.org/jira/browse/DUBBO-43
> [4] https://incubator.apache.org/ip-clearance/dubbo-getty.html
> [5] 
> https://lists.apache.org/thread.html/r46e30a742d5ced2daedbab3d45bd3bf8279c372d4fe1b5599dc8dd0f%40%3Cdev.dubbo.apache.org%3E
> [6] 
> https://lists.apache.org/thread.html/re9f3b21b96f5b8ed0f39981c92dc08147273c07fc755b6958a8e6adb%40%3Cprivate.dubbo.apache.org%3E
> 
> Jun


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



Re:Re: [MENTORS] Podling reports due today

2020-08-06 Thread 陈明雨
Thanks Dave ^^




--

此致!Best Regards
陈明雨 Mingyu Chen

Email:
chenmin...@apache.org





在 2020-08-07 01:32:54,"Dave Fisher"  写道:
>Hi Mingyu Chen,
>
>Thanks for submitting the report. I’ve signed off.
>
>Regards,
>Dave
>
>> On Aug 6, 2020, at 6:41 AM, 陈明雨  wrote:
>> 
>> Hi Justin:
>> 
>> 
>> Sorry that Doris has just sent the report a few hours ago.
>> Can we still catch up with this time?
>> 
>> 
>> 
>> 
>> --
>> 
>> 此致!Best Regards
>> 陈明雨 Mingyu Chen
>> 
>> Email:
>> chenmin...@apache.org
>> 
>> 
>> 
>> 
>> 
>> 在 2020-08-06 20:44:45,"Willem Jiang"  写道:
>>> Sorry for that, I will ping Doris PPMC for sending a report next month.
>>> 
>>> Willem Jiang
>>> 
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>> 
>>> On Thu, Aug 6, 2020 at 3:43 PM Justin Mclean  
>>> wrote:
 
 HI,
 
> Looks like Doris will reimport next moth.
 
 Report next month even :-)
 
 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


?????? [DISCUSS] EventMesh Proposal

2020-08-06 Thread Eason Chen
Hi,
EventMesh will no longer rely strongly on RocketMQ in the future, it is only 
one choice of the storage layer, other MQs, redis, blockchain can be 
supported in the future plans.


EventMesh is very different from Camel i think, it positioned in event 
governance and mesh cloud nativeization.




----
??: 
   "general"

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 https://github.com/WeBankFinTech/EventMesh/graphs/contributors
   gt 


[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-08-06 Thread Henri Yandell (Jira)


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172716#comment-17172716
 ] 

Henri Yandell commented on INCUBATOR-253:
-

Noting that the DJL project have updated their language with regards to Apache 
MXNet, covering point 19.

The DJL package naming in point 17 is referential, it's their (ai.djl)'s 
implementation of a provider for mxnet.

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



Re: [MENTORS] Podling reports due today

2020-08-06 Thread Dave Fisher
Hi Mingyu Chen,

Thanks for submitting the report. I’ve signed off.

Regards,
Dave

> On Aug 6, 2020, at 6:41 AM, 陈明雨  wrote:
> 
> Hi Justin:
> 
> 
> Sorry that Doris has just sent the report a few hours ago.
> Can we still catch up with this time?
> 
> 
> 
> 
> --
> 
> 此致!Best Regards
> 陈明雨 Mingyu Chen
> 
> Email:
> chenmin...@apache.org
> 
> 
> 
> 
> 
> 在 2020-08-06 20:44:45,"Willem Jiang"  写道:
>> Sorry for that, I will ping Doris PPMC for sending a report next month.
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> On Thu, Aug 6, 2020 at 3:43 PM Justin Mclean  
>> wrote:
>>> 
>>> HI,
>>> 
 Looks like Doris will reimport next moth.
>>> 
>>> Report next month even :-)
>>> 
>>> 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

2020-08-06 Thread Clebert Suconic
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'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 

Re: [DISCUSS] EventMesh Proposal

2020-08-06 Thread heng du
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

2020-08-06 Thread Clebert Suconic
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
> >  ;
> >  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 

Re: Re: [MENTORS] Podling reports due today

2020-08-06 Thread Furkan KAMACI
Hi Justin,

NLPCraft will report next month.

Kind Regards,
Furkan KAMACI

On Thu, Aug 6, 2020 at 4:41 PM 陈明雨  wrote:

> Hi Justin:
>
>
> Sorry that Doris has just sent the report a few hours ago.
> Can we still catch up with this time?
>
>
>
>
> --
>
> 此致!Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org
>
>
>
>
>
> 在 2020-08-06 20:44:45,"Willem Jiang"  写道:
> >Sorry for that, I will ping Doris PPMC for sending a report next month.
> >
> >Willem Jiang
> >
> >Twitter: willemjiang
> >Weibo: 姜宁willem
> >
> >On Thu, Aug 6, 2020 at 3:43 PM Justin Mclean 
> wrote:
> >>
> >> HI,
> >>
> >> > Looks like Doris will reimport next moth.
> >>
> >> Report next month even :-)
> >>
> >> 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:Re: [MENTORS] Podling reports due today

2020-08-06 Thread 陈明雨
Hi Justin:


Sorry that Doris has just sent the report a few hours ago.
Can we still catch up with this time?




--

此致!Best Regards
陈明雨 Mingyu Chen

Email:
chenmin...@apache.org





在 2020-08-06 20:44:45,"Willem Jiang"  写道:
>Sorry for that, I will ping Doris PPMC for sending a report next month.
>
>Willem Jiang
>
>Twitter: willemjiang
>Weibo: 姜宁willem
>
>On Thu, Aug 6, 2020 at 3:43 PM Justin Mclean  wrote:
>>
>> HI,
>>
>> > Looks like Doris will reimport next moth.
>>
>> Report next month even :-)
>>
>> 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

2020-08-06 Thread Sheng Wu
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
>  ;
>  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 

Re: [MENTORS] Podling reports due today

2020-08-06 Thread Willem Jiang
Sorry for that, I will ping Doris PPMC for sending a report next month.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Aug 6, 2020 at 3:43 PM Justin Mclean  wrote:
>
> HI,
>
> > Looks like Doris will reimport next moth.
>
> Report next month even :-)
>
> 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



?????? [DISCUSS] EventMesh Proposal

2020-08-06 Thread Eason Chen
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.


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"

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 https://github.com/WeBankFinTech/EventMesh/graphs/contributors

 Thanks,
 Ming Wen, Apache APISIX  Apache SkyWalking
 Twitter: _WenMing


 Eason Chen https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal


Re: [DISCUSS] EventMesh Proposal

2020-08-06 Thread Ming Wen
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!
> 
> 
>  nbsp;With best regards,
> 
>  nbsp;Eason Chen
> 
> 
> 
>  [1]
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal


?????? [DISCUSS] EventMesh Proposal

2020-08-06 Thread Eason Chen
Hi, wenming
1. I believe more people will join in the future ;)
2. Sure




----
??: 
   "general"

https://github.com/WeBankFinTech/EventMesh/graphs/contributors

Thanks,
Ming Wen, Apache APISIX  Apache SkyWalking
Twitter: _WenMing


Eason Chen https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal

Re: [DISCUSS] EventMesh Proposal

2020-08-06 Thread Sheng Wu
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

2020-08-06 Thread 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

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: [MENTORS] Podling reports due today

2020-08-06 Thread Justin Mclean
HI,

> Looks like Doris will reimport next moth.

Report next month even :-)

Thanks,
Justin

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



Re: [MENTORS] Podling reports due today

2020-08-06 Thread Justin Mclean
Hi,

Looks like Doris will reimport next moth.

What do you think we should do about Warble? Either your an incubating project 
with PPMC oversight or not, there isn’t really a consent of a dormant project.

Still missing and unless they are submitted ASAP they will be expected to 
report next month are:
Liminal
Livy
NLPCraft
Pinot
S2Graph
SDAP
Sedona
Training

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

2020-08-06 Thread Michael André Pearce
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

2020-08-06 Thread fpapon
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: [VOTE] Release Apache DolphinScheduler Maven Plugin (Incubating) 1.0.0

2020-08-06 Thread Jun Gao
I am sorry, I re-learned the information about the release, and there are 
indeed some problems with this release.

1. The binary package is indeed required in svn.
2. The license and notice files in the release-docs directory are not required 
in the source tar, because the source tar does not contain third-party 
dependencies.
3. I will build a binary tar and include right LICENSE .

So, I will re-release and vote again.

Thank you !

On 2020/08/05 15:26:42, Sheng Wu  wrote: 
> Questions.
> 1. Why I can't find the binary tar in the svn? But at the same time, you
> have one uploaded in the maven staging?
> 2. Why does the source tar include the `release-docs/LICENSE` and NOTICE
> 3. Why doesn't the LICENSE in the staging tar(
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1036/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/)
> include the right LICENSE?
> 
> I checked
> 1. incubating in name
> 2. ASC checked
> 3. sha512 exists
> 4. maven compile passed
> 5. LICENSE and NOTICE exist in the source tar
> 6. DISCLAIMER exists
> 7. rat check passed
> 
> 
> Sheng Wu 吴晟
> Twitter, wusheng1108
> 
> 
> JUN GAO  于2020年7月31日周五 下午3:33写道:
> 
> > Hello IPMC and DolphinScheduler Community,
> >
> > This is a call for a vote to release Apache DolphinScheduler Maven Plugin
> > (Incubating) version 1.0.0.
> >
> > The Apache DolphinScheduler community has voted on and approved a proposal
> > to release Apache DolphinScheduler Maven Plugin (Incubating) 1.0.0
> >
> > We now kindly request the Incubator IPMC members review and vote on this
> > incubator release.
> >
> > Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow
> > scheduling system, dedicated to solving the complex dependencies in data
> > processing, making the scheduling system out of the box for data
> > processing.
> >
> > DolphinScheduler community vote and result threads:
> >
> > https://lists.apache.org/thread.html/r65cebb453bf8f7668a82a49a4c2c224b8d153bdc55167a815ff85620%40%3Cdev.dolphinscheduler.apache.org%3E
> >
> >
> > https://lists.apache.org/thread.html/rd5320c6b7f2595ca5286215bed64261848dcb3c89d4e7880769a8771%40%3Cdev.dolphinscheduler.apache.org%3E
> >
> > The release candidates:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> >
> > Maven 2 staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1036/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/
> >
> > Git tag for the release:
> >
> > https://github.com/apache/incubator-dolphinscheduler-maven-plugin/releases/tag/1.0.0
> >
> > Release Commit ID:
> >
> > https://github.com/apache/incubator-dolphinscheduler-maven-plugin/commit/477b31d196de92a18975078f1b0963c49a9695d7
> >
> > Keys to verify the Release Candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS
> >
> > Look at here for how to verify this release candidate:
> >
> > https://github.com/apache/incubator-dolphinscheduler-maven-plugin/blob/1.0.0/README.md
> >
> > The vote will be open for at least 72 hours or until a necessary number of
> > votes are reached.
> > Please vote accordingly:
> >
> > [ ] +1 approveg
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove with the reason
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> >
> > [ ] Checksums and PGP signatures are valid.
> >
> > [ ] Source code artifacts have correct names matching the current release.
> >
> > [ ] LICENSE and NOTICE files are correct for each DolphinScheduler repo.
> >
> > [ ] All files have license headers if necessary.
> >
> > [ ] No compiled archives bundled in source archive.
> >
> > More detail checklist please refer:
> >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > --
> >
> > DolphinScheduler(Incubator)  PPMC
> > Jun Gao 高俊
> > gaojun2...@gmail.com
> >
> 

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