►
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).
B
A
All
right,
so
this
is
the
quarterly
meeting
we
had
a
little
bit
of
a
delay
going
in
between
the
q4
with
the
holidays,
slowing
down
and
q1
everything
going
on
then
so
normally.
What
would
happen
is
this
meeting
would
be
a
review
of
the
q4
objectives
and
talking
about
what
we're
going
to
do
in
q1,
considering
that
we
are
quite
a
ways
into
q1,
we've
kind
of
lumped
them
all
together
here.
A
At
this
point-
and
one
thing
I
did
add
to
the
to
the
planning
dock-
that
I'm
sharing
here-
is
the
quarter
breakout,
so
you
can
see
what
we
differentiate
each
quarter.
So
you
know,
october,
to
december
being
what
we're
reviewing
today
january
to
march
being
the
first
quarter
and
us
going
into
march,
not
having
a
ton
of
time
left
in
the
first
quarter,
we're
gonna
target
on
what's
going
on
for
the
second
quarter,
so
I'm
going
to
move
these
pieces
down
for
discussion
later.
A
A
Let
me
see
here:
membership
updates,
there's
no
major
changes,
so
everything's
kind
of
chugging
along
here,
moving
on
to
the
q4
review,
so
for
the
wins
we
had
the
new
reference
stocks,
the
case.io
finally
got
published
and
merged.
So
that's
awesome,
that's
a
huge
win!
So
for
those
who
don't
know
kate's
reference,
docs,
there's
a
website
called,
I
think
it's
kate,
it's
ref
dot,
io
or
k
ktsref.com.
A
I
forget
the
exact
url,
but
it
was
a
pragmatic
way
to
reference.
The
api
and
google
summer
of
code
or
google
season
of
docs
sorry
had
a
individual
philippe
martin,
create
the
reference
docs
and
basically
take
what
that
website
had
and
pull
it
into
the
kubernetes
documentation
to
have
a
more
of
a
holistic
view
on
that
and
a
more
of
a
better
developer
experience.
You
know
to
be
to
be
honest
with
everyone
here:
dot
pr
wrangler
program
continues
to
ensure
timely
response
to
submitted
prs.
A
A
A
And
then
also
sig
doc's
localization
subgroup
continues
to
drive
common
best
practices
and
tooling
across
localization
teams,
and
that's
a
huge
win
too,
because
for
those
that
don't
know,
there's
many
different
localizations
within
sig
docs
and
a
lot
of
them
have
their
own
methodology
for
working
and
that
sub
group
is
aiming
to
bring
everyone
under
the
same
understanding
using
the
same
tools.
It's
a
great
effort
led
by
fred,
topple
and
irva.
C
A
We
did
there's
still
some
ongoing
work
there
and
I'll
I've
actually
pulled
that
in
from
the
queue
ford.
Let
me
let
me
back
up
so
the
q4
planning
meeting.
We
talked
about
pulling
that
into
our
weekly
meeting
and
talking
about
the
status
of
that
there's.
Some
lingering
third
party
content
still
out
there
and
what
I've
done
is
I've
updated
the
agenda
for
the
next
weekly
meeting
to
start
carrying
that
over,
but
that
is
a
big
win,
though.
A
All
right
so
moving
on,
usually
in
some
of
these
quarterly
plannings,
we'll
talk
about
some
of
the
stats
about.
You
know
how
many
millions
of
views
or
what
the
current
statuses
of
the
ducks
in
that
quarterly
time
frame
that
we're
currently
reviewing-
and
I
thought
it'd
be
interesting
to
take
a
look
comparatively
between
the
different
quarters
and
some
of
the
trends
there.
A
A
Who
knows
why
you
would
lose
a
hundred
thousand?
You
know
clicks
or
views.
I
don't
think
that
that's
really
that
impactful
also
you
have
in
q4
the
holidays
coming
into
play
too.
So
I
would
imagine
a
lot
of
folks
took
time
off,
but
when
I
saw
that
I
I'm
used
to
seeing
exponential
growth
in
the
kubernetes
docs
quarter
after
quarter,
even
if
it
is
going
into
the
holidays,
it
seems
like
that
page
view
number
always
is
going
up.
A
So
I
was
curious
to
look
at
what
the
quarterly
or
q4
stats
were
for
2019,
and
so,
when
I
pulled
those
page
views
were
at
18
million
200
000.
So
I
think
that's
pretty
pretty
impressive
that
that
trajectory
looking
at
a
q4,
you
know
quarter
two
quarter,
quite
a
significant
jump
there.
You
know,
looking
at
roughly
seven
million
page
views
increased
over
the
year
at
the
same
time
frame
from
2019
so
anyways.
I
thought
that
was
worthwhile
or
worth
exploring
and
putting
that
into
more
of
a
frame
of
reference.
A
B
We've
we
made
a
change
and
I
don't
remember
exactly
when,
and
it
was
on
the
tools
page
and
rather
than
telling
people
how
to
install
tools.
We
said
if
you
want
to
install
kind
or
mini
cube
or
these
other
tools.
There
is
a
page
we're
not
going
to
document
that
like
there's
this
other
page,
so
maybe
people
are
bookmarking.
Those
and
maybe
search
engines
are
telling
them
to
go.
There.
A
D
A
Yeah,
so
we
used
to
send
out
a
monthly
report.
It
was
deemed
somewhat
spammy
quote:
unquote,
those
aren't
my
words,
those
are
someone
else's
and
ultimately,
what
was
decided
is
to
stop
the
report
and
run
it
on
demand.
Now
I
believe
anyone
can
get
access
to
our
analytics
with
the
read
only
view
the
challenge.
A
I
did
start
an
initiative
to
create
a
separate,
smaller
mailing
list
to
the
localization
leads
which
I
haven't
created
yet,
but
the
plan
was
to
send
every
six
months
one
of
these
reports
that
just
covers
the
various
localizations
to
that
mailing
list
group.
So
a
little
less
noise
a
little
bit
more
of
a
targeted
audience,
and
it's
on
me
to
to
get
that
set
up
so
hopefully
soon,
but
not
today.
A
A
Yeah
definitely
one
of
the
challenges
I
face
at
least
with
google
analytics
and
and
someone
please.
Let
me
know
if
I'm
wrong,
because
I'd
love
to
be
wrong
here,
it
seemed
like
when
you
build
a
dashboard
out.
You
can
only
email
out
one
dashboard
to
a
group,
so
you
can
email
like
many
different
dashboards,
but
they're
all
going
to
come
in
separate
emails,
there's
not
a
way
to
create
multiple
views
and
have
like
a
bunch
of
attached
pdfs
to
a
single
email.
A
If
folks
in
the
call
know
otherwise
or
folks.
Listening
to
this,
you
know
recording
upon
review.
Let
me
know
reach
out
to
me
if
there's
a
better
way
to
do
it,
but
what
I
plan
on
doing
right
now
is
just
having
kind
of
a
spammy
noise
go
to
the
more
of
the
targeted
audience
and
then
allowing
them
to
filter
it
with
you
know,
google
filters
or
outlook
filters,
you
name
it.
A
You
know-
and
I
feel
like
I'm
speaking
for
myself,
but
I
feel
like
I've
gotten
very
normalized
to
the
the
coven
normal
and
I've
joked
with
folks
when
texas
had
the
bad
ice
storm-
and
I
was
recovering
from
that-
I
was
like
well
we're
not
going
back
to
normal
we're
going
back
to
covent
normal,
but
that's
better
than
covet
pandemic
ice
storm
normal,
and
so
with
saying
that
I
feel
like
we've
all
or
I
shouldn't
say
we
all.
At
least
myself
have
started
to
normalize
that,
but
what's
going
on
right
now
is
not
normal.
A
And
the
other
challenge,
too,
is
a
contributor,
onboarding
and
succession.
So
once
again,
this
is
one
that's
kind
of
lingered
with
us
and
I
think
the
global
pandemic
probably
probably
makes
it
a
little
probably
makes
it
a
little
worse
as
well,
but
engaging
with
folks
and
building
that
mentorship
mentee
relationship
advancing
through
the
contributor
ladder.
There's
definitely
efforts
there,
but
they're
not
as
clear
as
they
could
be
and
they're,
not
as
I
want
to
say
as
formal
as
they
could
be,
but
I
feel
like
that's
the
wrong
word.
B
What
I'm
going
to
say
is
that,
if
anyone's
on
this
call
right
now
or
they're
watching
this
on
on
catch
up,
then
find
the
sig
docs
channel
on
on
on
kubernetes
slack
and
just
nudge
and
say
I'd
like
to
to
learn
about
this,
and
even
if
we
haven't
got
a
great
process
in
place,
we
have
people.
I
will
help
other
people
will
help.
So
that's
what
I
recommend.
F
I
was
just
going
to
ask
that
question
because
I
I
contributed
to
to
sig
docs
to
kubernetes
documentation
like
several
years
ago,
very
small
contributions.
I
would
really
like
to
get
back
into
it.
In
fact,
my
employer
amazon
web
services
wants
me
to
spend
most
of
my
time
contributing
to
upstream
docs,
so
I
would
love
to
be
giving
whatever
the
clearest
runway
is
to
to
get
started
with
that
awesome
and
chris,
I
don't
believe,
we've
met.
Is
this
your
first
time
attending
I
attended
about?
F
A
Cool
well
welcome
we're
happy
to
have
you
it's
a
little
bit
of
a
non-formal
introduction
joining
at
the
quarterly
meeting
to
get
up
to
speed.
However
you're
in
the
right
spot,
you
have
tons
of
folks
here
willing
to
help
out.
I
think
you
can
recognize
some
of
the
folks
in
this
call
and
find
him
in
slack.
Reach
out,
like
tim,
was
mentioning
on
the
sig
doc
slack
channel,
which
hopefully,
someone
could
plug
the
slack
channel
link
into
the
chat.
That'd
be
helpful,
done
beautiful,
awesome,
you're.
A
The
best
place
to
to
get
in
touch
with
us
and
also,
if
you
have
any
questions
here,
this
is
all
a
friendly
group.
I
mean
feel
free
to
interrupt
interject,
ask
questions.
I
I
feel
like
we're
here
to
make
other
people
effective
impactful
and
if
there's
anything,
we
can
do
to
make
your
life
easier.
I'm.
F
A
Yeah,
so
for
the
prs
there
is
a
little
bit
of
a
guide
or
a
walkthrough
on
the
kubernetes
website
about
submitting
the
pr
there.
As
far
as
getting
reviews,
it
should
have
automatically
assigned
some
reviewers
or
signs
and
folks
who
could
review
it.
I
would
say
just
my
general
rule
of
thumb
is
give
it.
You
know
a
little
bit
of
time
for
folks
to
review
it
who
have
been
assigned
if
it's
gone
on
for
a
significant
amount
of
time
without
any
review
or
feedback.
A
B
A
G
Yeah,
so
we
had
13
blog
posts
published
in
q4,
which
is
actually
really
awesome,
especially
considering
all
of
the
holidays
happening
in
q4,
so
that
was
great.
We
had
800
and
a
little
over
809
000
unique
views,
which
was
you
know,
a
decent
growth
quarter
over
quarter
thanks
to
the
the
docker
post
that,
I
think,
had
a
lot
of
views
this
this
past
quarter.
G
G
For
anyone
that's
interested,
we
do
have
positions
open
across
the
board
and
I
guess
I
didn't
drop
in
the
link
to
the
sub
project
in
here,
but
we
have
positions
for
editorial
lead
which
kind
of
wrangles
the
blog
post
coming
in
as
well
as
technical
editors
and
then
copy
editors
as
well,
and
then
the
second
bullet
is
increasing
blog
submissions.
This
is
a
little
misleading.
We,
actually,
you
know,
we're
still
averaging
really
great
blog
submissions,
but
they
tend
to
come
in
all
in
one
chunk,
especially
around
a
release.
G
A
G
A
A
A
A
A
So
without
further
ado
I
will
move
on
to,
I
just
must
have
an
owner
to
drive
him.
Yet
no
no
goals
without
odors
is
a
rule.
I
suppose
so.
The
first
thing
is
release
121
and
that
is
all
I'd,
give
it
an
assessment
of
1.0
it's
hard
to
rate
it
anyway
other
and
as
far
as
carrying
forward.
We
don't
really
have
a
chance
there.
I
don't
know
ray
if
you
want
to
give
a
quick
update
on
121
or
a
comment.
E
Yeah
so
121
we're
it's
as
far
as
docs
is
concerned,
where
we've
changed
some
of
the
process
and
it's
going
to
be
changed
in
one
1.22
as
well.
So
so
there's
some
changes
in
how
we
contact
enhancement
owners
to
make
sure
to
create
their
placeholder
prs
and
to
to
get
that
started
and,
like
I
mentioned
it's
gonna
be
changed
in
1.22
as
well.
So
so
it's
still
good.
It's
we're
still
on
on
schedule.
E
Not
it's
not
as
I
guess
we
don't
have
as
many
dark
prs
open
as
we
did
in
120
at
this
time,
because
the
the
doc
seem
hasn't
actually
started
contacting
aspen
owners
and
that's
that's
on
purpose,
because
because
the
the
other
sub
teams,
enhancement
team,
they're,
the
ones
contacting
the
enhancement,
enhancements
owners
and
toll
code
for
you,
so
we're
still
doing
fine.
And
so
I
want
to
thank
in
advance
all
these
sig
docs
reviewers.
You
guys
are
all
awesome.
E
You
guys
review
things
very
quickly,
so
I
want
to
give
a
thumbs
up
to
all
those
reviewers
and
to
jim
as
well,
and
I'm
sure
we're
going
to
do
a
lot
of
work
on
april
8th
when
1.21
is
scheduled
to
be
released
as
well,
so
yeah,
so
everything's
going
fine,
there's
some
role.
Processes
in
that
is
currently
changing.
So
I'll
change
that
in
the
doc's
role
handbook,
but
just
as
a
warning
it'll
be
changed
in
1.22
as
well.
So.
E
A
Gotcha
gotcha
appreciate
the
update
and,
as
always,
let
us
know
if
we
can
help
out
and
as
things
come
down
the
road
and
major
changes,
we'll
we'll
roll
with
the
punches
sounds
good.
Well,
thanks
ray
and
moving
on
to
the
thoughts
on
the
web
web
performance
subgroups,
this
was
brought
up
by
taylor,
taylor
messaged
me
and
said
that
he
will
not
be
here.
I
believe
this
is
the
one
that
we
are
chatting
about,
and
taylor
mentioned
that
he
would
like
to
carry
it
forward.
A
A
I
B
So
I
I
think
in
terms
of
assessment,
it's
like
point
one
like
some
stuff
happened,
but
it
wasn't
very
formally
organized
and
there's
been
a
lot
happening
so
yeah
point
one
on
the
on
the
assessment
and
I'm
kind
of
an
undefined
on
whether
to
carry
it
forward.
I
wouldn't
want
to
be
the
person
driving
that
I
have
other
things
that
I
would
want
to
be
driving
in
ahead
of
time.
B
To
add
a
bit
of
a
narrative
on
this,
like
at
about
the
time
of
the
switch
to
doxy,
that
kind
of
highlighted
that
the
the
existing
tasks
navigation
was
really
poor
and
we
dealt
with
like
the
sore
thumbness
of
it.
And
it's
like
it's
now,
it's
not
great,
but
it
works,
and
so
the
drive
isn't
necessarily
there,
and
I
want
to
save
some
of
that
drive
for
things
that
we
are
going
to
talk
about
later.
A
A
All
right
here
in
a
whole
lot
of
nothing.
I'm
gonna
give
this
an
assessment
of
zero.
Now
with
an
assessment
of
zero.
I
do
recognize
that
there
are
folks
that
are
doing
technical
reviews
on
css
and
on
javascript,
and
there
are,
the
lights
are
still
on
and
we're
still
good
there,
but
as
far
as
a
formal
effort
in
the
goal
sense,
I
don't
think
that
makes
a
lot
of
sense
as
far
as
carrying
it
forward
thumbs
up
thumbs
down.
B
D
A
A
A
There
was
a
this
concept,
came
up
to
create
videos
and
documentation
about
how
to
effectively
contribute
to
the
kubernetes
documentation.
This
was
supposed
to
be
more
of
like
a
prepping
step
and
what
happened
traditionally
is:
let's
say
we
had
four
hours
for
a
doc
sprint.
You
would
lose
a
lot
of
time
in
the
first
half
of
that
doc:
sprint,
building
the
configurations
for
people's
systems
to
contribute
to
the
docs
signing
the
cla.
Some
of
the
complexities
of
contributing
to
sig
docs
would
take
up
a
significant
amount
of
time
in
the
sprints.
A
So
therefore
we
created
this
goal
to
create
videos
to
say
hey
before
a
doc
sprint.
We
can
send
you
a
list
of
videos,
it
will
get
you
on
the
ground
and
running
faster.
So
when
you
go
to
the
actual
doc
sprint
in
the
conference,
we're
all
talking.
The
same
language,
we
are
all
moving
forward
under
the
same
direction
and
hopefully
be
a
little
bit
more
effective.
A
A
But
what
has
happened,
though,
is
jeffrey
was
one
of
the
folks
owning
this
and
they
did
post
a.
They
did
post
out
a
link
with
a
video
that
they
made
and
you
can
check
out
the
link
here.
Looking
for
feedback,
so
here's
where
we
talk
about
the
goal
talk
about
some
of
the
pieces.
I
just
mentioned
there
if
folks
are
interested,
feel
free
to
to
review
this
content.
Take
a
look
at
it.
A
As
far
as
the
assessment
goes.
I
really
want
to
give
this
like
a
one,
because
I
feel
like
it
was
started
and
done.
I
feel
like
it's
not
getting
the
attention
or
the
love
that
it
deserves,
saying
that
I'm
also
responsible
for
not
giving
it
as
much
attention,
as
I
think
I
probably
should
have.
To
be
honest,
so
does
that
sound,
fair
folks
agree
with
the
assessment
of
one,
maybe
a
0.5,
I
could
be
be
sold
either
either
way
I
don't
think
is
jeff
on
the
call.
C
C
A
A
A
E
Sadly,
and
I
do
apologize,
I
would
give
this
assessment
as
a
zero.
Had
a
company
change
last
quarter,
but
I
do
I
still
I
actually
still
have
signed
up
for
this
eq
for
the
cks
exam
haven't
prepped
for
it,
so
I
do
plan
on
when
I
do
prep
for
it
to
see.
If
and
after
I
do
take
the
exam
to
see
if
there's
there's
corresponding
documentation
on
the
kids
websites.
I
do
know-
I
don't
know
if
this
is
tight.
E
This
might
be
for
the
year-long
goals,
but
I
know
six
security
docks
they've
worked
on
on
a
harding
guide
and
if
someone
has
has
a
draft
board
hardened
guy,
that
might
I
don't
know
if
that
is
part
going
to
be
part
of
the
cks,
but
I'll
talk
about
the
six
security
docks
and
later
on
as
well
but
anyway,
so
I
give
it
a
session
of
zero.
I
do
want
to
carry
it
forward.
Still
have
that
still
signed
up
for
this
seat.
Guess
just
haven't
taken
it
yet.
B
A
B
A
A
A
A
H
A
Awesome,
no,
I'm
I'm
happy
you're
able
to
join
sorry.
I
missed
you
earlier.
I
was
going
through
and
we
were
talking
a
little
bit
about
the
current
status
of
it.
I
said
you
did
a
great
job
getting
that
intro
video
out
and
advertising
it
and
I
feel,
like
the
feedback
has
been
lacking,
and
I
took
responsibility
myself
for
not
also
being
active
in
that
feedback
and
so.
A
Definitely,
and
with
that,
I
think
that
the
next
steps
to
really
drive
this
home
is
getting
the
proper
feedback
and
the
reviews
that
you
require
and
then
seeing
how
we
can
implement
this
next
time,
we're
in
person
at
a
cubecon
or
a
doc.
That
is,
that
a
fair
assessment
or
anything
you
want
to
add
jeffrey.
C
A
C
Oh
absolutely,
I
think
we
want
to
keep
going
with
that.
We
still
got
more
work
to
do,
there's
still
some
decisions
to
be
made
and-
and
it's
just
a
good
cadence-
to
have
to
to
keep
the
local
disease
localization
teams
talking
and
agreeing
on
things
as
things
pop
up,
so
you
can
assess
it
as
you
like,
but
I
will
certainly
be
willing
to
carry
it
forward.
A
C
I
would
give
it
like
I'll
be
hard
on
us.
I'd
say
like
a
.7,
I
think
there's
still
more
work
to
be
done,
but
but
still
getting
everybody
together
and
making
some
decisions
and
getting
the
conversations
going
for
common,
tooling
and
practices.
So
I
mean
I
I
hate
to
review
myself.
That
seems
so
uncomfortable
but
point
seven.
I
don't
know
irving.
What
do
you
feel.
D
A
Yeah
definitely-
and
I'm
wondering
this
might
be
something
that
we
move
to
the
yearly
year-long
goals
as
well
until
it
gets
to
a
status
point
where
maybe
we
feel
comfortable
either
removing
it
from
the
the
chat
or
or
you
know
doing
whatever
we
want
to
with
that.
Does
that
sound
fair
to
folks
moving
this
to
the
yearly.
J
J
J
I
didn't
join
the
spanish
team
that
that's
that's
what
that's
my
that's
my
objective
and
I'm
here
just
to
turn
out
how
you
work,
because
the
spanish,
as
as
far
as
I
know,
doesn't
have
a
meetings
monthly,
I
asked
and
they
they
say
that
they
are
available
to
do
that,
but
they
are
not
doing
that
right
now.
So
I
joined
your
meeting.
A
A
I
feel
like,
if
you
have
any
questions
about
contributing
once
again
like
we
are
telling
chris
is
the
the
slack
channel
is
going
to
be
the
number
one
source
for
asking
any
questions.
You
have
anything
that
can
be
clarified.
I
really
feel
like
there's
no
judgment
there.
We
want
folks
to
be
successful.
We
want
to
help
out
so
any
questions
you
have
in
that
slack
channel
for
sig
docs
be
incredibly
welcomed.
J
A
B
A
A
All
right,
in
that
case
we
will
we'll
continue
trudging
on
here.
I
I
made
the
joke
to
someone
I
forget
who,
where
I
said
the
last
quarterly
meeting
I
was
like
this
is
gonna,
be
relatively
informal.
It
should
be
pretty
quick
and
then
ended
up
taking
like
nearly
the
entire
three
hours,
and
so
I
didn't
want
to
say
it
this
time,
and
hopefully
I
didn't
just
jinx
us,
but
but
we're
doing
good.
As
far
as
timing
goes
here,.
A
All
right
so
moving
on
to
the
year-long
2021
goals
we
copy
and
pasted
this
piece
from
above
so
automate
major
and
minor
release
content.
So
I've
taken
ownership
on
in
this
regard
and
tim
you've
done
a
lot
of
work
as
well
doing
pocs,
for
how
some
of
these
components
could
work
together,
such
as
a
releases
page,
I
feel
like
the
assessment
should
be
a
zero.
A
What
has
made
this
challenging
or
more
challenging
than
it
ought
to
be,
in
my
opinion,
is
that
there's
a
little
bit
of
a
dichotomy
when
it
comes
to
the
ownership
of
who
makes
the
releases
page,
considering
that
sig
release
is
such
a
large
sig
and
in
charge
of
the
releases
in
charge
of
the
release?
Cadence,
while
sig
docs
is
in
charge
of
the
website,
making
sure
that
the
website
is
following
the
content
standards
that
we
have
set
making
sure
that
that
basically,
the
website
is
in
order
and
the
contributors
are
actively
leveraging.
A
A
B
A
What
does
that
release
page
look
like
and
then
combine
some
of
the
work
that
tim
and
myself
have
done
on
the
releases
page
to
bring
it
all
under
one
run:
roof
at
the
end
of
the
day.
So
waiting
on
that
example,
pr
and
really
the
only
reason
we're
waiting
on
that
pr
is.
I
want
to
have
clarity.
I
want
to
make
sure
I
understand
completely
what
sig
release
is
desiring
out
of
this,
and
I
want
to
make
sure
that
they
understand
what
sig
docs
is
desiring
out
of
this.
A
B
I
I
want
this
to
it's.
It's
it's
really
important.
Like
a
releases
pages,
you
know
it's
important.
I
don't
know
I
I
I
haven't
looked
for
splitting
this
up
to
find
a
small
task
that
I
could
do
to
move
this
forward,
but
I
think
maybe
jim
you
and
I
we
should.
We
should
spend
some
time
on
that,
so
that
we
can
empower
other
people
to
chip
in
rather
than
saying,
there's
this
massive
thing.
It
needs
to
be
done.
A
Yeah
yeah,
I
absolutely
agree,
and,
like
I
was
saying,
is
I
really
want
alignment
with
sig
release
and
with
sig
docs
and
making
sure
there's
a
joint
effort
between
the
two
sigs
and
so
potentially
pulling
stephen
in
that
conversation
would
be
helpful
and-
and,
like
I
said,
I
I
think
at
the
end
of
the
day,
sig
release
also
wants
us
very
bad.
I
don't
think
anyone's
saying
that
they
don't
want
this.
A
I
I
think
it's
more
about
making
sure
that
the
information
is
correct
and
that
the
ownership
is
correct
and
we're
not
creating
more
technical
debt.
That
is
unnecessary,
making
sure
that
everyone's
aligned.
So
I
feel
like
we're
all
on
the
same
page
there
we
just
need
work,
we
need,
we
need
things
to
move.
A
G
G
You
know
ultimate
angle,
but
I
just
created
an
issue
for
an
mvp,
that's
sort
of
a
very
much
smaller
scale
there.
I
have
the
link
in
the
doc
there
to
basically
focus
on
defining
what
cell
content
is
finding
a
way
to
automate
it
and
then
working
with
a
very
small
section
of
the
docs
so
like
maybe
like,
for
example,
like
the
security
section
of
just
the
concepts
or
just
the
tutorials,
or
something
and
then
work
on
finding
pieces
that
are
stale
and
that's
in
those
sections
and
then
working
with
sig
security.
G
This
is
an
example
sake.
I
haven't
talked
to
stick
security
at
all.
This
is
just
an
example
just
to
sort
of
get
it
going
and
we
can
sort
of
prove
out
some
of
our
concepts
so
before
we
commit
to
like
updating.
All
of
our
content
with
owners
and
like
talking
to
all
the
things
I
want
to
make
sure
that
we
one
we
have
a
good
definition
of
how
to
find
sale
content.
G
We
were
going
off
of
the
last
commit
date,
but
I
think
taylor
wrote
up
a
script
and
that
doesn't
actually
reflect
a
lot
of
content
back,
so
we
kind
of
got
to
figure
that
out.
So
I
think
we
have
that's
sort
of
what
my
idea
is
for
the
mvp
going
forward.
Like
I
said
I
have
an
issue
there,
I'm
still
free
to
take
this
on
for
the
next
quarter
or
two
so
yeah.
I
think
it's
still
worth
carrying
forward.
A
Awesome
yeah,
I
I
think
as
long
as
there's
an
ownership
for
this
or
an
owner
for
this.
That
makes
a
lot
of
sense
to
me
to
carry
this
forward.
I
think
you've
done
a
lot
of
great
work
on
this.
Just
for
context.
For
folks,
in
the
call
who
may
not
be
aware,
this
goal
was
really
set
out
to
to
I'm
trying
to
think
of
the
right
wording
here.
A
Essentially,
the
the
docs
that
are
forever
changing
and
forever
updating
and
forever
getting
new
content
are
going
to
be
as
releases
come
out,
they're
going
to
be
features
enhancements,
things
that
are
new,
usually
get
updated
in
the
docs
very
regularly.
It's
new,
it's
shiny!
It's
fancy!
It's
all
great!
What
doesn't
tend
to
happen
is
the
older
legacy
docs,
where
maybe
something
hasn't
changed
in
a
couple
years
or
maybe
is
not
necessarily
impacted
by
those
changes.
B
A
Yep
definitely
one
other
kind
of
curveball
or
aspect
to
dealing
with
the
steel
content.
Is
this
kind
of
a
scary
topic
and
it's
very
easy
to
get
to
kind
of
get
defensive
when
talking
about
removing
still
content
or
editing,
stale
content
or
pointing
the
finger
at
saying
hey,
you
have
stale
content,
you
need
to
change
this
or
here's.
You
know
unplanned
work
that
you
now
have,
and
so
really
the
one
of
the
large
parts
of
this
initiative
is
clearing
out
a
path
for
communication.
Doing
the
smaller
pocs
opening
up
the
issue.
A
All
right
moving
on
to
the
doc
sprint,
so
this
one
should
be
relatively
quick.
I
feel
like
we
talked
a
little
bit
about
this
regarding
the
pre-videos
so
previously
when
we
talked
in
q4,
this
is
just
what
always
said
was
hey.
It
was
postponed
until
conferences
returned,
I
added
in
if
we
should
attempt
a
digital
docs
sprint.
A
To
be
totally
honest.
If
I
were
to
be
on
the
other
end
of
this
seat
and
to
hear
someone
suggested
doc's
print,
I
probably
would
not
be
for
it.
I
think
it
could
be
a
good,
beneficial
opportunity,
but
to
be
totally
honest
with
the
folks
in
this
call
I'm
zoomed
out
at
the
end
of
the
day.
You
know
I
have
a
lot
of
digital
meetings,
a
lot
of
digital
interactions
and
another
one
by
choice.
Doesn't
sound
too,
too
lovely
going
back
to
my
my
new
normal
here.
G
So
I
don't
know
necessarily
about
doing
the
full
doc
sprint,
but
do
we
have
like
just
for
this,
the
kubecon
conferences?
Do
we
have
a
regular
spot
that
we
can?
I
know
last
time
we
had
a
video
series.
That
was
a
talk
that
people
attended.
Is
that
something
that's
a
smaller
scale
thing
that
we
can
take
on
while
we
can't
do
doc
sprints
or
we
may
not
want
to
do
the
doc
sprints
since
it's
a
lot
more
work
to
do
with
digitally.
A
A
What
we
had
was
when
we
had
the
in-person
kubecons.
We
would
have
the
contributor
summit
beforehand
and
we
would
leverage
the
contributor
summit
and
the
time
spent
there
in
the
room
we
had
there
for
doc
sprint.
So
I
don't
think
there's
anything
formally.
However,
there's
nothing
really
stopping
us
from
establishing
our
own
either
like
a
zoom
meeting,
or
you
know
our
own
kind
of
side,
one-off
doc,
sprint.
A
H
A
Yeah,
I
think,
there's
a
lot
of
benefit
for
folks
that
can't
attend
to
kubecon.
Now
with
covet
going
on
and
everything
being
digital.
I
feel
like
it's
a
different
story,
but
but
I
think
the
point
is
valid
as
far
as
you
would
obviously
open
it
up
to
the
entire
world
as
opposed
to
a
specific
location,
a
specific
time,
a
specific
you
know
ticket
to
enter.
I
guess
if
you
will-
and
this
could
potentially
benefit
some
folks
who
are
new
contributors.
H
C
B
A
A
Cool
yeah
good
call
out
tim
and
totally
my
bad.
That
is
not
a
goal
reviewed
as
me:
randomly
interjecting
bullets,
random
ideas
that
I
was
thinking
of,
so
it
is
definitely
a
proposal
and
then
api
reference
generation,
zach
brought
up
the
next
steps
in
clarification
and
discussion
topic
I
feel
like
this
is
carryover
from
q4,
where
the
k-8s
reference
google
season
of
docs
user
was
having
some
issues
getting
the
pr
merge.
A
B
B
The
work
I
see-
maybe
yeah-
I
put
it
like
4.75
and
six
or
nines
or
loads
of
good
work-
has
done
like
all
of
the
hard
programming
is
done
right.
All
we
have
to
do
is
the
adoption
piece
all,
but
the
adoption
piece
is
is
a
separate
shape
of
work,
and
I
think
that's
something
that
I'm
I'm
willing
to
take.
Only
that's
it's
going
to
be
important.
B
A
Cool-
and
I
I
think
I
missed
as
far
as
the
exact
challenges
or
how
to
best
phrase
that
maybe
in
like
a
one-liner
as
far
as
what
actually
needs
work
or
clarification
here,
just
for
my
own
context,
I'll
type,
something
wrong,
all
right,
totally
fair
and
if
you're
willing
to
carry
that
one
forward.
I
have
no
objections
to
anyone
feel
differently
or
want
to
join
tim
and
carrying
this
forward.
I
Yeah
sure
that's
important,
so
I
guess
yeah
I
was
going
to
say
yes
tim.
What
do
you
think?
I
think
there
needs
to
be
some
clarification
about
what
are
the
remaining
tasks
or
steps
and
there's
an
existing
pull
request.
That's
out
there,
it's
been
out
there
for
a
while,
and
I
guess
trying
to
move
that
forward.
There's
another
one.
I
think
follow-up
to
that
for
the
one-two-one
release
and
I
think
the
ray
I
think
the
the
build
of
the
documentation
it
is
documented,
but
it's
not
documented
in
the
handbook.
I
So
there's
just
a
little
bit
of
work.
I
think
to
do
with
that.
I
think
there's
another
challenge.
As
far
as
maintaining
we
said
there
will
be
some
overlap
between
the
original
reference
documentation
and
now
this
new
one,
and
so
we
need
to
kind
of
have
a
plan
as
to
when
how
we're
going
to
phase
it
out.
Maybe
I
missed
the
discussion
earlier
on.
I
don't
know,
but
yeah
so.
B
B
So
there's
a
there's,
a
there's,
a
piece
of
work
around
winning
the
hearts
and
minds
to
say
this.
This
change
is
going
to
happen.
It's
probably
a
kep,
it's
probably
a
kubernetes
enhancement
proposal,
but
before
it's
a
kep,
it's
me
making
sure
that
I
engage
with
sega
architecture
or
another
person
who's
got
this
the
same.
You
know
time
commitment
to
to
engage
with
other
six
and
and
sell
this
story.
I
Yeah,
I
guess
I'm
a
little
bit
confused
about
the
sell,
the
story
because
I
think
there
was
you
know,
there's
been
a
blog
post
about
the
new
reference
and
I
think
maybe
we
just
need
more
information
as
as
to
say,
go,
look
at
it.
You
know,
and
let's
let's
figure
out
is
this.
Is
this
the
right?
Is
it
heading
in
the
right
direction?
What
changes
are
needed
and
that
sort
of
thing?
I
think
we
need
some
more
more
comments
from
from
everybody,
but
that's
just
a
personal
opinion.
I
B
H
I
Yeah,
okay,
I
think
I
know
which
one
you're
talking
about,
but
there
I
guess
I
I
think
I
want
something-
maybe
a
little
bit
more
formal
saying
this
is
what
we
need
to
do
now,
and
this
is
the
this
is
the
target
goal,
or
these
are
the
tasks
we
need
to
take
right
now,
so
we
can
make.
You
know,
get
to
this
point
in
one
two,
one
or
one,
two,
two
or
whatever
it's
gonna
take.
So
we
can
really.
I
I
B
A
A
All
right
cool,
so
moving
on,
we
do
have
a
break
slotted
here.
I
don't
know
if
the
proposal
would
take
necessarily
45
minutes.
We've
already
covered
this.
We're
now
going
to
talk
a
little
bit
about
these
remaining
three
and
we've
kind
of
touched
on
this
a
little
bit
already.
What
are
folks,
how
are
folks
doing
are
folks,
sick
of
hearing
me
talk
or
you
need
10
minutes,
or
you
want
to
keep
rolling
forward.
B
A
J
A
A
H
A
A
A
A
F
A
That,
oh
well,
all
right,
I'm
gonna
leave
that
there
and
I'll
update
the
links,
then
a
little
bit
later
so
moving
on
karen.
You
brought
up
spending
some
time
to
explore
analytics,
and
I
was
thinking
I'm
happy
to
to
jump
into
the
analytic
board
here.
But
is
there
anything
in
particular,
you
thought
would
be
worthwhile
to
take
a
look
at.
I
I
A
A
You
know
such
as
the
trajectory
through
gubernate's
website
and
I
believe
anyone
who
requests
access
to
the
google
analytics
has
read
only
access
to
this
as
well
as
you'll,
see
kubernetes
has
the
contributor
website,
which
is
the
case.io
or
k8s.dev,
and
then
there's
a
production,
kubernetes
github,
which
a
little
bit
of
a
hack.
I
don't
believe
it's
used
anymore,
but
there
was
a
little
snippet
of
javascript
that
was
put
on
a
ton
of
web.
A
You
have
markdown
docs
and
when
that
web
hook
or
that
now
web
hook
when
that
javascript
component
executed,
it
would
actually
track
in
google
analytics.
So
you
can
see
what
github
pages
actually
had
more
views
more
clicks.
What
have
you
as
a
way
of
tracking
github?
Essentially
I
don't
believe
that
is
working
anymore.
That
was
an
old
app
engine
application
that
no
longer
is
tracking
and
then
production,
kubernetes
and
then
raw,
and
I
forget
the
difference
between
the
two
of
them.
But
production
kubernetes
is
predominantly
where
we
go
for
analytics.
A
I
A
Yeah
no
worries
at
all,
not
my
apologies
for
not
diving
into
this,
but
essentially
this
on
the
far
left
hand.
Side
is
where
folks
land,
so
whether
it's
from
a
google
search,
whether
it's
from
directly
typing
in
the
url.
Basically
your
first
landing
point
and
from
that
point
point
where
you
go
from
there.
A
A
A
A
I
would
say
that
I'm
guilty
of
doing
the
exact
same
flow
as
well,
and
you
can
also
see
here
that
eight
million
of
the
requests
going
into
seven
million
of
them
going
into
two
million
one
million,
et
cetera,
et
cetera,
they're,
the
greater
100
100
pages
on
kubernetes
websites,
there's
so
many
other
pages
folks,
land
on
and
navigate
through
that,
don't
even
top
these.
You
know
top
three
or
four
that
actually
have
a
clear
defined
pattern.
B
There
is
a
there
is
a
sort
of
action
we
could
take
on
here.
There's
there's
a
narrow
action
and
a
broader
action,
so
the
narrow
action
is
hang
on.
The
main
thing
people
want
to
do
is
they
want
to
search
the
website?
That's
like
about
an
eighth
of
the
traffic.
Is
they
do
that,
but
they
have
to
click
twice
before
they
get
to.
I
have
to
have
to
click
to
the
docs
before
they
get
to
search,
so
the
narrow
action
is
well
hang
on.
B
I
Yeah
another
question
asked
is:
why
are
they?
Why
do
they
need
to
search?
Why
is
it
repeat
searching?
Is
it
because
you
know
they
they
can't
find
something
or
they
just
want
to
kind
of
know.
What's
out
there,
you
know
what's
what's
available,
they
they
find
a
little
bit
and
then
they
want
to
know
what
the
what
the
world
looks
like,
I
don't
know,
do.
A
A
The
other
piece
that
might
be
interesting,
too,
is
I'm
not
sure
if
this
is
the
page
that
I'm
thinking
of
and
I
won't
spend
a
ton
of
time
you
know
kind
of
while
y'all
watch
me
splunk
around
on
the
analytics
page,
but
I
do
think
it's
interesting
look
at
who's,
consuming
the
documents
from
what
devices
so
obviously
desktop
being
the
heaviest
hitter.
I
would
imagine
a
lot
of
folks
at
work
and
a
lot
of
folks
with
laptops
by
a
significant
margin.
A
A
lot
of
our
user
experience
is
going
to
come
from
folks
on
desktops
as
opposed
to
mobile
or
tablet
and
there's
you
know
breakdowns
of
individual
devices
too.
So
you
start
looking
at
mobile
devices.
For
example,
the
iphone
is
going
to
be
the
number
one
used
device
to
access
our
dock,
so
optimizing
for
mobile
is
another
takeaway
there,
or
something
similar
to
that.
I
did
update
the
quarterly
planning
to
start
to
use
analytics
to
create
action
items.
A
A
G
I
would
I
would
like
to
put
my
name
in
for
that
to
help,
because
I
think
it
has
a
lot
of
overlap
with
the
stale
things
going
on.
So
I
need
to
be
diving
into
the
analytics
anyway,
and
I
also
just
had
another
thought.
I
know
you,
we
stopped
doing
the
analytics
send
out
to
the
broader
communication,
but
do
we
want
to
do
like
a
narrow
if
it's
possible
to
set
up
like
a
sub
emailing
list
that
people,
if
they
want
to
get
the
monthly
reports
they
can
sign
up
for
it?
G
A
A
So
what
I'm
wondering
is
if
we
could
potentially
pair
the
efforts
between
what
I'm
talking
about
doing
with
the
localization
teams,
where
it's
kind
of
an
opt-in
mailing
list
separate
from
sig
doc,
separate
from
the
localization
sub
project.
It's
pretty
much,
and
maybe
I
maybe
the
takeaway
here-
is
to
not
make
it
localization
specific.
A
A
I
J
J
I
think
I
think
that
the
website
is
one
structure
you
have
to.
You
have
to
know
that
the
concept
would
be
before
get
in
the
context.
So
that's
why
the
all
the
tutors
are
on
the
on
the
first
page
of
the
documentation
that
then
you
go
to
the
concert
and
get
the
input
that
you
you
need,
and
I
don't
know
if
it
is
possible
to
know
from
the
google
narrative
if
they
are
using
more
the
search
for
google
search.
J
J
J
J
J
A
D
Because,
let's
say
we,
we
are
stumbled
upon
the
a
certain
page
and
then
we
notice
that
there
is
several
things
that
actually
interesting
or
or
we
want
to
learn
something
from
that
specific
page.
And
then
we
try
to
kind
of
click
related
documents
that
link
into
that
page
or
usually
people
just
kind
of
googling,
whatever
they
want
to
search
and
then
find
it
from
the
search
engine
result.
A
Gotcha,
so
I
put
this
bullet
here
and
we
can
definitely
take
a
look
to
see
and
it
I'm
I'm
going
to
make
an
assumption
that
most
likely
is
probably
searching
and
clicking
through
the
search
as
opposed
to
knowing
how
to
navigate
the
website,
but
that
that's
just
my
assumption
there
one
other
piece
related
to
this,
which
has
recently
become
available
to
us
by
using
doxy,
and
we
can
take
a
look
at
this,
but
I
don't
know
if
it
necessarily
makes
sense.
Is
this
feedback
wasn't
helpful?
A
Yes
or
no
you'll
see
this
a
lot
in
the
kubernetes
documentation.
I
don't
believe
we're
using
it
to
the
full
effect.
Well,
I
shouldn't
say
I
don't
believe
we
aren't
using
this
to
the
full
effect
of
the
impact
that
that
yes
or
no
feedback
has,
because
with
that
page
you
have
the
ability,
then
to
go
into
google
analytics
and-
and
actually
we
can
check
this
out
here.
So
we
can
go
into
behavior
events
and
overview.
A
G
I
A
A
So
it's
been
a
while,
since
I've
looked
at
this
I'll,
try
my
best
to
summarize
it,
but
I
could
have
screwed
this
up
a
little
bit,
but
essentially
when
they
click
the
yes.
This
is
helpful.
It's
a
javascript
action
that
marks
the
page
as
being
helpful
and
I
forget
how
they
actually
derive
the
nose
to
it.
So
here
the
average
values
are
every
rating
for
the
page
values
between
zero
and
one.
When
a
user
clicks,
no
a
value
is
zero
sent
to
google
analytics
when
users
click
yes,
a
value
of
one
is
sent.
A
So
now
we
can
get
a
percentage
of
the
average
value.
Is
the
aggregate
rating
for
that
page?
So
by
looking
at
this
event
here
and
the
total
events
in
this
average
value,
you
can
look
at
the
most
helpful
page
being
kubernetes
basics,
at
least
for
folks
that
gave
us
feedback
here
at
a
.89
significantly
higher.
Let
me
actually
sort
that
and
that's
going
to
get
ugly
as
well.
A
All
right,
so
I'm
not
going
to
waste
everyone's
time.
The
problem
here
is,
if
there's
a
page,
that
only
one
person
clicked
yes,
is
helpful
on
it's
going
to
have
a
score
of
an
average
view
or
average
helpfulness.
I
guess
if
you
will
of
one,
whereas
that
might
not
be
the
case
for
some
of
the
more
active
pages.
So,
let's
see
the
we'll
sort
by
total
events
we
see.
A
A
Yeah
sure
cool
yeah,
so
so
this
like
pieces
like
this
in
the
google
analytics,
I
feel
like,
are
underutilized
and
much
appreciation
karen
for
for
bringing
this
up,
because
I
do
think
it's
worthwhile
of
exploring
some
of
these
and
seeing
the
current
status
of
you
know
what
are
our
effective
docs.
What
are
ineffective,
docs
and
you
know,
if
you're
looking
at
these
pages
here,
it
looks
like
what
is
kubernetes
and
components
is
rated
pretty
high.
But
what
are
we
doing
wrong
with
cube
cuddle
commands?
A
I
I
A
J
All
right,
I
have
two
projects
or
three
three
projects
that
I
follow
is
a
website
contribute.
I
think-
and
I
don't
know
what,
but
when
I
use
that
tool
the
triage
party,
I
see
the
generic
kubernetes
as
the
only
source
of
issues
and
pull
requests
and
everything
else.
So
it's
me
that
I
don't
know
how
to
use
the
tool
or
that's
how
the
tool
work.
J
A
A
A
Takeaways
all
right
cube,
cuddle
documentation.
I
know
karen
brought
this
up.
I
saw
chiang
ming
made
some
comments
as
well
and
tim
commented.
I
struggled
to
really
wrap
my
mind
around
what
what
discussion
was
formulating
around
and
what
the
the
clear
discussion
to
be
had
was,
so
I'm
going
to
open
the
floor
up
to
whoever
feels
like
giving
context
on
this
and
I'll
be
the
note
taker.
B
I
I
guess
I'll
add
I
added
it
because
I
felt
like
yeah.
I
think
it
was
last
year
the
end
of
last
year
there
was
the
effort
to
make
the
cube
cuddle
site
right,
there's
like
a
documentation
site,
and
I
thought
there
should
be
some
kind
of
merging.
I
think
tim.
You
also
opened
a
pr
about
it.
There
should
be
some
kind
of
merge
between
the
cube
cover
command.
I
That's
here
with
sig
docs
and
this
new
effort
and
and
also,
I
think
that
it's
you
know
it's
kind
of
it's
a
continuous
effort
to
maintain
the
current
cube,
cuddle
command
reference,
and
it
also
looks
different.
So
it's
another
sort
of
a
third
factor,
so
those
are
there's
a
couple
things.
So
I
don't
know
what
the
state
of
the
the
new
cube
cuddle
site
is.
So
that's
that's
really
why
I
brought
it
up.
It's
sort
of
a
maintenance
question
and
a
direction
question.
A
Yeah-
and
I
I
know
that
the
one
of
the
things
that's-
that
the
q
that
the
kubernetes
project
has
been
facing
is
there's
a
lot
of
website
sprawl.
So
there
was
like
download
kubernetes.
There
was
like
the
ks.dev,
which
is
more
contributor,
focus,
there's
the
kubernetes
documentation
and
there's
the
cute
cuddle
site.
I
believe
enginex
ingress
is
a
github
page
and
there's
a
little
bit
of
fragmentation
there.
A
B
B
Well,
I
guess
there's
three
problems:
I've
seen
websites
where
behind
the
scenes,
if
you,
if
you
know
about
technology,
you
can
see
that
there's
actually
two
different
things,
but
the
people
who've
designed
them
have
made
it
so
that
one
dovetails
into
the
other
and
unless
you're
looking
for
it,
you
don't
notice
the
seams.
The
url
changes
and
everything's
slick
apple
had
that
setup
like
that
for
many
years
and
have
now
gone
for
a
single
unified
website.
B
Pretty
much
so
we're
not
doing
the
smooth
dovetailing
of
different
experiences
and
what
we're
doing
is
the
rough
unintegrated
things
experiences
that
don't
really
talk
to
each
other
and
don't
mention
each
other's
existence.
Unfortunately,
and
I
do
think
that
harms
coop
couple
is
such
an
important
command
for
people
to
use
that
it
harms
people's
experience
or
kubernetes.
I
Yeah,
I
agree
with
you
with
the
latter
part,
especially
because
I
feel
like
there's
not
cohesion
between
the
different
sites
and
and
efforts
and
the
command
reference
with
the
dockside.
Is
it's
been
there
for
a
while?
So
it
I
think
it's
yeah
it.
You
know
we
maintain
it,
but
I'm
not
sure
that
if
there's
I'm
not
sure
the
differences
between
what
we
have
and
what
the
other
sites
are
offering
the
accuracy.
You
know
the
documentation.
A
A
The
reason
I'm
bringing
this
up
is:
there's
ability
in
netlify
to
have
a
mono
repo,
which
is
essentially
multiple
sites
that
share
images,
components
utilities.
So
in
this
case
their
example
is
a
website
folder.
That
is
completely
standalone,
that
is
www.company.com
the
app
folders
app.company.com
and
then
doc
site
is
docsetcompany.com.
A
I
don't
know
if
this
is
the
answer,
but
it
might
be
kind
of
interesting
to
explore
about
potentially
giving
that
one
unified
view,
maybe
having
a
different
owners
and
approvers
file
in
a
certain
subnet,
a
segment
of
the
the
website
repository
to
start
bringing
it
all
under
one
one
umbrella.
But,
like
I
said
it
looks
like
this
might
only
be
sub
domains.
It
might
not
actually
be
like
company.com
foo
bar.
We
might
not
even
be
able
to
use
this,
but
I
thought
that
was
kind
of
cool
and
it
might
be
something
worth
exploring.
I
I
A
B
I
B
A
J
J
A
Yeah,
it's
really
about
consolidation,
so
here
I
can
open
up
this.
So
here's
the
cube,
cuddle
and
customize
page,
which,
if
you
notice,
is
an
entirely
separate
website
than
it
is
for
kubernetes
docs
or
just
the
regular
standard
kubernetes
website
here,
and
so
the
concept
is
since
these
are
two
entirely
independent
websites,
and
this
isn't
the
only
example.
There's
a
lot
of
other
fragments
of
websites.
A
J
B
A
B
Already,
I
won't
I
won't
now,
but
I
can
sketch
out
a
bunch
of
different
approaches,
and
some
of
those
approaches
are
really
sick,
docs
turning
up
on
six
clies
door
and
saying
we're
from
sick
docks
and
we're
here
to
help,
and
some
of
them
are
very
different.
There
isn't
a
way
to
do
this.
There
are
some
good
options,
but
they
all
involve
talking
to
people.
K
I
A
Yeah
sounds
great,
thank
you
for
bringing
that
up
and
I
totally
agree.
I
think
that
this
definitely
is
an
area
of
pain.
So
it's
it's.
It's
awesome
to
see,
and
that
brings
us
to
the
end
of
our
planned
agenda
with
proposals
and
that's
it
does
anybody
have
any
other
proposals
or
any
other
things
that
they
would
like
to
discuss
today
tonight,
depending
on
where
you're
at.
J
A
So
this
is
really
a
special
meeting
for
the
quarterly
meeting,
so
it's
only
once
a
quarter
or
every
three
months.
This
is
very
traditional
here
and
it's
really
a
way
to
track
larger
goals
or
larger
efforts
in
sick
docs.
So
where
traditionally
a
contributor
might
say
all
right,
I'm
going
to
contribute
to
sig
docs
and
fix
a
typo
or
fix
a
single
page
or
review
a
single
page,
very
small,
one-off,
pull
requests
that
don't
take
coordination
between
multiple
people
that
don't
take
coordination
between
multiple
special
interest
groups.
A
It's
really
a
way
for
sig
docs
to
come
together
as
one
group
and
align
on
what
are
our
overall
goals.
How
are
we
doing
on
our
goals
and
who's
owning
and
driving
this
goal
to
us
next
step?
You
know,
because,
unlike
the
corporate
world,
I
feel
like
a
lot
of
people,
have
different
bosses
and
different
involvements
with
open
source
kubernetes,
and
so
this
is
a
way
to
make
sure
that
we're
keeping
ourselves
accountable
for
the
work
that
we're
doing
and
making
sure
we're
holding
each
other
accountable
as
well.
J
A
You
know
crazy
ice
storms
in
texas.
Whatever
you
know,
natural
disasters
and
fun
stuff
happens
there.
We
ultimately
had
to
schedule
our
quarterly
planning
for
today,
which
is
at
the
end
of
february,
and
so
it's
not
really
fair
at
the
end
of
february
to
plan
for
a
quarter
that
you
only
have
a
month
left
in.
A
J
A
I
C
B
J
J
If
it
fails
again,
I
will
I
will
follow,
I
mean
for
this
special
meeting.
I
didn't
get
any
any
alert.
I
mean
I
I
I
get
the
alert
of
the
of
the
meeting,
but
the
the
link
was
for
february.
Hey,
I
don't
know
what
was
wrong
with
people
who
will
calendar,
but
the
reminder
and
the
link
with
the
reminder
was
was
okay,
but
the
link
was
wrong.
A
Yeah
yeah,
not
a
problem
at
all,
and
so
it's
not
your
problem
definitely
is
an
issue
that
that's
kind
of
self-inflicted
from
sig
docs
we
had
a,
we
had
a
invite
that
was
sent
out.
Many
many
I
shouldn't
say
many
many,
but
at
least
years
ago
original
invite
was
sent
out
with
a
certain
url
in
it
and
ultimately
that
meeting
was
rescheduled
and
changed
to
the
new
url.
I
forget
how
many
months
ago,
but
semi-recently
that
link
has
changed
so
it's
very
possible
in
between
that
old,
existing
link
in
the
new
link.