Re: [DISCUSS] YuniKorn Proposal

[Vinod Kumar Vavilapalli]

Yup, on it.

Thanks
+Vinod

> On Jan 9, 2020, at 12:42 PM, 俊平堵  wrote:
> 
> Agree. Shall we call for a vote? @Vinod Kumar Vavilapalli 
>  
> 
> Thanks,
> 
> Junping
> 
> Justin Mclean mailto:jus...@classsoftware.com>> 
> 于2020年1月9日周四 上午7:59写道：
> Hi,
> 
> I think this discussion has died down and everything has been resolved and 
> you can call for a vote.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
> 
> For additional commands, e-mail: general-h...@incubator.apache.org 
> 
> 

Re: [DISCUSS] YuniKorn Proposal

[俊平堵]

Agree. Shall we call for a vote? @Vinod Kumar Vavilapalli


Thanks,

Junping

Justin Mclean  于2020年1月9日周四 上午7:59写道：

> Hi,
>
> I think this discussion has died down and everything has been resolved and
> you can call for a vote.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] YuniKorn Proposal

[Justin Mclean]

Hi,

I think this discussion has died down and everything has been resolved and you 
can call for a vote.

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

Re: [DISCUSS] YuniKorn Proposal

[Casey]

Hi Craig,

In answer to your question:





*If Apache does incubate and graduate Yunikorn as a top level project, we
would require Cloudera to commit to recognize Yunikorn as an Apache project
in all of its materials. Otherwise, there would be confusion in the market
about whether Yunikorn was an Apache project or a Cloudera project. It
cannot be both.If Cloudera can commit to not using Yunikorn to describe its
own project once it graduates and becomes an Apache project, ok.If not, the
Apache project will need to find a new name.*
--
Cloudera can commit to using Apache YuniKorn if/when the YuniKorn project
graduates.

Thank you,
Casey
*Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts Manager
t. (949) 201-3201

NOTICE: Prepared by a member of the Cloudera legal team. This message and any
attachments may contain confidential and/or privileged information of Cloudera,
Inc. and/or its affiliates. If you have received this communication in
error, please advise the sender by reply email and immediately delete this
message and any attachments without copying, reviewing, or disclosing the
contents. Thank you for your cooperation.


On Mon, Jan 6, 2020 at 1:05 PM Wangda Tan  wrote:

> + @Casey  to answer the question since Casey may not
> subscribe to incubator emails.
>
> Thanks
>
> On Sat, Dec 21, 2019 at 7:01 PM Craig Russell 
> wrote:
>
>> Hi Casey,
>>
>> > On Dec 20, 2019, at 10:31 AM, Casey  wrote:
>> >
>> > Hi Folks,
>> >
>> > Cloudera does not have a trademark on YuniKorn; we do use the name in a
>> few
>> > places with a quick look.  So there's no trademark assignment needed,
>> but
>> > if there is something else you'd like us to do related to any ownership
>> > interest, please let me know.
>>
>> If Apache does incubate and graduate Yunikorn as a top level project, we
>> would require Cloudera to commit to recognize Yunikorn as an Apache project
>> in all of its materials.
>>
>> Otherwise, there would be confusion in the market about whether Yunikorn
>> was an Apache project or a Cloudera project. It cannot be both.
>>
>> If Cloudera can commit to not using Yunikorn to describe its own project
>> once it graduates and becomes an Apache project, ok.
>>
>> If not, the Apache project will need to find a new name.
>>
>> Regards
>> Craig
>> >
>> > Regards,
>> > Casey
>> >
>> > *Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts
>> Manager
>> > t. (949) 201-3201
>> >
>> > NOTICE: Prepared by a member of the Cloudera legal team. This message
>> and any
>> > attachments may contain confidential and/or privileged information of
>> Cloudera,
>> > Inc. and/or its affiliates. If you have received this communication in
>> > error, please advise the sender by reply email and immediately delete
>> this
>> > message and any attachments without copying, reviewing, or disclosing
>> the
>> > contents. Thank you for your cooperation.
>> >
>> >
>> > On Fri, Dec 20, 2019 at 1:22 PM Wangda Tan  wrote:
>> >
>> >> Added Casey Valk from Cloudera legal team to the thread to answer the
>> >> question regarding trademark of YuniKorn.
>> >>
>> >> Best,
>> >> Wangda
>> >>
>> >> On Tue, Dec 17, 2019 at 10:56 PM Wangda Tan  wrote:
>> >>
>> >>> Hi Justin/Craig,
>> >>>
>> >>> Thanks for sharing these information, very helpful.
>> >>>
>> >>> I think Cloudera doesn’t own the trademark and name. Checking with
>> >>> cloudera legal now and will keep the thread posted.
>> >>>
>> >>> Thanks
>> >>>
>> >>> On Tue, Dec 17, 2019 at 2:34 PM Justin Mclean <
>> jus...@classsoftware.com>
>> >>> wrote:
>> >>>
>>  Hi,
>> 
>>  Again thanks for your replies.
>> 
>> > *"The initial committers are from several relevant Apache projects
>> who
>>  are
>> > interested in YuniKorn and committed to giving guidance, suggestions
>>  to the
>> > project, help to grow the community; and if possible, participants
>> in
>>  code
>> > development."*
>> >
>> > They're aware of the PPMC requirements, I don't think there's any
>>  surprise
>> > to proposed initial committers.
>> 
>>  That great. A long way off but just be aware that if these people are
>>  listed on the graduation proposal for PMC members and they have not
>> been
>>  active in the project that may delay graduation.
>> 
>> > We have already got SGA (Software Grant Agreement) from Cloudera,
>> I'm
>>  not
>> > sure if we need to attach the SGA now, before vote or so. Is there
>> any
>> > additional documentation needed apart from SGA.
>> 
>>  No you don’t need to submit an SGA before voting on the proposal,
>> what
>>  we need is a clear indication that your name is unlikely to change
>> and that
>>  it’s Cloudera intent to hand over rights to the name.The name would
>> not
>>  need to be transferred until graduation.
>> 
>>  Thanks,
>>  Justin
>> >>>
>> >>>
>>
>> Craig L Russell
>> c...@apache.org
>>
>>

