►
From YouTube: SIG Contributor Experience 20180124
Description
Notes available here: https://docs.google.com/document/d/1qf-02B7EOrItQgwXFxgqZ5qjW0mtfu5qkYIF1Hl4ZLI/edit
A
A
Well,
we
also
have
Jorge
Castro
on
the
line,
who's
recording
for
us
and,
as
always,
please
be
respectful
and
know
that
this
is
a
record
for
recorded
session,
so
it'll
be
posted
on
the
Internet,
and
that
is
forever
hearing
that
the
murderer
posted
the
agenda
in
the
chat
and
the
intent
is
also
posted
in
the
Malinda
invite.
So
before
we
get
started
and
start
any
new
contributors
on.
A
A
little
later
on,
next
I
wanted
to
do
which
we
did
last
time,
which
is
a
really
quick
stand
up
if
you're
not
on
the
agenda,
meaning
if
you're
not
giving
an
update
today
on
the
official
agenda,
and
you
have
something
that
you'd
like
to
share
that
you're
working
on
either
wins
losses
or
something
that
you'd
like
to
embark
on,
speak
now
or
forever
hold
your
peace
all
right.
So,
let's
go
write.
It
up.
I
heard.
D
Some
stuff-
that's
not
on
the
agenda,
but
I'm
working
on
updating
the
generator
app
in
community
as
part
of
the
steering
committee
I'm,
trying
to
formalize
the
concept
of
sub-projects.
So
the
idea
is,
there
would
be
cigs
like
say,
gaps
that
have
sub
projects
such
as
helm,
which
is
contained
entirely
within
one.
A
D
A
D
C
D
Is
one
of
the
existing
state
leads,
so
speaking
is
a
steering
committee
member
there's
not
yet
any
like
official
sanction
way
to
go
about
doing
this.
I
have
witnessed
this
a
couple
times.
I
have
seen
sig
scheduling
where
they
just
kind
of
decided
amongst
themselves,
and
then
you
know
the
steering
committee
and
said:
hey
we're
swapping
one
person
for
another.
We
all
seemed
cool
there.
D
You
cool
that
steering
committee
says
yes
in,
say:
testing
I
had
somebody
reach
out
to
me
and
they
had
been
doing
a
bunch
of
substance
of
work
and
so
I
wanted
them
to
become
a
sickly
to
sort
of
take
on
more
of
the
administrivia
around
managing
their
project.
We
don't
personally
in
state
testing,
have
well
document
a
description
of
what
a
cig
lead
means
and
what
their
responsibilities
are.
But
the
idea
is
it's
not
just
for
the
status
and
privilege
it
is
actually
some
some
stuff
there.
D
D
D
How
we
go
about
doing
this
sort
of
thing
in
the
future
is
the
sort
of
thing
that,
again
speaking
as
a
steering
committee
member,
we
would
really
really
appreciate
that
this
sake
document
and
some
kind
of
Charter
you've
seen
traffic
across
the
kubernetes
death
and
kubernetes
a
bleeds
mailing
lists
where
Phil
and
Joe
and
I
think
Michelle
are
surveying
the
SIG's
to
figure
out
like
how
do
you
do
what
you
do?
What
goals
do
you
have?
What
processes
do
you
follow?
D
This
is
not
in
the
interest
of
like
mandating
that
every
sake
is
run
the
exact
same
way,
because
they're
all
a
little
bit
different,
but
it's
more
like
you
should
at
least
make
sure
that
stakes
have
certain
things
documented
and
defined,
such
as.
How
does
the
segment
decisions?
How
does
the
sink
change
its
leadership
blah
blah
blah?
So
you
don't
have
to
have
that
discussion
a
day.
I
just
wanted
enough.
A
You
very
much
number
one:
everybody
seriously
do
it
second
releases
to
piggyback
on
the
Charter
keyword
that
I
heard
there.
We
there's
a
q1,
ok,
our
planning
link
in
the
agenda
that
we'll
get
to
probably
last,
but
there
is
a
define
our
cig
Charter,
and
that
is
priority.
So,
if
folks
want
to
help
with
that
I'm
going
to
take
the
shot
at
the
first
draft,
but
would
love
other
help
and
collaboration
too?
D
So
speaking
of
sub
projects,
sub
projects
are
things
where
it's
like,
there's,
probably
more
a
core
subgroup
of
people
who
are
interested
in
this
thing,
and
it
doesn't
necessarily
have
to
involve
the
entire
state.
All
the
time.
I
think
there
are
at
least
two
sub
projects
that
fall
within
the
purview
of
this
sake.
Just
anecdotally
number
one
would
be
mentorship.
D
It's
super
great
and
awesome
and
Paris
has
been
trying
to
create
sort
of
an
off
cycle
meeting
where
this
group
can
talk
about
just
going
toward
ship
stuff
and
not
so
much
automation
and
tooling,
stuff
I
think
that's
a
great
idea
that
to
me
looks
and
feels
an
awful
lot
like
a
sub-project.
So
I
would
view
that
as
something
that
has
Paris
and
at
least
one
other
person
as
a
dedicated
lead,
it's
not
attend
a
meeting.
It's
got
its
own
agenda
agenda
link
is
asking
for
permission.
D
That
kind
of
spontaneously
happened
back
in
September
of
2017
was
a
real
burden
on
their
time
and
I
think
it
would
be
fantastic
to
first
raise
the
bus
factor
on
these
people
from
one
or
two
to
something
higher
bus
back
to
being.
If
George
gets
hit
by
a
bus
today,
I'm
not
sure
if
anybody
knows
how
to
update
the
YouTube
channel,
though
I
I
would
rather
like
keep
George
safe,
but
also
in
the
event
that
George
likes
to
walk
by
buses.
D
C
B
E
F
A
Well
next
week
we
actually
start
our
first
edition
of
this
meeting,
but
just
for
everything,
automation,
tooling,
testing,
etc.
So
we
can
definitely
save
that
conversation
for
next
week
and
go
into
a
deep
dive
there.
I
do
need
a
favor
from
someone,
though,
on
this
call,
if
somebody
could
update
the
yeah
mole
file
for
this
thing
today
with
the
other
meeting
time
for
so
that
we,
you
know,
have
it
officially
on
there,
because,
right
now
the
stake
is
only
saying.
The
sig
readme
is
only
saying
that
we
meet
once
bi-weekly
I.
A
C
D
Eventually,
we
would
love
to
be
able
to
step
away
and
hand
it
off
to
a
much
broader
community
in
much
the
same
way
that
we
have
seen
the
kubernetes
community
meeting
begun
to
be
led
by
more
people,
and
you
know
the
responsibilities
have
kind
of
been
shared
amongst
look
around
them
amongst
the
community
by
those
who
are
trusted
to
do
it
well,
I
think
that's
sort
of
the
goal
for
running
MIT
much
more
of
the
community
than
just
not
one
meeting,
especially
time
zones.
If
I'm
asleep.
F
A
And
I:
don't
I,
don't
I
absolutely
cannot
stand
being
a
human
single
point
of
failure
like
that's.
It's
just
icky
actually
keeps
me
up
at
night,
so
I
think
the
less
that
we
can
I
mean
I.
Think
I'm
more
than
George
and
I
can
pull
our
personal
emails
out
of
public
record
I
mean
trust
me.
We
want
to
be
found,
but
at
the
same
time
not
stop.
Okay,
let.
F
Me
add
something
real
quick.
You
might
have
seen
me
filing
a
lot
of
trivial,
seeming
little
issues
and
contributes,
but
it's
four
things
that
I'm
starting
to
find
like,
for
example,
I,
don't
have
access
to
the
Google
document
for
this
agenda.
We
don't
really
tell
people
they
need
to
sign
up
to
the
developer
mailing
list,
first
yeah
so
like
when
I.
When
you
see
something
like
that
in
the
past,
I've
been
like.
Oh
it's
just
one
of
those
things.
F
H
H
A
H
H
You
know
I
I
work
again,
like
a
simple
answer
coding
in
these
efforts
for
face
based
meeting
what
meat
patties
we
do
need
to
work
on
the
agenda
for
the
meeting.
You
know
another
thing
actually
George
asked
in
the
email
mailing
list
that
you
know
we
should.
We
should
start
working
on
that
something
that's
one
of
the
reason.
I
put
it
in
the
agenda
that
you
know
we
need
agenda
for
that
face-to-face
meeting.
You
decide
to
meet
next
month.
Why
and
so
far
you
know
I've
got
four
plus
ones.
H
A
A
A
Cool
I
mean
the
attentions
here
is
just
for
us
to
you
know,
like
I
said
all
got
like
he
said:
I'll
get
together,
but
more
most
importantly,
really
knock
out
a
lot
of
a
smaller
work
that
we've
been
maybe
putting
off
but
stuff
that
we
know
we
can
get
done.
For
instance,
Aaron
and
several
other
people
have
been
wanting
to
label
the
labels
and
define
the
labels
and
essentially
put
them
possibly
on
the
community
glossary.
A
But
you
know,
that's
kind
of
you
know
a
little
pry
think
of
our
priority
for
us,
but
yeah.
We
can
all
get
it
done
if
we
sit
together
and
crowdsource
it
for
an
hour.
So
activities
like
that.
That
would
really
help
the
project,
but
we,
you
know,
may
not
have
gone
around
to
do
yet
and
then
also,
of
course,
planning
and
things
like
that.
So.
A
I
H
H
Face-To-Face
meeting
should
ice
create
so
like
another
like
a
Google
Doc
and
share
with
the
group
and
don't
be
great,
I
mean,
and
we
can
start
with
the
what
you
just
mentioned:
the
label
stuff
but
yeah,
one
of
the
thing
I
I,
think
great
for
the
first
meeting
is
you
know
some
of
the
items
in
the
planning
we
had
it.
You
know
one
point
eight
time
and
that
was
pushed
in
1.9
and
we
keep
pushing
through
things
so
talk
exactly.
A
Alright
so
looks
like
we
have
some
decisions
that
by
Friday
we'll
make
the
final
call
as
to
whether
or
not
we'll
do
the
face-to-face
on-site
at
the
index
conference
and
again,
if
you're
on
the
call
right
now,
just
let
us
know
via
mailing
list
or
slack
channel.
If
you
have
intentions
of
coming,
so
we
can
include
you
alright.
A
A
Those
are
group,
mentoring,
meet
the
contributors
and
actually
for
outreach,
II
and
now
Google
Summer
of
Code.
Those
are
all
tiered
in
two
different
learning
styles
and
audiences.
So
group
mentoring
is
more
of
our
long-term
contributor
ladder
strategy
where
we
take
groups
of
people
who
are
currently
one
rung
of
the
ladder
into
a
nother.
C
A
For
instance,
the
incubation
right
now
is
current
members
going
to
review
our
owner's
files
and
then
the
short-term
kind
of
learning
on
demand,
I
just
need
to
talk
to
a
human
contributor
is
geared
at
that
is
meet
our
contributors.
It's
very
similar
to
use
our
office,
our
with
the
exception
of
contributor
questions.
We're
also
going
to
be
trying
out
a
like
30
minute,
peer
code
review
session,
which
I'm
super
excited
about
and
Ellen
on.
The
call
is
actually
been
helping
me
with
like
how
we
can
actually
get
the
logistics
done
for
that.
A
So
I
think
the
peer
code
review
session
would
be
really
cool
and
we'll
see
how
it
goes.
I
mean
it
could,
you
know
not
go
well
or
it
could
go
awesome.
So
our
first
time
is
February
7th
and
the
doc.
I
checked
that
doc
into
the
mentoring
folder
on
the
community,
repo
I'm,
not
sure
if
it's
officially
merged
at
all,
but
I'll
go
ahead
and
link
that
in
the
agenda
doc
in
a
second,
oh
I
have
plus
one
from
Gwyn
sweet,
yep,
so
yeah.
A
So
it's
outreach
e,
which
is
a
program
that
it's
a
third
party
program,
outreach
e
dot,
o-r-g
that
pays
underrepresented,
folks,
a
stipend
to
work
on
open
source
projects.
Other
projects
like
debian
and
and
some
other
linux
flavors
have
have
outreach
e
interns
as
well,
and
it's
a
long
term
3
plus
month
program
that
that
we
participate
in
and
then
Google
Summer
of
Code
nakita,
who
actually
can
through
google
Summer
of
Code
last
year
for
us
is
going
to
be
now
running
it
this
year
and
I'll
help
her
where
needed.
A
But
that's
what
we
have
for
mentoring
right
now:
I'm
actually
setting
a
humongous
mentoring
umbrella
issue
today,
so
that
everybody
can
see
where
they
can
plug
in
and
help,
because
I
need
tons
and
tons
of
help
with
us.
So
if
you're
interested
you'll
see
the
umbrella
issue
today,
mostly
the
work
that
needs
to
be
done
is
around
curriculum
creation
for
group
mentoring.
So,
ideally,
we'll
have
six
workshops
per
every
group
mentoring
session
and
those
six
workshops
would
represent
skills
that
you
know
each
type
of
individual
needs.
A
So,
for
instance,
what's
the
skills
needed
to
be
a
member?
What's
the
skills
needed
to
be
a
successful
reviewer?
What's
the
skills
that
were
missing
with
current
approvers
and
things
like
that,
and
then
we
target
the
long
term
strategy.
There
is
these
workshops
and
the
materials
that
we
would
create
would
ultimately
create
kubernetes
learning
and
development,
and
so
that's
the
the
kind
of
like
long
term
goal
that
I
envision
here
very
similar
to
like
kind
of
an
openstack
upstream
Institute.
Oh
no
I
just
went
off
and.
F
A
A
A
For
the
details
of
this
that's
getting
checked
in
today,
I
had
it
knit
and
I,
don't
know
it's
about
marriage
and
I.
Don't
want
to
mess
with
my
computer
right
now
could
with
zoom
I
might
threes,
so
I
will
send
that
out
to
not
only
the
slack
channel
but
for
contributor
experience,
but
I'll
probably
send
it
out
to
kubernetes
dev
and
several
other
mailing
lists
so
hold
tight.
G
A
Ea
experienced
contributor,
who
would
take
a
problem
and
the
problems
would
be
submitted
through
either
our
meet
our
contributors
channel,
or
you
know
some
other
way
that
we
can
finish
right
now
in
the
in
the
guide
that
I
wrote.
I
said
you
know,
submit
your
problems
that
you
would
like
peer
reviewed,
24
hours
before
our
meeting
and
then
what
Nikita
is
going
to
do
for
the
first
one
is
go
through
the
stuff.
A
That
is
that
people
have
linked
and
then
address
the
address,
the
ones
that
she
knows
who
she
has
the
skills
for
and
like
the
expertise
to
speak
on
and
also
take
into
consideration
time,
because
we'll
only
assign,
like
twenty
to
thirty
minutes
to
the
peer
review
part.
So
it
would
have
to
be.
You
know,
probably
something
that's
like
size,
medium
or
smaller
that
we
can
get
through,
but
this
is
just
to
get
everybody
talking
and
learning
together
and
kind
of
like
I
think
it.
You
know
peer
setting,
so.
A
And
really
just
set
the
tone
for
code
review
in
the
kubernetes
way
and
actually
George.
Let
me
hold
on,
hopefully
I-
don't
freeze
here,
but
George
actually
set
an
issue
recently
on
this
Barrett
on
that
very
same
topic
of
how
we
don't
have
any
documentation,
that's
geared
towards,
and
you
you
were
on
that
issue
as
well.
We
don't
have
any
documentation
gear
towards
like
how
to
be
a
code
reviewer,
the
kubernetes
way
we
have
like
how
to
do
faster.
You
know
how
they
reviewed
faster,
and
things
like
that.
A
So
in
that
issue,
I
did
start
a
doc
of
all
of
the
docs
that
we
have,
and
external
Doc's
that
would
relate
to
you
know,
could
have
reviews
the
kubernetes
way.
So
if
anybody
on
the
call
is
interested
in
that
collaboration
is
in
there
and
I'll
go
ahead
and,
like
I
said,
I'll
put
the
issue
in
the
agenda
today
as
well.
Yeah.
G
F
Gonna
share
my
screen
real
quick.
Can
you
all
see
that
so
I
went
ahead
and
added
this
to
Guinevere's
umbrella
issue
for
the
contributor
guide,
so
what
this
is
is
all
of
our
existing
developer
documentation
in
the
devil
directory
I
created
I
just
did
an
LS
and
basically
created
a
check
box
frame
for
it
because
there's
stuff
in
there
that
we're
gonna
want
in
the
contributor
guide
and
stuff.
That's
like
not
appropriate,
and
some
stuff
is
duplicated.
F
For
example,
clabon
be
had
the
same
stuff
that
was
in
another
document,
so
I
marked
it
down
as
hey
when
we're
all
done
with
this.
Let's
go
back
and
probably
delete
this
one
at
first
Gwen.
You
know
how
we
talked
about
when
we
move
something
to
contributor
guy.
We
should
delete
it
from
here.
In
hindsight,
that's
probably
a
bad
idea,
so
Joe
was
thinking.
You
guys
should
just
mark
the
document
as
deprecated
at
the
top
point
to
the
new
one
and
then
kind
of
give
people
a
warning
that
this
document
could
delete
at
any
time.
F
That
way
it
will
for
people
that
don't
sit
in
on
this
meeting
or
something
they
might.
You
know
it'll
give
them
a
heads
up.
So
basically,
my
plan
is
from
now
on
is
to
just
basically
scrub
each
one
of
these
documents
as
part
of
this
and
then
do
a
pull
request
like
I've
already
marked
the
ones
that
have
never
been
done
so
mostly
that's.
That's
all
I
really
wanted
to
share.
F
If
you
haven't
known
by
now
before
I
was
saying,
I
was
gonna,
do
a
buncha
could
trip
stuff
and
I
never
got
around
to
it,
so
I'm
actually
scheduling
time
now
so
I
highly
recommend
if,
if
you're
like
hey
I'm
gonna,
do
that
at
some
point
and
then
you
find
yourself
two
cycles
later,
not
completing
it,
putting
it
on
your
actual
calendar.
So
no
one
bothers
you
and
then
actually
saying
I've
dedicated
time,
for
this
has
been
really
useful.
F
For
me,
I
know:
that's
like
engineering,
101
and
I
just
suck
at
it,
but
yeah
progress
is
going
good.
Thank
you.
So
much
to
everyone,
who's
been
reviewing
on
my
PO
requests
and
that's
all
I
have
for
that.
I'll
have
the
next
one.
I
also
did
a
pull
request
to
move
all
the
community
meeting
information.
A
F
F
So,
if
you
want
to
help
of
this
I'll
just
ask
you
to
go
bottom
to
the
top
and
then
we're
like
meet
in
the
middle
forget
more
people
we
can
assign
them
or
what
I
didn't
I
didn't
want
to
file
like
75
bugs
one
for
each
file,
because
that
was
like
too
much
process.
I
feel
so,
if
you're
interested
in
in
working
on
this
fostro,
because
we're
gonna
have
to
do
it
twice.
F
I
found
myself
rewriting
something
and
then
realizing
when
I
got
to
the
next
document,
that
if
I
refer
to
the
old
one,
it's
not
going
to
look
right.
So
I
feel
like
we're.
Gonna
scrub
through
once
then
go
back
and
fix
the
context
for
a
lot
of
them.
That
now
don't
make
sense,
because
at
some
point
we
want
the
whole
thing
to
read
like
it's
written
by
a
common
person
right
now.
They
all
have
different
voices
different
styles,
but
I'm,
mostly
just
like
there's
so
much
old
stuff
in
there.
F
That
I'm,
just
mostly
like
cutting
out
like
a
lot
of
them,
have
a
separate
copy
of
the
COC
at
the
top
right.
So
like
just
cutting
that
out
and
linking
to
the
to
the
canonical
one
is
like
first
step,
then
we
go
back
and
you
know
figure
out.
Does
this
read
like
a
book
instead
of
50
files
that
are
something
of
your
rectory
and.
A
I,
don't
necessarily
worry
about
tone
right
now,
either
because
yeah
yeah,
you
can
always
have
Doc's
scrub
that
and
give
it
a
final
edit
so
yeah.
If
anybody
on
here
is
worried
about
their
writing
or
tone
or
anything
like
that,
I
wouldn't
necessarily
worry
about
that.
Just
get
the
meat
and
potatoes
and
those
boxes
checked.
A
Also
George
can
ship
it
off
to
the
tech,
writers,
mm-hmm
all
right,
moving
on
all
right,
so
next
topic
is:
do
we
want
an
intro
and
deep
dive
for
cube
Connie,
you
I'm,
pretty
sure
everybody
on
this
call
is
going
to
say.
Yes?
Is
there
anyone
that
says?
No
anyone
that
disagrees
with
us
having
a
intro
session
and
deep
dive
for
cube,
Khan
Copenhagen.
D
A
A
Yeah,
that's
fine
I'll!
Do
it
today,
okay,
hold
on.
Let
me
actually
write
that
down
so
I.
Remember
all
right!
Now,
the
meat
potatoes
of
today's
call
is
q1.
Okay,
our
planning
links
in
the
dock,
I'm
gonna
put
it
in
the
chat
too.
Just
in
case
folks.
Don't
have
that?
Oh
you
know
what
dang
it
I
think.
You
know
what
I'm
gonna
have
to
switch.
The
sharing
settings,
cuz
I
think
I've
created
this
with
my
Google
account
dang
it,
but
on.
A
C
A
Okay,
Tim
god,
okay,
okay,
looks
like
Pete,
some
peeps
are
getting
in,
so
that's
good.
Alright,
so
we
have
one
two
three,
four
five
objectives:
all
of
these
are
not
going
to
be
q1
despite
the
title,
so
that's
kind
of
what
we
need
to
discuss
as
far
as
what
we
should
be
pushing
forward
for
q1
what's
priority.
A
E
A
Sure
so,
okay,
ours
stand
for
objectives
and
key
results
and
the
objectives
should
be
something
not
necessarily
broad
but
something
a
little
bit
more
high-level
and
then
our
key
results
are
the
actions
and
and
the
results
from
what
we're
trying
to
achieve
so,
for
instance,
the
first
objective
that
we
have
down
is
create
programs
and
encourage
the
growth
of
all
contributor
latter
levels
and
then,
ideally
anything
that
we're
doing
that
would
be
like
training,
mentoring,
etc,
would
be
kind
of
falling
under
this.
This
objective,
so
first
things.
A
First,
does
anyone
see
any
objectives
on
here
that
are,
or
does
anybody
have
objectives
that
we
that
they
think
should
be
on
here
either
for
q1
or
this
year
that
it's
not
on
here,
I'd
like
to
start
there?
First,
all
right,
that's
a
sounds
like
a
no
all
right.
So
is
there
any
objective
on
here
that
folks
think
need
to
be
addressed.
So
let's
talk
about
q1
priority,
so
I'll
just
go
ahead
and
read
for
those
I
can't
join
into
the
the
spreadsheet
so
again,
objectives.
A
One
create
programs
that
encourage
growth
of
all
contributor
ladder,
levels
objective
to
the
kubernetes
contributor
experience.
Well,
document
and
continuously
improving
3,
make
dev
stats
work
for
us
and
come
up
with
metrics
that
measure
health
and
velocity
next
provide
sufficient
automation
that
direct
write
access
to
repos
is
no
longer
required
and
then
also
any
growth
and
promotion
of
contributor
experience
sake.
I
F
F
D
F
D
F
D
No,
it's
not
I,
wouldn't
so
much
view
it
as
a
reorg.
Just
that
it's
more
like
an
ask
to
every
sig.
Okay,
please
come
up
with
a
charter
that
states
what
you
own
and
some
other
pair
of
buttons
of
the
processes.
Okay
for
the
hot
potatoes
that
are
left
over
that
nobody
is
willing
to
own.
We
are
going
to
have
to
find
it
now.
Okay,
guys,
okay,.
J
F
F
Kind
of
now
that
that
answers
a
question
I
feel
like
our
number.
One
thing
we
need
to
do
right
away
is
sort
out
our
signature.
What
we're
responsible
for
what
we're?
Not
it
should
also
say
what
we're
not
responsible,
I
feel
so
that,
like
people,
don't
assume
that
we
own
things
that
we
don't
I,
guess
I'm
just
kind
of
make
it
really
scoped
yeah.
D
A
I
definitely
think
the
Charter
should
be
a
near
like
I
think
we
should
have
something
of
a
first
draft,
whether
it's
even
an
outline
by
the
next
meeting,
so
we'll
definitely
have
that
as
a
goal.
So,
if
you're
interested
in
in
chartering
chartering
it
up,
let's
talk
about
it
in
a
slack
channel
over
the
next
week
or
so
yeah.
F
When
you
share
the
dock,
just
share
it
with
the
cig.
Yes
I've
something
I'd
like
to
fix
without,
like
sometimes
I
start
documents.
That
is
meant
for
this
thing
and
then
I'll
share
it
with
only
one
or
two
of
you
and
then
like
I
want
to
get
in
the
habit
of
sharing
it
with
the
mailing
list,
so
that,
like
it,
gets
people
other
than
the
slackers
yeah.
A
Same
plus
one,
that's
I
mean
that's
pretty
much.
What
I
did
I
was
only.
We
were
only
sharing
this
between,
like
three
three
flukes
to
get
some
buy-in,
and
here
we
are
now
I
can't
share
with
the
group,
so
I
think
I
need
to
get
into
a
better
habit
of
doing
almost
everything
with
my
gmail
account
surgery.
All
right
so
we've
got,
it
sounds
like
priority
is
definitely
charters
or
anything
else.
That
folks
can
pick
from
here
pick
out
of
here
that
we
should
be
working
on
like
immediately.
A
A
D
A
Yes
and
I
can
yeah.
We
definitely
need
some
help
too,
with
the
Kay
ours
as
well,
so
I
mean
the
Finnegan.
This
is
first
draft
shot.
So
a
lot
of
these
krz,
a
you
know
in
its
current
state,
are
not
really
measurable,
as
stated.
So,
if
you
feel
like
you
know,
kicking
back
and
forth
with
us,
it's
like
hey.
How
are
we
going
to
measure
this?
Please
feel
free.
A
We
definitely
need
that
kind
of
dialogue,
I
mean,
for
instance,
how,
like
I'm,
just
gonna,
take
take
it
to
my
yard.
Here,
like
how
do
we
know
we
were
successful
when
we
put
together
a
contributor
guide
like
what's
that?
What's
our
measure
of
success,
that
a
contributor
guide
that
we
put
together
is
working
mm-hmm.
D
F
A
K
K
I
mean
I
totally
like
the
aspiration
of
that,
but
given
resources,
it
may
make
sense
to
initially
start
focusing
on
a
few
perfu
of
the
levels
or
or
simplifying
the
levels,
the
latter,
and
that
it's
something
that
would
be
measurable
across
all
of
them,
but
it
also
might
spread
the
team
very,
very
thin,
trying
to
to
reach
out
and
do
all
of
them.
In
parallel,
sorry,
I
agree.
D
With
that,
like
this
is
too
much
for
q1.
However
I'm
looking
at
this
document
through
the
lens
of
objectives
are
like
our
North
Star
for
2018,
not
necessarily
discrete
things
that
we
are
going
to
accomplish
within
q1
I.
Look
at
the
chaos
as
things
that
are
discrete
things
that
we
accomplished
I
think
there
are
too
many
of
them
for
q1,
but
I
think.
D
D
A
A
A
A
Correct
exactly
yeah
I
mean
something
like
the
automation,
tooling
and
stuff
like
that.
That
Erin
folks
are
working
on.
You
might
want
to
be
tied
to
releases,
but
I
mean
for
the
qualitative
things
that
may
not
be.
You
know
more
human
related
than
danyetta
quarterly
all
right,
so
we
have
ten
less
little
less
than
ten
minutes
left
questions
concerns
comments
about
the
okay
ours.
Also,
one
thing
is:
we
should
definitely
put
these
on
github.
A
We
should
definitely
put
our
project
planning
on
github
as
well
with
contact
names
and
how
to
reach
out
and
how
to
plug
people
in,
and
this
will
actually
I
feel
like
make
our
sake
easier
for
new
contributors
to
jump
in
and
help
us.
So
that's
cool
here
as
well.
It's
too
keep
this
document
inside
of
a
spreadsheet
and
don't
a
mailing
list,
but
also
to
put
on
github
and
and
to
be
completely
open.
I.
F
Apologize
for
asking
this
because
I
know
it'll
lead
to
bike
shedding.
But
do
we
want
to
use
like
any
kid
hubs
like
project
management,
board,
features
or
anything
up
to
y'all
and
then
someone's
gonna
say
I
prefer
Trello
and
then
we'll
argue
for
like
two
hours,
something.
D
F
F
D
D
Kind
of
operate
more
by
like
github
queries,
so
I
think
issues
that
are
consistently
labeled
with
state
contributor
experience
or
what
I
use
to
understand
what
the
stakes
workload
are
is
doesn't
necessarily
help
with
prioritization.
They
totally
get
that
and
the
reason
I'm
being
quiet
is
because
it's
y'all
sick.