Re: [DISCUSS] EasyScheduler incubator proposal

[Sheng Wu]

Hi

I will start the proposal vote soon. Thank everyone's support.

Sheng Wu 吴晟

Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
Twitter, wusheng1108


Sheng Wu  于2019年8月20日周二 上午9:56写道：

> Proposal name changed, new WIKI page link,
> https://cwiki.apache.org/confluence/display/INCUBATOR/DolphinSchedulerProposal
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> Twitter, wusheng1108
>
>
> Sheng Wu  于2019年8月19日周一 下午11:28写道：
>
>> Hi Justin and Incubator
>>
>> Regarding the project name potential conflict risk, the EasyScheduler
>> community decided to choose a new name.
>> Through a public community vote[1], they are going to use
>> `DolphinScheduler` as the new project name.
>>
>> Later, I will change the proposal and sync update w/ new link to here.
>>
>> Thank you.
>>
>>
>> [1]
>> https://github.com/analysys/EasyScheduler/issues/701#issuecomment-522626780
>>
>> Sheng Wu 吴晟
>>
>> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
>> Twitter, wusheng1108
>>
>>
>> Sheng Wu  于2019年8月18日周日 上午8:29写道：
>>
>>> Hi Justin
>>>
>>> Inline
>>>
>>> Justin Mclean  于2019年8月18日周日 上午7:25写道：
>>>
 Hi,

 Thanks for your proposal, it looks good.

 I have a couple of questions:
 - Re the name, other software exists with the same name e.g. [1] (and
 others) Has the project considered that it may not be able to keep this
 name and what it would do if this was the case?

>>>
>>> Oh, that is new, thanks for pointing that out in first place. From my
>>> perspective, it is better to rename now than later.
>>>
>>>
 - The NOTICE file refers to the The Analysys Foundation [2] what is the
 relation of this group to the project? Has the community agreed to want to
 move the project to the Apache Software Foundation? Is that documented
 anywhere?

>>>
>>> First, the Analysys is a company, not a Foundation.
>>> And Yes.
>>>
>>> In the proposal, we have this.
>>> > Source and Intellectual Property Submission Plan
>>> > As soon as EasyScheduler is approved to join Apache Incubator,
>>> Analysys will provide the Software Grant Agreement(SGA) and intial
>>> committers will submit ICLA(s). The code is already licensed under the
>>> Apache > Software License, version 2.0.
>>>
>>> We have got confirmation from them, SGA will be submitted by Analysys.
>>> This is not documented, but from I known, they will submit the SGA soon
>>> after this proposal accepted. I will make sure the SGA filed before the
>>> repositories transformation.
>>>
>>> At the same time, the community has approved the move too. Here is the
>>> discussion GitHub issue,
>>> https://github.com/analysys/EasyScheduler/issues/638
>>>
>>>
 - I notice the source files header already state “Licensed to the
 Apache Software Foundation”, I assume this is not actually the case. It
 looks to me that the headers may of been replaced, that may make IP
 provenance / clearance harder. A quick glance shows a number of 3rd party
 pieces of code that are likely to be in a releases, inckudeing this not
 listed in your dependancies. Is the project aware of this and what’s
 required here?

>>>
>>> I will check w/ them and get back later.
>>> For dependency list, they replace w/ a short version in the proposal,
>>> considering before the first incubator release, they plan to remove some
>>> dependency libs.
>>> Do we need the whole list? Including every dependency. We used to have
>>> that before.
>>>
>>>
 - It looks like the community mostly discusses things on instant
 messaging are they prepared to move the important bits of that conversation
 over to an ASF mailing list?

>>>
>>> Yes. I have told them this is required, and they will do that.
>>>
>>>

 Thanks,
 Justin

 1. http://easyscheduler.io
 2. https://www.analysys.cn
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org


>>>
>>> Sheng Wu 吴晟
>>>
>>> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
>>> Twitter, wusheng1108
>>>
>>

Re: [DISCUSS] EasyScheduler incubator proposal

[Sheng Wu]

Proposal name changed, new WIKI page link,
https://cwiki.apache.org/confluence/display/INCUBATOR/DolphinSchedulerProposal

Sheng Wu 吴晟

Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
Twitter, wusheng1108


Sheng Wu  于2019年8月19日周一 下午11:28写道：

> Hi Justin and Incubator
>
> Regarding the project name potential conflict risk, the EasyScheduler
> community decided to choose a new name.
> Through a public community vote[1], they are going to use
> `DolphinScheduler` as the new project name.
>
> Later, I will change the proposal and sync update w/ new link to here.
>
> Thank you.
>
>
> [1]
> https://github.com/analysys/EasyScheduler/issues/701#issuecomment-522626780
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> Twitter, wusheng1108
>
>
> Sheng Wu  于2019年8月18日周日 上午8:29写道：
>
>> Hi Justin
>>
>> Inline
>>
>> Justin Mclean  于2019年8月18日周日 上午7:25写道：
>>
>>> Hi,
>>>
>>> Thanks for your proposal, it looks good.
>>>
>>> I have a couple of questions:
>>> - Re the name, other software exists with the same name e.g. [1] (and
>>> others) Has the project considered that it may not be able to keep this
>>> name and what it would do if this was the case?
>>>
>>
>> Oh, that is new, thanks for pointing that out in first place. From my
>> perspective, it is better to rename now than later.
>>
>>
>>> - The NOTICE file refers to the The Analysys Foundation [2] what is the
>>> relation of this group to the project? Has the community agreed to want to
>>> move the project to the Apache Software Foundation? Is that documented
>>> anywhere?
>>>
>>
>> First, the Analysys is a company, not a Foundation.
>> And Yes.
>>
>> In the proposal, we have this.
>> > Source and Intellectual Property Submission Plan
>> > As soon as EasyScheduler is approved to join Apache Incubator, Analysys
>> will provide the Software Grant Agreement(SGA) and intial committers will
>> submit ICLA(s). The code is already licensed under the Apache > Software
>> License, version 2.0.
>>
>> We have got confirmation from them, SGA will be submitted by Analysys.
>> This is not documented, but from I known, they will submit the SGA soon
>> after this proposal accepted. I will make sure the SGA filed before the
>> repositories transformation.
>>
>> At the same time, the community has approved the move too. Here is the
>> discussion GitHub issue,
>> https://github.com/analysys/EasyScheduler/issues/638
>>
>>
>>> - I notice the source files header already state “Licensed to the Apache
>>> Software Foundation”, I assume this is not actually the case. It looks to
>>> me that the headers may of been replaced, that may make IP provenance /
>>> clearance harder. A quick glance shows a number of 3rd party pieces of code
>>> that are likely to be in a releases, inckudeing this not listed in your
>>> dependancies. Is the project aware of this and what’s required here?
>>>
>>
>> I will check w/ them and get back later.
>> For dependency list, they replace w/ a short version in the proposal,
>> considering before the first incubator release, they plan to remove some
>> dependency libs.
>> Do we need the whole list? Including every dependency. We used to have
>> that before.
>>
>>
>>> - It looks like the community mostly discusses things on instant
>>> messaging are they prepared to move the important bits of that conversation
>>> over to an ASF mailing list?
>>>
>>
>> Yes. I have told them this is required, and they will do that.
>>
>>
>>>
>>> Thanks,
>>> Justin
>>>
>>> 1. http://easyscheduler.io
>>> 2. https://www.analysys.cn
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>
>> Sheng Wu 吴晟
>>
>> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
>> Twitter, wusheng1108
>>
>