Re: [DISCUSS] YuniKorn Proposal

[Wangda Tan]

+ @Casey  to answer the question since Casey may not
subscribe to incubator emails.

Thanks

On Sat, Dec 21, 2019 at 7:01 PM Craig Russell  wrote:

> Hi Casey,
>
> > On Dec 20, 2019, at 10:31 AM, Casey  wrote:
> >
> > Hi Folks,
> >
> > Cloudera does not have a trademark on YuniKorn; we do use the name in a
> few
> > places with a quick look.  So there's no trademark assignment needed, but
> > if there is something else you'd like us to do related to any ownership
> > interest, please let me know.
>
> If Apache does incubate and graduate Yunikorn as a top level project, we
> would require Cloudera to commit to recognize Yunikorn as an Apache project
> in all of its materials.
>
> Otherwise, there would be confusion in the market about whether Yunikorn
> was an Apache project or a Cloudera project. It cannot be both.
>
> If Cloudera can commit to not using Yunikorn to describe its own project
> once it graduates and becomes an Apache project, ok.
>
> If not, the Apache project will need to find a new name.
>
> Regards
> Craig
> >
> > Regards,
> > Casey
> >
> > *Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts Manager
> > t. (949) 201-3201
> >
> > NOTICE: Prepared by a member of the Cloudera legal team. This message
> and any
> > attachments may contain confidential and/or privileged information of
> Cloudera,
> > Inc. and/or its affiliates. If you have received this communication in
> > error, please advise the sender by reply email and immediately delete
> this
> > message and any attachments without copying, reviewing, or disclosing the
> > contents. Thank you for your cooperation.
> >
> >
> > On Fri, Dec 20, 2019 at 1:22 PM Wangda Tan  wrote:
> >
> >> Added Casey Valk from Cloudera legal team to the thread to answer the
> >> question regarding trademark of YuniKorn.
> >>
> >> Best,
> >> Wangda
> >>
> >> On Tue, Dec 17, 2019 at 10:56 PM Wangda Tan  wrote:
> >>
> >>> Hi Justin/Craig,
> >>>
> >>> Thanks for sharing these information, very helpful.
> >>>
> >>> I think Cloudera doesn’t own the trademark and name. Checking with
> >>> cloudera legal now and will keep the thread posted.
> >>>
> >>> Thanks
> >>>
> >>> On Tue, Dec 17, 2019 at 2:34 PM Justin Mclean <
> jus...@classsoftware.com>
> >>> wrote:
> >>>
>  Hi,
> 
>  Again thanks for your replies.
> 
> > *"The initial committers are from several relevant Apache projects
> who
>  are
> > interested in YuniKorn and committed to giving guidance, suggestions
>  to the
> > project, help to grow the community; and if possible, participants in
>  code
> > development."*
> >
> > They're aware of the PPMC requirements, I don't think there's any
>  surprise
> > to proposed initial committers.
> 
>  That great. A long way off but just be aware that if these people are
>  listed on the graduation proposal for PMC members and they have not
> been
>  active in the project that may delay graduation.
> 
> > We have already got SGA (Software Grant Agreement) from Cloudera, I'm
>  not
> > sure if we need to attach the SGA now, before vote or so. Is there
> any
> > additional documentation needed apart from SGA.
> 
>  No you don’t need to submit an SGA before voting on the proposal, what
>  we need is a clear indication that your name is unlikely to change
> and that
>  it’s Cloudera intent to hand over rights to the name.The name would
> not
>  need to be transferred until graduation.
> 
>  Thanks,
>  Justin
> >>>
> >>>
>
> Craig L Russell
> c...@apache.org
>
>

Re: [DISCUSS] YuniKorn Proposal

[Craig Russell]

Hi Casey,

