►
From YouTube: Kubernetes Contributor Experience SIG Meeting 20190731
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
C
C
A
A
A
A
A
A
A
A
D
B
E
F
E
G
Super
late
for
you,
Allison
hey
it's
a
bit
early
but
I.
D
J
D
C
A
L
N
M
M
M
Still
on
so
no
one
can.
Can
you
reach
out
to
me
so
I
get.
C
E
Alright,
let's
get
going
here
this
morning,
welcome
everybody
to
the
July
31st
edition
of
contributor
experience.
My
name
is
Elsie
Philips
and
I'll
be
hosting
this
call
today,
as
we
kick
off,
I
would
just
like
to
remind
everybody
that
we
do
have
a
code
of
conduct.
The
TLDR
a
lot
is,
please
be
excellent
to
each
other.
I
I
If
you
want
to
volunteer
that
would
really
help
out
and
now
that
Club
cloud
providers
have
collapsed
in
a
sick
cloud
provider,
there
should
be
bouncing
soon
and
I
need
to
add
sig
usability,
I'm,
just
gonna
go
ahead
and
schedule
the
rest
of
the
year.
I
have
a
to
do
to
do
that
this
week
or
maybe
next
week.
I
have
a
I
have
an
event
that
I'm
going
to
this
week,
so
I'll
be
traveling,
but
I
will
try
to
publish
the
adventists
the
schedule
for
the
rest
of
the
year
as
soon
as
possible.
I
I
I
I
We
said
at
here
like
the
thing
that
blasts
everyone
in
the
channel
says:
hey
we're
going
live
and
then
we
put
like
a
thumbs
up
and
a
thumbs
down
emoji
to
see
what
people
would
say
and
I
I
thought
everyone
was
like
gonna,
flame
us
and
stuff,
but
most
people
generally
love
the
reminder
that
we
were
going
live
and
then
in
our
heads
we
were
thinking
well,
they
are
hanging
out
in
that
channel.
So
we're
gonna
do
that.
I
M
I
M
P
D
I
Q
M
Am
I
next
yep
you're
next
Paris
so
meet
our
contributors?
We,
if
anyone
wants
to
join
us,
still
have
a
lot
of
work
to
do
in
that
area
as
well.
So
if
anybody
wants
to
join
me
in
that,
that
being
scaling
it
out
further,
that
would
be
cool
and
then
just
what
else
that
I
have
on
the
agenda
today
I
think
I'd
steering
committee
election
right
hold
on
I'm.
Looking
at
the
notes.
M
Yeah
contributors
on
that
too
so
steering
committee
election
I
did
file
an
issue
for
that
to
get
them
kicked
off.
We
are
in
the
process
of
talking
to
them
about
election
officials.
All
the
stuff
is
in
the
in
the
issue
there
to
get
that
kicked
off.
If
we're
looking
at
the
same
timeline
that
we
did
last
year,
we're
expecting
announcements
at
some
point
around
August
20th,
but
that's
it
for
steering
committee
election
stuff.
Does
anybody
have
questions
with
that?
I.
M
Q
M
M
Any
other
questions
felt
out
all
right
and
then
the
contributor
summit
they
jumped
ahead
a
little
bit
with
the
Syrian
committee
contributor
summits
going
along
awesome.
I
feel
like,
with
the
exception
of
the
fact
that
we
don't
have
signed
contracts.
Everything
else
is
going
along
super
smooth.
We
have
the
addition
of
tons
of
shadows
so
that
we
can
sustain
this
next
year,
so
that
this
can
be
my
last
one.
As
far
as
leading
but
everything's
going
awesome.
M
We
we
would
love
your
feedback
for
the
content
at
this
point
and
that
can
be
located
in
a
github
issue
as
well
that
I'll
link
to
the
agenda
it
was
a
mega
email
was
also
sent
to
steering
I'll
forward
that
to
contributor
experience
as
well.
That
mega
issue
just
describes
the
content
proposal
and
things
along
those
lines,
but
that's
pretty
much
it
questions
about
contributors
on
that.
P
P
M
J
K
L
J
M
M
The
only
person
that's
in
these
sends
these
emails,
so
I
did
include
the
the
top
notes
there
I've
been
personally
sending
them
to
folks
individual
emails
and
not
the
kubernetes
SIG's
lead
list,
just
because
we
heard
from
several
folks
that
people
don't
keep
their
notifications
on
for
that
list
or
whatever
it
was,
but
that's
just
not
scalable,
and
so
we're
just
gonna
have
to
start
sending
them
to
the
leads
list
and
then
adhering
the
channel.
That's
what
I
was
going
to
do.
I
was
gonna.
Add
here
yesterday.
M
Just
haven't
gotten
there
yet,
but
it
is
what
it
is.
These
people
need
this
information
ASAP
most
of
the
time
it
has
stuff
to
do
with
them
personally,
as
well
as
as
their
groups
so
but
anyway
sent
out
the
one.
The
other
day
had
five
and
I
only
sent
I
usually
only
send
out
when
we
have
at
least
three
topics
to
cut
down
the
noise
of
the
emails,
because
that
was
the
original
problem
was
that
they
were
getting
too
many
emails
from
me,
a
SCADA
etc.
M
So
this
was
just
an
effort
to
consolidate
that
so
that
they
get
everything
in
one
chunk,
so
I
usually
do
for
at
least
three
action
items.
So
if
people
on
the
call
see
three
action
items
that
are
listed
in
there
with
the
correct
context
and
links
and
everything
and
that's
ready
to
go
just
send
it,
that's
the
deal
because
it
has
at
least
three
things.
That
means
like
we
have
at
least
three
things
that
are
hot,
that
are
ready
to
go
and
then
I
would
love
to
scale.
M
This
even
further
I
would
love
this
like
to
get
this
out
of
like
emails
and
somewhere
else.
But
some
of
the
stuff
is
a
little
like
admin,
intensive
I've
thought
about
sending
a
Takei
dev,
but
some
of
it's
like
hardcore
into
like
hey,
fixes,
zoom
control
on
your
admin
panel
kind
of
thing,
so
I'm
also
I'm.
Also
game
for
folks
who
want
to
like
help
scale,
this
effort
into
something
better
and
more
meaningful,
but
it's
really
great,
you
know,
get
some
information.
J
M
Just
trying
to
like,
because
I
felt
like
when
we
were
sending
individual
emails,
people
were
just
like
wow.
This
is
a
lot
of
administrivia,
especially
the
Zune
stuff,
because
at
one
point
I
felt
like
I,
was
sending
an
email
almost
every
week.
That
was
like
change
this
do
this
and
it
just
got
to
be
a
point
where
okay,
well,
let's
consolidate
and
act,
it
act
more
like
a
newsletter
of
action
items
and
dance.
J
M
I'm
selfish,
like
I,
mean
who
looks
like
I'm,
something
like
this
from
a
chair
role
to
like
I
want
checklist.
Yeah
like
in
this
whole
like
there's,
nothing
better
than
a
checklist,
so
I
feel
like
any
time
we're
doing
documentation
if
we
can
do
a
checklist
style
for
sake
operations.
That
is
like
the
best
where
people
can
just
go
break
down
and
say:
did
that
did
that
did
that
but
yeah?
No,
please
please
help
with
this.
M
Please
add
the
please
add
content
again
if
it's,
if
it's
stuff
that
like
we
need
to
go
to
individual
SIG's
for
then
go
to
individual
things
for
it.
But
if
it's
stuff,
where
we
need,
you
know
to
talk
to
you,
a
hundred
plus
chairs
and
tech
leads
and
get
them
to
disseminate
information.
Then
that's
kind
of
what
this
is
for.
M
E
F
So
what's
happening
with
APEC
coordinator,
so
I
actually
came
in
last
meeting.
I
was
super
excited
to
actually
be
here
and
say:
yeah,
you
know
we're
having
them
meeting
today.
It's
gonna
be
I'm
bad
at
time
zones,
but
it's
usually
about
6
p.m.
my
time.
So
there's
that
update
so
far
we're
just
currently
working
well.
Currently,
a
lot
of
ideas,
discussion
but
I
haven't
failed.
Us
think
up
that
much
Nikita
might
have
a
better
idea
as
well,
so
I'm
gonna
just
pass
the
invisible
mic
trust
so.
M
I've
got
a
tip
for
you,
contact
CNCs
and
see
if
they
have
any
different
communication
channels
for
a
PAC
user
and
users
and
stuff
like
that
like
how
they
get
ahold
of
people
for
Deepak,
coupons
and
stuff
like
that,
because
then
you
could
just
think
you
could
send
the
webinar
like
webinar
stuff
out
to
that
crew
and
that's
how
you
could
we
can
get
people.
You
know
obviously
more
interested
from
that
from
that
area.
M
Q
Q
So
I
need
to
figure
out
an
exact
time
and
then
set
our
first
meeting
a
whole
bunch
of
like
things
ongoing,
including
like
the
the
the
two
kind
of
key
ones
that
are
at
least
top
of
my
mind.
Right
now,
we're
we're
gonna
be
moving
to
rename
fada
bot,
something
that
we've
got
repeated
feedback
on,
because
people
don't
know
who
Eric
fada
is
which
I
feel
like
is
an
education
thing
like
they
need
to
know
who
Eric
fada
is,
but
at
least
four
new
contributors.
Q
So
that's
one
thing:
the
other
thing
is
we
have
some
actual
like
lines
of
communication
with
github
the
company
now
like,
and
and
really
like,
good,
clear
lines
of
communication.
A
couple
of
us
met
with
Brian
who's,
our
director
of
open-source
product
and
stuff
yesterday,
and
they
have
both
to
kind
of
accept
some
feedback
from
the
issue
that
we
had.
Q
This
was
a
couple
months
back
now,
where
all
of
a
sudden
people
could
assign
issues
and
peers
to
basically
anybody
and
I
kind
of
caught
us
by
surprise,
because
kind
of
some
of
our
permissions
model
was
around.
Who
is
allowed
to
be
assigned
things,
so
we
were
able
to
like
provide
some
valuable
feedback
to
them
as
well
as.
Q
P
K
I
think
I
do
think
is
weird
that
people
are
complaining
that
the
name
for
feet
about
is
confusing.
It
is
certainly
unique
and
I
think
if
you're
gonna
name
a
thing,
you
should
name
a
thing,
and
that
said,
I
actually
think
the
fact
that
it's
named
after
a
person
in
the
community
can
come
across
a
super
cliquish
and
not
very
well
coming
as
in,
like
you
have
to
be
the
special
person.
If
you
want
to
have
a
thing
name,
I.
K
Q
Was
the
the
the
thing
that
convinced
me
to
like?
Let
go
of
the
name
feita
box
I
was
very
like
it's
like
a
unique
thing,
and
it's
like
part
of
the
community
and
stuff
is
it's
an
inside
joke
and
inside
jokes
are
funny
if
you're
in
the
joke
and
very
confusing,
if
you're
not
and
something
that
is
especially
doing
a
thing
like
stale
closing
things.
So
we
have
people
who
are
not
even
involved
in
the
project.
Q
Go
and
open
up
an
issue
have
no
desire
to
even
become
a
contributor,
but
are
like
reporting
a
bug
and
if
eventually,
this
random
robot
with
somebody's
face
comes
along
and
closes
it
and
they
don't
understand
why?
If
it
or
is
like
reporting
that
it's
just
it's
stale,
that
that
kind
of
workflow.
That
was
the
argument.
That
kind
of
convinced
me
like
okay,
we
should
probably
like
let
go
of
the
name
and
change
it,
even
though
it
was
a
funny
inside
joke
for
a
while.
M
Yeah
I
mean
we.
There
is
incident
management,
training
for
moderators,
that's
being
coordinated
for
Sage
sharp
I
didn't
necessarily
have
that
update,
so
wasn't
necessarily
mine
to
give,
but
we
have
almost
all
of
the
moderators
accounted
for
in
either
one
of
one
or
two
sessions
still
waiting
on
others.
This
also
brings
up
a
curious
discussion.
Point
of
should
we
make
this
required
for
moderators.
O
M
This
is
an
incident
management
training
class.
So
for
folks
that
don't
that
did
not
know
this
was
happening.
The
code
of
conduct
committee
took
a
course
from
Sage
sharp
recently
on
general
incident
management
as
it
relates
to
code
of
conduct
and
stuff,
like
that,
there
was
actually
a
piece
inside
of
the
training
that
really
had
to
do
with
online
moderation,
which
got
me
thinking
hey.
We
have
folks
that
are
moderating
that
I've
never
moderated
before.
M
Courses
like
that
in
the
past
and
I
did
not
know
how
well
it
would
do
from
those,
but
it
was
actually
really
fun
that
she
uses
zoom
and,
like
you
go
into
these
individual
zoom
rooms
with
other
people
and
like
act
out
scenarios
and
so
it'll,
be
something
similar
but
very
tailored
to
online
moderation
and
not
like
events
and
stuff
like
that,
but
yeah
that
happens,
August,
26th,
I,
believe
and
hopefully
the
second
course
will
be
scheduled
for
sometime
and
tambour.
So
we
do
have
seats
available
and
that's
something
else.
M
I'm
trying
to
think
about
I
was
gonna.
Tell
the
steering
committee
that
we
have
I
think
four
seats
available
for
the
August
26
class.
So
I
don't
know
if
we
should
invite
other
folks
from
the
community
or
if
we
should
invite.
Maybe
some
other
CN
CF
projects
and
CF
is
funding
this.
So
I
was
gonna
talk
to
some
folks
there,
but
it's.
J
J
P
M
C
Thing
before
you
actually
make
it
like
a
requirement
for
moderators
is
that
we
have
the
monitors
pro
tempore,
a
temporary,
where
their
entire
deal
is
rotating
them
out.
So
these
coordinating
training
for
people.
If
we
with
the
intention
of
rotating
the
amount
like
every
six
months,
which
was
the
original
idea
might
be
well,
could.
M
C
M
We
put
the
onus
on
the
regular
moderators
to
do
some
kind
of
onboarding
session
with
the
proton
pure
of
folks.
That's,
like
you
know,
45
minutes
long
where
you
like,
maybe
just
go
through
a
quick
scenario
of
like
hey.
This
is
my
what
you
might
see
on
flack,
specifically
that
I
think
we
could
definitely
do
yeah
yeah.
I
I
M
M
Alright,
for
this
one,
we
definitely
need
to
think
about
what
we
want
to
do
for
a
meeting.
This
is
the
one
I
feel
like
the
one
sub
project
that
does
get
a
little
bit
neglected
from
us.
That's
probably
one
of
our
most
important
sub
projects
and
I
think
we
need
to
meet
so
I
think
we
need
at
least
a
monthly
cadence.
30
minutes
like
we
can
always
extend
if
we
need
more
I.
Think
starting
monthly
30
minutes
is
responsible.
M
I'm
gonna
send
out
I
think
only
two
people
responded
to
the
doodle
though,
and
we
have
like
12
maintainer,
z'
I,
don't
know
if
that
means
the
maintainer
z'
aren't
interested
in
meeting
or
if
the
maintainer
don't
care
or
what
exactly
that
means
and
I
definitely
use
the
word
maintainer
instead
of
owner,
so
other
folks
that
are
owners
on
the
line
for
the
contributor
guide,
the
non-code
guide
and
then
develop
the
devel
guide.
Let
us
meet
yeah.
M
Can
you
resend
the
doodle,
because
I
don't
remember
seeing
that?
But
doodle
is
on
these
the
meeting
notes:
oh
okay,
Oh
every
sub
project
doodle,
if
you're
still
like
community
management,
contributor
documentation
or
the
two
that
still
have
outstanding,
doodles
and
I
have
not
set
up
those
yet
just
because
of
the
low
response
rate
for
both.
I
I
Q
C
I
Hold
on,
let
me
let
me
just
give
her
birdy
the
URL
in
chat
here.
It's
just
kubernetes
contributor
nullified
comm
toss
up
here.
I
The
guide
events
which
we
need
to
update
the
calendar
and
then
a
link
to
the
code
of
combat
canal
into
the
job
board,
the
role
board,
not
jobs
and
we're
gonna,
get
a
new
pick,
a
new
home
page
before
we
launch
yeah.
So
that's
something.
I
would
like
to
get
feedback
on
this,
so
I,
initially
just
slapped
like
Gwen's
workshops
there,
but
we
could
probably
do
with
having
rewriting
a
new
paragraph
in
the
front.
I
N
M
On
I
feel,
like
introduction
is
like
an
introduction
to
the
community,
not
necessarily
a
workshop
sure
like
I,
mean
I
feel
like
workshops
and
education
should
be
its
own
tab.
This
is
where
I
was
hoping.
We
would
have
like
a
professional
help
us
with
information
architecture.
Okay,
well,
I,
just
kind
of
put
it
up
there
as
an.
M
J
I,
like
the
idea
of
one
of
the
things
I
hear
parents
asking
for,
is
like
hey:
can
we
have
a
conversation
about
content
and
have
it
like
curated,
yes,
towards
a
goal?
If
we're
meeting
on
a
monthly
cadence,
that's
one
of
the
things
that
could
be
a
standing
part
of
the
agenda.
What's
the
page
look
like
today,
how
do
we
freshen
it?
That
would
be
really
useful.
I
feel.
M
Like
all
the
research
that
we
did
and
the
content
strategy
is
like
telling
us
one
thing-
and
this
is
producing
another,
so
that's
why
it's
like
we're
getting
or
hearing
one
thing
from
contributors
as
to
what
they
want
to
see
and
what
they
want
to
surface.
And
we
have
data
that
says
what
they
want
to
surface,
but
I'm,
not
sure
we're
still
surfacing
it,
and
it's
like
I
feel
like
we're
just
giving
people
what
we
want
to
give
them.
Well.
I
M
M
Q
What
what
I'm,
but
so
like,
actually
looking
like
it's
spending
the
last
minute
clicking
through
this
site.
What
I
see
is
a
home
page.
That
is
basically
it
do.
We
need
some
content
for
the
home
page
and
everybody
can
like
agree
on
that.
We
have
the
contributor
guide,
we
have
an
event
site,
we
have
a
calendar,
we
have
a
link
to
our
code
of
conduct
and
we
have
the
roll
board.
Nothing.
There
seems
to
me
to
be
objectionable
or
necessarily
like
incomplete
I
can
see
polish
on
all
those
things.
Q
I
I
know
we
had
talked
about
doing
a
development
blog
on
the
home
page,
but
that
feels
like
kind
of
that
opens
a
whole
new
set
of
things
that
we
have
to
think
about,
so
I
would
prefer
to
like
yeah.
If
it's
like
welcome
to
the
community.
We
you
know
here
are
programs,
here's
how
you
get
started
and
then
just
like
start
from
that
and
that's
fine.
M
Feel
like
the
homepage
should
be
the
landing
page
and
not
necessarily
like
attacking
you
with
content
just
yet
I
guess.
That's
why
I
feel
like
that's
what
the
you
know.
The
further
links
are
like
contributor
and
events
and
calendar,
and
then
we
should
have
one
on
there.
That
says
like
new
contributors
and
then
that's
where
wins
like
when
should
be
like
first,
you
know
in
in
the
front
folder
since.
I
I'm
gonna
hit
the
road.
Then
why
don't
I
set
this
for
a
list
for
another
round
of
them?
Basically
said
say
everyone
look
at
the
homepage,
that's
like
the
problem
area
or
whatever,
because
then
I
have
to
be
gone
for
a
week
and
then,
when
I
get
back,
I
can
reassess
before
filing
the
issue
and
all
that
stuff
ya.
Q
Know
that's
what's
great,
it
does
not.
From
my
perspective,
it's
definitely
not
ready
to
click.
Go
live
mainly
because
of
the
homepage,
but
if
we
polish
up
the
homepage
and
there
I
can
see
a
few
other
things
that
just
need
polishing
like
if,
when
you
click
events,
it's
a
blank
page
and
then
you
click
into
these
specific
things
under
events,
there's
like
little
things
like
that
that
we
can
create
issues
for
and
get
polished
up,
but
I
don't
feel
like
we're
far
off
from
launching
this.
I
I
Q
K
Yeah
no
I
think
it
is
also
missing
the
developer
guide
we
want.
We
want
to
show
this
is.
M
Why
we
need
a
like
of
features
list
of
what
we
plan
to
launch?
First,
what
we
want
to
launch
second,
because
I
feel
like
we're
once
we
launch
this
site.
This
is
all
we're.
Gonna
get
all
we're
gonna
get
it's
Gwynn's
and
Paris's
going
with.
Where
is
this?
What
about
this?
What's
going
on
with
this,
so
I
feel
like
if
we
can
have
a
road
map
of
like
what
we
plan
to
do
and
that's
kind
of
where
I
was
going
with
like
logging.
Q
J
P
No
you're
fine,
like
launching
websites
like
George
I,
appreciate
getting
something
out
there
like
it's
awesome.
That
work
is
great.
Paris
I
appreciate
you
wanting
to
have
like
some
great
math
and
the
two
can.
The
two
can
work
in
tandem
is
all
I'm
saying
we
just
need
to
actually
sit
down
and
figure
it
out.
J
Thing
briefly
on
it:
within
the
contributor
documentation,
space
may
be
more
contributive
Ella
/
guide,
but
it
may
be
also
non
code,
so
I've
been
doing
cube,
con
reviews
and
obviously
keeping
confidentiality
in
mind.
I'm
waiting
to
see
what
gets
announced
eventually
in
the
program
in
the
coming
weeks.
J
J
J
The
decisions
have
been
made,
yep,
so
I
checked
with
Bryan
Liles,
specifically
on
that,
because
I
wasn't
sure-
and
he
said
yes,
that's
cool
I
like
that.
There's
there's
the
confidentiality
aspect,
but
also
this
is
supposed
to
be
community
and
positive
and
forward
moving,
and
if
it's
not
there,
reach
out
to
them
and
yeah.
That's
that's
a
good
thing
for
us
to
do
so,
and
he
fun
stuff
that.
E
I
think
that
sounds
wonderful.
What
would
you
propose
for
next
steps
on
that
so
probably
waiting
until
we
know
what
makes
it
in
and
what
doesn't
and
then
maybe
making
like
a
wish
list
of
probably
prioritizing,
as
you
said,
the
ones
that
didn't
make
it
in
first
and
then
would
the
contributor
documentation
group
then
reach
out
to
those
individuals
and
be
like
hey?
We
heard
you
submitted
this
really
cool
thing.
Come
join
us
in
our
sub
project.
You
know
to
contribute
your
knowledge
to
that,
so
it
can
be
immortalized
and
live
on
forever.
Yeah.
J
I've
kind
of
got
my
list
of
ones
from
the
review
that
I
did
and
I'll
keep
that
in
my
pocket
and
over
the
next
month
or
something
is
that
happens,
I'll
see
you
what
I
can
do
and
I'll
bring
it
up,
then
in
the
contributor
documentation
meeting,
but
I
also
wonder
if
I
can
for
the
things
that
I
wasn't
reviewing,
because
I've
only
got
a
chunk,
there's
probably
a
whole
bunch
of
other,
potentially
a
bunch
of
others
in
the
community
tract,
and
maybe
we
can
afterwards
get
the
official
list.
J
J
J
E
F
Q
Said
this
in
the
channel
yesterday,
but
for
anybody
you
might
have
missed
it.
It's
hotels
like
the
hotel
blocks
are
open
and
they
usually
sell
out
very
early,
and
most
of
them
have
very
friendly
cancellation
policies
like
72
hours
beforehand.
So
if
you're
considering
going,
might
be
good
to
book
a
hotel
that.
E
E
R
R
Do
we
need
to
remove
the
expired
placeholder
files,
so
we
had
a
few
PRS
open
in
kubernetes
community
and
some
audibles,
where
we
were.
Someone
removes
the
expert,
placeholders
files
and
I'm,
not
sure
that
we
should
continue
following
this
practice.
The
reason
why
the
placeholders
are
important
because
they
could
be
like
dumped
in
the
stone
somewhere,
especially
the
summerses
work,
don't
have
any
editable
access
to
examine
a
stroke
of
files
like
printed.
R
Q
Q
Q
Q
You
know
I
can
sympathize
with,
in
particular
the
use
case
where
we
don't
like
printed
printed
material
in
particular,
or
you
can't
go
back
and
rewrite
a
book.
I
would
hope
that
if
people
are
doing
that
they're
using
one
of
the
short
links,
because
those
we
do
have
control
over
things
like
go
to
Kate
CO
or
one
of
the
other,
like
short
link
generators
that
we
we
use
to
map
one
thing
to
another,
because
we
can
rewrite
those
and
for
things
that
have
moved
around
multiple
times,
we've
got.
Q
We've
gone
like
oh,
go,
create
a
short
link
so
that
we
can
have
a
at
least
a
consistent
redirect
to
not
have
to
go
to
update
documentation.
We've
done
things
like
for
API
conventions
and
owners
file,
documentation
like
there's
a
couple
of
key
things
that
we've
done,
that
for
I,
don't
know
I
I'm
kind
of
torn
again
I
understand
the
reason
why
we
would
leave
things
around,
but
I
also
don't
know
that
that's
sustainable
to
just
leave
to
stones
around,
because
it
makes
trying
to
find
the
actual
thing
that
you're
looking
for
very
confusing.
Q
If
you
have
like
ten
different,
you
know:
communication,
dot,
MD
or
whatever
files
scattered
throughout
the
repo,
as
in
particular
when
we
do
big
reorganizations
such
as
migrating
caps.
That
was
a
big
one
or
the
contributor
guide,
like
those
those
are
the
two
like
super
big
ones
that
we
had
like.
Oh,
we
have
50
tombstones
for
different
things.
I
just
don't
know
it's
sustainable
to
do
that
for
everything.
I.
M
R
If
we,
if
we
have
their
access
to
that
link,
so
I
am
absolutely
against
of
heaven.
You
know
like
having
the
big
mess
of
the
old
files.
I
agree
that
it's
really
not
comfortable
to
to
have
tons
of
different
files,
most
of
most
of
which
are
like
you
know,
not
not
really
useful,
because
they
just
are
down
stands.
But,
for
example,
if
I
will
find
some
historical
blog
posts
from
2016
and
I
will
click
the
Sun
or
click
on
some
link.
That
will
point
into
some
outdated
link
of
receive
four
four
zero.
R
Four
arrow
there,
the
key
topic
for
the
or
four,
but
hopefully,
if
will
keep
the
touchstone
I,
will
see
the
link
to
the
new
file
and
I
will
forward
to
that
file,
because
that
that's
unfortunate
that
github
doesn't
support
3d
direction
this
way,
but
Tom
stones
can
be
the
good
solution
for
what
is
the
manual
or
indirect
I
also
agreed
that
we
should
not
do
this
basically
for
everything,
but
for
something
big
like
again
like
the
contributor
guide
or
something
like
that,
it
could
be
useful.
I.
M
Feel
like
I
just
did
a
PR
the
other
day
for
cleaning
up
the
communication
folder
and
trying
to
like
reorganize
that
a
little
bit,
and
it
was
like
the
amount
of
tombstones
I
was
enough
to
put
in
there
and
like
the
mess
of
tombstones
that
are
already
in
there.
I
feel
like
the
YouTube
one
has
like
45
redirects
and
like
it
was
I
was
just
like
I
just
deleted.
The
PR
I
was
like
forget
it
like
I,.
M
Now
I
mean
and
I
was
like
the
second
part
of
my
PR,
but
it
was
like.
The
first
part
was
like
I
just
wanted
to
see
what
it
was.
Gonna
look
like
and
then
the
second
part
was
like
me,
adding
the
tombstones
and
and
that's
what
I
was
like.
This
is
really
messy.
All
like
that's
I
was
like
I'm,
just
gonna
go
ahead
and
hit
the
delete
button,
hit
the
delete
button
right
now
and
pretend
like
we
just
did
go
down
laughs.
C
Q
I'm,
what
I
would
I
guess,
maybe
I
what
I
would
suggest
as
a
compromise.
Is
it
at
least
maintaining
our
current
tombstone
policy,
which
is
like
three
roughly
three
months
or
release
and
then
cleaning
them
up?
But
if
there's
like
specific
files,
specific
use
cases
like
things,
things
that
would
be
longer
lived
or
things
that
we
feel
are
really
important
to
find
and
we've
identified
perhaps
keeping
a
tombstone
around
for
longer
or
indefinitely
on
a
case-by-case
basis.
If
we
identify
specific
things,
I
don't
know
I'm,
just
trying
I'm
trying
to
think
like
this.
Q
I
could
see
us
if
we
move
like
the
API
conventions
stock,
if
or
when
we
move
that
dock,
because
that
dock
is
linked
in
a
bazillion
different
places.
That
one
may
be
a
particular
use
case
where
we're
like.
Okay,
we
want
to
keep
a
tombstone
around
for
this
file
longer
or
indefinitely,
because
it's
it's
gonna
be
in
so
many
different
places.
Q
Q
R
R
E
M
J
C
I
M
E
I
Don't
worry
so
I
sat
in
on
sig
usability,
that's
happening.
They
seem
to
be
all
set
as
far
as
your
YouTube
and
all
their
community
resources.
I
just
wanted
to
mention
that
there's
an
e-cig
and
was
the
other
thing.
I
wrote
sorry
I
just
closed
the
tab.
Accidentally,
oh
we're
due
for
a
status
next
week
in
the
community
meeting.
So
just
a
heads
up,
Oh.
M
Admins
and
mugs
on
the
usability
stuff
just
a
flag
to
help
out
and
then
also
the
cloud
provider,
stuff
they're,
turning
they're
turning
multiple
SIG's
down
and
they
have
a
checklist
going.
So,
if
you're
a
mod
on
any
of
our
platforms,
reporting
for
duty
and
then
also
the
release
team
wants
their
stuff,
automated
I've
done
all
of
them
and
would
love
another
YouTube
admin
to
fake
it
help
figure
it
out,
love
you
forever!
Thank
you.