►
From YouTube: K8s SIG Docs meeting for 20220503
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
A
Great
and
we've
just
started
recording
over
here
at
zigdox,
welcome
to
the
bi-weekly
Steve
docs
meeting
that
we've
got
here
today,
the
Tuesday,
the
3rd
of
May
2022,
interestingly
enough
release
day
as
well
for
1.24,
so
we'll
definitely
have
some
updates
on
that
very
soon.
I
just
want
to
remind
folks
about
our
code
of
conduct
in
the
kubernetes
projects,
to
treat
everyone
with
respect
and
and
to
also
feel
free
to
ask
questions
and
you've
definitely
got
a
friendly
Community
around
you
that
are
happy
to
help.
A
You
get
the
answers
that
you
need
for
anyone
who's
joining
for
the
first
time
or
has
joined
many
times
before
I'm
Natalie,
my
pronouns.
Are
she
her
I'm
one
of
the
co-leads
of
sigdocs
and
we've
got
a
pretty
decent
agenda
today,
likely
a
shorter
meeting
but
we'll
see
how
we
go
so,
firstly,
to
get
started.
I'd
love
to
hear
from
any
new
contributors
on
the
call.
If
you
wanted
to
unmute
and
say
hello
or
perhaps
say
hello
in
the
chat,
we'd
love
to
hear
from
you.
B
Yeah
hello,
so
it's
my
first
time
here,
I've
been
working
a
little
bit
in
seek
security.
I
made
like
maybe
now
two
contributions
to
a
Juventus
website,
so
I
just
wanted
to
be
there
to.
Maybe
we
have
a
lot
to
talk
already,
but
I
wanted
to
talk
a
little
bit
about
an
issue
I
want
to
to
address
so
yeah
and
I'm.
My
I
live
in
France
and
I
work
for
a
security
company
in
Paris,
so.
A
Perfect
Maya,
thank
you
so
much
for
joining
us.
That's
great
I've
I've,
just
added
the
agenda
there
in
the
chat.
What
you
can
definitely
do
to
make
sure
that
we
get
to
your
point.
There's
a
sub-hitting
there
of
issues
in
PRS
feel
free
to
add
that
in
and
as
we're
going
through,
we'll
we'll
jump
to
that
and
be
able
to
chat
about
that
today.
Thank
you
so
much
and
welcome
great
to
great
to
have
you
on
board
thanks
any
other
new
contributors
who
wanted
to
say
hello.
C
Yep,
hello,
I'm,
David,
I,
I
work
over
at
VMware
and
I
was
just
looking
to
contribute
to
some
Upstream
work
and
some
of
my
free
time
and
kind
of
take
a
look
at
the
docs,
so
I
made
my
first
pull
request
earlier
today
for
the
kubernetes.io
site
and
that's
what
I
found
out
today
was
release
day
of
one
two
four,
so
I'm
definitely
learning
a
lot
and
definitely
looking
to
see
where
I
can
help
contribute
and
help
with
any
docs
things
and
stuff.
So
definitely
here
tap
me
anytime
and
yeah.
C
Definitely
thanks
for
thanks
for
being
so
open,
open
armed
to
new
contributors.
Coming
so
definitely
appreciate
that.
Thank
you.
Oh.
A
You
are
very
welcome.
We
are
always
happy
to
have
new
contributors
on
board
and
great
to
hear
that
first
contribution
came
in.
We
actually
have
a
really
great
system
here
in
terms
of
how
we
help
get
these
piers
and
issues
through.
It's
called
our
PR
wrangling
program
for
those
on
the
call
just
so
that
you
are
aware.
A
That's
where
we've
got
someone
who
has
a
weekly,
let's
say
schedule
that
throughout
their
scheduled
week,
they're
the
ones
who
are
chasing
up
certain
PR,
so
that
our
contributions
from
folks
like
you
David,
can
get
a
get
put
through
ASAP
a
little
bit
delayed
on
your
one,
obviously
with
today
being
being
release
today.
But
thank
you
so
much
for
for
saying,
hi
and
contributing
and
as
a
quick
reminder
to
folks,
this
week's
PR
Wrangler
is
Celeste.
A
Who
is
a
former
staff
writer
for
the
cncf?
And
next
next
week's
PRI
angular
is
going
to
be
Ray
is
on
the
call
with
us
today
as
well,
so
for
folks
needing
any
wrangling.
Kind
of
points
of
view
feel
free
to
tag
those
folks,
if
you
need
to
over
the
next
couple
weeks
to
get
some
help
from
them
great
so
before
we
move
on
just
want
to
double
check
any
other
new
contributors
that
want
to
say
hello
before
we
move
on
to
our
next
point,.
A
All
right
moving
on
we've
definitely
got
we've
just
updated
everyone
for
the
scheduled
PR
Wranglers
again
for
those
on
the
call
who
are
Wranglers
remember
remember
to
check
your
shifts.
We
will
be
having
a
small
break
in
a
couple
weeks,
given
that
it's
going
to
be
kubecon
EU
in
terms
of
wrangling.
A
So
for
folks
who
are
new
when
there's
big
events
happening,
we
likely
do
take
a
small
break
from
PR
wrangling
so
that
we
can
attend
these
events
and
and
participate
in
a
lot
of
the
work
and
conversations
that
are
going
on
around
cube,
kubecon
in
particular,
and
so
that's
coming
up
in
a
few
weeks.
So
but
we'll
be
posting
updates
in
the
seat.
Dockside
Channel
as
well,
when
those
timings
are
coming
up
too.
A
Okay.
First
thing
on
the
agenda:
the
the
person
of
the
hour
I
would
say,
or
the
day
Nate
I'd
love
to
I
head
over
to
you
to
update
on
the.
D
Current
release,
it's
not
just
me,
I,
see
it
I
see
a
a
Chris
and
Ray
and
Jim
are
all
on
it.
It's
it's
a
team,
it's
definitely
a
team
effort,
so
just
an
update
on
the
release.
We
are
currently
in
code
freeze.
So
if
you've
opened
a
PR
in
the
last
day,
thank
you
for
your
patience
and
we
will
get
to
it,
but
we
need
to
get
the
the
shift.
D
The
shift
going
in
the
I
can't
see
it
but
I
in
the
in
the
in
the
docs.
Rather
in
the
agenda
doc,
I've
noted
two
slack
Channel
I'm
gonna
I'm
gonna
update
in
sigmox
slack
channel
to
to
announce
when
things
have
been
updated
when
things
are
happening
just
to
keep
the
community
here
informed,
but
we
can
also
follow
navaroon's
thread.
That
is
basically
at
this
point.
D
We
are
waiting
for
the
binary
to
get
built
and
if
it's
going
to
time,
it
should
be
done
in
probably
the
next
hour
or
so,
which
then
triggers
the
the
next
step,
which
is
doing
the
the
website
shift
and
then,
after
that,
we'll
do
the
blog
release.
D
So
that
is
all
up
upcoming
and
again
thanks
to
Ray
and
Jim,
for
helping
out
on
the
netlify
site
side
of
the
release,
while
I'm
I'm
traveling,
it's
been
a
real
de-stressor
having
having
you
to
stand
by
so
that's
I
think
I
think
that's
where
things
are
going,
the
the
just
to
be
official
by
the
the
James
lavrank,
the
sound
of
the
all-go,
probably
about
40
minutes
ago.
So
we
are
I
mean
we're
we're
in
the
throes
of
a
release.
It's
happening
so.
A
Awesome
thanks
Nate
thanks
for
the
update
and
definitely
great
Colette,
it's
a
huge
team
effort
to
get
releases
like
this
underway
and
I
do
want
to
call
out
specifically
also
the
the
thank
you
that
you've
got
out
here
for
the
release
docs
team
overall,
not
only
yourself
Chris
nigas,.
D
As
well
yep
that
it's,
the
team
has
been
nothing
short
of
a
spectacular
this
time
around,
so
nothing
but
happiness
on
my
side
here.
So.
A
Awesome,
that's
really
great
thanks
again
for
that
update.
That's
awesome
for
those
on
the
call
that
want
to
follow.
Along
with
how
the
release
is
going.
As
Nate
mentioned,
there
is
the
release
management
status
thread.
Specifically,
you
can
find
that
linked
in
the
agenda,
doc
and
you'll
be
able
to
keep
up
there
as
well
and
Nate
is
cross
posting
updates,
specifically
in
the
sigdox
channel
too.
A
If
you
want
to
keep
up
with
those,
so
thanks
so
much
Nate
and
thanks
so
much
team
alrighty
now
in
terms
of
the
next
updates,
on
top
of
on
the
current
status
on
top
of,
should
I
say
website
being
frozen,
can
you
let
us
know
Nate
we're
all
going
to
give
us
information
when
generally
in
sigdocs,
when
it
is
unfrozen
again
and
PRS
are
flowing?
Is
that
correct.
D
Age,
essentially,
my
plan
is
to
at
each
step
be
vocal
about
what
what
I'm
doing
so
once
the
once
the
binary
I
don't
know
if
that's
the
right
term
for
it,
but
once
the
binary
is
released,
I
will
mention
insect
docs.
That
I
am
starting
the
process
of
I,
suppose
merging
in
the
1.24
official
Branch
that'll
be
the
next
step.
D
Once
that's
in
I
will
again
say:
okay,
that's
in
and
then
the
next
step
from
there
is
merging
in
the
announcement
blog
that
Nikki
and
and
and
the
rest
of
the
comms
team
have
prepared,
and
then
once
that's
been
done,
I'll
again
mention
that
and
once
at
that
point
I
believe
James.
The
release
lead
will
do
a
media
blast
to
sort
of
officially
do
the
release
and
you'll
see
I
think
on
the
docs
or
the
dev
at
kubernetes
list.
D
You'll
see
you'll
see
a
announcement
there
and
at
that
point,
there's
a
couple
more
things
that
I
need
to
do
around
preparing
the
next
release
cycle,
opening
up
a
a
dev125
branch
and
so
on
that
have
to
happen
before
we
can
unfreeze,
but
I'm,
hoping
that
once
that,
once
that
initial
binary
gets
dropped,
if
everything
sort
of
goes,
if
the
stars
line
and
everything
goes
smoothly,
I'm
hoping
that
it
won't
be
more
than
about
two
hours,
it
might
be
a
little
bit
longer,
but
I'm
not
expecting
it
to
take
too
too
long
to
get
everything
merged
in
we've
tried
to
line
things
up
so
that
it
should
be
fairly
straightforward.
A
Awesome
thanks
so
much
Nate
and
and
specifically
to
your
to
your
point
on
making
sure
to
create
that
1.25
branch
and
the
other
update
too.
In
terms
of
that
release
cycle,
it
starts
and
then
on
the
23rd
of
May
and
we've
got
Kristen
Martin
who's
going
to
be
the
125
docs
lead
to
which
the
release
date
is
scheduled
for
the
23rd
of
August
I
believe
as
well.
D
And
Shadow
applications
are
open,
so
if
you're
interested
and
we
try
to
get
a
a
at
least
two
new
folks.
So
even
if
you're,
if
you're
not
very
familiar
with
the
process
and
whatnot
you're
you're,
still
welcome
to
apply
even
if
you're,
very
new
to
the
project.
E
E
So
just
want
to
add
a
few
things.
The
125
week
cycle
will
start
after
kubecon
EU
on
May
23rd
and
it's
scheduled
for
August
to
release
on
August
23rd
on
the
shadow
application
on
the
link
there.
There
there's
links
to
the
role
handbook.
So
if
you
want
to
look
at
other
roles
besides
stocks,
but
docs
is
a
great
way
to
get
and
more
involved.
E
That
was
my
Avenue
to
get
more
involved
with
Sig
docs
was
being
part
of
the
release
team,
so
so
I
do
suggest,
taking
like
the
role
at
the
roll
handbooks
and
to
and
to
fill
out
the
application
before
Friday
end
of
day
Pacific
time,
May
6.
A
Awesome
thanks
so
much
Ray
and
for
folks
who
have
questions
about
the
the
shadow
program
as
well.
You
can
reach
out
specifically
in
Sig
docs
or
in
the
release
in
the
release,
docs
specific
Channel
or
the
release
Channel
2,
any
questions
that
you've
got,
that
you
see
Ray
or
nade,
or
anyone
from
the
from
the
team
kind
of
popping
up
feel
free
to
ask,
and
they
can
definitely
provide
some
advice
and
help
you
out.
So
thanks.
A
A
Alrighty
with
that
being
said,
let's
go
into
the
next
parts
of
our
agenda
and
then
Maya
you
mentioned
that
you
you
had
the
you
had
a
specific
issue
with
PR
that
you
wanted
to
mention
here.
I
think
you
put
at
the
bottom
here
we're
happy
to
chat
about
this.
Now,
if
you
like,
and
we
can
go
into
discussion
after
if
you're
cool
with
that.
A
Let's,
let's,
let's
definitely,
let's
chat
about
your
issue
there
so
feel
free
to
give
us
a
little
bit
of
insight
and
context
into
what
you
wanted
to
bring
up
today.
C
B
No,
no
okay,
okay,
because
I
was
thinking,
maybe
because
it's
the
release
and
it's
not
the
the
best
time
to
talk
about
this
stuff,
but
all
right.
So
so
the
the
the
issue
in
question.
So
there
is
a
link
in
the
in
the
I
can
put
in
the
chart.
It's
just
a
an
issue,
a
team
opened
a
while
ago
about
the
second
tutorial,
and
actually
we
worked
a
little
bit
with
with
Folks
at
the
seek
security
dock
about
a
security
checklist
and
I.
B
I
I,
like
I,
use
a
tutorial
to
try
a
little
bit
about
second,
and
so
the
idea
of
team
in
this
issue
was
to
get
rid
of
the
docker
as
a
requisite
and
maybe
to
be
a
little
more
Broad
and
and
yeah.
So
what
I?
What
I
brought
to
the
table
is
that
when
I
tried,
the
tutorial
actually
I
used,
Mini
Cube
instead
of
kind
and
I
was
thinking
like
to
resolve.
This
issue
should
like
a
should.
We
try
to
make
it
like.
B
Should
I
try
just
to
adapt
the
tutorial
to
use
podman
instead
of
a
Doctor
by
default
by
using
kind
of
or
or
instead
even
go
broader
and
use
mini
Cube
to
to
make
it
more
easy
to
to
use
and
make
it
more
General?
So
that's
the
idea,
I'm
not
sure
I'm
really
clear,
but
if
you're
in
my
comments
it
might
be
more
secure
than
and
clear
but
yeah
the
idea
was,
do
you
know
this
tutorial
and
what
do
you
think
about
using
kind
of
mini
cube
in
this
kind
of
tutorial.
E
Indifference,
there
I'm
definitely
using
kind
of
mini
Cube
for
the
tutorials
long
as
it
stated
I'm
not
sure
if
using
I
would
rather
use
a
container
runtimes
that
are
CRI
compliance.
Now,
what
you
know
with
with
124
I'm,
not
sure
podman
is
so,
and
we
could
state
that
we
could
have
tutorials
for
using
containerd
or
cryo.
E
That's
how
how
I
kind
of
feel
of
on
the
approach
I
know-
and
the
issue
says
right
now:
it
requires
Docker
to
run
when
you're
unkind.
You
know
some
kind
of
some
kind
of
leaning
to
make
it
more
generic
in
terms
of
container
runtime
use.
I
know:
that's
takes
a
little
bit
more
more
of
an
effort
to
use
other
container
runtimes,
and
that's
just
my
opinion.
I
am
you
know.
B
A
B
A
Yeah
I
also
agree
with
Ray
in
the
sense
of
making
sure
we're
just
stating,
whichever
like
very
explicitly
at
the
tutorial
phase
itself,
that
whatever
the
preference
or
whatever
is
being
used
in
studying
that
very
clearly
I
think
that
would
be
that's
really.
Actually.
My
only
opinion
on
that
that
is
whatever
we
have
to.
We
decide
we're
just
being
very
clear
about
the
decision
and
making
that
very
clear
to
folks
reading
yeah.
A
Alrighty
Maya
thanks
so
much
for
bringing
that
up.
A
It's
it's
one
of
those
things
where,
if
you're,
if
you're
still
unsure
in
terms
of
looking
for
opinions-
or
you
want
to
hear
also
from
more
folks
from
the
community,
given
that
not
everyone
attends
meetings
too
feel
free
to
also
even
bring
it
up
in
the
cdocs
channel
too.
If
you
want
to
actually
ask
some
more
questions
around
it,
that's
also
totally
fine
as
well,
and
we
can
also
facilitate
discussion
that
way.
B
A
Yeah,
definitely
for
sure,
thank
you
so
much
for
bringing
this
up.
That's
great
and
participation
like
this
from
folks
who
are
new
to
our
meetings,
as
always,
Subaru
welcome,
so
thanks,
again,
alrighty
moving
on
then
to
some
of
our
additional
questions
and
discussion
points
talking
specifically
about
website
changes
in
terms
of
how
fast
they
come
about
causing
problems
for
localizations
teams,
and
is
there
any
way
that
we
can
overcome
this
specifically
with
1.24?
It
has
more
changes
than
our
relation
releases
thanks
to
specifically
to
the
dockershim
removal.
E
Yeah
elaborate
I'm,
not
sure
yeah
I'm,
not
sure
who
put
this
topic
down.
It's
always
an
ongoing
I
feel
like
it's
a
long.
It's
always
ongoing
issue
where,
where
we
have
website
changes
and
it's
causing
issues
for
localization
teams
and
I
know
we
added
the
refactor
label,
it's
very
subjective
on
what
is
considered
a
PR.
That
is
a
refactor
to
be
notified
and
I
feel
like
it.
E
We
feel
the
impact
more
or
localization
seems
to
feel
the
impact
more
in
this
release,
or
they
will
soon
once
once
the
124
Branch
merges
to
Maine,
because,
as
Nate
mentioned
earlier,
that
we,
this
release
has
a
lot
more
docs
changes
in
law
events.
You
know
with
the
doctrine
removal
so
once
in
the
integration
Branch
emerges
where
it's
going
to
be,
there's
going
to
be
a
lot
more
updates
for
localization
teams.
E
We
typically
have
localization
changes
done
after
a
release
not
done
in
Peril,
so
so
it
has
to
be
published
to
to
Maine
before
localization
can
make
the
appropriate
changes.
Now,
if
I
don't
have
I,
don't
have
the
writing.
I
don't
have
an
answer
to
that.
I
know
we
have
the
refactor
label
and
I
don't
know.
If
that's,
if
that's
enough
I
don't
know.
If
there's
any
other
mechanisms,
we
should
have
in
place
for
localization
teams
to
be
notified.
Could.
E
What's
it
all
it
does
it
just
adds
a
label
just
label
refactor
to
a
pull
request
and
people
could
and
folks
can
do
queries
search
queries
with
like
pull
requests
with
that
label
with
that
label.
Refactor,
noting
that
it's
a
big
change
or
that
pull
request
is
doing
a
big
change
to
the
docs,
so
I
and
and
I
don't
know
if
there's
a
way
to
automate
notifications
to
the
localization
teams
to
what,
if
there
is
a
pull
request
to
ask
merch
would
that
label
and
it's
very
subjective?
E
We
don't
have
a
set
of
set
of
rules
of
what
is
refactor
or
what's
consider
refactor
I've
applied
it
whenever
I
do
pr
wrangling
when
I
consider
pull
requests
to
make
enough
changes
to
be
considered
every
Factor.
F
Yeah
I
have
a
question
about
this
because
in
fact,
I
was
going
to
add
it
to
the
agenda
today
because
in
the
meet
and
greet
we
had
a
few
hours
ago
before
I
know,
some
of
you
were
even
awake.
F
The
the
we
talked
about
the
fact
that
you
know
like
that
they
can't
get
all
PR's
from
English
into
their
languages
they're
just
too
many
of
them.
When
I
was
one
is,
maybe
we
could
go
about
a
completely
different
way?
Maybe
they
could
maybe
once
a
month
once
a
quarter
once
a
release.
Just
do
a
massive
diff.
You
know
just
say
here:
do
a
diff
of
the
last.
F
You
know
checkpoint
to
the
current
moment
and
then
hand
that
to
the
localization
teams,
because
something
like
that
I
mean
I
was
looking
at
some
of
the
PRS
we
had.
We
have
like
four
or
five
PR's
against
the
same
page.
Wouldn't
it
be
better
just
to
see
the
diff
of
what
the
page
was
to
what
the
page
is
and
let
them
look
at
that
be
a
lot
easier
to
scan
than
to
go
stepping
through
all
those
PRS.
E
We
have
something
like
that:
we
have.
We
have
a
script
that
does
that
the
localization
teams
should.
G
Yeah
so
I
think
the
problem.
The
issue
is
still
volume
right,
so
we
can
find
the
changes
either
with
the
refactory
label
or
with
with
the
script
that
Ray
was
mentioning
I
think
it's
actually
mentioned
in
the
localization
contributing
Pages
that
I
just
put
in
the
chat.
If
you
want
to
find
more
information
about
that,
but
the
the
issue
is
still
just
volume
right.
So
it's
it's.
There's
these
a
lot
of
changes
that
the
localization
teams,
maybe
they'd,
only
have
a
few
folks
who
are
able
to
help
out
and
they're.
G
You
know
not
full-time
and
translating
is
not
just
you
know
very
it's
not
necessarily
always
quick,
because
it
you
need
to
think
about
things
in
a
different
language
and
put
things
in
the
in
the
right
place.
G
So
it's
definitely
an
issue
that
we
that
is
ongoing,
and
we
we
talk
about
this
and
trying
to
create
some
standardizations
in
our
localization
subgroup,
which
we're
hoping
to
make
a
sub
project
in
the
future
in
the
near
future,
and
we
we
meet
months
once
a
month
and
we
actually
have
a
localization
a
sigdox
vocalization
channel.
So
if
this
is
a
topic
that
you're
interested
in
talking
about
more,
you
have
ideas,
we'd
love
to
hear
about
it.
G
There
I'm
one
of
the
co-leads
of
that
group
with
Brad
DePaul,
who
has
also
been
very
involved
over
the
past
year.
So
this
is
something
we
have
a
lot
of
room
to
grow
and
make
better
and
improve
for
folks,
and
we
don't
really
have
a
good
solution
at
the
moment.
There
are
some
some
ideas
out
there
and
different
localization
teams
are
a
little
further
along
in
their
Journey
on
how
to
handle
this
than
others,
which
is
one
of
the
reasons
why
we
started
a
localization
subgroup.
G
So
we
can
start
sharing
the
knowledge
and
creating
these
standardizations.
So
our
answer
is:
if
we
know
it's
an
issue,
we're
working
on
fixing
it,
but
we
don't
have
anything
concrete
right
now.
Yeah.
F
I'd
be
glad
to
be
involved
because
I
was
thinking,
you
know
you
have
a
massive
diff
and
then
you
have.
We
know
the
top
most
visited
pages
right.
So
let's
say
we
want
to
make
sure
that
the
most
visited
Pages
the
changes
to
those
most
visited
Pages,
maybe
could
be
the
the
things
that
we
hand
off.
You
know,
as
opposed
to
saying
you
know:
10
000
pages
top
100
Pages,
something
like
that
now,
but
yeah
I'd
be
glad
to
get
involved.
So
you
have
a
meeting
on
the
calendar.
A
Correct
it's
on
the
yeah,
it's
part
of
the
the
Sig
docs
or
the
calendar.
It
happens
monthly
as
well
on
a
Monday,
specifically
I.
Think
we
actually
just
had
a
meeting
yesterday
I
believe
so
the
next
one
will
come
in
the
next
month,
but
you
can
go
to
the
Sig
docs
localizations
slack,
the
channel
itself
as
well,
and
that's
where
a
lot
of
the
groups
co-locate
there,
but
before
I
keep
going
Nate.
You've
got
your
hand
up.
D
D
Projects
can
submit
ideas
to
if
there's,
if
there's
a
potential
Mentor
and
and
they
have
an
idea
for
something
that
needs
to
be
done,
we
can
we
can
potentially
provide
a
paid
mentorship
and
I've
been
really
hoping
to
try
and
drive
more
non-code
contributions.
D
I'd
be
very,
very
interested
in
seeing
a
lot
more
writers
and
and
designers
and
and
translators
coming
into
that
program.
So
I
just
want
to
sort
of
highlight
that
and
and
I'm
happy
to
be
available
to
to
to
help
either
coach
folks
through.
If
you
think
that
this
might
be
an
opportunity
for
people
to
do
some
of
that
type
of
work
for
pay,
I
I'd
be
happy
to
sort
of
talk
about
that.
D
So
I
just
want
to
sort
of
bring
up
the
LFX
mentorship
program
as
an
as
a
potential
opportunity.
Now
the
the
timing
isn't
great
for
cute
guys,
because
I
think
I
can't
remember
the
the
idea
submission
due
date.
Right
off
the
top
of
my
head,
but
I
couldn't
find
that
out
and
share
it
in
Sig
docs,
but
I
I'd
be
very
excited
to
see.
If
we
can't
get
some
localization
projects
that
folks
have
time
to
to
Mentor
or
if
that's
maybe
a
space
for
us.
A
D
Sure
why
don't
we?
Why
don't
we?
Why
don't
we
take
that
offline?
We
can
have
a
discussion.
That's
today
is
a
touch
busy
for
me,
so,
but
maybe
maybe
next
week
it
would
be
something
we
could.
We
could
put
something
together
or
let's
talk
sooner
than
that,
because
I
don't
know
what
the
deadline
is,
but
we
could
we
can
get
this
moving
fairly
fairly
soon.
A
Awesome
thanks
folks
for
that
discussion.
Also
thanks
for
your
availability
for
this
week,
even
as
well,
given
that
you're
a
busy
so
super
appreciate
that
too
thanks
I
think
that's
a
great
idea.
Utilizing
the
LFX
mentorship
super
super
awesome
idea.
So
thanks
thanks
for
that.
A
E
I
put
the
links
to
the
two
scripts
in
the
agenda
and
a
copy
of
the
of
the
contents
about
those
two
Scripts.
A
Perfect
thanks
so
much
Ray
and
with
that
I'm
actually
going
to
hand
over
the
the
mic
to
you
since
I
believe.
You've
got
the
next
agenda
item
here
with
the
new
contributors
meet
and
greet.
E
Yeah
I
noticed
well
Arch
hosted
the
the
First
new
contributors
main
groups,
that
was
this
week.
It's
on
the
first
Tuesday
of
the
month,
so
4
pm,
IST
12,
30
Central
very
early
in
the
morning
for
Pacific
3
30
a.m,
6
30
a.m,
Eastern
so
I'm,
actually
thinking
about
hosting
one
myself
just
so
that
I
I
I,
know
I'd
love
to
I,
Love
The,
I
love
the
Geo
diversity
of
new
contributors,
but
I'm.
E
Also
thinking
just
having
folks,
you
know
having
a
a
a
another
time,
like
probably
like
a
two
weeks
mid
like
the
second
week
or
a
second
Tuesday
of
the
month,
so
we
could
offset
a
little
bit
or
maybe
probably
not
second
Tuesday.
So
it
might
be
the
same
time
at
just
because
we
have
our
sick
docs
meetings,
but
at
another
time,
maybe
on
a
Thursday
or
Friday
just
to
just
to
add
another
available
time
and
I
would
host
that.
E
My
I
would
like
to
host
that
myself
so
send
it
I'll
put
this
in
slack
Channel,
also
to
now
that
when
they're
mainly
list
as
well
just
to
get
people's
thoughts
about
it,
foreign.
A
Ers
meet
and
greet
I
think
that's
really
great
love.
That
idea,
and
perhaps
what
we
could
do
is
maybe
find
out
from
from
Ash
in
this
big
dog
Channel
How,
the
Other
meeting
that
I
went
maybe
passing
on
some
interesting
tidbits
for
you
ready
for
a
possible
second
meeting
option
there.
That's
great.
A
Great
awesome
thanks
so
much
thanks,
so
much
Nate,
you
take
care
good
luck
today
and
since
we
will
be
seeing
Nate
along
in
the
sick,
dog
Channel
and
the
release,
Dog
Channel,
please
feel
free
to
follow
along
Along
on
his
on
his
release
day.
A
Journey
our
release
date
journey
I
should
say,
but
we
do
have
one
more
topic
and
it
actually
is
interestingly
mine,
slash
Abby's
for
today,
and
that
is
specifically
we
are
thinking
about,
or
thinking
very
purposely
and
has
sort
of
planning
to
do
a
doc
Sprint
at
kubecon
EU.
A
Given
there's
going
to
be
a
couple
of
us
there,
but
we
just
wanted
to
ask
here
on
the
meeting
and
as
well
we'll
be
asking
again
in
the
sync
docs
Channel
who's
going
to
be
around
possibly
at
kubeconi
to
facilitate
a
doc
Sprint,
because
we
actually
don't
know
if
we've
got
the
numbers
to
get
folks
on
board.
So
I
just
want
to
see
specifically
I
know:
people
are
arriving
at
different
times.
A
We
are
planning
the
doc
Sprint
for
the
Monday
16th
of
May
it'll
be
taking
place
between
2
p.m
and
5
p.m.
On
the
actual
day
of
that
contributor
Summit,
so
we're
focusing
on
the
afternoon
to
give
folks
possibility
of
arriving.
But
anyone
on
the
call
going
to
be
there
other
than
myself.
A
All
right,
looking
like
no,
which
is
fine,
what
we're
going
to
do,
is
possibly
actually
ask
those
that
same
question
and
try
and
actually
survey
the
sigdox
community.
Part
of
the
reason
I
want
to
double
check
if
there's
a
specifically
yeah
I
know
that
Ray
I'm
so
sorry,
but
part
of
the
reason
that
we
want
to
double
check
that
there's
actually
a
appetite
for
this
in
this
room.
A
We
don't
want
to
take
up
space
that
could
be
possibly
used
by
another
group
and
and
specifically
block
out
a
space
for
us
if
we're
not
going
to
use
so
I'm
just
trying
to
get
ahead
of
possibly
making
a
decision
in
one
way
or
another.
We've
got
a
bit
of
time
still
to
decide
on
that,
but
it's
just
still
figuring
out
what
we
can
do
logistics-wise
there
in
terms
of
topics
of
what
we're
thinking
about
looking
at
in
the
doc
Sprint.
Actually
Abby.
A
Do
you
mind
going
over
a
couple
of
suggestions?
There.
G
Yeah
sure
so,
I
kind
of
threw
together
a
doc
which
is
I,
will
put
in
the
chat
and
then
I
could
probably
also
add
it
into
the.
Hopefully.
Everyone
can
see.
I
can
add
it
into
the
agenda
later,
but
it
is
just
a
quick
rundown
of
the
things
people
have
mentioned
as
possible
topic
ideas.
G
Some
of
these
things
require
you
know,
obviously
more
legwork
to
set
up
for
having
the
event
and
then
what
also
kind
of
require
people
at
the
event
to
have
a
little
bit
more
knowledge
of
of
things.
Some
of
them
are
not
very
deep.
Tech
topics
is
that
the
word
I'm
looking
for
anyway
yeah.
So
this
is
the
the
doc
that
I
had
of
the
topic.
G
So
if
anyone
has
a
really
strong
feeling
about
wanting
to
work
on
these
topics,
like
you
know,
let
me
know
or
or
write
out
in
the
docker,
we
can
add
in
the
comment
of
the
agenda.
Section
I
think
it'd
be
really
cool
that
we've
just
thinking
about
the
new
contributor
meetings
that
just
got
kicked
off
today
with
Arch.
That
might
be
just
something
to
kind
of
run.
One
located
at
the
contributor
subit
to
do
sort
of
an
in-person
event
like
that
of
new
contributor
questions.
New
contributor
welcomes
in
that
sense
again.
G
We'd
have
to
make
sure
we
have
the
people
to
there
to
help
to
help
facilitate
that.
So.
A
For
sure
I
do
want
to
State,
though,
that
this
is
definitely
something
that
we
are
kind
of,
first-time
organizers
of
in
terms
of
myself
and
Abby.
So
we
are
just
trying
to
put
together
things
as
as
best
as
we
can,
but
at
the
same
time
we
were
trying
to
figure
out
if
we
could
facilitate
a
possible
virtual
option
and
it
wasn't
possible
at
this
at
this
specific
event.
A
At
this
time,
however,
kubecon
North
America
will
present
us
another
opportunity
to
get
together
in
person
for
folks
that
are
possibly
going
there
to
do
another
one
of
these
Sprints.
So
we
definitely
have
a
lot
more
opportunities
to
organize
virtual
possibilities
for
this
Sprint
as
well
as
another
in-person
one.
A
So
it's
not
so
bad
if
we
don't
get
something
off
the
ground
for
this
event
in
the
coming
two
weeks,
so
trying
to
always
look
at
a
silver
lining
here
in
terms
of
what
we're
organizing
but
yeah
for
folks,
they
take
a
look
at
the
the
doc
that
Abby
shared
a
couple
of
different
options
there.
Our
last
effort,
in
terms
of
our
last
resort,
should
I
say
in
terms
of
making
sure
that
we
can
potentially
use
the
space.
A
It's
just
have
a
space
to
stick
docks
Folks
at
the
contributor
Summit
to
meet
one.
Another
can
also
just
be
a
fun
meet
and
greet
kind
of
area
in
the
last
part
of
the
afternoon.
We're
super
happy
to
keep
the
space
still
for
that
kind
of
event
as
well,
given
that
folks
are
arriving
at
different
times.
So
if
it
turns
out,
we've
got
folks
interested
in
in
seeing
one
another,
but
perhaps
not
interested
in
working
on
something
in
the
flesh.
A
G
I
did
I
just
wanted
to
Echo
that
that's
a
really
great
point
that
people
can
just
we
don't
necessarily
have
to
be
doing
work.
Always
we
can
just
meet
and
hang
out
because
you
know
just
that
is
perfectly
valid
way
to
do
it,
and-
and
these
topics
can
also
be
used
going
forward,
because
our
goal
is
to
hope,
hopefully
host
these
events
more
as
we
have
more
events
happening
in
the
world
super.
E
I
also
just
want
to
note
that
there
will
be
act,
completes
or
overall,
six
meet
and
greets
if
you
want
to
meet
anyone
from
any
Sig.
It's
from
1
to
2
P.M
on
Friday
of
that
coupon
week,
and
it's
at
the
Joaquin
Rodrigo
room
I
put
in
the
notes
there.
A
Great
thanks
very
much
Ray.
There
is
going
to
be
a
lot
more
information
about
these
events
as
they're
becoming
finalized
and
posted
to
the
overall
General
agenda.
That's
happening
there.
Ray
I
believe
that's
something
that
is
a
contribex
is
organizing
that
or
the
summit
staff.
Sorry.
E
E
Is
organizing
this
so.
A
Great
alrighty
thanks
so
much
and
with
that
we've
actually
come
to
the
end
of
our
agenda
with
two
ish
minutes
to
go
just
want
to
double
check
before
we
close
out
for
today.
Any
other
extra
kind
of
topics
that
folks
wanted
to
bring
up
or
any
points
that
we've
missed,
that
you
wanted
to
chat
about
today.
A
Alrighty
so,
firstly,
thank
you
so
much
to
our
newbies
for
for
joining
the
call
and
saying
hello,
we
really
look
forward
to
your
contributions
and
your
collaboration
in
future.
A
It's
really
great
to
have
you,
and
also
thanks
to
our
usual
regular
folks,
who
are
coming
to
the
meetings
every
week,
really
great
Community
here
and
there,
and
hopefully
we
can
make
sure
that
we're
keeping
that
Spirit
Alive
at
the
different
events
that
are
coming
up
this
year
too,
which
is
exciting
to
hear
that
events
are
somewhat
back
on
the
agenda,
so
to
speak,
for
for
a
lot
of
folks
as
a
possibility
there.
A
So
thanks
again
everyone
big
sign
off
and
and
thank
you
from
sigdocs,
and
we
will
chat
on
slack
in
the
next
couple
weeks,
given
that
it's
kubecon
we'll
be
having
our
next
meeting,
specifically
in
slack
there
for
different
foods.
So
thanks
again
and
have
a
great
rest
of
your
week,.