Re: [DISCUSS] EasyScheduler incubator proposal

[Sheng Wu]

Hi Justin and Incubator

Regarding the project name potential conflict risk, the EasyScheduler
community decided to choose a new name.
Through a public community vote[1], they are going to use
`DolphinScheduler` as the new project name.

Later, I will change the proposal and sync update w/ new link to here.

Thank you.


[1]
https://github.com/analysys/EasyScheduler/issues/701#issuecomment-522626780

Sheng Wu 吴晟

Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
Twitter, wusheng1108


Sheng Wu  于2019年8月18日周日 上午8:29写道：

> Hi Justin
>
> Inline
>
> Justin Mclean  于2019年8月18日周日 上午7:25写道：
>
>> Hi,
>>
>> Thanks for your proposal, it looks good.
>>
>> I have a couple of questions:
>> - Re the name, other software exists with the same name e.g. [1] (and
>> others) Has the project considered that it may not be able to keep this
>> name and what it would do if this was the case?
>>
>
> Oh, that is new, thanks for pointing that out in first place. From my
> perspective, it is better to rename now than later.
>
>
>> - The NOTICE file refers to the The Analysys Foundation [2] what is the
>> relation of this group to the project? Has the community agreed to want to
>> move the project to the Apache Software Foundation? Is that documented
>> anywhere?
>>
>
> First, the Analysys is a company, not a Foundation.
> And Yes.
>
> In the proposal, we have this.
> > Source and Intellectual Property Submission Plan
> > As soon as EasyScheduler is approved to join Apache Incubator, Analysys
> will provide the Software Grant Agreement(SGA) and intial committers will
> submit ICLA(s). The code is already licensed under the Apache > Software
> License, version 2.0.
>
> We have got confirmation from them, SGA will be submitted by Analysys.
> This is not documented, but from I known, they will submit the SGA soon
> after this proposal accepted. I will make sure the SGA filed before the
> repositories transformation.
>
> At the same time, the community has approved the move too. Here is the
> discussion GitHub issue,
> https://github.com/analysys/EasyScheduler/issues/638
>
>
>> - I notice the source files header already state “Licensed to the Apache
>> Software Foundation”, I assume this is not actually the case. It looks to
>> me that the headers may of been replaced, that may make IP provenance /
>> clearance harder. A quick glance shows a number of 3rd party pieces of code
>> that are likely to be in a releases, inckudeing this not listed in your
>> dependancies. Is the project aware of this and what’s required here?
>>
>
> I will check w/ them and get back later.
> For dependency list, they replace w/ a short version in the proposal,
> considering before the first incubator release, they plan to remove some
> dependency libs.
> Do we need the whole list? Including every dependency. We used to have
> that before.
>
>
>> - It looks like the community mostly discusses things on instant
>> messaging are they prepared to move the important bits of that conversation
>> over to an ASF mailing list?
>>
>
> Yes. I have told them this is required, and they will do that.
>
>
>>
>> Thanks,
>> Justin
>>
>> 1. http://easyscheduler.io
>> 2. https://www.analysys.cn
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> Twitter, wusheng1108
>

Re: [DISCUSS] EasyScheduler incubator proposal

[William Guo]

Great to hear EasyScheduler for incubation.
Look forward to learning how will it solve DAG issue.



Thanks,
William Guo

On Mon, Aug 19, 2019 at 7:58 AM Dave Fisher  wrote:

