►
From YouTube: Keynote: Who Says Elephants Can't Dance with Node.js and JavaScript - Michael Dawson & Joe Sepi
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).
B
A
B
B
Asian
and
I'm
Michael
Dawson
IBM's
community
lead
for
nodejs.
That
means
I
get
to
spend
like
Joe
a
lot
of
time
working
out
with
the
community,
but
also
working
with
our
internal
teams.
Who
are
you
know,
building
tools
to
help
you
deploy
efficiently
with
nodejs
teams
that
are
deploying
you
know,
making
large-scale
nodejs
deployments
and
just
you
know,
supporting
our
customers
and
internal
teams
who
are
using
nodejs.
B
B
B
You
know
the
challenge
is,
is
that
you
know
sometimes
that
perception
gets
in
the
way
of
people
engaging
and
it's
a
sec.
Sorry
there
we
go
got
the
challenge.
Sometimes
you
know
it
gets
that
perception
gets
in
the
way
of
people
engaging,
and
it's
really
a
missed
opportunity,
because
you
know
iBM
is
doing
a
lot
of
things
in
the
node
in
JavaScript
front
in
the
community.
A
B
B
We've
done
a
lot
of
work
in
terms
of
making
sure
that
note
runs
on
IBM
platforms,
as
I
mentioned,
we
use
node
and
some
very
large
applications
internally
or
building
great
places
for
you
to
deploy
your
node.js
applications
and
even
working
on
tooling
that
you
know
when
you're
doing
your
initial
development
that
will
help
you
be
more
efficient
and
help.
You
make
sure
that
when
your
application
does
get
to
production,
it's
it's
going
to
be
successful
and
then,
finally
we
you
know
we
spend
a
lot
of
time
working
with
our
customers,
both
internal
and
external.
B
A
This
isn't
just
no
js'
as
well.
You
know
this
is
a
variety
of
open-source
tools.
Ibm
really
builds
on
open-source
and
has
been
involved
in
open
source
for
for
many
years.
You
know
no
js',
but
also
containers.
We
have
a
lot
of
work
that
we
do
in
that
space
as
well,
really
deeply
involved
in
open
source
yeah.
B
I
know
very
actively
involved
in
CNC
F
and
you
know
I
think
we
were
one
of
the
earlier
contributors
to
even
the
Linux
Foundation.
So
it's
been
a
really
long-standing,
long-standing
contribution,
involvement
and
I.
Think
it's
just
that
perception
of
you
know
a
company.
That's
been
around
a
long
time
that
is
maybe
slowing
down.
You
know
people
understand
people
seeing
the
the
way
that
IBM
is
acting
here.
B
A
A
O'leary
he's
on
my
team
as
well,
and
also
Chris
Hiller,
who
is
the
lead
maintainer
for
mocha,
is
on
same
team,
so
we
talked
pretty
regularly
and
the
ability
to
to
advance
the
work
of
the
foundation
through
the
cross
project
Council,
as
well
as
the
board
and
I
know
you're
on
the
board.
Michael,
so
I'll
turn
it
over.
You
yeah.
B
I
mean
really
I
see
our
involvement
is
like
grass
roots
in
the
projects,
like
you
said,
to
working
on
the
cross
project
Council
to
help
with
the
governance
and
help
bring
new
projects
in,
but
we're
also
involved
in
the
board.
Todd
Moore
has
been
the
chair
of
the
board
for
for
a
while
and
he's
been
a
really
big
supporter
of
nodejs
as
well.
B
J's
Foundation
getting
support
with
things
like
you
know:
github,
repos,
use
of
our
slack
channels
and
zooms
and
all
those
things,
those
small
things
which
can
actually
make
a
pretty
big
difference
without
having
to
be
a
project.
So
you
know
kedai,
the
the
foundation
already
supports
projects,
but
this
would
let
you
know
non
projects
you
know.
Have
a
people
come
together
to
collaborate
on
areas
under
the
foundation
that
are
not
necessarily
tied
to
specific
projects.
A
B
A
B
B
We
were
involved
from
the
very
beginning
in
terms
of
putting
together
the
LTS
release
process
to
support
stable
and
predictable
releases.
We
now
know
that
we're
gonna
get
you
know
a
new
current,
every
April
and
October,
and
that
in
October
that
you
know
the
previous
current
from
April
is
going
to
become
an
LTS
release.
So
we
know
that
you
know
we
have
that
predictability
as
well,
as
we
know
that
we
have.
You
know
thirty
months
of
support
once
the
release
goes.
B
B
So
that's
one
of
the
areas
that
you
know
we're
definitely
active
in
and
working
in,
Gerry
spoon
atoll
is
helping
to
lead
an
effort
there
on
putting
together
some
best
practices,
and
you
know
then
taking
those
best
practices
and
making
sure
we
have
good
tools
in
the
node
ecosystem
to
support
them.
Security
is
obviously
one
that's
always
important
to
people,
and
you
know:
we've
been
involved
in
the
security
working
group,
helping
to
define
things
like
the
security
processes
and
helping
to
manage
the
security
releases.
B
There's
a
lot
of
work
just
pulling
together
all
the
different
pieces
of
the
puzzle
to
get
one
of
those
releases
out,
so
we've
been
pretty
active.
There
performance
is,
of
course,
important
because
everybody
wants
to
get
the
most
out
of
heart,
their
hardware
that
they're
buying.
We
have
some.
You
know.
As
I
mentioned,
the
OBM
has
some
large
enterprise
customers
and
and
many
times
those
those
customers
run
in
in
a
number
of
different
languages
and
number
different
countries.
B
So
internationalization
is
important,
so
that's
an
area
that
we've
been
involved
in
as
well
and
then
finally,
it's
just
important
that
we
have
good
quality
releases.
So
we
we
help
with
the
code
quality
efforts,
things
like
the
code
coverage
site.
Other
aspects
of
the
safety
net,
like
Sid
Jim,
was
originally
contributed
by
an
IBM
er
and
just.
B
Yeah
I
think
it's
a
recognition
of
you
know
how
much
we
contribute
that
we
have
10
core
collaborators.
People
who
can
review
and
land
commits,
as
well
as
three
people
on
the
technical
steering
committee,
who
you
know,
help
to
figure
out
the
the
edge
cases
where
the
collaborators
can't
come
to
an
agreement
on
their
own.
And
it's
it's
great
that
we
can
be.
You
know,
contributing
and
helping
to
lead
on
on
that
front
and.
A
B
Her
talk,
she's
talking
about
some
great
work,
that's
being
done
in
the
package
maintenance
working
group
along
the
lines
of
you
know,
helping
maintain
errs
to
be
able
to
test
not
not
the
same
messaging,
but
something
along
the
same
lines
in
terms
of
being
able
to
test
dependencies
people
who
depend
on
your
modules
and
packages.
So
anyway,
that
should
be
an
interesting
talk
as
well.
I.
A
B
So
what
are
the
other
things
you
know?
This
is
in
the
in
the
community,
but
also
this
kind
of
important
is
you
know
we
have
put
a
fair
amount
of
work
to
make
sure
that
no
GS
runs
on
IBM's
platform,
so
anything
from
you
know
Linux
on
Z
Linux,
on
PE,
AIX
or
even
IBM
I,
where
Jesse
Gore's
insky,
who
does
a
great
job
advocating
for
open
source
on
IBM.
All
I
tells
me
it's
like
up
to.
25
percent
of
our
customers
are
using
node
on
IBM
I.
Now
it's
it's.
B
To
the
conferences,
it's
just
great
to
see
how
excited
people
are
about
nodejs
in
in
that
environment,
where
you
know
there
they
are
in
businesses,
maybe
they're
supporting
manufacturing
or
some
other
types
of
factories,
and
it's
it's
great
to
see
them
starting
to
use
node.js
for
all
that
kind
of
work
as
well.
No
json
the
mainframe
and
that's
right
and
mainframe
is
is
another
area
where
you
know
people
there's
significant
interest
of
people
starting
to
run.
You
know
the
right
workloads
to
get
the
advantages
that
you
do
with
known.
B
Oh
definitely,
and
on
that
major
deployment
front,
there
were
a
couple
that
we
want
to
share
today,
just
to
show
you
the
scope
of
some
of
the
deployments
that
we
have
in
in
in
IBM.
The
first
one
is
the
IBM
cloud
console.
So
if
you've
ever
gone
to
use
the
IBM
cloud,
it
provides
the
UI
and
this
lets.
You
know
you
create
those
different
services
like
whether
you're
creating
your
kubernetes
clusters.
B
Virtual
servers,
bare
metal
machines,
cloud,
foundry,
type,
applications,
servers,
service
applications.
The
cloud
UI
is
a
node.js
application
supporting
all
of
that.
It
also
provides
sort
of
a
plug-in
framework
in
that
when
we
want
to
bring
a
new
service,
because
the
IBM
cloud
provides
services,
in
addition
to
those
sort
of
foundational
components
like
open
shift
and
kubernetes.
A
B
You
know,
as
we
can
see,
there's
over
50
teams
who
have
taken
advantage
of
that,
so
that
just
gives
you
an
idea
of
how
much
use
there
is
and
that
we
have
50
different
teams.
Who've
just
contributed.
You
know
node.js
applications
to
the
IBM
cloud.
The
the
application
itself
is
over
90
micro
services,
it's
deployed
to
kubernetes
and
it's
distributed
over
10
different.
You
know
geographically
load-balanced
clusters
across
the
world,
so
really
a
big
node
application
that
we
run
24/7
yeah.
B
Yeah,
the
weather
company
is
the
next
one.
In
that
you
may
have
even
gone
there
to
check
your
weather.
You
can
get
the
seven-day
forecast
you
could
also.
You
know
it
has
a
whole
bunch
of
API,
and
so
it
can
help
you
make
your
application
better
by
incorporating
weather
data
and
in
a
lot
of
cases
you
know
that
can
really
add
value.
B
For
example,
if
you've
got
you
know
a
site
that
helps
people
pick
when
they
want
to
plant
seeds
or
anything
else
related
to
growing
food
or
or
plants,
it'd
be
great
to
be
able
to
give
them
insight.
In
terms
you
know,
maybe
when
it's
gonna
be
a
good
time
to
do
things
based
on
the
weather
or
not
yeah,.
B
That
stuff's
really
really
really
important
yeah.
Looking
back
to
the
application
itself
again,
it's
another
big
nodejs
application.
It's
it
serves
buildings
locations,
you
know
all
sorts
of
cities,
zip
codes,
internationalize,
we
mentioned
internationalization
before
60
languages,
230
different
locales
and
it's
deployed
in
four
different
regions:
seven
kubernetes
clusters,
four
hundred
more
than
four
hundred
worker
nodes,
dozen
services,
which
can
be
like
maybe
three
replicas
or
100,
replicas,
again
all
running
on
the
IBM
cloud
24/7.
So
you
know
another
really
big,
nodejs
application
that
you
know
IBM
runs
and
operates.
B
We
just
want
to
mention
a
couple
ways
you
can
deploy.
Nodejs,
you
know
one
is
the
ivan
public
cloud
and
the
other
one
is
IBM
cloud
pack
for
applications.
If
you
don't
necessarily
want
to
move
all
of
your
workload
up
up
to
the
cloud
in
terms
of
the
IBM
cloud,
you
know
it's,
it
provides
a
whole
bunch
of
services,
sort
of
foundational
services,
so
things
like
OpenShift
kubernetes
over
lists,
you
know,
but
in
addition
to
that
it
loads
in
a
whole
bunch
of
services.
B
So
if
you
need
a
database,
you
can
get
a
service
for
that.
If
you
need
to
connect
to
I,
owe
t
devices
there'll
be
a
service
for
that.
If
you
need
to
send
emails,
there'll
be
a
service
for
that,
so
it
it's
broadly.
You
know,
has
the
data
centers
all
over
the
world
and
really
provides
you
all
the
components
that
you'll
need
to
deploy
your
nodejs
application
successfully
and
scale
as
you
need
to
across
the
world.
B
It's
it's.
You
know
if
you
don't
want
to
move
all
your
applications
up
to
the
cloud.
The
way
I
look
at
IBM
cloud
pack
for
applications
is
there's
lots
of
great
projects
in
open
source
and
I
can
go
and
collect
all
those
together
myself,
but
it's
a
little
bit
like
building
the
car
by
yourself.
Do
you
want
to
go
out,
buy
all
the
parts
source
all
the
parts
put
it
together?
B
That's
probably
going
to
take
you
a
lot
of
time
and
effort
just
to
get
to
that
point,
and
once
you've
done
that
you're
you're,
probably
on
your
own,
for
support,
because
you've
built
your
own
custom
bespoke.
You
know,
infrastructure,
IBM
cloud
pack
for
applications
builds
on
those
tried
and
tested
open-source
applications,
but
brings
them
all
together
into
a
nicely
packaged.
B
You
know
offering
so
includes
OpenShift
things
like
Tecton
runtimes
and
packages
them
all
together
as
an
integrated
piece.
You
can
buy
and
then
get
support
for.
So
if
you
don't
want
to
move
all
your
applications
up
to
the
public
cloud,
IBM
cloud
pack
for
applications
is
a
great
option,
for
you
know
having
a
cloud
like
infrastructure
being
able
to
deploy
cloud
native
applications
in
your
own
environment
or
some
mix
where
it's
it's
a
hybrid.
You
know
some
things
locally
and
some
things
up
in
the
cloud
as
well
and.
B
So
you
know
once
you
get
your
application
to
production,
it's
of
course
important
to
many
people
to
be
able
to
have
a
trusted
partner
that
can
that
can
help
you
out.
Not
everybody
has
enough,
has
as
much
time
and
resources
to
be
able
to
be
involved
in
the
nodejs
community
so
be
able
to
like
you
know
if
you
find
a
bug,
contributed,
PR
or
get
it
reviewed,
get
it
landed,
and
that's
something
that
you
know
IBM
can
do
for
our
customers
because
of
our
involvement
there
we
have
a.
B
We
have
a
number
of
different
options
because
you
know,
depending
whether
you're
running
in
the
IBM
cloud,
you're
running
on
Red
Hat,
Enterprise
Linux,
you
know
through
our
Red
Hat
partnership
or
your
you
know,
deploying
on
your
own
in
the
mainframe
you're
going
to
need
two
different
types
of
support.
So
we
have
a
number
of
different
support
offerings
and
you
can
find
out
more
information
about
those
at
that
link
and.
A
Speaking
of
finding
out
more
information
to
learn
more
about
all
the
stuff
that
we've
been
talking
about,
you
can
go
to
developer.
Obm
dot-com,
slash,
Technology,
slash,
nodejs,
it's
right
on
the
home
page
of
the
developer.
Dot
I
began
ibm.com
site
as
well,
and
there
are
a
number
of
articles
and
tutorials
and
deployment
options
and
all
the
things
that
we've
been
talking
about
are
available
there
as
well.
Yeah.
B
There's
a
whole
bunch
of
great
content.
If
you're
interested
what
you
know
any
of
those
a
number
of
our
collaborators
are
doing.
We
have
a
video
series,
it
talks,
you
know
one-on-one
with
the
people
about
what
they're
doing
in
the
community,
and
you
know
a
wealth
of
articles
on
things
like
security
and
how
to
do
deployments
and
and
that
kind
of
stuff.
So.