►
From YouTube: Kubernetes Community Meeting 20160616
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
ElasticKube's Jenkins Kubernetes plugin; 1.3 release update; 1.3 feature tracking; SIG Cluster Ops; Online Meetup; Fixit announcement.
A
Okay,
so
this
is
the
Cooper
Nettie's
community
meeting
today
is
june
sixteenth
and
we
have
a
fun
agenda
ahead
of
us.
We're
going
to
hear
from
elastic
cube
talking
about
the
jenkins
plugin,
we're
going
to
hear
about
the
1.3
release.
The
1.3
features
update
some
cig
reports
and
some
new
and
exciting
online
and
future
community
events
show
let's
go
with
alberto.
Tell
us
more
about
elastic.
You
awesome.
B
Thank
you,
sir.
Thank
you,
everybody.
Well,
you
already
know
a
little
bit
about
elastic
cube.
We
did
the
presentation
a
couple
of
months
ago.
First,
allow
me
to
choose
myself.
It's
my
name
is
Alberto
arias.
Some
of
you
might
have
heard
that
elastic
box
has
been
acquired
by
CenturyLink.
It's
on
the
news.
We're
very
excited
about
that.
B
We
believe
that
that
is
going
to
give
us
the
resources
to
access
and
scale
that
we
don't
have
access
before,
and
our
mission
is
going
to
be
to
enable
hybrid
clouds,
crushed
enterprises
and,
of
course,
coordinators
pillar
of
data
strategy.
Over
the
last
couple
of
years,
we
have
invested
a
lot
in
Jenkins.
We
build
something
called
elastic,
bubba,
jenkins
plugin,
and
what
we
wanted
to
do
is
use
that
know-how
and
expertise
to
bring
some
of
those
use
cases
to
the
Covenant
suspendisse,
and
for
that
we
build
what
we
call
right.
B
B
Right
now,
the
plug-in
is
only
available
through
the
release
tab
on
github,
but
we
are
waiting
for
the
Jenkins
frogs
to
accept
it
as
part
of
the
list
of
plugins
and
install
right
from
the
UI
of
Jenkins.
So
let's
jump
into
the
goodies,
so
I
have
a
community's
cluster
you
to
make
sure
I.
Can
you
guys
see
now
kind
of
a
nice
payday
screen
thing.
B
B
B
So
I'm
selecting
now
it
Jenkins
chart.
This
is
the
deployments
the
flow
for
from
elastic
cube,
so
I
click
select
and
then
click
deploy
and,
of
course,
that
only
takes
a
few
seconds
now
happy
Jenkins
service
up
and
running,
and
so
people
to
access
it
yep
right
there
from
the
other
IP
address,
basically
different
replication
controller.
That
is
running
the
jacking
servers
and
threes
service
right
now,
I'm.
Just
using
a
note
for
mocking
to
be
able
to
access
that
Jenkins
server,
you
can
use
whichever
service
you
want,
and
it
should
be.
B
Let
me
say
one
okay,
so
Jenkins
is
up
and
running
I'm
gonna
go
ahead
and
install
the
plug-in.
This
only
takes
a
few
seconds.
I've
got
too
much
plugins
I
the
plug-in
will
be
available
through
this
list.
I'm
sure
we're
right
now.
I
have
to
upload
it
by
hand
until
the
folks
of
Jenkins
publish
it.
So
click
upload
will
take
about
20
seconds.
One
of
the
features
that
we
added
to
this
plug-in
is
out
of
this
covering.
B
B
Also,
there
is
the
capability
to
configure
the
repo
where
we're
going
to
pull
the
charts.
These
charts
will
be
available
as
deployment
steps
and
I'm
going
to
take
move
that
in
a
second
and
also
a
slave
configurations.
You
can
just
put
some
demo
that
describes
a
pot
and
that
is
going
to
be
used
as
a
template
to
create
the
slaves.
Those
are
slaves
will
automatically
call
back
to
that
Jenkins
server
and
be
used
to
execute
whatever
bill.
B
The
steps
need
to
be
running
on
that
dosis
labs,
so
I
don't
have
to
do
anything
is
up
already
just
installing
the
plugin
in
the
Jenkins
that
is
running
inside
the
covenants
cluster
pretty
much
out
of
configures.
You
don't
have
to
do
anything
else
to
get
it
started,
so
what
I'm
going
to
do
is
create
a
job.
This
is
a
freestyle
job
is
a
Jenkins
demo
and
I'm
going
to
use
one
of
the
build
steps
that
we
have
implemented
as
part
of
is
plugging
yeah
is
called
College
deploy
chart.
B
So
here
you
see,
the
options
can
have.
First
is
the
cloud
that
is
the
connection
to
the
open
areas
that
was
part
of
the
configuration,
the
repository
that
I'm
going
to
be
using,
and
these
automatically
kind
of
Coolsville
the
charts
from
that
repo
and
I
can
just
let
the
chart
that
I
want
to
deploy.
So,
let's,
let's
use
example
to
do
also
after
I
run
this
job,
I
want
to
automatically
nap
that
chart,
I'm
going
to
say:
hey,
you
know,
delete
all
the
artifacts
of
that
chart
after
the
computer
dis
job
finished
us.
B
I'm
also,
I'm
also
going
to
add
a
ticket
sales
job,
and
this
is
just
to
show
how
the
slave
is
going
to
be
created
in
the
cluster.
It's
going
to
wait
for
20
seconds
and
then
we're
going
to
do
a
co
dot.
So
this
is
my
job.
Now
click
Save
it's
ready
and
what
I'm
going
to
do
now
is
that
I'm
going
to
run
it
so
click
build.
You
can
see
it's
a
schedule.
B
Alright,
so
you
can
see
the
slave
is
coming
up,
it's
being
created
it's
up
and
running,
and
then
this,
if
we
can
see
the
console
output,
you
can
see
the
example
chart
is
being
deployed.
You
can
see
here
blogs.
The
point
chart
example
to
do
is
deployed
now
we're
waiting
20
seconds
and
once
you've
done,
you
should
clean
up
the
chart
and
remove
the
slaves.
B
So
there
you
go.
Everything
now
is
cleaned
up.
So
these
are
the
two
use
cases
that
we
wanted
to
start
off,
our
being
able
to
have
that
kind
of
mimics
processes
that
we
have
elastic
pops.
That's
the
ability
to
run
and
environment,
run
some
tests
and
clean
it
up
and
make
that
experience
extremely
easy.
B
We're
going
to
do
further
engagements
and
we're
going
to
make
it
really
easy
to
have
single
sign-on
across
coop,
API,
server,
elastic,
cube
and
Jenkins,
as
you
have
a
single
set
of
credentials,
and
you
can
just
access
all
of
these
environments
without
having
to
do
any
configuration.
Other
investments
that
we
are
doing
is
a
week.
Another
feedback
from
the
community
really
looking
forward
to
your
feedback,
is
implement
other
steps.
B
That
would
allows
us
to
do
things
like
rolling
updates
and
canary
deployments
and,
of
course,
interlace
those
with
all
the
build
steps
that
you
might
use
using
Jenkins
and
Fox.
Those
are
the
things
that
we
went
to
show
you
and
I'll
take
some
questions
and
just
went
to
answer
a
couple
of
questions
before
I.
Take
your
questions
because
we
have
been
getting
those
questions
from
alone
of
other
people.
B
So
what
is
the
difference
between
the
coordinators
and
the
governor?
The
sea
I
plug
in?
We
are
investing
resources
on
these
kunis,
yet
it
is
not
a
side
project.
We
have
dedicated
engineers
and
we've
been
talking
to
the
other
folks
that
live
in
the
little
corners
plugins
and
right
now,
it's
kind
of
like
a
side
project.
We
want
to
execute
really
fast.
So
did
we
wanted
to
first
implement
these
use
cases
and
then
go
back
to
the
community
is
okay?
B
Does
it
make
sense
to
merge
these
projects
and
what
is
the
process
to
collaborate
to
do
that?
But,
given
that
the
investment
is
going
to
be,
it
was
going
to
be
a
symmetrical.
We
want
to
first
do
these
things
in
a
we're
on
and
then
what
with
the
community,
to
merge
those
efforts
and
all
the
question
that
we
get
is
that
did
you
plan
to
support
anything
else
that
the
hub,
for
now
we
are
only
going
to
support
github
most
of
the
charts?
B
A
Alberto,
does
anybody
have
questions
I
didn't
see
any
pop
up
in
the
chat
as
we
were
going
and
how
can
people
will
get
ahold
of
you?
Okay,
can
you
post
links
there?
We
go
all
right.
Anybody
else
for
questions
Alberto.
Can
you
put
a
couple
of
notes
into
the
agenda
document
about
your
key
points
that
you
wanted
to
do?
We
wanted
to
get
four
and
blinks,
and
all
of
all
of
that,
so
that
we
can
have
a
record
of
this
because
we
didn't
actually
have
anybody
taking
notes
during
that
perfect.
A
A
E
Right,
can
you
hear
me?
Yes,
awesome,
we
are
closed
on
the
1.3
release,
so
just
a
quick
update.
We
plan
to
release
jun
24th,
that's
next
Friday,
so
six,
seven
business
days
depending
on
what
side
of
the
world
you're
on
from
now
we
branched
for
beta
last
week
and
we
did
a
fast-forward
to
pull
in
all
the
latest
fixes
I
believe
yesterday
or
the
day
before
and
now,
David
McMahon
is
struggling
through
assorted,
getting
assorted,
verify
scripts
to
work
just
right
to
get
the
beta
build
out.
So
we
had
hoped
that
that
would
be
yesterday.
E
I
was
not
yesterday.
It
ought
to
be
today
this
morning
this
afternoon,
he's
working
on
that,
so
that
will
get
us
a
beta
release
out
on
the
github
releases
and
then
from
then
forward
right
now
we
are
treating
the
blocking
bugs
as
in
AP
0
or
p1
bug
that
is
in
the
1.3
milestone,
and
so
that
we
right
now
we
have
to
pee
zeros
and
we
have
24
p
1.
So
we're
looking
at
26
total
bugs
that
we
need
to
get
fixed,
tested
and
verified
before
we
can
release.
That
was
a
much
higher
number.
E
A
day
or
two
ago
we
were
at
maybe
60
or
70,
and
so
we
did
a
pretty
pretty
hard
triage
to
get
down
to
those
26
bugs
left.
So
once
we
fix
and
merge
those
26
bugs,
we
obviously
have
docs
to
work
on
quite
a
bit
of
work
there
to
get
the
docs
all
set,
but
otherwise
that's
that's
the
work
that
remains
to
release
next
Friday
is.
E
A
A
F
Was
trying
to
take
notes
there?
Could
you
elaborate
on
the
docks
for
13
again,
I
wasn't
sure
if
there
was
like
a
are
we
just
supposed
to
be
contributing
the
docks
to
master,
or
is
there
a
13
branch
that
we
should
be
using
stuff
like
that?
I
wasn't
shirt
like
a
bid,
so
there's
this
whole,
like
life
cycle
of
when
things
are
going
to
get
cut
for
the
beta
I,
don't
know
what
the
same
thing
is
for
the
docks,
yeah.
H
F
Thank
you,
I
guess.
That
makes
sense
right
now,
if
I
want
to
make
sure
that
something
gets
in
the
docs
for
the
clear
I
should
be
putting
it
in
the
release.
One
free
branch,
not
the
master
branch
I-
should
be
doing
this
in
the
docs
repo,
not
the
group
that
is
correct,
but
only
if
it's
a
user
facing
feature
so.
H
The
docs
that
still
remain
in
the
main
repo
are
just
just
the
developer:
oriented
docs
for
the
people,
hacking
on
communities
itself,
so
docs
devel
and
the
proposals
and
design
docs.
So
I
wouldn't
expect
for
13
at
this
late
stage
that
you
would
have
any
of
those
kinds
of
docs.
They
would
go
in
the
main
reap
what
you
need
to
be
focusing
on
documentation
for
users
of
communities
at
this
point,
so
those
should
all
go
into
the
docs
rebuttal.
F
H
I,
currently,
the
master
branch
is
12.
Related
things
were
reevaluated
that
approach,
but
because
of
the
way,
github
stages,
the
docks.
Well,
we
have
to
do
to
publish
the
docs
is
actually
copy
them
to
other
orgs
and
github
to
stand
up
easily
stand
up
sites
like
communities
do
four
different
versions.
So
definitely
this
could
be
improved
a
lot
and
if
someone
is
interested
in
helping
make
that
more
sane,
please
reach
out
to
me,
which.
A
Leads
me
to
something
that
syrup
wanted
to
work
on
today,
which
is
creating
a
special
interest
group
around
the
docks.
So
that
will
be
that
will
be
kicked
off
today
would
be
my
suspicion,
or
at
least
this
week
sometime
so
we'll
have
a
space
walks
into
talking
here.
We'll
have
a
space
for
the
for
community
people
to
meet
up
with
all
the
people
internally
at
Google
that
are
working
on
Doc's
as
well,
so
that
will
be
getting
started
today.
It'll
be
you'll,
have
select
channels,
you
have
email
groups,
etc.
All
the
all,
the
usual
things.
J
J
Yeah
so
are
in
this
spreadsheet.
This
spreadsheet
burner
originally
like
deeply
involved
deeply,
like
I
used
a
lot
of
features
that
have
been
added
by
Max
park
to
his
original
document
that
we've
been
working
on
and
with
like
reviewed
on
the
previous,
a
our
previous
meeting
and
in
this
spreadsheet
I
have
split
it
into
three
such
sir.
J
The
actual
features
that
we
have
at
the
moment,
so
the
first
sheet
is
the
futuristic
and
one
two
three,
the
next
one
is
dead
features
that
have
a
milestone
as
one
wonderful
or
next
milestone,
and
the
Lakers
are
like.
The
proposals
did
don't
have
any
like
actual
milestones,
but
working
them
is
in
progress.
Research
by
the
community.
So
using
this
spreadsheet,
I've
created
a
wiki
page
sure
my
own
space
in
my
own
Fork
of
the
get
up.
J
Yes,
so
can
find
it
here,
it's
difficult
to
find
it
shirt
here.
I
have
found
it
when
I
sharing
the
screen,
yet
so
I've
created
it.
It's
like
more,
like
a
draft
like
a
mock-up
of
how
can
we
use
wiki
pages
for
tracking
their
actual
religious?
We
may
simply
I.
Take
a
look
at
the
extra
information
on
that
featured
is
learn
to
be
implemented.
We
may
take
a
look.
J
Yes,
so
to
community
or
ebook,
because
as
far
as
a
notice,
we
have
our
day
or
responded
for
here
and
I
suppose
it
would
be
a
better
placed
to
broken
Darrell
on
the
edge
from
features
here
so
did.
This
is
like
the
major
job
that
we've
been
done
during
the
last
time
or
getting
the
features
that
have
to
be
involved
in
211
load
monitoring
at
we
headed.
I
J
J
Yes,
it's
trip
on
sheep
sugar
like
an
amazing
place,
yeah
yeah
I
may
do
the
same
and
the
compliment
we
don't
have
week
yet
and
another
question:
do
I
really
need
to
dentist
weekend,
possibly
when
my
simply
put
that
into
like
a
subdirectory
release
123
and
the
markdown
files
there,
it
should
be
easier
to
maintain,
because
there
I,
I
received
a
lot
of
weight
trying
to
foreclose
Ryan
to
push
something
to
my
local
for
the
weekend.
What
can
we
still
like
it's
narrow
crevice?
Is
my
shoes,
alligator
yeah.
I
H
Yeah
and
so
I
think
the
advantage
of
pull
requests
is
that
pretty
much
anybody
can
create
a
pull
request
and
propose
a
change.
The
disadvantage
is
that
it
creates
a
a
workflow
around
it,
so
is
actually
a
barrier
to
maintaining
it,
so
it
all
depends
on
what
we
expect.
You
know
if
we
expect
someone
to
be
responsible
for
being
the
gatekeeper,
then
PR
workflow
makes
sense
if
we.
C
H
To
shortest
shard
ownership
for
people
keeping
things
up
to
date,
it's
kind
of
a
pain,
the
ass,
so
the
point
of
the
both
of
features
and
the
community
repose
is
that
we're
going
to
be
pretty
permissive
with
getting
people
write
access
to
those
repos
to
try
to
crowdsource
keeping
things
up
to
date
and
keeping
track
of
information.
I,
don't
really
care,
except
that
I
probably
will
not
ever
create
a
PR.
H
H
You
know
just
so
just
my
experience.
If
I
were
going
to
create
a
PR,
I
would
create
a
PR
and
if
anything
needed
to
be
changed
or
you
know,
God
forbid,
there
would
be
any
test
or
whatever
that
would
prevent
that
from
just
being
merged.
I
would
pretty
much
never
get
back
to
it
and
it
with
just
someone.
A
A
J
J
H
A
H
H
Yeah
yeah,
so
in
terms
of
the
wiki,
what
I
found
its
really
good
for
is
keeping
it
in
sync,
with
issues
and
PRS
for
things
which
have
a
lot
of
churn,
where
you
just
need
to
keep
multiple
things
up
to
date,
wiki's
really
handy
for
that,
because
you
can
just
edit
it
yeah.
You
know
if
I
can
basically
achieve
the
same
thing
through
a
PR
I,
don't
really
have
a
strong
opinion.
I
both
have
versioning
and
whatever.
H
I
Interesting,
okay,
all
right,
let's
give
it
a
shot
and
and
so,
and
what
I
was
going
to
say
at
the
beginning
was
that
we're
we're
trying
to
close
this
down
right
now
for
13.
So
please
take
a
look
at
a
horse
sheet
and
make
sure
that
your
thing
that
you
worked
really
hard
on
is
there
so
that
we
can
make
sure
to
highlight
it
and
be
very
positive
about
all
the
people
in
the
community.
Doing
cool
stuff.
I
C
A
A
J
I
sort
of
did
so:
let's,
let's
close
this
item,
so
I'm,
expecting
for
like
four
denerith
next,
like
12
horas,
these
items
to
be
updated
and
I
will
move
them
to
the
new
space
right,
so
we
have
agreed
so
do
we
won't
use
weekend
anymore
what
we
will
use
my
day
you
to
get
your
various
ways:
hot
dog
files
classic
knocked
out
files
and
classic
be
honest.
This
is.
I
I
Okay,
and
so
all
I
was
going
to
say,
is
that
to
be
clear,
this
is
the
process
going
forward.
If
you
would
like
to
work
on
things
in
14.
Now
is
the
time
to
start
so,
please,
there
is
I
item
temperature,
there's
exactly
how
to
work
on
it.
Everyone
is
subject
to
this,
including
Google
errs.
So
this
is
not
you
know
one.
You
know
the
all
equal,
except
for
me,
that's
more
than
equal.
I
J
I
Well,
that's
what
I'm
suggesting
right!
So
what
I'm
saying
is
that
if
something
is
a
kind,
I'm
proposing
and
and
feel
free
community
to
say,
this
is
too
much
but
I'm
proposing
if
something
is
kind
evils,
feature
or
kind
/
feature
if
it
does
not
have
a
PR.
That
is
our
exes
me
if
it
does
not
have
a
feature
tracking
proposal
in
this
future.
Repo
I
propose
that
we
as
the
community
safe
sorry,
this
is
rejected
until
you
go.
Do
the
work
oh
yeah
I
heard
yeah,
it's
good.
If
that's.
J
J
This
is
like
the
British,
simple
diagram
that
describes
the
procedure.
How
we
will
how
we
will
work
on
the
fishes
using
the
fishes
repo
and
how
the
features
from
the
future
stripper
are
going
to
be
added
to
like
the
upstream
reball
like
the
crepinette
history,
I
will
share
it.
I
will
share
it
implicit
to
the
nodes
and
I'm
not
make
sure
it
also
in
the
Middle
Eastern
women
continue
discussing
endure
and
possibly
if
someone
has
any
questions
right
now
when
I
speak
about
it,
I.
J
Yes,
I
also
think
about
it,
but
unfortunately
I
had
no
time
to
try
the
mail
before
our
meeting
here.
So
let's,
let's
speak
about
that
afternoon
after
our
call,
because
I
suppose
the
the
current
like
product
management
process
has
to
be
a
bitter,
implemented
and
started
with
the
new
features.
Reform
is
the
good
point
to
start
working
on
lineman
and
you
knew
your
project
management
process.
Listen
to
Commander.
A
A
K
So
for
cluster
Ops
has
been
working
regularly
on
this
reference
architecture
document
we
could
use
help
because
I
think
I'm
trying
to
find
a
place
where
we
can
sort
of
pull.
Here's
the
poured
mappings.
Here's
the
services
hears
things
like
that.
No,
it's
not
as
clear
in
the
docks
as
I'd
like
to
see.
So
I
think
this
reference
architecture
that
we're
putting
together
is
going
to
be
very
useful.
We
also
identified
cooper,
Nettie's
OSI
model
with
some
some
layers
and
things
like
that.
K
So
tickets
we're
trying
to
make
it
readable
and
generic,
so
I'm
happy
with
that.
I
don't
have
as
much
time
as
I'd
like
to
put
into
it.
It
needs
we
make
progress
every
week
but
slow
down.
So
please
please
jump
in
the
meetings
and
help
we
decided
as
a
group
that
there
were
22
other
objectives
for
us
in
the
short
term
that
we
want.
K
So
our
our
meeting
that
today
is
going
to
focus
on
not
the
prioritization
per
se,
but
the
process
that
we're
going
to
make
the
recommendations
so
the
process
for
the
process
but
I
think
we'll
wrap
that
up
today
and
that'll
be
pretty
much.
You
will
be
ready
to
start
analyzing
and
thinking
about
what
we
think
of
what
ops
thinks
is
important
from
a
window
for
perspective
and
one
of
one
of
our
goals
from
for
people
who
aren't
familiar
with
cluster
ops
I
jumped
right
into
doing
not.
K
What
is
cluster
offices
is
operators
coming
together,
all
sorts
of
different
ways
to
run
and
install
and
maintain
our
focuses
on
building
a
community
around
people
running
and
sustaining
Cooper
Nettie's
implementations,
and
so
we
want
to
be
the
go-to
people
provide
go
to
people
for
for
the
community
when
they
want
to
ask
questions
about.
Does
this
work
for
operators?
How
should
I
operate
it
yeah?
That's
the
we
want
to
host
those
discussions
in
the
meeting,
because
so
people
have
a
place
to
go
for
that.
K
So
that's
that's
item
one
influencing
one
dot,
for
we
feel
like
as
a
as
a
perfect
agenda
item
for
us
over
the
next
several
weeks
and
then
and
we
should
have
enough
reference
architecture
for
one
dot
3,
for
it
to
be
useful
in
the
one
about
three
release
and
for
people
to
use
it
as
a
sort
of
hey
I'm.
Going
to
point
to
this
and
it'll
help
me.
The
next
thing
down
is
a
docs
half
day.
So
the
other
thing
that
the
group
wants
to
work
on
doing
is
hacking
on
Doc's.
K
We
feel
like
there's
operators
who
would
be
happy
to
spend
a
day
doing
that
we
are
going
to
spend
probably
five
or
ten
minutes
saying
what
we
need
is
prereqs
for
a
docs,
hack
and
I
we'd
love
to
coordinate.
We
don't
need
to
carry
the
ball
on
this
one.
We
would
be
happy
to
support,
endorse
and
then
show
up.
We
don't
have
to
have
the
leadership
helm
here,
but
we.
A
K
That'd
be
awesome,
so
the
thing
that
we're
going
to
spend
10
minutes
talking
about
today
is
what
information
we
need
to
do
a
half
day
yeah,
so
you
know:
do
we
need
to
do
some
pre
videos
on
here's,
how
you
contribute?
Here's,
how
you
write
to
the
docs
right
so
we're
thinking
that
for
that
to
be
productive,
we're
going
to
need
to
have
a
certain
amount
of
preparatory
resources
available.
K
A
K
K
Going
to
spend
10
minutes
on
that
and
if
people
actually
I'd
rather
see
I'd,
love
to
see
coordination
of
the
day
itself
come
out
of
this
meeting
rather
than
cluster
ops,
because
I
think
we
want
the
bigger
audience
we're
willing
to
sign
up
and
make
sure
that
there's
people
actually
attend,
because
it's
not
it's
not
really
a
cluster
ops
thing,
but
we
want
to
see
it
happen.
So
we're
willing
to
put
some
time
into
it.
Awesome.
A
Let's
take
that
discussion
to
the
the
docks
Zig,
the
nascent
docks
Zig,
and
then
we
can
come
up
with
a
date
and
share
it
out
here
and
coordinate
across
here.
Awesome
cool!
Thank
you.
So
much
next
on
the
list
was
meetups
and
events,
because
we
have
a
growing
group
of
people
that
are
running
meetups.
There
are
now
a
hundred
and
twenty
meetups
around
the
world
that
actually
have
Cooper
Nettie's
as
a
discussion
point
in
them
and
Julian
is
going
to
tell
us
a
little
bit
about
a
new
extension
of
the
the
meetup
work.
A
That's
happening,
but
I
will
fit
first
pitch
that,
if
you
are,
if
you
do
run
or
are
interested
in
running
a
caverna
days
need
up,
there
is
a
coup.
Burnaby's
meet
up
leads
mailing
list,
which
has
discussion
points
about
interesting
things
we
might
do
around
the
globe
in
the
community.
At
local
events
is
probably
the
best
way
to
describe
it.
So
Julian,
oh
and
I
can
pitch
container
days
Hamburg
as
well.
Yes,.
L
Hi
there,
thanks
for
having
me
I'm
Julian
from
hamburg
in
Germany
and
the
founder
of
the
startup
loot.
So
we
are
providing
Cuba
need
assassin
service
to
my
background,
so
we
are
running
a
lot
of
local
meetups
in
Germany
and
then
throughout
Europe,
like
in
hamburg
and
munich,
and
in
Amsterdam
for
example,
and
so
we
quite
we
figure
out
that
there's
a
need
for
more
use
of
focused
on
line
meetups.
L
So
we
took
the
docker
meet
up
as
a
as
a
blueprint
and
created
a
queue
benitez
cloud
native
online
meetup,
where
we
want
to
have
more
user-focused
topics
and
I
just
heard
a
lot
of
topics
we
can
have
their
or
provide
their
a
platform
for
the
new
release.
Next
week
could
be
the
first
kickoff
for
this
meetup
group.
Then
the
heck
days
was
quite
interesting,
so
I
we'll
share
this
link
and
I
hope
you
guys
can
share
it
and
they're
spread
the
word
and
sent
me
some
ideas
sold
to
get
this.
L
L
A
And
on
top
of
the
things
that
we've
been
talking
about
here,
that
might
be
really
good
global
global
events
and
global
online
meetup
things.
There
is
a.
There
are
a
couple
of
upcoming
topics
for
the
community
that
we'd
love
localized,
help
in
one
of
which
is
the
Cooper
Nettie's
birthday
parties
that
are
going
to
be
upcoming,
so
I
will
be
sending
more
information
about
about
that
next
week.
Providing
backer
con
doesn't
suck
me
into
a
black
hole
of
conference
and
we
will
be
trying
to
do
more.
A
Local
events
around
caverna,
DS,
first
anniversary
of
the
one
point
0
release
and
there's
also
an
upcoming
fix
it
and
TJ
was
going
to
tell
us
a
little
bit
about
what
an
internal
Google
fix
it
looks
like
and
how
we
can
and
then
I'll
jump
in
and
talk
about
how
we
might
be
able
to
get
everyone
around
the
world
through
something
potentially
like
your
online
meet
up
or
or
other
ways
to
participate
over
the
last
week
of
june.
In
a
fix
it
so
TJ
are
you
still
on
yep.
E
We
don't
build
up
too
big
of
a
backlog
of
loped
right
bubs,
and
so
we
were
looking
at
having
one
in
a
few
weeks
and
obviously
Cooper
Nettie's
is
a
big
part
of
what
a
number
of
Googlers
work
on,
and
so
the
focus
would
probably
be.
Things
like,
like
I,
said,
low
priority
bugs,
but
also
testing,
improving
flakes,
adding
additional
tests
where
needed.
E
If
we're
missing
a
lot
of
coverage,
updating
unit
tests,
those
kind
of
things,
as
well
as
a
focus
on
developer
productivity,
because
a
lot
of
times
that
can
really
pay
gains
over
the
long
term
developer
productivity
in
this
project
is
probably
code
for,
submit
you
and
making
sure
that
the
the
process
for
sort
of
once
you
have
submitted
code
between
then
and
actually
getting
it
committed
improving
that
speed.
So
that's
sort
of
the
the
overview
of
what
we
typically
work
on
I
at
Google
when
we
say
take
some
time
aside
for
a
fix
it.
That's.
A
Getting
some
of
the
that
have
been
working
on
communities
a
long
time
to
do
some
guided
programs
and
potentially
some
office
hours
to
help
people
who
haven't
contributed
as
much
an
aren't
as
familiar
be
able
to
learn
a
little
bit
more
toward
during
the
fix
it
toward
the
next
fix
it
or
the
next
contribution
that
they
might
make.
Because
one
of
the
things
we
want
to
fix
and
fix.
It,
of
course,
is
making
sure
that
we're
educating
the
community
as
well
so
more
info
on
that
program
as
we
get
it
finalized.
A
J
A
What
is
the
high
all
right?
Generally,
people
turn
on
their
video
when
they
have
something
to
say:
okay,
so
any
other
random
business.
Otherwise
will
end
a
couple
minutes
early
this
week.
I
will
the
meetup
be
live-streamed.
Oh,
yes,
the
cooper
nidhi
seattle
need
up
next
week.
I,
don't
think
it
will
be
live,
streamed,
I,
think
the
I
know
the
online
cloud
native
online
meetup
will
be
a
live
stream
because
it's
all
one
on
and
but
I,
don't
know
that
the
Seattle
meetup
will
be
live
streams
next
week.
A
A
K
A
Okay,
well,
we
can.
We
can
look
at
that.
So
I
do
have
one
more
item,
which
is
an
introduction
of
a
new
team
member
here
within
Google
Mike
rubens
has
been
a
Reuben
pardon
me
has
joined
us
he's,
thumbing
up
here
and
my
Q&A.
Or
do
you
want
to
give
a
bit
of
an
intro
of
yourself
and
what
you're
going
to
be
doing
from
inside
the
team
here
except
you
have
no
audio,
so
we
will
only
introduce
you.
Yes,
you
can
make
faces
and
or
use
semaphore
flags.
Yes,
alright!
A
So
that's
Mike
and
at
some
point,
when
he
has
audio,
we
all
have
him
introduce
himself,
but
he
has
joined
as
a
team
manager
here,
a
technical
manager
here
at
google
and
is
focusing
on
Cooper
Nettie's
as
well.
So
some
day
we
asked
great
thumbs
up.
That's
the
very
short
version.
Will
let
him
chat
when
he
hasn't
a
mic
at
some
point.
A
All
right
have
a
lovely
week
and
I
will
cross
paths.
I
suspect,
with
many
of
you
at
dr.
Khan
next
week,
say
hi
reach
out,
there's
a
Cooper,
Nettie's
booth.
A
bunch
of
the
vendors
are
also
that
vendors
in
space
are
also
going
to
be
a
component.
Okay,
coupon,
dr.
Khan
whoops,
that's
a
Freudian
slip
at
dr.
Khan
and
we
will
turn
it
into
a
mini
coop
Khan.
There
is
a
workshop
on
Sunday
time.