►
From YouTube: 2022-07-15 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
It
doesn't
appear
that
we're
going
to
get
a
quorum
today,
give
it
a
couple
more
minutes.
I'm
going
to
close
off
the
session.
A
Hopefully,
hopefully
yeah-
I
I
haven't
heard
from
anyone
specifically
but
we'll
see,
goes.
B
Josh
mcdonald
marked
it
as
accepted.
Let
me
ping
him
on
slack
and
see
if
I
didn't
see
anyone
else
except
the
invite,
though,.
A
B
Okay
and
let's
see
so
open
telemetry
specification
settings,
let's
see
team.
B
B
Specs
triagers
yeah.
We
have
10
people
in
this
team.
B
B
B
A
Yeah
so
it
looked
like
there
was
only
a
couple
of
of
items,
items.
B
Yeah
we
should,
I
really
want
to
get
through
the
backlog
and
start
pulling
those
in
I
have
like
so
many
assigned
to
me.
I
need
to
get
back
on
and
start
fixing
that
it's
kind
of
insane,
but
we'll
do
it
over
time
right.
A
Actually,
the
more
folks
we
can
get
here,
we
can
plot
for
a
bit
more.
B
Yeah,
I
think
I
only
managed
to
actually
close
one
of
the
issues
from
last
time
that
we
triaged.
So
that's
not
on
my
personal
goal,
like
that's
like
way
below
what
I
wanted
to
do,
but
we'll
get
there.
A
B
A
B
Made
we
made
it
when
we
made
when
we
made
the
change
around
instrument
identity.
B
I
should
yeah,
I
still
don't
fully
buy
the
instrument
identity
change,
but
when
we
made
it
we
never
updated
the
spec.
So
that's
I'm
just
taking
a
look
to
make
sure
that's
true.
There
was
no
spec
change
yeah.
We
didn't
do
this.
B
B
B
B
So
basically,
what
this
is
is
we
never
finished
implementing
the
tooling
that
takes
the
definitions
in
yaml
and
generates
markdown
from
them,
there's
tooling,
for
tracing
to
do
that
for
spans,
there's
not
tooling,
for
metrics
and
there's
not
tooling
for
logs,
which
is
what
they're
calling
out
and
they
were
kind
of
confused
like.
Why?
Don't
we
do
this
for
metrics
and
we
do
it
for
traces?
Well,
we
never
finished
the
tooling.
A
B
B
B
All
right,
I
will.
I
will
open
that
tool
for
that
issue
as
a
feature
request.
B
Yeah
it
that's
like
yeah,
we
could
just
we
could
say
it's
triage
accepted,
but
blocked.
B
Okay,
so
we
want
markdown
table
generation
for.
B
Similar
to
tracing
account.
B
Cool
so
then
this
is
build
issue
105..
B
Thanks,
I
interpret
this
as
there's
more
up-to-date
tool
chain
required
to
make
this
possible.
Am
I
correct
in
the
assumption
I
gave
it
to
reverse
engineer.
The
metrics
hp
attributes
marked
on
the
ammo
blow
code,
generates
something
reasonable.
A
B
A
B
B
Two
is
we
need
to
then
go
update
the
specification
to
make
use
of
the
tool
and
what
my
thinking
is.
Is
we
repurpose
this
bug
to
say,
update
the
specification
to
make
use
of
the
tool
yeah
and
we
have
that
other
dependent
bug,
but
there's
no
way
for
me
to
say
that
something
is
blocked
on
another
bug
or
relying
on
another
bug.
I
think,
unless
there's
like
a
github's
convention
for
that.
B
B
Okay,
new
label
blocked
upstream
we'll
have
the
color
be
some
sort
of
red.
B
A
B
B
Yeah,
okay-
and
that
was
the
semantic
convention
thing,
so
I
will
add
that
blocked
up
stream,
okay,.
B
A
B
Oh,
should
I
should
I
say,
triage
accepted
and
blocked
upstream.
A
A
All
right
so,
let's
go
for
those
knives
and
then,
if
we
have
time
we
can
skip
down
to
this
one
here
going
back
a
month,
so
prometheus
hotel.
B
I
think
this
one
is
in
the
current
state
of
discussion
needed
in
that,
like
I
guess,
how
do
we
want
to
so
what
what
let
me
read
the
description
for
triage
discussion
needed
more
info
needed
hold
on.
What's
our
goal
for
triage
labels.
B
A
B
Of
those
options,
if
you
look
at
the
discussion,
that's
going
on
I'll
I'll
annotate
it
there,
because
that's
basically
what
we're
doing
we
are
there's
incompatibilities
between
what
prometheus
wants
to
do
with
their
his
high
resolution
histograms,
and
what
hotel
already
has.
A
B
Yeah,
the
problem
we
have
is
we're
debating
product
priorities
like
product
requirements
in
terms
of
technical
debates,
and
I
think
we
need.
We
just
need
more
information
about,
like
the
trade-offs
we're
actually
making,
as
we
go
through
here.
So
gotham
from
prometheus
is
proposing.
Like
hey.
Does
this
work
as
a
compromise
where
we
all
move
to
this
and
josh
is
like
hey?
I
did
this
as
a
experiment
and
I'm
starting
to
see
issues
with
this
proposal
so
effectively.
B
I
think
what
the
state
of
this
is
is
we
still
need
to
define
if
the
proposal
works
in
this
bug
before
we
accept
it
and
take
a
pr,
the
other
possibility
is
and
again
I
don't
know
how
we
want
to
do
triaging
in
hotel
in
general.
We
could
say
we
accept.
This
is
an
issue
that
needs
to
be
resolved
because
we
have,
and
the
discussion
will
be
in
the
pr,
but
I
feel
like
the
discussion
needs
to
remain
here
for
now.
A
Yeah
I
know
josh
has
been
working
on
this
for
a
while
yeah
and
there's
the
back
and
forth.
It
means
there's
definitely
more
attention
there,
so
I
think
yeah,
the
need
more
information
seems
to
fit
really
until
we're
satisfied
with
the
way
forward.
There.
B
A
All
right
so
we'll
go
ahead
and
see
this
one
needs
more
information.
B
I
yeah
I
did
look
through
this.
I
didn't
have
a
chance
myself
to
kind
of
evaluate
everything
that
was
being
asked
for
here.
Let
me
let
me
dive
into
it
just
a
little
bit
right
now.
B
B
Yeah,
I
feel
like
we
should
accept
this,
but
there's
some
comments
from.
B
Let's,
let's
mark,
let
me
add
this
to
the
tc
agenda
for
the
next
time
we
meet
to
talk
through
it,
and
maybe
we
say
triage
needs
more
info
yeah,
just
because
it
looks
like
there's
still
some
back
and
forth
between
carlos
and
tigran.
A
A
A
B
B
Anyway,
I'll
add
triage
needs
more
discussion.
I
guess.
A
All
right,
good,
that's
all
the
time
we
have
today.
Thanks,
appreciate
your
help
there
and
also
getting
the
the
privileges
as
well.
B
Yeah
no
problem
anytime.
Thank
you
for
running
this.
Like
it's,
it's
helpful
to
have
some
project
management.
You
know.