►
From YouTube: 2020-09-29 .NET SIG
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
A
B
B
A
A
A
A
I
do
not
have
any
other
topic,
so,
okay,
any
questions
anything
which
require
like
broader
discussion,
it's
time
to
bring
it
now,
otherwise
I'll
just
go
into
logger.
B
I
wonder
what
this
issue
is
about.
I
I
understand
I
haven't
had
a
chance
to
look
at
it.
There
is
an
issue
on
dotnet
design
from
craig
and
noah
and.
A
Yes,
I
mean
I
did
look
at
it,
but
I
didn't
have
a
chance
to
really
look
through
it.
It
seems
like
a
long
discussion
should
be
possible
to
bring
it.
A
B
It
I'm
just
curious
if
anybody
has
something
to
tell
during
the
in-person
meeting,
but
if
not,
let's
just
discuss
it
in
the
issue.
A
Yeah,
I
think
I
mean
it's
fairly
long.
I
lost
track
of
it
after
the
initial
two
things
so
yeah
I
mean
it
sounds
like
there
is
a
need
to
I
mean
craig
is
proposing.
There
is
a
need
to
let
people
supply
or
provide
the
activity
id
instead
of
letting
the
framework,
and
that
was
the
last
conversation
I
read,
and
there
is
also
an
issue
about
like
baggage
being
missed,
but
it's
already
replayed
why
it
is
missing.
So
don't
think
we
need
to
discuss
anything
on
today's
meeting
but
yeah.
A
I
encourage
everyone
to
have
a
look
at
it,
because
these
are.
This
may
have
some
implications,
and
this
is
also
a
good
time
to
take
part
is
part
in
the
next
release.
Dotnet
six.
A
So
if
there
are
like
missing
features,
we
want
to
add
like
now
is
the
right
time
to
engage
in
the
discussion
so
but
from
that
yeah.
I
don't
have
anything
to
talk
about
this.
I
think
there
was
an
ask
from
aws
first
about
allowing
inducer
to
specify
or
own
the
id
generation
and
it
they
walked
around
using
a
forget,
like
there's,
a
workaround
which
was
submitted
here.
Yeah
use
a
trace,
eddie
generator
if
they
have
some
interest
in
making
activity
expose
it
in
apa.
A
Then
this
is
the
right
place
to
talk
about
that,
because
in
one
of
these
issues
greg
is
talking
about
that.
So
I
mean
you
need
to
figure
out
which
one
that
is
all
right
yeah,
I
don't
have
any
other
updates.
So
I
will
just
quickly
give
an
overview
of
what's
going
to
happen
this
week
and
next
week
in
terms
of
login
integration.
A
So
we
already
have
like
few
codes
already
merged
last
week
about
logging,
so
just
to
give
a
real
background
for
logging.
There
is
no
api
being
introduced
by
open
telemetry,
open
telemetry
is
taking
a
approach
where
the
recommendation
is
to
use
whatever
apa,
which
is
already
available
in
the
language
and
integrate
it
with
open,
telemetry
and
also
produce
or
provide
an
ability
to
stamp
trace
id
and
span
id
like
everything
from
spam
context
into
the
logs.
A
That's
pretty
much
the
only
requirement
from
open
telemetry
specification
for
logs,
because
of
that
it
should
be
like
fairly
straightforward,
as
opposed
to
like
traces
and
metrics.
There
is
no
new
api
to
implement,
so
we
have
some
headstart
already,
like
riley
did
some
initial
prs,
where
we
are
doing
a
I
logger
provider
and
the
part
2
is
just
out.
A
A
So
you
will
have
like
low
processor
log,
exporter
and
logo
code,
which
represents
actual
log
itself,
and
things
like
that
and
like
vendors
should
be
able
to
write
a
log
exporter
just
like
they
have
trace
exporter,
and
we
are
trying
to
figure
out
whether
we
can
do
like
a
couple
of
built-in
ones,
like
I'm
still
exploring
whether
jaeger
and
zipkin
supports
it.
If
not,
we
can
do
something
like
elasticsearch
exporter,
but
either
way
we'll
still
have
an
otlp
exporter,
because
you
know
tlp.
The
protocol
is
already
defined
how
to
export
google
core.
A
So
that's
the
only
update
I
have
for
this
week
and
I
hope
that
this
should
be
ready
between
this.
Between
now
and
next
week,
we
should
have
it
working
end-to-end,
it's
already
working,
but
we're
just
finding
out
like
final
details
on
it.
A
So
if
there
are
questions
on
this,
we
can
take
it
now.
Otherwise,
yeah
I
don't
have
any
other
agenda.
I
think
this
is
pretty
much
the
only
thing
which
myself
and
really
working
on
this
week.
A
B
Was
looking
at
the
spec
matrix
capability
matrix
and
I
like,
for
instance,
there
is
a
resources
capabilities
and
we
didn't
mark
any
of
them
as
plus
either.
C
B
We
clearly
support
them.
So
if
we
scroll
to
different
table-
and
I
was
wondering
like
I
remember-
you
was
working
situated-
documented
mapping-
capabilities
of
open
apis
of
open
telemetry
to
api,
so
of
activity,
did
you
publish
it
or
it's
still
in
google
doc,
yeah.
A
A
A
Things-
and
I
mean
I
did
not
explain
the
difference
because
things
looked
fairly
self-explanatory.
That's
why
I
did
not
add
like
more
explanation,
but
I
think
I
can
like
expand
this
document,
because
there
will
be
some
document
in
the
dot
net
side
as
well,
which
explains
the
usage
of
activities
of
source.
They
currently
have
diagnostic
source
usage
and
activity
usage,
but
there
is
no
doc
yet
about
activity
source.
B
A
I
mean
what
was
the
okay,
so
resources
separated
resources
like
completely
different
from
these
two
yeah.
B
A
Yeah
I'll
be
checking
it
like
what
what
is
our
compliant
status
again
after
this
week,
when
I'm
done
with
some
logging
work,
yeah.
Okay,
yeah,
that
I
can.
B
Getting
closer
to
ga-
and
I
think
there
are
very
few
pga
issues-
will
be
more
some
specifications
soon
and
it's
a
good
timing
to
revisit
and
reiterate
on
this
matrix.
A
I
mean
it
should
be
like,
like
the
specs
is
expected
to
freeze
sometime
this
week
right.
A
A
Yeah
yeah
I'm
out
of
topic.
If
anyone
wants
to
discuss
anything,
we
can
use
this
time.
Otherwise
we
can
quickly
in
the
meeting.
A
C
So
for
the
auto
instrumentation
we
are
still
working
on
the
infrastructure,
initially
to
kind
of
load
that
the
active
source
diagnostic
source.
So
we
made
some
progress,
but
we
are
still
kind
of
work
on
whole
foundations.
Yet.
A
C
So
we
didn't
cetera
100
on
that,
but
the
idea
is
that
some
builds
are
gonna
depend
on
on
that,
but
there
is
a
concern
from
greg's
side
about
kind
of
not
depending
on
the
open
telemetry.net.
C
A
I
see
yeah
I
mean
greg
was
mentioning
some
time
back
that
there
is
a
way
to
I
mean
without
taking
a
binary
dependency,
there
is
a
way
to
like
get
the
source
code
directly
copied
into
the
auto
instrumentation
and
rebuild
and
recompile
there
yeah.
That's
why
I
was
curious.
Like
was
there
any
progress
on
that
side?
I
mean
I'm
not
blocked
or
anything.
I'm
just
curious
and
intense
asked.
C
Yeah
yeah,
one
thing
that
I
suggested
to
him:
perhaps
we
should
consider,
is
a
new
gap
source,
but
that
I
I
mean
publishing
as
a
nougat
source,
so
you
can
build
everything
there,
but
that
it's
something
that
we
can
design
in
a
little
bit.
Okay
got
it.
A
Yeah
all
right,
I
don't
have
any
other
topic,
so
see
you
all
next
week
I
mean
the
only
thing
which
I
expect
to
complete
next
week
is
the
logging,
but
if
there
is
any
other
issues
which
require
more
urgent
attention,
please
message
in
jitter,
so
we
can
take
a
look
at
that.
A
Oh
one,
one
final
thing,
while
you
say
so,
can
you
like
remind
us
what
was
the
policy
for
putting
a
vendor-specific
context
propagator
in
the
main
repo,
because
there
was
a
x-ray
propagator,
and
I
reflect
that
morgan
in
one
of
the
specifications
mentioned
that
anything
related
to
trace
id
generation
and
propagation
can
be
in
the
main
repo
itself.
But
then
there
is
a
conflicting
statement
in
the
specification
that
it
should
go
somewhere
else.
Do.
A
Any
like
any
status
change
or
anything
on
that.
B
A
B
It's
like
it
brings
like
entire
work
with
it.
So
if
it's
contained
and
can
really
can
live
for
inside
the
main
sequence,
it
should
be.
A
Okay,
so
this
is
the
statement
which
I'm
referring
about
like
this
says,
like
propagators,
should
be
allowed
in
the
main
api
hdk
repo,
and
the
contradicting
statement
is
right
here
I'll,
send
you
the
these
two
links,
but
it
says
this
is
from
propagated
page.
It
says
vendor
specific
propagators
should
be
encrypted
to
be
maintained
and
distributed
by
their
respective
ones.
B
A
Yeah
yeah
I'll
send
these
two
to
you,
so
we
can
like
come
up
with
like
what
is
the
final
recommendation
and
that
would
determine
whether
we
want
to
merge
it
here
or
we
want
to
put
it
somewhere
else.
B
Yeah,
I
think
it's
just
nobody
care
to
update
it,
but
yeah
I
will.
I
will
take
care
of
it.
Thank
you.