►
From YouTube: K8s SIG Docs meeting for 20220628
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
Welcome
everyone
welcome
to
the
June
28
2022
kubernetes
sick
docs.
Meeting
I
am
your
host.
My
name
is
Ray
lajano
I'm.
One
of
the
co-chairs
for
Sig
docs
do
want
to
remind
everyone,
since
this
is
an
official
kubernetes
meeting
and
we
do
buy
the
CNC
optic
code
of
conduct
to
just
to
be
nice
and
pleasant
and
kind
to
everyone,
and
this
meeting
is
being
recorded
and
will
be
uploaded
to
YouTube,
so
be
mindful
of
what
you
want
to
save
that
and
that
it
will
be
recorded.
A
Let's
just
share
the
meeting
agenda
in
the
slack
sorry
in
the
zoom,
chats
I'll
share
one
more
time
and
I'll
share
my
screen
here.
Foreign.
A
A
All
right
so
welcome
back
I
guess
to
all
Sig
docs
members
here,
but
if
there's
any
new
contributors,
please,
if
you
want
to
introduce
yourself,
you
feel
free
you
can.
You
could
also
introduce
yourself
on
the
chat
as
well
all
right.
Moving
on
this
week's
PR,
WR
Wrangler
is
Natalie.
Natalie
is
a
little
bit
under
under
the
weather.
But
Nelly
is
reviewing
PR's
this
week.
So
if
you
have
any
PRS,
then
that
needs
a
review.
Please
Nelly
is
the
pr
Wrangler
for
the
week.
A
Next
week,
though,
there
is
a
U.S
holiday,
so
we
do
not
have
an
assigned
PR
WR
Wrangler.
So
during
this
time,
I
usually
like
to
to
contribute
a
little
bit
more
and
and
do
some
reviews,
but
next
week,
so
just
be
aware
that
there's
no
official
PR
ringer
for
other
folks,
we
are
coming
around
to
the
end
of
the
pr
Wrangler
shift.
The
pr
Wrangler
shift
is
is
created
for
six
months
of
the
year
at
the
time.
A
So
we
should
be
well
we'll
be
looking
to
creating
the
the
pr
Wrangler
shift
for.
A
C
You
want
me
to
do.
C
B
C
Hi,
this
is
Kristen
I'm,
the
1.25
docs
lead
and,
let's
see
so,
we
just
hit
our
enhancement
series
last
week.
That
was
the
updated
date.
It
was
delayed.
So
our
team
myself
in
the
shadows,
we've
divided
up
the
enhancements
and
we're
working
on
contacting
the
enhancement
owners
to
remind
them
of
the
docs
requirements
and
deadlines.
C
Also,
one
of
my
Shadows
opened
the
first
PR
to
keep
the
dev
branch
in
sync
and
that's
awaiting
approval.
I
believe
there
was
according
to
Ray.
There
was
a
removal
of
a
banner,
so
it
did
require
more
approvals
from
the
steering
committee
than
than
normally
would
be
required.
So
that's
still
pending
and
you
can
read
about
the
upcoming
Milestones
for
code,
freeze,
placeholder,
PRS
and
all
that
in
the
agenda.
A
Thank
you
very
much.
I
did
about
the
pr
to
sync.
The
dev125
branch
I
did
ping
a
second
steering
committee
person
just
a
few
minutes
ago,
so
hopefully
we'll
get
and
we'll
get
some
some
eyes
on
it.
If
not
so,
I'll
go
down
the
list
and
ping
and
reach
out
to
more
steering
committee
members.
That's
because
when
we
created
the
dev
125
Branch,
we
create
the
branch
at
the
same
time
as
the
124
release.
A
On
that
on
release
day
and
on
release
day,
the
main
branch
had
the
Banner
for
the
dockish
removal,
so
the
dev
125
Branch
currently
has
that
banner
and
the
current
main
branch
does
not
have
a
banner.
So
in
order
to
sync
the
dev
125,
with
with
the
current
main
branch,
it
does
remove
the
banner
from
from
being
present
on
the
120
Dev
125
site,
so
we
do
need
and
for
any
Banner
pull
requests.
We
need
steering
committee
approvals
for
any
spanner
Banner
pull
requests.
A
Thank
you
very
much.
Excuse
me.
Do
we
want
to
make
note
that
the
first
feature
blog
pull
request
is
up
is
up.
You
know
already,
for
that's.
Excuse
me.
That's
pretty!
Ip
tables
cleanup
for
each
release.
We
have
a
set
of
feature
box,
highlight
key
enhancements
for
the
release
or
even
keyed
applications
as
well.
So
the
first
one
is
actually
up
inning
comments
or
questions.
A
I
did
have
a
question
on
the
chat
on
what
is
the
pr
Wrangler
ship,
so
the
pr
Wrangler
is
a
as
a
as
an
approver
reviewer
for
Sig
docs
and
who
is
someone
who
has
the
approver
permissions?
Who
will
review
PRS
for
the
week
open,
pull,
requests
well
and
do
reviews
of
them
and
we'll
see
if
and
we'll
make
some
comments
if
they
need
to
be?
A
If
then,
if
there
needs
to
be
updates
or
we'll
go
ahead
and
approve
or
lgtm
those
pull
requests,
and
if
there's
any
questions
about
an
open
pull
request,
you
might
have
reach
out
to
the
pr
Wrangler
for
that
week.
So
this
this
week
is
Natalie.
A
All
right,
moving
on
to
issues
in
PR's,
first
topic,
I
actually
added
on
here.
This
is
to
update
the
reviewing
PR
guide
or
reviewing
PR's
page
and
that
that
streaming
had-
and
that
was
also
broadcasted
on
this
on
the
sick
dog
slack
channel
just
to
get
more
eyes
on
it.
I
know
there's
some
multiple
LG
TMS
here
it
just
clarifies
on
on
the
reviewing
PR's
page
when
you
do
review
PRS
or
if
you,
if
you
ask,
for
a
requests
for
changes
of
of
PR's
things
like
to
add
a
hold.
A
If
you
don't,
if
you
feel
like
this,
PR
should
be
blocked
for
some
reason,
but
to
mention
also
specify
why
there
is
a
hold
as
well
also
to
just
some
some
tips
like
avoiding
the
click
and
improve
button
when
you're
finishing
the
review
and
to
use
the
to
use
the
slash
approve
label
when
you
actually
do
a
proof.
So
these
are
just
kind
of
clarifies
the
pr
reviewing
process
foreign
on
this
as
well.
Instead
of
having
consensus
on
it.
A
So
there's
three
LG
TMS
currently
so
feel
free
to
add
your
comments.
A
All
right
any
comments,
questions
all
right.
Next,
one
is
from
Chris
to
long
long,
Sandy
issue
and
a
very
important
issue
of
the
mermaid
diagrams
are
broken
so
I'll
just
hand
it
off
to
Chris.
D
D
Now,
for
you
know
a
bunch
of
time,
I
thought,
maybe
you
know
a
Brute
Force
approach
may
allow
me
to
get
in
there
and
figure
out.
D
What's
going
on
where
we
stand
right
now
is
it
looks
like
there's
some
underlying
you
know:
JavaScript
CSS
interactions
happening
with
with
mermaid
I
was
looking
into
the
so-called
layout,
thrashing
where
you've
got
JavaScript
running,
then
it
does
a
layout
and
it
has
to
go
back
to
do
JavaScript
and
that
might
apply
here,
but
you
know
I've
been
able
to
graph
it
out
and
that
kind
of
thing,
but
at
this
point
in
time
well
we're
also
not
seeing
the
syntax
error
anymore,
we're
seeing
sort
of
a
a
semi
or
incompleted
mermaid
diagram
with
a
zeroed
out
or
incomplete
viewport.
D
So
long
story
short
is
I.
Think
we've
got
some
issues
with
you
know
the
the
with
layout
thrashing
I
know
we
have
a
massive
Dom
in
one
of
the
areas
of
of
maybe
correcting
that
would
be.
You
know:
we've
got
a
big
Dom,
we've
got
a
gigantic
CSS
I
took
Tim's
approach
and
went
in
and
looked
at
the
different
scripts
that
are
that
are
running
when
someone
loads
up
a
a
page
with
a
mermaid
diagram
tried
to
cut
those
out.
D
It
didn't
really
do
anything
other
than
you
know,
giving
the
other
errors
elsewhere.
So
long
story
short
I'm,
putting
out
a
broadcast
a
request
for
help
for
some
JavaScript
expertise
and
put
that
out
a
couple
of
times
on
Sig
docs,
but
I
figure.
Now
is
the
right
time
to
to
escalate
this
I've
probably
taken
this.
D
As
far
as
I
can
I
can
go
like
I,
say:
I
can
document
everything
I
see,
sort
of
the
layout
thrashing
in
the
dev
tools,
performance
things
that
processes
that
allow
you
to
graph
out
what's
going
on,
so
how
can
I
reach
out
or
who
should
I
reach
out
to
or
what?
What
Sega
or
is
there
an
area
of
web
development?
And
what
have
you
to
to
help
to
help
solve?
This
thing
is
problem.
A
So
I
can't
think
of
a
specific
Sig
that
we
could
reach
out
to
for
those
who
are
on
this
meeting.
If
you're
familiar
with
with
mermaid
diagrams
feel
free,
please
reach
out,
we
definitely
need
some
help
on
these
broken
mermaid
diagrams
I
could
take
a.
Let
me
go.
Take
a
look
I'm
assuming
you.
You
had
the
chance
to
take
a
look
at
the
at
the
mermaid
repo
see
if
there's
any
similar
issues
as
well.
Yes,
absolutely
now.
D
Again,
we're
not
seeing
the
syntax
error
anymore:
yeah
played
around
with
different
versions
of
mermaid
Hugo
I
updated.
You
know
the
popper
and
bootstrap
JavaScript
libraries
did
all
I
could
do
I
think
to
try
and
figure
out
exactly
what's
going
on
now.
D
I
set
up
that
separate
doxy
example
repo
and
for
many
reasons,
I
think
the
Dom
is
very
small
there,
but
you
know
I
couldn't
reproduce
the
error
at
all:
everything's
squeaky,
clean
and
fast,
but
in
our
case
I
was
looking
at
yesterday
and
we've
got
over
4
300
Dom
elements
and
again
one
of
the
one
of
the
symptoms
of
layout
thrashing
is
a
gigantic
Dom.
I,
don't
know
if
it
can
do
anything
about
that.
D
But
I
suspect
that
something
happened
in
March
time
frame
which
somehow
maybe
a
different
script
was
loaded
or
maybe
it
wasn't
just
I
I,
don't
know
what
happened,
but
suddenly
we
had
these
syntax
errors,
but
now
we're
getting
specifically
that
empty
box
with
those
little
inverted
use
sign
and
that's
actually
a
pointer
to
the
live.
Editor
diagram,
so
net
net
we're
not
completing
the
the
the
layout,
the
computation
of
the
layout
and
then
the
presentation
on
the
on
the
web
page.
A
Okay,
I'm
gonna
do
some
forensic
to
see
if
there's
any
key
changes
in
March
that
could
relate
to
the
starts
of
the
broken
mermaid
diagrams
yeah.
D
Yeah
I
looked
at
that
I
know:
Tim
had
something
in
March
where
he
updated
from
mermaid
811.13,
also
cleaned
up
or
I
guess
improved
the
error
message.
If
you
know
JavaScript
isn't
running
so
there
was
a
couple
of
things
made
in
there.
I
thought
I
may
have
removed
those
changes
and
and
tried
it
again,
I'm
not
sure,
but
that's
the
only
only
thing
I
could
find
I
just
couldn't
find
anything
that
would
say
you
know:
hey.
D
We've
got
this
thing
going
on
it's
causing
problem,
although
we
do
see
the
you
know,
the
the
Google
apis,
the
Google
tag
manager
and
that
kind
of
thing
I
do
see
that
you
know
when
I
run
through
the
the
different
scenarios
when
I
you
know,
click
through
it
and
and.
D
It's
not
really
predictable.
The
page
will
load
one
time
load.
Another
time
then
it
doesn't
load
for
the
next.
You
know
correctly
for
the
next
few
clicks.
A
They
stopped
so
definitely
see
that
as
well,
which
does
not
I
can't
think
of
anything
currently,
in
fact,
that
would
make
it
unpredictable.
That
would
work
one
time,
but
not
the
other
times
right.
D
Right
and
again,
I
don't
want
people
to
give
up
on
mermaid
right
right,
because
we
need
a
you
know
a
standard
tool
and
it
does
seem
to
be
used
by
a
lot
of
people
in
the
industry.
So
again,
who?
Who
was
a
JavaScript
expert
out?
There
should
I
just
broadcast
another
plea
for
our
assistance.
Sure
there
must
be
someone
out
there
that
can
that
can
help
us
solve
this
problem.
A
I
could
also
have
the
kubernetes
contributor
Twitter
account
just
to
like
tweet
out
some
help.
They've
had
some,
they
did
tweet
out
some
help
wanted
from
Barry
siggs
from
the
annual
report,
so
we
could
actually
have.
We
could
have
a
similar
broadcast
as
well.
So
I
could
take
that
on.
D
One
point
one
more
thing:
I
think
I'll
do
ray,
is
I'll
open
up
yet
another
issue
on
the
mermaid
repo,
because
the
original
one
was
it
got
real
long
and
you
know
just
it
was
all
over
the
place.
So,
but
this
one
has
that
unique
presentation
where
you
just
see
the
empty
box,
and
so
it's
not
a
syntax
error.
It's
something
that's
happening
again.
My
my
feeling
is,
it
might
be
a
some
other
JavaScript
I
mean
maybe
dealing
with.
D
You
know
this,
this
Force
Reflow
or
this
you
know
this
layout
crashing
anyway,
I'll
open
up
an
issue
today
on
that,
maybe
we
can
get
some
feedback
from
those
folks.
I
also
looked
into
doxy
Dev
and
doxy
example.
I
didn't
see
anything
there
as
well.
Yeah.
A
Thank
you
yeah.
If
you
have
that
little
summary
and
maybe
I
will
give
you
a
draft
of
or
send
you
a
draft
of
what
the
tweets
will
be
before
contrabx
sends
it
out
or
publishes
it
excellent.
D
Hey
folks,
if
you
see
them,
you
know
I
mentioned
last
week,
I
thought
there
was
something
for
I
think
it
was
a
mermaid
short
code
that
I
used
as
a
comment
inside
a
note,
tag
and
I
guess,
for
whatever
reason,
it
was
being
interpreted
as
a
mermaid
short
code
and
that
was
causing
some
things
to
mess
up.
I,
don't
know
if
we
we
see
that
I
don't
know
if
I
haven't
seen
that
the
last
couple
of
days.
D
But
again,
if
anybody
has
any
issues-
or
you
see
an
error
just
reach
out
to
me
as
quickly
as
you
can
and
we'll
look
to
get
them
up
resolved.
D
Oh
one
last
thing
in
the
meantime,
as
a
stop
Gap,
because
we
got
a
couple
issues
about
you
know
the
Bro,
the
diagram
that
was
broken
in
the
Ingress
session,
a
couple
of
other
a
couple
of
other
of
those
places,
so
I
just
generated
an
SVG
for
mermaid
and
put
it
in
there.
So
we
won't
see
any
more
problems
there,
but
I'd
still
like
to
have
the
the
inline
mermaid
method
working
reliably.
A
D
A
Here
I
know:
other
kubernetes
cigs
are
using
mermaid
diagrams
in
GitHub,
because
you
could
actually
create
a
mermaid
diagram
and
and
represent
it
in
your
in
your
readme
as
a
diagram.
A
So
it
is,
we
are
adopting
it.
I
mean
the
other.
Six
are
adopting
mermaid
backgrounds
all
right.
Well,
thank
you
very
much.
A
A
Feel
free
to
ask
any
questions
about
this
on
the
slack
Channel,
so
this
is
actually
one
of
the
issues
ongoing
issues
with
the
docker
shim
removal
as
well,
which
so
this
still
needs
to
be
to
be
cleaned
up
a
little
bit
here.
So.
A
A
All
right,
lastly,
just
remember
to
ping
the
pr
Wrangler
for
the
week.
If
there's
any
reviews
that
you
would
like
moving
on
to
questions
and
discussion
topics
here,
the
monthly
localization
meeting
is
usually
held
on
the
first
Monday
of
the
month,
but
next
Monday
July
is
edition
of
the
localization
meeting.
Is
actually
it's
a
U.S
holiday
here.
So
we
so
folks
in
the
US
as
they
we
have
a
three
day
weekend.
So
it
would
be
moved
by
one
week.
A
So,
instead
of
from
instead
of
having
the
meeting
on
July
4th,
it
will
be
moved
to
Monday
July
11th.
E
And
yes,
I
had
an
additional
comment
on
that
I
will
be
sending
out
updating
the
calendar,
invite
and
making
sure
that
gets
announced
to
other
places
here.
So,
if
you're,
not
on
the
meeting,
you
won't
hear
me
saying
this,
but
anyway,
I
will
also
communicate
that
out
in
other
channels,
and
the
other
thing
I
wanted
to
mention
is
I
believe
with
Natalie's
email
about
the
localization
sub-project
a
few
weeks
ago.
I,
don't
remember
exactly
when
that
went
out,
but
I
believe
through
the
powers
of
lazy
consensus.
E
We
are
we're
now
officially
have
a
sub-project,
which
means
that
we
will
act
in
the
same
way
that
we
did
before,
but
we
now
are
officially
a
sub-project,
so
I
believe
there's
some
places
that
we
need
to
update
docs
to
mention
that
we're
we're
a
sub-project
which
I
need
to
find
to
do
that.
So
if
anyone
has
any
points
that
they
know
about,
that
need
to
be
updated.
Just
let
me
know,
and
I
I'll
I
can
take
that
action
item
to
try
to
update
places
but
yeah.
E
So
congrats.
Congratulations!
Everyone
on
the
localization
and
thank
you
for
everyone
who
helped
push
this
together.
I
am
one
of
the
leads
of
the
localization
sub
project
now
and
Brad
to
Topol
is
the
other,
the
other
lead.
We
hope
to
see
you
if
you're
interested
in
localization
hope
to
see
you
at
the
meeting
on
July
11th.
So
thank
you.
Ray.
A
Welcome
and
I
do
know
one
doc
at
least
it's
the
kubernetes
community
or
Sig
docs
directory,
and
they
read
me
there
where
we
list
out
all
the
sub
projects.
That's
that's
a
good
starting
point
for
it
to
add
the
localization
sub
project,
other
sub-projects.
They
usually
add
a
subdirectory
within
that
as
well.
If
it's
needed,
we
need
some
artifacts
hosted
all
right
and
I'll
I'll
look
out
as
well
for
any
more
places
where
we
need
to
add
that.
A
All
right
next
topic,
I'll
get
to
one
topic
from
the
chat:
the
new
contributor
meet
and
greets.
If
you're,
if
you're
a
new
contributor
to
Sig
docs,
we
have
a
monthly
new
contributor
meeting,
greet
that's
held
on
the
first
Tuesday
of
the
month.
That's
at
10,
30,
UTC,
10,
30
a.m,
UTC
or
4,
P.M
IST,
and
that's
on
the
sick,
docs
calendar.
A
So
if
you
join
the
sick,
Docs
Google
group-
and
if
you
check
out
the
calendar,
you
will
see
the
invite
or
you'll
get
the
invite
for
the
new
contributor
meet
and
greet
and
that's
held
by
arsh
Sharma.
Our
Sharma
is
the
is
the
Sig
docs
new
contributor
ambassador.
A
All
right
next
topic
is
regarding
catechota
scenarios.
This
is
from
the
chat,
so
the
cataclyn
scenarios,
so
catacota
public
has
been
removed
or
public
access
to
calculator
has
been
removed
for
ju
since
June
15.,
except
for
kubernetes.io.
So
all
the
kubernetes.io
scenarios
have
been
moved
on
a
separate
public
server
and
those
in
our
scenarios
on
kubernetes.io
are
still
are
still
live.
A
A
And
those
are
still
alive
any
questions
so
far.
A
Foreign
and
if
there's
any
open
PRS
like
I
mentioned
just
feel
free
to
reach
out
to
the
pr
Wrangler
for
the
week,
if
there's
any
open
PRS
regarding
catechodic
stereos,
all
right
just
want
to
briefly
go
over
the
document:
removal
project
board,
so
sick,
docs
and
folks
and
other
contributors
like
from
from
the
release
team
for
one
from
1.24.
We
had
a
monthly
document
removal
sessions,
sorry
weekly
sessions
on
deduction
removal
from
the
documentation.
A
So
we
ran
a
project
board
for
this
and
we
still
have
a
few
open
issues,
and
these
are
these
four
open
issues
here.
This
is
not
for
K
website.
As
you
see
the
prsm
fly.
This
is
for
under
under
crying
tools
there
or
CRI
tools.
So
we
have
four
still
remaining
issues
here.
We
do
have
an
open
PR
to
to
fix
this.
The
the
the
metrics
page
as
well.
A
This
other
one
should
be
closed
for
the
feature
gate,
but
I
will
check
and
the
storage
one
issue
is
the
one
that
Tim
brought
up
that
I
mentioned
on
the
agenda
a
few
minutes
ago.
That
means
that
needs
some
help
and
the
concepts
workloads
still
that
one
might
need
some
help
as
well.
A
So
take
a
look
to
see
if
so,
these
two
issues,
if
you're,
if
you're
looking
for
issues
to
work
on
the
storage
Concepts
page,
should
remove
Docker
in
the
text
and
code.
Samples
is
a
good
place
also
just
to
verify
that
the
workloads
concepts
page
does
not
mention
Docker
Shimmer
Docker
as
well.
So
there
might
so.
These
two
are
definitely
are
and
I
think
there
is.
A
Sorry
for
the
formatting
I'll
fix
that,
after
after
the
call
the
PSP
annotation
as
well,
and
the
link
to
cates.io
to
download
page
and
the
localization
side
sidebar
tree
anyway.
This
is
also
in
slack
as
well.
I
will
put
the
message.
The
link
here.
A
All
right
moving
on
past
the
deduction
removal
project
board,
like
I
mentioned
before,
there's
two
issues
that
need
some
help.
One
is
the
storage
volume
Concepts
and
the
workloads
concepts
as
well
all
right,
I'm,
gonna,
move
it
pass
on
to
mahe
about
the
PSP.
F
Thank
you,
so
I
was
wondering
myself
because
we
talked
a
little
bit
on
the
slack
channel
of
sex
security,
I
think
and
I
was
doing
some
research
about
security
policies
and
and
I
was
wondering
no
just
just
team
proposed
if
I
could
like,
if
we
could
or
I
could
write
a
blog
post
about
the
conservative
policy.
Duplication
like
very
similar
to
the
the
kashin
duplication
in
blog,
post
and
I
was
just
asking
you
today
well
like
there
was
enough
time
remaining
for
for
doing
so
and
team
just
already
answered
so
I.
A
Yes,
so
part
of
the
relating
back
to
the
docker
doc
shim
removal,
we
had
a
series
of
blog
posts,
not
just
one,
but
we
had
a
few
blog
posts
about
the
doctrine.
Removal
we
could
do
the
same
for
for
the
PSP
there's
still
time
until
until
125
is
released,
even
a
little
bit
after
125
is
released
as
well,
which
is
August
23rd.
A
So
if
you
would
like
so
yeah
it'll
be
great,
we
are
we
love
blog
posts,
especially
with
key
key
features
or
removals
that
are
going
to
affect
end
users.
Just
like
this
PSP
removal
as
well
yeah.
Just
let
us
know
when
the
blog
post
is
ready.
A
A
So
opening
a
hack,
MD
or
Google.
Doc
is
a
great
way
to
start
and
a
great
way
to
invite
editors
as
well
before
making
the
that
pull
request.
Because
there's
a
lot
more
feedback
and
a
lot
more
I
guess
requested.
Updates
with
the
blog
posts.
A
Here,
Nate's,
if
it's
an
open,
PR,
not
finished,
so
the
open
PR
line.
So
this
question
is
about
what
I
mentioned
with
the
metrics
page,
having
an
open
PR,
it's
been
open
for
a
while
and
there's
been
lots
of
back
and
forth
and
feedback
on
it.
A
So
it
I
think
I
gave
it
a
few
reviews
as
well.
I.
Think
Zach
also
gave
it
a
review
as
well.
I
think
there
might
just
need
to
be
one
more
change
on
it,
then
I
think
it'll
be
really
close
to
to
being
done,
and
that
was
that
PR
was
created
by
Augustus
B.
A
All
right,
another
question
from
the
slack
channel
is
when
does
a
new
Shadow
program
for
contributors
to
get
more
hands
on
the
community
of
kubernetes.
So
there's
multiple
Shadow
programs
that
the
community
has
the
most
well
known
as
the
release
steam
Shadow
program,
and
that
is-
and
there
is
a
doc
sub
team
for
the
release
team,
the
shadow
programs,
the
shadow
application
process
starts
a
little
bit
before
about
three
weeks
before
the
next
week.
Cycle
starts
so
also
one.
A
The
125
release
cycle
ends
on
August
23rd,
so
the
shadow
application
for
126
will
probably
starts
the
week
before
or
the
went
sorry
a
week
before
August
23.
or
around
August
23..
So
if
you,
if
you
keep
an
eye
out
like
on
the
sick
release
Channel
or
on
the
dab
mailing
list,
yeah
you'll
be
notified.
Other
Shout
Out
programs,
there
is
a
PR
Wrangler
Shadow
program
as
well.
A
The
the
pr
Wrangler,
the
pr
Wranglers
are
reviewers
improvers
of
the
of
the
website.
The
shadow
program
allows
you
to
to
just
get
insight
on
how
one
approver
how
what
their
process
is
like
when
they
review
PR's
4K
website.
Everyone
is
different,
so
everyone
has
a
different
review
process,
so
it
allows
you
to
to
do
a
one-on-one
either
Zoom
session
or
or
slack
messages
with
an
approver
for
sick
docs
on
to
just
to
learn
on
on
their
process
of
reviewing
as
well.
A
We
do
have
a
process
laid
out
on
the
kubernetes.io
on
how
to
review
PRS,
but
everyone
has
their
own
I.
Guess:
differences
as
well.
There
is
also
a
contribex
at
Shadow
program
that
is
about
about
to
start
as
well
there's
mentoring
programs
within
within
contribex,
and
that
is
about
to
start
as
well.
So
keep
a
lookout
for
that.
B
E
You
mentioned
that
there's
a
sec
Channel,
but
is
there
another
way
that
is
best
to
get
in
touch
with
the
team?
Is
there
a
meeting?
Is
there
an
emailing
list
to
join
or
how
to
get
more
information
about
joining
in
on
the
blog
team,
great.
A
A
A
That
has
not
been
well
attended
and
sometimes
I
poked,
the
sigdox
bach
channel
to
add
them
and
they're
up
their
updates
during
the
slack
and
the
other
the
off
week
of
the
sick
docs
meeting
when
we
have
a
slack
update
to
add
their
update
on
the
slack
on
the
slack
to
writes
there,
yeah
would
love
to
see
to
have
more
attendance
on
the
blog
meeting,
but
we
also
we
we've
also
made
a
call
out
for
more
blog
content
as
well.
A
We
tend
to
have
a
lot
more
blog,
reviewers
needed
towards
the
excuse
me
towards
the
end
of
the
release
cycle,
because
we
have
a
lot
of
feature
blogs,
usually
about
five
to
eight
feature
blogs
towards
the
end
of
the
release.
But
we
would
love
to
have
more
blog
content.
You
know
throughout
the
year
does
not
necessarily
have
to
be
tied
to
a
really
Cadets,
but
it'll
be
good
to
have
more
blog
content.
A
And
he
is
chatting
and
should
we
did
it
off,
he's
chatted.
We
probably
best
have
a
meeting
as
needed,
especially
if
there's
something
that
you'd
like
to
bring
up
check
out
this
hashtag
Sig
docs
blog
channel,
we're
actually
chatting
about
a
new
blocks.
The
mission
process.
Thank
you
Nate.
If
you
look,
if
you
go
into
the
Sig
dog's
blog
channel,
you
can
see
some
of
the
the
feedback
on
the
Block
submission
process.