►
From YouTube: Kubernetes SIG Contributor Experience 20171129
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
It'll
be
a
very
short
update.
I
swear
for
those
that
were
following,
along
with
the
mentoring
test.
Cohort
expectations
right
now
are
a
kickoff
for
the
test
cohort
the
week
after
cube
con,
we
did
have
a
sink
fall
out,
unfortunately,
due
to
most
of
the
folks
being
either
on
a
release,
team
or
cube
con
or
holidays,
and
things
like
that,
so
I've
been
busy
with
recruiting
another
sig,
which
is
now
stay
gaps
to
join
us
and
we
are
recruiting
the
mentees
again.
B
It's
predetermined
that
group
mentoring
cohort
that
will
be
going
from
member
status
to
review
our
status
in
the
organization.
The
box
are
actually
getting
uploaded
today,
github,
yet
a
transparency
and
that
will
be
located
in
the
community.
Repo
it'll
most
likely
be
under
community
slash,
mentoring
and
then
all
all
things
mentoring
will
be
under
there.
So
that's
going
to
include
docs
on
outreach
e.
B
B
It
was
very
similar
to
George's
use
their
office
hours,
except
contributors
came
on
who
are
interested
in
kind
of
beginning
their
journey,
and
we
had
I
think
it
was
a
total
of
four
to
five
questions,
mostly
from
the
same
individual,
but
they
were
all
very
good
questions.
Nonetheless,
Erin
and
a
couple
other
people
here
right
now
we're
on
the
call
probably
should
rename
it
from
contributor
office,
something
like
contributor,
onboarding
George
had
that
idea,
but
that's
about
it.
If
anybody
is
like
mentor
emotions.
Let
me
know.
A
Wonderful,
thank
you
so
much
Paris,
it's
a
dev,
I
think
you're
you're
up
next
next.
A
C
Just
those
in
agenda
so
guys
are
in
contradiction
to
what
we
talked
in
your
last
meeting.
You
know,
I
did
mention
about
the
triage
first
works
closely.
A
C
C
But
you
know
in
that
email.
I'm,
sorry,
you
know
not
proposing
right
now,
but
sort
of
you
know
to
just
discuss
with
everyone
right
to
create
some.
You
know
one
or
multiple
new
labels
towards
you
know
finding
the
closing
candidates
right
and
you
know,
I
part
of
a
condition
to
what
we
talked
last
week.
Air
and
I
know
one
of
the
action
item
I
had
was
on
the
dose
that
you
know
sort
of
showing
the
open
issues
there
right,
Percy
I
did
kill
an
issue.
C
C
You
know
so
two
things
right,
one
is
with
the
label.
We
can
display
the
close
candidate
for
the
seek.
You
know
last
we
talked
that
seeks,
has
always
sort
of
a
problem
or
a
bandwidth
limitation
right.
This
can
give
a
better
visibility
towards.
What's
what
are
the
you
know,
issues
out
there,
which
are
already
initially
triaged
by
somebody
and
that
can
be
closed
right
without
much
efforts
and
the
second
is
some
time
back.
C
You
know
a
couple
months
back,
we
talked
about
some
matrix
right
that
he
to
get
a
better
view
of
you
know
the
issues
we
are
running,
which
are
you
know,
dupes.
You
know
to
be
kids
for
I.
Having
like
a
question,
support
questions
right
or
are
issues
which
are
sort
of
you
know,
people
open
it
and
then
they
never
return
to
answer
questions
or
did
not
provide
information
which
is
required
to
recreate
two
different
issue.
C
So
I
mean
you
know,
those
are
the
two
purposes:
I've
been
thinking
with
the
new
label.
Again,
you
know
like
a
generic
label,
something
like
close
candidate
versus
you
know,
multiple
labels
towards
closing,
with
a
particular
reason.
What
I
per
wish
you
so
I
just
wanted
to
get
like
again.
You
know
to
put
this
under
discussion
and
see
if
this
makes
a
sense.
I
know.
Last
week
we
last
meeting,
we
also
talked
about
sending
you
know
cumulative
community,
but
before
that
I
thought
you
know.
E
A
F
This
also
works
for
pull
requests.
You
could
have
them
slash
close
and
then
next
to
that,
like
slash,
close,
duplicated,
slash,
close
whatever
the
bakken
automatically
label,
and
that's
that's
super
cool,
but
I
guess
like
why?
Wouldn't
he
just
like,
because
anybody
can
close
anybody
can
also
reopen.
So
generally
speaking,
one
helped
me
understand
the
negative
impact
of
allowing
somebody
to
just
slash
close
and
then
like
saying
why
they
closed
it
on
the
relation.
C
A
C
For
example,
and
one
of
the
things
we
are
you
know,
I'll
be
speaking
at
a
local
meet
up
tomorrow
in
Raleigh,
right
and
I'm
gonna
promote
this
triage
concept
with
some
other
things,
but
one
of
the
thing
I
know
Georgia,
George
and
I.
When
we
initially
talked-
and
you
know,
I
had
some
of
the
emails
right
was
triaging
can
be
an
easter
step
for
a
lot
of
new
folks
could
want
to
contribute
right
and
you
know
for
them.
C
They
do
not
remember
right,
you
know,
they're,
just
looking
the
issues
trying
to
put
their
comments,
their
findings
right
and
say:
hey,
you
know
what
I
cannot
really
week
read
or,
or
somebody
already
verified-
it's
already
been
fixed
right,
so
all
they
can
do
right
now
is
they
can
leave
a
comment
there
right?
Then
hey
I
already
work
on
it.
C
You
know
I
could
not
recreate
and
if
this
can
be
closed-
or
this
is
just
like
a
plain
question,
which
is
no
you
suggesting
that,
due
to
the
stack
or
floor,
you
know
someone
stack
several
fall
right,
for
example,
but
all
they
can
do
is
they
can
put
a
comment,
and
you
know
I
wrote
a
few
examples.
I
mean
I,
have
such
comments
and
many
issues
and-
and
you
know,
I
was
initially
asked,
for
example,
like
hey
help,
creating
reducing
the
issues
right
now,
if
I
mean
any
non
art
member.
C
But
if
not,
then
you
know
are
member
can
utilize.
Something
like
you
know,
close,
can
you
label
and
that
can
help
sig
member
right
if
they
want
a
sort
of
second
opinion.
So
those
are
the
two
things
I
thought
you
know
sort
of
will
be
very
helpful
and
then
then
measuring
right
at
the
end
of
the
day
or
month
or
end
of
the
release
cycle.
C
If
you
wanna
see
that
hey
we've
been
leading
with
this
number
of
numbers
of
issues
right
around
five
thousand
all
the
time,
forty
five
hundred
I
mean
how
many
of
them
are
just
plain
questions
or
in
the
duplicates,
and
you
know
that
kind
of
things
right,
basically
giving
the
better
idea
on
the
dashboard.
So
a
couple
different
things
I
mean
I
was
thinking.
F
Okay,
yeah,
you
do
this
me,
like
I,
my
gut
reaction.
Just
comes
from
the
places.
Do
you
know
how
many
hundreds
of
labels
we
already
have
like
introducing
or
seems
crazy,
but
I
I
get
I
get
your
point.
I
would
love
to
find
so
in
the
interest
of
like.
We
think
that
this
will
empower
and
encourage
more
people
to
triage
issues.
I
don't
think
we
did.
They
have
a
way
of
the
measure
who
is
actively
triaging
issues
today.
This
is
another
thing
that
could
be
added
to
desk.
F
That's
where,
like
right
now,
you
can
call
out
people
who,
like
slacks,
recruiter,
I,
think
there's
like
the
approvers,
histogram
and
I'm,
assuming
that
goes
by
people
who
use
slash
accrued,
it
seems
like
we
could
add.
We
can
ask
for
another
dashboard.
That's
like
people
who
use
certain
label
commands
anything
right
like
or
maybe
the
abstract
way
we
can
do
this
is
we
can
see
that
the
plot
command,
step
stats,
dashboard
shows
the
usage
of
box
commands
over
time
and.
F
C
Yep
and
and
I
mean
real
quick
again
with
the
light
agent
right.
I
totally
I
agree
err
on
that
right
now
we
don't
have
measure
or
matrix
towards
sort
of
recognizing
person.
Doing
triaging
right
and
I
mean
it's
a
you
know.
If
we
have
something
like
that,
you
know
that
can
actually
encourage
people
to
three.
That's
right,
because
they
can
actually,
you
know,
show
it
to
that
team.
Their
bosses
and
the
community
can
take
a
look
as
well
right
that
hate
these
guys.
C
F
C
A
Then
rounding
it
out
for
us
one
of
your:
do
you
want
to
talk
about
the
contributor
guide,
yeah
I,
just
hi,
everyone.
G
I
just
wanted
to
quickly
bring
to
everyone's
attention
that
there
is
a
new
contributor
guide
in
the
community.
Docs
and
I
know.
I
mentioned
this
in
the
channel
as
well,
but
you
know
with
Thanksgiving
and
koukin
I
think
I
just
want
to
you
know
not
let
it
fall
between
the
cracks.
This
is
a
thing
that
I
would
rely
on
everyone
to
kind
of
go
over
and
look
at
and
improve,
and
there
is
a
place
to
start,
and
there
also
is
an
umbrella
issue
and
I
can
need
to
post
with
them
in
the
chat.
H
A
H
If
so,
I
was
thinking
of
sitting
down,
maybe
did
Q
Khan
during
one
of
the
breaks
or
something
grabbing
a
table.
I
mean
going
through
all
the
checkboxes
and
figure
out
which
ones
were
missing
and
maybe
just
do
like
a
mass.
You
know,
George
will
take
these
five
items.
Someone
else
will
take
these
five
items,
starting
with
the
CLA
I.
Think
yeah.
B
D
H
B
G
A
G
F
Dressed
today,
but
I
guess
maybe
an
ask
for
our
next
two
questions.
Then
we'll
wait,
never
mind.
We're
not
meeting
here
in
coupon
about
the
meeting
after
coupon
I
would
hope
that
we
would
go
review
what
we
promised
for
1:9
and
see
how
we're
doing
of
those
promises.
I
fully
acknowledge
I'm
behind
on
whatever
I
promise
and.
H
F
H
H
A
A
Do
we
want
to
look
at
the
agenda
for
the
contributor
summit
and
see
if
we
hit
what
we
want
to
talk
about
there
and
then
tomorrow,
maybe
on
slack
I'll,
send
out
a
poll
for
whether
we
want
to
try
and
get
a
formal
slot
during
coupon?
If
that
doesn't
meet
our
needs
what's
happening
in
the
dev
summit,
I'll.