> Hi Sheng Wu,
>
> https://whimsy.apache.org/roster/committer/djkevincr
>
> You are correct. My mistake, I recall he asked several months ago.
>
> Regards,
> Dave
>
> > On Aug 18, 2019, at 4:51 PM, Sheng Wu  wrote:
> >
> > Hi Dave
> >
> > Before you did add Kevin into the mentor list, I have checked,
> > according to ASF Committer list[1], he has been a member of IPMC
> >
> >
> > [1] http://people.apache.org/phonebook.html?uid=djkevincr
> >
> > Sheng Wu 吴晟
> >
> > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> > Twitter, wusheng1108
> >
> >
> > Dave Fisher  于2019年8月19日周一 上午5:08写道：
> >
> >> Kevin,
> >>
> >> Since you a member all you need do to join the IPMC is to send an email
> to
> >> private@ requesting to be added.
> >>
> >> Regards,
> >> Dave
> >>
> >>> On Aug 18, 2019, at 3:42 AM, Kevin Ratnasekera 
> >> wrote:
> >>>
> >>> Hi Sheng,
> >>>
> >>> If there is space and help is needed, I am interested in mentoring the
> >> project. Even though, I am new to Apache Incubator, I am a long term
> >> contributor to Apache, member of ASF, as well as chair for one of Big
> data
> >> projects for Apache.
> >>>
> >>> Regards
> >>> Kevin
> >>>
> >>> On 2019/08/18 09:04:09, Sheng Wu  wrote:
>  Hi Justin
> 
>  Inline about License header thing.
> 
>  Sheng Wu  于2019年8月18日周日 上午8:29写道：
> 
> > Hi Justin
> >
> > Inline
> >
> > Justin Mclean  于2019年8月18日周日 上午7:25写道：
> >
> >> Hi,
> >>
> >> Thanks for your proposal, it looks good.
> >>
> >> I have a couple of questions:
> >> - Re the name, other software exists with the same name e.g. [1]
> (and
> >> others) Has the project considered that it may not be able to keep
> >> this
> >> name and what it would do if this was the case?
> >>
> >
> > Oh, that is new, thanks for pointing that out in first place. From my
> > perspective, it is better to rename now than later.
> >
> >
> >> - The NOTICE file refers to the The Analysys Foundation [2] what is
> >> the
> >> relation of this group to the project? Has the community agreed to
> >> want to
> >> move the project to the Apache Software Foundation? Is that
> documented
> >> anywhere?
> >>
> >
> > First, the Analysys is a company, not a Foundation.
> > And Yes.
> >
> > In the proposal, we have this.
> >> Source and Intellectual Property Submission Plan
> >> As soon as EasyScheduler is approved to join Apache Incubator,
> >> Analysys
> > will provide the Software Grant Agreement(SGA) and intial committers
> >> will
> > submit ICLA(s). The code is already licensed under the Apache >
> >> Software
> > License, version 2.0.
> >
> > We have got confirmation from them, SGA will be submitted by
> Analysys.
> > This is not documented, but from I known, they will submit the SGA
> soon
> > after this proposal accepted. I will make sure the SGA filed before
> the
> > repositories transformation.
> >
> > At the same time, the community has approved the move too. Here is
> the
> > discussion GitHub issue,
> > https://github.com/analysys/EasyScheduler/issues/638
> >
> >
> >> - I notice the source files header already state “Licensed to the
> >> Apache
> >> Software Foundation”, I assume this is not actually the case. It
> >> looks to
> >> me that the headers may of been replaced, that may make IP
> provenance
> >> /
> >> clearance harder. A quick glance shows a number of 3rd party pieces
> >> of code
> >> that are likely to be in a releases, inckudeing this not listed in
> >> your
> >> dependancies. Is the project aware of this and what’s required here?
> >>
> >
> > I will check w/ them and get back later.
> >
> 
>  Update. They provided feedback about this.
>  They are using the wrong Apache 2.0 header, from my understanding, the
> >> repo
>  belongs to Analysis Company GitHub org[1] clearly, there is no IP
> >> concern
>  for the donation.
> 
>  A question.
>  Before the proposal vote, do we need them to change it to right Apache
> >> 2.0
>  header? I mean, change it to, such as `Licensed to Analysis Inc.`?
> 
>  [1] https://github.com/analysys
> 
> 
> 
> > For dependency list, they replace w/ a short version in the proposal,
> > considering before the first incubator release, they plan to remove
> >> some
> > dependency libs.
> > Do we need the whole list? Including every dependency. We used to
> have
> > that before.
> >
> >
> >> - It looks like the community mostly discusses things on instant
> >> messaging are they prepared to move the important bits of that
> >> conversation
> >> over to an ASF mailing list?
> >>

Re: [DISCUSS] EasyScheduler incubator proposal

[Dave Fisher]

Hi Sheng Wu,

https://whimsy.apache.org/roster/committer/djkevincr

You are correct. My mistake, I recall he asked several months ago.

Regards,
Dave

> On Aug 18, 2019, at 4:51 PM, Sheng Wu  wrote:
> 
> Hi Dave
> 
> Before you did add Kevin into the mentor list, I have checked,
> according to ASF Committer list[1], he has been a member of IPMC
> 
> 
> [1] http://people.apache.org/phonebook.html?uid=djkevincr
> 
> Sheng Wu 吴晟
> 
> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> Twitter, wusheng1108
> 
> 
> Dave Fisher  于2019年8月19日周一 上午5:08写道：
> 
>> Kevin,
>> 
>> Since you a member all you need do to join the IPMC is to send an email to
>> private@ requesting to be added.
>> 
>> Regards,
>> Dave
>> 
>>> On Aug 18, 2019, at 3:42 AM, Kevin Ratnasekera 
>> wrote:
>>> 
>>> Hi Sheng,
>>> 
>>> If there is space and help is needed, I am interested in mentoring the
>> project. Even though, I am new to Apache Incubator, I am a long term
>> contributor to Apache, member of ASF, as well as chair for one of Big data
>> projects for Apache.
>>> 
>>> Regards
>>> Kevin
>>> 
>>> On 2019/08/18 09:04:09, Sheng Wu  wrote:
 Hi Justin
 
 Inline about License header thing.
 
 Sheng Wu  于2019年8月18日周日 上午8:29写道：
 
> Hi Justin
> 
> Inline
> 
> Justin Mclean  于2019年8月18日周日 上午7:25写道：
> 
>> Hi,
>> 
>> Thanks for your proposal, it looks good.
>> 
>> I have a couple of questions:
>> - Re the name, other software exists with the same name e.g. [1] (and
>> others) Has the project considered that it may not be able to keep
>> this
>> name and what it would do if this was the case?
>> 
> 
> Oh, that is new, thanks for pointing that out in first place. From my
> perspective, it is better to rename now than later.
> 
> 
>> - The NOTICE file refers to the The Analysys Foundation [2] what is
>> the
>> relation of this group to the project? Has the community agreed to
>> want to
>> move the project to the Apache Software Foundation? Is that documented
>> anywhere?
>> 
> 
> First, the Analysys is a company, not a Foundation.
> And Yes.
> 
> In the proposal, we have this.
>> Source and Intellectual Property Submission Plan
>> As soon as EasyScheduler is approved to join Apache Incubator,
>> Analysys
> will provide the Software Grant Agreement(SGA) and intial committers
>> will
> submit ICLA(s). The code is already licensed under the Apache >
>> Software
> License, version 2.0.
> 
> We have got confirmation from them, SGA will be submitted by Analysys.
> This is not documented, but from I known, they will submit the SGA soon
> after this proposal accepted. I will make sure the SGA filed before the
> repositories transformation.
> 
> At the same time, the community has approved the move too. Here is the
> discussion GitHub issue,
> https://github.com/analysys/EasyScheduler/issues/638
> 
> 
>> - I notice the source files header already state “Licensed to the
>> Apache
>> Software Foundation”, I assume this is not actually the case. It
>> looks to
>> me that the headers may of been replaced, that may make IP provenance
>> /
>> clearance harder. A quick glance shows a number of 3rd party pieces
>> of code
>> that are likely to be in a releases, inckudeing this not listed in
>> your
>> dependancies. Is the project aware of this and what’s required here?
>> 
> 
> I will check w/ them and get back later.
> 
 
 Update. They provided feedback about this.
 They are using the wrong Apache 2.0 header, from my understanding, the
>> repo
 belongs to Analysis Company GitHub org[1] clearly, there is no IP
>> concern
 for the donation.
 
 A question.
 Before the proposal vote, do we need them to change it to right Apache
>> 2.0
 header? I mean, change it to, such as `Licensed to Analysis Inc.`?
 
 [1] https://github.com/analysys
 
 
 
