►
From YouTube: 2021-04-06 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).
A
A
B
B
B
B
C
Hello,
so
hi,
I'm
you
here
so
basically,
I'm
joined
playing
like
on
february
and
right
now,
I'm
mostly
working
on
the
net
auto
instrumentation
code
base.
However,
I
start
to
feel
that
it
will
be
good
if
I
even
start
to
contribute
here
as
well
as
look
around
here,
because
we
try
to
reuse
some
stuff
from
here
and
I
also
wanted
to
just
know,
what's
going
on,
etc.
C
B
C
B
B
Okay,
personally,
I
use
vs
and
windows,
but
I
think,
like
someone
else,
was
using
vs
code,
like
we
only
have
like
few
folks
today.
So
if
anyone
else
is
using
non-windows,
please
speak
up
now.
A
Yeah
I
use
mac
os
okay
times
and
I
use
ps
code
but
yeah.
It's
sometimes
not
the
best
experience
for
some
things.
B
And
I
I
was
just
asking
like
like
I
saw
someone
raising
an
issue
in
like
slack.
I
think
I
assumed
that
that
was
you
about
vs
code,
sure.
A
Or
like
anyone
else,
so
I
haven't
caught
up
with
the
the
conversation
in
slack,
though
the
main
issue
that's
I've
encountered
with
vs
code
is
that
it
does
not
handle
preprocessor
directives
that
well
so
like
in
visual
studio.
You
know
how
that
you
have
that
ability
to
say.
Like
you
know,
I
wanna,
I
wanna
view
the
code
as
though
it
were
the
say,
the
net
standard,
two
one
compilation
of
everything
there
there
to
my
knowledge,
is
no
such
thing
in
vs
good,
so
it
has
some.
A
C
C
B
Yeah
and
if
there
are
like
issues
which
are
like
fixable
in
the
code,
like
some
warnings
yeah,
we
can
definitely
do
the
fix
if
you
want
to
submit
a
pr
like
if
you
find
what
the
actual
issue
is
go
for
it,
but
otherwise
we
can
help
there
as
well.
C
I
do
have
so
you
do
not
have
any.
B
C
Code
or
a
dev
container
folder
here
and
as
well,
it's
not
in
ignore
list.
So
right
when
I
created
the
dev
container
on
you
know
to
work
on
in
development
container.
You
know
it
pop-ups
in
my
git
status
that
I
should
add
them.
So
I
see
two
possibilities
or
I
add
them
to
git
ignore
or
maybe
you
should
start
checking
this
default
configuration
in.
So
if
you
look
at
the
open,
telemetry.net
instrumentation
repository,
you
have
a
second.
C
Instrumentation
correct,
so
we
have
simply
added
something
like
yeah.
This
dot
example
for
both
folders
just
to
be
sure
that
if
someone
wants
to
alter
it
somehow,
then
we
thought
that
it
would
be
safer.
Just
to
give
these
examples
and
in
the
contribution
md,
we
just
pointed
that
if
someone
wants
to
develop
in
vs
code,
one
can
simply
copy
paste
using
cp
or
whatever
if
they
want
to
use
that,
and
these
two
folders
are
in
ignore
in
get
ignore.
B
I
see
so,
how
is
it
going
to
help
like?
Is
it
because,
like
I
mean
I'm,
not
a
vs
code
user,
so
I
probably
won't
understand
the
whole
thing.
Is
it
just
to
make
the
life
easier
for
folks
who
are
using
vs
code.
B
Okay,
yeah,
I
mean
it's
a
reasonable
because
we
right
now
make
the
life
of
people
using
visual
studio
easier
by
having
the
actual
solution
fire
so
yeah.
I
don't
think
it
should
be
an
issue
to
have
vs
code
specific.
C
So
the
alternative
is
just
to
put
this
dot
def
container
and
dot
vs
code
folders
just
into
git
ignore.
So
if
someone
uses
this,
you
know
folders
at
least
he'll
have
clean
git,
git
status
on
this
environment.
I.
B
Think,
okay
yeah,
I
mean
that
would
be
like
very
easy
thing
to
start
like.
Let's
see
who
are
using
their
own
code,
use
it
and
not
pollute
the
actual
git
yeah
yeah
I
mean,
if
you
can
submit
it
here,
yeah.
We
can
definitely
take
it
in
as
to
the
actual,
like
checking
in
the
like
these
examples.
I
I'm
not
yet
sure,
because
I
I
am
yet
to
see
the
actual
value
but
like
if
it
is
something
which
is
useful
for
like
anyone
in
general
yeah.
B
Yeah
is
there
anything
else
like
which
you
are
looking
to
contribute
or
you're,
just
like
browsing
around
like
trying
to
get
a
feel
of
things.
C
C
B
C
C
C
B
Let's
look
at
that
actually,
so
you
are
looking
at
http
instrument.
C
C
B
Yep
definitely
yeah.
I
don't
know
like
I
thought,
like
the
discovery
is
fairly
good
for
instrumentation.http.
B
But
if
you
do
see
like
like
gaps
either
there
is
an
issue
or
if
you
are
up
for
it
like
do
the
pr
itself.
B
Utkash
was
working
on
like
some
of
the
code
coverage
like
he
definitely
had
a
lot
of
tests
in
the
last
couple
of
weeks,
but
I
think
it
was
mostly
restricted
to
instrumentation
dot
esp
net
core,
not
necessarily
http
one
yeah
yeah,
but
definitely
like.
If
you
see
like
gaps
yeah,
we
are
happy
to
take
it
in
yeah,
and
you
probably
already
noticed
like
this
is
covering
both
http
client
in
the
dot
net
code
and
the
framework
one.
So
it
may
be
like
tested
differently
yeah.
B
It
already
has
the
net
fx
at
the
end
of
the
file
name
yeah,
I
send
it
to
you,
go
for
it
and
yeah
I
mean
you
can
reach
out
to
us
and
it's
like.
We
should
be
able
to
help.
B
Okay,
if
there
are
no
other
topics,
I
I
mean
I
don't
have.
I
mean
I
wasn't
working
actively
on
this
repo
for
one
week
and
I
wouldn't
be
working
this
week
because
I'm
on
calling
my
primary
work
life
so
I'll
be
like
getting
back
to
open
pr's
early
next
week
or
if
there
is
any
pr
which
requires
immediate
attention
or
you're
just
like
waiting
to
get
some
approval.
B
Just
mention
me
either
in
the
pr
itself
or
in
the
slack.
So
I
can
take
a
look
at
it
quicker
rather
than
waiting
for
next
week
and
as
I
mentioned
like
the
week
before,
we
don't
have
an
etf
or
when
would
the
actual
1.1
would
be
released?
It's
still
pending.
We
want
to
release
it
when
instrumentations
are
ready
and
there
is
no
commitment
yet
from
the
specification
when
good
instrumentations
be
allowed
for
ga
I
mean
one
auto,
so
I'm
just
keeping
it
as
april
23
for
the
next
beta.
B
So
any
changes
which
we
are
pending
would
be
part
of
this
release
and
as
we
get
closer
to,
I
mean
as
soon
as
I
get
a
good
estimate
on.
When
can
we
do
like
actual
1.0
I'll,
create
a
milestone
and
put
the
actual
date
here?
B
B
So
just
a
heads
up,
but
it's
not
going
to
happen
this
week
or
next
week,
it's
quite
likely
in
the
third
week
of
maybe
towards
end
of
april
is
when
it's
going
to
happen,
yeah
that
I
said
I
do
not
have
any
updates.
If
there
are
any
open
questions,
we
can
take
it
now.
Otherwise
we
can
meet
again
next
time.
B
Okay,
no
other
questions,
so
thank
you,
everyone.
We
can
end
early
today,
it's
a
bit
like
slow
this
weeks,
but
once
we
actually
start
metrics,
I
I
expect
we
will
be
like
much
more
like
lively
with
more
prs
and
activity,
but
yeah
just
no
other
update
so
goodbye.
Thank
you.
Everyone
for
joining
yep.