> On Dec 20, 2019, at 10:31 AM, Casey  wrote:
> 
> Hi Folks,
> 
> Cloudera does not have a trademark on YuniKorn; we do use the name in a few
> places with a quick look.  So there's no trademark assignment needed, but
> if there is something else you'd like us to do related to any ownership
> interest, please let me know.

If Apache does incubate and graduate Yunikorn as a top level project, we would 
require Cloudera to commit to recognize Yunikorn as an Apache project in all of 
its materials. 

Otherwise, there would be confusion in the market about whether Yunikorn was an 
Apache project or a Cloudera project. It cannot be both.

If Cloudera can commit to not using Yunikorn to describe its own project once 
it graduates and becomes an Apache project, ok.

If not, the Apache project will need to find a new name.

Regards
Craig
> 
> Regards,
> Casey
> 
> *Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts Manager
> t. (949) 201-3201
> 
> NOTICE: Prepared by a member of the Cloudera legal team. This message and any
> attachments may contain confidential and/or privileged information of 
> Cloudera,
> Inc. and/or its affiliates. If you have received this communication in
> error, please advise the sender by reply email and immediately delete this
> message and any attachments without copying, reviewing, or disclosing the
> contents. Thank you for your cooperation.
> 
> 
> On Fri, Dec 20, 2019 at 1:22 PM Wangda Tan  wrote:
> 
>> Added Casey Valk from Cloudera legal team to the thread to answer the
>> question regarding trademark of YuniKorn.
>> 
>> Best,
>> Wangda
>> 
>> On Tue, Dec 17, 2019 at 10:56 PM Wangda Tan  wrote:
>> 
>>> Hi Justin/Craig,
>>> 
>>> Thanks for sharing these information, very helpful.
>>> 
>>> I think Cloudera doesn’t own the trademark and name. Checking with
>>> cloudera legal now and will keep the thread posted.
>>> 
>>> Thanks
>>> 
>>> On Tue, Dec 17, 2019 at 2:34 PM Justin Mclean 
>>> wrote:
>>> 
 Hi,
 
 Again thanks for your replies.
 
> *"The initial committers are from several relevant Apache projects who
 are
> interested in YuniKorn and committed to giving guidance, suggestions
 to the
> project, help to grow the community; and if possible, participants in
 code
> development."*
> 
> They're aware of the PPMC requirements, I don't think there's any
 surprise
> to proposed initial committers.
 
 That great. A long way off but just be aware that if these people are
 listed on the graduation proposal for PMC members and they have not been
 active in the project that may delay graduation.
 
> We have already got SGA (Software Grant Agreement) from Cloudera, I'm
 not
> sure if we need to attach the SGA now, before vote or so. Is there any
> additional documentation needed apart from SGA.
 
 No you don’t need to submit an SGA before voting on the proposal, what
 we need is a clear indication that your name is unlikely to change and that
 it’s Cloudera intent to hand over rights to the name.The name would not
 need to be transferred until graduation.
 
 Thanks,
 Justin
>>> 
>>> 

Craig L Russell
c...@apache.org


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

Re: [DISCUSS] YuniKorn Proposal

[Casey]

Hi Folks,

Cloudera does not have a trademark on YuniKorn; we do use the name in a few
places with a quick look.  So there's no trademark assignment needed, but
if there is something else you'd like us to do related to any ownership
interest, please let me know.

Regards,
Casey

*Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts Manager
t. (949) 201-3201

NOTICE: Prepared by a member of the Cloudera legal team. This message and any
attachments may contain confidential and/or privileged information of Cloudera,
Inc. and/or its affiliates. If you have received this communication in
error, please advise the sender by reply email and immediately delete this
message and any attachments without copying, reviewing, or disclosing the
contents. Thank you for your cooperation.


On Fri, Dec 20, 2019 at 1:22 PM Wangda Tan  wrote:

> Added Casey Valk from Cloudera legal team to the thread to answer the
> question regarding trademark of YuniKorn.
>
> Best,
> Wangda
>
> On Tue, Dec 17, 2019 at 10:56 PM Wangda Tan  wrote:
>
>> Hi Justin/Craig,
>>
>> Thanks for sharing these information, very helpful.
>>
>> I think Cloudera doesn’t own the trademark and name. Checking with
>> cloudera legal now and will keep the thread posted.
>>
>> Thanks
>>
>> On Tue, Dec 17, 2019 at 2:34 PM Justin Mclean 
>> wrote:
>>
>>> Hi,
>>>
>>> Again thanks for your replies.
>>>
>>> > *"The initial committers are from several relevant Apache projects who
>>> are
>>> > interested in YuniKorn and committed to giving guidance, suggestions
>>> to the
>>> > project, help to grow the community; and if possible, participants in
>>> code
>>> > development."*
>>> >
>>> > They're aware of the PPMC requirements, I don't think there's any
>>> surprise
>>> > to proposed initial committers.
>>>
>>> That great. A long way off but just be aware that if these people are
>>> listed on the graduation proposal for PMC members and they have not been
>>> active in the project that may delay graduation.
>>>
>>> > We have already got SGA (Software Grant Agreement) from Cloudera, I'm
>>> not
>>> > sure if we need to attach the SGA now, before vote or so. Is there any
>>> > additional documentation needed apart from SGA.
>>>
>>> No you don’t need to submit an SGA before voting on the proposal, what
>>> we need is a clear indication that your name is unlikely to change and that
>>> it’s Cloudera intent to hand over rights to the name.The name would not
>>> need to be transferred until graduation.
>>>
>>> Thanks,
>>> Justin
>>
>>