> For dependency list, they replace w/ a short version in the proposal,
> considering before the first incubator release, they plan to remove
>> some
> dependency libs.
> Do we need the whole list? Including every dependency. We used to have
> that before.
> 
> 
>> - It looks like the community mostly discusses things on instant
>> messaging are they prepared to move the important bits of that
>> conversation
>> over to an ASF mailing list?
>> 
> 
> Yes. I have told them this is required, and they will do that.
> 
> 
>> 
>> Thanks,
>> Justin
>> 
>> 1. http://easyscheduler.io
>> 2. https://www.analysys.cn
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
>

Re: [DISCUSS] EasyScheduler incubator proposal

[Sheng Wu]

Hi Dave

Before you did add Kevin into the mentor list, I have checked,
according to ASF Committer list[1], he has been a member of IPMC


[1] http://people.apache.org/phonebook.html?uid=djkevincr

Sheng Wu 吴晟

Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
Twitter, wusheng1108


Dave Fisher  于2019年8月19日周一 上午5:08写道：

> Kevin,
>
> Since you a member all you need do to join the IPMC is to send an email to
> private@ requesting to be added.
>
> Regards,
> Dave
>
> > On Aug 18, 2019, at 3:42 AM, Kevin Ratnasekera 
> wrote:
> >
> > Hi Sheng,
> >
> > If there is space and help is needed, I am interested in mentoring the
> project. Even though, I am new to Apache Incubator, I am a long term
> contributor to Apache, member of ASF, as well as chair for one of Big data
> projects for Apache.
> >
> > Regards
> > Kevin
> >
> > On 2019/08/18 09:04:09, Sheng Wu  wrote:
> >> Hi Justin
> >>
> >> Inline about License header thing.
> >>
> >> Sheng Wu  于2019年8月18日周日 上午8:29写道：
> >>
> >>> Hi Justin
> >>>
> >>> Inline
> >>>
> >>> Justin Mclean  于2019年8月18日周日 上午7:25写道：
> >>>
>  Hi,
> 
>  Thanks for your proposal, it looks good.
> 
>  I have a couple of questions:
>  - Re the name, other software exists with the same name e.g. [1] (and
>  others) Has the project considered that it may not be able to keep
> this
>  name and what it would do if this was the case?
> 
> >>>
> >>> Oh, that is new, thanks for pointing that out in first place. From my
> >>> perspective, it is better to rename now than later.
> >>>
> >>>
>  - The NOTICE file refers to the The Analysys Foundation [2] what is
> the
>  relation of this group to the project? Has the community agreed to
> want to
>  move the project to the Apache Software Foundation? Is that documented
>  anywhere?
> 
> >>>
> >>> First, the Analysys is a company, not a Foundation.
> >>> And Yes.
> >>>
> >>> In the proposal, we have this.
>  Source and Intellectual Property Submission Plan
>  As soon as EasyScheduler is approved to join Apache Incubator,
> Analysys
> >>> will provide the Software Grant Agreement(SGA) and intial committers
> will
> >>> submit ICLA(s). The code is already licensed under the Apache >
> Software
> >>> License, version 2.0.
> >>>
> >>> We have got confirmation from them, SGA will be submitted by Analysys.
> >>> This is not documented, but from I known, they will submit the SGA soon
> >>> after this proposal accepted. I will make sure the SGA filed before the
> >>> repositories transformation.
> >>>
> >>> At the same time, the community has approved the move too. Here is the
> >>> discussion GitHub issue,
> >>> https://github.com/analysys/EasyScheduler/issues/638
> >>>
> >>>
>  - I notice the source files header already state “Licensed to the
> Apache
>  Software Foundation”, I assume this is not actually the case. It
> looks to
>  me that the headers may of been replaced, that may make IP provenance
> /
>  clearance harder. A quick glance shows a number of 3rd party pieces
> of code
>  that are likely to be in a releases, inckudeing this not listed in
> your
>  dependancies. Is the project aware of this and what’s required here?
> 
> >>>
> >>> I will check w/ them and get back later.
> >>>
> >>
> >> Update. They provided feedback about this.
> >> They are using the wrong Apache 2.0 header, from my understanding, the
> repo
> >> belongs to Analysis Company GitHub org[1] clearly, there is no IP
> concern
> >> for the donation.
> >>
> >> A question.
> >> Before the proposal vote, do we need them to change it to right Apache
> 2.0
> >> header? I mean, change it to, such as `Licensed to Analysis Inc.`?
> >>
> >> [1] https://github.com/analysys
> >>
> >>
> >>
> >>> For dependency list, they replace w/ a short version in the proposal,
> >>> considering before the first incubator release, they plan to remove
> some
> >>> dependency libs.
> >>> Do we need the whole list? Including every dependency. We used to have
> >>> that before.
> >>>
> >>>
>  - It looks like the community mostly discusses things on instant
>  messaging are they prepared to move the important bits of that
> conversation
>  over to an ASF mailing list?
> 
> >>>
> >>> Yes. I have told them this is required, and they will do that.
> >>>
> >>>
> 
>  Thanks,
>  Justin
> 
>  1. http://easyscheduler.io
>  2. https://www.analysys.cn
>  -
>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>  For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 
> >>>
> >>> Sheng Wu 吴晟
> >>>
> >>> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> >>> Twitter, wusheng1108
> >>>
> >>
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional command

Re: [DISCUSS] EasyScheduler incubator proposal

[Dave Fisher]

Kevin,

Since you a member all you need do to join the IPMC is to send an email to 
private@ requesting to be added.

Regards,
Dave

> On Aug 18, 2019, at 3:42 AM, Kevin Ratnasekera  wrote:
> 
> Hi Sheng,
> 
> If there is space and help is needed, I am interested in mentoring the 
> project. Even though, I am new to Apache Incubator, I am a long term 
> contributor to Apache, member of ASF, as well as chair for one of Big data 
> projects for Apache.
> 
> Regards
> Kevin
> 
> On 2019/08/18 09:04:09, Sheng Wu  wrote: 
>> Hi Justin
>> 
>> Inline about License header thing.
>> 
>> Sheng Wu  于2019年8月18日周日 上午8:29写道：
>> 
>>> Hi Justin
>>> 
>>> Inline
>>> 
>>> Justin Mclean  于2019年8月18日周日 上午7:25写道：
>>> 
 Hi,
 
 Thanks for your proposal, it looks good.
 
 I have a couple of questions:
 - Re the name, other software exists with the same name e.g. [1] (and
 others) Has the project considered that it may not be able to keep this
 name and what it would do if this was the case?
 
