►
From YouTube: 2021-11-08 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
B
Normally
runs
the
meeting
yeah,
usually
morgan,
who
is
not
here,
I
was
about
to
volunteer,
but
what
about
you
josh
this.
A
Yeah
I
well,
I
have,
I
have
a
near
permanent
conflict.
I
do
I
want
to
talk
to
the
road
map
and
I
just
want
to
give
everyone
a
heads
up
that
I
plan
to
come
and
talk,
and
then
I
got
a
migraine,
so
I
will
be
super
grumpy
and
I
apologize
make
sense.
Thank
you
for
your
honesty.
B
Okay,
let's
go
over
the
agenda
items.
Thank
you
for
joining.
Please
don't
forget
to
add
your
names
specification
yeah
just
for
your
information,
there's
a
monthly
release,
cadence
and
we
will
be
doing
the
release
this
week
coming
up,
metrics
matrix
api
spec,
reaching
stable,
really.
C
Yeah,
it's
just
a
for
your
information.
I
send
a
pr
to
mark
the
matrix
api
spec
at
stable
and
we
discussed
this
during
the
last
week.
Metrics
say
there
is
no
objection
and
the
api
spec
has
been
has
been
feature
freeze
for
more
than
three
months
and
there's
no
outstanding
issue.
So
we
have
good
confidence
and
another
ask
for
everyone
is
if
you're
working
on
the
matrix
prototype.
B
D
Is
anybody
from
the
lobster
group
here
yeah
it's
andrew
glosky
here?
Basically,
the
main
thing
is
we're
just
continuing
to
focus
on
nailing
down
the
data
model
we're
targeting
stability
in
q1,
though
we
think
we'll
get
pretty
close
this
quarter
and
as
part
of
that
we've
we've
reached
out
to
the
folks
over
in
the
ebpf
working
group.
You
know
they're
they're,
concerned
with
events,
and
so
we
want
to
make
sure
our
logs
the
slash
events.
Format
is
suitable
for
them
as
well.
A
Can
I
ask
a
question
there:
are
you
involving
the
whoever
the
people
that
wanted
columnar
events
that
that
sipped
in
there
in
that
discussion,
or
is
this
completely
unrelated?
I'm
just
I'm
just
curious.
How
much
like
what
the
scope
of
that
discussion.
D
I'm
not
actually
sure
I
think
we
we
reached
out
to
this
group.
If
there's
another
group
out
there,
I
wasn't
aware
of
them
or
their
other
conversations.
I
haven't
seen
a
lot.
A
There's
a
there's
a
pending
sip
or
not
sorry
that
I'm
thinking
of
scala
a
penny
otep
there's
a
pending
otep
with
a
event-based
protocol.
If
I
just
want
to
make
sure
that
whatever's
decided
there,
if
it's
like
just
log
based
events
that
that
other
otep
is
out
of
scope,.
D
A
B
It
great
thank
you,
php.
E
B
I
forgot
that
probably
josh
john
wasn't
sorry
he's
taking
day
off
today,
because
it's
a
splunk's
company's
day
off
1.1.90
release
plan
for
this
week
and
they
will
be
skipping.
The
1.8
there's
there
are
details
below.
It
seems
java
instrumentation.
F
Yeah,
so
the
details
are
that
last
week
we
made
a
patch
release,
but
our
we
had
been
making
some
changes
to
our
release.
Automation
and
the
patch
release
accidentally
went
out
as
1.8.0
instead
of
1.7.1,
so
we
decided
to
skip
1.8.0.180.
F
Instead
of
making
the
next
like
major
release,
181
was
the
other
option
and
so
we're
going
to
jump
to
190
and
that's
why
the
sdk
is
going
to
skip
180
so
that
we
can
stay
in
sync.
G
Yeah
so
we're
moving
along
with
metrics.
I
would
call
the
api
you
know
almost
done
and
the
sdk
is
still
in
fairly
early
stages
and
unfortunately,
one
of
our
maintainers
announced
at
the
most
recent
meeting
that
he'll
be
stepping
down.
So
you
know
we
we
already
we
had
three
before
so.
We'll
still
have
two,
so
the
situation's
not
entirely
dire,
but
you
know
it's
it's
unfortunate,
but
it
is
what
it
is.
B
Yeah,
that's
probably
a
good
call
for
javascript
developers
to
join.
So
if
there's
anybody
in
your
company
I
had
mentioned
to
daniel
that
yeah,
we'll
probably
be
trying
to
bring
somebody
but
write
javascript,
so
yeah.
Let's.
G
G
B
Yeah,
that's
something
that
has
happened
in
other
things
as
well,
so
yeah,
that's
a
relatively
unexpected
scenario.
B
Okay-
let's
talk
about
that,
probably
in
an
issuing
community,
because
probably
it's
a
it's
a
common
thing:
okay,
yeah
trying
to
just
continue
with
the
gender
python.
H
Yes,
sorry
so
just
there's
a
plan
to
release
next
week
and
there's
more
progress
on
this
error,
handling
and
metrics.
Of
course,.
I
Yeah
so
as
mentioned,
there
is
only
a
little
bit
progress
since
last
two
weeks,
but
we
are
trying
to
address
remaining
metrics
issues
like
half
of
them
is
at
least
internal
issues
like
just
figuring
out
the
memory
optimization
and
then
the
public
facing
issue
where
we
still
have
like
missing
features
from
view
so
trying
to
add
them
as
well.
J
Yeah
not
too
much
to
add
other
than
what's
written
there.
No
major
work.
I
was
out
for
a
little
bit
of
last
week,
but
still
active
work
and
metrics
logging
and
bug
fixes.
E
Yeah,
so
matrix
api
is
mostly
done.
I
think
we
will
be
submitting
the
pr
in
this
week.
Mathematics
sdk
is
still
very
early
stage
and
we
are
also
preparing
for
the
trace
next
release
for
the
tcp
and
also,
I
think,
as
mentioned
here,
we're
working
working
on
the
improvement
in
the
build
from
the
release
star
wars,
because
we
I
mean
lots
of
users-
have
faced
some
issue:
how
to
do
a
build
from
the
target.
Most
of
our
build
pipeline
in
the
process
is
based
on
building
from
the
git
repo,
not
from
the
target.
E
B
Thank
you,
okay,
ruby,
swift!
I
think
there
are
no
updates.
Likewise
collector
collector
contrib
now
has
four
maintainers,
that's
very
nice.
Definitely
the
codes
base
is
getting
larger
and
larger.
So
thank
you
for
that
rost
working
on
both
fixes.
No,
no
major
updates
airline
updates.
Okay.
Now,
let's
jump
into
josh's
point
regarding
the
open,
telemetry
roadmap,
please
josh.
A
Yeah
and
again,
apologies-
I'm
fighting
a
migraine
here,
so
I
will
be
brief
and
hopefully
succinct
and
pretend
I'm
also
happy
so
yeah.
I
think
I
want
to
thank
everybody.
A
ton
for
the
hotel
road
map
help
so
far.
This
wouldn't
have
pulled
together
without
everyone
taking
a
look
at
things.
I
know
it's
a
giant
document
and
apologies
for
that.
I
think
we
will
learn
as
we
try
to
build
this
process
over
time.
I
want
to
give
you
all
the
current
plan.
A
A
So
what
I'd
like
is
for
everybody
to
take
a
look
at
the
information
in
there
and
make
it
up
to
date
as
much
as
you
possibly
can.
There
are
two
sections
that
I
think
every
maintainer
needs
to
be
aware
of.
One
is
there's
like
a
current
state
of
the
world
which
we're
going
to
you
know
should
already
be
kind
of
obvious
from
open
telemetry
I
o
status,
but
to
some
extent
it
wasn't
so
we're
going
to
see
how
to
migrate
that
back
into
open
telemetry.
A
I
o
status
as
it
makes
sense,
and
then
the
other
bit
is
a
set
of
road
maps.
There's
a
high
level
road
map,
which
is
meant
to
pull
from
underlying
road
maps.
The
idea
here
is
we'd
like
to
take
the
information
in
this
and
advertise
to
open
telemetry
users,
what's
ready
what
to
adopt
and
what's
coming
right.
So
if
we
can
answer
those
three
questions
after
this
beautiful
in
a
more
you
know,
cohesive,
you
know
holistic
way.
The
current
plan
then,
is
basically
two
more
weeks
of
review
for
this.
A
Let
it
sit
let
more
comments
and
concerns
now
that
it's
in
a
more
stable
state,
I
think
you
can
go
to
town
on
your
comments.
There
are
sections
that
I
think
we
need
to
cut
out
and
publish
individually.
I
think
the
metrics
roadmap
by
itself,
the
logs,
were
met
by
itself.
The
semantic
convention
roadmap
by
itself
might
make
sense
to
peace
out
instead
of
put
all
in
one
giant
document.
A
A
The
next
thing
is
the
idea
here
is
going
forward,
we're
going
to
try
to
run
a
hotel
roadmap
exercise
about
every
six
months,
so
sometime
around
q2
of
next
year,
you
know,
may
april
june-ish
we
might
run
another
one
of
these
and
then
we
might
do
another
one
in
october
again
of
the
next
year,
just
to
try
to
give
ourselves
goals
to
give
ourselves
aspirations
to
kind
of
figure
out
where
we're
going.
A
That
sort
of
thing
last
we're
gonna,
start
doing
a
little
bit
of
status
checks
and
a
quarter
a
little
bit
more.
How
are
we
doing
against
our
roadmap?
What
do
we
need
to
meet
our
map?
Should
we
advertise
to
people
that
things
are
slipping?
Changing
that
sort
of
thing
to
kind
of
address?
You
know
we
we
effectively
had
a
few
significant
delays
in
this
in
the
history
of
this
project
and
we
can
go
into
like
a
retrospective
of
why
that
happened,
and
I
think
that's
useful.
A
All
we're
asking
here
is
that
basically
every
quarter
every
three
months
we're
going
to
ask
hey.
How
are
things
going
and
what's
slowing
things
down?
How
can
we
improve
it
so
that
part
of,
like
a
retrospective
planning,
I
do
hear
the
open
source
maintainer
concerns,
and
I
do
know
that
open
source
is
very
spurtive
and
kind
of
bursty.
A
So
basically,
the
ask
around
this
road
map
is
things
that
you
know
you
can
commit
to
with
dedicated
people
on
the
project
that
you
know
won't
leave
make
those
commits
things
that
are
not
clear,
because
someone's
scratching
an
itch:
we
advertise
them
as
cool
projects.
People
can
work
on,
but
we'd
make
no
expectations
of
progress,
and
then
you
know
there's
a
section,
the
doc.
A
Actually,
if
you
click
through
the
doc,
I
don't
know
if
I
should
present,
but
there's
a
section,
the
doc
that
talks
about
just
goals
of
the
project
and
like
aspirations
that
we
have
it's
kind
of
somewhere
in
the
middle,
where
we're
going
like
for
traces
basically
provide
key
signals
for
robust
sampling
options
is
one
of
the
goals.
You'll
know
that
is
from
the
trace
sampling
sig.
That's
one
of
the
things
that
we'd
like
to
provide,
to
the
extent
that
we
have
a
set
of
goals
that
we
orient
people
around
and
maintainers.
A
Please
review
the
document
and
make
sure
what
you're
doing
is
denoted
somewhere.
A
So,
if
you're
working
on
like
a
really
cool,
open,
telemetry
thing-
and
you
know
that
you
want
to
launch
it
if
your
project
is
in
state
x,
please
make
sure
it's
accounted
for
in
that
document,
so
that
we
all
know
that
we
we
can
all
see,
and
so
we
can
all
advertise
again
we're
going
to
give
it
two
more
weeks,
review
and
comments
and
we'll
be
making
updates
on
there.
If
you
need
edit
access
to
the
document,
because
you
have
a
significant
section,
you'd
like
to
write,
that
is
fine,
that's
totally
fine.
A
The
next
ai
basically
is
after
you
reviewed
it.
I'd
like
for
everyone
to
basically
make
a
comment
that
they've
reviewed
it
if
you'd
like,
I
can
make
comments
for
people
to
say
like
please
approve
here,
but
I'd
like
to
have
us
all
kind
of
get
behind
the
document
and
say
yes,
this
is
the
state
of
the
world.
As
far
as
I
know-
and
this
is
the
direction
we're
going
make
sure
you
somewhere,
please
mark
the
document.
A
If
you
have
any
major
concerns,
please
bring
them
forward.
In
this
meeting
I
usually
have
a
conflict
and
I
can't
attend,
but
I
will
do
my
best
to
attend
for
the
next
two
weeks
so
that
we
can
talk
about
things
here.
A
You
can
also
just
ping
me
on
slack,
I'm
available
almost
any
time
and
then
after
that
two
week
period,
we're
gonna,
take
the
document
and
fragment
it
off
into
different
ways
of
you
know,
press
and
so
the
last
ai
is
at
the
end
of
that
two
weeks,
if
you're
interested
in
owning
any
you
know
blog
article
you'd
like
to
write
or,
like
you
know,
thing
you'd
like
to
tell
users
if
you'd
like
to
do
that
on
behalf
of
open
telemetry.
A
Let
me
know,
because
I'm
looking
for
a
lot
of
help
here,
there's
a
there's
a
good
bit
to
do
but
effectively.
The
only
thing
I'm
asking
of
maintainers
is
just
review.
The
document
mark
that
you
reviewed
it
and
if
you
see
something
missing,
that's
really
important
from
your
community
to
advertise.
Please
add
it.
B
B
Okay,
yeah.
Let's,
let's
review
that,
that's
everything
the
agenda,
so
I
think
this
is
it
so
stay
safe.
Everybody
take
a
break.
If
you
need
to
and
talk
to
you
soon,
ciao.