►
From YouTube: [SIG ContribEx] Weekly Meeting for 20220216
Description
[SIG ContribEx] Weekly Meeting for 20220216
A
A
Christian
will
be
here
taking
over
as
host
a
little
housekeeping
before
we
begin,
we
abide
by
a
code
of
conduct
which,
in
short
means
be
excellent
to
each
other
and
without
further
ado,
make
sure
you
put
your
name
in
the
meeting
notes,
I'm
going
to
chuck
the
meeting
notes
down
here
and
yeah
with
that.
Let's
get
right
into
it.
First
up
eddie
had
a
query
and
it's
not
in
the
agenda
but
I'll
write
that
down.
B
I
put
it
at
the
very
bottom,
so
hopefully
real
quick.
Last
year
I
talked
to
paris
and
a
few
others.
We
as
sig
leaves
and
chairs,
and
you
know,
contributes
and
whatever
we
should
have
a
way
to
get
kubecon
tickets
for
like
active
contributors
that
need
one.
So
I
just
want
to
bring
that
up
again.
I
don't
know
who
to
talk
to
who
to
coordinate
with,
but
like
cmcf
should
definitely
give
us
a
pool
of
tickets
that
we
can
distribute.
B
A
B
A
So
my
gut
feeling
on
this
because
it
kind
of
falls
into
a
bit
of
a
there-
is
a
transaction
kind
of
thing.
I
think
this
should
also
kind
of
be
brought
to
the
attention
of
kind
of
steering,
maybe
because
it
affects
everyone
in
the
project,
and
perhaps
we
will
ping
we'll
be
good
to
reach
out
to
cncf
as
well,
but
yeah.
I
would
have
a
chat
with
some
of
the
other
contrabex
leads
and
I'll
keep
tabs
on
this
I'll.
Keep
you
all
updated
yeah,
but
it
should.
A
A
B
C
Yeah
we
need
it,
we
need
a
a
process
for
it
right
now
and
I
need
to
continue
to
ask
steering
to
get
with
cncf
to
figure
this
out.
So
that's
where
we
are.
There
is
an
open
issue
too
that
we
do
update.
So
let
me
get
it
out
and
then
y'all
can
follow
that
along
I'll
bring
this
to
the
next
steering
committee
meeting
to
see
where
our
blockers
are
and
if
we
need
any
help
from
y'all,
we'll
ask.
A
So,
yes,
I
will
say
my
words
and
whoosh
so
contributor
summit.
It
is,
it
is
happening.
You
know
we
need
to
start
a
meeting
to
discuss
logistics
if
someone
could
spin
up
a
doodle
and
post
it
in
the
contributor
summit
channel
on
slack.
That
would
be
great
logistics
to
be
discussed
content.
It's
probably
going
to
be
the
same
as
north
america.
A
It's
going
to
be
chill
out
space
just
because
there's
some
uncertainty,
but
this
could
be
this.
This
is
subject
to
change
after
we
have
our
first
meeting
and
we
kind
of
discuss.
What's
going
on,
you
know
website,
we
should
probably
create
a
save
to
date,
page
if
and
documents
in
the
community
repo.
Now
this
has
been
on
my
radar
for
weeks,
but
tonight
I
will
get
something
pr'ed
in.
A
I
will
get
a
pr
up
with
details
about
the
contributor
summit,
with
the
space
that
we
have
and
the
dates
and
all
that,
so
we
should
be
able
to
get
that
on
the
ball,
especially
we're
in
february.
Valencia
is
in
very
much
april
may
so
it's
a
couple
months
out
so
yeah
we've
got
we've
got
time,
but
the
window
for
we've
got
time
is
closing
very
soon
like
so
this
this
week.
A
D
E
D
C
David,
I
was
on
today
david's,
not
here.
There
is
a
lot
of
updates
here,
which
is
that
david
and
carlos
carlos
is
going
to
be
hosting
office
hours
now
as
well,
david
and
carlos
are
looking
into
taking
the
whole
entire
program
to
cncf
and
not
necessarily
contributes
anymore,
since
this
is
sort
of
like
outside
of
our
scope
and
it's
better
suited
for
that
level,
and
also
just
like
the
sustainability
reasons.
C
We
are
not
there
yet,
though,
and
it's
not
going
to
be
official
until
we
actually
migrate
the
documentation
over
that's
sort
of
what
I'm
that's
my
milestone
in
my
head
of
when
we're
done
with
this.
So
once
we
can
migrate
documentation
out
of
the
kubernetes
repository
that
has
to
do
with
the
operational
elements
of
office
hours,
then
it'll
officially
be
a
cncf
thing.
D
C
Yeah
yeah,
and
if
you
chris,
if
that's
something
you
want
to
help
advocate
for
too,
please
help
yeah
the
more
people
we
have
the
better
but
yeah
just
trying
to
figure
out
where
that
lives-
and
I
was
on
this
morning
preaching
the
good
word
of
contrebex
and
trying
to
get
more
contributors,
especially
for
some
of
the
engineering
projects
that
we
have
with,
like
all
the
migration
work
and
the
automation
work.
That's
going
on.
So
that's
it
for
office
hours.
F
G
So,
yes,
we
are
seriously
doing
it
this
month,
despite
all
kinds
of
randomness,
but
we
will
have
a
the
meeting.
Invite
is
out
it
should
have
just
gone
out
before
this.
So
thank
you
to
bob
for
getting
that
that
issue
handled
so
you'll
be
able
to
find
that
on
your
calendar
moving
forward,
nigel
will
be
our
host,
so
yay
nigel
and
nigel
has
an
email
request
out
to
get
an
email
out
to
kdev.
G
I
think
we're
supposed
to
do
that
through
the
forum
now,
unlike
before,
where
it
was
just
random
emails
and
wild
west.
So
that's
that
thank
you
for
the
tweets
and
we're
very
excited
over
those,
and
we've
got
three
major
topics.
Well,
three
plus
a
little
bit.
I
guess
I
should
say
we
have
the
docker
shim
removal
topic.
We
have
the
reliability
bar
proposal
topic
and
we
also
have
some
updates
on
1.24
and
there
will
be
a
very
very
brief.
Yes,
we
move
k,
dev
yay
from
from
paris.
G
So
those
are
the
updates
on
what
we're
doing,
and
there
is
also
now
a
form
where
people
can
propose
topics
and
just
tell
us
what
topic
it's
going
to
be
when
they
would
like
to
present
it
and
who's
going
to
be.
The
expert
on
said,
said:
community
meeting
just
to
help
the
discussion
along,
I'm
still
trying
to
figure
out
how
I
get
that
just
in
the
contrabex
google
drive.
G
C
G
C
C
Issue
like
an
issue
template
on,
I
don't
know,
that's
that's
what
I'm
thinking
about,
but
yeah
we
also
do
have.
We
do
have
a
drive
that
we
can.
We
would
set
it
up
for
you
and
then
we
could
set
you
as
the
the
editor,
so
just
yeah,
just
you
can
put
in
a
so
yeah
the
second
case
scenario
or,
like
the
now
scenario,
just
put
in
an
issue
that
says
that
you
need
a
form
from
created
from
the
drive
with
you
as
an
editor.
G
C
C
G
F
H
H
G
D
F
I
think
so
I
think
there's
there's
still
a
few
other
things
that
like
I,
I
need
to
definitely
like
go
through
the
agenda
again
rehearse
the
spiel
at
the
beginning
again
and
I'm
running
a
community
meeting
for
my
project
here
in
an
hour
or
so
so
yeah.
I
think
I
think
everything
will
be
fine.
All
right.
E
D
F
G
Cool
you're
going
to
be
just
fine,
I
will
say
so:
I'm
going
to
be
on
to
be
the
recorder
and
the
usher.
If
somebody
else
would
also
like
to
join
in
to
help
with
note-taking,
I'm
sure
that
would
be
immensely
helpful
if
anybody
would
like
to
just
kind
of
show
up
and
say
I'll,
do
it,
but
yeah
so
and
you've
got
you
also
track
down
all
the
people
that
need
to
talk
about
the
things
so.
C
C
G
A
G
D
C
Yes,
well
now
that
we
know
that
the
calendar
is
unjammed
for
the
dev
list
that
we,
because
we
did
the
obviously
did
the
test
this
morning
with
the
the
community
meeting.
So
I
definitely
think
we
should
kick
up
meet
our
contributors
again,
but
I
wanted
to
discuss
here
a
little
bit
about
the
sustainability
of
the
program,
because
it
is
a
it's
definitely
a
intense
gathering
and
preparation
of
it.
I
would
say
it's
not
hard,
so
it's
great
for
new
contributors
who
want
to
kind
of
help
out.
C
The
problem
is,
though,
the
how
long
it
takes
you
to
do.
One
individual
monthly
episode
is
at
least
five
hours,
which
is
a
long
time,
and
the
other
thing
is
now
that
we
have
office
hours,
kicking
back
up
again,
they're
doing
a
new
format
and
the
new
format
includes
a
contributor
at
the
beginning
of
it
talking
about
what
they're
working
on.
So
there
is
sort
of
a
meet
the
maintainer
slash,
contributor,
vibe,
already
going
on
there.
C
The
goal
of
the
group
or
excuse
me
the
session
for
meet
our
contributors
was
really
rapid
fire
q,
a
as
it
go
as
it
relates
to
mentoring.
People
always
say:
oh,
I
need
a
mentor
right
and
a
lot
of
the
times.
I
just
need
someone
to
ask
quick
questions
too
and
get
feedback
on
that.
So
that's
where
this
whole
thing
cut
became
in
because
one-on-one
doesn't
scale.
So
my
thing
is:
should
we
continue
to
do
this?
C
C
C
G
E
C
I
will,
I
will
tell
you
what
the
heck
we
just
talked
about,
because
I
know
we
have
a
full
agenda
and
we
need
to
go
on.
We
need
to
press
on
so
I
will
get
with
you,
because
it's
about
office
hours
and
maybe
combining
office
hours
with
a
program
that
we
also
do
called
meet
our
contributors,
which
is
kind
of
what
you
did
this
morning.
Remember
with
me,
yeah.
C
D
C
I
think
that
would
be
amazing
for
this
project,
because,
right
now
we
do
it
very
ad
hoc
and
eeyore
out
of
the
kindness
of
his
heart,
because
he
does
lfx
stuff
has
been,
has
been
kind
of
handling
a
lot
of
it.
So
I'm
wondering
if
it's
something
that
we
need
to
make
more
formal
within
the
sig
as
a
role
so
thoughts
on
that.
I
know
debbie.
I
Got
some
thoughts
I
had
a
discussion
regarding
this
like,
like
six,
were
not
getting
the
dates,
often
to
submit
the
proposal.
So
we
had
a
discussion
on
this
in
the
upstream
marketing
team.
So
we
have
a
umbrella
issue
on
the
board
like
reaching
out
to
six
to
submit
the
proposals
before
the
dates
and
use
slack
bots
to
to
means
inform
them
about
the
deadlines
of
v8,
lfx
or
gsoc
when
it
happens
in
the
cycle.
I
I
C
Yeah
and
I'm
thinking
full
life
cycle
too,
so
I'm
not
just
thinking
like
the
the
management
of
the
outreach
which
is
kind
of
where
you're,
where
you're
coming
from
right.
Now,
I'm
also
talking
about
even
the
proactive
like
managing
of
things
that
they
see
that
could
be
internship
projects
and
then
also
managing
the
interns,
while
they're
here
to
make
sure
that
they're
good,
which
is
something
we
don't
do
a
lot
of
yeah.
C
I
D
D
F
The
short
version
is,
work
has
been
bananas
and
I
am
very
far
behind,
but
the
the
action
item
right
now
is
to
create
an
umbrella
issue,
and
in
the
process
of
that
I
had
an
idea
of
some
other
stuff
that
I
needed
to
test.
That
may
be
a
lot
less
work,
so
hopefully
this
week
I
will
have
time
to
test
it
and
see
if
that
works,
and
if
it
does
then
great
either
way.
An
issue
is
going
to
be
open
that
captures
all
of
the
issues
that
have
already
been
opened.
F
F
D
D
I
D
Yeah
like
what
to
do
because
there's
so
many
shadow
applicants,
we'll
say
nowadays
that
there's
places
we
could
direct
them
where
they
could
help
right
so
or
other
programs,
if
they're
new
to
the
community
right,
if
they're,
not
already
an
org
member,
say
we're
going
to
do
something
around
that
good
point.
Yes,.
D
K
K
We
decided
to
try
a
different
process
and
we
created
a
google
doc
with
the
changes
that
we
wanted
to
make,
and
it
was
a
it
was
a
poor
choice
because
we
ended
up
having
to
go
through
this
horrible,
google,
doc
markdown
conversion
thing
that
ended
up
creating
just
the
world's
largest
diff
for
some
of
our
markdown
files.
But
we
do
have
a
pr
in
and
it's
it's
getting
some
attention
and
we
have
a
couple
more
documents
that
we
went
through
that
process
with.
K
So
that's
almost
done
we're
going
to
be
working
on
a
pretty
big
kind
of
restructuring
of
the
help
wanted
guide
to
to
kind
of
drive
new
contributors
into
or
new
contributors
and
existing
contributors
into
the
path
that
they
that
would
be
most
helpful.
We
had
a
long
conversation
with
paris
about
different
approaches.
That
would
be
more
helpful
with
that,
so
that's
kind
of
where
that
is
the
developer
guide.
K
I
think
I
reported
on
this
last
time
we
looked
at
the
developer
guide
and
it
hasn't
really
changed
a
whole
lot
since
the
last
time
that
joel
and
I
went
through
and
rewrote
a
bunch
of
stuff,
which
was,
I
think,
a
year
ago
or
a
year
and
a
half
ago.
So
I,
if
people
have
feelings
about
more
stuff
that
needs
to
change
in
the
developer,
guide
or
more
things
that
need
to
be
updated.
I
would
really
love
to
hear
that.
I
think,
where
we
kind
of
got
where
we
sort
of
ended
things.
K
Last
time
we
worked
on,
it
was
running
into
all
of
the
sig
documentation.
That
is
underneath
the
developer
guide
and
there's
a
there's,
a
very
old
stale
issue
out
there
asking
all
of
the
sig
leads
to
look
at
their
developer
guide
stuff,
and
I
think
some
some
progress
may
have
happened
on
that,
but
not
a
whole
lot.
So
I'll
have
to
look
at
that
and
see.
D
H
K
K
K
H
F
H
K
F
H
K
J
D
J
C
J
C
J
C
K
J
C
K
A
K
K
C
D
J
And
basically,
people
click
a
button
edit
something
and
they
they
get
a
preview
of
like
what
the
changes
were
yeah
in
a
link.
Okay,
I
don't
want
to
take
a
lot
of
time.
Sorry,
oh
you're,
fine.
The
other
thing
was.
I
was
trying
to
add
something
to
the
agenda,
but
I
don't
have
a
way
to
add
something
to
the
agenda.
Do
I
need
to
belong
to
a
google
group
or
join
a
google
group
or
which
google
group
do
I
join.
I
don't
know.
C
C
J
J
D
D
J
Okay,
it's
not
vendor
specific.
I
can.
I
can
drop
the
link
and
you
can
see
the
books.
We
did
production
kubernetes.
That
was
a
free
book
so
anytime
that
if,
if
there's
a
free
book,
we'll
pick
the
free
book
so
with
the
production
kubernetes
that
was
free,
97
things
that
sre
needs
to
know.
That
was
free.
The
one
that
we're
doing
now
is
production,
networking
and
kubernetes
that's
from
john,
and
that
was
not
available
for
free.
J
D
J
C
Cncf
is
a
perfect
home
for
this,
like
it's
the
same
exact
problem
that
we
have
with
office
hours,
where
it's
just
not
necessarily
our
audience
100
right
and
we
don't
necessarily
have
the
people
to
do
the
maintenance
on
it,
and
I
know
you're
going
to
say
you're
going
to
you're
doing
the
maintenance,
but
there's
also
the
maintenance
of
the
infrastructure
and
everything
like
that.
That
is
involved
with
it.
C
And
so
that's
why
we're
looking
for
a
home
for
office
hours
too.
So
I
think,
wherever
we
find
a
home
for
office
hours,
we
should
also
find
a
home
for
the
book
club
because
they
go
hand.
It
sounds
like
they
go
hand
in
hand
almost
because
it's
downstream
users
looking
for
support
in
some
kind
of
way,
whether
that's
like
enrichment
through
learning
or
troubleshooting
right.
This
is
something
that's
actually
been
brought
up
so
many
times
within
this
project,
as
far
as,
if
we
don't
have
a
sig.
C
J
Came
yeah.
I
came
to
this
sick
because
it
was
the
only
thing
close
like
contributing
experience,
but
I
think
this
thing
is
focused
on
finding
contributors
right
and
supporting
the
contributors
to
kubernetes,
and
these
two
programs,
the
office
hours,
that
I'm
involved
in
the
book
club
are
more
advocacy,
like
you
said,
like
community,
for
users
finding
finding
help
to
learn
about
kubernetes.
I
think
that's
that
would
be
a
stick.
It
could
be
a
cncf
thing
also.
J
C
L
L
J
C
J
Yeah,
and
mainly,
is
to
if
I'm
not
here
somebody
else,
I
can
grow
all
their
hosts
right
and
the
book
can
continue
exactly
the
same
thing:
we're
doing
with
office
hours
right,
dave
kind
of
like
passenger
button
to
me.
So
I'll
do
yeah
I'll,
do
office
hours
for
a
year
right
and
see
if
somebody
else
can
pick
it
up
next
year.
I.
D
C
J
Guys
it's
not
it's
not
a
a
lot
of
it's.
If
we
do
the
automation
for
adding
people
to
the
mailing
list,
the
the
thing
to
run
it
is
like.
I
don't
want
to
take
a
lot
of
time.
It's
like
basically
to
help
people
finish
the
books,
a
lot
of
people
buy
books
or
know
people
that
wrote
a
book
and
then,
when
you
go
to
keep
considering
hey
how
you
doing
and
the
person
asks
like.
J
So
this
way
right,
I'm
saying
like
we
didn't
this
time
is
six
weeks
and
like
every
week
I'm
selling
we're
in
chapter
three
we're
in
chapter
four
chapter
six
and
then
we're
done
and
everybody
read
the
book.
We
move
to
the
next
book
and
we
get
through
all
the
books
this
year
that
we
want
to
that's
all
cool.
D
C
All
right
we
need
so
many
more
maintainers
y'all
help
us
grow
this
sig,
so
that
that's
my
that's
my
end.
My
end
is
we're
not
gonna
all
be
here
forever.
Just
like,
I
said
the
carlos,
and
we
have
so
many
holes
right
now
in
some
of
our
sub
projects
with
ownership
so
yeah
if
y'all.
Another
thing
is
too.
If
anybody
is
listening
and
needs
help
with
their
employer
and
getting
support
to
do
this
stuff.
I
want
you
to
call
me.