►
From YouTube: Keynote Address | JakartaOne Livestream 2020
Description
Mike Milinkovich delivers a keynote to the audience at JakartaOne Livestream 2020
Get Social!
Website: jakarta.ee
Subscribe: https://www.youtube.com/user/EclipseFdn
Follow us on Twitter: https://twitter.com/JakartaEE
Like us on Facebook: https://www.facebook.com/JakartaEE/
Join us on LinkedIn: https://www.linkedin.com/groups/13597
Tag us: #JakartaEE
A
And
we're
live
so
we're
moving
on
it's
it's
a
very
fast
day
for
us
here,
I
hope
you're
all
enjoying
it,
and
now
we
have
the
keynote.
I
know
you've
been
waiting
for
the
keynote
for
quite
some
time
now
and
I
am
absolutely
sure
all
of
you
would
agree
that
is
completely
unnecessary
to
introduce
mike
malinkovic,
but
nevertheless
mike
our
executive
director
at
eclipse
foundation,
enabling
us
all
to
help
the
community
and
organize
so
community
can
thrive
on
open
source
so
mike.
B
All
right,
tanya,
thank
you!
So
much,
I'm
very
excited
to
be
here.
Thank
you.
Everybody
for
attending
jakarta.
One
live
stream.
It's
obviously
a
big
day
to
ship
the
jakarta
e9.
B
My
talk
here
is
going
to
be
pretty
brief,
and
but
I
just
wanted
to
start
off
with
with
a
real
congratulations
to
all
of
the
people
that
participated
in
the
release
and
just
wanted
to.
I
mean
I'm
sure,
you've
heard
these
names
before,
but
I
just
wanted
to
take
a
moment
to
thank
folks
like
kevin
sutter
from
ibm,
steve
millage
from
paera
scott
marlow
from
red
hat.
B
B
It's
really
worth
it
to
remember
that,
there's
a
ton
of
people
bit
that
are
behind
all
of
this
at
this
work
and
it's
really
exciting
to
be
able
to
recognize
them.
B
So,
just
to
remember
a
recap:
when
we
talk
about
shipping
a
jakarta
ee
release,
there's
really
three
elements
to
to
the
to
that
release,
and
the
first
one
is,
of
course,
the
open
specifications
and
that's
leveraging
a
specification
process
that
that
we
created
from
scratch
a
couple
years
ago,
as
we
started
this
journey
of
moving
java
ee
into
jakarta
ee,
then
there's
the
open
source,
tck
license
and
process,
and
you
know
the
fact
that
the
tcks
are
now
open
source
is
a
really
big
deal
and
definitely
been.
B
You
know
one
of
the
was
one
of
the
major
milestones
in
starting
up
jakarta,
ee
and
the
fact
that
you
know
anybody
can
and
can
make.
You
know
bona
fide
a
claims
of
compatibility.
I
think
really
helps
helps
us
grow.
The
jakarta
ee
ecosystem
and
then
last,
but
certainly,
not
least
as
the
is
the
compatible
implementations
and
one
of
the
things
that
we
do
with
the
jakarta
ee
process
is
that
before
we
can
ship
or
release
there
has
to
be
at
least
one
open
source
compatible
implementation
available.
B
This
time
around,
it's
eclipse,
glass,
fish
and
as
it
was
last
time
and
but
it's
I
think,
it's
really
important-
that
that
we
have
that
step
in
that
making
sure
that,
before
before,
we
declare
a
spec
release
final,
that
we
have
an
open
source
implementation
that
the
community
can
can
download
and
use.
B
So
those
are
the
three
elements
in
any
jakarta
ee
release
and,
of
course,
jakarta.
Ee9.
The
big
news
is
the
big
bang,
and
really
it's
about
all
about
changing
the
name
space
from
java
x
to
jakarta,
and
you
know
why
did
we
do
that
and
really
the
reason?
Why
was
that
was
the
way
that
we
finally
agreed
to
with
oracle
as
part
of
this
process,
that
we
were
able
to
get
the
ability
to
really
drive
this
platform
forward
in
the
future.
B
So
moving
to
the
jakarta,
namespace
was
necessary
to
to
really
make
this
a
foundation
for
future
innovation.
As
part
of
that,
you
know,
we've
been
steadily
lowering
the
barriers
to
f
barriers
to
entry
to
get
in
involved
in
in
jakarta
ee,
and
this
this
is
a
you
know,
another
step
in
that
process.
B
And
finally,
you
know
doing
the
big
bang.
There
was
a
lot
of
conversation
that
went
into
this
decision
of
changing
the
name
space
and
but
doing
a
single
release
where
the
entire
focus
was
on
the
name.
Space
change
was
something
that
was
very
much
a
a
thoughtful
decision
by
the
community
and
by
the
group
that
governs
jakarta
ee,
because
you
know
this
is
an
enormous
ecosystem.
B
There's
a
lot
of
different
pieces
that
have
to
that
have
to
move
forward
and
by
providing
them
with
a
release
that,
where
the
the
name
space
is
the
single
thing
that
really
changed.
We
think
and
I
think
we're
seeing
the
evidence
that
this
is
going
to
work
out.
That's
going
to
help
the
ecosystem
move
forward.
B
One
of
the
things
that
we're
really
excited
about
is
that,
as
we
went
through
this
release
cycle,
we
saw
123
new
contributors
to
jakarta
ee
and
that's
a
number
that
we
want
to
see
continue
to
grow.
So
please,
if
you're,
if
you're
attending
this
event
and
you're
listening
in
or
listening
later,
think
about
how
you
can
contribute
to
future
releases
of
jakarta
ee,
because
it's
really
your
contributions
that
are
going
to
make
this
entire
initiative
a
success.
B
But
you
know
some
of
the
numbers
just
to
show
you.
The
scale
of
what
we're
talking
about
here
is:
there's.
There's
18
member
companies
now
involved
in
jakarta
the
jakarta
e
working
group
and
we're
up
to
65
million
lines
of
code.
Of
course
that's
including
the
content
of
the
specifications.
But
then
the
tck
is
millions
of
lines
of
code
in
and
of
itself,
and
then,
of
course,
the
glass
fish
code
that
provides
the
compatible
implementation
adds
to
that
total
as
well.
B
So
there's
you
know:
31
open
source
projects
and
a
total
of
60
git
repositories
involved
in
this
effort.
So,
as
you
can
imagine,
it's
there's
a
lot
of
moving
parts
and
coordinating
all
of
the
activities
and
making
a
release.
A
success
does
involve
a
lot
of
work
and
again
I
mentioned
some
names
a
few
moments
ago,
and
it
was
people
like
that
that
really
made
all
of
this
possible
we're
particularly
happy
with
the
what
we
saw
with
jakarta
ee-8
in
terms
of
the
number
of
compatible
implementations.
B
And
so,
if
you
go
back
in
the
history
of
java
ee,
it's
certainly
been
a
while,
since
we've
seen
this
many
fully
certified
vendor
products
for
a
release
of
the
platform,
and
so
one
of
the
things
that
that
we
think
is
really
helping
reinvigorate
this
this
this
ecosystem
is
the
the
ability
for
member
companies
to
more
on
a
more
cost,
effective
basis
label
their
products
as
jared
carta,
ee
compatible.
B
You
know
the
red
hat
products,
jboss
and
and
web
wildfly
open
liberty
and
webster
liberty
from
ibm
fujitsu,
then
apoc
and
primetime.
Now
these
are
and
there's
there's
several
more
coming.
So
this
is.
This
is
a
real
sign
of
success
and
adoption
for
the
jakarta
e
platform.
B
So
looking
forward-
and
I
know
that-
there's
a
been
a
panel
and
there's
another
panel
coming
up
and
there's
lots
of
other
people
that
can
they
can
talk
about
this
at
greater
lengths
than
I,
but
we're
really
excited
to
look
forward
to
what's
happening
next
in
jakarta,
ee
and
of
course
the
next
thing
that's
happening
is
jakarta,
ee
9.1,
which
is
going
to
add
java
se11
support
and
moving
so
moving
forward
on
the
version
of
java.
That's
that's
supported
by
it
by
jakarta
ee.
B
So
that's
moving
from
the
net
sort
of
the
next
long-term
support
release
and
then
following
that
is
going
to
be
jakarta.
Ee
10,
which
is
you
know,
really
the
first
time
where
we
are
going
to
be
really
focused
on
new
innovations
and
so
there's
a
number
of
the
different
themes
and
there's
again.
This
is
an
opportunity
for
the
community
to
get
involved
because
none
of
this
is
cast
in
stone
as
yet.
B
But
some
of
the
themes
that
have
been
discussed
for
this
release
is
to
take
better
advantage
of
cdi
and
have
a
more
common
approach
to
how
dependency
injection
works
throughout
all
of
the
specifications
leverage.
Some
of
the
new
innovations
that
are
happening
in
java
se-
and
you
know
taking
advantage
of
some
of
those
things
to
make
better
more
readable,
more
maintainable,
higher
performance
code,
portability
and
vendor
neutrality.
B
I
mean
I've
talked
about
eclipse
glass
fish
a
few
times,
but
in
the
future
right
now
the
eclipse
glass
fish
is
kind
of
tied
to
the
way
the
tck
is
implemented
and
there's
definitely
interest
in
getting
other
implementations.
Open
source
implementations
be
ready
to
be
used
as
compatible
implementations
going
forward,
and
then,
of
course,
then
there's
the
innovations
and
the
specifications
themselves.
B
So
the
idea
is
there's
at
least
10
specifications
that
have
already
said
that
they
want
to
participate
in
a
future
release
by
modifying
their
their
specs
and
and
bringing
them
forward.
I
mean,
of
course,
that's.
You
know,
that's
originally
why
this
this
whole
process
started
and
that's
very
exciting,
to
see,
there's
a
lot
of
work
that
we
can
still
do
to
make
the
process
itself
even
simpler
and
more
streamlined.
So,
of
course,
we're
going
to
do
that
and
refactoring
the
tcks
so
that
individual
specs
can
have
their
own
standalone.
B
So
with
that-
and
I
think
I've
said
this
more
than
once-
we're
really
looking
for
the
community
to
get
engaged
so
please
come
and
participate
in
the
jakarta
e
working
group,
the
jakarta
e
community.
You
can
get
connected
with
us
through
twitter,
using
those
handles
or
those
ids
and
but
really
participate
and
contribute
in
the
specification
projects,
the
tck
projects
and
helping
drive
forward
with
these,
with
these
compatible
implementations
going
forward.
B
So
with
that,
I
thank
you
and
perhaps
have
managed
to
give
a
few
minutes
back
to
the
agenda
of
the
event
and
I'm
looking
forward
to
to
seeing
how
the
the
event
goes
for
the
rest
of
the
day
and
thank
you,
of
course,
to
to
to
tanya
and
hudson
for
all
the
great
work
they're
doing
behind
the
scenes
to
make
today
a
success.
C
Thanks
mike
and
thanks
everyone
for
joining
we're
going
to
take
just
about
a
five
minute
break
here
before
the
next
session
starts.
Mike
did
more
than
get
us
caught
up.
He
actually
even
put
us
ahead.
So
thank
you
mike
and
enjoy
a
couple
minutes.
Everyone
and
we'll
get
started
again
at
12
20
for
the
industry
keynote.