►
From YouTube: Jakarta EE Community Call | 2019-10-16
Description
The Jakarta EE Community call is a monthly meetup via Zoom that drives community conversation and provides a space for participants to ask questions on topics of interest in an Ask Me Anything (AMA) format.
// AGENDA
- What needs to be done with the rest of Jakarta EE specification documents? (Ivar Grimstad)
- Jakarta EE 8 release - retrospective (Ed Bratt)
- Community Reminders (Tanja Obradovic)
-Open discussion and questions
/// JOIN THE CALL
To join the next community call click the link to add it to your calendar: http://bit.ly/2B6oSPH
//// 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/showcase/jakartaee/?lipi=urn%3Ali%3Apage%3Ad_flagship3_company%3B%2BY4nmS3ARKC2lQYqAQ7YgA%3D%3D
Tag us: #JakartaEE
A
Okay,
everyone
so
I
think
it's
top
of
the
hour.
This
is
what
we
have
for
the
agenda
today.
Of
course,
I
first
want
to
welcome
you
to
the
call,
and
so
today
we
want
to
talk
about
the
rest
of
the
Jakarta
specification
documents
and
what
needs
to
be
done
to
prepare
them
for
the
Jakarta,
EEE
and
Eva
will
will
take
that
over.
A
We
also
want
to
talk
about
the
Jakarta,
Eve
8
release
and
we'll
get
the
retrospective
from
and
Brad
and
then
finally,
I
will
just
give
you
a
couple
of
reminders
with
regards
to
eclipse
con
Europe
that
is
starting
next
week
and
I
am
certainly
hoping
that
you
all
saw
the
Jakarta
elections
email.
So
please
for
all
eligible
commuter
members.
A
Commuters,
actually,
this
is
invited
invitation
to
to
nominate
someone
or
nominate
themselves
if
they
are
eligible.
So
I
think
if
there
is
nothing
else
on,
the
topic
will
certainly
leave
a
couple
of
minutes
or
enough
time
for
the
questions.
You
can
always
reach
us
if
there
are
any
comments
or
questions,
but
let's
get
going
with
Eva.
So
even
you
want
to
take
over
and
share
your
screen
and
start
doing
it
that
way.
I'll
stop
sharing!
A
B
So
today,
I'll
go
through
a
couple
of
steps
of
how
to
get
started
with
converting
the
specifications
to
Jakarta
EE.
As
you
know,
they
are
donated
by
Oracle
and
they
are
the
Java
EE
versions
of
specifications
and
we
need
to
perform
a
couple
of
steps
in
order
to
make
them
for
Jakarta,
II
and
I.
Think
we've
been
promised
that
they
should
be
available
at
least
a
couple
of
them
either
tonight
or
tomorrow.
B
So
when
you
see
an
email
in
your
in
your
inbox,
if
you
were
a
developer
or
committer
on
the
project,
you
will
get
an
email
that
the
there
are
some
documents
available
in
inbox.
A
law
office
allows
some
some
links
to
they're
just
long
in
there
and
download
the
safe
and
I'll
show
how
you
go
forward
from
that
step
them.
So
I'll
just
share
my
desktop
here.
B
B
B
B
So
I've
got
it
here,
you
see,
I,
have
the
security
folder
here
and
I
have
the
the
source
for
for
this
specification
document.
Now
all
the
documents
have
been
converted
to
ask
it
out,
no
matter
what
the
liquid
format
was.
No
I
happened
to
know
that
the
security
spec
was
ASCII
dogs.
All
from
the
beginnings
of
this
transformation
is
pretty
easy
and
straightforward.
B
If
has
been
converted
from,
for
example,
a
world
or
something
else,
it
may
be
one
big
file,
so
so
the
recommendation
there
is
to
split
it
off
in
different
sections,
as
he's
already
done
here
with
the
security,
since
it
was
it's
a
rather
than
new
spec,
so
it
was
written
and
asked
it
up
from
the
beginning.
So
this
is
probably
the
easiest
one.
B
B
So
what
I've
done
here
is
I've
fork
the
security
I'd
behind
to
my
private
red
ball
in
order
to
just
do
it
locally
here
and
push
it
to
Myra
from
my
fork
and
then
now
I'll
try
to
pull
request
into
the
the
main
repository,
so
they
can
have
a
look
at
it.
So
I've
done
that
here
and
I
close
this
one
down
to
my
computer
error.
So
this
document
or
project.
B
Has
a
parent
bomb,
it
has
a
a
where
the
Javadoc
is
generated
from
any
high
suspects.
So
in
this
case
you
have
both
the
FBI
and
the
speck
in
the
same
repository,
and
that
is
because
this
project
chose
to
have
it,
so
you
may
split
them
up
in
different
repositories,
and
there
are
given
reason
for
doing
that.
Then
there
are
good
reasons
to
keep
them
together
and
it's
just
a
matter
of
taste
we're
not
dictating
you
have
to
do
this
and
that
the
advantages
of
having
them
together
is
that
you
can
version
them
together.
B
You
can
reference
a
guide
easily
from
the
spent
documents
and
and
back
and
forth.
So
that
is
a
good
reason
for
having
them
together
or
ask
this.
If
you
wanna
release
like
minor
updates
to
either
the
FBI
or
respect
documents
independently
of
each
other,
so
to
just
push
patches
or
service
police's,
it
may
make
sense
to
split
them
in
different,
but
is
just
a
matter
of
the
taste
for
your
particular
project
or
how
you
see
it
evolving
and
you
can
always
change
it
later.
So
in
this
case
we
have
the
spec
unit
variance
a
so.
B
If
I
openly
the
spec
documents,
you
will
see
that
all
the
specs
have
this
same
structure.
It
has
a
ask:
you
look
folder
where
you
have
a
scope
statement,
and
this
is
how
the
Jakara
e84
specifications
were.
We
just
add
a
little
tip
and
that's
it.
So
what
we
need
to
do
here
is
to
do
add
the
the
real
specification
document
and
the
easiest
way
of
doing
that
is
actually
just
take.
Take
the
SQL
files
from
from
the
the
downloader
source
and
just
copy
it
into
the
same
folder.
B
The
ASCII
notice
is
the
one
that
there
is.
There
are
downloaded
from
the
the
zipper
and
the
a
doc
is
the
one
that
we
used
to
have
in
in
the
Jakara
EAH
specification.
This
one
has
all
the
logos
and
stuff
so
I
recommend
to
use
this
one.
So
what
I'll
do
is
just
to
to
look
at
the
contents
here
and
see
that
I
have
the
license
and
the
preface
that
concepts
about
education
and
everything
in
the
blog
repeat
just
copy
this
list
over
to
the
the
document.
C
B
Specification,
another
Z.
We
have
the
EFSA
license,
which
is
the
one
you're
going
to
use,
so
you
can
remove
the
the
old
license
from
the
Java
version
and
also
remove
the
scope
just
for
fun
yeah.
So
this
is
what
I've
done.
So
what
I'm
do
now
is
just
just
simply
type
name
in
please
package
policy,
how
it
goes
so
as
if
this
one
is
super
easy,
since
it's
tis,
it's
already
we're
in
asciidoc
and
already
we're
in
in
different
chapters.
So
so
you
don't
have
to
split
it,
but
I
really
recommend.
B
B
C
A
C
C
C
Then
I
took
the
context
of
the
safe
into
the
original
spec
documents,
and
the
next
thing
I'm
going
to
do
is
connect
and
push
the
branch
and
I'm
great
there
for
ghosts,
but
I
wanted
to
just
build
it
first
and
I'm,
not
sure
why
it's
so
slow,
it's
a
success
here.
So
let's
go
in
and
look
at
it.
It's
all
just
open
the
you
see
it.
It
creates
a
skip
on
them,
so
I'll
just
unzip
this
one.
C
C
So
it
doesn't
want
to
open,
let's
go
out
in
my
France
room
over
here
from
the
final
security
spec
target,
and
we
are
disrespect
and
we
have
the
PDF
here
and,
as
you
see
it's
a
nice
technology
security
specification
just
as
a
new
version,
the
date
everything
the
time-
accountants
it
there.
So
it
has
only
the
correct
information.
It
has
the
customization
specification
license
and
it
has
all
the
contents
as
you
recognize
from
the
Java
EE
version.
C
C
If
it,
you
should
use
the
specification
and
name
version
of
the
specification
rather
than
using
a
JSON
number.
So
then,
then
you
avoid
the
biggest
either
if
you
reference
a
existing
Java,
EE
technology
and
or
acronym
M,
then
and
and
J's.
This
is
okay.
As
long
as
you
just
stated
in
the
beginning
of
a
document
that
this,
our
existing
certification,
Bureau
referencing
and
you
when
you
do
the
refere,
a
references
just
make
sure
that
you
don't
change
anything.
The
behavior
or
the
meaning
of
the
document
should
be
equivalent.
B
C
B
To
do
how
the
Jacana
e9
is
it's
handled
and
also,
if
you
want
to
release
this
document
as
a
part
of
Jakarta
ee8,
we
can
do
it,
don't
release
o
it
and
push
it
up,
so
the
specification
will
be
there,
but
you
cannot
do
any
changes
that
changes
anything.
Then
then
it
cannot
be
a
part
of
your
38
and
we
really
recommend
that
we
get
these
documents
out.
So
the
Jakarta
EA
release
will
have
these
full
documents.
B
Kevin
has
helped
us
here
with
creating
a
lot
of
helpful
hints.
While
we
go
through
the
conversion,
it
depends
on
how
its
formatted
and
it,
if
it's
generated
from
the
word
document
or
something
it
could
be
some
weird-ass
Kulick
thing
here
in
there.
So
you
need
to
go
carefully
through
and
just
make
sure
that
all
the
images
and
things
look
the
same.
So
there
are
some
helpful
tips,
tips
and
tricks
there
and
of
course,
as
with
anything,
if
you
discover
something
new,
that
would
be
good
for
everybody
to
know.
B
B
B
B
B
So
don't
under
I
don't
have
a
quick
update
added
the
expect
documents
here.
I
can
go
in
and
and
now
do
a
pull
request
to
the
actual
project,
and
here
I
would
say
that
if
you
plan
on
doing
this
change
before
you
do
any
other
changes
which
I
really
recommend
you
should
you,
you
should
just
merge
it
into
master
and
then
start
working
otherwise
create
a
separate
branch
and
do
it
but
I
think
the
security
project,
we're
gonna,
do
it's
pretty
fast,
I
think
so.
I'll
just
click.
B
This
pull
request
into
the
master
branch
and
it's
a
good
idea
to
let
somebody
look
at
it.
So
you
can,
you
can
add
some
reviewers
from
the
project
here.
Maybe
our
John
want
to
look
at
this
one,
for
example,
and
then,
when
his
approved
we'll
just
push
it
then
he's
really
fast.
He's
already
proved
it.
So
as
soon
as
this
one
asked
completed,
the
checks
will
just
merge.
It.
B
C
B
This
is
the
start,
so
you
can
just
get
the
document
in
there
and
then
they
ask
you
looking
after
that,
it
just
it's
manual
labor,
it's
tedious
and
it's
it's
probably
you're,
not
gonna,
be
right
on
the
first
attempt,
so
you
just
have
to
go
some
iterations
and
just
do
it
now.
The
thing
is
that
we
are
getting
documents
now,
I
think.
D
B
A
E
All
right
so
I
just
wanted
to
present
a
sort
of
a
a
wrap
up
of
what
we
did.
This
is
kind
of
a
repeat:
if
you
saw
the
my
presentation
at
code,
one
but
I
know
many.
Many
people
were,
you
know
unable
to
travel.
So,
just
to
recap
what
our
deliverables
were
right.
We
wanted
to
get
to
complete.
It
generate
a
complete
set
of
the
charity
eights
best
vacations.
There
wasn't
we
didn't
want
to
make
any
changes
to
those
specifications.
E
We
did
need
to
make
sure
that
we
had
a
complete
specification
document,
an
API
release,
a
jacquard
eee
api
released
a
jacquard
ee
TCK,
and
we
want
to
make
sure
that
we
had
verified
had
at
least
one
verified
compatible
implementation.
We
started
the
year
with
Koch
contributions
and
implementations
for
all
the
original
api's.
We
completed
that
Java
EE
compliance
past
and
we
released
eclipse,
GlassFish
and
all
of
its
associated
components.
E
In
any
case,
that
is
all
behind
us.
Hopefully
you
should.
We
should
start
seeing
some
new
specs
coming
out
pretty
soon
and
then
the
last
thing
all
the
TCK
contributions
we
needed
to
verify
that
those
were
complete
contributions.
Is
that
all
the
code,
all
the
documentation,
all
the
setup
for
running
the
tests
was
completed
and
that
we
had
tests
TCK,
test
jobs
for
all
of
the
component
specifications?
So
there's
an
awful
lot
of
work
there
right
all
the
component
specifications
were
completed.
We
delivered
them
on
ratified
them
under
the
cart
specification
process.
E
The
platform
specification
documents
for
the
full
profile
and
web
profile
are
complete
and
they
contain
all
the
specification
text.
So
now
our
next
job
as
Ivar
was
just
describing,
is
to
bring
all
the
other
the
rest
of
those
documents
over
to
eclipse
and
get
them
converted,
let's
see.
So
what
is
each
contain?
It?
Each
specification
has
a
specification
document
in
most
cases,
there's
Java
Docs
and
a
TCK.
There
are
a
few
examples
that
don't
have
one
or
the
other,
but
everything
has
to
have
a
reference
reference
to
an
implementation
that
meets
all
the
compatibility
requirements.
E
So
we
managed
to
get
it
all
done.
34
specifications
and
all
these
are
included
in
31
different
projects.
Some.
Obviously,
some
projects
have
more
than
one
specification
in
them
and
on
day
one.
We
had
multiple
organizations
who
produced
compatible
implementations
and,
as
of
today,
we've
got
you
know:
Eclipse
GlassFish,
open,
Liberty,
PI,
our
server
and
wildfire
are
all
certified
compatible
with
Jakarta
ee8.
We
never
had
a
you
know
that
many
compatible
implementations
just
quickly
after
any
Java
EE
release.
E
If
you're
interested
you
could
browse
to
Jakarta,
dyi,
slash
compatibility
and
so
yeah
I
think
I
had
down
here.
That's,
of
course
the
zoom
features
are
helping
me.
So
here's
the
compatible
products
page
all
of
the
products
are
listed
here.
You
there's
a
link
to
that.
Each
products
download
and
then
a
link
to
the
you
know
the
evidence
that
we
was
provided
for
determining
if
that
project
was
compatible.
So
we
expect
this
list
to
continue
to
grow.
There
are
still
commercial
grade
products
that
that
could
be
added
to
this
list.
So
I
guess
some.
E
If
you
don't
see
your
favorite
application
server
here,
wait
a
while
or
talk
to
your
vendor,
see
I
know
ask
them
when
they're,
when
you
think
that
they
will
be
getting
at
jakar
de
release,
alright
loading
okay,
so
we
brought
up
a
complete
new
website,
basically
by
it
by
the
bootstraps.
This
is
Jakarta
de.
If
you
haven't
gone
and
visited
that
to
make
sure
you
give
it
a
look
and
then
just
you
know,
I
find
it
much
easier
to
find
the
specification.
E
Now,
it's
guarded
ie
slash
specifications,
they're
all
sort
of
there
and
ready
to
go.
Let's
see,
I
think
I
have
a
so
here's
the
homepage
for
Jakarta
EE
right.
We
keep
an
active
list
of
events
that
are
coming
up
with
it
that
are
related
to
Java.
You
know
enterprise
technologies,
people
can
submit
their
events.
If
you
have
an
event
coming
up-
and
you
don't
see
it
listed
here-
there's
a
button
here
follow
the
form
and
you
can
submit
events
to
show
up
here.
E
We
looked
at
that
one
and
then
here's
the
specifications
page
right
and
you'll
see
all
of
the
different
specifications
that
are
part
of
Jakarta
e.
Are
listed
here,
you
know
you,
you
can
drill
into
these.
Eventually
there
will
be
more
than
one,
but
here's.
What
a
particular
specification
itself
looks
like
there'll,
be
links
to
specification
itself,
there'll
be
Java,
Docs,
there's
a
TCK,
and
how
do
you
get
it
from
maven?
Alright,
so
this
is
I.
Think
we've,
you
know
it.
The
organization
here
is
a
great
start.
E
We've
got
I'm
sure,
there's
going
to
be
more
sort
of
growing
pains
associated
with
that
man
we
have
contributed,
or
there
are
fifteen
implementation
projects
that
are
part
of
this.
Oh,
this
entire
working
group
and
that
list
is
I
predict
will
continue
to
grow
and
then
so
altogether.
Forty
seven
different
projects
that
are
part
of
the
Java
EE
specification
and
implementation
working
group.
Those
are
all
here
at
Eclipse,
org,
slash
projects.
E
I
ee
forge
a
that's
a
sort
of
a
holdover
from
when
we
started
this
and
it's
all
contained
in
one
hundred
and
twenty
one
git
repositories,
so
you
know
get
crackin.
If
you
want
to
memorize
where
all
these
things
are
and
what
they
do,
we
could
have
done
this
without
a
community
right.
We,
you
know
this.
The
major
organizations
here
I
see
I,
didn't
even
list
Oracle,
but
you
know
Oracle
IBM,
Red,
Hat,
Tomi
tribe,
was
pivotal
in
helping
helping
us
get
things
done.
E
Payara
was
pivotable
pivotal
in
getting
a
lot
of
the
compatible
implementations
up
and
running
there.
There
are
tzk
is
Fujitsu,
London,
Java,
community
web
tied
and
even
tails,
and
we
had
contributions
from
from
them.
Somebody
works
with
Salesforce
there's
a
lot
of
people
behind
these
corporations,
and
you
know
lots
of
thanks
and
lots
of
kudos
go
to
those
people.
I
listed
a
bunch
of
individuals
that
I
I,
don't
personally
know
their
corporate
connections.
I'm
sure
I
didn't
list
everybody.
So
please
accept
my
apologies.
E
E
Ace
but,
but
some
you
know
a
list
of
thanks
to
go
on
with
this-
let's
see
so
what's
next
probably
want
to
follow
the
platform
specification
project
for
most
of
the
active
discussion
going
on
right
now,
there's
a
mailing
list.
If
you're
not
on
it,
it's
I
put
the
link
here,
sorry
yeah,
well,
I
guess:
I
could
just
click
the
link
or
Inc.
So
so
here's
how
this
is
the
signup
page,
if
you're
interested
in
adding
your
set
yourself
to
this.
This
button
changes
this
button
red
button
here.
E
For
me
it
would
unsubscribe
me,
but
if
you're
not
subscribed,
this
button
says
subscribe.
Alright,
let's
see
and
then
there's
the
github
project
which
I've
just
listed
out
as
a
complete
URL.
You
can
watch
our
star
that
that
prop
that
repository
and
all
of
the
issues
that
are
applied
and
all
the
discussion
that's
associated
with
those
issues
will
go
on,
will
will
magically
appear
in
your
inbox.
If
that's
what
you
want,
there's
other
ways
to
keep
track
of
it.
E
I,
don't
want
I,
don't
have
time
to
go
through
all
of
those
here
there
will
be
a
few
more
specifications
that
will
come
be
coming
up
on
ballot
real
soon
now
there
are
say
collection
of
specifications
that
were
deprecated
out
of
job
from
Java
SE,
basically
from
nine
forward.
These
are
still
necessary
for
jakar
de
the
poll.
Requests
are
submitted
and
we're
just
waiting
for
some
airtime
with
the
specification
community
to
get
to
some
reviewed
and
ready
to
go
to
ballot.
E
There
are
brand
new
specifications
that
are
part
of
Jakarta
ee
that
are
very
close
to
getting
on
to
getting
proposed,
for
am
some
kind
of
a
ballot.
I
think
a
planning
review
or
more
maybe
even
a
release
for
you
so
keep
an
eye
out
for
those
things.
They
should
be
happening
pretty
soon.
That's
it
for
the
for
what
we
got
done.
I
I
can
pause
here
for
if
there's
any
questions
comments,
anybody
wants
to
give
kudos
to
anybody.
E
A
sleepy
audience
well
sleepy
here
anyway,
all
right
so
I've
tried
to
provide
some
links.
I
will
put
these
slides.
Well,
I'll
definitely
put
the
slides
where
they're
being
useful
and
you
can
you
can
look
at
them
grab
the
links
out
of
these.
If
you
want
alright,
so
retrospective
feedback
I
just
wanted
to
touch
on
this
quickly,
you,
if
you're,
subscribed
to
the
working
group
email,
you
will
have
seen
and
you
might
have
seen
a
message
from
David
Blevins.
E
The
subject
was
community
retrospective
on
Jakarta,
a
release
right,
so
we're
basically
trying
to
capture
your
feedback
in
a
Google
document.
Anybody
can
edit
it
you
can
edit
it
anonymously
or
you
can
edit
it.
You
know
and
include
your
your
name
credentials
if
you
like
I,
think
Google
tracks,
who
you
know
it's
probably
I.
Don't
my
belief
is
you
don't
wait
you're
not
required
to
log
in
so
so,
if
you
want
to,
if
you
want
to
provide
anonymous
love,
if
you
want
to
provide
anonymous,
hate
I
think
that's
all
possible
in
this
document.
E
Let's
see
if
I
click
it
I,
I
thought
I
had
it
opened
already,
but
I
guess
I'll
open
it
again,
so
you
know
try
to
follow
the
directions
that
David's
outlined
at
the
top.
Here
you
know
try
to
be
clear
about
what
it
is
that
you're
you're
suggesting
and
the
specification
and
steering
group
we
have
committed
to
reviewing
these
this
feedback
and
trying
to
assess
how
what
things
do
we
want
to
take
on,
and
how
can
we
you
know?
How
can
we?
How
can
we
do
this
better?
E
How
can
we
improve
the
process,
improve
our
how
we
present
it?
You
know
to
community
members
and
also
improve
the
participation
right.
What
can
we
do
to
make
it
aware
of
we
hit
the
mark
and
where
we
missed
right
so
we'll
take
both
kinds
of
feedback.
You
know
we,
let's
see
the
I
diss
archive
link
is
to
the
email
in
case
you
didn't
get
it
yet.
You
didn't
see
it.
So
this
is
all
these
don't.
It
doesn't
require
login
to
read
any
of
the
email.
E
I,
don't
think
it
requires
login
to
read
in
a
the
email
for
a
mom
from
the
web.
Server,
if
somebody's
on
the
line
that
knows
differently,
please
please
correct
me
because,
unfortunately
I'm
a
member
of
all
these
things,
so
if
I
you
know,
I
I
won't
I
have
a
hard
time
getting
the
logged
out
view.
So
anyway,
we
would
like
your
feedback
and
we
could
even
take
some
feedback
here.
I
think
we
might
have
time
if
anybody
is
dying
to
raise
raise
any
points
here.
E
I
have
one
I
have
another
section
here
where
I'll
I
can
talk
about
how
to
get
involved,
because
one
of
the
feedback
items
was
I
tried
to
get
involved,
but
we
couldn't
successfully
navigate
the
the
we
couldn't
navigate
to
actually
getting
involved,
based
on
the
information
we've
given
so
having
my
problem
is
I've
been
in
so
imbued
in
all
this
I
have
a
hard
time
seeing
what
you
know
where
I'm
missing
the
mark
in
terms
of
well.
You
know
what
we're
saying
and
how
we're
giving
directions.
D
Of
comment
that
I've
heard
a
lot
is
that
the
initial
process
was
quite
a
bit
of
work
and
we
had
to
make
things
up
as
we
went
along
so
I
think,
specifically
the
WebSockets
lead
and
some
critical
comments
there
that
things
changed
while
he
was
doing
it
and
then
you
did
it
and
things
changed
again,
so
that
was
certainly
something
that
we
could
improve
next
time.
On
the
other
hand,
the
this
was
the
first
time.
So
if
we
do
the
process
again,
then
all
those
things
should
be
very
easier.
E
Yes,
we
had
that
problem
ourselves
right.
We
were
trying
to
it's
a
little
bit
like
you
know,
changing
out
the
engine
in
a
car
that
you're
driving
down
the
freeway
right.
So
you
know
we
we
also
had
we
would
we
would
start
running
down
the
process
and
we'd
find
out.
Oh,
we
can't
do
this
because
this
doesn't
exist
yet
or
you
know
in,
and
there
are
definitely
some
actions
that
we
will
be
taking
to
try
to
refine.
E
D
Yeah,
so
maybe
one
piece
of
comment,
too
I
think
that
feel
actually
put
that
on
the
list
already.
But
it's
me
the
access
to
the
other
jobs
that
are
being
created
and
Jenkins
from
jobs
that
you
don't
have
access
to.
So
a
lot
of
people
are
creating
very
similar
jobs
for
running
the
TCK
and
with
half
you,
and
they
can't
see
each
other's
work,
so
I
think
that
it's
still
not
solve.
This
is.
E
D
E
So
I
do
know
there
were
some
questions
about
where
actually
to
file
issues.
I've
noticed
some
confusion
about
that
right.
There
are
two
issue:
trackers,
there's
the
for
anybody:
who's
used
to
working
on
eclipse
there.
They
might
be
focused
on
trying
to
write
up
issues
and
then
assign
them
via
the
Bugzilla,
that's
part
of
a
good
foundation
and
then
there's
the
issue,
trackers
associated
with
repositories,
and
so,
if
you
play
back
121
repositories
each
one
of
those
has
an
issue
tracker
right.
E
So
it
can
be
quite
daunting
to
figure
out
which,
which
one
should
I
actually
is
the
right
one
to
use
for
that
issue.
So,
for
example,
with
the
TT
Ches,
you
know
there's
the
tea
there's
the
repository
where
the
TCK
code
lives,
there's
a
repository,
a
different
repository
for
specification
and
then
there's
a
repository
for
the
api's.
E
And
so,
if
you,
if
you
bump
into
something,
that's
not
working,
as
you
expect
do
you,
which
one
of
those
three
repositories
do
you
should
you
use
and
I
think
during
the
process
we
decided
that
those
all
those
we
would
like
all
of
those
to
go
to
the
specification
project
first
and
then,
if
the
specification
project
decides
it
needs
to
be
addressed
in
an
API
change
or
or
a.m.
or
a
ttk
change,
then
they
would
create
a
secondary
issue
in
the
actual
code
based
project,
but
unfortunately
I
don't
know
that
we've
communicated
that
super
well.
E
So
the
rest
of
slides,
basically
just
go
over.
How
would
you
become
a
contributor,
you
know
and
I
I
don't
know
if
this
audience
wants
to
go
to
that
level?
That's
sort
of
a
primer
I
call
it
you
know.
First
thing
you
need
to
do
is
decide
what
you
want
to
do
right.
If
you
just
want
to
provide
feedback,
you
know
anybody
can
download
any
of
the
implementations.
Anybody
can
read
the
documents
you
can
use
the
implementations.
If
you
find
issues
and
problems,
you
can't
you
you
could
tweet
about
it.
E
If
you
have
a
Twitter
account,
but
but
if
you
want
to
file
issues,
you
must
the
the
lowest
bar
I
could
think
of
as
create
a
github
account.
If
you
don't
have
it
already
and
then
and
that's
pretty
straightforward,
github
calm
to
flesh,
join
and
just
follow
the
pant,
the
forms
there
create
a
github
account
and
then
you
can
I
think
you're
off
the
races.
You
could
file
issues
against
the
documentation
any
in
the
tutorials.
E
The
specification
of
the
implementations
right,
there's,
no
I,
don't
think
there
is
any
additional
requirement
needed
for
providing
that
level
of
feedback
to
github.
If
somebody
knows
different,
please
tell
me
if
you
want
to
go
further
and
actually
help
with
your
contributions
right.
If
you
want
to
create
some
fixes,
if
you
want
to
make
some
updates,
you
must
be
a
contributor
right
and
so
there's
sort
of
two
things.
I
would
say
you
should
try
to
make
sure
you
understand.
Right.
Eclipse
has
a
handbook
for
how
development
is
supposed
to
work.
E
You
know,
obligate
you
regarding
your
contribute
contributions.
Can
you
make
contributions
right
and
if
so,
what
does
your
employer
gonna
tell
you
yes
or
no,
or
how
do
they?
How
do
they
monitor
that?
You
know
we
don't
want
to
get
anybody
in
trouble.
We
want
to
make
sure
that
everybody
who's
doing
these
contributions
is
so
you
know,
is
doing
it
with
the
you
know:
the
full
cooperation
of
their
organization,
so
github
organization,
twerked
with
github,
there's
a
bunch
of
tutorials.
You
know
YouTube
videos
their
github
guides.
E
You
know,
there's
there's
a
wealth
of
information
for
getting
started
at
github.
The
guide
is
one
of
them.
You
must
create
an
eclipse
user
account
and
to
make
a
contribution.
You
must
complete
the
eclipse,
contributor
country
view
agreement
right.
If
you
don't
work
for
a
company
that
is
already
a
member
of
eclipse
organization.
The
contributor
agreement
is
pretty
easy.
E
E
There
is
some
additional
paperwork
that
you
will
need
to
fill
out
before
you
can
make
any
contributions
and
the
Eclipse
Foundation
will
handle
that
by
sending
you
some
emails,
the
I
would
say
the
most
common
thing
that
I've
seen
is
those
emails
come
back
and
they
not
they
don't
quite
have
the
subjects
or
somehow
they
get
lost
in
your
inbox.
So
do
watch
out
for
that.
E
If
you
are
creating
your
your
first
account
at
Eclipse
Foundation,
once
you
have
a
github,
IDE
and
you've
got
your
Eclipse
account,
you
should
be
able
to
create
pull
requests
that
will
pass.
The
required
origination
record
checks
these
these
get
done
every
time
somebody
doesn't
come
in
and
and
there
the
system
will
check.
Is
this
coming
from
somebody
that
I,
that
is,
has
been
authorized
to
provide
source
code
or
changes
to
this
some
to
the
second
to
this
project.
E
If
you're,
not
a
committer
to
the
project
right,
you
need
to
add
signed
off
by
that's
a
get
tagged
to
every
one
of
your
commits
I.
Don't
think
I
think
we
go
through
if
you
don't
do
that,
but
you
are
a
member
of
a
committee
member
of
the
project,
but
I
could
be
wrong.
I'm,
not
a
hundred
percent
sure
about
that.
E
E
So
that's
the
other
place
where
that
ECA
check
might
get
lost
is
if
you
submit
and
you'll
write,
a
different
account,
a
different
email
I
in
those
two,
so
it
won't
find
it
might
not
find
you
and
then
you'll
get
this
big
red
check
mark
by
your
eclipse.
That's
or
a
big
red
excuse
me
that
says
this
person's
not
authorized.
Once
you
create
the
pull
request.
E
One
of
the
existing
committers
on
the
project
should
pick
it
up
and
do
a
review
and
once
they
agree
and
they've
approved
all
your
changes
that
you
know
so
one
of
the
commuters
from
the
project
will
be
able
to
merge
your
changes
into
the
repository
either
a
branch
or
in
the
mail
on
whichever
one
that
you're
working
on
so
I
believe.
That's
everything
that
you
need
to
make
a
basic
contribution.
E
Suggestions
right
do
your
best
to
reach
out
to
the
existing
committed
group
using
the
project's
development
list
or
perhaps
by
initiating
a
discussion
through
the
issue
tracker
right,
a
lot
of
times
or
sometimes
people
will
just
sort
of
make
a
contribute
contribution
into
the
contributors.
It
may
look
like
it's
coming
out
of
the
blue
and
they
maybe
don't
recognize
it.
They
need
to
take
action.
E
Some
of
us
myself,
for
example,
I'm,
subscribed
to
all
of
those
repositories.
I'm
subscribed
to
all
of
those
lists
and
I.
Just
might
my
inbox
is
just
a
total
mess
all
the
time
so
I'm
terrible
at
finding
things,
especially
I'm,
terrible
at
finding
things
that
I
didn't
expect
so
try
to
reach
out
and
make
a
direct
connection
to
people
that
are
already
associated
with
the
project.
I
think,
if
you
know
the
better
the
project
membership,
the
comater
members
are
tuned
to
looking
for
your
feedback,
the
more
likely
or
your
changes.
Your
commits,
your
PRS.
E
Your
commentary
will
be
acted
on
quickly.
If
you,
you
know,
if
you
try
all
this
and
you
still
can't
get
there,
try
posting
subject
the
de
Jakarta
EE
community
mailing
list.
So
and
see,
if
that
you
know
somebody,
there
will
probably
shame
the
committers
from
the
project
into
you
know
taking
some
quick
action
on
for
you.
Okay,
any
I
think
that.
D
D
D
E
On
occasion
you
will
get
I've
had
some
emails
and
I,
don't
know,
there's
a
there's,
some
kind
of
filtering
or
qualification
that's
applied
where
it
says
your
email
looks
like
it
might
be
spam.
We're
we've
sent
it
on
to
the
moderator.
Sometimes
that
can
take
a
little
while
to
get
resolved
so,
but
you
should
get
a
you
should
be.
The
autoresponder
should
respond
fairly
quickly
that
that
happened
to
you.
I
wish
I
understood
that
more,
but
everyone
someone
I'll
send
so
I
will
send
something
out
and
I
know.
E
I'm
am
a
member
of
the
lists
and
I
get
those
that
feedback.
I
suspect.
It's.
You
know
another
type
of
spam
filter
they're
just
trying
to
keep
the
noise
down.
Having
lived
through,
forges
that
you
know,
Java
doesn't
had,
for
example,
for
a
while
before
they
got
their
spam
control
sort
of
in
place.
It
was
just
a
nightmare
with
all
this
crap
that
came
across
those
lists.
So
you
know
this
is
one
of
those
you
got
to
live
with
some
restrictions
or
you're
just
going
to
hate
your
inbox.
E
E
E
If
you
want
to
work
with
the
Jenkins
jobs,
the
CI
CD
systems
that
that
are
available,
you
have
to
be
a
competitor.
That's
the
only
way
you
can
actually
get
in
and
see
all
the
nuts
and
bolts
of
a
particular
projects,
continuous
integrations
or
continuous,
build
jobs.
I
will
say
this
if
you,
if
this
is
something
that
you
want
to
work
on,
raise
that
issue
with
your
project.
E
Team
and
I'd
be
shocked
if
they
didn't
immediately
promote
you
to
commit
err,
maybe
I'm
wrong,
but
but
the
that
is
an
area
where
there's
no
there's
no
clean
way
and
I'm
aware
of,
if
you're,
just
an
observer
for
getting
around
and
working
with
those
systems
and
see
some
chat
stuff.
Let's
see
what's
happening
here,.
D
So
one
thing
we
might
be
able
to
do
is
just
a
thing
that
came
to
mind
and
love
to
ensure
how
feasible
it
is,
but
to
actually
store
the
jobs
that
we
create
on
Jenkins,
the
the
xml
representation
of
it
in
version
control
and
get
off
as
well.
So
people
could
actually
do
PR
to
that
and
look
at
it
might
might
be
something.
But
then
again
it
might
be
trouble
to
keep
those
in
sync.
E
You
know
that
that
might
be
some
kind
of
an
improvement
that
we
could
invest
some
time
into,
but
for
now
they're
very
distinct,
I
think
that
they,
if
let's
say
you,
have
been
working
on
a
project
and
you've
got
a
large
package
or
something
you
you
want
to
contribute
a
substantial
body
of
code
almost
for
sure
you're
going
to
need
to
become
a
committee
on
that
project
to
to
perform
that
contribution,
because
you'll
need
to
you'll
need
to
go
through
the
intellectual
property
review.
That
eclipse
requires
four
big
contributions.
E
E
D
A
C
D
E
A
A
Couple
of
nominations
and
South
dominations,
but
this
is
an
invite
for
everyone
to.
If
you
are
a
commuter
member
and
if
you're
eligible,
please,
you
know
sign
up
for
if
you're
a
commuter,
let
me
be
correct
and
you
wanna
be
part
of
the
jacquard,
a
steering
committee
or
Jakarta
marketing
and
brand
committee.
We
have
those
three
vacant
seats,
so
please
get
in
touch
and,
of
course,
get
involved
and
have
your
voice
heard
in
the
working
group.
A
That's
that's
one
quick
reminder,
and
then
the
second
one
is
most
of
us,
certainly
on
a
good
foundation
will
be
next
year,
sorry
next
week,
but
next
year,
hopefully
as
well
at
the
same
time
at
Eclipse,
con
Europe
we
are
meeting
at
and
expect
I
think
you
at
Lewisburg
next
week
so
do
get
in
touch.
Please
let
us
know
if
you
are
there,
we
would
love
to
talk
to
you.
A
We
have
just
a
couple
of
minutes
left
if
there
are
any
questions
on
this
part
or
any
other
topics
that
we
should
discuss.
We
also
have
others
from
the
community.
Here
we
can
take
advantage
of
having
Mike
on
the
call
as
well.
So
please
ask
questions
or
provide
us
feedback.
We
would,
as
adds
a
couple
of
times,
we're
desperate
to
hear
from
you.
A
And
if
no
questions
you
know,
I
would
invite
you
to
actually
spread
the
word
invite
people
to
not
just
participate
on
these
meetings.
We
we
would
like
to
you,
know,
get
more
attendance,
so
we
can
get
more
feedback
and
we
can
attract
more
people
not
just
to
these
calls,
but
monthly,
update,
blogs
or
anything
that
were
doing.