►
From YouTube: Kubernetes SIG Contributor Experience 20170809
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
B
C
B
Yeah
exactly
that
one,
so
that's
linked
in
the
meeting
notes
and
that
that
doc
has,
if
you
scroll
down,
it's
got,
questions
we'd
like
to
get
answered
and
some
of
the
metrics
that
might
be
helpful.
So
it's
kind
of
a
brainstorm
but
I
think
we
should
start
from
questions
rather
than
from
metrics,
because
sometimes
we
may
end
up
with
the
wrong
metric
and
so
on.
Who's
working
on
this
a
while
ago,
kind
of
shed
some
light
on
how
this
can
be
tricky.
B
If
we
look
at
like
average
time
to
lg
TM,
for
example
like
picking
that
metric
out,
it
seems
useful
initially,
but
there's
some
some
areas
where
it
can
be
tricky,
so
instead
I
kind
of
rephrase
it
like
what
are
we
actually
trying
to
get
answered
and
so
I
have
a
list
of
questions
there.
So
if
you
just
want
to
take
a
look
and
contribute
that'd
be
great,
we
also
have
these
are
a
little
bit
stale
I
think
relevant.
Metrics
is
from
when
we
did
the
brainstorm
about
a
year
ago,
one
but
some
things
down
there.
B
B
If
you
want
to
take
a
look
at
velodrome
decades
that
IO
you
can
see,
there
are
multiple
repos
listed
now
it's
here.
The
link
to
the
chat
and
I'm
also
trying
to
eye
open
an
issue
in
testan
for
I,
wasn't
sure
might
have
been
in
community
I'm,
not
sure
which
is
the
best
places,
but
I
noticed
them.
The
number
of
people
are
emailing.
The
membership
list
with
you
know
I
think
I've
done
enough.
But
how
do
I
know
if
I've
done
enough?
B
The
question
is
just:
how
can
we
show
it
effectively
and
efficiently
so
I'm
working
on
that
as
well?
I,
don't
know
if
I've
shared
that
dashboard
yet
because
I
think
the
only
thing
that
I
have
is
like
a
number
of
issues
that
you've
commented
under
total
number
of
comments
and
I
haven't
been
able
to
break
it
out
by
order
number
yet
but
I'm
working
on
that
right
now,.
A
Great,
thank
you
yet
and
then
I
think.
B
A
D
Lucas,
the
guy
that
the
original
author
of
the
code
that
was
going
to
make
this
change
sort
of
got
side
banded
by
some
other
things
board
C&C
at
his
employer
came
back
and
said:
hey,
okay,
I
can
push
this
forward.
I
think
pretty
much.
Everything
is
ready
to
go.
I
believe
where
we're
at
is
that
we
need
to
actually
come
out
with
a
come
up
with
a
rollout
plan
and
then
execute
on
it,
and
we
need
the
code
PR
to
finally
get
marks
and
I.
We
were
waiting
on
Joe
Sydney's
final
approval
for
that.
B
D
47
and
that
Mott
I
just
want
to
see
how
to
make
sure
we
we
don't
have
to
undo
a
change
against
47
repos.
So
my
open
question
is
I,
don't
know
who
has
the
credentials
or
privileges
to
be
able
to
actually
execute
on
rolling?
This
out,
you
know
requires
somebody's
got
credentials
to
I'm,
assuming
it's
somebody
who
can
access
to
an
OAuth
key
that
can
actually
write
labels
against
all
the
repos
and
it's
somebody
who
can
deploy
to
probably
the
same
cluster
that
munch
github
is
running
on.
B
D
All
right,
if
you
don't
get
to
I'll,
try
and
get
them
and
we'll
see
where
we
go
from
there
but
yeah
it's
my
concern
is
I
like
I
think
we
just
thinks
he's
done
the
coding
and
now
falls
in
our
court
to
find
an
owner
to
actually
push
the
rollout
forward.
Make
sure
things
look
good,
continue,
rolling
it
out
to
the
rest
of
the
repos.
Hey
we
get
to
brag
about
how
awesome
this
is
so
on
and
so
forth.
B
D
B
D
D
D
B
D
It
must
have
been
the
release
me
release
a
graph
where
we
click
that
action
item
where
we
got
to
figure
out
if
somebody's
actually
going
to
like
Don,
laid
out
a
really
cool
plan
for
it
everybody
said
yes,
so
the
question
is:
if
there's
anybody
who's
actually
staffing
that
effort
to
improve
the
release.
Those
generation
based
on
these
issues
looks
because,
if
not,
it
doesn't
seem
like
it's
being
incredibly
helpful
as
a
requirement.
D
B
You
put
that
in
the
in
the
description
actually,
and
so
I
did
kind
of
a
blanket.
It's
not
I.
Just
figured
I
do
like
a
random
sample.
They
looked
at
PRS
and
I
filtered
out
the
ones
that
were
extra
small
because
those
are
most
likely
to
be
trivial
and
a
large
number
of
those
had
approved
no
issue,
but
as
the
PRS
got
a
little
bit
larger,
a
lot
of
them
were
referencing
issues.
B
I
can't
give
you
an
exact
percentage,
but
I
don't
think
people
were
misusing
it
and
just
you
know,
for
PRS
that
needed
release,
notes
or
that
needed
have
referred
issues.
I'm,
not
sure
that
I
saw
that.
So
take
a
look,
and,
let
me
know
people
actually
are.
We
should
probably
have
some
data
on
that
to
see
if
it's
really
being
yeah.
D
He
got
queries
or
something
needs
for
that.
That
would
be
cool
because
I
mean
it
does
seem
like
the
right
compromises
that
should
be
required
at
a
certain
threshold,
and
maybe
that
threshold
was
PR
side
or
something
of
that
that
nature
anyway,
so
work
in
progress
on
documenting
that
just
they're.
The
owners
thing
I
did
finally
make
progress
on
documenting
clutters
files
and
how
they
are
used
today.
D
I
could
sort
of
comment
on
there,
but
we're
on
focusing
most
of
my
efforts
now
is:
how
do
we
actually
prune
owner's
files,
make
sure
they're
populated
with
interested
individuals
and
enough
of
them
to
actually
make
sure
that
the
owners
process
is
working
as
intended?
This
kind
of
ties
into
the
contributor
ladder
climbing
so
I
have
documented
how
the
process
works
now
I
as
a
human
and
I'm
trying
to
figure
out
what
questions
I'm,
asking
myself
as
I,
add
and
remove
people
and
I
will
use
that
pull
request
into
the
doc
to
that.
D
As
far
as
grooming,
contributing
that
envy
and
all
that
stuff
I
want
to
cleanse.
Oh
wait.
That's
George
anyway,
George.
F
A
F
What's
happening,
okay,
where,
where
are
we
hold
on
I'm
scrolling
halfway?
We're.
F
Thank
you,
sorry
about
that.
So
I've
got
the
first
poll
for
support
that
MD
is
in
there
and
it's
being
peered.
It's
gone
through
a
few
reviews
so
now
I'm,
just
kind
of
waiting
for
the
Auto
merge
thing
to
merge
that
and
then
I
plan
to
go
back
and
and
start
doing
the
deep
linking
bits.
G
Progress
alive
right,
yes,
I
and
I
think
you
know
honor
and
avoided
a
link
of
what's
out
there
right
now
in
the
last
time,
as
you
can
see,
knees,
comment
and
I
think
that
looks
that
that
I
ever
actually
wasn't
out
of
the
link
when
I
thought
of
this
comment
that
actually
answers
a
lot
of
my
questions
there.
You
know
the
comment.
G
It
I
think
it's
clearly
mentioning
all
the
different
roles
rights
you
know
of
just
new
pontiff
eaters,
part
member
in
a
reviewer,
assignee
and
owner,
so
Aaron
I
mean
I'm,
not
sure
what
do
you
think
I
think
it
looks
that
that
community
membership
that
MD
file
I
think
that
that's
a
good
coverage
of
all
those
things
yeah.
D
I
agree,
I
think
that's
sort
of
like
post
the
link
there
is
it
to
do
in
that
doc
or
a
note
that
says
that
it's
not
final,
yeah
and
I
mean
for
the,
for
the
purposes
is:
what's
the
latter?
Look
like
I
think
this
document
satisfies
bad
intent.
I
will
still
be
paying
some
attention
to
this
document
and
poking
I
think
filled
with
aquas
the
original
author
of
this
over
the
next
little
while
as
I
look
to
figure
out
if
I
want
to
have
people
to
the
reviewers
a
list.
D
G
And
that's
what
I
thought
actually,
on
top
of
the
doc,
it
says
it's
in
progress,
so
I
was
wondering
myself
too,
and
you
know
just
to
keep
on
like
that.
If
somebody's
already,
actually
you
know
tracking
gates
and
adding
it
because
it's
akin
to
doc
in
progress,
so
yeah.
D
My
my
I
feel
like
the
intent
for
that
was
to
describe
that.
It
is
a
living
document,
not
necessarily
a
hard-line
set
in
stone,
as
we
figure
out
whether
or
not
some
of
the
wrong
numbers
used
for
metrics
on
like
amount
of
time
participating
amounts
of
pull
requests.
What
exactly
substances
means
are
things
that
will
need
to
be
iterated
upon
too
so
I
don't
know.
A
A
F
I'm
going
to
go
on
an
order
first,
because
once
it's
dependent
on
the
other
I
I
announce
the
office
hours
for
the
users,
that's
going
to
be
in
two
weeks,
so
I
posted
all
the
information
there
on
the
user,
mailing
list
and
I've
been
collecting
new
volunteers
and
stuff.
One
thing
I
want
to
say
it
was
really
really
happy
and
impressed
by
the
senior
people
who
signed
up
to
help
users
so
like
funding
burns.
F
Tim,
Hawking
Clayton,
like
all
these,
like
high
high
level
folks
like
took
the
time
to
write
themselves
down
to
volunteer
to
help
like
new
users
and
I,
think
that's
really
awesome
and
something
we
should
like
always
strive
to
like
help.
Somebody
out
as
a
result
of
collecting
that
I'm
able
to
have
a
better
idea
of
ejected
sub-objective
a
there,
which
is
kind
of
doing
a
user
support
rotation.
That's
just
basically
a
rotating
version
of
that,
except
done
on
slack,
so
I've
been
hanging
out
in
in
kubernetes
users
and
novice
now
and
I'm.
F
Finding
a
lot
of
people
who
might
not
be
like
core
contributors
like
writing
core
go
code,
but
they
do
data
DevOps
at
work
and
they
maintain
the
kubernetes
cluster,
so
I'm
going
to
target
that
audience
is
kind
of
like
an
untapped
level
of
expertise.
That
I
think
we
should
definitely
tap
into
no
progress
on
socializing,
slash,
commands
and
haven't
even
started
on
Stack
Exchange
out.
Yet
so,
okay.
A
E
E
Massively
Ximena
tracing
yeah-
this
is
this
is
something
it
just
keeps
coming
up
over
and
over
again
and
I
kind
of
put
this
in
at
the
end
of
the
agenda
to
just
to
talk
about
this,
but
we
we
actually
haven't
done
any
specific
work
on
this
and
I.
Think
that
that's
unfortunate,
because
this
is
probably
one
of
the
things
that's
like
slipped
while
I
was
sick.
I
will
take
a
look
at
this
and
connect
with
Jago
and
find
out
what
is
happening
here
because
right
now,
I'm
not
really
sure
so.
D
B
You
can
encourage
sick,
though,
to
start
thinking
about
the
up.
Moving
issues
in
the
milestone.
Eight
I
mean
JC,
probably
start
thinking
about
how
you
want
to
get
signal.
I
know
we're
far
from
the
release
date,
but
one
of
the
things
that's
been
a
challenge
for
every
release.
You
can
talk
to
Dan
or
Caleb
or
Phil,
or
whoever
is
figuring
out
the
go
no-go
signal
and
a
lot
of
the
times.
I
think
people
have
used
every
issue
in
the
milestone
and
the
it's
nice
when
SIG's
have
formally
accepted
that.
B
That
is
an
issue
and
it's
something
that
they're
working
on.
So
you
might
want
to
consider
socializing
that
a
little
bit
and
making
that
well
known
that
that's
going
to
be
the
policy
and
you
want
them
to
apply
the
fruit
for
milestone
and
maybe
further
thing
about
the
automation
that
that's
going
to
be
necessary
for
that.
If
that's.
D
The
stuff
that
Marty
is
working
on
where
it's
going
to
kick
stuff
out
if
it
doesn't
have
the
appropriate
set
of
labels
and
it's
going
to
post
a
comment
that
describes
why
it's
been
kicked
out
and
what
labels
they
can
fly.
They
would
like
get
it
back
in
I
believe
but
I
greet.
We
have
some
socializing
to
do
who's
doing
that.
Maru.
E
B
E
A
Okay,
moving
on
George
getting.
F
Yeah
so
Tim
brought
this
up.
Tim
st.
Claire
brought
this
up
to
me
and
with
github
landing,
a
bunch
of
features.
I
know,
I,
haven't
heard
us
talk
about
teams
recently,
so
I
figured
out
I
would
bring
it
back
up
again,
but
I
don't
know
how
many
of
you've
seen
that
we
have
260
seven
teams
in
the
kubernetes,
org
well,
Aaron
Aaron
probably
knows
mom.
D
F
So
I
was
looking
and
like.
If
you
see
how
long
you
see
if
I
could
share
my
screen
real,
quick,
oh
I,
guess
someone
else
is
sharing
their
screen.
So
I
looked
at
some
of
the
sleep
up,
Chang
yeah
and
if
you
look
at
the
list
of
of
members
on,
let
me
see
if
I
can
share
the
right.
I.
F
Apparently
can't
share
Sunny's
and
Linux
nevermind.
So
if
you
look
at
the
list
of
groups
and
things
like
a
lot
of
them
have
just
like
the
same
people
like
all
the
way
down
and
then
like,
if
you
change
the
page,
you
see
all
it,
it
even
lines
up
like
their
hacker
got
to
you.
So
it's
like
perfectly
aligned.
F
So
the
question
was
like
you
know,
is
this
like
the
most
efficient,
like
I'm,
still
kind
of
unclear
as
to
like
so
Tim's
main
point
like
as
a
sig
co-lead
I.
Don't
understand
why
I
have
to
manage
like
all
of
these
lists,
and
things
like
it
just
seems
like
a
hot
like
a
hot
mess
to
me
and
I
was
like
I,
don't
I,
don't
get
it
either
so
I
have
figured
I
would
bring
it
up.
Yeah.
D
So
that
was
part
of
an
effort
to
better
manage
the
communication
streams,
primarily
around
github
notifications,
to
separate
them
into
different
sections
and
as
a
person
who
has
gone
through
the
process
of
setting
up
all
those
lists
and
teams,
it
is
kind
of
a
pain,
particularly
is
now.
D
You
have
to
create
like
five
or
just
seven,
like
bots
user
accounts,
which
is
a
real
pain
I'm
just
like,
because
they
seem
to
be
out
of
their
own
lists,
so
they
can
get
their
emails
sent
to
the
right
Google
group,
and
then
you
now
have
to
also
manage
the
two-factor
off
for
each
of
those
five
to
seven
github
bot
users.
So
it's
all
kind
of
pain.
D
E
E
H
I'm
not
miscible
to
desert
because
actually
brand
rented,
that
we
have
created
procedure
half
a
year
ago
in
December
and
January,
and
it
seems
that
so
many
people
have
some
concerns
to
getting
it.
Speaking
about
the
to
fortification.
The
best
way
that
we
have
proposed
is
to
use
backup
codes
to
like
take
that
can
be
easily
shared
with
with
some
people
but
anyway.
H
So
if
you
are
a
sink
owner-
and
it
would
be
great
if
not
not
a
single
secona
but
multiple
SiC
owners
will
I
will
like
test,
if,
if
it
really
works,
because
for
me
personally,
it
works
better
than
it
has
been
before.
So
please
raise
your
concerns,
provide
your
situations.
How
can
we
also
get
in
a
better
way
and
pre-greek
so.
D
I
totally
come
back
to
you.
What
you
have
to
measure
is:
are
the
right
people
getting
notified
at
the
right
time
and
I
like
I
hate,
to
do
this
on
camera,
but
my
wrist
up
team
is
nobody
told
me
what
the
team's
work
for
names
are
not
self
descriptive,
as
somebody
who
makes
no
sense
to
me
and
is
not
clear
which
of
these
sixteen
I
should
notify.
D
As
a
member
of
the
kubernetes
organization,
I
have
the
luxury
of
seeing
how
many
people
are
in
which
team
and
sorry
I'm
just
going
to
notify
the
team
that
has
the
most
members
in
it.
As
somebody
who
created
the
teams
in
the
first
place,
yeah
I
pretty
much
just
added
the
same
people
to
all
the
teams
and
wanted
to
try
and
find
some
way
to
incentivize
others
to
add
themselves
to
the
right
teams,
and
that
never
happened.
D
Also
I,
don't
know
about
you
guys,
but
in
creating
these
things,
like
Google,
eventually
thought
I
was
a
robot
I
started
to
have
to
like
select
which
of
these
pictures
are
shops.
It
was
great,
and
nobody
explained
to
me
what
played
there
too,
like
nobody.
Nobody
gave
me
that
definition
as
we
were
supposed
to
just
sort
of
as
an
experiment
try
this
out
and
it's
super
duper
unclear
now.
In
theory,
the
data
is
out
there
right,
because
all
of
these
Google
groups
should
exist.
D
D
I
get
the
sense
that
there
are
some
groups
that
really
do
find
it
valuable
to
notify
high
traffic
individuals
just
for
the
purpose
of
design
reviews
to
make
sure
they
don't
get
pinged
on
every
little
full
request
or
every
little
typo
fix,
but
I
think
some
people
find
it
valuable,
but
I'm
not
sure
any
of
that
representation
is
here
today.
I
would
get
a
bigger
killing
the
teams
entirely,
but
I
feel
like
yeah.
F
Yeah
because
like
it
feels
or
maybe
making
it
even
opt-in,
because
I'm
looking
at
sig
instrumentation
right
now
and
all
of
their
groups
have
the
same
nine
people
in
them,
yeah
and
then
I've
noticed
also.
It
kind
of
tends
to
lead
to
noise
and
bug
report
where
it's
like.
Oh
no
sig
network,
misc,
I
meant
to
put
in
sync,
and
then
you
get
people
just
responding
with
CC
and
then
another
group,
and
it's
like
wait
a
minute.
F
D
D
Moving
away,
that's
going
to
be
useful
to
you,
so
instead
you
start
having
them
all
forwarded
to
email,
and
maybe
you
can
start
setting
up
rules
so
that,
depending
on
which
google
group,
these
notifications
are
coming
in
on
they'll
and
in
certain
places
and
you've
got
a
system
that
works
for
you
to
to
use
this.
But
I
I,
don't
know
other
thing,
just
hard
numbers,
at
least
as
a
I
think
it
was
a
week
or
two
ago.
D
F
F
And
I
would
like
I
would
like
to
help
with
this.
Can
we
can
we
kind
of
maybe
nail
down
a
little
bit
more
actionable
items
for
the
notes
that
I
can
I.
H
Mean
yeah,
so
anybody
here
any
is
any
suggestions.
How
can
we
a
crimp,
Lemann.
D
Justice
model
experiments
are
great,
I,
think
Caleb's
doing
an
experiment,
we're
just
not
going
to
do
that
and
see
how
that
works
for
us
is
a
cig
I
think
we
have
a
large
volume
of
data
out
there.
If
anybody
is
interested
to
see
how
often
people
are
actually
using
the
different
groups,
it
could
be
that
the
result
we
come
back
with
is
people
are
pretty
much
just
using
one
team,
probably
the
MIS
teams
that
has
the
most
people,
and
then
we
come
to
an
open
question
of.
D
Does
that
mean
we
should
just
go
back
to
using
miss
teams?
Or
does
this
mean
we
need
to
re-educate
on
the
teams
or
do
we
need
to
rethink
the
teams
but
I
think
I
personally
with
the
Advanta?
Having
that
this
question
with
some
data
to
back
it,
okay
or
I,
don't
know,
maybe
there's
enough
pain
and
frustration.
I
just
heard
from
multiple
people
who've
gone
through
the
creation
of
this
product.
D
The
process
of
creating
this
stuff
doesn't
seem
like
any
of
us,
find
it
useful
both
in
the
administrative
side
and
then
the
actual,
using
of
it
side,
but
we're
not
necessarily
the
end.
Consumers
of
this
I
feel,
like
that's
the
class
of
people
that
aren't
being
represented,
which
is
why,
and
with
those
asking
that
we
find
a
way
to
gather
data
on
it.
Yeah.
F
B
Hierarchy:
two
teams:
now
you
can
have
sub
teams,
so
I
think
the
purpose.
Initially.
You
are
correct
me
if
I'm
wrong
was
to
like
make
it
so
there
was
a
subset
of
a
sig
dedicated
to
bug
triage
and
a
subset
dedicated
to
reviewing
PRS
and
things
like
that,
and
so
various
parts
of
a
sig
could
be
like
more
specialized,
and
that
was
the
point
of
all
the
teams.
It
may
not
be
how
it's
being
used,
but,
along
with
that
hierarchical
model,
is
if
I
ask
you.
D
H
Okay,
like
here,
if
you
had
hidden,
if
you
hit
in
the
group
that
is
specifically
on
proposals
on
the
future
proposal,
so
I
like
Muslim,
specific
requests,
so
exactly
that
people
could
have
signed
into
that
group.
Reverse
of
the
specification
and
a
very
clear
message.
It
was
actually
the
initial
idea
if
I
work
in
online
box
or
like
pocket,
rationalization
again
ended
and
if
I'm
not
working,
I
won't
receive,
and
so
also.
F
F
B
The
question
is:
do
we
design
for
the
state
of
the
world
now
or
do
we
design
for
the
state
of
the
world
that
we
want
and
try
and
figure
out
how
to
get
us
there
and
I?
Think
that
was
the
idea
with
this.
Like
there's
good
intention,
it
doesn't
seem
to
get
us
to
the
state
that
we
want
right,
but
can
we
can
we
alter
it?
So
we
get
to
this
state
where
people
are
able
to
get
more
specialized
notifications.
B
B
F
F
If
you
need
something
you
ping
me
on
slack
personally
and
then
I'll
go
like
like
I
feel
like
if
we're
trying
to
optimize
for
them
that
they've
already
kind
of
I,
don't
know
if
like
given
up
but,
like
you
know,
they've
got
their
own
they've
got
like
I've
tried
some
tools.
I
tried
this
tool.
That
gives
you
like
a
real-time
view,
like
an
inbox
view
and
I
use
that
for
a
week
and
then
I
was
like
so.
D
Just
to
throw
out
a
straw
man,
what
if
you
were
to
put
out
a
proposal?
That's
you
know
declaring
a
github
team
bankruptcy.
Can
we
please
just
get
rid
of
all
the
other
teams
and
go
back
to
one
team
per
se?
What
objections
do
you
think
would
be
raised
and
what
data
or
arguments
do
you
think
you
would
need
to
have
prepared?
What
sort
of
plan
do
you
think
you'd
want
to
put
forward
I?
D
Think
well.
I
would
have
the
argument
that
once
we
have
SIG's
owning
one
or
more
repositories,
you
probably
want
at
least
three
teams
to
map
to
github
Zagal
structure.
I
mean
probably
least
two
teams,
one
for
admin
rights
on
that
verbo.
One
with
just
you
know,
pull
and
push
most
would
push
access,
so
I
guess
the
the
number
I.
Definitely
not
it's.
It's
probably
not
one,
definitely
not
seven,
but
something
somewhere
around
one
or
two
I.
Think
well.
H
D
Hierarchy
doesn't
allow
for
specificity.
If
you
know
you
want
to
notify
the
bugs
people,
you
can
notify
just
the
bugs
people.
If
you
don't
know
who
you
want
to
notify,
you
would
notify
the
whole
team
that
would
still
hit
the
bugs
people.
So
if,
when
the
bugs
people's
perspective,
it
doesn't
make
the
signal
for
their
membership
on
a
team
any
stronger
or
less
strong.
Does
that
make
sense.
B
But
it's
not
a
flaw
in
our
culture,
then.
Is
it
something
that
we
can
change
like
through
through
culture
by
asking
people
to
mention
more
specifically
by
making
it
clear
what
the
sub
teams
are?
If
there
was
a
standard
set
of
sub
teams
for
every
sig
sort
of
like
there
are
a
standard
like
you
know,
feature
requests,
bug,
fixes
etcetera.
Would
that
be
enough
to
address
the
issue
or
do
you
think
people
are
just
going
to
always
mention,
but.
I
Killer
this
is
dense,
I
had
something
idea
on
the
PR
side,
even
this
the
problem
that
people
are
not
able
to
reach
the
approvers
and
reviewers
rather
than
and
specific
six
and
for
each
PR,
you
know
it
would
be
dynamically
Catholic.
Who
are
the
possible
people
who
have
to
approve
this
or
review
this?
So
is
there
a
mismatch
between
trying
to
use
the
same?
But
you
know
the
approval
list
of
up
reverse
and
list
of
reviewers
is
totally
different
from
know
what
yep
the
person
needs
totally.
D
I
I
D
Although
yeah
my
experience,
I
still
had
to
go
nag
people
personally
on
flack,
which
is
unfortunate,
but
it's
that
that
that
assigning
people
seems
to
be
like
a
less
noisy
way
to
put
it
on
a
less
moist
dashboard
for
them.
Right
now,
I
mean
if
it's
not
clear,
I'm
this
close
to
just
saying
like
screw
it.
Let's
just
put
forth
a
proposal
and
presented
a
community
that
we
drop
all
the
other
teams
and
just
go
to
this
team.
I
just
feel
like
that's,
not
something
I
have
a
bandwidth
to
do
right
now.
D
F
F
Let's
get
rid
of
like
like
take
it
I'm,
trying
to
think
of
a
way
to
make
it
so
we
can
get
feedback
from
the
leads
without
it,
devolving
to
like
yeah,
like
hey
just
deleting
them
anyway,
like
that,
doesn't
really
get
us
anywhere,
which
of
these
teams.
Are
you
actually
using.
D
Okay,
a
useful
question:
I,
don't
know
again
I
kind
of
actually
like
the
when
we
did
when
we
added
all
those
save
labels
and
we've
added
the
need
sake,
automation
that
does
seem
to
steer
people
toward
guiding
save
labels.
D
F
C
Unless
you're
really
in
ingrain,
then
each
individual
meeting,
you
might
not
know
whom
owns
those
individual
things
but
I
do
find.
Having
like
some
I
think
the
misc
team
seems
to
be
either
you
don't
know
else
is
an
actual
bug
or
if
it's
not
a
pull
request.
So
you
don't
use
the
pull
request
thing
or
maybe
you're
just
interested
in
what's
going
on
with
the
cig,
so
you
follow
misc
or
you
join
misc,
just
to
get
an
understanding
of
the
arbitrary
issues.
C
Not
really
reposing
anything
is
just
wondering
if
we
did
sort
of
extending
grooving
either
to
they've
utilized
this
years,
and
that
would
also
help
with
some
of
the
good.
It
was
that
a
giant
proposal
to
convince
all
of
these
kings
and
their
individual
mailing
lists.
It
seems
like
only
about
half
of
the
cigs
that
I've
actually
done
that.
B
D
I
think
stick
testing
would
be
a
good
channel
2's
best
effort.
Ryan
instrument
is
basically
really
open
to
creative
ideas.
To
use
Cuba
nadir
to
better
provide
actionable
data
and
give
Reiter
is
actually
what
I
was
referring
to
when
I
talked
about
just
an
alternative
to
the
use
of
data
of
notifications,
just
like
throw
those
out
entirely
and
look
solely
at
PRS
that
have
your
name
on
them.
D
You
can
even
use
it
to
stock
your
potential
approvers
and
see
which
ones
seem
to
have
a
crap
ton
of
PRS
associated
with
them,
and
maybe
you
want
to
go,
find
another
trigger
to
go.
Get
your
PR
approved.
It's
necessarily
something
I've
wanted
to
write
down
under
soft
just
yet,
because
I
think
it's
a
workaround
for
unhealthy
level
of
approvers.
F
C
D
And
and
yes
back
to
Morgan's
super
earlier
point
about
there
not
being
enough
people
in
order
to
actually
staff
these
teams-
that's
yeah!
That's
that's!
Being
worked
on
like
I'm
trying
to
tackle
that
in
a
small
by
looking
at
it
through
the
lens
of
donors,
files
and
stuff,
but
I
do
plan
on
coming
up
with
ways
to
identify
and
nominate
people
who
may.
D
A
Okay,
geez
I
think
you
addressed
the
next
point
in
the
agenda
earlier.
Do
you
want
to
speak
any
more
to
that
or
are.
E
D
I
thought
of
it
as
a
treat
highlighted
they
need
to
okay
to
testing
in
the
past
is
a
sign
that
you
may
be
dealing
with
a
new
contributor
or
somebody
who
hasn't
been
through
the
process
before
so
you
can
help
Shepherd
and
watch
that
PR
in
general.
That's
pretty
little
effort.
The
stall
things
is
tangled
in
tricky
yeah.
E
So
I
mean
we
gotta
find
some
answer
this,
because
unless
we
can
find
somebody
to
do
some
work
on
the
bot
to
fix
that
the
dot
dot
owners
problem,
cadet
seems
like
an
issue
or
owners
files
with
no
approvers
or
means
somebody.
Somebody
did
some
shelf
food
to
show
that
out,
I
think
was
Erina
and
basically
there's
a
ton
of
these
that
are
broken.
They're,
like
a
hundred
or
so
those
files
in
kubernetes
package.
D
Sub
directories,
so
I
would
open
that
up
as
an
issue
in
the
tests,
infra
repo
and
let's
escalate
the
priority
of
that
get.
That
worked,
because
that's
not
right
well,
I
think
that
owners
filed
without
approvers,
but
just
reviewers
was
intended
to
work.
The
automation
may
not
be
doing
the
right
thing
by
pulling
the
approvers
from
a
higher
level
node
in
be
in
the
tree.
So
this
it
was
a
design
to
give
people
who
are
lower
the
opportunity
to
review
a
PR
and
sign
off
on
it
and
then
basically
at
a
higher
level.
C
E
D
I've
done
that
in
the
past
here
or
there
and
I
do
believe
that
every
little
bit
helps
but
I.
Think
if
you
do
that,
it's
also
useful
to
do
that
with
an
eye
towards
how
can
I
systematize
this,
you
know
document
just
a
lot
of
people
can
do
it
or
describe
it
in
an
easy
enough
way
that
it
could
be
automated
right.
Okay,.
A
Thank
you
guys
and
then
George
I
think
you
also
hit
on
the
next
item
earlier.
So
are
you
good
at
that
great
okay?
Does
anybody
else
have
something
through
the
last
six
minutes,
but
they
wanted
to
talk
about
specifically.