►
From YouTube: Kubernetes Contributor Experience 20190911
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
All
right
good
morning,
everybody
are
you
needing
it
or
afternoon
or
wherever
you
are
no
welcome
to
the
September
11th
edition
of
contributor
experience.
My
name
is
Elsie
Phillips
and
I'll
be
hosting
the
call
today.
I
want
to
start
off
the
call
by
reminding
everybody
that
we
do
have
a
code
of
conduct.
The
TLDR
on
that
is
just
please
be
excellent
to
each
other.
C
D
A
E
F
E
E
B
Contributor
summits,
Paris
registration
is
live.
Why.
G
Your
friends
immediately
kind
of
thing,
if
you
work
for
a
large
employer,
please
forward
the
link
around.
As
of
yesterday,
we
already
had
like
over
a
hundred
rSVPs.
The
capacity
is
450
again.
Please
tell
your
friends
we're
gonna
update,
kubernetes
dev
mailing
list
weekly
until
the
show
with
the
capacity
numbers
and
any
other
information
that
is
necessary
for
folks.
The
schedule
will
be
released
sometime
in
the
beginning
of
october
and
that's
pretty
much
it
for
the
contributor
summit,
but
on
a
meta
request.
G
We
do
have
a
sake
meet-and-greet
in
the
afternoon
that
Dawn's
running
and
other
folks
and
Jason
and
and
some
other
contributors
we
need
to
contributor
experienced
reps
I
will
indeed
be
there
to
help.
You
I'll
be
around
the
table,
but
I'd
like
to
have
two
dedicated
folks
there
on
site
that
own
that
are
only
doing
signe
and
greed
and
no
other
duties
for
the
contributor
summit.
Do
I,
have
any
takers
here
and
end.
Or
would
you
like
me
to
describe
what
the
Signum
greed
is
or
have
dawn?
Do
it.
A
H
Sure
so
the
Sigma
gree,
basically
is
the
place
where
the
SIG's
can
talk
to
both
new
and
existing
contributors
about
what
it
is
they
do,
and
the
people
who
are
interested
in
contributing
to
that
sig
come
to
the
table.
They
can
ask
questions.
They
can
talk
about
what
it's
like
to
participate
in
that
sig.
So
from
the
sig
side,
it's
sort
of
a
recruiting
time
and
from
the
individual
side,
both
new
contributors.
It's
for
new
contributors,
you've
just
gone
through
the
workshop.
You
can
approach
SIG's,
they
might
be
interested
and
learn
more
about
them.
H
Also,
existing
contributors,
who
maybe
contribute
to
other
SIG's
but
are
interested
in
another
area,
can
talk
to
an
another
sig
and
see
what
it's
like
to
contribute
so
pretty
cool
to
be
about
an
hour.
But
we
need
people
to
sit
at
the
contrib
X
table
and
talk
about
what
it's
like
to
participate
in
kitchen,
Beck's
and
I
will
drop
the
section
of
form
that
we
want
you
to
fill
out
so
that
we
can
keep
track
of
all
of
the
people
who
have
agreed.
F
H
G
D
G
E
Not
much
to
updates
I
mean
I'm,
assuming
everyone's
reading,
the
updates
I'm
sending
the
Kate
stuff.
The
deadline
today
is
actually
our
first
deadline.
The
elections
like
less
than
a
month
away,
so
all
bios
for
all
the
people
running
and
voter
exceptions
and
the
voter
exception
forms
yeah.
So
those
should
all
be
closed
out
by
the
end
of
the
day,
I
sent
a
reminder
yesterday,
24
hours
early,
to
remind
everybody.
So
after
that
we
have
about
a
week
for
Bob.
E
G
G
There
we
go
so
this
is
you
reach
out
to
me
or
reach
out
and
slack
again
for
folks
who
don't
know
made?
Our
contributors
is
an
upstream
and
mentoring,
on-demand
initiative,
where
we
answer
fun,
questions
like
what's
your
favorite
color
and
why's
my
test
flaking
on
live
air.
It's
very
awesome
and
that's
it
form.
You
know,
contributors
I
would
love
other
help
as
well
like
programmatic
support.
So
that's
you
to
feel
free
to
jump
on
board
this
train
and
look
to
have
you
for
other
mentoring,
an
incident
that
we
have
going.
G
We
actually
are
putting
in
I
need
to
put
in
the
recs
today
to
actually
for
outreach
interns.
One
is
going
to
be
proposed
to
do
more
work
on
the
developer
guide,
help
marquee
out
marquees,
really
stepping
up
for
developer
guide
stuff
as
well.
We're
Edouard
worked
a
lot
on
the
RER
kotecha
of
the
files
themselves
into
structures
that
make
sense
for
the
sinks
that
need
them
murky
and
crew.
G
We'll
be
focusing
a
lot
on
content
development
of
some
things
that
we
have
issues
with
and
then
the
other
wreck
that's
gonna
go
in
will
be
for
the
contributors
site
for
some
front-end
health,
as
well
as
technical
writing,
help
I'm
gonna
get
I'm
gonna
try
my
hardest
to
get
those
out
today.
If
anybody
wants
to
help
me
write,
those
I
would
love
help,
but
otherwise
they'll
go
out
very
late
this
afternoon
this.
What
does
this
mean
for
you
as
the
individual
contributor
on
the
line
right
now?
G
This
means
we're
gonna
get
a
lot
of
people
who
are
applying
out
Ricci
and
in
order
to
apply
it
out
Ricci
you
have
to
do
a
first
PR.
So
if
anybody
listening
could
throw
down
good
first
issues
as
well
as
health
wanted
story
in
that
time
period,
not
necessarily
now,
because
you
know
they'll
get
eaten
by
all
of
our
awesome
new
contributors,
but
at
that
time
period
and
then
we'll
push
everybody
into
the
outreach
e
apps
slack
channel.
G
And
that's
where
we'll
do
you
sort
of
mentor
triage
as
we
call
it
and
help
people
along
they're
contributor
journey,
while
they're
making
an
outreach
contribution,
so
cool
things
are
cool.
Things
are
on
the
front
here.
We
also
need
to
make
sure
that
all
of
the
G
Sox
students
have
a
demo
slot
at
the
community
meeting
I.
G
Don't
necessarily
think
we
have
any
owners
on
that,
but
I
will
take
that
as
an
owner
if
they
don't
have
one
and
then
other
mentoring,
stuff
marquees,
also
stepping
up
to
help
me
with
some
of
the
issue:
triage
related
to
mentoring,
because
I
put
I
an
ik
issues
and
into
github,
and
they
need
to
be
cast
out
and
chunked
down
a
little
bit
better
and
sliced
up
a
little
bit.
So
thanks
to
marki.
For
that
really
appreciate
it
and
I
think
that's
it
for
mentoring.
I
was
a
lot.
G
E
A
Okay,
community
management
back
to
Paris-
you
didn't
know
you
know,
does
anybody
have
anything
for
her.
G
I've
got
three
things
ready
to
roll
now,
which
means
that
a
which
means
that
a
chair
email
will
go
out
today
because
we
have
at
least
three,
so
all
of
them
course
pertain
because
that's
the
probably
the
thing
that
is
most
intricate
right
now,
if
you
will,
with
the
most
moving
parts
in
the
community,
but
if
anybody
else
has
anything
that
the
chairs
need
to
know
immediately.
Please
include
it
in
that
as
either
a
comment
or
a
suggestion,
or
something
and
we'll
get
that
out
today.
G
Don't
think
Yang's
on
and
I
don't
think
Nikita's
on
either,
but
I
know
that
they
are
doing
really
cool
stuff.
There's.
Actually
an
AIPAC
meeting,
a
planning
meeting
on
the
contributor
experience
meeting
notes
right
before
this
August
29th.
You
can
see
some
of
the
stuff
that
they're
lovely
they're
talking
about
the
kubernetes
summits
in
seoul
and
sydney,
possibly
doing
new
contributor
workshops
there,
which
is
a
really
good
idea.
G
K
A
assignment
is
to
only
have
one
assignees
sort
of
this
idea
that
we
should
have
one
person
that's
responsible
for
a
PR
rather
than
having
to
each
one
of
which
points
to
the
other
when
they
are
asked
why
they
don't
do
anything
and
I
am
the
most
guilty
person
of
all
of
pointing
to
the
other
person,
so
that
if
people
have
comments,
I
think
it'll
be
great
to
destroy
attention.
Then,
please,
chime
in
on
that
and
we're
having
good
discussion
already
on.
L
For
the
sub-project
itself,
no
specific
updates,
there's
like
a
couple
things
that
are
in
progress.
But
the
biggest
thing
that
is
waiting
on
me
is
doing
some
of
the
sub-project
owner
responsibilities
to
get
like
an
agenda
and
dock
and
stop
created
for
our
regular
meetings,
but
no
no
specific
updates
for
the
skirt.
Yet.
G
G
The
marque
ended
up
taking
some
of
the
the
chunks
of
like
the
dead
guide
triage
that
we
have
going
on
to
make
sure
that
we're
covered
there,
and
then
we
did
not
talk
much
about
the
contributor
guide
or
the
non-code
guide,
but
we
also
talked
about
the
contributor
site
and
we're
just
waiting
for
a
home
page
to
go
through
some
revisions.
Wait
just
a
little
I
guess
on
the
ghost
I'm
dead
and
that's
really
it
for
what
happened
in
that
meeting.
J
The
developer
guide
I
had
a
meeting
with
Eduardo
to
sort
of
go
over
the
large.
He
has
a
large
body
of
work
that
he
did
on
this
and
sort
of
quantify
everything
there
and
then
sort
of
get
all
of
the
other
issues
that
are
sort
of
around
this
and
length
start
linking
them
all
together.
I
started
that
I
also
started
a
document
that
I've
linked
in
the
umbrella
issue
to
start
tying
all
this
together
and
then
start
to
do
the
actual
documentation.
G
I'm
super
pumped
thanks
again
I,
think
I
said
this
like
80
times,
but
I
think
this
is
one
of
the
important
pieces
to
our
sig
as
we
make
sure
that
all
of
our
contributor
documentation
is
like
p
zero,
and
this
is
greatly
helping
the
tragedy
of
the
commons
so
really
appreciate
your
help
here.
Thank
you
for
the
opportunity.
Thank
everybody
else
for
the
opportunity.
D
G
Think
they
had
been
taking
a
hiatus
I.
Just
like
read
other
reasons
and
assignments.
The
work
is
now
the
contributor
documentation
meeting
so
that
we
can
all
talk
about
all
the
guides
at
the
same
time
and
all
the
documentation
at
the
same
time.
So
we
don't
have
like
individuals
like
40
individual
meeting,
so
we
can
definitely
kick
off
that
conversation
in
the
next
meeting
that
we
have
if
you're
interested.
B
C
C
So
what
I've
shared
are
the
documents
about
easy,
CLA
and
also
the
github
location?
This
is
an
open
source
project,
so
we
do
accept
PRS.
If
you
have
any
suggestions,
you
can
open
up
issues
and
feature
requests
and
so
on
and
so
forth.
But
let
me
just
do
a
quick
demo.
This
is
gonna
focus
on
the
contributor
piece
of
easy
CLA
and
for
most
of
kubernetes
this
is
going
to
be
very
lightweight.
You
won't
notice
much
much
of
a
change
at
all
and
that's
kind
of
the
point
we
migrated
like
99%
of
your
data.
C
C
C
L
C
F
C
C
Then
it
directs
them
to
this
console.
They
would
select
corporate
if
they're
associated
with
a
with
a
company,
if
they're
just
contributing
on
their
own,
not
under
any
kind
of
organisation
to
click
individual
in
this
case
we're
gonna
click
corporate
and
then
you
search
for
your
company,
my
company's
most
awesome
and
then
I,
just
click
the
checkbox
continue
and
now
I
will
be
greenlit
in
the
future.
For
this
specific
one,
it
does
require
a
nice
ele
on
top
of
your
company
CLA,
but
that
will
not
be
the
case
for
kubernetes.
C
E
C
C
L
These
so
contest
actions,
don't
change
anything
with
the
tech
CLA
commands,
let's
check
the
LA
command
in
a
trowel
command
specifically,
and
what
it
does
is
that
look
for
the
status
context
and
associate
slight
label
to
it,
because
the
the
CLA
status
will
still
come
in
as
like
a
like
a
commit
data
but
tied,
and
everything
else
is
set
up
to
use
labels.
So
there
will
check.
L
Cla
will
still
be
eight
things
if,
like
we
dropped
webhook
and
things
are
distinct
between
the
two,
so
we'll
still
need
that
the
major
difference
as
far
as
I
understand
it
is
the
back
end.
Things
is
report
the
context
his
open-source
network,
as
opposed
to
the
previous
closed
source,
Linux
Foundation
check.
My
interest
is
Jacob
I'm.
Sorry,
I
have
a
few
questions,
so
I'm
interested.
Where
is
the
like
database
for
this
sort
like
where
is
the
listings
of
who
has
find
the
LA,
is.
L
C
L
Okay
and
I
know
so,
like
you
and
I,
like
you
had
done
like
a
private
demo
for
me
a
few
months
ago,
and
there
was
some
questions
around
how
we
were
associating
users
and
such
because
there
was
like
be
these
full
database
or
what
the
mix
of
like
in
some
cases,
use
the
github
handle,
and
some
cases
also
checking
the
email
address
to
find
the
commitment.
How
how
is
this
setting
and
who
is
attracting
guests
like?
Is
it
checking
the
email
addresses
on
the
commits,
or
is
it
strictly
checking
like
the
user,
who.
K
C
It
checks,
it
checks,
everybody
that's
associated
with
the
PR,
so
it
could
be
multiple
people.
It
could
be
multiple
PI's.
So
when
you
do
when,
when
you
do
the
commit,
then
it's
gonna,
it's
gonna
check
to
see
if
you're
covered
by
a
CLA,
either
by
your
email
address.
If
they
can't
find
your
email
address,
you
will
look
for
your
github
ID.
We
have
almost
all
of
your
github
IDs,
so
it'll
check
that
list
as
well
and
then,
if
it
doesn't
find
anything,
it
will
also
the
white
lists.
L
One
was
do
when
we
do
like
large
feature
branch
merges
in.
So
if
we
have
a
feature
branch
that
is
merging
back
in
it
may
have
hundreds
of
commits
in
it,
and
these
hundreds
of
commits
may
be
from
like
dozens
of
different
contributors
that
has
like
different
email
addresses
associated
with
them
is
this
would
like?
How
would
this
DLA
bought,
handle
that
use
case?
Would
it
go
in
and
check
each
individual
commit
or
PLA
compliance
right.
C
So
I
did
talk
to
dims
about
this
and
he
he
was
saying
that
they,
he
is
describing
the
scenario
that
I
believe
he
just
described
and
since
you
guys
want
to
keep
the
history
of
every
previous
commit
as
you
move
it
and
then
recommit
it
somewhere
else,
it
will
be
checking
all
of
those
IDs
again,
and
so
there
is
an
open
feature
request
to
like
just
do
like
a
an
approval
workflow
to
pass
all
those
previous
commits
that
may
or
may
not
be
covered
by
slow
in
the
past.
Does
that
answer
your
question?
L
L
L
C
L
C
For
GR
PCG
RPC
has
already
adopted
in
LA
I
managed,
almost
all
of
that
so
I
somebody
promoted
me
temporarily
to
admin.
I
mean
web
hooks
for
the
existing
CLA
bot
and
then
I
installed
the
EZ
CLA
application
and
then
added
all
the
repos
that
you
guys
want
to
have
cele
checks
for
to
the
list
on
the
project
console.
C
L
C
L
C
Right
great,
so
I
did
share
three
links
in
the
chat,
so
the
first
one
is
the
boss.
There's
a
lot
of
documentation
there
and
there
are
like,
like
adding
additional
repos.
There
are
steps
and
screenshots
in
there,
but
I
can
certainly
do
a
demo.
I
can
record
it
and
so
on
and
so
forth.
I.
E
C
A
E
G
G
L
L
They're,
like
I
wish,
this
is
there's
some
there's
some
of
these
topics
that
I
just
wish.
We
had
more
like
there's
their
specific
data
questions
that
I
would
have
that
would
like
make
that
I
feel
like
would
drive
the
answer,
but
like
poring,
through
the
data
to
gather
them
just
takes
a
long
time
and
it's
time
that
I
personally
do
not
have,
but
the
questions
specifically
that
that
come
to
mind
here
are
like
so
we
had.
L
We
had
it
at
one
reviewer
per
PR
and
when
we
had
it
at
one
reviewer
per
PR,
we
they
was.
It
was
their.
What
like,
there
was
certain
features
that
we
didn't
have
before,
so
we
have
vacation
status
and
stops
now
that
we
didn't
have
before,
but
we
were
finding
response
times
really
low
and
contributors
didn't
know
how
to
get
attention
to
their
PR.
If
that
one
person
was
not
responding.
L
So
then
that
that
is
literally
the
reason
why
we
flipped
it
up
to
two,
because
then
there
were
do
people
that
they
could
pain
and
the
likelihood
of
like
them.
You
know,
acts
pinging,
two
different
people
and
neither
of
them
like
it
just
increased
the
chances
that
somebody
would
respond
when
they're
like
hey.
Why
is
it
might
be
air
getting
attention?
I.
L
Think
like
to
me,
so
this
were
like
a
company
if
Cooper,
if
kubernetes
was
a
company,
I
would
be
telling
all
my
employees
that
hey
you
need
to
what
you
need
to
take
ownership
if
you're
assigned
to
something,
even
if
like
there's
two
people
assigned,
if
you
want
assign
yourself
from
it,
you
can't
just
unassign
yourself
and
leave
it
be.
You
need
to
like
make
sure
that
somebody
owns
the
particular
thing
that
you
got
assigned
to
it's
tougher
and
open-source.
L
L
And
it
limits
it
limits
from
the
contributor
side,
then
you
just
have
one
person
to
pay
and
if
that
person
isn't
responsive
like
getting
responses
on
PRS
is
like
it's
still
a
problem.
I
just
don't
know
why,
and
I
can
definitely
like
see
that
as
a
problem,
but
I
don't
know
if
this
particular
change
will
have
a
positive
effect
or
negative
effect.
I
just
don't
have
that
enough
enough
data
numbers
so.
G
Why
don't
we
use
the
contributor
summit
to
our
advantage
here,
like
I,
feel
like
every
conversation
that
we
have
gotten
in
over
the
last
year?
That's
project
wide
has
been
hell
and
I
want
to
fix
that,
and
because
I
feel
like
we're
missing
out
on
amazing
opportunities
to
have
streamlined
services,
because
everybody
just
does
like
a
thing
and
then
also
like
the
bots
and
stuff,
don't
necessarily
talk
to
their
thing
or
like
whatever
it
is
right.
So
why
can't?
G
J
L
G
G
G
Hop
is
I,
want
us
to
be
able
to
get
to
consensus
quicker
for
project-wide
things
like
this,
and
we
have
these
events
like
these
contributor
summits,
where
we
all
get
together,
and
we
can
make
just
that.
We
can
have
discussions.
That
would
lead
us
to
consensus
faster
or
at
least
get
everybody
on
the
same
page
with
us
and.
L
I,
don't
I
don't
feel
like
this
issue
is
a
problem
of
consensus.
There
are
other
issues
where
consensus
and
reaching
consensus
on
a
particular
topic
is
a
problem.
This
one
in
particular,
I,
don't
feel
like
is
a
consensus
issue
if
we
felt
like
literally
if
we
felt
it's
contributor
experience,
but
this
was
like
a
positive
change
and
we
knew
that
this
is
going
to
be
positive
change
and
we
gave
it
a
thumbs
up
that
it
was
going
to
be
a
positive
change.
I
can
have
this
out
next
week
and.
G
I'm
asking:
how
do
we
get
there
like?
How
do
we
get
there
like,
because
I
seemed
and
I'm
using
this?
As
just
an
example
like
this
is
like
only
an
example.
So
that's
why
that's
where
the
jump
is
I'm,
saying
that
I
see
this
type
of
thing
come
forward
a
lot
and
like
our
our
response
is
usually
oh,
that's
a
project.
Why
change?
We
would
need
to
gather
so
much
consensus.
L
Don't
we
don't,
but
the
Paris
I
disagree,
but
but
seeing
that
this
lacks
is
consensus.
I
think
the
thing
that
this
lacks
is
data
like
I
literally
if
this
was
if
this
was
just
like,
if
I
was
King,
Christophe
and
I
was
wearing
a
crown,
I
could
just
make
the
vision.
I
literally,
would
not
know
which
decision
to
make
do
we
go
with
two
or
one?
It's
no
I,
don't
think
like
it's
a
gathering
consent
of
the
body.
L
L
G
L
So
for
this,
for
this
particular
issue,
I
would
the
data
that
I
would
be
trying
to
look
for
is
like
there's
two
ways
to
approaches.
It
would
either
be
number
one
we
do.
We
have
a
historical
reference
point
of
data
to
look
for
in
this
particular
case.
We
were
previously
at
one:
that's
not
like
one
reviewer
one
assignee,
and
then
we
switched
it
up
to
two.
L
If
we
look
at
the
data
of
that
point
in
time
which
I
was
like
god,
it's
probably
like
two
years
ago,
if
we
looked
at
the
data
at
that
point
in
time
and
see
like
did
changing
it
from
one
to
have
a
positive
effect,
in
particular
the
time
to
first
response
on
on
upon
a
PR.
If
that
improved
after
that
change,
then
I'd
be
reluctant
to
go
back
to
one.
If
there
was
no
change
or
it
worsened,
then
I'd
be
very
open
to
going
going
from
two
to
one
now,
the
other
way
to
approach.
L
G
That's
why
I'm
a
fan
of
talking
about
this
at
the
contributor
summit,
because
we
I
want
other
people
to
know
how
we
make
this?
How
we
make
these
decisions
like
this
is
the
important
piece,
because
we
tell
people
whoa
or
we
don't
tell
them
anything
at
all
and
then
and
then
it
kind
of
leaves
people
hanging
and
feeling
unheard.
So
that's
why
I
feel
like
if
we
can
at
least
describe
this
and
describe
like
what
they
should
come
with
when
they're
making
this
kind
of
a
suggested
change
like
historical
data,
etc.
G
G
Idea
of
this
idea
of
like
SIG's,
just
not
being
in
the
loop
with
us,
with
changes
to
constantly
comes
up
and
like
that's
what
I'm,
like
I'm,
trying
to
figure
out
how
we
can
use
this
contributor
summited
to
answer
all
of
these
kind
of
like
how
can
we
make
project
wide
changes
without
either
getting
people
super
upset
because
they
didn't
hear
about
it
or
getting
people
super
upset
because
we
moved
so
slow
on
their
problems.
So
it's
like.
How
can
we
need
folks
in
the
middle
right?
G
So
that's
why
I'm
like
trying
to
creatively
think
about
this
contrived
exception
that
we
could
do
that's
like
a
discussion
session.
I
would
be
facilitated
and
our
end
goal
here
would
be
getting
maybe
even
like
SIG's
to
create,
like
contra
Beck's
liaison
roles
within
their
SIG's,
so
that
they
can
watch
for
breaking
changes
and
watch
for
project
wide
changes
and
stuff
like
that
to
where
we
could
like
communicate
a
little
bit
better
as
well.
So
that's
where
I'm
going
like
I
used
this
as
an
ample,
because
this
has
been
on
my
mind
like
this.
G
G
So
that's
that's
where
I
am
right
now!
No,
we
don't
need.
No.
We
don't
need
any
answer
on
this
at
this
point
in
time,
but
like
in
the
next
week
or
so,
I'm
gonna
try
to
figure
out
what
we
can
serve
to
serve
from
like
a
session
perspective.
That
would
be
valuable,
like
I'm.
Thinking
like
like
the
perfect
title,
would
be
something
like
why
we
can't
have
nice
things.
Project
wide.
L
Is
we
did
something
similar
to
this
in
Seattle,
and
the
people
in
the
room
were
a
lot
of
like
new
contributors,
people
without
opinions,
because
the
session
was
Co
scheduled
at
the
same
time
as
like
Network
and
node
and
architecture
all
at
the
same
time,
so
anybody
who
actually
had
an
opinion
and
the
audience
that
I
would
really
like
the
audience.
That
would
really
be
helpful.
L
They're,
they're
people
like
say
your
contributors
fig,
leaves
save
chairs
like
those
that
group
of
folks,
that's
all
like
spread
far
and
wide
at
that
point
in
time
like
I,
don't,
but
those
are
the
people.
Who's
like
opinions
like
I
need
to
be
able
to
go
and
like
in
that
context,
go
to
like
they
know
it
would
be
like
hey
sig
know.
What
can
we
do
to
help
you
be
more
responsive?
How
can
we
make
the
boss
help?
L
L
The
other
thing
that's
been
on
my
mind
and
like
we're
running
out
of
time,
but
I
want
to
briefly
bring
up.
So
there
was
like
there
was
a
couple
discussions
at
a
couple,
different
forums
or
is
on
slack
on
Twitter,
about
trout,
test
failures,
emails
and
they
are.
That
is
an
issue.
For
example,
we
lack
consensus
on
some
people
really
like
them
and
they're
critical
to
their
workflow,
others,
eight
to
them
with
a
passion,
and
there
are
good
arguments
on
either
side
for
something
like
that.
L
What
I
want
to
do
and
like
they'd,
be
the
kind
of
a
next
step
there
for
me,
I
would
like
to
hear
feedback
to
the
contribute.
Something,
but
I
also
have
some
questions.
I
want
to
get
on
to
the
contributor
survey
and
I
need
to
make
a
point
of
lighting
those
questions
ASAP,
so
we
can
get
them
on
to
the
survey.
But
I
replied
on
that
survey
issue
last
week.
L
They're,
like
hey,
there's
some
specific
questions
that
I
want
to
craft
on
that
survey
about
how
people
are
interacting
with
their
automation,
because
then
I
can
take
that
data
as
like
an
authority
of
mandate
to
be
like
okay,
so
the
people
who
reply
it
said
this
and
if
you
didn't
reply
too
bad,
so
sad
I
can't
take
your
opinion
into
effect.
If
you
didn't
use
your
opportunity
to
actually
make
your
voice
heard,
this
is
what
the
people
want.
So,
let's
drive
some
changes
forward
in
that
direction.
L
G
G
H
I
did
there's
some
data
about
the
time
to
first
engagement,
the
second
one
yeah
that
one's
a
little
bit
easier
to
read
the
one
with
the
quarters.
So
Christoph
I,
don't
know
if
that
gives
you
some
data
that
you
were
interested
in.
It
doesn't
look
like.
There
was
much
change
a
couple
of
years
ago,
but
I
don't
know
exactly
when
you
made
the
change.
L
G
I
G
So
I
wanted
to
talk
about
this.
I
am
gonna,
start
the
build
from
home,
so
retro
that
we
had
and
also
the
questions
that
we
did
last
time
and
then
what
I'm
gonna
do
is
assign
owners
for
questions
not
because
they
need
an
owner
of
her
question,
but
just
because
they
need
at
least
an
eyeball
per
question
like
Josh
has
some
stuff
that
he
wanted
to
change
for
the
community
meeting
discussion
and
then
Christoph,
as
Christoph
just
mentioned,
had
some
things
for
for
tests,
infra
and
Frau
and
stuff.
G
Like
that,
the
list
of
questions
that
we
asked
or
right
here
conveniently
the
full
question
list,
is
right
here:
I'd.
Imagine
that
look.
So
we
had
32
questions
so
I'm
gonna
try
to
get
it
down
to
less
than
25
this
time,
and
also
I
would
guess,
like
half
of
them
will
probably
stay
because
at
least
half
of
them
are
a
lot
of
demographic
stuff.
So
we
should
start
to
collect
trends
which
will
be
nice
especially
like
does
your
employer
support
your
upstream
adventures
stuff,
like
that?
G
The
things
that
I
wanted
to
talk
about,
like
in
the
next
five
minutes
really
quickly
are
the
things
that
I
talk
about
our
priorities
like
what
we're
discussing
right
now
and
then,
like
some
of
this
tolling
stuff.
Like
do
you
find
the
tooling
useful
like?
Should
we
ask
those
kinds
of
questions
in
the
retro
in
the
issue
itself
back
here?
G
Some
of
those
questions
ended
up
actually
being
the
weakest
from
a
response
section
and
when
I
say
weakest,
I
mean
there
wasn't
a
clear
trend,
so
I'm
wondering
if
that
means
we
need
to
like
reword
the
question
or
if
that
just
means
everybody
has
beef
to
pick
with
every
one
of
those
BOTS
or
if
everybody
loves
everything
so
like
that's
according
to.
According
to
the
data,
the
data
analysts
that
I
had
look
at
it.
G
That's
what
they
said
about
some
of
the
questions
they
were
like:
they
either
love
it
hate
it
or
everybody
loves
something
or
hate
something
different,
so
yeah
yeah
and
that's
crystal
shaking
his
head
because,
like
that's
kind
of
the
responses
that
we
get
usually
as
well,
but
like
okay,
like
if
that's
the
case,
then
we
at
least
need
to
like
say
that.
Oh
let's
say
that
publicly,
like
hey
our
community,
can't
come
to
a
consensus
on
this
very
issue,
but.
L
And
that's
why
I,
like
the
questions
that
I
want
to
craft
around,
that
section
like
I
I,
will
take
responsibility
for
all
the
tooling
type
questions
and
like
github
type
questions
I'll
take
owner
and
responsibility
for
those,
because
I
want
to
word
them
very
specifically,
so
that
hopefully
we
can
get
like
a
clear
direction
out
of
it.
Okay,.
G
G
The
reason
why
I'm
asking
is
because
we
could
legitimately
have
the
data
by
contributor
summit
and
I
could
be
to
get
it
analyzed
for
us
by
contributor
summit.
So
then
we
could
not
only
have
like
data,
that's
driving
the
discussions,
but
then
we
can
also
have
a
like
a
sort
of
a
like
level
set
everybody
about
our
contributor
base
in
the
very
beginning
of
the
summit
itself,
like
in
the
Welcome,
which
is
something
that
I
was
super
interested
in.
L
L
I'm,
probably
like
existing
questions
that
are
in
there,
I
will
probably
just
drop
completely
and
rewrite,
and
I
may
have
up
to
like
I
am
maybe
five
or
six
total,
because
I
also
need
some
specific
about
proud
testing
comments.
But
I
will
keep
it
between
three
to
six
questions
that
I
want
to
ask
and
the.
L
But
so
the
what
the
love
and
concerns
I
was
going
to
bring
up
was
we,
as
in
contrive
X,
should
make
sure
that
we
are
courting
very
specifically
with
the
elections
team
that
we
that
our
communication,
but
we
at
least
think
about
how
the
communications
go
out
like
art.
Will
there
be
any
overlap
between
the
two
like
the
election
period,
and
this
would
die.
L
Either
boost
our
responsiveness
of
the
contributor
survey,
or
would
it
essentially
like
drown
out
if
there's
a
lot
of
communication
like
I,
don't
know
what
the
answers
are,
but
at
least
we
should
think
about
a
coordinate
between
those
two
groups
that
we
are
sending
out
like
two
separate
things
to
our
entire
contributor
base.
We.
G
G
Right
this
is
the
high
time
for
contributor
news,
like
I,
am
I'm
all
over
this
eyeball
stuff,
my
PR,
my
PR
brains
on
it
so
they're
like
I,
know
it's
10:30
I
want
to
get
like
I
want
to
get
this
one
question
out
of
the
way
that
this
is
where
the
priority
comes
in
I'll
show
you
a
put
on.
It
is
station.
G
Yes,
21.
Some
of
the
major
projects
were
working
on
a
listed
below
check
one
that
is
the
most
important
to
you.
This
is
the
one
where
we
actually
had
very
good
data
on
it,
and
this
is
where
we
can
really
start
to
prioritize
where
we
need
to
put
resources
on
and
even
help
with
triage,
like
getting
priority
stuff
like
done,
because
this
is
again
what
people
think
we
should
be
doing
and
like
getting
like.
Obviously,
we
know
what
we
need
to
be
doing,
so
this
is
kind
of
that
like
meet
in
the
middle
question.