►
From YouTube: [SIG ContribEx] Weekly Meeting for 20211208
Description
[SIG ContribEx] Weekly Meeting for 20211208
A
There
we
go
okay,
everyone
welcome
to
the
december
eighth
computer
experience,
bi-weekly
meeting
I'll,
be
your
host
today,
bob
killen
one
of
the
co-chairs
for
sick
computer
experience.
A
As
a
general
reminder,
these
calls
are
recorded,
it'll
be
posted
to
youtube
at
some
point
in
the
future,
and
we
abide
by
the
scenes
of
code
of
connect
which
essentially
boils
down
to
please
be
excellent
to
each
other
with
that,
if
someone
is
available
to
be
a
note
taker
that
would
be
super
super
awesome
cool.
Thank
you.
A
Please
go
ahead
and
test
your
name
in
the
notes,
and
with
that
do
we
is
anyone
new
to
the
call.
Do
we
want
to
bounce
their
introductions.
B
I
can
say
a
quick
hello.
I
this
is
my
first
time
on
on
this
call,
I'm
xander
I
I
just
led
enhancements
for
the
1.23
kubernetes
release
and
through
that
there
were
some
things
that
kind
of
came
up
about
how
we
take
shadow
applications,
and
things
like
that
that
I
think
tie
really
closely
into
contributor
experience.
So
I
wanted
to
kind
of
come
and
hang
out
here
for
a
little
bit
and
and
see
see
what
y'all
work
on
and
yeah
happy
to
be
here
cool.
Thank
you.
A
C
We'll
just
rages
on
me:
you
didn't,
I
was
gonna
fall
for
it
all
right.
My
name
is
ray
lahanna.
I
was
the
release
sleep
for
123,
which
came
out
yesterday.
Thank
you.
I'm
also
involved
in
a
few
other
things
around
kubernetes.
So
you
might
see
me
in
about
the
community
celebration
or
sig
docs,
or
six
security
or
sig
release,
we'll
play
the
hot
potato
game.
So
go
ahead
and
pick
someone
else
to
go
all
right.
How
about
nigel.
D
What's
up
yo,
I'm
nigel,
I
wasn't
involved
in
the
one
top
23
release.
I
I'm
a
community
manager
for
an
open
source,
kubernetes
distribution,
getting
used
to
now
being
a
part
of
the
sig
contrabex
and
helping
out
where
I
can
I'll
toss
it
over
to
abby.
E
Hello,
I'm
I'm
abby,
like
nigel's,
mentions
I
and
first
time
here
on
on
this
call.
I
work
in
sick
docs
mostly,
but
I'm
I'm
trying
to
see
how
other
things
are
our
other
cigar
and
then
sort
of
join
other
meetings
and
I'll
kick
it
over
to
laura.
F
I'm
laura
I'm
a
developer
advocate
over
here
at
palumi
and
I
have
not
been
on
this
call
in
a
couple
weeks
because
I
keep
getting
sent
everywhere,
but
yeah,
I'm
the
one
who
does
the
community
meetings
that
are
on
hold
right
now
because
of
the
k,
dev
migration,
so
other
than
that
yeah
hi
and
I
am
gonna
kick
it
over
to.
I
need
names,
paris,.
G
Let's
see,
oh
no,
hey.
H
I
I'm
sorry
it's
kind
of
late
for
me,
so
my
name
is
anno.
I'm
the
co-chair
of
c
k,
stanford,
I'm
also
visa
manager
associate
you
I
used
to
be
in
country
packs
full
time,
but
because
I'm
now
a
signature,
I'm
really
present.
With
my
sake.
I
E
E
J
Hello
folks,
this
is
pratish,
I'm
a
junior
student
from
india-
and
I
have
been
with
the
sick-
contributes
for
quite
a
time
now.
I
mostly
work
with
the
contributor
site
and
go
around
try
aging
issues
and
all
so
yeah
having
a
great
time
here.
Next,
I
would
like
to
pass
on
to
deva.
J
Hi
hi
everyone,
I'm
devrata,
I'm
also
from
india,
I'm
a
finance
student,
so
yeah
I
have
been
involved
with,
contributes
thanks
to
paris
for
her
mentoring
and
yeah
like
yeah.
I
do
stuffs
like
you
know,
wherever
there
is
required
for
volunteers.
I
just
you
know,
signed
up
for
that,
and
recently
I've
been
working
with
the
mentoring
sub
project
for
the
caterpillar
scenario
and
yeah.
It
has
been
quite
a
fun
thing.
K
Thank
you
for
that
dave,
brother,
hi,
everyone.
I
am
srikaran
and
I
am
fairly
new
to
the
community.
I
started
contributing
post
kubecon,
north
america,
so
as
I
I
work
two
jobs,
so
I
work
as
a
software
engineer
at
a
company
called
code
month
so
where
I
do
a
lot
of
back
end
development
and
I
also
work
at
a
developer
advocate
as
a
developer
advocate
at
a
startup
called
dasha
ai.
K
So
it's
I
find
both
fields
really
really
interesting
and
I
hope
I
can
contribute
in
some
way
or
the
other
every
week.
Thank
you.
K
I
I
I'm
not
entirely
sure
who
hasn't
gone
yet.
So
if
someone
could
point
point
out,
that
would
be
great.
L
Yeah,
hello,
everyone.
I
am
oshi
and
a
final
year,
engineering
student
from
india
and
I'm
working
as
a
technical
writer
internet
cloud,
so
I
recently
started
attending
meetings
in
part
two
via
community
yeah.
So
I
hope
I
like
contribute
to
the
community.
Thank
you.
J
I
hope
there's
no
one
left
except
me
I'll,
go
then
hello.
All
my
name
is
I've
been
contributing
to
kubernetes
around
half
a
year
now
it
and
I've
I'm
con,
I'm
getting
involved
in
the
contrabex
project
for
a
few
months
now,
under
as
as
paris
is
guiding
few
of
us
to
getting
getting
started
with
the
contrabex
project.
So
yeah
happy
to
be
here.
M
Yeah
so
hello,
everyone,
this
is
avinashtripati.
Also
a
student
from
india.
I've
been
into
contributing
kubernetes
for
like
four
or
five
months,
mostly
I'm
learning
kubernetes
and
trying
to
look
for
some
opportunities
to
contribute
here.
I've
missed
a
lot
of
meetings
of
counterfeit,
so
I
was
like
okay
now
I
have
to
come
back
to
this
so
yeah
happy
to
be
here.
M
L
A
Thank
you
cool
welcome.
A
Hopefully
you
know
you
find
this
interesting
or
at
least
get
a
little
bit
of
idea
of
all
the
fun
stuff
that
goes
on
here
with
that
now
that
we
are
through
everyone,
we'll
kick
it
off
with
our
regular
stuff
and
that's
events,
office
hours,
paris,
you
have
a
comment
here.
G
Yeah
mine
was,
I
just
need
to
talk
to
raw
code,
about
taking
it
to
cncf
versus
controvex.
A
Yeah,
thank
you
for
dropping
the
link
to
the
notes
again,
yeah
and
honestly,
it's
it's
sort
of
functioning
as
it
is.
F
Still,
no
updates,
I'm
finally
catching
up
to
all
of
the
updates
around
the
k.
Dev
mailing
list
migration
so
I'll
be
interested
to
hear
where
we
are
where
we
are
on
that
and
where
I
can
help,
but
yeah
no
real
updates,
because
we
are
doing
the
k,
dev
migration
instead.
So
my
guess
is:
we
probably
won't
start
this
back
up
until
january
at
the
earliest.
N
A
I
agree
with
that
at
this
point.
Okay,
any
comments,
questions
regarding
that
or
do
we
move
on
to
contributor
summits.
A
And
no
worries
josh,
okay,
contributions,
the
the
big
thing
we
actually
really
need
to
start
planning
kubecon
eu
already.
We
have
to
put
in
a
request
for
how
much
space
we
want
by
the
end
of
the
month.
N
N
Yeah,
that's
my
take
so
my
my
suggestion
would
be:
let's
try
to
get
registration
up
as
early
as
possible
in
january
with
a
public
decision
deadline
so
that
like,
if
we're
deciding
to
not
do
it
because
of
lack
of
registration,
we'll
be
deciding
that
in
early
march
and
not
later
than
that,
yeah.
N
I'm
already
running
into
this,
I'm
currently
reviewing
submissions
for
southern
california,
linux
expo,
which
is
kind
of
strictly
a
us-based
conference,
so
people
aren't
even
facing
international
travel
restrictions
and
speaker
submissions
are
way
down
and
notably
absent
as
anybody
who
works
for
a
like
a
fortune
100
company,
because
they
don't
know
what
their
travel
policy
is
and
so
they're
not
applying
for
things.
F
Yeah
laura,
I
was
going
to
say
I
have
a
feeling.
A
lot
of
companies
are
waiting
to
see
the
fallout
from
re
invent
the
holidays
before
they
actually
open
up,
but
I
mean
frankly
like
at
least
down
here
in
austin.
The
aws
offices
are
reopening,
so
I
think
that's
a
good
sign
they're,
starting
to
tell
people
that
we're
allowed
to
hold
meet-ups
there
in
person
again
as
long
as
you're,
vaccinated
and
masked
and
all
that
fun
stuff.
F
D
C
Well,
I
feel
like
having
it
earlier,
puts
it
on
people's
radars
earlier
to
get
the
approvals
needed
and
if
with
me
for
my
company,
it's
better,
we
have
started
talking
about
coupon
eu
already,
and
so
I
think
earlier
it's
better
what.
A
F
We
we
did
a
maybe
for
kubecon
north
america,
because
we
weren't
sure
whether
people
were
gonna
come,
but
I
think
the
bigger
question
was
people
couldn't
come
to
the
main
event
and
we
were
required
to
people
were
required
to
have
a
ticket
to
that
before
they
could
register,
and
so
a
lot
of
the
maybes
were
people
who
weren't
sure
whether
their
company
was
going
to
pay
for
that
ticket.
F
N
A
A
Yeah,
that's
what
I
mean
yeah
yeah.
We
did.
I
think
it
was
like,
maybe
like
pending,
like
travel
restrictions
or
something
like
that
was
the.
I
think
the
wording
is
like
last
time
right.
N
I
mean
one
that
would
give
us
information
would
be
sort
of
pending
approval
to
attend
kubecon,
because
then,
a
month
out
from
kubecon,
we
could
ask
deb
to
run
our
registration
list
against
their
registration
list,
and
we
would
have
a
good
idea
of
how
many
those
maybes
were
actually
attended.
D
D
A
D
A
A
A
Yeah
keep
con
a.
N
A
So
the
computer
hacking
day
so
basically
just
take
like
the
reg
from
the
computer
hacking
day
and
the
actual
kubecon
reg
to
see
because
they
they
know
if
they
actually
showed
up
or
not
so
basically,
to
see
like
how
many
out
of
the
list
actually
showed
up
and
used
that
number.
As
sort
of
our
base
estimate
for
kubecon
eu,
I
mean.
N
No,
that
was
why
we
cancelled
all
of
scheduled
activities,
because
that
was
what
we
were
expecting
the
yeah.
I
mean
really
what
this
comes
down
to
is
I'd
like
to
know
three
or
four
weeks
out,
rather
than
a
week
and
a
half
out
yeah
if
we're
going
to
pull
it
because
of
of
lack
of
attendance,
the
and
and
I'm
sure
that
deb
would
you
know
in
the
linux
foundation,
people
would
really
appreciate
knowing
earlier
since
vendors
have
cancellation
dates.
The
so.
N
Yeah
well
yeah.
That
would
also
be
my
suggestion.
Is
let's
not
try
to
make
this
a
crazy
thing,
like
maybe
honestly,
maybe
one
room
with
scheduled
activities
in
one
room
with
unscheduled
activities
and
and
if
we
suddenly
get
a
surge
of
registration,
you
know
arranged
with
deb
that
there's
another
room.
We
can
maybe
announce.
A
I
A
A
E
Yeah,
I
just
had
one
other
thing
to
kind
of
add
st
docs
has
been
talking
about
running
a
doc
sprint
at
the
the
cube
county.
U
so
it's
not
necessarily
event
that
people
would
have
to
register,
for
I
don't
think,
that's
how
it's
been
done
in
the
past,
but
it
would
be
something
that
we'd
like
to
get
space
for.
If
we
do
so,
I
just
want
to
put
that
on
people's
radar.
A
Okay,
yeah,
that's
not
a
problem.
We
can.
We
can
request
like
a
board
room
or
something
like
that
for
okay
for
that
cool.
So
I
think
the
the
general
consensus
at
this
point
is
far
as
potential.
You
know
room
reservation
and
we
can,
you
know
potentially
cancel
later
on,
go
for
one.
A
You
know
one
or
two
rooms
and
try
and
get
reg
out
as
early
as
possible,
with
a
maybe
option
for
like
pending
travel
restrictions,
or
something
like
that.
I
think
that
does
that
summarize
everything
is
the
big
takeaways.
A
Sorry
letter
a
okay:
well,
we
can
brainstorm
on
potential
other,
maybe
options,
because
we
we
have
time
for
the
reg
form.
It's
just
the
space
reservation
that
we
need
to
get
in,
like
sooner
rather
than
later,.
N
D
N
That
that
was
a
good
room
to
have
unstructured
stuff,
because
we
actually
had
a
couple
of
separate
groups
go
in.
There
show
up
for
impromptu
hacking
sessions,
and
we
were
far
enough
apart
that
it
really,
there
really
was
no
spillover.
Okay,
the
so
have
like
one
room
like
that
and
one
smaller
sort
of
lecture
structured
room
for
scheduled
content
or
workshop
structured
room.
I
think
for
scheduled
content,
and
you
know
somewhere
where
potentially
we
could,
I
don't
know,
do
we
even
want
to
worry
about
potentially
annexing
another
room.
E
A
N
A
Okay,
next
up
on
the
list,
is
just
the
contributor
celebration
next
week.
Please,
you
know
social
boost
if
you
haven't
registered,
please
register
it'll
be
similar
to
last
year
in
that
we're
using
discord
as
our
main
platform.
A
N
Mostly
just
awareness-
I
I
you
know,
still
feel
like
most
folks
even
in
the
community-
are
not
necessarily
aware
that
it's
going
to
happen
or
if
they
are
aware
that
it's
going
to
happen.
It's
it's
a
vague
awareness
and
not
they
haven't
looked
at
the
page
to
see
what
the
activities
are
yeah.
So
that's
pretty
much
it.
Oh
and
also
you
know,
pray
for
a
video
set
up,
because
we
are
once
again
going
to
be
doing
a
lot
of
this
on
new
video
configurations.
A
And
we
will
well,
we
can.
We
can
follow
up
in
the
summit
call
on
on
monday,
the
I
would
say
one
thing
like
if
you
want
to
like
it's
sort
of
structured
for
impromptu
activities.
So
if
you
want
to,
if
you
want
to
like
pop
in
and
do
a
like,
if
you
want
to
play
halo
or
something
like
that,
there's
a
channel
for
lfg.
So
there's
I've
gotten
lots
of
people
asking
me
about
halo.
A
J
Yeah,
just
just
a
reminder
that
we
discussed
on
sending
the
comps
on
slack
channels
which
we
didn't
send.
I
guess
that
would
be
a
great
thing
to
do
for
the
awareness
yeah.
We
could
do
that
so
like
we
could
put
in
the
agenda
and
someone
could
do
it
by
this
week.
Then
it's
good.
A
That's
it
like:
let's,
let's
try
and
knock
that
out
when
the
next
big
comms
announcement
goes
out
with,
like
more
of
the
schedule
updated
so
hopefully,
either
later
today
or
tomorrow,.
I
A
I
N
Yeah
I
mean
I've
been
putting
it
in
lwkd
every
week,
okay
right,
but
but
I
think
a
lot
of
people,
I'm
I'm
just
I'm
on
another
channel
with
one
of
my
co-organizers
for
contributor
celebration,
stuff
and-
and
I
think
a
lot
of
people
are
in
the
boat
that
we're
in
where
we
kind
of
feel
like
somehow.
We
have
two
months
of
work
to
do
in
the
the
two
and
a
half
weeks
of
actual
work
time.
We.
A
A
A
Don't
know
how
2023
is
going
to
be
like,
but
we
should
probably
start
actually
like
writing
down
more
of
the
stuff.
Regarding
how
the
contributor
celebrations
are
organized
and
run
last
year.
It
was
you
know,
kind
of
thrown
together
because
we
didn't
think
we'd
be
doing
another
one
and
this
year
we're
doing
another
one.
A
G
A
G
G
G
G
I'm
actually
going
to
share
my
screen
right
now,
because
I
want
to
show
y'all
some
of
the
stuff
that
we've
got
going
on
and
where
the
help
is
really
wanted,
what
a
one
sec
or
actually
can
you
pass
me
the
potato?
The
share
potato?
G
Yes,
awesome!
All
right
safari
share
all
right,
so
proposal
we've
got
right
here
so
for
contacts
for
folks.
Right
now
we
are
living
off
of
a
google
group
which
is
kubernetes
dash
dev
google,
at
google
groups.com.
G
This
is
where
all
of
our
upstream
news
calendars
documentation,
whatever
it's
shared
with,
we
are
taking
that
to
a
kubernetes
domain,
so
it
would
be
named
here
at
kubernetes.io
with
a
timeline
that's
set
in
here
right
now,
which
needs
approval
and
then
also.
We
also
need
to
talk
about
the
naming
convention
on
this
call
right
now
and
get
some
general
consensus
which
would
be
taken
to
a
mailing
list
for
further
decisions.
G
The
naming
convention
stuff
right
now
to
give
everybody
some
context.
As
I
mentioned
it's
currently
kubernetes-dev
many
folks
have
brought
up
that.
We
should
a
either
shorten
that
or
b
make
it
more
inclusive
or
see
both
and
so
right
now
what
we've
got
going
on
is
what
you
see
on
this
issue.
G
We
can
either
shorten
it
to
dev
at
kubernetes.io
or
possibly
make
it
more
inclusive,
to
talk
about
the
what
and
not
the
who
and
make
it
upstream
at
kubernetes.io,
but
just
some
things
that
we
need
to
be
aware
of
is
one
contributors
at
kubernetes.io
is
already
taken,
and
community
at
kubernetes.io
is
already
taken.
A
G
Yeah
at
least
another
month,
oh
I'm
gonna.
N
G
G
Does
anybody
have
comments
or
suggestions
for
the
name
or
actually
have
any
comments
about
the
process
or
the
migration
in
general?
I
F
I
N
N
It's
kind
of
a
normal
convention
across
a
lot
of
the
cloud
native
projects
and
projects
elsewhere
that
if
you
only
have
one
mailing
list,
it's
often
called
project
name-dev,
and
so
I
bet
there's
a
lot
of
people
who
don't
speak
english
as
a
first
language.
You
don't
even
know
what
the
term
dev
is
short
for
will
nevertheless
recognize
it.
As
you
know,
this
is
the
community
mailing
list
stream.
N
I
think
it's
a
convention,
whereas
I'll
tell
you
from
being
at
red
hat,
which
I
think
was
probably
using
the
term
upstream
before
anybody
else.
I've
run
into
issues
occasionally
with
some
of
our
events
in
non-english
speaking
countries,
where
we've
had
to
use
other
words,
because
the
term
upstream
was
very
confusing
to
people.
G
I
I
G
I
mean
that's,
I
feel
like,
isn't
that
a
moment
to
educate
that
upstream
means
closest
to
the
maintainers
and
downstream
means
closest
to
your
distro.
F
I
guess
the
thing
I
think
of
is
how
often
I
had
to
explain
where
that
came
from
upstream
versus
downstream
to
people
who
maybe
aren't
embedded
in
some
kind
of
engineering
process,
or
had
some
history
like
I
used
to
have
that
a
ton
with
the
docs
teams
that
I
would
work
with,
because
we
used
triangular
workflows
on
git
and
trying
to
explain
why
the
convention
was
upstream
was
always
something
to
take
a
while,
and
I
don't
mind
teaching
it
it's
more
of
a
will.
People
feel
like
this
is
something
they
can
join.
F
A
The
like
community
would
be
my
first
choice
that
are
contributors,
but
both
of
those
are
are
sort
of
already
taken.
Yeah.
A
So,
honestly,
like
right
now
mike
that's
telling
me
to
use
dev.
G
G
Okay,
all
right,
so
that's
so
that's
one
and
then
so
that's
the
one
thing
we
need
to
agree
on.
The
next
thing
we
need
to
agree
on
is
this
timeline,
specifically
the
the
flip
which
I'm
thinking
somewhere
around
january
3rd
or
2nd.
The
second
is
a
sunday.
The
third
is
a
monday.
G
Obviously
I
put
the
10th
in
there
because
I
got
scared,
but
honestly,
this
whole
process
is
so
much
easier
than
what
it
looks
like.
I
promise
you
as
far
as
like
the
creation
of
a
list
and
adding
you
know
and
adding
people
to
it,
and
things
like
that.
I
mean
the
whole
entire
process
in
itself
is
going
to
take
a
few
hours
tops.
So
much
of
this
is
communication
and
getting
other
people
on
board.
A
G
A
No,
but
you
don't
have
to
do
that
from
the
sc
account
you
can
do
that
from
any
account.
That's
has
manager
access
over
the
future
mailing
list.
A
A
I
would
basically
do
it
at
the
cut
the
the
cut
over
because
I'm
sure
some
will
sign
up
like
if
we
did
it
like
today.
I'm
sure
someone
will
sign
up
between
now
and
january
3rd
or
10th,
but
we
can
create
the
we
can
create
the
group
and
stub
it
out
whenever,
as
well
as
like
establishing
the
moderators
and
everything
it's
just
the
you
know,
sinking
of
the
groups
and
turning
off
posting
access
to
the
current
kdev.
G
Right
when
that's
I've
got
turning
off
posting
access
for
them
right
here,
which
is
the
flip.
O
G
K
A
No,
I
can.
I
can
show
you
about
this
like
later,
but
like
yeah,
it's
it's
essentially
just
creating.
Let
me
see.
C
A
Here,
yeah
and
if
you
go,
take
a
look
at
the
like
the
first
one
is
community
and
people
are
listed
as
the
owners
or
managers
and
as
soon
as
the
pr
is
merged,
the
group
will
be
created
and
those
people
will
be
granted
access
to
be
able
to
do.
The
import
and
everything.
G
A
A
G
A
G
G
H
G
Comfortable
with
it,
I
am
and
do
people
what
what
do
people
prefer
for
the
date
flip.
I
actually
looked
at
the
calendar
today
and
the
sunday
is
january
2nd-
and
I
actually
prefer
sunday
for
this,
so
that
it
doesn't
really
mess
up.
Everybody's
work
first
work
day
of
the
new
year,
which
is
the
third
yeah.
A
Honestly,
like
I'm
a
fan
of
getting
ahead
of
it
sooner
rather
than
later,
just
because,
once
the
comms
start
coming
out
regarding
the
1.24
release,
we
will
want
to
make
sure
all
of
that
is
going
to
the
new
mailing
list.
We
don't
want.
You
know
one
post
being
on
the
previous
one
and
another
one
being
on
the
new
one.
G
All
right,
and
then
this
is
where
I
need
just
I'm
gonna.
This
is
gonna,
be
done
today
like
within
the
next
few
hours,
but
I
would
love
for
folks
to
look
at
this.
These
are
all
the
comms
that
are
going
out
and
please
suggest
that
they're,
not
necessarily
in
sentences
yet
but
they're
in
bullets.
G
As
well
as
any
other
sunset
details,
this
will
be
done
today
so
that
we
can
get
this
one
out
today,
which
is
our
intentions
to
kubernetes
dev,
so
yeah.
This
is
our
intentions
and
our
timeline
and
giving
people.
At
least
you
know
a
three
plus
week,
heads
up
three
and
a
half
week,
heads
up
damn
near
a
month.
A
G
Oh
got
that
on
here,
so
that's
the
comms
and
then
the
other
thing
that
we
need
that
we
need
help
with
for
folks
on
the
line
that
would
like
to
chip
in
is
the
stuff
that
goes
live
it's
the
post-migration
before
I
go
live.
So
this
is
the
like.
G
You
know
the
fuzziness,
the
fuzziness
in
between
the
like,
you
know
when
we
get
out
the
the
horn
that
says
that
we're
live,
but
we
need
to
do
a
search
for
all
of
a
doc,
all
the
documentation
that
indicates
kubernetes-dev
and
make
a
pr
to
change
all
that
stuff
to
whatever
that
new
address
is
and
then
also
help
any
leads
that
might
be
still
straggling
for
changing
their
documents
over
and
then,
of
course.
What
else
am
I
missing?
N
G
So
I
don't
see
any
major
fires.
The
major
fires
I
see
are
more
things
like
meeting
meeting
agendas
so
like
going
through
sixth
game
and
making
sure
all
of
the
documents
that
are
listed
in
six
xaml
are,
you
know,
have
the
new
ownership,
I
think
is
super
important,
but
yeah,
no
listing
listing
all
that
stuff-
and
you
know,
helping
us
discover
and
being
being
a
bug
hunter
with
us
is
super-
is
going
to
be
pretty
great.
A
We
we
are
now
down
to
like
it's.
Okay,
it's
the
next
biggest
important
thing,
we're
down
to
seven
minutes.
So,
instead
of
going
through
the
rest
of
the
agenda,
I
first
want
to
call:
does
anyone
have
anything
they
want
to
talk
about
or
should
be
talked
about
now.
G
I
do
I'm
sorry
to
take
up
all
this
meeting
y'all
I
have
so
much
stuff
going
on.
I
also
need
people
to
look
at
the
new
pr
for
the
community
management
lead,
slash,
lead,
moderator
and
then
that's
it
for
me.
I
just
I
wanted
to
talk
about
that,
but
since
we
don't
have
time,
I
need
folks
to
look
at
the
pr
and
also
provide
some
lgtms
for
marquee
as
well.
So
that's
it
for.
J
I
have
I
have
one
thing
about
the
contributor
care
decoder.
The
one
pr
needs
to
be
matched
for
the
scenario
to
what
web
book
has
been
mastered
like
okay,
it's
it's
under
the
mentoring
section,
and
I
I
put
it
on
the
contributor
caterpillar
setup.
J
A
Okay,
I
will
take
a
look
at
that
later.
I
J
A
A
J
We
have
a
doubt
in
the
contributor
side,
I'm
pasting
the
issue
here.
I
just
needed
some
pointers
on
this
issue.
I'd
love
to
work
on
this.
A
A
lot
of
this,
so
you
know
we
can
we
can
flop
on
this.
Some
of
this
stuff
is
like,
like
all
the
devil,
docs
need
to
be
updated
before
they
can
be
imported.
A
A
And
that
is
also
blocked
on.
I
put
a
help
wanted
thing
in
the
contributor
site
section
for
anyone
that
knows
go,
and
preferably
some
regex
and
bash
experience
to
help
with
the
way
the
content
there
is
ingested.
A
It's
it's
had.
Several
people
pick
it
up
and
drop
it,
but
it
would
help
with
like,
instead
of
doing
my
awful
bash
stuff.
J
Actually,
at
present,
I
am
involved
with
that,
and
baron
are
working
on
that
just
two
weeks
before
you
know
us
give
up
on
that
and
we
are
like
collaborating.
A
A
Okay,
cool.
We
have
two
minutes
left,
I
guess
the
only
other
thing
is
easy.
Cla
is
delayed,
we're
going
to
try
and
get
that
up
and
going
again
in
the
new
year.
A
A
And
with
that,
if
there
are
other
items
that
people
wanted
to
talk
about,
please
drop
them
in
slack
or
you
know.
Take
a
look
at
some
of
the
other
notes
that
are
listed
in
there.
A
G
I
was
going
to
say:
I've
got
an
owner's
survey
in
there.
That
also
needs
to
be
reviewed,
and
then
also
I
just
I
just
posted
the
contributor
celebration
stuff
inside
of
kubernetes
contributors
and
slack,
and
we
don't
post
enough
in
there
at
all
hardly
anyway.
So
I
think
we
should
just
post
a
lot
of
stuff
in
there
in
general.
So
folks
want
to
talk
about
their
upstream
adventures
and
that
channel
it's
9.
000
people
go
for
it.
A
Okay,
with
that,
we
are
at
time
I'm
going
to
go
ahead
and
stop
the
recording,
and
we
will
pick
up
in
slack
later
out.