Re: [DISCUSS] YuniKorn Proposal

[Wangda Tan]

Added Casey Valk from Cloudera legal team to the thread to answer the
question regarding trademark of YuniKorn.

Best,
Wangda

On Tue, Dec 17, 2019 at 10:56 PM Wangda Tan  wrote:

> Hi Justin/Craig,
>
> Thanks for sharing these information, very helpful.
>
> I think Cloudera doesn’t own the trademark and name. Checking with
> cloudera legal now and will keep the thread posted.
>
> Thanks
>
> On Tue, Dec 17, 2019 at 2:34 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> Again thanks for your replies.
>>
>> > *"The initial committers are from several relevant Apache projects who
>> are
>> > interested in YuniKorn and committed to giving guidance, suggestions to
>> the
>> > project, help to grow the community; and if possible, participants in
>> code
>> > development."*
>> >
>> > They're aware of the PPMC requirements, I don't think there's any
>> surprise
>> > to proposed initial committers.
>>
>> That great. A long way off but just be aware that if these people are
>> listed on the graduation proposal for PMC members and they have not been
>> active in the project that may delay graduation.
>>
>> > We have already got SGA (Software Grant Agreement) from Cloudera, I'm
>> not
>> > sure if we need to attach the SGA now, before vote or so. Is there any
>> > additional documentation needed apart from SGA.
>>
>> No you don’t need to submit an SGA before voting on the proposal, what we
>> need is a clear indication that your name is unlikely to change and that
>> it’s Cloudera intent to hand over rights to the name.The name would not
>> need to be transferred until graduation.
>>
>> Thanks,
>> Justin
>
>

Re: [DISCUSS] YuniKorn Proposal

[Wangda Tan]

Hi Justin/Craig,

Thanks for sharing these information, very helpful.

I think Cloudera doesn’t own the trademark and name. Checking with cloudera
legal now and will keep the thread posted.

Thanks

On Tue, Dec 17, 2019 at 2:34 PM Justin Mclean 
wrote:

> Hi,
>
> Again thanks for your replies.
>
> > *"The initial committers are from several relevant Apache projects who
> are
> > interested in YuniKorn and committed to giving guidance, suggestions to
> the
> > project, help to grow the community; and if possible, participants in
> code
> > development."*
> >
> > They're aware of the PPMC requirements, I don't think there's any
> surprise
> > to proposed initial committers.
>
> That great. A long way off but just be aware that if these people are
> listed on the graduation proposal for PMC members and they have not been
> active in the project that may delay graduation.
>
> > We have already got SGA (Software Grant Agreement) from Cloudera, I'm not
> > sure if we need to attach the SGA now, before vote or so. Is there any
> > additional documentation needed apart from SGA.
>
> No you don’t need to submit an SGA before voting on the proposal, what we
> need is a clear indication that your name is unlikely to change and that
> it’s Cloudera intent to hand over rights to the name.The name would not
> need to be transferred until graduation.
>
> Thanks,
> Justin

Re: [DISCUSS] YuniKorn Proposal

[Justin Mclean]

Hi, 

Again thanks for your replies.

> *"The initial committers are from several relevant Apache projects who are
> interested in YuniKorn and committed to giving guidance, suggestions to the
> project, help to grow the community; and if possible, participants in code
> development."*
> 
> They're aware of the PPMC requirements, I don't think there's any surprise
> to proposed initial committers.

That great. A long way off but just be aware that if these people are listed on 
the graduation proposal for PMC members and they have not been active in the 
project that may delay graduation.

> We have already got SGA (Software Grant Agreement) from Cloudera, I'm not
> sure if we need to attach the SGA now, before vote or so. Is there any
> additional documentation needed apart from SGA.

No you don’t need to submit an SGA before voting on the proposal, what we need 
is a clear indication that your name is unlikely to change and that it’s 
Cloudera intent to hand over rights to the name.The name would not need to be 
transferred until graduation.

Thanks,
Justin

Re: [DISCUSS] YuniKorn Proposal

[Craig Russell]

Hi Wangda,

There is a distinction between licensing the code to Apache, which is done via 
SGA, and giving Apache rights to the name, which is done by a trademark 
assignment.

Apache in general will not use the name if Cloudera who owns the name intends 
to keep using it. Apache would need to rename the project if Cloudera intends 
to keep it.

