►
From YouTube: Kubernetes Community Meeting 20180712
Description
This is our weekly community meeting, for more information check this page: https://github.com/kubernetes/community/blob/master/events/community-meeting.md
A
Hi
everyone
welcome
to
this
Thursday
July
12th
edition
of
kubernetes
community
meeting.
My
name
is
Paris
I
work
at
Google,
I,
do
community
related
stuff
and
I,
also
co-chair
contributor
experience
and
to
some
sub
projects
under
contributor
experience
as
well.
Thanks
to
everyone
for
joining
us
today,
we
do
have
a
jam-packed
agenda.
However,
we
do
have
some
modifications.
I
will
guide
everybody
through
those
first
things.
First,
we
usually
have
a
demo.
Unfortunately,
our
demo
today
was
stuck
in
a
metal
tube
and
they
could
not
join
us
at
the
last
minute.
A
B
A
C
Well,
1.12
release:
let's
chart
video
wave
at
everybody,
hi
I
will
be
the
112
or
am
the
112
release
lead
and
we'll
be
giving
updates
during
the
cycle
in
the
community
meeting
regularly
and
sending
out
emails
as
well,
but
cycles
underway.
We
have
our
team
listed
there
in
the
notes,
along
with
a
link
to
the
schedule.
Main
thing
going
on
right
now
is
feature
collection,
so
we
reaching
out
to
SIG's.
C
It's
already
been
buy
a
couple
times
on
ke
dev,
there's
a
link
also
to
the
spreadsheet,
where
a
current
feature
work
is
being
noted.
I'm
Steven
augustus,
our
futures
lead
we'll
be
reaching
out
to
folks,
as
as
his
shadows
in
the
roll
and
myself,
and
probably
also
I
sundar,
my
shadow,
some
key
dates
just
to
call
out.
Obviously,
we've
got
the
link
to
the
full
schedule
there,
and
these
things
are
on
the
community
calendar
now
as
well,
but
feature
freeze
is
at
the
end
of
the
month
of
July.
C
The
current
months
and
code
slush
and
code
freeze
will
be
end
of
August
and
beginning
of
September,
respectively
and
following
along
with
what
happened
in
1.11
with
the
shortening
of
those
periods.
We
will
continue
that
here
in
1/12,
because
it
seemed
like
it
worked
reasonably
well,
but
that
really
depends
on
us
having
a
clean,
CI
signal.
So
the
release
team
pushed
aggressively
and
the
111
cycle,
and
will
continue
to
do
that
here
in
112
to
ensure
that
there's
solid
attention
to
keeping
test
signal
Green.
C
If
for
some
reason
we
we
have
issues
with
that
not
necessarily
foreseen,
but
if
it
does
we'll
have
to
make
a
call,
sometime,
probably
an
early
August,
to
step
that
up
again
and
really
emphasize
two
different
SIG's.
If
we're
having
issues
that
this
be
rectified,
and
if
it
wasn't,
we
might
have
to
pull
the
the
code.
Slash
code,
freeze
back
and
elongate
them
just
so.
C
We
have
plenty
of
time
to
stabilize
ahead
of
the
release,
but
not
foreseeing
that,
but
just
mentioning
it,
and
we
will,
as
a
team
work
aggressively
to
communicate
that
ahead
of
time
and
and
really
I
would
say,
expect
that
not
to
be
the
outcome,
but
this
is
still
somewhat
a
new
change
to
go
with
the
shorter
cycle
there
on
that.
The
code
freeze,
so
I
really
want
to
highlight
that
and
related
to
that.
C
So
please
give
some
consideration
when
you're
doing
your
feature,
work
definitions
to
a
lot
sometime
to
starting
to
draft
the
documentation
and
not
having
those
come
just
at
the
very
last
moments
and
then
similar
for
test
cases.
We
want
to
at
least
know
that
those
are
coming.
We
plan
insertion
in
a
timely
way
and
and
ideally
having
them,
come
already
green
on
the
feature
and
I
think
that's
the
the
main
stuff
to
communicate
on
112.
A
D
You
too,
so
on
111,
one
I
sent
out
an
email
to
kubernetes
announced
the
planned
cut.
Gate
is
Monday,
July
16
and
we're
gonna
freeze
the
branch
end
of
day
today,
so
you're,
getting
all
the
last-minute
cherry
picks
and
a
bunch
of
them
still
need
some
action.
We're
tracking
them
actively
I
think
there's
three
changes
which
are
marked
action
required
right
now.
D
Two
of
them
are
part
of
the
the
email
that
I
sent
out
and
then
one
more
go
at
it.
I'll
probably
have
an
update,
email
as
well,
but
yeah
things
are
looking
good.
The
there
was
some
issue
with
PRS
merging
because
of
cops
test
this
morning
that
Liggett
brought
up
so
I.
We
need
to
follow
up
on
that
and
make
sure
things
merge
by
the
end
of
the
day,
but
otherwise
tests.
Look
good
grass
looks
green,
mostly
yeah,.
A
All
right,
Green
is
good
all
right.
Next,
we
are
filling
in
this
week
with
the
cup
of
the
week
and
Janet.
Are
you
want
yes,
I'm
on
all
right
great?
So
this
is
a
new
segment
for
us.
We
have
been
reviewing
caps
as
caps
our
semi
new
to
the
project
as
well,
and
this
gives
us
a
good
chance
to
highlight
some
of
the
work
that's
coming
through
from
SIG's,
so
Janet
take
it
away.
Okay,.
E
So
I
open.
Can
anyone
see
my
screen
good
to
go?
Oh
so,
I
open
a
cap
for
garbage
collection
and
it's
most
smelly
for
cleaning
up
the
frequently
created
and
short
live
objects.
So
currently
the
existing
dr.
cracker
doesn't
allow
you
to
clean
up
those
resources
that
doesn't
have
any
owners.
E
For
example,
when
a
pod
terminates
or
if,
when
a
job
completes,
when
the
resource
finishes,
we
don't
have
a
way
to
garbage,
collect
them
and
also
for
resource
like
coffee,
claps
and
secrets,
or
any
other
CRTs
that
eat
that
is
used
or
referenced
by
other
resources
and
some
people.
We,
we
have
seen
some
pattern
that
people
don't
update
those.
They
just
create
me
once
and
update
the
references
in
the
other
resources
like.
E
The
coins
so
in
order
to
clean
up
built
resource
I,
wrote
this
cap
to
propose
and
to
introduce
a
TTL
mechanism
to
garbage
collector
and
also
to
allow
users
to
specify
that
they
want
to
clean
up
some
resources
after
they
finish
or
after
they
are
not
used
by
other
resources.
And
so,
if
you
have
comments
on
this
cap
feel
free
to
go
to
this
link
and
take
a
look
at
the
cap
and
also
I'm
going
to
discuss
this
in
the
next
C
API
machinery
meeting,
which
is
next
Wednesday.
On.
B
E
C
E
C
A
A
F
F
Switch
give
feedback,
let
us
know
the
know.
Crd
conversion
made
it
in
and
I
want
to
be
clear
about
what
this
is
and
isn't.
So
this
gives
you
the
ability
to
promote
a
custom
resource
definition
from
one
version
to
another,
but
without
any
accompanying
API
changes
with
it.
So
this
means
that
it
gets
served
at
the
new
endpoint
say
you
went
from
alpha
1
to
beta
1
it'll
be
served
at
the
beta
endpoint,
but
you
won't
be
able
to
do
any
data
transformation.
F
You
won't
be
able
to
differentiate
your
data
formats,
so
it
is
useful,
but
it
is
limited
and
be
aware
of
those
limitations.
There
is
still
work
going
on
on
server
side
apply,
it's
active,
there
is
still
a
feature
ranch
and
a
lot
of
work
was
done
there
and
111.
There
are
some
designs
out.
If
you
want
to
review
them,
then
also
in
111,
we
did
work
for
making
the
controller
manager
start
from
a
config.
It
takes
a
lot
of
base
work
to
make
that
happen.
F
So
they've
been
a
lot
of
developer
things
happening
there
in
112.
We
are
actually
moving
a
piece
of
the
apply
work
out
from
the
feature
branch
into
master,
the
dry
run,
a
police
has
been
working
on
getting
it
into
master
I.
Think
the
API
changes
were
LG
TM
to
yesterday
or
today
and
it'll
be
properly
feature
gated.
But
it's
been
a
much
asked
for
feature.
That'll
be
really
nice
for
custom
resource
definitions.
F
We
are
going
to
be
working
on
the
path
to
more
advanced
conversion
and
that's
going
to
require
us
to
get
pruning
in
I
expect
we'll
be
able
to
do
that.
That's
removing
extra
data
items
field
the
full
think
which
is
extremely
common.
There
was
design
for
it
long
ago
where
we
are
actively
working
on
that
and
then
we're
gonna
be
reviewing
designs
starting
next
week
for
more
advanced
version.
Eight
given
given
how
tight
we
are
I,
don't
know
that
we
expect
to
have
an
implementation,
but
design
should
be
moving
forward
and
that's
a
good
thing.
F
The
feature
branch
work
for
server-side
apply
is
going
to
continue
the
prereq
work
and
the
controller
manager
for
developers
out
there
who
see
stuff
move
around
there
is.
There
is
an
end
goal.
We
are
working
towards
running
from
configure
just
it's
taking
a
long
time
to
get
from
here
to
there
and
then
one
final
thing:
generic
initializers
they
came
in
as
alpha
a
little
bit
before
webhooks
admission
webhooks
came
in,
but
we
are
looking
at
it.
F
It
looks
like
a
very
similar
feature
and
we
are
considering
removing
generic
initializers
in
the
future
before
we
do
that,
we're
still
going
to
work
on
what
we
need
to
do
for
initializing
namespaces,
but
if
you
are
a
user
of
generic
initializers
and
think
you
have
a
strong
use
case.
That
cannot
be
satisfied
with
admission.
Please
come
to
the
API
machinery
meeting
and
let
us
know
so
that
we
don't
take
away
a
feature.
You
like.
A
G
G
Cool
yeah,
so
some
updates
from
suggesting
over
the
last
couple
months,
one
of
the
big
things
that
we
really
do
is
implement
caches,
and
so
those
both
helped
in
performance
gains
for
test
runs
and
also
a
lot
more
for
our
internal
infrastructure.
We
developed
a
couple
different
workflows
that
are
declared
in
fig
driven
to
administer
it
github
organizations
and
projects
and
keep
that
a
little
bit
more
transparent.
We
improved
a
couple
of
UX
items
with
the
robot
and
how
people
interact
with
it.
G
We
exposed
a
couple
simpler
ways
to
write
jobs
for
test
authors,
we're
continuing
to
mature
the
workflows
for
merging
using
tied.
We
have
now
an
aggregated
place
to
place
here,
federated
conformance
test
results,
and
we
are
seeing
adoption
of
our
infrastructure
by
communities
that
are
both
related
securities
and
at
large
one
of
the
catches
that
we've
lent.
It
was
a
github
caching.
G
We
also
implemented
a
cache
from
there
for
build-out
effects,
and
so
this
graph
that
we're
looking
at
at
the
bottom
is
the
test
time.
Duration
in
minutes
for
the
Bassel
build
test,
and
you
can
see
the
quite
obvious
drop
here
in
test
time
and
we've
seen
that
I'm
cashing
they
continue
to
be
performing
on
a
system.
G
We
are
continuing
to
make
the
interaction
with
the
robot
a
little
bit
nicer
as
github.
It
adds
you
know,
new
features
to
their
web
UI,
so
one
of
the
big
ones
is
you
can
lgt
em?
You
can
prove
from
a
review
comment
now.
It's
it
doesn't
need
to
be
a
standalone
comment,
as
used
to
be
also.
We
are
finalizing
and
rolling
out
a
feature
so
that
if
you
change
a
owners
file
in
your
pull
request,
the
robots
will
validate
that
the
changed
file
is
valid
today.
G
If
you
change
it,
and
someone
doesn't
notice
that
you
know,
perhaps
your
format
is
incorrect.
It'll
start
I'm
cascading
some
failures
from
the
infrastructure
side
of
things.
There
are
a
couple
tools
that
are
being
developed
and
rolling
out.
That
will
aim
to
make
organization
administration
easier.
So
there's
this
tool
pair
bolos.
The
point
here
is
to
automate
the
entire
management
of
the
organization.
G
We
also
rolled
out
automatic,
rash
protection
for
all
the
repos.
This
is
setting
requirement
set
us
context,
just
making
sure
that
you
know
only
a
certain
amount,
people
or
robots
can
merge
two
different
wretches.
Also.
As
a
note,
the
rollout
of
this
feature,
which
I
take
simplify
the
best
practices
for
how
we're
gonna
roll
out
your
defacing
changes
in
the
future.
G
One
of
the
interesting
ways
that
we
can
configure
jobs
now
is
as
a
job
author.
If
you
have
a
test
script
that
you
want
to
run
and
an
image,
those
are
the
two
smallest
pieces
of
information
we
need,
and
so
there's
a
lot
less
information
that
you
need
to
understand
about
the
testing
for
sure
to
writers.
Job
we're
pretty
excited
about
this
onboarding
to
the
large
code
system
for
a
stack
will
be
a
lot
easier.
With
this
feature,
we
continue
to
mature.
G
Coming
with
that
tool
is
a
request
for
request
status
page,
and
so
this
status
page
will
show
you
sort
of
the
difference
between
where
your
PR
is
today
and
what
it
needs
to
have
for
things
to
emerge.
So,
if
we're
looking
at
this
pull
request
in
this
image,
you'll
notice
that
there's
a
required
label-
that's
missing
this-
that
LG
TM
label
and
in
order
to
merge,
you're
gonna,
need
to
resolve
those
labels.
If
we
quickly
go
to
this
page.
G
We
also
now
have
a
test
boot
dashboard,
where
CN
CF
performance,
so
trails
can
be
published,
there's
a
simple
process
in
uploader
tool
that
helps
you
sort
of
add
your
Center.
So
you
can
see
here,
there's
a
bunch
of
different
GCE
releases
that
are
showing
their
conformance
test
results
and
we've
on-boarded
OpenStack
as
well
on
to
this
Brussels
in
this
cycle.
As
I
noted
before
one
of
the
exciting
things
for
us
is
they're
actually
seeing
this
infrastructure
start
to
get
adopted
by
a
bunch
of
different
organizations.
G
H
Wow
sorry,
the
tide
base
PR
Status,
page
yep.
What
would
it
take
to
record
archival
snapshots
of
status?
That
is
that
is
like
everyday
say.
Record
aggregates
of
this
is
how
many
PRS
are
stuck
on
these
particular
label.
Slash
issues.
G
I'm
not
sure
that
the
page
supports
that
today,
but
I
think
that
wouldn't
be
too
hard
and
we're
just
sort
of
dumping
the
difference
in
state
and
which
of
the
casting
meeting
sure
I
tend
to
talk
about
that.
Are
we
we
have
a
weekly
suggesting
meeting,
that's
on
Tuesdays
1
p.m.
Pacific.
You
try
there
I'm,
trying
to
press
the
stop
share
button
by
the
way.
Paracin
I,
don't
think
it's
working
so.
A
G
A
All
right,
so
next
up
is
me
with
contributor
experience,
update,
LC,
Philips
and
I
both
co-chair
this
saying,
and
we
do
have
some
team
leads
or
excuse
me.
Technical
leads
that
really
work
with
testing
closely
you'll
see
a
lot
of
overlap
with
testing
and
contributor
experience,
and
we
are
two
groups
that
do
work
closely
together,
teach
or
that
the
contributor
has
a
smooth
ride
on
all
of
our
systems.
A
All
right
and
the
links
to
the
slides
are
in
the
agenda.
There
are.
This
DAC
is
jam-packed
with
links,
whether
that's
the
docs
or
issues
or
what-have-you,
so
as
I
go,
feel
free
to
comment
on
any
of
the
issues
now
or
whenever.
So
our
first
project
that
I'm
going
to
cover
some
highlights
and
things
that
we're
working
on
are
he
is
the
contributor
guide
and
contributor
documentation.
A
Next
is
a
community
management
section
of
our
duties,
which
includes
things
like
events
and
communication
and,
of
course,
mentoring,
dev,
stats
and,
if
folks
do
not
know
what
death
stats
is
desktop
deaths
at
Starrcade,
CN,
CF
tayo,
it's
a
great
dashboard
where
you
can
measure
the
health
and
velocity
of
the
project
and
pretty
much
anything
else.
He
actually
leads
that
up
and
Josh
does
a
lot
with
data
validation
as
well,
along
with
Lukas
from
CN
CF.
So
it's
a
really
great
project
that
I'll
also
mention
at
the
end
and
then
also
a
github
management.
A
A
sub
project
which
is
now
proposed,
I,
actually
did
not
like
I,
did
not
link
that
clearly
exciting.
My
note
there
us
all
at
that
lis
Christoph
actually
just
proposed
that
recently
and
I
checked
that
out
too
so.
First
things.
First,
the
contributor
died
documentation.
The
issue
that
we
had
for
umbrella
issue
is
now
officially
closed.
Of
course,
we're
accepting
PRS
at
any
time
for
any
gaps
or
suggestions
that
you
think
we
need
to
add,
especially
if
you're
a
reviewer.
A
We
also
have
a
non
code
guide,
part
to
that
that
we've
decided
to
pick
up
that
meets
every
Wednesday
as
a
sub-project
of
contributor
experience,
and
they
talk
about
how
to
ramp
someone
onto
the
project
in
ways
that
aren't
necessarily
related
to
code,
and
this
is
also
a
really
great
way
to
ramp
people
into
code
so
that
they
are
and
the
sort
of
ecosystem
elements
of
of
the
project.
Next
we're
working
on
as
a
developer
guide
portion
to
the
contributor
9
as
well.
You
can
see
I
also
did
not
add
the
issue
link
there.
A
Tim
pepper
is
actually
going
to
be
up
reach
out
to
on
slack
if
you'd
like
to
help
and
his
ideas
right.
There
contributor
not
kubernetes
that
IO
the
or
is
not
fine
along
this.
That's
under
discussion
right
now,
but
I
thought
it
would
be
nice
to
show
kind
of
what
we're
going
for.
This
is
going
to
be
a
contributor
contributor
audience
only
site
which
is
different
from
kubernetes
that
iOS
flash
community,
because
community
we
define
is
users
and
contributors.
A
So
now
we
find
our
contributor
population
is
large
enough
to
segment
its
communications,
which
will
also
help
in
be
just
will
help
with
feelings
of
being
inundated
with
everything
that's
going
on
with
the
project.
So
we
hope
that
this
will
help
focus
contributors
on
contributor
related
information,
and
it
will
actually
have
a
more
modern
calendar
as
the
first
feature,
and
this
will
include
all
of
your
city
meetings
and
things
along
those
lines.
Things
that
won't
include
are
more
community
related
meetings
which
will
ultimately
go
on
to
the
humanity
side
iota
slash
community
site.
A
You
can
check
out
the
prototype
there,
that's
without
a
UI,
that's
without
a
skin
George
put
that
up
on
Hugo
recently,
and
we
also
have
a
couple
more
contributors
that
are
helping
whistling
back-end
items
as
well.
We're
actually
hoping
to
launch
the
first
edition
within
the
next
90
days
when
it
uses
the
community
management
piece,
and
this
is
the
piece
that
really
takes
a
lot
of
time,
because
it
is
highly
transactional
and
as
our
community
grows
into
thousands.
A
So
we
are
official
and
so
look
out
for
all
things
related
to
contributors
limit
within
the
next
couple
of
weeks
and
as
cute
con
starts
to
heat
up.
We
also
do
a
la
carte
events,
a
lot
of
other
communities
for
a
space
or
offer
us
a
contributor
track
or
some
kind
of
session,
and
we,
if
we
can,
we
will
definitely
do
that,
for
instance
like
at
AFRICOM,
so
the
community,
the
community
management
piece
of
the
largest
in
my
opinion
and
I
know
others
would
agree,
is
probably
the
communication
pipelines
that
we
run.
A
As
you
all
know,
we
do
have
a
lot
of
spam,
and
things
like
that,
so
one
of
our
main
priorities
right
now
is
to
really
clean
up
this
area
and
not
necessarily
even
for
spam,
but
to
reduce
a
number
pipelines
that
we
had
and
really
strengthen
the
ones
that
are
working
out
well
for
us.
So
again,
a
lot
of
those
pain
points
that
you
might
be
feeling
now
hope.
A
We
hope
to
within
the
next
couple
of
months
really
alleviate
those
concerns
that
you
might
have
the
mod
guides
in
there
right
now
that
you
see
our
first
attempt
at
Modifieds
mi
died
a
general
mod
guide
anyway,
again
from
me
from
a
perspective
of
its
umbrella
for
all
of
these
communication
platforms,
and
then
what
we
intend
to
do
is
drill
down
into
each
one
and
really
really
take
us
out
of
the
process
you
mean,
so
you
can
see
eagle.
He
use
moderators
for
some
of
these
platforms,
so
just
really
document
each
one
of
those
deaths.
A
So
first
things.
First,
we
moderate
this
meeting
that
we're
along
right.
Now,
for
instance,
we
have
a.
We
have
an
addition
of
something
called
a
co-host
and
that
co-hosts
responsibility
solely
is
too
much
for
bad
actors,
watch
by
people
who
are
doing
things
against
their
code
of
conduct
and
then
ultimately
remove
them
in
order
take
and
then
take
other
actions
zoom.
A
So
we
have
been
walking
down
as
soon
as
much
as
possible
without
taking
away
the
the
public
nature
of
meetings,
because
obviously
that's
important
at
open
source
and
other
resources
that
we've
that
we've
looked
at,
don't
necessarily
meet
the
bar
for
for
that
public
nature,
so
we've
actually
created
a
lot
of
best
practices
around
moderation
of
public
meetings
and
we're
actually
looking
with
some
executives
to
really
see
what
we
can
do
and
features
that
can
be
rolled
out
from
a
security
perspective.
That
would
address
our
needs.
So
much
more
on
that
soon.
A
If
you
are
a
saint
chair
and
you're.
Listening
to
this,
you
have
been
sent
a
ton
of
information
on
how
to
properly
conduct
zoom
calls.
Please
read
that
there
a
lot
that
we
could
not
do
from
a
global
perspective
that
individual
users
will
have
to
do
so.
Please
read
those
guidelines
carefully.
We're
also
doing
the
mailing
lists.
Kate
of
kate
users
only
which
is
new
for
us.
The
moderation
team
is
pretty
much
the
same
team
as
it
is
across
the
board.
A
You
can
actually
get
to
it's
very
rapidly
with
with
slack
and
where,
and
there
was
under
the
slack
admins
channel,
even
though
it
might
not
be
a
slack
issue.
It's
just
a
way
for
if
you
need
to
get
a
hold
of
us
as
quick
as
possible,
I
could
be
a
very
good
way
in,
for
instance,
if
you
do
see
spam
with
kTVK
users,
you
need
to
ask
the
community
to
help
us
community
moderate.
So
if
you
see
something
that
isn't
right,
please
call
it
out
we're
all
humans
and,
unfortunately,
cannot
read
emails
all
day
long.
A
A
It's
actually
very
low
moderation
compared
to
other
mailing
lists
that
see
you
know
at
least
12
spammers
a
day,
I
would
say
on
average,
so
slack,
we're
only
doing
you
know,
I'd,
say
mm-hmm,
maybe
like
one
to
two
at
most
moderation
type
activities
a
week
there
and
then
discuss
that
kubernetes
data.
Oh
that's
a
cup
that
we
recently
put
in
and
George
and
Bob
Jillian
and
many
others
have
been
putting
a
moderation
team
around
this
this
platform.
A
We
are
now
officially
going
to
go
forward
with
it
as
a
supportive
project.
We
recently
did
a
mailing
list
item
for
for
that
this
week,
so
we're
just
waiting
for
some
plus
ones
under
objections
for
that,
and
then,
of
course,
the
redesign
humanities
that
IO
slash
community,
it's
underway,
updates
and
decisions
are
gonna
happen
in
sick
docks
and
ours.
Please
feel
free
on
the
issue,
link
there
to
add
comments
and
suggestions.
This
is
gonna
house,
a
general
calendar,
take
updates
and
other
really
cool
modern
additions.
A
Like
embedded
office
hours
on
YouTube
and
things
along
those
lines,
mentoring,
we
are
doing
really
well
with
New
York
contributors.
That
is
a
scalable
solution.
When
mentors
don't
have
time
to
take
on
someone
at
a
one-on-one,
we
do
it
once
a
month.
Yesterday's
was
a
special
edition.
We
actually
had
steering
committee
members
on
and
that
was
super
fun
lots
of
like.
What's
the
sub-project
question
so
definitely
feel
free
to
check
that
out.
When
you
can
outreach
e,
we
do
participate
in
outreach.
A
A
So,
if
you
are
in
a
state
that
it
needs
new
members,
not
necessarily
new
contributors
but
new
members
of
a
different
levels
or
more
approvers,
for
instance,
please
see
me
so
that
we
can
try
to
carry
out
one
of
these
to
see
if
it
meets
your
needs
and
then,
of
course,
google
Summer
of
Code
is
under
way.
We
do
have
one
and
he
is
under
API
machinery.
It
shouts
those
three
individuals
in
Keita
Stephan
David,
for
their
help
with
that
and
his
work
is
actually
included
in
the
link
right
there
and
that's
a
all
right.
A
H
A
Issue
triage
issue:
hygiene
I
actually
wrote
all
these
down
on
a
pad,
but
I
just
knew
that
the
it
was
gonna
be
much
longer
than
10
minutes,
but
all
of
this
is
very
relevant
to
this
call
for
contributors
that
are
on
this
call.
So
all
right
and
Josh,
thanks
for
all
your
all,
your
work
with
contributor
experience.
A
Alright.
Next,
let's
move
on
to
the
announcements
part
of
the
call
shoutouts.
This
is
our
weekly
shout
out
to
pool
contributors
who
are
doing
something
great
for
either
you
or
the
project
itself.
If
you
have
someone,
please
enter
them
in
the
shout
outs
and
the
floc
Channel
and
we'll
read
them
off
here
every
week.
First
things
first
josh
is
shouting
out
chase
for
inventing
and
running
really
effective
retros
for
releases.
A
It
was
a
really
really
cool
time
and
experience.
Thank
you
and
then
the
next
shout
out
it
looks
like
I
didn't
copy
over
the
face
by
thicknesses
from
James
and
James
is
shouting
out
Steve
again
for
immediately
jumping
to
spend
time
debugging
and
fixing
issues
with
our
proud
employment
and
tied
knot
merging
our
PRS
looking
forward
to
rolling
out
the
fix
it
has
caused
issues
for
us
for
one
to
two
months
now
so
congrats
to
Steve.
For
for
helping
out
that
crew
office
hours
is
next
Wednesday
volunteers
to
help
answer.