►
From YouTube: SIG Contributor Experience 20180404
Description
Our meetings our weekly and public, find out more here!
https://github.com/kubernetes/community/tree/master/sig-contributor-experience
B
Beautiful
thank
you
good
morning,
everybody
and
welcome
to
this
edition.
The
April
4th
2018
edition
of
contributor
experience,
Paris
will
be,
is
just
running
a
couple
of
minutes.
Late
and
she'll
be
joining
in
a
few.
If
you
could,
please
add
your
name
to
the
agenda
under
attendance,
that
would
be
great.
B
B
B
A
So
we
are
set
for
hosting
for
the
next
three
weeks,
but
we
need
to
start
think
about
on
the
spreadsheet
itself
on
who
wants
to
after
queue
we're
basically
set
until
cube
con.
After
that
we
need
to
start
thinking
about
doing
hosts.
So
the
spreadsheet
is
linked
to
sorry
I
can't
what
I'm,
what
I'm,
recording
I
can't
really
look
things
up.
A
But
if
you
look
at
the
community
meeting
notes
at
the
top
there's
like
a
planning
spreadsheet,
that
we
have
that
kind
of
lists,
what
SIG's
are
doing
the
reports
that
week
and
who
the
host
is.
So
if
we
want
to
do
it
like
last
time
and
then
just
add
a
few
more
dates,
we
can
do
that,
but
we're
good
for
the
next
three
weeks
at
least
great.
A
B
C
Today
we
have
again
a
one
o'clock
edition
I'm,
just
having
a
really
hard
time
getting
contributors
to
sign
up
for
this
I
am
dude
write
a
blog
post
for
CNCs,
slash
kubernetes
blog
about
it,
but
if
everybody
on
this
call
could
help
us
like
retweet
this
stuff
help
us
like
write
blog
posts
about
it,
I
think
we
would
definitely
get
a
better
gauge
here,
I'm
just
up
to
my
eyeballs
right
now.
So.
C
C
Ideally,
I
put
out
a
spreadsheet
that
people
could
sign
up
for,
but
nobody's
using
the
spreadsheet,
I'm
gonna
kill
the
spreadsheet
actually
and
think
about
other
ways
that
people
could
sign
up.
That
would
be
better
I,
don't
know,
maybe
making
a
PR
against
the
meet
our
contributors
doc.
But
George
do
you
have
anything
add
for
user
office.
A
E
E
C
E
A
B
Okay,
so
right
now,
what
is
the
best
way
so,
like,
let's
say,
I
sent
out
some
tweets
to
promote
this,
and
somebody
contacted
me.
I
was
like
hey
I
want
to
do.
This,
should
I
just
refer
their
names
to
you,
George
and
or
Paris
of
what
is
the
best
way
for
people
to
to
volunteer
right
now.
If
the
spreadsheets
gonna
go
away,
yeah.
C
F
F
D
My
perspective
I
think
that
makes
sense
if
we
can
tidy
up
the
cherry-pick
process
so
that
we
know
what
we're
doing
for
111,
but
then
also
within
that
one
of
the
maybe,
by
the
time,
we're
done
with
1.11
have
separately
done
some
combining
and
scrubbing
of
the
rest
of
the
docs.
And
if
the
prowl
plugin
also
comes
along,
then
the
result
should
be
something
a
lot
easier
to
document
like.
F
Yeah,
the
short
version
for
those
who
haven't
followed
along
with
this
epic
task
is
that
it's
it's
way
easier
to
just
go
poke
a
human
being
ticking
a
label
called
cherry-pick
approved
to
your
polar
costs,
to
release
branches.
All
of
this
confusion
over
like
cherry-pick
candidate
and
cherry-pick
approved
and
setting
the
milestones
right
and
all
that
stuff
is
for,
like
automation,
to
sometimes
maybe
kind
of
sort
of
magically
set
this
level.
F
F
All
these
things
are
addressed
a
little
better
by
combate
commands,
just
like
squash
cherry
thing,
but
we
need
to
think
about
what
labeling
should
be
done
to
help
release
branch
managers
track
what's
going
in
and
what
has
yet
to
go
in
anyway,
while
I
have
the
floor
and
I'll
put
this
in
the
meeting
notes
afterwards,
Christophe
and
I
had
a
brief
chat.
Instinct
testing
yesterday
over
trying
to
get
some
clarity
on
what
we
want.
F
She
come
to
me
what
we
want
to
prove
to
me
and
what,
if
anything,
we
want
somebody
using
github
or
requester
to
you
approve,
deny
request,
changes
thing
like
what
we
want
that
to
correspond
to
you
and
we're
going
to
have
a
breakout
session
from
state
testing.
I
feel
like
Christophe,
probably
accurately
represents
this
groups
opinions,
but
if
anybody
else
is
interested
feel
free
to
reach
out
we'll
make
sure
for
that
info
along
happens,
not
linked
to
the
PR
and
stuff
in
meeting
notes.
That's
it
for
me.
F
A
They
figured
out
that
most
of
our
information
in
slack
is
basically
throw
away
and
not
very
useful
as
a
knowledge
base,
so
they're
actually
pivoting
and
not
even
doing
any
of
this
anymore,
so
that
kind
of
just
all
went
away,
but
I
did
find
out
there's
a
lot
of
people
that
I
think
are
really
doing
a
great
job
in
kubernetes
users
through
the
everyday
slog
of
answering
user
questions.
We
should
maybe
consider
giving
them
more
recognition
or
something
like
that.
A
B
F
B
H
Yes,
new
here,
matt
record
I
work
at
Google
on
container,
tooling,
I,
guess
specifically
kubernetes
tooling,
so
I
helped
start
mini
cube
way
back
when
and
you
know,
I've
been
working
on
a
bunch
of
stuff,
including
scaffold
and
more
stuff,
so
kind
of
out
of
that
work.
You
know,
we've
we've
seen
this
kind
of
need
for
this.
H
This
developer,
tooling,
you
know
group
or
you
know,
I,
don't
know
exactly
what
it
manifests
itself
as,
but
just
a
place
to
talk
about
this
tooling,
and
there
was
some
interest
from
I
guess
some
of
you
guys,
you
know.
Does
the
scope
overlap?
You
know
where?
Where
do
we
fit
in?
How
do
we
kind
of
coordinate?
How
can
we
produce
something
that
is
useful
to
you
guys,
because
there's
some
point
where
you
know
the
contributors
to
kubernetes
and
community
projects
are
also
developers.
H
You
know
and
they're
using
this
piece
tooling.
So
you
know,
one
great
example
is:
is
mini
cube,
which
is
like
first
and
foremost
tool
for
you
know,
developers
to
get
started
with
kubernetes
and
get
a
local
cluster,
but
it's
it
also
has
a
use
case
where
a
lot
of
contributors
are
using
it,
for
you
know,
downstream
projects
like
sto
and
and
all
of
these
other
projects,
as
part
of
you
know
their
developer
experience.
H
So
there
is
some
overlap
there
and
just
figuring
out
how
we
could
communicate
that
to
you
guys
so
that
we
can
get
feedback
from
contributors
on
these
tools
and
and
just
kind
of
share
information
and
in
the
best
way
possible
and
then
also
I,
guess.
Another
kind
of
topic
relevant
for
this
group
is
on
I
guess
is
more
of
a
personal
issue,
but
I
mean
in
slack
right
now
we
have
a
mini
cube,
slack
channel
with
I
think
it's
got
over
two
thousand
people
in
it.
H
There's
a
draft
slack
channel
and
it's
great
to
have
slight
channels
for
these
specific
tools.
But
the
contributors
for
these
tools
don't
talk
to
each
other,
which
is
a
bit
of
a
problem.
So
I
don't
know
if
it
we
create
this
working
group.
If
we
have
a
slack
channel,
maybe
that
alleviate
some
of
this
pain,
but
actually
getting
the
contributors
of
these
tools
talking
to
each
other
and
and
not
having
I
feel
like.
H
H
Yeah
I
mean
just
figuring
out
a
way
that
I
don't
know
what
what
we
could
reduce,
as
as
a
group
I,
don't
know
if
it's
some
sort
of
report
or
some
sort
of
channel
where
we
could
actively
get
feedback
on
these
tools
from
contributors
who
you
know,
maybe
aren't
using
these
tools
day
to
day,
but
our
kind
of
experts
and
you
know
the
underlying
technology.
So
basically
how?
How
can
we
spoke
this
project
to
help
you
guys
more
so.
G
Well,
I
think
so,
based
off
of,
like
I,
add
a
little
bit
background
in
this,
because
I
was
in
cig
testing
yesterday,
where
Matt
was
making.
Basically,
this
exact
same
exact
time
talk,
I,
think
from
a
scoping
perspective.
I
think
that's
that's
the
first
step
that
that
that
needs
to
be
done
is
scoping
like
what
is
covered.
G
Definitely
in
forming
like
I
think
we
would
be
downstream
consumers
of
things
that
maybe
could
that
may
come
out
of
this
because
testing
like
a
you
know,
as
as
was
mentioned
yesterday
in
cig
testing,
testing,
kubernetes
and
testing
the
upstream,
like
upstream
kubernetes
against
whatever
development
tools
are
out.
There
provides
a
good
user
experience
across
the
board,
but
yeah
I
think
I
think
right
now.
If
anybody
has
any
feedback,
I
think
the
best
place
to
going
and
leave
feedback.
H
Cool
sounds
good
yeah,
just
making
sure
that,
like
we
have
an
effective
way
of
sharing
information
on.
If
this
group
is,
there
might
not
be
overlap
between
these
six,
but
we
we
want
an
effective
way
to
actually
communicate
what
we
find.
What
we're
working
on,
because
I
mean
we
notice
in
the
past
that
you
know
the
tools
that
we
work
on
on.
Sometimes
the
features
are
not,
as
you
know,
broadly
broadcast,
as
as
we
would
hope
so,
just
making
sure
that
everyone's
kinda
on
the
same
page
and
we're
not
reinventing
the
wheel
anywhere
so
I'm.
C
Not
happy
to
create
a
slot
channel
for
you
to
if
you
visit
the
slack,
admins,
Channel
and
just
drop
in
whatever
suggested
name
that
you
have
for
the
group.
We
can
even
create
that
within
the
hour
that
you've
requested
so
feel
free
to
do
that
and
then
what
you
can
do
is
advertise
that
channel
into
all
the
developer
tools
individually
and
let
them
know
that
you
know
that's
a
channel
that
might
be
interest
to
them.
So
definitely
that's
slack
is
an
area
that
we
have.
F
Do
but
I
kind
of
agree
with
the
point
where
I
made
in
chat
like
I,
feel
like
a
lot
of
this
discussion
could
be
had
in
in
say,
gaps
and
like
okay
number
one
getting
people
to
actually
talk
to
each
other
is
hard
it
as
it
turns
out,
but
I
think
like.
If
you
take
the
effort
to
lurk
and
say
gaps,
and
when
people
are
asking
questions
about
that
tooling,
you
can
sort
of
route
them
to
the
right
channel
or
place
that
sometimes
does
provide
high
visibility
that
hey
there
you're,
like
other
efforts
going
on.
F
So
I
think
more
of
an
active
presence
there
kind
of
get
to
an
audience
to
begin
with
who's
who's
receptive
to
any
answers
you
might
be
able
to
provide,
but
the
problem
of
getting
like
the
individual
sub
project
maintainer
is
to
remind
themselves
that
there's
a
broader
world
out
there
and
talk
to
each
other,
that's
a
little
bit.
It
takes
a
little
bit
more
effort,
but
I
think
that's
something
see.
Apps
could
absolutely
helpless.
C
So
follow
up
to
my
email
from
earlier
this
week
might
have
even
been
yesterday,
I'm,
not
even
sure,
but
we
have
two
slots
at
cube.
Con
EU
one
is
an
update
one
as
a
deep
dive
update
is
essentially
what
we've
been
doing
for
the
roadshow,
just
updating
people
as
to
what
we've
been
working
on
by.
Why
are
we
working
on
it?
C
Why
we
care
and
then
the
deep
dive
is
going
into
either
one
of
the
projects
and
we're
working
on
or
a
problem
that
we're
having
and
getting
audience
feedback
contributor
feedback
and
possibly
even
getting
some
work
done
during
that
session.
Both
are
actually
only
thirty
minutes,
though,
so
the
actually
like
the
road.
The
update
is
sort
of
covered,
and
you
know
everyone
else.
C
Ii
and
I
will
put
together
some
slides
for
that
and
email
everyone,
those
slides
to
make
sure
that
we're
covering
all
the
work,
that's
being
done
in
the
group
like
I'd,
say
a
week
before
cube
con.
Hopefully,
but
then
the
deep
dive
I
did
talk
to
Ryan
J
at
Red
Hat.
Is
he
on
the
line?
I
thought
I
said:
yeah
there
is
Ryan.
You
still
cannot
come
correct,
I.
H
C
So
we
were
thinking
that
Ryan
would
cover
the
developer
guide
for
the
deep
dive
it,
but
it
doesn't
sound
like
Ryan
is
officially
on
the
hook
for
travel,
yet
t
pep.
How
do
you
feel
about
covering
that
kind
of
a
session?
I
mean
I'm
also
down
to
help
in
moderate
and
timebox
us
and
keep
us
honest,
but
I
think
the
developer
guide
would
be
a
really
great
30-minute,
spend
cube
con
I.
D
C
I
think
it's
it's
Thursday
at
1550,
so
yeah
I
just
got
to
meet,
get
get
with
me
offline
and
we'll
figure
it
out.
But
does
anybody
my
point
of
bringing
it
up
on
this
conversation
is?
Does
anybody
have
any
other
deep
dive
topics
that
they
think
we
should
be
covering
that
are
either
more
important
or
would
be
better
for
us
to
spend
our
30
minutes
with.
H
C
Alright,
so
with
the
mentoring
program,
we
have
five
different
projects,
all
of
which
are
individuals
helping
upstream
contributors,
I'd
like
to
give
them
an
identity
outside
of
thanks
for
helping-
and
this
is
how
we
form
communities
is
by
giving
people
identities
in
this
field.
So,
for
instance,
docker
has
captain's.
However,
in
Dockers
sense,
that's
evangelists
not
mentor,
it's
not
like
it
necessarily
matters
for
branding
but
I.
Think
you'll.
C
You
kind
of
understand
what
I'm
saying
here
and
ideally,
when
we
blog
about
this
and
when
we
get
more
PR
about
this
and
do
more
Docs,
we
will
say
kubernetes
insert
word
here
and
the
insert
word
here
has
been
racking
my
brain,
and
this
is
the
call
for
help.
I've
actually
engaged
for
marketing
professionals,
including
folks
at
linux
foundation,
and
none
of
us
can
come
up
with
a
good
solution.
C
I'll
go
on
public
record
and
say
that
and
I
think
it's
also
because
I've
been
working
with
it
for
at
least
three
months,
so
in
Martin,
in
the
land
of
creative
services,
when
you've
been
working
with
something
you're
like
I.
Just
want
this
to
be
shipped
and
done
with
already
so.
I
could
call
them
like
hippos
and
I'd,
be
totally
happy
with
it
at
this
point,
but
some
of
the
names
that
we
have
are
like
kubernetes
mentors
because
believe
it
or
not.
The
word
mentor
is
Greek
and
that
would
go
with
us.
C
However,
I
think
that's
kind
of
bland
and
doesn't
really
capture
the
essence
of
what
these
people
are
doing.
So,
for
instance,
these
people
are
not
mentoring,
users
and
our
user
base,
and
our
contributor
base
have
a
serious
Venn
diagram
overlap,
as
everybody
here
knows,
so,
I
want
to
make
sure
that
these
people
are
not
going
to
also
get
bombarded
with
user.
C
These
questions
when
they
are
on
their
Twitter
bio
that
says
kubernetes
mentor,
which
they
most
likely
will
and,
of
course
most
of
these
Google
would
probably
help
them
because
all
of
them
are
so
empathetic
but
again,
at
the
same
time,
I
really
want
to
try
to
make
something.
Quirky
and
creative
I
have
a
list,
but
I'm
gonna
share
with
everyone.
As
soon
as
I
can
dig
it
out
of
my
email
right
now,
I'll
share
it
with
everyone
in
the
zoom
chat,
also
in
the
slack
chat
as
well.
C
And
greet
shipwright
and
Greek:
oh
yeah,
that
that
could
be
good
to
Josh.
Yes,
so
the
words
that
I
just
put
in
the
chat
kubernetes
pilots.
So
we
have
pilot
right
now.
That's
what
I've
been
working
with
just
to
keep
going
and
not
have
a
blocker,
but
but
I
don't
know.
If
everybody
knows
the
kubernetes
means
helmsman,
which
ultimately
means
pilot,
so
I
feel
like
it's
kind
of
like
saying
water
is
wet
and
also
when
we,
when
we
have
called
people
pilots
in
the
past,
people
thought
that
they
were
testing
kubernetes.
C
So
that
was
a
little
bit
unclear
there.
We
also
kubernetes
skipper
kubernetes
contributor
mentors
so
adding
three
words,
but
that's
kind
of
long,
but
we
can
condense
that
and
they
like
capes,
so
Kate's
mentor
or
to
make
Kate's
contributor
mentor
or
died
or
advisor
kubernetes
ladder,
mentor,
died
or
advisor
through
an
ADIZ
upstream
guide
or
advisor
and
then
also
cube
mentor,
cube,
mentor,
cube,
M
and
TR
to
play
on
coop,
cube
control.
I
C
C
C
Mate,
yeah,
ok,
so
I'll
add
this
solution:
Wireless
and
yeah.
Just
everybody
here,
their
creative
juices
flowing
and
get
back
to
me.
Dm
me
on
slack
reach
out
to
me
by
pigeon.
Al
doesn't
matter
get
to
me
and
I'm
gonna.
Send
the
shortlist
today
this
afternoon
to
the
steering
committee.
Have
them
laugh
at
the
list
for
a
little
while
they
will
know
good
party
Wednesday,
laugh
and
then
and
then
we
will
go
forward.
C
The
reason
why
this
is
such
a
blocker
for
me
is
because
I
want
to
write
more
and
more
documentation
and
I
can't
write,
insert
word
here
anymore
and
that
does
not
suffice
for
blog
posts,
so
much
appreciated
on
the
help
front
and
the
winner
will
obviously
get
multiple
swag
items
for
me.
So
very
awesome.
Thank
you
very
much.
I'm
done
with
that
topic.
B
C
Alright,
so
we
did
find
out
this
week
with
we've.
Had
some
hiccups
on
the
spam
glitch
and
folks
were
thinking
that
they,
their
emails,
were
deleted
and
things
like
that,
so
they
brought
up
the
topic
of
who
owns
these
lists.
The
lists
again
being
kubernetes
does
kubernetes
users.
These
are
the
google
groups
that
we
own
C
and
C
F,
so
moderates
other
lists,
but
the
current
owners
for
these
groups
or
individuals,
mostly
brain
grants,
and
some
other
folks
that
had
started
the
project
and
have
been
with
a
project
forever.
C
So
they
are
curious
as
to
where
this
moderation
should
sit.
I,
think
we
we
moderate
most
communication
channels
at
this
point
through
contributor
experience,
I
think
that
we
should
probably
house
those
here
like
I,
think
K
users
is
a
little
bit
of
a
stretch,
but
it's
not
the
first
stretch
that
we're
taking
on
by
any
means.
But
again
it's
kind
of
like
like
what
we
said
earlier
and
to
match
point
with
the
working
group.
It's
like
we're
a
horizontal
group
and
we,
our
users,
are
the
contributors
for
the
most
part
in
vice-versa.
C
So
I
think
we
should
get
a
higher
team
together,
probably
the
same
team
that
we
have
for
slack
and
other
people
who
would
like
to
moderate
this
and
when
I
say
moderate
I
mean
that
in
the
lightest
form
possible
latest
literally
lightest,
but
this
is
just
making
sure
that
there's
spam
has
come
through
lately.
The
spam
is
deleted
in
a
timely
fashion
and
that
people
are
acting
appropriately
and
I
mean
we
typically
don't
have
any
of
those
cases.
C
A
C
C
C
I
would
probably
need
a
process
and
in
which
we
decide
who
and
what
I
mean
right
now.
It's
just
the
people
that
have
asked
to
be
put
on
and
based
off
time
zones
and
things
like
that,
especially
with
slack
so
we've
probably
put
in
some
kind
of
guidelines
around
time
zones
and
coverage
and
and
stuff
like
that.
Okay,.
F
Like
the
ideal
of
what
impossible
case
is
a
super
strict
decision
tree
that
says
yes,
you
should,
you
know,
do
something.
No,
you
should
not
do
something,
because
then
you
can
run
anybody
through
that.
On
the
other
end
of
the
spectrum,
we
have
like
don't
violate
the
code
of
conduct
and
I
feel,
like
the
guidelines
for
moderation
are
probably
somewhere
in
the
middle,
where
you
need
to
trust
moderators
to
have
direction,
but
it
should
also
be
pretty
clear
like
when
people
are
stepping
over
the
line.
You
don't
want
them
to
know.
C
F
A
C
The
moderation
of
mailing
list
versus
slack
is
probably
20%
of
the
workload
that
slack
moderators
get.
So
if,
if
that
I
mean
maybe
even
ten
honestly,
so
it's
a
much
much
smaller
workload.
But
if
this
groups
taking
it
on,
then
that's
again
an
addition
to
the
workload
of
the
moderators
that
are
doing
those
so
I
will
start
with
a
draft
first
pass
and
moderation
guidelines
and
then
we'll
take
it
to
this
group
next
week
to
see
what
everybody's
thoughts
are.
Okay,
I.
G
Have
just
one
question:
I'm
gonna
put
Aaron
on
the
spot
with
your
steering
committee
hat.
Is
there
an
update
as
far
as
a
code
of
conduct
committee
as
far
as
an
escalation
point,
if,
like
from
a
light
community
management
standpoint,
a
light
moderation
standpoint?
If
there
is
questions
or
if
a
problem
does
arise,.
F
Until
such
time
as
there
is
a
code
of
conduct
committee,
if
there
is
one
just
treat
the
steering
committee
as
a
code
of
conduct
of
committee,
I
I
personally
would
like
to
break
that
responsibility
out
into
a
separate
committee
of
people,
but
and
with
issues
at
the
moment.
So
it's
still
like
it's
still
on
our
minds.
I
think
the
last
time
we
discussed
it,
the
consensus
was
it.
F
F
J
C
J
No,
that's
fine
and
I'm
glad
you
did
it
so
I
think
we
can
have
a
big
discussion
around
it.
So
just
two
brief
about
the
issue.
You
know
it's
about
the
new
labels
we
recently
added-
and
this
particular
issue
is
about
updating
the
triage
guidelines
showing
the
usage
for
these
labels
right.
So
mainly,
we
have
a
comments
from
Erin
on
the
separate
issue,
not
in
this
particular
issue
but
but
for
this
issue
and
then
Christoph
nothing.
J
You
know
we
have
provided
the
motivations
for
these
labels
earlier
and
when
we
send
the
proposal
and
I
work
with
Garrett
at
that
time,
Eddie
crest
I
had
lots
of
common
in
the
dark
as
well
and
then
you
know
we
had
the
email
list
proposal
and
we
did
get
some
comments
there
as
well
from
Jordan.
You
know
Bryan
grants
and,
and
but
the
eventual
concession
was
to
go
forward
with
it.
You
know
I
did
bring
up
at
the
country
box
meeting
last
month
at
index.
J
F
J
F
I
hear
all
of
the
history
I
guess,
like
my
my
apologies
for
like
having
maybe
a
slight
change
in
opinion
now
that,
were
this
part
of
course.
But
to
me
the
change
of
opinion
came
from
the
fact
that
you
implement
this
with
a
bot
command.
The
suggestion
was
to
use
slash
clothes
and
then
optionally
orbeez
enough,
for
that.
F
The
difficulty
is
that
slash
clothes
as
a
command
that
only
people
who
are
members
of
the
committee's
or
it
can
use,
and
my
my
understanding
of
the
reason
for
these
labels
was
to
allow
a
broader
audience
of
people
who
haven't
yet
become
members
of
the
cuber
Nettie's
organization
to
do
issue
triage
as
one
way
of
demonstrating
intent
to
help
out
the
community.
And
if
that's
the
case,
it's
technically
like
difficult
to
have
different
implications
of
the
same
bot
command,
be
restricted
to
different
groups
of
users.
So
my
suggestion
was,
it
kind
of
seems
like
these.
F
Labels
are
already
intended
more
for
issue
triage,
not
necessarily
issue
closure
and
so
I'm
wondering
if
it
made
sense
to
rename
them
to
triage
foo
and
then
have
a
slash
triage
command
for
that.
Stepping
back
a
little
bit
more
like
just
personally
speaking,
I
have
an
objection
to
spraying
more
labels
all
over
the
kubernetes
organization,
when
we
don't
actually
have
a
reason
to
use
them.
The
fact
that
there's
no
bot
commands
for
these
means
that
only
a
restricted
group
of
people
can
actually
use
them
and
I
would
have
preferred
this
to
be
done.
J
Absolutely
and-
and
you
know,
I
mean
even
today
also
and
when
we
proposes
labels,
the
intention
was
never
to
have.
You
know
like
a
associated
bot
commands
for
this
label,
so
the
intention
was
and
I
know,
I
did
put
in
the
in
the
issue
as
well.
The
intention
was
for
people
who
do
not
have
in
would
not
like
the
arc
member
who
do
not
have
a
privilege
to
close
something
right
to
run
a
bath
command.
So
for
anyone
like
a
new
contributors
right.
J
If
someone
is
looking
at
the
issue,
they
that
the
intention
for
this
label
was
for
them
to
just
add
the
label
so
that
you
know
and
I
know,
I
keep
saying
that
to
to
identify
issues
which
are
the
close
candidates.
So
what
happens
is
if
I'm
network
member,
for
example,
I
mean
you
contribute
I'm
looking
at
submission,
I'm
like
hey,
this
is
a
duplicate
issue,
or
this
is
I,
cannot
recreate.
You
know,
reproduce
it
anymore
right
as
an
nun
or
member.
You
know,
I
would
just
add
a
comment.
That's
all
I
could
do
right.
J
You
know
you,
you
can
have
some
labels
for
sig
and
whatnot,
but
I
all
just
add
the
comments.
Now
these
issues
are
easy
to
close
by
someone
who
has
Authority
close.
We
can
do
the
slash,
close
command
right.
The
intention
for
this
label
is,
you
know,
as
an
our
member
I
can
go
and
search
for
this
particular
label.
You
know
with
the
close
with
it's
a
closed
duplicate
clues
you
know,
can
do,
cannot
reproduce
or
you
know
close.
There
are
four
different
labels
there.
J
Well,
you
know
I
can,
as
all
member
can
go
and
search
for
this
label
or
if
I'm,
you
know
for
a
particular
seek
members
as
well,
and
then
you
know
those
are
like
a
easy
close,
because
somebody
already
did
some
work
there
right
could
not
reproduce
or
anything,
and-
and
you
know
if
they're
I
can
find
like
20
days
later
issues,
it
would
be
easy
to
close
what
series
you
know.
You
cannot
really
search
for
the
comments
right
versus
I'm.
F
Gonna
agreement
with
that
I'm
just
saying
as
a
technical
implementation
detail,
if
you
want
to
enable
people
who
were
formerly
only
capable
of
applying
comments
to
apply
these
treeoche
labels,
there
needs
to
be
a
box
man
for
that
and
in
order
to
implement
the
botkin
and
such
that
they
can
do
it.
It's
got
to
be
made
thing
other
than
clothes,
and
so
typically,
when
we
allow
people
to
add
any
anybody
to
add
a
label
so
like
slash,
say,
foo
or
slash
priority
food.
The
labels
are
prefixed
with
that
pocketed
so
I'm
just
suggesting.
F
Instead
of
calling
the
labels
closed,
duplicated
closed
cannot
reproduce
call
them
triaged
slash,
cannot
duplicate
or
whatever.
So
you
still
get
my
use
case
where,
like
we
could
have
humans
or
bots,
go
search
for
everything.
That's
been
triaged
and
we're
enabling
people
who
are
not
yet
org
members
to
apply
these
labels
to
do
good
work
contribute
our
nation's
that.
J
Sounds
sounds
sounds
really
good
to
me
around.
You
know
that
serves
the
purpose
right
for
folks
to
identify
the
issues
which
are
sort
of
triage
initially,
so
do
you
we
end
up
for
the
discussion
on
that
about
replacing
the
clothes
with
triage,
and
you
know
we
I
can
just
go
ahead
and
create
a
PR
to
change
those
labels
that
make
sense
so
so.
F
B
B
C
B
A
So
if
you
follow
the
link,
none
of
this
should
be
a
surprise.
We
went
through
this
as
a
Google
Doc
and
then
it's
actually
sitting
as
a
template
in
community,
slash
that
contribute
experience
and
the
ideas
what's
order
or
whatever
we
copy
it
over,
and
this
is
kind
of
like
stuff
that
doesn't
automate
very
well
auditing,
slack
channels
that
kind
of
stuff,
so
I
made
a
checklist
and
I
was
thinking.
Hey
it'd
be
really
great.
A
A
A
A
It's
just
a
bunch
of
Google
Groups,
and
so
it's
like
I
wonder
why
we
don't
have
user
forums
like
docker,
Mozilla
and
a
whole
bunch
of
other
open
source
projects,
so
I
started
thinking.
I
talked
to
Chris
a
little
bit
kind
of
started.
Looking
at
it,
you
know,
and
it
was
like
hey.
You
know
this
can
also
actually
maybe
replace
mailing
lists.
Then
we
find
out
that
some
other
open
source
groups,
like
ghost,
are
moving
their
community
entirely
to
that
and
I.
A
You
know
that
that's
a
bridge
too
far,
I
think
right
now,
but
I
figured
I
would
start
a
conversation,
so
I
started
I,
couldn't
sleep
last
night
and
I
kind
of
wrote
out
an
entire
cap
and
I'm
drafting
it,
but
I
do
want
to
put
one
of
the
first
things
on
there
is
like
this
is
not
the
elect
replace
slack
cap.
If
you
want
to
lead
that
by
all
means,
someone
else
do
that,
but
I'm
starting
to
think
of.
A
Would
it
be
great
if
we
had
in
like
a
nice
integrative
forum
that
had
the
match,
kubernetes
branding
in
some
of
the
examples
of
docker
community
does
a
really
great
job
of
integrating
that,
and
it
looks
really
nice
and
things
like
that.
There's
some
concerns.
How
does
it
relate
to
stack
overflow
and
mailing
lists,
and
how
much
work
is
this
and
all
that
kind
of
stuff
and
I'm
kind
of
covering
that
in
the
cup
and
mostly
I'm
thinking
hey?
A
F
I
just
wanted
to
share
the
screen
if
you
haven't
seen
it
yet
this
thing
right
here:
if
you're
gonna
go
that
piece,
io
/,
github
labels,
you
think
this
dock,
it's
generated
based
off
the
labels
file,
so
I'm
trying
to
make
this
the
place
that
everybody
goes
to.
What
they're
asking
questions
like?
Does
this
github
label
mean?
Why
do
you
have
this
github
label?
So
here's
the
description
of
like
what
are
the
labels
that
should
be
here.
There
are
labels
that
our
automation
can
seems
today.
F
So
this
just
to
underscore
when
I
was
the
point,
I
was
trying
to
make
earlier
like
I,
don't
want
to
blast
the
label
across
all
kubernetes
unless
we
have
automation
that
uses
it
across
all
of
the
identities.
How
to
add
a
new
label?
Do
this
thing
in
for
this
paper
and
then
this
describes
sort
of
what
the
labels
are,
who
can
use
them?
F
Our
intent
is
to
eventually
so
much
in
the
same
way
that
we
have
fought
commands
be
a
thing
about
work
like
a
static
table
that
humans
had
to
update
and
eventually
turned
into
a
page,
that's
lying
on
prowl.
What
to
do?
The
same
thing
labels
were
just
not
there,
yet
it
seemed
more
important
to
get
the
content
first.
Also
for
what
it's
worth.
Each
of
these
labels
are
like
deep
link,
so
you
can
do
a
little
click
on
the
label
and
then
copy
paste
that
link
over
to
somebody.
F
C
A
B
And
then
I'll
do
a
quick,
dev
stats
update
here.
So
we
are
we've
designed
a
priority
queue
request
to
dead
stats
and
I.
Think
I
saw
Lucas
on
the
law.
Fine,
so
Dan
Cohn
has
enabled
us
to
given
us
permissions
to
make
that
happen,
and
so
how
we're
going
to
do
this
priority
queue
was
that
we
would
do
it
via
github
project
boards,
so
the
submitter.
B
So
if
you
have
a
request,
you'll
submit
a
card
to
the
project
board,
with
a
thorough
description
of
the
proposed
change
and
then
at
the
next
contributes
dev
stats
meeting,
which
is
Thursdays
for
anybody.
Who's
interested
in
joining
all
new
proposals
will
be
discussed.
Then,
if
the
proposal
is
just
be
good,
the
card
will
be
moved
into
an
approved
comm
and
the
committee
will
assign
it
a
priority
level,
high
medium
or
low,
and
then,
if
the
committee
needs
additional
information,
you
judge
that
proposal.
I
will
follow
up
with
submitter
about
that.
B
If
the
proposal
is
rejected,
that
proposal
is
moved
to
the
rejected
column,
with
a
note
and
the
card
as
to
why
the
proposal
was
rejected
and
then,
if
any
proposals
are
approved,
I'll
convert
into
an
issue
and
sign
it.
So
that
is
the
current
thought
plan
we're
gonna,
try
and
implement
that
or
port
back
on
how
that
goes
in
about
an
hour
we're
going
to
be
going
through
some
more
dev
stats,
graphs
and
looking
at
definitions
and
seeing
if
we
need
them
and
doing
some
some
pairing.
B
F
So
if
you
look
at
the
F
stats,
you
will
notice
that
reports
that
primarily
Kemp
commits
are
going
lower
numbers
than
they've
had
in
the
past
retro
actively
we're
still
looking
for
there's,
definitely
some
place
or
some
places
where
we
are
majorly
double
counting
contributors,
and
we
don't
know
where
that
is
yet.
So
if
anybody
has
any
brilliant
ideas,
please
pick
up
on
dead
stats
war
on
contrib
x,.