The Yunikorn brand is currently in use by Cloudera. If you can clarify that 
Cloudera intends to assign the trademark to Apache, then we will need to have 
that in writing (in the proposal) and work with Trademarks to work on the 
trademark assignment.

Regards,
Craig

> On Dec 16, 2019, at 11:04 PM, Wangda Tan  wrote:
> 
>>> We will add it to the proposal before a vote. We have done similar
>>> practices like a PODLINGNAMESEARCH.
>> 
>> Great sounds good. Have you checked with Cloudera legal that they would be
>> willing to hand the name over to the ASF?
>> 
>> We recently has a situation where a podling was unable to use it name a
>> few months into incubation because of this and it caused Infra a lot of
>> unnecessary work.
>> 
> 
> We have already got SGA (Software Grant Agreement) from Cloudera, I'm not
> sure if we need to attach the SGA now, before vote or so. Is there any
> additional documentation needed apart from SGA.
> 
> Thanks,
> Wangda Tan
> 

Craig L Russell
c...@apache.org

Re: [DISCUSS] YuniKorn Proposal

[Wangda Tan]

Hi Justin,

Please find my responses inline below.

On Sat, Dec 14, 2019 at 4:36 PM Justin Mclean 
wrote:

> Hi,
>
> Thats for your replies.
>
> > The reason the number of contributors not significantly grow is the
> project
> > is hosted under cloudera.com, contributors from other companies are not
> > comfortable with contributing to other company's repo and even hesitate
> to
> > try that.
>
> Fair enough. Are there any concerns along those lines given it still the
> same core set of developers that will be working on it?
>

No concerns, we will continue to invest in this project as it is important
to our product, and expanding the community with more diversities is on our
top of the priority


> > To answer what is the philosophy behind non-code committers we added.
> > - The initial committers are from several relevant Apache projects who
> are
> > interested in YuniKorn and committed to giving guidance, suggestions and
> > participant in the future if possible.
>
> The if possible concerns me. Are these people committed to being PPMC
> members or not? All initial commutes are PPMC members not just committers.
>
> Do people on the initial committer list realise their responsibilities
> also include:
> - voting on releases
> - helping with board reports
> - understand and applying ASF policies and values
> - helping to grow the community
> - voting on new committers and PPMC members
>
> I not aware of the discussions that took place before this proposal come
> to the Incubator so everyone may already be aware and willing to do that.
> However, if that’s not the case, it may be better to vote them in as
> committers/PPMC members once they make contributions to the project.
>

I think my previous response is not right, what I meant is:

*"The initial committers are from several relevant Apache projects who are
interested in YuniKorn and committed to giving guidance, suggestions to the
project, help to grow the community; and if possible, participants in code
development."*

They're aware of the PPMC requirements, I don't think there's any surprise
to proposed initial committers.



>
> > We will add it to the proposal before a vote. We have done similar
> > practices like a PODLINGNAMESEARCH.
>
> Great sounds good. Have you checked with Cloudera legal that they would be
> willing to hand the name over to the ASF?
>
> We recently has a situation where a podling was unable to use it name a
> few months into incubation because of this and it caused Infra a lot of
> unnecessary work.
>

We have already got SGA (Software Grant Agreement) from Cloudera, I'm not
sure if we need to attach the SGA now, before vote or so. Is there any
additional documentation needed apart from SGA.

Thanks,
Wangda Tan


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

Re: [DISCUSS] YuniKorn Proposal

[Justin Mclean]

Hi,

Thats for your replies.

> The reason the number of contributors not significantly grow is the project
> is hosted under cloudera.com, contributors from other companies are not
> comfortable with contributing to other company's repo and even hesitate to
> try that.

Fair enough. Are there any concerns along those lines given it still the same 
core set of developers that will be working on it?

> To answer what is the philosophy behind non-code committers we added.
> - The initial committers are from several relevant Apache projects who are
> interested in YuniKorn and committed to giving guidance, suggestions and
> participant in the future if possible.

The if possible concerns me. Are these people committed to being PPMC members 
or not? All initial commutes are PPMC members not just committers.

Do people on the initial committer list realise their responsibilities also 
include:
- voting on releases
- helping with board reports
- understand and applying ASF policies and values
- helping to grow the community
- voting on new committers and PPMC members

I not aware of the discussions that took place before this proposal come to the 
Incubator so everyone may already be aware and willing to do that.
However, if that’s not the case, it may be better to vote them in as 
committers/PPMC members once they make contributions to the project.

> We will add it to the proposal before a vote. We have done similar
> practices like a PODLINGNAMESEARCH. 

Great sounds good. Have you checked with Cloudera legal that they would be 
willing to hand the name over to the ASF?

We recently has a situation where a podling was unable to use it name a few 
months into incubation because of this and it caused Infra a lot of unnecessary 
work.

Thanks,
Justin


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

Re: [DISCUSS] YuniKorn Proposal

[Wangda Tan]

Hi Justin,

Thanks for digging into this and giving feedback, let me try to answer
these questions:


