►
From YouTube: 2021-11-15 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
Okay,
let's
kick
this
off,
so
thank
you
for
joining
everybody
to
our
weekly
maintainers
call
if
you're
new
here
welcome
to
the
community.
So
let's
start
with
the
weekly
sig
check-in.
Do
we
have
any
updates
from
the
spec
group?
I
think
I
saw
a
note
from
riley
saying
he's
not
here
today
and
I
don't
see
carlos
yet
so
why
don't?
I
just
move
this
to
the
bottom
and
we'll
see
if
people
catch
in.
A
Great
okay,
so
metrics
we
can
update
the
api.
Spec
is
now
stable.
Sdk
spec
is
pretty
close
to
stable,
we're
focusing
on
the
prometheus
data
model
and
exporter
specification
all
right
for
logs
we've
ongoing
focus
on
the
data
model
and
stability.
For
those
who
aren't
aware,
the
logs
group
is
now
meeting
weekly
rather
than
bi-weekly,
to
do
a
big
spike
on
more
logging
functionality.
So,
if
you're
interested
in
that,
please
join
us
on
wednesdays
php.
We
have
slow
and
steady
progress.
A
Still
looking
for
more
maintainers
and
contributors
java
1.9.0
was
released
last
week.
Note
we
skipped
1.8.0
to
stay
in
sync
with
the
instrumentation
project
that
had
a
misfortune,
patch
release
and
needed
to
jump
to
1.9.2
makes
sense
plan
to
stabilize
the
metrics
api
in
1.10.0.
A
A
How
is
how
is
it
you
say,
progress
is
good,
like
any
feedback
for
the
the
specification,
authors
or
anything,
or
it
looks
fairly
straightforward.
D
So
what
we've
implemented
so
far
is
fairly
straightforward.
We've,
I
guess,
implemented
all
of
the
obvious
things
we're
now
moving
into
things
like
we
have
to
do
the
views
api,
which
the
specification
on
that
is
quite
extensive,
but
it's
not
obvious
how
to
implement
it.
So
we're
looking
at
like
the
go
sdk,
which
I
think
it
already
has
a
little
bit
further
along
than
we
are-
and
I
think
python
is
a
little
further
along
than
we
are
so
we're
sort
of
basing
our
implementation
on
those.
E
A
Right
python,
new
release,
1.7.1
any
updates
from
the
python
folks
about
like
any
notable
improvements
or
or
should
we
just
keep
going.
A
F
Yeah,
I
can
just
give
a
quick
update,
so
the
sdk
work
is
still
progressing.
We
are
trying
to
address
some
memory
issues,
however,
the
api
which,
for
dotnet
case
it's
part
of
the
dotnet
runtime,
so
they
went
ga
as
of
last
week,
so
it's
part
of
the
dot
net
6
release.
F
F
Except
the
view
half
of
the
view
feature,
but
we
just
prioritizing
like
addressing
some
memory
issues
we
want
to
like
reclaim
the
memory
if
the
user
is
opting
for
delta.
We
don't
want
to
remember
all
the
data
points,
so
those
are
the
things
which
we
are
trying
to
address
for
the
upcoming
release.
A
Yep
yep
I
like
that.
That's
a
good
pun
by
the
way,
addressing
memory
issues
I
like
for
go.
No
major
updates
release
1.2.0,
slash
v,
0.25
0.25.0
made
last
week.
Quick
question:
is
this
like
sdk
versus
api
version
numbers.
G
F
A
Great
active
work,
ongoing
active
work
is
ongoing
for
metrics
logging
and
bug
fixes
c,
plus,
plus
initial
metrics.
Api
is
merged.
Sdk
implementation
is
in
progress
with
our
timelines
listed
here,
trace
v
1.1.0
planned
for
this
week,
also
looking
for
more
contributors,
all
right,
any
updates
from
ruby
I'll
take
that
as
a
no
swift,
no
major
updates.
Collector
0.39.0
was
released
last
week,
collector
folks,
any
thing
sort
of
worth
noting
in
this
release.
A
Oh,
I
guess
not
anymore:
okay,
we'll
keep
going
erlang
finished,
most
remaining
missing
spec
items,
including
custom
id
generators
and
the
simple
span.
Processor
last
thing
to
do
is
limits
on
span
fields
like
astro
attributes
and
the
specification
had
a
1.8
release
last
friday.
A
Nothing
all
right!
Well,
this
is
a
quiet
week
going
once
going
twice
great
all
right!
Well,
I'll
see
you
guys
on
the
various
calls
this
week,
and
otherwise
next
monday
have
a
great
week.