►
From YouTube: 2021-04-07 meeting
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).
B
B
B
B
B
So
yeah
there's
that
also
1.1.0
got
released
last
night
or
if
you
were
in
japan
yesterday
morning,
I'm
not
exactly
sure
when
it
was
in
japan
yeah.
So
there's
that.
So
I
assume
that
the
agent
will
update
within
the
next
few
days
to
use
it
there's
not
really
very
much
in
the
way
of
changes.
So.
C
B
B
C
B
B
Oh,
so
this
is
an
interesting
one.
This
is
kind
of
a
big.
It's
gonna
be
a
big
hunk
of
work.
I
think
where
did
it
go?
B
The
idea
is,
would
be
really
cool
if
we
had
a
way
to
do
some,
some
kind
of
code
generation
with
an
annotation
process
or
something
that
would
let
you
know
akin
to
auto
value.
Maybe
I
don't
know
I
mean
some
sort
of
non-auto
instrumentation
solution
for
using
the
annotations.
B
B
Okay,
so
yeah
I
mean
there's
lots
of
possible
ways.
To
probably
I
mean
I
don't
know,
there's
lots
of
there's
we
could
you
could
imagine
creating
an
animation
processor
that
would
run
at
build
time
and
generate
code
or
you
could
do
something
like
lombok.
If
you
wanted
to
be
really
crazy
or
you
could
imagine,
writing
an
aspect-
and
I
don't
know
doing
some
aspect-
j
stuff,
which
is
also
generated
code,
I
guess,
or
proxy
or
dynamic
proxies,
in
which
case
you
could
only
do
it
on
interfaces.
I
think
I
don't
recall
my
dynamic
proxy
knowledge.
B
Yeah
I
mean
there's,
there's,
there's
a
bunch
of
different
ways.
It's
more!
It's
kind
of
a
you
know
an
open-ended
feature
request.
B
A
C
B
C
Meow
blah
blah
blah
blah
blah
blah,
but
that
that
essentially
very
seriously
similar
thing
you
can't
have
an
annotation.
You
can
have
your.
You
can
write
the
I
state
transformation
in
groovy,
which
essentially
works
almost
the
same
way
as
annotation
processor.
In
java,
only
it's
much
more
user-friendly
or
groovy.
C
C
A
B
Right
yeah,
so
if
anybody
is
interested
in
picking
up
any
of
these
help
wanteds
I
kind
of
been
tagging
every
feature
request,
as
I
help
wanted
recently,
just
because
I
don't
have
time
to
work
on
them,
and
it
would
be
great
if
we
could
get
more
people
involved.
B
Unfortunately,
I
was
hoping
to
put
more
things
of
like
good
first
issue,
but
there's
just
not
much
good
for
first
issue
fodder
like
if
you're
a
junior,
very
early
career
developer,
it's
just
not
a
lot,
it's
easy
to
pick
up
and
work
on
in
this
project.
It's
a
pretty
like
it's
a
pretty
daunting
project
period.
If
you've
not
worked
in
a
pretty
complex
multi-module
project
before,
like
there's
a
lot
of
stuff.
A
B
A
Oh
okay,
you
see
yeah,
okay,
I
suppose
in
that
respect,
yeah.
B
B
B
B
B
D
C
Another
question
I
mean
users
are
going
to
request
a
lot
of
different
ideas
from
us
and
we
probably
will
not
implement
the
majority
of
them.
Do
you
want
indefinitely
growing
backlog.
B
B
C
B
Well,
I
think
the
advantage
is
that
if,
if,
when
person
two
comes
along
and
wants
to
request
it
and
person
three
comes
along
and
wants
to
request
it
and
person
four
comes
along,
then
we
can
see
that
oh,
this
is
something
that
a
whole
bunch
of
people
want.
They
can
all
add
their
comments
to
that
existing
issue.
B
We
don't
have
to
open
a
new
issue
every
time
and
then
close
it
and
open
a
new
issue
every
time
and
close
it,
but
you
keep
it
open
and
then
people
can,
you
know,
add
thumbs
ups
or
comments
or
requests
more
requests,
and
if
there's
enough,
you
know
weight
on
that,
then
we
can
work
on
it.
I
mean,
for
example,
like
if
you
look
at
the
idea,
like
the
intellij
idea.
B
Backlog
like
there's
feature
requests
that
are
10
years
old
in
there
that
they're
they're
keeping
open
in
case
people
like
my
one
for
code
reviews
like
it's
now
a
big
thing,
but
I
put
that
in
I
put
that
feature
request
in
five
years
ago
or
maybe
even
eight
years
ago,
and
you
know
it
got
it
finally
got
enough
up
votes
that
they
decided
they
were
going
to
work
on
it.
So
I
don't
have
a
problem.
It
doesn't
bother
me
to
keep
a
bunch
of
open
feature,
requests
open.
B
I
mean
if
there
are
things
that
we
would,
there
could
be
things
that
we
say
no.
This
is
this
belongs
in
the
instrumentation
repo
and
those
ones
I
close,
or
I
can
move
them
over.
But
if
they're
things
that
could
be
valid,
I
mean
I'm.
I
don't
personally
have
a
problem
as
a
maintainer
having
them
sit
there.
It
doesn't.
C
C
D
B
Well,
if
it
gets
a
thumbs
down,
it
usually
gets
closed.
So,
okay,
how
about
the
most
laughs?
What
gets
the
most
laughs?
Nobody
put
any
laughs
on
anything.
So
sad,
we
do
have
things
with
thumbs
up,
though,
actually
this,
I
think,
is
already
done.
A
B
A
B
A
There's
a
java
9
plus
api's
thing,
but
that
I
don't
think
that's
the
same.
That's
a
little
different
yeah!
That's.
B
Not
module
support.
What
we
have
right
now
is
compatible
with
modules,
like
we've
been
very
careful
to
make
sure
that
every
module,
every
not
java,
9
module
and
every
gradle
module
only
has
a
unique
package
or
set
of
packages
that
it
makes
public.
D
B
I
think
is
the
core
requirement
in
order
to
support
modules.
Like
you
can't
have
you
can't
have
good
package,
I
o
open
telemetry
tracing
into
exported
by
two
different
packages.
So
so
are
there
other
things
that
we
could
do
to
facilitate
modules
using
our
things
as
java
modules?
I
don't
know
enough
about
modules.
C
We
could
have
defined
module
names.
C
B
Well,
nobody
has
asked
for
it
so
clearly,
not
not
a
major
big
issue,
there's
some
things
that
are
pretty
easy
in
here,
like
the
zip
code.
Integration
test
using
test
containers
would
be
an
easy
thing
to
write.
So
I'm
going
to
do
that.
B
B
C
B
B
C
Those
but
those
those
examples
you
don't
need
to
to
run
those
examples
against
snapshots.
I
mean,
if
you
have
examples
against
the
stable
api,
then
you
can
run
them
both
against
released
and
snapshot
versions
and
all
examples.
Examples
of
that
include
unstable
api.
You
run
only
against
released
versions,
that's
right,
but
I.
B
Think
we're
then
trying
to
use
those
examples
for
two
things
like.
I
think
the
examples
should
be.
I
think
the
things
we
call
examples
should
be
like
here
is
how
to
do
stuff
and
against
the
latest
release,
but
there's
a
different
thing
that
we
want
to
test,
which
is
which
the
examples
are
not
like.
The
examples
don't
cover
everything.
D
B
The
whole
api
surface
they're
really
just
like
hey
here's,
here's
a
recipe
for
doing
some
standard
tasks.
C
B
A
And
do
you
know
who
you
can
have
edit
the
calendar?
I
was
going
to
reach
out
to
morgan,
okay,.
B
Cool,
I
think
he
has
I
mean
I
may
have
permissions
on
that,
but
hey
it's
tyler.
I
didn't
even
see
you
here,
hey
tyler,
welcome
to
our
last
meeting
on
wednesday,
hello
yeah.
I
was
going
to
reach
out
to
morgan,
so
I'll
figure
out.
Oh
somebody
there's
somebody
at
splunk
who
will
be
able
to
remove
that
calendar
item
and
I
know
trask
has
permissions
to
edit
the
the
instrumentation
ones.
So
he
can
change
the
description
or
whatever
cool.
B
As
you
respond
to
saying,
go
forth
and
be
productive.