On Thu, Dec 12, 2019 at 6:35 PM Justin Mclean 
wrote:

> Hi,
>
> Sounds like a good proposal.
>
> I can see it was opened source back in March but you haven’t seemed to
> have made any releases or added any new committers since then. An I correct
> in that assumption? Is the any reason for that? I note in the proposal that
> you have people from other organisations that you say are already
> collaborating with you on Github, but I cannot see much if any activity
> from them. The core repo has 5 main committers (and two others). The other
> repos are similar. As you note not all contribution are code, so I may be
> missing something. Can you explain how the initial committers were chosen
> and provide a bit more detail on their relationship to the project?
>

We added a committer Tao Yang after the project started. (See contribution
from Tao:
https://github.com/cloudera/yunikorn-core/commits?author=TaoYang526)

We actually did some releases, but on Docker Hub:
https://hub.docker.com/r/yunikorn/yunikorn-scheduler-k8s/tags. We didn't
put it to Github's release page.

The reason the number of contributors not significantly grow is the project
is hosted under cloudera.com, contributors from other companies are not
comfortable with contributing to other company's repo and even hesitate to
try that.

To answer what is the philosophy behind non-code committers we added.
- The initial committers are from several relevant Apache projects who are
interested in YuniKorn and committed to giving guidance, suggestions and
participant in the future if possible.

- Following folks are from YARN community (see following folks), we
collaborated on YARN scheduler for years and they have lots of domain
knowledge about scheduling. They're willing to give feedbacks and
suggestions to YuniKorn. And we already got tons of help and important
feedbacks from them.

Carlo Curino (cur...@apache.org) (Microsoft)
Subramaniam Krishnan (su...@apache.org) (Microsoft)
Arun Suresh (asur...@apache.org) (Microsoft)
Konstantinos Karanasos (kkarana...@apache.org) (Microsoft)
Jonathan Hung (jh...@apache.org) (LinkedIn)
Junping Du (junping...@apache.org) (Tencent)
Jason Lowe (jl...@apache.org) (Nvidia)

And DB Tsai is from Apache Spark community, getting Spark to integrate with
YuniKorn is very important task for us, and we need help from Spark
community. We received many valuable suggestions from DB about what the
project should go to better support batch workload like Spark.

Vinod Kumar Vavilapalli is helping the project from the beginning, from the
project execution, requirements and how to create a community,  we received
lots of suggestions and he volunteered to be the champion of the project.


>
> You mention the use of Slack, weekly catch up and open community meetings.
> How is the information discussed there passed on to other community members
> who are not on slack or not able to attend those meetings? Are any
> decisions made at those meetings or on Slack?
>

We made most of the decisions on Github issues, PRs and code review
publically. On the Slack or catch up meetings we mostly discuss issues we
talk about bugs or product issues.

For planning, we also keep
https://github.com/cloudera/yunikorn-core/blob/master/docs/roadmap.md up to
date, so other community members can get that easier.

To better improve, we will make use of mailing list, etc. in the future
like other Apache project once be part of the Apache incubator. Which can
get other contributors participated and we want to build an open community
instead of making closed-door decisions.


>
> The length of time to incubate seems a little on the short side,
> especially for a project that doesn’t seem to have a large community around
> it and most of the core set of developers working for a single company. I’d
> be happy to be proven wrong about that, but if the project ended up in
> incubation for longer would this be an issue?. Projects typically spend 1
> to 1 1/2 years in the incubator, some take less time some take more, some a
> lot more.
>

That makes sense, and I didn't see any issue if more incubation time
needed. We want to graduate once it is ready to graduate.


>
> There’s at least one section missing from your proposal [1], the
> information on the project name is important, can you answer that? Infra in
> particular is concerned about the amount of effort a name change takes.
>

We will add it to the proposal before a vote. We have done similar
practices like a PODLINGNAMESEARCH. We have done search of "YuniKorn" on
Github, nothing related to scheduler or distributed system. We also did a
search of YuniKorn as a trademark, no hit. And YuniKorn search on internet
also no relevant hit. Since the name is unique, easy to remember,
pronounce, and relevant to the project, we believe it is a good name.

I think we don't need to file PODLINGNAMESEARCH before the 

Re: [DISCUSS] YuniKorn Proposal

[Justin Mclean]

Hi,

Sounds like a good proposal.

I can see it was opened source back in March but you haven’t seemed to have 
made any releases or added any new committers since then. An I correct in that 
assumption? Is the any reason for that? I note in the proposal that you have 
people from other organisations that you say are already collaborating with you 
on Github, but I cannot see much if any activity from them. The core repo has 5 
main committers (and two others). The other repos are similar. As you note not 
all contribution are code, so I may be missing something. Can you explain how 
the initial committers were chosen and provide a bit more detail on their 
relationship to the project?

You mention the use of Slack, weekly catch up and open community meetings. How 
is the information discussed there passed on to other community members who are 
not on slack or not able to attend those meetings? Are any decisions made at 
those meetings or on Slack?

The length of time to incubate seems a little on the short side, especially for 
a project that doesn’t seem to have a large community around it and most of the 
core set of developers working for a single company. I’d be happy to be proven 
wrong about that, but if the project ended up in incubation for longer would 
this be an issue?. Projects typically spend 1 to 1 1/2 years in the incubator, 
some take less time some take more, some a lot more.

There’s at least one section missing from your proposal [1], the information on 
the project name is important, can you answer that? Infra in particular is 
concerned about the amount of effort a name change takes.

Your mentors need to be IPMC members [2][3] but as Dave notes, being ASF 
members they can ask to join the IPMC.

Thanks,
Justin

1. https://wiki.apache.org/confluence/display/INCUBATOR/New+Podling+Proposal
2. https://incubator.apache.org/guides/participation.html#as_a_mentor
3. https://incubator.apache.org/guides/mentor.html#mentors_must_be_on_the_ipmc


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

Re: [DISCUSS] YuniKorn Proposal

[Felix Cheung]

+1 ;)