>>> 
>>> Oh, that is new, thanks for pointing that out in first place. From my
>>> perspective, it is better to rename now than later.
>>> 
>>> 
 - The NOTICE file refers to the The Analysys Foundation [2] what is the
 relation of this group to the project? Has the community agreed to want to
 move the project to the Apache Software Foundation? Is that documented
 anywhere?
 
>>> 
>>> First, the Analysys is a company, not a Foundation.
>>> And Yes.
>>> 
>>> In the proposal, we have this.
 Source and Intellectual Property Submission Plan
 As soon as EasyScheduler is approved to join Apache Incubator, Analysys
>>> will provide the Software Grant Agreement(SGA) and intial committers will
>>> submit ICLA(s). The code is already licensed under the Apache > Software
>>> License, version 2.0.
>>> 
>>> We have got confirmation from them, SGA will be submitted by Analysys.
>>> This is not documented, but from I known, they will submit the SGA soon
>>> after this proposal accepted. I will make sure the SGA filed before the
>>> repositories transformation.
>>> 
>>> At the same time, the community has approved the move too. Here is the
>>> discussion GitHub issue,
>>> https://github.com/analysys/EasyScheduler/issues/638
>>> 
>>> 
 - I notice the source files header already state “Licensed to the Apache
 Software Foundation”, I assume this is not actually the case. It looks to
 me that the headers may of been replaced, that may make IP provenance /
 clearance harder. A quick glance shows a number of 3rd party pieces of code
 that are likely to be in a releases, inckudeing this not listed in your
 dependancies. Is the project aware of this and what’s required here?
 
>>> 
>>> I will check w/ them and get back later.
>>> 
>> 
>> Update. They provided feedback about this.
>> They are using the wrong Apache 2.0 header, from my understanding, the repo
>> belongs to Analysis Company GitHub org[1] clearly, there is no IP concern
>> for the donation.
>> 
>> A question.
>> Before the proposal vote, do we need them to change it to right Apache 2.0
>> header? I mean, change it to, such as `Licensed to Analysis Inc.`?
>> 
>> [1] https://github.com/analysys
>> 
>> 
>> 
>>> For dependency list, they replace w/ a short version in the proposal,
>>> considering before the first incubator release, they plan to remove some
>>> dependency libs.
>>> Do we need the whole list? Including every dependency. We used to have
>>> that before.
>>> 
>>> 
 - It looks like the community mostly discusses things on instant
 messaging are they prepared to move the important bits of that conversation
 over to an ASF mailing list?
 
>>> 
>>> Yes. I have told them this is required, and they will do that.
>>> 
>>> 
 
 Thanks,
 Justin
 
 1. http://easyscheduler.io
 2. https://www.analysys.cn
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>>> 
>>> Sheng Wu 吴晟
>>> 
>>> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
>>> Twitter, wusheng1108
>>> 
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [DISCUSS] EasyScheduler incubator proposal

[Sheng Wu]

Hi Kevin

Welcome, we have spaces always :)
I just added you into the proposal.

Sheng Wu 吴晟

Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
Twitter, wusheng1108


Kevin Ratnasekera  于2019年8月18日周日 下午6:43写道：

> Hi Sheng,
>
> If there is space and help is needed, I am interested in mentoring the
> project. Even though, I am new to Apache Incubator, I am a long term
> contributor to Apache, member of ASF, as well as chair for one of Big data
> projects for Apache.
>
> Regards
> Kevin
>
> On 2019/08/18 09:04:09, Sheng Wu  wrote:
> > Hi Justin
> >
> > Inline about License header thing.
> >
> > Sheng Wu  于2019年8月18日周日 上午8:29写道：
> >
> > > Hi Justin
> > >
> > > Inline
> > >
> > > Justin Mclean  于2019年8月18日周日 上午7:25写道：
> > >
> > >> Hi,
> > >>
> > >> Thanks for your proposal, it looks good.
> > >>
> > >> I have a couple of questions:
> > >> - Re the name, other software exists with the same name e.g. [1] (and
> > >> others) Has the project considered that it may not be able to keep
> this
> > >> name and what it would do if this was the case?
> > >>
> > >
> > > Oh, that is new, thanks for pointing that out in first place. From my
> > > perspective, it is better to rename now than later.
> > >
> > >
> > >> - The NOTICE file refers to the The Analysys Foundation [2] what is
> the
> > >> relation of this group to the project? Has the community agreed to
> want to
> > >> move the project to the Apache Software Foundation? Is that documented
> > >> anywhere?
> > >>
> > >
> > > First, the Analysys is a company, not a Foundation.
> > > And Yes.
> > >
> > > In the proposal, we have this.
> > > > Source and Intellectual Property Submission Plan
> > > > As soon as EasyScheduler is approved to join Apache Incubator,
> Analysys
> > > will provide the Software Grant Agreement(SGA) and intial committers
> will
> > > submit ICLA(s). The code is already licensed under the Apache >
> Software
> > > License, version 2.0.
> > >
> > > We have got confirmation from them, SGA will be submitted by Analysys.
> > > This is not documented, but from I known, they will submit the SGA soon
> > > after this proposal accepted. I will make sure the SGA filed before the
> > > repositories transformation.
> > >
> > > At the same time, the community has approved the move too. Here is the
> > > discussion GitHub issue,
> > > https://github.com/analysys/EasyScheduler/issues/638
> > >
> > >
> > >> - I notice the source files header already state “Licensed to the
> Apache
> > >> Software Foundation”, I assume this is not actually the case. It
> looks to
> > >> me that the headers may of been replaced, that may make IP provenance
> /
> > >> clearance harder. A quick glance shows a number of 3rd party pieces
> of code
> > >> that are likely to be in a releases, inckudeing this not listed in
> your
> > >> dependancies. Is the project aware of this and what’s required here?
> > >>
> > >
> > > I will check w/ them and get back later.
> > >
> >
> > Update. They provided feedback about this.
> > They are using the wrong Apache 2.0 header, from my understanding, the
> repo
> > belongs to Analysis Company GitHub org[1] clearly, there is no IP concern
> > for the donation.
> >
> > A question.
> > Before the proposal vote, do we need them to change it to right Apache
> 2.0
> > header? I mean, change it to, such as `Licensed to Analysis Inc.`?
> >
> > [1] https://github.com/analysys
> >
> >
> >
> > > For dependency list, they replace w/ a short version in the proposal,
> > > considering before the first incubator release, they plan to remove
> some
> > > dependency libs.
> > > Do we need the whole list? Including every dependency. We used to have
> > > that before.
> > >
> > >
> > >> - It looks like the community mostly discusses things on instant
> > >> messaging are they prepared to move the important bits of that
> conversation
> > >> over to an ASF mailing list?
> > >>
> > >
> > > Yes. I have told them this is required, and they will do that.
> > >
> > >
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> > >> 1. http://easyscheduler.io
> > >> 2. https://www.analysys.cn
> > >> -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>
> > >>
> > >
> > > Sheng Wu 吴晟
> > >
> > > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> > > Twitter, wusheng1108
> > >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] EasyScheduler incubator proposal

