►
From YouTube: 2020-08-26 .NET Auto-Instrumentation 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).
B
B
While
we're
waiting,
I
got
a
quick
question
about
the
datadog
agent.
Do
you
know
if
it
works
on.
B
Oh,
does
the
datadog
agent
work
on
mac
os.
C
I'm
not
sure,
that's
a
question
that
greg
you
have
to
work
yeah.
I
I
I
build
on
on
mac,
but
basically
there
is
a
bunch
of
steps
that
I
do
if
docker
compose
on
the
code
base.
You
know
I
do
some
small
stuff
when
I'm
working
kind
of
on
a
specific
thing.
I
use
that.net
command
line,
but
then,
when
I
need
to
test
and
do
the
final
validation
integration,
then
docker
compose
just
a
second
here,
I'm
gonna
shut
my
window.
C
C
C
Contribution
but
important
stuff
is
small
but
important,
and
we
had
a
conversation
about
the
branching
on
the
pr.
I
think
we
can
do
that
on
the
pr
we
don't
need
to.
Unless
there
is
questions
we
can
discuss
here,
but
I
think
the
general
approach
is
to
try
to
follow
the
open,
telemetry
and
basically
open
telemetry.
Just
follow
some
other
practices.
I
think
from
kubernetes
is,
if
I
recall
correctly,
that
basically
they
try
to
avoid
to
have
a
lot
of
branches
on
the
ripple.
The
branches
become
things
for
releases.
C
You
know
so
basically
everyone
forks
and
we
update
from
our
own
forks
to
create
the
pull
requests.
But,
as
I
said,
I
think
we
can
discuss
and
discuss
that
on
the
pr
I've
been
starting
to
work
on,
enabling
the
ci
I'm
still
not
there.
C
Yet
I
I
have
it
passing
for
most
but
failing
some
tests,
but
I
think
when
I
get
to
the
point
that
is
failing
tests
that
are
perhaps
flake
or
something
I
I
think
you'll
be
good
to
commit
and
we
go
from
there
we'll
work
on
the
tests
or
whatever
is
needed
from
there,
and
I
think
today
the
the
most
important
thing,
I
think,
is
for
us
to
think
about
what
we
wanted
to
work
first
on
the
repo
and
so
our
contributors
kind
of
get
in
sync,
and
we
can
kind
of
direct
the
the
movement
of
the
the
contributions
and
changes
in
in
that
direction.
A
Make
sense,
and
by
the
way,
paulo,
paulo
sorry,
I.
A
Was
out
on
monday
and
I'm
out
thursday
friday?
So
if
there's
something
I
saw
some
messages
of
you
like,
we
can
think
later,
if
you're
blocked
on
something.
From
my
end,
please,
like
ping
me
and
I
get
this
resolved.
I
just
had
a
very
noisy
week.
Sorry
about
that.
C
No,
no,
no,
no
problem
greg,
no
worries,
we
we
we
follow
up
on
those
and
we
we
can
follow
up
on
on
the
pr's
or
guitar
as
needed.
C
Thank
you
so
with
that,
I
think
we
can
kind
of
move
to
the
the
road
map
discussion.
C
We
had
some
earlier
document
that
kind
of
describes
this
kind
of
one
that
I
put
out
initially
with
a
relatively
few
discussions.
So
we
have
the
roadmap
stage
that
I
propose
initially,
basically
the
bootstrap
that
we
are
doing
right
now
and
basically
we
need
to
get
the
ci
and
then
we
we
need
to
decide
what
we
should
kind
of
focus
everyone
to
work
together
in
this
next
step.
There
was
also
kind
of
guiding
this
some
share
short
term
priorities.
C
That
was
that
we
discussed
it
initially
and
I
think
of
course,
the
trace
being
able
to
use
the
opentelemetry.net
sdk
and
move
into
active
source
you'll
be
kind
of
the
top
priorities,
but
I
would
like
to
hear
from
the
community
and
the
other
folks
how
how
they
want
to
organize
or
if
they
have
some
priority,
that
is
perhaps
different
or
conflicting,
with
some
of.
A
That
so
generally,
I
agree.
Maybe
if
you
can
oh
yeah,
you
already
have
it
on
the
screen.
Sorry,
so
general.
I
agree.