►
From YouTube: Jakarta EE Community Call - March 2020
Description
Jakarta EE Community Calls are intended for the wide Jakarta EE community providing progress on the releases and activities related to Jakarta EE.
Agenda:
- Getting started guide for Jakarta EE contributions (Steve Millidge)
- Jakarta EE 9 release - Jakarta EE Platform project member (Kevin Sutter)
- Jakarta EE 9 plan and progress
- Update from the Eclipse Foundation
- News, events, programs, marketing
- Topics / questions from the community
A
Hi,
everyone
welcome
to
another
Jakarta
community
call
today
were
here
already
with
with
Kevin
Sutter
from
IBM,
who
is
leading
the
effort
of
being
Jakarta.
He
nine
breweries,
and
he
will
be
talking
about
that.
But
I'm
here
presenting
the
agenda
for
today's
meeting
and
I
do
want
to
recognize
that
were
living
in
a
little
bit
different
situation,
then
in
February,
at
least
in
this
western
hemisphere,
were
all
impacted
by
the
corona
virus.
B
Thank
you,
okay.
So
what
I
wanted
to
do
today
is
kind
of
walk
through
some
of
the
items
related
to
our
current
jacquard
ee9
plan,
where
we're
at
with
the
progress
and
then
even
touch
on
some
of
the
process.
I
know
we've
been
getting
a
lot
of
questions
on
the
various
mailing
lists
on
you
know
how
do
I
contribute
and
what
what's
still
left
to
do?
B
You
know
people
are
seeing
the
API
is
getting
done
and
they're
wondering
what
else
needs
to
be
done
and
how
can
I
help
contribute
so
I
want
to
try
to
walk
through
that.
I
do
have
a
presentation
but
I'm
going
to
be
kind
of
bopping
over
to
a
browser
quite
often,
and
actually
walk
through
different
things
related
to
where
we're
at
and
in
what
the
process
is.
B
B
The
majority
of
our
discussions
happen
on
to
mailing
lists,
there's
the
platform
mailing
list
and
that's
really
the
Jakarta
ee9
platform
development
mailing
list.
But
a
lot
of
the
discussions
are
happening
there
and
then,
when
we
need
to
reach
all
of
the
different
specification
projects,
there
is
a
mailing
list
for
the
specification
project
leads.
Now
anybody
can
subscribe
to
these
mailing
lists,
so
you
don't
have
to
be
on
the
platform
project.
You
don't
have
to
be
a
project
lead
in
order
to
be
on
these
mailing
lists.
Anybody
can
subscribe
to
them
and
monitor
the
discussion.
B
That's
happening
there.
That's
where
Steve
and
I
and
others
you
know
Bill
Shannon,
David
Blevins.
You
know
we're
all
working
together,
trying
to
get
jacquard
ee9
together,
figure
it
out
and
get
it
delivered,
and
so
that's
where
our
discussions
are
mainly
happening.
Now,
when
you
drop
down
a
level,
then
you
know
maybe
you're
interested
in
JSF
or
I
guess
you
know
now:
it's
Jakarta
server
faces
and
are
maybe
you're
interested
in
enterprise,
beans
or
JPA.
B
B
B
B
You'll
notice,
that
the
number
one
item
here
at
the
top
of
our
list
is
namespace
changes,
and
so
the
biggest
change
that
we're
doing
for
jacquard
ee9
is
changing
from
the
java
X
package
name
to
the
Jakarta
package
name,
and
this
is
a
requirement
that
had
to
be
put
in
place
based
on
the
contribution
from
Oracle,
and
so
the
this
is
nothing
that
we
could
challenge
or
anything.
We
knew
that
we
had
to
do
it,
so
this
is
the
biggest
change
that
we're
doing
and
we're
trying
to
limit
the
changes
to
just
this
namespace
change.
B
There
are
a
couple
of
exceptions
which
I'll
touch
on
when
we
go
back
to
the
charts
where
individual
components
had
to
do
a
release
plan.
But
this
way
we
could
define
a
single
release
plan
that
covers
99%
of
all
of
the
work.
That's
going
in
across
all
of
the
components,
so
we
did
identify
this
namespace
change
the
specification
documents,
so
those
of
you
that
are
familiar
with
Jakarta
ee8,
the
platform
specification
and
the
web
profile
specification.
Those
were
the
only
two
that
actually
had
text.
B
You
know
real
text
from
past
releases
of
Java
EE
and
those
were
the
only
documents
that
had
all
of
that
information
from
the
past
releases.
All
of
the
component
pieces,
the
JSP
JSF
EJB
JPA.
All
of
those
we
only
had
boilerplate
specifications
and
all
it
was-
was
our
scope
statement
for
that
component
and
then
we
relied
on
the
Java
doc
and
that's
what
we
did
for
the
specifications.
The
component
specifications
in
the
past,
but
now
all
of
the
source
code
for
the
specifications
is
available
to
every
component.
B
So
we're
not
identifying
this
as
an
absolute
requirement
for
Jakarta
EE
9.
But
since
all
of
the
source
code
is
there,
almost
all
the
components
are
stepping
up
and
saying
yes,
I
do
want
to
update
the
you
know
the
specification
document
and
get
that
released
as
a
real
specification
and
so
almost
all
components.
Actually
I
haven't
heard
of
any
component.
That
is
not
doing
this
work,
so
we're
all
very
active
on
trying
to
get
this
locations
up-to-date.
B
B
We
don't
want
to
enforce
a
require
any
new
implementations
to
implement
these
older
items.
So
we
are
not
enforcing
backwards.
Compatibility
with
previous
releases,
which
occurred
at
89,
so
we're
trying
to
set
a
new
bar
and
the
bar
is
lower
and
we're
trying
to
set
a
new
lower
bar
for
entry
for
new
implementations.
B
So
we
are
not
requiring
backwards.
Compatibility
for
Jakarta
e9
now
individual
implementations-
they
they
may
very
well
need
to
do
that
or
want
to
do
that.
I'll
speak
from
my
personal
experience
with
IBM
and
our
Liberty
application
server
is
yes,
we
will
have
backwards,
compatibility
with
the
previous
releases,
because
that
that's
what
we
do
and
other
implementations
will
probably
be
doing
the
same
thing
but
from
an
overall
specification
view,
point
from
Jakarta
EE
specification
view
point:
we
are
not
documenting
this
backwards:
compatibility
requirement,
the
other
thing:
the
Java
SE
version.
B
We
are
going
to
require
Java
s
11
for
doing
certification
testing,
but
all
of
the
api's
will
be
compiled
at
Java,
SE
8,
and
that
will
that
would
allow
other
implementations
to
actually
build
their
application
server
at
Java,
SE
8
level
and
do
their
testing
at
si
8
level.
But
if
you
do
se
eight,
you
also
have
to
do
SE
11,
so
Java
11
is
the
minimum
requirement
and
if
you
want
to
go
backwards
to
Java
8,
that's
a
separate
step.
B
Ok,
so
just
to
show
here
some,
you
know
the
various
components
that
are
all
part
of
Jakarta
ee9
want
to
highlight
a
few
here:
the
ones
that
were
added
to
Jakarta
EE
9,
so
Java,
SE
11
identified
a
few
technologies
that
were
not
going
to
be
part
of
their
Java.
Se
release
is
going
forward,
so
those
items
are
Jakarta
activation,
XML,
binding,
XML,
Web,
Services
web
services,
metadata
and
soap
with
attachments.
B
There's
also
two
other
specifications
that
were
part
of
Jakarta
ee
8
that
we
are
going
to
now
mark
optional.
One
of
them
is
a
full
specification
enterprise,
web
services,
otherwise
known
as
JSR
109
that
will
be
marked
optional
and
then
there's
an
API
group,
a
2.0
JB
to
point
X,
API
group,
it's
a
specific
API
group,
that's
defined
in
the
EJB
specification
and
that
API
group
is
going
to
be
marked
optional.
B
In
addition,
there's
a
few
specifications
that
are
going
to
be
pruned,
and
basically
these
are
all
of
them
that
were
in
the
stable
project
within
each
4j
or
within
jakarta,
EE
and
so
xml
registries
jacks
are
jack's
RPC,
the
deployment
and
management
and
all
of
those
will
be
pruned
removed
from
jakarta
ee9.
The
other
piece
that
we
voted
to
remove
is
the
distributed
interoperability,
that's
defined
in
the
EJB
3.2
core
specifications.
Specifically,
this
is
chapter
10,
so
one
to
highlight
that
that
that
will
also
be
removed.
B
The
other
thing
that
I'm
going
to
be
touching
on
as
we
get
into
the
project
board,
are
the
different
waves
and
we've
identified
these
dependency
waves.
So
as
each
of
these
technologies
are
completed,
we
know
that
some
of
them
have
to
be
done
before
others
and
the
ones
that
are
at
the
it's
called
an
independent
wave
in
the
release
platform.
We
also
call
it
our
release
plan.
We
call
wave
zero
as
well,
so
the
independent
one
is
wave
zero
and
then
you
can
see
that
we
have
out
to
wave
seven.
B
One
of
them
was
Jakarta
activation
and
that's
mainly
because
that
was
kind
of
dropped
from
Java
SE
11
and
we
wanted
to
bring
that
in
and
so
there
we
want
to
have
a
separate
release
plan
for
that
and
it
was
actually
dropping
a
UI
library
that
no
longer
exists
and
so
that
affected
their
API
a
little
bit,
and
we
wanted
to
update
that
so
that
required
a
separate
release
plan
and
for
EJ
B's.
There
was
another
API
that
was
removed
a
long
time
ago,
the
identity
and
that
affected
one
of
their
API
s.
B
And
then,
as
you
just
heard,
there
were
several
updates
to
the
EJB
with
making
the
API
group
the
two
point:
X
API
group
optional,
and
by
dropping
support
for
the
distributed
Interop
and
so
there's
more
of
a
ripple
effect
through
their
release
plan.
And
so
then
they
did
their
own
release
plan
as
well.
B
We
are
trying
to
track
all
of
the
work
with
the
project
boards
and
this
is
where
people
are
asking:
okay,
but
I,
don't
know
what
needs
to
be
done.
So
this
is
what
I
you
know
and
how
can
I
contribute.
So
this
is
what
I
want
to
do
is
kind
of
walk
through
what
we're
doing
with
the
project
board
and
what
are
the
different
pieces
that
each
of
these
components
are
requiring
so,
first
of
all,
before
I
go
into
the
detail.
B
I
want
to
mention
the
four
pieces
that
we
need
in
order
for
a
component
to
release
or
a
specification
to
release.
We
need
all
of
the
api's
updated
to
move
from
the
java
x-2
jakarta
namespace.
We
need
while
the
specifications
I
mentioned,
it's
not
a
firm
requirement,
but
all
of
the
components
are
working
towards
that
goal.
So
we
will
have
a
complete
complement
of
specifications.
B
B
So
the
first
column
that
I
kind
of
want
to
highlight
are
all
of
the
api's.
Now,
just
this
week
we
were
able
to
complete
a
milestone
or
release
candidate
for
all
of
the
api's
across
all
of
jakarta.
Ee9
back
on
my
chart,
I
had
indicated
that
even
the
platform
and
web
profile
the
release
candidate,
one
for
those
complete
packages.
Those
were
released
this
week
as
well.
So
all
of
these
are
available
in
maven
and
so
I'll
just
gonna
show
that
all
of
the
different
api's
are
available.
B
Now
we
did
it
this
way
to
put
to
make
them
available
in
maven,
so
that
external
projects,
not
only
the
EE
4j
stuff,
but
all
the
external
projects
could
start
experimenting
with
this.
I
know
that
we
have
started
to
do
it
within
IBM
and
I'm
sure
other
organizations
have
done
it
too.
Lean
people
have
probably
started
to
take
a
look
at
this
as
well
and
starting
to
see.
B
What's
going
to
be
the
impact
by
bringing
in
all
of
these
new
api's,
so
you'll
notice,
also
I
have
mentioned
waves
and
you'll,
see
that
there's
different
waves
I
have
labels
on
all
these
different
things
across
the
board
if
you're
not
familiar
with
project
boards
having
these
different
labels
makes
it
very
easy
to
filter
information.
So
as
an
example,
let's
pretend
I
want
to
only
look
at
the
items
that
are
coming
in
wave
1.
So
now
by
just
filtering
on
wave
1,
you
can
see
kind
of
where
we're
at
across
the
project.
B
You
can
see
that
you
know
the
majority
of
the
projects
are
still
over
here,
where
we're
trying
to
get
through
the
early
phases
of
the
checklist
and
then
there's
a
few
more
that
are
moving
forward
and
we've
got
two
that
are
almost
ready
to
step
into
the
review
cycle
and
now
I
had
sent
out
a
request.
Last
week
and
I
know
that
al
the
expression
language
we
are
trying
to
move
that
forward.
B
We've
got
concurrency
that
we
are
trying
to
move
forward
as
well,
and
hopefully,
we've
got
bean
validation
coming
as
well,
and
what
I
want
to
do
is
I
want
to
try
to
take
these
through
the
process
to
actually
get
them
all
the
way
through
the
process
of
creating
their
their
PRS,
which
I'm
going
to
talk
about
and
doing
the
final
releases
just
to
try
to
get
this.
You
know
the
wheels
greased
basically
to
try
to
show
that
the
process
is
working
and
to
give
view
of
how
to
get
there
as
an
example.
B
Here
you
know
it's
very
easy
to
put
in
a
different
wave
and
you'll
notice
that,
like
for
wave
0,
there
are
some
things
that
are
out
here
where
we
are
trying
to
get
it
ready
for
a
final
review,
and
so
there's
different.
You
know,
depending
on
the
state
of
each
of
these
components,
they'll
be
across
all
these
different
columns
as
we're
trying
to
move
them
forward.
B
Okay,
so
I
came
back
here
because
I
kind
of
wanted
to
highlight
these
waves
and
what
we
are
trying
to
do
now.
I
know
these
dates
are
not
not
necessarily
achievable.
At
this
point,
I
I
went
very
conservative
with
these
dates,
but
I
looked
at
all
of
them
being
sequential
in
saying,
okay,
we
needed
wave
one
completely
done
before
we
do
wave
two
completely
done
before
we
do
wave
three
and
I
know
in
reality.
That
is
not
really
the
case.
B
When
we
digit
card
ee8,
we
had
a
lot
of
overlap
and
that
and
that's
all
good
that
we
have
this
overlap,
but
just
to
try
to
lay
out
the
overall
schedule.
I
did
it
very
conservatively
and
did
it
sequentially
and
then
that's
why
we're
trying
to
get
some
of
these
components
across
the
finish
line
for
wave
one
so
that
we
can
really
see
okay?
How
much
work
is
that
to
get
to
wave
one
get
it
complete,
get
the
ballots
started
and
then
apply
that
across
all
the
other
components
to
find
out.
Okay.
B
B
Because
I'm
going
to
show
a
little
bit
on
what
we
actually
need
from
each
of
these
components.
So
if
people
are
asking
what?
What
is
it
that
we,
you
know
where
can
I
help?
What
I
would
first
do
is
take
a
look
at
a
components,
specification
version,
epic
issue,
so
any
of
those
issues
that
are
on
the
project
board.
It
has
a
checklist
in
here
of
all
the
items
that
need
to
be
done
in
order
to
be
complete
so
like
this
one
is
JPA.
B
I
know
that
that
team
is
working
on
updating
their
specification,
but
I
know
it's
not
complete
either.
So
if
anyone
has
any
interest
in
helping
out
the
JPA
team
on
doing
their
specification,
this
would
be
a
good
component
to
maybe
you
know,
get
involved
with
theirs.
I'm
going
to
go
into
some
other
detail
here
as
well.
The
API
is
we've
already
talked
about,
and
everybody
has.
The
API
is
available
in
maven
central.
So
that's
all
good.
We've
got
the
tcks
that
all
need
to
be
updated.
B
The
compatible
implementations
need
to
be
updated,
and
then
we
need
to
get
into
the
final
preparation
for
the
release.
So
this
is
where
everyone
you
know,
if
you're
looking
to
help
out-
and
you
have
an
interest
in
a
particular
technology,
find
out
where
this
team
is
at
looking
at
this
checklist
and
then
contact
that
team
via
their
mailing
list
and
find
out
how
you
can
help
out.
Most
of
it
will
be
second
stop
that
Oh
same
thing
there.
Okay,
most
of
the
most
of
the
work,
is
going
to
be.
B
You
know,
divided
up,
there's
probably
going
to
be
multiple
people,
they're
looking
for
pr's
they'll
be
reviewed.
You
know,
as
you
generate
more
experience
and
Carmo
with
the
project
I
mean
then
there's
a
chance
of
getting
invited
to
be
a
committer
as
well.
So
there's
a
lot
of
benefits
for
helping
out
but
I.
B
Okay,
so
now
I
just
want
to
get
into
a
little
bit
more
detail
on
each
of
the
items
that
need
to
be
done
to
see
if
there's
areas
where
you
might
have
interest
in
helping
out
the
specifications.
So
we
want
to
get
rid
of
the
boilerplate
specifications
and
put
the
real
specifications
in
place.
All
of
the
specifications
source
for
all
of
the
components
are
now
available
and
almost
all
of
them
are
in
the
respective
components.
B
Github
repos
I
do
have
a
link
here
and
I
will
be
making
these
charts
available
as
well
via
that
the
folder
that
Tanja
sets
up,
and
so
all
of
these
different
links
will
be
available
to
you.
But
in
case
the
component
that
you're
interested
in
doesn't
have
the
real
source
yet,
and
it's
still
the
boilerplate,
then
this
link
here
will
help
you
find
the
source
and,
if
you're,
having
an
issue
with
finding
it,
just
ping
me
directly,
and
we
can
get
you
going
on
that.
B
One
thing
that
we
have
found
is
that
large
specifications
are
easier
to
manage
if
they're
broken
down
into
chapters
so
I
know
I
helped
with
the
platform
spec.
The
server
faces
spec
in
the
enterprise
being
spec,
just
breaking
it
down
into
chapters
it
makes
it
easier
to
consume
so
for
people
that
are
doing
the
updates,
it
makes
it
easier
to
just
kind
of
confine
yourself
to
a
single
chapter
and
granted.
B
But
the
idea
here
is:
we
don't
want
someone
to
dive
into
a
whole
specification,
let's
say
server
faces,
and
then
they
they're
working
on
a
PR
that
the
you
know
huge
document
and
then
pretty
soon.
Other
people
are
putting
stuff
in
and
then
you've
got
merge
conflicts
and
that
just
makes
it
very
difficult.
So
take
a
look
at
that.
If
you've
got
a
large
specification
of
may
be
worthwhile
to
break
it
into
chapters,
if
it's
a
small
spec,
then
maybe
it's
better
just
to
leave
it
single
a
single
source
file.
B
It's
really
up
to
each
component
to
decide
that
and
there's
kind
of
like
a
two-step
process.
The
first
thing
is
just
to
what
I'm
calling
two
colorizing
it
and
it's
basically
all
of
the
references
to
the
old
Java,
EE
stuff,
the
old
Java
EE
links,
there's
references
to
old,
Java,
EE,
URLs
and
websites,
old
Java,
EE
technology
names,
there's
a
lot
of
things
there
just
to
get
it
to
card
eyes,
and
so
that
was
a
first
step
like
this
is
what
I
did
with
the
platform
specification
for
Jakarta
ee
8.
B
So
that's
kind
of
the
first
step.
But
then
the
next
step
is
getting
it
to
the
Jakarta
ee9
level
and
that's
doing
all
of
the
updates
from
Java
X
to
Jakarta.
I
am
now
a
lot
of
times.
That's
just
like
a
global
change.
Yeah,
it
I
have
found
it
easier
to
just
do
a
global
change
and
then,
as
you're
going
through
and
reviewing
it,
maybe
you're
going
to
find
some
exceptions
to
the
changes
that
were
done
to
change
to
Jakarta.
Maybe
there's
some
that
still
had
to
be
Java
X.
B
B
Okay,
the
tcks
every
component
and
the
platform
has
a
TCK
now,
a
lot
of
people,
maybe
you've
heard
the
term
cts
and
that's
kind
of
equivalent
to
the
platform
TCK,
so
I
put
a
link
here.
These
this
link
provides
all
of
the
different
component
tcks
that
are
part
of
the
platform
TCK.
So
there's
a
ton
of
different
directories
under
this
and
there's
also
just
to
be
aware
in
case
you're.
Looking
at
this-
and
you
say,
oh
I
found
a
folder
for
concurrency,
so
all
of
the
tests
for
concurrency
are
in
this
folder.
B
That
may
not
be
the
case
because
maybe
concurrency
has
some
dependencies
on
other
components,
and
so
maybe
there's
another
folder
or
two
that
contains
those
dependency
type
tests.
So
just
to
be
aware,
it's
probably
good.
You
know.
If
you're
looking
for
things
related
to
your
component,
you
might
have
to
do
a
search
across
this
whole
directory
to
find
out
if
there's
other
tests
that
are
bringing
in
your
particular
component,
that
also
need
to
be
updated.
B
Now
the
platform
TCK
is
dependent
on
a
very
archaic
test
harness,
but
it
does
work
and
that's
what
the
platform
TCK
is
currently
set
up
to
do.
There's
quite
a
discussion
going
on
our
platform
mailing
list
where
we
are
trying
to
figure
out
a
way
to
I,
don't
know
how
you
want
to
not
standardize
but
to
develop
standalone
tcks
that
can
still
be
used
as
part
of
the
platform
TCK,
so
CDI
and
bean
validation.
Those
are
the
classic
examples
because
they
were
produced
by
Red
Hat
and
they
were
always
separate.
B
Once
he
got
that
set
up
in
your
environment,
then
it
was
pretty
easy
to
to
test
CDI
and
bean
validation.
I
know
and
Iggy
Bear
has
he's
kind
of
started.
This
discussion
on
the
platform
mailing
list
and
using
JSON
B
as
an
example
in
trying
to
get
the
TC
K
is
more
ingrained
with
the
individual
components
so
that
then
they
could
be
tested
on
an
ongoing
basis
without
having
to
wait
until
the
platform.
B
T
CK
is
ready
to
be
tested,
so
there's
benefits
to
having
Lee
standalone
tests,
and
so
that's
kind
of
the
move
that
we're
doing.
But
it's
not
a
requirement
for
Jakarta
ee9.
So
I
want
to
make
sure
that
that's
clear,
there's
no
requirement
to
do
standalone
tcks,
but
some
of
the
components
are
looking
at
doing
it
to
try
and
make
it
more
ready
for
the
future.
We
want
to
figure
out
what
is
the
proper
path
going
forward
for
Jakarta
EE
10,
and
so
that's
why
some
of
the
components
are
starting
earlier.
B
Okay,
so
the
other
piece
that
has
to
be
done
is
a
compatible
implementation,
now
GlassFish
Eclipse
class
GlassFish,
that
is
the
overall
platform
compatible
implementation.
So,
when
we
release
the
platform
specification-
and
we
have
the
platform
API
is
we
require
GlassFish
as
being
the
compatible
implementation?
B
There's
also
some
compatible
implementations
that
are
built
separately,
but
they
still
feed
into
GlassFish
and
so
I
put
a
list
there.
So
maybe
you
know
if
someone
on
the
call,
if
you
have
an
interest
in
jax-rs
well,
Jersey
is
the
compatible
implementation
for
jax-rs
and
then
that
feeds
into
GlassFish.
So
maybe
you
have
an
interest
there,
where
you
could
help
out
with
a
compatible
implementation
of
Jersey
and
there's
corresponding
ones.
Mahara
is
JSF,
so
Cheerios
for
security,
Tyrus
websockets
yes'm
is
JSON.
B
B
Metro
is
a
bunch
of
different
items,
it's
still
a
separate
deliverable,
but
it
it
covers
many
different
specifications
and
that's
why
the
the
link
is
not
direct,
because
there
are
so
many
different
ones
and
then,
of
course,
we
have
a
few
standalone
compatible
implementations
and
these
feed
into
the
items
that
I
mentioned
before,
with
CDI
and
bean
validation,
and
so
those
compatible
implementations.
Yes,
they
are
developed
separately,
they're
maintained
in
separate
repositories,
but
they're
brought
in
as
part
of
the
overall
deliverable
for
Jakarta
EE.
B
Ok,
so
that's
where
I!
This
is:
where
I'm
going
to
be
finishing
up,
yep
I'm
on
this
discharge
here,
just
to
kind
of
bring
us
back
and
describe
the
different
parts
that
need
to
be
done
now,
the
api's
as
I've
described.
They
should
pretty
much
be
done,
except
for
the
items
that
we
find
during
testing,
and
we
have
found
a
few
things
during
testing.
So
we're
doing
new
updates
to
the
release,
candidates
or
milestone
drivers,
but
the
api's
are
pretty
much
done.
B
Specifications
are
there's
a
lot
of
work
left
to
be
done
on
those,
especially
the
larger
specifications.
So
if
you
want
to
help
out
in
an
easy
area
to
try
to
you
know
if
you're
really
good
at
asking
doc,
that
would
be
fantastic
because
we
need
that
type
of
conversion
to
get
them
all
into
ASCII
doc
format
and
then
the
tcks
and
compatible
implementations.
B
Okay
and
then
just
put
a
few
pointers
out
here,
the
overall
flow
everything
that
I've
talked
about
so
far
with
you
know,
going
through
the
different
parts
and
preparing
for
a
release,
that's
all
covered
by
the
operations
guide.
So
that
is
the
number
one
place
if
you're
wondering
okay,
where
do
I
go
to
find
out
what
the
flow
is?
Why
are
they
trying
to
do
this
part
of
the
process
now
versus
later
or
whatever
take
a
look
at
this
operations
guide?
B
That
should
give
you
an
overall
flow
of
what
we
are
trying
to
do
for
releasing
the
specification.
I've
walked
over
the
project
board.
Quite
quite
a
bit.
I've
mentioned
the
mailing
lists.
We
also
have
a
new
link
here.
The
jacquard
EEE
connect
mailing
lists
that
that's
something
that
was
just
put
in
place
so
that
you
know
Eclipse
has
a
total
list
of
all
of
their
mailing
lists,
but
then
you
have
to
filter
it
and
try
to
figure
out
which
ones
are
related
to
Jakarta
EE.
This
one
here
takes
you
to
that
level
of
detail.
B
So
it's
a
one-stop
shop
to
look
at
all
of
the
mailing
lists
that
are
available
for
Jakarta,
EE
and
I've
mentioned
all
of
the
different
communications
that
we
do
on
the
platform
mailing
list.
We
also
have
a
weekly
call
it's
every
Tuesday,
except
for
the
first
Tuesday
of
each
month,
because
then
that
time
slot
is
reserved
for
the
pmc
call.
So
basically
it's
three
or
four
other
calls
during
the
month
and
they're
on
tuesdays
and
that
link
that
will
take
you
right
to
the
Google
Calendar
for
the
information
on
that
and
ok.
A
A
Okay,
so
once
Shabnam
is
getting
on,
I
just
want
to
see
if
you
can
see
actually
I
wanted
to
share
I'm,
not
able
to
share
that
so
I
will
at
the
end
here,
show
the
Jakarta
community
drive
and
show
you
where
you
can
find
the
slides
just
in
case
you're
not
familiar
with
it.
So
the
the
folder
is
already
here.
C
A
A
Okay,
so
let
me
just
start
with
recognizing
again
that
were
in
the
brand-new
situation
for
most
of
us
and
we're
trying
to
adopt
to
what's
going
on
and
be
more
present
online
and
what
happened.
The
end
of
February
just
goes
hand
in
hand
with
with
that.
So
our
Jakarta
1
livestream
program
is
is
still
very
popular
and
we
had
one
live
stream
in
Japan
in
Japanese.
It
was
quite
successful.
We
had
six
hours
of
content
220th
and
these
10
sessions
and
we're
looking
to
organize
these
type
of
event
in
a
in
a
local
language.
A
A
C
So
cloud
native
for
java
day
was
a
co-located
event
at
cube.
Con
amsterdam,
which
was
originally
was
supposed
to
happen
on
March
30th,
but
since
cube
Cohen,
has
postponed
the
their
event
due
to
the
Prophet
19
situation.
So
we
also
postponed
the
cloud
native
for
Java
day.
I
just
have
to
mention
that
a
lot
of
work
and
efforts
have
been
put
into
preparations.
C
For
this
event,
we
had
around
hundred
registrations
for
cloud
native
or
Java
day
by
the
time
it
got
cancelled,
but
Joe
Carter,
II
working
group
and
also
the
Marketing
Committee,
are
still
interested
to
run
this
event.
So
we
are
waiting
for
more
updates
from
cube
con
to
confirm
the
dates,
and
so
please
keep
an
eye
out
on
the
cloud
negative
for
Java
a
website
for
more
updates
and
stay
tuned.
It's
going
to
happen,
but
we
just
don't
know
that
it
takes
you
yeah.
A
Thanks
number,
so
you
know
where
we
were
all
looking
forward
to
go
and
visit
Amsterdam
and
connect
with
everyone,
but
you
know
we
will
do
that
just
at
the
later
date,
however,
we
are
still
preparing
for
our
other
conferences,
and
now
most
of
the
conferences
will
be
moving
to
the
and
turning
into
virtual
events,
so
the
nest.
Next
to
that,
we
were
planning
to
attend
and
we
will
still
be
present
in
the
virtual
form,
our
redhead
summit
and
IBM.
Think
so
Shabnam
do
you
have
any
specific
some
on
this
one?
What's
going
on
and.
C
Yeah
Red
Hat
summit
is
going
to
be
on
April
28th
to
29th
and
I.
Think
Evora
has
a
presentation
there
and
as
far
as
I
know,
they
haven't
updated
the
dates
or
the
time
yet,
but
they're
going
to
send
updates
soon
and
for
IBM
think
it's
going
to
be
from
May
5th
to
May
7th
and
again
we
don't
have
the
dates
of
the
exact
schedule
of
the
Jakarta
EE
related
sessions,
but
we're
going
to
once
we
have
more
updates.
A
C
A
Thank
you.
So,
let's
move
on
so
yeah
we're
super
excited
that
we
now
have
additional
compatible
products.
So
right
now
we
have
tiny
tote
in
10
compatible
products
in
total,
so
JBoss
Enterprise,
Application
Platform
by
our
server
and
jus
Jews
and
I'm
sure
I'm
not
pronouncing
this
right,
but
an
apology's
for
that,
but
that's
another
compatible
product
and
then
a
little
bit
more
in
may
be
nicer,
slides
for
presenting
all
the
companies
that
have
their
compatible
products.
So
we
have
six
full
platform
compatible
products
and
for
show
hold
on.
A
This
is
I,
think
it's
six
full
and
six
web
product.
So
we
will
correct
this
light
before
we
share
it
with
you.
But
you
know
this
is
this
is
super
exciting
news
and
it's
good
to
see
that
we're
growing
also
it's
reflected
in
the
Jakarta
working
group
members.
So
we
have
prime
tone
as
the
enterprise
member.
We
have
the
acoustic
as
well
as
the
new
member
as
well
as
the
t-mac
soft.
A
D
So,
as
you
mentioned,
we
have
started
these
two
initiatives:
the
adopter
spec
and
sponsoring
the
croud
casting
out
for
jokes
tears
and
I'll
go
through
a
little
bit
of
detail
of
both
of
them.
So
if
you
take
the
next
slide,
so
this
slide
shows
the
one
that's
changed
there.
You
go,
shows
the
link
for
information
about
adopters
Bank,
and
the
next
slide
will
give
you
how
this
page
looks
like
and
all
the
information
here.
That's
all
you
need
to
be
able
to
sign
up
with
your
jargon
and
examples
for
activities.
D
You
can
do
too
involve
helpful
respects,
like
the
things
Kevin
mentioned
in
his
talk
and
and
other
things.
So
we
have
written
up
a
couple
of
examples
here
for
what
you
can
do
to
help
and
also
there
are
instructions
for
how
to
get
listed
on
these
pages.
So
the
next
slide
will
show
how
a
specification
page
will
look
like,
and
this
jason
processing
hasn't
been
enough
two
by
two
chunks,
and
you
can
see
the
madras
joke
and
so
java
here.
D
D
A
D
D
We
are
have
a
created,
a
podcast
account
and
all
charts
can
set
up
their
events
there
and
a
stream
for
free
like
we're
doing
right
now,
and
the
next
slide
will
show
that
we
already
have
two
events
coming
up.
So
we
have
the
jacks
jug
or
unit
talk
later
today
and
also
the
Istanbul
jug
is
a
sauna
for
an
April
16
and
there
are
a
couple
of
ones
coming
in
between
there
as
well.
So
so
the
rocket
channel
four
jug
is
going
to
a
place.
D
So
the
chromecast
channel
to
navigate
to
is
the
crocuses
io
/
chromecast
under
storge
ee,
jokes,
and
that
will
list
the
page
has
showed
in
the
previous
slide,
where
we
will
get
all
the
upcoming
events
and
the
instructions
for
how
do
you
sign
up
and
get
your
events
out?
There?
Isn't
our
Google
Drive?
It's
kind
of
hard
to
read
of
this
URL,
but
well
you
can
get
the
slice
afterwards
and
we
tweeted
it
so
so
you'll
find.
D
A
I
would
just
add
that
we
are
also
preparing
a
PowerPoint
presentation
for
juggs
that
you
can
use
and
whoever
is
interested
in
jakarta
and
also
locally
present,
so
that
will
come
shortly
and
just
to
thank
you
both
Shabnam
and
evar.
We
put
quite
a
bit
of
work
in
this,
so
you
let
us
know
how
you
like
it
or
don't
like
it,
how
we
can
improve
Shabnam.
Would
you
like
to
add
anything
else?
No.
C
C
A
So
this
is
the
folder
Jakarta
community
and
in
the
year
2020
we
already
have
the
March
folder
setups
here,
where
you
will
find
this
presentation
and
pretty
soon
Kevin
will
drop
in
his
presentation
on
Jakarta
II
in
nine
progress.
So
that's
where
you
can
find
the
information,
but
in
general
this
is
the
folder
where
you
can
find
the
information
on
jugs
on
the
live
stream,
or
you
know
pictures
or
anything
else.
If
you
let
us
know
what
else
you
would
be
interested
in
we'll
put
it
there
as
well.
Now,
let
me
see
send
the
link.
A
The
screen
threeways
yeah
yeah,
so
do
let
us
know
please
how
we
can
improve
and
how
we
can
get
you
more
involved
and
engaged
I.
Do
owe
you
a
session
with
this
and
we'll
get
on
it
as
soon
as
possible
and
I
will
send
it
out
to
the
community
mailing
list
any
questions
or
any
any
anything.
You
want
to
share
at
this
point
in
the
chat.