►
From YouTube: 2020-10-28 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
A
Yeah
all
right,
let's
get
started,
whoever
is
in
the
call,
please
mark
your
name
in
the
attendees
list.
I
don't
have
a
lot
of
agenda
here,
but
I
I
will
just
go
over
a
couple
of
release,
plans
and
milestones
and
when,
when
are
the
next
releases
expected.
A
So
let
me
go
over
the
milestone,
so
I
just
created
this
a
little
earlier,
so
it's
not
yet
assigned
with
correct
issue.
So
the
last
release
was
about
week
and
a
half
back,
so
the
next
one
would
be
by
next
monday,
which
would
be
the
last
beta,
followed
by
two
release:
candidates,
rc1
rc2,
followed
by
the
actual
ga.
So
I
put
like
number
30
as
a
actual
ga
date
to
rc's
before
that.
A
Hopefully
we
shouldn't
have
any
breaking
change
after
rc1,
so
depending
on
like,
if,
if
there
are
any
pending
decisions
to
be
made
about
public
apa,
we
may
adjust
it
by
like
a
day
or
two.
A
That's
the
quick
update
on
the
overall
release
plan
and
going
back.
I
will
be
scheduling
in
the
next
submitting
a
review
of
the
public
api.
I
mean
if
anyone
was
following
the
report.
There
is
a
pr
which
we
haven't
yet
merged
because
we
were
actively
making
changes
so
it
it
shows
you
all
the
public
apis
exposed
from
this
repo.
A
So
this
is
so
far
not
yet
merged,
but
once
it
is
merged
we
will
know
like
if
any
breaking
change,
not
just
making
any
change
in
public
api.
If
it
is
made,
it
will
be
called
by
this
tool,
so
it
can
be
like
conscious.
If
you
are
making
a
api
change,
it
will
be
a
conscious
decision,
so
this
will
be
merged.
Probably
by
end
of
this
week
and
the
plan
is,
we
can
do
like
a
community
review
in
the
next
meeting.
A
If
the
time
is
not
enough
separate
one,
so
we
can
go
over
all
the
public
ap
and
see
if
it
still
makes
sense
I'll
be
doing
some
cleanups
for
things
which
are
very
obvious,
but
it
probably
makes
sense
to
have
like
more
eyes
looking
at
this
and
make
sure
that
we
are
not.
A
We
are
not
exposing
anything
which
we
don't
want
public
and
we
are
exposing
things
as
public
which
are
required
by
the
spec
as
well.
So
that's
something
which
we'll
cover
in
the
next
week.
So
just
put
a
link.
I
I
mean,
if
it's
not
finished
in
the
next
seg
meeting
I'll
show
you
a
follow-up
meeting
just
to
do
the
public
api
review
and,
along
with
that,
I
will
be
actively
populating
or
marking
all
open
issues,
pr
sus
release
required
for
ga
or
not
required
same
as
what
specification
repo
has
done.
A
So
the
goal
is
to
make
sure
we
like
prioritize
our
resources
to
those
issues
which
are
required
for
ga,
so
any
changes
which
are
like
not
breaking
or
any
changes
which
are
additive
it
can
be
released
after
ga,
so
we'll
try
to
focus
on
things
which
are
like
marked
as
required
for
ga
it's
not
completed,
say
few
weeks,
since
we
really
did
a
cleanup
I'll
be
doing
that
at
the
end
of
this
meeting
or
probably
by
tomorrow.
A
So
we'll
get
a
good
read
on
what
other
things
which
we
need
to
solve
before
we
we
can
see.
A
So
that
is
my
updates
yeah.
We
have
more
things
put
into
the
agenda.
Let
me
is
there
any
question
on
the
release
plan
and
milestones
if
you
have
any
other
proposals
or
how
to
track
this,
I'm
happy
to
hear
that
some
project,
some
reports,
are
doing
a
project.
Ga
tracker-
I
didn't
have
like
a
lot
of
success.
Doing
that.
Maybe
I
I'll
work
with
chris
and
I
was
trying
to
do
this
sometime.
C
Yeah
from
my
experience,
projects
works
great
if
projects
were
great
with
with
the
like
visualizing
work,
and
if
you
only
communicate
via
like
messages
and
npr's,
it
doesn't
make
a
big
difference.
C
Andrew
andrew,
what's
his
name
yeah
he's
using
projects
a
lot.
I
think.
C
A
It
was
mostly
about
permissions
because
requirements
trying
to
do
that
and
okay,
let
me
see
if
projects
make
sense,
if
that's
the
case,
and
it
gives
a
very
good
visual
read
on
how
and
where
things
are,
but
by
default
I'll
make
sure
all
the
like
issues
are
assigned
with
milestones
and
tags.
So
this
should
be
a
good
read
of
what
is
expected
for
ga.
C
Yeah,
so
this
is
a
proposal
of
what
pr
will
look
like
it's
a
first
stop
or
started
like,
as
I
said,
that
we're
trying
to
expose
up
into
like
metrics
through
open
ceremony
sdk,
and
we
discovered
some
limitations
like
first
pr
was
that
start
time
is
not
present,
and
this
pr
is
under
review
right
now.
C
I
see
eddie
commented
there
and
mike
so
hopefully
it
will
go
forward
and
this
pr
second
one
is
to
add
a
new
aggregator,
and
I
really
want
somebody
who
also
has
stack
in
the
game
and
like
want
to
make
sure
that
matrix
works
review
it
from
perspective
of
usability
for
your
scenarios.
C
So
yeah,
please
read
up
what
laura's
suggestion
and
suggestion
and
we
can
start
implementing
it.
It's
it's
intentionally
smaller
one,
because
we
see
like
it's
already
14
files
and
it's
supposed
to
grow
even
bigger.
So
we
want
to
get
feedback
before
we
go
deeper.
A
A
A
So
would
it
make
sense
to
like
first
modify
the
existing
metric
instruments
to
match?
What
is
in
the
current
specification
and
then
do
the
skeleton
for
more
aggregation
types.
C
Maybe
if
you
can
comment
on
that,
it
would
be
great
to
discuss.
I
mean
we
have
two
goals,
I
validate,
how
it
works
and
to
end
and
make
it
compliant
with
specs.
So
we
really
want
to
make
it
work
end-to-end
and
like
if
we
will
make
it
compliant
to
the
specs
along
the
way
it's
great.
If
not,
maybe
we
can
do
it
all
together
as
a
as
a
bigger
kind
of
change.
A
Activity
matrix
for
like
quite
some
time
like
alan,
had
a
pr
where
we
are
collecting
some
counters
automatically,
which
is
again
built
on
top
of
this,
but
that
I
said
this
is
probably
the
first
pr
or
second
pair
we
are
having
in
matrix
yeah.
I
take
a
look
I'll
put
the
commander
board
like
about
being
compliant
to
the
spec
as
well
and
link
to
the
actual
spec
issue.
Is
it
someone
from
google
or
like.
C
And
I
can
very
good
because
I
I
really
like
in
some
context
and
metrics
and
I
I
wasn't
involved
very
heavily
so
for
me
just.
C
C
E
F
F
A
Okay,
something
is
happening.
Okay,
at
least
we
are
good
now
so
prashanth
can
you.
G
Ask
what
is
the
deal
with
this
one
yeah?
We
are
plenty
to
add
some
like
more
attributes
in
http
and
a
circle
span,
because
currently
the
odin,
the
ot
span
only
requires
some
attributes
and
yeah.
We
do
understand
that
we
provide
the
api
for
us
to
enrich
the
span
right,
and
but
we
realize
that
the
english
action-
this
is
only
one
action.
G
What
if
customer
wants
to
you
know
add
like
two,
for
instance,
if
they
are
using
x-ray
and
using
another
vendor
space
back-end
and
for
x-rays,
they
have
to
enrich
the
thing
for
for
x-ray
segment
sub
segments,
but
ending
at
the
same
time.
They
are.
The
other
vendor
also
wants
to
call
their
own
english
method
to
do
some
other
enrichment.
So
in
our
case.
A
Yeah
I
mean,
I
think
I
feel
very
clear
when
I
mentioned
so.
If
the
things
which
we
want
to
add
are
in
the
semantic
conventions,
then
we
don't
want
to
use
enrich.
It
should
be
done
by
the
sdk.
We
should
be
doing
it
in
the
instrumentation
itself,
but
if
it
is
something
which
is
not
defined
in
the
semantic
conventions,
then
it
is
like
user
specific.
We
don't
want
to
do
it
in
the
instrumentation.
A
Let
user
use
the
enrich
api
and
add
anything,
but
I
believe
the
ask
is
about
these
fields,
which
are
already
like
defined
in
the
common
semantic
convention,
so
we
should
be
able
to
just
do
that
in
instrumentation.
A
That
was
my
last
comment.
We
can
make
it
part
of
the
instrumentation.
So
are
you
asking
I'm
offering
to
submit
api.
B
A
What
I
meant
here
is
like
there
are
a
lot
of
attributes
here
which
are
marked
as
like
required
and
now
so
my
guess
is
like
by
default.
We
should
be
marking
populating
all
the
required
ones.
Everything
else
should
be
obtained
like.
A
Let
me
see
if
we
have
one
example
like
so
we
do
have
some
options
in
the
instrumentations.
Let's
pick
one
of
them
and
see.
B
Right
so
that
that
was
the
same
confusion
that
I
had
like.
So
we,
the
sdk
must
populate
the
fields
that
are
required,
but
the
ones
that
are
not
required
should
we
still
like
try
our
best
to
get
those
fields
populated
or
is
it
on
the
user
to
opt
into
those
fields.
A
B
A
Option
here
there
is
at
least
there
is
one
or
two
instrumentation
which
had
the
ability
to
turn
on
and
off
things,
but
unfortunately
I'm
not
seeing
it
yeah.
I
think
it
was
secret.
Let's
look
at
sql.
What
do
we
have.
H
A
Can
always
populate
all
the
attributes,
even
if
they
are
marked
as
optional
in
the
yep
right
yeah?
We
do
do
like
few
things
for
sql.
A
I
think
the
primary
motivation
was
it's
possible
that
sql
text
could
be
like
more
sensitive
data,
so
we
decided
to
make
it
opt-in,
but
if
there
are
no,
because
there
is
one
of
the
ask-
was
about
ip
address
right,
so
I'm
not
sure
whether
we
should
like
collect
it
by
default
without
user,
explicitly
asking
us
to
collect
it
here.
This
may
be
okay,
but
anything
which
is
potentially
like
identifying
the
user
or
anything
which
can
be
sensitive.
A
H
A
H
A
It
can
be
owned
by
default,
that's
also
like
fine,
but
there
should
be
a
way
to
turn
it
off
easily.
B
Yeah
that
I
agree
in
case
of
like
sensitive
information
that
we
can
provide
an
opt-out
mechanism
with
a
good
documentation
around
those.
A
This
would
be
like
if
it
was
like
an
option
directly
here.
It
should
be
like
very
easy
to
do
that,
it's
still
possible
by
writing
on
and
you
can
set
anything
to
null,
so
this
will
be
just
eliminated.
A
G
Yeah
we're
playing
previously
we're
planning
to
submit
the
pr
to
the
main
repo,
but
seems
like
we
have
to
do
this
in
our
country.
Reaper
right
in
the
processor,
our
own
processor,.
A
G
A
Yeah,
I
mean
the-
I
think,
I'm
bit
not
very
obvious
here,
because
what
I
meant
by
these
two
is:
if
there
is
some
field
which
you
want
to
populate
on
the
span,
slash
activity
which
is
not
defined
in
the
semantic
conventions,
then,
let's
not
do
it
do
in
the
sdk.
Let's
do
it
either
in
the
conrad
or
let
user
do
it
in
their
own
way
by
using
a
processor
or
using
an
image.
A
B
Yeah
about
getting
the
default
resource
with
the
environment,
where
you're
like?
Is
this
the
one
you're
talking
about.
B
Yeah,
actually
I
I
I
can
take
this
up
and
submit
a
pr.
B
A
Yes,
let's
look
at
this
issue,
one
three,
okay,
this
is
already
covered.
What
is
this
issue?
I
think
we
haven't
that.
That's.
B
A
pr
in
contrib
for
adding
instrumentation
for
aws
sdk
calls.
A
B
A
Thanks
for
bringing
this,
I
will
be
taking
a
look
so
okay,
cool
and
then
there
is
another
thing
since
sages.
Also
here
polu,
can
you
bring
up
that
same
topic
again
about
activity
overwrite?
I
think
it's
already
appear
here.
So,
let's
take
it.
A
And
figuring
out
whether
this
would
work,
but
one
issue
which
we
found
like
today
is
when
you
do
when
you
override
the
parent
id,
we
are
doing
it
in
the
activity
started
callback
in
a
separate
listener,
but
basically
what
this
really
means
is.
This
is
happening
after
the
activity
has
started,
and
that
also
means
the
sampling
has
already
translated.
Sampling.
Algorithm
is
already
run
now
you
are
replacing
the
active.
A
This
means
like
if
there
is
any
downstream
services
which
would
be
running
the
sampling
they'll,
be
doing
the
sampling
algorithm
based
on
the
new
id,
whereas
the
parent
has
done
it
on
like
a
different
id.
So
we
may
get
like
inconsistent
sampling
decisions
so
like
sergey,
do
you
have
any
thoughts
on
like
how
do
we
get
out
of
this?
If
you
like,
suggesting
we,
I
mean
you're,
suggesting
to
run
the
sampler
one
more
time,
based
on
an
extension
right.
G
Right
I
suggest
like
if
the
id
overriding
is
happened
after
the
sampling
decision,
then
we
not
only
replace
the
trace
id.
We
also
update
the
sampling
rules,
simply
decision
yeah.
A
A
Is
added
as
the
very
first
one
yeah
right?
Yes
again,
do
you
have
any
comments
on
this
approach
like
especially
about
running
the
sampling
like
one
more
time
so
that
everyone
gets
the
same
consistent
decision
if
they
are
using
the
trace
id
based,
sampler.
C
Yeah,
specifically
for
isp.net,
I
remember
there
was
a
callback
that
was
called
before
activity
started.
So
that's
where
you
can
replace
trace
id.
At
least
that
was
the
idea,
but
it
wasn't
genetic
solution
for
every
like
every
library,
okay,.
A
A
Okay,
but
that
is
only
going
to
be
like
applicable
for,
like
this
specific
asp.net
core
slash,
http,
client
right.
C
Yeah,
it
will
only
work
for
this
scenario
for
this
library
for
other
libraries.
I
don't
think
that
there
is
a
generic
solution
for
that
trying
sampler
again
is
not
a
bad
idea.
C
A
Okay
yeah,
so
there
was
an
issue
which
is
already
open
in
the
specification
about
like
making
it
a
must-have
requirement
for
the
ids
to
be
customizable.
A
A
C
I
really
hope
that
we
will
give
like
go
away
from
the
requirement
to
generate
less
random
trace
id,
so
we
can,
but
if
we
need
to
understand
why
it's
not
a
possibility,
I
mean
one
thing
is
making
sure
that
it
works
with
older
systems
like
with
existing
systems,
and
I
can
understand
that
but
long
term.
C
C
This
idea
generation
is
hidden
intentionally,
but
I
mean
if
it's
needed
to
be
open,
we
need
to
talk
to
the
team
and
ask
them
to
to
to
add
another
extensibility
point.
There.
A
Okay,
yeah
yeah,
I'm
hoping
that,
like
once
the
spec
is
really
sold
because
right
now
the
spec
does
not
require
it.
But
once
the
spec
says
it
is
a
must-have,
then
we
can
use
that
and
see
if
we
can
make
it
happen
in
dotnet
itself,
but
yeah
for
now.
We
have
to
leave
with
this
like
hacks,
slash,
workarounds,
yeah
I'll
see
if
I
mean
like
already
trying
some
experience
to
see
whether
it
works
and
we'll
continue
this
discussion
off
and
let's
bring
back
any
open
issues
to
the
next
one.
C
Yeah
because,
like
one
of
the
scenarios
we
discussed
with
asp.net
team
long
ago,
given
it
was
long
ago
to
share
request
id
with
ies,
so
whenever
ies
forwards
a
request
to
isp.net,
then
they
will
be
able
to
share
the
same
request.
Id
so
ies
logs
can
be
aligned
with
isp.net
logs,
but
it
will
require
changes
in
ies
because
we
don't
much
by
bitness
of
trace
id
right
now.
A
A
C
Get
a
yeah
one
duo
like
no
one
above
this
is
enabled
here
and
here.
If
you,
if
you
start
activity,
then
it
somehow
will
be
inherited
or
something
so
yeah.
I
think
I
think
you
need
to
start
another
activity
here.
C
Yeah,
I
think
something
like
that.
We've
been
discussing.
F
A
Yeah,
I
mean
everything
in
like
the
dot
net
report.
They
all
use
the
activity
dot
start
api
because
the
activity
source,
one
is
not
a
ga.
So
there
are
plans
to
convert
this
and
then
yeah
until
then.
It's
still
this
I
mean.
If,
if
all
of
asp.net
core
was
already
using
activity
source,
then
we
wouldn't
need
to
write
all
those
instrumentation.
G
Yeah,
so
I
have
a
question
so
seems
like
the
activity
created
through
sp
net
core
and
espn8.
They
have
a
neck
default
tracing
flags
right,
but
this
just
flag
is
not
designed.
It's
not
gonna
decide
if
they
are
gonna,
sam,
sampled
or
not.
This
will
be
decided
in
the
adapter
right.
Yes,
yeah,
absolutely
yeah.
So
that
means
the
the
our
trace
id
overriding
would
happen
before
and
you
can
make
simplizations
in
sp
net
core
understanding.
Is
that
correct.
A
A
So
that,
like
my
understanding,
is
clear
so
why
doing
the
replace
trace
id
here
like
you,
are
not
going
to
be
affected
by
the
sampling
decision
in
case
of
asp.net
core
and
all
the
legacy
instrumentations
which
we
have,
because
in
those
cases
we
do
not
have
the
samplers
run
by
default.
So
we
do
like
a
different
way
of
running
the
assemblies
by
using
something
called
activity,
source
adapter,
and
in
that
case
this
is
fine,
because
somewheres
are
run
like
after
activity
started.
So
we
should
be
able
to
respect.
A
I
mean
the
sounder
should
be
able
to
respect
whatever
is
set
here
as
the
trace
id.
G
Yeah,
so
the
odin
exception
is
that
when
user
is
using
the
activity
source,
the
start
activity
and
when
they
are
using
like
a
trace
id
dependent,
dependent
sampling
rules
right
in
that
case,
we
may
need
to.
E
A
Option
because
that
is
already
solved
by
this
approach,
so
all
we
need
to
solve
these
activity
source
based
activities.
They
will
have
to
rerun
the
assembler
to
take
care
of
these
scenarios.
G
A
Some
more
time
to
make
sure
like
there
is
no
other
side
effect
or
anything
I
mean
this
is
something
which
we
can
discuss.
Often
we
don't
have
to
have
everyone
on
the
call
to
discuss
that.
Okay,
okay,.
A
All
right,
we
do
not
have
any
open
issues
left,
but
I've
been
like
creating
issues
like
wherever
we
are
like
lacking
or
not
complying
with
respect.
So
expect
me
to
open
like
a
bunch
of
issues
like
tonight
and
tomorrow,
and
then
I'll
do
a
triaging.
So
if
there
are
folks
who
are
looking
to
contribute,
please
message
in
the
jitter
channel
we
can
find
like
issues
because
there
are
very
large
number
of
issues
would
be
like
really
small,
like
out
of
compliance
thing
like
spec
has
changed.
A
We
didn't
catch
up,
so
it
should
be
like
very
straightforward.
Look
at
the
spec.
What
is
the
drift
make
the
change?
So
if
there
are
folks
who
are
are
trying
to
do
like
initial
pr's,
just
let
me
know
or
message
in
the
jitter.
There
are
many
folks
who
can
help
you,
but
then
there
are
like
issues
which
are
a
little
more
complex
and
we
need
to
solve
it
somehow,
like
one
of
the
example
is
this:
we
have
been
solid
yeah,
I
mean
it's.
A
All
right,
I
do
not
have
any
more
topics,
so
is
there
any.
E
Any
topic
cjo
I've
just
got
a
got,
a
question
for
you.
I
wanted
to
understand
a
little
bit
more
about
what
we're
talking
about
when
we've
talked
about.
Logging
is
going
to
go
ga,
and
so,
like
my
understanding,
you
know
of
logging
and
like
in
our
agent.
The
way
we
do
it
is.
We
have
like
additional
log
enricher
repositories
that
are
like
for
specific,
like
siri
log,
and
you
know
log
for
net
and
stuff
like
that
and
those
function
by
doing
both
like
an
enrichment
on
the
logs.
E
So
like
adding
like
the
the
span
id
to
the
log
message
and
then
also
like
a
formatting
component
and
then
from
from
there
we
use
some
sort
of
generic
log
florida
like
fluentd
or
whatever
to
you,
know
ship
those
off
to
our
back
end,
but
so
I'm
wondering
kind
of
what
it
means
when
we're
talking
about
logging
in
the
case
of
the
sdk
and
kind
of
what
that
means.
When
we're
saying
that's
going,
ga.
A
So
when
here
is
my
understanding
when
we
say
vnga,
we
you
know
make
the
equivalent
of
span
in
log
word
so
for
in
case
of
logs,
we
have
like
processor
exporter
sampler.
I
think
sampler
is
only
one
missing.
Everything
else
is
already
there
like
you.
Can
you
have
an
option
to
like
change
anything
in
the
log
record
or
enrich
it
further
change,
formatting
or
in
like
stamp
it
with
span
id
or
something
else
from
the
activity?
A
If
your
back
end
supports
logs,
then
you
don't
really
need
to
do
anything
to
me.
You
just
need
to
write
your
own
exporter
to
send
it
to
your
backlog
back
end,
and
there
is
no
new
api.
It's
just
a
logger,
so
there
is
no
new
api
to
introduce
just
a
just
a
pipeline
if
there
is
no
better
words,
I'm
using
the
word
pipeline,
where
you
run
like
sampler
processor
exporter,
just
like
we
do
for
stands.
A
So
that
is
my
understanding
of
ga,
but
I
have
to
check
whether
what
the
specs
is
because
if
the
spec
says
we
cannot
ga
then
yeah,
we
will
not
call
the
log
signal
cg
I
this
is
something
which
I
I
have
to
confirm,
but
based
on
my
understanding,
when
I
last
checked
at
least
this
year,
there
is
no
apa
coming,
so
we
don't
have
to
wait
for
any
apis
to
be
introduced.
We
can
just
adapt
to
whatever
is
available
and
we
should
be
good.
E
Yeah-
and
I
guess
just
one
one
last
question
from
my
understanding,
so
this
is
you
have
to
be
using
the
the
I
logger
interface
to
support
this
right
so
like
what,
if
somebody's
using
like
siri
log
or
some,
you
know
some
other
specific
package.
Well,
then,
we
have
to
use
some
sort
of
case.
A
Yeah
yeah,
it's
very
similar
to
the
activity
like
if
like
span
or
activity,
is
our
api.
If
a
library
is
already
emitting
that,
then
we
are
good.
If
they
are
not
doing,
then
we
need
to
write
adapters,
so
that
is
for
I
logger
as
well.
If
you
are
not
using,
I
logger,
then
you
have
to
re-instrument
or
write
adapters
to
convert
from
that
format
to
yoga
okay,
yeah
and
it's
like
I
logger
also
has
a
limitation.
It's
not
supported
in
dotnet
452
and
dot
net
for
six.
A
So
if
you
are
in
any
of
those
like
dotnet
frameworks,
then
you're
out
of
like
there
is
no
looking
solution
here
at
least
today,.
A
And
we
I
mean
I'm
yet
to
figure
out
whether
there
is
a
way
to
like
send
these
logs
into
yeager
or
sikkim.
A
A
Yeah,
so
we'll
only
have
to
use
like
send
it
to
otlp,
because
there
is
a
profile
defined
for
sending
it
to
the
otp
exporter
and
from
there
like,
I
don't
know
it
could
be
elasticsearch
or
something
else
yeah,
but
if,
like
there
are
like
new
relic,
you
wants
to
export
it
to
a
new
ruling.
Backend
or
ashore
wants
to
export
it
to
a
short
back
end.
The
infra
pieces
to
make
that
happen
is
already
here.
A
You
can
write
your
own
exporter
and
there
is
a
some
limit
implementation
which
shows
like
in
memory
exporter,
so
we
can
just
take
it
this
I
mean
this
is
just
printing
it
in
the
console,
but
you
can
change
it
and
export
it
to
your
back
end
now.
This
is
probably
like
the
early
version
I
I'll
be
like
working
through
this
this
week
to
make
it
support
more
things
like
certain
things
are
like
missing
you
if
you
have
used
iloka
before
you
know
like
the
scopes,
are
missing
here.
A
A
local
support
scopes
and
this
log
record
currently
do
not
have
scope.
So
there
are
things
which
are
missing,
but
it's
relatively
easy
things
to
solve.
So
we'll
be
solving
it
in
the
next
few
weeks,
whether
it
will
be
called
ga
or
preview.
That
is
something
on
me.
I
have
to
figure
out
what
does
the
stick
says
then?
Come
back
to
that.
A
Okay,
yeah:
are
there
any
other
topics
to
discuss.
A
Okay,
yeah,
it
looks
like
we
have
one
new
member
vishwash
like
if
you
are
here
for
first
time
you
want
to
just
introduce
yourself
to
the
team.
I
don't
recollect
whether
you
introduce
yourself
before
so.
If
you
want,
you
can
go
ahead
and
do
it
now.
I
Hey
yeah
sure,
hey
hello,
everyone.
This
is
from
microsoft,
working
with
sergio
looking
to
get
started
with
opentelemetry.net
yeah,
I'm
just
very
new
haven't
submitted
any
pr's,
yet
just
trying
to
increase
my
knowledge
and
soon
will
be
starting
to
contribute.
Yeah
thanks.
A
Thank
you,
members
from
microsoft
who
are
new
to
the
project
so
like.
If
I
mean
we'll
try
to
find
like
really
easy
issues
to
start
with,
and
hopefully
they
can
also
do
more
contributions
by
the
time
we
are
ready
for
ga
so
like
there
are
too
many
issues
right
now
open,
so
we
want
to
get
like
maximum
help
as
possible.
A
All
right
is
there
anything
else.
If
not,
we
can
stop
the
meeting
for
now
and
meet
again
next
week.
All
right,
that's
it
then.
Thank
you.
Everyone
see
you
next
week,
thanks
bye.