►
From YouTube: 2021-03-10 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
A
Let's
see
if
we
get
more
or
the
same
number
of
attendees
as
last.
A
C
C
Isn't
it
at
the
same
time
as
the
other
one?
Is
it
the
instrumentation
one's
at
nine,
so
half
an
hour
earlier,
okay,.
A
Trask
is
a
better
leader
than
I
am
that's
all
it
is
it's
clearly
a
leadership,
failure
and
leadership.
A
B
C
A
A
A
I
don't
know
I
should
open
up
the
the
meeting
notes
from
the
the
specs
say.
The
maintainer's
thing,
but
it's
mostly
just
until
metrics,
is
ready.
A
lot
of
quality
of
life.
A
A
A
A
D
A
C
A
Let
me
I
can
tell
you
what
I'm
planning
to
do
today
after
I'm
done
kind
of
reviewing
open
pr's,
I'm
going
to
attempt
to
write
some
meta
documentation,
so
basically
something
I
want
to
put
at
the
top
of
the
readme
in
both
this
repo
and
the
instrumentation
repo
and
probably
the
whatever
the
contributory
vote.
A
A
And
so
I
want
to
just
write
a
little
like
hey,
who?
What
are
you
interested
in
if
you're
interested
in
a
you
know
super
simple,
auto
instrumentation
project
with
the
java
agent
go
here
if
you're
interested
in
learning
about
how
to
write
instrumentation
go
here
if
you're
interested
in
learning
how
to
configure
the
sdk
locally
go
here
like
just
kind
of
a
meta,
a
meta
thing
that
we
can
put
everywhere,
so
that
and
I'd
like
to
pin
it
in
like
the
cncf
slack
channels
as
well,
so
that
we
can
just
say:
hey
figure
out.
A
The
other
thing
I
would
note
since
nikita
you're,
a
maintainer
of
inflammatory
java
instrumentation.
Maybe
you
can
address
this
or
kick
somebody
to
address
it.
So
if,
let's
say
I
land
here
and
I
want
to
know
how
to
configure
the
agent,
where
do
I
go
well
I'll
start
scrolling?
Hey
configuring,
the
agent.
That
seems
like
a
good
thing,
I'm
going
to
click
that
the
agent
is
highly
configurable,
all
right,
I'll
click
that
configuration
parameters.
This
is
by
the
way
how
many
clicks
have
I
done
now.
A
A
A
Reason
it
sends
me
into
a
really
weird
place
in
this
document
like
the
sampler
documentation.
It's
we
need
to
fix
this
so
yeah.
This
is
it's
really
bad,
like
it's
really
hard
like,
I
had
a
hard
time
figuring
out
how
to
get
to
agent
configuration
documentation
myself
and
I
helped
write
a
lot
of
it.
So
I
mean
I
see
here,
click
here
to
see
the
detailed
list,
except
that
it
isn't.
B
Like
this,
this
got
made
worse,
so
everything
everything
used
to
just
be
there
in
line
right.
It
used
to
be
one
huge,
read
me
and
I
did
some
work
about
pulling
sections
out.
So
it
wasn't
just
this
wall
of
text
when
you
came
into
the
repo
and
all
of
the
configuration
was
like
in
configuration.md
or
whatever,
which
is
where
that
links
too
yeah.
B
So
everything
that
used
to
be
in
the
readme
wasn't
here
and
then
I
think
there
was
a
discussion
that
I
think
I
was
I
didn't
I
wasn't
around
for,
but
I
think
the
discussion
went
yeah.
A
bunch
of
this
configuration
stuff
is
now
auto
configuration
that
lives
in
the
other
repo.
It
shouldn't
be
maintained
over
here,
and
so
I
think
that's
why
it
got
pulled
out
into
that
dock
link
or
that
config
link
or
whatever
right.
A
Yeah
like
this
is
weird
that
this
is
here
like
in
between
db
statement,
sanitization
and
suppressing
specific,
auto
instrumentation,
which
is
again
another
link
like
it
feels
like
it's
just
things
are
really
fractured,
as
you
said
right
now,
and
I
think
that
maybe
this
link
should
not
just
jump
into
this
document.
This
link
should
go
to
the
actual
documentation
for
like
where
this
is
supposed
to
be,
except
that
this
thing
doesn't
mean
anything
you
should
just
go
here.
B
Yeah-
and
I
was
torn
kind
of
on
that
too,
like
I
thought,
I
think
when
the
readme
is
of
a
certain
size,
it's
important
to
have
a
table
of
contents
yeah
that
links
down
into
the
sections
you
care
about,
but
I
was
also
hesitant
to
completely
remove
the
little
section
that
says
like
config,
so
I
put
some
words
in
there,
but
they're
not
very
helpful,
and
they
really
just
point
to
the
real
thing
well,
but
they
don't
actually
go
into
the
real
thing
because
they
used.
A
D
D
B
I
mean,
I
think
what
that'll
involve,
though,
is
bringing
some
of
that
back
out
of
hotel
java
back
into
instrumentation.
A
Yeah,
I
think,
yeah,
that's
I'm
not
shy
hundred
percent
sure
about
that.
I
think
what
we
can
do
is
make
this
block
not
have
this
link
be
so
microscopic
and
hidden
like
I.
I
think
that
we
could
probably
like
what
I
would.
What
I
think
would
be
super
useful
here
actually
is
rather
than
just
having
this
read.
A
The
docs
is
actually
have
a
little
like
the
table
of
contents
for
this
document
linked
to
in
in
this
little
block
here,
like
configuring,
this
export
configuring,
this
exporter,
blah
blah
blah
and
just
have
a
whole
set
of
links
there
that
link
into
the
anchors
in
those
auto
instruments
auto
configure
docs.
I
think
that
would
be.
D
That
again
may
break
if
you
change
your
documentation,
absolutely
what,
but
what
I
think
this
document
is
really
missing
is
like
a
little
bit
description
about
like
we
have
several
different
types
of
configuration.
Sdk
configuration
is
once
agent-specific
configuration
is
another
spi
is
the
third
and
enable
disabling
or
instrumentation
specific
configuration
is
yet
another.
D
B
D
D
Okay,
but
then
another
thought
is
that
we
still
can
have
like
problem
oriented
the
goal,
oriented
documentation
here
yeah,
and
we
can
have
an
exhaustive
documentation
of
everything
they
can
be
just
two
separate
things
and
so
that
goal-oriented
sections
of
control
or
documentation.
That
probably,
is
a
very
great
good
idea.
Indeed,.
A
Does
markdown
have
the
ability
to
embed
pieces
of
other
documents
within
it?
I
don't
think
so.
No
that
sucks
like
this
is
probably
why
other
projects
don't
just
use
plain,
jane
markdown
for
their
documentation
like
to
use
a
doc
and
things
that
are
more
powerful
yeah
anyway.
I
want
to
take
a
run
at
at
least
writing
the
goal,
driven
like
pointers
that
we
can
put
in,
and
then
it
would
be
great.
B
A
B
A
B
D
But
you
have
a
section
if
you
scroll
to
the
scroll
to
your
yeah
yeah
this
one.
This.
A
A
A
It
might
actually
be
like
I
might
take
a
run
in
doing
at
least
this
part
table
of
content.
Defying
this
part
first,
before
doing
my
goal,
driven
or
user
persona
driven-
I
don't
know
both.
Those
things
are
important.
A
Yeah,
that's
my
problem.
Hey!
You
know,
what's
really
good
on
ice
cream
by
the
way,
if
you
have
vanilla
ice
cream,
I
recommend
putting
some
hazelnut
liqueur
on
your
vanilla
ice
cream.
D
I
haven't
tried
yet,
but
on
my
to-do
list
is
pedro
jimenez
on
vanilla
ice
cream.
Oh.
A
A
Well,
if
you
want
to
retire
from
software,
I
have
a
business
idea
for
you.
D
We
do
have
birch
sap
industry
here,
yeah.
A
So
this
is
actually
that's
super
interesting.
I
just
got
some.
I
ordered
I
have
this,
this
wine
and
food
importer
that
I
order
stuff
from
and
he
imported
some
birch
sap
water,
birch
water
from
finland,
which
I
assume
is
the
same
thing
that
you
all
have
there
yeah
yep
there
were
three
flavors.
There
was
a
mint.
There
was
a
plane
which
the
plane
just
tasted
like
water.
It
had
no
flavor
little
bit.
A
A
Not
very
much
plain
mint
and
then
what
was
the
other
one?
I
don't
remember
anyway,
it
was
interesting.
It
was
a
good
experiment.
It
was
definitely
way
too
much
money
for
what
I
got.
D
A
Bet
but
it
was
yeah,
it's
definitely
fun
to
try
something.
I've
never
had
before
jason
we're
talking
about
this
birch
birch
water
that
they
make
in
finland
and
estonia.
Basically,
it's
birch
sap,
like
they
use
birch
sap
like
we
would
maple
sap
sort
of,
except
it's
not
nearly
as
sweet
as
maple
syrup.
A
D
A
A
A
Monologue
opened
this
issue
of
stabilizing
service
name.
Currently,
all
attributes
are
experimental,
but
anyway,
service
name
is
fairly
important.
Yeah
anyway,
I
don't
think
there's
anything
to
do
there.
Here's
an
interesting
one
that
it's
worth
you
know
your
opinion
is
valuable
on
this
one,
so
semantic
attributes
you
may
be
familiar
with
them.
You
may
not
they're
generated
from
the
ammo
that
are
using
the
specification.
A
A
A
Like
os
there's
all
sorts
of
os's,
we
might
want
to
tag
right,
so
custom
values
are
fine,
but
there's
some
that
it's
false.
A
A
A
A
Where
I
guess
these
are
the
only
net
transport
values
that
are
allowed,
okay
cannot
invent
anything
new,
that's
a
bummer,
except
for
others
exactly
so
anyway.
Monrog's
issue
is
how
come.
Sometimes
we
have
public
static,
final
class
with
a
bunch
of
strings
in
it
and
otherwise
other
times
we
have
enums,
which
is.
B
B
A
Like
I
don't
even
know
when
these
things
like,
why
do
we
have
these
here
they're,
just
like
a
convenience
for
people
who
want
to
like
there
must
be
a
place
where
you're
supposed
to
stick
a
neck
transport
value,
but
we
don't
really
have
any
way
to
do
that.
Specifically,
you
have
to
pull
the
string
value
out
of
it
to
use
it,
but.
B
A
B
A
Here's
architecture
like
I
wonder
why-
and
this
is
actually
maybe
even
more
a
question
for
the
spec
like
why
in
some
cases
do
we
allow
custom
or
other
and
other
ones
we
just
say:
custom
value
is
true.
I'm.
B
B
A
A
What
is
this?
No,
that's
just
a
description
of
it
mill
mill
the
mill
right.
B
B
A
B
D
B
I
think,
if
it
were
up
to
me,
I
would
define
all
of
the
ones
that
we
know
and
leave
it
wide
open
for
extension,
all
of
it,
but
that's
also
why
I'm
not
writing
the
spec
committee,
but
you
could
be
so.
You
would
basically.
B
A
B
Anyway,
where,
where
is
the
code
that
does
that
generation
can
show
you.
A
So
if
I
go
to
open
function,
java
build
scripts
semantic
convention
templates,
there's
a
ginger
template.
A
B
A
E
C
A
B
A
So
when
you
call
export
and
you
follow
flush
when
you
call
shutdown
all
those
things
return,
complete
will
result,
so
you
can
async,
so
you
can
do
it,
implement
it
as
async
and
respond
to
it
as
if
it
were
async
as
desired.
Yeah,
complicated,
very
complicated,
and
in
fact
he
comments
here.
Completable
future
has
a
cancel
method,
but
it
doesn't
actually
signal
anything
to
the
thing
that's
cancelling.
B
A
A
A
B
B
E
E
A
A
A
B
A
You
can
read
his
essay
that
he
has
written
here.
Okay,.
B
A
B
A
B
I
mean
I
guess
that
that
raises
the
question
of
whether
or
not
doing
things
that
are
outside
of
the
spec
does
that
violate
the
spec.
Like
is
the
spec
intended
to
be
comprehensive,
and
I
think
the
answer
is
definitely
not.
B
A
Yeah
move
validation
methods
to
the
public
api,
so
he
yeah
he
needs
to
add
his
own
validation.
Oh
then
wrap
it
and
add
it
anyway.
All
right.