►
From YouTube: [SIG ContribEx] Weekly Meeting 20210707
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone
and
welcome
to
the
july
7th
kubernetes
sick
contributes
bi-weekly
meeting
I'll,
be
your
host.
Today,
bob
killen
co-chair
of
say,
contributes
just
as
a
journal
fyi.
These
meetings
are
recorded
and
we
post
to
the
internet.
We
abide
by
the
cncf
code
of
conduct,
which
essentially
boils
down
to
please
be
excellent
to
each
other
with
that,
let's
kick
right
into
the
agenda.
B
Yeah,
so
we
were
working
on
a
script
to
replace
the
existing
patch
script,
which
like
brings
in
content
from
other
repositories
into
the
contributor
side,
and
we
have
now
reached
a
point
where,
like
we
are
able
to
pick
up
all
the
links
in
the
markdown
files
and
what
I
wanted
to
know.
Next
was
like
what
to
replace
those
links
with
actually
like,
because
these
are
links
which
refer
to
other
markdown
files.
But
when
we
like
have
the
actual
thing
for
hugo,
we
want
them
to
be
real
links.
A
A
A
A
Okay,
cool,
so
just
as
a
quick
room
reminder
is.
This
is
honestly
a
awful
piece
of
bash
that
I
wrote
to
help
ingest
content
from
other
other
sites
or
other
repos
and
we're
working
on
replacing
it
with
the
go
version
to
do
that.
We,
like
the
link
stuff,
has
been
sorted
out
and
now
it's
just
going
over
how
it
actually
determines
if
a
how
to
update
links.
A
The
first
thing
I
know
that
it
does
is
any
file
that
it's
touching
it
expands
any
links
so
like
if
something
is
matching
like.
If
a
link
is
like
bug,
bounty
like
this,
it
will
expand
to
be
the
full
path
of
what
it
would
be
from
the
root
of
the
repo.
A
So
I
think
here
so
it's
like
computer
cheat
sheet
becomes
guide
contributor
cheat
sheet.
If
this
was
content
being
synced
from
the
community
repo.
B
Is
this,
like
is
the
right
url
on
the
right
side,
like
from
the
github
repo,
like
from
what
folks
would
specify
in
the
yaml
file
as
the
destination.
A
Yes,
so
like,
if
someone
is
specifying
it's
the
korean
community
repo
and
we're
and
we're
syncing,
like
the
you
know,
bug
bounty
dock
and
any
links
that
it
finds.
That
is
like
bug
bounty
like
that.
It
essentially
follows
this
as
if
it
is
a
file
like
if
you're
at
a
cli,
and
then
it's
like
okay,
here's
the
true
path
of
it
and
that
expand
then
like
it
will
expand
it
out
and
replace
it
with
the
expanded
path.
A
Well,
sorry,
it
doesn't
replace
it
with
the
expanded
path,
but
like
at
least
logs
what
that
path
would
be,
and
if,
like
the
reason
why
we
have
to
do
it,
the
file
way
is
because
there
are
some
things
like
this.
A
That
use,
like
you
know,
dot
dot
to
traverse
the
repo
like
as
if
it
were,
because,
like
that's
something
markdown
understands,
that's
not
something
that
html
or
what
anything
else
understands
and
because
this
is
going
to
a
file
that
doesn't
exist
in
the
directory.
We're
copying
over
in
this
case.
It's
your
computer's
guide.
It
maps
it
out
like
it
replaces
it
with
the
full
link
like
that,
because
that
document
is
not
being
copied
over
and
you
still
want
the
link
to
work.
B
Yeah
so,
basically
like
we
have
the
underscore
temp
folder,
where
we
actually
cloned
it
and
like
in
an
underscore
output
folder
where
all
the
final
files
are,
and
what
this
would
do
is
like
transform
this
dot
dot
into
the
github
link
for
the
like
original
file
and
replace
it
with
that
right.
Yep.
A
A
So
it's
just
like
if
something
is
linking
to
the
like
the
full
path
like
this,
instead
of
a
file
reference
path
like
that,
but
it
exists
and
something
that
we
are
copying
over
then
we
should
swap
it
out.
It's
the
same.
Why.
B
A
A
Because
then
they
would
like,
if
it's
something
that's
copied
to
the
site,
that
would
take
them
off
the
site
to
the
community
repo,
instead
of
keeping
them
within
the
site
now
to
make
things
more
complicated.
We
also
have
a
shortcut
like
a
shorthand
way
that
we
reference
links,
you'll
see
this
around
it's
like
get.kates.io
and
that
essentially
rewrites
urls.
A
A
A
B
A
A
Then
it
essentially
like
it
keeps
a
map
of
what
the
link
was
and
what
it
should
be
and
then
runs
the
regex
regex
against
the
the
dock
to
replace
it
with
like
what
it
will
be
if
it
like.
If
it
helped
too,
we
can
go
over
this
yeah.
So
so
here
here's
where
I'm
you
can
see
the
like,
where
it
swaps,
the
like
html
link.
A
But
if
it
helps
we
can,
we
can
actually
like
schedule
some
one-on-one
time.
I
know
you
had
like
mentioned
that
in
chat.
I
was
kind
of
like
mostly
out
of
the
office,
the
the
past
two
days,
but
we
can
schedule
something
and
and
like
go
over
this
more
in
depth.
If
that
would
help.
B
A
D
A
A
A
So
I
know
we
kind
of
dive
down
that.
Does
anyone
have
any
other
questions
or
things
for
the
contributor
docs
subproject.
A
Mentoring,
one
thing
that
I
do
know
is
that
we
are
still
waiting
on
the
stream
yard
license
to
be
completed.
I've
pinged
ihor
a
couple
times
now
about
getting
that
result,
and
I
will
just
continue
to
bug
him
to
to
get
that
paid
for,
for
at
least
a
moc.
A
E
Hey
everyone
so
yeah.
I
still
need
to
get
those
pull
requests
in,
but
I
have
completed
all
the
comments
and
all
the
feedback
that
everyone
had.
I
removed
all
those
excess
labels,
so
this
just
needs
the
needs.
The
slash
looks
good
to
me
and
the
another
review,
and
I
think
that
should
be
all
good
to
roll
out.
I'm
not
sure
I
need
to
just
double
check
on
that
right
now.
E
If
there
is
any
there
isn't
any
conflicts
so
yeah
there
isn't
any
conflicts
on
the
pr
and
yeah
that
should
help
like
just
have
a
concrete
foundation
for,
like
all
the
documentation
around
how
you
make
a
guide,
how
you
structure
things
and
then
the
next
one
to
tackle
is
the
one
the
website
where
it's
just
the
basic
skeleton
of
it
all,
and
so
people
can
just
pr
straight
their
editions.
E
They
they
compare
their
con,
their
improvements
and
their
written
guides
into
that
those
stubs.
And
then
hopefully
we
get
all
this
there's
a
well.
We
aim
to
get
this
workshop
material
done
by
kubecon
in
it
like.
I
think
I
think
that's
a
good
target.
It'll
be
it'll,
be
a
bit
tight,
but
I
think
it'll
be
yeah
yeah.
That's
that's
my
opportunity.
Even.
A
I
don't
have
anything
for
the
need
to
know
list.
The
chair,
tl
meeting
is
tomorrow,
but
there
is
actually
something
I
want
to
highlight
in
this.
A
A
The
other
thing
is
this:
is
the
the
same
for
episodic
contributors,
those
that
go
sort
of
three
or
more
months
between
interacting
with
a
project
in
some
form.
A
Now,
there's
been
the
one
interesting
step
to
go
along
with
this
is
that
the
we
are
doing
roughly
the
same
amount
of
work,
every
release
like
it's
kind
of
crazy,
it's
like
it's
plus
or
minus
10,
pr's
average
from
2019
to
now,
and
that's
like
across
all
the
orgs,
I'm
just
grabbing
the
spreadsheet.
Now
to
pull
it
up.
A
So
our
our
current
contributors
are
doing
more
work
overall,
like
I
don't
know
about
everyone
else,
but
like
I
know,
I've
been
feeling
pretty
burned
out
and
I
I
a
lot
of
other
contributors.
I've
talked
to
have
also
been
feeling
burned
out,
there's
a
lot
that
plays
into
that.
In
fact,
like
there
was
a,
I
think,
a
some
research
that
came
out
or
a
paper
or
whatever
that
came
out
not
too
long
ago.
A
This
isn't
something
I
necessarily
have
a
fix,
but
at
least
wanted
to
like
bring
this
up
to
everyone
on
some
of
these
challenges,
one
other,
so
it's
just
like.
So
this
is
graph
this
one's
graphed
over
time,
but
you
can
see
this
little
big
peak
in
new
contributors
is
right
at
the
time
of
hacktoberfest
last
year.
So
like
this,
this
is
this
sort
of
throws
out
the
the
data
a
little
bit,
but
it's
still
like
good
signal.
A
And
this
green
line
here
is
our
average
pr
workload
like
the
total
number
of
prs,
I'm
like
completing
each
release
cycle.
So
again,
that
is,
looks
like
110
to
120,
so
like
really
not
much
of
a
difference,
release
of
really
release,
but
our
current
contributors
are
definitely
picking
up
more
of
the
work.
F
We
did
some
like
analyzation
and
openstack
at
some
point
of
like
over
time,
like
how
many
people
do
the
majority
of
the
work,
and
it's
like
a
little
bit
scary,
where
I
think
it's
like
under
100.
People
do
like
90
of
the
work
or
something,
but
I
think
that's
actually
a
pattern
in
a
lot
of
open
source
communities
once
they
like
stabilize.
C
F
Like
you,
you
have
a
group
of
like
highly
involved
and
like
really
project
aware
people
that
are
doing
the
majority
of
the
work
and
it's
hard
to
mentor.
People
up
to
that
point
to
like
help
supplement
those
that
like
leave
the
community
or
like
yeah
or
whatever
so
like
yeah,
burn
out
scary,
big
problem
everywhere.
A
The
the
other
thing
like-
and
this
is
this
is
sort
of
like
a
hot
take
for
me-
is
that
the
kubernetes,
I
won't
say,
is
like
past
the
hype
phase.
A
But
at
this
point,
like
a
lot
of
like
vendors
and
other
groups,
are
prioritizing
like
the
other
projects
that
run
on
top
of
kubernetes
and
not
necessarily
kubernetes
itself.
F
Yep
yeah
you're
on
the
unfortunate
crappy
part
of
the
hype
curve,
where
you're
going
down
to
the
plateau,
but
you'll
get
to
the
plateau
and
it'll
be
great.
Let
me
tell
you.
A
The
the
one
thing
that,
like
a
a
lot
of
our
sigs,
do
need
better,
like
onboarding
documentation
for
themselves.
I've
talked
to
a
few
groups
about
this:
a
few
other
paths
on
potentially
adding
more
roles
to
help
just
give
people
a
leg
up
and
getting
started
into
some
of
those
of
those
areas.
A
But
the
my
other
general
thought
is
like
a
lot
of
the
sigs
need
to
prioritize
more
to
like
try
and
avert
further
burnout.
And
I
don't
have
like
a
necessarily
answer
to
this
or
anything
like
that.
But
something
for
folks
to
like
mull
over
and
think
about.
A
D
I
was
going
to
say
one
thing
that
I've
been
noticing
is
people
saying
they're,
not
really
sure
how
to
get
acknowledgement
up
to
their
superiors
in
general,
like
on
smaller
companies.
Maybe
larger
companies
are
easier,
but
a
lot
of
the
smaller
companies.
I
talk
to
it's
kind
of
hard
to
say
like
well,
I'm
over
here
doing
all
of
these
other
things
and
they're
still
expect
to
keep
the
velocity
on
the
projects
they
work
on
during
work.
D
I
don't
know
if,
like
it's
kind
of
hard
to
like
hand
out
badges
or
things
like
that,
that
make
it
a
little
more
obvious,
but
they're
constantly
engaged
with
a
community,
but
I
know
that's
worked
in
the
past
and
other
things.
I've
done
that
kind
of
acknowledgement.
So
I
don't
know
if
that
might
be
something
that
might
help.
A
Yeah
I've
been
as
like
part
of
the
problem,
too,
is
like
kubernetes
is
so
big
that,
like
we
do
contributor
awards
and
things
like
that,
and
we
gave
out
like
more
than
50
last
year
and
that's
still
just
a
tiny
part
of
our
overall
community.
A
D
I
know
linux
foundation
does
I
think
if
they're
called
a
claim
is
the
company,
but
they
do
badges
like
verified
badges
for
program
committees?
Things
like
that
that
you
can
put
on
your
linkedin
if
we
already
have
access
to
it.
A
That
is
a
potential
idea.
I
know
I
don't
know
how
much
like
people
actually
put
into
like.
C
I
think,
like
with
all
things
kubernetes
people
would
care
about
this.
One
right,
like
yes,
linkedin,
tries
to
add
more
badges
as
part
of
their.
You
know
overall
overarching
marketing,
whatever
schemes,
but
if
people
could
actually
say
like
listen,
I
have
these
responsibilities
and
duties
within
the
project.
C
C
F
C
F
Yeah,
it
definitely
works
for
a
while,
but
don't
sprawl
too
much.
I
guess.
A
It's
like
that's,
contributes
controversy
used
to
have
like
triage
roles,
but
we
don't
get
enough
into
like
k
community
to
really
warrant
triage
roles
so
that
just
kind
of
went
up
not
being
abandoned,
where
we
have
some
other
like
really
well
defined.
Roles
is
stuff.
Like
the
events
team
marketing
has
you
know
a
bit
more
so
just
like.
I
know
a
couple
other
six
that
could
potentially
come
up
with
some
other
ones
too.
A
It's
a
new
contributor
vote
for
a
badge,
so
I
actually
have
something
that
I
cannot
send
a
recorded
call
also
about
this
with
regard
to
that.
So
maybe
maybe
once
this
is
over.
A
A
Okay,
dev
stats
laurie's
in
here
I
don't
have
an
update
on
this
one.
Either
there
will
be
some
new
dashboards
launching
soon
that
is
partially
blocked
on
me
to
write
a
script
to
crawl,
the
kk
repo
for
some
additional
stats,
but
soon.
A
A
The
lf
has
been
trying
to
get
rid
of
their
current
cla
system
for
some
time
now
and
they
rewrote
it
like
from
the
ground
up
in
a
new
thing
called
easy
cla,
but
this
also
involves
a
fairly
large
database.
Migration
re-enabling,
like
some
other
stuff
with
rci
and
a
host
of
things
I
had.
I
did
an
audit
with
them
and,
like
a
bunch
of
our
org
members,
were
not
found
in
the
cla
system.
A
So
there's
been
some
some
oops
stuff
there
when
we
expanded
the
the
scope
of
the
audit
out
to
like
pr
authors,
something
like
800
were
missing
and
so
currently
diving
down
that
that
path
with
them
to
try
and
get
all
that
sorted
out
before
potential
migration.
Unfortunately,
the
people
that
can
work
on
this
is
also
fairly
limited,
because
you
must
be
a
github
admin
and
you
must
have
access
to
the
easy
cli
system.
A
A
But
once
that's
done,
our
target
time
frame
for
switching
over
the
new
system
will
be
the
second
week
of
august.
The
week
of
august,
9th.
A
A
Happens
does
I
think,
that's
mostly
it
at
least
regarding
github
management.
Does
anyone
have
any
questions
about
that
fun.
A
Okay,
nothing
from
slack
infra,
that's
sort
of
the
rock
events.
D
If
I
can
hit
unmute
on
this
computer,
so
I
I've
also
been
out
a
little
bit,
so
I'm
just
kind
of
getting
back
and
getting
reorganized,
there's
an
open
pr
to
update
the
website
and
the
repo
with
information
about
the
new
format
for
the
community
meeting.
Also,
along
with
that
oksana,
I
think
I'm
sorry
if
I
pronounce
the
name
wrong.
Hi.
D
Okay,
oksana
is
going
to
be
our
host
for
july,
so
that's
very
exciting
and
I
will
be
catching
up
with
you
either
later
this
week
or
early
next
week
to
kind
of
get
everything
organized
for
that,
and
there
was
something
else
that
I
had
about
the
community
meeting
hold
on.
D
D
We
were
talking
about
doing
a
couple
of
other
things,
just
to
maybe
clean
up
the
community
meeting
a
little
bit,
but
we're
going
to
keep
on
with
the
format
for
a
little
bit
see
if
we
can
start
getting
some
traction
as
long
as
it's
regular.
I
think
people
will
do
that
and
I
need
to
help
follow
up
regarding
the
calendar
situation,
but
I
know
that's
kind
of
a
huge
thing,
but
I'm
putting
myself
on
the
table
to
help
with
that.
A
There
is
also
an
initiative
there's
an
open
issue
in
steering
that
is
semi-related
regarding
migrating
everyone
over
to
kubernetes,
managed
accounts
and
being
able
to
automate
some
of
that.
D
C
D
Oh
so
sorry
they
asked
about
the
youtube
videos
is.
I
need
the
links
for
the
may
and
june
community
meetings.
I
can't
find
them
in
the
playlist,
so
I
don't
know
where
I
find
them.
So
I.
A
C
D
People
I'm
gonna
bump
up
and
annoy
people,
but
yes,
please
and
thank
you
and
I
will
open
up
an
issue
and
find
the
steering
issue
and
try
to
connect
everything.
Yeah.
D
But
those
are
the
big
issues.
Those
are
the
big
things
about
the
community
meeting.
D
D
We
haven't
been
very
good
about
doing
it,
mostly
because
I've
been
one
of
those
like
oh
wait,
it's
the
third
week.
How
did
this
happen?
That
happens
a
lot
for
me,
so
I
don't
know
what
day
it
is.
D
A
D
D
D
Okay,
you'll
have
a
good
time
so,
anyway,
back
to
you,
mom.
A
Yep
I
was
hoping
deb
would
be
able
to
make
it
by
now.
She
said:
she'd
be
like
20
to
30
minutes
late,
so
maybe
things
are
just
taking
a
bit
more
time.
The
big
thing
with
the
contributor
summits
is
at
this
point.
You
know:
we've
we've
sort
of
done
the
pre-work.
A
We
are
now
spitting
up
the
team
to
actually
start
hand
like
we're
going
to
schedule
the
the
weekly
meetings
and
assembling
the
team
to
handle
that
I
sent
an
email
out
to
the
contrabex
mailing
list
and
there's
an
open
issue
in
k
community
for
calling
for
volunteers.
A
There
are
some
some
roles
for
both
people
that
aren't
planning
on
attending
or
like
being
able
to
attend
in
person.
I
should
say,
and
for
those
that
will
be
there
in
terms
of
compared
to
our
previous
computer
summits,
this
will
probably
be
a
lot
more
lighter
weight
just
because
we
honestly
have
no
idea
on
attendance.
C
A
A
Yeah
goal
is
to
get
that
squared
away,
essentially
like
one
week
from
now,
so
that
way
we
can
then
get
the
doodle
pull
and
all
that
out.
A
The
other
thing
I
just
want
to
get
in
people's
minds
it's
still
a
little
early,
but
the
steering
election
that
will
be
happening
later
this
year.
There
is
a
conflict
with
our
normal
schedule
and
kubecon.
A
So
there's
going
to
be
a
like
we're
going
to
talk
about
in
the
steering
meeting
of
whether
like
should
the
election
results
happen
before
post
kubecon
type
thing
to
try
and
nail
out
at
least
when
a
beginning
and
end
happens,
but
that
will
be
we'll
be
looking
to
assemble.
That
team,
like
probably
by
the
end
of
the.
A
Month,
I
think
that's
it
as
far
as
events
at
this
point
does
anyone
else
have
any
questions
comments.
A
Okay,
we're
done
with
the
vents.
Are
there
any
other
general
open
mic
discussion
items
that
people
want
to
bring
up.