►
From YouTube: SIG Contributor Experience 20180207
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
I
mean
we
really
need
a
product
owner
for
dev
stats,
I
think
most
folks
on
this
call
are
familiar.
If
not
if
this
is
your
first
time
with
us
dents
that
Kate,
although
it's
a
dashboard
system
that
we're
utilizing
to
get
pretty
much
any
and
all
metrics
out
of
cooler,
names,
kubernetes
and
it's
repos,
we've
been
doing
dem
stats,
pull
ups
every
other
week
for
15
minutes
on
Fridays
to
just
go
through
what
it
is,
but
I
think
that's
still
not
necessarily
hitting
the
mark
from
what
we
need.
B
So
I
think
we
just
need
somebody
official,
a
you
know,
quote
quote
official
that
can
help
leave
this
as
a
product
owner
and
I.
Don't
one
second
I'm
looking
at
chat,
ok,
cool
thanks
and
I'm
a
product
owner
perspective.
We
really
mean
actually
going
to
these
cigs
asking
them
for
use
cases
and
then
reverse
engineering,
Deb
stats
I
mean
right
now,
we've
got
this
pile
of
data
and
we
don't
even
necessarily
know.
If
that's
you
know
the
data
that
we
even
need.
B
Just
like
a
service
level
of
like
objective
or
something,
that's
not
customer
related,
just
something
that
we're
saying
to
folks
that
we
want
to
accomplish.
So
you
know
we
want
to
see
an
increase
in
the
number
of
unique
contributors.
For
instance,
it's
like
by
how
much
again
all
of
that
stuff
would
is
TDA
at
the
moment.
So
we
really
need
to
talk
to
people
like
save
architecture
and
other
things
to
get
their
kind
of
buy-in
and
weigh
in
on
this.
B
So
we
really
need
someone
I
think
to
kind
of
just
take
this
by
its
horns
and
make
a
project
out
of
it.
This
could
definitely
be
something
for
a
first-time
contributor,
maybe
somebody
that's
not
new
to
open-source,
though,
but
maybe
first-time
contributor
to
kubernetes
somebody
that
likes
data
analysis.
B
A
Yes,
so,
like
specialize,
I
just
want
to
say
they're
there,
their
metrics
for
ourselves
they're
our
purview
is
our
Charter
for
concern.
Max
Harris
and
I
are
actually
working
on
defining
it,
but
a
high
level
we're
trying
to
maintain
the
project's
health
and
velocity
and
making
sure
that
contributors
have
a
positive
experience.
So
dubsteps
is
a
way
to
kind
of
give
us
feedback
into
that,
and
what
the
stats
are
struggling
affects
our
sense
of
how
well
the
project
is
doing
so.
A
B
C
But
for
some
stats,
that's
a
mean
time
between
a
response
to
a
pull
request.
Those
are
considered
user-facing
right
so
with
our
is
that
also
an
SLO
like
we'd,
have
our
own
internal
stats
that
we
care
about
right,
but
then,
like
the
one
that
I
guess
would
make
us
really
look
bad
to
the
public.
Would
those
be
a
separate
thing
or
is
it
all
the
solos?
C
A
C
D
B
Not
that's
up
for
discussion,
I
mean
literally.
All
of
this
is
up
yep
literally.
All
of
this
is
up
for
discussion
as
to
like
what
each
dashboard
means
and
why
we
care
about
it,
and
if
we
don't
care
about
it
and
filing
an
issue
to
get
that
dashboard
removed,
because,
like
I
said,
this
is
a
public
facing
thing
now,
and
the
public
is
very
much
aware
of
it,
so
we
just
need
to
get
on
top
of
it
as
well.
We.
E
A
C
F
G
E
Want
to
share
I
can
or
if
you
just
follow
the
link.
I
will
just
brief
about
the
work
get
and
myself.
We
did
a
few
weeks
back.
We
also
had
Eric
for
review
on.
That
is
everyone
on
the
link
by
the
way
spring,
you
sure
out
the
dark,
open,
yeah,
alright,
perfectly
alright.
So
basically
we
try
to
identify
different
reasons
to
close
an
issue
and-
and
this
work
is
you
know
it's
basically
targeting
towards
the
issue
clear,
ongoing
work.
So,
as
you
can
see,
we
have
identified
a
few
different
reasons
right.
E
You
know
why
you
why
they
she's
gonna
close.
You
know
the
first
one
is
pretty
obvious:
it's
fixed
and
it's
closed.
We
already
have
a
label
for
that
right
and
then
and
the
next
one
is
inactive
issues.
You
know
this
was
a
part
of
the
original
proposal.
You
know
the
email
I
send
a
few
months
back
to
November
last
year,
very
initial
email-
that
if
the
issues
are
inactive
for
a
longer
time,
you
know
we
should
have
a
label
to
close
automatically
and-
and
luckily
we
have
a
the
first
abort
right.
E
So
it's
closing
issues
as
Garrett
says
or
ninety
days.
We
don't
need
label
there.
Third,
one
is
support,
questions
and
they're.
All
there
is
also
label
out
there
kind
support,
though
we
notice
there
are
issues,
I
don't
see
its
properly
used,
but
I
think
there
would
be
a
separate
discussions,
but
we
have
label
for
any
support
questions
as
well.
You
know
we
are
hit
easily.
We
have
so
many
of
those
issues
out
there
with
the
questions
the
next
to
duplicate
issue.
E
We
don't
have
a
label
right
now,
so
we
really
don't
have
identity
for
a
way
to
identify
how
many
duplicates
we
are
hitting.
This
is
again,
you
know.
Part
of
the
disturb
discussion
had
some
time
back
with
with
Lucas,
and
you
know
we
have
labels,
then
they
can
I
mean
he
can
do
a
really
good
job
there
right,
displaying
stats
so
duplicate,
we
I
think
so
far.
We
agree,
if
that
we
need
a
label
there.
The
second
one
is
issues
that
cannot
be
reproduced
either
they
are
already
fixed
or
or
these
make
of
information.
E
So
to
cover
that
we
agree
that
we
need
a
label
there
get.
It
did
a
really
good
job
with
the
color
coding
here
so
to
unifies
cases
for
the
label,
and
then
you
know
I'm
not
going
to
the
whole
dock
right
now,
but
even
with
the
with
the
with
with
you
know,
a
little
inconsistency
based
between
what
we
have
in
our
guidelines
and
and
that
90
days
for
sixties
closing
by
the
part.
So
something
that's
also
mentioned
here,
but
as
you
can
see,
there
are
a
few
different
requisite
labels.
Here
you
can
go
over
each.
E
E
So
the
whole
point
of
this
discussion
is,
you
know.
Like
I
said
we
already
reviewed
the
work
get
myself.
Eric
has
lots
of
feedback
there,
so
everyone
can
take
a
look,
provide
their
feedbacks,
I
guess
we
will.
The
next
step
will
be
to
to
take
it
to
the
product
committee
right
on
the
Kuban
is
do
list
and
and
in
having
a
broader
opinion.
If
anyone
has
any
objections
on
adding
that
least
those
couple,
three
different
labels
we
identified
so.
A
I
have
a
technical
comment.
I
was
just
thinking
about
this,
a
little
bit
more
in
the
last
couple
days,
I
like
the
idea
of
having
the
labels
more
the
increased
granularity
in
dev
stats
of
understanding
where
our
issues
are
coming
from
and
why
we're
closing
issues
but
I,
don't
think
we
need
new
Bachmann's
I
think
we
can
add
an
argument
to
the
close
command
because
all
of
these
new
labels,
we
want
to
close
the
issue
as
well
right.
We
rarely
want
to
apply
this
label
with
it
or
we
never
want
to
apply
this
label.
E
A
Yeah
I
just
like
fewer
commands
and
then
yeah
these.
We
can
basically
just
propose
these
kinds.
These
new
labels
and
changes
to
dev
stats
and
changes
to
the
close
command.
I
think
those
are
the
three
things
that
are
gonna
happen.
We
want
four
new
labels
added.
We
want
to
add
or
modify
an
existing
dashboard
on
dev
stats
that
lets
us
see
why
labels
or
why
issues
are
being
closed
and
we
want
to
modify
the
close
command.
Does
that
sound,
reasonable
yeah.
H
Yeah
I
I
think
that
that's
good,
but
one
thing
that
I
would
suggest
is:
we've
had
issues
with
adding
labels
before
and
them
not
being
clear,
especially
in
non
core
repos
I'm
thinking
helm.
We
should
probably
actively
solicit
feedback
on
this
from
like
helm
and
say,
like
hey,
does.
Does
this
make
sense
to
you
as
well.
E
We
had
some
discussion
in
in
the
community
meeting
sometime
back
about
consistency
across
all
the
repos
and
we
had
sort
of
you
know.
On-And-Off
feedback
right,
I
think
Erin
proposed
few
things
right
now.
Let's
just
keep
it
to
the
cube
kubernetes
in
hell,
not
not
some
of
the
repos
like
mini
cube
or
what
else
right.
Just
just
worry
about
that.
H
A
C
E
Let
me
try
to
understand
myself
when
we
say
modified
the
close
command
and
again
we're
not
talking
about
the
label
that
itself
but
the
way.
So,
basically
we
we
are.
We
are
talking
that
if
we
introduced
a
new
label
called
close
duplicate
right,
it
will
basically
invoke
the
close
close
label
in
the
background
right,
but
it
will
provide
the
label
close
duplicate.
Is
that
what
you
mean
initially
care
it
with
modifying
the
close
command
yeah.
E
A
C
C
E
E
C
I
just
wanted
to
say
like
if
we
put
it
as
part
of
the
close
command
it'll
train
people
to
use
a
way,
as
opposed
to
oh
I,
think
this
should
be
closed.
Setting
the
label
and
then
three
months
later.
Nothing
like
will
the
bots
check
if
it
has
the
label,
even
if
yet
don't
tell
it
slash
clothes
I'm,
just
wondering
if
we're
gonna
accidentally
create
a
bunch
of
issues
that
say:
I
should
be
closed
but
don't
actually
get
close
I,
don't
I
guess
check
on
yeah.
H
E
C
C
H
A
C
I'm
gonna
introduce
y'all,
real,
quick
and
then
Jose
won't
reduce
himself,
but
just
to
kind
of
train
you
all
up,
I
was
Chris
short.
Did
a
blog
post
on
check
out
my
new
kubernetes
learned
how
to
kubernetes
there
was
a
raspberry
pi's.
I
was
like
oh
I
was
going
to
do
that
great
and
then
I
looked
cos
and
I
was
like
that's
until
mcmoney
right
there
and
I
have
one
of
those.
So
I
was
talking.
C
Tim
and
I
have
been
meeting
for
the
past
know
two
three
weeks
with
crazy
ideas
about
when
it'd
be
neat.
If
you
had
an
Intel
nook
and
it
just
like
came
set
up
out
of
the
boxing
cube
admin
an
it
and
then
you
just
had
like
a
little
developer
nook
that
you
can
give
your
developers
something
cheap
enough.
An
engineering
manager
can
like
expense,
you
know,
buy
it
at
the
kubernetes
store
or
whatever
and
they
get
started.
C
You
know,
while
the
rest
of
their
organization
figures
out
how
they're
gonna
do
kubernetes
and
you
know
getting
cloud
accounts
and
all
that
kind
of
stuff.
So
it
ends
up
that
Jose.
Here
him
and
I
go
way
back
and
he's
working
in
and
tell
them
they're
looking
at
throwing
more
engineers
at
kubernetes.
So
we
got
our
heads
together
and
then
Jose.
You
want
to
introduce
yourself
here.
C
G
I
know
each
other
back
from
I,
guess
the
puppet
community
in
2008,
or
something
like
that.
So
as
I
was
getting
ramped
I
just
to
roll
it
Intel
to
sort
of
be
the
program
manager
for
our
communities
upstream
efforts,
so
you'll
probably
see
me
around,
hopefully
a
little
bit
more.
Let's
get
started
so
we've
got
right
now,
a
team
of
about
sixteen
people
resourced
on
turbine
at
ease
so
we'll
be
hopefully
adding
adding
a
lot
more
to
the
conversation
in
the
next
year.
G
So
so
yeah
I
ran
into
George
sort
of
on
this
mailing
list
and
we
just
got
to
talking
you
know
about
what
little
projects
when
we
get
started.
Obviously
looking
for
some
quick
wins
sort
of
getting
getting
into
any
role,
and
so
this
seems
like
an
easy
thing
for
us
to
do.
We
could
take
a
look
and
reimage
it
with
one
of
our
SI
partners
and
then
sell
it
out,
for
the
community
is
sort
of
a
developer
kit
and
so
I
think
generally
what
we
were
looking
at
for
discussion.
G
It
is
you
know
one
is
this
interesting
to
the
team
you
know.
Do
you
think
this
would
be
useful
for
other
teams
too,
if
it
is
who's
interested
in
helping
kind
of
define
the
scope
and
what
we
actually
end
up
working
on,
I
think
George
and
I
are
going
to
go
off
and
maybe
make
like
a
product
requirements.
G
C
A
cool
developer
experience
that
they
can
just
start
using
right
away.
So
yeah
I
got
asked
a
really
good
question:
cuz,
that's
what
I
do
what
the
heck
is
enough
and
what
I
stand
for
it?
How
is
it
spelled?
I
just.
G
Googled
it
thanks
Jason
next
next
unit
of
compute
nucl
capital,
and
it's
just
it's
just
a
small.
It's
like
a
tiny
small
power
processor
on
you
know
it's
like
I've
sort
of
like
a
Raspberry
Pi
at
forex
86,
so
you've
got
a
bunch
of
ports
on
the
back
and
you
could
use
it
as
like
a
a
gaming
rig.
You
really
wanted
to
keep
it
up
and
put
a
graphics
card
in
it
or
you
could
just
use
it
as
a
desktop
computer
or
I.
G
G
Now
this
is
all
geared
at
the
home
and
sort
of
maker
market
at
Intel
and
if
we
can
sort
of
show
them
that
there's
interest
in
the
data
center,
maybe
we
can
get
a
lower
bin
data
center
processor
included
into
a
small
form
factor,
and
if
we
can
do
that,
you
know
if
we
can
figure
out
how
to
deal
with
the
power
consumption
and
stuff
like
that.
We
can,
you
know,
maybe
talk
to
them
about
unlocking
some
of
the
features
that
are
in.
G
You
know
that
I
normally
bend
down
for
a
low-end
processor
so
that
people
could
develop
with
you
know,
sort
of
the
high
end
data
center
processors
in
a
home
lab
or
you
know,
at
a
startup
or
something
like
that
and
then
have
it.
You
know,
run
performant
applications
in
the
data
center.
So
that's
sort
of
like
the
longer-term
pot,
but
right
now,
since
I,
can
we
get
people
developing
on
x86.
C
C
So
it's
similar
to
this
form
factor.
This
is
a
chrome
box,
but
it's
basically
the
same
thing.
It's
like
you
can
stack
three
or
four
of
them
on
your
desk
and
they
make
cool
little
like
developer
kits
and
okay.
Please
send
me
a
private
message
and
make
contact,
because
I
definitely
have
four
questions.
Yes
well,
I.
Think
we'll
do
it
to
the
public
project
that
will
weep
in
sorry,
I
was
gonna,
say
Jase,
make
sure
you
loop
in
Jess,
because
I
think
she
told
me
they
were
working
on
something
like
this.
Yes,
yeah.
Thank.
A
C
A
Does
a
lot
of
work
on
integrating
kubernetes
with
the
Raspberry
Pi
he's
the
lead
for
cluster
lifecycle
and
I
think
he
got
his
background
with
kubernetes
as
a
student
so
wants
to
make
kubernetes
accessible
to
students
as
well.
His
homepage
has
like
a
cluster
raspberry
PI's
on
it
and
inspections
for
getting
up
and
running
with,
like
a
maker
type
kit
and
getting
people
developing
on
kubernetes
without
a
lot
of
costs
right.
C
A
C
F
C
The
necks
are
powerful
enough
that,
if
you
put
stuff
in
cata
containers,
it
will
replicate
having
separate
nodes,
despite
it
being
one
box
which
I
think
is
key
versus
just
telling
people
to
use
mini
cube
like
they
get
a
real
like
each
note
like
each
pot
on
each
node
will
get
a
real
IP
address.
Just
like
unreal
bare
metal
so,
like
part
of
it,
is
like
not
just
give
people
a
nice
developer
experience,
but
something
that
when
they
do
get
to
the
real
cluster
right,
they
won't.
G
B
We
had
our
first
live
stream
event
this
morning.
I
thought
it
was
fun.
George
was
on
the
call
he
was
on
our
ones
and
Tuesday
K
YouTube
we
had
I
think
was
like
what
20
viewers
on
live
at
7:30
at
7:30
a.m.
Pacific
time,
so
not
bad.
We
filled
almost
an
hour
with
questions
from
slack
and
from
Twitter
about
mostly
new
contributions.
It
was
really
awesome.
B
B
We
have
a
good
base
right
now
of
people,
but
they
will
obviously
burn
out
eventually,
if
we,
if
we
keep
them
on
so
definitely
welcoming
new
volunteers,
for
that
I
put
the
issue
for
volunteers
with
the
signup
sheet
very
similar
to
George's
user
office
hours
for
folks
just
sign
up
I'm,
also
going
to
be
going
to
ke
dev
and
asking
there
as
well.
Please
get
the
word
out
about
this.
It's
like
I
said
it's
something.
That's
a
creative
way
of
scaling,
mentorship
I,
don't
know
if
anybody
was
on
the
call.
C
B
We
did
get,
we
did
get
some
good
traction
on
Twitter,
so
I
think
we'll
we'll
continue
with
that.
We
might
even
want
to
pop
it
on
reddit
and
you
know,
keep
going
with
advertising
cycles,
but
here's
to
that
does
anybody.
Have
any
questions
concerns
comments
about
that
cool
I
was
it
was
super
fun,
I'm,
actually
gonna
skip
the
goals
and
end
that
last
and
that's
scary
and
I
can
get
into
the
goals.
But
the
the
next
thing
I
actually
want
to
propose
is
another
mentoring
strategy,
so
that
will
round
out
I.
B
Think
we're
what
at
five
at
this
point,
but
the
mentoring
idea
that
I
want
to
propose
is
what
I'm
dubbing
is
kind
of
the
Buddy
Program,
it's
very
similar
to
what
I
was
talking
about
in
the
contribute
at
select
the
other
day.
If
you
weren't
there,
it's
pretty
much
taking
a
program
that
they
go
community
has
adopted
for
events,
so
it's
very
similar
like
with
George
and
other
people
been
talking
about
it.
Maybe
like
hey,
why
don't
we
have
a
booth,
AQ
Khan
for
like
new
folks
til?
B
They
come
over
and
say,
hey,
what's
up
kind
of
like
a
connection
point
so
that
it's
not
so
overwhelming
for
people
so
I'm
thinking
about
taking
that
idea
and
essentially
scaling
it
one
up
to
long
term.
So
it's
very
similar
to
kind
of
one-on-one
mentoring,
but
without
the
strings
attached.
So
we
would
have
a
list
of
mentors
who
would
be
free,
not
necessarily
free.
B
We
don't
know
their
availability,
but
free
as
in
they
would
be
open
to
speaking
to
someone
that
they
don't
know
for
about
one
hour
and
they
would
ultimately
give
them
a
tour
of
kubernetes.
So
like
asking
them,
you
know
what
their
goals
are
saying
like
asking
them
about
their
interests.
Saying:
hey!
Okay,
maybe
think
networking
is
a
place
for
you.
This
is
the
approach
that
I
would
take
to
get
in
there.
B
These
are
the
issues
that
I
might
want
to
start
with
so
I'm
going
to
propose
that
in
in
an
issue
today,
so
it's
it's
more
similar
to
one-on-one,
where
people
will
get
a
more
automatic
ratification
like
group.
Mentoring
right
now
is
very
long
term
and
you
have
to
be
like
going
to
a
cohort.
It's
sort
of
like
an
application
process,
that's
more
structured,
so
this
would
be
a
little
bit
more
whimsical
and
I.
Think
that
might
handle
cuz
I'm
right
now.
B
I'm,
just
getting
pounded
with
people
like
hey
I,
need
a
mentor,
handing
a
mentor
right
now
and
then,
of
course,
mentors
are
saying:
I
don't
want
time
at
all
time,
but
I
think
if
we
took
the
the
time
the
the
reoccurring
time,
commitment
out
and
say:
oh
well,
we
only
need
you
for
one
hour.
You
know
every
other
month,
I
think
that
could
alleviate
that
kind
of
like
a
like
a
time
commitment,
if
you
will
so
anybody
have
any
thoughts
or
concerns
about
that
Chris
I
know
you
were.
F
B
Yeah
and
I
and
I'm
down
with
that
too
I
mean
we
can.
This
is
just
beginning
phases
that
I'm
thinking,
so
all
of
that
is
up
for
discussion.
So
if
you
want,
we
can
start
a
little
Tiger
team
and
think
about
how
we're
going
to
tackle
that
issue
and
I
know.
I
think
George
might
want
to
help
too
I.
Don't
know
if
I'm
signing
him
up
for
that.
If
he
wants
to
do
it
he's
like
any
whatever.
B
Cool
all
right,
yeah,
like
I,
said
I
think
this
might
alleviate
quicker
pain
points.
It
might
not
necessarily
scale
large,
but
at
the
same
time,
like
I,
said
I
think
addressing
some
of
the
needs
that
we
have
is
definitely
a
priority
and
I
think
he
owes
some
of
the
immediate
needs
of
folks
are
taking
precedence.
B
So
that's
it
for
mentoring.
I
am
I'll,
put
the
mentoring
umbrella
issue
in
the
in
the
chat
and
on
the
agenda
as
well.
This
is
where
I'm
keeping
all
of
our
opportunities
for
mentorship
and
next
week,
next
week's
meeting
we'll
talk
about
that
in
much
more
detail,
but
I
will
spare
this
crew,
so
I
guess.
Our
next
issue
that
we
need
to
discuss
is
goals
specifically
for
the
next
release.
B
End
of
March
I
have
the
goal
we
have
our
goals
link
in
there
you'll
see
that
we
we've
started
to
really
finesse
these
out
much
more
I'm,
actually
not
calling
them
ok,
ours,
anymore,
just
so
that
folks
can
jump
in
them
and
understand
them
a
little
bit
better.
I
actually
put
our
motto
at
the
top
I,
don't
think
I,
don't
think.
Garrett
has
seen
this
doc,
yes,
but
it
said
something
to
me
yesterday
that
I
swear
I,
think
we
should
live
by
in
this
group,
and
that
is
so
awesome
automated
it
better
be
documented.
B
That's
honestly,
that
is
our
motto
for
the
area.
I
think
it
can't
be
automated
we're
documenting
it
period
like
if
and
especially
like.
We
have
like
some
folks
like
Gwynn
and
others
who
come
along
and
say:
hey.
This
stinks
dot
live
document
it
like
why
it
stinks
and
how
we
can
get
better.
This
is
how
I
think
we
can
really
bring
in
new
contributors
as
well,
especially
from
the
meet
our
contributors
call
earlier.
B
The
more
new
newcomers
come
to
us
and
say
hey.
This
stinks
like
let's
figure
out
why
it
stinks.
Let's
figure
out
what
holds
we
can
hold.
We
can
fill
I
know.
I,
think
this
is
like
our
best
way
to
do
it.
So
I
did
put
in
some
priority
numbers
in
there
and
I
think
this
is
what
I'd
like
to
discuss
with
the
team,
and
there
are
holes
as
well
and
in
the
owner
section,
so
I'd
love
to
get
some
more
volunteers
for
the
holes.
B
So
I
think
our
key
are
a
lot
of
our
key
results,
really
just
have
to
do
with
launching
them
and
getting
them
up
and
running
and
then
like
going
along
with
our
motto
of
if
they
can't
be
automated
a
better,
be
documented,
then
I
think
our
key
takeaway
for
all
of
these
programs
that
we
all
have
documentation
I
mean,
for
instance,
outreach
e
is
ending
at
the
end
of
March
I
better.
Have
that
documented
ji-suk
is
spinning
up
Nikita's.
Getting
that
documented
I
think
that's
a
that's
a
key
part
of
our
success.
B
It's
making
sure
that
all
these
programs
are
about
to
get
documented
so
that
we
can
scale
them
eventually,
and
the
next
objective
is
the
kubernetes
contributor
experience
as
well
document
well
documented
and
continuously
improving
George.
You
promised
a
consolidated,
comprehensive,
insists
on
contributor
guide,
it's
published
by
the
end
of
February
I,
wanted
to
see
what
you
thought
about
me,
taking
some
of
those
words
out
and
putting
MVP
or
something
I've
got
21
yeah.
B
I
J
Yep
feature
complete,
I
have
I've
gotten
I've,
actually
gotten
some
feedback
from
people
on.
What's
what's
there
already,
especially
from
the
team
at
Amazon,
because
they're
just
all
starting
to
like
ramp
up
on
all
of
this,
and
so
I
can
actually
ask
specifically
for
even
more
feedback
from
em,
because
I
think
they're.
Exactly
our
target
can.
C
J
I
Areas
I
think
that
stands
out
still
is
an
in
need
of
scrubbing
is
the
code
review
area
but
Paris
after
next
week's
talk
with
Tim
Hawkins,
so
I'm
gonna,
try
and
capture
as
much
as
I
can
out
of
that,
then
spend
some
time
scrubbing.
All
of
those
docks
and
I
think
that'll
round
out.
One
of
the
major
sections
are.
J
C
B
One
of
their
workshops
is
actually
going
to
be
a
Tim
Hawk
and
live
code
review
where
he
goes
through
some
PRS
that
I
think
he's
might
anonymize
I'm,
not
too
sure
yet,
but
just
pretty
much
like
a
checklist
of
things.
That's
one
of
the
things
that
we
hear
a
lot
from
approvers
plus
it's
that
the
code
reviews
are
lacking
or
missing
certain
key
elements,
or
you
know
things
like
that,
so
just
trying
to
get
folks
up
to
speed
who
or
already
on
the
call,
but
all
right.
B
So
other
things
in
this
objective
that
we
had
George
and
myself
and
I
know.
Other
people
are
working
to
Tim
included
working
to
smooth
out
the
community
meeting.
Now
that
were
so
large
we're
just
making
trying
to
make
this
experience
as
professional
as
possible
for
people
who
are
joining
and
I
think
you
know
we're
making
steady
improvements.
B
Err
George
is
doing
human
content
for
contributors
with
help
from
a
lot
of
other
folks,
it
looks
like
Aaron
signed
himself
up
for
insuring
github
labels
are
well-documented,
so
it
looks
like
Aaron's
gonna
leave
that
and
then
also
we've
got
the
sadhus
and
Garrett's
activity
with
the
label.
You
know
we
just
heard
and
then
a
new
community
website
George.
Do
you
want
to
update
folks
with
ID
info
that
you
that
you've
heard
or
is
it
just
yeah.
C
Real
quick
I
was
thanking
with
CN
CF
folks,
and
they
mentioned
that
they're
planning
on
revamping
the
entire
kubernetes
IO
website
and
they're
like
oh,
we
could
put
this
in
the
community
section
and
I
was
like
what
community
section
so
I've
inserted
myself
in
Paris
into
their
processes,
so
we
can
find
out.
What's
going
on,
I
haven't
met
with
them
officially
yet,
but
as
soon
as
I
find
out.
C
A
C
C
B
So
before
we
move
on
to
the
next
objective,
did
everybody
look
at
the
priority
numbers
with
zero
being
like?
We
absolutely
have
to
do
that
now?
I
did
zero
out
the
slack
admin
guidelines
and
moderation
just
because
we
were
done
and
we're
ready
to
we're
ready
to
release
that.
So,
if
you
have
any
comments
or
questions
about
the
prioritization,
we
use
either
speak
Nano
or
insert
a
comment
on
the
doc.
B
So
the
next
one
is
objective
is
make
stem
staffs
work
for
us
and
come
up
with
metrics
that
mentor
health
and
velocity.
That's
what
we
talked
about
earlier,
especially
meeting
with
a
product
owner.
The
next
objective
provides
sufficient
automation
that
direct
write
access
to
repos
is
no
longer
required.
Ji,
broad
and
Aaron
and
contributor
issues
and
steering
committee
are
working
on
some
of
some
of
those
items.
B
Prioritization
is
actually
often
waiting
on
Aaron
on
that
one
and
then
the
other
objectives
that
we
have
is
growth
and
promotion
of
the
contributor
experience
saying
so,
like
our
face-to-face
meetings,
define
scope
by
the
way
of
a
formal,
Charter,
Darrin
and
I
are
super
close
to
being
on
the
first
draft.
Oh
man,
we
were
almost
done
today
before
the
call,
but
we
just
want
to
tie
up
some
loose
ends
and
then
we'll
send
them
send
out
the
first
draft
to
folks
to
look
at.
B
We
did
sign
up
for
a
intro
in
deep
dive
session
at
Q
con
Copenhagen,
so
we
could
definitely
use
some
help
with
organization
there
and
then
defining
community
management
as
a
sub
project
of
the
sig
and
other
different
levels
of
sub
projects.
Of
this
thing.
So
questions
concern
comments
about
that.
Sorry,
I
wasn't
looking
at
your
faces.
I
was
reading
off
of
the
sheet
George.
C
Sorry
mute
button,
have
you
done
the
draft
of
the
sit
charter
and
all
that
stuff.
D
A
B
A
By
the
way
to
follow
the
template,
fill
with
rock
from
I
guess
and
the
steering
committee
are
proposing
a
governance,
template
I
think
it's
been
set
out
to
contribute
so
I
just
added
a
link
to
the
chat.
If
you
want
to
take
a
look
at
that
we're
trying
to
to
write
our
Charter
in
accordance
with
the
with
that
template
exactly.
B
So
we're
just
trying
to
get
ahead
of
the
game.
It
has
not
been
fully
approved
by
the
steering
committee.
I.
Don't
think
it
sounds
like
it's
about
to,
but
just
just
so
that
we're
ahead
of
things,
there's
a
tldr
version
and
then
there's
a
long
version.
Of
course,
Garrett
and
I
started
with
the
tail
dealer,
then
good,
cotr
and
then
Matt
I
know
you
had
your
hand
up.
K
A
K
B
K
When
it
comes
to,
you
know,
promotion
of
the
contrabass
saying
has
anybody
thought
about
doing
a
road
show
to
the
other
SIG's
to
go
into
each
one
and
to
talk
about
contrib,
X
I
know
a
lot
of
folks,
don't
think
about
it,
and
they
don't
think
of
much
about
the
experience
of
the
contributors.
In
fact,
a
lot
of
times
when
they
think
of
the
contributors
they
think
of
themselves
and
they're
the
most
active
people
in
the
project.
K
B
Yeah
I
mean
we
can't
even
George
said:
let's
do
this,
and
because
what
about
yeah,
let's
split
them
up
I
mean
there's
35,
plus
things
and
working
groups
at
this
point,
I
think
if
we
all
split
them
up
and
it's
something
that
we
can
achieve
and
maybe
we'll
have
just
like
a
script,
I
mean
we
don't
necessarily
have
to
follow
the
script,
but
some
kind
of
talking
points
list.
Okay,
these
things
I
mean
we
could
probably
even
like
slam
in
a
label
conversation
slam
in
a
lgm
T.
This
is
what
L
GMT
means.
B
B
B
Thanks
to
everybody,
for
all
of
your
help,
I
knew
the
contributor
guide
has
been
such
a
count.
I
can't
even
say
that
actually
we're
recording
it's
been
such
an
awesome
experience
for
you
all
and
your
hard
work
does
not
go
unnoticed
same
way,
I
saw
dev
with
issue
triage
and
Chris
it's
about
to
take
the
buddy
program
here.
Everybody
on
this
call
contributors
are
thanking
us,
so
Cheers
go
and
you
up
one
more
thing:
yeah.
J
I
I
was
a
little
confused.
Oh
no,
that
was
just
applause.
Sorry,
no
I
am
I'm
having
to
meet
the
contributors
this
afternoon
as
well.
No.
J
B
I'll
just
PLD
are
from
today
the
biggest
the
the
biggest
trends
and
questions
were
what
sig
do.
I
join
and
I
am
overwhelmed
with
SIG's,
so
yeah
going
exactly
in
the
slack
channel.
If
you
wanna
yep
and
the
backlog
of
in
the
slack
Channel,
we
tried
to
keep
it
that
way
anyway,
I
see
I
see
that's
the
meet
the
contributors,
not
Channel.
Okay,
perfect
thanks.