►
Description
Kubernetes SIG Contributor Experience Biweekly Meeting for 20220105
A
Recording
in
progress
we're
good
to
go
hi.
Everyone
welcome
to
the
first
meeting
of
2022
for
contributor
experience,
I'm
your
host
alison
downey,
I'm
co-chair
along
with
bob
here
and
yeah
just
some
housekeeping
before
we
begin.
So
we
abide
by
the
code
of
conduct
here,
the
kubernetes
code
of
conduct.
In
short,
what
that
means
is
be
excellent
to
each
other,
and
is
there
anybody
new
on
the
line
or
should
we
just
do
like
a
round
of
intros
or
I'm
not
sure,
I'm
bob?
B
A
So
let's
just
skip
the
intros
for
today,
but
I
wanted
to
kind
of
start
off
this
first
meeting
of
the
year
with
just
kind
of
like
a
pitch
a
speech.
I
don't
know
a
very
brief
one.
I
don't
want
to
ramble
on
for
a
really
long
year.
I
have
a
tendency
to
do
that
sometimes,
but
I
want
to
say
we're
here
we're
now
here
it's
2022..
Can
we
can
you
know?
Look
I
wanted
to
take
the
time
for
us
to
like
look
back
at
2021.
A
Briefly,
like
I
think
2021
was,
it
was
very
challenging.
You
know
lots
of
things
happened,
but
we
still
managed
to
pull
it
off.
So
I
want
to
say
a
big
thank
you
to
everyone
here
on
the
team
everyone
who's
coming
in
and
helping
out
of
like
getting
involved
and
wanting
to
get
involved.
It
really
means
a
lot
to
me
and
it
means
a
lot
yeah.
So
you
know
we
did.
We
did
the
steering
election.
We
pulled
off
contributor
celebration.
A
A
You
know
I
I
want
it
to
be,
like
you
know,
just
better
than
last
year
so,
and
I
I
see
this
first
kind
of
quarter
here-
that
we've
got,
there
is
many
opportunities
for
us
to
kind
of
get
the
ball
rolling
and
you
know
get
back
to
you,
know,
contributor
summit
and
that's
kind
of
one
of
the
things
we're
going
to
be
touching
on
in
this
meeting
today,
which
is,
I
don't
know
if
it's
too
early
to
start
thinking
about
valencia
or
if
it's
the
right
time.
It's
not.
Okay,
that's
great.
C
A
But
yeah
I'm
like
hoopcon
valencia.
I
really
hope
to
see
more
of
y'all
in
the
flesh
in
person
and
yeah.
Just
have
a
great
event.
So
I
think
you
know
this
is
the
right
time
to
start
planning
these
things
and
start
thinking
about.
You
know
how
that
could
look
and
with
that
out
of
the
way,
let's
get
right
into
the
meeting
so
events
office
hours
is
there.
B
B
B
A
Yeah,
I
think,
moving
it
cloud
native
tv
would
probably
be
a
really
good
spot
for
it.
I
think
there's
gonna
be
some
ramping
up
of
that
in
the
coming
weeks.
Hopefully
I
and
yeah
we
can
see
what
things
we
can
shift
over
to
there.
I
think
that's
one
of
the
things.
The
only
thing
I
think
can
think
at
the
moment
that
we're
going
to
probably
shift
over
there
and
that'll
help
kind
of
take
one
thing
off
our
plate
here,
so
we
can
focus
more
on
like
contributors,
so
yeah
next.
A
All
righty,
let's
get
to
the
next
item,
so
laura's
left
her
notes
here,
so
she
can't
make
it
in
person.
The
update
is
that
the
k
dev
migration
is
done.
We
can
start
the
meeting
back
up
again,
there's
a
question
here.
Would
it
be
better
to
let
people
get
settled
for
january
into
the
new
mailing
list
before
sending
out
a
meeting,
invite
so
plan
for
february
to
start
back
up
fort's
welcome,
so
I
want
to
have
a
little
discussion
about
that.
What
is
everyone's
thoughts
here.
B
C
D
B
A
A
A
That
decision
is
probably
the
best
thing
course
of
action,
yeah,
so
yeah,
I
think
probably
an
action
item
on
here
would
be
to
start
some
sort
of
dock
or
I
don't
want
to
go
into
trying
to
schedule
another
meeting
on
the
first
week
of
january
that
that
might
not
be
a
great
idea,
but
just
to
start
a
doc
start.
You
know
actually
pr
into
the
repo
please
pr
into
the
repo
new
folder
yeah
for
contributor
summit,
2022
eu.
E
E
A
I
think,
if
we're
this
far
out,
we
can
actually
potentially
plan
out
some
kind
of
like
we
could
have
a
potential
redundancy
plan
for
like
doing
like
virtual
kind
of
version
of
the
talk.
If
you
still
want
to
pre
like
like,
if,
if
we
do
the
usual
tracks
right,
where
we've
got
the
you
know
the
con,
the
talks
cp
and
all
that
we
can
like
if,
if
it
ends
up
all
up
in
the
air,
we
can
ask
people,
do
you
still
want
somewhere
where
you
can
present
and
then
maybe
we
could
do
something
virtual?
B
A
F
B
On
this
is
that
we
already
have
we
had
to
put
the
room
reservation
in
before
the
end
of
last
year,
and
we
we
literally
reserved
apprentice
the
same
type
of
space.
We
did
for
n
a
because
we
were
banking
on
it,
not
being
you
know,
similar
at
at
best
in
terms
of
attendance,
so
we
only
have
one
room
with
rounds
and
one
smaller
room
with
that,
like
as
a
meeting
room
and
then
sick
docs
will
also
have
a
room.
B
So
the
the
sort
of
the
assumption
going
in
was
like
it
would
sort
of
be
a
repeat:
well,
people
can
do
like
people
could
submit
stuff
but
like
they're
and
we
haven't
submitted
like
any
av
requests.
Yet,
but
the
like
it's
going
to
be
round
it's
going
to
essentially
just
be
like.
You
know,
one
room
for
hanging
out
and
doing
stuff.
B
B
A
Okay,
yeah,
I
that's
the
one
thing
with
the
celebration.
I
I
wasn't
very
involved
with
that
and
I'm
really
sorry
to
hear
that,
like
it
didn't
go
so
well,
but
I'm
very
kind
of
grateful
for
like
yo
you're,
putting
in
the
effort
bob
and
like
all
the
team,
putting
in
the
effort
to
try
and
make
it
happen.
I
think
there
are
some
things
that
I
think
would
be
valuable
to
take
from
the
like
celebration
in
terms
like
the
awards.
A
Definitely,
but
some
of
the
like
scheduled
programming
and
stuff
that
we
had
the
other
contributor
celebration
that
we
did,
for
instance,
for
instance,
the
what's
the
the
the
club,
the
bake
off
and
all
that
it'll
be
cool
to
have
some
sort
of
variety
like
show
like
some
like
one
or
two
kind
of
things
that
we've
put
together,
where
it's
like.
You
know
us
as
contributors
having
fun
together
on
a
stream
like.
A
C
A
I
think
if
we
can
kind
of
get
in
place
like
a
road
map
for
this
year
of
this
is
all
the
stuff
we
want
to
do
and
then
put
that
into
the
repo.
I
think
that's
something
that
I
can
take
on
so
I
can
be
like
this
is
when
we
should
really
start
like
planning
and
thinking
about
this
and
starting
to
talk
about
it
and
then
get
that
in,
like
a
visual
form
where
we
can
go
and
check
back
on
every
every
zoom
meeting
like
this.
A
That
will
probably
help
us
a
lot
with
the
trying
to
keep
an
eye
on
when
we
need
to
start
preparing
for
things,
because
I
think
one
thing
I
felt
about
last
year
is
that
it
was
like
oh
wait,
when's
this.
We
need
a
plan
for
it.
We
need
a
plan
for
it
and
yeah
so
getting
a
high
level.
Like
view
of
when
we
need
to
start
doing
things
and
stop
yeah,
that's
that's
another.
I've
gone
on
a
little
tangent
here,
yeah,
so
any
other
thoughts.
Folks.
D
All
right,
can
you
hear
me
now
yeah,
you
know
all
right
now
that
we
have
a
dev
list.
We
can
kick
back
meet
our
contributors,
but
going
back
to
like
the
road
map
stuff,
I
personally
think
meet
our
contributors
is
very
low
priority
compared
to
other
things
that
we
have
on
our
plates
right
now
and
who's
active
in
this
group
and
doing
work.
D
I
think
it's
much
more
of
a
priority
for
us
to
do
the
community
meeting
than
it
is
for
us
to
do
meet
our
contributors,
because
I
feel
like
right
now
in
the
project
state.
We
don't
need
new
contributors,
we
need
maintainers,
which
is
a
whole
different
conversation
and
like
retaining
the
maintainers
that
we
have.
So
I
feel,
like
the
community
meeting,
would
get
us
to
some
of
those
goals
and
objectives,
so
I
still
would
like
to
put
meet
our
contributors
on
a
semi-hold
until
we
bootstrap
the
the
community
meeting
back
up.
C
D
B
Hey,
I
actually
think
laura's
structuring,
like
idea,
would
work
well.
The
big
problem
was
we
had
we,
since
we
didn't
have
any
meeting
notifications
or
anything
like
that.
We
weren't
getting
people
to
show
up
like
talking
about
some
of
the
the
bigger
cross-cutting
caps
and
some
of
the
the
other
sort
of
inter-sig
important
things.
Yeah
is
definitely
worthwhile,
and
so
it's
important
to,
like
you
know
to
our
maintainers.
D
C
C
D
And
that's
why
I
think,
like
a
programmatic
structure
needs
to
be
in
place
so
that
it's
not
like
all
one
like
j,
I
mean
josh,
I'm
josh
is
like
kind
of
like
I
see
josh
like
shaking.
Like
you
know,
josh
knows
I
feel
like
it's
just
so
hard
on,
like
that
one
individual
to
curate
like
every
month,
without
it
being
like
a
programmatic
thing.
You
know
it
exactly
and
like
that's
why
it's
like
that's
too
much
of
a
burden
on
one
person
like
you
know,
so
that's
why
I'm
like
from
when
we
bootstrap
this.
D
We
should
bootstrap
it
from
like
a
sustainability
perspective
and
not
like
think
about
it
as
like
a
one-off
event
every
month
so
before
when
we
had
it.
When
we
had
like
the
sig
updates,
it
was
very
structured,
but
now
that
sigs
do
also
updates
at
kubecon.
You
know
we
had
to
kind
of
give
and
take
like
the
burden
on
them.
So
anyway,.
A
Yeah,
and
also,
I
think
another
thought
I'd
like
to
add-
is
yeah
not
just
one
person,
not
a
proof
of
concept.
I
totally
agree
with
you
on
a
lot
of
these
on
on
these
notes,
paris,
and
we
really
need
to
be
thinking
about
the
structure
and
how
do
we
like
make
something?
That's
going
to
last,
like
I
think,
yeah
come
and
and
then
another
thought
on
the
same
line
like
as
we've
got
meet
our
contributors
and-
and
you
know
the
community
meeting
and
all
that
I
think
if
we
do
do
less.
A
C
A
Quantity
yeah
quality
of
a
quantity
and
then
that's
another
thing
as
well.
We
could
probably
shift
to
cloud
native
tv.
Potentially
you
know
there
could
be
a
whole
thing
which
is
meet
the
contributors
behind
the
projects
that
you're
using
in
the
cloud
native
space,
like
that.
That's
another
little
tangent
that
went
on
there
tangent
something
to
investigate
and
I'll
look
into
that
one
yeah.
A
E
B
One
quick
thing:
I
think,
if
I
recall
our
last
conversation
around
some
of
the
like
outreach,
yellow
effects.
All
of
that
was
with
a
conversation
with
the
about,
instead
of
having
to
like
resubmit
to
create
proposals
for
all
of
them.
Just
like
let
the
cigs
let
people
create
proposals,
then
it's
essentially
just
like
resubmit
or
slightly
massage,
to
go
for
the
next
one.
B
C
A
B
B
E
B
We
we
have
some
tech
writers,
they'll,
be
starting
soon,
both
on
updating
the
contributor
guide,
basically
redoing
it
from
scratch
and
giving
it
one
deduping,
giving
it
one
style
one
voice.
So
that
way,
it's
not
look!
It's
not
like
piecemeal
from
like
50
different
authors,
and
that
will
feed
directly
into
the
workshop.
That's
going
to
be
developed.
A
I
think
that's
not
really,
I
think
that's
all
sorted
as
well,
like
I'm
very,
very
glad
that
thank
you
very
much
bob
actually
for
taking
the
time
to
get
the
tech
riders
onto
that.
I
really
appreciate
that
because
it's
the
one
project
that
has
been
spurting
on
the
back
of
my
head,
like
I'm
like,
oh
no,
but
I
hope
to
see
like
that
very
soon
in
the
future,
it's
gonna,
be
it's
gonna
be
awesome.
A
D
A
D
So
it
was
a
lot
of
changes
at
a
lot
of
a
lot
of
the
time,
so
we
essentially
tried
to
aggregate
it
and
you
know
bubble
it
up
to
them
at
certain
cadences.
So
it
wasn't
so
much
all
of
the
time
like
a
fire
hose
so,
but
now
that
we
also
have
the
monthly
meeting
and
things
like
that,
where
we
can
like
disperse
information
and
they
have
a
leads
list
and
stuff
like
that,
we
probably
just
don't
need
it
anymore.
So
I
think
that's
my
my
two.
My
two
second
take.
A
I
feel
so
on
board
on
that,
especially
with
the
if
you
aggregate
everything
it's
also
like
a
lot
of
stuff
to
take
in
all
at
once.
So
just
sending
things
periodically
out
to
the
list,
I'm
like
yeah
as
they
say,
yeah
as
they
come
up,
sounds
good.
It's
another
thing
we
can
update
on
the
agenda,
template
100,
yeah
and
next
up.
We
have
dev
stats.
D
D
E
A
C
H
I
tried
the
automation
on
my
side
and
the
thing
was
that
the
default
branch
is
still
named
as
master
when
I
tried
in
my
repo
I
renamed
my
branched
to
main
and
the
automation
worked
on
my
side.
So
I
guess
that
would
be
the
issue.
I've
mentioned
the
I've
mentioned
in
in
the
contributor
to
its
issue,
issue
thing
so
yeah.
H
B
B
B
C
I
A
B
B
So
let's
need
to
check
back
with
them
and
see
if
those
other
issues
have
been
resolved,
if
not
push
on
them
to
get
them
resolved
and
then
just
do
the
final
cut
over.
I
think
at
this
point,
like
most
of
the
the
things
have
been
taken.
Care
of
there
was
just
like.
I
think
two
remaining
issues
reported
on
the
tracking
issue.
A
G
Hello,
so
my
name
is
james
lavrak,
my
pronouns.
Are
he
him?
I'm
the
release
lead
for
kubernetes
124,
I'm
also
joined
by
xander
who's,
released
the
shadow
for
124.,
we're
going
around
all
the
sigs
and
just
checking
in
ahead
of
the
start
of
124
next
week
and
just
wanted
to
make
ourselves
available
to
answer
any
questions
and
see
what
people's
plans
are
for
the
upcoming
release
and
things
like
this.
C
G
Yeah,
yes,
we're
we're
aware
of
docker
shin.
That's
been
very,
very
big
photo
discussion.
The
only
thing
I
can
think
of
really
is
unfortunately,
joseph
isn't
on
this
call,
but
joseph
r
ea
is
going
to
be
sending
out
the
email
to
all
of
the
shadow
applicants
who,
unfortunately,
were
not
selected
tomorrow
and,
of
course,
a
big
part
of
that
is
typically
oh.
If
you
still
want
to
be
involved,
there's
things
you
can
things
you
can
do.
I
don't.
G
I
haven't
seen
joseph's
draft
for
that
email,
they're,
usually
pretty
similar
from
what
I
said
anyway,
but
I
guess,
if
there's
anything
you
wanted
to
highlight,
as
you
know,
for
people
who
didn't
get
selected
if
they
still
want
to
be
involved
in
the
projects
as
a
whole.
Is
there
anywhere
you
wanted
us
to
shove
them?
Let's
say
shove
them
kind
of
direct
them.
A
I
think
I
just
had
like
a
random
idea
pop
in
my
head,
so
when
it
comes
to
you
know
folks
not
getting
selected
for
like
the
release,
maybe
that
would
be
an
interesting
blog
post
for
marketing.
Like
you
know,
contributor
kind
of
like
advice,
you
know
what
do
I?
What
can
I
do
if,
like
you
know,
I'm
rejected
from
being
a
shadow
like
if
I'm
my
shadow
applications
rejected
and
that
that
kind
of
you
know
be
an
interesting
it'll,
be
interesting,
like
story
to
kind
of
share
with
the
wider
community.
C
E
The
the
the
reason
the
release
team
gets
so
many
applicants
is
because
it's
has
a
structured
process
for
new
contributors,
but
but
the
answer
really
is
okay.
Well,
here's
release
engineering,
and
here
is
the
you
know,
contributex
marketing
team,
and
here
is
you
know,
whoever
else
is
there
and-
and
we
would
need
to
find
out
who
is
there
in
terms
of
saying
here
are
other
teams
that
are
interested
in
people
who
who
want
to
participate?
Because
it's
not
I
mean
the
thing,
is
you
know
for
the
release
team?
A
I
think
as
well
now
that,
like
we're
kind
of
ramping
up
again,
I
think
maybe
there
is
some
contrabex
effort
where
we
are
going
from
kind
of
sick
to
sick
and
kind
of
asking
them.
How
can
we
enable
you
to
kind
of
recruit
more
people
like?
What
do
you
need
kind
of
that?
That's,
I
think
something
that
might
need
to
happen.
I
don't
know
rather.
C
Yeah,
I
almost
wonder
if
that's
like
we
talked
about
oh
crap,
I
lost
my
train
of
thought,
but
we
talked
about
you
know.
The
community
needs
a
program
right
like
that
could
easily
fold
into
part
of
that.
I
feel
like
is
getting
some
of
those
inputs,
because
I
feel
like
that
program
team,
for
the
community
meeting
that's
going
to
have
to
reach
out
to
six
on
a
regular
basis
as
it
is.
H
I
guess
for
this
sick
part,
we
did
the
thing
in
the
beginning
of
the
year,
like
paris
and
all
we
have
a
health
wanted
section,
the
annual
survey
where
the
six
come
up
and
say
these
are
the
work
we
need
help
with
and
some
of
the
work
isn't
getting
done.
Also,
we
we
did
post
regular
tweets
about
it
and
we
didn't
receive
any
any
of
the
like
that
there
weren't
many
people
who
were
interested,
so
we
can
roll
out
that,
but
I
I
already
have
that
documentation.
H
So
if
you,
if
you
need,
if
you
needed
to
send
it
to
the
people
who
are
not
selected
in
this
side
of
release
address,
so
it
might
help
them,
because
it
has
all
almost
all
the
six
and
the
sections
in
which
they
need
help
and
each
annual
survey
we
receive
a
lot
of
you
know,
pointers
from
each
of
the
things
so
yeah.
I
think
we
could
use
that
part
to
get
people.
H
I
Starting
point,
I
know
with
sig
docs
we're
starting
a
new
contributor
ambassador
person
and,
and
then
this
person
will
have
more
formalized
meetings
they
might
be
monthly
to
to
ramp
up
folks
who
are
interested
in
in
contributing
to
to
sig
docs.
I
don't
know
if
other
sigs
are
doing
this
as
well.
I
I
agree
that
this
might
be
a
good
blog
post
on
on.
You
know
what
happens
and
how
to
contribute
to
the
projects
or
like
how
or
how.
B
B
They
tend
to
very
much
be
aspirational
goals,
because
it's
contrabex
has
been
a
thing
where
we
get
a
lot
of
people
that
start
projects
and
then
move
on
to
like
other
parts
of
the
project
and
never
finish
the
thing
that
was
started
and
we
kind
of
we
are
the
gateway
for
other
cigs
for
a
lot
of
stuff.
So
it's
just
kind
of
like.
A
I'm
going
to
set
an
aspirational
goal
here
for
two
weeks
like
end.
This
is
very
aspirational.
I
I
should
push
it
up
by
an
extra
week,
but
that
that
would
be
too
long
would
already
be
through
most
of
the
month
but
end
of
next
week
by
the
end
of
next
week.
It
would
be
nice
to
have
gotten
started
on
that,
like
a
decent
chunk
of
that
tidy
up
done
so
that
the
next
time
we
meet.
A
What
should
not
be
next,
I
don't
know
if
we're
going
back
to
weekly
zooms
or
just
continuing
with
our
bi-weekly
cadence,
because
I'm
fine
with
that
the
by
week
clicking
is
nice,
but
that'll
give
next
time
we
have
a
zoom
call
meeting
like
this.
We
can
kind
of
show
what
the
new
kind
of
roadmap
looks
like
the
milestones
and
how
that
all
looks
tidied
up
so
yeah
by
then
by
the
next
zoom
face-to-face
meeting.
Yeah
get
that
tidy
up
underway
for
a
contributing
experience.
A
B
Sort
of
on
that
note
it'd
be
whoever
is
on
the
release.
Comms
there
is
a
weekly
contrabex
marketing
meeting.
I
know
it's.
Some
people
have
dropped
by
that
in
the
past,
if
they've,
like
those
that
have
been
sort
of
involved
in
both
areas
have
known
to
drop
in,
but
it'd
be
great
to
at
least
have
that
written
down
somewhere
or
like
as
a
little
note
for
people
like
hey.