►
From YouTube: Contributor Experience (10/18/2017)
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
A
So
let's
go
ahead
and
get
started,
I
think
the
first
thing
yet
on
the
agenda
actually
is
Paris
and
the
contributor
a
ladder
and
mentoring
program
that
you're
working
on
I
know
I
sent
out
the
the
survey
to
our
team,
but
maybe
she
can
describe
it
a
little
bit
more
detail
and
talk
about
the
program
a
bit.
Yes,.
C
And
I
actually
wanted
to
do
the
survey.
It's
not
another
bullet
and
it's
completely
neglected
that
so
I
apologize,
so
first
things.
First
sig
Docs
actually
is
starting
the
personas.
If
folks
do
not
know
or
have
not
heard
about
that
on
the
call
really
quick
they're
going
to
be
taking
a
new
Doc's
approach
for
kubernetes
IO
and
having
the
individual
picking
user
persona.
C
Some
of
those
user
personas
include
things
like
platform,
development,
ecosystem,
developer
code,
contributor,
etc,
etc.
It's
kind
of
like
a
choose-your-own-adventure
which
is
really
cool,
especially
as
a
whole
way
of
doing
all
of
these
complex
Doc's
and
also
I'm,
starting
to
pilot
some
ideas,
around
group
mentoring
and
some
untraditional
mentoring
paths
as
a
way
to
help
our
contributor
funnel.
As
everybody
knows,
on
the
call.
C
We
have
this
like
mungus,
first
level
of
new
contributor
drive
by
contributor,
but
then
easily
small,
at
the
top,
with
owners
and
maintainer,
so
essentially
just
trying
to
help
help
that
Lake
in
the
middle.
So
we
decided
to
go
in
together
on
a
survey
which
we
have
about.
100
results
right
now
extremely
thoughtful
results
too,
which
is
awesome
for
for
us
to
do
once
we
do
kind
of
an
executive
summary.
C
It
has
to
do
with
things
like
what
part
of
the
process
is
that
exactly
broken
in
your
eyes
and
your
opinion,
lots
of
opinions,
which
is
good
because
it'll
help
us
identify
some
exact
holes
and
gaps
instead
of
this
general,
these
general
general
terms
that
we
hear
a
lot
like,
for
instance,
communication,
broken
I'm
sure
everybody
on
the
call
is
heard
that
at
some
point
it's
like
well.
What
about
the
communications,
Bergen
and
a
lot
of
these
thoughtful
comments
have
included
that
information.
C
So
I'll
do
an
executive
summary
in
a
few
days
with
that,
but
the
deal
is
we'd
really
like
to
get
to
150,
because
that
will
show
a
little
bit
of
a
sample
size
as
it
correlates
to
the
current
very
active
members
of
the
community,
so
I'll
post
that
in
there
in
a
second
but
then
very
quickly,
to
go
to
the
next
stage,
which
is
the
actual
mentoring
piece.
I
am
posting,
I
am
gonna
post
this
in
a
guide
right
now,
no
I
mean
in
the
agenda
of
what
I
once.
C
C
So
when
I
shared
with
you
is
super
raw.
So
I
apologize,
there's
tons
of
comments
on
this
next
in
the
next
session,
which
is
in
two
weeks,
I
plan
to
have
a
deck
together
to
present
on
something
a
little
bit
more
serious
and
then,
ideally,
hopefully
kick
off
a
pilot
at
some
point
in
november/december
and
not
to
rant
too
too
far
ahead.
But
again,
looking
at
the
idea
and
the
concept
of
group
mentoring
versus
one-on-one
mentoring,.
C
And
what
I
mean
by
that
is
everybody
on
the
call
is
really
familiar
with
standard
grassroots
one-on-one,
coaching
mentoring,
which
takes
time
and
that's
what
we
hear
all
the
time
from
people
who
say
they
don't
want
to
be
mentors
is
I.
Just
don't
have
the
time
right
now
so
group
mentoring
in
a
very
class
based
session,
where
people
will
graduate
into
these
roles.
They
think
is
a
really
good
response
for
us
and
I
did
start
what
a
workflow
slash
process
would
look
like
there,
and
that
is
on
the
dock,
that
I
shared
as
well
again.
C
So
I
have
been
largely
doing
inspiration
from
OpenStack.
They
have
an
awesome
upstream
Institute.
Also,
there
is
a
hold
on
one
second
I'm
scrolling
through
the
dock.
Right
now
on
the
back,
there's
research
last
people
to
contact.
That's
where
I've
gotten
a
lot
of
this
heavy
inspiration
from
like
exorcism
IO
has
a
really
cool
mentoring
program
as
well.
That
talks
about
this
group
mentoring,
I
also
were
when
I
was
living
in
Baltimore
City
non
open-source
project
related,
but
how
to
do
with
mentoring,
youth
in
Baltimore
City.
They
did
a
mentoring,
family
approach.
C
That
I
had
that's
stuck
with
me
for
a
lifetime
and
it
really
works
and
mentoring
might
be
the
way
to
go
here
to
again
to
help
alleviate
suspicion
and
constraints
that
we
have
here,
but
open,
open,
open
stack
with
the
upstream
Institute.
They
don't
necessarily
do
group
per
se,
but
they
have
classes
and
things
for
groups
take
those
classes
so
again,
modeling
off
of
all
of
this
kind
of
inspiration
into
what
would
work
for
kubernetes
and
what
would
work
for
us
so.
A
Just
to
contrast
with
some
of
the
existing
efforts
that
are
out
there,
I
think
George
was
working
on.
George
is
working
on
kubernetes
office
hours,
that's
more
directed,
though
at
people
using
kubernetes
is
that
correct-
and
this
is
going
to
be
very
similar,
maybe
with
more
targeted
courses,
but
our
classes
are
topics,
people
writing
and
contributing
to
the
project.
Correct.
C
So
that's
where
the
and,
like
I
said
next,
our
next
session
I'll
put
together
a
deck,
so
we
can
go
through
a
lot
of
these
details
and
I'm
ironing
out,
and
so
then
you
know
we
can
definitely
get
some
detailed
feedback
there,
but
then
also
long
term
goals
would
be
for
us
to
scale
those
programs
in
multiple
detour
stories.
I
mean
I'm
just
using
the
user
story.
Right
now
that
is
I'm
a
man
I'm
a
currently
a
member
and
I'd.
C
Like
you
perceived
the
ladder,
other
user
stories
are
hi
I'm
a
fresh
contributor
I
have
no
idea
where
to
start
the
other
users,
Soria
I
have
done
one
contribution
and
I'd
like
to
become
a
member.
Oh,
we
can
probably
talk
about
nine
different
user
stories,
but
this
is
just
very,
very,
very
focused
on
the
initial
problems,
which
again
are
communication
and
things
that
have
been
brought
up
in
the
survey
that
I'll
do
the
executive
summary
on
and.
C
Definitely
and
I'll
have
that
in
my
deck,
I
mean
the
the
mentors
I
mean,
especially
you
serve
batches
of
mentors.
They
have
to
be
on
the
contributor
ladder.
Currently
I
mean
we
don't.
We
can't
have
like
a
new
contributor
mentoring,
someone
that's
going
to
reviewer
state,
so
these
essentially,
my
idea
is
that
our
current
committee,
as
well
as
owners
and
maintain
errs,
would
be
nominating
at
least
20
people.
That
would
be
mentoring
and,
of
course,
these
people
would
have
to
volunteer.
This
is
not
you
know
we're
not
looking
for
mentor.
C
You
know
we're
not
looking
for
forced
mentors
here,
we're
looking
for
people
who
want
to,
but
also
people
who
are,
you
know
and
then
kind
of
like
a
nominated
fashion,
because
people
trust
them
already
I.
Think
building
trust
within
this
community
of
mentor,
I
mean
of
owners,
maintained,
errs,
approvers,
etc,
is
probably
one
of
our
hardest
challenges,
so
it
would
be
great
to
get
their
buy-in
here
of
a
is
this
program
going
to
work
for
them
and
and
be
who
do
they
do?
C
They
think
should
be
leading
this
from
a
mentor
perspective,
but
I
mean
long-term
goal.
It
like
I
said,
is
to
have
a
multi-tiered
plan
here
and
that
would
include
things
like
upstream
office
hours,
similar
to
what
George
is
doing,
but
it
from
a
different
from
kind
of
like
a
lenz,
contributor
workshops
and
things
like
that.
Like
different
ways
of
viewing
mentoring
that
aren't
necessarily
mentoring.
C
E
C
That's
really
focused
on
new
contributors,
so
but
yes,
IMT
I'm,
actually
taking
a
lot
of
what
they
also
do
on
the
best
practice
side
for
mentors,
meaning
the
actual
press.
The
actual
process
and
engagement
all
said
mentors
I
have
been
talking
to
Josh
Simmons
on
the
Google
side
and
also
Nikita
I'm,
not
sure
if
she's
on
the
call.
But
Nikita
is
one
of
our
former
google
Summer
of
Code
interns
who
was
working
on
kubernetes.
So
she
does
have
that
insight
as
well
and
she's,
helping
me
with
actual
pieces
of
their
mentorship
hi.
B
A
C
Tba
on
a
lot
of
that
I'm
working
today
and
tomorrow
on
this
pretty
much
solely
and
next
session,
with
next
session
I
plan
to
have
much
more
of
like
what
we
need
help
with
and
where
we
need
help
on
the
actual.
Actually,
no,
let
me
let
me
take
a
step
back
on
the
doctors,
a
requirement,
slash
questions,
process
needed
tab.
If
you
will
on
the
spreadsheet
and
some
of
that
stuff
I
actually
do
need
some
help
with,
especially
like
doc
creation
updates
needed
for
current
docs.
C
F
I
feel
I
feel
like
if
this
covers,
like
kind
of
the
people,
have
been
around
a
while
and
I've
kind
of
got
the
users
handled
with
office
hours,
and
then
we
find
a
place
for
new
contributors.
Those
are
three
areas
or
or
we
could
really
make
a
difference
other
than
it
taking
a
lot
of
effort
right
like
you
cannot
like.
You
almost
have
to
do
this
full-time,
while
I
do
users
full-time
right
totally.
C
C
So
definitely
if
anybody
wants
to
help
ping
me
offline
and
I
can
get
you
plugged
in
somewhere
and
re
pilots.
I
would
definitely
like
to
run
that
by
a
marketing
professional
but
I'm
on
I'm
bored
I'm
on
board,
with
it
I'm
on
board.
So
no
I'm,
not
the
black
or
whatsoever
I.
Think
I
definitely
want
to
run
that
by
a
working
professional,
because
we
should
do
a
full
marketing
blast
on
something.
That's
cool
tugboat,
thanks
Josh.
E
C
Debian
is
known
for
having
good
docks
for
upstream,
but
if
anybody
on
the
call
wants
to
help
with
some
of
this
research,
we're
just
literally
line
by
lining
it
to
see
where
our
where
our
holes
are
and
where
we
have
room
for
growth
and
then
making
either
new
docks
against
that
or
updating
the
docks
that
we
currently
have.
Some
of
the
docks
that
we
currently
have
have
fluorophores
in
them.
C
So
just
making
sure
that
all
this
is
a
very
smooth
process
for
the
contributor
and
then
ultimately
again
gaining
it
back
on
kubernetes
IO,
which,
where
it
should
be
housed
with
the
rest
of
the
documentation
and
not
necessarily
embedded
within
github.
But
if
anybody
on
the
call
wants
to
help
with
some
of
that
research.
It's
definitely
well
needed.
I'm,
actually
going
to
put
in
the
analysis,
spread
that
I
have
right
now
in
the
dock.
Yeah.
C
Yeah
and
George
did
a
wonderful
job
on
the
OpenStack
keys,
since
he,
since
he's
very,
it
has
been
very
close
with
those
docks,
so
he
already
knew.
But
if
there's
anybody
on
the
call
that
is
very
familiar
with
the
nodejs
docks
as
well
as
debian
or
another
project
that
you
think
has
superior
upstream
contributor
docks,
then
we
can
do
that
as
well.
So.
A
I
just
want
to
mention
so
that
we
don't
have
too
many
duplicate
efforts.
I
think
Paul
Morey
from
Red
Hat,
maybe
also
was
working
on
something
similar.
He
opened
up
an
issue
a
few
months
ago
about
contributing
kubernetes
and
making
sure
that
people
are
clear
on
the
conventions
and
just
a
general
guide.
A
C
We
learn
if
that
is
there's
a
ton
of
discussion
if
everybody
wants
to
read
that
issue.
But
a
lot
of
what
he's
talking
about
is
going
into
a
developer's
guide,
I'm
working
on
more
be
contributor
guide,
which
the
developer
guide
is
a
part
of
and
Paul
and
also
Ryan
I,
can't
remember:
Ryan,
spread,
name
I'm.
C
Sorry,
I
was
off
my
head,
I'll
look
Brian
from
Red
Hat
as
well
they're
going
leader
Vernon
you
thank
you
they're,
going
to
be
working
very
heavily
on
the
developer
guide
piece,
which
has
a
lot
to
do
the
API
conventions
and
and
which
would
also
include
how
to
build
on
top
of
kubernetes
and
whereas
my
concern
is
mostly
with
upstream.
So
that's
how
we're
kind
of
splitting
up
this
work
is
sort
of
upstream
and
then
dev
guide,
so
contributor,
guide
and
deb
guide,
but
dev
guide
will
obviously
be
also
nested.
Within
this
contributor
guide.
B
C
A
A
H
A
That
was
convenient,
I,
think
it's
tools
like
that
are
things
that
we
are
going
to
want
to
include
in
that
make
sure
that
we
have
included
in
the
the
contributor
guides
I.
C
C
On
that
same
on
that
same
tip
with
sig's
and
contributing
one
of
the
things
I
that
I
need
to
reach
out
to
all
save
leads
for,
especially
as
part
of
this
mentoring
piece
is
that
all
SIG's
should
have
a
contributing
MD
file
in
the
repo
right
now
we
only
have
six
CLI
and
also
multi
cluster
that
have
contributor
guides.
You
know
just
very
basic
like
when
our
meeting
is
what
we
do,
why
we
do
it
how
to
actually
get
started.
C
For
instance,
I
know
some
of
the
SIG's
have
different
upper
amps
and
different
guides
and
different
instructions
on
how
to
contribute
and
or
and/or
wide,
why
to
contribute.
So
it's
mandatory,
though,
once
we
kick
off
this
mentoring
piece
that
every
seek
has
one
of
those
so
I'm,
trying
to
also
figure
out
how
to
get
everything
on
board,
with
with
doing
that
and,
of
course,
using
the
correct
labels,
which
I'm
sure
will
talk
about
in
a
second.
But
that's
definitely
a
piece
that
we
need
to
drive.
C
F
H
I
think
Phil
started
and
he
started
6
CLI
and
it's
a
guide,
but
as
far
as
requiring
all
states
to
have
a
thing
there
there's
a
60
ml
file
where
we
sort
of
tried
to
enforce
it
at
minimum
that
all
of
the
read
knees
for
eat
all
of
the
six
are
generated
by
this
file,
and
it
includes
like
here
the
cichlids.
What's
your
weekly
meeting,
what's
your
slack
channel
where's
your
agenda,
all
that
stuff
and
say
I,
think,
what's
your
what's
your
purpose?
C
F
H
Speaking
of
contributing
MD
personally,
a
good
first
step
might
be
to
refresh
the
contributing
that
MD
file
in
the
main
content
repo,
it's
pretty
sparse
and
links
to
you
confusing,
out-of-date
stuff,
so
I
would
make
sure
if
we're
building
an
on-ramp
that
we
we
would
start
there
before.
We
because
like
to
put
contributing
MD
files
in
all
the
sig
directories
assumes
that
people
know
what
a
Sikh
is
and
why
they
should
look
at
this
particular
Sigma,
since
that
particular
thing.
C
I'll
link
there
to
it.
The
analysis
guide
on
one
of
the
tabs
has
all
of
the
locations
of
any
where
we
talked
about
new
contributors.
So
you'll
see
that
it's
a
it's
a
lengthy
list
that
we
have
to
update
and
or
sunset
some
of
that
stuff.
So
I'll
link
that
as
soon
as
I
get
out
of
this
google
drive
hell
right
now:
it'll,
probably
45
tabs
open,
oh
yeah,.
H
H
H
F
C
A
A
H
I,
don't
necessarily
measures
value
right,
but
if
we
are,
if
our
contributor
ladder,
if
mentorship
is
succeeding,
we
would
expect
this
graph
to
go
up
into
the
right
in
the
same
way
that
we
expect
the
number
of
reviewers
to
go
up
into
the
right.
Sorry,
I'm
doing
it,
though
it's
weird
there
we
go
up
and
to
the
right,
yeah
you're
raising
your
hand.
Oh.
G
Thanks
Evan
thanks
for
noticing,
yeah
or
just
just
an
observation,
you
know
the
values,
how
we
measure
it
right,
son
you
mentioned,
and
that
LG
TM
right
the
label
in
a
PR
and
then
approve
label
right
now,
I
noticed
that
you
know
there
are
peers
with
you
know:
multiple
has
DTM
and
there
happens
in
many
PRS,
because
you
know
somebody
say
LG
TM
and
then
you
know,
for
whatever
reason:
the
the
taste
Fred's
right.
You
know
some
formatting
issues
sometime.
G
H
Don't
know
so,
if
you
care
deeply
about
that,
I
would
encourage
you
to
go.
Look
at
the
actual
queries
that
are
driving
these
and
then,
if
they
look
like
they're,
generating
false
or
buggy
data
that
we
file
issues
against
the
tha
TV
repo,
because
I
mean
that's
something.
I
just
would
like
to
do.
But
I
just
don't
know
if
I'm
gonna
have
the
bandwidth
to
get
it,
but
I
do
think
like
inherently
they
there's,
probably
bugs
and
how
the
data
is
collected.
There's
probably
miss
counseling
can
probably
double
counting.
G
H
In
a
/
approve
also
be
counted
as
an
LG
TM.
Should
an
LG
TM
Catherine's
improve
I'm,
not
sure
just
like,
based
on
the
based
on
these
graphs
right
now,
anyway,
it
looks
like
the
number
of
approvers
is
not
going
up
into
the
right,
so
we're
going
to
do
it
to
the
left
for
me,
yeah,
okay,
so
the
other
interesting
graph
for
me
anyway.
H
This
is
the
time
before
any
comment
activity
from
somebody
who
is
not
an
author
again
I'm,
not
sure
this
is
for
issues
and
PR
is
just
issues
just
PRS
I,
don't
know
if
this
includes
or
excludes
bot
activity.
So
those
would
all
be
good
things
to
question
for
the
fidelity
of
it
of
this
data.
But
what
I
find
interesting
is
so
the
blue
line
here
is
15
percentile
median
and
80
percentile
and
they're
all
relatively
speaking,
kind
of
staying
saying
they
are
also
not
trending
in
I
hope
to
be
a
downward
Direction
right.
H
So
in
the
15th
percentile
case,
you're
likely
to
get
a
response
on
your
issue
or
PR
in
less
than
an
hour,
but
in
the
median
case,
it's
somewhere
between
8
to
16
hours
and
then
85th
percentile
case
it's
somewhere
in
the
five
days
to
three
weeks,
rage.
Whatever
we
could
do
to
improve
time.
The
first
activity
certainly
seems
like
it
would
help
in
in
all
of
the
cases.
Okay,
one
other
graph,
if
I
can
find
it
here,
it's
not
open
to
merge.
H
All
right,
I'll
find
the
graph
later,
but
essentially
there's
a
graph
that
sort
of
shows
a
time
from
PR
open
to
Peter,
LG
team's
time
from
LG
team's
time
approved
and
time
approved
to
time
lurched.
Maybe
this
and
this
graph
really
clearly
shows
I'm
just
not
going
to
find
it
basically
the
time
for
somebody
to
actually.
First
look
at
a
PR
is
the
bulk
of
the
reason
a
PR
stays
open
and
does
not
get
merged.
H
H
That
would
really
help
us
win
through
things
and
then,
finally,
to
Garrett
and
Quinton's
point
about
companies
attempting
to
game
things
right,
I'm
wondering
if
people
are
looking
at
dashboards
like
this,
the
company
stats,
which
shows
like
how
how
many
active
authors
are
there
per
company
right.
So
what
username
corresponds
to
what
company?
Here,
that's
what
the
get
DM
repository
is
all
about.
There
was
one
that
I
found
was
really
interesting.
H
Maybe
it's
companies,
velocity,
yeah,
I,
think
it's
this
one
companies
velocity
I,
find
to
be
the
most
interesting
from
measuring
whether
or
not
companies
as
a
whole
are
trying
to
do
meaningful
things.
If
you
want
to
look
at
whether
or
not
people
are
gaming,
the
system
so
to
speak,
you
might
want
to
check
this
one
out,
because
this
shows
company
activity
and
it
breaks
it
down,
not
just
by
pull
requests
right.
It
also
shows
distinct
authors
of
either
issues
or
pull
requests.
It
shows
whether
or
not
companies
are
filing
issues.
H
Do
they
care
enough
about
kubernetes
to
actively
be
engaged
in
filing
issues?
Do
they
care
enough
about
humanities
to
be
creating
pull
requests?
Okay,
maybe
this
is
the
one
that
can
easily
be
gained
commits,
maybe
that's
easily
gained.
If
you
make
a
lot
of
tiny
commits,
are
they
actively
commenting
on
issues
I'm
really
interested
in
in
this
one
and
how
we
can
maybe
go
from
this
to
to
some
kind
of
metric
that
shows,
like
our
company
is
actively
involved
in
triaging
issues.
Cuz
a
lot
of
non
code.
H
Oriented
work
can
be
like
shepherding
the
discussion,
steering
the
discussion
realizing
this
problems
been
solved
over
here,
appropriately
applying
the
right
label
to
get
it
to
the
appropriate
stake,
and
that's
all
super
valuable
work
that,
like
our
contributor
ladder
right
now,
doesn't
so
much
measure
as
it
talks
about
owners
and
code
and
PRS
right.
But
these
are
the
sorts
of
metrics.
We
can
start
to
use
to
to
encourage
that
behavior
and
so
to
the
next
point
on
the
agenda.
I'll
stop
sharing
them.
H
They've
done
for
kubernetes,
you
know:
what's
their
activity
been
like
that?
Does
this
put
them
beyond
a
certain
threshold
where
they
look
like
a
they're
really
engaged
in
interested
in
kubernetes?
Should
we
reach
out
to
them-
and
you
know,
see
and
acknowledge
that
reward
them
and
then
include
their
mentorship?
So
ok
I'm
pouring
to
Paris
and
I've
done
ranting
now
yeah.
A
I
totally
agree
Aaron.
That
makes
a
lot
of
sense,
especially
the
suggestions.
You
have
around
non
code
contributions,
a
lot
of
the
incentives
and
discussions
around
PRS
created
lines
of
code,
written
lines
of
code
modified
things
that
are
super
beneficial,
that
pay
down
technical
debt
are
equally,
if
not
more
important,
with
the
project.
As
far
as
the
tool
that
you
mentioned
for
identifying
contributors
early,
it
exists
right
now.
The
Summer
of
Code
student
that
someone
mentioned
earlier
Nikita
had
put
it
together.
I
think
I'd
seen
it
before
and
I.
A
Read
it
and
looks
pretty
great,
though
the
problem
is,
is
it's
it's
a
pull
based
mechanism,
so
I
need
your
github
ID
already
and
I
need
to
know
to
look
and
then
I
need
to
know
what
to
look
for.
I
would
love
something
that
had
kind
of
alerting
and
monitoring
that
looked
at
people
contributing
to
the
project
used
her
tool
kind
of
as
the
mechanism
for
getting
their
stats
and
then
I,
don't
know,
send
an
email
to
contribute
or
to
a
few
leads
or
something
saying
hey.
A
F
B
A
H
Can
turn
a
new
button
yeah?
H
We
were
also
looking
at
implementing
our
own
Prometheus
metrics
to
sort
of
collect
this
as
well.
One
of
the
things
I'm
interested
in
is
it
seems
like
this
is
probably
not
updated.
H
Super
rapidly
I'm
gonna
see
if
I
can
get
some
clarity
on
what
the
update
cycle
is
because
I
think
the
github
event
archive
is
only
updated,
like
maybe
daily
something
like
that
or
possibly
hourly.
But
from
our
perspective,
we're
wondering
this
is
this
granular
enough.
This
seems
like
brand-new
owner
for
reporting,
probably
not
granular
enough
for
alerting
I
still
haven't
found
that
graph
I'm
talking
about,
but
I
will
link
it
in
chat
might
find
it.
A
Alright,
let's
see
next
on
the
agenda
was
sinking
labels.
I
just
want
a
quick
update
on
that.
I've
looked
at
the
tool
tools,
merged
intestine
for
I've,
read
it
a
few
times
it
works,
I
rolled
it
out
to
test
infra
and
community
manually
I.
Think
the
the
clusters
for
munch,
github
and
prowl,
which
is
where
I
expect
I'd,
want
to
run.
This
tool
are
both
on
one
point:
seven
clusters
and
I'm
waiting
for
them
to
be
updated
to
one
point:
eight,
because
this
is
a
regularly
occurring
job.
A
Just
a
quick
and
cron
jobs
come
out
with
one
point:
eight,
that's
the
reason
for
waiting
for
one
point:
eight
just
refreshed:
this
is
the
work
that
Aaron
had
done.
I
think
you
curated
manually
curated,
the
list
of
labels
that
are
gonna
be
propagated
across
all
repos
in
New
York,
and
this
tool
will
make
sure
that
they
are
synchronized.
A
And
so,
if
we
get
a
new
cig,
we
add
that
cig
label
in
one
place
and
every
repo
gets
that
cig
level,
and
it
makes
sense
to
some
extent
for
to
have
this
kind
of
consistency
across
the
project.
This
way,
when
you're
in
any
of
the
repos,
you
kind
of
get
a
similar
experience
that
it's
all
part
of
one
organization,
so
that's
what's
going
on
there.
A
I
would
look
for
that
in
the
next
couple
weeks,
I'll
follow
up
and
send
an
email
out
when
it's
running
I
sent
an
email
out
to
Josh
I
know
your
feedback
was
to
get
buy-in
from
sig
leads
I
didn't
have
anyone
reach
out
to
me
directly,
but
I
mentioned
the
list
of
labels,
as
well
as
the
intention
to
run
this
out
roll
this
out
I'll.
Send
it
out
one
more
time
before
you
actually
do
the
rollout
to
see
if
anyone
has
any
of
last-minute
thoughts
on
her
suggestions.
There.
H
Yeah
and
credit,
where
credit's
due
Lucas,
the
guy,
who
wrote
that
fence
all
the
fancy
graphs,
that
I
was
just
showing
he
wrote
the
label
tool
as
well.
I
just
looked
through
the
list
of
labels,
and
my
understanding
is
this
is
additive
only
it's
not
subtractive,
so
people
can
still
manually
add
their
own
labels
to
their
own
pet
repositories
if
they
so
choose.
But
this
is
going
to
enforce
state
labels,
three
kind
labels
and
priority
labels
across
all
Rico's.
H
A
H
F
I
did
I
just
wanted
to
a
link
here
because
he
doesn't
make
some
valid
points
on
pain
points.
I,
don't
quite
agree
with
his
proposed
solution,
but
I
figured
I
would
start
a
dialogue,
make
sure
people
are
seeing
it
feels
like
if
we
did
a
better
job,
I
think
integrating
things
at
the
top-level
website.
It
would
address
a
lot
of
these
issues,
but
I
just
wanted
to
make
sure
that
people
were
aware
of.
Some
of
my
people
are
having
I
also.
C
Want
to
make
a
comment
that
I
think
with
everything
that
we've
just
discussed
in
the
last
40
minutes,
that
a
lot
of
his
concerns
are
going
to
be
alleviated
with
better
community
page
on
kubernetes
I.
Oh,
that's,
more
robust
and
a
better
contributor
guide
on
kubernetes
I/o,
where
we
just
have
kubernetes
io
as
a
central
point
for
a
lot
of
things
and
a
lot
of
hot
links
instead
of
using
github
as
a
way
for
people
to
comb.
C
H
Yeah
there's
a
fair
amount
of
gardening,
and
that
could
happen
so
I
think,
like
our
efforts
to
create
a
brand
new
program,
means
we're
making
a
new
space
and
we're
gonna
populate
it
and
we're
gonna
say
that's
the
authoritative
space.
This
isn't
the
first
time
we've
tried
to
do
this.
You've
just
always
tried
to
do
it
in
a
new
markdown
file
and
github
in
this
subfolder
of
this
repo
over
here.
H
What
we
tend
to
not
to
the
beste
as
a
community
is
act
with
the
authority
to
say
and
we're
getting
rid
of
the
old
stuff
for
fear
that
somebody
might
care
about
the
old
stuff,
and
so
we
left
behind
this
trail
of
detritus
that,
like
nobody
knows
whether
it's
valid
or
not
and
I,
think
the
the
contributing
about
anything
linking
to
the
wrong
pull
request
thing.
If
you
can
point
me
to
a
single
page,
that
cogently
explains
all
the
stuff
for
pull
requests
and
communities.
H
Don't
I,
don't
really
want
to
go
the
OpenStack
route
of
saying
that
kubernetes
is
so
unique
and
different
that
we're
going
to
create
all
of
our
own
project
you
for
structure
and
we're
not
going
to
rely
on
third-party
services
that
do
certain
aspects
really.
Well,
we
just
kind
of
don't
have
the
staff
for
that
if
we
as
a
project
grow
to
the
point
where
we
do
have
the
staff
to
support
that
great
one
example
where
we're
there
right
now
is.
H
There
is
no
third
party
CI
service
that
can
handle
the
volume
of
traffic
and
tests
that
we
run
ergo.
We
have
our
own
CI
solution
that
we
have
a
team
of
people,
maintaining
we're
not,
but
we
don't
have
the
staff
to
do
that
for
each
and
everything
I'm
glad
that
it
works
for
Drupal.
Truly
we're
just
not
there
yet.
F
Yeah,
it
kind
of
leaves
out
a
lot
of
our
scale
issues
you
know,
like
I,
went
through
the
Drupal
site
and
thought
you
know
there's
no
way.
This
could
work
for
us.
There's
only
this
work
for
us,
but
I
just
wanted
to
get
eyeballs
on
it
because
he's
a
contributor
already
and
I
figured
you
know
he
would
know
the
pain,
and
maybe
we
can
approach
him
a
cute
con
or
something
and
get
more
actionable
feedback.
I
guess
it's!
It's
a
lot
of.
H
For
what
it's
worth
like,
it's
a
lot
of
pain,
I,
hear
in
areas
surrounding
kubernetes
as
well,
not
just
kubernetes
itself.
So
like
one
area
that
Matt
Farina
is
trying
to
improve
as
the
contributor
experience
around
charts
and
the
applications
that
are
built
on
top
of
kubernetes
and
I.
Think
Matt
butcher
knows
a
little
bit
about
that.
C
C
Yes,
the
CLI
link
is
in
there,
so
fill
with
rock
is
going
to
be
hosting
an
intern
for
outreach
e.
The
outreach
e
guidelines
are
on
that
link.
It's
pretty
much
someone
that's
getting
paid
by
CN
CF
as
a
stipend
to
do
work
on
our
behalf
as
an
intern
capacity.
It's
mostly
creating
some
commands
and
another
goal
related
tasks.
C
C
So
the
next
one
will
kick
off
and
I
think
it's
like
March
April
of
next
year,
so
hopefully,
next
year
we
can
get
some
more
interest
from
other
SIG's
and
maybe
even
people
outside
of
kubernetes
kubernetes
core
that
might
be
interested
in
taking
a
outreach
intern.
The
only
deal
is
it
is
paid
for
ultimately
by
the
CN
CF
and
we
would
have
to
get
approval
from
them.
H
F
C
H
H
I,
wouldn't
I
would
ask
that
if
you
signed
up
for
a
thing
to
review
whether
or
not
you
are
aware
that
you're
signed
up
for
thing
and
possibly
if
there's
like
a
github
issue
that
should
be
tracking
that
someplace,
adding
links
to
github
issues
always
helps
to
be
able
to
check
status
or
like
updating
a
stock
like
crossing
stuff
off
gotten
it
done
which
I
guarantee
you
had
mentioned
something
about
waiting
for
the
testing
for
cluster
to
upgrade
to
180.
You
have
an
issue
open
for
that.
No.
H
Just
like
I'm
trying
to
get
better
about
having
us
open
issues
for
stuff
that
we're
forecasting.
So
even
if
it's
not
something
that
has
to
get
done
today,
just
knowing
that
we
have
it
on
our
plate,
so
like
the
docs
that
get
kubernetes
docking
hub,
do
repo
being
renamed
to
website
right.
That's
something
that,
like
I,
think
our
munchers
will
just
transparently
support,
because
github
today
API
is
awesome
and
transparently
redirects
readings,
but
will
want
to
follow
that.