►
From YouTube: Kubernetes Contributor Experience SIG 20180525
Description
We meet every Wednesday to discuss Kubernetes Contributor Experience projects. Join us!
https://github.com/kubernetes/community/tree/master/sig-contributor-experience
A
All
right,
we're
recording
sweet
good
morning,
everybody
or
afternoon
or
evening
or
wherever
you
are
in
the
world-
welcome
to
the
April
25th
edition
of
contributor
experience.
If
everybody
on
the
call
could
add
themselves
to
the
attendees
list
in
the
agenda,
that
would
be
great.
So
first
we're
gonna
handle
the
recurring
items
of
business,
so
it
sounds
like
Paris
already
did.
The
new
contributor
intro
/
welcomes
Paris.
Is
that
right
all.
B
C
A
B
Good
we're
actually
gonna
do
a
live
edition
of
meet
our
contributors
at
the
diversity
luncheon
at
cute
and
we're
good
there.
I'm
not
I'm,
actually
not
good
for
June,
but
I'm,
not
even
gonna.
Think
about
that!
Well,
yeah,
I'm,
sorry,
sorry,
yeah!
So
yeah!
Let's
not
even
worry
about
that!
Are
you
good
with
office
hours,
George,
okay,
cool
all.
A
D
B
B
B
Yeah
I
mean
the
data
is
already
done
so
I
mean
the
data's
cooked
I
just
need
to
do
it
so
yeah
I'll
put
it
down,
I
mean
it's
gonna.
Take
me
less
than
30
seconds
to
present
it,
so
hey
might
as
well
and
then
yeah
so
I'll
I'll
do
slacking
or
the
slack
data
tomorrow
Jonas
by
the
way
that
we
do
this
every
meeting
this
is
just
kind
of
like
are
reoccurring
things.
If
you
will
like
community
management,
esque
things
just
in
case
you're
lost
right
now.
A
B
B
So
charters
done
we're
good
there.
Projects
on
those
goals,
doc
is
liquid.
That's
good!
We
are
still
in
the
middle
of
a
Dee
spoofing.
If
you
will
community
management
topics,
but
I
think
we
are
damn
near
close.
George
and
I
both
know
the
YouTube
a
nerds
at
this
point,
so
we
no
longer
have
just
George
and
I
think
that's
it.
There's
no
real
blockers
on
any
of
the
cig
planning
stuff
questions
concerns
comments
about
cig
planning.
A
B
Alright
and
then
mentoring
I'm
going
to
blow
through
this
really
quick,
because
I
could
take
up
the
entire
hour
and
I
know.
No
one
wants
to
do
that
for
the
entire
hour,
but
mentoring,
we've
got
group
mentoring,
I've
got
a
cohort,
spinning
up
right
now
for
new
contributors
to
members
for
CLI
and
storage.
B
We
are
in
the
middle
in
the
midst
of
automating.
A
lot
of
this
process.
I
did
do
a
flow
chart.
I
will
include
the
flow
chart
on
the
meeting
notes
and
one
second
after
I
get
finished
talking,
but
the
flow
chart
is
what
we
want.
The
first
MVP
of
the
system
to
look
like
in
this
system
is
going
to
be
alerting
us
when
people
fill
out
the
form
and
when
certain
events
are
being
kicked
off
from
the
form
and
like
I,
said,
I'll
share
everybody
with
the
flow
chart.
B
So
if
there's
anybody
interested
in
automation,
I
have
a
couple
people
that
have
agreed
to
give
a
few
hours,
but
after
they've
looked
at
the
flow
chart,
they
realized
that
we
definitely
need
more
than
a
few
hours.
So
we
could
do
a
little
team.
If
you
will
they're
meet
our
contributors
is
going
awesome.
I
think
we
have
had
175
use
of
just
on
the
last
one,
which
is
awesome
because
we're
billing
this
as
mentors
on-demand.
So
essentially
we
just
influenced
175
people
on
their
mutant
journey.
B
B
That
has
been
renamed
the
one
hour
she's
made
the
one-on-one
hour
and
the
docs
have
been
checked
in
for
that.
I'll
include
the
links
when
the
agenda
to
when
I
get
when
I
get
done.
Talking
as
well
just
need
to
again
come
up
with
the
automated
process
for
that
which
goes
hand-in-hand
with
group
mentorian,
because
we're
using
the
same
and
tormenta
sheet
for
that.
B
So
it's
like
a
one-stop
shop
form
and
then
that's
when
it
kicks
off
the
automated
things
that
need
to
happen
just
another
thing
on
the
mentoring
tip,
we
didn't
check
in
the
mentor
guidelines
as
well,
so
the
mentor
folder
itself
is
growing
really
rapidly.
So
if
anybody
wants
to
check
out
the
mentoring,
folder
I
need
to
do
some
more
cleanup
in
the
group
mentoring
file,
but
that's
where
we
are
with
mentoring
and
then
contributor,
documentation,
George
you've
got
a
lot
of
this.
F
So
the
contributor
guide
is
basically
mostly
complete
other
than
the
review,
the
reviews
section,
which
is
still
kind
of
a
bunch
of
notes
and
nothing
else
and
I
kind
of
wanted
to
discuss
it
more
and
figure
out
what
we're
gonna
do
like
around
cube
con
and
because
I'll
have
developers
there
maybe
see
if
I
get
a
volunteer.
We
well.
B
F
H
F
I'm
trying
I'm
really
trying
not
to
tell
Joe
hey
you
proposed
this
thing
and
then
kind
of
bailed
like
no.
You
went
on
holiday,
let's
give
him
a
little
chance
to
catch
up
and
then,
if
I
think
it
becomes
I
think
so
I've
been
talking
to
to
some
of
new
contributors
as
well
as
like
it's
one
of
those
things
where
like
hey.
If
Joe
is
too
busy,
do
we
plan
a
call,
get
three
people
who
are
motivated
to
implement
it,
get
the
general
guidance
from
Joe
and
I
told
him.
F
B
F
H
B
So,
just
let
I
guess
let
Joe
know
that
if
you
need
to
speak
and
and
then
I
know
Aaron's
not
on
the
line
about
label
documentation,
but
there
has
been
some
serious
work
around
the
documentation
of
labels
and
I
think
we're
pretty
much
set
there.
Actually
someone
to
update
the
the
projects
list
as
well
and
then
is
that
a
Vaughn
I
see
him
there.
He
is
son
I've,
given
him
a
late.
The
latest
on
issue
hygiene.
I
Yeah
sure
the
the
latest
is
actually
around
the
labels.
Okay,
so
basically
I
know
in
our
last
couple
country,
X
meetings-
and
you
know
we
talked
about
having
those
new
labels.
You
know
line
them
up
for
the
triage
on
the
specific
to
triage.
So
for
labels
with
prefix
triage,
slash
has
been
added
and
they
will
descriptions
and
the
usage
is
also
added
in
the
triage
guidelines,
so
that
has
been
reviewed
a
lot
of
review
from
Christopher
black
course.
I
H
D
I
Yep
now
one
thing
I
wanna
update
is
one
of
the
issue.
I
have
opened
and
I
know,
I
did
I
did
put
in
my
email
to
the
country
backs
and
some
other
sakes.
You
know
Chris,
Christopher
and
I
talked
that
we
should
update
on
the
mailing
list.
The
same
email,
I
think
Fred,
which
was
proposed,
which
was
with
the
proposal.
E
If
you
want
to
tie
them
together,
this
jump
straight
into
my
agenda
item,
because
we
have
a
bunch
of
kind
label
changes
potentially
pending
the
so
for
all
of
those
I'd
actually
like
to
get
an
official
vote
from
the
cig
to
endorse
that
plan.
Just
because
we
have
a
lot
of
stop
energy,
around
label
changes
and
not
a
lot
of
people
supporting
it.
Particularly.
E
Look
at
that
issue
that
I
have
it's
a
tracking
issue
that
a
certain
steering
committee
asked
member
asked
me
to
create
and
then
didn't
support
the
so
I
I
kind
of
feel
like
like
for
all
of
these.
These
cleanups,
including
you
know,
moving
kind
support
to
triage
support
and
a
bunch
of
others.
We
need
to
actually
have
an
official
see
endorsement
of
this
plan,
or
it's
just
waiting
around
as
an
open
issue
forever.
J
Am
yeah,
I,
I
think
I
think
we
can
move
forward
with
this,
but
we
need
to
go
through
the
process
and
get
it
out
to
the
mailing
list,
because
I
think
there's
a
tracking
issue,
but
I
can't
remember
if
we
actually
send
something
out
a
mailing
list
to
announce
like
hey.
We
need
to
discuss
this
and
come
to
some
sort
of
consensus
right.
E
You
know
what
what
we
have
known
as
neither
tracking
issue.
We
have
one
from
one
contributor
who
is
negative
on
the
changes,
and
we
have
one
comment
from
Aaron
and
that's
it
and
basis
without
sig.
Endorsement.
I
can't
move
ahead
to
the
next
stage,
which
is
putting
it
out
on
the
mailing
lists,
and
it
really
needs
some
more
approval
than
that.
J
J
D
I
I
B
So
workflow
an
automation,
I,
know
I,
might
skip
this
one
as
well,
because
I
know
crystals
trying
to
get
updated
with
the
with
the
kind
labels,
so
I'm
gonna
go
ahead
and
skip
this.
Next
is
the
communication
channels.
I
do
have
note
that
I'm
gonna
change
this
subheading
to
match
the
sub-project,
that's
in
SIG's
Amal
and
that's
going
to
say,
community
management
and
we'll
put
some
other
community
management.
B
Escalade
topics
in
here
later
on,
but
select
guidelines
are
done
on
that
same
topic,
we
probably
need
to
add
the
moderation
guideline
topics
in
here
as
a
PR,
George,
I.
Think
the
last
time
I
checked
this
morning.
You
were
just
making
some
Corrections
and
still
socializing
for
commentary
correct.
Yes,.
H
F
B
Can
you
do
me
a
favor
as
well?
Can
you
put
the
the
commentary
link
inside
of
the
agenda
today
and
then
got
a
medal?
Just
yeah
that'll
just
remind
me
to
update
the
project
file
to
weekly
community
meeting.
That's
good,
no
blockers
there,
we're
George's
and
I
in
a
bunch
of
other
people
are
gonna,
be
working
on
the
next
several
months
schedule.
B
Demos
are
still
pretty
crazy
with
the
length
I
think
we're
out
to
like
almost
July
at
this
point,
but
they
did
that's.
The
breaks,
Roadshow
I
think
we've
hit
the
last
time.
I
checked
85
percent.
We
still
had
some
cigs
that
we're
missing,
but
we've
hit
most
of
them,
which
is
awesome.
We've
gotten
a
ton
of
feedback.
B
That's
been
very
positive,
focusing
to
love
to
have
a
representative
from
contributor
experience,
so
I
think
it
would
be
really
cool
if
we
could
all
start
to
go.
You
know
go
to
a
couple
more
meetings
a
week
from
other
SIG's
just
to
like
show
that
we're
here
and
and
ready
to
help
them
things
along
those
lines.
B
If
we
can
open
up
those
communication,
doors,
I
think
we'd
see
vast
improvements
with
what
people's
perceptions
of
our
project
communication
channels
are
all
right
and
then
communication
documentation,
that's
sort
of
what
we
were
just
talking
about
with
moderation,
guidelines
and
things
like
that.
We're
really
trying
to
revamp
the
communication
folder
to
be
as
robust
as
possible,
and
if
people
on
the
call
think
that
there
are
communication
channels,
it
should
be
documented
that
are
not
in
that
folder.
Please.
A
So
what
I
later
today,
I'm
gonna
do
I'm
going
to
send
our
proposal
for
the
graphs
or
that
we
would
like
for
Lukas
to
take
off
with
the
dashboard
out
on
the
mailing
list
and
to
see
if
people
have
thoughts
or
feelings
about
that.
If
we're
gonna
kill
a
graphs,
it's
super
important
to
somebody.
We
should
probably
know
that
and
then
based
off
of
that
feedback,
then
we'll
seed
with
the
with
continued
me
to
clean
up
dev
stats
and
then
data
validation,
Josh.
E
The
one
area
where
I
know
that
data
is
bad
but
can't
fix.
Is
it's
been
the
last
time
that
the
CNC
F
did
an
audit
of
people's
company
affiliations
in
their
contributor
file?
Was
last
November,
so
you,
you
know
any
of
the
graphs
that
have
to
do
with
companies
are
going
to
have
suffered
in
terms
of
accuracy,
mostly
what
it
looks
like
is.
We
have
less
corporate
contributions
now
than
we
did
four
months
ago,
which
is
not
accurate.
It's
just
that
people
have
left
companies
and
other
people
have
been
hired,
and
none
of
that's
reflected.
E
B
Well,
we've
got
our
major
event
next
week:
I,
don't
think
yeah
I
mean
that's
our
major
update,
going
to
be
done
and
over
with
and
then
and
then
we
go
immediately
into
planning,
China
and
Seattle.
So
it's
just
pretty
much
a
cube
con
kind
of
year
for
these
folks
and
the
contributor
summit
is
on
Tuesday
we're
rockin
and
rollin
there,
and
then
the
update
and
deep
dive
we'll
get
into
in
a
second
when
we
start
to
talk
about
that
stuff.
B
But
no
real
hindrances
or
blockers
won't
anything
that
we
have
events
related,
Josh
I
know
we
talked
about
in
the
contributor
summit
update
it
feels
like
yesterday,
but
it
might
have
been
on
Monday
I.
Don't
remember,
we
wanted
to
do
some
kind
of
what
was
it
like:
a
mini
release
team,
if
you
will
for
events
where
people
lead
events
by
by
like
rotation,
what
was
yeah.
E
I
would
yeah
I
was
kind
of
thinking
of
that,
just
because
we're
getting
too
many
events
for
just
our
team
of
three
or
four
people
to
be
planning
them
all
the
time,
particularly
because
we're
getting
overlap
and
and
I
was
just
thinking
that
the
release
team
model
that
we
already
have
might
be
good
for
that
that
is,
we
figure
out
a
set
of
rules
that
we
need
for
each
event.
You
know-
maybe
it's
not.
Maybe
we
have
a
couple
different
types
of
events
that
have
different
sets
of
roles.
Yeah.
E
B
We
are,
we
are
there
for
everybody
on
the
call.
We
will
have
a
three
hour
contributor
office
hours
at
dr.
Cohn.
So
if
anybody
besides
Josh
and
I's
going
love
to
have
you
there
to
help
out
I
have
no
idea
what
to
expect.
They
told
me
anywhere
between
zero
and
two
thousand
people
could
show
up,
so
he
we're
gonna.
Give
it
a
good
go
though
so
I'm
gonna
start
that
stuff
after
Google
I/o,
which
is
the
second
week
of
May,
so
you'll
hear
more
about
dr.
B
Cohn,
then,
but
ya
know
I
think,
let's
get
maybe
a
little
dot
going,
maybe
some
kind
of
short
proposal
of
what
it
would
look
like
to
do.
Events
rotation
like
the
release
team,
and
then
we
can
talk
about
it.
After
cube,
con
cool,
all
right,
I
think
that's
it
for
the
stand
up.
With
the
exception
of
Christoph,
you
wanted
to
recom
en't
on
the
kind
labels
and
then
also,
if
you
had
any
updates
on
anything
contributor,
workflow
and
automation
related.
J
Yeah,
so
circling
back
on
the
normalizing
labels
issue,
I,
viewed
it
and
basically
my
conclusion,
based
on
the
compete
where
the
conversation
ended
up,
is
everybody's
kind
of
in
violent
agreement
on
that
issue.
There
are
some
concerns
about
potential
conflating
of
what
is
a
bug,
but
I,
don't
think
that's
the
problem.
We're
ever
gonna
be
able
to
solve
as
long
as
we
like
are
allowing
people
to
label
issues,
especially
when
we
ask
issue
reporters
to
like
hey,
take
a
guess
of
whether
this
is
a
feature
request
or
a
bug.
J
There
are
plenty
of
things
that
people
will
report
as
a
bug
in
are
not
bugs
so
I,
don't
think
we're
ever
gonna
solve
that
kind
of
conflation
issue,
but
what
is
a
bug,
but
as
far
as
like
a
consolidating
and
and
getting
rid
of
some
of
the
really
old
kind
labels,
and
that
goes
up
I
think
this
is
a
position
that
we
can
move
forward.
I
would
see
the
next
step
being
putting
it
out
to
the
Contra
backs.
Mailing
list
with
like
a
concrete
proposal
of
this,
is
what
we're
going
to
do.
J
J
B
B
Maybe
I
mean
maybe,
if
we're
just
nervous
about
noise,
then
once
a
week
we
will
collect
any
changes
and
then,
once
a
week
publish
a
an
email
like
digest
decade
of
but
I,
don't
think.
We've
had
any
major
changes
this
week.
So
I
guess
this
one
would
probably
just
stand
alone.
I
mean
we
could
also
just
button
it
up
in
general
to
like
issue
hygiene
and
triage
related
kind
of,
not
necessarily
just
about
labeling
on.
E
B
J
E
J
Think
folder
inside
of
ten
infra
and
Aaron
actually
very
recently
went
and
updated
that
documentation
with
his
label
list,
because
there's
actually
like
a
step
in
there
to
both
update
the
documentation
for
the
labels,
as
well
as
the
actual
label,
think
yamo
file.
So
there
should
be
new
documentation
in
there
but
yeah
if
you're,
if
you're
missing
something
you're
but
there's
something
that
isn't
properly
documented.
There
yeah
just
just
ping
myself
or
Aaron.
B
J
J
B
And
I
know
sure
I
don't
think
he's
on
right
now,
my
child,
such
an
pepper
who's,
been
doing
some
really
awesome
work
on
the
cherry
pick
process,
documentation
I
was
it's
really
awesome.
That's
one
of
the
like
key
ones
that
we
had
so
that's
the
work
is
going
really
well
thanks
to
Tim,
even
though
I'm
sure
he'll
listen
to
the
audio
today,
all
right
any
but,
like
I
said
anybody
want
to
or
think
we
should
be
working
on
something
for
q2
that
we
have
not
mentioned
yet.
B
B
All
right,
I,
don't
think
we're
gonna
need
ten
minutes.
I
just
put
that
just
to
try
to
hog
the
schedule.
The
first
link
is
the
update
planning
doc
very
curious
to
hear
what
people's
opinions
are
now
that
they
just
heard
that
stand
up.
What
should
we
highlight
for
the
update
we
have
35
minutes?
Does
anybody
have
any
opinions
on
things
that
we
should
deeper
into
to?
Let
other
community
members
know.
B
B
That
would
be
me
and
you
and
we'll
talk
about
like
I,
said
we'll
talk
about
the
flow
at
noon
and
when
we
need
today,
okay,
but
you
and
I,
we
can
like
trade
off
and
talk
about
different
aspects
like
you
can
do
dev
stats
and
maybe
take
some
of
the
automation
and
we
can.
We
can
like
slice
and
dice
it.
That
way
is
anyone
on
the
line
going
to
be
at
the
update
session.
George.
Are
you
gonna
be
there
or
we
cool?
Maybe
maybe
we
get
up
I'll.
F
F
G
B
F
I
think,
though,
like
especially
during
a
contributors
summit,
I
think
a
lot
of
leads
will
start
asking
us
questions
of
things
that
we
covered
during
the
roadshow
yep.
So
for
me,
like
I've,
been
trying
to
go
to
Service
Catalog
for
a
while.
It
just
hasn't
happened
for
me
for
some
reason,
so
I'm
just
gonna
sit
down
with
like
Paul
and
Doug
and
kind
of
just
give
them
a
tldr.
You
know
over
a
drink
or
something
and
be
like
here's.
F
What
we
do
for
you,
Bam
Bam,
Bam
and
like
if
we
have
them
all
in
one
place
and
use
you
have
the
opportunity
to
like
you
know,
hey
man,
how
you
do
with
labels,
you
know
or
whatever
it
is.
You
know,
you're
talking
about
I,
think
it's
a
good
opportunity
when
you
physically
have
them
there
to
to
bust
out
a
lot
of
things
and
questions,
especially
like
the
new
working
group
like
I'm,
expecting
like
I
put
I
put
in
our
in
our
thing.
F
B
B
C
I
I
think
for
pretty
much
all
contributors,
and
especially
in
new
contributors
me
being
one
of
them.
I
think
it
would
be
good
to
get
a
little
more
updates
on
like
how
do
we
do
the
one-on-one
meetings
necessary
necessary
steps
to
to
get
those
rolling
necessary
steps
to
get
involved
with
them?
That's
that's
for
both
new
and
existing
contributors,
because
you
want
existing
contributors
to
be
there
as
well.
So
I
think
that,
particularly
when
you
have
both
new
and
existing
contributors-
and
you
have
the
stage
I
would
say,
talk
about
those
to
get
involved
there.
C
B
Cool
and
quick
plug
for
everyone,
I
have
a
35
minute
talk
on
mentoring,
so
I,
don't
I,
don't
know
if
I'm
gonna
go
into
deep,
deep
conversations
about
mentoring
in
the
deep
dive,
but
I
definitely
will
at
least
let
people
know
that
if
they
can't
make
it
to
the
session
that
they
can
find
the
35
minutes
of
me,
rambling
about
all
the
mentoring
programs.
So
that's
the
good
news
and
then
we
can
also
ramble
about
the
stuff
that
George
and
other
people
are
doing
with
the
documentation
aspect
as
well,
so
that.
C
B
Yeah,
thank
you
so
much.
That
was
a
good
validation
that
we
needed
for
that.
So
Elsie
and
I
will
get
together
at
noon
today.
Pacific
time
and
we're
gonna
start
with
the
flow
and
we'll
paying
everybody
if
we
need
them
for
anything
else,
for
that
and
also
sort
of
Josh
anything
issued
triage
related
to
that.
You
want
people
to
know
in
this
35
minute
update,
even
if
it's
just
a
link,
I
think
that's
important,
because
we
have
to
turn
the
slides
in
and
I
know.
A
lot
of
people
actually
do.
B
Look
at
the
sake
updates
lives.
So
links
are
probably
our
most
critical
thing
on
this.
Not
even
you
know
the
format
or
anything
just
to
make
sure
that
we
have
actionable
steps
that
people
can
take
alright
and
then
Tim
I
saw
you
joined
hey.
How
are
you
alright?
So
let's
go
right
into
the
deep
dive
then
so
Tim
and
I
actually
met
yesterday,
Ryan
J
who's,
who
said
he
would
help.
Take
this
up.
Take
this
up,
meaning
the
shepherd
in
all
of
the
work
that's
being
done
around
the
developer
guide
or
the
new
developer
guide.
B
B
D
D
D
B
B
Okay,
now
you've
seen
all
this
stuff.
What
are
we
missing?
What
can
we
do
better
and
then
really
just
actually
start
a
live
note-taking
session
and
then
hit
the
ground
running
when
we
come
back
from
Q
Khan
and
start
work?
That's
where
my
head
was
Tim.
Take
it
away
with
what
you
think
to
that
delivery.
L
B
D
B
E
B
Yeah,
that's
an
act,
that's
really
I!
Think
10,
Tim
and
I
talked
about
that.
Yesterday,
too,
with
the
docs
team,
like
I,
think
was
just
like
important
to
get
people
involved
in
this
just
because
it
has
been
pulling
teeth
because
we've
gotten
a
lot
of
people
that
have,
you
know,
issued
complaints
via
issue
and
things
like
that.
But
nobody
that's
actually
wanted
to
do.
B
They'll
do
the
work
which,
like
we
have
a
couple
of
us,
they're
willing
to
do
the
work,
but
in
my
case,
I'm
like
I
need
to
hear
what
some
of
the
other
complaints
are.
Besides
like
API
conventions
or
if
that's
the
only
complaint
and
we're
good
to
go,
and
we
just
clean
up
the
file
and
ship
out
a
better
readme.
So
but
we
know
that
there's
holes,
so
I
just
want
to
hear
like
where
the
other
holes
are
I've.
D
B
L
B
F
Got
one
yep
sorry,
so
one
thing
I
noticed
that
we
did
in
Austin.
Is
it
felt
like
we
had
a
lot
of
people
coming
up
to
us,
asking
us
questions
and
stuff
like
that?
I
think
this
time
we
should
like
get
a
ziploc
bag
or
something
to
keep
all
their
business
cards,
because
when
we
soon
as
we
came
home
and
we
went
to
the
meetings
there
was
like
nobody
and
like
it
was
like.
Oh
no,
we
should
have
written
people
down
and
like
it
sounded
like
people
were
excited,
but
everyone
sounds
excited
at
a
conference.
F
You
know
they're,
like
sure,
I'll
volunteer
for
this
or
whatever
I
was
thinking
like.
If
we
made
it
a
little
bit
more
formal
where
it
was
like
all
right.
You
put
your
you
know:
you
put
your
business
card
in
Paris
of
magic
bag
and
then
like
you're
in
you
know,
and
then
it
kind
of
like
gets
people
more
engaged
like
I
feel
there
was
a
lot
of
people
that
we
reached
out
to
and
then
we
never.
We
never
followed
up
with
the
open
source
lolly.
So
I
thought
like.
Should
we
get
Ally?
F
You
know
one
of
those
card
reader
things,
but
then
we'd
lose
it.
Let's
just
get
like
a
ziploc
bag
and
have
like
a
shared.
You
know
and
then,
like
all
of
us
as
we're
walking
around.
We
just
say
you
know
this
person
is
interested
and
you
write
it
on
the
card.
You
toss
it
in
there
and
when
we
get
home
you
know
we
kind
of
organize
it
better
or
something
or
something
something
that
enables
us
to
reach
them
again.
Deadly
Oh,
I
felt
like
people
were
excited
and
then
I'd,
never
yeah.
F
B
Right,
I'm
gonna
be
really
brief.
With
this
I've
started,
the
contributor
experience
mid-year
survey,
I'd
love
to
get
your
opinions,
suggestions,
feedback
whatever
on
the
poll
of
questions.
So
if
you
have
had
a
burning
desire
to
ask
our
contributors,
something
about
their
workflow,
their
automation
or
our
automation
or
testing,
and
for
our
mentoring,
whatever
it
is,
I
literally
just
started.
There's
about
forty
other
questions.
I
have
on
the
top
of
my
mind,
but
I
wanted
to
start
throwing
this
out
there
because
I'd
like
to
get
it
out
mid,
June
and
I.
B
B
F
I
was
talking
to
Chris
enesta
check,
I,
hope,
I,
got
it
right
this
time
at
the
CN
CF,
because
we
needed
proper,
single
sign-on
for
discuss.
Kubernetes
do
and
he
says:
hey.
We
had
this
all
set
up
on,
discuss
CN
CF
io,
so
he
set
that
up
and
he
was
like,
wouldn't
make
more
sense
to
have
like
kubernetes.
Just
be
part
of
this
we've
they've.
It's
got
data
in
there
from
a
trial
that
they
tried
like
a
few
years
ago.
That
kind
of
stuff.
F
So
I
wanted
to
run
that
by
everybody,
because
I
know,
April
was
like
I'm
keeping
an
eye
on
how
y'all
are
doing
discourse
cuz.
We
might.
We
might
not
be
interested.
So
it's
live
on,
discuss,
CN,
CF,
dot,
IO
and
kubernetes
I've
tried
discourse,
calm
is
still
up,
I
haven't
taken
that
down
or
anything,
but
my
free
trial
is
running
out
on
kubernetes
that
tried
discourse
or
so
I
wanted
to
run
by
how
do
people
feel
about?
We
would
just
have
a
section
under
a
CNC
F
forum,
but
one
I
could
think
of.
E
F
E
F
F
F
No,
it's
gonna
stay,
but
I
did
I
was
able
to
get
some
really
good
feedback
from
the
chef
community.
Who
do
you
say
like
list
and
they
wrote
out
an
entire
instruction
set
on
how
their
open
source
project
uses
it
that
we
would
just
totally
steal?
No,
they
took
screenshots,
so
you
can
just
follow.
Allah
I
mean
they
did
a
really
good
job.
So
is
that
public,
cuz
I
yeah,
absolutely
just
chef
mailing
lists
nice.
Thank
you.
So.
F
B
F
A
simple
block
post
so
the
way
they
communicated
they
were
moving
from
their
mailing
lists.
A
discourse
was
done
poorly,
so
I
linked
to
a
blog
post
in
the
CAF
from
a
person
who
was
an
outsider
contributor
looking
in
and
he
wrote
a
long
blog
post
of
stuff
that
we
need
to
avoid.
Basically,
so
yes
and
I
documented
everything
that
they
general
he
likes
it,
but
the
way
they
migrated
it
you
know
mentally
I
was
like
okay,
don't
do
that?
Don't
do
that.
So
I
was
really
fortunate
that
they
were
able
to
document
this.
F
F
G
F
E
Well,
I
already
talked
about
the
kind
of
labels
and
then
I
just
dropped
a
link
in
there
and
that
just
to
let
this
group
know
that
the
release
team
is
talking
about
some
changes.
We
need
to
make
to
how
milestones
are
tracked,
labeling
wise
in
order
to
support
tide.
You
don't
need
to
do
anything
about
this,
but
I
thought
it
was
important
for
contributes
to
know
about
it.
Oh.
D
C
D
C
Yeah
you
kind
of
nailed
it
there.
I
want
to
I
definitely
want
to
be
a
part
of
this
and
I
want
to
make
sure
I
understand
everything.
First
before
I
before
I
do
too
much
the
I'm
really
looking
forward
to
the
contributor
summit
next
week,
so
I'll
be
there
I'll,
be
in
the
the
first
track.
It's
going
to
be
very
interesting
and
I.
Think
I'm
gonna
gain
a
lot
of
knowledge
from
there
and
I
apologize
for
the
car
alarm
outside
yeah,
so
I'm
real,
looking
forward
to
that
and
yeah.
C
G
K
B
Glossary
is
our
friend
for
stuff
that
we
think
should
be
defined.
There
is
a
community
tab
too,
on
the
glossary,
so
if
it's
not
even
necessarily
related
to
pods
and
and
cube
control,
and
all
the
other
good
keywords
that
we
have,
if
it's
like
community
related
like
tide
or
prow
or
whatever
one
is
there,
there
hey.