►
From YouTube: K8s SIG Docs Meeting for 20230110
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
Alrighty
hi
everybody
Welcome,
firstly,
Happy
2023
and
the
first
general
Sig
docs
meeting
of
the
year.
For
those
who
don't
know
me:
I'm
Natalie
I'm,
one
of
the
co-chairs
and
we've
got
a
host
of
new
and
seasoned
faces
here
on
the
meeting
for
for
today.
A
Firstly,
thanks
everyone
for
joining
I'm,
going
to
post
again
the
agenda
just
in
the
chat
there
for
you
to
access.
But
the
first
thing
you
want
to
say
is
a
big
welcome.
I
hope
you
had
a
great
time
over
the
holiday
break,
regardless
of
what
you
were
celebrating
or
doing,
and
some
time
to
recharge
and
re-energize
into
2023.
We're
ready
in
sync
docs
to
get
a
lot
of
a
lot
of
work
done.
A
You've
probably
seen
some
really
great
work
out
of
Divya,
with
a
lot
of
cleanup
going
on
in
terms
of
reviewers
and
approvers
and
so
on,
which
is
really
great
energy
that
I'm
trying
to
myself
channel,
which
has
been,
which
has
really
been
great,
to
see
that
coming
out
from
Divya
our
other
co-chair,
who
it's
very
late
to
join
these
meetings.
So
she
often
hosts
out
APAC
meetings
for
folks
who
want
to
join
those
calls
that
are
on
monthly
first
things.
A
First,
what
I
want
to
do
is
with
the
agenda
that
we've
got
here.
I'll
go
through
a
couple
of
the
areas
of
our
agenda.
A
First
thing
to
do
is
to
mention
that
this
is
a
a
cncf
meeting,
and
that
means
that
we
do
abide
by
the
cncf
code
of
conduct,
meaning
that
we
just
want
to
make
sure
that
everyone
is
kind
respectful
to
one
another,
and
that
includes
not
only
in
this
meeting,
but
also
in
the
slack
in
our
channels
and
via
messages,
but
also
on
issues
and
PR's,
and
so
on
and
I
love
to
remind
everyone
here
in
the
in
the
in
the
meetings
too,
and
we
also
have
that
note
in
our
agenda
as
well
that
if
you
have
any
issues
that
a
code
of
conduct
related
you'll
see
in
the
agenda
a
place
where
you
can
actually
reach
out
to
some
folks
chat
about
the
specific
issue
and
hopefully
get
those
things
addressed.
A
Alrighty
with
that
with
that
out,
the
way
what
I'd
love
to
do
is
see.
If
we
can
welcome
some
new
contributors
here
or
some
new
participants
to
see
docs,
if
you're
new,
either
to
the
community
to
the
meeting-
and
you
want
to
say
hello-
please
feel
free
to
unmute
or
pop
your
pop,
a
hello
in
the
chat.
Now.
B
Hi,
my
name
is
Patrice
I'm
part
of
the
cncf
tech
docs
team
I
was
responsible
for
the
cmcf
Google
analytics
for
migration
and
that's
my
involvement
in
terms
of
kubernetes
Docs,
so
hi
everybody.
A
Hi
Patrice
thanks
so
much
great
to
great
to
have
you
here,
I'll,
be
adding
your
name
to
the
gender
as
a
bit
of
a
hello
but
yeah
great
great
intro.
Thanks
for
introducing
yourself,
we
look
forward
to
seeing
more
of
you
anyone
else
who
wants
to
say
hello,
who's
new
here
to
seek
Docs.
C
Yeah
hello:
this
is
Rajesh,
so
this
is
my
second
meeting
after
last
year,
maybe
in
the
end
of
November,
so
I
attended
the
first
meeting
and
I'm
here
to
learn
I'm
a
new
contributor
here,
so
I'm
also
joining
the
contrabass
meetings
as
well,
so
trying
to
understand,
learn
and
also
contribute
for
the
syntop
community,
so
I'm,
quite
new,
so
I'm
just
understanding
trying
to
digest
and
maybe
start
contributing
their
list
in
the
upcoming
weeks
or
days
yeah.
So
that's.
C
A
Awesome
welcome
thanks
so
much
for
saying,
hi
yeah
your
time
to
contribute
can
be
as
slow
or
as
fast
as
you
need
it
to
be,
or
is
that
you
want
it
to
be?
There's
no
time
limit
here
and
there's
a
lot
of
really
great
resources
that
you
can
access
in
the
sick,
docs
channel
to
help
you
with
that
contribution,
Journey,
so
yeah
definitely
feel
free
to
in
the
in
the
channel
or
here
in
the
meeting,
ask
whatever
questions
that
you
have
absolutely.
D
I'm
not
new,
but
I
do
want
to
say
hi
I'm
Ray
when
they're
co-chairs
come
back.
I
had
some
illnesses
since
mid-november,
so
and
plus
with
holiday
time,
but
I
just
want
to
say
I'm
back
I'm,
slowly
catching
up
with
slack.
So
if
you
sent
me
a
message
or
expecting
something
for
me,
I
I
apologize
for
my
slow
reply
and
I'll
get
to
all
my
messages.
A
Yeah
welcome
back
Ray,
really
great
great
to
let
your
full
of
Health
again,
that's
really
awesome
and
that
you
also
got
to
say
hopefully
takes
still
some
time
off
with
your
family
enjoy
some
downtime
when
you
weren't
sick
as
well.
Hopefully.
A
Alrighty
for
anyone
else
who
wants
to
say
hi
feel
free
to
show
in
the
chat
vital
I
just
saw
you
saw
in
the
chat.
You
said:
Happy,
New,
Year,
Happy,
New
Year
to
you
too,
and
feel
free
to
also
add
in
your
names.
If
you
wish
to
also
on
the
agenda
in
terms
of
being
a
new
contributor,
that's
also,
okay,
you
can
communicate
in
any
way
you
want
with
us.
A
Whatever
way
is
comfortable
for
you
alrighty,
so
the
way
we
usually
run,
these
meetings
is
that
we
go
through
a
few
things
in
terms
of
some
of
the
general
kind
of
ways
that
we
work
here
in
zigdocs,
and
one
of
the
big
ways
that
we
work
in
terms
of
pushing
contributions
through
is
through
a
program
that
we
call
PR
angling.
A
This
is
something
where,
each
week,
one
of
our
reviewers
one
of
our
approvers
in
Sig
docs,
is
the
person
in
charge
of
kind
of
getting
our
contributions
through
the
many
PRS
that
we
often
have
in
the
in
the
in
the
repo
and
interestingly
enough
I.
Am
this
week's
PR
WR
Wrangler?
A
It's
me,
so
you
may
see
me
popping
up
in
different
PRS
here
or
there
I'm
going
to
be
with
the
New
Year
I'm,
taking
a
renewed
approach
in
actually
working
back
through
some
of
our
very,
very
old
old
PRS
that
are
still
open,
especially
with
some
of
the
localization
teams
to
see
if
we
can
get
a
couple
folks
who
may
not
need
to
be
on
a
specific
localization
team,
at
least
kind
of
pushing
some
suggestions,
changes
or
lgtms
those
kinds
of
things
and
tagging
the
appropriate
fix.
A
So
that's
what
I'm
I'm
choosing
to
do
with
my
week
this
week
to
try
and
get
through
a
bit
of
the
old
backlog
there
in
terms
of
the
XPR
Wrangler
that
will
be
Divya
and
she'll
be
on
for
next
week
and
for
all
approvals
that
are
on
the
call.
If
you
can,
please
remember
to
keep
your
eye
on
the
pr
Wrangler
shifts.
There
is
a
new
2023
calendar
that
was
created
thanks
to
Abby
who's,
on
the
call
who
put
that
calendar
together.
A
So
thanks
so
much
Abby
for
putting
that
on
Nate
you've
got
your
help.
Will.
A
Great
question
actually
I
think
I
actually
think
it
was
just
a
mission
of
an
extra
column
as
opposed
to
a
decision
of
not
continuing
or
anything
and
Abby
I
have
a
feeling
you're
nodding
there.
So.
F
A
Out
I
think
what
we
can
do,
Abby
once
you've
updated
that
column.
Maybe
we
can
actually
make
a
call
out
in
the
Sig
docs
Channel
itself
that
it's
2023,
please
put
your
hand
up.
If
you
want
to
Shadow
on
a
certain
week,
and
then
we
can
kind
of
make
sure
that
we
can
get
focuses
names
on
there
again.
A
note
for
approvers
that
page
is
should
be
editable
by
a
certain
a
certain
approvers.
A
So
we
can
add
in
those
folks,
in
that
extra
column,
on
who's,
shadowing
and
we'd
need
your
the
person's
GitHub
handle
in
terms
to
add
there,
so
that
we
know
who's
shadowing
as
well
great
alrighty
with
that
going
on.
Let's
move
on
to
the
next
part
of
our
agenda
for
new
folks,
the
next
part
is
usually
when
we
talk
about
the
current
release
and,
interestingly
it's
the
new
year.
We
are
only
one
day
into
the
current
release,
which
is
1.27.
A
Sigdox
does
a
lot
in
terms
of
helping
to
ship
it
in
the
docs
area
of
the
release
cycle.
There
is
a
docs
lead
that
we
work
very
closely
with
to
try
and
Shepard
through
changes
that
are
required.
A
A
lot
of
new
caps,
which
is
kubernetes
enhancement,
proposals
need
to
come
with
docs
new
changes
and
features,
and
so
we
try
and
help
put
in
putting
in
reviews
and
working
with
the
docs
lead
to
Shepherd
those
changes
and
additions
through
and
it's
only
day,
two
of
the
release,
so
actually
there's
not
much
to
do,
but
what
I
wanted
to
do
is
just
go
through
some
of
the
important
dates
that
Xander,
the
current
release
lead
for
one
two,
seven
sent
through
to
the
kubernetes
dev
mailing
list
recently,
and
so
those
are
obviously
the
release
cycle
begun
yesterday
on
the
9th
of
January.
A
The
enhancements
freeze
will
come
up
on
Thursday
February,
the
9th
and
Mark
Rossetti,
who
is
our
enhancements,
lead
and
as
part
of
C
Windows
has
actually
already
sent
an
email
out
calling
for
enhancements
for
the
1.27
cycle,
so
check
your
check
check
the
mailing
list
there,
the
Google
group
for
that
information.
A
The
next
really
important
deadline
is
the
code
freeze,
which
is
Tuesday,
March,
14th
and
then
release
day.
Is
Tuesday
April
11th
now
you'll
probably
see
that
there's
a
couple
there
for
folks
who
are
seasoned
on
the
release
side,
you
might
see
that
there's
a
couple
of
dates
missing
in
terms
of
docs
deadlines
and
so
on.
A
I,
don't
believe,
they've
actually
been
hashed
out
yet,
but
as
soon
as
we
get
those
deadlines
in
we'll
be
adding
them
to
the
agenda
so
that
we
can
keep
up
to
date
with
those
dates
for
ourselves
and
our
community
here.
But
these
are
the
dates
that
we
have
so
far.
That
seem
to
be
somewhat
official.
Of
course,
things
can
always
slightly
change,
as
we
saw
with
even
last
release
as
well,
depending
on
other
things,
but
at
the
moment
that's
what
we're
kind
of
tracking
with
in
terms
of
dates.
A
E
Just
a
note,
I
believe
Mickey
voxel
is
our
docs
lead
this
round.
A
Yes,
yes,
great
I
should
I
I'll
off
to
the
meeting
or
if
someone
wants
to
do
so
in
the
agenda
now,
I
can
add
in
the
the
different
the
couple
of
folks
in
terms
of
leads
that
we
should
keep
keep
an
eye
on
there
and
and
how
to
say
clue
into
our
meetings
when
they're
taking
place.
A
So
we
can
get
those
updates
from
the
docs
lead
too
thanks
for
that
name,
all
righty,
and
so
it's
very,
very
short
agenda
item
there
for
the
release,
given
that
it's
just
started,
but
there'll
be
a
lot
more
to
talk
about
in
the
in
the
coming
weeks.
As
as
the
release
progresses,
okay,
I'm,
going
to
now
move
over
to
the
issues
and
PR
section
of
our
agenda
area
and,
as
I
mentioned,
Divya
doing
some
great
work.
A
As
you
can
see,
she's
she's,
putting
a
few
agenda
items
that
we're
going
to
just
talk
about
now,
very
very
quickly
and
the
first
being
in
terms
of
coming
from
us
as
the
docs
leads.
We
insec
docs
need
the
community's
help
with
catacota
tutorials
they're
going
to
be
shutting
down
soon,
and
we
need
to
agree
upon
the
dates
with
O'reilly
and
then
there's
a
bunch
of
work
to
be
done
on
the
docsides
of
things.
A
There's
a
GitHub
issue
already
up,
so
that
we
can
discuss
the
feasibility
of
an
announcement,
blog
and
possible
replacement
options,
but
I
wanted
to
kind
of
see
a
specifically
I
know.
Tim
you've
also
been
involved
specifically
with
O'reilly
on
this
on
this
topic.
If
you
wanted
to
add
anything
here,.
G
I
guess
I'm
the
person
who
replied
to
them
first,
and
so
Jesse
at
O'reilly,
has
has
said
hello
Tim
on
all
the
replies.
It
certainly
doesn't
have
to
be
me
that
does
all
the
remaining
work
I
would
love
if
it
wasn't
yeah.
That's
what
I
want
to
say.
Natalie.
A
Great
no
problem,
two
I
think
it
sounds
like
the
next
to-do's
that
we
have
is
that
we
have
to
agree
on
a
date
that
it
basically
goes
away.
Is
that
do
I?
Have
that
understanding,
correct.
G
I
think
the
first
thing
to
do
is
to
is
to
start
putting
the
Frameworks
in
place
for
the
comms,
and
then
you
know
swiftly
on
the
heels
of
starting
that
work.
We
could
also
look
at
agreeing
a
date,
but
we
have
to
I
think
we
have
to
start
telling
our
our
readers
people
visiting
our
website
that
this
thing
is
going
because
it
will
be
a
shock.
It.
C
G
Me
that
it
was
going
to
get
turned
off
quite
so
soon.
A
For
sure,
and
so
with
that
I
I,
similarly
to
how
I'm
just
thinking
of
other
things,
that
our
community
was
quite
shocked
about
in
terms
of
learning
that
is
going
away
and
dockersham
is
obviously
just
kind
of
scarred
upon
my
brain.
A
D
I
think
there's
a
few
I
think
we
should
I,
don't
know
if
there's
another
main
list
we
have,
because
since
this
will
affect
a
lot
of
the
folks
who
are
new
to
kubernetes
or
users
of
kubernetes
well,
we
certainly
can't
I
think
we
should.
D
We
should
send
it
to
to
kdev
where
the
audience
the
more
of
the
folks
who
contribute
to
kubernetes
and
work
on
kubernetes,
but
I'll
take
a
look
to
see
if
there's
any
other
mailing
list
that
we
have
that
we
could
send
this
out
to
I
believe
the
wider
communication
is
better
than
more
narrow,
so
I'll
take
a
look
at
that.
A
A
Sorry,
I'm
I'm
one
on
a
train
today,
so
I'm
going
back
and
forth
between
the
agenda
and
doing
notes
here.
Great
I,
agree,
yeah,
Cube
weekly
is
a
great
idea
and
and
Nate
would
you
know
the
right
contact
specifically
for
cube
weekly
that
we
could
already
get
in
touch
with.
E
A
Awesome
and
then
my
suggestion
would
be
in
terms
of
like
there's
a
lot
of
communication
that
needs
to
go
out.
So
what
we
probably
want
to
do
is
share
the
load
in
terms
of
a
couple
of
different
people
owning
the
communications
going
out
in
different
places.
So
one
person
does
the
blog
one
person.
A
Does
the
mailing
lists
Etc
that
kind
of
thing
just
to
share
out
that
load,
but
all
of
us
collaborating
on
the
actual
messaging
so
that
we
can
kind
of
reuse
and
re-paste
as
needed
and
and
have
the
kind
of
same
message
going
forward.
That's
the
my
general
kind
of
thinking
there
Tim.
G
So
we're
making
an
assumption
here
and
I
just
want
to
make
that
clear
to
people
I
think
this
option
we're
making
is
that
converting
to
another
system
is
not
going
to
be
possible
in
the
time
we've
got
before.
O'reilly
want
to
turn
it
off.
E
G
E
E
I
thought
we
had
like
not
a
back
door
exactly,
but
a
way
to
continue
using
it
is
that
what
is
getting
turned
off
now.
G
What
we
didn't
know
until
much
more
recently
it
was
was
that
actually
that
that,
except
is
it
wasn't
going
to
be
maintained,
it
was
so
I
think
we
knew
it
was
best
asked
that
I
knew
so
for
a
while
we
had
gosh.
This
is
really
important,
catacote
again
and
getting
shut
down
and
we're
like
right.
Okay,
you
know
we
hadn't
had
an
announcement
about
this.
G
We
need
to
deal
with
this,
and
then
we
heard
from
Ben
Hall,
who
has
now
left
O'reilly
Ben
Paul
was
a
a
key
person
in
setting
up
Kat,
Dakota
and
Ben
Hall
said,
hang
on
no
way.
I've
I
have
secured
I'm
paraphrasing
here,
but
I
have
secured
a
stay
of
execution
just
for
the
kubernetes
website.
It'll
stay
on
yeah.
E
G
Learned
more
recently,
I
think
December
was
that
it'll
stay
on
has
turned
into
actually
no,
it
won't
and
we
we
need
to
be
offered
as
well.
To
me
this
was
not
a
massive
surprise,
but
the
timing
was
awkward
right.
E
Did
we
do
we
have
do
we
have
the
the
conversations
ready
to
hand
about
some
of
the,
because
I
remember
having
conversations
about
Alternatives
already?
Is
that
still
likely
to
be
relevant
for
us.
G
G
E
E
Removal
stuff,
which
is
to
say
that
we
should
probably
build
a
team
to
try
and
manage
this
as
it's
as
it's
yeah
right
and
the
last
the
for
for
the
docker
film
removal
stuff.
We
had
myself
and
Celestine
several
folks
from
across
the
there
was
a
big
Community
effort.
It
wasn't
just
this
last
night
by
any
especially
the
imagination
so
but
I
feel
like.
We
may
need
to
spearheaded
the
same
sort
of
way.
C
Yeah,
so
actually,
since
I'm,
a
new
person
here,
I'm
not
able
to
follow
the
discussions
quite
honestly
so
but
I
can
I
wanted
to
learn
and
understand,
like
how
I
can
help
here,
maybe
I'm,
also
going
through
the
documentation
updates.
So
I
would
like
to
you
know,
help
me
contribute
anywhere
in
the
discussion.
So
just
wanted
to
understand.
G
G
So
so
you
know
for
the
people
watching
on
YouTube
in
five
years
time
wondering
where
it
all
went
and
what
we
were
talking
about.
G
We
we
have
right
now
we
have,
we
use
a
thing
called
catacoda,
which
started
out
as
a
public
website
for
really
I
think
it
started
out
as
a
public
website
for
learning
kubernetes
in
particular,
and
became
more
that's
my
understanding,
so
we
use
categodata
and
we
have
tutorials
where
the
web
page
talks
you
through
trying
a
thing
such
as
learning
about
Ingress
or
learning
about
minicube
and
on
some
of
our
web
pages
you
get
a
button.
G
G
There
is
bad
weather
here
and
we
rely
on
that.
I
say
we
rely
on
it.
If
if
category
goes
off
and
we
don't
do
anything,
we
will
get
a
the
issues,
account
will
go
up
quickly.
People
will
file
issues
and
whatever
and
at
a
minimum.
We
need
to
communicate
that
because
these
tutorials
are
popular.
These
web
pages,
where
people
learn
kubernetes,
are
popular
yeah,
and
these
are
some
of
the
first
things
that
people
come
to
when
they
arrive
at
our
site
and
go
well.
A
Right
and
and
what
we're
discussing
now
is
because
those
tutorials
are
going
offline
for
good
and
great
call
out
there
Nate
in
terms
of
how
this
felt
Deja
Vu,
because
it's
also
news
to
me
that
for
kubernetes
is
also
going
as
the
prior
update
to
this
was.
It
will
still
be
online
for
us,
but
what
we're
now
trying
to
solve
is
okay.
This
is
coming
very
soon.
In
fact,
the
date
is
not
confirmed.
A
We
just
know
it
soon
and
given,
given
that
time
frame
and
the
capacity
of
work
that
all
of
us
are
able
to
do,
it's
very
likely
that
we
need
to
prioritize
communicating
that
that
is
happening
first
before
try
or
maybe
in
parallel
than
trying
to
possibly
replace
that
tutorial
service
with
something
else.
A
What
that
something
else
is
we
don't
know
that
work
also
needs
to
happen
in
terms
of
investigation
and
looking
into
what
would
be
the
replacement,
and
that
work
is
very
important,
because
that
replacement,
actually
what
we
choose
would
serve
as
a
way
that
we,
the
kubernetes
project
kind
of
prefers,
a
certain
type
of
tutorial
and
so
on,
and-
and
so
that's
also
going
to
be
a
very
important
thing
that
it's
not
just
within
the
stigdox
community
that
we
just
say.
Yes,
we
want
this.
G
There's
another
detail:
that's
going
to
be
relevant,
catacoda
does
not
cost
money
to
use,
and
you
do
not
have
to
sign
up
to
use
it,
which
has
meant
huge
volumes
of
abuse,
and
that
has
litter
problems
all
of
the
Alternatives
either
cost
money
to
use
or
require
sign
up
or
both.
G
So
that
is
going
to
be
like
there
is
a
change
Brewing
where
we
change
from
it.
You
can
try
this
out
to
go
and
sign
up
to
a
service
that
is
not
ours
and
try
this
out
all
the
possibility
that
we
remove
this
tutorial.
You
know:
remove
a
big
chunk
of
functionality
that
people
like
so
there's
a
whole
bunch
of
things
to
communicate,
to
do
to
plan.
A
Yeah
and
I
think
you
pointed
out
something
very
important
there
in
parts
of
the
communication
team,
which
is
calling
out
that
hadakuda
had
provided
a
way
for
someone
freely
without
signing
up
and
without
paying
to
be
able
to
learn
and
given
that
we're
an
open
source
project.
A
That
was
also
our
preference
to
push
folks
to
to
a
to
a
solution
like
this
on
the
tutorial
side
and
so
needing
to
find
an
alternative
to
that,
and
if
one
doesn't
exist,
we'd
prefer
not
to
ask
people
to
pay
to
do
tutorials
and,
and
that's
something
that
on
the
communications
are
we
may
need
to
kind
of
call
out
in
either
the
blog
posts
and
and
emails
that
we
send
to
so
what
I'm
here
Nate
please.
A
G
The
message
from
O'reilly
was
we'd
like
to
shut
this
down
at
the
end
of
the
year,
and
we
got
that.
Let
me
just
check
my
message:
I,
don't
think
this
is
a
public
message,
so
I'm
not
quite
anything
confidential.
G
Yes,
on
the
7th
of
December,
it
is
our
intent
to
take
the
site
down
entirely
by
the
end
of
the
year,
though
this
is
something
I'd
like
to
discuss
and
that's
from
Jesse
Meeks
at
O'reilly.
So.
A
E
E
E
Just
because
it's
it's
in
in
addition
to
putting
the
communication
out
I,
think
we
should
start
reaching
out
to
folks
that
we
know
can
help
with
this
I
mean
we
have
to
find
some
folks
with
some
capacity
to
some
time
to
do
this
and
and
get
like
a
board
together
and
get
on.
A
It
I
can
I
completely
agree.
I
completely
agree,
yeah
I
think
that's
a
great
idea.
I've
just
noted
that
in
the
agenda
here
and
I
think
in
the
issue
that
you've
linked
there
in
the
agenda
as
well,
Tim
we
we
could.
We
should
keep
discussing
in
the
issue
specifically
there.
G
A
Okay,
what
I
want
to
do
just
quickly
is
just
recap:
what
I
think
that
at
least
the
next
immediate
steps
would
be
and
then
see
if
we
get
a
general
agreement
before
we
go
to
other
comments,
so
the
general
agreement
I
believe,
is
we
just
want
to
communicate
that
this
is
happening
versus
trying
to
push
it
out
any
further.
So
we
need
to
communicate
that
the
shutdown
is
happening.
A
We
have
several
channels
of
communication
that
needs
to
go
in
into,
and
so
we
need
to
get
a
team
together
to
try
and
help
a
create
that
communication
and
b
roll
it
out
and
doing
that
fairly
fairly
soon.
It
sounds
like
the
the
two
to
Do's
that
that
are
currently
on
the
table
right
now,
any
pushback
on
that
or
additions
I.
E
I
also
think
that
Beyond
just
the
communication
that
when
I
I
was
talking
about
putting
a
team
together,
I
was
I,
I
I
mean
start
doing
the
work
like
start
planning
how
it
can
can
go,
because
if
we've
only
got
weeks
and
we
are
putting
a
team
together
to
communicate
we're
going
to
miss
our
our
potential
deadline
here.
E
So
I
I
would
suggest
that
we
we
reach
out
to
folks
who
again
like
I
I,
like
putting
it
out
there
to
to
to
to
to
say:
okay
communicate
with
the
whole
I
think
there
are.
There
are
a
couple
of
people.
I
have
in
mind
that
if
they
have
capacity
can
just
start
right
and
I
think
that
we,
if
we
should
probably
start
reaching
out
to
those
folks,
potentially
even
individually,
just
to
get
things
rolling
and
things
like
understanding
what
what?
E
A
Gotcha
Patrice
I
want
to
go
to
you
next.
B
G
I
will
because
if
someone
got
a,
if
you
grab
for
cat
button
in
the
English
docs,
you
will
and
do
a
grep
count.
I
can
do
that
or
someone
else
willing
to.
A
Yeah
so
so
then
I'm
hearing
that
there
are
so
I
I
completely
agree
with
you
Nate
to
go
back
to
your
point
about
also
doing
the
work,
but
I'm
also
cognizant
of
the
fact
that
if
we
don't
communicate
very
soon
about
the
imminent
shutdown
I
think
those
these
need
to
be
two
separate
streams
of
work
that
happen
in
parallel.
Let's
say
yeah
so
so.
A
For
me,
the
communication
is
kind
of
like
first
we're
very
very
soon
after
they're,
getting
the
team
together
to
do
the
work
can
happen,
but
ideally,
ideally
in
the
next
couple
of
weeks,
we
have
something
out
comms
wide.
That's
what
that's
kind
of
what
I'm
thinking.
E
Yeah
and
and
come
together
and
and
that's
and
that's
again,
if
we're
talking
about
the
scale
of
weeks
and
if
they
really
are
wanting
to
shut
this
thing
down.
December
31st
of
last
year,
I'd
like
to
see
this
like.
If,
if
by
the
time
we
meet
again,
we
haven't
done
the
comms
and
and
and
started
this
work.
I
think
we're
we'll
have
been
dragging
our
feet.
D
A
Totally
so
Tim,
just
in
your
comment,
there
we've
got
the
link
from
the
tutorial
Bunsen
things
to
tell
for
sharing
those
those
two
and
then
the
whole
separate
rebook.
If
I
could
ask
if
we
could
pop
that
into
the
issue
as
well,
so
we
don't
lose
it
in
this
chat.
That
would
be
really
great
so
that
we've
got
a
place
to
start
from
when
we
start
that
parallel
work.
A
That
would
be
awesome,
I'm
putting
my
hand
up
to
already
try
and
start
getting
folks
together
on
the
communication
side
of
things,
and
we
can
chat,
maybe
either
in
our
slack
in
our
slack
groups
or
a
little
bit
after
once.
That
work
is
at
least
started
to
then
set
up
that
parallel
work
stream
of
actually
what
I
believe
we're
going
to
be
doing
is
removing
the
links
to
the
tutorials
and
the
short
codes.
A
Basically,
okay,
we've
got
25
Pages
great
thanks
Tim,
but
let's
use
the
issue
as
the
kind
of
main
source
of
Truth
for
a
lot
of
the
information
that
we
want
to
kind
of
put
together
and
I'll
jump
in
there
to,
as
I
said
after
the
meeting
to
kind
of
list,
what
the
next
steps
are
and
and
assign
myself
and
maybe
put
a
call
out
to
others
of
who'd
like
to
kind
of
sign
up
and
help
with
some
of
that
work.
A
Great
any
other.
Last
areas
here,
I
know
I'm
I'm
wary
of
time,
given
that
we've
spent
a
bit
of
time
on
this
topic
and
just
want
to
check
if
anyone's
got
any
last
points.
G
Yeah,
this
is
something
where
there
isn't
one
right
answer:
I
mean
like
with
docashin.
There
was
one
right
answer
that
a
cap
had
gone
through.
It
was
removed
to
dockershim.
G
We
should
open
a
GitHub
discussion
and
direct
people
and
tell
people
if
you
want
to
discuss
it,
give
people
that
Mark
that
place
as
went
to
discuss
it.
A
Yeah
definitely
for
sure
a
question:
you've
got
Nate
other
tutorials,
localized
I,
don't
believe
so.
F
A
So
nay,
your
question
was:
are
they
contained
on?
Are
their
links
also
on
the
localized
versions
of
our
docs
I?
Think
was
your
question
great?
Okay?
Yes,
that
is
easy
to
answer.
I
believe
they
would
be,
but
the
true
tutorials
are
all
in
the
same
language
that
they
come
in
yeah.
A
All
righty
cognizant
of
time
we've
got
a
couple
of
to-do's
and
we'll
be
using
that
main
issue
for
this
to
communicate
a
lot
of
that.
There
might
be
folks
in
this
in
this
current
virtual
room.
A
They
get
kind
of
pings
from
me
in
terms
of
a
couple
of
suggestions
and
things
to
work
on,
but
you'll
be
hearing
from
me
in
a
little
while
yeah
thanks
so
much
for
the
great
discussion,
everyone
to
try
and
kind
of
get
ourselves
a
bit
galvanized
around
this
and
and
yeah
I'll
move
us
on
to
the
next
agenda
topic,
but
any
other
comments
around
the
catechoda
work.
A
Let's
concentrate
that
in
the
issue
there,
so
we've
got
a
centralized
place
where
a
lot
of
the
information
is
being
stored,
thanks
all
right
moving
down
now
for
the
next
Point
here,
which
is
also
about
a
general
awareness
Point
here
from
Divya,
as
I
mentioned
earlier,
we're
doing
a
bunch
of
pruning
of
the
previous
and
reviewers
list
based
on
devstack
contributions.
A
Now
I
want
to
note
here-
and
this
was
already
noted
in
a
couple
of
the
other
PRS-
that
that's
not
always
a
great
indicator
of
how
people
contribute
and
how
they
work
in
different
areas
of
our
project,
especially
on
the
localization
side.
A
lot
of
times.
A
And
so
we
just
wanted
to
clear
that
up
as
a
we're
trying
to
do
some
cleanup
just
to
make
sure
folks
are
still
around
still
wanting
to
kind
of
be
reviewers
and
approvers
for
not
only
the
English
stocks
but
also
the
other
localized
docs.
And
it's
also
an
opportunity
that,
if
people
don't
want
to
anymore,
they
can
have
their
names
often
and
and
not
feel
pressure
that
they
need
to
kind
of
continue
if
they
don't
wish
to.
A
So
that's
really
the
the
the
use
case
here
that
that
we're
going
with
New
Year
kind
of
cleaning
house
so
to
speak,
and-
and
this
is
something
that
that
is
being
spearheaded
by
dvo,
which
is
great
she's-
got
some
slack
threads
here,
as
well
as
the
Google
group
thread
that
we
sent
out
to
the
mailing
list,
and
you
can
see
the
specific
pull
requests
there,
that
that
have
been
opened.
A
A
But
of
course
I
do
want
to
State,
especially
for
new
folks
here
that,
if
something
like
that
was
to
happen,
that
you
were
a
viewer
or
approver
for
either
the
English
documentation
or
another
localized
area
and
after
inactivity,
your
name
comes
off
of
those
lists.
You
can
be
requested
to
be
re-added.
That's
absolutely
completely!
Okay,
you
can
come
back
when
you
have
the
capacity
to
and
that's
something
that
we
will.
A
I
also
want
to
kind
of
put
out
there,
as
as
a
as
a
as
a
as
a
way
of
being
able
to
move
forward
here.
That
folks
can
always
take
breaks,
have
some
inactive
time
in
open
source
projects
like
ours
and
come
back
when
they've
got
the
capacity
and
the
means
to
want
to
contribute
and
work
in
that
in
those
roles
again.
A
So
just
putting
that
out,
there
feel
free
to
have
a
look
at
some
of
those
PR's
to
make
sure
your
names
are
or
are
not
included,
and
thanks
so
much
to
divio.
If
you
are
watching
in
the
future
for
a
lot
of
that
work
that
you're
doing
there
on
the
cleanup
side
thanks
so
much
all
right,
more
more
admin
and
cleanup
we're
updating
the
maintain
access
to
netlify,
based
on
a
few
discussions
as
well
just
putting
that
in
information.
A
Here
specifically,
this
came
up
coming
off
of
the
discussion
from
not
only
our
doc
Sprint
in
in
the
North
American
version
of
the
of
kubecon
that
we
that
we
held
there,
but
also
with
the
release
retro
that
was
held
for
1.26.
A
A
So
we
wanted
to
basically
make
sure
that
we're
cleaning
up
that
process
so
that
release
can
continue
to
be
smooth
and
that
stick
docks
can
continue
to
support
in
the
best
way
possible,
as
releases
happen,
so
that
there's
no
hiccups
on
the
admins
and
permissions
side.
So
we're
cleaning
up
there
again,
big
thanks
to
Divya
for
doing
a
lot
of
that
work.
A
All
right.
That's
the
big
three
of
divya's
areas
that
she's
added
there
that
we've
now
discussed
so
I'd,
now
love
to
go
to
the
rest
of
our
agenda
and
hear
natish
thanks
so
much
for
waiting.
Well,
we
went
through
a
lot
of
different
different
other
topics,
but
you've
got
here
an
issue
and
appear
that
you'd
like
to
discuss.
H
Yeah,
the
pl
was
basically
for
the
like
the
improving
that
regarding
mentioning
about
notes.
So
what
the
thing
that
I
was
writing
about
the
notes
and
the
docs
are
written
very
good,
and
there
are
particular
lines
that
basically
says
that
there
are
two
main
ways
to
have
nodes
added
to
REI
server
right.
So
I
was
like
just
guessing.
H
Is
actually
the
node
objects
that
I
need
to
erase
server,
which
you
know
represents
the
nodes,
so
I
thought
like
what
basically
is
an
issue
and
add
some
documentation?
Although
I
have
raised
a
PR
after
the
team
has
basically
mentioned
about
Piazza
welcome,
but
as
per
the
latest
review
by
the
10
GM.
Sorry,
if
I'm
pronouncing
that
I'm
wrong,
he
basically
mentioned
that.
Maybe
the
pr
might
not
sound
so
good
or
might
not
be
sound
so
beneficial.
H
So
I
would
like
to
take
out
the
suggestion
from
maintainers
like
how
to
proceed
with
this
issue
as
well
as
the
period
because
the
issue
has
been
raised
by
me
and,
of
course,
the
peers
as
well.
A
A
A
A
Okay,
I
do
believe.
I
do
think
that's
what
nutrition
is
asking
some
advice
here
in
terms
of
oh,
yes,
Natasha
back
hello,.
A
No
worries
if
I
can
suggest
possibly
something
that
might
help
if
you
turn
off
your
video,
but
keep
your
audio
that
might
help
with
some
of
the
comms
issue.
Yeah
great
I
was
just
wanted
to
double
check.
What
you're
asking
around
this
issue
in
PR
is
that
given
kimming's
comments
in
the
pr
about
the
usefulness
of
what
you've
added
you're
checking
how
to
proceed
with
this
change?
Is
that
correct.
A
Great
anyone
on
the
call
won't
have
any
comments
or
suggestions.
A
Nate
no
I.
E
Just
want
to
say
making
the
argument
that
you
have
you
you've
already
addressed
the
the
issue.
You've
said
hey,
this
is
what
I
think
and
and
why
I
think
it,
which
I
think
goes
a
long
way
to
sort
of
getting
your
point
across.
So
at
this
point,
you've
you've
done
that
and
I'm
curious
to
see
what
keyming's
response
to
that
is
or
any
other
reviewers
response
to
it.
A
lot
of
these
types
of
PRS
are
back
and
forth
discussions,
and
so
don't
feel
slated
it's
it's.
G
One
of
the
things
that
concerns
me
is
that
if
we
merge
this,
as
is
there's
a
bunch
of
suggestions
that
Jimmy's
made-
and
it's
not
a
great
idea
to
merge
a
PR
that
kind
of
creates
more
work
for
cleanup,
so
nitish
the
the
sort
of
the
style
guide
feedback
where
you
could
go
through
our
style
guide
and
and
see
the
sort
of
as
a
fairly
unambiguous
thing.
Our
style
guide
says
you
write
these
things
a
certain
way.
G
So,
when
you're
mentioning
nodes,
you
use
a
capital
N,
because
it's
a
kind
in
the
kubernetes
API
those
things
need
fixing,
because
it's
only
a
small
PR.
You
will
see
sometimes
that
I
mean
I'm
a
reviewer.
Sometimes
someone
hasn't
got
the
capitalization
right.
It's
a
big
PR
and
there's
a
couple
of
places
where
things
aren't
right
and
in
a
big
PR
the
the
scales
balance
differently.
G
There
might
be
a
whole
load
of
good
stuff,
maybe
they're
documenting
a
whole
new
thing
or
they're,
making
an
important
change
and
not
everything
is
perfect
and
the
balance
there
is
well
overall.
The
website
is
better,
but
if
we
merge
this,
as
is
I'm
afraid,
we
would
be
making
work
for
someone
to
do
an
immediate
follow-up
PR
to
fix
these
things,
and
so
one
of
the
things
one
of
the
concerns
is
that
we
should
fix
all
that
and
and
for
a
small
PR
like
this.
G
My
second
point
is
that
nodes
are
interesting,
so
they
are
an
interesting
kind
of
object
in
kubernetes
because
they
are
external
and
most
kubernetes.
Things
are
either
internal
to
kubernetes
or
much
more
directly
under
kubernetes
controls.
So
you
have
a
deployment
and
then
it
makes
these
things
called
pods
which
are
kubernetes
Concepts.
G
You
have
a
pod
and
okay.
That
goes
and
makes
containers
and
so
on,
but
the
Pod
itself
is
a
thing
that
didn't
exist
in
people's
understanding
of
the
cloud
before
kubernetes
came
along
nodes
we
had
nodes
before,
and
so
there
is
this
distinct
distinction
to
making
people's
minds
I,
don't
know
where
that
belongs.
I,
don't
know
where
that
distinction
belongs
between
objects
and
the
things
they
represent.
Maybe
it
belongs
on
a
different
page.
G
This
page
is
is
an
important
one
to
get
right,
so,
unfortunately,
the
scales
again
are
going
to
tip
towards.
We
need
to
get
the
text
bang
on
right
and
it's
going
to
tip
away
from
this
is
good
enough.
G
In
my
view,
I
think
we
need
a
PR
that
really
explains
this
concept
well
and
that
is
difficult
to
craft.
I've
worked
on
this
page
I
know
that
I
found
it
difficult
to
explain,
notes
to
an
audience.
So,
unfortunately,
the
the
task
you
have
picnic-ish
is
one
which
is
which
requires
you
know
quite
good
documentation,
skill
and
and
thought,
and
that's
just
how
it
is
we,
it's
not
good
for
the
kubernetes
project
for
us
to
consider
anything
except
really
thought
through
PRS.
A
Yeah
and
and
going
back
to
Nate's
point
is
that
these
kinds
of
changes
often
result
in
a
lot
of
conversation
back
and
forth
in
the
pr
itself
and
you're
really
at
the
beginning.
It
seems
of
that
discussion
and
so
looking
at
kimming's
suggestions
keeming
by
the
way.
In
addition,
for
you
to
know,
is
actually
one
of
our
tech
leads
here
at
sigdox,
and
so
looking
through.
A
Cuming
suggestions
would
be
a
great
first
place
to
start
and
engaging
in
a
discussion
of
specifically
the
issue
and
your
point
of
view,
and
then
looking
at
like
Tim,
has
mentioned
how
we
can
make
every
single
aspect
of
the
change
that
you're
making
really
be
high
quality.
Given
the
importance
and
scale
of
the
of
the
pr
that
is,
that
is
being
opened.
H
Sure,
thank
you
so
much
before
the
like
the
after
the
gaming
suggestion.
I
was
thinking
about
like
putting
the
suggestions
asking
mentioned
and
it
was
like
thought
like.
Okay,
the
documentation
is
good
enough.
Maybe
I
should
not
bring
those
changes,
but
please,
let
me
know
if
I'm
sounding
this
correct,
basically
I
have
to
you
know,
go
through
the
documentation
style
and
put
out
the
kimming
suggestion
and
take
this
PR
on
further
discussions
right.
A
A
Great
thanks,
Satish
and
feel
free
to
turn
your
video
back
on.
If
you
want
so
you
feel
like
you're
part
of
the
meeting
just
so
that
to
you
know,
don't
want
to
make
don't
want
to
make
you
feel
like
you
have
to
keep
it
off
the
whole
time.
Just
so,
just
for
the
audio
was.
It
was
great
to
be
able
to
hear
you
clearly
there.
So
thank
you
all
right,
thanks
so
much
for
bringing
that
to
our
attention
and
Tish
I
want
to
move
on
to
the
next.
C
So
maybe
I
would
like
to
collaborate
with
nitish
in
this
PR
and
then
maybe
I
can
join
with
him
to
maybe
the
starting
point.
This
little
Deep
dive
into
this
issue,
and
you
know,
but
this
maybe
you
can
let
me
know
if
I
we
can
catch
up
offline
and
then
we
can
do
this
together.
Yeah
thank.
A
Awesome
thanks
everyone,
okay,
I'm,
being
a
bad
moderator
in
the
sense
of
the
time
that
we
are
spending
in
this
meeting
in
our
first
one
this
year,
I
know
Tim's
face
is,
is
everyone's
feeling
right
now,
so
I'd
like
to
go
through
the
next
next
discussion
points
a
little
quickly
if
possible,
so
we
can
get
them
done
in
the
next
10
minutes.
Tim
I
want
to
go
to
you
now.
A
G
Yeah
so
I
hope
that
someone
else
can
speak
as
well.
In
fact,
I
might
ask
Ray
Ray,
because
I
know
you're
familiar
with
this
PR.
If
you
could
join
in
and
I,
don't
want
it
all
to
be
me
because
the
whole
the
whole
problem
with
this
PR
was
probably
you
know,
I
think
too
much
of
one
voice,
mine
but
I
I
want
to
highlight
it.
So
this
is
basically
or
disc
the
the
the
the
pilot
this
PL.
G
G
That
disagreement
happens
where
everyone
can
see
it,
which
is
a
little
bit
embarrassing
for
me,
but
it
still
needs
to
happen,
and
so
this
is
a
chance
for
me
to
get
feedback
on
how
I
handle
things
here
with
this
PR
and
what
we
could
learn,
what
so,
what
I
could
learn
and
what
we
could
learn
about
getting
PR's
in
and
about
maybe
like
things
like
review
guidelines
whatever,
so
that
we
do
a
better
job
next
time,
and
this
is
where
I'd,
like
you
Ray,
if
you're
willing
to
to
come
in
and
and
offer
your
perspective
on
on
the
context
here,.
D
Yeah,
this
is
a
difficult
pull
request
to
well
the
for
me.
D
Whenever
I
review,
pull
requests,
I
always
wait,
balance
the
benefits
of
the
pull
request
and
and
there's
another
consideration
that
I
do
not
consider,
because
that
should
be
is
them
parts,
and
this
also
might
I
think
it
was
mentioned
in
terms
of
the
comments
of-
or
it
has
been
mentioned
in
other
comments
for
other
PRS
is
that
when
we
refactor
pull
Pages
and
when
we
and
we
rewrite
Pages
as
well
like
how
does
that
affect
localizations
and
other
teams
with
with
with
the
project
and
I,
know
what
this
pull
request?
D
Another
pull
requests
are
large,
there's
also
the
concept
of
of
how
we
balance,
how
large
of
a
pull
request
should
be
versus
where
we,
where
we
separate
out
pull
requests
or
we
step
out
by
commit
I,
don't
have
any
I
I,
I,
I
I,
don't
know
if
I
have
any
advice
or
about
about
what
this
specific
pull
request.
D
I
would
have
to
I
put
I'd
put
more
Cycles
on
it,
but
I
think
we
just
need
to
discuss
quite
a
bit
more
and
actually
have
policies
or
put
it
in
in
a
review
guide.
We
do
have
a
reviewing
guide
and
enter
on
our
on
our
website
on
reviewing
and
and
how
and
also
making
PRS
and
refactoring
pages.
So
I
do
need
to
take
some
more
Cycles
on
how
on
how
we
move
forward
and
what
we
learn
from
this
pull
request.
A
A
This
is
no
in
no
way
shape
or
form
just
only
talking
to
you,
but
I
think
that
what
we
can
all
learn
is
that
there
are
many
ways
that
we
discuss
certain
things
and
share
information
around
things
that
are
going
on
in
a
certain
PR
and
there's
all
a
lot
of
different
contexts
in,
in
this
specific
case,
that
I
think
was
actually
missing
from
the
main
PR
itself,
where
a
lot
of
communication
was
taking
place
and
one
piece
of
context
that
was
missing
was
that
a
PR
that
was
needed
for
docs
for
the
previous
lease
was
relying
on
this
one,
which
was
part
of
the
reason
for
I.
A
Believe
you
Tim
actually
coming
to
the
meeting
to
say:
hey,
we
kind
of
do
need
to
kind
of
get
this
through.
What
do
we
think
and
so
I
think
communication
around
all
the
different
kind
of
moving
Parts
us
learning
that
having
that
in
actually
one
place
that
we
can
continue
those
discussions,
as
you
say,
Ray
and
all
of
us
can
be
involved
in
figuring,
something
out
and
then
agreeing
or
disagreeing
I.
A
Think
that's
the
big
thing
that
we've
learned
here
on
on
this
from
this
specific
PR,
where,
on
top
of
that,
those
I
think
a
few
assumptions
made
around
certain
answers
being
okay,
but
we
just
didn't
know
and
so
I
think
yeah
the
communication
pieces.
For
me,
the
the
big
learning
here
in
communicating
in
one
specific
Main
Place
versus
a
little
bit
in
a
Sig
docs
meeting
a
little
bit
on
a
PR
a
little
bit
in
a
slack
thread.
Having
all
the
main
points
in
one
one
area.
G
A
Yeah
definitely
I
think
if
there's
a
way
for
us
to
possibly
attend
an
APAC
meeting
in
future,
that's
a
little
bit
nicer
to
our
time
zones
Tim
that
might
be
great
as
well,
so
that
we
can
all
be
in
the
same
room.
That
might
be
a
really
great
idea.
A
All
right,
yes,
knock,
knock
agenda
time.
We've
got
a
couple
more
points
and
then
we're
almost
done
for
the
for
our
first
meeting
of
the
year,
Nate
and
Patrice
for
the
release.
Branch
deploys
I'd
love
to
hand
it
over
to
you.
B
The
interest
interest
of
time-
maybe
Abby
could
go
first,
because
this
can
be
pushed
to
the
next
meeting.
A
F
Patricia
Abby,
please,
over
to
you
Yes
mine,
is
more
of
a
general
awareness.
No
I've
opened
a
PR
about
adding
documentation
to
the
kubernetes
community
repo
around
our
localization
sub
project,
so
I
just
wanted
to
share
that
out
a
link
out
to
the
pr
really
open
to
feedback.
If
people
are
interested
in
taking
a
look
at
what
those
dots
are,
I
just
wanted
to
put
it
out
to
the
put
it
out
on
into
the
world
into
the
recording
to
get
some
feedback,
and
that
was
it
for
me.
A
Great
thanks
Abby
for
those
who
don't
know
localization
lead
all
localization
topics,
questions
interest,
please
ping
Abby.
She
would
love
to
help
you
and
connect
with
you
all
right,
Patrice
and
Nate.
Please
close
us
out
for
today's
meeting.
B
Yes,
so
the
context
for
this
is
the
migration
to
Google
analytics
4
right
now,
it's
it's
done,
but
as
Abby
and
I
have
discussed
out
of
band
there's
a
manual
step
that
needs
to
be
done
every
time
a
release
comes
out
and
we'd
like
to
streamline
that
a
bit
and
in
relation
to
that
there's
this
PR
comment
which
Tim
has
reviewed.
So
it's
maybe
kind
of
maybe
a
ping
for
Tim.
B
If
she
could
take
another
look
at
the
comment,
you
would
ask
me
to
provide
a
bit
more
context
and
justification
for
the
particular
change
request
and
that's
there
and
that
could
be
enough
for
today
for
today
and
the
next
meeting
we
could
maybe
spend
a
bit
more
time
on
it
and
Tim.
You
can
offer
some
feedback
or
if
you
have
feedback
now,
that
would
be
welcome
as
well.
G
I
I
I
guess.
My
one
comment
is
that
if
I
have
looked
at
a
PR,
it
is
absolutely
open
to
someone
else.
Who's
not
called
Tim
to
to
do
the
next
review
on
it.
Okay,
yes,.
A
Team
does
Tim.
Does
a
lot
of
work
here.
So
we're
just
trying
to
take
a
bit
of
a
load
of
sleep.
Ray
you've
got
your
hand
up
yeah.
D
So
I'll
take
a
look.
I'll,
take
a
look
at
this
and
also
to
see
what
the
steps
necessary
when
we
do
cut
a
release.
Branch
I'm
gonna
do
an
update
to
the
handbook
for
the
blue
stocks,
leader
team
as
well.
So
we
should
have
this
in
the
handbook,
even
if
it's
not
necessarily
a
step
for
the
for
the
release.
Stocks
lead,
but
at
least
we
we
have
it
codified
and
have
it
for
any
any.
In,
like
a
like
a
tech
leader,
stick
co-chair
would
have
to
do
so.
F
Abby,
yes,
the
only
other
piece
I
wanted
to
mention,
which
is
connected
to
divya's
netlify
access.
Pr
is
some
of
the
blocking
steps
for
moving
forward
with
the
things
we
want
to
do
with
the
Google
Analytics
and
making
things
easier
for
the
release
depend
on
doing
some
updates
in
netlify,
which
we
don't
have
anybody
who
has
access
to
that?
Who
has
the
bandwidth
I
know?
Patrice
has
offered
to
do
it,
but
he
doesn't
have
access,
do
not
apply
to
make
these
changes,
so
it's
or
a
lot
of
the
things
building
together.
F
So
that's
just
one
piece
I
wanted
to
raise
that
it's
connected
to
the
netify
access
as
well
a
little
bit.
A
That's
a
really
good
point
that
you've
brought
up
I'm
just
looking
at
the
time
that
we
have
I
know
that,
as
as
docs
leads,
we
are
looking
into
trying
to
figure
out
who,
at
the
cncf,
should
have
knit
lafly
access
to
actually
unblock
work
like
this.
That's
like
a
parallel
piece
of
work,
that's
kind
of
in
in
the
midst
at
the
moment
and
I'm,
hoping
that
that
could
be
kind
of
a
solve
suit
that
helps
unblock
some
of
this
work
potentially
as
well.
I
believe
we've
got
a
issue.
A
The
devious
opened
an
issue
specifically
for
that,
so
we
can
kind
of
jump
in
and
Revitalize
that
so
that
possibly
Patrice
or
others
at
the
cncf
could
kind
of
jump
in
and
unblock
some
work
there
great
Patrice
I
wanted
to
offer
for
you
and
Nate.
We
can
prioritize
this
topic
again
at
the
next
meeting
kind
of
put
it
at
the
Top
If
you
like,
so
that
we
can
come
back
to
any
further
comments
if
needed,
feel
free
to
kind
of
do
that
and
put
it
at
the
top
of
the
list.
A
I,
the
the
the
you
have
been
given
the
the
permissions
that
has
been
so
that's
so
that
you
can
take
that
time
to
discuss
for
next
time,
thanks
great
a
minute
before
the
usual
longer
time
of
our
meeting,
but
Nate
you've
got
some
you've
got
a
hand
up
just
quickly.
E
Just
just
quick
weekly
goes
out
on
Fridays
and
if
we
want
to
get
something
in
for
that
week,
we
like
to
get
things
in
by
Thursday
at
12
p.m.
Ct
and
I
do
know
who
the
person
is
now
so
I
can
pick
that
up
offline
and
delay.
You
know
great.
A
Yeah,
if
we
could
have
that
same
info
in
the
issue
again
as
well,
so
that
we've
got
that
all
centralized
that'd
be
awesome,
very,
very
short
deadline
for
this
week,
a
bit
longer
for
next
week,
but
let's
save
a
bit
of
it
as
a
stretch.
Call
if
that's
a
possibility,
all
right,
big
thanks
to
everyone.
A
I
know
it
was
a
longer
meeting
than
what
we
usually
are
used
to
starting
off
2023
strong,
really
looking
forward
to
collaborating
with
you
all
and
a
couple
of
things
that
we've
mentioned
today
and
further
work
happening
for
the
127
release
as
it
progresses.
I
want
to
wish
you
all,
as
we
say
here
in
Germany,
guten
Rush,
which
means
happy
slide
into
2023.,
and
wishing
you
all
a
really
nice
rest
of
your
week
and
we'll
see
you
in
a
couple
of
weeks
for
our
next
meeting
take
care.
Everyone.