►
From YouTube: K8s SIG Docs Meeting for 20200929
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
Rolling
and
action:
okay:
this
is
the
sig
docs
weekly
meeting
on
the
29th
of
september
2020.,
I'm
tim
banister
and
jim
angel.
I
think
you're
gonna
lead
until
you've
got
a
disappear.
B
Yep,
you
got
it
jim
angel
co-chair
and
it
looks
like
we
have
brad
and
abigail
joining
us
here
today.
So
a
light
crowd
and,
I
believe,
all
returning
contributors,
some
tochi,
I'm
not
sure
if
you're
a
new
contributor
or.
C
Not
hello,
I'm
I'm
a
shadow
in
the
release
dog
team.
Oh
perfect,.
A
Okay,
oh
new
contributor
is
already
there.
I
put
it
in
twice.
Let
me
take
the
second
one
out:
okay,
updates
and
reminders.
We
did
not
have
a
pull
request.
Wrangler
for
this
week
I
have
jumped
in.
I
will
take
the
chair
this
week.
We
need
a
pull
request
wrangler
for
next
week.
So
is
anyone
willing
to
take
that
slot.
D
A
Okay,
cool,
let
me
the
highlight
here
thanks
brad
sure
cool,
so
yeah
approvers
make
sure
you
next
make
sure
you
know
your
schedule.
Pr
angler
shifts
back
to
you,
jim.
B
Awesome,
no
appreciate
that
tim.
Thank
you
for
stepping
up
too
for
the
pr
wrangler
shifts
there
as
well.
Thank
you.
Brad.
Definitely
appreciate
that.
So
moving
along
to
the
release
120
for
updates
somtochi.
Is
that
something
you
could
provide
us
with.
C
I
knew
not
much
has
been
done
for
now,
and
probably
I
should
leave
that
to
my
lead
to
the
the
leader
of
the
team.
That's
anna
yeah
yeah,
we're
having
like
meetings
and
a
list
of
pull
requests.
Basically,
but
yeah
she'll
give
like
more
updates.
B
B
It's
definitely
a
very
fair
update
early
on
in
the
release
cycle.
So
moving
on
to
the
blog
update
tim
is
that
something
you
could
potentially
fill
us
in
on.
A
I
saw
one
blog
article,
which
is
the
first
of
article
mirroring
from
the
kkks.dev
or
kubernetes.dev
website.
This
is
a
new
thing,
like
we've
not
had
as
far
as
I
know,
websites
that
we
are
willing
to
mirror
from.
So
I
believe
that
the
policies
that
we
want,
what
the
old
world
of
print
used
to
call
first
world
serialization
rights.
A
We
wanted
to
publish
the
article
first
and
then,
because
it's
open
source
you
can
go
and
copy
it
and
attribute
it,
but
you
couldn't
take
an
article
you'd
published
on
your
own
blog
and
then
submit
it
to
kubernetes,
but
you
can,
if
it
is
from
another
bit
of
kubernetes.
A
I
think
I
think
that
we
need
the
blog
team
to
make
a
bit
of
clarification
on
that.
Maybe
we
might
need
to
update
some
guides
just
to
make
that
super
clear
to
people
that
you
can
do
that,
but
in
terms
of
does
it
make
sense
yeah.
But
I
think
we
should
do
this
mirroring,
like
that's
an
opinion
and
it
seems
reasonable,
there's
also
an
article
come
in
from
cockroachdb.
E
Interrupt
there
is
like
12
people
in
the
other
meeting.
Oh
my
word,
hey
we
go.
Let
me
go
rescue
them
and
guide
them
here.
Went
back
one
minute
awesome!
Thank
you.
Zach.
F
I
think
we
should
change
the
link
in
the
agenda
right.
B
That
should
have
also
been
updated
as
well.
I'm
not
sure
if
it
was
up.
So
basically
if
people
were
subscribed
to
the
the
google
group
for
sig
docs,
they
would
have
gotten
an
update
about
the
meeting
link
if
it's
a
copy
of
a
calendar
or
independent
or
detached
from
there.
They'd
have
to
rely
on
the
slack
announcements,
I'm
guessing.
That
might
have
been
what.
G
B
Yeah
for
this
first
meeting,
we
probably
should
have
just
posted
the
the
url
and
slack
and
just
get
everyone
on
the
same
page
there,
but
yeah.
G
B
Yeah
that
I
learned
recently
too,
is
that,
and
I
had
to
had
to
do
this
for
personally
I
was
on
the
google
groups
mailing
list,
I'd
get
like
from
the
google
groups
and
I'd
copy
the
calendar
invite
to
my
work,
invite
and
it
wasn't
until
recently.
I
realized
that
you
could
have
multiple
emails
subscribed
to
that
google
group
and
once
you're
subscribed.
Then
you
get
the
invites
from
the
group
where
you
don't
need
to
copy
it,
maintain
the
to
list
and
all
that
good
stuff.
So.
G
B
B
H
Okay,
thanks
yeah,
I'm
kristen
martin,
I'm
a
sig
release,
120
docs
shadow,
I'm
working
with
anna
and
happy
to
join
you
on
the
meeting
today,
thanks.
I
I
I
should
tell
you
what
I
do.
I'm
a
dev
advocate
specifying
specifically
working
on
docs.
J
Hi
my
name's
ashley.
This
is
my
first
time
attending
a
meeting,
but
I've
been
technically
part
of
the
group
for
quite
a
while.
So
yeah
thanks
for
welcoming
me
and
I'm
glad
I
found
out
where
the
new
link
was
for
the
new
chat
room.
J
J
B
Cool,
so
moving
on
to
the
updates
reminders.
The
pr
wrangler
this
week
is
tim
tim
stepped
up
because
we
didn't
have
a
pr
wrangler
so
much
thanks
there
as
well
as
next
week.
There
was
a
conflict
and
brad
stepped
up
there.
So
much
appreciated
and
moving
on
to
the
release.
120
updates
some
tochi
updated
that
there
was
some
progress.
I'm
not
sure
anna,
if
you'd
like
to
give
us
additional
information,
but
it
sounds
like
things
are
on
track.
There.
B
Here
from
the
blog
update
tim
mentioned
that
there
was
one
blog
article
that
is
going
to
be
mirrored
from
khdev
or
vice
versa,
and
this
is
the
first
time
where
we've
had
dual
source
content
or
you
know
dual
blogs,
and
this
is
a
new
thing
that
might
need
some
further
discussion
from
the
blog
side
and
it's
more
about
who
publishes
first
and
where
is
that
source
copied
from
and
most
likely
will
be
published
on
the
kubernetes
blog
and
then
copied
over
k's
dev.
D
Sure
so,
basically,
we
are
ready
to
kick
off
our
localization
subgroup
and
we
identified
a
group
of
participants
that
are
interested
and
if
anyone
on
this
call
is
interested
as
well
slack
me
we're
going
to
get
the
details
out,
but
anybody
who's
interested
is
welcome
to
participate
our
we're
going
to
have
a
monthly
meeting,
we're
going
to
do
most
most
of
the
stuff
on
our
localization
slack
channel,
but
we
will
have
a
monthly
meeting
and
the
time
that
seemed
to
work
best
for
everyone
was
11,
am
eastern,
so
odds
and
ends
that
I
need
to
worry
about,
and
you
know,
jim
or
zach
help.
D
You
know
make
sure
we
have
access
to
our
zoom
account.
Do
we
do
we
need
a
meeting?
Invite
a
calendar.
Invite,
like
you
know,
is
that
a
common
convention
that
we
like
to
use
here
or
is
that
not
necessary?
D
I
will
certainly
put
together
a
google
doc
that
looks
like
the
documentation,
the
the
the
weekly
meeting
upcoming
meeting
doc
that
you're
seeing
now,
but
I'll
do
one
for
the
subgroup
that
you
know
has
the
mission
at
this
stage
at
the
top.
It
has
the
the
weekly
agenda,
we'll
have
the
information
on
how
to
join
the
meeting
so
I'll
I'll
put
together
a
google
doc.
I
assume
that's
that
that
would
be
standard
procedure
and
then
leak
linked
it
into
the
our
localization
page
in
our
documentation.
So
I
plan
on
doing
all
that
soon.
D
The
one
thing
I
wanted
to
discuss
was
just
to
make
sure
jim
that
we
were
hitting
the
right
deliverables.
So,
as
I
understand
it,
just
the
level
said
everyone.
We
have
a
large
number
of
localization
teams.
Now
some
are
building
their
own
tools
to
help
with
certain
aspects
of
their
processes,
and
the
subgroup
was
really
meant
to
make
sure
that
we've
got
the
different
localization
teams
talking
and
working
on.
You
know
if
there's
ways
they
can
share
tools
with
each
other
great,
but
also
worrying
about
that.
They
were
all
documenting
things
in
different
places.
D
B
Yeah-
and
I
definitely
have
some
comments
or
suggestions
here,
but
I
don't
think
it's
necessarily
all
you
know
my
doing.
There's
a
lot
of
folks
on
this
call.
Who
can
you
know,
contribute
very
more
more
so
effectively
than
I
can
when
it
comes
to
localization,
but
but
you
hit
the
nail
on
the
head
overall,
it
was
the
fact
that
there
was
so
many
different
localization
groups
running
their
own
kind
of
sprint
or
marathon
and
having
an
avenue
where
we
can
synchronize
all
those
efforts
and
to
make
sure
there
isn't
duplication
or
duplicated
work
there.
B
You
know
one
example
of
that
that
I
saw
recently
was
part
of
the
release
cycle.
The
release
lead
reaches
out
to
the
localization
team.
Maybe
there's
a
better
way
that
you
know,
communication
or
handoff
can
happen
for
the
release
team.
If
there's
a
point
of
contact
there
or
a
source
document
for
like
an
introduction,
that's
a
very
pinpoint
example,
but
I
just
think
there's
so
many
different
moving
parts
here
and
it's
grown
to
be
such
a
large
undertaking
of
of
sig
docs.
B
I
think
there's
a
lot
of
opportunity
there
to
make
sure
we're
not
duplicating
efforts
there
and
I
would
look
heavily
into
what,
if
irva
or
tim
or
some
of
the
other
people
who
have
had
more
involvement
with
localization.
If
they
have
any
comments
about
that
direction,.
A
I'm
gonna
chip
in
jim.
I
guess
what
my
contribution
to
localization
has
been
landing
prs
in
the
english
localization
just
before
someone
or
maybe
just
after
someone
has
translated
the
previous
massively
out
of
date,
page
that
I've
I've
revised.
A
So
I
think,
there's
a
there
is
definitely
payoff
in
synchronizing
because
there
will
be
people
who
you
know
must
be
fuming
like
they
look
at
their
work.
It's
landed
two
days
later,
there's
a
massive
500
line,
diff.
Let's,
let's
try
and
cut
that
out.
I
think
it's
a
really
good
idea.
D
A
I
would
be
keen
to
find
out
what
localization
teams
want
from
english,
the
upstream
localization
and
understanding
what
people
want
you
know
will
help
us
work
out
how
to
deliver
that.
D
D
B
And
I
I
think
part
of
what
we're
talking
about
here
is
great
topics
for
conversation
for
that
working
group
localization
meeting
and
then
when
decisions
are
made
or
saying
hey,
this
process
works.
Well,
this
one
doesn't
maybe
service
that
back
up
at
a
regular
status
check
in
here
for
the
the
regular
docs
meeting.
D
B
B
All
right,
so
I'm
going
to
be
a
little
selfish
here,
because
I
got
a
split.
So
I'm
going
to
jump
to
a
few
of
the
items
I
have
towards
the
bottom
and
then
we'll
start
back
up
at
the
kubecon
n
a
action
item.
So
a
quick
issue
in
pr
that
I
posted
there
is
just
some
permission
changes
so
some
folks
with
approvers
and
gay
website.
If
they
don't
mind
taking
a
peek
at
the
issue.
B
24170,
all
it's
doing
is
removing
some
emeritus
approvers
and
reviewers
from
the
kubernetes
teams,
as
well
as
some
inactive
folks
from
getting
scheduled
to
the
pr
wranglers,
the
pr
wrangler
schedule.
So
not
a
big
deal.
There
just
wanted
to
raise
awareness
and
moving
on
to
the
process
you
might
have
seen
in
the
sig
docs
channel.
I
created
a
slew
of
reminders.
B
This
is
very
selfishly
for
myself.
I
tend
to
forget
about
the
quarterly
planning
the
quarterly
review
meetings
that
come
up
regularly,
and
so
what
I
did
is
I
ended
up
scheduling
a
slackbot
reminder
that
would
come
into
the
kubernetes
chat
and
say:
hey.
You
know
start
thinking
about
planning
a
quarterly
review
or
a
meeting
they're
coming
up
for
those
who
aren't
aware.
B
Sig
docs,
as
a
special
interest
group,
does
a
quarterly
review
where
we
take
a
look
at
bigger
projects
or
bigger
accomplishments,
and
we
take
a
look
at
what
was
accomplished
in
that
quarter
and
what
we'd
like
to
plan
for
for
the
next
quarter.
So
these
are
a
lot
more
of
a
wide
set
goal,
as
opposed
to
you
know:
merging
prs
keeping
up
with
the
daily.
You
know,
craft
of
you
know
documentation,
so
I
just
want
to
give
a
heads
up.
That's
what
those
reminders
are
for.
B
The
other
thing
I
wanted
to
bring
up
too
is
you
know
traditional
quarter
might
look
like
it
starts
in
january.
Obviously,
every
you
know
three
months
or
so
there
with
a
synchronization
point.
One
thing
I've
noticed
in
docs
over
the
past
couple
years
is
around
the
holidays.
A
lot
of
momentum
is
lost.
Understandably
folks
you
know,
take
vacation,
take
holiday,
and
so
traditionally,
what
I've
seen
is
that
last
quarter
that
q4
review
q1
planning
tends
to
take
place
in
november-ish
december.
B
You
know
when
we
had
kubecon
in
just
in
november
that
made
a
lot
of
sense
when,
when
needed,
we
also
had
it
in
december,
so
it's
kind
of
a
bigger
gap
between
the
q4
review
and
the
q1
review.
But
if
you
look
at
when
I
set
those
the
alerts,
there's
april
1st
july
1st
october,
1st
and
december
1st,
so
with
saying
that
we're
going
to
get
ping
done
october
first
and
start
thinking
about
quarterly
review,
that's
coming
in
the
pipelines,
I
wanted
to
bring
everyone's
attention
to
that.
B
I
have
a
link
to
the
q3
doc
for
reference
in
this
in
this
blurb
here,
but
we
can
definitely
start
bringing
up.
You
know.
When
do
we
want
to
meet?
How
do
we
want
to
parse
that
out
and
do
we
want
to
do
a
short
little
sprint
in
between
q3
and
q4
here
or
potentially
merge
them
all
into
one?
It
just
really
really
depends
what
folks
are
thinking
any
questions
or
comments
on
the
quarterly
review
that
will
be
coming
down.
The
pipelines.
B
Cool
then,
the
last
item
that
I
threw
on
the
agenda
here
was
that
just
showing
awareness
that
our
youtube
playlist
is
kind
of
out
of
whack,
it
hasn't
been
updated
since
february.
So
I'm
working
with
some
of
the
folks
on
slack
about
fixing
that
and
making
sure
their
youtube
playlist
is
up
to
date,
if
you're
not
sure
about
our
playlist.
I
believe
I
thought
we
had
it
linked
in
the
docs
series
for
sure
on
our
sig
community
page,
which
I'll
add
a
link
in
there.
B
F
D
D
B
That
I'm
not
sure
of,
but
it
definitely
is
coming
up
soon
and
just
real
quick
for
context.
For
folks
on
this
call,
this
year's
kubecon's
a
little
different
than
it
has
been
in
years
past
in
years
past.
We
would
do
a
contributor
summit
and
not
traditionally
be
represented
in
the
traditional
special
interest
group
track
on
cubecon
or
in
cubecon.
B
So,
besides
the
contributor
summit,
we
really
haven't
had
a
ton
of
official
presentations
and
what
you'd
see
in
the
past
with
other
sigs
is
you'd,
see
that
there's
a
intro
to
a
special
interest
group
and
then
there's
a
deep
dive.
So,
for
example,
there's
an
intro
to
the
sig
release
team
and
then
there's
a
deep
dive
into
the
sig
release
team
or
confirm
x,
or
what
have
you
and
historically
docs
hasn't
been
part
of
that.
B
So
there's
been
two
changes
this
year,
the
first
one
being
that
sig
docs
is
going
to
take
part
in
the
regular
track.
There
is
no
contributor
summit
planned
as
of
yet,
and
the
second
part
is
they're
no
longer
splitting
it
with
an
introduction
and
a
deep
dive.
It's
kind
of
like
all
in
one
right
now.
So
the
discussion
now
that
we're
bringing
up
that
ever
brought
up
is
that
that
we
need
to
decide
what
kind
of
content
we're
covering
who's
owning
the
decks
who's
producing.
B
That,
I
think,
there's
a
lot
of
decisions
to
be
made
and
if
I
had
to
make
a
guess,
I
would
imagine
that
that
this
might
just
be
a
separate
meeting
where
it
just
heads
down:
let's,
let's
create
planning
and
go
from
there,
but
I'm
open
for
any
questions
or
comments
on
this.
This
meeting
so.
D
So
it's
probably
a
short
separate
meeting.
I
would
agree
with
you
jim.
I
I've
actually
been
through
this,
because
I've
led
many
times
the
sig
ibm
cloud
provider
and
that's
gone
through
the
cycle
of
intro
plus
deep
dive
and
then
that's
also
been
combined
into
a
single
session
as
well.
So
I'm
I'm
living
this,
I
I
don't
know
how
much
time
we
have.
D
I
wish
I
knew
that
off
the
top
of
my
head,
but
suffice
to
say
what
I
believe
happens
is
we
typically
will
have
a
certain
amount
of
material
that
we
present
and
get
our
audience
excited
about.
What
we
do
and-
and
you
know,
if
it's
hey-
we
want
to
get
more
contributors
whatever.
Whatever
our
purpose
is
that's
what
we
focus
on
and
then
you
typically
lead
some
leave
some
time
for
questions
and
discussion,
and
so
I
think
it's
up
to
us
to
figure
out
how
much
time
we
have.
D
Is
it
just
the
intro
material
that
I
provided,
because
there
was
a,
I
think
it
was
celeste
or
someone
had
mentioned
hey.
We
could
really
also
add
use
some
of
our
time
to
to
talk
about
best
practices.
For
for
how
to
do
technical
writing,
which
I
think
would
be
very
valuable
as
well.
So
I
think
it
just
comes
down
to
figuring
out
how
much
time
we
have.
D
What
are
the
top
priority
topics
that
we
want
to
cover
and
who
wants
to
cover
them
and
and
then
how
much
time
we
want
to
leave
for
discussion
and
then
I
believe
we
do
have
to
hurry,
because
if
I
recall
we
do
have
to
record
this
meeting
of
the
content
ahead
of
time
and
then
we
do.
The
questions
live.
K
So
I
tim
and
I
are
planning
to
work
I
mean
we
had
talked
about.
I
need
to
start
that.
So
there
is
this
contributor
summit
where
they
are
planning
to
record
everything,
and
previously
the
milestone
was
1.20
and
I
don't
know
if
that's
gonna
happen
for
cubecon
na,
but
it
will
eventually
happen
all
those
whatever
brad
presented
in
the
I
have
brad's
flight.
K
Whatever
he
presented,
it's
gonna
go
in
a
video,
probably
we'll
add
more
content
and
we'll
work
through.
Do
some
live
demo?
Something
of
that
sort.
So
do
we
need
to
coordinate,
or
is
it
totally
unrelated?
I
would
love
to
have
them
coordinated
because
video,
that's
gonna,
be
there
somewhere
else
and
I'm
not
sure
how
they
are
planning
to
use
it.
K
D
So
so
does
it,
it
sounds
like
we
have
two
presentations.
I
just
want
to
make
sure
I
understand
it
sounds
like
we've
got
a
presentation
as
part
of
the
summit,
and
then
I
mean
it's
part
of
the
conference
and
then
there's
also
something
for
the
contributor
summit,
because
I
remember
zach
asked
some
of
us
to
sign
up.
I
think
for
the
actual
kubecon
conference,
intro
deep
dive
presentation
am,
I
am
I
right
jim
or
am
I
confused.
B
G
So
how
about
this?
Because
now
I'm
concerned:
let's,
let's
I'm
sorry,
I'm
gonna
dictate
this
maybe
a
little
bit.
Maybe
if
you
signed
up
for
a
thing
on
behalf
of
sig
doc's
post
in
the
channel
and
then
we'll
have
a
tally
of
what
things
we
signed
up
for
collectively
and
then
we
can
like
divide
and
conquer
slash.
Staying
coordination
from
there.
D
But
hold
on,
I
think,
there's
only
two.
I
think
zach
asked
us
for
names
and
said
who
wants
to
do
the
whatever
right
and
several
of
us
volunteered
and
then
it
sounded
like
there
was
another.
Then
there
was
a
separate
thing,
which
was
the
contributor
summit
right
and
I
think
irvy.
You
were
driving
that
as
well
and
tim
and
then
we
had
the
call
last
week
or
a
week
before.
I
can't
remember
where
we
didn't
have
enough
folks
on
the
call
celeste
to
confirm
that
there
was
just
two
separate
work
items
there
is
there.
D
A
Yeah
also,
I'm
aware
you
said
you
were
gonna
leave
at
a
11
pacific
time,
jim
whoops
look
around
the
door,
okay,
so
the
thing
that
I
believe
I'm
signed
up
with
savita
to
record
a
video.
A
I
think
that
was
mentioned
in
slack
like
months
ago,
but
slacks
history
search
is
not
great,
so
I'm
not
going
to
go
and
even
try,
but
that
is
for
a
new
contributor
workshop
that
I
have
this
down
as
ncw
in
my
notes-
and
I
think
that's
very
much
related
to
things
that
happen
at
kubecon
in
person
normally,
but
that's
what
it
was
for.
B
Yeah,
that
makes
sense
it's
more
of
a
contributor
experience,
new
contributor
workshop,
as
opposed
to
the
official
kubecon
sig
track
for
sig
docs.
So
there's
two
things
and
I
believe,
we're
on
the
same
page.
It
still
be
good
to
figure
out
who
signed
up
for
what
in
the
slack
channel,
we
could
split
them
to
two
and
real
quick.
Is
there
any
other
questions
or
comments
on
that.
B
Okay,
hearing
nothing
real
quick.
I
just
wanted
to
touch
on
the
issues
in
pr
section
before
sneaking
out
here.
We
had
that
umbrella
issue
opened
up
for
third-party
content
removal
and
we
had
that
targeted
for
completion
by
release
of
119
and
now
we're
starting
the
120
cycle.
B
B
It's
going
to,
of
course,
be
ongoing
effort
to
remove
third
party
content,
but
at
the
same
time,
is
it
possible
to
wrap
up
some
of
these
issues
or
they
agreed
upon
deliverables
for
119
and
just
raising
awareness
around
that
and
if
anyone
needs
any
context
further
on
that
issue,
then
click
on
the
umbrella
issue
it
links
into
the
cap
it
talks
about
why
we're
doing
it
and
it
talks
about
you
know
what
happens
after
the
120
and
later
releases.
So
let's
keep
an
eye
on
that.
B
A
You
right
so
that
was
jim
on
third
party
content.
Removal
and
nate.
You've
got
a
comment,
an
issue
about
mini
cube.
I
Yes,
I
was
looking
at
doing
a
quick
text
update
to
remove
some
information
about
hypervisor
from
the
mini
cube,
install
and
then
was
talking
with
celeste
and
zach
and
thinking.
Well,
actually,
it
looks
like
a
lot
of
the
mini
cube.
Install
information
might
be
better
suited
being
left
on
the
minicube
site
and
we
can
provide
a
link
to
it
rather
than
trying
to
keep
our
site
up
to
date,
as
it
gets
stale
fairly
fairly
quickly
and
fairly
regularly.
I
would
expect
so
that's
that's
what
this
is
about.
I
And
the
reason
the
reason
we
wanted
to
bring
it
up
here
was
because
there's
a
lot
of
there's
a
lot
of
traffic
on
that
site,
and
so
we
didn't
want
to
yank
it
and
change
it
without
sort
of
bringing
it
up
to
the
group.
First.
A
I'm
gonna
chip
in
with
a
couple
of
opinions.
Then
we
can
redirect.
So
one
thing
you
can
totally
do
is
you
can
configure
a
redirect
from
the
existing
page
to
the
new
one?
I
think
that
might
be
a
viable
thing
to
do.
So.
That's
my
first
comment
and
the
other
thing
is
we
can
take
any
sections
of
the
of
the
page.
That's
there
on
the
kubernetes
website
and
sort
of
donate
them
to
minicube
and
I
think
nate.
A
If
you're
looking
at
cutting
out
that
content,
it
might
be
worth
looking
to
see
if
there's
anything
that
you
think
is
really
missing
from
the
documentation,
we're
planning
to
link
to
and
suggest
a
pull
request,
and
so
look
we're
going
to
delete
this.
But
would
you
would
you
please
like
this
yeah?
What
do
you
think.
I
I
think
that
makes
sense
when
you,
when
you
say
taking
sections
of
the
existing
page
and
donating
them
to
hours,
is
there
would
that
be
an
automated
update,
or
is
that
something
that
we
would
need
to
continue
to
revisit
as
the
as
their
site
updates?.
A
It
would
be
like
a
copy
and
paste
you've.
We've
got
some
mark
down
if
you
judge
that
that
markdown
would
be
really
missing
from
the
revised.
You
know,
after
the
change
that
particular
bit
of
markdown
text
would
be
missing
and
there
would
be
a
net
loss
to
the
people
who
want
to
run
mini
cube
on
the
laptop
community.
A
That's
a
thing
you
can
do.
Okay,.
L
Hey
there
wasn't
a
I
don't.
I
can't
hear
there
was
an
existing
pr
and
I'm
not
sure
if
it's
still
open,
but
that
was
by
stromberg
thomas
jonberg.
Is
it
and
I
think
he
actually
heavily
edited
or
reduced
the
current
page?
So
you
might
want
to
look
at
that
or
try
to
search
for
that,
so
it
still
maintained
a
link,
or
at
least
a
page
in
the
kubernetes
stocks,
but
it
pretty
much
forwarded
every
all
the
traffic
to
the
the
actual
mini
cube
repository.
A
I
I
haven't
seen
it
yet.
No
that
link,
if
you
could
put
it
in
either
the
agenda
or
or
the
the
issue
that
nate
has
linked
to
that,
would
be
fantastic.
A
A
A
Okay,
any
I'm
gonna
stop
showing,
so
I
can
actually
see
people's
faces
and
see
if
and
we'll
put
their
hand
up
any
more.
Anyone
got
any
more
questions.
Anything
people
want
to
talk
about.
E
One
possible
note
on
meetings
at
kubecon
to
muddy
the
waters
even
further.
The
cncf
tech
writers
will
be
hosting
an
open
hours
specifically
for
tech
talks
not
limited
to
kubernetes,
but
across
all
of
the
cncf
cncf
landscape
projects.
So
I
will
make
sure
to
signal
clearly
how
that
is
different
from
everything
else.
E
So
there
are
three
moving
pieces
of
docks
in
the
in
the
kubecon
landscape
and
I
will
do
my
best
to
make
sure
that
that
is
clearly
signaled.
What
is
what.
D
D
D
So
so
quick
question
for
the
subgroup.
Do
I
need
a
a
meeting
invite,
or
is
it
just
okay
to
just?
What
do
you
recommend
I'm
looking
at
the
chairs
for
advice
there,
because
or
is
it
just
we
announce
it
and
announce
it
and
announce
it.
E
The
that's
obvious,
that's
a
really
good
question.
I
know
that
the
kubernetes
community
repo
has
some
guidelines
around
organizing
things,
like
slack
channels,
even
getting
a
youtube
channel.
E
If
you
want
to
record
your
meetings,
let
me
let
me
find
the
the
guidance
for
getting
a
new
slack
channel
and
or
sorry
getting
a
meeting
invite
in
the
the
community
repo,
and
let
me
share
that
out.
D
E
I
I
don't
know
if
zoom
will
allow
that
I
think
zoom
may
disallow
activity
or
like
confine
activity
to
a
certain
window
around
a
time
slot.
But
honestly,
I
don't
know,
but
let's
start.
A
Oh
I'll
just
chuck
that
in
the
agenda
slash
minutes.
A
A
I
think
that
is
an
unmuting
type
issue
right,
your
last
chance
to
contribute
to
this
weekly
meeting
people.