►
From YouTube: Friends of Jakarta EE | Sept 23, 2020
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
Want more great Eclipse Community webinars? Become a member of our Jakarta Tech Talks Meetup: https://www.meetup.com/jakartatechtalks
A
C
A
A
A
D
F
D
A
F
D
F
F
Specifications-
and
I
noticed
when
I
was
reviewing,
for
example,
jakarta
transactions,
so
I
don't
know
if
everyone
knows
how
we're
managing
the
release
of
these
different
specifications.
Maybe
I
can
talk
a
bit
about
that,
probably
because
I'm
starting
in
the
middle
for
those
of
you
who
aren't
familiar
so
ultimately,
what
we
have
to
do
is
steve
if
you
want
to
scroll
to
the
right
just
a
bit
past
the
notes.
Okay,
click
on
one
of
those
specification
links.
F
Okay,
so
our
process
is
basically
every
specification
has
to
create
this
pr,
a
pr
like
this
one
and
what
that
pr
does
is
basically
puts
the
specification,
html
and
pdf
into
a
commit.
It
puts
the
javadoc
into
a
commit
and
that
commit
is
against
the
specifications
repository,
which
is
the
thing
that
is
responsible
for
the
data
on
the
jakarta
ee
specifications
section
of
the
website.
F
You
know
process
of
getting
complete.
It
has
to
prepare
that
data
that
goes
in
the
website
and
and
so
what
we're
doing
is
basically
trying
to
get
all
these
specifications
to
make
this
pr
to
get
the
pr
complete
to
see
the
bunch
of
check
boxes
on
this
and
then
to
go
up
for
vote
once
they
go
for
vote
and
they
pass
the
vote.
Then
we
merge
this
pr.
F
F
You
can
go
back
to
the
spreadsheet
now,
so
we
have
a
lot
of
pr's
that
we
have
to
to
take
a
look
at
and
they're
all
in
various
stages,
and
a
lot
of
these
specifications
aren't
up
for
vote
yet
because
they're
missing
certain
things
like
they
haven't,
promoted
their
tck
or
maybe
they've
got
a
pr
in
their
own
project.
That's
pending,
they
generally
need,
or
they
just
need.
Somebody
on
the
mailing
list,
saying
hey:
why
aren't
we
doing
anything
this
week?
F
F
They
had
a
pr
open
for
almost
a
month
for
changes
to
the
specification
that
no
one
reviewed,
because
there's
just
not
a
lot
of
people
on
the
project,
so
there's
only
like
26
people
subscribed
to
the
mailing
list
and
when
there
is
somebody
there
doing
work,
there
aren't
any
other
people
there
to
review
prs,
and
so
it
stayed
there.
So
one
of
the
things
that
would
be
really
really
helpful
is
if
people
could
go
to
the
individual
specifications
listed
here
and
see
if
there
are
any
open
pr's.
F
E
A
So,
yes,
so
hussain,
what
is
stopping
you
from
voting
in
the
mailing
list
when
you
are
helping
the
ipi
move
forward?
I
have
seen
only
one
vote
coming
from
web
type
greg
all
this
time
since
we
started
jakarta,
e9
release.
My
curiosity
is
what
is
stopping
non-committers
from
voting
in
the
mailing
list?
We
need
more
of
that.
If
you
do
work,
you
owe
you
you
have
that
who's.
G
A
F
A
C
Yeah,
so
the
voting
is
there.
There
are
elected
representatives
for
participant
members
and
I
have
to
remember
all
the
classes
of
voters.
So
generally
the
elected
members
get
they.
They
they
cast
a
vote
for
the
the
group
that
they
represent
right.
So
we
don't.
We
always
accept
any
vote
that
go
that
gets
posted
to
the
list.
C
So
if
somebody
had
something
to
say
about
a
particular
ballot,
we
would
welcome
that
feedback,
but
the
votes
that
count
are
the
ones
from
the
from
the
the
the
the
members
that
are
actually
detailed
in
the
specification
committee.
So
if
you
go
look
at
the
specification
committee
about
page
you'll,
that'll
show
you
who's,
who
who
your
representatives
are
and
or
who
are
the
strategic
member.
A
I
think
we
got
that,
but
the
the
idea
is
that
you
are
correct
only
there
is
like
the
votes
that
are
formal
by
the
10
members
that
are
part
of
the
specification,
but
also
the
community
that
helps
and
the
prs
and
then
the
ipis
and
the
projects
they
can
vote
themselves
and
they
will
be
listed,
but
not
the
count.
The
vote
doesn't
count
as
one
of
the
ten,
but
it's
important
to
get
that
feedback.
A
That
is
what
we
we
we're
trying
to
to
amplify,
and
I
don't
think
we
have
done
a
good
job
explaining
that,
because
we
have
had
one
vote
and
we
have
been
working
on
jakarta
e9
for
months.
So
what
can
we
do?
Do
we
need
to
write
a
blog
that
we
need
to
tweet
about
it?
Do
we
need
to
use
the
jakarta
in
media
to
say
if
you're
helping
on
the
apis,
you
can
vote?
We
need
to
hear
from
you
something
like
this.
Okay,
what
can
we
do
to
to
to
make
this
known.
C
C
F
No,
no,
I
think
I
think,
everybody's
welcome
to
you
know
to
summarize
what
ed
said
earlier
about.
You
know
everybody
can
vote
just
the
specification
committee.
Member
votes
are
the
ones
that
count
for
making
a
special
final.
You
know,
apache
has
the
same
rule.
For
example,
when
you
vote
on
a
release,
it's
actually
not
the
committer
votes
that
make
the
release
final.
It's
the
pmc
votes,
so
they
have
a
similar
sort
of
tiered
perspective.
F
F
You
know,
maybe
we
just
leave
it
in
java
x
and
we
can.
We
can
migrate
it
to
jaccard
in
the
future.
That's
less
work,
but
the
overwhelming
majority
of
the
community
said
we
should.
We
should
change
this
from
javax
to
jakarta
and
because
those
votes
came
in
that
changed
all
the
vendor
votes.
Well,
all
right.
If
it
means
this
much
to
the
community,
then
we
should
just
do
it
now.
F
So
that's
an
example
of
you
know
how
people
expressing
their
voice
does
impact
things,
and
since
this
is
a
very
historic
release,
this
is
like
the
first
release
under
the
jakarta
namespace,
everybody
should
vote,
and
you
know,
for
example,
when
ejb
ballot
goes
up
for
vote.
He's
saying
you
should
definitely
cast
a
vote
because
you
did
so
much
work
on
it.
It
would
be
a
shame
not
to
see
a
vote
from
you.
F
H
My
my
overall
feedback,
as
you
mentioned,
is
every
time
we
have
you
doing
some
releases
on
the
patchy
side
of
the
fence.
We
we
identified
that
people
are
not
specifically
part
of
the
pmc
they
both
plus
one
or
minus
one,
and
they
provide
the
feedback
and
that
feedback
is
really
helpful,
and
otherwise,
I
think,
if
we
didn't
encourage
people
to
to
to
vote,
they
weren't
eager
to
actually
review
what
is
on
on
the
table
for
voting.
A
F
F
F
A
F
A
lot
of
things
that
that
can't
go
up
for
vote
until
the
platform
specification
goes
up
for
vote
or
you
know
near
that
time.
So
you
know
so
we're
gonna
have
a
we're.
Gonna
have
at
least
like
five
specifications
going
up
for
vote
in
the
very
middle
of
november,
so
we
don't
want
more
than
we
have
to
going
up
for
a
vote
at
that
late.
We
want
as
much
to
be
cleared
between
now
and
october,
as
we
possibly
can.
F
C
A
A
Perfect,
I
was
thinking
where's,
the
pr
when
we
were
looking
at
the
other
side
at
the
right
time.
Okay,
so
the
page.
Can
we
add
this
page
to
the
minutes?
I
think
we
should
retweet
it
with
it,
hopefully
with
the
jakarta
media
media,
so
that
you
know
we
need
to
bring.
My
recommendation
is
like
we
should
be
everyone
that
is
working
in
the
prs
should
should-
or
at
least
some
of
us
that
know
we
should
tweet
about
it
to
bring
attention
more
often,
this
this
link
has
not
like.
A
A
F
Well,
if
it's
totally
welcome,
you
know,
that's
that's
the
whole
goal
of
this
course
trying
to
get
as
many
people
helping
as
possible.
The
standard
situation
is
that,
when
we're
in
release
mode
and
a
lot
of
this
stuff
comes
up,
there's
some
knowledge
transfer
but
generally
more
time
spent
on
trying
to
get
the
release
out
the
door
than
we
spend
on
transferring
knowledge.
F
A
B
F
You
know,
hopefully,
hopefully
people
do
watch
this
and
hopefully
people
do
try
to
become
involved,
and
I
I
understand
this
is
not
enough.
This
is
very
little
information.
Considering
how
much
information
you
really
need
to
get
involved,
but
it
is
okay,
just
to
sort
of
show
up
and
say
I
want
to
help.
What
can
I
do?
That's
fine
question.
F
A
D
H
D
D
E
F
D
A
A
We
have
only
yeah
one
missing,
so
please
add
your
names.
You
know
we
just
talked
about
jakarta,
89
and
a
question
for
everyone
here
who
is
involved
in
this
release.
We
have
something
I
saw
something
come
in
from
for
jakarta,
helping
jakarta
e10.
I
haven't
seen
that
contribution
that
contributors
wiki
or
whatever
it
is.
So
how
do
we?
A
How
do
we
see
the
jakarta
a9
impact
jakarta
e-10?
That
is
the
first
release
from
this
project
to
have
to
contain
features
because
we're
not
documenting
enough.
What's
going
to
happen
there?
What
are
the
considerations
that
we
need
to
consider
that
we
need
to
think
about
for
those
contributors
that
are
not
helping
now
but
will
help
on
the
10
because
they
want
to
only
work
on
features.
F
B
B
Then
start
doing
that
start
discussing
that,
but
but
be
aware
that
many
people
will
be
busy
with
the
nine
release,
but
that
doesn't
mean
that
you
cannot
start
doing
things
discussing
things,
creating
issues,
creating
pull
requests,
branching
off
and
and
and
do
the
stuff.
So
you
will
be
able
to
actually
do
a
a
new
release
of
servlets
pretty
soon
after
e9
is
out
because
it
doesn't
kind
of
doesn't
need
to
hang
on
on
a
big
platform,
or
at
least
we
want
these
specs
to
evolve
individually.
A
But,
and
if
I
do
you
see
an
improvement
in
the
melonists,
because
what
I
see
in
the
in
the
specs
is
that
the
mailing
lists
from
each
api
they're
not
growing,
though
momentum
is
happening
with
jakarta
e10
on
the
potential
for
features,
I
don't
see
those
lists
growing.
So
what
do
we
think
about?
Where
are
those
conversations
happening
or
are
they
happening?
Where.
B
E
B
So
if
you
have
a
feature
you
want
to
do
and
get
the
discussions
in
there
where
people
can
see
it.
So
it's
important
to
use
the
the
the
mailing
list
for
the
project
and
the
and
the
issue
tracker.
I
think
if
there
are
discussions
going
on
elsewhere,
it's
not
necessarily
a
bad
thing,
but
they
are
happening
without
anybody
knowing
it.
So
it's
better
to
bring
it
in
where
everybody
can
see
it.
A
E
A
Yup
you're
like
there
okay,
so
many
of
you
know
if
you
are
added,
if
you
have
subscribed
to
the
jakarta
tck
today,
we
yes,
as
of
yesterday,
we
had
the
mailing
list
had
95
subscribers,
so
as
cats
remember
over
a
month
ago,
when
the
conversations
started
and
they
were
only
80.
well
today,
there
are
at
least
15
plus
extra
from
those
conversations,
so
applause
to
everyone
who
is
working
on
that.
If
we
gain
one
subscriber
every
single
time
we
sign
up,
we
do
something
that
is
a
win
for
the
project.
A
I
If
you
share
your
zoom
calls
and
passwords
on
twitter
or
facebook
or
other
social
media
they're
easily,
it's
easy
to
search
for
zoom
and
pwd
keywords,
and
you
can
find
all
kinds
of
community
zoom
calls,
but
that's
all
I'll
say
about
that.
So
wait
till
after
to
to
tweet
about
it.
It
was
one
thing
we
learned
our
post
on
facebook
or
whatever,
but
yeah.
So
from
that
from
that
call
we
started
yeah.
We
had.
I
We
had
a
presentation,
we
started
doing
a
demo
and
then
the
call
got
hacked
and
it's
it
it's
weird.
On
sunday
I
recall
I
practiced
the
demo,
which
was
updated
and
it
worked
fine
come
monday,
we're
going
to
record
it
again
and
the
demo
didn't
work
anymore,
which
is
great
to
have
a
live
demo
that
doesn't
work,
so
you
can
fix
it,
but
anyways
we'll
get
the
demo
recorded
soon.
I
A
Go
ahead,
scott,
I
want
to
interject
and
just
say
that
for
those
of
you
that
did
not
know
over
a
month
ago,
we
started
we
met
for
the
first
time
it
was
maybe
three
weeks
ago
I
can't
remember
anymore,
but
we
we
started
the
threat.
Eddie
started
the
threat
and
then
scott
got
in
I
got
in,
and
then
we
discovered
that
there's
so
much
documentation.
That
needs
to
happen
because
the
tck
is
open.
A
We
did
have
some
issues
last
friday,
so
we
need
to
find
a
way
to
secure
those
calls,
but
the
goals,
I
think,
will
need
to
continue
to
happen,
and
one
of
the
main
things
that
we
found
out
is
that
we
will
use
git
pages
for
the
wiki
that
we
have
started
and
the
votes
is
going.
So
anyone
here
we
can
add
the
the
mail
the
before
we
need
to
add
the
forum
for
the
votes
so
that
we
can
move
forward.
A
I
think
we
can
move
forward
already,
but
the
documentation
has
not
started.
We
have
done
like
a
skeleton
job
and
then
one
of
the
major
things
that
we
found
out
is
that
the
demos
code,
demos
need
to
happen
related
to
the
tck.
Scott
is
one
of
the
best
equipped
to
do
so
because
he
has
been
working
on
the
tck
with
his
teams
since
2013
right.
I
I
I
I
need
some
important
layer
and
like
it'll
yeah
I
went,
I
went
to
our
architect
and
said:
hey
any
idea
how
we
can
create
this
and
he
said
yeah
yeah
I'll.
Do
that
and
you
you
know
he
did.
He
did
the
the
pudding
layer,
which
was
great,
and
so
I
was
kind
of
like.
I
was
done
with
my
initial
task
with
that
and
then
you
know
many
years
later
at.
H
I
F
I
I
I
We
want
to
exclude
sorry
we,
okay,
let
me
start
from
the
beginning
and
there
on
that.
So
for
ee9
we
no
longer
require
interoperability
and,
as
a
result,
the
java
sc
8
java
java
rmi
classes
are
not
are
no
longer
expected
or
required
to
be
used
in
ee9
as
a
result,
and
for
that
reason
you
know
they're
not
in
the
in
the
jakarta
name,
space
and
and
all
that
that
has
an
impact
on
how
we
test
things
like
connector.
A
E
I
I'm
back
sorry
about
that.
Okay,
go
ahead,
go
go
ahead,
I
was
talking
and
suddenly
the
screen
just
went,
you
know
just
kind
of
went,
yeah
disappeared,
but
so
so
anyways,
you
know
the
keyword.
Keywords
are
ways
to
is
a
way
to
enable
or
disable
a
particular
test
for
like
optional
technologies
and
in
the
case
of
rmi.
I
These
are
tests
that
are
something
that
you
may
want
to
run
just
to
make
sure
those
tests
still
work,
but
the
these,
the
you
know,
the
these
are
technologies
that
aren't
even
in
ee9
anymore,
but
we're
using
keyword
properties
as
a
way
as
a
mechanism
to
let
you
still
run
like
the
rmi
iop
test
or
some
you
know,
to
run
some
tests
that
use
those
technologies
that
are
in
java
sc.
So
you
can
still
test
your
code
so
we're
keeping
some
functionality
in
there.
I
So
you
know
along
down
this
path
of
using
keyword
properties.
We
have
noticed
some
inconsistencies
as
well
like
for
tests
that
are
using
rmi,
iaop
or
rmi.
We
noticed
that
we
were,
you
know.
Currently,
you
know
enabling
those
tests,
if
someone
was
testing
web
pro,
specify
the
java,
ee
or
web
profile
keywords,
and
we
decided
hey.
I
You
know
if
you're
running,
if
you
want
to
run
the
ee,
the
full
platform
or
the
web
profile,
you
may
not
want
to
run
these
tests
so
instead
we're
updating
those
rmi
tests
or
tests
that
use
rmi
to
be
more
explicit
and
you
have
to
actually
say
he
opt
in
to
do
the
rmi
iop
technology.
So
just
a
little
bit
of
background
about
you
know
what
we're
been
doing
the
last
week
or
so
in
changes.
I
We
also
have
been
discussing
the
you
know
whether
to
use
the
github
pages
or
the
wiki
for
things
that
change
frequently
and
for
things
that
change
frequently.
It
may
still
be
easier
to
use
the
wiki
for
some
things
like
the
tck
status.
Is
the
feedback
I've
been
getting?
I
didn't
get
that
on
the
mailing
list,
but
it
is
feedback
that
I
did
get
from
just
from
hot
from
further
conversations.
I
A
Scott,
let
me
interject
so
you're
saying
that
we
should
have
both
the
wiki,
but
I
I
I
am
confused.
Should
the
week
the
wiki
doesn't
allow
for
contributors
that
do
not
have
access
commit
access
to
help.
So
how
will
that
example
to
the
project?
We
need
prs
to
fix
what
it
is
and
adjust
and
are
you
well
are
we
if
we
use
the
wiki
we're
closing
the
circle
of
how
good
the
documentation
will
potentially
be?
This
is
why
we
moved
into
pages.
Am
I
confusing
am
I
misunderstanding,
you
here
so.
I
I
I
I
don't
want
to
prevent
someone
who
makes
frequent
changes
to
a
status
page
from
doing
that,
because
that's
you
know
given
the
choice,
if
the
only
way
to
do
that
is
through
github
pages,
and
they
don't
have
time,
then
does
that
mean
we
lose
the
the
regular
tck
status
updates
because
they're
just
not
going
to
have
time
to
keep
up
to
it
so
that
there's
a
trade-off.
There
there's
a
lot
there
yeah.
So
we
still
have
a
lot
of
duplication.
I
I
think
we
should
push
ahead
to
the
github
pages
for
most
other
content,
that's
my
opinion
open
to
others.
If
there's
other,
you
know,
if
there's
some
there's
other
variations
of
other
things
that
should
still
be
on
the
wiki,
but
to
me
I
think
personally,
I'm
okay
with
the
status
page
staying
on
the
wiki.
H
So
based
on
my
understanding,
anyone
can
send
a
pr
with
an
update
to
any
of
that
documentation,
including
the
status
of
dck
results,
or
you
know
any
other
stuff,
and
it's
just
a
matter
for
the
commuters
from
that
project
to
to
to
approve
the
pr
to
to
get
merged.
Obviously,
there
is
a
step
there
that
is
the
that
is
that
the
contributor
needs
to
have
an
eclipse
account
and
have
signed
the
eca.
A
So
last
time-
and
this
is
on
the
tck
friday-
call
that
we
demoed
how
to
do
so
and
it
wasn't
recorded
and
it
took
three
minutes
david.
Do
you
want
to
do
the
demo
right
now
that
is
recorded
so
that
we
can
start
the
documentation,
the
the
contribution
or
do
we
wait
and
you
create
a
demo
and
populate
it
on
the
private?
What's
going
on,
because.
F
F
Well,
I
did
want
to.
I
did
want
to
try
to
well.
While
scott
was
talking
about
the
rmi
and
various
things,
I
did
want
to
clarify
some
points
that
are
very,
very
confusing
and
want
to
make
sure
that
we
were
maybe
not
being
too
aggressive
with
our
removal.
Slash
optional
work,
so
rmi
java,
x,
rmi,
is
not
removed.
So
if
the
statement
was
made
that
was
removed,
our
java,
any
usage
of
javax
rmi,
was
removed
from
ee9.
It
is
not
the
case.
F
Javax
rmi
is
different
than
corba.
Corba
has
been
removed,
the
requirement
for
corba
has
been
removed
from
the
platform
entirely,
and
so
anything
that
references,
the
old
you
know
org
omg,
orb
class
or
anything
of
that
you
know
line,
that's
been
removed,
rmi
it
and
the.
What
what's
confusing
is
that
rmi
iop
was
added.
It
was
has
been
used,
the
entire
time
of
the
specification
to
refer
to
this
concept,
that
your
protocol
cannot
interfere
with
either
rmi
or
iop.
F
F
So
you
can't,
you
can't
go
against
those,
so
we
do
have
interop
tests
that
those
should
get
removed.
They've
never
been
part
of
the
web
profile.
So
I'm
very
curious
what
issues
we
see
in
the
web
profile
that
would
actually
require
any
action
at
all,
and
so,
if
there's
something
there,
maybe
we
are
overstepping
a
bit
in
terms
of
looking
for
any
usages
of
the
package.
Javax
are
online
saying
that
is
a
test
that
should
be
removed.
I
F
E
F
F
They
shouldn't
be
in
the
web
profile
either
because
remote
ejbs
were
never
part
of
the
web
profile.
So
again,
I
don't
see
anything
in
the
from
a
web
pro
pos
web
profile
perspective
that
would
have
needed
changing.
So
we
should
probably
look
at
that
really
carefully.
Is
this
just?
Does
this
get
discussed
on
like
platform
call
or
something.
D
A
We
have
five
minutes
to
go
before
the
specification
call
happens
for
a
few
of
you.
So
does
anyone
have
questions?
I
remember
you
wanted
to
ask
some
questions
is.
Can
you
still
be
talking
about
the
tck,
because
there's
so
much
work?
Ed
is
here
with
the
tck.
Also,
so
do
you
want
to
take
an
answer?
Question
well.
F
F
There's
no
implementation
work
associated
with
that
as
we
covered
in
the
pr,
but
lance
didn't
mention
that
I
should
fix
or
improve
or
add
an
assertion.
I
don't
know
what
assertions
do
and
what
I'm
supposed
to
be
doing.
If
I
add
an
assertion-
and
I
don't
know
where
to
to
go
for
help-
I
mean
like
I
know
where
to
go
for
help-
I
could
ask
the
list,
but
I
don't
know
if
there's
like
a
document.
C
Yeah,
let's
see
so
assertions
are
so
they're
we're
trying
to
we've
always
been
trying
to
follow
the
omg
assertion
process,
which
says
you
know,
here's
a
there's,
a
a
you
know
a
repeatable
link
between
what
you've
written
in
the
specification
and
what
you're
actually
testing
so
assertions
are
derived
from
either
the
javadocs
or
the
specification
text
in
in
the
case
of
javadocs,
we
have
some
automation
for
pulling
those
assertions
out
and
capturing
them
in
an
xml
file.
That
xml
file
is
then
used
to
generate
the
assertions
html
pages
that
come
with
each
spec
right.
E
C
So
those
ten,
if
you,
if
you
look
at
the
assertion
list
for
all
the
for
all
the
specifications,
you'll
generally
find
that
the
assertions
from
the
javadocs
is
much
more,
it's
a
much
richer
set
and
then
they
create
a
coverage
doc,
which
I
believe,
maps
the
assertions
that
are
pulled
out
of
those
documents
to
the
actual
tests
and
that's
the
actual,
that's
what
they
count
as
coverage.
The
ratio
of
the
number
of
assertions
versus
the
tested,
one
tested
assertions;
okay,
so
it's
not
actually
a
coverage,
as
in
code
coverage,.
F
B
I
I
can
give
some
input
on
these
bean
validation
has
done
it
automatically
from
the
ascii
dock.
So
you
put
your
assertions
in
there's
a
code
word
in
the
ascii
doc
and
you
just
use
an
xsl
transformation
to
generate
this
file
and
we
do
the
same
with
mvc.
So
it's
actually
automated
from
the
spec
document.
B
B
A
Yeah,
so
you
guys
go
to
the
next
call
and
I'm
going
to
ask
thanks
everyone
for
joining.
I
am
going
to
ask
hussain:
can
you
on
the
copy
paste,
with
the
link
copy
paste
of
the
minutes,
for
today's
call?
There
is
a
thread
happening
that
I
started
yesterday
to
remind
everyone
about
this
call,
and
can
you
send
the
copy
paste
of
the
link
and
also
copy
paste
of
the
entire
minutes?
To
that
thread,
are
you
able
to
do
that
and
just
don't
add
minutes,
don't
know
names
just
your.
A
A
A
F
E
A
A
Yeah,
so
this
is
how
we
do
it
so
hussain.
Will
you
do
that
right
now,
before
don't
procrastinate,
it
yeah
perfect,
keep
healthy.
Everyone
keep
healthy.
I
will
stop
recording
and
will
be
added
to
the
jakarta
youtube
mailing
list
as
soon
as
we
have
the
collateral
repo
ready
to
receive
the
the
prs.
So
thanks
everyone
see
you
next
time,
peace.
Thank
you.
Everyone
see
you
bye.