[Kevin Ratnasekera]

Hi Sheng,

If there is space and help is needed, I am interested in mentoring the project. 
Even though, I am new to Apache Incubator, I am a long term contributor to 
Apache, member of ASF, as well as chair for one of Big data projects for Apache.

Regards
Kevin

On 2019/08/18 09:04:09, Sheng Wu  wrote: 
> Hi Justin
> 
> Inline about License header thing.
> 
> Sheng Wu  于2019年8月18日周日 上午8:29写道：
> 
> > Hi Justin
> >
> > Inline
> >
> > Justin Mclean  于2019年8月18日周日 上午7:25写道：
> >
> >> Hi,
> >>
> >> Thanks for your proposal, it looks good.
> >>
> >> I have a couple of questions:
> >> - Re the name, other software exists with the same name e.g. [1] (and
> >> others) Has the project considered that it may not be able to keep this
> >> name and what it would do if this was the case?
> >>
> >
> > Oh, that is new, thanks for pointing that out in first place. From my
> > perspective, it is better to rename now than later.
> >
> >
> >> - The NOTICE file refers to the The Analysys Foundation [2] what is the
> >> relation of this group to the project? Has the community agreed to want to
> >> move the project to the Apache Software Foundation? Is that documented
> >> anywhere?
> >>
> >
> > First, the Analysys is a company, not a Foundation.
> > And Yes.
> >
> > In the proposal, we have this.
> > > Source and Intellectual Property Submission Plan
> > > As soon as EasyScheduler is approved to join Apache Incubator, Analysys
> > will provide the Software Grant Agreement(SGA) and intial committers will
> > submit ICLA(s). The code is already licensed under the Apache > Software
> > License, version 2.0.
> >
> > We have got confirmation from them, SGA will be submitted by Analysys.
> > This is not documented, but from I known, they will submit the SGA soon
> > after this proposal accepted. I will make sure the SGA filed before the
> > repositories transformation.
> >
> > At the same time, the community has approved the move too. Here is the
> > discussion GitHub issue,
> > https://github.com/analysys/EasyScheduler/issues/638
> >
> >
> >> - I notice the source files header already state “Licensed to the Apache
> >> Software Foundation”, I assume this is not actually the case. It looks to
> >> me that the headers may of been replaced, that may make IP provenance /
> >> clearance harder. A quick glance shows a number of 3rd party pieces of code
> >> that are likely to be in a releases, inckudeing this not listed in your
> >> dependancies. Is the project aware of this and what’s required here?
> >>
> >
> > I will check w/ them and get back later.
> >
> 
> Update. They provided feedback about this.
> They are using the wrong Apache 2.0 header, from my understanding, the repo
> belongs to Analysis Company GitHub org[1] clearly, there is no IP concern
> for the donation.
> 
> A question.
> Before the proposal vote, do we need them to change it to right Apache 2.0
> header? I mean, change it to, such as `Licensed to Analysis Inc.`?
> 
> [1] https://github.com/analysys
> 
> 
> 
> > For dependency list, they replace w/ a short version in the proposal,
> > considering before the first incubator release, they plan to remove some
> > dependency libs.
> > Do we need the whole list? Including every dependency. We used to have
> > that before.
> >
> >
> >> - It looks like the community mostly discusses things on instant
> >> messaging are they prepared to move the important bits of that conversation
> >> over to an ASF mailing list?
> >>
> >
> > Yes. I have told them this is required, and they will do that.
> >
> >
> >>
> >> Thanks,
> >> Justin
> >>
> >> 1. http://easyscheduler.io
> >> 2. https://www.analysys.cn
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
> > Sheng Wu 吴晟
> >
> > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> > Twitter, wusheng1108
> >
> 

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

Re: [DISCUSS] EasyScheduler incubator proposal

[Sheng Wu]

Hi Justin

Inline about License header thing.

Sheng Wu  于2019年8月18日周日 上午8:29写道：

> Hi Justin
>
> Inline
>
> Justin Mclean  于2019年8月18日周日 上午7:25写道：
>
>> Hi,
>>
>> Thanks for your proposal, it looks good.
>>
>> I have a couple of questions:
>> - Re the name, other software exists with the same name e.g. [1] (and
>> others) Has the project considered that it may not be able to keep this
>> name and what it would do if this was the case?
>>
>
> Oh, that is new, thanks for pointing that out in first place. From my
> perspective, it is better to rename now than later.
>
>
>> - The NOTICE file refers to the The Analysys Foundation [2] what is the
>> relation of this group to the project? Has the community agreed to want to
>> move the project to the Apache Software Foundation? Is that documented
>> anywhere?
>>
>
> First, the Analysys is a company, not a Foundation.
> And Yes.
>
> In the proposal, we have this.
> > Source and Intellectual Property Submission Plan
> > As soon as EasyScheduler is approved to join Apache Incubator, Analysys
> will provide the Software Grant Agreement(SGA) and intial committers will
> submit ICLA(s). The code is already licensed under the Apache > Software
> License, version 2.0.
>
> We have got confirmation from them, SGA will be submitted by Analysys.
> This is not documented, but from I known, they will submit the SGA soon
> after this proposal accepted. I will make sure the SGA filed before the
> repositories transformation.
>
> At the same time, the community has approved the move too. Here is the
> discussion GitHub issue,
> https://github.com/analysys/EasyScheduler/issues/638
>
>
>> - I notice the source files header already state “Licensed to the Apache
>> Software Foundation”, I assume this is not actually the case. It looks to
>> me that the headers may of been replaced, that may make IP provenance /
>> clearance harder. A quick glance shows a number of 3rd party pieces of code
>> that are likely to be in a releases, inckudeing this not listed in your
>> dependancies. Is the project aware of this and what’s required here?
>>
>
> I will check w/ them and get back later.
>

Update. They provided feedback about this.
They are using the wrong Apache 2.0 header, from my understanding, the repo
belongs to Analysis Company GitHub org[1] clearly, there is no IP concern
for the donation.

