Maybe a more focused discussion with a smaller group of core sig-scheduling
folks will be better. We can consider asking them for such a meeting
earlier than 11/18, as Weiwei mentioned.
That avoids conflict with the meetup too.

On Thu, Nov 4, 2021 at 10:46 PM Weiwei Yang <[email protected]> wrote:

> I see.
> Let's discuss this in the next sync-up call.
> Thank you!
>
> On Thu, Nov 4, 2021 at 9:04 PM Chenya Zhang <[email protected]>
> wrote:
>
> > btw. We have the YK Meetup on Nov 18th 4:30 - 6:00pm. Hope it will not be
> > in conflict with the K8s Sig call.
> >
> > On Thu, Nov 4, 2021 at 5:33 PM Sunil Govindan <[email protected]> wrote:
> >
> > > Thanks, Chaoron.
> > >
> > >
> > > On Thu, Nov 4, 2021 at 5:23 PM Chaoran Yu <[email protected]>
> > wrote:
> > >
> > > > Sure, let's use my list as the agenda and finalize next Wednesday
> > > >
> > > > On Thu, Nov 4, 2021 at 3:58 PM Sunil Govindan <[email protected]>
> > wrote:
> > > >
> > > > > Hi Weiwei
> > > > >
> > > > > Yes. I suggest meeting next Wed inside of the YK community.
> > > > > Based on that we can take a call whether to join on 18th.
> > > > >
> > > > > Thanks, Chaoron for summing it up. And we could use that as agenda.
> > Is
> > > > that
> > > > > fine?
> > > > >
> > > > > Thanks
> > > > > Sunil
> > > > >
> > > > > On Thu, Nov 4, 2021 at 3:21 PM Weiwei Yang <[email protected]>
> wrote:
> > > > >
> > > > > > I think Chaoran covered most of the questions we discussed
> > yesterday.
> > > > > > Sunil, are you suggesting to meet next Wed inside of the YK
> > community
> > > > > > before setting up a call with sig-scheduling?
> > > > > > I noticed the next sig-scheduling meeting is Nov 18, we probably
> > can
> > > > try
> > > > > to
> > > > > > set up sometime earlier than that with a smaller group of people.
> > > > > >
> > > > > > On Thu, Nov 4, 2021 at 1:02 PM Chaoran Yu <
> [email protected]
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Hi Sunil,
> > > > > > >
> > > > > > > Next Wednesday at the same time works for me. From what I
> > > understand
> > > > in
> > > > > > the
> > > > > > > meeting yesterday, we want to initiate a conversation with
> > > > > sig-scheduling
> > > > > > > without committing to any actions just yet.
> > > > > > >
> > > > > > > The information we want to gather from them include the
> > following:
> > > > > > >
> > > > > > > * What's the overall process and timeline when contributing a
> > > plugin?
> > > > > > > * Besides contributing code directly in the plugins repo, can
> the
> > > > code
> > > > > > live
> > > > > > > in an outside repo (e.g. Apache repos)? Any other options?
> > > > > > > * The scheduler-plugins repo doesn't align with Kubernetes
> itself
> > > in
> > > > > > terms
> > > > > > > of release cadence nor does it match the latest k8s version.
> How
> > is
> > > > it
> > > > > > > maintained?
> > > > > > > * How does the default scheduler in the core K8s repo
> incorporate
> > > > > > > community-contributed plugins? What's the process of promoting
> a
> > > > > plugin?
> > > > > > >
> > > > > > > We can finalize the agenda when we meet next week
> > > > > > >
> > > > > > > On Thu, Nov 4, 2021 at 12:21 PM Sunil Govindan <
> > [email protected]>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Folks,
> > > > > > > >
> > > > > > > > Thanks for joining our weekly sync call.
> > > > > > > >
> > > > > > > > We have an action item to discuss with the SIG team sooner.
> > Could
> > > > we
> > > > > > > > conclude the meeting agenda earlier within the YuniKorn
> > community
> > > > > > itself
> > > > > > > > before we have that call?
> > > > > > > > We can have one more YuniKorn community call next week to
> > > conclude
> > > > > > before
> > > > > > > > starting the discussion with K8s. I could help schedule this
> at
> > > the
> > > > > > same
> > > > > > > > time as yesterday (3.00 pm PST) if there are no objections.
> > > > > > > >
> > > > > > > > Please share your thoughts.
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > > Sunil
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to