On Wed, Dec 11, 2019 at 12:08 PM Dave Fisher  wrote:

> Hi -
>
> Very interesting proposal. +1.
>
> Please note that two of your nominated mentors will need to ask to join
> the IPMC by request at private@i.a.o
>
> Regards,
> Dave
>
> > On Dec 11, 2019, at 11:50 AM, Weiwei Yang  wrote:
> >
> > Greetings folks:
> >
> > Please consider the following proposal, which is also on the wiki
> > 
> > [1].
> > I look forward to hearing feedback from you.
> >
> >
> > *YuniKorn - An Unified Resource Scheduler*
> >
> > 1. Abstract
> > YuniKorn is a standalone resource scheduler responsible for scheduling
> > batch jobs and long-running services on large scale distributed systems
> > running in on-premises environments as well as different public clouds.
> >
> > 2. Proposal
> > YuniKorn ['ju:nikɔ:n] is a unified resource scheduler aiming to achieve
> > fine-grained resource sharing for various workloads efficiently on a
> large
> > scale, multi-tenant and cloud-native environments. YuniKorn brings a
> > unified, cross-platform scheduling experience for mixed workloads, with
> > support for but not limited to, Apache™ Hadoop® YARN and Kubernetes.
> >
> > Currently, YuniKorn is an open-source project with Apache 2.0 license.
> The
> > source code is hosted as a git-repo under the github.com/cloudera
> domain.
> > We would like to share it with the ASF and expand the community to a
> wider
> > range of users and contributors.
> >
> > 2.1 Background
> > Enterprise users run their workloads on different platforms such as
> Apache™
> > Hadoop® YARN and Kubernetes. They need to work with different resource
> > schedulers in order to plan their workloads to run on these platforms
> > efficiently. The scheduler implementations are fragmented, and not
> > optimized to balance existing use-cases like batch workloads along with
> new
> > needs such as cloud-native architecture, autoscaling, etc. We need a
> single
> > resource planning/management framework to manage resources on different
> > platforms using the same semantics, in order to address all the important
> > resource management requirements.
> >
> > 2.2 Rationale
> > There is no solution that exists now to address the needs of having a
> > unified resource scheduling experiences across platforms. That makes it
> > difficult to manage workloads running on different environments, from
> > on-premise to Cloud. YuniKorn aims to satisfy these needs. YuniKorn is
> > designed around the following principles:
> >
> > 1) Support different environments
> > As the compute platforms are evolving quickly, there are more and more
> > challenges appear in on-prem, cloud or hybrid environments. YuniKorn aims
> > to bring unified scheduling experiences across multiple environments with
> > enhanced scheduling capabilities.
> >
> > 2) Support extensive types of workloads
> > To improve the efficiency of the computing platform, a key idea is to run
> > different types of applications, like long-running services and batch
> jobs,
> > on shared resources. YuniKorn is an effort to address all the scheduling
> > features needed for such mixed workload environments.
> >
> > 3) Benefit both big-data and cloud-native communities
> > A resource scheduler needs to be capable of supporting mixed workloads,
> > both batch, and long-running services. This is the key to improving
> cluster
> > utilization, and to reduce the complexity of dev-ops. By creating a
> common
> > scheduler that is decoupled from the container platforms underneath, it
> can
> > benefit both Apache™ Hadoop® YARN and the Kubernetes communities.
> >
> > 2.3 Initial Goals
> > Initial goals are:
> > - Move the existing codebase, documentation to Apache hosted repo
> > - Set up mailing lists, website, CI/CD pipeline under Apache
> infrastructure
> > - Setup JIRA for issue tracking
> > - Incremental development and releases according to Apache guidelines
> > - Expand the community and bring more diversified contributors/users to
> > the community
> >
> > 2.4 Current Status
> >
> > 2.4.1 Meritocracy
> > Many of the initial developers of YuniKorn are already Apache committers
> > and PMC members from other Apache projects, such as Apache Hadoop and
> > Apache Submarine. Many of us have worked in the Apache Hadoop community
> for
> > years and know the Apache way well. We believe strongly in meritocracy in
> > electing committers and PMC members. We believe that contributions can
> come
> > in forms other than just code: for example, one of our initial proposed
> > committers has contributed solely in the area of project documentation.
> We
> > will encourage contributions and participation of all types, and ensure
> > that contributors are appropriately recognized.
> >
> > 2.4.2 Community
> > YuniKorn is a relatively new open source project, Cloudera is the
> original
> > development sponsor for YuniKorn. From the beginning of the project
> itself,
> > we 