A question.
Before the proposal vote, do we need them to change it to right Apache 2.0
header? I mean, change it to, such as `Licensed to Analysis Inc.`?

[1] https://github.com/analysys



> For dependency list, they replace w/ a short version in the proposal,
> considering before the first incubator release, they plan to remove some
> dependency libs.
> Do we need the whole list? Including every dependency. We used to have
> that before.
>
>
>> - It looks like the community mostly discusses things on instant
>> messaging are they prepared to move the important bits of that conversation
>> over to an ASF mailing list?
>>
>
> Yes. I have told them this is required, and they will do that.
>
>
>>
>> Thanks,
>> Justin
>>
>> 1. http://easyscheduler.io
>> 2. https://www.analysys.cn
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> Twitter, wusheng1108
>

Re: [DISCUSS] EasyScheduler incubator proposal

[Sheng Wu]

Hi Furkan

Welcome. Added.

Sheng Wu 吴晟

Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
Twitter, wusheng1108


Furkan KAMACI  于2019年8月18日周日 上午11:24写道：

> Hi Sheng,
>
> I am interested to be a mentor of EasyScheduler!
>
> Kind Regards,
> Furkan KAMACI
>
> 18 Ağu 2019 Paz, saat 04:06 tarihinde Sheng Wu 
> şunu yazdı:
>
> > For EasyScheduler name, I am asking for the team :)
> >
> > For the dependency, yes, I know. I have done a round of dependency check
> w/
> > them. Several dependencies w/ incompatible License are going to be
> removed,
> > they have planned it.
> >
> > Thank you.
> >
> > Sheng Wu 吴晟
> >
> > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> > Twitter, wusheng1108
> >
> >
> > Justin Mclean  于2019年8月18日周日 上午8:51写道：
> >
> > > Hi,
> > >
> > > Thanks for the reply and answers.
> > >
> > > > Oh, that is new, thanks for pointing that out in first place. From my
> > > > perspective, it is better to rename now than later.
> > >
> > > I suggest you have a talk to branding / trademarks and see what they
> > > think. It may be OK to keep the name but if you did find out it needed
> to
> > > change later on, then that could be a lot of work.
> > >
> > > > Do we need the whole list? Including every dependency. We used to
> have
> > > that before.
> > >
> > > No need to list the full list, it's just to check that you look into
> this
> > > and that they no surprises down the tracks e.g. software who license
> > isn’t
> > > compatible with ALv2 is being included or is a dependancy.
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [DISCUSS] EasyScheduler incubator proposal

[Furkan KAMACI]

Hi Sheng,

I am interested to be a mentor of EasyScheduler!

Kind Regards,
Furkan KAMACI

18 Ağu 2019 Paz, saat 04:06 tarihinde Sheng Wu 
şunu yazdı:

> For EasyScheduler name, I am asking for the team :)
>
> For the dependency, yes, I know. I have done a round of dependency check w/
> them. Several dependencies w/ incompatible License are going to be removed,
> they have planned it.
>
> Thank you.
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> Twitter, wusheng1108
>
>
> Justin Mclean  于2019年8月18日周日 上午8:51写道：
>
> > Hi,
> >
> > Thanks for the reply and answers.
> >
> > > Oh, that is new, thanks for pointing that out in first place. From my
> > > perspective, it is better to rename now than later.
> >
> > I suggest you have a talk to branding / trademarks and see what they
> > think. It may be OK to keep the name but if you did find out it needed to
> > change later on, then that could be a lot of work.
> >
> > > Do we need the whole list? Including every dependency. We used to have
> > that before.
> >
> > No need to list the full list, it's just to check that you look into this
> > and that they no surprises down the tracks e.g. software who license
> isn’t
> > compatible with ALv2 is being included or is a dependancy.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] EasyScheduler incubator proposal

[Sheng Wu]

For EasyScheduler name, I am asking for the team :)

For the dependency, yes, I know. I have done a round of dependency check w/
them. Several dependencies w/ incompatible License are going to be removed,
they have planned it.

Thank you.

Sheng Wu 吴晟

Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
Twitter, wusheng1108


Justin Mclean  于2019年8月18日周日 上午8:51写道：

> Hi,
>
> Thanks for the reply and answers.
>
> > Oh, that is new, thanks for pointing that out in first place. From my
> > perspective, it is better to rename now than later.
>
> I suggest you have a talk to branding / trademarks and see what they
> think. It may be OK to keep the name but if you did find out it needed to
> change later on, then that could be a lot of work.
>
> > Do we need the whole list? Including every dependency. We used to have
> that before.
>
> No need to list the full list, it's just to check that you look into this
> and that they no surprises down the tracks e.g. software who license isn’t
> compatible with ALv2 is being included or is a dependancy.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] EasyScheduler incubator proposal

[Justin Mclean]

Hi,

Thanks for the reply and answers.

> Oh, that is new, thanks for pointing that out in first place. From my
> perspective, it is better to rename now than later.

I suggest you have a talk to branding / trademarks and see what they think. It 
may be OK to keep the name but if you did find out it needed to change later 
on, then that could be a lot of work.

> Do we need the whole list? Including every dependency. We used to have that 
> before.

No need to list the full list, it's just to check that you look into this and 
that they no surprises down the tracks e.g. software who license isn’t 
compatible with ALv2 is being included or is a dependancy.

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

Re: [DISCUSS] EasyScheduler incubator proposal

[Sheng Wu]

Hi Justin

Inline

Justin Mclean  于2019年8月18日周日 上午7:25写道：

> Hi,
>
> Thanks for your proposal, it looks good.
>
> I have a couple of questions:
> - Re the name, other software exists with the same name e.g. [1] (and
> others) Has the project considered that it may not be able to keep this
> name and what it would do if this was the case?
>

Oh, that is new, thanks for pointing that out in first place. From my
perspective, it is better to rename now than later.


> - The NOTICE file refers to the The Analysys Foundation [2] what is the
> relation of this group to the project? Has the community agreed to want to
> move the project to the Apache Software Foundation? Is that documented
> anywhere?
>

First, the Analysys is a company, not a Foundation.
And Yes.

In the proposal, we have this.
> Source and Intellectual Property Submission Plan
> As soon as EasyScheduler is approved to join Apache Incubator, Analysys
will provide the Software Grant Agreement(SGA) and intial committers will
submit ICLA(s). The code is already licensed under the Apache > Software
License, version 2.0.

