►
From YouTube: [SIG ContribEx] Weekly Meeting 20210804
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
first
kinder
books
meeting
in
august.
I
am
your
host
today
killen
one
of
the
co-chairs
of
signature
bex
and
to
get
a
few
things
out
of
the
way
these
meetings
are
recorded.
They'll
be
posted
the
internet
later
today,
and
we
abide
by
a
code
of
connect
which
essentially
boils
down
to
please
be
excellent
to
each
other.
Oh
my
god,
sorry
mike
my
cat
was
like
mickey
more
and
bit
my
foot.
A
Okay,
I
guess
with
that:
let's
actually
do
some
intros
I'll
toss
it
over
to
well
we'll
do
the
hot
potato
game
and
I
will
toss
it
over
to
josh.
B
Howdy,
I'm
josh
burkus
and
doing
my
best
queen
video
impression,
because
I'm
on
my
laptop
camera,
the
and
I
work
a
little
bit
on
mentoring
and
on
a
variety
of
other
things,
including
the
upcoming
steering
committee
elections,
which
I'm
gonna
add
to
the
agenda.
As
soon
as
I'm
done
talking.
And
let
me
pass
it
over
to
kim.
C
Hey
everyone,
I'm
kim,
I'm
a
developer
advocate
at
digitalocean,
focusing
on
kubernetes
and
I'm
hoping
to
get
more
involved
in
the
kubernetes
community.
So
here
I
am
so.
C
Well,
thank
you
laura.
D
Hi
so
I'm
laura
santamaria,
I
am
a
developer
advocate
at
volumi
and
I
help
manage
the
commun,
the
community
meeting
and
I'm
part
of
contributor
summit
this
round
and
I'm
on
slack
a
lot.
But
I
miss
like
half
the
zoom
meetings
all
the
time.
So
that's
me
and
I'm
going
to
toss
it
to
allison.
E
Hey
everyone,
I'm
allison,
I'm
a
co-chair
for
his
contributor
experience.
It
is
a
very
lovely
sunny
but
cloudy
day
today
in
london
and
yeah
good
to
see
everyone
here
on
the
line,
I'm
gonna
pass
the
hot
potato
over
to
kathleen.
F
Hi
everyone
I
joined
in
the
middle
of
the
introductions,
so
I'm
not
sure
who
hasn't
gone
yet.
So
if
someone
hasn't
gone
yet,
please
jump
in
after
me,
but
I'm
caslin
fields
and
I'm
a
developer
advocate
at
google
and
I'm
a
member
of
the
sub
project.
That's
the
right
terminology!
Isn't
it
of
the
controbex
group,
which
is
focused
on
contributor
communications,
both
communicating
with
communicate
with
contributors
what's
happening
and
communicating
externally
more
about
what
contributors
are
doing.
G
I
I
can
go
next,
so
hi.
Thank.
G
Is
this
better
yeah?
Okay,
thanks
so
hi,
I'm
madhav,
I'm
currently
a
student,
but
I've
been
doing
like
I'm
in
a
lot
of
other
places
in
the
community
right
now.
This
is,
I
think,
my
second
contrabex
like
zoom
meeting.
Otherwise
I'm
usually
there
on
like
the
async
meetings,
but
it's
nice
to
be
here
thanks,
I'm
not
sure
who
hasn't
gone.
You
know.
Would
you
like
to
go
next.
H
A
Okay,
that's
okay,
with
that,
let's
jump
right
into
sort
of
our
regularly
scheduled
business
and
that's
first
with
events.
A
D
Me
so
right
now,
august's
community
meeting
is
going
to
be
the
retro
for
release.
We
thought
it
might
be
good
to
kind
of
blend
the
two
together
just
because
that
way
lots
of
people
will
join.
Hopefully,
possibly.
There
also
was
a
discussion.
I've
been
meaning
to
bring
this
up
in
a
meeting,
and
I
think
this
is
the
first
one.
I've
actually
been
in
person
at
there
was
kind
of
a
discussion
about
whether
whether
the
community
meeting
is
working,
whether
we
should
persist
with
the
current
model.
D
D
I
think
the
big
thing
we're
really
running
into
right
now
is
just
you
can't
get
it
on
people's
calendars,
so
we're
working
on
that
problem
so
like
that,
I
know,
there's
updates
on
that.
So
I
think
that's
the
main
thing,
and
there
probably
is
some
zoom
fatigue
as
well,
but
I
wanted
to
bring
it
up
because
I
know
the
one
big
thing
that
we
run
into
is
that
it
does
take
a
lot
of
like
work.
A
I
do
think
like
it's
worth
running
with
the
current
sort
of
idea
we
want
for
it.
I
do
think
that
the
biggest
problem
has
just
been
getting
on
people's
calendars,
but
we
we
now
have
an
update
there
and
that
we
can
actually
export
the
kdev
list.
Now
we
were
not
able
to
previously
do
that
so
like
theoretically,
a
migration
now
should
be
very
simple.
D
Okay,
I
was
wondering
what
the
k
dev
export.
I
knew
that
was
important,
but
I
wasn't
100
sure
why,
but
now
you're
saying
it's
so
that
we
can
migrate
over
to
a
different
system.
Yep.
A
We'll
be
able
to
have
a
like
dev
at
cabrinis.io,
a
managed
account
that
we
can
actually
like
send
calendar,
invites
to
and
not
run
into
the
api
limits,
because
the
bit
the
list
is
so
big
and
once
that
and
we
get
start
getting
things
on
people's
calendars.
It's
the
same
thing
I
think
with
like
meet
our
contributors
like
yeah.
The
big
problem
is
we,
unless
we,
you
know
invite
every
six
individual
mailing
list
we're
not
going
to
get
folks,
but
all
right.
D
D
D
So
I
don't
know
if
we
want
to
talk
about
that
later
or
if
we
want
to
talk
about
that
now.
I
know
I
volunteered
to
kind
of
help
get
the
ball
rolling,
so
I
can
set
up
to
put
a
plan
together,
but
I
think
I
really
should
talk
to
contributor
coms,
because
I
don't
really
know
what
I'm
doing
making
comms
so
yay.
D
G
A
A
A
Okay,
the
contributor's
assignment
things
are
progressing.
Well,
we,
the
reg
form,
is
now
live,
although
we've
not
sent
out
comms
or
updated
the
website,
yet
we
are
still
sort
of
checking
along
with
our
original
idea
and
plan.
I
can
drop
the
link
to
like
the
planning
dock
there.
A
I
think,
like
the
next
big
thing
that
we
need
to
decide
sooner
rather
than
later,
is
the
where
we're
actually
hosting
the
social
event
and
just
to
make
sure
we
can
get
the
the
quote
and
lock
down
the
space.
A
If
you
are
interested
more
in
the
contributor
summit
stuff,
there's
a
separate
meeting
on
mondays-
I
don't
it's
sometime
in
the
afternoon,
but
you
should
all
have
to
invite
if
you
join
the
the
kendrick's
mailing
list,
but
if
that's
something
you're
interested
in
helping
with
that's
like
following
along,
there
is
the
best
place
to
to
get
involved.
B
Yeah,
so
our
first
step
in
terms
of
starting
up
a
steering
election
is
selecting
an
election
committee,
I'm
going
to
be
in
the
election
committee
this
year,
because
I
kind
of
have
to
because
this
will
be
our
first
steering
election
with
alexo.
B
Normally
we
have
a
three-person
election
committee
and
how
we
did
it
last
year
was
we
divided
up
into
three
roles,
one
of
which
was
general
tech
running
the
election
system,
one
of
which
was
so
maintaining
the
voter
list
and
then
the
third
one
of
which
was
columns
basically
sending
out
all
the
messages
around
the
election.
B
So,
as
far
as
I
know,
we're
still
looking
for
the
voter
list
person
and
the
comms
person
for
the
election,
and
particularly
this
year,
I
would
like
at
least
one
of
those
two
people
to
be
interested
in
learning
the
technical
mechanics
of
running
alecto
so
that
they
can
be
the
continuation
next
year,
and
I
don't
have
to
be
so.
If
anybody's
interested
in
that
the
go
ahead,
and
let
me
and
bob
know.
B
Ask
okay
with
the
with
the
hitch
that,
because
it
is
the
steering
committee
election,
it
can't
be
either
broburg
or
short.
B
The
that's
one
of
the
other,
that's
actually
one
of
the
other
hitches.
Is
we
really
want
the
three
people
to
all
have
three
different
employers.
A
Comments,
then
that
will
take
us
over
to
mentoring
and
meet
our
contributors.
I
think
the
big
thing
here
is:
we
now
actually
have
stream
yard
it's
all
configured
and
the
the
hard
part
is
calendars
and
sending
calendar
invites,
which
should
also
be
resolved
by
some
of
the
the
mailing
list
stuff.
I
We
have
updates
about
about
halifax
mentoring,
so
we
are
kicking
off
the
fall
of
fall
cycle
pretty
soon
and
for
the
reference
here
is
the
link
with
the
attentive
schedule
when
we'll
have
and
we'll
have
the
next
step.
So
I
know
that
there
have
been
a
few
people
in
the
community
who've
been
curious
about
the
dates
of
the
lfx
mentoring
program
for
the
full
cycle.
So
here
are
the
actual
dates.
I
As
usual,
the
mentoring
cycle
itself
will
happen,
like
the
dates
are
since
september,
1st
till
the
end
of
november,
and
during
the
next
week,
we'll
have
all
the
projects
listed,
who
are
participating
in
the
program
and
mentees
will
be
able
to
participate
in
them
and
not
just
participate,
but
apply.
I
There
are
no
updates
on
the
grcc
side,
so
everything
is
smooth
and
the
end
of
program
is
by
the
end
of
august.
So
my
news
coming
soon,
but
we
have
17
mentees
this
time
around
with
all
sincere
projects.
Nice
curious.
I
19,
I
believe
1908
or
18.,
so
basically
the
same
number.
Okay,.
I
Yeah
yeah,
like
I
remember
like
for
the
last
three
or
four
consecutive
years,
we
have
like
something
around
20-90
years
per
year,
so
basically
the
same.
The
same
number.
A
Cool
any
questions
comments
regarding
those
outreach.
E
Hello
so
contributor
workshop
stuff
current
state
of
it
is
we
had
a
good
chat
about
the
things
on
monday,
where
we're
going
to
potentially
be
getting
the
technical
writers.
I'm
sorry,
I
always
forget,
like
full-on
context
of
this
there's
gonna
be
technical
writers
from
the
google
season
of
docs.
I
think
budget
wasn't
was
it
that
one
wasn't.
A
Not
from
the
seasons
of
doc's
budget
but
yeah,
I
I
have
earmarked
money.
I
work
for
google.
I've
set
aside
some
money
to
bring
on
tech
readers
to
help
us
with
the
new
contributor
workshop.
E
So
we're
gonna
get
some
help
with
that
soon.
Hopefully
I
still
need
to
get
the
like
page
layout,
all
kind
of
there
and
then
from
once
the
page
layouts
there.
It's
just
a
sense
of
translating
the
information
that
we
have
already
into
more
of
like
a
guide
format
so
like
from
the
slides
and
talks
format
to
to
a
doc's
style
yeah.
So
that's
the
update
from
there.
A
Cool,
thank
you.
Does
anyone
have
any
questions
regarding
the
new
contributor
sort
of
workshop
course.
G
I'm
I
couldn't
attend
the
monday's
meeting
regarding
the
contributor
summit,
but
if
there
is
anything
required
like
if
there's
any
help
record
with
the
content
of
ncw,
I
can
probably
help
out.
So
I
helped
run
a
few
new
contributor
workshops
for
a
couple
of
kcd
events
over
here.
So
I
can
try
and
help
out.
A
Nice
there
are
a
bunch
of
open
issues
in
github
and
we,
I
think,
they're
all
prefixed
with
like
ncw
or
like.
Do
you
remember
the
the
prefix
allison.
A
So
if
that
helps
too.
A
Oh
no
yeah,
it's
it's
a
for
this
summit
and
just
like
we've
had
a
lot
of
issues
with
running
the
new
computer
workshops
in
person
at
events,
and
it's
like
a
huge
like
strain
on
a
bunch
of
staff
and
especially
with
the
uncertainty
this
year
with
like
who
can
be
there
like.
We
are.
We
are
not
doing
a
new
contributor
workshop
at
all
for
the
summit.
A
G
B
Ever
because,
if
you
look
at
the
number
of
people
who
attended
the
new
contributor
workshop,
you
know
for
the
people
whose
github
ids
we
have
and
their
contribution
history.
After
that
I
forget
who
did
this,
but
somebody
did
an
analysis
on
the
first
three
of
them
and
there
was
just
a
severe
fall
off
like
the
first
one.
We
got
a
bunch
of
new
contributors
who
hung
around
and
after
that
there
was
kind
of
a
steep
decline.
B
The
now
I
understand
that
various
meetups
have
had
better
results
with
doing
local
new
contributor
workshops,
and
so
I
think,
still
having
some
kind
of
a
kit
for
them
to
do
a
local
small
one
makes
sense.
I
think
those
are
probably
more
effective
than
the
ones
at
kubecon
completely.
A
Agree
there,
oh
actually
one
one
thing
of
note:
sort
of
this
is
going
back
to
contributing
summit,
slash
events.
We
do
have
space
for
a
sig
meet
and
greet
during
kubecon
itself.
A
So,
in
addition,
I
believe
the
time
is
like
wednesday
morning.
A
A
A
Okay
off
to
community
management
start
with
the
need
to
know
chair
tl
email.
We
have
several
things
sort
of
on
the
docket
that
should
be
added
to
that,
namely
around
the
contributor
summit.
So,
and
just
like
a
reminder
that
hey
the
steering
committee
election
will
be
coming
up.
A
The
other
big
thing
is
the
general
discussion
around
like
potentially
making
like
tech
leads
mandatory
in
terms
and
term
limits,
and
that's
going
to
be
sort
of
discussed
at
some
future
chair
and
tl
meetings.
A
A
Send
to
all
the
things
I
guess
this
would
actually
probably
be
the
best
place
to
also
discuss
that
the
k-dub
migrations
are,
you
know,
jumping
back
to
our
earlier
earlier
chat.
A
A
I
don't
know
if
other
people
have
thoughts
but
like
I
just
want
to
make
sure
that
we,
like
all
our
steering
election
coms
like
go
to
the
place.
People
expect
them.
D
D
B
B
G
D
I
thought
that
you
were
saying
that
alecto
is
like
a
new
platform
for
yeah,
so,
like
I
wouldn't
have
a
brand
new
voting
platform
and
migrating
kdev.
At
the
same
time,
I
think
that
would
get
people
too
confused
have
like
one
thing:
change,
which
is
the
election
system,
the
voting
system
and
then
leave
k
dev
alone
until
after
so
I
agree
with
the
assessment
of
one
thing
and
doing
kw
later.
B
B
Like
I
mean,
obviously,
I'm
trying
to
recruit
a
comms
person,
this
is
going
to
be
partly
up
to
them,
but,
but
you
know
given
how
many
times
we've
been
saying:
oh
yeah,
we
should
resume
doing
this
thing,
but
the
calendar
is
a
problem.
B
A
B
The
well
so
then,
that's
a
question
of
who
has
time
to
work
on
this
during
august
yeah,
the
one
of
my
other
questions
about
this
is
so
we
planning
on
doing
a
straight
migration
now
that
we
can
actually
extract
the
names.
A
Yep,
the
one
other
nice
thing
with
the
exported
list
is,
it
includes
all
the
emails
that
are
bouncing
so
be
able
to
screen.
B
B
So
it's
still
gonna
the
the
wow,
so
google
groups-
don't
google
groups,
don't
unsubscribe
those
people
automatically.
B
B
A
B
The
yeah
I
like
I
said
before
it's
not
so
much
getting
so
like
elections
honestly,
would
be
one
of
the
least
affected
things
by
the
switch
because,
like
the
only
thing
that
happens,
then
is
any
comms
we
sent
about.
Elections
need
to
be
sent
to
both
lists,
both
the
old
and
the
new
one
and
beyond
that,
it's
not
we're
not
dependent
on
the
list
for
people's
permissions
to
vote.
B
What's
going
to
be
painful,
for
the
switchover
of
lists
is
permissions
on
google
documents
yep.
The
other
thing
is
like.
A
B
Everyone
yeah,
so
it
sounds
like
next
step,
would
be
both
from
this
meeting
and
then
out
on
slack,
etc,
to
see
who's
interested
in
helping
with
us,
because
we
probably
want
five
or
six
people
who
who
are
interested
in
in
helping
with
the
migration
yeah
to
carry
it
off
the.
And
if
we
don't
get
those
five
or
six
people,
then
then
we
maybe
want
to
you
know.
Maybe
we
do
want
to
delay.
A
A
I
just
like
the
I
think,
the
biggest
thing
it'll
just
be
coordinating
the
comms
is
just
like.
We
are
migrating
to
this
list.
We
actually
want
to
do
it
for
all
all
of
the
the
sig
mailing
lists,
but
then
give
people
an
explicit
date
and
of
when
this
change
will
happen.
A
B
A
The
other
one
will
just
be
like
updating
all
the
various
all
our
docs
for
that
reference.
Kdev
yep.
D
D
A
B
B
B
F
A
Hey,
I
don't
know
if
it'd
wind
up
working
out
like
because
the
main
thing
is
we're
trying
to
get
the
like
the
the
leads
are
the
people
that
would
probably
be
like
have
the
least
problems
changing.
If
that
makes
sense,
just
because,
like
they'll
deal
with
it,
where
is
trying
to
catch
the
general
problems
or
no.
A
Yes,
it's
just
that
a
person
has
to
like
someone
the
someone
that
the
person
that
exports
the
list
has
to
have
admin
access
to
the
list,
so
it'd
be
like
if
we're
if
it
was
for
like
sig
release,
would
either
have
to
go
in
as
like
contributors
at
to
export
the
list
or
like
have
myself
added
as
an
admin
to
the
list
to
export
it
and
then
like
sort
of
seed.
The
new
one,
okay,.
H
H
A
The
big
thing
would
just
be
the
I
guess,
the
the
the
time
frame
and
how
fast
we
can
make
make
the
the
transition
from
working
group
to
sig
happen.
B
A
Okay,
so
are
there
any
more
thoughts
on
the
the
kid
of
migration?
At
this
point,
it
sort
of
sounds
like
our
next
action
items
are
to
a
start
drafting
all
the
co
like
recruit,
a
team
draft,
the
coms
and
then
test
with
like
kate,
sinfra
and
or
controvex.
D
A
Okay,
any
more
sort
of
things
on
that
subject.
F
Hi
sounds
like
there's
quite
a
bit
of
work
shaping
up
for
us,
which
is
exciting.
I
went
ahead
and
put
in
our
note
stock.
The
contributor
coms
team
meets
on
fridays
at
8,
pm,
pacific
time
or
8
am
pacific
time.
What
am
I
saying
so?
I
went
ahead
and
updated
our
note
stock
with
some
of
the
asks
from
this
meeting.
F
I
put
in
a
note
about
having
someone
taking
ownership
of
working
with
the
steering
election
committee
to
make
sure
that
we're
getting
out
comms
about
the
steering
election
and
also
about
the
kdev
email
list,
and
I
actually
missed
our
last
meeting
but
I'll
pull
some
notes
from
our
note
stock.
F
F
Contributors
on
it
there
we
go
yes,
so
comm's
about
the
contributor
summit
is
on
our
list.
From
last
week
we
were
talking
about
columns
about
registration
and
the
cfp
for
the
contributor
summit.
F
If
that's
going
to
be
a
thing
and
said
to
reach
out
to
laura,
so
that's
good
and
then
bart
farrell
from
our
group
is
doing
some
really
awesome
work
with
creating
a
video
series
to
highlight
the
work
of
contributors
he's
having
a
few
contributors
to
these
short
little
videos
talking
about
their
experience,
contributing
to
kubernetes,
which
is
pretty
awesome,
so
figured
I'd,
throw
that
out.
F
A
A
Then
contributor
docs,
I
personally
don't
have
any
updates.
Does
anyone
have
updates
on
docs
at
this
point
in
time.
A
Okay,
then
we'll
move
on
to
github
management.
The
biggest
thing
is
the
easy
cla
migration
which
we
still
want
to
try
for
next
week.
The
problem
is
that
the
pr
to
actually
add
the
support
to
our
ci
is
still
open.
A
We
have
not
tested
it
yet,
and
it's
it's
just
been
a
lot
of
back
and
forth.
I
can
let
me
dig
up
the
issue
quick.
A
But
essentially,
as
soon
as
that
merges
for
me,
it
is
sort
of
like
p0
to
test
that.
So
that
way
we
can,
we
can
get
it
going.
A
A
A
I
would
only
push
out
comms
at
this
point
if
the
ci
test
is
successful.
Well,
well,
not
successful,
but
the
results
of
the
ci
test
like
yes,
we
are
continuing
to
move
forward
with
this
or
no,
we
are
not
moving
forward
with.
This
is
the
thing
that
we
should
send
out.
G
Yeah
I
had
a
question
regarding
guitar
management,
so
recently
I've
been
note.
Sorry
is
okay.
I
forgot
okay
anyway,
so
recently
I've
been
noticing
that
across
a
lot
of
repositories,
there
are
a
lot
of
good
first
issues
or
headquarters
that
are
coming
up,
which
is
awesome,
but
one
issue
that
I
think
is
there
is
that
a
lot
of
people
aren't
giving
near
enough
context
for
it
to
be
marked
as
one
even
through
the
bot
prompts
saying
that
these
are
the
guidelines
for
it
to
be
qualified
as
one
so
you
what
happens.
G
A
lot
of
the
times
is
that
people
who
pick
up
those
issues
a
lot
of
them
like
reach
out
to
me
saying
that
hey,
can
you
help
me
out
or
they
reach
out
to
someone
else
saying
hey?
Can
you
help
me
out,
so
I
usually
like
go
and
like
go
through
the
code
base,
go
through
the
issue
and
like
leave
a
few
comments,
giving
context,
but
I
don't
think
that's
the
right
way
to
like
always
go
about
it.
G
So
I
wanted
to
ask
if
there
has
been
any
previous
discussion
regarding
a
better
way
to
maybe
prompt
or
a
better
way
to
indicate
that
something
like
this
like
importance
of
like
giving
enough
context.
So
usually,
what
also
I
recently
started
doing
is
like
periodically
going
through
the
good
first
issues
or
the
help
wanted
ones,
and
if
there
isn't
like
enough
context,
I,
like
ping,
the
author
on
the
issue
page
and
remove
the
label
first
and
saying
that
once
you
give
these
contacts,
please
feel
free
to
add
the
label
once
again.
G
B
A
A
I
don't
think
there
has
been
previous
discussion
on
that.
There's
been
like
on
that
issue.
Specifically,
one
of
the
things
is
like
anyone
can
flag
an
issue
as
good
first
issue,
so
I
think
it
would
be
like
more
so
like
sending
a
reminder
or
something
like
that
out
to
potentially
get
more
more
people
like
sort
of
in
the
know
like
hey,
you
need
to
provide
more
information
about
this
about
these
things.
B
But
there's
there
isn't
really
any
better
way
to
do
it,
except
one
at
a
time
because,
ultimately,
like
for
a
lot
of
issues
for
a
lot
of
you
know
issues,
you
need
the
original
author
of
the
issue
to
modify
their
thing,
or
at
least
you
need
somebody
with
knowledge
of
that
area
of
the
code
to
provide
the
context.
B
G
In
general,
like
not
any
particular
so
like
folks
reach
out,
they
find
good
first
issues
in
like
either
casings
or
sometimes
care
client,
but
mostly
in
kk
also,
so
they
reach
out
saying
that
hey.
Can
you
help
me
out?
This
is
a
good
person,
but
I'm
not
sure
what
to
do
here
or
how
to
get
started.
G
So
I
I
try
and
like
provide
some
context
through
comments,
but
I
was
just
wondering
if
there
was
better
gender
better
but
a
reminder,
something
a
good
idea
or
like
something
in
the
form
of
a
reminder,
because
I
understand
that
it's
not
really
anyone's
fault
here,
also
like
people
who
create
the
issue.
Also,
it's
not
really
like
you
there's
no
there's
no
blame
game
over
here
as
well.
So
I
was
just
wondering
if
there
was
anything
else
that
people
had
in
mind
for
improving
this.
B
The
only
thing
I
can
say
is
feel
free
to
say
that
you're
doing
that
on
behalf
of
sig
contributor
experience
the
I
I
can't
think
of
something
different.
You
can
do.
You
know,
aside
from
the
additional
hey
ping,
the
issue
author
and
slack,
particularly
if
you're
not
in
a
position
to
supply
the
additional
context
like.
Obviously,
if
you
know
enough
to
put
the
additional
context
in
there
as
a
comment,
then
just
do
it
because
that's
going
to
be
the
fastest
way
to
get
the
good
first
issue
up
to
date.
B
But
if
you
don't,
which
is
gonna,
be
true
with
a
lot
of
issues,
then
you
know
ping
the
person
in
a
comment,
but
also
ping
them
on
slack,
because
a
lot
of
our
contributors
are
just
not
checking
their
github
notifications
because
they
get
too
many
of
them.
The
and
say
you
know
and
part
of
it,
I
think,
would
be
good
to
supply
contributors
with
this
sort
of
bullet
point
list
of
the
things
that
they
need
to
cover
for
a
good
first
issue,
because
I
think
a
lot
of
people
don't
know
the
actually.
A
B
Well,
I
mean
I
don't
see
why
we
couldn't
do
that
on
all
the
relevant
repositories.
It'd.
B
Admins,
the
the
the
bigger
issue
is
that
a
lot
of
things
don't
start
out
as
good.
First
issues
yeah.
They
start
out
as
regular
issues
and
then
get
converted
into
a
good
first
issue,
and
that
would
bypass
the
template
entirely.
But
there's
no
harm
in
having
the
template.
D
What
what
about
a?
What
about
a
github
action,
if
I
think
we're
doing
some
github
actions
or
maybe
it's
a
proud
bot
thing?
What
about
adding
something
that
just
says:
if
you
add
the
label,
then
it
gives
you
the
checklist
as
a
comment.
G
D
B
D
Yeah
you're,
probably
not
going
to
get
people
reading
I'll,
be
honest.
A
lot
of
people
don't
really
read
no
matter
how
many
times
we
love
putting
all
kinds
of
stuff
all
over
the
place,
but
having
the
checklist
right
there
with
their
name
attached
to
it,
makes
it
clear
and
then
somebody
coming
to
the
issue
can
go.
Oh,
they
haven't
finished
the
checklist.
So
this
isn't
really
a
good
first
issue
for
me
to
pick
up-
or
at
least
they
know
who
to
reach
out
to
to
say.
Oh,
you
didn't
finish
this
checklist.
D
Let
me
reach
out
to
them
directly,
so
that
might
be
one
way
to
kind
of
help
it
does
it's
not
a
solution
in
the
sense
of
like
this
fixes
everything,
but
it
does
kind
of
help
out
with
some
of
that
idea,
especially
if
it
starts
out
as
a
regular
issue,
and
then
somebody
adds
the
tag
later.
G
I
think
the
reverse
is
also
very
much
true
because,
like
I
think
this
idea
about
having
it
as
a
comment
makes
a
lot
of
sense
because,
for
example,
a
few
months
back,
there
was
an
issue
in
client.
Go
with
the
author
of
flag.
Does
good
first
issue
initially,
but
then
that
issue
turned
out
to
span
over
two
whole
api
machine
team
meetings.
Just
like
people
discussing
and
debating
whether
it's
it
should
be,
whether
it
should
be
a
cap
or
a
wizard.
G
D
F
D
A
You
go
okay,
any
other
sort
of
questions,
comments
on
this
subject
or
github
management
in
general.
We
have
eight
minutes
left,
so
I
want
to
make
sure
that
we
also
get
to
the
open
items.
A
Okay,
slack
infra,
I
think
the
only
update
here
is
huddles
are
awful.
A
A
Yep
saving
a
rant
on
that
one
for
later,
but
any
other
questions
comments
on
slack
infra.
B
We
already
blocked
that
the
yeah,
but
we
have
a
lot
of
channels.
A
A
Okay,
any
questions
on
that.
H
H
H
Nope,
I
just
realized-
I
have
access
to
the
console,
but
they
do.
My
verification
is
not
that
for
communities
that
I
o.
So
I
was
curious
if
we
need,
we
still
need
to
do
that.
B
A
B
Well,
seo
would
be,
I
don't
know
who
seo
would
be
the
box,
but,
but
part
of
is
to
actually
figure
out
yeah,
probably
more
likely
docs
than
anybody
else,
since
they
control
the
website.
But
the
first
question
is
whether
or
not
it's
needed
I
mean
my
personal
experience
is
anytime.
I
search
for
a.
B
How
do
I
do
x
in
kubernetes
if
kubernetes.I
o
is
not
the
first
link,
it's
the
second
or
third,
so
I
mean
because
the
the
way
forward
on
that
is
pretty
simple,
which
is
that
we
contact
the
cncf
and
linux
foundation
does
have
at
least
a
contract
seo
expert,
and
we
have
them
go
through
things.
I'm
just
you
know.
H
B
Yeah-
and
that
is
a
problem
because
shortcut
links
do
tend
to
have
terrible
seo,
and-
and
it
is
my
experience
that
when
I'm
looking
for
something
that's
on
k8s.io,
google
often
doesn't
know
about
it.
Okay,
so
yeah.
I
think
you're
right
that
there
is
a
genuine
problem
there
and
I
don't
know
the
solution
to
that,
except
to
have
good
static
links
to
those
pages
which
then
you
know
has
its
own
infrastructure
requirements.
J
There
basically
odds
just.
A
A
Cool
and
I
will
say
like
there's:
no
big
rush
on
it,
so
if,
if
it's
it,
it's
working,
if,
if
something
comes
up,
yeah.