►
From YouTube: Jakarta EE Community Call | 2019-03-27
Description
A Jakarta EE status update for the Working Group and broader Jakarta EE community.
///GET SOCIAL!
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
B
A
A
A
B
D
We
we
had
a
good
news
too
recognizing
that
a
Clippers
last
fish
5.1
has
been
delivered
and
that
was
gotta.
Eight
survived
as
we're
driving
out
towards
Jakarta
each
eight
within
the
community.
There's
a
lot
of
work
and
it's
a
lot
of
important
work.
That's
being
done
within
the
community
to
fully
move
Java
EE
into
into
Jakarta
t
so
exciting
times
and
in
parallel
as
well.
D
We're
looking
at
and
tough
as
a
community
of
nothing
up
on
our
planning
efforts
for
you
not
and
P
bar
will
get
it
to
more
detail
on
that
later
on
in
the
presentation:
okay,
cool,
alright!
So
next
next
slide,
Jenna,
alright,
the
pillars
of
what
we
call
these
the
pillars
of
work
and
that
there
really
AM
initiatives.
B
D
Are
being
driven
out
in
the
community
in
order
to
get
us
to
the
full
delivery
of
be8
and
the
transfer
of
java
ee
into
a
sound
foundation,
you
know
foundation
is
actively
working
with
oracle
on
some
some
of
the
supporting
agreements.
Let
that
work
continues
within
the
community.
We've
worked
on
aspects,
that's
bringing
the
the
java
ee
m
specs
into
into
jakarta,
become
jakarta,
expects
and
what's
guiding,
that
is
the
car
spec
processed
that
is
currently
being
worked
on
within
the
spec
community,
and
we
need
give
us
a
little
update
on
that
in
his
action.
D
So
the
very
important
work
with
regards
to
having
specifications
for
an
int
lock
in
perspective,
as
well
as
a
basis
for
for
future
innovation
in
engine
power
adopt.
You
know,
what's
always
been
fundamental
to
do
what
the
Java
has
been
tcks
and
test
compatibility
gets
and
with
the
TCK
for
Jakarta.
That
list
that
was.
D
D
Cool
so
with
TCGA
front,
the
pKa,
of
course,
is
what
is
contributed
and
is
as
host
to
that.
Eclipse
work
is
underway
on
the
process
side
of
it,
so
that
Jakarta
has
has
a
TCK
process
that
will
explain
how
the
TCGA
is
run
and
and
how
certification
is
is
achieved
so
that
that
that
pillar
is
being
actively
worked
on
and
in
conjunction
with
that
and
the
spec
one
is
really
formalizing
the
approach
for
declaring
a
spec
final,
where
you
find
it
has
it
labeled,
D,
CK's
and
so
on.
D
That's
that's
really
running
the
TCK
which
maps
on
to
the
specifications
that
that
work
is
is
actually
getting
underway
because
the
the
TCK
is
at
is
that
eclipse
and
as
we
drive
towards
Jakarta
ee8
certification,
and
we
do
expect
to
see
eclipses
GlassFish,
open,
Liberty,
pier
server,
wildfly
and
Tommy.
You
know
achieve
achieved
certification
at
you
know
at
some
point
once
the
once,
the
the
specs
have
declared
are
declared
final,
so
that'll
be
exciting
and
conjunction
with.
D
That,
of
course,
is
our
the
marketing
act,
expects
and
we're
marketing
we're
looking
to
the
the
marketing
committee
to
really
formalize
the
local
usage
guidelines,
so
that
we've
got
clarity
on
how
selling
ship
logo,
and
so
on,
as
well
as
PR
activities
that
will
support
Jakarta
ee8,
so
in
a
coordinated
way
within
the
community.
These
efforts,
these
initiatives
are,
are
moving
along
and
and
of
course,
as
I
mentioned
earlier,
moving
along
and
parallel
with
Jakarta
et9,
you
really
split
phases
to
get
clarity
on
what
where
it's
going
next.
D
Alright,
so
how
can
you
help-
and
this
really
is
an
initiative-
that's
owned
and
driven
within
within
the
Jakarta
ee
community?
So
it
is
essential
that
that
that
you
do
help
and
you
do
get
involved
part
of
what's
important-
are
the
agreements
that
that
underpin
what
we
do.
The
membership
contribute
committee
agreement,
the
workgroup
just
a
patient
agreement.
D
These
agreements
need
to
get
to
get
executed
so
that
we've
got
the
right
underlying
governance
to
to
the
project.
So
if
you
do
have
questions
you
know
reach
out
to
the
foundation,
we
can.
We
can
help
with
the
with
the
agreement,
understanding
and
what,
where
you're
at
and
what
needs
to
what
needs
to
get
done,
and
it
was
part
of
the
the
spec
process
that
that
Wayne
will
get
into
next.
We
will
be
doing
a
restructuring
reviews
for
the
specifications.
D
The
pmc
will
be
fully
engaged
in
owning
and
driving
and
helping
get
that
work
done
within
within
the
aspect
projects
that
will
be
created
out
of
the
existing
projects
again
and
more
details
to
the
follow.
You
know.
Part
of
that
will
be
renaming
to
Jakarta
names
and
all
that
will
we'll
get.
Will
get
work
and
be
part
of
the
process
that
will
be
fully
implementing
in
order
to
get
the
Jakarta
ee8
spec
documents
done
next
slide.
D
Alright,
and
you
know
what
what
project
wouldn't
be
complete
without
a
Kanban
board,
so
there
is,
there
is
a
project
board
in
github.
That's
been
been
assembled
by
by
the
community
to
organize
the
work
as
well
as
in
the
left/right
fashion.
You
know
I
spell
out
what
what
needs
to
get
done
in
order
for
us
to
evolve
the
existing
projects
into
into
spec
projects.
A
B
E
Can
drive
know
if
you
could
just
continue
driving.
That
would
be
great,
so
I
actually
do
hear
some
typing.
Could
everyone,
if
you're
not
preparing
to
to
to
ask
a
question
or
join
in
the
conversation?
Can
you
just
please
mute?
Thank
you.
Oh
that
sounds
way
better.
Okay
carry
on
please
alright
next
slide
good.
So
in
the
last
month
I
guess
we
pushed
out
a
new
version
of
the
Eclipse
Foundation
specification
process
like
any
new
new
new
process
that
we
create.
You
know
we
tend
to
rapidly
evolve
it
as
we
discover
deficiencies.
E
So
we
we
notice
a
couple
of
things
that
needed
to
be
addressed
and
we
worked
on
that.
The
Eclipse
Foundation
specification
process
is
not
strictly
owned
by
the
well,
not
even
at
all,
not
at
all
owned
by
the
Jakarta
ee
working
group
or
the
specification
committee
of
that
working
group,
but
they
have
been
instrumental
in
assembling
it
and
very
you
know
their
their
employment
to
this
process
has
been
very
valuable
as
we
move
forward
and
roll
out,
the
specification
process
to
other
groups
will
engage
with
a
a
wider
community
to
to
evolve
it
further.
E
If
you
look
at
the
document,
you'll
notice
that
we
grouped
those
together
really
those
have
meaning
more
to
the
individual
they're,
really
no
different.
As
far
as
the
process
is
concerned,
generally,
we
take
the
a
similar
notion-
or
at
least
in
my
mind,
we
take
a
similar
notion
to
how
semantic
versioning
works.
A
major
releases
may
involve
API
breakage,
a
minor
releases
additions,
the
service
releases,
errata
or
bug
fixes
that
sort
of
thing.
E
Anyway,
from
a
process
point
of
view,
service
releases
are
different
from
major
and
minor
releases.
We
also
formalize
is
more
what
the
specification
committees
ballot
process
looks
like
in
the
previous
version.
We
basically
stated
that
approval
was
required,
and
in
this
version
we
we
qualified
what
what
the
approval
process
actually
looks
like
in
terms
of
a
duration
of
of
how
long
about
it
that
takes
place
and
and
and
whatnot.
There
is
a
of
course,
a
Kanban
board,
a
project
board
in
github
that
it's
now
now
closed.
E
But
if
you're
interested
in
seeing
specific
details
and
discussion
related
to
the
changes,
there's
a
URL
at
the
bottom
of
this
slide
next
slide.
Please
thank
you.
I
thought,
I
would
just
take
a
run
at
describing
the
relationship
between
some
of
these
process
documents
and
kind
of
an
interesting
twist.
E
Tania
and
I
both
had
the
same
problem
with
this
document
and
ultimately,
I
decided
to
go
with
this
I've
actually
attempted
to
draw
it
in
a
UML
sort
of
fashion
and
that
we
both
observed
that
I
did
it
upside
down,
but
anyway,
the
the
development
process
is
kind
of
the
the
route
or
they.
You
know
the
super.
E
The
Super
document
that
guides
the
the
manner
by
which
development
is
done
at
the
Eclipse
Foundation
that
defines
our
open
source
rules
of
engagement,
openness,
transparency,
vendor
neutrality,
meritocracy,
driven
responsibilities,
that
sort
of
thing
it
defines
what
a
committer
is.
What
a
project
is
project
leads,
committers,
sorry
think
emitters
place
PMC's,
because
committers
are
super
important,
our
whole
release
process
and
how
we
do
reviews,
that's
all
described
by
the
Eclipse
development
process.
E
The
Eclipse
Foundation
specification
process
builds
on
that
to
provide
some
guidance
regarding
how
specification
projects
work,
their
lifecycle,
how
the
specification
committee
interacts
with
the
process
specifically
in
terms
of
how
they
do
their
approval
process
through
balloting,
a
process,
but
fundamentally
the
the
eclipse
foundation
specification
process
is
set
up
to
manage
the
intellectual
property
flows
that
that
could
occur
around
specifications
right
so
most
of
basically
well.
Basically,
everything
that's
in
that
document
is
about
ensuring
intellectual
property
flow
is
managed
properly.
Now
that
is
kind
of
generally
how
specification
work
is
done
at
the
Eclipse
Foundation.
E
It
is
possible
and
in
fact
the
it's
actually
possible
for
for
top-level
projects
to
customize
how
the
Eclipse
development
process
is
engaged.
In
we,
when
we
set
this
up,
we
knew
that
different
working
groups
we're
going
to
have
different
requirements
slightly
different
requirements,
so
the
the
Eclipse
Foundation
specification
process
provides
the
baseline.
This
is
what
must
be
done
to
do
specification
work
at
a
minimum,
and
then
it
permits
four
different
working
group,
Jakarta
ee
working
group
to
tune
or
customize
or
specialize
the
the
process.
E
Next
slide,
please
in
terms
of
where
we
are
in
the
process
of
engaging
and
real
specification
work
at
the
Eclipse
Foundation
for
with
the
jacquard
EEE.
We
we
have
a
bunch
of
projects
that
have
API
code
and
right
now.
All
of
the
projects
that
are
engaged
in
that
sort
of
work
are
just
regular
old
Eclipse
projects,
open
source
projects
that
are
basically
subject
to
the
Eclipse
development
process.
E
What
we
need
to
do
is
convert
those
into
specification
projects
so
that
they
can
engage
in
real
specification
work
to
do
that,
we
need
to
have
this
jacquard
EEE
specification
process,
nailed
down
and
I'm
hopeful
that
we
will
we're
getting
close
to
that.
We
need
to
have
the
various
committers
engaged
in
the
project
projects
to
have
be
covered
by
the
necessary
paperwork
which
I
think
we
talked
about
elsewhere,
and
we
need
to
have
scope
statements
for
the
various
specifications.
E
Now
many
the
scope
defines
the
boundaries
under
which
the
or
by
which
the
the
project
team
will
operate
kind
of
the
the
range
of
functionality
that
the
the
project
that
specification
project
will
define,
for
example.
This
is
this
is
considered
a
strong
requirement
as
part
of
managing
the
intellectual
property
flows.
So
we
need
this
before
we
can
move
forward,
and
that
was
the
Kanban
board
that
Paul
presented
earlier
and
we're
inviting
everybody
project
it
team's
project
leads
in
particular
to
engage
in
that
process.
E
We're
gonna
start
doing
that,
just
for
example,
and
also
a
piece
of
this,
and
that
we
believe
we
have
this
piece
sorted
is
we're
gonna,
actually
rename
some
of
these
projects,
so
I've
got
an
example
here.
What
we
currently
call
the
Eclipse
project
for
servlet,
which
was
always
intended
as
a
placeholder
name,
we're
going
to
move
forward
with
a
project
named
Jakarta,
servlet,
again
just
an
example
of
one
of
the
projects
next
slide.
E
B
Wayne,
this
is
Jess
McConnell
about
the
the
the
previous
slide,
yep,
what's
being
done
with
the
existing
projects
that
have
already
released
artifacts
and
stuff
into
maven
central
outside
of
all
these
process
process
specifications
and
all
that
kind
of
stuff
is:
is
there
no
more
of
that
until
these
things
are
locked
in
or
is
it
just
sort
of
the
Wild
West?
Oh
all,.
B
E
E
E
Thank
you
for
your
question.
Sorry.
If
I
punted
too
much
the
for
the
Scopes
projects
have
a
scope,
so
the
project
scope
will
be.
You
know,
for
example,
to
implement
the
spera
to
to
write
the
specification
document
employ
or
provide
an
API
and
and
possibly
a
TCK,
so
interpret
individual
projects
may
implement
some
subset
of
those
things
or
you
know,
and
that
can
be
a
future
looking
statement
as
well.
Even
if
the
sort
of
TCK
is
not
currently
part
of
a
project,
it
could
be.
You
know
at
some
point
in
the
future.
It's
in
scope.
E
E
You
know
I
can
say
that
the
servlet
Jakarta
servlet
project
implements
the
document
that
the
IEEE
API
and
the
TCK
and
then
a
description
of
what
the
servlet
specification
is
and
actually
that
I
went
through
an
exercise
of
trying
to
actually
sort
that
out
and
it
turns
out.
It
was
more
difficult
than
I
had
hoped,
but
not
impossible
anyway,
and
that's
something
we
need
to
work
with.
E
C
C
When
I'm
crazy
there,
on
your
show
to
get
a
page
afterwards,
it's
also
that
we
started
a
little
bit
for
just
defining
activities
for
how
to
get
started
with
a
the
roadmap
for
the
next
releases,
and
that
is
done
on
in
the
Jakara
ii
platform
project
on
the
Eclipse
Jake.
You
know
when
we
have
these
project
boards,
but
also
started
here,
is
to
gather
issues
for
how
you
want
this.
C
C
C
C
All
of
this
work
is
its
ongoing
it
it's
kind
of
with
gathering
all
these
sources
of
information
and
trying
to
get
it
into
this
Jacana
a
bathroom
project
and
get
up,
so
we
can
get
all
ashes
in
there
and
then
we
can
distribute
them
to
the
different
projects
to
stay
update
on
all
this,
encourage
you
to
join
the
platform
mailing
list.
So
that's
the
Jacana
flattened
dead,
also
look
at
the
product
home
for
the
mapping
project
and,
of
course,
also
follow
the
the
project
on
ghetto.
C
A
So
let
me
jump
into
the
marketing
update
if
that's
okay,
I
will
share
email
from
like
the
Nicola
and
and
then
go
through
that.
Just
give
me
a
second
here
and
I
will
put
it
all
the
material
available
to
you
guys
up
to
the
couple,
so
are
just
a
little
bit
on
the
marketing
committees.
We
don't
have
a
the
chair
at
this
point
and,
and
you
know
the
committee
is
managing
that,
through
rotating
into
the
role
on
a
monthly
basis.
A
A
The
guy
we're
trying
to
determine
also
the
how
to
use
those
and
and
created
active
documents
as
well
the
logos.
However,
we
we
will
be
voting
on
them.
Finally,
actually
that's
tomorrow,
March
28th,
so
people
share
that
with
the
community.
I
do
believe
the
community
at
least
it'd
be
a
larger
or
everyone
who
is
signed
up
on
the
working
group
distribution.
Mailing
list
was
consulted
on
on
on
these
as
well.
A
A
We
had
the
boat
actually
yesterday
within
the
steering
committee
and
that
was
approved
so
we're
going
to
acknowledge
that
on
the
upcoming
marketing
hearing
tomorrow
we
have
done
tons
of
updates
on
DITA
Carter
II
website.
And
if
you
go
and
look
at
there,
you
will
see
the
blogs.
You
will
see
the
resources
page
and
of
course
you
are
going
to
see
Jakarta
e
developer
survey
that
we
just
closed
yesterday
and
I'm
really
hopeful
that
all
of
you
had
a
chance
to
participate
and
let
us
know
you
know
how
for
the
organization.
A
A
A
E
B
A
A
A
C
B
C
C
B
C
So
the
intention
is
that
we
will
take
the
existing
specifications
as
they
were
released
for
when
we
did
it
in
January,
when
we
did
the
Eclipse
classification
final
one
release,
then
we
also
released
all
the
the
api's
and
what
we
will
do
is
actually
use
the
same
tag
of
ranch
and
just
update
the
version
numbers
do
the
the
renaming
and
potentially
some
some
XML,
namespaces
or
URLs.
So
we
keep
the
changes
minimal
as
possible.
So
the
intention
is
that
it
will
be
more
or
less
exactly
the
same.
B
C
That
hasn't
been
set
up
yet,
but
I'm
pretty
sure
did
I
think
it's
Dimitri
will
be
in
charge
of
this
as
he
was
little
Eclipse
flashing
final
one
and
and
he
will
set
off
a
similar
project
board
on
github.
So
we
can
follow
the
stages
there
as
soon
as
he's
got
around
to
it,
but
but
kind
of
Li.
The
the
thing
that
we
have
to
wait
for
until
we
can
even
start,
that
is
to
get
the
the
specification
project
process
defined
and
also
the
the
trademark
agreements
sign.
A
Yeah,
so
one
one
that
is
in
work
in
parallel,
we
can
proceed
with
some
of
the
work
and
and
that's
where
the
community
can
get
engaged,
providing
that
the
spectra
process
which
we're
wrapping
up
hopefully
very
shortly,
and
the
paperwork
from
the
commuters
is
done
right.
Then
we
can
start
some
work
in
the
parallel,
while
we're
still
working
on
finalizing
our
trade
agreements
and
working
towards
getting
these
specification
documents
into
our
specification
projects.
B
C
B
D
So
for
clarity,
January
29th
was
when
eclipse
GlassFish
5.1
delivered
and,
as
you
know,
pointed
out,
we're
not
at
the
point
now.
The
community
is
not
at
the
point
now
to
communicate
a
date
for
Jakarta,
e8
or
GlassFish
about
to,
but
there's
a
lot
of
work
going
on.
That's
moving
us
towards
that
courts
not
objective,
but.
A
C
Without
promising
anything
that
we
would
really
really
like
to
have
something
to
show
when
the
two
big
events
or
the
major
events,
this
fall
is
going
like
clicks
on
Europe
and
an
orca
code
one.
We
really
really
like
to
have
something
to
show
that
ok,
but
it's
kind
of
out
of
our
control
right
now,
yeah.
A
B
B
How
far
or
how
much
have
you
focused
on
this
and
what's
plans
about
the
Eclipse
IDE?
Will
it
be
like
I
mean
I
think
that
the
community
expects
from
you
us
that
we
have
something
implemented
that
works
perfectly
since
Eclipse
best
fish,
its
Takata
is
now
and
pickup
said,
he's
on
one
hand
now.
So,
what's
the
plans
there
so.
E
First
and
foremost,
the
Eclipse
Foundation
is
a
place
where
open-source
development
works
and
the
Eclipse
Foundation
does
not
actually
employ
any
of
the
developers.
Ultimately,
what
the
Eclipse
IDE
project
decide
to
do
is
really
up
to
them
and
the
the
amount
of
energy
that
comes
to
the
community
to
assist
them
in
that
sort
of
activity.
So
this
is
sort
of
a
non-answer,
but
so
we
we
do
not
include
the
Eclipse
IDE
is
not
included
in
any
of
our
current
plans
around
Jakarta
EE.