►
From YouTube: 2020-10-02 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
Hi
josh,
you
are,
I
hear
you're
helping
out
quite
a
bit
in
the
metric
sick.
Is
that
so.
C
A
So
I
usually
need
a
maintainer
sorry
a
tc
member
on
before
we
can
actually
go
through
all
of
this
and
triage,
but
we
can
spend
the
time
talking
about
some
of
these
issues
and.
A
Actually,
let
me
back
up
how
much
do
you
know
about
the
process
of
what
we
have
for
triaging
issues
and
then
what
they
mean
for
getting
to
ga.
A
So
we
have
this
top
level.
Github
project
called
ga
spec
burn
down,
got
it
so
this
has
everything
that
is
labeled
release
required
for
ga
and
release
allowed
for
g8
stuff
that
we
desire
for
ga.
A
B
A
Title
actually
has
to
be
updated,
so
we
got
different
columns.
One
is
like
to
do
in
progress
and
done
so
31
and
to
do
six
in
progress
if
it's
got
a
pr
related
to
that
issue.
It's
in
progress,
okay,
and
with
that
we've
also
cut
across
multiple
different
dimensions,
two
dimensions,
an
area
and
then
the
which
means
like
the
the
topic
area
and
then
also
spec,
which
means
the
sub
directory
under
the
spec
project.
A
And
that's
opened
against
the
specification
repo,
that's
the
state
of
where
we
are
right
now,
once
the
specification
has
been
specified,
all
the
languages
can
implement
the
java
javascript
python
go
rust
or
length.
Why
not,
then
they
can
implement
with
common
expected
behavior,
and
then
we
have
ourselves
a
suite
of
client
libraries
in
the
collector
in
a
protocol
that
work
harmoniously
together.
D
A
So
we're
right
now
at
the
point
of
trying
to
freeze
the
trace
portion
of
the
spec
so
stuff,
that's
marked
with
spec
trace
and
once
that's
frozen,
we're
going
to
move
on
to
the
metrics
portion
of
the
spec
and
then
once
that's
frozen.
I
think
those
are
the
two
like
very
large
big
hurdles
to
overcome
in
order
to
arrive
at
it
at
the
decision
point
for
the
date
for
ga.
B
A
A
And,
and
as
the
languages
are
implementing
it,
we
can
do
small
tweaks
as
each
one
of
these
as
the
specs
are
frozen.
A
They
are
hardened
with
a
prototype
if,
if
it's
a
complicated
thing
that
they're
not
sure
whether
it
works
across
all
different
languages,
okay,
so
in
order
to
build
some
validity
towards
what's
written
in
the
specs,
so
it's
not
just
like
people
in
ivy
tower
are
thinking
words
in
english
and
then
right.
A
B
A
So
spec
metrics
is
are
the
things
that
will
probably
be
most
relevant
towards
the
metrics
sick
right
and
what
I'll
be
going
over
at
this
meeting
as
soon
as
people
start
jumping
on
is
new
issues,
that's
open
because
they
can
come
from
anywhere
making
sure
they
have
the
proper
labels
in
the
proper,
whether
we
want
for
ga
or
after
j,
and
then,
if
it's
required
for
ja,
what
the
priority
is
all
right.
So.
D
A
Of
it
I
already
see
22
hours
ago,
j
macd
opened
one
for
spec
metrics.
He
he's
one
of
the
maintainers
and
the
metric
cigarette.
I'm
sure
he
self-labeled
that
right
and
yeah
all
right,
so
they
already
did
some
talking
on
that
stuff.
So
we
got
to
figure
out
like
what
priority
this
is
that
way.
People
have
an
understanding
of
focus.
That's
been
one
of
the
challenges
in
the
community
is
everyone's
got
very
technical.
They
have
a
lot
of
great
ideas,
but
like
the
biggest
thing
that
we
gotta
nail.
A
What
is
that
and
try
to
categorize
that
that's
how
this
labeling
is
is
meant
to
help
that
I
see
okay,
so
I'll
pause
right
there
do
you
have
any
questions
about.
B
No,
I
I
did
file
some
issues,
though
under
respect
metrics,
so
we
could
look
at
those
a
few
folks
who
are
interested
in
owning
those
issues
and
and
working
on
a
first.
A
B
So
I've
been
focused
on
the
looks
like
chris
already
took
one
good
so
yeah
these
define
metric
semantic
conventions
tickets.
I
made
a
separate
one
for
each
sort
of
category
the
analogous
to
the
the
trace
semantic
conventions.
B
And
yeah,
so
chris
wildman
looks
like
he.
Maybe
he
commented
on
messaging
systems.
B
He's
a
okay.
He
he
took
this
one
all
right
good
deal.
I
wasn't
sure
if
he
was
he
was
on
the
project
yet
or
or
if
someone
else
was
okay,
I'm
going
to
take
it.
So
that's
messaging
systems
and
then
there's
also
what
the
one
for.
B
Too
great,
and
so
those
are
both
like
all
of
these
were
issues
that
I
felt
like
should
probably
fit
into
what's
needed
for
ga
ahead
of
the
the
spec
freeze
two
weeks
from
now.
Okay,.
A
Okay,
so
I
it'd
be
good
if
you
put
a
comment
down.
A
I
I'm
not
as
familiar
with
the
what
is
the
best
call
for
the
stuff
on
the
ga.
I
I
trust
the
six
judgment,
but
I
mean
you
can
put
in
here.
Your
desires
like.
I
think
this
is
kind
of
required
for
ga,
as
opposed
to
categorizing.
Like
you
know,
this
is
nice
to
have
I'm
trying
to
figure
out
like
whether
there's
other
ways
to
do
it.
I'm
not
sure,
I'm
finally
sticking
it
anyways
just
to
track
it.
You
know.
A
So
if
you
have
an
opinion
there
stating
that
it
will
also
help
with
the
triaging
and
also
setting
expectations.
Okay,.
B
A
B
A
E
B
I
don't
know
if
there's
been
any
more
discussion
here
either
since
I
last
left
it
doesn't
seem
like.
B
A
Name,
yeah.
B
And
I
I
don't
think
that
we
we
reached
an
agreement
on
that,
but
it
feels
like
like
definitely
something
that
that
would
need
to
be
agreed
upon
before
before
the
spec
freeze.
Right.
A
B
Yeah,
that
could
be
the
case.
I
haven't
I'm
not
familiar
enough
with
this.
A
This
one's
already
marked
for
priority
p1,
so
this
one
will
go
in.
Are
you
familiar
with
the
priorities.
B
No,
I
had
a
question
about
that.
So
we
have
three
buckets
right.
There's
p1
p2
p3
is.
It
is
basically
just
like
if
we
can't
get
everything,
that's
scoped
for
ga
done
at
least
get
the
p1s
done.
A
So
so
the
priorities
go
in
conjunction
with
the
release.
A
So
right
now,
if
it's
required
for
ga
it's
it's
a
must-have
and
then
of
the
must-have
just
last
week
we
had
scrubbed
it.
So
we
used
to
have
p1p23s
p3s.
We
moved
the
p3s
to
after
ga
in
the
p2s
we
triaged
and
find
out
whether
we
need
to
bump
some
to
p1
or
move
it
to
allow
for
ga
so
required
for
ga
actually
should
essentially
only
have
p1.
A
J
and
then,
if
I
do.
A
All
right,
so
it
because
we've
we've
excluded
metrics
for
now,
in
order
to
concentrate
on
the
trace,
corresponding,
you
know,
context
and
baggage
issues
as
well.
Those
are
required
for
the
trace
spec
to
be
frozen
down.
We've
got
these
two.
This
is
something
I'd
like
to
talk
about
at
the
triage
meeting
today.
A
And
so
we
got
a
bunch
of
these
required
for
ga
18
of
them
they
got
p1p2s
p3s,
and
so
that's
what
we
need
to
sort
out
is
whether
are
all
of
them
actually
required
for
ga,
because
last
week
we
created
a
new
label
called
allowed
for
ga.
I.
B
A
Which
means
it's
nice
to
have
if
it's
not
done
by
the
time,
we
want
to
call
it
ga
and
it's
still
open
we're
going
to
still
move
with
ga,
okay,
so
the
easiest
candidate
for
that
are
p3s
right,
like
I
kind
of
say
like
why
was
it
labeled
the
p3
if
it
was
actually
like?
Oh,
this
is
crazy
important.
We
actually
is
in
the
p1.
So
that's
the
kind
of
compensation
we
need
to
have
it
in
order
to
be
able
to
scrub
all
this
down.
B
Okay
sounds
good,
and
the
the
freeze
for
the
metric
spec
is
is
mid-october
right.
It's
like
the
15th
or.
A
Maintainers
meeting
I
put
in
this
graph
just
to
draft
out
what
the
timeline
could
be,
but
this
is
not
definitive
like
I,
I'm
not
authoritative
in
setting
the
dates
I'm
just
trying
to
be
transparent
in
terms
of
like
where
we
are
and
what
I
see
in
the
bucket.
So
that
way
the
community
can
make
a
decision
towards
what
is
reasonable
to
accomplish.
A
So
I
put
this
down
as
what
I
saw
as
the
things
that
we
have
in
flight,
so
the
trace
spec.
We
were
trying
to
freeze
by
the
28th
it's
already
october,
2nd.
So
this
traceback
issue,
this
red
line-
is
already
moving
forward
towards
the
fifth
and
from
that
the
initial
estimation
for
trace
implementation.
A
It's
like
after
the
specs,
lock
down
across
the
board
across
the
languages
that
we
want
for
ga
java.
Javascript
python
go.
You
know
the
c
sharps.
They
all
said.
Yeah
four
weeks
sounds
reasonable
to
implement
everything
on
that
trace.
Spec,
okay,.
B
A
Straight
up
four
calendar
weeks,
so
the
metric
spec
has
this.
I
didn't
know
what
to
put
down
in
here
like
three
weeks.
Is
it
reasonable
to
depends
on
how
we
triage
those
things
I
have
to
get
the
p1s
merged
is
three,
but
it's
too
short
or
two
because
plenty
of
time.
Why
not
and
then
the
metrics
implementation
goes
parallel
with
it,
but
like
after
this
freezes,
I'm
sure
there's
extra
work
on
how
much
extra
work
two
weeks
three
weeks.
A
That's
why
I'm
not
sure
here
was
kubecon
north
america
on
the
17th.
It's
actually
you
know,
17th
is
the
tuesday
so
that
that
was
our
initial
target.
C
A
That
we
had
set
earlier
in
the
summer
how
close
we're
buttoned
up
against
that
and
how
much
this
target
is
still
realistic
in
order
to
say
yeah
sure
ga
is
the
question
that
we
need
to
answer
for
the
community,
because
they'll
change
our
messaging
on
cubicon,
north
america,
whether
we
say
here's,
ga
or
whether
you
say
ga
is
coming
soon.
We've
arrived
at
this
point:
the
stuff's
been
frozen.
This
is
frozen.
You
can
try
it
out
like
on
these
languages
and
we
have
a
new
date
for
ga
or
something
so.
A
Okay,
that's
where
we
are
in
terms
of
the
status.
A
A
Right
but,
as
you
know,
there's
like
a
craft
little
sick,
sig
meetings
and.
A
But
yeah
it
it
would
be.
If
you
have
time,
it'd
be
great
for
you
to
also
join
this.
A
E
B
A
So
it
was
the
spec
sig
is
more
down
to
the
degree
technical
with
the
technical
committee
to
be
able
to
discuss
specification,
specific
topics.
The
maintainers
are
just
like
maintainers
from
every
single
language,
including
the
spectre,
okay,
and
talk
about
ga
timelines
and
stuff
like
that.
A
And
this
specs
sick
would
also
be
good
to
attend
if
you
could
as
well
or
at
least
that
here
are
the
notes,
if
you're
interested
in
getting
the
summary,
the
people
try
to
keep
keep
at
least
the
relevant
topics
they
talked
about.
So
if
there's
something
that
you
need
to
bring
up
for
like
metrics
or
something
like
that,
you
just
throw
it
in
there
if
it
helps.
If
you
want
me
to
also
highlight
it,
you
can
send
me
a
getter
message
or
something
like
that.
A
Okay
and
just
say,
hey
andrew,
like
this
is
important
for
this,
or
if
it's
put
it
in
here,
it'll
definitely
get
on
the
agenda
right
and
if
you
need
any
help
with
coordinating
making
sure
someone
has
some
time
to
speak
about
it
or
something
like
that,
I'll
just
make
sure
that
the
time
box
is
kept.
A
A
A
B
Yeah,
so
I'm
the
the
engineering
manager
for
the
metrics
team
at
new
relic.
B
Yeah,
the
dimensional
metrics
data
type,
that's
an
analog
to
the
hotel
standard,
so
yeah.
B
Fantastic
yeah
yeah,
so
I've
got
a
couple
of
folks
from
my
team
are
involved
chris
chris
wildman
and
and
yuki
who
are
working
on
some
of
the
spec
and
then
some
other
folks.
From
like
our
serverless
team
and
yeah.
I
don't
think
we
have
roughly
half
a
dozen
people
involved
from
different
different
teams.
A
Wow,
okay,
cool,
then
it's
your
efforts
would
be
greatly
appreciated.
B
Yeah
yeah
I'm
happy
to
help
and
yeah
you
know
have
some.
You
know:
project
management
experience
as
a
engineering
manager,
and
so
I'm
happy
to
help
with
like
issue
triage
and
like
maintaining
road
maps
and
stuff
like
that.
A
Okay,
yeah
we,
the
community,
covers
a
lot
of
ground,
could
always
use
some
help
in
this.
We
it
took
a
while
for
us
to
get
towards
an
organization
point,
an
organization
procedure
process
to
be
able
to
collectively
talk
about
like
what
what
we
need
to
get
to
ga,
like
I
said,
there's
a
lot
of.
Do
you
have
experience
with
open
source.
B
A
Okay,
because
it's
a
vendor,
neutral
environment,
like
we
got
a
lot
of
companies
from
different
time
zones,
all
that
stuff,
it
is
got
its
more
cats
and
herding
cats
yeah.
But
I
like
to
say,
because
the
open
source
nature
of
this
and
like
not
everyone,
it's
not
the
same
company.
A
We
don't
have
a
reporting
structure
per
se,
but
we
are
I
like
the
vibe
of
the
community,
that
we
can
at
least
talk
about
issues
and
be
able
to
collaborate
on
certain
things
and
make
progress
like,
of
course,
it's
different
opinions,
but
they
seem
to
be.
You
know,
willing
to
work
together
and
they're
all
interested,
definitely
generally
interested
in
in
trying
to
get
something
that
is
like
best
of
class
best
in
the
industry
worth
it.
They
come
from
the
open,
tracing
open
center.
B
Got
it
yeah,
and
I
had
some
experience
with
that.
I
used
some
open
tracing
and
open
senses
stuff
when
that
when
it
was
brand
new
and
they're
just
like
just
getting
started
on
that
standard,
I
was
really
excited
about
it
and,
like
we
built
the
company,
I
was
working
out
at
the
time
we
built
distributed
tracing
into
like
all
of
our
services
and
we're
following
that
standard
and
like
I
was
like
yeah,
it's
really
cool
to
see
all
of
it
kind
of
coming
together.
Now.
A
Yeah,
it's
I'm
really
happy
to
also
be
in
the
cncf
umbrella
of
open
source
communities
as
well,
because
it's
there's
really
helpful
support
structure
there
in
order
to
in
order
to
be
able
to
highlight
the
project.
So
I
hope
I
hope
we
can
grow
a
healthy
community.
B
D
B
Like
coming
at
it
like
being
brand
new
to
it,
I
feel,
like
you
know
that
it
feels
like
the
concern
to
me
is
making
sure
that
we
get
to
this
ga
release
in
good
timing.
B
So
the
people
who
are
involved
now
feel
like
it's
been
worth
it
for
them,
like
you
know,
there's
like
a
lot
of
vendors
that
are
like
putting
in
a
lot
of
their
employees,
time
and
energy
into
the
project,
and
I'm
sure,
like
they
probably
have
things
that
want
to
like
line
up
with
the
ga
release
and
and
so
to
me.
It
feels
like
this.
This
big
push
to
like
try
to
get
things
out
this
fall
is
is,
is
important.
A
E
C
B
Cool
yeah,
it's
exciting
yeah.
I
like
that.
It's
yeah
I
like
that.
It's
bigger
than
just
just
one
company
like
having
having
so
many
different
people
involved.
It
feels
like
we've,
got
a
really
good,
healthy
chance
at
like
finally
having
a
standard
for
telemetry
data,
and
you
know
somebody
who
was
formerly
an
engineer
and
worked
with
all
of
this
stuff.
A
lot
like
I
yeah
been
wanting
that
for
a
long
time,
so
I
know
other
people
do
too.
E
C
A
I
joined
the
company
lightstep
that
I'm
with
back
in
february
and
they
had
involvement
with
open
telemetry
as
well.
The
founder
of
vhs
ben
siegelman,
okay,
he's
also
heavily
involved
in
open
tracing,
so
we're
interested
in
getting
this
project
going
as
well.
So
that
way
it
could
be
helpful
for
the
bicep
company
as
well.
E
A
A
And
carla
should
be
jumping
on
soon
as
well
and
we
have
some.
Let
me
see
past.
C
C
Central
mass
like
near
spring
village,
so.
C
Oh
okay,
yeah.
I
I
was
born
in
new
hampshire,
northampton,
so
yeah
north
america.
A
C
C
A
All
right
all
right,
I
grew
up
in
north
of
boston,
so
suburbs
not
so
much.
You
know
southie
mark
wahlberg
type
accent,
but
I
had
a
couple
of
school
teachers
who
you
know,
get
the
soccer
ball
and
you
know
put
it
in
the
locker.
You
know.
E
C
D
D
Yeah,
this
is
the
one
I
put
it's
long
story
short.
There
was
a
long
discussion
about
whether
third
party
propagators
could
exist
in
open,
telemetry
ripples
and
after
yes,
or
no
an
ongoing
discussion,
we
said
no
and
now
sergey.
I
probably
got
confused
about
some
agreement
that
we
middle
agreement
we
found,
which
we
later
reverted
and
now
it's
like.
He
reverted
that
back.
So
I
would
say
that
this
is
required.
This
is
allow
for
ga,
let's
say.
D
This
is
for
stuff,
like
aws
or
like
step
specific
stuff
yeah.
So
basically,
the
previous
agreement
is
that
we
won't
be
maintaining
them
like
vendors.
Are
you
know
we're
happy
to
have
them
maintain
their
own
ripples?
Not
us.
D
Yeah
anyway,
what
was
this
so
the
agreement
is
that
we
will
discuss
that
on
maintainers
meeting
next
monday.
D
That's
metric
so
tyler,
maybe
or
josh
you
guys
can
make
a
call.
C
Yeah,
I
don't
know
if
josh
is
on
the
call.
I
don't
think
so,
but.
C
I
thought
that
he
was
opening
this
to
address
before
the
ga,
so
I
think
if
that's
a
it's
required
for
ga
from
the
meeting
estimate.
Okay
yeah-
I
I
would
probably
say
this
is
a
pretty
high
priority.
Maybe
a
p2,
but
that's
the
conservative
one.
It
might
be
a
p1.
I
josh
could
probably
fix
it
if
it
needs
to
get
fixed,
though
so
I
would
probably
just
get
required
for
ga
and
p2.
A
C
Okay,
I
think
it
might
just
be
it
allowed
for
ga,
then,
because
I,
if
I'm
not
mistaken,
this
should
be
able
to
be
fixed
in
a
backwards
compatible
way,
but
the
problem
is
like:
if
the
api
wouldn't
change,
the
behavior
would
like,
if
you
registered
a
invalid
or
duplicate
it
would
return
you
an
error
instead
or
it
would
fail
in
some
way
yeah.
D
You
can
you
can
make
a
call
and
just
cc
judge
mcdonald
to
verify
this.
A
Hey
macd
is
the
person
yeah.
If
you
think
this
is
adjustment.
C
Maybe
an
api,
I'm
pretty
sure.
Yes,
yeah,
okay,
yeah.
A
Oh,
do
we
have
enough
to
know
who
would
be
a
suitable
person
for
for
the
required
ones?
I
also
try
to
get
an
assignee
towards
it.
Do
we
have
enough
to
know
who
would
be
the
best
person
to
assign
this
to.
E
C
A
A
A
A
A
C
D
C
C
D
B
C
C
C
A
A
B
Yeah
so
the
same
as
the
last
one-
and
this
is
the
one
for
rpc,
I
think
we're
still
looking
for
like
I
wanted
to
ask
in
the
cl
the
sid
call
yesterday.
If
anyone
from
google
want
to
weigh
in
here.
C
Yeah,
I
feel
like
we
should
try
to
get
some
involvement
from
people
at
google.
There.
B
C
Okay,
can
we
assign
this
to
you
joshua.
A
All
right,
one,
six,
another
one.
B
B
Let's
see
michael
is
is
michael
in
the
project.
C
Yeah,
you
have
to
be
a
part
of
the
organization,
so
it
well.
If
you
had
commits
you,
could
become
a
part
of
the
organization.
It's
just
yeah.
You
can't
blind
assign
them.
You'd
have
to
put
a
comment
in
here
with
his
name
or
something
like
that.
I
think
before.
Okay
I'll
do
that
yeah.
B
E
C
E
A
A
Cool
all
right,
that's
the
most
important
agenda
item
I
had
for
today.
I
I
think
carlos,
the
the
I
talked
with
josh
here
about,
like
we
were
going
to
flip
the
maintainers
and
spec
meetings
call,
but
I
think
I
reread
the
meeting
notes
morgan's
going
to
bring
this
up
on
the
monday
first,
so
we're
still
going
to
have
maintainers
meeting
on
the
monday
meeting
on
the
tuesday,
I
guess
to
communicate
with
everyone,
because
the
topic
wasn't
brought
up
at
the
last
maintainers
meeting.