►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
If
you
haven't
already,
please
add
your
name
to
the
attendee
list,
as
you
can
see
here
in
the
meeting
notes,
we
want
to
make
sure
that
we
have
everyone
who's
on
the
call
here,
so
we
can
reach
out
if
we
want
to
do
any
follow-ups
or-
or
things
like
that,
so
please
add
your
name
and
affiliation
there
and
then
we'll
go
through
status
updates
and
if
you
have
any
discussion
topics
that
you
would
like
to
bring
up.
Please
do
that
as
well.
A
You
can
add
them
here
to
the
hackmd
as
we
go
through
so
with
that,
let's
start
with
nolan
nolan
is
out
he's
at
a
doctor's
appointment,
but
he
does
have
a
rough
draft
of
a
prosper
of
the
proposal
for
valero
debug.
So
maybe
we
can
have
a
look
at
that
next
week.
A
Next
up
we
have
bridget.
B
Hi
everyone,
so
thank
you,
everyone
who
is
for
your
patience.
I've
been
working
on
this
plug-in
versioning
design
doc
as
I've
been
working
on.
I've
just
been
realizing
that
the
plug-in
framework
is
quite
complex.
So
it's
taken
me
quite
a
few
times
to
like
go
through
this
and
make
sure
that
I
understand
it.
B
I
have
put
the
design
dock
in
a
google
doc
so
far,
just
because
I
think
it'll
be
easier
to
gather
comments
and
have
folks
maybe
understand
the
process
a
little
bit
more
like
suggest
things
in
there
and
then
once
we
kind
of
refine
it
a
bit
more
I'll
move
it
into
a
pr,
but
hopefully
everyone
can
access
this.
B
I
I'm
hoping
that
I
can
gather
some
comments
and
some
feedback
over
the
next
week
and
incorporate
that
and
then
I'll
try
to
present
it
at
the
next
community
meeting
so
next
week,
so
yeah
so
please
feel
free
to
really
feedback.
Tell
me
if
I've
missed
anything
or
just
like
really
under
misunderstood,
something
I'll
be
continuing
to
add
to
this,
as
well
as
new
things
come
up,
but.
C
Yeah,
that's
it
for
me.
I
just
learned
yesterday
that
there
were
server
plugins
like
if
you
go
to
the
valero
package,
server,
there's
plugins
and
then
we
have
our
custom
plugins
and
of
course
we
have
the
standard.
Plugins
is
this?
Does
this?
I
guess
this
covers
just
the
custom
plugins
that
people
can.
B
Yeah
so
the
like,
the
the
server
aspect
of
the
plug-ins,
so
each
plug-in,
essentially
even
like
the
custom,
plug-ins
and
everything
that's
internal.
They
all
essentially
run
a
grpc
service
and
then
the
valero,
the
main
valero
process
acts
as
a
client
and
communicates
with
that
plugin
server.
B
So
that's
how
it's
implemented
so
the
plugins
communicate
by
grpc.
So
maybe
you
might
understand
a
little
bit
more
about
the
process
after
reading
this,
maybe
there's
something
that
I've
missed.
So
if
you've
noticed
something
else,
some
other
aspect
of
the
the
plugins
I've
missed
yeah,
please
feel
free
to
to
read
and
leave
some
feedback.
I
appreciate.
A
All
right,
carlesia,
carmelizing.
D
I'm
gonna
make
this
a
word.
I
love
it.
I
I
don't
know,
I'm
not
sure.
If
the
carville
team
likes
it,
I
made
making
progress
with
this
list
of
requirements
before
I
tackled
the
design
dock
for
the
for
the
carvel.
D
Basically,
what
we're
trying
to
do
is
have
all
the
artifacts
so
pillar
can
the
little
users
can
use
carvel,
carbilized
artifacts
to
deploy
and
configure
valero,
and
I
have
to
answer
some
of
the
some
of
these
questions
and
I
still
need
a
review
from
nolan,
but
I
am,
I
am
still
doing
research
and
to
move
on
to
the
design
doc.
D
D
A
I
have
a
question
regarding
this:
could
you
just
open
them
up
to
see
that
we
got
proper
review
requests
to
the
right
people.
D
The
the
way
it
works
is
so
there's
a
it's
a
github
action.
There
are
different
ones,
so
we're
using
the
specific
ones,
the
specific
one
but
the
basically
they
all
work
the
same.
We
have
a
list
of
reviewers
and
in
our
case
all
of
them
of
I
think
five
of
us
now
maintainers
and
then
we
configure
it
to
say
out
of
this
list
pick
two.
So
every
pr
that
gets
open.
D
This
action
will
randomly
assign
two
people
as
reviewers
for
that
pr
and
it's
nice,
because
if
nobody
gets
assigned
that's
bad
and
if
everybody
gets
a
sign,
that's
a
in
my
opinion.
That's
also
bad
because
at
least
it's
not
ideal,
because
then
it's
like,
we
are
responsible.
Nobody
is
responsible,
so
now
yeah
and
we
have
to
be
careful
about
if
we
can't
review
the
pr
handoff
to
someone
else,
that
kind
of
thing,
but
at
least
we
every
pr
will
have
two
reviewers
who
are
responsible.
E
I
have
a
question
about
that.
Just
that
that
kind
of
sets
the
default
view,
I'm
guessing.
If
there's
a
particular
pr
that
I
have
an
interest
in
reviewing
that
I'm
not
assigned
to.
I
can
go
ahead
and
review
it
and
that'll
count
as
one
of
the
two
anyway.
E
D
Just
so
so
we
make
sure
that
pr's
get
merged
yeah,
but
you
you
can
even
say:
if
you
not
assigned
you,
can
you
can
talk
to
the
other
maintainer
and
say:
hey,
don't
merge
this
pro.
You
write
on
npr,
hey,
don't
merge
this
vr
before
I
review
it
because
I
really
want.
I
have
some
opinions,
so
you
can
ask
for
the
pr
to
be
held
until
you
review
it
or
you
can
say
hey.
Do
you
want
to
get
off
of
reviewing
this
and
put
me
in
your
place.
D
A
Did
we
are
we
using
the
github
owners
functionality
here
at
all.
D
A
Okay,
but
looking
into
that
a
little
just,
it's
interesting
to
see
that
that
we
can
put
owners
under
certain
structures
within
the
project
and
all
for
call
on
people
for
review
for
certain
feature
degrees.
D
I
am
not
remembering
I
I
am
misremembering
what
this
is.
I
remember
that
there's
this
thing
called
bonus
is
the
owners,
people
who
are
what
qualifies
as
owners,
because
not
all
of
them
we
weren't
able
to
put
all
the
maintainers
as
github
the
same
equivalency
as
we,
the
vmware
maintainers,
have
because
of
security
reasons,
because
they
have
access
to
things
that
so
we
haven't
been
able
to
sort
it
out.
So
if
it's
through
there,
we
can't
do
it
because
external
maintainers
wouldn't
be
able
to
be
added,
but
I'm
not
remembering
exactly
what
that
is.
A
Yeah,
it's
a
it's
a
different
thing,
called
code
owners.
A
So
you
can,
let
me
let
me
show
the
screen
again
the
way
for
making
sure
that
we
define
individuals
or
teams
are
responsible
for
code
ana
repository
as
well,
so
you
can
have
something
like
yeah.
They
have
a
few
examples
here,
everything
under
docs
and
we
we
make
sure
that
this
this
email
or
the
the
person
tied
to
this
email
gets
and
gets
a
notification.
D
B
D
D
F
I
think
upstream
kubernetes
uses
something
like
this,
but
it's
configuring,
a
system
called
pro
and
they
have
a
file
name.
Owners
and
owners
have
two
sections.
Reviewers
and
approvers,
so
kind
of,
like
approver,
has
a
higher
responsibility
than
a
reviewer.
F
An
approver
can
override
with
slash
approve
command
and
that
actually
achieves
what
you're.
Looking
for
in
terms
of
assigning
the
right,
reviewer
and
owner
to
a
particular
pr.
D
Thank
you
for
explaining,
so
so
we
do
have
an
interest
in
looking
into
prowl.
We
haven't
assigned
time
to
do
that
yet,
but
so
we
would
need
something.
So
that's
basically
you
establish
for
the
owner.
The
owners
are
categorize
them
in
different
ways,
and
then
you
have
to
have
a
trigger
that
says.
You
know,
look
up
this
list,
so
we
can
do
that
with
github
action
now
and.
D
A
Hey
yeah
not
bad
well,
this
is
cool
making
sure
that
we
have
the
github
action,
though,
is
all
set
up
and
working.
Thank
you,
kalisia.
G
Yes,
I
think
we
mentioned
this
last
tuesday,
but
we
finally
nolan
dave
and
I
finished
our
backlog
triage.
It
had
ballooned
to
411
issues
which
felt
much
well,
we've
only
thank
you,
jonas,
but
it's
only
the
triage.
We
finished.
We
still
have
another
big
chunk
of
work,
but
we'll
celebrate
halfway
points.
So
now,
there's
290
issues
rough.
So
we
closed
122
issues.
Definitely
it
was
not
ideal.
G
There
were
a
lot
of
good
ideas
in
there,
but
in
short,
if
they
either
didn't
align
with
our
future
direction
or
we
didn't
think
we
could
get
to
them
for
the
next
two
years
we
we
felt
like
having
them
open
was,
was
worse
kind
of
they
were
sitting
in
purgatory
kind
of
just
sitting
there.
So
of
the
290
issues
about
a
quarter.
We
are
considering
for
2022
or
beyond,
so
this
would
probably
be
valera
2.0
right
and,
of
course,
that'll
be
once
dave's
back
from
his
vacation.
G
We're
going
to
reduce
those
we've
got
about
half
of
the
issues
supposedly
are
for
1.7
or
1.8,
not
suppose,
sorry,
I
shouldn't
say
supposedly,
but
in
short,
we
will
not
do
140
issues
in
the
remainder
of
2021,
but
they
are
at
least
in
contention.
There
also
might
be
duplicates
we're
going
to
try
to
reduce
that.
Likewise,
we'll
do
this
when
dave's
back
and
lastly,
there's
about
70
issues.
A
Know
think
this
is
great.
Closing
out.
122
issues
out
of
400
level
is
big,
so
that's
that's
fantastic
to
see
closing
out
a
quarter
of
more
than
a
quarter
of
all
the
issues
there
so
to
get
it
more
manageable
and
then
make
it
yeah
I'll
see
all
the
others
being
aligned
for
future
releases.
A
Awesome
any
questions,
comments
for
eleanor.
A
Right,
so
we
have
one
thing
that
I
wanted
to
bring
up.
I
haven't
added
it
in
here,
but
we
have
started
some
work
on
a
cfp
for
kubecon
north
america,
so
we're
gonna
see
if
we
can
get
valero
on
stage
there,
which
would
be
awesome.
So
we've
got
scott
and
carlesia
and
eleanor
working
on
things
here,
which
is
fantastic
to
see
so
for
the
community.
A
Here,
if
you
are
using
or
have
built
something
on
top
of
valero,
we
would
love
to
hear
about
what
you're
using
it
for
and
how
it's
being
used.
So
if
you
have
anything
like
that,
please
ping
me
on
slack.
If
you
want
a
shout
out
in
the
shout
out,
or
maybe
even
a
larger
explanation
of
the
the
thing
that
you
do,
please
ping
me
on
slack
in
the
kubernetes
like
there
at
jonas
rosslyn
and
I'd
love
to
get
you.
A
In
that's
it
from
me
any
questions
on
that.
A
Nope
all
right
and
contributor-
shout
outs,
they're
usually
done
by
nolan
and
he
is
out
today
so
we'll
we'll
keep
those
for
next
week.
A
A
Perfect
perfect,
yeah
and
yeah:
please
run
it
and
then
we
can
talk
about
them
next
week
as
well.
I
see
also
there's
an
issue
with
the
meeting
invite
the
new
zoom
link
so
I'll
make
sure
that
that
gets
updated.
I
believe
I
sent
that
out
as
an
update
last
week.
A
If
that
didn't
happen,
I
apologize
so
I'll
make
sure
that
you
all
get
the
new
link
as
well
in
your
inboxes
and
if
you
don't
get
a
a
an
updated
invite
by
this
afternoon,
please
ping
me
in
public
and
say:
hey
jonas,
where
the
heck
is
the
calendar,
invite
so,
yes,
felicia.
A
All
right,
so
that's
it
for
today.
Thank
you.
Everyone
for
for
joining
and
have
a
great
rest
of
the
week,
see
y'all
next
week.