Re: [DISCUSS] PolarisProposal to the incubator
5 mentors are awesome! Excited to see this kind of support. Cheers, Wangda On 2024/08/01 13:21:09 Jean-Baptiste Onofré wrote: > Hi Wangda, > > Thanks for your message and your proposal. Now, we already have 5 > mentors on the proposal. For good execution/mentoring, I think it's > largely enough. I will let know you if one mentor wants to be > replaced. > > Thanks again! > > Regards > JB > > On Thu, Aug 1, 2024 at 2:43 AM Wangda Tan wrote: > > > > It is a super interesting project, I'm +1 on Polaris joining the Apache > > incubator. I'd be willing to offer guidance or be a mentor if needed. > > > > Best, > > Wangda Tan > > > > On 2024/07/30 17:33:57 Jean-Baptiste Onofré wrote: > > > Hi folks, > > > > > > We would like to propose a new project to the ASF incubator: Polaris. > > > > > > Polaris is a catalog for data lakes. It provides new levels of choice, > > > flexibility and control over data, with full enterprise security and > > > Apache Iceberg interoperability across a multitude of engines and > > > infrastructure. Polaris builds on standards such as those created by > > > Apache Iceberg, providing the following benefits for the ecosystem: > > > * Multi-engine interoperability over a single copy of data, > > > eliminating the need for moving and copying data across different > > > engines and catalogs. > > > * An interoperable security model providing a unified authorization > > > layer independent from the engines processing analytical tables. > > > * For multi-catalog scenarios, a unified catalog level view of data > > > across multiple catalogs via catalog notification integrations. > > > * The ability to host Polaris Catalog on the infrastructure of your > > > choice. > > > > > > Here is the proposal: > > > https://cwiki.apache.org/confluence/display/INCUBATOR/PolarisProposal > > > > > > Comments and feedback are welcome. > > > > > > Thanks! > > > Regards > > > JB > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] PolarisProposal to the incubator
It is a super interesting project, I'm +1 on Polaris joining the Apache incubator. I'd be willing to offer guidance or be a mentor if needed. Best, Wangda Tan On 2024/07/30 17:33:57 Jean-Baptiste Onofré wrote: > Hi folks, > > We would like to propose a new project to the ASF incubator: Polaris. > > Polaris is a catalog for data lakes. It provides new levels of choice, > flexibility and control over data, with full enterprise security and > Apache Iceberg interoperability across a multitude of engines and > infrastructure. Polaris builds on standards such as those created by > Apache Iceberg, providing the following benefits for the ecosystem: > * Multi-engine interoperability over a single copy of data, > eliminating the need for moving and copying data across different > engines and catalogs. > * An interoperable security model providing a unified authorization > layer independent from the engines processing analytical tables. > * For multi-catalog scenarios, a unified catalog level view of data > across multiple catalogs via catalog notification integrations. > * The ability to host Polaris Catalog on the infrastructure of your choice. > > Here is the proposal: > https://cwiki.apache.org/confluence/display/INCUBATOR/PolarisProposal > > Comments and feedback are welcome. > > Thanks! > Regards > JB > > - > 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: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0 (RC2)
+1 from me: Checked: - incubating in name - both of Signatures/hashes are good - LICENSE/NOTICE good - No unexpected binary files - Checked all source files have ASF headers - Compilable from source -Wangda On Sun, Aug 8, 2021 at 11:18 PM Xun Liu wrote: > hi Weiwei Yang > > Thank you for your prompt reply. > +1 (non-binding) from me. > > Best regards > Xun Liu > > On Mon, Aug 9, 2021 at 1:51 PM Weiwei Yang wrote: > > > hi Xun, Justin > > > > Thanks for the suggestion! > > I have created https://issues.apache.org/jira/browse/YUNIKORN-789 to > > address this. > > > > On Sun, Aug 8, 2021 at 10:48 PM Justin Mclean > > wrote: > > > > > Hi, > > > > > > > I have a question. > > > > I did not see the two files `NOTICE` and `DISCLAIMER` in the > > > > [1],[2],[3],[4] repo of incubator-yunikorn. > > > > > > It would be good if they are there, but what matters is if they end up > in > > > the release artefacts. > > > > > > Thanks, > > > Justin > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > >
Re: [VOTE] Accept Kyuubi into the Apache Incubator
+1, binding Best, Wangda On 2021/06/14 13:57:27, Willem Jiang wrote: > Hi all, > > Following up the [DISCUSS] thread on Kyuubi[1], I would like to call a > VOTE to accept Kyuubi into the Apache Incubator. > > Please cast your vote: > > [ ] +1, bring Kyuubi into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring Kyuubi into the Incubator, because... > > The vote will open at least for 72 hours, and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > Please check out the Kyuubi Proposal from the incubator wiki[2]. > > [1] > https://lists.apache.org/thread.html/rbd3224354d80c495ddf604853a1d8153c422cdf8d154738d34a8b5e2%40%3Cgeneral.incubator.apache.org%3E > [2] https://cwiki.apache.org/confluence/display/INCUBATOR/KyuubiProposal > > Regards, > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > - > 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: [VOTE] Release Apache YuniKorn (Incubating) 0.10.0
Thanks @taoy...@apache.org for running this release, +1 (Binding). [√] Checked signature and hash [√] “incubating" included in the name [√] Checked LICENSE, NOTICE, and DISCLAIMER (except 2021 which is pointed out by other folks) [√] Source files have ASF header. On Thu, Apr 8, 2021 at 12:27 AM Juan Pan wrote: > Hi +1 binding > > > Here is my checking list. > > > [x] Download links are valid. > [x] Checksums and PGP signatures are valid. > [x] LICENSE, NOTICE and DISCLAIMER files exist. > [x] All files have license headers if necessary. > > > But, the `Copyright 2019-2020` of NOTICE is expected to fix. > > > > > >Juan Pan (Trista) > > Senior DBA & PMC of Apache ShardingSphere > E-mail: panj...@apache.org > > > > > On 04/6/2021 09:58，Tao Yang wrote： > Hello IPMC > > The Apache YuniKorn community has voted and approved the release Apache > YuniKorn (incubating) 0.10.0. We now kindly request the IPMC members review > and vote for this release. > > YuniKorn is a standalone, universal resource scheduler that can support > both long-running and batch workloads. The current release provides some > enhanced functions, including gang-scheduling support, application > lifecycle control, improvements on web UI and web-site, etc. > > YuniKorn community vote thread: > > https://lists.apache.org/thread.html/rfbb34a8facfeecebdbd4ca17a65556166e522b029190520915915661%40%3Cdev.yunikorn.apache.org%3E > > Vote result thread: > > https://lists.apache.org/thread.html/re18dbfd2be3a5d11c1e25fa86b3b111ea4e802e00119da81df35a7df%40%3Cdev.yunikorn.apache.org%3E > > Issues included in this release: > https://issues.apache.org/jira/projects/YUNIKORN/versions/12348351 > > The release candidate: > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.10.0/ > > This release has been signed with a PGP available here: > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/KEYS > > Git tag for the release: > - https://github.com/apache/incubator-yunikorn-core/tree/v0.10.0 > - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.10.0 > - > > https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.10.0 > - https://github.com/apache/incubator-yunikorn-web/tree/v0.10.0 > > The vote will be open for at least 72 hours or until the necessary number > of votes is reached. > > Please vote accordingly: > [ ] +1 Approve the release of Apache YuniKorn (Incubating) 0.10.0 > [ ] +0 > [ ] -1 Do not approve (please specify the reason) > > Thanks, > Tao Yang > Apache YuniKorn (Incubating) >
Re: [VOTE] Release Apache YuniKorn (Incubating) 0.9.0
+1 (Binding) I checked: [√] No unexpected binaries in source code. [√] Downloaded artifacts and verified signature/hash [√] Incubating in name [√] License and Notice files are fine [√] DISCLAIMER is fine [√] Source code has proper ASF Header I haven't tried to build from source code. Thanks, Wangda Tan On Wed, Aug 19, 2020 at 10:51 AM Felix Cheung wrote: > I see > > jlowe is a binding IPMC vote that can carry forward from dev@ vote. > > We just need 1 more binding vote. > > > On Mon, Aug 17, 2020 at 11:06 PM Felix Cheung > wrote: > > > +1 (binding) > > > > - incubating in name > > - signature and hash fine > > - DISCLAIMER is fine > > - LICENSE and NOTICE are fine > > - No unexpected binary files > > - All source files have ASF headers > > > > - didn't try - compile from source > > > > > > On Mon, Aug 17, 2020 at 9:12 PM Wilfred Spiegelenburg < > wilfr...@apache.org> > > wrote: > > > >> Hello IPMC > >> > >> > >> > >> The Apache YuniKorn community has voted and approved the release Apache > >> > >> YuniKorn (incubating) 0.9.0. We now kindly request the IPMC members > review > >> > >> and vote in this release. > >> > >> > >> > >> YuniKorn is a standalone, universal resource scheduler that can support > >> > >> both long-running and batch workloads. The current release provides a > >> fully > >> > >> functional resource scheduler for K8s. > >> > >> > >> > >> YuniKorn community vote thread: > >> > >> > >> > https://lists.apache.org/thread.html/rcb63f4de161439e90b47b53388028119c35f8137f78847405f6a2d4d%40%3Cdev.yunikorn.apache.org%3E > >> > >> > >> > >> Vote result thread: > >> > >> > >> > https://lists.apache.org/thread.html/ra20372465b758b8f9bb3271ec6b4483774eb07af5df83712e7d5ecf7%40%3Cdev.yunikorn.apache.org%3E > >> > >> > >> > >> Issues included in this release: > >> > >> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347799 > >> > >> > >> > >> The release candidate: > >> > >> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.9.0/ > >> > >> > >> > >> This release has been signed with a PGP available here: > >> > >> https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS > >> > >> > >> > >> Git tag for the release: > >> > >> - https://github.com/apache/incubator-yunikorn-core/tree/v0.9.0 > >> > >> - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.9.0 > >> > >> - > >> > >> > >> > >> > >> > https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.9.0 > >> > >> - https://github.com/apache/incubator-yunikorn-web/tree/v0.9.0 > >> > >> > >> > >> The vote will be open for at least 72 hours or until the necessary > number > >> > >> of votes is reached. > >> > >> > >> > >> Please vote accordingly: > >> > >> > >> > >> [ ] +1 Approve the release of Apache YuniKorn (Incubating) 0.9.0 > >> > >> [ ] +0 > >> > >> [ ] -1 Do not approve (please specify the reason) > >> > >> > >> > >> Thanks, > >> > >> Wilfred Spiegelenburg > >> > >> Apache YuniKorn (Incubating) > >> > >> > > > > >
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 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
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
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
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
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
