►
From YouTube: K8s SIG Docs Meeting for 20200915
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Have
we
got
any
new
contributors
today,
or
indeed
people
who've,
who
are
returning
and
haven't
been
joining
in
a
while
and
would
like
welcome
back.
B
It's
been
a
while,
since
I've
been
here,
my
two-year-old
finally
is
napping
on
the
time.
I
want
him
to
go
to
go
to
sleep
so.
A
B
So
I'm
a
software
engineer
at
red
hat
I
been
contributing
to
docs
on
and
off.
I've
also
been
looking
to
incorporate
the
lessons
that
docs
has
been
learning
into
some
of
my
own
projects,
including
this
new
project,
shipwright
that
we
just
had
our
first
release
on
last
week
very
helpful.
A
Okay,
housekeeping
updates
and
reminders
this
week's
pull
request.
Wrangler
is
tuning
chewing
not
appearing
in
this
movie,
but
no
worries,
assuming
we'll
be
wrangling
and
has
been
wrangling
already
next
week
is
beneath.
If
you're
an
approver
make
sure
you
know
your
scheduled
pr.
Wrangler
shifts.
A
Hello
lorenzo
agenda:
let's
talk
about
sig
release
over
to
you,
anna.
C
Thank
you
so
really
started
yesterday,
I'm
currently
in
process
of
going
over
the
shadow
application,
so
shadows
are
not,
they
haven't
been
decided
yet.
I
did
make
a
pull
request
today,
which
is
written
here.
So
I
know
rv
gave
me
a
looks
good
to
me
label,
but
I
actually
need
an
approval.
So
if
anyone
can
approve
that
that
would
be
really
helpful
and
another
thing
I'm
actually
less
brought
up
in
the
sig
release
channel.
C
It's
about
all
the
channels
that
we
have
for
communication,
and
I
think
it's
actually
a
really
good
idea
to
combine
those.
So
I'm
talking
about
there's
one
for
release
docs
that
was
created
last
release,
but
it
was
never
used
and
then
there's
one
called
sick,
doc's
release
channel,
which
was
which
have
been
used
by
the
sig
dogs
group
and
the
release
team
for
a
while.
Now
and
I
actually
looked
up
if
it's
documented
anywhere
and
that
channel
it
is
documented
in
the
documents.
C
So
if
we
want
to
move
to
this
like
new
release,
docs
channel,
we
would
have
to
change
those
areas.
So
I
guess
I
just
wanted
to
get
the
team's
opinion
on
what
the
sig
docs
release
is
used
for
because
I
know
what
release
docs
is
used
for.
D
Yeah,
so
just
to
back
that
up
and
give
people
a
little
more
context,
anna,
so
in
sig
release,
today,
tim
pepper
very
kindly
pinned
a
pinned,
a
message
which
outlines
all
the
release
related
slack
channels
and
when
he
did
that,
I
noticed
that
he
pinned
for
doc's
release
dash
docs,
which
I
was
unaware,
existed
up
until
that
moment,
because
sig
dash,
really
or
sig
dash
docs
dash
release
is
the
one
that
we
all
typically
use.
D
So
the
question
is:
do
we
have
a
bit
of
overlap
here
and
how
should
we
address
that?
Because
too
many
channels,
no
good
for
the
brain.
E
Yeah
actually
for
previous
releases,
I
noticed
that
the
lid
will
create
a
kind
of
dm
for
each
of
the
shadows.
So
it's
wondering
if
there
is
a
better
way
to
communicate
to
each
other,
because
if
let's
say
we
are
using
the
m,
then
it's
kind
of
hard
to
track
things
or
any
advice.
C
On
that
yeah,
so
I
actually
talked
to
elise
a
while
back
about
this
whole
like
channel
dm
versus
an
open
channel,
and
I
think
what
we're
gonna
do
is
actually
communicate
with
the
shadows
through
on
a
public
channel
now
and
if
a
dm
is
required,
we
will
still
use
a
dm
for
some
private
conversation,
but
we're
trying
to
make
everything
as
open
as
possible.
C
D
D
I
guess
the
question
I'm
asking
is:
do
you
need
two
channels?
Do
you
need
one
channel
specifically
for
talk
amongst
shadows
and
then
one
to
sort
of
reach
out
to
the
docs
community
yeah
and
if
you
need
a
channel
to
reach
out
to
the
docs
community?
My
question
is:
how
is
how
is
that
different
than
just
reaching
out
to
sig
docs.
C
Yeah
because
last
last
release,
I
think
we
we
actually
used
the
sig
docs
channel
to
ask
everyone
for
pr
reviews
and
stuff
right.
So
if
that's
still,
okay
with
the
team,
then
I
would
just
use
one
channel
to
communicate
with
the
shadows
and
then
use
sig
docs
to
communicate
any
reviews
or
communicate
with
the
sig
dogs
team.
A
I'm
going
to
make
a
couple
of
points
here.
First
of
all,
if
you
need
to
follow
up
and
really
sort
of
chase
up
that
something
hasn't
been
pr
reviewed.
There
is
the
sort
of
I
wouldn't
say
nuclear
option,
but
slightly
stronger
option
of
the
pr
reviews
channel,
which
is
fairly
naggy.
That
is
for,
like
processes
have
failed,
and
you
know
we
need
to
get
a
pr
review
to
happen.
So
the
pr
reviews
channel
is
for
that
purpose
and
it
is
available
for
documentation
as
much
as
anything
else.
A
I
think,
if
you're
using
that,
then
something
has
gone
wrong
if
you're
using
that
for
documentation,
then
something
has
gone
wrong
here,
but
it
exists
if
you
need
to
reach
out
to
website
contributors,
for
you
know,
for
the
main
english
localization,
especially
then
sig
docs
is
the
right
channel.
A
If
you
need
to
get.
For
example,
you've
got
a
pull
request,
which
is
lgtm
and
you're,
really
chasing
up
an
approval
to
build
on
that
lgtm.
There
is
sig
docs
approvers,
so
that's
a
good
choice.
If
it's
you
know,
you
know
what
you
don't
want
the
strong
option.
You
just
want
to
save
this.
This
looks
ready
for
approval
and
now,
as
a
release
team,
you
can
do
your
own
approvals
for
the
release
branch,
but
it
might
be
relevant
for
some
changes.
A
So
that's
like
you
know
generally
and
that's
what's
in
place
outside
of
release,
and
then
you
have
the
two
channels
that
you've
mentioned.
You've
got
release
docs,
which
was
new
to
me,
and
you've
got
sig
doc's
release,
and
I
guess
this
is
more
opinion
now.
Rather
than
fact,
it
doesn't
seem
to
me
that
you
need
a
channel
that
has
the
release
team
and
the
shadows
in
it
that
that's
public,
but
that
you're
using
separately
one
of
those
release
channels
would
be
the
right
place
for
any
any
conversation.
A
That's
you
know.
Unless
it
needs
to
be
in
a
dm,
because
it's
sensitive
in
some
way,
then
then
I
would
put
it
in
one
of
those
channels.
Once
we
pick
one.
D
Yeah,
I
agree
if
I
had
to
give
an
opinion,
I
would
say
that
you
should
go
with
release
docs,
because
you
are
specifically
talking
about
the
release
in
that
regards
and
I
think
that
belongs
more
in
sig
releases
wheelhouse
than
it
does
in
sig
docs.
If
that
makes
sense
functionally
it's
either
or
but
I
I
I
have
always
questioned
the
presence
of
sig
doc's
release,
especially
now
that
a
second
channel
has
appeared.
C
Okay,
I
mean
that
sounds
good
to
me.
I
think,
if
we
deprecate
the
channel,
we
just
need
to
update
the
docs
that
has
that
referenced.
So
I.
D
Need
to
update
the
docs
and
talk
to
steven
augustus,
because
he
will
know
what
yaml
files
you
need
to
edit
to
actually
formally
archive
the
channel.
A
So
it
sounds
like
we're
reaching
against
consensus
here
and
it's
on
well.
Celeste
is
selecting
release
docs
now.
Does
anyone
wish
to
put
forward
a
conflicting
suggestion
and
like
propose
keeping
syndox
releases,
the
main
channel?
Here's
your
opportunity.
A
Okay,
I
think
we're
picking
release
docs,
I'm
going
to
put
that
in
the
agenda:
google,
doc.
A
A
From
me,
I
suggest
we
park
the
access
control
and
come
back
to
it.
The
the
pull
request
about
adding
access.
A
Yeah
there's
a
the
next
item
is
about
chair
transition.
We
might
have
more
chairs
on
the
call
soon.
A
So
chad
transaction
transition,
zach
becomes
emeritus
on
september,
the
15th
nominates
irve
to
replace
him.
This
is
a
bit
of
process.
E
Yeah,
so
there's
no
action
item
for
this,
and
actually
he
asked
if
in
advance,
contributing
to
become
a
chairs.
It's
mentions
that
one
should
be
at
least
one
really
sleek
one
time
release
lead
or
two
time
shadows
for
the
dogs,
and
he
said
he
want
to
discuss
more
about
this
letter,
but
I'm
not
sure
because
he
is
still
on
vacations
and
probably
we
will
discuss
it
later
when
he
back.
D
E
I
already
knew
about
about
it.
Actually,
he
he
mentions
the
advanced,
contributing
rules
about
becoming
a
chairs.
F
A
So
I'm
not
sure
we
have
lazy
consensus
and
unfortunately,
jim
angel,
kevin,
barnett
and
zac
are
not
on
this
call.
A
So
I'm
happy
to
be
the
sort
of
interim
chair
and
stepping
up,
but
I
don't
know
exactly
what
process
to
follow.
Anyone
got
any
guidance.
D
G
D
A
Okay,
thanks
for
bearing
with
me
on
that
people,
let's
go
back
to
the
access
control
question
then,
because
I
was
hoping
this
would
be
a
bit
easier,
but
anna
you've
asked
for
access.
A
A
Okay,
sorry
about
the
bureaucracy.
These
things
are
important,
but
also
boring.
Let's
talk
about
pull
requests
and
issues
celeste.
D
Okay,
so
I'm
gonna
go
through
these
real
quick,
because
I
think
we've
got
some
bigger
talks
coming
up
so
the
first
one
is
one
of
tim's
pull
requests.
That's
been
sitting
for
a
while.
This
is
an
implementation
change
in
how
we
bring
in
the
cncf
landscape
on
pages
like
the
training
and
the
partner
pages
I've,
given
it.
That
looks
good
to
me,
because
it
does
look
good
to
me,
but
I
do
need
somebody
who
has
a
bit
of
web
chops
to
give
it
the
approve.
D
It
needs
a
second
pair
of
eyes.
That's
all
on
that
one
and
as
for
the
second
pull
request,
I
need
help
reviewing
this,
so
the
story
is,
as
I
was
going
through
my
large
pr
of
removing
extraneous
files
from
the
website
over
the
past
few
months.
One
of
the
net
results
that
came
through
was
the
case.
Study
pages
are
super
tangly
and
super
difficult
to
maintain
and
have
a
lot
of
custom
css
that
doesn't
need
to
be
there.
D
So
I
wrote
a
small
issue
on
how
we
could
potentially
optimize
those
with
the
full
intent
that
I
was
probably
going
to
be
the
one
who
actually
went
ahead
and
implemented
it,
and
then
we
got
a
lovely
contributor
who
went
ahead
and
implemented
it
for
me
or
solved
some
slash.
All
of
these.
D
This
is
a
really
big
pr.
I
do
not
personally
feel
sorry
you're,
muted,.
A
D
This
is
it's
a
wonk
and
walking
big
pr,
because
it
has
to
change
files
in
almost
all
the
case,
studies
specifically
to
remove
things
like
custom,
css
or
inline
css.
D
This
is
a
really
big
pr,
I'm
not
sure
I'm
equipped
to
review
this
alone,
and
I
would
really
appreciate
a
second
pair
of
eyes
on
this,
because
I
have
been
afraid
of
reviewing
it,
and
I
think
we
also
need
to
discuss
whether
this
is
the
approach
is
the
right
approach
or
just
in
general,
long
story
short.
Please
take
a
look
at
this
and
that's
all
I
really
have
to
say
thank
you
for
changing.
A
So,
on
the
second
one,
this
one
improve
maintainability
of
case
studies.
This
is
kind
of
like
a
call
for
advice
and
help
celeste.
I
think.
E
A
A
Oh
yeah,
this
is
the
so
I
I've
switched
back
to
pr1
and
no
I
don't
want
that
url.
I
want.
A
I'm
going
to
show
the
original
and
I'm
going
to
show
the
the
preview
deploy
preview.
Thank
you
thanks.
Everyone
for
bearing
with
me
this
here's.
The
original
here
is
the
deploy
preview,
that's
slightly
different
because
it
was
kubecon
when
the
deploy
preview
preview
rendered.
A
I'm
going
to
ask
the
meeting.
Is
everyone
happy
with
me
merging
this
because,
as
an
approver,
I
can
merge
it
and
I'm
happy
for
the
meeting
to
be
this
discussion
right
now
to
be
in
a
chance
for
someone
to
object.
D
So,
on
the
training
and
partners
pages
of
kubernetes
dot
io,
we
have
this
thing
called
the
cncf
landscape,
and
this
is
a
it's
like
a
small
javascript
application
that
somebody
over
in
the
cncf
developed,
which
pulls
in
filtered
information
about
the
different
companies
that
do
cncf
things.
So
on
the
partner
page,
it's
who
are
our
certified
service
provider
partners
that
we're
filtering
for
on
the
training
page.
It's
who
have
we
certified
as
a
trading
partner.
D
And
the
way
the
original
implementation
works
is
it's
very
like
copy
and
paste,
and
what
tim's
change
does
is
parameterize
it
a
little
bit
so
that,
when
we're
pulling
into
hugo,
we
don't
have
to
pull
in
the
scripts
every
single
time
we
can
just
say
and
now
display
a
cncf
landscape
with
given
these
parameters,
so
it
just
it
cleans
up.
A
little
bit
of
our
code
brings
in
a
little
less
javascript
great.
A
You
can
see
that
we
basically
the
there's
a
shortcut
I
had
on
screen
and
now
with
a
few
bits
of
html5
data
attributes.
You
drop
the
javascript
and
you
put
this
in
and
that's
merged
thanks
very
much
thanks
for
bringing
that
up.
Celeste.
A
Let's
talk
about
localization
great,
so
I'm
going
to
throw
another
tab
over
here.
F
A
F
So
irvi
does
this
make
sense.
I
mean
that's
how
I
viewed
it
and
if
you
read
the
comments,
hopefully
that
will
will
reinforce
that.
F
So
yeah
yeah
there
it
is
right
there,
jim
angel
zachary
sailor.
Maybe
a
subgroup
would
be
better,
so
the
action
I
previously
was
zac
had
set
up
a
slack
channel.
It
was
a
good
day
and
I
voluntold
myself
to
go
ahead
and
be
the
subgroup
chair,
because
nobody
else
wanted
it.
F
I
I
tried
to
put
it
on
somebody
else
and
that
didn't
work,
so
I'm
happy
to
to
lead
it
and
drive
it,
and
so
the
first
thing
I
did
is
kind
of
the
next
part
of
this
was
to
put
together
a
mission
statement
and
see
if
everybody
liked
the
mission
statement
see
if
it
captured
what
we
thought
the
subgroup
was
going
to
do
and
then,
if,
if
the
mission
statement
is
good,
I
think
irvy's
going
to
help
me
to
to
help
pick
a
meeting
time
that
works
for
people
and
get
it
calendared.
F
And
then
I
would
be
happy
to
drive
the
work
irving.
Does
that
make
sense.
F
A
Thanks
for
the
update
brad,
that's
clarified
what
what's
going
on?
I've
tidied
the
agenda
up
a
bit.
What
do
you
need
from
today's
meeting.
F
Just
for
people
to
look
at
the
the
the
mission
statement
and
say:
yes,
this
is
pretty
much
the
scope
of
what
we
wanted,
the
subgroup
to
be
or
brad
as
usual.
You
missed
the
mark.
Why
weren't
you
paying
attention?
That's
fine,
too.
I
know
irves
reviewed
it,
but
but
yeah
it
was
really
the
key
was
just
to
have.
F
The
question
for
me
was
how
much
of
this
is
irvi
everybody
building
their
own
localization
document,
putting
in
the
same
place
and
how
much
of
this
is
going
to
be?
Oh,
could
they
all
work
together
on
a
document
that
could
be
used
across
localization
teams?
I
don't
know
how
much
of
each
there's
going
to
be
right.
So
there's
the
con
there's
the
potential
for
reuse
and
commonality
and
common
tools,
and
so,
for
example,
if
one
localization
team
came
up
with
a
great
way
to
identify
changes
and
documents
right
to
say
what
to
translate.
F
We
don't
want
all
the
localization
teams
to
have
to
re
reinvent
that
that
wheel
and
build
their
own.
So
I
think
there
was
going
to
be
a
little
bit
of
that
in
the
subgroup
and
then
obviously
that
the
main
issue
that
you
know
the
localization
contributing
and
maintaining
guides
that
ideally
will
help
the
localization
teams
to
create
in
a
consistent
fashion
everything
you
want
to
add
to
that.
Did
I
miss
anything.
E
Yeah,
actually,
the
first
concern
for
this
subgroup
is.
We
know
that
there
is
several
problems
that
can
be
found
in
several
localizations
team
as
well,
but
the
thing
is
how
we
address
this
kind
of
problems
is
like
for
each
teams.
They
have
their
own
way
to
solve
these
problems.
E
However,
there
is
some
kind
of
pattern
actually
for
for
these
specific
problems,
for
example,
so
I
think
we
can
kind
of
reuse
the
scripts
or
any
tools
that
can
be
used
for
solving
problems
with
specific
patterns
I
mean
like
common
patterns,
but
if,
let's
say
the
problem
is
really
specific
to
the
language
itself
like
then
it's
kind
of
difficult
to.
E
To
use
a
common
sure.
E
Yes-
and
there
is
a
question
of
let's
say
that
a
member
is
actually
inactive
for
a
while,
and
you
know
that
there
will
be
huge
loads
on
approver
that
still
working
on
the
things
here,
but
I'm
not
sure
on
how
the
performance
of
of
this
kind
of
things.
If
let's
say
the
approval,
just
somehow
can
be
contacted
things
like
that.
And
then
the
lots
just
accommodated
on
one
person
or
two-person
things
like
that.
And
it
will
be
kind
of
difficult
to
to
manage
right.
F
And
that,
and
that
too
could
be
different
per
localization
team
right.
If
you
had
a
smaller
team,
you
might
want
to
allow
your
emeritus
folks
more
approvals,
because
you
need
the
extra
help
and
other
localization
teams
may
be
like
well.
No,
if
you
haven't
been
around
for
a
while.
Well,
no
you
can't
approve.
F
A
A
F
Might
be
a
little
too
specific
or
I'm
a
little
worried
if
people
the
word
the
verb
toil
or
the
word
toil.
If
that
noise.
A
A
So
are
people
broadly
happy
with
the
the
draft
that
brad's
put
forward,
which
is
like
bar
one?
Small
change
is,
as
it
was
originally.
F
So
so
next
steps
irby
I'm
going
to
work
with
you
since
you,
you
know
a
lot
of
the
the
localization
teams
and
a
lot
of
experience,
and
hopefully
together
we
can
get
this
kicked
off
and
find.
I
guess
the
challenge
was,
you
know:
do
we
want
to
do
like
two
meetings
a
month
where
one
is
got
a
time,
that's
friendly
to
european
and
one
that's
got
a
time
that's
friendly
to
asian.
F
Luckily
I
don't
sleep
much
and
I
have
horrible
sleep
habits,
so
I
can
actually,
even
though
I'm
eastern
standard,
I
can
do
horribly
horribly
difficult
times
pretty
easily.
You
know
midnights
and
what-have-yous.
So
so
I
think
irving.
Our
next
step
is
to
try
and
figure
that
out
right
to
just
figure
out
who
wants
to
participate
in
the
subgroup
and
and
then
to
jointly
try
and
figure
out
times
that
work
for
both
of
us.
E
Okay,
sure,
but
the
thing
is
probably
we
can
announce
it
in
the
selectional
force
and
looks
who
defaults
that
will
be
interested
in
in
joining
these
subgroups
as
well.
F
A
Okay,
thanks
very
much
that
sounds
really
promising
and
localization
is
really
important.
It's
a
it's!
A
key
goal
of
the
clown
native
computing
foundation
to
include
people.
Localization
is
a
big
part
of
that.
A
So
on
to
process
public
service
announcement
here
on
the
september
27th
zuma
rolling
out
a
change
to
how
groups
are
authenticated
and
rooms
are
often
authenticated.
We
sigdocs
will
need
to
update
the
zoom
call
that
we
use
for
the
weekly
meeting
to
add
a
password.
A
We
are
using,
don't
tell
anyone,
it's
very
secret,
seven,
seven,
seven,
seven,
seven,
five
sevens
and
we'll
put
this
in
in
slack
and
so
on.
We've
had
very
little
zoom
bombing,
we're
we're
not
making
these
channels
super
public
and
we'll
revise
that
if
there
is
a
problem,
but
at
the
moment
that's
what
we're
gonna
do
yeah
also
yeah,
please
help
out
anyone
that
you
see
confused
about
the
new
passcode.
A
Okay,
next
item
kubecon
talks,
etc.
Ervy
you
and
I
have
said
that
we
will
do
some
talks
for
kubecon.
E
A
I
have
to
confess
I've
not
put
any
time
into
that.
So
far,
do
you
have
a?
I
don't
know
if
you've
made
a
start
already.
E
No,
no,
I
I
have
under
that,
because
I'm
still
confused
on
what
kind
of
talks
that
we
will
give
to
people
here.
So
probably
we
can
create
a
skeleton
for
for
this
force
and
then
we
can
put
any
material
that
we
want
to
bring
up.
A
Okay,
well,
I
guess
action
on
me
and
ervy
to
actually
do
something
on
this,
I'm
just
making
it
visible
that
we
haven't
really.
F
So
tim
is
this
different
than
where
we
get
together.
The
thing
that
zach
sent
out
or
were
five
of
us,
do
like
the
new
contributor
days,
it's
a
different
thing
than
that
or
the
same
thing.
E
Not
really
oh
yeah,
I
have
questions
about
celeste
ideas
of
getting
101
introductions
about
technical
writings.
So
do
we
want
to
put
that
in
the
session
as
well.
E
Okay,
so
my
question
is:
do
we
still
plan
to
put
the
introductions
on
technical
writing
on
the
session
as
well?
What's.
D
Our
the
answer
to
that
is,
if
you'd
like
it,
then
I
would
happily
be
able
to
give
some
time
to
that
and
to
do
that.
Do
you
what's
the
plan
for
our
time
slot
so
far,
guys.
E
E
F
I
mean:
is
this
the
one
where
we
have
like
a
half
day
session?
I
guess
that's.
What
was
kind
of
my
question.
I
didn't
know
if
you
were
doing
a
separate
talk,
you
were
doing
the
oh,
the
things
we
typically
do
at
the
conference,
which
is
like
a
half
day
session.
Where
we
do
an
introduction
to
kubernetes,
I
mean
had
an
introduction
to
the
docs
rather
and
how
to
be
a
contributor,
and
then
celeste
was
going
to
talk
about.
F
We
were
going
to
sneak
in
some
pay
that
how
to
be
how
to
be
a
technical
writer.
We
were
going
to
make
that
part
of
the
agenda.
Are
we
all
talking
about
the
same
thing
or
a
different
thing?
I'm
just
kind
of
confused.
D
Me
too
me
too,
and
I
wonder
if
that's
the
key
thing
that
we
actually
need
to
figure
out
right
now,
okay,
so
we
have
a
time
slot
at
coupon.
F
D
D
Hi
so
kubernetes.dev
exists
the
sig
controbex
kind
of
stood
up
a
site
that
should,
in
theory,
be
the
portal
to
all
things
contributor
for
kubernetes,
and
there
is
a
question
around
how
we
want
to
link
and
get
and
integrate
this
in
with
the
main
kubernetes.I
o
site.
D
The
main
question
I
have
is
from
sig
contrerbex's
perspective.
It
would
be
an
outright
replacement
of
kubernetes
dot
io
community,
and
are
we
okay
with
that
nobody's
touched
that
page
for
for
a
while?
Now
also.
A
I
think
this
we
should
split
this
into
into
two
questions,
a
few
different
questions
and
then
and
then
try
and
answer
those
okay.
One
question
is:
are
we
maintaining
the
existing
community
page?
Well,
that's
one
question:
I'm
gonna
put
these
in
the
chat
actually.
D
Yeah,
so
I
think,
okay,
so
just
to
before
I
answer
or
address
your
v's
question,
it
does
not
look
like
this
site
has
been,
or
this
page
has
been
meaningfully
updated.
D
Since
I
want
to
say
before
we
converted
to
hugo
there's
been
minor
updates
through
2018
and
2019,
but
they're
they're
like
fixed
capitalization
level,
minor
updates.
So
I
think
the
answer
of
are
we
meaningfully
maintaining.
This
is
no.
C
D
Yeah
yeah,
but
I
still
I
still
kind
of.
D
Doubt
I
think
the
thing
that
that
would
be
most
meaningfully
missing
that
wouldn't
eventually
find
its
time
on
kubernetes.dev,
because
I
know
that
they
have
a
new
meetups
calendar.
They
have
a
new
events,
slash
community
community
meetings
calendar.
I
imagine
they've
got
like
the
github
link
is
literally
just
a
link
to
kubernetes
kubernetes,
and
I
know
that
they're
trying
to
de-emphasize
stack
overflow
because
nobody
involved
in
the
project
truly
takes
ownership
of
stack
overflow.
So
I
think
the
thing
that
would
be
meaningfully
missing.
D
There
is
a
link
to
the
code
of
conduct
if
we
were
to
do
an
outright
replacement,
but
I
know
I
think,
talking
to
bob
killen,
who
was
the
one
who
stood
up
kubernetes.dab.
D
D
Moreover,
it's
how
I'm
not
a
fan
of
like
spinning
up
separate
sites
for
every
little
hope
and
dream
in
this
case,
I
think
it
might
make
sense,
I'm
not
a
fan
of
their
domain
name,
because
I
think
it's
confusing
for
somebody
who
isn't
a
contributor
to
know
which
one's
the
docs
and
which
one's
this
contributor
site
like.
D
I
think
that
was
a
really
bad
move,
and
I
wish
they
would
have
consulted
us,
and
I
think
that
they're,
if
we
have
two
kind
of
large
web
presences,
now
it
becomes
a
question
of
what
is
the
kubernetes
website
maintenance
group
rather
than
the
docs
maintenance
versus
the
community
maintenance
like.
I
think
we
need
to
be
a
bit
more
like
that,
specifically
for
web
maintenance.
Stuff.
A
Well,
we've
got
15
minutes.
I
actually
thought
we'd
get
through
this
before
the
the
the
hours
up,
but
I
think
this
is
important
to
talk
about
and
we
may
need
to
come
back
to
it
at
a
future
weekly
meeting
yeah.
So
we've
got
a
point
from
celeste
over.
You
asked
a
question
and
then
I
didn't
capture
it.
So
please,
if
you've
got
access
to
the
agenda
type
it
in
again.
I'm
very
sorry
that
I
I
missed
it.
E
Okay,
so
I'm
asking
about
the
maintenance
of
the
website,
the
new
website
of
kubernetes.dev.
We
will
maintain
it
and
because
I
know
that
we
have
two
separate
website,
then
the
main
dynamics
will
kind
of
need
to
be
taken
care
of
sort
of.
D
Yeah,
my
understanding
is
that
sig
contrubax
will
ensure
the
freshness
of
that
content.
It
contributes
content.
What
concerns
me
is
the
website
maintenance
aspect
of
it
because
I
know
like
hugo
and
doxie
are
not
bob
killen's
kind
of
bread
and
butter.
So
that's
what
concerns
me
about
that
website
is
the
actual
website.
A
So
I
think
this
is
a
different
point
on
a
spectrum,
so
what
we
we've
got,
I
I
guess
we've
got
special
interest
groups
that
engage
sort
of
with
with
sig
docs,
but
leave
content
maintenance
to
us
a
lot
so
most
of
the
technical
sigs
are
kind
of.
A
This
is
going
to
sound
a
bit
a
bit
brutal,
but
I'm
going
to
say
that
you
know
you
do
get
features
that
land
as
ga
and
then
we
mentioned.
Oh,
should
you
know?
Can
we
have
some
documentation
for
this
and
it's
a
bit
of
a
surprise
for
the
special
interest
group
that
this
is
a
thing
that
you
need
to
do
that
happens.
A
Some
s6
are
really
proactive
at
adding
documentation
like
cluster
life
cycle,
really
engages
with
sig
docs
and
sort
of
takes
ownership
of
technical
reviews
for
their
content,
and
then
I'm
I
see
this
as
contrabex
being
a
different
part
of
the
spectrum
where
they're
actually
they're
owning
it
strongly,
but
we've
not
been
involved.
D
Yeah,
I
would
say
so
they
are
in
general,
very
good
about
maintaining
their
content,
and
this
is
a
an
exercise
in
making
sure
that
everything's
not
in
a
git
repo,
because
that's
not
super
beginner
friendly.
D
A
So
I
want
to
walk
through
the
questions
that
are
up
there.
Now
we've
got
a
set
of
questions,
let's
try
and
come
up
with
as
many
answers
as
we
can
in
the
time
we've
got.
A
A
Well,
I
think
that's
a
different
question.
It's
a
valid
question,
but
this
page
are
we
maintaining
it?
Well.
Do
people
want
to
say
that
it's
you
know
it's
it's
valid,
it's
stale!
What.
A
A
B
What
this?
If
this
is.
B
If
it
jumps
out
or
if
it's
something
that
feels
more
like
this
is
just
the
audience
seems
geared
more
towards
developers,
at
least
the
existing
site.
A
F
A
So
I,
what
worries
me
about
redirecting
community
to
kubernetes.dev
is
where
do
we
put
links
to
makeup
meetups?
Where
do
we
say
here
here
is
a
conference
that
you
can
go
to
if
all
you
want
to
do
is
meet
other
people
who
use
kubernetes
and
have
never
committed
a
line
of
code
to
it?
F
So
I
think
you're
saying
that
that
would
be
the
home,
for
is
what
you're
saying
the
kubernetes.dev
for,
from
the
doc
point
of
view,
we
you're
saying
we
ought
to
do
more
to
exploit
using
that
to
create
our
virtual
community
of
people.
Our
outreach
programs
for
docs.
A
It's
not
quite
contributor
experience,
because
not
all
the
community
is
contributing,
it's
not
documentation,
because
this
isn't
about
documentation.
Maybe
there's
a
I
don't.
I
don't
know
all
the
six,
maybe
there's
a
cigarette
activity
that
is
more
about
that
kind
of
community
outreach
that
that
I'm
not
aware
of.
D
D
Yeah,
I
would,
I
think,
I
think,
that's
at
this
level-
that's
appropriate,
I'm
the
appropriate
person
to
do
it.
I
think
your
concern
is
valid
tim
about,
for
example,
kubernetes
community
stuff.
That
is
not
necessarily
the
contributor
community,
so
kind
of
driving
back
to
the
practical.
What
are
we
going
to
do
with
this
new
site
question.
A
A
D
D
A
So
we
don't
even
have
to
worry
about
localizing
it
fantastic
over
your
question:
how
is
the
new
kubernetes
dev
maintained.
E
E
I
think
it
should
be
contributes
right,
but
there
is
several
things
that
still
attach
in
in
in
the
documentations
part
like
code
of
conduct
and
stuff,
so
how
we
will
maintain
that
kind
of
things
because
seems
like
there's
two
different
websites
with
different
purpose.
Yet
there
are
still
overlapping
components
on
both
websites.
C
I
don't
think
this
is
a
conversation
that
we
can
answer.
Isn't
that
like
it
don't
we
have
to
talk
to
the
contribute?
I'm
sorry
I
forget
the
name
there
who
maintains
this
website
contributor
experience.
Contributor
experience.
Yes,
I
don't
know
if
that's
like
something
that,
like
people
from
here,
need
to
attend
their
meeting
or
like
we
can
ask
them
to
join
our
meeting
or,
if
there's
a
meeting
somewhere
that
people
can
just
talk.
C
I
guess
I
don't
know,
I
think
that's
a
good
solution
just
to
talk
about
all
the
concerns
that
rv
and
celeste
brought.
A
A
D
A
And
I
think
one
question
that
we
should
is
really
a
question
that
maybe
you'll
take
to
that
discussion.
Celeste
is
how
does
this
fit
in,
with
the
contribute
page
that
we
have
specifically
about
documentation.
D
D
Yeah,
so
I
think
I
think,
at
least
from
my
perspective
right
now,
but
perhaps
that
will
change
my
mind.
Is
each
sig
owns
its
own
contribution
guidelines,
so
I
think
it
falls
under
that
these
are
kubernetes
docs
contribution
guidelines
and
we
own
them
and
can
disperse
them.
However,
we
please,
I
know,
I
know-
and
I
raised
this
issue
when
they
when
they
launched
their
their
website.
I
was
like
okay,
cool
we're.
Gonna,
give
people
two
different
ways
of
kind
of
becoming
a
first
contributor,
but
I
think
that
particularly
for
sig
docs
as
well.
A
I
guess
I'll
relate
to
my
experience,
which
was
when
I
noticed
this
website
I
saw
you
know
like
this
is
a
little
bit
like
a
bias,
so
there's
a
contribute
section
right
in
the
to
the
docs.
Not
you
know,
contribute
just.
E
A
The
kubelet
or
whatever
yeah
or
the
cli-
and
I
thought
I
I
know-
what's
happened
there
like
the
docs
sig
owns
this
page,
so
it
tells
you
how
to
contribute
to
docs.
A
So
I
think
actually,
this
new
new
site
is,
is
going
to
help
address
that
balance
where
at
the
moment,
new
contributors
are
driven
to
contribute
to
the
docks
rather
than
you
know,
there
are
many
places
where
people
contribute.
So
I
think
this
is
a
positive
thing.
That's
that's
my
view.
D
No,
I
agree,
I
think
it's
a
positive
thing
as
well.
I,
but
again
I
think,
sig
docs
is
we're
always
a
bit
different
than
a
lot
of
the
other
stakes,
because
we
aren't
necessarily
a
code
zig
dldr
pause,
and
let
me
let
me
format
that
opinion
a
bit
further.
A
C
I
have
one
day
so.
A
A
C
A
A
Points
that
oh
there's
something
in
the
chat,
let
me
just
check
oh
hello,
rgh,
who's
that
welcome
to
sigdocs
and
that's
a
sig
meeting.
People.