►
From YouTube: [SIG ContribEx] Weekly Meeting for 20220608
Description
[SIG ContribEx] Weekly Meeting for 20220608
A
Hello,
everyone
and
welcome
to
the
june
8th
sig
contributor
experience
meeting.
I
am
your
host
today
bob
one
of
the
co-chairs,
also
known
as
mr
bobby
tables.
As
a
general
reminder,
these
calls
are
recorded
and
we
abide
by
the
cncf
code
of
conduct,
which
essentially
boils
down
to
please
be
excellent
to
each
other.
A
A
D
If
I
can
find
my
unmute
button,
that
would
be
a
good
start,
so
we
did
not
have
the
may
community
meeting.
I
don't
remember
if
we.
D
A
D
And
I
was
out
for
that.
So
that's
why
I
can't
remember
anything.
Yes,
so
we
did
not
have
a
meeting
in
may
and
then
june
is
coming
up.
I
have
not
had
anyone
volunteer
any
topics
lately,
so
I'm
probably.
B
D
I
I
did
have
a
volunteer
to
help
host
in
in
a
dm,
so
I
probably
will
reach
out
to
that
person
and
have
them
host
if
they're
still
available
to
do
it,
but
if
people
can
be
ushers
and
recorders
just
to
make
sure
and
anyone
feeling,
like
being
a
note
taker
would
probably
be
helpful,
but
I
think
the
bigger
thing
right
now
is:
I
don't
know
if
there's
any
topics,
because
we
have
the
freeze
and
everything
going
on
just
no
one's
volunteered
anything.
So
I'm
gonna
start
poking
the
dragon
around.
If
there.
F
F
D
If
you
would,
that
would
be
amazing,
they
can
just
dm
me
and
say
yes,
I
will
happily
talk
about
said
topic
and
I
can
leave
them
from
there.
That
would
be
awesome
if
they're,
actually,
you
know
also
not
going
to
be
at
open
source
summit
like.
E
A
Report
summary
will
be
good.
I
actually
like
in
the
steering
meeting
on
monday,
like
I
think
I
wrote
that
down
as
an
item
to
put
on
the
the
community
meeting
for
next
month.
Oh
perfect,
so
yes.
D
So
good
call
out,
we
can
just
do
two
topics,
even
because
I
don't
know
how
many
folks
are
going
to
be
attending
this
this
month
right
but
yeah.
So
that's
the
updates
about
the
community
meeting.
I.
A
Something
else
to
potentially
bring
out
during
kubecon
we
had
interesting
new
yep,
so
cc
would
be
great
to
have
on
there
to
give
a
update
on
the
release.
A
The
oh
so
sorry
at
kubecon
the
meeting
the
sessions
weren't
recorded
just
because
we
had
no
idea
in
logistics.
Anything
like
that,
but
there
was
a
very
good
discussion
on
reliability
and
sustainability
and
there
were
a
couple
action
items
that
came
out
of
that.
A
So
it'd
be
great
to
sort
of
bring
some
of
this
up
with
the
broader
community.
Just
for
the
record
here,
the
three
action
items
were
to
create
a
report,
so
this
is
essentially
dev
stats
that
would
track
kind
bug
and
triage
accepted,
so
things
that
we
recognize
are
issues
that
aren't
getting
handled
so
like
essentially
signal
maintainer
signal,
better
code
coverage
reporting
and
then
bringing
up
more
formal
mentoring
and
trying
to
get
more
groups
involved
with
that,
like
I
know,
sixth
seal,
I
just
kicked
something
off.
A
Okay,
but
it'd,
be
it'd,
be
good
to
sort
of
bring
this
up
and
rehash
those
things
with
the
community
at
large.
That
could
not
be
at
kubecon
in
person.
D
D
A
A
D
G
Be
a
thing
to
join
in
like
start
up
with
the
annual
report
and
then
pop
into
that,
because
I
think
you
know
it'll
probably
be
a
natural
lead-in,
yeah
yeah.
G
D
A
D
D
So
we'll
probably
do
release
lead,
release,
lead
registry
annual
reports,
reliability,
discussion
from
kubecon
and
the
action
items
that
came
out
of
it
yep.
E
But
the
the
registry
change-
that's
not
like
a
breaking
like
docker
shim
thing
right,
that's
just
like
hey.
Do
us
a
favor?
Yes,
okay,.
B
B
Oh
by
the
way,
we're
having
the
the
contributor
summit
retro
from
europe
on
monday
at
7
pm
european
10
a.m,
pacific!
If
anybody
wants
to
be
in
for
that-
and
that
should
certainly
include
anybody
who's
going
to
be
on
the
north
america
team,
yep.
A
A
It'll
have
to
be
definitely
pushed
back
a
little
bit.
The
the
tail
dr
is
like
jeff
and
myself
are
going
to
be
leading
it,
and
I
have.
I
have
had
a
permanent
conflict
with
that
meeting
at
that
time
slot,
so
that
definitely
will
not
be
be
that
exact
same
one,
probably
just
a
little
bit
later
in
the
day,
like
30
minutes,.
A
Mine's
a
steering
meeting,
so
I
can't
really
skip
that,
but
yeah
I'm
expecting.
I
will
probably
start
you
know
sending
out
the
call
for
volunteers
and
things
like
that
within
the
next
two,
like
essentially
by
the
next
kendricks
meeting.
A
We
are
expecting
this
to
be
a
true
return
to
form
for
those
that
didn't
potentially
catch.
There
was
like
15
1
550
ecfp
submissions,
which
is
roughly
250
more
than
the
last
previous
highest
kubecon.
A
C
A
E
A
It
is
the
highest
it
is
the
highest.
It
was
250
more
submissions
than
the
last
highest
one
wow,
so
that
plus
hotels
being
sold
out,
probably
going
to
be
a
lot
of
people
there
yeah
with
that
again
true
return
to
forum,
we'll
be
going
back
to
like
what
we've
done
in
summits
previously
like
2019
and
earlier
with
more
formal
cfpe
tracks,
and
things
like
that.
I
do
still
like
unconference.
A
I
still
think
we
should
do
but
we'll
we
definitely
want
to
to
have
curated
content,
especially
on
things
with
people
growing
in
the
maintainer
roles.
Other
big
thing
is:
this
is
a
general
reminder.
There
will
be
no
new
contributor
workshop
during
the
summit
that
has
not
worked
out
well
for
us
in
the
past.
A
It
will
just
be
you
know,
essentially
cubase
or
members
and
sponsored
attendees.
I
don't.
I
don't
want
to
use
this
entire.
You
know
meeting
for
talking
about
the
summit,
but
just
like
sort
of
setting
the
stage
a
little
bit
for
it,
for
you
know
before
we
start
kicking
off
playing
and
all
that
yeah.
E
A
We
want
to
have
it's
just
like.
Essentially,
the
audience
is
people
that
are
already
org
members
right,
people
that
have
some
have
some
commitment
to
the
project
already
sure
sure.
C
Maybe
but
I
mean
that
doesn't
mean
we
can't
have
a
side
room
with
just
one
thing:
yeah,
I'm
talking
about
doing
well,
yeah.
A
We'll
still
be
doing
meet
our
con,
like
not
your
contributor,
it's
the
the
sig
meet
and
greet
during
the
event.
That's
been
very
successful.
Right
josh.
I
think
you
were
also
talking
about
potentially
doing
a
tldr
version
of
the
contributor
summit.
Not
during
the
the
summit
day
you
mean
the
new
contributor
introduction,
yeah.
B
Yeah
people
kick
that
around
it's
going
to
depend
on
people,
volunteering
to
staff,
it
of
course,
but
yeah
doing
this
sort
of
non-interactive
or
minimally
interactive
basics.
E
Yeah,
I
I
just
yeah,
I'm
just
a
huge
proponent
of
us
doing
something
that
is
like,
maybe
not
a
part
of
the
contributor
summit,
but
something
at
cubecon
at
large
to
bring
in
folks
that
this
is
my
first
cubecon
I
don't
know.
What's
going
on
like
well
we'd
love
to
have
you
as
part
like
how
do
we
start
that
pipe?
What's
up
my
first.
E
A
A
I
could
literally
predict
with
100
accuracy
that
stuff
the
people
that
had
like
that's.
Why
we're
doing
the
new
contributor
course
that
people
can
do
like
on
online
and,
like
I
think,
a
tldr,
you
know
we
can
still
do
a
tl,
dr
version,
but
like
we
should
not
pour
the
resources
that
we
used
to
pour
into
it.
Yeah.
B
And-
and
that
was
why
I
was
thinking
something
that's
like
maybe
an
hour
and
a
half
yep
yep,
the
that
said,
I'd
really
like
to
it's
dependent
on
other
people
being
enthusiastic
about
carrying
this
out,
because
emily
fox
co-chair
of
kubecon
has
made
noises
about
drafting
me
into
another
thing
that
would
preclude
my
being
leading
in
an
activity
like
that.
A
Something
else
that
we
can
keep
in
our
back
pockets.
I've
talked
to
github
about
this.
A
A
B
A
That
is
not
under
consideration
for
at
a
that's
here.
Cool
the
hard
part
is
many
of
us
also
have
vendor
commitments
and
like
it,
we've
already
had
difficulties
with
it
just
being
one
day,
the
the
other
alternatives
to
try
and
push
it
like
earlier
in
the
week
like
sunday
but
yeah.
I
I
don't
know
it's
something
we
can
think
about
more
for
next
year.
H
I
recall:
we've
also
discussed
having
it
as
a
completely
separate
off-cycle
event,
sort
of
a
kubecon.
A
B
B
A
Yep
and
in
fact
they
told
us
like
steering
and
the
openstack
tc
meet
on
a
regular
cadence
and
they
also
advised
against
it.
So
I
don't
think
we'll
be
doing
a
a
separate
thing.
At
least
a
separate
large
thing.
A
A
Any
other
summit
related
items.
Sorry,
okay,
steering
election.
It's
worth
it
to
start
thinking
about
this
soon
josh
is
like.
Have
the
bugs
been
worked
out
with
alecto.
B
Yeah,
so
what
electo
is,
is
we've
completed
the
work
on
making
it
more
secure
and
transparent
thanks
to
our
intern
vedant?
So
he's
finished
his
internship
and
we
got
all
of
those
things
finished.
B
B
A
B
The
and
and
you
know-
and
I
have
to
preserve
the
history
of
the
elections
for
the
other
two
users.
So
if.
B
B
But
at
least
having
somebody
to
review
my
code
would
be
good,
even
if
he
doesn't
find
any
bugs
so,
okay,
the
yeah,
and
because
we
have
to
create
the
election
sub
project.
And
then
the
election
sub
project
needs
to
make
recommendations
for
the
new
election
committee,
which
will
in
needs
to
include
one
of
either
noaa
or
haslam.
Were
you
in
the
election
committee
last
time?
It
feels
like
it's
been
forever.
No
do.
B
A
Something
else
actually
dims
volunteered
to
also
be
on
the
election
committee,
because
he
cannot
run
again.
Okay,.
B
That
would
be
awesome.
The
so
oh
allison
was
the
election
committee
last
time.
So
noah
needs
to
be
in
the
election
committee
this
time.
Okay,
so
because
he'll
be
the
only
continuity
person,
the
so
and
I
need
to
not
be
on
it,
because
I
need
to
not
be
on
it.
The
the
the
only
election
committee
I
was
not
on
was
the
first
one,
so.
B
A
I
think
that
is
it
regarding
steering
election
updates.
Oh
there,
as
other
election
updates,
not
steering,
is
steering
will
be
voting
on
code
of
connect
committee
soon,
so
there'll
be
a
call
for
people
that
want
to
volunteer
for
the
code
of
kind
of
committee
going
out
sometime
soon-ish,
because
I
think
that
starts
in
july.
Okay,.
B
A
Cool
any
other
election
related
items
at
this
time.
A
Okay,
that
takes
us
to
mentoring,
meet
our
contributors
still
on
hold
new
computer
workshop.
We
kind
of
talked
about
that
a
little
bit
already
eric
are
the
the
the
two
tech
writers
that
have
been
working
with
us
in
the
past
are
gonna,
be
starting
working
on
that
course
soon.
A
Group
mentoring:
I
think
the
only
update
on
this
one
is
the
cigabs
and
six
cli
combo
one
there's
an
open
issue
and
k
community
asking
people
are
interested
in
that.
I
think
that's
the
the
the
only
update
on
the
group
mentoring
thing
right
now:
debba.
J
Yeah,
so
I
missed
out
a
few
of
the
graduated
athletics
to
know
what
was
the
experience,
so
some
of
them
asked
like
if
we,
if
our
communities
give
some
projects
likes
or
not,
because
I
remember
when
I
was
a
mentee
with
my
organization-
it's
a
common
practice
with
cnc
fox
to
provide
them
some
swags
for
the
contribution
they
do.
A
So
for
any
swag
requests,
it
just
goes
to
the
contrabex
leads
and
because
we
have
a
pool
of
various
codes
and
things
like
that
available
of
different
items.
J
Okay,
so
so
do
I
now
need
to
reach
out
to
the
leads
saying:
hey:
these
are
the
graduate
mentees
and
now
we
need
some
slides
yep.
A
So
essentially
it's
like
ping,
me
ping.
You
know:
okay,
kristoff
nikita.
We
all
have
access
to
the
same
spreadsheet
for
swag
codes.
Oh
cool
I'll
pick,
you,
okay!
J
Yeah,
so
it
was
regarding
mnd,
so
we
just
you
know
mother
said
they
will
take
care
of
that.
But
for
others
like
there
are
six
mentees
who
graduated
from
community
at
this
time.
So
two
of
them
raised
out
like
hey.
Is
there
anything
available
or
not?
That's
like
clickbait.
A
Yep,
just
you
know
pick
me
up
like
if
you
want
to
either
open
an
issue
or
ping
me
in
slack
and
can
get
you
a
code,
yeah
sure.
C
I
I
put
it
in
the
chat.
I
wanted
to
mention
that
the
apac
meet
our
contributors
group,
which
I'm
guessing
have
you
been
involved
with
them?
More
recently,
debba
they've
been
joining
our
meetings
and
saying
that
they
just
finished
up
a
blog
post
on
the
china
region.
I
don't
know
if
it's
out,
though,
or
in
pr
right
now,
but
I
thought.
J
Okay,
okay,
so
the
blog
series
is,
I
think,
ray
is
reviewing
it
and
we
will
get
a
placeholder
pr
by
today
or
tomorrow.
As
soon
as
the
review
is
over.
A
Okay,
community
management.
E
Hello,
may
I
please
have
credentials.
A
Yeah,
just
do
me
a
favor
dm
me
and
I'll
send
credits
to
you
like,
unfortunately,
for
zoom
zoom
root
account.
It
is
just
one
set
one
shared
password
you.
We
can't.
E
A
That's
all
I
have
okay,
one
other
thing,
and
this
might
be
a
look
for
lfx
thing.
Coming
up.
More
groups
are
now
running
into
the
issue
where
they
can
no
longer
send
calendar
invites
to
their
mailing
list.
A
For
some
historical
context,
kristoff
wrote
a
terrible,
terrible
script
that
he's
not
proud
of
that.
He
basically
removed
all
the
tests
and
forced
it
through
to
do
the
migration
for
for
kdev,
but
we
need
to
actually
turn
that
into
something
that
can
be
done
for
other
groups.
A
As
far
as
the
you
know,
calendar
invites
to
like
working.
A
I
think
we
have
an
issue
for
it.
I
have
to
go
back
and
check,
but
if
not,
I
need
to
create
one
and
start
actually
working
on
that.
I
I
We
have
a
lot
of
activity
going
on.
We
have
a
good
number
of
members,
both
who
have
been
coming
for
a
while
and
a
few
new
ones
from
our
kubecon
tweet
efforts
mainly
and
we're
making
sure
that
they're
all
getting
engaged
in
a
variety
of
different
activities,
including
catching
up
on
the
1.24
feature
blog
tweets
because
we
kind
of
dropped
those
amidst
cubecon.
G
I
And
then
we're
also
working
on
some
new,
updated
role,
definitions
as
well
as
some
other
repo
updates,
including
changing
the
name
of
the
repo,
because
we
want
to
change
our
team
name
to
be
primarily
contributor
comms
rather
than
upstream
marketing.
We
feel
that
it
represents
our
work
better
and
is
also
clearer
and
more
consistent
if
we
have
contributor
comms
everywhere.
Since
that
are
that's
our
at.
I
In
slack
and
speaking
of
slack,
we
were
interested
in
creating
a
new
channel
for
the
sub
project
so
that
we
can
more
easily
communicate
amidst
our
members,
I
don't
know
what
the
process
for
that
is.
A
A
It's
in
the
issue
yeah,
it's
just
open
up
opening
a
pr
for
sub
projects.
It
usually
follows
sig
name
dash
sub
project,
so
it'd
be
like
sig,
kendra,
x,
toms,
or
something
like
that.
I
I
A
A
Okay,
contributor
docs-
I
don't
have
any
updates
here
at
this
point
in
time.
Outside
of
the
earlier
comment
regarding
the
tech
writers
will
be
starting
work
on
the.
A
I'm
totally
brain
farting
on
it
right
now
on
on
the
training
thing.
Does
anyone
else
have
updates
on
it.
H
I
have
a
question
shoot
because
I've
been
gone
for
a
while
and
I'm
just
sort
of
getting
my
way
back
in.
Has
anybody
touched
not
the
con
in
the
context
of
the
contributor
guide?
Has
anybody
touched
the
non-code
contributor
guide
in
a
while.
A
I
don't
believe
so.
In
fact,
I
think
it
was
it
might
have
actually
been.
I
think
it's
like
this
dude.
H
A
Okay,
any
other
docs
related
things.
A
Okay,
github
management-
I
don't
really
have
any
updates
here
or
no
are
you
still
on
the
call.
A
Okay,
so
that
takes
us
through
our
main
agenda.
W
have
something
in
the
open
mic
discussions.
J
J
You
know
issue
regarding
shifting
it
to
kubernetes
repository,
so
I
don't
know
how
we
are
going
to
make
it
but
like
they
have
category
has
given
some
relaxation
to
like
they
have
created
a
new
server
for
communities,
dot
io
website
where
in
caterpillar
scenarios
that's
present
there
will
run
out,
but
for
this
community's
bootcamp
scenarios
I
don't
know.
J
So
I
was
thinking
what
we
could
plan
about
it
or
like
we
just
leave
it
as
it
is.
J
So
initially
ben
hall,
yeah.
A
So
what
why
is
it?
What
has
to
happen
is
and
for
it
to
move
into
the
github
organization?
It's
an
it's
an
issue
in
k,
org,
there's
a
github
transfer
request.
The
owners
of
catacota
scenarios
will
have
to
transfer
it
to
a
temporary
repo
before
we
essentially
ingest
it.
A
Another
alternative
would
basically
be
to
take
the
contents
of
it
and
essentially
like
if,
if,
if
transferring
is
an
issue
for
them,
we
take
the
contents
of
it.
J
Yeah
so
like
we
have
to
figure
it
out,
because
we
have
to
again
get
back
to
the
catacotta
folks
because
they
are
not
supporting
anything
outside
of
case
last
website.
A
So
yeah,
oh,
that's
awesome!
So
the
they
are
only
it's
only
if
it's
in
k
website.
J
Yes,
yes,
at
present,
like
there
was
an
umbrella
issue
or
tracking
down
what
what
dependency
we
have
at
gay
website,
and
they
came
up
with
this
reply
that
they
will
support
that
part.
J
A
Yeah,
okay,
you
know,
I
think
next
steps
are
k.
Org.
J
A
A
A
We
want
to
do
this
for
contrib
x2.
First,
like
honestly,
the
current
control
x,
leadership
is
is
also
really
over
subscribed.
So
we'll
want
to
nominate
josh
to
come
on
as
another
chair
to
help
with
things
and,
in
addition
to
josh
coming
on,
an
email
will
be
going
out
later
this
week,
where
we'll
be
looking
for
essentially
shadows
for
chairs
and
tls
to
you
know,
potentially
go
into
that
or
grow
into
that
role.
B
Right
I'll,
say
specifically,
my
goal
here
is
to
actually
make
my
tenure
as
chair
as
short
as
possible.
The
so.
B
If
you
are
interested,
if
you
think
you
might
have
the
time
to
become
contradicts
chair.
A
The
other
thing
like
while
it
does
seem
like
it's
a
lot
of
work.
It's
also
a
lot
of
work
right
now,
because
it
is,
you
know
just
a
few
people
we
are.
We
are
not
necessarily
looking
to
just
replace
the
two
chairs.
We
are
looking
to
potentially
have
more
chairs
and
more
eventually,
this
will
dovetail
into
some
plants
from
steering
where
we
plan
to
have
like
terms
so
that
way,
you
know
you
essentially
only
agree
to
be
a
chair
for
a
certain
period
of
time.
A
In
any
case,
expect
more
comms
about
this
more
formalized
thing
soon
have
a
a
google
doc,
but
the
draft
comms
for
it
already
it's
just.
I
think
I
think
kristoff
was
going
to
send
it
out
later
this
week.
A
A
Okay,
we
will
call
it
there
and
give
everyone
a
few
minutes
before
their
next
meeting.