►
From YouTube: K8s SIG Docs Meeting 20191211
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
Alright,
hello,
everybody
welcome
to
the
weekly
Sig
Doc's
meeting
Tuesday
12:30
Central
Time,
my
name
is
Jim
angel
I
will
be
your
host
today.
So
kicking
things
off.
Let
me
take
a
look
here
at
the
agenda.
First
things.
First,
do
we
have
any
new
contributors
joining
us
today
on
the
call
that
like
to
introduce
themselves.
A
A
B
Sort
of
skipping
ahead
to
an
item
a
little
further
down
the
agenda,
which
is
I'm
on
the
hook
for
wrangling,
the
PR
regular
schedule
for
the
first
half
of
2020
and
I
have
not
yet
wrangled.
The
folks
I
asked
to
help
me
and
next
week
is
the
we
moved
the
AIPAC
friendly
time.
That's
a
meeting.
I
can't
make,
and
a
lot
of
folks
on
this
call
don't
make
that
meeting
either.
B
So
I
think
that
what
we
should
do,
I'm
suggesting
because
I
think
we've
got
time
and
in
this
meeting
I
will
go
in
and
take
a
first
pass
on
my
own
and
ping
Jim
and
Brad
and
Caitlin,
who
all
agreed
to
help
wrangle
this,
and
then
we
can
do
it
asynchronously,
because
I
think
that's
going
to
be
the
most
efficient
way
to
get
it
up
before
the
end
of
the
year,
so
that
people
know
what's
coming
up
and
so
that
there's
time
to
say,
hey,
wait.
A
minute.
B
I
can't
make
this
week
can
I
switch
around
or
somebody's
missing
from
the
list,
even
though
Zach
did
go
in
and
clean
up
the
owners
file.
Just
so,
we
have
a
little
bit
more
time.
I
should
be
able
to
get
to
that
the
for
next
Tuesday's
meeting.
So
those
of
you
who
are
in
the
meeting
can
announce
it
and
then
I
will
also
put
it
in
the
cigar
channel,
with
my
apologies
for
not
having
it
ready
for
this
week,
but
I
think
we
can
close
the
communication
loop
and
we
can
continue
to
adjust.
B
C
B
A
Cool
so
moving
along
here
with
our
agenda,
given
a
quick
update
on
the
release,
a
big
congratulations
to
Domini
and
the
release
team
for
cig
Doc's,
the
117
is
out
the
door
successfully
yesterday,
so
big
congrats
to
them.
We
had
a
few
snags
with
the
117
branch,
or
that
I
should
be
more
clear.
The
116
release
branch,
which
was
the
master
branch
yesterday-
that
gets
kind
of
I,
guess,
unscented
and
I
guess
this
might
be
a
good
opportunity
to
quickly
just
talk
about
the
the
branching
strategy.
So
we
traditionally
work
out
of
the
master
branches.
A
All
of
our
documentation
goes
into
master
and
as
part
of
the
release
process,
we
then
still
work
out
a
master
so
think
of
it.
This
way,
on
Monday
the
release
day
when
1:16
becomes
1:17
and
theory,
we
don't
change
anything
from
a
kubernetes
website
perspective.
It's
still
getting
operated
on
out
of
the
master
branch.
So
what
we
do
is
at
the
time
that
we
release
a
version
of
kubernetes.
Is
we
take
like
a
snapshot
if
you
will
of
the
current
state
of
master
and
put
it
in
a
release?
A
Whatever
that
current
version
is
so
we've
had
recently
today
with
this,
were
yes
yesterday
with
the
117
release
was
when
we
went
to
cut
that
snapshot
of
master
and
put
it
in
a
release,
116
kind
of
bucket.
If
you
will,
there
was
commits
from
different
localizations
that
have
overlapped
and
conflicted
that
Damini
had
to
resolve
so
we're
in
a
good
spot
right
now,
where
we
have
the
117
Doc's
live.
A
However,
the
release
116,
which
is
the
old
state
of
Master,
has
emerged
conflicts
and
that
the
mayonnaise
currently
working
on
resolving
so
I
think
we
have
some
future
meetings
there.
Some
future
discussions
on
branching
strategy
and
how
we
handle
this
moving
forward.
We
haven't
seen
this
in
particular,
or
this
issue
in
particularly
on
this
portion
of
the
release,
but
every
time
we
do
have
a
release,
there's
always
some
sort
of
fun,
so
keep
it
ever
enough
to
end
that,
and
a
big
thanks
to
the
folks
who
helped
out
with
the
release.
Yesterday,
I
got.
A
So
that's
a
great
question
and
that's
really
what
I
talking
about
where
master
doesn't
have
any
sort
of
change?
If
you
will
so
we're
still
operating
on
a
master
really,
what
happens?
Is
we
take
a
snapshot
of
the
git
commit
before
we
release
the
blog
unless
they
release
the
blog?
Usually
every
single
Cooper
news
release
has
like
a
CN,
CF,
official
blog
post.
That
goes
out.
So
it's.
A
Whatever
point
does
the
blog
get
merged?
Yes
use,
the
blog
is
merged
and
theory
quote
I'm
doing
air
quotes
here
and
theory
now
master
Butte,
1:17,
so
kind
of
a
fun
fact.
There's.
When
you
go
to
the
kubernetes
website,
then
you
use
those
top
drop-down
menus
to
switch
different
versions.
Each
version
goes
to
a
different
branch
on
the
kubernetes
website.
The
main
one
being
latest
goes
out
of
master
to
go
into
one.
Sixteen,
that's
the
release.
116
branch
I
was
just
referring
to
that.
Has
some
merge
conflicts
currently
and
his
name
down
the
row.
D
A
B
There
is
I
think
of
variables
that
are
supposed
to
pull
in
the
version
number
two
that
snippet
and
it
doesn't
always
happen
either
that
or
it
was
broken
and
somebody
accidentally
hard-coded
it
and
overrode
the
variable
anyway.
There's
there's
various
possibilities
for
why
that
happened.
It's
not
I'm
pretty
sure
this
is
not
a
brand
new
thing
to
this
release
alone.
B
A
D
D
A
And
just
add
to
that
quick
so
that
release
the
big
piece
is
getting
the
117
drop
down
working,
getting
the
blogpost
release
and
actually
getting
the
release
moving
forward
and
out
the
door,
but
inevitably
there's
always
some
sort
of
you
know
one
offer
to
office
or
sometimes
three
offs,
that
we
have
to
go
back
and
patch
in
and
change
and
then
usually
when
things
like
this
happen,
we
go
and
update
the
release
team
handbook.
So
we
can
try
to
avoid
that
in
the
future,
but
good
Bernays.
A
B
B
I
will
continue
to
attend
meetings
as
I
can
I
will
keep
myself
in
the
approval,
rotation
and
contribute
as
I
can,
but
in
a
more
of
a
sort
of
a
mentoring
and
emeritus
status,
possibly
analogous
to
Jared's
and
to
keep.
This
is
a
three
person
lead
role
going
Kaitlyn
Bernard
has
agreed
to
step
up
so
take
it
away.
Kaitlyn,
introduce
yourself
to
people
who
might
not
be
familiar
with
I
mean
Kaitlyn
is
amazing,
she's
been
wrangling,
the
blog
for
forever
and
expanding
that
role
into
more
and
more
docs
leadership
facto
anyway.
E
Awesome
thanks
so
much
Jennifer
I
know:
I
I
speak
for
pretty
much
everyone
when
I
say
thank
you
for
all
of
your
leadership
and
all
your
contributions
to
the
team,
but
I'm
super
excited
to
be
stepping
up
into
this
role.
I've
been
caught,
I
think
involved
in
sigdoc
now
for
the
past
two
to
three
years,
or
so
primarily
and
the
bloggin
formalizing
all
of
that
process,
so
I'm
really
looking
forward
to
working
it
with
you
all
now
in
a
chair
position,.
D
A
Awesome
yeah.
Thank
you
very
much.
Thank
you.
Jennifer
Thank,
You
Kayla,
when
both
of
you
have
been
around
since
I've
joined
him
in
part
of
sig
Docs
and
have
been
helpful
for,
for
me
at
least,
and
through
my
journey
in
sig,
Docs
and
I
I
can't
say:
I
would
be
as
successful
today
without
some
guidance
and
leadership
from
everybody
here
on
this
call
and
and
peers
of
ours.
As
part
of
this
call
so
I
know
you're
not
going
anywhere
Jennifer,
but
we
will
miss
you
and
looking
forward
to
working
more
with
you
Kaitlyn.
A
C
E
Yeah
sure
I'll
I'll
give
some
context
here
so
last
week
it
became
clear
that
I
we
haven't
really
given
enough
guidelines,
I
think
to
a
lot
of
people
with
approver
status
on
some
of
the
outlier
cases,
all
say
of
what
needs
to
be
routed
to
different
teams.
What
different
teams
need
to
review
and
stuff
like
that?
For
example,
we
have
formalized
the
blog
review
process
into
a
separate
team
earlier
this
year
and
are
trying
to
better
communicate
out
some
of
those
changes.
E
You
know
what
should
what
would
the
LGG
and
label
should
be
approved?
What
needs
go
to
the
blog
team?
What
should
be
a
chair
level
review
stuff
like
that
to
definitely
feel
free
to
take
a
look
at
the
stock.
I
would
also
love
any
feedback
for
how
this
information
can
be
presented,
more
helpful
to
people
so,
and
this
talk
is
just
be
one
so
far
so
Brad
anything
dad.
No.
C
You
know
I
think
one
of
the
reason
we
ran
into
this
is
there
would
be
certain
areas
that
that
we're
not
my
area
of
expertise,
a
you
know
that
are
more
on
the
platform
infrastructure
side,
maybe
tweaking
a
cascading
style
sheet.
So
me
personally,
I
would
never
hit
one
of
those
issues
and
trying
to
prove
him.
I
was
always
very
careful
to
route
them
to
two
to
a
chair
or
somebody
who
who
seemed
to
have
that
experience.
C
But
if
you
make
someone
an
approver
and
it
turns
out
they
have
that
background,
they
look
at
that
and
say:
oh
that's,
just
like
making
an
approval
just
like
making
a
documentation
approval
and
so
realizing
that
different
people
with
different
backgrounds
come
in
and
they
might
feel
confident
to
approve
something.
But
the
reality
is.
Is
we
had
some
tribal
knowledge
that
said?
Listen
certain
things
go
to
chairs
certain
things,
go
to
blogs
and
let's
try
and
make
that
more
clear.
So
we
all
don't
get
freshmen
at
each
other.
C
I
think
it's
a
good
way
to
look
at
it.
So
I
know
we've
both
been
trying
to
add
all
the
use
cases
we
found
you
need
for
this.
You
need
to
worry
about
this
or
don't
approve
this
or
you
know
this
needs
to
be
routed
to
a
chair.
I
think
we've
got
them
all
in
I.
Think
the
one
I
was
a
little
worried
about
was
really
understanding.
What
is
connotes
and
architectural
change?
Are
there
certain
files?
You
know?
C
Is
it
you
know
it
was
really
easy
for
me,
because
there
are
certain
pieces
of
the
platform
infrastructure.
I
was
like
I'm,
not
touching,
that
that
that's
Jared
or
that's
Zach,
without
GM
or
Jennifer
right,
but
we
needed
something
better
than
that
sort
of
very
ad
hoc,
so
I
think
that's
what
we're
trying
to
accomplish.
B
Yes,
I
would
take
a
look
and
try
to
help
address
the
what's
the
best
way
to
sort
of
include
and
present
this
information
on
the
page.
If
that
question
is
still
outstanding,
I
do
think
this
is
absolutely
awesome
and
just
I
mean
all
the
like.
Continuing
refinement
that
we
do
of
kinds
of
changes,
and
you
know
who
should
who
should
do
what
kinds
of
things
what
you
said,
Brad
about
CSS
was
just
like
really
rang
home.
B
B
D
So
it
says
serve
as
a
new
contributor
ambassador
and
then
below
that
section
says.
Current
new
contributor
ambassadors
are
announced
at
each
cig,
docs
meeting
in
the
cig,
docs
Channel
I've
always
had
the
cig
Doc's
channel
open
every
day.
I
have
not
seen
that
announcement.
Is
that
something
that
we
was
a
good
idea?
One
point
is
that
still
something
that
is
that
happens,
I.
C
Yeah
I
mean
we
had
sort
of
this
sort
of
a
new
leadership
role
of
the
the
sigdoc
ambassador.
So
if,
if
there
was
a
new
person
shows
up
in
the
channel
and
they
need
a
friend
or
a
helping
hand
or
someone,
they
can
feel
comfortable.
Asking
questions
to
that
was
the
signal
ambassador
and
I
I
know
I
volunteered
to
do
it.
So
if
anything,
pops
up,
you
know-
and
someone
says,
hey
Brad.
C
Can
you
go
just
check
on
this
person
or
help
this
person
so
I
know
it's
at
least
for
the
one
time
they
mentioned
me
or
I?
Think
we
announced
it
once
but
I
guess
it
doesn't
happen
that
often
I
guess
we
could
always
use
more
ambassadors.
But
if
you
volunteer
to
be
one
on
we'll
be
happy
to
make
sure
your
name
gets
announced
in
the
slack
Channel,
it's
just
a
nice
role.
If
that's
what
it
was
referring
to,
you.
B
Listening
to
you,
I
was
thinking
I,
wonder
and
I
was
part
of
the
group
that
originally
brainstormed
this
role.
Maybe
Jared
has
recollections
here
too,
and
but
I
don't
recall
this
particular
piece
of
it.
It
seems
to
me
as
though
it
could
be
a
really
good
idea,
though,
to
commit
ourselves
to
regularly
announcing
who
the
current
contribute.
New
contributor
ambassador
is
both
in
the
sick,
docks
meeting
notes
and
in
the
channel,
because
of
course,
yeah
contributors
aren't
gonna,
know
so
good
point.
G
B
C
B
Of
the
agenda
you
know
reminder
you
know:
new
contribute
new
contributors,
here's
your
new
contributor
ambassador.
We
could
put
that
as
part
of
the
that
piece
of
the
agenda
so
that
can
wrote.
You
know
that
can
be
just
a
regular,
weekly
saying
and
then
like
every
other
week,
we
dump
it
into
the
channel,
that's
kind
of
what
you
were
expecting
David.
That's
what
I
heard
as
you
absolutely.
D
Yeah,
that's
it
yep,
just
kind
of
who
has
that
role
for
the
for
the
month,
and
you
know
I'm
new
to
the
PR
thing
myself.
So
I'd
like
to
document
my
learnings
from
that
so
I
might
reach
out.
We
might
post
that
first
on
the
sick,
docs
channel
check
that
box
off
and
then
I
might
reach
out
to
Brad
or
whoever,
whatever
brave
soul.
I
know.
A
Also
yeah
I
think
this
is
all
great
feedback.
I
did
take
note
that
we
should
look
into
more
formally
announcing
that
new
contributor
investor
role
and
I'd
like
to
take
that
do
an
action
item.
I,
don't
know.
Is
there
anyone
willing
to
own
that
or
to
see
that
actually
throughout
I?
Don't
have
the
cycle
at
the
moment
for
seeing
this
through,
but
to
some
on
the
call
that
will
have
the
bandwidth
to
take
on
the
new
competitor,
Nukem
bass
or
new
contributor
ambassador
role
and
making
sure
that.
C
A
A
Talking
more
about
the
next
step,
so
it
seems
like
we
all
agree.
This
is
a
generally
a
bad
idea
and
it
seems
like
it
would
be
beneficial
to
folks
new
to
cig
docks
I'm,
seeing
that
we
actually
are
promoting
it.
Seeing
that
we
are
actually
every
two
weeks
and
announcing
and
keeping
in
the
meeting
agenda,
keeping
it
fresh
someone
to
actually
take
the
ownership
of
the
day
twos
operations
of
maintaining
that
I.
B
F
F
So
I
think
we
should
just
like
put
it
in
the
media
agenda
to
announce
it
in
January
and
I
think
maybe
just
putting
a
list
of
names
out
there
like
here
and
your
contributor
investors
that
you
can
reach
out
to
who
are
able
to
help
out.
If
you
are
a
new
contributor
and
you
don't
know
where
to
start
and
then
weekends
for
Shepherd
them
through.
A
F
I'm
working
with
Zack
on
that
as
well
so
there's
a
since
I've
worked
on
doxy
here
at
Google,
I
feel
like
I,
should
be
somewhat
responsible
for
helping
kubernetes
land
that
so
I
have
synced
the
contractor.
That
Zack
has
lined
up
with
some
other
fellow
tech
writers
here
at
Google,
the
bolts
to
work
on
doxy,
and
so,
if
there
are
any
questions
or
snags
that
we
hit
during
the
migration
there'll
be
some
technical
expertise
available
to
draw
up
on.
F
D
Yeah
I
spun
up
Doxey
on
my
home
lab
and
push
it
out
to
s3
you.
It's
really
fun
to
play
with
actually
I'm
curious.
If
Zack
has
any
ideas
for
customizations.
If
because
it
does
look
pretty
straightforward
and
plain
so,
I
would
think
there'd
be
kind
of
like
some
kind
of
visual
uplift
as
its
you
know,
put
into
production,
because
it's
that's
kind
of
what
I
would
assume
yeah.
F
D
A
Awesome
I
made
a
note
there
David
about
the
visual
uplift,
so
we
can
bring
that
back
around
next
week.
If
you
like
wins
except
I,
agree,
it
sounds
like
right,
we're
all
in
the
same
page
there
that
visual
uplift
is
long
overdue
and
that
I
think
it's
the
ongoing
joke
that
the
website
is
the
best
that
2012
has
to
offer
so
we'll
get.
There
will
be
better
and
moving
on
the
kept
update.
So
this
is
gonna.
Also
look
toward
Zack,
Ford
I
know.
A
A
And
I'll
add
the
link
to
the
agenda
as
well.
If
it's
not
buried
down
there,
once
I'm
not
doing
a
million
things,
and
if
anyone
has
any
other
feedback
or
comments
they
want
to
leave
in
and
the
cap
that
be
appreciated.
Really
what
I
want
to
do
is
start
to
move
that
cup
forward.
To
saying
you
know:
what
are
we
gonna?
A
Do
there's
been
a
lot
of
iterations
on
it,
there's
been
a
lot
of
bike
shedding
and
some
positive
bike
shedding
on
it
and
I
think
we're
getting
to
a
spot
now
where
we
need
to
make
a
decision
and
move
forward
and
get
it
merged
and
let's,
let's
start,
let's
start
stop
defining
the
cup
and
actually
implementing
the
cup.
If
that's
the
way
we're
gonna
move
forward.
A
F
F
A
A
Cool
and
real,
quick
we're
not
leaving
Hugo
behind
so
Hugo
is
the
engine
that
generates
our
website
and
Daxi
is
a
theme
for
Hugo,
so
just
for
clarification,
there
will
still
be
using
Hugo
to
generate
and
build.
Our
websites
will
still
be
using
meta
v
for
hosting
our
website.
It's
what
we'll
be
doing
is
stripping
out
that
theme
and
evaluating
the
core
content
to
bring
our
website
up
to
standards
that
are
a
little
bit
more
modern
and
yeah.
B
A
But
I
neither
here
nor
there
I
suppose
for
vacations,
so
you
can
take
a
look
at
the
dock
there.
It
looks
like
Zach,
Jennifer
and
Brad
I'll
have
some
time
off
coming
up
in
December
in
January,
I'm,
not
gonna
sit
there
and
reread
all
the
vacation
schedules
to
you,
but
I.
Think
a
lot
of
folks
are
traveling
during
the
holidays.
So
speak
be
aware
that
our
regular
schedule,
I
think
we've
already
touched
on
that
Jennifer.
A
B
A
Cool
cruising
along
here
so
moving
on
last
week,
I'm
just
getting
carried
over
from
last
week's
meeting
was
talking
about
overlapping
initiatives
in
between
special
interest
groups,
so
mainly
contribute
a
contributor
experience
and
sig
Docs
I
have
also
thrown
in
single
release
in
the
conversations,
but
really
I
haven't
taken
any
action
yet
on
this.
But
the
plan
is
is
to
involve
the
chairs
to
potentially
get
some
sort
of
weekly
monthly.
A
I
guess
is
what
I'm
saying
and
the
people
are
interested
in
different
SIG's
might
not
always
have
the
purview
of
seeing
what
sig
Docs
is
working
on
are
seeing
what
it
contributes
is
working
on,
and
what
really
stemmed
all
of
this
is
Petrovic
is
looking
at
a
markdown
linter
for
their
their
current
repository
and
we're
also
looking
for
a
markdown
linter
and
in
our
repository.
So
really.
This
stems
from.
A
Let's
make
sure
that
we're
not
duplicating
efforts
and
if
we
are
trying
to
solve
the
same
problem,
let's
make
sure
we're
solving
it
together
and
that's
the
longest
short
of
it.
So
no
update
there,
but
there'll
be
more
communication
to
come
and
potentially
some
future
updates
and
moving
on
to
the
blog
sub
project
and
I'll
kick
this
over
to
you.
Caitlin.
E
Thanks
and
so
I
just
wanted
to
give
basically
a
refresher
for
what
the
blog
process
looks
like,
as
I
said,
we
formalized
this
as
a
sub
project
of
sig
Docs
earlier
this
year.
So
with
that
some
things
have
changed
in
the
review
and
approved
process
for
this
content.
I'm
gonna
drop
the
link
in
here
as
well.
The
link
I
dropped
is
kind
of
your
source
of
truth
for
this
whole
process.
E
Basically,
we
have
a
blog
team,
which
is
a
sub
team
of
sig
Docs,
that
reviews
all
incoming
content
for
both
technical
expertise.
We
have
copy
editors
to
make
sure
it
adheres
to
the
style
guide.
All
of
that
within
that
really
only
the
content
that
needs
to
go
through
the
blog
team
is
new
blog
post
just
because
we
own
the
editorial
calendar.
We
have
some
of
that
background
knowledge
as
to
what's
coming
down
the
pipe
and
to
make
sure
that
the
content
adheres
to
these
different
guidelines,
primarily
the
two
big
things
for
content.
E
Is
we
only
accept
original
content
on
the
kubernetes
blog,
so
we
don't
accept
any
cross
post.
You
know
it's
not
an
amplification
channel.
We
want
this
to
be
really
valuable
content
to
the
community,
and
then
everything
has
to
be
open
source
and
vendor
neutral,
so
the
blog
team
will
go
through
and
make
sure
that
it
adheres
to
all
of
that.
Everything
gets
tagged
with
a
blog
label,
so
you'll
know
you're
an
approver,
a
reviewer
you'll
know
if
it
needs
to
get
if
it
should
be
assigned
out
to
us.
E
We
do
have
an
auto
labeling
feature
where
it
should
be
assigning
it
to
us
occasionally.
Sometimes
it
might
get
missed
within
the
process.
So
if
you
see
that
happen,
you
can
assign
it
to
me
directly
or
anyone
else
on
the
blog
team.
We
have
a
github
team
there
as
well
for
any
questions
on
that.
We
have
a
cig.
E
We
have
a
doc
blog
channel
in
slack,
as
well
as
a
mailing
list
for
any
content
that
comes
out
and
then
the
only
other
thing
I
wanted
to
say
was
something
we
added
within
this
new
process
was
like
I
said.
The
only
things
that
really
need
to
go
through
us
is
brand
new
content
or
if,
for
some
reason,
it
was
like
a
really
big
structural
change
to
a
blog
post,
any
other
improver.
A
review
on
the
team
is
empowered
and
welcome
to
review
content
and
approve
anything
like
link
changes.
A
E
E
E
E
E
A
G
G
A
Awesome,
thank
you
very
much
and
thank
you
for
bringing
this
up.
I
do
think
it's
the
valid
a
valid
conversation
to
have
and
looking
at
the
issue
that
was
opened
up,
I
see
here
that
Luba
mirror
mentioned
that
it
was
their
opinion
that
the
best
options
to
include
relevant
locations
that
these
commands
need
to
be
run
as
root
and
then
eliminate
root
from
the
command
line
interface.
So
that
sounds
reasonable
to
me.
D
The
other
I
think
you
have
to
involve
the
cube
ATM
team,
because
I
think
they
have
their
own
into
end
testing,
that
they
do
and
I'd
be
curious
if
it
does
have
sudo
commands
in
it
and
if,
if
it
doesn't,
if
it
does
have
sudo
in
their
intent,
testing
I
think
maybe
they
should
be
involved,
because
the
documentation
should
match
the
actual
testing
that
that
group
does
that's
in
charge
of
qadian.
In
my
opinion,
you.
A
Know
I
would
agree
with
that
for
the
cube
ATM
pieces.
There
are
more
examples
in
the
kubernetes
documentation
where
pseudo
does
come
up
to.
Definitely,
in
this
specific
case,
cube
ATM
makes
sense
fair
enough,
so
ever
know
you're
gonna
say
something.
A
A
A
Sorry
walking
and
talking
here,
I
think
a
style
up
style
guide,
updates
needed
to
have
just
a
stance
on
this
I
don't
know
if
it
has
to
be
necessarily
the
correct
stance
out
of
the
gate.
I,
like
the
opinion
of
if
it
was
just
mentioned
in
the
article
and
then
the
actual
command
examples
itself
doesn't
have.
The
pseudo
declaratively
spelled
out
every
single
time
completely
open
for
debate.
I
don't
want
to
be.
A
You
know,
Jim
says
this,
so
this
is
how
we're
moving
forward
I'm
not
attached
to
that
opinion
by
any
means,
but
just
gut
gut
checking
right
now.
I'm
talking
talking
out
loud.
That
seems
to
make
sense.
Is
there
anybody
on
this
call
that
would
want
to
own
that
action
item
to
to
create
that
style,
guide,
update
or,
at
the
very
least,
open
an
issue
to
update
the
style
guide.
A
A
The
issue
that
vanilla
originally
opened
up
about
the
consistency
issues
so
I
think
pending
ownership
and
pending
moving
forward.
It
sounds
like
there's
not
really
a
strong
feeling,
one
where
the
other
is
just.
We
need
to
get
some
sort
of
opinion
and
this
style
guide.
So
we
need
someone
to
own
that
process.
G
G
G
H
Think
if
you
were
to
do
that
and
we
were
to
encounter
any
strong
opinions
against
us,
we
can
then
have
a
more
meaningful
discussion.
But
my
ghost
instinct
would
be
that
you
won't
get
any
strong
opinions
on
us,
but
if
you
made
a
style
choice-
and
we
would
probably
as
immunity
go
with
your
choice
unless
upon
further
consideration,
we
can
think
of
a
reason
to
not
make
the
choice
that
you
make
so
so
I.
What
I'd
recommend
is
make
a
choice
and
let's
see
what
happens,
you
know
and
I.
H
An
end
user,
but
if,
if
I
was
to
copy
and
paste
commands
from
the
webpage
that
their
number
one
I
must
be
careful,
how
I
do
that
and
number
two:
it's
not
a
problem
to
include
or
exclude
assertive,
and
it's
not
a
big
problem
to
insert
a
suited
if
I
need
to
so
I
think
yeah.
Whatever
choice
you
make
is
probably
an
okay
choice:
okay,.
G
G
B
I
think
I'm,
probably
the
only
like
semi
formally
trained
to
crater
left
on
the
call.
It's
a
really
classic.
Check
Writer
thing
just
pick
one
and
stick
to
it,
which
is
what
everybody
else
has
been
saying
right,
just
pick
it
and
stick
to
it
so
yeah.
If
people
need
to
bike
shed
they'll
bike
shed,
but
more
often
than
not,
they
just
appreciate
having
the
guidance.
G
A
D
A
H
So
so
I
had
a
look
at
this
and
about
two
or
three
months
ago
and
then
I
submitted
to
talk
to
four
for
the
contributor
experience
and
much
to
my
surprise,
it
was
accepted.
So
I
was
I
was
head
down
with
that
on
until
you
can't
San
Diego.
So
I
have
some
time
this
month.
To
put
into
this
and
overall
my
first
pass.
H
I
did
a
bit
of
moaning
about
this
acute
comment.
Somebody
said
to
me:
well,
it's
not
that
hard!
All
you
have
to
do
is
drop
in
the
HTML,
annotated
as
to
how
you
want
it
and
and
dropping
in
an
extra
JavaScript
library
shouldn't
be
a
problem,
and
then
I
realized
that
in
that
casual
conversation,
that
I
realized
that
my
issue
is.
H
Is
that
and
I
effectively
need
to
look
at
the
process
to
generate
the
markdown
and
perhaps
modify
it
to
generate
HTML,
which
which
we
would
then
include,
then
annotate
and
then
jQuery
sort,
jQuery,
filter
so
and
so
I'll.
Take
that
I'll
make
the
time
this
month
and
we'll
probably
be
around
around
the
holidays,
to
get
stuck
into
this
myself,
but
it.
But
if
there
was
anyone
on
the
call
or
anyone
in
in
the
slack
room
that
could
help
me
with
Hugo
and
help
me
with
this.
That
would
be
awesome.
A
Yeah
definitely
I
think
there's
a
few
different
ways.
You
can
slice
up
data
in
Hugo.
There's
are
many
different
approaches.
I
can't
say
one
is
more
correct
than
the
other,
but
as
you
kind
of
trudge
down
this
journey,
if
you
post
any
open
questions
into
the
sig
Doc's
Channel
I'm,
very
active
and
there
so
as
many
other
folks
on
this
call,
I
think
you'll
get
the
help
that
you
need.
Our
hope
that
you
to
help
that
you
need-
and
it's
not
accelerating
yeah.
H
B
A
Less
housekeeping
item
here
is
that
next
week,
even
though
it's
not
the
third
meeting
time
of
the
month,
we're
going
to
do
the
asia-pacific
time,
meeting
I'll
set
up
the
communications
via
the
sigdoc
Channel
after
the
meeting
today.
Just
an
update
so
no
regular
time.
Meeting
next
week
will
be
the
APEC
friendly
time
and
then
the
last
thing
to
that
I
didn't
touch
on
about
the
chair,
shuffling
between
Jennifer
and
Caitlyn.
B
Not
trying
to
I'm
not
trying
to
take
it
away
from
a
public
forum,
but
we
are
coming
to
up
on
the
end
of
the
meeting
and
I'm,
just
thinking
that
maybe
if
Kaitlyn
and
I
just
agree
about
what
our
availability
is,
we
can
then
put
our
conclusions
in
a
public
Channel.
My
brain
is
just
spinning
right
now,
I'm
in
San
Francisco
for
three
solid
days
worth
a
day.
B
Job,
Ness
and
I
just
declined
this
morning,
so
I
could
tend
this
meet
attend
this
meeting
I'm
now
like
really
not
in
kubernetes
land
for
the
rest
of
this
week
and
we'll
be
returning
at
least
briefly
between
now
and
the
end
of
the
year.
So
I
don't
have
an
answer
for
you.
That's
why
I'm
that's
why
I'm
even
sort
of
sloppy
and
fuzzy
here
it's.
H
B
A
A
Here
nothing
I'll
give
us
the
countdown
later.
I
should
say
countdown
for
final
thoughts.
Otherwise
everyone's
gonna
stand
there
and
wait
for
the
countdown
to
finish
and
not
interject
but
anyways.
That's
an
official
sigmax
meeting
appreciate
y'all
joining
me
in
us
today
and
no
talk
to
you
soon.
Thank.