►
From YouTube: K8s SIG Docs Meeting for 20201020
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
October
20th-
and
it
looks
like
all
familiar
faces,
joining
us
here,
so
welcome
back
so
moving
on
this
week's
pr
wrangler
is
karen
bradshaw
or
kb
hockey
on
github
and
next
week
it
is
caitlin,
bernard
and
approvers.
Make
sure
you
know
your
scheduled
pr
wrangling
shifts
which
are
linked
in
the
agenda.
A
C
I
will
this
is
ray.
Our
current
status
is
green,
so
the
dev
1.20
branch
was
synced
with
master.
Also,
the
dev
1.20
branch
is
healthy.
As
for
docs
pr
stats,
we
are
currently
tracking
seven
docs
three
are
merged,
three
are
ready
for
review
and
one
is
in
draft
work
in
progress.
C
A
Awesome
thanks
ray
and
I've
seen
a
ton
of
activity
on
the
docs
release
channel
too,
and
I
think
you're
you're
doing
a
great
job
of
keeping
everyone
informed
and
I'd
see
all
the
activity.
And
it's
really
awesome
to
see
the
the
docs
evolving
to
somewhat
of
a
well-oiled
machine.
You
know
before
it
wasn't
necessarily
as
smooth
of
a
process
and
I
feel
like
we're
starting
to
get
some
some
sort
of
standards
and
it's
definitely
awesome
to
see.
A
A
A
A
A
One
thing
I
did
want
to
mention
is
that
I
did
create
the
calendar,
invite
for
that,
and
I
shared
it
out
with
the
sig
docs
mailing
list.
So
folks
are
interested
in
joining
the
localization
working
group.
They
meet
mondays
the
first
monday
of
the
month
and
you
can
get
that
invite
by
joining
the
sig
docs
google
group.
You
should
get
that
invite
then
all
right
moving
on
to
issues
and
pr's,
I
see
nothing
listed.
Does
anybody
have
any
issues
or
pr's?
They
would
like
to
raise
awareness
on.
A
B
B
So
let
me
share
the
current
status,
which
is
that
I'm
I'm
rendering
it
into
mpeg-4
version,
because
I
did
it
in
webm,
but
it's
edited
and
it's
ready
to
go.
A
D
B
F
A
Absolutely
I
will
take
a
look
at
that
and
give
it
a
quick
review
after
this
call
appreciate
the
awareness.
A
Yeah,
thank
you
all
right.
Moving
on
there,
just
some
general
reminders
in
housekeeping
here
is
we
canceled
the
11th
november.
The
third
meeting
for
the
election
I'll
probably
remind
folks,
as
we
near
that
date.
Just
so,
you
know
folks
know
what's
going
on
as
we
you
know,
draw
near
to
the
u.s
election
and
then
the
q4
quarterly
planning
dates
was
moved.
So
previously
it
was
on
the
thursday.
It
was
moved
to
this
wednesday
that
is
october
21st
at
5
pm,
pacific.
A
So
folks
are
interested
in
joining
the
quarterly
planning
talking
about
quarterly
objectives
and
more
long-term
objectives.
In
reviewing
some
of
the
successes
we've
had
in
q3
and
encouraged
to
join
that
meeting,
as
well
as
in
the
agenda.
There's
an
agenda
doc
linked
so
in
this
in
the
weekly
sig
docs
meeting.
There's
an
agenda
for
the
quarterly
planning
meeting,
doc
link
there
in
the
in
the
bulleted
item,
and
if
you
have
anything
you'd
like
to
discuss,
it,
doesn't
have
to
be
anything
that
previously
existed.
A
A
Let's
say
you
know,
css
improvements,
javascript
improvements,
just
the
way,
the
site
loads
and
performs
that's
something
you
can
just
kind
of
throw
out
in
the
wild
and
maybe
you're
not
willing
to
work
on
that,
and
maybe
you
want
to
see
if
others
are
interested
in
teaming
up
and
working
on,
that
the
quarterly
planning
is
a
great
time
to
get
feedback
and
figure
out.
You
know
who's
willing
to
own
what
and
at
what
capacity,
and
if
it's
a
you
know
an
item
that
we'd
like
to
move
forward
at
a
wider.
A
D
Sure
so
hi
everyone
hope
everyone's
doing
good,
so
sick
security
met
the
second
time
yesterday
and
one
of
the
sub
project
focuses
six
security
docs,
and
I
remember
that
saying
doc.
D
Security
used
to
be
a
part
of
sick
dogs
back
then-
and
I
think
the
new
home
is
security
now
and
predominantly
it
can
address
certain
guidelines
and
hardening
guide
and
vulnerability
reports
we
met
for
the
first
time
there
was
a
breakout
group
room
yesterday
and
there
were
like
three
to
four
volunteers
met
for
the
first
time
yesterday
we
are
still
figuring
out
the
plan
and
the
goals
and
stuff
like
that.
D
So
this
is
just
like
a
very
initial
update
that
the
projects
sub
projects
gonna,
be
it's
getting
kicked
off.
So,
yes,
I
and
I
volunteered
to
co-lead
the
sub
project
now
and
looking
for
more
volunteers
and
input
and
opinions
feedback.
Anything
is
welcome.
D
A
A
D
I
will
once
I
have
everything
I'll
come
back
with
a
whole,
all
the
links
and
stuff
like
that,
but
this
is
to
save
initial
update.
D
So,
for
now
there
is
a
security
channel
and
I
am
working
on
getting
a
separate
slack
channel
and
I
am
also
going
to
work
on
getting
a
meeting
set
up
once
a
month,
so
we
are
planning
to
meet
once
a
month
and
work
asynchronously.
D
There
is
gonna,
be
six
security
meeting
twice
a
month.
I
think
and
we'll
report
there,
and
I
also
want
to
make
sure
some
of
the
big
updates
are
conveyed
to
sick
dogs
groups
as
well.
So
whenever
something
is
big,
I
will
update
but
the
to
answer
your
questions.
I'm
sorry,
I
just
diverged
a
little
bit.
Yes,
channel's
gonna
come
up
and
there's
gonna
be
a
meeting
soon.
D
So
once
I
have
all
those
things
I'll
come
back
here
with
the
information,
I
don't
have
anything
yet,
and
there
is
also
some
logistics
issue
that
we
are
trying
to
figure
out
if
we're
gonna
use
the
same
security
dock,
google
doc
for
all
the
sub
projects
or
there's
gonna,
be
a
separate
google
doc
for
sub
project
stuff.
D
The
previous
one
is
sick
dogs,
security.
It
comes
under
sick
dogs,
I
think,
and
the
new
one
is
going
to
be
security
docs.
It
comes
under
the
security
project,
so
it's
going
to
be
a
new
channel.
D
B
If
there's
a,
if
there
is
a
six
doc
security
channel,
even
an
archived
one,
I
would
be
tempted
to
unarchive
it
mention
the
new
channel
and
archive
it
again.
A
Awesome
yeah
now
I
would
completely
agree
with
that:
let's
archive
the
sig
doc
security
slack
channel
and
create
the
one
that's
security
docs,
I
know
somewhat
confusing,
but
to
give
context
for
folks
in
this
call.
Originally,
the
idea
was
pitched.
I
believe
it
was
at
a
quarterly
meeting
saying
we
want
to
have
a
subgroup
or
a
working
group
focused
on
improving
the
security
aspect
of
documentation,
so
naturally
that
working
group
or
that
subproject
got
created
underneath
sig
docs
is
kind
of
a
overarching
stig
representing
the
sig
doc
security.
A
There
is
a
good
amount
of
meetings,
but
ultimately,
the
leader
of
that
initiative
had
to
step
down
and
some
folks
kind
of
stepped
up
and
rotated
through
that
leadership
role
and
said
doc,
security.
But
ultimately
it
didn't
have
the
driving
force
needed
to
maintain
that
consistency
and
to
drive
to
any
sort
of
completion.
A
So
I'm
hoping
that
the
sig
security
docs,
the
sig
security,
overarching
documentation
effort
has
a
little
bit
more
staying
power
and
folks
who
are
getting
involved
and
helping
out
there.
One
thing
I
can
do
savita
also
is
share
the
old,
sig
doc
security
document
that
I
have
just
to
see
it
might
help.
It
might
not
feel
free
to
take
a
look
at
that
and
I
will
send
it
over
your
way.
D
Thank
you.
That
would
definitely
help
me.
I
was
gonna
anyways
ask
because
I
was
searching
for
the
channel
and
I
remember
that
it
got
archived
like
a
few
months.
I
don't
even
remember
how
many
months
ago-
and
I
could
never
make
it
to
that
meeting,
because
it
was
complaining
with
something.
So
I
never
had
a
background
on
what
was
happening
in
that
particular
project
then
so
it
would
really
be
helpful.
A
You
know-
and
I
think
part
of
that
was
due
to
the
the
folks
who
were
involved
as
far
as
just
you
know,
having
that
leadership
to
be
able
to
drive
that,
I
think
is
really
what
what
it
needed
to
drive
forward
so
definitely
share
that
out
with
you
and
then,
as
far
as
creating
the
calendar
invite
I
know
for
sig
docs.
We
recently
consolidated
down
to
a
shared
calendar
that
we
create
all
of
our
events
from
so
some
of
that
chatty.
A
So
I
would
recommend
that
before
creating
the
own
calendar,
invite
you
might
want
to
reach
out
to
sig
security
and
see
if
they
have
a
shared
calendar,
they
want
to
consolidate
their
meetings,
the
reason
being
or
the
reason
why
that'd
be
beneficial
is
it
makes
it
simple
to
transition
to
other
leaders.
It
makes
it
a
little
bit
more
clear
to
share
out
the
other
tech
leads
et
cetera,
et
cetera,
so
general
consolidation,
where
we
can
and
simplification,
hopefully
along
the
lines.