►
From YouTube: JCasC Office Hours, Sep 25, 2019
Description
Regular JCasC project meeting. Status updates and discussions. Meeting notes: https://docs.google.com/document/d/1Hm07Q1egWL6VVAqNgu27bcMnqNZhYJmXKRvknVw4Y84/edit#heading=h.b36frpe4t93
A
Cool,
so
here
we
are
25th
of
September.
We
have
myself
Tim,
Jacob
and
John
on
the
call
just
going
through
the
agenda.
I,
don't
believe,
there's
been
any
release
since
the
last
one
16
days
ago.
No,
you
had
a
chat
with
Olli
Donna
on
Friday.
He
asked
to
do
the
next
release
and
I
think
the
plan
was
due
on
Friday,
but
we
didn't
leave
up
doing
it.
I'll
ping
him
after
this
and
see
if
he
wants
to
do
released.
A
Some
Java
doc
updates
and
JSON
schema
documentation,
and
we
have
a
recent
contribution
which
just
emerged
this
morning,
which
was
moving
well
validating
some
of
the
demos
from
the
integration
tests
as
a
new
configured
with
readme
just
happened.
They're
configured
with
readme
annotation,
which
will
read
from
the
demos
folder
invalidates
any
of
the
demos
that
have
been
set
up
so
I
think
only
two
or
three
we
set
up
in
this
pull
request
with
a
follow
up
or
arrested
or
the
rest
of
them.
But
here
this
is
what
America
validating
the
Active
Directory
demo.
A
It
looks
for
the
markdown
in
the
readme
file,
which
is
really
good,
so
it
means
that
the
demo,
as
we
know
their
work
and
if
we
want
it-
and
we
can
bump
the
version
in
the
integration
test
and
see
that
the
demo
is
still
valid
on
the
new
version
so
should
be
really
useful.
We
see
on
the
traffic
stats
that
we
get
quite
a
lot
a
lot
of
people
viewing
the
demo.
B
A
A
So
we
have
a
new
integration
test,
would
get
a
branch
sauce
and
a
heading
github
actions
as
a
backup
CI
just
check
where
the
Travis
was
removed
or
no
I,
don't
think
Travis
has
been
removed.
Yet
I
know
Joseph
was
having
some
issues
it
didn't
look
like
it
was
actually
triggering
have.
Actions
is
now
on
a
Jenkins,
Sai
or
Jenkins.
The
I
organization.
A
A
A
A
It
doesn't
look
like
it's
from
backported
so
anyway,
so
people
who
are
on
her
on
the
2.1
7
6
release
line
I
can
get
cask
in
the
bomb.
So
you
won't
need
to
specify
the
configurations
code
version
for
the
main
plug-in
and
for
the
tests,
which
is
nice,
means
as
you
pump
your
versions
and
dependable
pumps
them
you
don't
have
to
maintain
it.
A
A
So,
there's
a
pretty
big
warning
at
the
top
that
says
that
this
will.
This
will
definitely
change
before
we
market
as
a
TA
feature,
but
it's
currently
in
its
current
state.
It
works
as
far
as
the
descriptors.
It
describes
the
configuration,
but
it
doesn't
give
you
any
auto
completion
and
it
doesn't
provide
any
documentation
and
it
doesn't
tell
you
if
the
attributes
are
wrong
either
the
only
thing
it
really
does
at
the
moment.
It
tells
you
if
you
get
the
data
types
wrong.
A
System
Reed,
so
this
Paul
Chryst
is
still
outstanding,
but
we'd
really
like
to
give
em
it's
currently
being
reviewed
by
Daniel
Beck
once
or
twice
and
Oh
Lucas
said:
he'll
review
it
a
couple
of
times
just
waiting
for
him
to
get
back
to
it,
but
yeah.
If
anyone
wants
to
review
this
would
be
quite
useful,
as
it's
really
just
waiting
on
reviews,
especially
from
the
security
team.
A
Just
a
background
on
it.
It's
to
give
a
new
permission
that
allows
users
to
see
the
system
configuration
but
not
change
it
so,
and
then
so
in
the
case
of
eight
fully
configured
us
courage,
Jenkins,
you
can
allow
your
users
to
export
configuration
and
see
all
the
options
and
see
what's
installed,
which
will
help
them
contribute
to
to
your
config,
but
they
can't
they
can't
making
changes
and
the
other
side
of
it
is.
Your
administrator
is
blocked
from
configuring
it
through
the
UI.