►
From YouTube: 2021-10-26 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
Yeah,
it's
two
minutes
past
four.
I
think
we
can
go
ahead
and
get
started.
So
it
looks
like
we
have
a
couple
of
items
in
the
agenda:
okay,
scrubbing
off
sensitivity,
viewer.
A
Okay,
I
don't
know
who
put
that
in
the
agenda,
so
maybe
I'd
like
to
like
find
out
what
is
the
specific
ask?
It
looks
like
a
very
general
thing,
so
it
might
be
worth
doing
it
in
the
specification
itself.
Okay
stack
traces,
yeah,
oh
okay,
yeah!
These
are
all
like
coming
directly
from
the
specs,
so
I
think
this
should
be
better
served
by
opening
an
issue
in
the
specification
rather
than
inventing
something.for.net
alone
I'll,
see
if
debug
or
or
open
the
other
one
is
here.
A
Let's
come
back.
If
anyone
has
anything
we'll
talk
about
it
left
later,
I
just
have
like
a
few
quick
updates.
Let
me
go
from
the
backwards,
so
I
think
most
of
the
folks
here
are
eligible
for
voting
in
the
open,
telemetry
governance
committee
election.
So
if
you
haven't
done
that,
please
do
so.
There
is
like
less
than
one
day
left
for
the
voting.
So
look
at
this
link,
which
will
take
you
to
the
slack
chat,
which
contains
a
link
to
the
actual
voting
itself.
A
I
forget.
I
don't
know
why
it's
not
showing
us
a
hyperlink,
but
anyway
you
can
find
it
from
the
chat
or
it's
already
in
the
open,
elementary
slack
channel
as
well.
A
A
There
wouldn't
be
anything
like
really
needed
for
net
six,
because
dotnet
six
is
not
expected
to
have
any
breaking
changes,
so
we
should
just
work
as,
but
the
task
is
mostly
to
confirm
that
we
do
it
throughout
testing
to
make
sure
nothing
is
broken
and
like
we
already
have
issues
assigned,
so
it
should
be
taken
care
of
it's
mostly
about
like
adding.6
to
the
cas,
and
the
second
thing
is
the
metric
signal:
that's
the
entire
focus
of
most
mods.
Sorry,
I
think
I
can
hear
someone.
A
Is
there
a
question
yeah?
I
just
knew
myself:
oh
okay,
no
problem
yeah!
So
for
this
to
happen,
there
are
two
external
dependencies.
One
is
the
stable
release
of
the
diagnostic
source
itself.
That's
where
the
api
is
coming
from
so
as
of
today,
I
don't
see
any
risk
to
that.
It's
going
to
happen
on
number
nine,
as
per
the
original
schedule,
so
dotnet
would
be
releasing
the
stable
release
like
in
the
next
two
weeks.
The
second
requirement
is,
we
need
the
spec
on
which
this
is
built
should
be
marked
as
stable.
A
So
as
of
today,
it's
marked
as
going
to
be
ready
by
the
end
of
this
week,
but
based
on
the
spec
updates
aspect
meetings
this
morning.
It
would
only
be
reaching
feature
freeze
on
this
week,
which
means
end
of
october,
and
the
spec
would
reach
stable
once
at
least
three
languages
would
reach
a
stable
version
of
the
metric
sdk
and
one
of
them
is
dotnet
and
others
are
java,
go
and
python.
So
it's
quite
likely
that
this
date
for
marking
the
specification
of
stable
would
be
moved
to
a
later
date.
A
I
don't
know
exactly
what
that
date
would
be,
but
based
on
my
estimate,
they're
targeting
end
of
november,
so
which
means
the
1.2
release
would
be
blocked
until
we
reach
that
stage.
So
correspondingly,
I
have
created
like
two
rc
milestones.
A
So,
basically,
when
we
do
rc,
we
kind
of
be
feature
complete
and
there
would
be
no
breaking
changes
unless
there
is
like
something
like
some
p0
like
really
really
broken
things,
so
we
wouldn't
be
planning
any
breaking
changes
after
rc1.
So
I
did
not
put
the
dates
because
I
want
to
go
backwards
from
this
state,
so
I
expect
to
get
this
date
from
the
stack
sometime
soon
and
based
on
that
we
will
work
backwards
and
feature
wise.
A
A
So,
just
if
you
look
for
all
the
issues
which
are
targeting
or
which
I
have
the
tag
matrix
in
it
and
the
tag
required
for
js,
I'm
using
the
required
for
g
attack
from
tracing,
because
this
is
the
first
time
we
are
releasing
metrics,
so
I'm
just
reusing
anything
related
to
matrix,
which
we
need
for
1.2
us
release
required
for
ga.
So
there
are
a
lot
of
things
which
are
like
next
to
how
not
really
required
so
I
removed
them.
A
So
this
is
the
finalist
thing
there
might
be
like
three
or
four
other
relatively
small
issues
as
well.
So
this.
B
A
Final
list
of
things
which
we
are
after
before
we
can
do
the
102
and
of
that
there
are
like
few,
which
are
like
really
non
non-trivial
data,
so
that
would
be
like
the
metric
view,
which
is
from
a
feature
perspective.
We
are
like
about
eight
seventy
percent
and
we
still
have
two
more
things
to
do,
and
then
the
ability
to
clean
up
metric
points
if
it's
not
used
so
alan
has
apr
on
it.
A
But
those
two
are
the
like:
somewhat
bigger
items,
and
then
there
are
like
relatively
smaller
items
like,
even
though
like
supporting
metal
traders,
multiple
of
them
are
like
important
feature.
They
are
like
relatively
self-contained
change,
so
we
should
be
able
to
handle
that
without
touching
the
overall
sdk
so
and
we
just
updated
the
spec
compliance
metrics.
A
Let
me
see
if
I
have
the
pr
for
that
yeah.
So
this
is
a
specification
compliance
matrix
where
we
are
basically
like
putting
check
marks
against
what
are
the
features
which
are
implemented
in
dot
net
and
what
are
the
things
which
we
don't
have,
so
I
did
an
initial
version
of
it.
A
So
there
are
quite
few
of
them
which
are
negative
like
minus,
but
those
are
things
which
we
expect
to
remain
negative
forever,
because
these
are
things
which
are
coming
directly
from
dotnet,
so
so
for
now
we'll
just
like
mark
it
as
negative,
but
later
we'll
put
a
like
asterisk
or
something
to
indicate
like
why
it
is
negative
or
like
put
it
as
positive
and
then
put
an
explanation
saying
why
it
is
the
way
because
in
dot
net
a
lot
of
things
are
coming
directly
from
runtime.
A
So
we
may
not
have
the
exact
feature
parity.
So
that's
pretty
much
all
the
updates
so
should
be
like
done
with,
like
all
the
pending
issues,
which
we
need.
So
if
you
know
of
any
issues
which
are
like
required,
but
it's
not
right
here,
please
do
let
me
know
I
can
tag
it
accordingly.
A
So
this
is
the
list
of
issues
with
matrix
and
marcus
record
4g.
So
if
you
just
look
at
all
the
issues
with
metrics,
we
have
maybe
like
slightly
more
than
that,
so
once
we
filter
it
using
required
for
ga,
then
we'll
get
like
slightly
lesser.
A
So
you
can
see
like
anything
which
requires
instrumentation,
like
those
are
like
our
not
required
for
sdk
to
stable
stability,
so
they
are
important
but
not
blocking
the
gear
release.
So
that's
all
that's
an
update
from
me.
So
if
we
have
any
new
questions
we
can
take
it.
So
I
see
a
new
person
christopher.
A
I
don't
recognize
seeing
you
before.
So
do
you
want
to
just
say
hello
to
the
rest
of
the
folks
here.
B
Hi,
yes,
I
am
new
to
the
call
I've
been
in
the
slack
channel
for
about
a
month
now,
our
team
at
I
work
for
walters
kluwer
and
our
team.
There
has
been
working
on
implementing
opentelemetry.net
in
our
application
and
we're
we're
hoping
to
to
have
a
production
release
and
stuff
this
coming
december
with
our
kind
of
our
first
foray
into
it.
So
I'm
just.
A
B
Lurking
to
see
you
know
the
overall
governance
of
opentelemetry.net
and
just
see
how
how
it
is
working
on
the
back
end.
B
I
mean
overall,
our
intent
is
to
adopt
the
whole
of
you
know
the
open
telemetry
specification,
but
obviously
right
logs
and
metrics
are
you
know
what
metrics
are
not
quite
at
ga,
as
you
pointed
out
earlier,
and
logs
are
coming
up
behind
that
right.
But
you
know
our
first
release
is
definitely
just
going
to
be
with
with
traces.
A
If
you
can
like
put
your
name
in
that
in
this
list,
that
would
be
great.
You
may,
if
you
have
no
objection,
you
can
put
your
company
name
as
well.
A
To
open
elementary.net
community
so
that
ends
the
agenda,
so
I
don't
have
anyone
to
talk
about
the
scrubbing
of
sensitive
things
from
asp.net
core
and
other,
like
other
instrumentation
libraries,
but
I
suppose
it's
important,
but
we'll
come
back
to
it.
If
there
is
a
stronger
ask,
since
we
are
like
mostly
focusing
on
matrix-
and
this
is
I
mean
it
might
defect
matrix,
but
this
is
specifically
asking
about
stack,
tracers
and
other
things
which
are
only
for
instrumentation
libraries,
which
are
emitting
traces
or
log.
So
let's
come
back
to
it.
A
If
there
is
a
need
for
now
I'll
just
keep
it
like
that,
and
I
know
like
the
debug
works
in
microsoft,
so
I
might
be
able
to
learn
a
little
bit
more
from
him
and
update
the
community
accordingly.
A
Are
there
any
questions
to
be
discussed?
Otherwise
we
can
end
early
and
meet
again
next
week.
A
Okay,
no
question
so:
okay
again
and
early
and
meet
you
all
next
week.
Thank
you.