►
From YouTube: SIG Docs meeting for 20210810
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
I
I
see
some
faces
or
names
I
don't
recognize,
but
if
you're
returning-
it's
just
you
know-
maybe
misconnected
no
big
deal
glad
to
have
you
happy
to
see
some
familiar
faces
as
well
and
welcome
and
as
always,
if
there's
any
questions
feel
free
to
put
them
in
chat,
feel
free
to
find
us
on
slack
as
well
on
the
sig
docs
channel
a
lot
of
friendly
folks
willing
to
help
out
all
right
moving
on
to
updates
and
reminders,
this
week's
pr
wrangler
is
savita
and
next
week's
pr
wrangler
is
brad
topple
and
I
want
to
say
that
brad
might
be
out
of
the
office,
so
I'm
going
to
confirm
confirm
next
week
with
brad
or
at
least
make
sure
that
we
have
covered
for
the
pr
wrangler
shift,
if
not
I'll,
step
in
and
take
care
of
that.
A
I
said
deja
vu
in
the
meeting
agenda
because
I
believe
brad
was
a
pr
wrangler
prior
to
this
week
as
well,
so
double
duty
for
brad
at
the
very
least
so
much
thanks
there
and
as
always
pr
wranglers
make
sure
you
know
your
shifts.
There's
a
link
in
the
agenda.
A
Let
me
throw
the
agenda
in
chat
here
just
for
folks
if
they
need
to
to
follow
along
right.
Moving
on
to
the
agenda
release
122,
it
is
complete
that
is
awesome,
congrats
a
lot
to
the
release
team,
sig
docs,
release
team.
It
is
no
small
effort.
Everything
gets
caught
on
fire
towards
the
end
of
release
there,
and
I
know
we
per
usual
had
some
issues
with
some
of
the
reference
generation
ducks.
A
The
bigger
part
of
being
a
shadow
is
learning
the
kind
of
inner
workings
of
what
happens
behind
the
scenes,
as
well
as
being
able
to
see
kind
of.
You
know
how
the
sausage
is
made
when
a
release
actually
happens
when
the
site
rolls
over
to
a
new
version.
When
we
cut
new
branches
when
we
synchronize
those
branches,
there's
a
lot
of
technical
of
technical
processes
that
maybe
is
not
so
out
in
the
open.
They're,
definitely
documented
out
there
in
the
role
handbooks.
A
B
Like
you
said,
it's
just
a
really
good
way
to
see
how
things
are
done.
Basically,
you
know
we
get
to
see
the
enhancements
that
are
coming
in.
We
are
assigned
certain
ones
to
track
and
to
make
sure
that
people
you
know
first
open
just
a
blank,
a
pr
and
then
fill
it
in
by
certain
dates
and
and
get
them
done
reviewed
by
certain
dates
that
was
kind
of
what
our
job
was.
But
yeah
victor
did
a
great
job
a
lot
of
times.
B
He
would
just
like
fix
things,
and
you
know
at
times,
so
I
I
didn't,
learn
all
the
details.
I
would
like
to
have
learned,
and
so
I
might
go
back
and
do
it
again,
but
for
the
most
part
it
was
a
very
good
experience.
I
I
would
go
to
some
of
the
other
meetings
as
well
the
release
team
meetings
and
and
just
just
to
understand
how
it
all
worked.
A
Yep,
absolutely
that's
a
great
point,
too.
Is
that
part
of
the
the
idea
of
using
the
shadow
process
is
having
folks
that
can
stick
around
for
multiple
releases
and
traditionally
the
requirement
to
lead
a
sig
docs
release.
Is
that
you've
been
around
for
at
least
two
releases
as
a
shadow?
So
it's
not
really
a
one-and-done
thing.
It's
a
little
bit
larger
of
a
commitment,
but
it's
structured
in
a
way
with
multiple
shadows.
So
folks
do
have
you
know.
As
we
know,
life
comes
up,
especially
in
days
like
today
with
the
pandemic
and
everything.
A
C
Yeah
my
my
gadgets
crash
but
never
mind
that
I
was
gonna,
ask
chris
about
how
that
much.
There
is
about
your
opinion,
chris
of
the
balance
of
technical
versus
people
work
in
being
a
shadow.
B
B
You
know
whatever
you
know,
whatever
they're
contributing
to
the
docs
for
the
for
the
enhancements,
but
certainly
I
mean
I
would
read
them
and
I
would
I
would
review
when
I
saw
things
and
it
certainly
doesn't
hurt
to
be
technical,
but
you
don't
have
to
be
deeply
technical
to
do
the
job.
A
So
moving
on
to
the
issues
in
pr
I
put
pr's,
I
put
one
in
here
I
found
last
night.
I
saw
timmy
left
a
comment
just
before
this
meeting
here
and
I'm
caught
up
on
that.
The
reason
why
I
brought
this
pr
to
attention
I'll
send
the
link
in
chat
here
is
it's
a
conversation
around
technical
accuracy
as
well
as
in
my
case
I.
I
think
it
comes
down
to
understanding
the
information
shared,
and
so
let
me
summarize
some
context
here
and
then
really.
A
What
I'm
looking
at
for
is
to
have
some
sort
of
sig
docs
group
consensus.
I
don't
really
have
an
opinion
one
way
or
the
other.
I
would
just
like
to
not
make
the
decision
in
a
bubble
and
have
us
all
aligned,
and
so
with
that,
when
we're
talking
about
milicores
and
we're
talking
about
cpu
slicing
in
kubernetes,
usually
what
we're
talking
about
is
1
1000th
of
a
cpu,
and
so
it
doesn't
matter
if
the
cpu,
what
kind
of
you
know
I
guess
gigahertz
megahertz,
whatever
type
of
speed
the
core?
A
A
The
measuring
unit
is
the
time
series
of
a
millicore
which
is
1
1000th
of
a
cpu
not
really
to
be
concerned
with
the
actual
speed
of
the
cpu,
and
I
could
be
screwing
up
the
explanation
of
it,
but
ultimately
the
the
wording
as
it
is
today
says
that
this
specific
value
is
converted
to
its
millicore
value
and
multiplied
by
100..
The
resulting
value
is
the
total
amount
of
cpu
time
that
a
container
can
use
every
100
milliseconds
a
container
cannot
use
more
than
a
share
of
cpu
time.
A
So
the
change
is
requesting
to
say
that
it's
converted
to
its
millicore
value,
multiplied
by
100.
The
resulting
value
is
the
total
amount
of
cpu
time
in
microseconds.
A
So
really
what
this
pr
comes
down
to
is
the
idea
of
adding
the
word.
Microseconds
is
an
extremely
small
small
change,
but
really
what
it
comes
down
to
and
why
I
bring
this
up
is
to
me
as
a
reader
who
is
not
extremely
deep
into
the
inner
kernel
workings
of
lytics.
A
It
confuses
me
a
little
bit
more
when
we
start
to
talk
about
microseconds,
and
this
is
mainly
me
not
being
exposed
to
the
word.
Microseconds
I
feel
like
milliseconds
is
very
common
in
technology
we
talk
about
ping
milliseconds
and
when
I
see
microseconds,
it
just
doesn't
resonate
with
me
as
a
reader
and
so
anyways.
The
conversation
comes
down
to.
It
is
technically
accurate
that
the
author
and
the
pr
and
the
change
is
correct
in
the
sense
that
it
is
measured
in
microseconds
and
adding
a
unit
is
completely
factually
accurate.
A
The
reason
I
bring
this
up
is,
I
feel,
like
it
might
make
the
reading
journey
of
a
user,
maybe
a
little
bit
fuzzier
in
the
case
of
readability,
usability
information.
You
know,
I
guess
the
information
the
waste
laid
out
and
then
tim
left
a
comment
in
this
pr
saying
that
you
know
this
information
is
really
around
docker
specifically,
and
the
whole
page
could
actually
use
a
little
bit
of
a
refresher.
So
it's
a
little
bit
of
expansion
on
the
scope
there,
but
let
me
pause
there
see
if
there's
any
questions
or
any
opinions.
A
A
And
I
guess,
if
there's
no
questions
or
comments
do
folks
feel
strongly
one
way
or
the
other.
Once
again,
I
I
feel
torn
on
this
one
because
it
is
technically
accurate.
While
I
disagree
with
the
change
from
a
reader,
if
that
makes
sense,.
D
There
discussing
you
know
multi-core
or
multi-slice
cpus.
B
So
if
this
is
a
docker
section,
it
may
not
be
a
bad
thing
to
just
align
with
their
wording
just
so
they
don't
think
that
so
reader
wouldn't
think
it's
something
different.
So,
but
that's
just
at
a
quick
glance.
I
have
no
deep
knowledge
of
this
topic.
A
C
I
I
think
the
way
to
resolve
you
know
this
pr
is
to
accept
it
and
then
log
an
issue
to
say.
Oh
my
gosh
there's
kubernetes.
Now,
since
I
don't
know
1.2
or
something
supports
more
than
one
container
runtime
and
more
than
one
mechanism,
and
we
don't
cover
that
in
this
key
page,
and
so
I
think,
there's
an
issue
around
making
it
much
more
neutral.
C
I
noticed
jim,
you
actually
were
talking
about
how
kubernetes
uses
milliseconds
as
its
default
unit.
It
doesn't.
The
default
unit
in
kubernetes
is
one
cpu.
C
But
the
point
is,
if
we're
confusing
sig
chairs
right,
that's
not
to
say
that
to
criticize
the
the
sig
or
the
chair
is
to
criticize
the
docks,
and
I
think
there
is
room
to
improve
yup
strong,
plus
one.
A
Cool,
I'm
I'm
good
with
that
result.
So
we'll
merge
this,
as
is
also
one
thing
I
want
to
call
is
this
is
a
first
time
contributor,
so
we
we
definitely
want
to
be
a
very
welcoming,
and
I
guess
what
I'm
trying
to
get
as
when
you're
a
first-time
contributor,
there's
so
much
to
learn,
there's
so
much
with
sick
dogs.
A
A
Alright
yeah
nice
cool,
we'll
move
on
if
y'all
work
out,
your
av
issues
feel
free
to
interrupt
me,
really
happy
and
glad
to
have
you
all
and
and
feel
free
to
introduce
yourselves
in
chat.
If,
if
not
so
moving
on
to
the,
I
guess,
is
there
any
other
issues
or
prs
folks
would
like
to
talk
about.
A
All
right
moving
on
to
the
discussion
section,
so
the
first
thing
to
cover
is
the
chair,
transitions
and
rotations.
I'm
sure
some
of
y'all
may
have
noticed.
Paris
has
been
stepping
in
and
helping
out
a
whole
quite
a
bit
wha.
What's
going
on
here
with
sig
docs,
I'm
not
sure
how
much
was
shared
with
the
team
and
and
what
paris
has
shared.
I'm
still
catching
up
on
some
of
the
previous
videos.
A
But
what's
going
on
is
right
now
the
co-chairs
are
dealing
with
limited
bandwidth,
some
availability
concerns
and
just
general
overall,
not
being
able
to
put
in
the
work
that
is
required
of
a
coach
or
myself
included,
and
so
what
we're
looking
for
is
folks
that
are
willing
to
step
up
into
the
co-chair
capacity
even
at
a
shadow
type
level.
We're
really
happy
to
train
folks
in
more
of
a
leadership
type
role
and
what
we're
looking
for
is
to
really
spread
the
workload
out.
A
A
You
know
rolling
as
a
successful
org
was
saying
that
all
the
current
co-chairs,
including
myself,
are
doing
this
on
a
voluntary
basis
on
a
voluntary
basis,
and
so
it
makes
it
very
challenging
for
working
conflicting
priorities
to
kind
of
step
in
and
step
out,
and
it
doesn't
make
it
right
or
wrong.
It.
Just
is
the
truth
and
that's
where
we
are
at
today
and
I
really
want
to
raise
visibility
here.
So
you
all
know.
A
What's
going
on
you're
aware
of
what's
happening,
you
see
paris,
helping
out
sharing
some
of
these
meetings
and
it's
not
not
a
state
of
emergency
or
a
state
of
a
panic.
It's
really
a
state
of
awareness,
and
we
want
to
make
sure
that
folks
are
aware
of
what's
going
on,
and
it's
been
this
way
for
quite
some
time,
but
we're
kind
of
hitting
that
perfect
storm
of
availability
concerns
and
issues
as
well
as
de-prioritization
for
some
of
the
co-chairs.
A
A
I
just
don't
think
it's
fair
to
the
sick,
docs
community
to
be
a
co-chair
in
that
administrative
capacity
and
not
be
available
full-time,
or
at
least
in
the
time
that
I
said
that
I
would
be
available
for
those
that
are
interested
there
is
in
the
contributor
guide
a
outline
of
what
are
the
responsibilities
of
a
co-chair
and,
in
general,
it's
about
six
hours
a
week.
That's
the
estimate
and
it
just
kind
of
outlines
some
of
the
duties
and
responsibilities.
A
The
other
thing
I'll
mention
is
there
is
tech
leads
as
well
as
co-chairs,
and
a
tech
lead
is
more
responsible
for
the
technical
operations
of
sig
docs
tim
banister
is
one
of
our
tech
leads
and
really
focusing
on
the
the
technical
aspects
of
documentation,
managing
prs,
making
sure
that
those
lights
stay
on
and
any
of
the
technical
issues
are
resolved.
A
I
will
say
tim.
You
definitely
do
a
little
bit
more
blended
into
the
co-chair
area.
I
don't
want
to
say
you're
exclusively
a
tech
lead,
but
but
definitely
glad
to
have
you
and
glenda
glad
to
see
you
helping
out.
C
If
I
could
share
a
bit
on
that,
jim
absolutely
so
one
of
the
things
that's
going
around
sort
of
kubernetes
governance
that
exciting
topic
is
mandatory.
Tech
leads
so
jim
you-
and
I
haven't-
haven't
spoken
about
this,
but
there's
an
idea
that
instead
of
tech
leads
being
an
optional
thing,
that
sigs
can
have.
They
become
a
thing
that
is,
six
are
expected
to
have,
and
so
with
that
in
mind,
I
it
it
struck
me
that
moving
into
being
a
formal
chair
doesn't
actually
solve.
C
You
know
the
staffing
problem,
quite
as
well
as
it
might
so.
You
know
that's
one
of
the
reasons
why
I'm
not
immediately
putting
myself
forward
and
saying
that
and
another
one
is
that
they
are
different
roles.
You
don't
have
to
become
a
tech,
lead
and
then
become
a
chair
or
become
a
chair
and
then
become
a
tech
lead.
They.
They
have
different
responsibilities.
A
Yep
as
strong
plus
one
that
and
hopefully
tim,
you
didn't
get
the
impression
that
I
was
making
that
that
assumption
that
you're
moving
into
a
co-chair
role.
I
I
believe
that
you
are
happy
doing
the
tech
lead
role,
and
I
was
just
complimenting
the
fact
that
you
definitely
have
a
little
blurry
gray
spot
there.
Where
you
help
us
out,
you
help
us
out
a
whole
whole
bunch,
so
really
appreciate
that.
A
D
Yeah
jim,
how
how
would
you
get
started?
I
mean
I've
seen
the
the
sites
you
referred
to
in
terms
of
what's
required,
but
do
you
just
start
shadowing
or
do
you
sign
up
and
start
shadowing
or
yeah.
A
A
There
is
also
the
general
contributor
ladder
so
folks
who
aren't
even
a
kubernetes
member.
It's
not
like
you
can
just
kind
of
jump
straight
to
a
co-chair.
You
might
need
to
work
yourself
from
a
kubernetes
member
to
a
reviewer
to
an
approver
all
the
way
to
the
co-chair,
but
that's
not
a
reason
to
to
not
put
out
the
feelers
of
interest.
You
know
if
you're
interested
in
doing
any
sort
of
co-chairing,
as
it
is
a
requirement
to
officially
be
a
co-chair
to
be
an
approver
and
all
that
good
stuff.
A
It's
a
long
cycle
and
and
sig
docs
isn't
going
anywhere
and
so
shadowing
and
learning
some
of
those
fundamentals,
as
you're
growing
in
the
community
is,
is
not
a
problem
at
all.
Either.
C
Good
terrific
cool,
I
want
to
say
one
more
thing
go
for
it,
I
meant
to
say
I
had
this
plan,
I
can't
program
and
go
and
that's
going
to
surprise
some
people
a
lot
and
I
guess
other
people
are
going
to
go.
What's
go.
Kubernetes
is
basically
written
in
golang
and
it's
not
a
language.
I
I
use
on
a
day
to
day
I
can't
write
in
it.
C
I
can
read
it
and
spot
bugs
maybe-ish
and
I
can
use
go
templates
because
my
gosh,
the
website,
uses
those
a
lot,
but
I
can't
programming
go
and
I
want
to
emphasize
that
you
don't
need
a
lot
of
technical
knowledge
to
be.
You
know
a
technical
lead.
You
don't
have
to
be
able
to
use
kubernetes.
Well,
it
does
help.
You
don't
have
to
be
able
to
use
kubernetes
at
all
to
be
an
effective
chair
so
long
as
that
you've
got
an
ability
to
work
with
people
who
do.
A
Cool
all
right.
Well,
in
that
case,
let's
keep
rolling
here.
I
don't
want
to
bleed
that
topic
out,
but
that's
going
to
be
kind
of
a
reoccurring
theme
as
we
progress
into
the
the
holidays
here
and
then
things
are
slowing
down
so
their
topic
here.
I
believe
paris
brought
this
up.
It
sounds
like
there
is
general
consensus
that
moving
to
maybe
a
bi-weekly
slack
type
of
stand-up
or
meetings
would
be
acceptable.
Does
this
ring
a
bell
with
folks.
A
Okay-
and
so
I
guess,
are
we
just
waiting
on
someone
to
make
the
decision
or
to
make
that
transition.
E
Both
gotcha,
I
think
I'll
just
say:
oh
just
just
the
just
the
topic
or
the
idea
was
just
brought
up,
but
no
nothing
was
decided.
Gotcha,
hey
would.
D
That
replace
the
meetings
that
we're
having
right
now
or
just
sort
of
the
augment
of
what
we
do
right
now.
It.
A
Would
replace
the
meetings
we
have
right
now
so
going
back
to
the
concept
of
kind
of
having
a
skeleton
crew
of
co-chairs
right
now
and
in
different
conflicting
priorities.
What
it
would
do
is
reduce
one
meeting
every
other
week,
and
so
it
would
be
in
slack
as
opposed
to
this
in
person
and
this
ketchup.
It
would
be
a
threaded
meeting
in
slack
asynchronously
and
it
would
just
save
you
know
the
the
need
to
actually
have
dedicated
time
to
meet
every
week.
A
The
slight
challenge
with
it
is:
we
do
have
the
apac
meeting
the
fourth
wednesday
or
the
after
the
fourth
tuesday
of
the
month,
that's
kind
of
confusing
how
it's
actually
in
the
calendar,
but
basically
it's
the
fourth
tuesday
of
the
month
that
the
that
the
apec
meeting
happens
and-
and
I'm
thinking
that
if
we
were
to
do
bi-weekly,
it's
not
so
much
in
order
there's
sometimes
where
a
month
we'll
have
five
weeks
before
the
apec
meeting
and
sometimes
it'll
be
four
weeks.
So
it
just
depends.
A
That
might
be
a
slight
challenge,
but
I
don't
think
it's
a
reason
why
we
couldn't
experiment
with
this,
and
the
idea
being.
Is
that
having
less
face-to-face
meetings
would
allow
other
folks
to
free
up
the
time
for
other
things,
as
well
as
with
a
shorter
co-chair
staff.
It
allows
us
to
free
up
our
time
and
our
resources
as
well
and
still
be
evolved
and
active
and
keep
the
community
moving.
E
All
right
yeah
with
this
I
know
the
we
have
there's
a
blog
meaning
subproject
meeting
as
well.
That's
every
other
week,
sig
release
day
alternates,
release
engineering
and
suit
and
seek
release
meetings
every
tuesday
with
this,
and
what
would
we
be
able
to
alternate
a
sig
docs
and
sig
docs
blogs,
sub
project
meeting.
A
Yeah,
I
would
be
open
for
that.
The
one
negative
aspect
of
that
would
be.
You
lose
the
the
regular
sync
with
the
docs
team
each
week,
but
I
don't
know
if
that's
necessarily
a
a
negative
or
not.
But
potentially
you
could
do
alternating
docs
and
blogs
each
week
and
then
the
week
that
it
is
blogs
you
could
have
a
slack
stand
up,
for
example,
for
sick
docs.
D
So,
jim
that
that
explanation
there
sounded,
you
know
a
little
bit
confusing.
Could
you
just
clair,
I'm
missing
that
if
we
replace
these
all
together
and
just
do
slacks
or
or
again
just
clarification
there,
yeah.
A
Absolutely
so
sorry,
if
I'm
not
doing
a
good
job
explaining
this,
but
the
the
idea
being
is
right.
Now
we
meet
and
let's
just
simplify
it,
we'll
take
all
the
meetings
out
of
the
picture
and
we'll
just
focus
on
this
specific
sig
docs
meeting
we
meet
weekly
on
tuesdays,
and
so
the
idea
being
is
that
we
would
move
to
slack
every
other
week.
A
A
All
right
moving
on
to
the
just
this
kind
of
announcements-
I
guess
here
it
should
have
an
announcement
section-
is
there
is
a
contributor
summit
going
on
in
the
north
america
kubecon
in
los
angeles,
and
they
just
opened
up
a
call
for
papers
and
registration
is
now
open.
For
those
that
aren't
aware.
A
But
in
the
past
what
we've
done
is
we've
done
doc,
sprints,
where
we
get
a
group
of
people
together
either
new
contributors
or
existing
and
we've
ran
through
some
existing
problems
issues
or
had
usually
a
unified
goal
in
mind
to
tackle.
We've
also
done
technical,
deep
dives,
where
I've
gone
through
the
actual
code
base.
Where
we
pull
up
a
projector,
we
go
through
the
actual
code
base.
We
say:
here's
how
hugo
works.
A
Here's
where
the
different
aspects
of
the
website
interact
with
each
other,
here's
how
the
sites
are
getting
built
once
again,
more
the
how
the
sausage
is
made
and
allowing
folks
to
ask
questions
and
getting
more
into
the
background
of
sig
docs,
and
that
seemed
to
be
pretty
beneficial
as
well.
So
I'm
putting
it
in
the
agenda.
If
anyone
has
any
ideas
they
want
to
hear
they
want
to
see,
they
want
to
get
involved,
feel
free
to
reach
out
just
to
directly
on
the
sig
doc's
main
channel
there,
and
we
can
definitely
get
something
going
on.
A
I
personally
plan
on
attending
in
person,
if
possible,
that's
a
very
big
asterisk,
depending
on
what's
going
on
in
the
world
and
and
just
know
that
the
meeting
is
supporting,
also
remote
attendance.
So
if
you
do
want
to
get
involved-
and
you
don't
plan
on
attending,
there
is
the
remote
option
still
to
be
active.
A
And
then
the
other
bullet
I
want
to
mention
is
the
kubecon
talk,
so
our
maintainer
track
got
accepted,
and
I
believe
this
came
up
in
a
previous
meeting
as
well.
I
just
wanted
to
keep
it
fresh
in
folks
minds
that
we
need
to
have
some
of
the
content
prepared
and
ready.
I
think
it
was
august
27th,
but
I'll
double
check
on
the
date.
It's
coming
up,
quick
and
we
have
to.
A
A
I
would
imagine
this
is
a
great
opportunity
to
call
out
new
contributors
and
a
great
opportunity
to
talk
about
the
current
state
of
docs.
As
far
as
the
things
I
mentioned
around
co-chairs
and
contributor
ladders
and
I'd
really
like
to
see
a
call
to
action
in
the
kubecon
talk
around
really
supporting
the
documentation,
sub
special
interest
group.
I
think
we
can
make
a
really
powerful
talk
about
around
that.
D
Would
this
be
like
a
recruiting
effort,
or
would
we
be
looking
to
you
know,
clarify
or
give
some
insight
into
how
some
of
the
processes
are
done?.
A
So
I
would
be
open
to
both.
It
really
just
depends
on
on
what
we
want
to
how
we
want
to
present
the
ideas
and
how
we
want
to
present
the
overall
topic
but
yeah.
I
would
foresee
it
being
both
and
less
less
recruiting,
but
more
or
less
saying
here's,
the
state
of
the
world.
Here's
how
you
get
help.
You
know,
here's
how
you
can
get
started.
I
guess
it
is
recruiting.
A
I
just
feel
like
we're
recruiting
to
me
seems
like
we're
going
out
and
plucking
folks
out
of
you
know
somewhere
getting
involved,
but
but
yeah
I
don't
know
if
I
answered
your
question
or
not,
but
I
think
it
could
be
up
to
us
to
decide.
E
So
the
past
few
releases,
1.20
1.21.22
part
of
the
sigdoc's
release
team's
handbook,
is
to
is
to
generate
the
reference
guide.
E
The
past
several
releases,
there's
always
there's
been
issues
in
generating
the
reference
guide,
and
so
I,
what
I
want
to
what
I
propose
is
is
for
those
who
have
the
tacit
knowledge
to
to
generate
these
docs
and
the
api
reference
guide
as
well
to
update
the
role
handbook
with
that,
because
one
for
the
api
reference
guide,
we
just
happened
to
get
a
pr
from
a
github
user
to
update
the
api
reference
guide,
but
we
but
want
to
extract
that
task
knowledge
out,
so
that
so
that
those
skills
are
are
transferable
to
the
next
team
and
so.
E
Yep
there
have
been
some
issues
with
with
go
as
well
and
for
121
and
percy
spent
like
three
days
trying
to
get
it
trying
to
get
that
script
to
work
did
not
get
it
to
work.
So
I
could
take
this
on
personally
just
to
paying
the
the
people
that
I
know
of
who
have
who
do
have
the
task
of
knowledge
and
ask
them
to
document
their
sets
and
add.
Then
we
can
add
that
to
the
royal
handbook
for
the
release
team.
C
Maybe
I
can
ask
a
question:
is
there
some,
like?
I
don't
know
what
people
are
good
at
here?
I
know
a
bunch
of
people
are
good
at
contributing
excellent
technical
documentation,
but
maybe
there's
someone
who's
linked.
Actually,
like
I
don't
know
anything
about
these
reference
docs,
but
I
do
know
you
know
golang
or
you
know
this
is
the
sort
of
reference
generation
is
right
up
my
street
and
yet
you're
thinking
yeah,
but
I
don't
know
the
whole
story,
so
I
couldn't
help.
F
Anyone,
I
don't
know
the
docs
very
well
and
I
don't
know
the
api
spec,
but
I
do
I
mean
I
know
it
enough
as
a
user,
but
I
do
know
go
so
maybe
that's
handy.
A
That's
incredibly
handy
yeah,
what
a
coincidence
and
you're
leading
the
the
upcoming
release.
Oh
yes,
I
am.
G
F
C
To
use
containers
as
a
technology
to
package
up
the
reference
generation
and
make
that
happen
in
a
container
rather
than
on
a
contributors
well
still
on
a
contributor's
pc,
but
moving
it
into
a
container,
enables
a
bunch
of
future
work
and
fits
in
very
well
with
our
cloud
native
philosophy.
C
So
if
you
would
feel
like,
you
could
help
with
that
jesse.
That
would
be
fantastic.
F
C
You
at
the
forest
and
introduce
you
to
people
who
have
got
lost
there.
A
Thank
you
and
thanks
ray
for
bringing
that
up,
I've
got
you
there
driving
this
driving
this
and
it
sounds
like
we
have
some
folks
involved
for
first
solution.
So
that's
great
any
other
things
that
folks
want
to
discuss.
Before.
Moving
on
to
this
other
section,
I
recently
added.
A
Cool
so
moving
on
this
other
section,
it
didn't
really
fit
quite
in
the
discussion
or
issues
and
pr
just
things
I
thought
was
worth
bringing
up.
The
very
first
thing
is:
I
want
to
apologize
to
sigdoc's
community
like
seriously
just
because
I
started
to
or
for
some
of
those
that
know.
A
I've
said
I'm
gonna
upload
the
meeting
videos
for
probably
a
month
or
so
now
I
didn't
realize
until
looking
last
night,
we
don't
have
updated
videos
dating
back
to
february,
and
so
that's
just
not
not
a
responsible
action
as
a
co-chair
and
that's
not
an
acceptable
behavior
and
I'm
surprised
someone
hasn't
nudged
me
sooner.
I
guess
it
shows
how
many
people
really
care
about
the
the
videos
getting
uploaded.
A
But
no
speaking
personally,
though,
I
do
reference
these
videos,
I
do
go
back
and
I
watch
them.
Obviously
I
haven't
done
it
since
february,
but
when
there's
a
meeting
I
miss
it's
great
to
grab
context
so,
for
example,
as
paris
and
I
are
switching
between
hosts
it's
great-
to
grab
contacts
from
a
meeting
that
I
missed
and
being
able
to
jump
in
and
watch
that
previous
meeting.
A
So
we
got
here
because
the
automation
is
broken,
that
uploads
the
videos,
but
still
that's
no
excuse
to
to
have
videos
dating
back
all
the
way
to
february
that
we're
delayed
on
so
once
you
know
it's
kind
of
one
of
those
things
that
started
out
as
a
small
thing,
and
that
was
a
big
thing,
and
so
I'm
apologizing
for
that.
But
now
we're
dealing
with
the
problems
of
having
around
28
total
videos.
We
need
to
upload
and
youtube.
A
Has
a
15
video
upload
limit,
there's
a
24
hour
cycle,
and
so
right
now
I'm
uploading
those
videos.
I
got
them
all
downloaded,
I'm
in
the
process
of
currently
transitioning
those
onto
youtube,
but
but
I
did
want
to
sincerely
apologize
to
the
folks
and
for
folks
that
rely
on
asynchronous
communication
to
these
videos.
So
once
again
it's
really
unacceptable
behavior,
but
we're
making
it
right.
A
And
then
the
next
item
here
is
the
meeting
notes.
I
believe
some
other
folks
in
the
community
may
have
volunteered
to
do
this,
and
so
I
apologize
if
I
was
cookie
looking
or
stepping
on
any
toes,
but
we
converted
the
2020
meeting
minutes
into
markdown.
There
is
instruction
set
in
the
community
documentation
which
I
can
link
in
the
agenda.
A
The
idea
is,
after
a
year
of
sigdoc's
meetings,
the
google
doc
gets
to
be
so
long
and
lengthy.
It
doesn't
make
sense
to
continue
building
on
that
same
doc,
so
usually
annually.
We
will
take
the
year
block
from
january
1st
to
the
end
of
the
year.
We
would
convert
it
to
markdown
using
a
google
doc
plugin,
and
then
we
commit
it
to
the
the
community
repository
there's
instructions
in
the
community
repository
on
how
to
do
that.
I
did
that
for
the
2020
meeting
minutes,
everything
is
good
there.
A
Now
the
last
thing
here
I
don't
know
if
this
has
been
happening
or
was
the
first
time
I
saw
it
with
chrome
version
92
if
you
open
up
a
netlify
preview
window
for
a
pr
there's
now
these
chrome
security
warnings
that
say
like
hey,
did
you
really
mean
to
go
to
this
website?
It
looks
like
you
really
wanted
to
go
to
kubernetes.io
and
is
the
first
time
coming
across
that
it
looks
like
when
you
hit
a
page
with
a
invalid
ssl.
It
goes
completely
white.
A
It
kind
of
looks
a
little
scary
has
a
little
warning
on
it.
You
sure
you
want
to
do
this
type
thing
and
I'm
raising
awareness,
because
if
other
folks
do
this
or
it
becomes
an
issue,
we
might
want
to
document
this
either
in
our
readme,
or
we
might
want
to
find
a
solution
here
on
how
we
don't
have
that
kind
of
scary
message
of
you.
Look
like
you're
getting
hijacked
by
kubernetes,
even
though
you
just
opened
a
pr.
A
Okay,
cool
so
yeah
just
raising
awareness
there
and,
and
just
if
we
start
seeing
more
of
it,
we
know
how
to
respond
to
it.
Maybe
there's
another
option
as
well:.
C
G
If
I
can
just
hop
back
to
your
markdown
note,
if
there's
no
comments
about
your,
your
chrome
warning
go
for
it.
I've
seen
a
couple
of
other
projects,
use
a
site
called
hackmd.io
and
it
looks
like
it's
sort
of
a
a
google
docs
style
tool
that
can
connect
to
a
a
or
a
repo,
and
it
has
when
I
say,
google
docs
style.
G
I
mean
multiple
people
can
can
hack
on
at
the
same
time,
and
it
is
in
markdown
to
begin
with,
so
that
might
be
rather
than
using
google
docs
to
begin
with,
and
then
converting
it
might
be
worthwhile
to
to
explore
other
tools
that
might
be
able
to
to
generate
documentation.
That
is
immediately
able
to
be
put
into
a
terminal
purchase.
A
Yeah,
no,
it's
a
great
suggestion
and
I
personally
love
hackmd.io.
It's
a
great
solution
for
writing
in
markdown.
I
use
it
when
I'm
writing
a
personal
blog
post
or
whenever
I'm
writing
in
markdown.
I
track
a
lot
of
notes
in
there.
I
find
it
to
be
a
great
resource
I
know.
Confer
backs
was
looking
at
converting
all
of
the
all
the
special
interest
groups
to
using
heck
md.
I
want
to
say
that
george
castro
is
leading
that
and
george
castro
stepped
away
into
other
responsibilities.
A
C
A
C
So
you're
really
just
talking
for
the
meeting
agenda,
correct.
Okay,
what
for
just
like
converting
sig
ducts
to
it?
I
think
I
heard
converting
sig,
ducts
and
thinking
okay,
wow.
A
Yep
yeah
it's
strictly
for
the
the
meeting
minutes
and
that
would
just
save
you.
The
extra
step
like
nate
pointed
out.
As
far
as
doing
the
google
docs
mark
duncan
version,
it's
already
in
markdown
copy
and
paste
and
you're
good
to
go.
G
It
would
also,
I
think,
probably
help
searchability,
because
right
now,
if
it's
in
google
docs,
that's
not
necessarily
gonna
show
up
in
searches
where
having
it
publicly
in
the
rebel
might
be
might
be
valuable.
There.
A
Yep
definitely
cool,
I
see
a
couple
plus
ones
in
chat
as
well.
Appreciate
you
bringing
it
up
nate,
I
I
really
don't
know
how
really
we'd
move
that
forward.
I
think
we
should
definitely
keep
this
in
consideration,
but
but
let's
kind
of
see
how
things
unfold
here
and
if
there
is
an
effort
to
go
towards
hack
md,
let's
do
it
I'll
check
in
with
sig
contrib
x
as
well
and
see
if
there's
any
interest
at
unifying
that
effort
as
well.
A
D
Hey
so
clarification,
okay,
so
I
think
I
saw
the
schedule
and
there's
a
talk
wednesday
afternoon
around
dinner
time.
Did
I
see
that
k-8s
sig.
A
Docs
I
haven't
looked
at
the
schedule.
Honestly,
I
don't
know
if
anyone
else
has
confirmed
that.
A
Yeah,
I
would
imagine,
if
you
saw
on
the
sched
website,
that's
probably
accurate
for
the
the
sick
dogs
conference
or
the
talk
it's
that
wednesday
in
the
afternoon.
D
Okay,
this
is
separate
from
the
contributor
maintainer
day:
zero
yeah
effort,
yeah.
A
And
so
that's
a
good
clarification
and
I'll.
Just
kind
of
reiterate
here
is
that
there
is
a
official
kubecon
talk
as
part
of
the
maintainers
track
where
we
sit
there
and
present
what
sig
docs
is
doing
kind
of
a
call
to
action,
a
call
to
help
it's
a
deep
dive
into
sig.
Docs
really
meant
for
any
sort
of
consumption.
New
contributors
folks
are
dabbling
in
documentation.
A
Anyone
who's
attending
the
conference
can
really
just
watch
the
video
or
attend
that
session.
The
contributor
summit
is
really
focused
on
contributors.
It's
really
about
the
the
nitty-gritty
of
running
the
documentation,
sprints
doing
the
technical,
deep
dives
and
is
focused
all
around
empowering
and
growing
contributors,
so
the
difference
being
folks
are
attending
kubecon,
don't
always
have
to
be
a
contributor,
whereas
contributor
summit
is
really
going
to
be
focused
on
contributions.
A
G
Maybe
we
don't
have
time
to
discuss
it
this
round,
but
we've
got
a
lot
of
valuable
links
and
conversation
in
our
chat,
and
I
find
that
with
zoom
the
chat.
Even
if
we
record
the
the
video,
the
chat
tends
to
be
quite
ephemeral
and
I
was
wondering
if
there
was
a
way
that
we
could
not
necessarily
catch
the
chat
verbatim
but
capturing
some
of
the
links
and
whatnot
I
mean
slack.
A
Cool
yeah
that'd
be
a
huge
help,
thanks
for
bringing
that
up
nate
and
thanks
tim.
The
other
comment
I
would
have
is
that
when
you
record
a
meeting
and
zoom
to
the
cloud,
it
does
give
you
a
text
layout
of
the
of
the
chat
of
the
at
least
the
public
chat.
So
we
do
have
record
of
it.
The
challenge
is
normally.
When
I
go
into
zoom,
I
download
the
the
video
it's
going
to
be
the
actual
video
we
upload
to
youtube.
There's
really
not
much.
A
I
feel
like
I
can
do
with
that,
but
but
I
do
want
to
raise
visibility
that
someone's,
like
oh
shoot,
there's
something
in
the
chat
two
weeks
ago
or
last
night.
You
know,
and
I
want
to
reference
it.
There
is
record
of
the
chat
and
it
is
available
in
zoom
that
that
co-chairs
and
tech
leads
have
access
to
capturing.