We have got confirmation from them, SGA will be submitted by Analysys. This
is not documented, but from I known, they will submit the SGA soon after
this proposal accepted. I will make sure the SGA filed before the
repositories transformation.

At the same time, the community has approved the move too. Here is the
discussion GitHub issue,
https://github.com/analysys/EasyScheduler/issues/638


> - I notice the source files header already state “Licensed to the Apache
> Software Foundation”, I assume this is not actually the case. It looks to
> me that the headers may of been replaced, that may make IP provenance /
> clearance harder. A quick glance shows a number of 3rd party pieces of code
> that are likely to be in a releases, inckudeing this not listed in your
> dependancies. Is the project aware of this and what’s required here?
>

I will check w/ them and get back later.
For dependency list, they replace w/ a short version in the proposal,
considering before the first incubator release, they plan to remove some
dependency libs.
Do we need the whole list? Including every dependency. We used to have that
before.


> - It looks like the community mostly discusses things on instant messaging
> are they prepared to move the important bits of that conversation over to
> an ASF mailing list?
>

Yes. I have told them this is required, and they will do that.


>
> Thanks,
> Justin
>
> 1. http://easyscheduler.io
> 2. https://www.analysys.cn
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Sheng Wu 吴晟

Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
Twitter, wusheng1108

Re: [DISCUSS] EasyScheduler incubator proposal

[Justin Mclean]

Hi,

Thanks for your proposal, it looks good.

I have a couple of questions:
- Re the name, other software exists with the same name e.g. [1] (and others) 
Has the project considered that it may not be able to keep this name and what 
it would do if this was the case?
- The NOTICE file refers to the The Analysys Foundation [2] what is the 
relation of this group to the project? Has the community agreed to want to move 
the project to the Apache Software Foundation? Is that documented anywhere?
- I notice the source files header already state “Licensed to the Apache 
Software Foundation”, I assume this is not actually the case. It looks to me 
that the headers may of been replaced, that may make IP provenance / clearance 
harder. A quick glance shows a number of 3rd party pieces of code that are 
likely to be in a releases, inckudeing this not listed in your dependancies. Is 
the project aware of this and what’s required here?
- It looks like the community mostly discusses things on instant messaging are 
they prepared to move the important bits of that conversation over to an ASF 
mailing list?

Thanks,
Justin

1. http://easyscheduler.io
2. https://www.analysys.cn
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[DISCUSS] EasyScheduler incubator proposal

[Sheng Wu]

Hi Incubator

Please consider accepting the new project proposal.

EasyScheduler is a distributed ETL scheduling engine with powerful DAG
visualization interface. EasyScheduler focuses on solving the problem of
'complex task dependencies & triggers' in the data processing. Just like
its name, we dedicated to making the scheduling system out of the box.

Lidong Dai w/ his community team and Shaofeng Shi(IPMC) reached out to me
recently, and asked me to Champion and mentor the project.
The whole project team is willing to join the incubator, learn/follow the
Apache Way, and build widely community.
In this project, we have 3 mentors(IPMC members)
- Sheng Wu, was in the whole SkyWalking incubator journey from day 1, right
now as SkyWalking VP and PMC, also am a part of ShardingSphere PPMC
- Shaofeng Shi, Kylin PMC member
- Liang Chen, CarbonData V.P. and PMC member, was in the whole CarbonData
incubator journey from day 1.

This is my first time to be an official Champion, we are welcome other
experienced IPMC members to mentor the project.

The proposal has been posted in Incubator WIKI[1] and as following

--
Abstract

EasyScheduler is a distributed ETL scheduling engine with powerful DAG
visualization interface. EasyScheduler focuses on solving the problem of
'complex task dependencies & triggers' in data processing. Just like its
name, we dedicated to making the scheduling system out of the box.
Proposal

EasyScheduler provides many easy-to-use features to accelerate the
engineering efficiency on data ETL workflow job. We propose a new concept
of 'instance of process' and 'instance of task' to let developers to tuning
their jobs on the running state of workflow instead of changing the task's
template. Its main objectives are as follows:

   - Define the complex tasks' dependencies & triggers in a DAG graph by
   dragging and dropping.
   - Support cluster HA.
   - Support multi-tenant and parallel or serial backfilling data.
   - Support automatical failure job retry and recovery.
   - Support many data task types and process priority, task priority and
   relative task timeout alarm.

For now, EasyScheduler has a fairly huge community in China. It is also
widely adopted by many companies and organizations
 as its ETL scheduling
tool.

We believe that bringing EasyScheduler into ASF could advance development
of a much more stronger and more diverse open source community.

Analysys submits this proposal to donate EasyScheduler's source codes and
all related documentations to Apache Software Foundation. The codes are
already under Apache License Version 2.0.

   - Code base: https://www.github.com/analysys/easyscheduler
   - English Documentations: https://analysys.github.io/easyscheduler_docs
   - Chinese Documentations:
   https://analysys.github.io/easyscheduler_docs_cn

Background

We want to find a data processing tool with the following features:

   - Easy to use，developers can build a ETL process with a very simple drag
   and drop operation. not only for ETL developers，people who can't write code
   also can use this tool for ETL operation such as system adminitrator.
   - Solving the problem of "complex task dependencies" , and it can
   monitor the ETL running status.
   - Support multi-tenant.
   - Support many task types: Shell, MR, Spark, SQL (mysql, postgresql,
   hive, sparksql), Python, Sub_Process, Procedure, etc.
   - Support HA and linear scalability.

For the above reasons, we realized that no existing product met our
requirements, so we decided to develop this tool ourselves. We designed
EasyScheduler at the end of 2017. The first internal use version was
completed in May 2018. We then iterated several internal versions and the
system gradually became stabilized.

Then we open the source code of EasyScheduler on March 2019. It soon gained
lot's of ETL developers interest and stars on github.
Rationale

Many organizations (>30) (refer to Who is using EasyScheduler
 ) already benefit
from running EasyScheduler to make data process pipelines more easier. More
than 100 feature ideas
 come from
EasyScheduler community. Some 3rd-party projects also plan to integrate
with EasyScheduler through task plugin, such as Scriptis
, waterdrop
. These will strengthen the
features of EasyScheduler.
Current StatusMeritocracy

EasyScheduler was incubated at Analysys in 2017 and open sourced on GitHub
in March 2019. Once open sourced, we have been quickly adopted by multiple
organizations，EasyScheduler has contributors and users from many companies;
we have set up the Committer Team. New contributors are guided and reviewed
by existed committer members. Contributions are always welcomed and highly
valued.
Community

Now we have set development teams for EasyS