►
From YouTube: K8s SIG Docs meeting for 20220809
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
A
few
housekeeping
items
too,
we
do
buy
it
by
the
scene,
staff
code
of
conduct,
which
boils
down
to
just
to
be
kind
and
excellent
to
each
other
as
well,
and
this
meeting
is
being
recorded
and
uploaded
to
YouTube.
So
if
you
do
not
want
to
be
on
camera,
please
turn
off
your
camera
as
well,
and
also
be.
Please
be
mindful
what
you
say
all
right.
So,
let's
just
go
down
the
list
here
on
the
agenda
I'll
place
the
link
to
the
agenda
on
the
zoom
chats.
B
Junior
at
the
University
of
London
and
I
am
tinkering
with
electronics
and
computer
from
Early
Childhood,
apart
from
Tech
I
have
five
plus
years
of
trading
experience
in
crypto,
Equity
Forex
and
more
I,
recently
interned
at
TPS,
Munich
and
currently
working
with
MRH
fellowship
with
their
company
Partners
sonala
labs
and
I.
Am
volunteering
at
the
code
path.org
as
a
mentor
and
have
mentored
at
the
open
source
program
called
she
code,
Africa.
A
All
right,
if
you
have
any
questions,
feel
free
as
well
to
reach
out
on
slack
on
the
sick,
dog
Channel
or
just
to
bring
up
any
topics
at
the
end
at
the
end
of
the
towards
our
open
discussion
here,
all
right.
Anyone
else,
if
everyone's
fairly
yeah,
very
pretty
familiar
with
Sig
docs,
all
right,
updates
reminders.
This
week's
PR
WR
Wrangler
is
is
Anna
Jung.
A
So
if
you
have
any
PRS
that
you
would
like
to
be
reviewed,
please
reach
out
to
Anna
next
week's
PR
Wrangler
is
Brad
topple
with
Amman
Seraph
Shadow
and
for
previous,
please
look
at
the
pr
Wrangler
shifts,
so
they
have
been
updated
till
the
end
of
the
year.
So
please
take
a
look
at
that
see
a
check
to
see
when
you
are
regularly
all
right.
First
topic
on
agenda
is
the
release
updates
to
release.
125
is
coming
to
a
close
in
a
few
weeks.
A
Don't
see
any
Dark
Shadows
on
the
call,
so
I'll
give
the
updates
I
posted
this
update
as
well,
and
the
current
status
is
green.
There
is
a
PR
open
to
sync
the
Bain
Branch,
with
Dev
125..
There's
a
few
errors
in
it,
so
I'm
going
to
take
a
look
at
it,
see
make
sure
that
they
that
they
have
been
fixed.
A
Currently
today
is
a
big
day.
It's
the
docs
ready
for
review
deadline
is
today
is
by
end
of
day
we're
tracking
40
40
enhancements,
31
PR
you're,
ready
for
review
four
docs
PRS
have
already
merged
two
are
are
in
draft
and
one
it
has
a
no
PR
so
that
one
node
PR
I've
already
reached
out
to
ask
for
PR.
If
worst
case
scenario,
we
do
not
get
a
PR,
the
minimum
that
it
needs
just
a
feature.
A
State
update,
so
I'll
make
that
PR
later
this
afternoon,
if
that
has
not
been
created,
the
pr
authors
for
those
two
in
draft
have
been,
and
we've
already
reached
out
on
GitHub
and
we'll
also
reach
out
on
a
slack
to
get
those
updated.
A
C
Hello,
hello,
hello,
so
we
have
16
feature
blogs
being
tracked
right
now
one
of
them
might
get
bumped,
but
that's
okay,
I
think
we
can.
We
can
technically
replace
it
with
an
article,
that's
coming
out
on
the
history
of
or
well
the
historical
context
of
PSP,
which
is
being
written
by
maheb
right.
That's
you
nice.
C
Anyway.
That's
a
decent
number
of
feature
blogs
in
general,
the
shadows
for
the
comms
team
and
myself
are
deciding
this
week.
What
order
they're
going
to
go
in
and
then
bothering
the
respective
authors
with
like
their
specific
launch
date
and
also
when
they
need
to
hard
deadline,
have
a
draft
in
for
review,
but
I
wanted
to
get
with
Sig
docs
to
see
if
y'all
had
any
opinions
as
well
on
like
what
definitely
needs
to
come
out
the
week
immediately
after
release.
C
The
spreadsheet
is
here,
drop
it
in
the
zoom
chat,
and
this
is
not
like
a
pressing,
oh
yeah.
There
we
go.
Thank
you.
This
is
not
like
a
super
pressing
concern.
Just
I
I
wanted
your
opinion
too
and
I'm
trying
to
make
this
like
very
transparent
for
the
Shadows.
So
they
understand
how
to
do
this
next
release,
or
rather
when
I'm
not
there,
so
any
opinions
on
which
of
these
like
hard
need
to
come
out
week.
One.
A
My
personal
opinion-
and
this
is
release
hat
on
as
well-
is
anything
tied
with
the
major
theme
is,
is
like
so
like
the
Pod
security
Mission.
The
historical
context
of
the
PSP
as
well
I
would
actually
see
those
like
back
to
back
if
possible.
Like
you
know,
historical
PSP,
then,
maybe
next
day
the
Pod
screen
Mission
just.
D
B
A
It
kind
of
makes
sense
to
kind
of,
like
you
know,
kind
of
I
don't
know
just
make
them
logical.
Like
ordered
I
know
there
are
some
blog
reviewers
on
here
as
well.
If
you
want
to
add
in
your
inputs.
E
Sorry
fumbling
for
the
mute
button
I'd
give
it
a
plus
one
on
that
anything
anything
anything
matching.
The
theme
is
obviously
wanting
to
get
out
real,
quick
and
then
I'm.
A
fan
of
the
history,
stuff
and
I
think
that
it
is
more
interesting
earlier
in
the
schedule
than
later.
Okay,
so
I
would
I
would
request.
One
raise
content
or
comment
set
are.
A
Because
I
would
prefer
to
do
that.
Okay,
totally
fine
with
that
too
totally
fine,
yeah,
yeah
well
I
wasn't
sure
where
it
was
if
it
was
going
to
be
after
release
but
I'm,
actually
in
favor
of
that
actually.
C
Okay,
like
a
hack
and
d
earlier
today,
so
I'm
going
to
take
a
look
at
that
after
this
meeting.
But
yes,
my
it
is
my
preference
to
get
that
one
out
like
like
as
soon
as
possible.
So
okay,
excellent.
D
C
Soon,
as
this
schedule
is
finalized,
I
will
send
it
to
the
Sig
docs
Channel
and
I
will
also
keep
it
updated
so
in
case
anything
anything
changes,
but
is
there
any
other
Elite
specific
requests,
concerns
or
questions
for
comms
on
the
blog
schedule.
E
I've
got
a
line
item
in
the
discussion
points
about
the
project.
The
blog
project
board
I
was
wondering,
if
maybe
this
would
be
a
good
time
to
bring
that
up.
Briefly,
there's
been
some
conversation
that
I've
linked
about
trying
to
get
the
existing
board
updated,
so
that
folks,
who
are
editors,
can
manipulate
this
board.
Now
it
looks
like
this
particular
board
is
I
suppose
obsolete
in
that
it's
not
able
to
be
programmatically
updated.
So
if
you
get
added
as
a
Blog
editor,
you
are
still
not
able
to
be
made.
A
manipulator
of
this
course.
E
It
seems
like
there
is
an
option
to
create
a
new
board
in
the
new
guest
file
that
do
that.
I
saw
a
couple
of
folks
doing
like
a
plus
one,
and
it's
like
what
it
wanted
to
bring
it
up
here
and
see
if,
if
creating
a
new
board
with
the
idea
that
automating
permissions
on
it
was
a
worthwhile
sort
of
endeavor.
A
Yeah,
so
just
to
kind
of
tie
both
a
bit
I
placed
the
125
blog
PR's
and
the
left
care
is
planned
so
that
the
block
team
is
aware
of
them
and
there
I
did
try
to
create
a
group
of
GitHub
group
for
blog
editors.
So
we
could
add
it
to
the
administration,
for
this
board
turns
out.
It
looks
like
we
need
to
use
the
new
GitHub.
We
need
to
use
the
new
github's
projects
beta
board
for
that,
but
the
group
is
actually
created.
A
So
we
have
that
in
case
that
we
could
use
to
and.
E
Our
our
release
teams,
like
the
comms
release
teams,
a
part
of
that
blog
editor
group.
D
A
Yeah
I
actually
like
love
the
idea
that
we
don't
have
so
in
the
role
handbook
for
docs
the
docs
lead.
It
becomes
a
docs
reviewer,
okay,
an
approver.
We
should
do
that
for
the
comments
lead
as
well.
They
should
be
a
Blog
approver
or
a
reviewer
both,
and
so
they
would
be
part
of
that
group
automatically.
A
Then
the
blog
sleep
and
then
comps
team
could
have
to
manage
the
blocks
board
going
forward.
So
all
right,
hopefully
I,
remember
it
I'll
make
those
changes
to
the
handbook.
All
right.
A
No
I
could
create
a
board.
Yeah
I
can
create
a
board
with
that.
So
I'll
get
that
created
and
try
to
tie
in
this.
The
administration
permissions
to
block
reviewers.
A
All
right
take
that
as
my
takeaway
any
questions
for
the
125
feature:
blogs.
A
I
do
like
to
make
note
that
we
like
to
save
about
three,
maybe
in
four
weeks
or
three
weeks
of
of
after
the
125
release
for
just
feature
blocks.
So
we
we
typically
like
to
get
those
scheduled
outs,
but
every
other
day
or
so
we
don't
I,
don't
think
we've
done
it
back
to
back
days.
I
think
we
gave
it
a
day,
a
buffer
time
for
each
blog
release,
so
yeah.
C
C
A
A
F
I
opened
this
issue,
and
this
appear
because
I
when
I
see
this
document,
the
he
said
don't
be
thunderous
message:
a
member
to
get
get
your
sponsor,
but
I
think
it's
a
reasonable.
So
I
changed
it
to
the
don't
message
your
member
randomly
oh
I,
see
it
will
be
more
clear.
A
Yeah
I
see
that
all
right.
Thank
you.
I'm,
going
to
review
this
I
know
we
have
a
high
number
of
pull
requests
open,
so
I've
been
helping
out
a
little
bit
this
week,
so
try
to
put
a
review
on
that
later
today.
Thank.
F
A
Before
we
move
on
I,
see
Carol
from
the
docs
125
team,
Carol
I
gave
the
kind
of
the
same
update
that
was
that
was
presented
in
the
release
team
meeting
today.
If
there's
any
added
anything
you
want
to
add
feel
free
to
add
something.
Now.
A
All
right,
moving
on
to
questions
and
discussion
points
first
ones
from
Nate
about
the
cncflfx
mentorship.
E
Hello,
everyone.
This
is
not
necessarily
strictly
a
a
docs
announcement,
but
I've
just
been
going
around
letting
folks
know
that
we
have
our
term
three
September
through
November,
currently
accepting
project
proposals.
E
You
know
if
you've
got
a
project,
we'd
love,
we
would
love
to
to
have
more
non-code
projects
or
documentation.
Projects
are,
are
totally
viable
for
for
this.
So
if
you
do
have
a
an
idea,
I
think
that
only
like
chairs
or
maintainers
can
actually
officially
create
a
proposal,
but
I
wanted
to
to
encourage
folks
to
think
about
it
and
if
you've
got
a
project
idea,
talk
to
your
your
chairs
and
potentially
get
something
written
for
the
docs.
E
It's
all
paid
work.
It's
a
there's,
a
snipe
end
attached.
So
this
is
a
very
good
way
to
get
folks
involved
in
open
source
and
especially
in
potentially
starting
writing
or
technical
writing,
or
even
if
you
know,
designers,
if
you
need
I,
I
I'm,
always
telling
folks
that
it
doesn't
matter
if
you're
a
coder,
a
a
a
a
writer,
a
designer
or
even
a
project
manager.
E
We've
got,
we've
cut
work,
and
so
this
is
a
good
opportunity
to
to
try
and
bring
folks
in
and
get
to
get
some
more
get
some
more
work
on
on
the
project.
Then.
A
All
right,
thank
you
for
bringing
that
up
next
topic
for
content
in
KQ
miniature.
We
use
kate.dev
if
available
so
I
think
this
is
about
the
glossary
for
Sig's
list.
Right
did
see
this
actually
made
a
comment
about
this
that
this
PR
changes
the
link
four
six
to
the
contributor
sites.
My
comment
is
that
the
the
source
of
or
the
official
source
of
trip
for
six
is
the
k.
Community
six
list
or
six
dot
yaml
actually
might
even
pose
this
to
change
to
six
I
am
also
that's
actually
the
same.
A
It's
actually
the
official
source
of
six
but
six
list.
Dot
MD
is
the
is
the
is
the
actual,
or
is
it
human,
readable
version
of
that
yeah
Sean?
Do
you
want
it
to
have?
Do
you
have
a
comment
or
question
about
this?
Well.
F
Can
you
switch
back
to
later,
also
or
is
tarantula
anchor
is
now
learning
it's
I
say
they
have
case
that
they
have
link.
So
you
change
to
the
list
link
instead
of
GitHub
right
I
think
we
have
some
some
of
the
community
if
I
are,
in
the
case,
dot
Dev,
but
I
want
to
hear
how
others
think
about
this.
Should
we,
which,
which
is
you
use.
A
The
only
the
two
reason
why
I
suggested
just
keeping
it
or
to
the
KQ
mini
6
list
is
one
and
that's
one
of
the
source
of
trip,
even
though,
even
though
the
contribution
might
use
that
set
and
use
that
page
to
generate
off
of
it.
But
if
you
look
down
like
we
actually
referred
to
multiple
other
pages
in
that
GitHub
k,
Community
right,
they
say
governance,
the
working
group
and,
and
also
just
taking
me
as
well.
A
A
A
All
right
feel
free
to
add
in
your
additional
comments
to
this
pull
request.
This
is
three
five,
six,
four
eight
it's
linked
here
on
the
agenda.
A
A
I
do
have
one
additional
topic
that
I
did
not
add
on
here.
For
those
who
are
attending
kubecon
in
Detroit's
there
it
will
be
contributor
day
on
the
Monday
of
coupon
and
we
do
have
reserved
space
for
Doc
Sprint
and
we're
open
for
suggestions.
If
there's
a
topic
for
topics
or
themes,
I
know
there's
one
for
for
troubleshooting
as
well.
Someone
reach
out
to
me
a
little
bit
on
troubleshooting
as
well,
so
we
could
do
a
little
bit
on
that.
So
we
have
a
room
available
at
the
at
the
contributor
Summits.
A
So
we
could
go
over
some
topics.
We
could
I'll
have
some
good
first
issues
as
well,
so
so
any
person
who
hasn't
contribute
to
2K
websites
could
take
a
stab,
but
that's
what
it's
good
first
issues,
but
just
reach
out
I'll
post
again
on
slack
next
week
for
any
kind
of
topics
or
things
that
people
want
to
talk
about
or
bring
up
for
during
the
contributor
Summit.
E
Are
we
going
to
in
addition
to
having
the
Sprint?
Are
we
going
to
have
like
a
doc
specific,
get-togethers
sort
of
talk
or
resist
I?
Guess
I
guess
the
other
question
is:
are
they
also
going
to
do
the
same
sort
of
thing
that
they
did
the
time
where
they
had
a
like
a
board
of
hey
here's,
the
topics
that
are
folks.
E
A
We
could
do
both.
We
actually
had
room
from
11
to
5
I
believe
so
it's
long,
it's
a
long
time.
So
we
could.
We
can
have
both
accommodates
for
quite
a
few
things
as
well
during
the
main
part
of
kubecon
Detroit's.
There
actually
will
be
a
Sig
meet
and
greets
if
for
folks
who
just
want
to
meet
up
represents
from
six
will
be
available
in
in
that
session.
So
that
is
not
that
time
has
not
yet
been
determined.
So.