►
From YouTube: Jakarta EE Community Call | 2020-06-16
Description
//// 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
Okay,
so
I
hope
we
are
live
now
welcome
everyone,
so
we're
starting
another
monthly
call
update
called
for
the
community
just
to
keep
you
informed
what
we're
doing
and
what
have
we
done
so
far
in
actually
now
last
couple
of
months
with
in
Jakarta
a
working
group
last
month,
just
a
reminder
we
didn't
have
our
call
just
because
we
had
the
Jakarta
one
live
stream.
Seen
for
J,
so
I
do
hope.
You
had
a
chance
to
attend
that
and
if
you
haven't,
as
you
know,
we
do
have
the
recordings
available.
A
A
A
A
A
A
A
E
E
A
A
E
E
D
A
A
E
D
E
E
The
general
chat
on
the
right
side
and
next
to
it
on
the
left
side,
you
have
the
Q&A,
so
that
is
been
moderated
by
the
by
the
clip
Eclipse
Foundation
and
staff,
and
then
we
have
also
opportunities
to
contribute
so
yeah,
let's
jump
into
the
background.
Thank
you
much
for
all
the
attendees
right
now
that
we
have
a
little
bit
of
background
and
and
when
we
were
discouraged
this
day
with
the
Scott
and
the
community
is
useful
to
present
a
little
bit
of
the.
Why
and
how
we
get
here
with
the
TC
case.
E
So
a
common
question
that
we
got
we
spoke
with
either
community
customer
and
so
on
is
how
Jakarta
e
is
made
of
at
this
point.
So
this
is
still
being
called
artifacts
ap
is
that
normally
developers
interact
on
a
daily
basis,
but
all
that
is
just
a
tip
of
the
iceberg,
because
do
you
have
a
condition
of
the
specification
that
provide
the
the
basis
for
the
implementations
to
develop
the
code
and
also
the
TC
case,
which
is
basically
the
test
that
do
you
apply
for
those
implementations,
reference
implementation
that
actually
complies
with
the
specification
documents.
D
So
the
in
the
TC
k
are
the
technology
compatibility
kits
for
testing
that
age
Chicago
EE
server
implementation
is
compatible.
Oh,
you
haven't
the
old
slide.
That's
okay,
I
yeah!
It's
my
typo!
We
try
to
say
that
we're
a
company
that
we're
testing
for
compliance,
I
started
for
or
we're
testing
for
compatibility.
Now,
not
compliance
more
so,
but
just
terminology
is
important
that
we
all
get
used
to
use
them,
but
anyways
the
I
think
the
the
TCK
the
platform
TCK
project
is
may
be
the
largest
of
one
of
the
largest
projects.
D
We
have
around
at
five
million
lines
of
test
source
that
you
know
that's
made
up
of.
You
know
java
tests,
ant
scripting
and
what
have
you
and
I
didn't
realize
it?
Was
you
quite
that
large,
until
we
actually
measured
a
few
days
ago
for
this
presentation,
so
I
think
it's
going
to
be
the
biggest
one?
An
interesting
thing
to
note.
There
are
some
restrictions
on
what
TCK
a
test
can
depend
on
and
we
only
can
depend
on
the
testable
aspects
of
the
specifications.
D
D
Elements
that
were
verifying
are
not
subject
to
change.
You
can't
request
those
to
change.
They
are
hard
and
fast
interesting
to
know
that
for
many
years
the
tcks
have
tested
the
various
API
signatures
against
select
subsetting
super
setting.
You
know
you
can't
add
methods,
you
can't
remove
methods
and
at
least
historically
there
has
been
the
case.
D
You
know,
Joe
Connor
can
change
that
and
we're
talking
about
improving
the
signature
test
at
some
point,
but
that's
kind
of
that's
kind
of
where
we're
at
and
it's
also
yeah,
there's
also
a
lot
of
and
scripting
that
controls
the
TCK
testing
and
we
use
the
Java
test
time
which
isn't
as
well-known
as
sage
a
unit.
But
it's
it's
been
used
for
many
years
for
various
tcks
at
originally
at
Sun,
Oracle
and
now
like
open,
JDK
and
other.
You
know,
Java
implementations
and
the
TCK
and
I
think
we
can
go
on.
E
E
In
terms
of
physically
TCK
questions
and
answers,
okay,
so
the
the
first
thing
that
someone
can
find
on
the
mainland
is,
and
also
on
blog
posts
and
videos
is
what's
going
on
lately
is.
How
did
this
case
is
related?
Tck
is
related
with
the
naming
migration.
So,
as
you
may
know,
you
may
all
know
for
Jakarta
ie9.
We
have
the
big
man
approached
for
migrating
the
Java
in
space
into
the
Jakarta
in
space.
So
right
now,
one
of
the
work
that
has
been
done
on
the
TC
case
is
actually
this
migration.
E
From
from
from
the
TCGA
point
of
view
to
be
able
to
compile
and
therefore
then
run
participate
against
the
implementations
also
I
one
example.
Once
upon
example,
is
the
one
that
you're
seeing
on
just
under
scream
just
a
simple
naming
convention,
you
may
see
it,
but
actually
is
it's.
It
has
been
a
spread
across
many
pull
requests
in
the
github
project.
All
the
links
that
we
are
talking
here
are
at
the
end
of
the
of
the
slides.
It's
cut
already
provide
a
link
on
the
chat,
so
you
can
find
there
so
so
yeah.
E
Basically,
this
is
just
one
of
the
many
tasks
that
later
you're
going
to
see
in
this
roadmap
that
we
have
in
terms
for
the
TCK
to
be
complete
and
enable
the
Jakarta
ae
test
compatibility,
yeah.
So
Scott
can
you
go
over
the
platform
TCK
versus
ten
alone,
because
this
is
kind
of
related
with
with
many
questions
also
that
we
got
in
the
mail
list
about
the
profiles
and
all
that?
Yes,.
D
The
stay
at
the
stand
alone,
TCK,
yeah
well,
terminology-
is
key.
So
it's
an
it's
good
to
know
some.
What
these
terms
are
referring
to
the
stand
alone,
tcks
are
really
the
individual
specifications
tests
that
verify
that
the
APA,
the
API
signatures
are
correct.
For
that
specification
and
the
implementation
pass,
the
whatever
functionality
tests
are
in
the
TCK,
and
that's
so
that's
so.
The
standalone
TCK
is
a
map
to
the
individuals
specifications.
D
The
platform
TCK
you
used
to
be
referred
to
as
the
CTS,
but
and
now
we
refer
to
it
as
the
platform
TCK,
it
tests
the
in
an
entire
EE
implementation
for
compliance
by
testing
all
the
various
containers
and
with
all
of
the
different
specifications,
or
at
least
most
of
them.
So
it's
a
more
platform
or
server
level
test,
as
opposed
to
the
individual
specification
level.
You
know,
that's
it
it
in
a
nutshell,
though,
the
major
difference
there.
E
Thanks,
thank
you.
We
also
have
the
the
difference
between
their
when,
when
you
say,
Jakarta
ie
web
profile
versus
the
full
platform
profile,
so
they
the
TCK,
can
be
divided
in
these
two.
Obviously,
because
one
is
the
subset
as
I
prefer
to
call
it
the
name.
The
web
profile
is
a
subset
from
the
full
platform,
so
in
terms
of
goals
or
steps.
First,
we
can
say
we
we
have
we
the
prey.
E
It
has
been
working
towards
the
external
on
TC
case,
to
a
slowly
transition,
then
into
the
web
profile
TK
and
eventually
have
the
full
platform
D
CK.
So
it
can
be
divided
in
different
in
the
in
stages.
If
you
wanted
to
call
it
so,
whatever
you
see
on
the
mailing
list
that
we
are
referring
about
platform
full
platform
TCK,
the
word
profile
we're
talking
just
of
the
subset
of
tests
and
how
they
are
category
side
in
say
inside
of
the
project
so
yeah
and
then
we
have,
they
are
kill
em.
D
D
You
know
what
what
you
know.
One
idea:
a
lot
of
these
ideas
have
been
discussed
on
the
TCK
mailing
lists
and
there's
been
some
prototyping,
but
nothing
has
really
been
accepted.
As
the
you
know,
it's
gonna
happen,
but
we
even
we
will
continue
to
discuss
it,
but
I
wanted
to
put
the
idea
out
there,
because
if
we
do
bring
our
Kelly
the
alien
technology
into
the
TCK
I
think
that's
gonna
that'll
be
a
area
that
will
be
wildly.
D
Worked
on
by
many
in
the
community
because,
like
I,
said
before,
there's
five
million
lines
of
code
in
the
TCK,
so
we're
going
to
need
need
a
lot
of
help
if
we
do
get
engaged
in
that
effort,
so
some
some
ideas
of
what
achillion
test
you
know,
which
is
like
a
server
container
test
framework
which
lets
you
use
in
what
they
call
shrink,
wrap
lets.
You
do.
D
You
know,
wrap
a
test
that
uses
ee
components
together
easily
and
deploy
that
against
many
differents
AE
server
implementations.
If
so,
if
we
brought
it
into
the
platform
TCK,
what
one
of
the
integer
that,
with
a
she
had
configuration
sorry
with
a
she
had
platform
configuration,
we
might
be
able
to
get
more
testing
in
those
what
we
call
standalone
tcks
and
that
in
the
long
run,
could
end.
We
could
end
up
with
a
lot
of
separate
standalone
or
small
or
platform
tcks,
and
it's
not
a
given
that
we
would
do
that.
D
But
it's
you
know
it
would
be
a
possibility
to
refactor
some
of
the
platform
TCK.
One
of
the
things
that
I
do
worry
about
is
what
you
know.
What
happens
when
we
get
to
whether
it's
EE,
10,
11
or
12
and
I
worry
about
our
ability
to
quickly
bring
in
new
test
capabilities,
and
that
was
one
of
the
things
I
was
thinking
about
about
bringing
achillion
and
that
might
give
us
greater
ability
to
quickly
adapt
to
new
technology
that
we
might
bring
in
in
the
future.
D
So
a
very
important
part
of
this
is
if
we,
whether
we
do
the
arquillians
support
in
the
platform
TCK
or
if
we
were
to
do
it
in
in
the
standalone
tcks,
regardless
of
where
it
goes,
we
always
need
to
validate
that
we
haven't.
We
reduced
the
platform
testing,
it
needs
to
be
equivalent
because
we
don't
want
to
have
a
less
compatible
eee
implementation
in
the
future.
D
A
D
D
Don't
I,
don't
think
those
got
off
the
ground
but
yeah
so
yeah,
but
that's
still
the
case,
but
there's
yeah,
that's
that
was
actually
I,
think
that
was
the
first
state
alone,
TCK
that
wanted
to
bring
up
Hille
in
and
and
also
wanted
to
bring
maven
in
as
well
to
the
platform
TCK
and
split
up
the
platform
TCK
into
separate
TCK.
So
that
was
where
that
idea
came
from
was
actually
the
jax-rs
but
yeah
that
hasn't
happened.
Okay,
let's
thanks.
E
E
Know
we
are
running
out
of
time,
I
get!
That's
that's
also
part
of
what
we
need
to
be
aware,
right,
Tanya
to
have
a
space
for
further
rest
of
the
panel,
so
yeah.
So
briefly
speaking,
it's
good.
Can
you
just
tell
us
here
you
see
there.
The
overall
of
this
is
light.
So
we
came
past
you.
They
contribute
opportunities,
yep.
D
Yes
of
every
you
know
so
very
quickly:
yeah
yeah,
you
know
a
lot
of
the
this.
A
lot
of
on
the
slide
is
really
yeah.
We've
we're
removing
we're
removing
technologies
from
ee9
and
we've
removed,
such
techno
tech
from
the
TCK,
and
we
need
to
you
know,
do
some
validation
that
we
anything
that
is
my
optional
now
is
still
optional
and
you
know
etc,
etc,
but
this
is
actually.
This
is
a
very
important
slide,
but
yeah.
C
E
You
I
think
it's
good.
We
also
have,
in
terms
of
opportunities
to
have
to
contribute
well.
This
is
the
three
simple
steps
which
how
you
can
can
start
as
a
contributor
actively
to
to
these
and
many
other
Jakarta
specifications.
It
Clara
create
an
eclipse,
account
sign
the
accuse
contribution
agreement,
and
these
are
the
two
mailing
lists
that
you
can
pay
attention
to
TCK
related
conversations
so
say
we
really
hope
to
see
you
many
of
you
around
those
mailing
list.
We
have
awesome
TCK
work
in
progress.
E
This
is
a
in
the
report
that
that
you're
gonna
see
in
the
next
slide
with
all
daily,
with
all
the
links
where
we
are
keeping
track
of
what
has
been
done
already.
Some
of
the
work
that
we
mention
is
track
it
here
in
terms
of
possible
areas
for
contribution.
We
have
plan
to
write
this
cut.
We
have
documentation,
we
have
looking
at
the
kids
of
issues
and
and
again
the
platform
to
seek
aid.
I
think
is
the
best
entry
point
where
you
can
say
hi.
How
can
I
help
and
contribute
rights?
Good
yep.
E
We
also
have
the
Jakarta
ie9
release
plan.
I.
Think
we
are
gonna,
have
also
an
update
from
Kevin
about
that
and
that's
pretty
much
what
we
have.
We
start
a
little
bit
late,
so
we
are
kind
of
rushing
a
little
bit.
What
I
don't
know
if
you
have
any
any
other
thoughts
to
share
with
the
community
to
engage
them
to
to
join
us
and
work
on
on
the
TCK
fun
also
for
the
Jakarta
e9,
no.
D
A
E
Okay
Scott,
can
you
hear
me
I
can
hear
you
okay,
we
lost
Tania,
okay,
yeah
I'm,
gonna,
stop
sharing
I'm
gonna
paste
again
the
link
for
dis
lights
and
feel
free
to
follow
any
questions
on
the
mailing
list
and,
let's
see
who
is
next.
Let
me
just
share
my
screen
here:
okay,
Carolyn
Kevin's.
Next,
okay,
let
me
find
the
button
here
to
stop
sharing.
D
E
D
Before
you
stop
sharing
Kevin,
do
you
want
us
to
show
your
slides?
While
you
talk,
although
you
could
be
invited
to
talk
okay,
it's
been
taken
care
of
yeah
we're
gonna.
Do
oh!
Thank
you
very.
E
E
E
D
F
You
not
the
slideshow
a
certain
way,
and
that
turns
out
that
that
only
displays
part
of
the
screen,
so
I
went
back
to
my
old
mechanism
and
now
it's
working
okay.
So
let's
get
going
and
see
how
this
works
out.
So
looking
at
the
agenda
and
stuff
I
probably
should
have
went
first
because
I'm
going
to
be
talking
about
some
of
the
TCK
stuff
at
a
very
high
level,
and
then
we
could
have
went
into
more
detail.
But
this
will
work.
F
F
There
are
people
on
this
call
that
you
know
this
is
brand
new
to
them
for
Jakarta,
e9
I
do
have
a
pointer
here
to
the
overall
release
plan
and
I'm
just
going
to
touch
on
the
highlights,
and
the
big
thing
is
in
yellow
and
and
Scott
and
C's
are
already
touched
on
this-
that
the
big
change
for
Jakarta
e9
is
that
we're
changing
the
namespace
from
Java
X
to
Jakarta,
and
that
goes
through
everything
all
the
specifications.
All
the
API
is
all
the
tcks
all
of
the
compatible
implementations.
F
F
The
other
thing
that
we're
doing
that's
a
little
different
with
Jakarta
e9
is
that
we
are
actually
removing
some
features.
Some
specifications
from
the
platform
in
the
past
the
term
was
pruning
but
pruning
in
the
past.
In
Java,
EE
only
meant
making
it
optional,
and
what
we
are
doing
now
is
we
are
actually
removing
them
from
the
platform.
So
these
five
features
here
jacks
are
PC
jacks
our
deployment
management
and
a
section
of
the
EJB
spec
related
to
distributed
interrupts.
All
of
those
are
going
to
be
removed
from
the
platform.
F
F
There
are
some
additional
features
that
are
being
added
back
in
because
Java
s
11
dropped
them,
and
so
we
needed
to
pick
them
up
in
order
to
make
our
story
whole,
and
so
we've
got
Jakarta
activation,
which
is
going
to
be
required
and
it's
required
because
Jakarta
mail
requires
it.
So
that's
that's
going
to
be
a
required
new
addition.
The
other
ones
are
optional,
so
the
jacks
be
the
jacks,
the
XML
web
services,
the
metadata
jws
and
the
soap
with
attachments
or
si
AJ.
F
It's
commonly
known
as
all
of
those
are
going
to
be
new
to
the
platform,
but
they're
going
to
be
optional.
Specifications
and
we've
also
identified
the
two
point
x,
api
group
from
the
EJB
spec
that
will
be
marked
as
optional,
along
with
all
the
other
web
services
that
were
bringing
in
Java
SE
11
the
enterprise
web
services
or
jsr
109.
That
will
also
be
marked
optional.
C
C
F
This
project
board
it's
easier
to
walk
through
this
live
than
to
try
to
use
the
charts.
So
this
is
what
we're
using
to
try
to
track
the
work
for
Jakarta
ee9.
The
main
item
I
want
to
focus
on
here
is
the
milestone
one
ready.
So
what
we
are
doing
is
we
are
driving
towards
a
milestone
delivery
in
June
this
month,
and
what
we're
trying
to
do
is
to
get
all
of
the
specification
projects
to
that
state
so
that
they
would
have
some
form
of
their
specification.
F
Hopefully,
their
API
is
complete
and
some
form
of
their
TCK
in
some
form
of
they're
compatible
implementation,
at
least
to
a
state
that
it
can
all
be
integrated
into
GlassFish
in
the
platform
TCK,
so
that
we
have
something
that
is
demonstratable,
something
that
potential
users
and
customers
could
actually
download
and
play
with
and
experiment
with,
and
it
would
also
help
with
any
of
the
stack
products.
So
any
of
the
stack
frameworks
or
the
ID
es
or
any
of
the
monitoring
tools,
anything
that
would
build
upon
or
what
used
to
build
upon
Java
EE.
F
Now
we
would
have
Jakarta
EE
with
the
new
namespace
and
they
could
start
experimenting
with
it.
So
that's
the
goal
of
the
milestone,
one
ready,
you'll
notice.
We
have
quite
a
few
features
in
here
that
are
already
to
that
state
and
they're.
You
know
prepping,
for
this
milestone
release
so
there's
quite
a
few
there.
F
What
I
want
to
point
out
in
case
people
are
looking
for
areas
to
help
out
in
theirs,
I
have
a
more
progress
column
and
an
almost
there
column,
and
these
features
still
require
some
additional
effort
in
order
to
get
it
over
to
the
milestone
one
ready.
So
if
any
of
these
you
know
Jakarta
faces
authentication
security
servlet.
F
F
Same
thing,
I
want
to
go
back
here
on
our
home
page
for
Jakarta
EE.
There
is
this
box
right
here
called
specifications,
and
this
is
our
location
where
all
the
users,
this
is
live
right
now
everyone
can
go
to
this
and
find
all
of
the
specifications.
Api
is
tcks
and
compatible
implementations
for
all
of
the
specifications
that
make
up
Jakarta
EE.
So
you
can
see,
as
you
page
down,
there's
many
many
different
pieces
that
make
up
the
platform
with
them
Jakarta
EE.
F
What
I
want
to
point
out
is
how
we
are
updating
these
pages
for
the
milestone,
so
the
platform
and
web
profile
and
I'm
kind
of
in
charge
of
those
and
those
aren't
ready
yet
because
we
don't
have
all
of
the
other
pieces
done
so
I'm
going
to
come
down
here
to
annotations
and
show
what
we
are
doing
so
within
annotations.
We
have
this
milestone
release.
So,
if
you
would
click
on
that,
this
has
links
to
all
of
the
items
that
are
being
delivered
with
Jakarta
annotations
for
the
milestone
release.
F
So
you
could
even
come
in
here.
You
could
click
on
this,
this
one's
already
ready
that
you
can
go
in
and
look
at
the
specification
for
Jakarta
annotations.
So
even
though
the
full
milestone
for
the
platform
hasn't
been
released,
yet
the
individual
pieces
are
starting
to
get
put
into
place
for
the
milestone.
So
this
allows
you
to
go
back
and,
for
you
know
to
look
at
you
know
if
there's
particular
areas,
servlet
authentication,
jsps
JPA.
F
If
any
of
those
that
you
have
an
interest
in,
you
can
start
to
look
at
what
these
specifications
are
going
to
look
like
for
the
milestone.
Look
at
the
current
state.
You
could
start
reviewing
them
using
them,
providing
input
via
issues
or
talking
on
their
mailing
list.
All
of
this
capability
is
available
to
interact
with
the
community.
F
So
one
of
the
things
I
guess
I
have
it
highlighted
in
yellow
down
here.
One
of
the
things
that
we
are
really
trying
to
do
is
to
publish
and
promote
all
of
the
activity
that
we've
been
doing
for
all
of
the
different
components,
so
that
that's
a
big
push
as
to
why
we're
doing
this
for
all
of
the
individual
components
I've
mentioned
this
milestone
delivery.
We
plan
to
have
this
ready
this
month,
where
the
the
current
date
is
a
June
23rd.
F
So
far,
it's
looking
like
we're
gonna
be
able
to
make
that
things
are
falling
into
place,
we're
getting
more
successes
and
more
capability
with
the
T
CK's
and
the
GlassFish.
But
just
be
aware,
this
is
a
milestone.
Delivery,
so
do
not
expect
a
hundred
percent
passing
of
the
TC
case
or
a
hundred
percent
compatible
implementations.
F
F
Maybe
that
isn't
your
a
couple
of
key,
but
maybe
you
do
like
to
present
or
write
white
papers
or
blogs,
there's
a
lot
of
different
ways
to
get
involved
with
jakarta
ee
without
diving
in
and
working
on,
the
you
know
specific
code,
that's
getting
delivered,
so
we
look
for
participation,
there's
mainly
lists.
We
do
have
slack
channels
that
were
available
on
and
it's
a
good
way
to
keep
in
touch.
C
C
C
B
E
B
Why
now
is
the
time
to
start,
to
really
dig
into
the
specifications
into
the
milestone
release
and
look
at
how
you
can
start
to
leverage
that
to
be
ready
for
the
the
final
release.
That's
coming
in
q3,
we,
we,
the
community
intentionally,
made
Jakarta
9
a
namespace,
only
release,
and
this
allows
the
downstream
providers
of
tooling
and
and
implementations
to
to
make
this
change
with
little
impact
in
in
terms
of
other
than
the
the
namespace
change.
B
There
isn't
any
new
functionality
that
they
really
need
to
be
concerned
with
they
can
make
the
namespace
change
and
and
do
that,
starting
with
the
milestone
release,
as
as
Kevin
was
mentioning,
we
have
that
coming
in
second
quarter.
Hopefully
you
know,
Kevin
mentioned
the
23rd,
where
we're
getting
pretty
confident
that
that's
going
to
take
place,
but
we
really
want
to
enable
tool,
tools,
implementers
and
vendors
in
particular.
C
B
C
While
you're
doing
that
I'll
get
Tonya
on
there,
you
go
so
we've
had
a
little
bit
of
issues
with
the
chromecast
this
time
and
I
apologize
that
the
purpose
of
this
this
call
today
is
the
is
an
update
call,
so
it's
kind
of
an
update
to
the
community.
What's
going
on,
it's
not
it
as
interactive
as
some
some
would
like,
and
what
we've
said
from
this
as
we
want
to
keep
the
update
call
as
it
is.
This
is
an
update
to
the
community.
C
It's
not
meant
for
very
much
interactivity
necessarily,
but
what
we
want
to
do
is
to
set
up
a
new
call
and
we've
called
it
Friends
of
Jakara
ee
call
and
the
the
thought
of
this
call
is
a
monthly
call
and
a
suggestion
is
that
it
will
be
the
fourth
Wednesday
of
the
month
since
this
one.
This
call
is
the
second
Wednesday,
so
it
will
be
two
weeks
apart,
I've
published
an
agenda
document
that
is
open
for
everybody
to
edit
it's
available
on
on
the
Google
Drive,
it's
available
in
the
the.
C
In
the
calendar
as
well,
so
this
is
a
it's
assume,
invite
that
is
in
the
calendar.
So
if
you
go
to
the
public
calendar,
you
will
find
that
every
month
there
is
a
chicanery
update
call
on
the
second
Wednesday
and
on
the
first
one.
Fourth
one
there
is
a
friends
of
the
chick,
REE
monthly
call,
and
they
thought
of
this
call
is
it's
open
source?
C
Whoever
is
there
are
the
right
people,
whoever
whatever
you
decide
on
this
call
or
do
on?
This
call,
is
the
right
thing.
So
it's
a
kind
of
mobile
space
thing
just
go
ahead,
see
how
it
goes
it's
it's.
The
document
is
editable
by
anyone
has
the
link
the
link
is
linked
from
the
community
calendar.
There
is
also
a
zoom
in
right
here,
so
so
it's
it's
in
soom,
it's
an
agenda
document
in
Google
Drive
and
just
go
with
it.
I'll
join
the
first
call
and
help
with
the
logistics.
C
So
I
hope
you
like
that
and
I
hope
you
join
in
this
call.
In
the
two
weeks,
June
24th,
it's
11:00
Eastern
exactly
the
same
time
as
this
call,
so
it's
a
8
8
a.m.
Pacific,
11:00,
Eastern,
5
p.m.
in
Europe.
So
with
that
I
think
we
are
three
minutes
overdue
and
I
glad
you
enjoyed
or
hope
you
enjoy
this.
Even
though
we
had
some
problems
and
let's
see
you
again
next
month
and
please
join
the
Friends
of
Jakarta
ye
open
space
in
two
weeks.
Thank
you
very
much.