Re: [DISCUSS] YuniKorn Proposal

[Dave Fisher]

Hi -

Very interesting proposal. +1.

Please note that two of your nominated mentors will need to ask to join the 
IPMC by request at private@i.a.o

Regards,
Dave

> On Dec 11, 2019, at 11:50 AM, Weiwei Yang  wrote:
> 
> Greetings folks:
> 
> Please consider the following proposal, which is also on the wiki
> 
> [1].
> I look forward to hearing feedback from you.
> 
> 
> *YuniKorn - An Unified Resource Scheduler*
> 
> 1. Abstract
> YuniKorn is a standalone resource scheduler responsible for scheduling
> batch jobs and long-running services on large scale distributed systems
> running in on-premises environments as well as different public clouds.
> 
> 2. Proposal
> YuniKorn ['ju:nikɔ:n] is a unified resource scheduler aiming to achieve
> fine-grained resource sharing for various workloads efficiently on a large
> scale, multi-tenant and cloud-native environments. YuniKorn brings a
> unified, cross-platform scheduling experience for mixed workloads, with
> support for but not limited to, Apache™ Hadoop® YARN and Kubernetes.
> 
> Currently, YuniKorn is an open-source project with Apache 2.0 license. The
> source code is hosted as a git-repo under the github.com/cloudera domain.
> We would like to share it with the ASF and expand the community to a wider
> range of users and contributors.
> 
> 2.1 Background
> Enterprise users run their workloads on different platforms such as Apache™
> Hadoop® YARN and Kubernetes. They need to work with different resource
> schedulers in order to plan their workloads to run on these platforms
> efficiently. The scheduler implementations are fragmented, and not
> optimized to balance existing use-cases like batch workloads along with new
> needs such as cloud-native architecture, autoscaling, etc. We need a single
> resource planning/management framework to manage resources on different
> platforms using the same semantics, in order to address all the important
> resource management requirements.
> 
> 2.2 Rationale
> There is no solution that exists now to address the needs of having a
> unified resource scheduling experiences across platforms. That makes it
> difficult to manage workloads running on different environments, from
> on-premise to Cloud. YuniKorn aims to satisfy these needs. YuniKorn is
> designed around the following principles:
> 
> 1) Support different environments
> As the compute platforms are evolving quickly, there are more and more
> challenges appear in on-prem, cloud or hybrid environments. YuniKorn aims
> to bring unified scheduling experiences across multiple environments with
> enhanced scheduling capabilities.
> 
> 2) Support extensive types of workloads
> To improve the efficiency of the computing platform, a key idea is to run
> different types of applications, like long-running services and batch jobs,
> on shared resources. YuniKorn is an effort to address all the scheduling
> features needed for such mixed workload environments.
> 
> 3) Benefit both big-data and cloud-native communities
> A resource scheduler needs to be capable of supporting mixed workloads,
> both batch, and long-running services. This is the key to improving cluster
> utilization, and to reduce the complexity of dev-ops. By creating a common
> scheduler that is decoupled from the container platforms underneath, it can
> benefit both Apache™ Hadoop® YARN and the Kubernetes communities.
> 
> 2.3 Initial Goals
> Initial goals are:
> - Move the existing codebase, documentation to Apache hosted repo
> - Set up mailing lists, website, CI/CD pipeline under Apache infrastructure
> - Setup JIRA for issue tracking
> - Incremental development and releases according to Apache guidelines
> - Expand the community and bring more diversified contributors/users to
> the community
> 
> 2.4 Current Status
> 
> 2.4.1 Meritocracy
> Many of the initial developers of YuniKorn are already Apache committers
> and PMC members from other Apache projects, such as Apache Hadoop and
> Apache Submarine. Many of us have worked in the Apache Hadoop community for
> years and know the Apache way well. We believe strongly in meritocracy in
> electing committers and PMC members. We believe that contributions can come
> in forms other than just code: for example, one of our initial proposed
> committers has contributed solely in the area of project documentation. We
> will encourage contributions and participation of all types, and ensure
> that contributors are appropriately recognized.
> 
> 2.4.2 Community
> YuniKorn is a relatively new open source project, Cloudera is the original
> development sponsor for YuniKorn. From the beginning of the project itself,
> we had clearly aimed to have this as an open-source project, so we started
> to build the community from the very early stages. We received a lot of
> feedback and valuable suggestions from other community members while the
> project was hosted as an open-source project on GitHub.