►
From YouTube: Kubernetes SIG Contributor Experience 20171105
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).
D
You
hear
me:
okay,
yeah
yeah,
so
you
know
a
few
months
back
when
we
created
the
triage
guideline.
You
know
we
will
talk
about
a
few
things,
and
this
is
what
the
thing
I
would
not
sort
of
prevention.
So
what's
happening,
I
I've
been.
You
know,
noticing
it
that
once
we,
you
know,
do
initial
triage
right
on
issues.
I
mean
our
goal
is
to
reduce
the
issues.
Lots
of
them
are
questions
and
some
of
them
could
not
be
recreated
some
of
them
already
fixed
whatnot.
D
D
You
know
and
and
all
these
issues
I'm
talking
you
know
they
have
a
cig
label.
So
apparently
you
know
the
sig
is
getting
notification.
When
someone
like
me,
add
a
comment
to
close
the
issue,
so
you
know
I'm
wondering
like
I
say
we
did
talk
a
little
bit
about
it
earlier
that
each
cig
should
have
a
sort
of
triage
representative
which
you
know.
Hopefully
we
can
see
see
you
know,
while
the
issue
three
yards,
that
hey,
can
you
please
close
it?
D
You
know
if
you
agree
with
it
right
and
like
I
said,
a
lot
of
issues
are
trivial
issues.
You
know
they
can
be
closed
by
a
member,
but
having
sig
representative
you,
you
know
who
is
for
the
triage
I
think
they'll
be
very
helpful,
something
we
should
have
and
and
with
that
you
know,
I
think
if
we
can
reach
out
to
all
the
cigs
and
ask
them
right
if
they
are
since,
like
they,
it's
not
already
there
right.
E
Yeah
so
I
think
one
thing
that
might
be
helpful
here
is
some
kind
of
dashboard
that
we
can
point
out.
That
shows
like
the
relative
open
issue,
count
for
every
single
cig.
E
That
dashboard
does
not
show
that
dashboard
just
shows
all
of
the
opened
and
closed
issues
over
some
rolling
time
period,
and
then
you
can
use
the
cig
filter
box
to
break
it
down
by
individual
sig.
But
if
you
really
want
to
get
people
competitive
or
if
you
want
to
do
some
public
bragging
or
shaming,
you
probably
want
to
be
able
to
show
a
graph
of
all
of
the
SIG's
side-by-side,
and
this
is
something
we
kind
of
tried
to
do
back.
When
we
first
mandated
that
every
issue
have
a
sig
label
attached
to
it.
E
We
were
using
a
dashboard
generated
by
Sappho
that
showed
all
of
the
issues
that
had
a
neat
sig
label
applied
to
it,
and
then
the
relative,
like
open
issues
in
PR,
I,
think
for
each
sick
and
I
would
really
request
that
somebody
other
than
me
file
an
issue
against
them
stats
so
that
it
doesn't
look
like
I'm,
the
only
person
who's
using
dem
stats
and
I'm
asking
for
customization
Florence.
Oh
it's
interesting
like
all
right.
E
Okay,
we're
sad
I
mean
like,
if
sort
of,
if
you
want
to
drive
the
issue,
triage
thing
go
for
it
like
file.
It
you'd
be
shocked
at
how
responsive
Lukas
is
to
actually
doing
things
based
on
those
issues
so
that
it
sounds
like
that
would
be
a
good
way
of
just
demonstrating
to
like.
You
could
totally
do
this
during
a
community
meeting
or,
however
you'd,
let's
send
an
email
to
kubernetes,
dev
and
just
be
like
hey,
look
at
this
dashboard
and
like
look
at
how
many
issues
have
been
opened
in
the
past.
E
I,
don't
know
how
long
and
see
how
they're
spread
across
SIG's
and
you'll
find
some
way
to
have
that
dead.
Excuse
me
have
that
dashboard
show
these
things
that
are
making
progress
like
you
know,
I'd
have
to
spend
some
time
thinking
about
what
metrics
and
what
that
dashboard
might
look
like,
but
again,
I
know
at
the
bare
minimum.
The
thing
we
used
to
use
was
a
dashboard
that
just
should
open
issues
by
all
said:
that's
a
pretty
easy
start.
D
Not
absolutely
I
think
I
will
I
will
look
at
the
deer
stats.
You
know
a
little
bit
more
and
see
if
we
can
add
something,
but
even
on
top
of
that
you
know
not
just
open
issues.
Right
I
mean
even
like
going
further
with
initial
triage.
It's
open
issues
that
can
be
closed.
Right,
like
it's
been,
you
know,
have
been
initially
triage.
It
been
sort
of
identified,
as
you
know,
do
as
a
do
as
a
question
right
as
something
which
the
initial
they
should
report
or
never
replied
to
a
question
right.
D
Those
issues
I
know
if
you
can
show
you
know
those
issues
that
are
sort
of
candidate.
To
close,
you
know
with
someone
who
can
close
it.
You
know
and
I
assume
somebody
from
sig
is
even
better.
You
know
better
to
close
it
right,
because
you
know
it's
also
saying
it
might
be
something
you
know
I
mean
even
if
it.
If
it's
closed,
you
know
in
some
cases
I
assume
you
know
in
the
wrong
way.
It
can
always
be
reopened
right,
but,
like
I
said
someone,
so
sick
should
be
helpful,
so
those
issues
I,
don't
know.
D
E
F
E
D
So
lot
of
issues
you
know
they
already
have
seed
label.
You
know
in
many
cases
it's
the
label
created
by
a
member
right
who
knows
I
hate
this
issue.
It
belongs
to
something
like
common
she's
like
sick
Network
right.
So
if
it
is
a
label,
I
think
someone
from
that
cig
light.
I
mean
you're,
irritating
sakes.
E
I,
it
seems
like
maybe
some
of
them
aren't
I
can
tell
you
that
stake
testing.
We
kind
of
don't
really
have
the
bandwidth
to
do
that
actively
across
kubernetes
kubernetes
were
a
lot
more
active.
Isn't
one
thing,
though,
that
we
have
direct
ownership
over,
but
so
the
next
thing
would
be
to
actually
use
one
of
the
gift
hub
teams
has
notified
us
a
sometimes
that's.
You
know
the
best
way
I
have
to
notify
a
group
of
people
or
let
them
know
that.
E
There's
something
happening
on
this
issue
and
then
yeah,
as
you
said
like
in
the
past,
sometimes
I
think
I
have
I,
have
closed
issues
and
been
like
hey
I,
don't
think
this
is
relevant
anymore
and
if
you
think
I'm
doing
the
wrong
thing,
you
please
reopen
it,
but
I
thought
like
the
question
you're
asking
is:
how
do
we
incent
the
other
SIG's
to
do
this.
D
Absolutely
and
I
mean
the
main
thing
I'm
looking
here
is
is
to
close
the
issues
which
should
be
closed.
You
know,
instead
of
sitting
there
right
I
mean
regardless
of
sig.
You
know,
honestly
that
and
that's
our
goal
right
to
reduce
number
of
open
issues.
You
know
to
get
a
better
understanding
of
what
kind
of
work
is
required,
because
many
times
we
just
go
with
the
numbers
right
and
if
you
think
the
hey,
these
numbers
can
be
reduced
and
somebody's
already
identifying
those
issues.
E
D
E
Mean
there
there
might
be
nothing
wrong
with
just
putting
it
together,
a
quick
email
to
kubernetes
day
or
something
and
saying
like
hey,
we've
noticed
here's
a
query
that
you
as
a
site
owner,
could
use
to
see
all
the
open
issues
that
are
assigned
to
you
and
a
couple
of
us
are
trying
to
help
out
with
triage
and
we're
noticing,
there's
some
issues
that
are
closed.
Here's
my
best
guess
for
how
to
get
in
contact
with
you
as
an
individual
cig.
So
I
like
try
and
get
you
to
close
the
issues.
Does
this
make
sense?
E
D
B
G
Yeah
sorry
I
was
just
eating
lunch
ahaha,
trying
to
sneak
in
there
yeah,
so
the
contributor
guy.
We
we
synced
up
with
a
developer
guide
folks,
there's
one
guy
who
just
started
and
Red
Hat
and
he's
gonna
be
working
on
it.
Unfortunately,
he
can't
really
commit
until
the
first
of
the
year,
cuz
Q,
cons,
kind
of
sneaking
up
on
everybody
and
I've
got
some
great
contributions
from
someone
in
Samsung
who's.
Helping
me
redo
the
table
of
contents
to
be
more
user
friendly.
So
there's
more
work
on
that
other
than
that.
G
You
know
if
still
open
for
contributors.
If
people
want
to
dive
in
and
stuff
I
can
help
walk
them
through
that
and
then
what
we'd
like
to
do
is
take
the
off
the
Wednesday's
when
we're
not
meeting
for
this
sig
to
have
sink
meetings
on
doing
the
contributor
and
developer
guide
stuff
I
figured
it'd
be
good
for
us
to
like
set
milestones
and
kind
of
get
us
going
in
a
regular
thing.
G
But
it's
not
gonna,
be
an
official
working
group
because
I'm
trying
to
avoid
making
a
working
group
so
I
will
I
don't
post
that
and
then,
as
far
as
the
contributor
cheat
sheet,
we
put
it
it's
in
the
community
repos
somewhere.
I
forgot
it
exactly,
but
I
put
it
where
Christoph
told
me
to,
and
it
seems
to
make
sense
and
I'll
go
ahead
and
update
that
link
and
that's
all
I
have
and.
H
+1
to
the
contributor
guide:
if
anybody
on
this
call
wants
to
help,
there's
plenty
of
help
and
the
good
news
is
that
most
of
the
copy
is
there,
it
just
needs
to
be
copypasta
together.
It
makes
it
needs
to
flow.
So
thanks
to
everybody,
that's
already
provided
opinions
and
help.
So
far,
it's
been
greatly
appreciated.
B
G
We
haven't
really
gotten
to
the
point
where
exciting
chunks
yet
like,
for
example,
Igor,
was
to
work
on
the
getting
started
section
and
he's
kind
of
working
on
a
set
of
slides
and
things
like
that
separately.
We
haven't
had
a
person
say:
hey
I,
want
to
I,
want
to
handle
this
and
then
go
do
that
quite
yet,
but
I
feel
like
the
table
of
contents
is
like
mostly
stable.
Now.
I've
also
have
not
had
as
much
time
keyboard
time
to
just
work
on
it.
I'm
hoping.
H
To
do
that
more
this
week,
a
lot
of
the
cleanup
has
just
been
taking
out
information
that
is
just
completely
inaccurate
or
404
links
and
stuff
like
that
means
stuff.
That's
just
completely
dead
copy
I
mean
that's
what
we've
been
doing,
that's
what
we
did
to
start
so
now
that
we're
at
this
point
of
okay,
those
of
this
copy
is
legit
or
many
people
on
this
call
have
commented
on
the
dock.
Like
hey
I,
don't
think
this
even
needs
to
be
in
a
contributor
guide
kind
of
kind
of
strategy.
H
E
Mentioning
it
thinking
like
hey
it's
low-hanging
fruit,
if
somebody
wants
to
do
it,
but
if
nobody
wants
to
take
it
on
I
will
but
I
want
to
have
any
yeah
contributing
a
DNR
like
this
makes
no
sense.
I
want
to
like
improve
the
situation,
can
actually
see
the
issue
where
it's
like
hey.
We
are
aware
of
this
and
we
are
addressing
it
and
if
you
want
to
help
out
here,
yeah.
G
I
A
So
I've
been
looking
at
the
Google
Doc
for
the
I've,
just
kind
of
been
cleaning
up
the
table
of
contents
in
a
way
that
feels
like
it
makes
more
sense
to
somebody
who's
like
totally
new
to
this
I'm
waiting
in
there
and
I'm
like
I'm.
Looking
for
information
I'm,
finding
it
for
leaks
down,
and
that's
weird
so
I
kind
of
want
to
know
so.
I
don't
know,
I
feel
like
a
lot
of
the
information.
A
Is
there
and
and
I
think,
as
Paris
mentioned,
a
lot
of
the
dead
links
have
been
cleaned
up
and
a
lot
of
the
out-of-date
information
has
been
kina
as
well.
So
once
I
found
all
those
pieces,
I
quit
successfully
submitted
PR
against
community,
at
least
and
and
I
just
sort
of
I,
just
I,
don't
know
I
feel
like
a
lot
of.
It
is
mostly
there.
So
it's
really
just
a
matter
of
puzzling
it
together.
A
So
I'm
a
little
bit
and
a
little
bit
curious
as
to
what
the
next
step
looks
like
I
really,
are
we
just
going
to
I,
don't
know
I.
The
main
thing
that
is
confusing
to
me
is
that
I'm,
looking
at
this
from
the
perspective
of
like
github
file
tree
and
things
will
be
linked
to
each
other
and
from
a
top
level,
and
then
you
can
go
hey
for
how
to
submit
a
PR
go
here.
A
H
For,
though,
for
the
website
we'll
need
way
less
than
55
pages
so
now
the
task
is:
how
can
we
use
the
information
that
we
have
in
a
very
concise
manner
to
fit
it
on
the
website
and
then
also
add
in
links
to
the
proper
community,
repo
Docs?
So
I
see
it?
It's
a
couple
different
parts
number
one
getting
the
information,
that's
in
community
repo
right
now
up
to
date
and
Sun
setting
some
of
the
docs
that
are
already
in
there
like,
for
instance,
there's
like
a
welcome
new
developer
guide
that
probably
should
be
sunsetted.
H
Now
that
we're
working
in
so
we'll
probably
transfer
to
just
a
cleaner
sheet
and
then
we'll
submit
that
against
the
website,
ER
and
then
the
docs
folks
will
do
their
will
do
their
magic
and
sparkles
and
and
throw
all
their
confetti
at
it.
At
least
that's
what
I'm,
hoping
for
and
the
end
counterpart
that
I
have
Andrew
Chen
and
that's
kind
of
what
he's
looking
for
too.
H
So
so
that's
why
I
see
parts
cleaning
up
the
community
repo
is
is
kind
of
the
first
and
foremost
and
then
okay
is
is
the
website
piece
where
we
have
this
25
to
35
pages
doc
me
right
now,
George's
done
wonderful
and
you
also
done
a
wonderful
job
with
like
consolidating
it
down,
because
we
had
originally
68
pages.
What
Eric
was
referring
to
so
now,
just
like
getting
that
down
into
a
much
concise
format
so
that
it
can
go
on
a
website
is
the
final
step.
So.
A
The
main
reason
that
it's
not
like
40
pages
right
now
is
because
I
literally
just
said
in
order
to
do
this,
follow
this
link
because
to
me
as
again
as
a
new
person,
I
really
like
seeing
here
are
the
fourth
or
five
big
topics,
then
a
top
level
and
then
follow
these
links.
So
you
know
like
a
choose-your-own-adventure
kind
of
thing,
except
we're
secretly
guiding
people
down
the
correct
links,
so
they
win
at
the
end
and
when
you
say
you
want
to
make
it
concise
for
the
website,
I
sort
of
would
love
it
to
be.
A
H
H
But
ya
know
you're
on
it,
I
mean
what
I
do.
Ideally,
it
would
just
be
a
couple
lines
or
bullets
of
texts
per
thing
and
then
ultimately,
a
link
that
would
link
to
the
appropriate
community
doc.
So
that's
why
I'm
saying
that
the
it's
better
that
we
start
with
the
community
repo,
correct
and
liquid
air
and
saying
make
that
the
contributing
MD
file
correct,
and
then
we
move
to
the
like
the
condensing
of
the
papers.
Down
to
the
pages.
The
pages
sounds
45
pages.
Yes,.
J
G
A
F
G
We
don't
really
have
like
a
like
strong
commitment
to
anything
that
exists
already
so
I
think
we
should
try
to
do
with
fresh
minds,
pretend
we're
new
contributors
and
then
just
make
something
for
people,
as
opposed
to
like
there
was
one
file.
I
was
like
I'm,
not
saving
this
I'm.
Just
this
one
will
obviously
be
deleted
at
some
point:
I'm,
so
I,
you
know,
I
think
we
have
the
freedom
to
make
it.
What
we
want
so
great
chop
away.
Why.
G
Right
so
I
would
I
was
thinking
that
all
like
you'd
have
the
table
of
contest
will
be
one
file
and
then
each
section
will
be
a
separate
file
in
github
and
that's
how
we
consume
the
guide
and
a
lot
of
people
will.
But
then
the
web
page
generates
those,
so
we
can
have
as
many
files
and
restructure.
However,
we
want
the
only
reason
we
did.
One
huge
Google
Doc
is
just.
G
A
A
G
G
J
G
J
E
Look,
it
doesn't
have
to
happen,
but
I've
just
asked
in
a
couple
different
forums
and
like
somewhere
here
I
have
this
hope
and
dream
that
everything
can
be
named
consistently
for
a
given
cig
and
I
kind
of
want
the
sake
valley,
a
file
in
community.
To
be
that
thing
so,
based
on
that
key
I
can
go,
I
can
expect
again
hub
team
to
be
named
a
certain
way.
Google
group
to
be
named
a
certain
way.
A
slack
channel
be
named
a
certain
way
and
this
cig
started
out
as
a
working
group.
E
So
the
google
group
is
named,
kubernetes
WD
contributes
and
I
would
I
was
wondering
how
people
felt
about
trying
to
rename
it
cig
contributor
experience
to
match
the
name
of
the
folder
in
kubernetes
community
and
the
kid
hook
label
and
all
that
stuff.
My
hesitancy
is
whether
or
not
just
outright
renaming
the
group
rate
links
to
previous
messages
when
it
was
called
WG
conserve,
X
I,
don't
know
if
it
would
break
references
to
the
old
email
address.
I
have
no
personal
experience,
renaming
Google
Groups
and
seeing
one
of
the
things
seamlessly
followed.
E
I
I
E
B
E
E
Okay,
next
topic
is
me
as
well:
let's
see
it's
def
sets,
so
basically
it
was
kind
of
what
I
was
saying
when
saw
death
was
mentioning
something
I
sometimes
feel
like
I
am
the
only
person
who
actively
tries
to
use
dev
stats
to
end?
Is
there
any
questions?
I
have
about
the
way
the
project
is
behaving
and
I
would
be
greatly
interested
to
hear
how
other
people
are
using
it
and
be
encourage
other
people
to
try
and
file
issues
against
the
dev
stats
repo,
because
pretty
much
every
time
I
see
Lucas
talk
about
it.
E
He
mentions
hey,
please
like
use
issues
to
talk
to
me.
Please
submit
pull
requests.
I
am
sitting
here,
oh
wait
actively
awaiting
your
feedback
and,
if
I
go
look
at
the
issues
like
right
now,
like
they're,
still
really
not
a
whole
lot
now,
I
think
this
thing
is
super
cool
and
if
I
had
more
free
time,
I
would
really
be
like
trying
to
poke
at
it
and
prod
at
it
and
explore
where
things
could
be
changed.
E
You
know
I
feel
some
of
the
dashboards
have
repository
groups
where
really
they
should
have
the
ability
to
call
out
specifically
specific
repositories.
Paris
and
I
were
talking
the
other
day
about
how
it'd
really
be
great,
oftentimes,
I.
Think
of
things
in
the
context
of
the
past
release
or
the
past
two
releases,
whereas
right
now
the
dashboard
is
like.
You
know
the
past
week
the
past
month
and
we
have
like
little
markers
for
those
releases,
but
we
don't
have
quick
ranges
for
that.
E
Apparently,
that
sort
of
on
a
feature
request
but,
like
generally
speaking,
if
I
have
a
question
for
like
what
are
people
doing
or
how
is
the
project
behaving
or
are
we
doing
better
or
worse
for
thing?
X
I
always
been
trying
to
like
start
with
a
dev
stats
dashboard
and
see
if
I
can
use
that.
To
answer
my
question
and
if
I
can't
like
what
would
the
ideal
dashboard
be
and
then
can
I
go
create
an
issue
for
that.
E
H
Yes,
I
have
been
poking
around
at
def
stats
as
Aaron
knows,
because
I
ping
him
all
the
time
for
the
most
little
things
and
he
wants
to
pull
his
hair
out
now
from
all
my
inquiries,
and
that's
totally
fine
I
understand
so
like
Morgan
also
mentioned
in
the
chat.
I
think
we
should
definitely
have.
We
got
how
to
use
dev
stats
class
because
my
like
advanced
statements,
kind
of
suck
and
my
sequel
skills
are
very
like
rusty
at
best.
H
So
in
the
end,
a
lot
of
what's
on
there
like
the
the
premade
charts
and
the
the
premade
graphs,
and
things
like
that
are
good,
but
I
kind
of
want
to
take
a
lot
of
that
stuff.
A
step
further
and
like
kind
of
like
either
related
to
a
release
or
related
to
a
certain
time
period.
That's
not
listed
in
dev
stats,
so
I
think
it
would
be
cool
if
it's
Lucas
right
his
first
name,
Aaron,
okay,
I,
think
it
would
be
cool.
H
Like
I'll
submit
an
issue
Lucas
to
see
if
he
would
be
cool
with,
like
the
notion
of
like
a
30
minute
premiere
of
how
to
use
this
and
get
what
you
need
out
of
it
and
if
not
like
what
you
should
come
to
me
about
issues
with
cetera
and
I,
think
maybe
we
can
have
it
advertised
that
too,
like
Zig
leaves
too
maybe
it's.
Maybe
people
have
just
been
quiet
because
they
look
at
it.
They're
intimidated,
I,
don't
know,
but
that's
that's
kind
of
my
two
cents.
G
G
We
were
way
more
active
than
we
were
life
cycle.
I
think
that
would
be
really
really
cool.
For
you
know
the
kind
of
show
work
where
people
are
doing
it.
I
do
want
to
talk.
I
had
a
planet
to
talk
to
Lucas
at
like
corner
him,
I
mean
we
can
do
this
together.
Aaron
like
like
how
you
mentioned
teaching
the
milestones
to
like
releases
I
feel
like
maybe
like
the
bug
I
filed,
for
it
was
like
way
too
complicated.
G
E
E
E
A
B
B
E
Yeah,
that
would
be
week,
that'd
be
great,
but
I
honestly
think,
like
whatever
we
show
at
this
meeting,
if
we're
like
yeah
that
looks
cool
just
like
sign
up
to
show
it
at
the
community
meeting.
If
there's
time,
because
there
has
been
time
lately
and
I-
think
we
just
continually
getting
it
in
front
of
people's
faces
and
showing
that
there
are
we're
learning
stuff
about
the
project
is
cool
yep.
G
And
I
have
a
semi
related
question
to
that.
Remember
how
I
think
it
was
two
weeks
ago
you
presented
that
the
amount
of
approvers
hasn't
really
grown
on
4.0
is
that
is
that
what
it
is
yeah
so
have
we
actually
like
told
this
to
like
sig
leads
and
like
like
I,
feel
like
if
we
told
more
people
about
that,
specifically,
we
can
kind
of
tell
them.
It
would
be
great
if
SIG's
would
try
to
get
one
or.
E
Know
my
plan,
for
that
is
to
continue
to
say
it
over
and
over
in
as
many
different
forums
and
ways
as
possible.
If
I
sit
here
and
say,
guess
what
guys
I
have
a
plan
for
how
to
do
this?
It's
not
going
to
work
because
I
don't
have
the
drive
plan
I'm
trying
to
demonstrate
hey
we're,
noticing
this
and
don't
we
collectively
agree.
This
is
kind
of
weird
and
odd,
so
I've
done
it
in
the
community
meeting
I'm
bringing
it
right
in
committee.
We've
talked
about
it
here.
E
E
One
of
the
one
of
the
things
that
we
were
discussing
during
state
testing-
and
maybe
I
mentioned
this
at
one
of
the
community-
is
like
right
now.
When
the
bot
suggests
an
approver,
it
tries
to
ultimately
suggest
whoever
has
the
power
to
approve
everything
all
at
once,
which
means
that
it's
going
to
end
up
hitting
the
same
seven
people
at
the
root
of
the
tree.
E
Burnett
is
repo,
and
then
it
will
often
do
this
because,
like
there's,
there's
a
bunch
of
changes
in
a
leaf
at
the
donors
file
and
there's
one
change
over
here
that
doesn't
have
an
owner's
file,
and
so
it
just
goes
well.
It
took
more
aggressively
drop
owners
files
and
all
the
leaves
and
prune
them
and
stuff.
We
would
make
life
better
for
ourselves,
so
something
I'm
personally
trying
to
lead
by
example,
is
right.
E
G
H
And
I
think
every
community
meeting
during
the
announcements
like
we
shouldn't
even
put
it
necessarily
on
me
like
on
you,
know
a
demo
or
anything
but
during
the
announcements
one
of
us
should
like
even
just
pull
up
a
chart
and
be
like
okay
and
if
you'll
say
like.
Oh,
that
chart
isn't
interesting
and
we
can
say
what
is
interesting.
You
know
I
can
kind
of
go
from
there.
No.
E
G
You
could
start
easy
with
just
saying:
hey:
here's
a
graph
showing
growth
and
approvers
yeah.
We
all
know
this
is
horrible.
Cube
Khan
is
coming
up
and
you're
all
gonna
have
a
lot
of
meetings
start
thinking
about
how
we
grow.
This
right,
like
you'll,
have
to
figure
it
out
ma'am
and
just
keeping
them
back
of
your
head,
that
we
need
to
start
thinking
about
mentorship
and
all
that
stuff,
and
if
you
want
to
get
involved,
more
Paris
is
working
on
this.
G
E
H
I
promise
it'll
be
quick,
so
the
deck
is
linked
in
our
notes.
The
deck
includes
link
to
mentor-mentee
guidelines
expectations.
Survey
results
are
in
the
back
from
the
survey
that
we
conducted
a
while
ago,
community
membership
doc,
which
is
the
ladder
to
some
people,
etc.
So,
please
feel
free
to
browse
comment
and
help.
There
is
a
Help
slide
at
the
very
end
that
I'm
completing
now,
but
the
most
areas
that
we
need
the
most
help
with
is
identifying
some
more
meat
and
potatoes
to
the
mentor-mentee
guidelines.
H
Ideally
we're
going
to
be
building
this
around
the
test
cohort.
You
know
as
we
go
as
we
iterate,
but
anything
that
you
can
think
of
from
a
foundational
perspective
that
we're
missing
in
either
category.
Please
definitely
reach
out
this
week,
I'm
locking
in
the
predetermined
test
cohort.
This
is
not
the
way
that
we're
going
to
do
it.
You
know
once
we've
once
we've
left
the
kind
of
test
phase,
but
just
it's
a
test
and
I
want
to
see.
H
If
group
mentoring
works
period
for
our
culture
we're
doing
a
predetermined
test,
meaning
the
mentors
are
already
locked
in.
We
have
this
week
we're
going
to
be
asking
certain
people
to
be
the
mentees.
We
are
going
to
do:
mentee,
I'm,
sorry,
member
reviewer,
meaning
if
the
ten
mentees
that
we
get
are
all
currently
members
and
they
all
would
like
to
go
to
reviewer
status.
The
mentors
are
three
of
them
and
they
each
represent
three
different
SIG's
working
groups
or
sub
projects.
H
We
actually
have
one
from
CCL,
say:
CLI,
one
from
Q,
the
ADM
and
one
from
one
from
I
forgot
she's.
My
language
cops,
so
that
kind
of
represents
a
working
group
of
sig
and
a
sub-project
to
see
if
it
would
work
and
in
any
of
those
settings,
so
the
mentees
will
be
kind
of
working
towards
reviewer
status
in
each
one
of
those.
Every
week
we'll
have
a
stand
up.
The
program
is
going
to
be
three
months.
The
stand
up
will
include
issue
grooming,
as
well
as
like
a
development
area
for
them.
H
H
Things
like
how
to
you
know
better
communicate
via
github
without
going
back
and
forth,
and
things
like
that
and
I'm
sure
she
can
talk
on
that
a
second.
But
if
anybody
has
any
questions,
concerns
comments
or
anything
mentoring
related,
please,
let
me
know
I
think
everybody
on
the
call
just
based
on
the
the
call
list
right
now
that
I'm
seeing
had
seen
the
deck
or
heard
one
of
my
mini
political
speeches.
K
Yes
and
a
few
other
tools
and
projects
that
are
on
github.
So
my
idea
is
basically,
it
was
kind
of
like
soft
skills
as
a
service,
but
adapting
that
40
meanness,
because
soft
skills
can
be
contributed.
Construed
in
ways
that
are
actually
like
underestimate
how
important
they
are
so
collaboration
thinking,
people,
building
teams
around
open
source
projects,
and
so
I
gave
her
a
couple
ideas
around
that
and
the
one
hour
workshop
she's
talking
about.
K
Is
we
she
emailed
the
three
pilots
for
the
program
this
pitch,
but
it's
basically
bringing
people
together
or
doing
it
one-on-one
to
talk
to
them
about
some
of
the
challenges
that
they
have,
especially
around
stress
when
they're
talking
to
contributors,
you
know
how
they
interact
with
the
community
to
see
if
they
have
any
issues,
bring
abrupt
or
not
being
mentorians
as
they
might
be
like.
How
could
we
help
them
get
better
and
that
idea
came
from
my
chat
with
Jason
I
had
around
the
same
time.
So
that's
where
I
come
from.
K
What
I
would
like
to
do
is
actually
to
work
with
people
one-on-one
or
in
small
groups,
to
help
them
kind
of
understand
their
patterns
and
stress
around
their
work
and
help
see
if
we
can
help
them
really
reflect
the
kinds
of
open
values
and
transparency
in
corporation.
They
probably
have
it's
just
in
a
crunch.
They
might
not
might
not
demonstrate,
because
there
are,
because
this
seemed
less
of
these
was
like
I'd
say
with.
K
K
You
yeah,
that's
that's
a
separate
thing
and
what
I
was
talking
to
the
Paris
and
Jase
about.
So
it's
like
a
compendium
of
the
collection
of
notes
and
then
so
I'm
I'm
in
a
hotel
right
now.
So
the
internet
is
a
little
slow.
K
So
that's
the
concept
for
this
particular
mentoring
program:
the
subpage.
There
is
this
idea
of
this
session,
around
handling,
stress
or
and
communicating
more
effectively,
and
then
that
could
be
part
of
a
longer
initiative
that
was
that
I
started
separate
from
from
this
environment.
It
was
just
an
idea
that
I
had
during
docker
con
about
a
month
ago,
but
it
all
kind
of
fits
together.