►
From YouTube: Jakarta EE Community Call | 2020-2-12
Description
- Jakarta EE 9 / Jakartafying update - Ivar Grimstad
- Enabling Individual Participation in Jakarta EE Working Group - Wayne
- Working with JUGs - Shabnam
- Presenting Jakarta EE related topics to JUGs
- “Adopt a Spec” for JUGs
- Topics / questions from the community
A
A
Okay,
fantastic,
so
so
here
is
the
agenda
for
today,
so
we
will
have
the
update
on
Jakarta,
e9,
so
and
and
Jack
of
Jakarta
fiying
of
the
specification
documents.
Then
we'll
pull
Wayne
in
so
he
can
tell
us
about
the
work
that
has
been
done
on
enabling
individual
participation
in
the
work
of
the
Jakarta
working
group
and
particularly
with
the
work
on
the
specification
project
and
then
I
will
then
talk
to
boolean
Shabnam.
A
B
To
start
with,
I
go
through
the
theme
of
Jakarta
and
Ryan
and
I.
We
have
kind
of
three
main
areas
variable
this
release
and
that
is
to
lower
the
entry
barriers.
That
means
that
we
want
to
make
it
as
easy
as
possible
for
new
implementers
to
to
go
and
check
out
a
specs
tonight,
any
mute
your
because
they
are
hearing
keyboards
here.
Oh.
B
Worries
that
so
so
we
want
to
lower
the
entry
barriers
to
make
it
easier
for
new
vendors
to
come
in.
So
we
we're
not
only
having
the
usual
suspects
of
vendors
doing
the
chicory
implementations,
but
we
want
to
make
it
as
easy
as
possible
for
new
to
come
in
so,
and
that
is
what
we
mean
one
lower
at
the
entry
barriers
and
one
example
of
that
is
that
we
remove
stuff
that
we
don't
need
anymore.
B
So
we
take
it
a
little
bit
out
of
the
HIV
specification,
for
example,
that
that
the
those
who
one
implant
it
can
implement
it
and
if
you're
a
new
vendor
and
come
in,
you
don't
have
to
implement
all
this
legacy
stuff,
and
we
also
want
to
make
it
a
platform
for
innovation
so
to
make
it
ready
for
for
future
work.
So
that
is
also
what
we're
doing
to
the
kind
of
set
up
the
specifications
in
a
way.
B
B
We
want
to
make
it
as
easy
as
possible
for
for
customers
or
applications
running
on
earlier
versions
on
Java,
EE
and
Jakari
e8
and
come
over
to
Jakarta
in
9,
so
that
involves
some
some
tooling
or
some
magic
or
some
stuff
in
the
implementations.
That
should
make
it
as
easy
as
possible
to
move
from
the
Java
x9
face
to
the
chicken
head
space.
For
example,
let's
dive
a
little
into
the
technical
things,
and
these
are
some
topics
that
are
very
fresh.
B
We
discussed
them
yesterday
in
our
platform
call
and
one
of
the
things
that
we
want
to
do
in
this
or
are
going
to
doing
this
to
release,
and
this
kind
of
the
main
major
thing
in
this
release
is
to
go
from
the
Java
X
namespace
to
the
Jakarta
namespace
and,
and
it's
only
the
Java
X
part
of
the
name
left.
Shall
we
change?
We
don't
want
to
change
any
class
names
or
or
change
any
packages
or
anything
it's
just
more
or
less,
remove
gel
X
and
replace
it
with
Jakarta.
B
B
Annotation
there,
so
so
what
you
want
to
do
is
also
to
add
the
deprecated
and
the
nation
in
the
java
source
code,
so
so
to
really
mark
they
say
these
methods
or
classes
or
interfaces
as
deprecated.
So
that
is
also
something
we
should
do
just
to
have
consistent
throughout
the
platform.
So
some
have
done
that
some
have
not
so
wanna
add
this
after
that
created
annotation,
and
that
is
okay,
even
though
it
will
actually.
B
Cause
some
changes
in
the
TCGA
or
the
test
suites
when
we
have
this
annotation,
but
that
is
something
we
are
aware
of,
and
we
want
to
do
this
properly
names
all
properties
that
are
of
Java
X
should
be
changed
to
or
must
be
changed
to
Jakara,
and
that
is
kind
of
the
part
of
the
namespace
change
it's.
It's
is
not
this
Java
package,
but
it's
the
actual
property
in
there.
So
so
this
will
be
changed
as
well.
B
B
Get
there
by
Friday
it's
a
couple
of
days
left
and
and
it's
not
that
serious,
if
not
everybody
is
there
yet
because
we've
divided
into
waves.
So
so
when
0
is
something
all
these
can
be
done
more
or
less
whenever,
because
they
don't
depend
on
anything
and
nothing
depend
on
them,
then
we
have
waved
one
that
has
to
be
completed
before
way
through
to
and
with
the
two
before
three
of
them.
So
so.
A
B
So
if
you
want
to
discuss
things
like
the
generics
things
and
stuff,
then
join
the
jacquard
pattern
down
lists.
If
you
want
to
discuss
more
over
community
things
got
the
community
mailing
lists.
All
the
sources
are
on
the
if
je
organization
won't
get
out
and
the
plan
I
just
showed
is
or
get
aboard
on
the
eve
jet
project.
B
A
A
A
C
I
sharing
just
one
screen
this
time.
Yes,
you
are
oh
okay,
so
lesson
here
is
try
this
try
this
that
more
than
30
seconds
ahead
of
the
time
you
need
to
speak.
So,
oh,
okay,
we
we
changed
our
order
a
little
bit
here.
So
I
just
want
to
take
a
couple
of
minutes
to
talk
about
the
changes
that
some
changes
that
we
made
to
fix,
a
problem
that
was
identified.
C
C
C
After
establishing
a
pattern
of
making
high-quality
contributions
to
a
specification
project
and
demonstrating
that
you
understand,
the
processes
are
around
specification.
Development
at
the
Eclipse
Foundation
that
contributor
should
be
I'll
argue
should
be
invited
to
join
the
project
as
a
committer.
Now
committers
are
the
ones
that
hold
the
keys.
These
are
the
people
who
have
the
ability
to
merge
commits
they
are
the
ultimate
authority
in
any
project,
a
subject
of
course
again
with
the
specification
process.
We,
the
specification
committee,
has
a
certain
amount
of
oversight.
C
There
are
certain
boundaries
to
committers,
can't
just
do
whatever
they
want
anyway.
So
once
you
become
a
committer
and
what
I'm,
showing
on
the
list
of
the
ambition
on
the
screen
right
now
is
the
decision
process.
If
you
are
a
student,
you're,
unemployed
or
you're
you're
self-employed,
we
have
a
individual
working
group
participation
agreement.
You
sign
that
that
gives
you
basically
all
the
the
legal
clearances
and
assurances
is
a
legal
agreement
between
you
and
the
Eclipse
Foundation.
That
sets
you
up
to
be
a
committer
good
to
go.
C
If
your
employer
is
a
member
of
the
Eclipse
Foundation
and
is
a
member
of
the
working
group,
in
this
case
the
jacquard
EEE
working
group,
then
you're
basically
good
to
go
and
you
can
be
a
committer
we
already.
If
you're.
If
your
employer
is
already
a
participant
in
the
working
group,
then
we
already
have
all
the
necessary
paperwork
in
place
and
all
the
necessary
agreements.
Are
there
so
you're
good
to
go?
It's
that
gray
area
in
the
middle?
C
If
your
employer
is
not
already
a
member
of
the
Eclipse
foundation
or
your
employer
is
not
a
member
of
the
participant
pardon
me
in
the
working
group,
then
we
need
your
employer
to
sign
an
additional
agreement.
This
is
a
consent
agreement
where
the
employer
consents
to
your
involvement
in
a
specification
process
in
the
specification
process
in
the
development
of
specifications.
C
If
and
then,
we
also
have
the
individual
working
group
participation
agreement
for
that,
so
we
need
the
committer
to
sign
the
individual
working
group
participation
agreement
and
their
employer
to
sign
this
consent
agreement
with
those
two
things
in
place.
We
have
everything
we
need
for
you
to
be
a
committer,
the
discussion
that
started.
This
was
really
about
fees
and
there
is
no
fee
for
that
path
that
there
there's
no
no
money
required,
but
what
we
do
require
is
explicit
a
explicit
agreement
signed
by
your
employer.
So
that's
basically
it
in
a
nutshell.
C
Yes,
so
in
it,
yes,
so
in
addition
to
the
I've
actually
yeah,
so
we've
thrown
we've
thrown
some
documentation
up
onto
the
legal
page,
I
will
be
pushing
out
a
new
chapter
in
the
eclipse
project.
Handbook
that
discusses
this
among
other
aspects
of
specification
development
so
that
documentation
will
be
hopefully
the
end
of
today.
C
A
C
C
So
yes,
so
as
we
as
we're
actually
working
with
a
number
of
other
groups
on
specification,
related
work,
and
this
will
apply
to
all
of
these
all
of
the
organisms.
All
of
the
different
working
groups
that
are
engaged
in
specification
work,
but
certainly
it
does
apply
to
the
jacquard
EEE
working
group.
D
Right
great,
so
I
would
like
to
share
with
you
some
of
the
initiatives
that
you're
currently
working
on
to
enable
Java
user
groups
as
a
part
of
the
2020
Jakarta
program
plan
goals
to
grow
the
developer
community
and
increase
Jakarta
developer
participation,
we're
working
on
ways
to
enable
drugs
and
get
them
informed
about
and
involve
more
in
Jakarta
EE.
So
to
provide
marketing
support.
We
are
preparing
a
Jakarta,
II
template
and
presentation
that
the
community
members
can
use
for
presentation
at
jerk
meetups.
D
So
once
that's
ready,
we
will
make
it
publicly
available
for
the
community
use
and
hopefully
they'll
be
helpful
to
enable
the
community
to
get
the
word
out
about
your
car
to
EE
and
provide
information
and
the
latest
updates
to
the
drugs
out
there.
Another
initiative
that
we're
working
on
is
adopt
a
Jakarta,
a
specification
program
which
is
basically
intended
to
encourage
AK
leaders
and
members
to
get
involved
by
adopting
a
Jakarta
specification.
So
we
are
developing
the
adopted
specification
program
page.
D
Am
I
sharing
the
page?
Can
you
see
that
Tania
yeah
yeah?
Absolutely
all
right
great,
so
we're
developing
the
adopted
specification
page
still
work-in-progress
and
this
page
is
not
live
yet,
but
our
web
dev
has
created
a
mock-up
that
I
can
that
I'm
sharing
with
you.
So
as
I
mentioned,
the
goal
of
this
program
is
to
encourage
X
to
get
more
involved
in
Jakarta
EE
and
as
a
part
of
this
program.
D
In
Djakarta
a
website.
We
can
provide
the
opportunity
for
the
drugs
to
meet
with
Jaffar
je
experts
to
discuss
Jakarta
related
topics,
enable
drugs
to
have
Jakarta,
II
release
parties,
and
also
we
would
provide
priority
for
drugs
that
are
interested
in
organizing
local
Jakarta
bond
livestreams
in
the
regions.
And,
finally,
we
are
providing
instructions
for
drugs
to
sign
up
by
creating
a
pull
request
so
that
once
they
adopt
a
specification,
their
logos
will
be
featured
under
the
page
of
the
specification
that
they're
adopting.
D
So
if
you're
interested
to
get
more
involved
in
conversations
related
to
this
program
join
our
slack
channel,
which
you
can
find
that
in
our
stay
connected
page
here
is
the
URL
to
the
slack
channel
so
be
sure
to
join
and
get
involved.
So
that's
all
I
have
back
to
you
Tony.
If
there
are
any
questions.
A
A
A
A
A
I'm
still
hoping
that
crowdcast
is
something
that
you
prefer
over
zoom
for
the
meetings.
If
this
is,
you
know
if
this
still
works
better,
let
me
know,
or
if
there
is
a
preference,
we're
just
experimenting.
This
is
our
second
meeting
with
with
crowdcast
and
and
I
think
it
works
good,
but
would
like
to
hear
from
you.
A
A
Not
many
questions
so
please
we
will
post
the
recording
out
there
the
chorus
as
soon
as
we
finish,
the
the
meeting.
The
same
Linkous
is
going
to
be
the
recording.
If
any,
follow-up
questions
or
any
anything
you
were.
What
you
would
like
to
share
with
us
just
feel
free
to
reach
out
so
mushy
days
is
coming
bad,
so
is
there
has
four
expand
and
involved
in
specification
yeah
absolutely
so
the
adopter
spec
program
is
actually
intended
of.
We
are
not
really
talking
about
the
Java
EE
any
any
longer.
A
So
for
the
time
being-
and
you
will
see
shortly
when
we
go
live-
we
have
a
first
jug
from
Madras
that
is
interested
in
adopting
a
spec,
so
we
will
of
course,
be
very
social
about
that
and
let
you
know
if
you
are
a
member
of
a
jug
or
leader
jug
somewhere,
and
you
would
be
interested
to
adopt
this
back.
Please
reach
out
I
just
shared
in
in
in
the
chat,
the
the
slack
workspace,
and
you
know
you
can
you
can
ping
me
there
you
can
reach
reach
out
to
us.
A
A
Okay,
so
that's
it
today,
we're
having
another
meeting
next
next
month,
but
in
the
meanwhile
I
think
I
will
schedule
another
meeting
with
Steve
millage,
who
will
tell
us
a
little
bit
more
and
be
more
specific
on
how
to
get
involved
so
hang
on
and
and
and
look
out
for
for
that,
invite
as
well
Oh
Alexis
I
love
the
the
perfect
spelling
there
or
phone
to
brother.
Okay
thanks,
everyone
we'll
be
in
touch
bye
for
now,.