►
From YouTube: Jakarta EE Community Call | 2019-11-13
Description
Jakarta EE Community Calls are intended for the wide Jakarta EE community providing progress on the releases and activities related to Jakarta EE.
Agenda:
- Demonstration on how to Jakartify specification documents (Arjan Tijms and Markus Karg )
- Jakarta EE 9 release - roadmap (Steve Milidge)
- Election Results (Tanja Obradovic)
A
A
The
current
files
for
Jakarta,
e9
release
and
I
will
kill
you
just
a
quick
update
on
what's
going
on
with
with
the
elections
and
as
always,
we're
welcoming
input
from
the
community
just
to
for
the
recording
sake
as
well
to
let
you
know,
even
though
we
see
relatively
low
attendance
on
these
calls,
when
we're
recording
line,
which
is
unfortunate.
We're
going
to
you
know,
I
am
welcoming
everyone
to
arrive,
and
I
have
to
say
that
it
was
quite
a
quite
a
bit
of
viewing
of
the
recording.
A
A
B
D
A
A
C
Great
okay,
so
you
asked
me
to
share
an
insight
into
the
status
of
Chikara
fiying,
the
specification
and
well
I.
I
just
want
to
start
with
the
problems
we
have
with
that.
We
had
too
few
people
working
on
that.
As
you
can
see,
we're
were
other
busy
people
and
that's
mostly
it,
and
there
is
a
real
lot
of
work
to
do.
We
have
this
nice
checklist
initiated
by
Iowa
thanks
for
that,
with
a
lot
of
issues
to
do
and
roughly
50%
is
done
already,
but
the
other
50%
is
the
real
work
to
do
so.
C
C
A
C
D
C
Here
we
have,
we
have
organized
UI
things
that
the
logos
and
the
fonts,
and
all
that
this
is
all
done-
that's
great,
but
this
was
already
done
mostly
before
when
we
did
the
boiler
plate,
so
we
just
filled
in
the
text
from
Oracle
into
that
all
applied
specification
and
compiled
it,
and
it
was
done
so.
The
this
is
not
the
hard
thing
to
do.
The
whole
thing
is,
you
have
to
go
through
all.
D
C
C
So
this
is
a
step
by
step
to
be
done
when
when
they
have
done
one
step
and
and
have
something
on
the
web,
then
we
can
change
that
link
and
then
we
have
to
wait
for
the
next
specification
and
we
have
to
change
that
link
and
we
have
to
keep
track
of
of
that.
So
this
is
well.
You
have
to
go
through
the
text
over
and
over
and
over
again
unless
all
specifications
are
online.
So
here
we
have
the
the
intros.
C
C
C
There
is
one
poor
request
in
particular
that
is
interesting,
which
is
called
804
spec
overhaul
first
ranch.
If
you
pull
this
code,
which
is
eight
commits.
Currently,
you
simply
can
use
maven
mvn
package
to
compile
the
PDF
file.
So
in
fact
you
you
can
just
use
it
like
source
code.
So
if
you
want
to
help
with
reworking
on
the
specification,
just
pull
this
code
and
use
mvn
package
and
you
can
start
to
work
on
it
by
picking
one
of
the
open
issues.
C
This
is
the
issue
tracker
just
go
into
issue
tracker
everything
that
has
no
name
beside.
It
is
free
to
work
on
so
here's
a
list
of
stuff
you
can
work
on
and
if
you
start
working
on
that,
just
go
to
edit.
It
put
your
name
into
it
and
press
update
command,
and
then
we
know
you're
working
on
that.
If
you're
done
just
open,
another
pull
request
and
we
will
review
that
and
refuse
is
the
next
problem,
because
we
have
a
nice
rule
at
checks
or
s.
Nobody
must
directly
push
to
master.
C
D
E
While
Ariana's
getting
ready,
this
is
Kevin
I
just
wanted
to
thank
Marcus
for
the
presentation
on
updating
that
spec
and
I
really
appreciated
your
view
on
how
much
work
it
was
to
actually
get
this
done
because
you
know,
if
we
look
at
some
of
the
comments
and
the
community,
you
know
people
are
asking
all.
When
is
this
going
to
be
done?
E
What
is
this
going
to
be
done
and
it's
like
yeah
we're
always
looking
for
help
I
mean
not
only
for
the
jacks
are
aspect,
but
for
several
of
them,
as
as
we
get
them
from
Oracle,
and
we
we
need
to
do
this
work.
It's
not
just
magic
overnight
thing
in
there
out
there
there's
there's
quite
a
bit
of
work
that
has
to
be
done
to
make
them
useful
by
Jakarta.
So
thanks
for
that
overview
and
having
a
separate
viewpoint
on
how
much
work
it
is
to
get
this
ready,
yeah.
C
A
B
Perfect,
so
yes,
I
did
security
is
back.
This
one
was
a
bit
easier
to
start
with
for
two
reasons.
The
first
reason
is
that
that
I
mainly
wrote
the
initial
text
myself
so
I'm
quite
familiar
with
the
text.
The
second
one
is
a
young
spec,
so
it's
not
that
big
yet
and
the
third
one
is
was
already
in
asciidoc
format.
So
there's
not
a
lot
of
weird
formatting
from
any
conversion
or
what
have
you
so
we
did
needed
to
do
some
things.
B
I
summarized
them
a
little
bit
hastily
my
laptop
here
signalman
computer's,
not
working
at
the
moment,
so
Guillermo
he
changed
a
couple
of
terms
at
first
then.
The
second
thing
we
did
was
deleting
some
of
the
original
files.
That's
where
basically,
the
header
and
the
license
files.
The
days
these
weren't
needed
and
the
unused
placeholder
scope
that
was
used
for
the
skeleton
document.
So
I
can
quick,
look
yeah.
B
So
these
were
basically
these
three
files
that
could
just
be
deleted
and
placed
with
the
Jakarta
version.
It
was
relatively
easy.
The
second
thing
that
we
did
was
renaming
our
files
to
have
consistent
extension,
so
the
original
files
as
they
were
transferred
they
all
had
the
asciidoc
extension
jakarta,
was
using
the
a
docx
extension.
B
B
It
says
here
that
the
a
doc
is
recommended,
so
that's
what
I
did
change
them
to
a
doc.
So
the
next
thing
that
we
did
was
actually
looking
at
the
preface
I
mentioned
some
of
the
original
people
working
on
it
clarified
that
these
things
were
in
the
past.
They
were
under
the
JCP
specification.
The
it
was
changed
to
specification
is
on
the
JCP
expert
group
on
the
GCP
at
the
ICP
was
half
here
and
then
edit
the
clips
people.
So
this
was
next
go
back
to
this.
B
Then,
basically,
what
next
is
just
reading
through
the
document,
seeing
where
things
still
missing
these
things,
communists,
that's
essentially
going
to
the
sewers
which
have
here
then
building
it
just
using
mafic
line
style
and
so
built
into
PDF.
You
can
see
the
PDF
in
your
targets,
folder
in
Nathan
click
on
it,
I
hope
it
shows
up
on
the
screen.
You
get
a
rendered
version
and
it's
basically
a
matter
of
reading
trivet
see
if
you
miss
anything,
whether
there's
any
spelling
mistakes
when
you
change
table
spaces
or
missings,
and
that's
basically
what's
been
doing.
B
Maybe
now
reads:
chapter
2
essentially,
so
there
were
small
things
like
the
replacement
from
Jakarta
from
Java
EE
to
Jakarta
has
a
misty
space
somewhere.
So
the
word
like
all
spaces
made
missings
and
other
things
that
were
added
a
JSF
thing
was
made,
so
that
was
changed
into
Jakarta
surface
face,
as
we
did
this
summer,
find
it
quickly.
B
So
that's
the
one
area,
so
they
still
said
JSF
and
expression.
Language
was
changed
to
Jakarta
expression,
language.
That's
it's
wrong
and
it's
basically
what
we
continue
to
do.
So,
as
I
mentioned,
we
now
reached
chapter
2.
There's
a
couple
more
chapters,
but
not
not
just
big
spark,
so
we'll
probably
I'll
be
able
to
go
through
these
in
this
few
days.
B
B
Yeah,
so
CD
is
an
exception,
so
CDI
was
not
an
Oracle
term.
It's
not
on
the
list
of
forbidden
terms.
We
clarify
it
in
several
occasions
by
prepending
it
with
Takata,
so
it's
Jakarta
City
on,
but
it's
not
forbidden
to
you
use
CDI.
It
is
kind
of
a
built-in
usage
SF
and
yell.
It
should
be
what
helps
you
all.
E
B
B
Yes,
here
so
easy,
the
first
uses
of
the
year
French
to
drag
its
men,
sit
in
full.
So
here
it's
Jakarta
circle,
specification
version
4
and
between
square
bracket
servlet,
for
that,
oh
and
the
same
goes
for
Jakarta
authentication
and
then
in
the
follow-up
that
references,
it's
just
the
short
term
and
this
link
to
the
specification
page
here.
B
So
in
this
case
surface
for
links
to
the
static
are
circles
for
its
updates
on
the
Jakarta
he
website
and
in
same
fashion,
authentication,
Takada
authentication
links
to
Jakarta
indication,
but
it's
Jakarta,
ie
I
mean
this
links,
as
Marcus
mentioned.
They
have
to
be
checked,
of
course,
so
that
some
amount
of
work
is
that
crazy
must
work,
but
he
do
extract
them
and
similarly
there's
a
few
eternal
links
which
you
needed,
such
as
well,
since
they
could
have
changed
when
you
did
the
replacement
for
terms,
but
they
all,
like
I,
said
it's.
B
It's
going
quite
well,
it's
relatively
fast.
It's
basically
just
reading
through
the
document
and
whenever
you
see
something
you
change
it
and
I
do
a
pull
request
and
then
the
other
guys
review
it
and
it's
basically
it's
unlike
jax-rs.
We
don't
have
the
heart
requirement
for
refuse,
so
it's
still
ok
to
merge
it
in.
If
people
haven't
reviewed
it
and
basically
we
operate
under
the
assumption
that
if
something
went
in
that
this
is
quite
correct,
it's
still
searched
control.
So
people
can
refer
to
it,
but
that's
up
to
the
project.
B
D
B
G
G
Our
aim
is
to
have
you
know,
someone
who
leads
it
and
someone
who
assists
so
I've
volunteered
to
assist
by
giving
moral
support
to
the
lead
and
that's
pending.
So
again,
this
is
all
community.
So
what
I'm
saying
is
you
know
my
view
of
where
this
is,
but
I
am
in
many
of
these
committees
and
things
so
I.
You
know,
I
have
a
pretty
broad
view
of
where
we're
at
at
the
moment.
G
So,
let's
just
wanted
to
sort
of
recap
as
it's
the
sort
of
community
call
of
where
we
are
now
so
obviously,
Jakarta
e8
was
released
just
in
time
for
code
one,
and
that
obviously
gives
us
full
compatibility
with
Java
8.
So
the
aim
was
to
have
it
to
be
binary
compatible
so
that
we
could
state
that
Carter
e8
was
binary
compatible
to
Java
EE
8,
one
of
the
big
things.
Obviously
now,
as
we
just
seen
on
the
last
two
conversations,
is
the
specifications
on
our
open
source
open.
G
There
are
on
github
and
they're
all
following
an
open
process
which
is
Jakarta
respec
process
and,
as
Irena
Marcus
said,
they're
all
willing
to
pull
requests
to
assist
in
moving
these.
The
other
big
big
piece
of
Jakarta
e8,
obviously,
is
the
open
source
TCK
license
and
the
open
source
process
and
the
fact
that
we
can
actually
see
the
code
for
the
TCK.
G
That
is
a
huge
change
from
where
we
were
with
java
8
and
finally,
we've
got
a
set
of
compatible
implementations
in
jakarta
ee.
You
have
to
have
an
open
source,
compatible
implementation
to
have
a
specification
and
that
that
that
impacts
took
actually
nine
as
well,
which
we'll
see,
but
at
the
moment
we
have
four.
So
we
have
eclipse
last
fish,
open,
Liberty,
payara
server
and
wild
fly.
G
So
now
now
that
that
was
done,
that
has
been
a
bit
of
a
lull,
as
everyone
had
you
know,
took
some
breathing
space
and
went
to
many
conferences,
but
now
we're
turning
our
minds
to
Dakar
3
9.
So
this
is
sort
of
my
view
of
how
I
see
the
various
releases
that
we
got
over.
You
know
the
next
year,
or
so
so,
Carter
e8
as
I've
just
said,
that
was
the
compatibility
release.
G
That's
a
release
that
is
the
same
as
Java
EE
8
Jakarta
ie
9
is
really
what
we're
calling
a
sort
of
tooling
release
which
I'll
explore
a
bit
more
cartoon
9
will
be
the
namespace
change
and
we
have
to
move
for
any
API.
We
want
to
evolve
or
change.
We
have
to
move
from
the
direct
namespace
to
the
Jakarta
namespace,
so
focus
it's
got
to
be
nine.
G
Look
to
get
that
done
and
the
other
focus
will
be
deprecation
and
removal
of
a
bunch
of
old
api's
in
specifications
which
again
I'll
cover
a
little
bit
later
it
in
sort
of
my
view.
One
of
the
goals
are,
one
of
my
girls
have
been
pushing
forward
in
those
committees
is
for
two
Carter
e92
to
lower
the
barrier
of
entry
for
it
for
new
players
in
the
market.
So
the
more
things
we
can
remove
that
are
not
really
used
anymore.
G
G
We
don't
put
in
place
any
changes
that
will
break
up
with
compatibility,
I've,
dozens
or
existing
specifications.
That
doesn't
mean
you
know
we
don't
do
any
changes
to
API
so
about
all,
although
that
hasn't
you
decided
and
agreed
yet,
but
it's
possible
that
we
allow
or
upward
compatible
changes
and
some
bug
fixes
and
clarifications
those
sort
of
things.
G
G
If
doing
a
move
would
be
just
due
to
namespace,
so
they
haven't,
they
haven't,
got
compile
errors
due
to
you,
know
things
being
removed
or
behaviors
changing
or
API
changing
drastically.
So
it's
the
goal
really
50
car
39
is
to
target
it
as
a
as
a
stable
point
in
this
transition
over
to
the
new
namespace.
G
G
So
the
interesting
thing
about
Dakar
tree
9
is
a
lot
of
talk
about
cadence
and
things
that
Carter
EE
and
whether
to
follow
a
release,
train
model
or
or
what,
but
for
Carter
e9
the
scope
is
fixed.
You
know,
there's
certain
specifications
that
we
need
to
migrate
over
to
the
new
namespace.
So
what
we're
going
to
have
to
do
is
essentially
determine
the
date
because
the
scopes
fixed,
so
the
dates
gonna
have
to
move
around
the
fixed
quantum
of
work
that
we
have
to
do
so
purely
on
a
sort
of
analysis.
Point
of
view.
G
What
how
do
we
come
up
with
a
date
and
again,
we've
only
just
started
the
calls
about
this
in
the
platform
development
group,
one
of
them
was
yesterday.
One
thing
we
need
to
do
is
we
need
to
do
dependency
analysis,
as
Marcus
Cenarion
shown
just
on
the
specification
level.
Specs
depend
on
other
specs
namespace.
You
know,
API
is
independent
of
the
api's,
so
we
need
to
look
at
the
dependency
analysis
tree
of
for
this
namespace
change.
G
You
can
have
already
done
a
PR
for
this
on
concurrency,
which
doesn't
depend
on
much
else.
So
that
was
very
easy,
but
obviously,
if
you
depend
on
another
API,
you
can't
change
your
API
definition
until
I
API
is
changed
as
well,
and
these
will
all
need
to
be
staged
so
that
you
can
refer
to
it
through
maven,
so
we're
gonna
have
to
go
for
a
model
where
we
take
the
dependency
analysis.
G
Obviously,
a
major
piece
of
work
will
also
be
the
the
the
big
platform
TCK
project.
There
are
a
few
TCK
projects
for
that.
One
is
going
to
need
a
lot
of
work
once
all
art
staged
artifacts
are
available
so
that
that
can
then
be
converted
and
there's
a
chicken
and
egg
here
around
TCK
passing
T
CK's
and
obviously
changing
our
API
s
and
finally,
the
other
big
thing
that
is
required
to
actually
do
a
final
release
of
dakari
nine.
G
G
G
Also,
as
a
final
thing.
We
are
prioritizing
early
delivery
over
any
changes,
so
feature
changes
or
backwardly
compatible
changes.
So
essentially
we
want
to
pick
the
earliest
possible
date
we
can
have
in
2020
and
hopefully
at
least
first
half
2020,
so
anything
that
could
slow
it
down.
We
will
postpone
and
aim
to
you
know
people
should
prioritize
speed
over
anything
else,
so
going
digging
a
little
bit
into
what
we
see
is
the
content
to
car
3
9.
G
G
G
We've
also
sort
of
agreed
that
backward
compatibility
will
be
a
runtime
concern,
so
that's
backward
compatibility
to
an
application
still
using
with
Jeff
X
the
original
Jetix
namespace,
rather
than
imposing
it
on
a
specification
level.
We
will
leave
that
to
the
market
for
runtimes
to
support
old
applications
running
in
a
namespace
again
mainly
to
prevent
the
need
for
any
new
players
going
forward
to
have
to
support
old
applications,
because
if
you
put
it
in
the
spec,
it's
probably
gonna
live
there
from
for
many
years.
G
G
Gotta
have
concerns
out
of
the
way
on
that
one,
oh,
what's
being
proved,
I
won't
read
them
all
out,
but
essentially
some
of
the
old
XML
specifications,
some
of
the
old
administration
and
specifications
like
deployment
and
management
and
the
old
egb,
2.1
and
area
work,
as
well
as
the
old
web
services.
Spec
that
isn't
really
used
anymore,
so
they'll
be
removed
again.
Will
will
have
a
vote
on
that,
just
to
confirm
that
I,
don't
think
it's
particularly
controversial
and
like
say
I
dead
from
se8
will
be
X
more
binding
in
an
activation.
G
So
that's
what
would
be
in
Jakarta
9
so
from
a
Jakari
10
perspective.
I
would
see
this
as
a
feature
release
and
the
important
thing
really
from
which
country
10
perspective
is.
We
can
start
that
work
now
in
all
the
specifications,
and
you
know
it's
encouraged
for
projects
to
do
start
doing
e
10
work
as
well
as
you're
doing
the
EU
9
namespace
migration.
G
So
this
can
work
in
parallel.
I
suspect
that,
but
again
this
needs
to
go
out
for
conversation
and
review.
That
e
10
will
follow
more
of
a
release,
train
model
in
that
the
day
date
will
likely
to
be
fixed
and
the
scope
adjusted
depending
on
when
specifications
are
available
and
have
updated
and
can
do
a
release
to
meet
that
release.
Train
date
beyond
Shikari
10,
the
cadence
of
Wendy
Carter
II,
will
be
released
to
stop
being
decided
personally.
G
D
G
Yes,
that
would
not
make
sense,
I
think
for
concurrency.
We've
put
the
namespace
release
into
the
next
major
version
and
then
in
the
branch
and
then
we'll
do
the
similar
for
no
the
3.0
or
whatever
the
next
four
ten
years
as
well
into
master
in
room
at
various
points.
In
time.
Probably
the
epi
means
project
can
can
do
their
own
thing,
but,
as
Kevin
said,
sensible
wait
for
word.
G
Final
slide
really
is
just
a
call
to
action
really
is
dakar.
Tree
is
open
its
open
source,
and
that
also
means
that
everybody
can
contribute
we're.
Looking
for
you
for
the
contribute-
and
I
think
every
project
is
absolutely
up
for
more
more
committees,
more
contributors,
but
in
the
first
instance
the
platform
there.
The
list
is
covers
the
sort
of
platform
specification.
G
So
you
can
join
that
if
you
want
to
know
what's
happening
on
the
release,
planning
and
progress,
there's
a
general
community
list
and
then
every
single
project
and
specification
has
their
own
mailing
list
typically
expect
name
dev
everything's
on
github,
it's
all
open
source
as
as
Marcus
and
Aaron
said
they
all
willing
to
have
pr's.
You
can
raise
issues
and
each
API
how's
it
get
hub
repos.
If
you
want
to
do
some
namespace
change
work,
then
you
know
just
just
go
for
it
about
I
know.
G
F
Yes,
tea
fight
is
that
well,
I
I
can
tutor
and
I
want
to
contribute.
I
have
a
lot
of
specifications,
yeah
look
if
there
is
some
work
needed
and
there's
a
platform
which
would
be
the
best
way
to
look
for
what
is
it
go
by
every
specification
and
see
if
there
are
any
issues
open
or
just
start,
creating
crew
requests
or
go
through
the
platform
to
see
on
the
board,
something
that
can
be
done?
I
yeah
I
feel
just
Fork
repository
of
a
specification
and
do
a
pull
request
for
the
namespace
change.
G
G
B
Yeah,
so
it's
basically
indeed
just
go
for
it.
So
it's
as
Steve
mentioned
it's
a
specification,
probably
that
you
should
be
like
I've
read
any
using
in
four-way.
So
if
you
do
ap
offer
specificity,
you
know
nothing
about
it.
Let
that's
less
likely
for
you
to
to
succeed,
but
if
it's
a
specification
that
he
usually
you
know
exactly
what
you're
doing
or
you
know
even
half
what
you're
doing
than
just
to
go
for
it
indeed,.
C
B
Or
creating
issue
first
and
then
like
ask
for
some
feedback
so,
for
instance,
in
JSF,
the
the
work
for
the
namespace
change
be
based
off
of
2.3
and
that's
in
a
separate
branch
and
the
McMaster
is
currently
going
to
be
first
and
then
rebuilt
from
two
three.
If
you
don't
know
that
you
would
do
the
PR
mom
master,
then
it
couldn't
be
accepted
there,
and
that
with
me,
some
extra
work
for
you.
Indeed,
there's
market
status
handy,
it's
good
to
first,
ask
which
branch,
if
you
do
or
not
somebody
else
is
working
on
it.
Yes,.
A
B
So
maybe
comments
about
the
JDK
eleven
item
that
Steve
mentioned.
So
we
briefly
discussed
that
before
and
like
one
of
the
proposals
was
and
there's
been,
no
means
that
it's
going
to
be
accepted
a
final
over
whatever,
but
that's
to
have
to
do
subsets
of
the
specification.
Basically,
so
it
would
have
to
Carter
ee9
for
JDK
8
and
you
got
nine
for
JDK
eleven
and
those
could
potentially
be
two
certifications.
B
A
B
Yes,
on
the
one
hand,
the
if
Jakarta
89
is
just
about
name
space.
At
least
you
should
perhaps
only
do
the
name
space.
On
the
other
hand,
JDK
8
is
quite
old,
and
this
is
the
opportunity
to
at
least
move
suit
etiquette
11,
most
platforms
are
all
very
using
the
Ericka
11
anyway
much
of
the
offenders
I'm,
and
so
it
wouldn't
be
a
really
big
step,
but
it's
something
that
needs
to
be
discussed
that
time
is
running
out
quickly.
Yes,.
B
B
So
if
you
supported
us
offender
like
we
did
for
pyaara,
then
you
don't
necessarily
have
to
guarantee
that
it
works
or
that
the
TCK
has
passed
on
it
and
the
tostring
are
still
in
the
next
point
there.
The
TCK
would
need
to
be
updated,
at
least
in
some
way,
to
support
verifying
that
it
works.
The
delicate
11
could
also
mean
some
work,
which
could
delay
the
release
of
Jakarta.
You
know.
A
D
A
A
A
And
thanks
for
all
your
work
and
just
a
reminder
to
everyone
else
who
is
you
know
that
we
have
two
vacant
spots
in
the
marketing
and
brand
committee
for
any
you
know
participant
members.
If
you
are
eligible,
please
get
in
touch
and
see
me
how
and
if
you
can
be
involved
and
keep
in
mind
that
next
frame
there,
which
spring
we
will
have
another
yearly
election.
A
A
A
Yeah
this
month
we
will
have
a
newsletter
from
eclipse
foundation
dedicated
to
Jakarta
EE.
So
please
have
a
look
at
that
as
well
and
as
always,
give
us
your
feedback
on
anything.
That's
pretty
much
everything
that
I
have
for
today,
so
any
other
topics
or
questions
from
the
community,
and
we
have
a
small
attendance
on
the
code.
But
this
is
we're
going
to
be
recorded
and
I
want
to
invite
people
to
you
know,
even
when
they
are
viewing
the
recording.
If
they
have
a
questions,
comments.
A
A
So
if
there
are
no
questions
and
comments,
then
we'll
just
close
with
this,
and
thanks
for
attending
the
community
folder.
As
always,
let
me
just
go
quickly
there.
We
have
using
the
wrong
Mouse
here:
okay,
let's
let's
go
here
so
the
community
folder
here
has
all
the
details.
One
of
the
folder
each
each
month
has
its
own
folder.
So
in
the
month
of
November,
we
have
those
two
slides,
sorry
satisfies
that
were
shared
with
us
and
I
will
put
the
recording
link
here
as
well
or
the
recording
itself
here.