►
From YouTube: K8s SIG Docs Meeting for 20201006
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
You're,
nothing
welcome
back
everyone
moving
on
to
updates
and
reminders.
This
week's
pr
wrangler
is
brad.
The
official
representative
of
sig
docs,
much
appreciated
sure,
and
next
week
is
raja,
and
I
haven't
spoken
to
raja
in
a
while
so
I'll
message
her
on
slack
and
see
if
she's
still
willing
to
be
a
pr
wrangler.
If
not,
we
might
need
to
volunteer
for
next
week.
A
D
Hello,
this
is
ray
yes,
so
this
past
week
or
last
week,
kristen
synced
the
dev
120
branch
with
master
and
that
pr
was
merged
yesterday.
Thank
you,
jim.
Thank
you
zavita
for
approving
that
pr
also
there's
one
thing.
We
want
to
add
as
an
additional
topic
as
well
and
anna's
here
as
well.
I
want
to
discuss
about
creating
an
extra
pr
template
for
pr's
that
are
related
to
the
release
and
if
we
could
add
a
sentence
or
soon
to
collaborate
a
little
more,
that
would
be
great.
E
Sure,
thanks
ray
so
one
of
the
things
that
was
brought
up
in
multiple
retros,
so
I'm
working
on
a
lot
of
retro
items
from
previous
retros
and
one
of
them
was
how
can
we
make
sure
that
kkprs
are
very
visible
to
the
docs
team
so
that
when
we
go
and
review
and
approve
the
docs
for
the
release
like
we
don't
have
to
go,
find
the
enhancement
and
then
go
find
the
kkpr
related
to
it?
And
my
thinking
was
that
we
could
either
add
like
an
extra
pr
template.
E
But
there's
like
I
actually
tried
this
out,
because
I
didn't
know
that
we
could
do
this.
But
it's
kind
of
like
it's
not
that
great,
because
you
have
to
like
enter
a
query
in
the
url
itself
and
then
list
like
the
pr
template
name
so
that
so
because
there's
already
a
default
pr-
and
I
don't
want
to
get
rid
of
that-
I
want
to
just
add
on
to
another
like
add
on
another
template.
So
I
wasn't
really
sure
exactly
what
the
team
felt
about
it.
E
And
in
addition
to
that,
if
this
doesn't
work
out,
I
was
just
thinking.
Maybe
we
could
replace
or
like
modify
the
existing
dock
that
we
currently
have
for
the
release
to
have
like
a
little
sample
like
a
description,
template
thing
there,
where
people
can
just
like
copy
and
paste
into
the
description.
A
E
I
I'm
actually
on
like
a
new
work
laptop,
so
I
don't
have
it
here,
but
I
can
show
it.
I
guess
next
time
if,
but
it's
like,
I
don't
know
here,
give
me
one
second,
maybe
we
can
move
on
and
come
back.
A
I
was
gonna
say
it's
not
really
a
problem.
I
am
fully
supportive
of
this.
I
don't
know
if
anyone
has
any
experience
in
this
area.
I
personally
haven't
done
anything
here.
I
think
at
the
very
you
know
worst
case
scenario.
We
could
potentially
update
the
template
that
we
have
as
is,
and
it
would
be
an
improvement.
I
would
guess,
but
I'm
definitely
not
opposed
to
this
at
all,
and
I
don't
know,
does
anyone
else
have
experience
in
this
area
with
pr
templates.
A
D
And
one
more
thing
to
add
jim
about
the
120
release.
So
today
is
the
enhancement
sprees,
so
we'll
be
starting
to
track
pr
docs
for
enhancements
for
120.
A
A
All
right,
moving
on
to
localization,
I
know
that
there
is
an
awesome
meeting
kicked
off
on
monday
sounds
like
some
exciting
stuff's
going
on
there.
I
don't
know.
Would
somebody
like
to
give
a
little
more
context
on
what
is
the
localization
working
group?
What
had
happened
and
give
a
little
more
info
to
the
team.
B
Sure
sure
I'd
be
happy
to
jim.
Basically,
we
had
wonderful
representation
from
a
variety
of
the
localization
teams,
and
it
was
a
really
great
opportunity
to
for
each
of
the
teams
to
share
their
best
practices,
so
a
great
way
to
for
us
to
level
set.
Our
kickoff
meeting
was
each
of
the
teams
talking
about
how
they
were
doing
things
most
of
it
revolved
around
how
they
were
updating
their
version
of
the
localization
page.
So,
in
the
english
version,
we've
got
a
localization
page
that
talks
about
how
to
get
started.
B
What
a
lot
of
the
localization
teams
are
doing
is
updating
and
changing
the
content
of
that
page
to
to
describe
how
their
workflow
works,
how
their
processes
work
as
a
concrete
example,
a
lot
of
them
provide
a
glossary,
so
certain
words,
you
know,
like
technical
terms,
maybe
there's
more
than
one
example,
more
than
one
possible
translation
and
so
for
consistency.
B
So
I
think
it
was
in
japanese
there's
like
two
different
terms
for
server
right,
there's,
a
short
version:
okay
and
a
longer
version.
If
I
got
that
right,
and
so
they
have
like
instructions
on
well,
we
should
always
say
use
the
longer
version
or
what
have
you
so?
A
lot
of
great
best
practices
were
captured
in
our
first
weekly
agenda.
B
If
people
want
to
go
look
at
that
and
we
have
sort
of
folks
who
want
to
talk
at
our
next
meeting
and
go
into
more
detail-
and
I
don't
know
if
kohei
wants
to
add
to
that-
he
was
one
of
the
key
folks
talking.
F
Yeah
yeah,
basically,
we
shared
how
we
manage
the
localization
and
its
contents
apart
from
the
english,
and
we
also
have
to
follow
up.
The
english
like,
which
is
the
con,
is
up
to
date,
and
we
are
basically
always
far
behind
compared
to
the
upstream,
so
yeah
we
discussed
how
we
want
to
keep
it
up
to
date
and
yeah.
We
shared
some
strategy,
not.
G
F
From
our
team,
but
also
like
they're,
there
was
a
this
korean
person.
You
know
korean
translation
is
doing
really
well
so
yeah.
I
I
also
learned
a
lot
of
from
from
their
team
too.
So
yeah,
that's
what
happened,
and
I
also
shared
the
link
of
the
last
night's.
I
mean
it
was
night
for
me.
Yeah
last
night's
documentation,
link
google
doc.
So
if
you're
interested,
you
can
have
a
look
at
that
too.
A
B
Just
that
I'm
working
on
as
we
speak,
updating
the
community
yaml
page
and
so
I'm
in
I'm
actually
multitasking
and
doing
that
as
we
speak,
but
just
adding
the
meeting
notes
to
the
community
page
and
then
I'll
add
it
to
the
docs
page
after
I
get
that
one
done
so
that
that's
in
flight,
but
I
didn't
forget
about
it.
B
A
Sounds
good
and
just
talking
a
little
bit
about
how
the
meetings
get
uploaded
to
youtube.
I
think
this
is
a
process,
that's
kind
of
behind
the
scenes
I
wanted
to
share
with
the
team
here.
Just
so
we're
all
aware
of
what
happens.
I
personally
learned
this
recently
as
well,
because
we're
about
a
month
behind
of
our
youtube
videos
uploading
to
to
our
playlist
and
I'm
actually
kind
of
talking-
I'm
jumping
ahead
here,
maybe
talking
about
the
last
section
of
my
head
on
the
agenda
about
fixing
our
youtube
playlist,
but
in
short,
our
zoom
account.
A
The
sigdoc
zoom
account
that
hosts
this
meeting,
that's
pretty
much
the
official.
I
guess
a
sponsor
of
all
of
our
zoom
meetings
has
a
plugin
in
there
and
what
I
mean
by
that
is,
if
you
log
into
zoom
using
the
credentials
for
the
official
sig
docs
account,
you
can
integrate
plug-ins
to
that
zoom
account.
So
I
didn't
know
that
zoom
had
plug-ins
but
apparently
there's
a
whole
plethora
of
plugins
that
you
could
use
to
improve
your
zoom
experience.
A
I
had
no
idea
honestly,
so
one
of
those
plugins
is
called
splain
and
splain.
What
it
does
is
connect
zoom
to
youtube
and
what
spline
does
is
whenever
the
meeting
is
recorded
to
the
cloud
it
will
say.
A
When
I
asked
do
we
need
to
like
unsync
the
plugin
and
re-synchronize
it
or
do
some
sort
of
like
wake
it
back
up.
Bob
killen
told
me
no,
this
plane
just
pretty
much
is
like
that
and
it
might
fix
itself,
and
it
might
not
so
we'll
give
it
a
few
more
weeks
here,
like
I
said
I'll
manually,
upload
this
video
most
likely
I'll
upload
the
video
from
monday.
It
sounds
like
they're
still
not
moving
forward
on
that
when
I
upload
it
manually,
I
use
my
own
personal
account.
I
upload
it
there.
A
I
disable
comments,
I
add
it
to
the
playlist
kind
of
clunky,
but
I
know
there's
other
people
in
the
community
that
do
the
same
thing
there,
but
the
reason
I'm
going
into
this
much
details.
This
whole
process
was
completely
like
blind
to
me.
I
had
no
idea
how
this
is
getting
managed.
What
people
are
doing,
and
I
wanted
to
share
that
with
more
people.
B
A
B
A
Really
don't
see
a
problem
with
that
unless
there's
a
reason
to
break
it
out,
I
could
be
swayed
the
other
way
saying
that
maybe
you
want
all
the
localization
stuff
separate
so
then
folks
could
review
it
separately,
but
I
got
no
opinion.
B
A
Cool
yeah,
I
say:
let's
do
that,
we'll
keep
it
simple,
put
in
the
same
playlist,
be
all
good
there:
okay,
great
cool,
so
moving
on
to
the
next
agenda
item
for
issues
and
prs
and
also
there's
anybody
else
on
the
call
who
has
any
issues
or
pr's
feel
free
to
link
them
down
there
or
throw
them
in
chat.
We
could
talk
about
them.
The
one
that
I
wanted
to
bring
to
folks
attention
was
the
hacktoberfest
and
spam.
A
If
you
get
five
contributions
in
before
the
end
of
the
month
up
to
70
000
entries,
it
unfortunately
leads
to
a
lot
of
spam
and
a
lot
of
spam
pr's
where
maybe
they're
lacking
a
quality,
and
this
is
a
little
bit
of
a
challenge
more
so
I
think
for
docs
than
any
other
area
of
kubernetes,
or
maybe
you
know
the
open
source
community
documentation.
In
particular,
we
have
those
simple
small
prs.
We
have
those
drive
by
pr's.
A
Personally,
I
got
into
contributing
to
open
source
by
creating
some
of
those
small
lack
of
really
any
true
sustenance.
Pr's
that
you
know
now
could
be
considered
spammy.
So
there's
this
kind
of
fine
line.
You
have
to
walk
when
you're
reviewing
these
pr's,
because
you
start
to
get
this
influx
of
prs
and
you
have
to
determine
whether
they're
spammy
or
not,
and
kind
of
walk
that
fine
line
of
being
in
an
inclusive
community
at
the
same
time
rejecting
spam
for
oktoberfest
for
a
free
t-shirt.
A
Luckily,
for
this
event
in
particular,
maybe
not
luckily
unluckily,
there
was
a
very
specific
youtuber
who
was
popular,
who
gave
a
very
clear
instruction
set
on
how
to
create
spammy
pr's,
which
would
be
like
open
up.
The
readme
and
add
dash
is
awesome
to
the
word
kubernetes,
and
so
what
we
ended
up
seeing
was
an
influx
of
about
50
to
60
prs
within
24
hours
of
everyone.
Just
adding
these
real
trivial
dashes
awesome
prs
to
the
readme.
A
There
was
folks
updating,
localization
readings
in
english,
even
though
they
weren't
they're,
adding
english
content
to
non-english
files,
for
example.
So
this
is
just
bringing
awareness
to
this.
There
is
a
happy
ending
here.
Digitalocean
realized
the
negative
impacts
to
maintainers
in
the
open
source
community
that
this
had
brought
and,
as
a
result,
they've
switched
their
rule
set
to
make
it
so
opt-in.
So
not
everybody
can
just
create
prs
in
any
project.
A
They've
started
to
open
up
round
tables
with
community
maintainers,
so
they
wanted
to
learn
how
they
can
make
this
event
better,
how
they
can
really
encourage
growth
in
a
more
healthy
manner
and
they've
started
to
detect
what
is
the
spanning
pr's
on
their
end.
So
they're
not
awarding
t-shirts
to
folks
who
are
just
doing
these
fly-by-spamming
pr's
and,
I
say
family
with
a
clear
distinction
of
spamming
pr's
for
a
free
t-shirt
and
fly
by
pr's
that
we
want
to
encourage.
A
H
So
digital
digitalocean
put
some
community
feelers
out
and
I've
booked
in
on
friday
to
a
maintain
a
roundtable,
an
open
source
maintain
a
round
table,
slash
group
therapy
session.
So
I'll
report
back
on
that.
The
next
time
I'm
at
a
weekly
meeting
for
sick
docs.
H
And
other
areas
you
know,
saw
the
the
bat
signal
go
up
and
I
had
an
easy
time.
But
there
were
a
lot
of
prs
getting
closed.
H
B
A
Yeah
I
was
gonna
big
plus
one
to
that
tim
as
well,
there's
a
lot
of
folks
who
contributes
in
the
greater
kubernetes
community
that
saw
kubernetes
website
repo
getting
spammed
and
they
jumped
in
right
away
to
help
and
before
I
would
even
see
a
pr
hit,
it
would
most
likely
have
been
closed
by
someone
from
confirmed
x.
They
were
lightning
quick.
They
dumped
two
of
the
tasks
at
hand
and
definitely
a
big
shout
out
to
them,
and
thanks
for
helping
on
that.
D
I
had
a
question
on
not
really
spammy
issues,
but
I've
seen
some
issues
that
are
more
like
support
issues
created,
and
I've
promised
in
the
past
to
to
try
to
kubernetes
use
your
slack
channel
stack
overflow
or
the
office
hours
link,
but
is
there?
Is
there
like
a
proper
flow
on
like
and
like
how
to
close
it?
Besides
asking
the
author
to
close
it?
So
the
author
may
not,
you
know,
may
not
go
back
and
close
it
after
some
time.
They
still
want
their
answer
to
the
support
question.
A
A
A
A
Here
are
no
strong
opinions,
one
way
or
the
other
yeah
like.
I
said
so
kind
of
once
again
that
that
fine
line
to
balance
I'm
more
than
happy
to
help
out
folks
who
you
know
message
me
on
slack,
find
me
on
github
but
there's
an
open
issue.
It's
a
support
issue,
no
real
action
to
be
taken.
I
see
no
issue
and
just
saying
very
politely,
hey
look.
This
is
a
support
thing.
Here's
where
you
can
get
help
reach
out
to
me.
If
you
have
any
questions,
things
of
that
nature.
A
Cool
and
it
looks
like
in
chat
here-
we
have
apr,
it
looks
like
this
needs
to
be
approved
and
merged
and
there's
been
a
review
applied
by
raghav
and
I
say
the
name
right,
ragam
fund.
A
Awesome
sorry
about
that,
so
anything
in
particular
with
this
issue
brought
up
or
just
looking
for
approvers
to
get
more
eyes
on.
A
H
So,
looking
at
that
pr,
I
think
it
could
use
maybe
a
couple
of
tweaks
to
to
the
the
english
it
hasn't
been
reviewed.
Yet
to
do
that,
that's
that's
what
I'm
seeing
sort
of
after
a
quick
look
sure
we
did
have
a
busy
week.
C
C
That
yeah
then
at
least
yeah
big.
I
know
awesome.
B
Yeah
I
mean
I
I'm
working
through
the
list
as
pr
wrangler,
so
I'll
write
it
down
and
make
sure
I
get
to
it.
I
mean,
obviously,
if
it's
just
english
tim
I'll
take
care
of
it.
B
So
it's
24
35.
A
Cool
anything
else
folks
want
to
talk
about
regarding
the
agenda
before
moving
on
to
process
the
fun
stuff.
H
Can
I
can
I
add,
since
there
are
a
bunch
of
people
on
this
call,
so
sigdocs
is
having
a
chat,
a
talk
at
the
next
kubecon
and
before
the
end
of
this
meeting.
If
anyone
wants
to
suggest
a
thing
that
they
wish
they'd
known
when
they
started
contributing
to
sig
docs
into
the
website,
I
should
have
asked
this
earlier,
but
just
a
cropped
up
in
my
mind,
I'd
be
good
to
hear.
C
H
So
sigdocs
at
the
next
kubecon,
which
is
online
and
virtual,
is
presenting
a
talk
introduction
to
sigdocs.
H
What
do
you
now
with
a
bit
of
experience
and
hindsight?
What
do
you
now
wish
that
you
had
known
when
you
first
started
contributing
if
people
have
suggestions
as
to
what
should
be
in
that
talk
because
of
something
they
wish?
They'd
known,
it'd
be
great
to
hear
it
either
in
this
call
or
in
the
slack
channel
afterwards,.
A
A
The
first
day,
before
cube
kind
of
happens
where
it's
for
contributors
there's
not
usually
a
traditional
sig
docs
conference
like
event
in
kubecon,
we
don't
really
do
any
deep
dives,
we
don't
do
any
intros,
and
so
this
is
a
first
for
sig
dax
board,
there's
no
contributor
summit,
but
there's
actually
an
official
kubecon
talk
and
what
I
would
imagine
will
happen
is
similar
to
other
intros
and
deep
dives,
because
that's
the
other
thing
too
is
there's
no
longer
two.
Two
talks
for
each
sig.
A
A
Cover
an
introduction
to
what
sig
docs
is
what
we
do
moving
on
to
more
of
the
deeper
things
there
in
the
span
of,
I
think
it's
45
minutes
we
have
plus
tim,
brings
up
an
excellent
point
if
there's
folks,
who
are
completely
new
to
docs,
what's
important
to
them,
you
know
there's
no
point
in
preaching
to
the
the
people
who
have
already
been
involved
in
sick
docs.
It's
what
do
you
wish?
You
would
have
known
before
joining.
A
Cool
yeah,
I
know
personally,
I
I
think
you
know
starting
thinking
back
when
I
joined
sig
docs,
my
biggest
blocker
was
the
process
like
how
things
get
approved,
how
things
get
in
what
the
lingo
is.
Lgtm,
slash,
approve,
slash,
label,
slash
block
this
slash.
You
know,
you
know
what
have
you
there?
I!
A
I
don't
know
how
you
can
teach
that
necessarily
to
folks
who
are
new
or
joining
about
what's
important,
because
there's
so
much
to
learn
how
docs
are
getting
merged,
how
they're
getting
approved,
who
reviews
them
who's,
giving
attention
to
issues.
Where
do
you
get
help?
You
know
things
of
that
nature.
So,
personally
speaking,
that
was
a
big
learning
experience
for
me
that
I
just
kind
of
acquired
over
time.
G
As
for
me,
I
think
it's
it's
also
about
process,
but
the
difference
is
like
when
I
try
to
ask
for
a
review.
I
don't
know
the
comment
that
so
usually
the
suggestions
is
not
belongs
to
those
who
are
the
revealed
pr
or
the
someone
who
has
a
native
language
for
that
specific
language.
So
it's
kind
of
like
really
difficult
for
me
to
ask
for
review
from
the
right
person.
I
guess.
B
I
mean
just
a
logistic
issue
with
zach
being
out
a
little
bit
do
and
the
other
folks
that
are
on
the
hook
for
presenting
at
the
conference,
I
think,
is
celeste
and
tim
and
myself
tim
are
you
on
point?
I
know
I
I
think
I
had
given
you
a
copy
of
my
deck,
but
are
are
you
which
one
of
us
is
kind
of
running
with
it
to
make
sure
we're
going
to
be
ready
to
record
and
all
that
good
stuff?
So
I
don't
know
who's
in
charge.
H
H
There's
a
just
be
clear:
loads
of
people
have
shed
decks
with
me
and
the
one
that
I
think
brad's
talking
about
I
haven't
seen,
doesn't
mean
I
haven't
been
sent
it,
but
it
hasn't
gone
in
front
of
my
eyeballs.
H
Cool
there's
a
direct
I'll
dm
you
about
that
brad.
F
So
regarding
this
I
have
a
question
so
since
we
opened
a
new
subgroup,
look
for
localization!
Do
you
think
we
can
talk
about
that?
A
little
bit
of
this
talk,
or
should
we
like
separate
that
from
the
sig
docs
itself.
A
I
think
that'd
be
very
important
to
include
this
localization
working
group,
at
least
to
mention.
At
the
very
least
you
know
I
know,
since
it
is
a
working
group
and
it's
underneath
the
umbrella
of
sig
ducts,
I
would
imagine
there
would
be
a
mention
about
blog,
which
is
also
a
sub
project,
as
well
as
the
localization,
pretty
much
all
things
that
are
docks.
What
do
you
need
to
you
know?
Take
someone
from
who's
completely
new
to
docs,
to
more
experience
in
45
minutes
easy
as
that.
F
Yeah,
like
even
just
five
minutes-
or
you
know
on
that,
just
fine.
If
there's
any
time
that
we
can
talk
about
localization,
we
can
absolutely
help
you
guys.
G
The
thing
is
why
this
is
will
be
interesting,
because
when
people
start
to
contribute,
I
think
they
will
feel
more
safe
when
they
contribute
in
their
own
language,
or
at
least.
G
A
D
A
A
So
the
last
thing
on
our
agenda
here
I
already
touched
on
the
youtube
playlist.
It's
fixed,
there's
a
link
there,
but
the
last
thing
on
our
agenda
is
quarterly
queue
for
planning
dates.
So
traditionally
we
kind
of
throw
out
a
date
there
if
it
works
for
folks
great.
If
there's
some,
you
know
people
we
can
accommodate,
for
we
can
definitely
move
this
or
change
it
around
right.
Now
I
put
the
tentative
date
as
thursday
october
22nd
at
5
p.m.
Pacific.
A
The
challenge
we
face
is
meeting
everyone's
locality
as
well
as
making
it
a
time,
that's
friendly
for
everybody,
and
it's
not
a
perfect
answer.
So
what
I've
done
is
copied
off
of
what
we
did
in
july.
So
for
the
q3
planning
we
did
a
5
pm
thursday
meeting.
So
there's
no
science
behind
that
date.
It
doesn't
have
to
be
that
date
or
time,
but
that's
what
I'm
suggesting
does
anybody
have
any
strong
opinions
can
make?
It
cannot
make
it
based
on
that
october.
25Th
22nd
deadline.
Sorry.
A
Cool,
so
hearing
no
major
objections,
I'll
keep
it
at
that
time
frame.
If
there's
anyone
who
completely
objects
to
it
has
any
issues
feel
free
to
reach
out
on
slack
what
I'll
end
up
doing
is
and
why
it's
important
to
set
this
date
is
I'll
open
up
a
doc
for
the
q4
planning,
and
it
allows
people
to
review
where
we're
at
what
we're
planning
on
talking
about,
as
well
as,
if
there's
any
new
big
initiatives
that
folks
want
to
talk
about
at
the
q4
planning
or
things
that
folks
want
to.
A
You
know
sign
up
for
tackling
it's
really
more,
the
long
term
goals
of
sig
docs
and
the
purpose
of
it
is.
You
know
we
do
a
lot
of
day-to-day
churning
of
you
know:
merging
prs,
maintaining
dog
health,
maintaining
community
health.
This
is
more
of
the
bigger
picture.
I
know.
For
example,
one
of
my
items
from
q3
planning
was
improving
the
release
process,
and
so,
like
that's
a
wider
goal,
it's
going
to
span.
You
know
multiple
quarters,
it's
going
to
span
multiple
releases
and
it's
going
to
be
something
that
that
involves
tracking.
A
F
One
thing
one
one
question
yep,
so
sorry,
I'm
bringing
back
to
the
topic
about
the
cube,
call.
What's
the
deadline
for
contents
decision
making
do
we
have
no.
H
Particular
deadline,
so
we
we,
the
people
doing
the
talk,
have
to
have
our
slides,
update
uploaded
by
I
think
the
last
week
in
october,
but
in
terms
of
what
goes
in
there
like,
if
we
haven't
got
it
done
in
a
couple
of
days
like
I'd,
say
monday
next
week
would
be
quite
late
to
have
decided
what
the
content
is,
because
we
need
to
actually
rehearse
and
record
it.
F
I
asked
them
that
question
because
we
we
basically
decided
the
sig
docs
localization
meeting
just
one
once
a
month.
So
if
we
ever
talk
about
anything
about
localization,
I
think
we
have
to
set
another
meeting.
B
Well,
yeah,
but
I
think
you
gotta
remember
that
we've
got
about
45
minutes
for
this
presentation,
which
is,
and
then
you
have
to
leave
time
for
questions,
and
so
it's
my
guess
that
really
what
we'll
get
to
in
the
presentation
for
localization
will
be
a
nice
chart.
I
mean
there's
already
content
in
the
deck
for
for
localization,
but
a
nice
chart
talking
about
and
highlighting
that
we
have
a
localization
subgroup
and
here's
what
the
goals
and
the
mission
statement
are.
B
My
my
guess
is
we're
not
going
to
be
able
to
get
to
more
than
that,
because
it's
not
like
the
old
days.
G
B
B
G
H
A
The
slide
presentation
yeah,
I
think
one
thing
we
could
always
do-
is
share
out
the
slides
once
they're
prepared
or
at
that
final
draft
state
share
them
out.
The
group
is
read
only
or
something
let
folks
make
comments
to
them,
or
you
know
make
a
copy
of
it.
If
you
want,
I
think
that'd
be
there's
no
drawback
to
getting
more
feedback.