►
From YouTube: Kubernetes Contributor Experience SIG 20180808
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
B
First
of
all,
we
ran
out
of
Stig's,
so
I
went
ahead
and
repopulated
what
the
schedule
should
look
like
through
the
end
of
October
as
far
as
SIG's
going
and
then
over
here
on
column
G,
we
have
Bank
blank
slots
for
people
to
be
hosts.
So,
if
want
to
host,
please
fill
in
your
name.
We
at
least
need
a
host
for
next
week
and
then
Paris
goes
and
then
we
have
blank
closed.
B
So,
if
you
can
host,
if
you
don't
know
how
to
host
you
can
shadow
being
a
host
or
I
can
show
you
how
to
do
it.
It's
it's
pretty
simple
and
as
far
as
the
number
of
SIG's
that
are
going
because
we
keep
moving
around.
Sometimes
some
can't
go
on
a
certain
week.
I
move
around
we've
been
moving
around
SIG's
on
when
they
actually
give
their
updates
and
stuff
like
that.
I
am
pretty
sure.
B
I
got
every
single
snag
in
the
next
cycle
and
then
I
left
two
slots
and
stay
empty
just
in
case
in
case
a
sig
needs
to
postpone
or
something
like
that
we
can
move
them
to
a
slot.
I
would
really
appreciate,
if
column,
D
and
F
for
the
next
meetings.
If
someone
can
just
spot
check
that
make
sure
I
didn't
miss
a
sig
I'm,
like
pretty
sure
I
didn't
miss
this
thing
and.
B
He
WS
is
actually
going
today.
Oh
yes,
yes,
oh
yeah,
sorry
yeah!
We
had
a
demo
drop,
so
we
decided
to
smart
an
AWS
right
there,
so
that
kind
of
worked
out
perfectly
I'm.
Sorry,
that's
not
reflected
here
and
that's
that's
pretty
much
for
the
recurring
thing.
So
please
sign
up
for
host.
If
you
have
interesting
people
that
would
be
great
to
invite
us
hosts,
please
let
me
know
we're
gonna
always
do
that.
I
like
to
get
cool
people
in
and
out
who
can
host.
A
A
No
okay,
great,
it
looks
like
George,
you
might
have
the
next
one
right,
yes,
contributor
bored
bike
shed
extravaganza.
Yes,.
B
So
this
is
the
contributor
box
mailing
list
about
having
like
a
contributor
job
board
and
then
everyone's
like.
We
can't
call
it
a
job
board,
and
now
we
got
a
bunch
of
names
and
really
the
the
name
is
the
only
thing
I
have
blocking
me.
I've
made
a
perma
type,
a
discus
forum,
sub
forum
with,
like
templates
or
SIG's
looking
for
volunteers,
volunteers,
looking
for
SIG's
I
got
a
cool
picture
and
all
that
stuff,
so
really
all
I
need
is
a
main,
and
then
we
can
do
it.
D
G
H
H
Thing
about
that,
the
thing
about
the
name
is
I'd
want
to
kind
of
have
at
least
a
you
know:
80
85
%
settled
name
before
we
start
advertising
and
wide.
So
people
know
what
to
call
it
before
we
like
talked
about
in
the
community
meeting,
or
things
like
that.
So
I
think
poll
would
probably
be
a
good
thing
like
if
we
can
just
toss
out
a
quick
poll
with
a
bunch
of
suggestions
and
whichever
one
reaches
the
top,
then
that's
the
name.
We
go
with
I
I.
B
H
J
Are
soo,
as
we've
discussed?
If
you
are
a
few
weeks
ago,
one
of
the
poorest
meetings
would
like
to
completely
sunset:
existing
github,
github
box,
medalists
and
so
on.
So
we
have
removed
that
part
from
this
equation
procedure,
but
we
still
have
some
tails
on
github
and
in
the
mineralogists.
So
I've
drafted
a
brief
announcement
to
the
community.
So
I'd
like
you
to
take
a
look
at
it
and
if
it
looks
good
I'd
like
to
push
to
Cuban
at
his
death
tomorrow
and
announce
it
repeated
at
a
cabinet.
As
committee
meeting.
J
D
My
concern
with
the
leading
the
google
groups
is
that
if
people
were
following
the
google
group,
if
they
were
following
the
account
creation
process
like
that,
google
group
email
address
is
the
only
recovery
email
address
available
for
those
kids
other
accounts.
So
if
we
end
up
deleting
the
google
groups
without
the
github
accounts
being
deleted,
but
they're
they're
calling
their
zombies,
and
maybe
we
don't
care,
that's
fine
that
could
be
to
try
this.
D
Then
we
don't
care
about,
but,
like
I
tried,
reaching
out
to
sake
scalability,
for
example,
because
I
have
the
analyst
to
their
github
accounts
and
I.
It's
been
three
weeks
and
I
still
actually
haven't
gotten
a
response
back
so
I'm,
assuming
they
don't
care
that
much
and
I
could
just
get
rid
of
it.
But
I
see
Matt
has
his
hand
out
well.
K
D
Like
I
mean
yeah,
I
went
back
as
a
human
and
looked
at
all
the
Google
Groups
for
state
testing
or
gone
right.
I
got
rid
of
them
the
contra
to
the
mere
accounts,
because
I
went
back
and
looked
and
they're
just
like
they
hold
all
the
github
notifications
that
were
sent
to
those
teams
that
nobody's
bothered
looking
at.
J
J
K
K
D
Okay,
so,
like
kind
of
I
just
feel
like
deleting
the
Google
blogger
factor,
we
might
be
aggressive
and
turned
back
from
a
human,
but
to
help
incentivize
people
and
remind
people
that
those
things
are
probably
useless
and
will
go
away.
I'm
gonna,
open
up
the
pr2,
remove
all
reference
to
those
Google
Groups
from
every
six
readme,
so
I'm,
not
deleting
the
Google
Groups
I'm,
just
making
sure
there
aren't
dead
links
that
go
to
nowhere
so,
for
example,
so
yeah
this
page.
D
Those
actually
lists
that
you
have
all
these
Google
Groups,
but
when
I
click
through
I
get
a
not
found
and
it's
kind
of
a
pain
to
script.
This,
because
I'd
need
an
API
to
ask
whether
or
not
the
Google
group
exists,
and
since
this
is
the
paid
version
of
G
suite
I,
don't
have
an
API,
so
I'm
just
gonna
blank.
It
remove
all
links
to
the
Google
groups
from
all
SIG's
read
these
okay
I'll
have
a
PR
out
later.
D
J
D
J
A
L
Like
listening
and
everyone,
small,
though
worries
so
the
share
screen.
L
A
L
Know
I
just
searched
for
was
a
writing
and
replication
controller
respect.
Just
is
you
know,
I
found
that
random
one.
These
are
the
results
that
I
came
back
and
so
what
I
did?
Was
it
like
three
formatted
the
text
to
look
kind
of
similar
to
what
it
looked
like
on
the
on
the
page?
So,
like
all
the
little
code
blocks
or
code
blocks,
all
the
links
are
links
and
stuff
and
you
can
expand
it
out
and
when
you,
when
somebody
actually
goes
through
click
on
it,
then
screen.
L
L
Some
reason
zoom
makes
my
whole
lot
types
or
my
whole
lot,
tough
stuff,
so
when
you
actually
click
on
it,
instead
of
going
just
to
the
dock,
it
kind
of
goes
to
that
section
within
the
dock.
To
make
sure
that
you
know
people
are
kind
of
go
to
the
right
place.
So
that's
the
big
one.
This
was
only
deployed
yesterday,
so
we'll
see
how
it
goes.
L
L
L
Feedback
but
there's
not
a
lot
of
negative
feedback
either,
so
that's
kind
of
bad,
so
yeah,
so
I'm
thinking,
I'm
figuring
out
the
graphs
and
stuff
today
and
then
the
other
thing
that
I
spend
a
lot
of
time
in
last
week
was
again
relevance.
Making
sure
that,
like
the
answers,
are
as
relevant
as
possible,
working
on
a
completely
new
model
with
like
a
lot
more
crazier
machine
learning,
style
stuff
that
you
know
come
out
some
some
point
soon.
B
So
I
I,
don't
I,
don't
think
I've
synched
with
you
Nawab
lad,
but
have
you
noticed
I
know
the
graphs
are
wrong,
as
you
said,
but
have
you
noticed
any
uptick
anything
since
you've
been
indexing?
The
Stack
Overflow
questions
for
a
while.
Now,
yes,
yeah.
L
So
I
mean
we're
definitely
providing
more
answers.
I
think
we're
able
to
provide
more
answers.
Oh
Stack,
Overflow
questions
they're,
definitely
like
you
know,
we're
definitely
showing
stuff
more
often
and
we're
able
to
display
more
stuff
again,
it's
hard.
It's
because
I
have
to
figure
out
how
far
back
the
metrics
go,
they're
wrong
and
also
I
recently
within
the
last,
like
maybe
two
weeks,
that
I
start
actually
collecting,
like
the
actual
proposed
answers
that
we
give
and
like
things
like
the
you
know
what
what
somebody
asked.
What
was
the?
L
L
Okay
yeah:
this
is
helpful
in
figuring
out,
what's
wrong
with
the
graphs
and
stuff,
but
yeah
I'm.
Definitely
seeing
more
like
answers.
I'm,
seeing
that,
like
a
lot
of
the
proposed
answers,
we
give
our
Stack
Overflow
answers
and
a
lot
of
the
ones
that
you
know
that
people
say
is
helpful
or
the
answers.
Their
question
does
come
from
Stack
Overflow.
L
You
mean,
what's
the
website
discussed,
not
the
slide
channel,
not
like
a
slack
channel
discussed.
So
yes,
I
was
like
I
was
looking
at
that,
like
once
discussed,
has
a
lot
more
kind
of
questions
and
answers
right
now,
it's
it's
a
there's
like
some
categories
of
like
general
discussion,
which
I
kind
of
don't
you
know,
doesn't
make
sense
to
pull
in.
But
yes,
I
want
to
a
pull
the
those
questions
out
of
to
like
index,
to
show
slack
users,
and
then
I
actually
have
never
looked
at
like
to
discuss.
L
B
E
B
Yeah
I
think
we'd
need.
We
need
the
metrics
for
that
right,
like
I.
Think,
like
you
mentioned
earlier,
with
the
amount
of
people
that
are
growing
in
users
so
far,
there's
43,000
and
they're
somewhere,
like
I,
think
we
should
perhaps
either
pick
I,
don't
know
like
a.
However
many
people
chose
this
answer
help
me
or
something
maybe
there's
like
a
gold
metric
that
we
can
pick
there
without
you
know,
without
making
the
metric
go.
Oh,
oh.
L
A
L
B
L
B
A
L
So
I
mean
in
most
of
the
lake,
if
you
break
down
those
conversations
as
well
a
lot
of
it
or
a
lot
of
it
isn't
like
a
question.
A
lot
of
it
is
either
responses
or
potential
responses
to
things
so
like
one
of
it
like
the
thing
that
this
thing
first
does
is
it
takes
a
big
block
of
conversation
and
or
like
a
big
block
of
text
and
converts
it
into
like
conversations
where
it's
like
back
and
forth.
So
most
of
his
messages
are
not
necessarily
like
hey.
This
is
my
question.
B
G
L
That,
like
once
it's
once
it's
a
lot
more
like
better
at
like
giving
you
more
successful
answers
like
once.
We
actually
sure
that,
like
you
know
at
least
50%
of
the
time
which,
like
a
very
low
number
but
at
least
like
a
large
number
of
times
that
when
we
offer
a
solution-
or
we
offer
an
answer-
it's
actually
the
right
answer,
or
it's
most
likely
going
to
be
considered
a
good
answer
or
a
helpful
answer.
A
J
Yeah,
so
we
had
enough
requests
from
the
communities
community
and
some
concerns.
Did
we
don't
have
an
official
community
provided
slide
deck
for
for
the
cabinet,
isolated
presentations
like
the
general
updates
in
the
community
or
your
presentations
that
you
are
making
at
a
different
events,
so
Alex
from
CMC
FM
grateful
for
her?
She
created
the
draft
of
Houck
and
a
slide
deck
template
may
look
like
in
the
late
years,
so
it's
reviewed.
J
A
J
So
feel,
free
to
command
a
slide
deck
itself.
I
should
be
open
for
commands.
If
not
just
let
me
know
feel
free
to
ping
me
Derek,
don't
slack
on
the
mail.
Okay,.
J
F
I
However,
you're
gonna
have
to
take
it
away
if
all
of
a
sudden
there
was
loud
love
noise
because
their
kitchens
being
worked
on.
So
after
talking
with
George
and
Bob,
we
were
looking
at
trying
to
automate
a
bunch
of
the
like
social
media
accounts
and
populate
more
information
and
to
discuss.
So
we
have
all
these
different
sources
of
truth,
aggregating
them
into
discuss
and
then
being
able
to
say
certain
things,
get
posted
to
say
slack
or
say,
Twitter.
I
We've
kind
of
demoed
that
well
didn't
demo,
but
showed
last
week
we
were
using
if
this
than
that,
as
a
proof
of
concept
to
Paris
and
I
believe
Chris
short
and
someone
else
for
like
that's
bad
and
it
was,
it
was
a
pilot.
So
whatever
then,
we
started
playing
with
zapier
and
rebuilt
everything
from
if
this
than
that
into
zapier,
and
that
was
very,
very
easy
and
also,
instead
of
having
to
create
multiple
rules
to
branch
out,
you
could
have
one
rule
to
do.
I
You
know
forking
essentially,
so
we
set
that
up
almost
right
after
that
meeting
and
it's
been
running
for
the
last
week.
Unfortunately,
it's
been
posting
under
me,
so
my
face
got
slapped
all
over
disgust
and
George
was
very,
very
happy
about
it,
but
it
looks
like
it's
a
success,
so
I
would
like
feedback
on
that.
If
there
other
sources
of
truth
to
auto
post
things,
please
please
let
us
know
we're
actually
setting
it
up.
I
H
So
I
can
find
my
mute
button
just
wanted
to
give
a
quick
update
on
the
stuff
that
we're
doing
over
a
new
github
administration
team.
So
we've
now
formed
all
the
people
that
are
members
of
the
team
are
now
owners
and
all
the
orgs
and
as
of
about
ten
minutes
ago,
or
so,
we've
now
completed
our
audit
and
have
removed
everyone
else
that
may
have
those
kind
of
root
level
privileges
in
a
legacy
kind
of
scenario.
So
now
we
have
unlike
an
actual
team
that
is
handling
all
the
github
stuff,
so
that
is
very
good.
H
Considering
there's
been
a
couple
different
news
stories
and
recently
that
have
gone
over
the
internet,
around
compromises
in
github
and
with
github
tokens
and
all
that
kind
of
stuff.
So
we
were
we're
now
in
a
in
a
bit
of
a
better
place,
as
we're
kind
of
we
can
now
audit
and
maintain
all
of
our
github
orgs
in
the
same
way.
H
In
particular,
I'm
looking
to
the
next
we'll
be
getting
issued,
templates
I've
got
actually
a
PR
out
right
now.
We're
gonna
get
some
issue
templates
and
some
processes
in
place
so
that
if
people
need
changes
like
hey,
I
want
to
I
need
a
new
repo,
oh
delta
c
Cabrini's
org
repo,
which
is
kind
of,
are
going
to
be
our
meta
repo
for
the
new
tooling
and
the
process
at
this
point
that
we're
looking
at
doing
is
people
opening
issues
against
that
repo
and
then
being
able
to.
H
So
that
we
can
kind
of
track
who's
handling,
what
executing
on
requests
and
getting
the
information
that
we
need
to
be
able
to
do
those
things.
So
this
will
be
like
policies
and
procedures
stuff
that
that's
kind
of
the
next
thing
that
we're
working
on
I'll
drop
a
link
out
to
the
the
PR
that
I
have
open
into
the
into
the
meeting
notes.
C
A
C
C
D
C
D
So
if
this
is
an
automation
problem,
the
escalation
policy
is
you
go
one
issue
and
then
you
reach
out
to
folks
in
tests
infra
and
if
they're
not
responding
there,
you
reach
out
they're
testing
off
the
table.
There's
a
peanut.
Maybe
this
has
emerged
yet
but
I
know
I've
reviewed
a
PR
that
Christophe
put
together
that
actually
documented
these
policies,
for
how
do
you
contact
us
and
if
you
need
to
escalate
how?
Where
do
you
do
that.
H
Yeah
that
one
hasn't
merged
yet
either
I
will
put
that
in
the
the
meeting
notes
as
well,
but
it
does
specifically
split
out
automation
and
call
that
out
Josh,
because
there
is
a
different
path
for
that.
The
github
administration
team
is
going
to
be
more
kind
of
like
the
day-to-day
github
tasks,
whereas
automation
actually
has
its
own
thing.
There's
testing
ops
in
flack
and
there
is
the
testing
for
on-call.
D
I
also
think
for
what
it's
worth
this
might
be
worth
talking
about.
The
community
meeting
tomorrow
during
an
update,
especially
since,
like
I,
know,
we
just
kind
of
had
a
grand
purge
of
people
with
owner
powers
on
a
whole.
The
github
works
it
like
could
to
remind
people
now
that
that
happened.
Here's
who
you
come
contact
and
here's
how
you
contact
us
I.
H
D
F
Sure
all
you
Bob,
okay,
the
repos
there
things
been
migrated
over
to
it,
merged
a
couple
things
in
over
the
weekend.
So
a
like
squares
posts,
all
that
go
there
to
where
it's
just
waiting
for
the
unit's
name
to
be
then
pointed
at
the
net.
It's
a
cname
entry
for
that
instance,
the
net
LeFay
address.
Also
there
was
a
little
bit
of
confusion.
I
know
I
think
it
was
like
last
Friday
I,
don't
Christopher!
You
had
me
mentioning
like
setting
stuff
up
with
the
Kate
community.
Repos
ie
people
get
PR
previews.
F
Sorry
about
that
was
like
a
complete.
You
know,
out-of-band
conversation
that
didn't
get
bubbled
back.
It's
not
gonna
happen
at
this
point.
No
big
deal
right
now.
We're
thinking
for
as
far
as
like
frequency
of
updating
the
site
is
enough.
I.
You
can
actually
tell
it
to
you
like
when
you
want
to
update
so
I
can
have
it.
Essentially
you
do
a
build,
no
nightly
or
something
like
that,
so
the
so
I'll
just
be
generated.
Then
that's
it
really.
There's
the
much
to
say
about
it.
Remember
anything
George.
B
A
B
E
Yes,
now
that
I'm
stationary,
thank
you
for
the
patience,
so
first
things.
First,
we're
gonna
send
out
a
global
meetings
poll.
What
this
means
is
that
we've
heard
from
several
contributors
that
are
outside
of
the
continental
United
States
and
they
would
like
a
more
suitable
time.
The
docs
team
is
doing
it.
Other
stakes:
do
it
know,
does
it
so?
E
What
we're
gonna
do
is
throw
out
a
poll
to
see
what
times
would
kind
of
work
best
for
who
and
when
we're
thinking
that
it's
either
going
to
be
very
early
morning
of
West
Coast
hours
so
somewhere
between
7:00
a.m.
and
8:30
a.m.
or
very
late
at
night
for
West
Coast
hours,
which
would
be
7
p.m.
to
something
like
10:00
p.m.
and
then
this
would
replace
one
of
the
weekly
meetings.
So
we
would
not
have
two
weekly
meetings.
E
E
E
E
So
the
good
news
is
that
we
have
some
other
communities
that
we
can
talk
to
and
guide
us
through
this
process,
but
what
I
need
the
most
help
on
is
the
discovery
aspects
in
the
issue
which
I'll
link
in
a
second
has
a
document
that
is
a
spreadsheet
of
like
what
it
is
why
it
is
who
owns
it,
etc.
This
also
is
going
to
include
like
who
owns
the
calendar
invites
so
that
we
can
get
a
sense
of
like
how
we
can
centralize
the
calendar
service.
E
The
calendar
service
is
going
to
ultimately
feed
into
the
contributor
site
and
the
community
site.
So
a
lot
of
this
is
p0
stuff
that
we're
talking
about
that.
We
need
to
figure
out.
First,
I
am
gonna
slap,
a
help
on
it
issue.
On
this
end,
a
good
first
time
issue
on
this
as
I
will
welcome
new
contributors
through
how
to
get
this
information.
E
So
if
there's
anybody
on
the
line
that
would
like
to
help
with
this
project,
please
let
me
know
it's
very
like
the
the
I,
don't
want
to
say
it's
very
simple
but
like,
for
instance,
they
get
a
link
to
the
blog.
You
can
just
google
it
etc.
So
it's
not
like
you
have
to
if
we
have
to
no
code
or
anything
like
that
for
this,
so
that
is
it
I
think
for
the
communication
and
collaboration
platform
at
least
what
I
wanted
to
say
right
now.
Does
anybody
have
any
comments
that
they
want
to
add
on.
E
I
need
process
help
die
early
for
the
101
hour
as
well
as
group
mentoring.
We
are
attempting
to
automate
these
things
as
well,
but
we
realized
that
there's
a
lot
of
process
changes
that
need
to
have
and
I'm
extremely
over
committed
right
now.
So
this
is
my
80th
call
for
help
in
regards
to
mentoring.
If
no
one
wants
to
that's
fine,
it's
just
getting
reprioritized
it's
something
like
t2,
so
yeah,
that's
my
pretty
much.
My
last
call
for
help
did.
E
C
E
I
mean
like
I'll,
give
you
a
very
specific
example
for
the
one-on-one
hour.
A
lot
of
the
interest
air
has
been
with
code
based
tours
as
well
as
parent
programming,
and
we
need
to
set
a
standard
for
how
people
are
pair
programming
or
at
least
give
them
limited
options
so
that
mentors
aren't
fiddling
around
with
how
they're
actually
doing
a
pair
of
program
with
someone.
E
So
we
should
give
recommendations
as
to
programs
that
they
can
use,
and
things
like
that,
because
the
whole
idea
with
this
is
to
save
people,
time
and
energy
and
reduce
the
burden
that
they
feel
so
that's
a
process,
improvement
that
needs
to
change
and,
ultimately,
documentation.
That
needs
to
be
written
and
research.
That
needs
to
be
done
on
pair
programming
tools
and
that's
from
a
retro
that
I
did
with
people
that
have
done
pair
programming
for
us
in
this
capacity
with
people
that
they
don't
know.
E
E
E
But
my
thoughts
here
are
still
with
the:
how
can
we
get
contributor
experience
related
news
to
SIG's
that
need
this
especially
process
changes
stuff
that
Chris
often
many
other
people
work
on,
and
we've
talked
about
this
idea
a
few
times
with
many
of
us
going
to
sig
meetings
or
other
sig
meetings
already
or
being
involved
in
multiple
SIG's.
So
we
could
get
something
like
official
on
paper
that
says
like.
Oh,
you
are
the
community's
liaison
for
say
testing.
E
You
are
the
community's
liaison
for
this
group,
and
that
means
we
know
we
have
some
kind
of
communication
funnel
into
those
groups
and
that
we
feel,
like
those
groups,
are
getting
the
information
that
they
need
from
us
so
that
they
don't.
We
don't
always
have
to
put
them
to
our
mailing
list
or
our
issue
log,
or
something
like
that.
This
isn't
necessarily
like
required,
or
anything
like
that.
It's
just
I
feel
like
for
me.
E
It
makes
me
sleep
better
at
night,
knowing
that
our
community,
our
micro
community
here,
has
a
voice
in
the
other
40
micro
communities
that
we
have
in
kubernetes.
So
questions
concerns
comments
about
that.
I
was
gonna,
throw
up
a
dreaded
spreadsheet
like
next
I
know.
Aaron
just
came
up
from
you.
If
he
heard
me
say
the
word
spreadsheet
was
like,
oh
god,
no,
like.
D
I'm
not
thrilled
with
the
idea
of
VA
songs
I
can
it
was
the
so
the
reasons
the
end
committee
has
it
is.
If
you
have
some
questions
related
to
steer
stuff,
you
have
people,
you
can
directly
ask
because
people
seem
to
be
afraid
to
ask
a
mailing
list.
Similarly,
there
are
things
where
we
need
to
go
chase
down
each
and
every
cig
and
make
sure
they
do
something
to
comply,
and
so
this
is
a
way
of
dividing
and
conquering
that
work.
D
D
The
otherwise,
like
good
liaison
thing
I
think
is
intended
primarily
for
us
to
solve
the
like,
so
they're,
not
sakes
problem.
We
have
the
same
problem,
though
yeah
that's
one
lame-o
I'm
putting
I'm
codifying
it
in
60
ml
and
it's
gonna
show
up
on
every
since
readme.
It's
not
approach
works
for
steering.
Maybe
you
can
follow
along
instead
of
yeah
red
sheep.
E
E
B
B
D
B
I
get
the
feeling
that
they're
getting
the
emails
and
they
know
they
just
like,
for
example,
they
saw
they're
like
man,
I,
don't
have
time
to
sit
there
and
delete
15
of
them
service
accounts,
whatever
I've
got
better
things
to
do
right,
like
I
suspect.
You
know,
and
this
is
not
based
on
any
data
right
but
like
we
do
mentioned
things
I
think
enough,
often
enough
on
dev
leads
and
the
community
meeting
that
I
suspect
them
that
you
know
people
are
just
too
busy
and
they're
making
that
judgment
in
their
head.
B
E
E
Stuff
I
feel
like
this
is
a
band
a
and
I
think
that's
how
steering
committee
is
looking
at
it
as
well,
but
it's
better
than
what
we
have
currently,
which
is
people
not
reading
emails
and
then
us
having
to
go
in
as
bad
actors
and
kill
their
zoom
meeting,
for
instance,
for
like
the
zoom
moderation
stuff.
So
that's
why
I
keep
going
back
to
this
idea
and,
like
I
said
every
single
one
of
us
I
mean
I'm.
E
Looking
at
all
your
faces
right
now,
every
single
one
of
us
goes
to
at
least
one
other
sig
meeting
a
week.
So
what
is
it
so
like
that's
kind
of
what
I
want
to
know
like
what
meeting?
Is
it
so
that
I
know
like
Oh,
Joe
I
know
Josh,
there's
a
note
every
week
so
like.
If
we
need
something
from
know,
then
I
can
be
like
Josh
help
me
out
here.
N
O
G
My
snarky
comment
about
labels
and
github
monitor
is
to
kind
of
remind
that,
at
least
in
another
place
on
sake,
release
or
the
release
team.
Specifically,
we've
chosen
explicitly
to
try
to
just
go
to
reaching
out
one
on
one
but
as
necessary,
and
there
may
be
it
scales
better
because
there's
it's
always
targeted
issues,
it's
not
a
broadcast.
We
need
to
tell
everybody
about
something.
H
D
So
George's
point
earlier
about,
like
I,
don't
know:
I,
don't
have
the
data
so
I'm
just
like
winging
it
here
like.
How
do
we
actually
just
I
would
try
to
be
mindful?
How
can
you
get
the
data
as
you're
interacting
it'd,
be
sort
of
like
I
want
to
get
a
thing
done?
How
can
I
collect
who's
actually
got
this
thing
done,
and
it
has
a
help
you
and
then
show
that
anyway,
we're
beating
a
dead
horse.
We
have
three
one
demo.
E
Well,
the
last
item
is
literally
gonna
be
30
seconds,
which
is
again,
I
have
not
lazily
put
the
link
in
the
gender,
but
I
will
still
collecting
survey
ideas,
question
ideas,
I
know,
Josh
is
out
of
the
few
etc
and
we
will
circle
back
with
this
verb
before
we
send
out
the
survey.
This
would
be
the
kubernetes
contributor
experience
survey.
Obviously,
questions
about
communication
platforms
and
collaboration
platforms
are
on
there,
but
also
our
processes
as
far
as
workflow
and
stuff
like
that
is
concerned.
E
I
technically
think
we're
pretty
decent
right
now.
I
just
haven't
heard
from
a
large
crew
of
people,
I
mean
not
large
crew,
but
I
haven't
heard
from
like
a
diverse
set
of
people.
I
mean
it's
only
been
like
four
of
us
and
this
crews
200
people
deep
so
I
just
wanted
to
make
sure
that
everybody
thinks
that
you
know
we're
asking
the
right
things
so
I'm
just
looking
for
to
hear
from
other
folks.
That's
all!
If
not
then
I'll
take
the
silence
as
we're
good
to
go
and
I'll
person.