►
From YouTube: [SIG ContribEx] Weekly Meeting for 20230510
Description
[SIG ContribEx] Weekly Meeting for 20230510
A
A
We
have
a
doc
for
notes.
If
you
have
any
agenda
items
that
you
want
to
cover
today
do
go
ahead
and
put
them
in
there
Josh.
You
had
volunteered
to
take
notes
earlier.
You
still
need
to
do
that
cool.
Thank
you,
and
here,
at
the
beginning
of
the
meeting,
we
usually
like
to
offer
an
opportunity
for
any
new
folks
on
the
call
to
introduce
themselves
totally
optional.
If
you
would
like
to
unmute
or
type
into
the
chat
to
introduce
yourself,
you
are
welcome
to
do
so
now.
B
We
have
anybody
new,
do
we
hello,
so
hello,
folks,
hello,
yeah,
I'm,
Yash
and
I've
I've
been
to
sitcoms
Castle,
helped
me
out
and
yeah
I'm,
exploring
the
kubernetes
ecosystem
so
happy
for
the
helping
out.
Thank
you.
C
D
Welcome
I'm
I'm
Josh
burkus
I'm,
one
of
the
soon
to
be
Emeritus
chairs
of
sick
contributor
experience.
C
F
E
E
I'm
Chris
I
am
also
a
co-chair
of
contributor
comps.
A
And
I'm
kazlyn
I'm,
a
co-chair,
co-lead
I,
think
is
really
the
term
of
of
the
contributor
com,
subproject
and
I.
Don't
think
there's
any
hopefully
about
it,
but
one
of
the
new
Sig
and
tripex
chairs,
taking
over
for
Bob
and
Josh.
A
A
A
So
then,
it's
exciting
to
have
a
couple
of
new
folks
a
little
background
on
Sig
contributor
experience.
We
are
a
special
interest
group
within
the
larger
kubernetes
project
that
focuses
on
all
sorts
of
aspects
of
how
contributors
do
their
work
in
open
source
kubernetes.
So
our
Focus
as
a
group
within
the
cabernetes
project,
is
on
making
sure
that
other
contributors
have
a
great
time
contributing
to
the
project.
So
you'll
see
a
bunch
of
aspects
of
that
in
our
meeting
today,
where
we'll
go
over
our
various
sub-projects
and
activities
that
we
have
going
on.
A
It's
a
little
bit
of
a
quiet
time
right
this
moment,
because
it's
right
after
kubecon.
Theoretically,
though,
we'll
see
about
that.
A
A
We
did
just
have
the
contributor
Summit
AT
kubecon
EU
a
couple
weeks
ago,
three
weeks
ago,
four
weeks
ago.
How
did
that
happen?
A
But
that's
yeah,
that's
all
finished
up.
We
did
have
the
Retro
for
that
took
a
few
notes
on
things
that
we
want
to
do
next
time
and
planning
for
the
contributor
Summit
at
kubecon.
North
America
should
be
starting
up
in
the
next
couple
of
weeks.
Probably
yeah
Nigel's
gonna
be
heading
that
who's,
not
on
the
call
today,
of
course,
but
he
will
be
the
lead
of
that.
So
soon
there
should
be
an
issue
coming
out.
A
That
will
say
we're
gonna
be
doing
our
contributor
Summit
planning,
who
wants
to
volunteer
to
help
out
with
that
and
folks
will
need
to
volunteer
on
that
issue
for
lead
and
Shadow
positions.
So
news
about
that
will
be
posted
in
and
probably
the
contributor
Summit
Channel
and
around.
A
A
Nothing
as
usual,
no
updates
at
least
to
the
status
well.
Actually,
I
do
have
one
update
on
that,
which
is
that
we
did
get
the
annual
report
doc
prden,
and
we
do
mention
that
the
mentoring
sub-project
needs
some
help
in
that
for
context.
For
the
new
folks,
the
mentoring
sub-project
really
needs
some
help
from
someone
who's
familiar
with
like
program
management.
A
The
type
of
help
it
needs
really
is
coordination
of
like
getting
a
bunch
of
folks
together,
working
in
the
same
direction
on
several
different
kind
of
sub
projects,
because
there
are
several
different
mentoring
programs
that
we
try
to
support
yeah,
and
it
looks
like
there's
a
couple
of
those
mentoring
programs
that
you
wanted
to
mention.
Josh.
D
Oh
just
so,
we
have
LFX
and
Google
similar
code
segments
currently
in
progress
and
have
a
couple
of
sigs
doing
projects
with
both
of
those
programs.
D
The
we're
not
currently
doing
outreachy,
mostly
because
we
really
need
an
Outreach
coordinator,
the
cncf
folks
take
care
of
coordinating,
LFX
and
GS
or
C4S.
They
don't
take
care
of
outmichi
currently,
and
so
until
we
have
somebody
to
do
that,
we
won't
be
doing
outreaching.
C
F
That,
like
I
I,
talked
to
Dawn
and
Nate
a
little
bit
about
getting
some
metrics
on
the
actual,
like
conversion
rate
of
mentees
from
those
programs
into
maintainers,
or
at
least
you
know,
further
contributors
talking
to
some
of
the
the
leads
and
other
people
here,
there's
been
hesitation
about
getting
more
involved
in
the
mentoring
programs,
because
so
frequently
the
mentees
will
join
and
then,
basically,
once
the
that
ends,
they
they
disappear.
F
Or
go
to
like
other
projects.
D
F
D
I'll
have
to
send
that
to
you,
because
I
haven't
been
doing
it
so
so
I
don't
actually
have
a
link.
The.
D
D
D
F
D
The
other
thing
we
discussed
is
that
LFX
is
not
necessarily
limited
to
students,
just
as
outreachy
is
not
necessarily
limited
to
students,
and
we
could
be
looking
at
using
those
programs
or
simply
using
the
same
good
first
issues
ETC
that
we
generate
for
those
programs
to
do
more
professional
mentoring,
as
in
mentoring
of
people
who
have
changed
jobs
that
bring
them
into
kubernetes
or
in
the
case
of
cncf
other
Cloud
native
projects,
and
need
help
getting
started
as
contributors.
D
So
yeah
and
and
one
would
expect
those
kinds
of
people
to
actually
have
more
stick-to-itiveness.
C
E
F
D
Were
never
many,
there
were
never
many
like
when
when
we
got
Nikita,
we
were
actually
doing
gsoc
in
a
big
way.
That's
true.
You
know,
and-
and
we
were
doing
like
four
Outreach
interns
a
year
and
a
bunch
of
other
things,
so
so
Nikita
represents
like
one
out
of
30
people,
so
the
and-
and
it's
always
going
to
be
that
way
right,
because
if
you're
having
somebody
do
the
mentorship
program
right
before
they
graduate
they're,
not
necessarily
graduating
into
a
kubernetes
related
job
yeah.
D
C
F
Help
people
with
yeah
at
least
having
having
experienced
sense
of
help
people
yeah.
D
Well
and
part
of
the
idea
and
the
idea
behind
having
things
like
gsoc
originally,
was
that
it
creates
an
ecosystem,
as
in
you,
don't
necessarily
get
the
student
you
mentored,
but
there's
now.
This
pool
of
students
who
know
it
contributing
to
a
public
open
source
project
is
like
that
you
might
draw
from
as
a
contributor,
even
though
they
did
their
gsrc
for
a
completely
different
project.
D
The
so.
D
But
the
other
reason
to
keep
doing
these
things
is
that
entry-level
opportunities
or
entry
level
opportunities,
whether
we're
talking
about
a
student
or
a
a
person
who
just
finished
a
code
camp
or
a
person
who
has
changed
tech,
jobs
and
and
is
now
in
a
job
where
they
are
working
on
something
kubernetes
related
in.
In
any
case,
they
need
the
same
sort
of
open
door
to
get
into
the
project.
D
So
from
a
perspective
of
actually
preparing
opportunities
to
help,
people
get
started,
it's
not
different
and-
and
that's
from
my
perspective,
the
main
value
to
our
project
of
participating
in
these
student
mentorship
programs
is
not
so
much
the
students
as
it
is
the
fact
that
it
gets
sigs
to
actually
update
their
good.
First,
issues.
F
The
we
I
will
say,
like
we've,
had
a
lot
of
things
that
have
basically
stopped
doing
good
first
issues
just
because
they
get
like
people.
The
a
good
example
with
6cli.
Someone
literally
wrote
a
bot
to
scan
like
the
cube,
color,
repo
and
others
just
to
assign
it
to
them
as
soon
as
anything,
labeled
good
first
issue
popped
up,
and
then
they
never
do
it.
Yep.
F
I've
yeah
yeah
I've
been
talking
to
Eddie
about
it,
and
that
is,
let's
say,
let's
say
a
bot,
but
that
happens
relatively
frequently
where
lots
of
people
compete
over
the
good
first
issues
and
no
one
actually
follows
through.
F
Yeah
most
most
of
the
leads
have
sort
of
unlabeled
good
first
issues
in
their
back
pocket
for
people
that
actually
show
initiative.
E
D
So
we
need
to
actually
bring
that
up
at
cncf
mentoring
area
because
we're
exposing
the
good
first
issues
even
more
through
the
the
new
clothes
tributor
site
and
and
so
obviously,
and
now,
I'm
I'm.
Thinking
about
the
horrors
of
somebody
figuring
out
how
to
hook
up
text
generators.
F
D
E
D
The
so,
and
but
we
would
need
to
talk
about
what
that
is.
C
A
D
Hope,
you're
enjoying
it
the
problem
that
rate
is
that
easy
for
new
contributors
to
get
started
right.
We
don't
want
there
to
be
barriers
in
the
way
that
prevent
people
from
becoming
a
contributor.
On
the
other
hand,
we
also
don't
want
our
reviewers
and
maintainers
to
be
spending
a
lot
of
time
dealing
with
Spam
right.
A
C
F
D
To
open
source
Summit
there's
a.
F
D
The
yeah
and
the
and
the
problem
is
this
is
likely
to
kill
clotributor,
which
is
something
that
that
potential
contributors
within
Cloud
native
look
for
for
a
long
time,
because
if
it's
happening
the
kubernetes,
it's
happening
to
the
other
Cloud
native
projects,
the
so
the
what's
really
annoying
is
well
I.
Guess
the
people
who
are
using
Bots
for
this
are
probably
using
Code.
F
Other
frustrating
thing
with
that,
too,
is
like.
Sometimes
people
will
go
right
from
you
know,
asking
to
assign
the
issue
to
just
like
opening
PRS
and
then
there's
literally
you
get
three
or
four
PRS
essentially
doing
the
same
thing,
just
because
people
race
to
do
to
complete
it.
E
D
Well,
I
know
the
single
punctuation
mark,
PR's,
yeah,
I've,
rejected
contributor
site
doesn't
attract
the
level
of
this,
but
but
we
do
get
the
ones
where
people
are
literally
correcting
optional
punctuation,
as
in
there
could
be
a
comma
here
that
could
not
be
a
comma
here.
It
doesn't
really
matter
and
they're
changing
it.
D
Oh,
my
favorite
is
line
breaks
in
the
markdown
people
moving
around
line
breaks
in
the
markdown,
so
it
looks
like
they
did
a
PR
because
I
actually
did,
and
it
was
a
PR
that
was
supposedly
response
to
an
issue
did
not
address
the
issue
at
all.
Instead,
all
they
did
was
they
put
in.
They
moved
all
the
line.
Breaks
around
you
know
effectively
making
it
a
thousand
line.
Change
I'm
like
no.
No.
F
So,
first
for
some
other,
like
stuff
sort
of
related
to
that
there
have
been
certain
like
I'll,
say
it's.
It's
been
frequent
in
some
some
other
countries,
but
where
people
basically
use
like
look
at
the
diffs
of
how
many
things
I've
done
as
like
it's
the
the
problem
with
like
the
chasing
the
green
stars
on
GitHub
or
like
devastats,
showing
the
top
10
list
of
of
contributors.
People
using
that
essentially
to
game
employment,
yup.
D
There's
like
no
amount
of
discouragement
we
could
put
in
somebody's
way.
That
would
stop
them
from
doing
that.
F
The
I
think
the
the
big
thing
for
us
is
because
people
also
use
org
membership
for
that
and
we've.
F
Specifically
had
a
lot
through
the
release,
team
and
I
know:
we've
talked
about
this
before
are
people
that
basically
join
just
to
get
org
membership
and
then
stop
or
they
they
will
literally
open
up.
You
know
one
PR
a
year
to
basically
keep
keep
the
badge
without
actually
doing
work.
D
A
A
F
It's
100
variable
from
repo
to
repo
and
like
project
like,
even
in
some
of
the
larger
repos
that
are
owned
by
multiple
groups.
F
D
Yeah,
the
and
and
peers
can
be
open
for
a
long
time
if
what
the
underlying
PR
refers
to
is
something
that
requires
researcher
debate.
D
E
F
There's
another
one
that
this
was
a
KK
one,
but
it
had
been
in
debate
since
2017.
C
C
D
D
D
I
mean,
obviously,
they
can't
GitHub
can't
prevent
real
people
from
acting
badly,
but
they
might
be
able
to
do
something
about
the
box
right
the
and
they
might
be
able
to
do
something
about.
D
Identifying
I'm
not
quite
sure
what
would
be
visible
or
if
they
actually
discuss
it,
but
I'm
thinking
about
what
what
patterns
would
indicate
that
somebody
I
you
know
was,
for
example,
doing
Mass
punctuation
mark
PR's,
the.
D
C
F
A
I
mean
I
think,
there's
also
an
important
message
here
of
folks
who
are
new
to
kubernetes.
You
can't
just
expect
to
find
a
good
first
issue
and
do
it
that
way:
asynchronously
without
talking
to
anyone
right,
it's
very
important
to
actually
talk
to
the
people,
doing
the
work
to
try
to
understand
what's
going
on,
and
sometimes
that
takes
a
long
time
and
that's
just
the
way
it
is
and
here's
why
I
think
the
here's?
Why
is
something
that
a
lot
of
folks
don't
get
and
could
Val
could
really
benefit
from
one.
F
A
E
Yeah,
so
the
Sig
Network
Spotlight
went
out
yesterday
and
caslin
got
access
to
file
a
service
request
for
Mastodon
on
Buffer
awesome.
Thank
you
caslin,
because
my
service
desk
access
is
gone
now.
A
F
Along
one
quick
thing
on
that
too,
for
Mastodon,
the
LF
now
has
their
official
server.
Should
we
move
the
kubernetes
one
to
that
one.
E
E
A
A
D
A
good
example
of
of
what
you
know
how
a
lot
of
marketing
folks,
who
don't
understand
the
differences
between
different
social
media
channels,
decide
that
they're
going
to
join
Mastodon
the
it's
funny,
because
none
of
their
stuff
officially
says
that
it's
only
a
Twitter
mirror.
E
D
D
E
A
Yeah,
all
right
so
I
think
that's
it
for
Calm
stuff
right
now:
contributor,
documentation.
C
E
A
F
A
F
Ping
Craig.
D
C
E
Yeah
Craig
won
that
one.
Let's
see
you
want
me
to
do
it
Chasm,
you
want
to
do
it.
What
do
you
well,
whatever
you've.
F
So
four
four
code
spaces,
depending
on
how
we
we
configure
it,
they
will
like
it,
wouldn't
come
from
our
budget.
It
would
be
on
them
and
every
person
gets
a
you
know
certain
allocation
per
month.
F
Github,
if
we
were
say
wanted
to
do
a
workshop
or
tutorial,
they
will
give
us
credits
to
do
to
like
run
those
workshops.
We
just
have
to
request
it
ahead
of
time.
Yeah,
that's
cool.
F
C
D
No,
if
we
were
gonna,
do
any
contributor,
Workshop
type
things
it
would
be.
Updating
and
sort
of
helping
package
contribute
a
workshop
so
that
organizers
of
kcds
could
do
one
if
they
wanted
to
yeah.
That's
been
a
lot
more
successful
than
doing
one
at
coupon,
partly
because
there's
less
fewer
time,
conflicts,
the
and
and
sort
of
less.
D
General
mobishness
the
so.
C
D
Yeah,
so
I'll
actually
take
this
one,
because
we
did
a
contributor
site
hack
session
at
the
contributor
Summit.
D
We
were
not
able
to
get
the
site
upgraded
to
the
current
Hugo,
because
we
still
have
major
rewrite
issues,
because
there
is
no
backwards
compatibility
in
Hugo
and
but
we
were
able
to
upgrade
it
by
like
four
or
five
versions
to
something
that
at
least
is
currently
getting
patches
the
and
so
that's
actually
live
already.
We
merged
that
during
the
contributor,
Summit
the
and
then
we're
we're
stuck
on
that
particular
version.
D
I,
don't
remember
what
the
number
is
until
somebody
wants
to
do
a
rewrite
or
for
that
matter
honestly
consider
reporting
this
to
something
else.
The.
C
D
C
G
F
A
All
right
exciting
to
hear
that's
the
only
GitHub
management
thing,
then
Open
Mic
discussion.
F
So
I've
opened
up
a
PR
to
add
the
sick
and
tripx
leads
list,
as
well
as
the
actual
sick
and
trimix
list
to
be
managed.
Kate's
groups-
oh
cool.
We
can
the
the
Kindred
breaks
list.
We
can
actually
export
and
import
into
the
new
one.
F
We
just
have
to
coordinate
the
change
and
essentially
record
the
like
make
it
a
procedure
because,
like
we're
running
into
more
problems
with
sigs
that
are
bumping
into
various
limits
like
sick
Auto
scaling
has
lost
access
to
their
leads
list
ouch,
it
happens
a
lot
actually
because
most
of
these
Sig
lists
were
created.
F
Originally,
you
know
years
ago
and
people
using
their
corporate
accounts
and
when
their
employer
changes,
we
have
like
they
lose
access
to
the
list
and
they
can't
make
changes
to
it
and
there
there's
been
sort
of
a
slow
like
some
of
the
sigs
have
already
started
to
migrate,
but
like
we,
we
really
should
just
get
something
like
put
together
a
process
for
it.
F
E
F
That
is,
that
is
a
design
feature
to
prevent
people
from
spamming.
Oh
yeah
good
point
using
public
Google
Groups
right.
The
the
rate
limits
for
named
accounts,
like
anything
that
we
have
at
kubernetes
IO,
is
significantly
higher
because
there's
an
assumption,
since
it
is
a
paid
thing
that
someone
is
actually
being
a
steward
of
it
and
not
just
creating
another
group
to
spam.
People.
F
It
will
need
someone
from
the
the
Zoom
team
anyway,
because
they
have
to
migrate
their
Zoom
account
over,
but
I
I
would
say
like
that,
should
be
a
goal
to
try
and
do
by
like
say
your
end
is
to
get
all
the
Sig
lists
over
to
you.
F
You
know
managed
accounts
that
will
also
simplify
a
lot
of
other
things,
for
the
groups
in
man
like
just
general
management
like
any
leads
changes,
is
a
change
to
it's
a
PR,
and
it
also
means
that
say
the
leads
list
can
just
be
made
up
of
other
named
accounts,
so
you're
not
having
to
PR
people
into
multiple
places.
You
literally
just
add
them
to
like
the
leads
list
of
one
place
and
they
get
all
the
other
permissions.
They
need.
A
Good
points
it
sounds
like
we
should
talk
more
later
about
who
might
be
good
folks
to
help
guide
others
through
the
mailing
list,
migrations.
F
The
cree,
the
creation,
is
all
PR.
Okay,
it's
just
to
migrate
members.
You
have
to
do
that
through
the
UI,
because
the
public
Google
Groups
there
is
no
API
access
right,
so
there's
no
way
to
just
like
script,
getting
the
list
and
moving
them
over.
F
F
The
other
I'd
say
stretch
goal
out
of
all.
This
would
be
to
eventually
just
create
actual
right
now.
This
would
require
steering's
help,
but
to
create
actual
Google
Drives
for
every
Sig,
because
that
solves
a
lot
of
the
permissions
issues.
G
A
All
right,
important
considerations:
we
have
eight
minutes
left
next
item,
Arno.
G
F
Yeah
the
Nigel
has
the
workflow
tested.
It
just
has
to
be
set
up.
F
E
E
F
C
D
One
thing
in
these
more
recent
things,
like
the
migrations
and
everything
else
for
our
our
incoming
group
of
contravex
leadership
that
you
might
want
to
consider
is
you
know,
towards
the
end,
and
one
of
the
reasons
why
a
lot
of
us
realize
it
was
time
for
us
to
retire.
Is
it's
become
customary
for
the
contributor
experience?
Tech
leads
to
not
attend
this
meeting,
which
becomes
a
problem
because
our
last
15
minutes
has
all
actually
been
Tech
lead
business.
D
A
A
A
A
Okay,
if
we're
done,
though
I
can
go
ahead
and
wrap
up
the
meeting.
Thank
you
all
for
coming
today
and
I
hope.
You
all
learned
something
I
know.
I
did
and
we'll
have
this
meeting
again
in
two
weeks.
You
can
find
us
on
slack
until
then,
I'm
gonna
go
ahead
and
stop
the
recording,
unless
folks
want
to
talk
about
anything
else,
on
the
recording
yeah,
all
right,
bye,
bye,
YouTube,.