►
From YouTube: How to Jakartify Your Specification Docs | 2019-11-13
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Great
okay,
so
you
asked
me
to
share
an
insight
into
the
stages
of
Jakara
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
that
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.
A
A
B
A
B
A
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
boilerplate,
so
we
just
filled
in
the
text
from
Oracle
into
that
boilerplate
specification
and
compiled
it,
and
it
was
done
so
this
is
not
the
hard
thing
to
do.
The
whole
thing
is,
you
have
to
go
through
all.
B
A
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.
A
A
A
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
8
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
mbn
package
and
you
can
start
to
work
on
it
by
picking
one
of
the
open
issues.
A
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
poor
request-
and
we
will
review
that
and
refuses
the
next
problem,
because
we
have
a
nice
rule
at
checks-
RS,
nobody
must
directly
push
to
master.
A
C
B
D
Well,
Ariane
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
well.
When
is
this
going
to
be
done?
One
is
it's
going
to
be
done
and
it's
like
yeah
we're
always
looking
for
help.
D
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
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.
A
D
B
C
Perfect,
so
yes,
I
do
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.
I
summarized
them
a
little
bit
hastily
my
laptop
here.
C
So
the
main
computers
not
working
at
the
moment
so
kuma
he
changed
a
couple
of
terms
at
first
then.
The
second
thing
we
did
was
deleting
some
of
the
original
files
that
were
there
and
basically
the
header
and
the
license
files
a
days
these
weren't
needed
and
the
unused
placeholder
sculpt.
That
was
used
for
the
skeleton
document.
So
I
can
quick,
look
yeah,
so
these
were
basically
these
three
files
that
could
just
be
deleted
in
place
with
the
Jakarta
version.
It
was
relatively
easy.
C
The
second
thing
that
we
did
was
renaming
our
files
consistent
extension,
so
the
original
files
as
they
were,
transferred
they
already
asked
a
docx
extension
Chikara
was
using
the
a
docx
extension.
Actually,
a
doc
seems
to
be
the
preferred
one
to
you.
So
I
looked
it
up
at
the
recommended
practices,
and
it
actually
says
here.
C
It
says
here
that
the
a
doc
is
recommended,
so
that's
what
I
did
change
them
to
a
dark.
So
the
next
thing
that
we
did
was
actually
looking
at
the
preface
it's
going
to
mention
some
of
the
original
people
working
on
it
clarified
that
these
things
were
in
the
past,
so
they
were
under
the
JCP
specification.
The
it
was
changed
to
specification.
It's
on
the
JCP
expert
group
on
the
DCP,
a
DHCP
was
half
here
and
then
edit,
the
Eclipse
people.
So
this
was
done
next,
come
back
to
this.
C
Then,
basically,
what
next
is
just
reading
through
the
document,
seeing
where
things
still
missing
whistling
communists,
that's
essentially
going
to
the
source
here
then
building
it
just
using
mafic,
clean
style
and
so
built
into
a
PDF.
You
can
see
the
PDF
in
your
targets,
folder
in
click
on
it,
I
hope
it's
just
a
front
screen.
You
get
a
rendered
version
and
it's
basically
a
matter
of
reading
through
it
see
if
you
miss
anything,
whether
there's
any
spelling
mistakes,
maybe
change
table
spaces
or
missings,
and
that's
basically
what's
been
doing.
C
So
that's
the
one
area,
so
this
still
said
JSF
and
expression.
Language
has
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
reach
chapter
2,
there's
a
couple
more
chapters,
but
not
not
just
in
big
spark,
so
we'll
probably
I'll
be
able
to
go
through
these
in
just
few
days.
C
C
D
C
C
But
it's
Jakarta,
ie
I
mean
these
links,
as
Marcus
mentioned.
They
have
to
be
checked,
of
course,
so
that
some
amount
of
work
is
not
crazy,
must
work
but
key
to
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
are
like
I
said
it's.
It's
going
quite
well,
it's
relatively
fast.
C
It's
basically
just
reading
through
the
document
and
whenever
you
see
something
you
change
it
and
they
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
hard
requirement
for
refuse.
So
it's
still
ok
to
merge
it
in.
If
people
haven't
reviewed
it
and
basically
we
operate
on
the
assumption
that
if
something
went
in
that
this
is
quite
correct,
it's
still
search
control.