Re: [DISCUSS] YuniKorn Proposal

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

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 >

Re: [DISCUSS] YuniKorn Proposal

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:

Re: [DISCUSS] YuniKorn Proposal

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

Re: [DISCUSS] YuniKorn Proposal

+ @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

Re: [DISCUSS] YuniKorn Proposal

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

Re: [DISCUSS] YuniKorn Proposal

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.

Re: [DISCUSS] YuniKorn Proposal

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

Re: [DISCUSS] YuniKorn Proposal

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

Re: [DISCUSS] YuniKorn Proposal

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."* > >

Re: [DISCUSS] YuniKorn Proposal

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

Re: [DISCUSS] YuniKorn Proposal

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

Re: [DISCUSS] YuniKorn Proposal

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

Re: [DISCUSS] YuniKorn Proposal

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

Re: [DISCUSS] YuniKorn Proposal

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

Re: [DISCUSS] YuniKorn Proposal

+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: > >

Re: [DISCUSS] YuniKorn Proposal

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

[DISCUSS] YuniKorn Proposal

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