►
From YouTube: 2021-01-29 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
Oh
cool
today
I
imagine
it's
going
to
be
kind
of
a
light
day.
A
I
actually
didn't
have
any
agenda
items
to
talk
about,
but
I
wanted
to
stop
in
definitely
wait
a
little
bit
if
you're
here
on
the
call
please
join
or
open
up
the
google
doc
that's
associated
with
the
meeting
and
add
your
name
as
an
attendee,
we'll
track
these
kinds
of
things,
and
then
we
can
talk
about
whatever
you
all
want
to
talk
about
in
the
agenda
items,
but
yeah
I'm
liking
already
what
I'm
seeing
so
far,
the
project
board
hasn't
really
moved.
A
But
we
can
kind
of
dive
into
some
of
the
details.
C
A
So
first
question:
I'm
seeing
from
david
is
about
moving
the
meeting
time.
B
A
B
I
can
explain:
I
actually
brought
this
up
at
the
collector
sig
as
well,
because
well
first,
it's
just
a
question
of
like
is
anyone
on
the
call
from
like
one
of
the
asia
time
zones
that
benefits
from
having
this
meeting?
B
I
know
my
colleagues
james
and
nile
used
to
attend
regularly,
but
things
have
shifted
within
google
and
now
I'm
here
instead.
So
I
just
wanted
to
like
check
in
and
see.
Is
this
still
the
right
time
for
for
the
rest
of
the
community,
because
I
do
notice
that,
like
these
later
meetings
are
a
little
bit
light
more
lightly
attended
than
the
earlier
ones
so.
A
That's
a
good
question.
Yeah.
I
think
you
you
nailed
it
on
the
head
as
to
like
you
know.
Obviously
you
know
why
we
moved
it
but
yeah.
If
we're
not
gonna,
be
accommodating
people
in
the
apac
time
zones
like
I'm,
I'm
good
with
moving
it
back.
I
would
definitely
want
to
get
some
buy-in
from
some
of
the
other
people
on
the
sake.
A
One
thing
I've
also
kind
of
considered
is,
I
don't
know
what
time
would
be
good
for
japan,
but
we
do
have
a
collaborator
over
in
japan
exam
okay,.
C
A
A
But
yeah
I'm
totally
on
board
for
moving
back
to
just
unifying
on
10
a.m.
That
was
great.
It
worked
really
well
for
a
while,
so
looking
at
rich
as
well,
if
you
would
attend
the
10
a.m,
meeting
more
frequently
or
less
frequently.
D
I
usually
can't
make
the
10
a.m
thing
because
there's
another
meeting
scheduled
right
over.
It's
like
this
important
thing,
fat
planning
meeting
that
I
can't
skip
okay
but
steve-
and
I
are
both
pacific
time.
B
Anyways,
we
don't
have
to
decide
today,
but
I
want
to
throw
it
out
there
and
then
I'll
probably
check
in
every
late
meeting
and
then,
if
three
or
four
of
them
go
by
and
no
one
at
the
meeting
is
there
who
wants
the
meeting
later,
then
then
I
say
we
move
forward.
A
Yeah,
I
will
have
a
better
idea
at
the
next
late
meeting.
Okay
right
now,
I
don't
think
I
have
too
strong
opinion
either
way,
but
yeah.
A
C
A
Cool
awesome
yeah
thanks
for
adding
some
notes,
I'm
gonna
jump
ahead
rich.
If
you
wanted
to
talk
a
little
bit
about
your
question
or
any
api
changes
coming
soon
before
ga.
D
Yeah,
this
is
something
I
should
probably
know
after
just
looking
at
the
repo
and
the
plans,
but
I
would
just
wanted
to
throw
it
out.
There
are
in
the
past,
at
new
relic,
we've
had
tyler,
be
able
to
make
prs
to
our
open
telemetry
exporter
and
other
things
to
help
kind
of
accommodate
the
the
api
changes
that
have
been
happening
before
ga.
A
Okay.
I
think
this
is
the
right
one.
So
there
is
this
p1
burndown,
which
is
you
know.
I
don't
even
think
it's
that
useful.
So
let
me
back
that
up
really
quick.
Let's
just
go
to
there
is
this.
This
project
board
that
is
at
the
top
org
level
was,
is
put
up
here,
just
to
make
sure
that
it's
super
visible
as
to
like
our
progress
on
this
on
this
front
tracks.
All
of
the
open
issues.
I
really
keep
this
one
up
today,
the
p1
board.
A
I
don't
keep
up
to
date,
nearly
as
much
as
I
used
to,
which
is
something
we
could
work
on
if
it's
useful,
but
I've
never
found
anybody
else.
Besides
me,
I
think
that's
useful,
especially
when
you
can
do
filtering
like
this
label.
A
I
swear,
I
know
how
to
spell
yeah
something
like
this.
So
all
of
the
p1
issues
are
p1
specifically
because
they're
likely
going
to
be
including
api
breaking
changes
so
in
the
to
do
column,
there's
16
issues
that
are
associated
here,
things
like
actually
I
don't
even
know
this
is
a
p1.
A
Reconsider
context
keys
too
many
trace
packages,
you
know
so
obviously,
package
name
renames
unify
attributes
and
labels.
That's
a
pretty
big
one,
so
there's
definitely
api
breaking
changes.
What
parts
of
the
packaging
that
they're
gonna
actually
touch
is
not
necessarily
like
that
clear.
I
guess
we
could
also
filter
this
by
like
area
tracing
or
something
like
that
or
area
propagation,
because
those
are
supposed
to
be
included
in
the
the
1-0
release.
A
Metrics,
however,
might
not
that's
still
kind
of
a
and
unclear
depending
on
like
what
this
project's
timeline
is
for
actually
going
ga
and
what
our
appetite
is
for
wanting
to
push
that
forward,
which
is
not
necessarily
something
we
need
to
talk
too
much
about
right
now,
but
at
the
very
least,
the
tracing
and
propagation
stuff
is
going
to
get
moved
forward
as
with
the
rest
of
the
project,
and
so
anything
that
is
associated
with
the
p1
here
I
would
look
at
as
including
some
sort
of
api
breaking
change.
A
That
being
said,
I
might
have
mislabeled
this
as
well
like
this
could
probably
be
a
p2,
and
since
we
have
a
light
agenda,
let's
just
do
it
live
as
a
certain
tv
pundits
would
say
yeah.
So
now
it's
a
p2
and
like
these
kinds
of
things
are
definitely
gonna.
Be
this.
A
Place
to
look
for
api
breaking
changes
that
that
kind
of
helps
you
I
can
yeah.
Let
me
just
do
this
and
ideally
this
is
a
recreation
on
the
p1
project
board,
but
since
I
don't
really
update
that
too
often,
I
might
just
delete
that
project
and
just
unify
on
having
something
like
this,
unless
you
think
it'd
be
more
useful,
otherwise,.
A
That
being
said,
all
of
our
change
logs
should
also
include
any
sort
of
api
breaking
changes
that
could
probably
also
be
helpful
to
kind
of
go
over.
We
do
a
pretty
good
job,
making
sure
that
our
all
of
our
changes
are
captured
here.
Anything
in
the
change
column
is
likely
going
to
be
apr
backwards
and
compatible
same
here
with
the
removed.
So
these
are
things
that
are
just
going
to
be.
A
You
know,
obviously
removed
from
an
api
is
going
to
be
about
an
api
breaking
change.
Now.
Things
like
this
probably
didn't
actually
need
to
get
included
in
this.
Also,
what
happened
to
our
links,
these
used
to
link
really
well,
that's
again,
maybe
some
minutiae
that
a
maintainer
should
take
care
of
sorry
about
that.
D
They
stopped
doing
that.
I
now
have
to
put
in
the
full
url
of
the
pr.
A
A
It
is
moving
kind
of
fast.
The
trace
api
is
definitely
something
I
want
to
keep
focusing
on.
So
when
we
do.
A
That
yeah,
so
there's
not
too
many
coming
up
here.
This
is
definitely
one.
This
might
get
closed.
I
think
we
talked
about
this
in
a
little
while
this
is.
A
This
is
what
we
talked
a
lot
about
at
last
week's
meeting.
Oh
sorry,
no!
This
isn't
the
one
I'm
thinking
about!
There's
the
package
restructuring
one,
I'm
kind
of
surprised,
I'm
not
saying!
Oh,
that
wasn't
labeled
as
trace
like
that
makes
more
sense.
A
In
the
sdk
side
of
things,
so
it's
not
going
to
be
an
api
breaking
change,
so
yeah
yeah.
That
being
said,
I'm
kind
of
rambling
at
this
point,
but
if
you
do
find
something
that
you
do
find
mislabeled,
please
if
you're
an
approver
fix
it.
I
you
know,
I
take
a
first
pass
on
a
lot
of
the
stuff
we
can
use
to
help
and
then,
if
you're,
not
approver,
just
comment
on
it
and
say
that
you
think
that
should
be
labeled
differently
or
something
like
that
and
happy
to
adjust.
A
Yeah,
that's
a
good
one
and
yeah
like
feel
free
to
hit
me
up
and
get
her.
If
you
wanted
some
more
like
quick
interaction,
I'm.
A
Bit
not
in
the
seat
this
week,
but
next
week
I
should
be
a
little
bit
more
and
then
the
week
after
that,
definitely
some
more
but
yeah.
I
definitely
can
happy
to
work
with
you
on
that
and
then
we
also
have
triager
roles
in
the
project
if
you'd
wanted
to
take
on
some
more
responsibility
there,
but
it's
all
progressive,
you
know
whatever
whatever's
appropriate
cool
aaron.
I
see
you
added
something
about
open,
telemetry
proto
go.
C
Yeah
earlier
this
week,
I
found
that
I
was
about
to
go
and
recreate
all
of
the
logic
in
one
of
my
projects
to
generate
the
protobufs
and
and
whatnot
so
that
I
could
have
access
to
them,
and
I
figured
that
could
be
very
useful
and
somebody
two
months
ago
started
this
project
and
hasn't
done
anything
with
it
yeah.
C
A
It
is
the
person
who
asked
for
that
repo
to
be
creative.
Is
me,
so
I'm
the
one
to
also
blame.
A
Yeah
there's,
unfortunately,
a
lot
to
do
and
I'm
not
making
headway
some
days
but
yeah
cool.
This
is
definitely
the
right
sig
for
now
it
may
change
in
the
future
hint.
If
you
want
to
be
more
part
of
this
in
the
future,
we're
looking
for
volunteers
but
yeah.
I
definitely
am,
I
think,
the
most
responsible
for
this
code
base
I'll
try
to
prioritize
taking
a
look
possibly
tomorrow,
but
I
can
definitely
get
to
it
next
week
for
sure
it's
your.
As
you
pointed
out,
the
user.
A
Ask
and
demand
is
very
real
for
anybody
who
wants
to
use
the
proto
in
their
own
library,
and
so
it's
it's
a
really
important
thing.
So
I
I'm
really
excited
that.
You
submitted
something
I'd
love
to
take
a
look
at
it
and
there's
probably
a
lot
more
work
to
do
in
this
repo,
so
yeah.
Hopefully
we
can
get
some
momentum
going
on
this
and
I
apologize
again
for
not
getting
getting
access
to
it.
Yet.
A
I
love
it,
I
mean
that's
the
beauty
of
open
source
right.
I
really
appreciate
that
yeah,
absolutely
yeah
cool,
but
yeah
definitely
keep
coming
to
the
sig
meeting.
If
you
have
questions
given
that,
like,
I
think
that
there's
a
collect
or
there's
gonna
be
a
connection
here.
Ideally,
if
this
is
well
done,
the
collector
could
potentially
still
can
start
to
depend
on
this
as
well,
so
it
would
be
unified
in
that
central
place.
A
That
was
kind
of
the
end
goal
was
like
any
sort
of
place
that
wanted
the
hotel
otlp
like
to
have
it
rendered
in
that
one
spot
and
that'd
be
the
canonical
location
so
yeah,
but
for
right
now
I
think.
C
C
So
some
of
the
things
that
would
be
follow
on
from
this
that
pr
just
has
the
code
generation.
It
doesn't
have
the
generated
code
artifacts
to
keep
it
small
yeah.
It
also
expects.
C
If
you
look
at
the
the
mod
file,
you
should
see
it
there.
Oh
okay.
B
C
What's
in
the
hotel,
go
okay.
A
Yeah
yeah,
I
think
we
can
work
on
that.
I
feel
like
there
was
a
conflict
of
the
vanity
urls,
but
we
haven't
got
anything
to
discuss
what
the
name
is
is
kind
of
immature.
We
can
always
change
it
after
the
fact,
but
yeah
we
can
definitely
set
up
a
url
as
well.
That's
definitely
something
you
can
do
as
well.
A
Yeah,
I
think
there
was
one
that
was
kind
of
just
left
hanging.
Oh,
I
think
it
was
bogged
who
opened
it.
A
So
I
don't
think
he's
going
to
complain,
but
yeah
this
one,
okay
yeah.
That
was
something
different.
Okay,
we
could
definitely
take
care
of
all
that
and,
like
I
said,
I
think,
I'm
guessing
next
week.
I'll
have
a
little
more
time
to
look
at
this,
but
I
might
be
able
to
get
to
it
tomorrow.
So
I
really
appreciate
it
yeah
and
on
the
generation
side
of
things,
I
was
also
kind
of
wondering
how
we
wanted
to
structure
that
sorry
to
bore
the
other
people
on
the
call.
A
It's
just
been
sitting
on
the
back
of
my
mind,
because
one
of
the
other
things
was
like.
Do
we
want
to
start
generating
the
code
from
the
current
proto
specification,
or
did
we
want
to
backboard
all
of
the
old
previous
part
of
the
definitions?
And
then,
if
we're
going
to
do
that,
we
want
to
tag
that
repository
like
sequentially.
So
I
think
if
there's
probably
we
probably
want
to
do
the
latter,
we
probably
want
to
have
like
the
old
stuff
as
well.
A
So
if
somebody
has
an
old
version
that
you
wanted
to
depend
on,
it
could
be
generated
there.
I
don't
know
if
it's
like
the
most
useful,
because
if
they
have
an
old
version,
that
means
that
they
also
have
an
upstream
generated
version
of
it.
So
they're
gonna
have
conflicts
eventually
if
they
try
to
register
a
service.
So,
like
I
haven't,
thought
all
the
way
through
that
idea.
Yet
but
yeah,
if
you
have
any
ideas,
I'd
love
to
hear
them.
I.
C
My
like
my
general
gut
feeling,
is
potentially
generate
the
old
ones
based
on
the
tags
of
the
proto
repo
and
just
follow
along
those
okay,
but
I
don't
know,
I
also
did
not
include
any
kind
of
automation,
because
I
figured
get
the
the
core
issue
out
first
and
then
we
can
add
automation
to
it
later
we
can
add
checks
that
we're
not
checking
in
the
dirty
repository
or
any.
A
D
Given
we're
at
the
that
agenda
item
you're
welcome
to
just
do
it
cool
this
one's
real,
fast
and
and
it's
related
to
the
api
changes.
Last
time
I
checked,
the
opentelemetry.io
website
has
a
getting
started
guide
with
the
latest
v.16
0.16
changes
and
then
there's
krezmir's
document
in
the
in
the
repo
itself
that
hasn't
been
updated.
Is
anybody
doing
that,
or
is
that
something
I
should
just
do?
A
Yeah,
sorry,
can
you
help
me
walk
through
this?
It's
been
a
little
while,
since
I
thought
about
this
one,
so
I
definitely
know
that
the
upstream
open
telemetry
website
has
some
really
good
documentation
as
to
like
how
getting
started
and
that
kind
of
stuff
and.
A
Okay,
I
know
that
there
was
a
issue
that
he
had
opened
christmas
for
demarcation,
and
that
was
something
I
should
probably
close.
A
This,
I
think
it
was
this
yeah.
I
think
he
superseded
another
issue.
Oh
yeah,
here
we
go.
He
superseded
this
one,
yes,
and
I
don't
think
we
have
a.
I
think
this
is
exactly
the
question
you
were
just
asking.
Rich
was
like
currently
have
three
places
to
put
documentation
the
website
and
readme
and
then
package
documentation
as
well.
I
think
we
need
to
make
it
clear,
especially
for
people
like
yourself
who
are
asking
this
question,
that
you
know
after
the
fact
that
where
do
we
actually
want
things
to
go.
A
I
have
some
opinions.
I
really
like
to
not
duplicate
things.
I
really
like
the
readme
to
be
for
developers
not
necessarily
like
the
average
end
user
and
then
the
package
documentation.
I
I'd
like
that
to
be
developer-centric,
but
also
for
somebody
who's
going
to
be
using
the
code.
You
know
that
these
this
is,
I
think,
we're
like
iana
was
pointing
out
is
like
the
number
one
place,
that
a
lot
of
go
developers.
A
Look
for
how
to
use
our
api
as
well
as
how
they
you
know,
structure
their
code
as
well
is
is
from
the
godox
themselves,
and
I
think
we
can
do
a
really
good
job
here.
Yeah
I'm
seeing
some
thumbs
up.
A
A
It's
going
to
be
a
great
place
to
link
for
blogs,
because
it's
hypertext
at
that
point,
and
so
like
I
think,
that's
something
we
should
try
to
unify
on
the
readme
can
be,
I
think,
more
developer,
centric
with
bare
bones
of
very
canonical
things.
A
D
I
don't
I
don't
I.
I
also
do
not
like
the
duplication
and
short
of
writing,
something
that
automatically
pulls
in
the
stuff
from
our
readme
and
stuffs
it
on
the
open
to
line.
You
know
that
just
seems
brittle
and
would
need
a
maintainer
and
no
thank
you
so
yeah.
I
like
the
idea
of
draining
the
readme
and
shoving
the
user-friendly
sort
of
telestory
thing
up
to
open
telemetry.
I
o
and
then
getting
the
api
documentation
where,
where
it
belongs
in
in
in
package.docker,
whatever
yeah.
A
Yeah-
and
I
think
the
only
other
thing
I
would
add
to
the
package
documentation,
this
is
like
we
got
to
stop
putting
in
go
code
in
that
documentation.
We're
pretty
bad
about
that,
because
there's
really
good
example.
Tests
where,
if
you
build
the
actual
go
documentation
will
put
the
code
exactly
where
you
want
it,
and
then
it
gets
checked
by
the
compiler
versus
like
us,
trying
to
handwrite
it,
which.
A
Again,
there's
a
really,
you
know
classic
place
where
we've
had
four
different
users
come
by
and
go
like
this
doesn't
compile
anymore,
we'll
go
like
yeah,
okay.
That
was
a
bad
idea.
Another
thing
is
there:
is
this
developer
style
guide?
A
I
think
that
this
is
a
little
bit
more
of
like
we
might
be
able
to
split
these
out
a
little
one
thing
that
we
talk
a
lot
about
here
is
this
configuration
which
probably
needs
a
revisal
based
on
what
we're
doing
but
like
I
think
it
was
another
option.
Just
like
you
know,
just
talk
about
like
project
styling
guys
for
other
developers.
A
If
you
want
to,
you
know,
contribute
to
the
project
so
that
it's
easier
to
understand
some
of
the
past
decisions
that
we
made
but
yeah
it
just
kind
of
adds
to
the
the
cacophony
of
documentation.
Here.
I
think
if
we,
if
we
do
a
good
job
laying
out
like
what's
happening
here
like
it,
should
be
a
little
bit
better
and
we
can
rip
some
things
out,
but
yeah.
If
I
heard
you
correctly
rich,
you
were
talking
about.
Maybe
taking
this
on.
D
A
Yeah
the
project
would
love
it
so
yeah
it
just
if
you
do
want
to
be
sure
just
to
comment
on
this
issue,
maybe
some
of
the
direction
I'm.
I
just
read
this
that
this
is
something
that
people
are
looking
to
comment
on,
but
like
there's,
not
a
really
clear
direction
in
this
issue
yet
so
I
wouldn't
necessarily
go
off
and
do
this
work
without
making
it
clear
in
the
issue.
A
What
we're
going
to
actually
accomplish,
I
think,
is
a
pretty
good
idea,
which
I
should
probably
leave
a
note
in
here
which
I'll
try
to
do
after
the
meeting,
but.
A
Cool
yeah,
like
I
was
saying,
I
think
it
might
be
a
little
bit
of
a
short
meeting
here,
but
I
plan
on
that
being
a
big
change
in
the
upcoming
future,
because
my
time
is
going
to
be
much
more
committed
to
this.
I
think
going
forward,
so
yeah
pretty
excited
about
that
and
pretty
excited
to
work
with
you
all
to
continue
producing
this
yeah
aaron.
A
If
I
haven't
taken
a
look
at
that
pr
for
some
reason
feel
free
to
ping
me,
I
can
get
distracted
as
you
can
tell,
but
that's
an
important
one.
That's
been
on
hold
for
two
months,
so
I
want
to
try
to
prioritize
that.
A
Oh
yeah,
mr
alias
israelis,.
C
A
A
Yeah
yeah,
I
think
things
you
do
you
know
decades
ago,
that
you're
just
like
wow
that
was
kind
of
anyways.
At
this
point,
it's
a
branding
issue
right
right,
yeah
like
I
can't
move
away,
and
I
can't
not
yeah.
So
that's
just
what
it
is
yeah
my
favorite
other
one
is
my
friend's
vitamin
move
so
given
this
is
on
youtube
now
he's
on
youtube.
So
this
is
pretty
great
it'll
make
my
day
well
cool.
I
think
that's
it!
I'm
gonna
just
take
a
look
around.
Anyone
else
have
anything
else.
A
They
want
to
talk
about
awesome.
Well,
thank
you.
Everyone
for
joining
today.
The
metricsig
is
coming
up
in
20
34
minutes.
So
if
you
have
time,
please
stop
in
there.
The
discussions
have
been
pretty
active
lately
and
could
definitely
use
input
from
a
lot
of
different,
diverse
sources.
So
if
you
have
an
opinion,
please
stop
in,
but
otherwise
I'll
see
you
all
next
week
and
david.
A
If
you
show
up
at
the
10am
one
it
might
be,
since
it's
also
more
active
on
that
one,
we
could
bring
it
up
again
next
week,
I'm
really
ready
to
sail
okay,
yeah,
we'll
we'll
check
in
and
keep
going
until.
Then
thanks
everyone
and
talk
to
you
later
cool
thanks,
bye.
Everyone.