►
From YouTube: K8s SIG Docs Meeting for 20221004
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
and
recording
has
has
begun
here.
Welcome
everyone
to
this
community
edition
of
Sig
docs
on
a
community
meeting,
should
I
say
for
Sig
docs.
It
is
Tuesday
the
4th
of
October
2022
in
everyone's
respective
time
zones.
I
will
say,
given
that
we
are
trying
to
use
the
UTC
standard,
it
is
1730
UTC
in
terms
of
our
starting
time
today
and
big
welcome
to
everyone.
A
I
wanted
to
just
remind
folks
that,
as
this
is
a
kubernetes
community
meeting,
we
do
abide
by
the
kubernetes
code
of
conduct,
and
that
does
mean
that
we
want
folks
to
be
respectful
and
kind
to
one
another
in
all
of
the
ways
that
we
work
and
collaborate
together,
including
this
meeting,
including
on
issues
and
PRS
and
including
written
via
our
slack
Community
as
well.
A
So
just
a
note
on
that,
if
anyone
has
any
issues
or
things
that
they
want
to
point
out
regarding
issues
with
the
code
of
conduct
and
things
that
they're
experiencing
in
TIG
docs,
there
is
a
way
to
reach
the
community
community
and
with
kubernetes
that
I'll
share
in
the
chat
shortly
and
then
we'll
put
that
in
the
notes
too,
so
that
folks
know
a
way
that
they
can
report
those
things.
A
Firstly,
big
thanks
to
Ray
who's
going
to
take
notes
for
me
because
I
suck
at
multitasking.
Thank
you
to
Ray
and
to
kick
the
Kickstart
today's
agenda
I
wanted
to
quickly
ask
if
we've
got
any
new
folks
on
the
call
that
wanted
to
call
out
and
say
hello,
you
can
add
it
in
the
chat
or
unmute
Emily
I've
seen
you
raised
your
hand,
I'd
love
to
get
you
to
introduce
yourself
and
say
hi.
B
Hi
everyone,
a
message
earlier
in
this
live
Channel.
My
name
is
Emily
I
am
from
Canada
I,
currently
go
to
university
at
the
University
of
Toronto
and
I've
heard
about
kubernetes
about
a
year
ago,
but
I
wasn't
confident
enough
to
contribute
since
I
didn't
have
any
Works
experience
back
then,
but
now
that
I
have
like
five
month
ish
into
my
Co-op,
which
is
in
a
software
company
I
think
it's
time
for
me
to
contribute
looking
forward
to
working
on
kubernetes
with
everyone.
Thank
you.
A
That's
awesome:
Emily
welcome
it's
great
to
have
you
as
part
of
the
kubernetes
crew.
Anyone
who's
willing
to
contribute
is
is
definitely
a
crew
member
here
and
yeah.
You've
already
mentioned
that
you,
you
said
hi
and
slack.
That's
great.
A
lot
of
the
pin
messages
that
you
already
referred
to
will
really
help
you
on
your
contribution.
Journey,
which
is
awesome.
A
You've
got
a
lot
of
helpful
folks
here
and
on
the
slack
asynchronously,
who
are
happy
to
help
you
out
and
answer
any
questions
that
you
have
so
big
welcome
great
great
to
have
you
here
for
sure.
Thank
you.
C
Yeah
I
think
I
could
say
hello
well
here
my
name
is
Carol.
Valencia
I
am
happy
with
the
sick,
Dogs
release
of
this
release,
yeah.
Well
any
doubts
that
you
have
it
or
any
problem.
Just
please
pick
me
I
think
also
some
of
my
thing
from
my
shadow.
It's
here,
I,
don't
know
it's
here.
He
presented
this
receipt
yeah.
We
both
are
working
together
in
this
new
release,
great.
A
To
have
you
here
Carol,
thank
you
for
saying
hello.
We
we
may
actually
defer
to
you
a
little
bit
later
when
we
go
into
a
bit
of
a
release
update
for
126.
if
you've
got
any
updates
there,
we
can
get
to
you
that
soon
but
great
for
you
to
say,
hi,
welcome.
We're
always
happy
to
have
new
folks
around
in
sick
docs.
So
welcome
thanks.
So
much.
D
And
I'm
an
undergrad
at
the
University
of
Toronto
I
I,
usually
contribute
to
kubernetes
and
tensorflow
a
lot.
A
D
Yeah,
that
is
correct,
awesome,
so
this
time
around
at
cubecon
next
view
a
bit
heavy
schedule,
because
I
have
like
four
talks
in
a
single
day:
co-located
events
and
the
main
event
so
I
don't
know
how
I'll
manage
it.
Somehow
amazing.
A
Well,
congratulations
on
all
those
great
opportunities
and
welcome
to
seek
docs.
We,
we
I,
believe
you've
actually
made
some
a
couple
of
contributions
already
that
been
a
super
appreciated,
specifically
by
Tim.
If
he's
around
I
know,
he
gave
you
a
shout
out
recently
about
some
great
work
that
you've
done
so
thanks,
rishit
welcome.
Thank
you.
So
much.
E
A
A
Yes
welcome.
Thank
you
so
much
we're
we're
looking
forward
to
helping
you.
This
is
great
brand
new
not
only
to
kubernetes
but
open
source.
That's
really
exciting
great
to
hear
about
hacktoberfest
as
well.
Unfortunately,
the
kubernetes
project
doesn't
participate,
but
many
other
really
awesome
and
beautiful
projects
do
but
we're.
E
A
Really
happy
to
help
out,
and
that's
that's
really
awesome-
that
you're
getting
into
open
source
welcome.
A
If
you
wish
to
say
hello-
or
you
can
add
your
name
also
to
the
agenda-
that
we
have
as
just
a
note
that
you
were
a
new
person
in
the
meeting,
that's
also
completely
okay,
a
reminder
that
you
need
to
be
part
of
the
Sig
docs
mailing
list
in
order
to
be
able
to
edit
the
agenda
and
that'll,
give
you
the
access
to
be
able
to
jump
in
and
add
different
talking
points
or
your
name,
and
so
with
that.
Thank
you.
A
So
much
to
everyone
who
said
hi
and
who's
introduced
themselves
great
to
see
so
many
new
folks,
it's
so
exciting.
Docs
is
often
a
way
that
a
lot
of
people
get
started
with
kubernetes,
so
we're
a
big
fan
of
having
folks
that
are
new,
contributing
this
way
and
finding
their
preferred
contributing
path,
either
through
Dark
Soul
in
other
different
special
interest
groups
throughout
the
project.
A
So
that's
great
to
have
you
all
welcome
we're
going
to
move
on
to
the
next
point
of
our
agenda
now,
for
those
who
are
new,
we
in
Stick
docks
have
a
an
initiative
that
we
call
PR
wrangling
and
what
that
is
is
that
every
week,
one
of
the
approvers
that
we
have
a
list
of
approvers
for
Sig
docs,
one
of
us
is
kind
of
tasked
with
the
week
of
trying
to
move
PR's
and
contributions
that
are
coming
in
through
the
pipeline,
so
we
can
get
them
kind
of
either
reviewed
or
merged,
or
possibly
you
know
requesting
changes
as
quickly
as
possible
so
that
we
can
kind
of
move
through
and
get
those
contact
contribution
work
going.
A
Given
that
we're
a
big
project,
we
get
a
lot
of
contributions,
so
we
want
to
make
sure
we're
doing
that,
and
this
week's
PR
Wrangler
is
me
me,
I'm
the
one
who's
who's
jumping
on
this
week,
I've
done
a
bit
of
work
over
the
weekend.
I'll
continue
throughout
the
week,
and
next
week's
Wrangler
I
believe
is
Taylor
dozal.
A
One
of
our
tech
leads,
who
is
also
working
for
the
cncf,
but
a
big
reminder
to
the
other,
approvers
and
Wranglers
on
the
call
here
to
check
your
check,
your
wrangling
shifts
and
we'll
also
keep
reminders
in
the
seek
docs
Channel
and
in
meetings
so
yeah.
If
folks
need
anything
on
the
wrangling
side
feel
free
to
ping
me
in
the
docs.
Channel
I'll,
hopefully
be
able
to
be
online
a
couple
of
different
times
this
week
to
help
with
the
wrangling
alrighty.
A
Now
we're
going
to
the
next
part
of
our
agenda
and
that's
looking
at
the
next.
This
next
release
we're
at
release
one
two:
six
we're
looking
at
the
current
status,
we're
taken
from
the
release
team
notes
thanks
so
much
Ray
current
release
is
green.
Have
we
got
anyone
from
the
release
team
that
is
wants
to
speak
to
an
update
here.
C
F
I
just
wanted
to
say
hello,
Carol
I
was
a
former
dark
Fleet.
So
if
you've
got
any
questions,
if
you
need
any
help
I'm
around
and
happy
to
to
help
out,
also
I'd
love
to
pick
your
brain
on
what
your
thoughts
are
on
the
new
project
board
I'm
very
excited
to
move
away
from
the
the
old
sheet,
so
I'm
curious
to
see
how
it's
going
to
work
out.
C
Yeah
I
think
I
did
a
fair
Arrangement
that
it
was
great
the
new
fields
that
we
will
be
similar
to
the
spreadsheet.
Ray
Legend
help
me
with
this,
and
it
looks
it
looks
nice
like
it's
similar
to
the
spreadsheet.
We
already
put
our
name
that
it
will
be
our
team
Richard
cat,
everyone
that
belongs
to
the
docs
teams,
yeah
I
I
think
I
only
have
some
doubts
about
the
statistics.
C
How
will
be
generated
but
I
think
this
is
some
will
be
fixed
with
some
features
about
GitHub
that
we
have
some
graphics
to
create
this,
but
yeah.
A
So
as
a
note
to
folks
in
the
agenda,
we
do
have
just
the
key
release,
dates,
they're
listed
October,
60
enhancement,
freeze
and
then
the
first
of
November
being
the
feature
blog
freeze
as
well,
which
is
something
that
we'll
also
be
caring
a
lot
about
in
terms
of
a
lot
of
the
work
happening
out
of
the
release
for
docs.
So
thanks
so
much
Carol
if
you've
got
any
other
questions
around
release.
A
Obviously
Carol
and
the
shadow
team
are
happy
to
answer
them
feel
free
to
order
also
add
them
at
the
end
of
the
agenda.
If
you
wanted
to
bring
them
up
later
on
all
right.
Moving
to
the
next
part
of
our
agenda,
I've
got
no
no
one's
put
down
any
issues
or
PR's
to
kind
of
look
through,
which
is
not
a
bad
sign,
which
is
completely
fine,
but
I
do
want
to
quickly
open
up
if
there
is
an
issue
or
PR
that
folks
want
to
get
us
get
our
attention
on.
A
Going
once
twice:
oh
that
I
think
that's
a
no.
So
that's
great
good
news
for
me,
the
Wrangler!
So
that's
it
means
I
can
get
on
with
the
job,
which
is
awesome,
but
we
do
have
a
couple
of
things
now
in
our
discussion
area
that
I
wanted
to
get
to
for
this
edition
of
our
cdocs
meeting
and
the
first
one
is
actually
around
wrangling.
A
I
realized
that
we
still
have
Victor
on
the
Wrangler
list
for
the
week
of
October
16.,
but
Victor
is
no
longer
a
PR
Wrangler
and
he's
actually
been
taken
off
the
approval
list
by
request
from
him
as
he's
a
bit
I'm,
not
so
active
and
so
I
wanted
to
see.
If
there
was
any
folks
here.
A
If
not
that's
fine
any
approvals
here
that
wanted
to
put
their
hand
up
for
October
16,
otherwise
I
will
look
for
a
new
Wrangler
in
the
in
the
channel,
but
just
in
case.
Anyone
here
wanted
to
put.
A
16Th
great
thanks
so
much
Ray,
Richard
I,
see
you've
got
your
hand
up.
I
wanted
to
mention
that,
unfortunately,
PR
wrangling
is
only
for
approvers,
so
you
do
need
approver
access
and
credentials
in
order
to
Wrangle.
But
if
you're
interested
in
continuing
to
shadow
on
the
wrangling
process,
you
absolutely
can.
D
Recording
yeah
thanks.
A
Awesome
no
worries
at
all.
We
do
try
and
make
sure
that
we
are
progressing
Folks
up
the
reviewer
and
approval
ladder
here
in
sigdots.
We
always
need
the
help
and-
and
that's
something
that
hopefully
we'll
have
some
more
information
on
in
the
in
the
weeks
to
come
in
a
couple
of
mentorship
programs
that
we're
hopefully
Brewing
in
in
the
background
there,
but
we'll
be
able
to
give
some
more
information
on
that
soon.
A
So
thanks
Ray,
thanks
for
putting
that
in
I,
can
add
the
edits
to
that
later
on
after
the
meeting
to
the
to
the
schedule.
Thank
you
all
right,
jumping
into
the
next
agenda
topic.
A
I've,
put
this
as
myself
and
Abby
and
I
see
Abby
you're
on
the
call,
but
I
just
wanted
to
kind
of
call
out
for
the
community
here
that
we've
had
Brad
who's
been
a
huge
force
in
the
localization
work
for
Sig
docs
he's
stepping
down
as
an
active
lead
for
the
localization
sub
project,
which
does
leave
localization
in
the
very
capable
hands
of
Abby
and
I.
Just
wanted
to
see.
A
If
Abby,
you
wanted
to
say
anything
to
that,
so
that
we
can
possibly
let
the
rest
of
the
community
know
how
they
can
support
you.
H
Yeah,
so
that's
an
excellent
question,
so
Brad
has
been
very
long
time
contributor
in
the
sigdox
community
and
he
started
off
the
localization
sub
working
group
as
it
was
originally
originally
called,
and
we
are
now
an
official
sub-project
within
within
the
project.
So
we
have
a
long,
long-standing
longevity
within
within
our
group
and
so
going
forward.
I
think
you
know,
I
I
definitely
would
love
to
continue
working
within
the
group,
but
we
are.
H
We
will
be
looking
for
folks
to
help
lead
our
sub-project,
so
it's
not
just
one
person,
because
obviously
one
person
can
get
sick
or
go
away
or
whatever.
So
we
definitely
need
some
people
to
help
with
that.
So,
if
you're
interested,
let
me
know
we
our
ASAP
project,
we
have
our
own
channel.
H
So
if
you
are
new
I
know
we
have
a
lot
of
new
folks
on
the
call
we
have
our
own
Sig,
docs,
Sig,
hyphen,
docs,
hyphen,
localization
I,
believe
is
our
slack
Channel
I
can
put
it
in
the
chat
in
a
minute
if
people
wanted
to
join
or
if
you're
interested
or,
if
you're
a
contributor
who
is
interested
in
in
helping
our
localization
teams.
H
If
you
know
languages
that
we
have
our
docs
translated
into,
would
we
love
to
do
that
I've
rambled
on
along
enough
about
this
topic,
but
yeah?
So
thank
you
Natalie
for
bringing
this
up
I'm,
not
sure
if
Brad
has
he's
not
on
the
call
but
I'm
not
sure
if
he's
posted
anything
in
the
channels,
but
I'm
sure
that
he
will
be
doing
that
soon.
A
Yeah,
that's
it
yeah
huge,
huge
kudos
to
you
Abby
for
a
lot
of
the
work
that
you've
been
doing
alongside
Brad
and
also
with
the
continuation
of
the
localization
work.
That
you'll
be
doing.
It's
really
great
I
think,
but
we
chatted
like
very
very
briefly,
but
likely
very
much
in
the
New
Year
we'd
want
to
probably
cement
a
couple
of
new
folks
to
help
out.
A
So,
as
you
mentioned,
there's
no
bus
factor
in
in
in
helping
out
with
different
issues
and
things
for
folks
who
don't
know
what
the
localization
sub
project
is.
A
It's
the
specific
kind
of
leadership
of
all
the
different
other
languages
that
the
kubernetes
kubernetes
docs
are
available
in
other
than
English,
and
we've
got
a
great
bunch
of
maintainers
of
all
the
different
languages
who
get
a
lot
of
support
from
Abby
and
and
Brad
and
in
in
in
helping
out
with
a
lot
of
the
processes
needed
that
that
help
with
the
with
a
lot
of
the
decision
making.
A
There
there's
also
a
monthly
community
meeting
that
takes
place
as
well,
and
that's
something
that
I
I,
assume
Abby
localization
leads
would
probably
have
a
chance
in
hosting
and
meeting
the
localization
folks
that
are
involved
so
yeah,
as
Abby
said,
reach
out
to
Abby,
if
you're,
if
you're
interested
but
we'll
likely
square
that
away
in
the
New
Year.
A
Given
that
we're
getting
close
to
a
big
chunk
of
release,
work
and
then
holiday
season,
so
yeah
New
Year
is
probably
a
good
time
to
Target
a
lot
of
that
change.
A
Great
thanks
so
much
moving
on
to
the
next
agenda
topic
and
we've
got
Ray
specifically
around
the
doc
Sprint.
Let's
I'd
love
to
hand
it
over
to
you
and
I
can
take
over
with
notes.
Yeah.
G
Hey
folks,
so
the
kubernetes
contributor
Summit
will
be
will
be
taking
place
on
Monday
of
kubecon
week,
which
is
October
24th
Abby
Divya
Natalie
myself
will
be
on
site.
We
have
carved
out
a
room
and
time
for
Doc
Spritz.
Currently
the
time
sets
starting
at
11,
there's
currently
ending
at
five,
but
it's
probably
gonna
end
before
five,
since
there
are
some
things.
G
Other
parts
of
the
contributor
Summit
that's
going
to
take
place
as
well
I'm,
just
trying
to
gather
topics
on
what
folks
would
like
to
do
during
a
doc
Sprint.
G
So
we
we
started
a
few
from
from
last
week's
meeting,
there's
also
a
few
from
from
Abby
in
here,
as
well,
also
from
Tim
as
well
just
kind
of
go
and
run
just
just
reviewing
these
so
pages
are
alpha
sorted
in
English
for
the
English
site,
but
this
does
not
work
out
for
localization,
so
we
want
to.
We
have
requested
for
new
pages
to
have
page
weights
to
the
English
site.
G
So
one
of
the
doc
Sprint
efforts
could
be
adding
page
weights
to
the
entire
English
site
so
which
will
help
out
all
localization
efforts
afterwards,
and
another
topic
is
that
we've
we
like
to
have
a
title
case
in
in
terms
of
the
the
top
header
which
is
placed
in
the
front
matter,
but
not
all
pages
abide
to
this,
so
one
efforts
for
the
doc
Sprint
could
be
having
making
sure
all
the
pages
are
are
using
title
case
for
the
top
page
header.
G
Other
topics
is
like
bug:
issue
bash
as
well
as
or
if
there's
any
rough
spots
in
the
docs
to
to
smooth
those
over
cleaning
up
some
mermaid
diagrams
as
well
is
one
one
topic
and
just
a
general
repo
cleanup
is
another
topic
as
well,
so
those
are
some
options
but
feel
free
to
ping.
Me
ping,
the
sick,
docs
slack
Channel
as
well.
G
If
you
have
any
suggestions
or
if
you're
going
to
be
at
the
summit
as
well,
let
me
get
the
where
you
would
where
you
could
sign
up
this.
If
you
go
to
kubernetes
Dev,
slash
events,
let
me
get
the
link
I,
think
22
contributor,
Summit,
North,
America
I'm,
putting
it
in
the
put
it
in
the
zoom
chat
and
also
in
the
Sig
docs
meeting
agenda
as
well.
So
you
go
to
kubernets.dev
events,
2022
and
just
click
on
the
North
America
for
kubernetes
controvers,
Summit
Center.
There's
a
registration
link
there.
G
So
all
right
just
pause
for
any
questions
or
comments.
Innate.
F
G
Yes,
you
do
need
to
sign
up,
and
also
for
folks,
we'll
probably
see
that
there
was
a
social
in
the
evening
time.
You
actually
have
to
sign
up
for
the
for
the
contributor
Summit
to
even
to
also
attend
the
social
as
well.
So.
A
I
also
want
thanks
thanks,
so
much
for
that
breakdown.
Right
I
also
want
to
mention
for
folks
in
case
you
weren't
aware,
but
the
contributor
Summit
is
unfortunately
not
virtual.
It's
only
on
site
and
in
person,
even
though
kubecon
and
Clarity
of
con
does
offer
a
virtual
option.
Unfortunately,
the
contributor
Summit
isn't
I
would
love
for
us
to
one
day.
Do
this
I,
don't
believe
we
have
the
technology
just
yet
so
so
yeah.
A
So
I
wanted
to
note
that
if
you
are
on
site
in
kubecon
in
in
Detroit,
then
coming
for
the
Monday
for
the
contributor
Summit,
that
would
be
great
another
condition
of
signing
up
for
the
contribute
Summit
most
for
most
of
the
time.
I
believe
there
are
a
couple
of
exceptions,
but
you
should
be
an
org
member.
That's
another
piece
of
the
puzzle
there
getting
org
membership
is
easy
in
the
sense
of
if
you've
got
five
contributions,
and
you
find
a
couple
of
sponsors
that
are
willing
to
say.
A
Hey
here
are
some
contributions
I've
made
and
we're
really
proud
of.
You.
We've
done
that
recently
in
seek
docs.
So,
if
you're
doing
a
lot
of
docs
contributions
and
want
to
be
an
org
member,
a
lot
of
the
folks
can
help
you
out
post
your
information
in
the
seek
docs
channel
in
order
to
get
that
happening
thanks
again,
so
much
Ray
I
think
I've
got
another
idea
for
the
possible
dog
spread.
I
do
remember.
I
do
remember
we
were
chatting
about
as
part
of
PR
wrangling.
A
G
Yeah
I,
actually
like
the
idea
and
also
to
jump
on
that
as
well.
Kubernetes
as
a
whole
is
actually
parts
of
github's
and
get
the
information
right
before
I
I
state
state.
This
thing
correctly
so
we
are
on.
We
are
doing
parts
of
tests
for,
let
me
see
here
so
it's
an
alpha.
It's
a
new
functionality
in
GitHub.
G
It's
called
markdown
task
list,
so
this
is,
we
could
possibly
incorporate
this,
so
this
is
to
have
epic
issues
and
we
could
have
multiple
tasks
or
multiple
issues
kind
of
nested
within
parent
issues,
but
it
also
populates
into
GitHub
projects.
So
one
of
my
long-term
goals-
and
we
have
a
project
board
for
this-
is
long-term
issues
for
for
Sig
Docs.
G
G
You
know
paste
that
and
there's
also
a
some
docs
on
it
as
well.
So
that's
just
some
that
email
went
out
to
the
dev
mailing
view
or
on
the
Deb
mailing
list.
You
I
should
have
already
received
that
notification.
A
Great
awesome
yeah
that
could
be
also
something
we'd,
possibly
look
at
at
the
Sprint
I
do
want
to
get
involved
and
and
kind
of
organize
that
and
that
the
epics
in
a
way
that
could
be
better
manageable.
That's
a
great
idea,
too,
for
sure
all
right
if
anyone
else
has
any
other
possible
ideas
for
what
we
could
tackle
at
the
doc
Sprint
now
is
your
chance
to
speak
up
foreign.
I
And
also
a
suggestion,
I
I
don't
see
a
lot
of
ways
of
gathering.
You
know
problems.
People
are
having
for
the
docs
is
some
of
that
information
gathered
somewhere
like
oh
wow,
nobody
understands
so
and
so
in
the
docs
things
that
could
be
opportunities
for
larger
writing
opportunities,
because,
right
now
we
tend
to
kind
of
pick
at
things.
You
know
we
we
fix
things
up
and
and
doing
small
change
over
time
can
be
really
great,
but
also
sometimes
you
just
need
to
like
rewrite
things.
G
That
way,
we
can
yeah
it's
in
that
GitHub
projects
board.
It's.
Let
me
try
to
get
the
link
here.
So
I've
created
a
project
board
for
this
a
while
ago,
but
haven't
maintained
it
because
there's
no
Automation
in
it
yet
and
I
believe
since
well.
I
also
did
it
when
github's
project
board
was
actually
in
beta,
so
some
of
the
functionality
wasn't
quite
quite
there.
Yet
I'll
try
to
get
the
link
here,
while.
A
You're
getting
that
link
Ray,
you
make
a
really
good
point
Chris
by
the
way.
Where
is
that
a
lot
of
our
work
in
docs
is
very
reactive
rather
than
proactive
in
terms
of
us
like
actually
going
out
to
users
and
like
looking
for
feedback
and
and
I,
think
that
there's
a
lot
of
Goodwill
in
wanting
to
do
that,
but
maybe
just
not
as
much
capacity
in
terms
of
the
amount
of
work
and
contributions
and
peers
that
are
coming
in
versus
being
able
to
kind
of
do
proactive
work.
A
So
the
doc
Sprint
is
actually.
You
know
another
good
opportunity
to
try
and
do
that.
But
unfortunately,
the
the
downside
and
trade-off
to
this
is
that
it
is
very
restrictive
in
that
it's
for
in-person
collaboration.
Only
and
I
really
do
think
that
something
like
this
could
actually
be
a
hugely
beneficial
exercise,
asynchronously
and
being
able
to
open
it
up
larger
to
the
broader
Community.
But
it's
a
very
good
point
and
I,
don't
think,
there's
a
very
easy
answer
for
the
proactive
reach.
I.
I
Think
I
was
going
to
say
having
people
together,
you
know
physically
can
sometimes
just
be
a
good
way
to
just
talk
through
the
brainstorm
and
go
hey.
You
know
what
are
the?
What
are
the
real
problems,
we're
having?
What
are
the
things
that
we
could
and
then
maybe
how
to
address
them?
You
know
what
so,
how
should
something
be
Rewritten
and
maybe
who
can
take
them
on
and
then
we
can
go
to
a
virtual
meeting
after
that?
You
know.
A
For
sure,
because
a
lot
of
those
questions
are
like,
how
can
we
tackle
it?
Those
ideas
come
up
and
then
we
need
to
go
back
to
specifically
our
localization
Community.
To
then
ask
is
this
possible
going
down
to
the
the
different
localized
versions
too,
because
a
lot
of
that
time,
big
changes
like
that
can
actually
be
be
very
hard
to
to
be
able
to.
Then
you
know
take
in
on
the
on
the
localization
side
too.
So
it's
but
I
yeah,
a
huge
plus
one
to
what
you
said.
A
Chris
I,
think,
starting
that
conversation
in
in
in
some
place,
some
form
and
sometimes
in
person
helps
can
is,
is
the
way
is
the
way
that
we
can
kind
of
Kick
this
off
cool
thanks.
G
All
right
so
I've
posted
the
link
both
on
the
zoom
chats
and
also
on
the
Google
Docs
meeting
agenda
as
well.
So
this
is
a
project
board
for
long-term
report
issues
that
has
pretty
much
big,
big
updates
or
paired
issues
like
updating
damage
and
docs
and
updating
storage
stocks.
That's,
unfortunately,
you
have
to
do
link
through
and
it's
a
little
deeper
into
like
into
the
more
of
the
granular
details
on.
G
What's
on
what
the
issues
are
like
the
update,
Secrets
documentation
like
I,
know,
Shannon
was
published
or
it
has
a
has
a
PR
to
update
the
secrets
and
I
know
Tim.
Has
a
house
has
a
PR
on
up
to
update
another
about
another
kubernetes
resource
or
in
multiple
pages?
G
So
so
this
is
kind
of
what's
like
Chris
mentioned,
that's
I
think
it's
good
to
have
us,
and
so
we
have
I
guess
bigger
goals
instead
of
being
reactive,
so
we
could
make
a
more
cons,
more
I,
guess
clear
documentation,
changes
with
with
the
goal
in
mind.
A
Definitely
thanks
for
thanks
for
that,
I,
yeah,
completely
agree
and
I.
Think
Chris
I'll
there's
a
bunch
of
us
on
the
on
the
ground
in
in
in
in
Detroit,
who
will
be
at
the
contributor
Summit.
That
I
will
probably
definitely
want
to
touch
on
this
and
then
report
back
into
docs,
either
via
both
by
the
community
meeting
and
asynchronously.
A
So
we
can
get
a
lot
more
of
the
the
community
involved,
because
I
think
this
is
something
that
needs
a
lot
more
of
our
contributor
base
at
a
very
Global
to
actually
be
involved
in
a
lot
of
the
discussion
and
kind
of
Road
mapping
there
for
sure.
I
A
Great
great
reminder,
then,
to
sign
up
for
the
summit
for
sure
signing
up
is
not
only
important
for
capacity,
but
I
believe
there
is
swag
to
entice
you
even
more.
So
if
you
want
to
sign
up
for
that
all
right
folks,
we
have
reached
the
end
of
our
agenda.
That's
that's
of
folks
of
of
the
submitted
things
for
our
agenda.
I
want
to
quickly
open
it
up
to
see
if
anyone
else
has
any
other
topics
or
issues
that
they'd
like
to
bring
up
and
Nate
I
can
see
your
hand.
F
Just
a
quick
revisit
of
our
issues,
there
is
one
that
needs
a
it's.
A
blog
entry
review,
I
just
wanted
to
bring
it
up
for
awareness.
F
Did
yeah
yeah,
perfect,
okay,
great
yeah,
it's
a
it's
a
blog
entry
about
explaining
the
usage
of
the
Pod
OS
field,
so
I
I!
Guess.
Actually
it's
more
of
a
note
for
you
not
only
if
you're
wrangling
this
week,
but
this
one
could
probably
use
some.
A
H
Hello,
well,
you
were
mentioning
how,
before
you
mentioned
about
being
proactive
about
getting
feedback
from
users,
you
reminded
me
of
a
question
that
I
just
never
actually
asked,
and
do
we
get
like
a
report
or
any
type
of
monitoring
on
the
bottom
of
the
page
of
all
of
our
Pages.
Have
you
know
feedback
welcome
and
it's
a
yes
or
no
button
like
was
this
page
helpful?
Does
anyone
use
that
button?
Does
anyone
get
the
feedback
from
that
button?.
A
A
We
recently
had
some
access
issues
to
the
analytics
in
the
first
place,
for
a
couple
of
us
leads
that
we
I
think
are
still
either
have
recently
just
been
addressed
or
are
still
trying
to
be,
and
I
will
openly
meet
that
I,
unfortunately,
upon
receiving
access
have
yet
to
dive
in,
but,
unfortunately,
I
only
got
access
very
recently
in
the
last
few
weeks
and
I
believe
Ray
was
in
a
similar
in
a
similar
spot
there.
A
So
it's
something
that,
as
leads,
we
need
to
look
into
because
it
was
a
kind
of
a
a
dropped
ball
and
then
with
our
with
us
coming
in
as
leads,
we
realize.
Oh,
we
don't
have
this
and
we
need
access
to
be
able
to,
like
you
said,
look
into
things
like.
Was
this
helpful,
yes
or
no
and
possibly
use
that
as
a
basis
for
starting
conversations
of
this
page
doesn't
get
a
lot
of
great
feedback?
Why
is
that?
And
and
so
on,.
H
Okay,
thank
you,
I
will
I
will
I
will
try
to
check
around
and
see
if
I
can
get
that
or
something,
because
I
know
that
I
have
access
and
I
have
poked
around
with
a
lot
of
the
analytics
before
so
I'll
see.
If
I
can
figure
out
something
where
that
data
is
being
reported
and
I
bring
that
back
so.
A
Great
in
the
meantime,
I
think
we
can
also
ask
Jim.
He
was
the
analytics
access
extraordinaire
for
us
that
we
can
ask
and
see.
If
he's
knows
exactly
where
that
information
can
be
found
for
sure.
A
Alrighty
with
that
being
the
case,
I'm
sure
many
of
you
have
probably
heard
my
cat
yelling
in
the
background
he
wants
to
be
fed.
So
it's
a
great
time
to
end
the
meeting
I
want
to
say
a
big
thanks
to
everyone
for
attending
for
folks
who
are
watching
this
afterwards
in
the
in
the
recording
we've
taken
notes
now,
Jenna
thanks
Ray
again
for
note-taking,
just
want
to
note
that
this
was
great
and
next
time
you
host
Ray
I
will
take
notes
and
we
can
we
can.
A
We
can
do
this
tag
team,
it's
a
great
system
for
for
anyone
else,
who's
got
questions
or
anything
that
comes
up
after
the
meeting
our
slack
channel.
A
Is
there
see
Dash
docs
in
the
kubernetes
Community
we're
always
around
and
willing
to
help,
and
next
week
we'll
be
having
a
slack
online
online
meeting
where
we'll
have
threads
there
for
any
other
issues
and
things
coming
up
and
so
in
the
meantime,
I
hope
you
all
are
looking
after
yourselves
and
that
you're
in
good
health
and
we'll
see
you
for
the
next
community
meeting
in
a
couple
weeks.