►
From YouTube: [SIG ContribEx] Weekly Meeting 20221109
Description
[SIG ContribEx] Weekly Meeting 20221109
A
Hi
today
is
November
9th
and
welcome
to
the
bi-weekly
contractex
meeting,
just
as
a
regular
reminder,
this
is
a
kubernetes
community
meeting,
which
means
it
follows
the
kubernetes
and
cncf
code
of
conduct,
which
boils
down
to
be
excellent
to
one
another,
and
this
is
also
being
recorded
and
will
be
posted
online
for
future
reference.
So
please
don't
do
or
say
anything
that
you
don't
want
out
there.
A
C
A
D
E
F
A
D
Yeah,
so
community
meeting
is
next
week.
I
was
going
to
be
posting
up
today,
since
it's
about
the
right
time
to
post
up
to
ask
people
for
topics
and
make
sure
everybody
knows
about
it.
The
plan
is,
though,
I
think
we're
going
to
be
talking
a
lot
about
kubecon,
specifically
about
the
contributor
Summit
open
spaces,
so
I'm,
hoping
that
people
who
took
notes
will
be
there.
But
that's
currently
my
update
on
the
community
meeting.
D
D
B
D
B
Yeah
and
so
I
would
actually
say
out
of
those
two.
The
second
might
actually
be
more
important
for
the
community
meeting,
because
if,
if
if
release
is
considering
that
hey
a
bunch
of
stuff
that
used
to
be
available
on
the
official
image
registry
is
not
going
to
be
available
anymore,
then
that's
kind
of
an
important
thing
to
get
into
as
many
forums
as
possible.
Yeah,
because,
among
other
things
now
that
we
actually
have
data
we're
paying
an
absurd
amount
of
money
for
people
to
be
able
to
download
images
for
119.
D
B
D
B
D
B
D
B
D
B
D
Go
talk
to
them
today
or
at
least
leave
the
messages
and
Slack
sounds
good
and
then
for
Open
Spaces
I'm,
going
to
just
put
a
call
out
into
the
various
channels
saying
if
you
were
in
open
space
and
you
took
notes,
would
you
come
lead,
or
at
least
at
least
link
to
where
the
open
space
notes
are
and
tell
people
go?
Read
these
first
we
can
come
expecting
to
discuss.
B
D
B
D
B
B
F
D
B
Yeah
meeting
in
the
collective
leads
leads
are
not
ready
to
set
out
yet
so
and
I
think
it
needs
to
go
with
the
the
existing
leads.
First
Paris
basically
filed
the
issue
because
she's
trying
to
get
everything
out
of
her
personal
to-do
list.
Unless,
because
you
expected
anything
to
happen
immediately,.
A
Sounds
good,
okay,
mentoring!
Do
we
have
any
updates
on
mentoring?
I
know,
meta
contributors
is
now
part
of
officers,
but
we
don't
really
have
folks
from
officers
here
at
yet
so
group
mentoring,
I
I,
reached
out
to
a
few
folks
who
are
part
of
the
CLI
and
apps
cohort.
Just
to
like
ask
what's
up
how's
it
going?
Is
it
still
going
on?
I
haven't
really
heard
back
from
anyone,
so
I
don't
really
have
updates
on
how
it's
going.
B
E
B
E
B
B
E
There
was
a
fair
number
of
that,
but
there
was
also
a
fair
number
of
people
going:
hey
I'm,
already
kind
of
involved,
but
I
don't
really
know
how
to
get
further
and
pointing
out
who
in
the
room,
would
be
a
good
person
to
talk
to
and
what
sigs
they
should
attend
and
et
cetera,
et
cetera.
So
it
was
related,
but
slightly
more
than
the
high
I
want
to
get
involved.
B
B
E
B
A
So
my
my
experience
was
a
little
different,
so
I
was
on
the
community
table
at
the
speed
mentoring
session
and
a
lot
of
the
conversations
we
had
were
around
weren't
around,
like
okay.
How
do
I
get
started
or
I'm
already
part
of
this
like?
It
was
a
lot
of
lot
of
experience
sharing
that
was
going
around.
So
there
was
all
a
lot
of
these
different
perspectives
that
were
coming
in
around
what
their
perspective
of
contributing
looks
like
what
barriers
they've
faced
and
so
on.
So
I
I
didn't
really
I.
A
A
Sent
them
like
are
usually
a
set
of
resources
and
took
it
from
there,
and
that
seemed
to
be
effective
because,
like
these
people
have
shown
like
they've,
come
back
with
questions
and
feedback
and
I
think
this
has
worked
out
slightly
better
than
some
of
my
previous
experiences
with
mentoring,
where
folks
might
not
come
back
a
second
time,
and
things
like
that.
So
this
is
also
like
some.
A
B
A
F
In
hand
with
what
Josh
was
discussing
about
the
CNC
contributor
work
and
the
main
thing
we
are
busy
with
night
and
jaitima
from
the
mainstream
group
redoing
the
CNC
of
mentoring,
Kira
Reaper,
because
at
the
moment
the
repo
is
not
very
user-friendly
for
somebody
that
is
specifically
new
and
wants
to
to
feel
his
way
around.
So
we
basically
busy
breaking
the
repo
in
just
four
specific
groups,
which
is
the
one,
is
the
main
T.
F
The
mentor
then
also
a
project
area
where
all
the
working
documents
and
the
projects
and
information
about
projects
and
all
that
go
and
then
the
fourth
section
would
be
the
mentoring
working
group
admin
where
the
community
meeting
information
and
everything
about
them.
The
working
group
itself
goes
so
the
idea
is,
then,
if
a
main
d
goes
to
the
the
repo
there's,
a
section
that
says
menti.
This
is
the
timelines.
This
is
the
the
type
of
programs
you
can
get
involved
with.
F
This
is
how
explaining
the
whole
process
through
the
mint
is,
and
hopefully
it
will
make
the
questions
that
we
get
about.
Where
do
I
start
easier
and
we're
also
doing
a
lot
of
FAQs
that
we
can?
It
would
be
great
once
we
got
the
repo
reorganized
to
get
everybody
that
think
of
another
FAQ
to
add
those
in
and
Bolt
the
information
there.
So,
but
it's
not
a
long
way
to
go
at
the
moment
there
is
a
V2
branch
on
the
main
repo.
F
F
I
think
that
is
for
the
sensitive
serving
the
kubernetes
community.
So
it's
the
the
reorganize
is
not
specifically
focused
on
on
the
kubernetes
part,
but
it's
as
a
service
to
the
kubernetes
community
as
a
whole.
Yeah,
oh,
the
whole
cncf
community.
So
if
there
is
since
given
any
specific
projects
or
things
that
we
want
to
add
to
the
repo
I
think
that's,
that
would
also
be
a
good
idea
if
we
want
to
highlight
things
there
specifically
under
kubernetes,
because
it's
it's
a
CNC
overall.
B
F
What
what
what
we
try
to
avoid
is
duplication
and
just
off
the
top
of
my
head
would
be
less
less
than
earn
it
in
kubernetes.
But
absolutely,
let's
have
a
link
there.
Yeah,
let's
say:
if
you
don't
want
to
get
involved
in
outreachy
season
of
dogs
or
any
only
other
projects,
here's
the
kubernetes
link
and
then
you
can
go
there
and
then
also.
It
would
probably
good
to
streamline
what
the
cncf
mentioning
site
says
about
getting
involved.
A
A
E
A
Yeah,
it
did
so
specifically
so
the
way
we
talked
about
non
code
is,
we
talked
about
it
in
a
slide
under
the
how
to
contribute
section.
So
we,
the
entire
quantity
back
session,
was
around
like
okay.
These
are
some
projects.
These
are
the
updates
that
we
have
and
then
in
the
how
to
contribute
section.
It's
like
okay,
it's
not
just
this,
there's
a
huge
other.
A
There
is
all
of
this
other
aspect
of
it
that
you
can
contribute
to,
but
I'm
not
sure
if
we
were
able
to
imbibe
any
specific
points
that
you
had
mentioned
like
because
I'm,
or
at
least
I
wasn't
there
for
the
for
that
meeting.
But
we
lived
off
for
a
significant
amount
of
time
about
non-core
contributions
and
how
to
get
involved
there.
So
I
don't
know
if
that's
what
you
asked
but
sorry
well,.
E
E
A
E
C
B
E
I,
don't
know
if
that's
necessarily
where
the
non-code
meeting
is
going
to
go
is
to
onboard
the
non-code
contributors
themselves,
yet
yeah.
Our
our
primary
effort
right
now
is
around
the
non-code
initiatives
and
working
on
the
initiative,
as
opposed
to
onboarding
people
into
the
initiative.
Okay,
if
that
makes
sense,
yeah
but
I
think
kdev
is
probably
I'll
work
with
columns,
because
I
think
kdev
is
the
way
to
go.
Okay,.
A
Sounds
good
also,
maybe
since
Noah
this
was
a
really
good
point
to
bring
up
in
the
session,
but
like
we
dropped
the
ball
on
this,
maybe
it
would
be
nice
if
we
can
like
share
the
contracts,
maintain
a
slides
with
the
contractex
mailing
list
once
before,
but
it
is
like
sometime
before
the
session,
to
like
get
feedback
in
order
to
try
and
avoid
some
of
this
slip-ups
next
time.
That's.
B
A
A
I
do
have
a
few
tasks
that
have
been
like
playing
around
with
it's
on
me
to
like
write
it
up
document
it
so
that
it
becomes
consumable
and
accessible
to
other
people
who
want
to
get
started.
So
I
I'll
spend
some
time
on
that
see
if,
like
see,
if
I
can
document
that
a
little
more
and
like
send
it
out.