►
From YouTube: 2021-12-16 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
After
all,
this
jumping
around
I'm
not
even
sure
if
we
have
any
topics
for
today.
Maybe
I
was
hoping
aaron
would
be
here
and
we
could
talk
about
the
metrics
implementation
with
that's
happening,
but.
A
Yeah
I
mean
there
is
an
issue,
but
I
can't
so
my
I
don't
know
if
the
google
calendar
gets
updated
consistently,
like
the
link
I
had
this
morning
until
I
went
to
the
open,
telemetry
calendar
specifically
and
click
through
the
hotel
calendar
was,
it
was
using
an
old
link
in
my
gmail
calendar,
so
I
don't
know
what
to
do
about
it.
B
B
Will
join
the
meeting
a
few
minutes
late?
Someone
else
has
any
topics
doing.
C
Hey,
I
I
wanted
to
ask
him
something
for
other
projects:
that's
under
the
open,
telemetry
arc.
So
to
give
you
some
context,
there
was
a
project
that
google
donated
to
the
open
telemetry
that
that
basically
adds
the
trace
context,
information
and
and
other
information
to
the
sql
query.
So
they
want
to
release
a
new
packages
with
the
open,
telemetry
namespace
and
an
issuer
deprecation
message
to
the
google
cloud.
C
So
the
maintenance
from
that
team-
they
they,
you
know
they
want
to
use
pipeline
secrets
so
that
they
can,
you
know,
publish
the
initial
packages.
C
So
basically,
they
that
that
team
needs
the
test
pi
by
token
and
the
pipe
token
so
that
they
can
release
it.
From
from
that
repo.
A
I
mean
there's
nothing
that
prevents
them
from
releasing
the
from
releasing
the
package
under
that
name.
Right
like
it's,
not
it's
not
a
package,
that's
owned
by
us
anywhere.
A
C
So
so
far,
the
packages
that
published
is
under
the
like
google
cloud,
but
since
it's
moved
to
the
open
telemetry
so
on
the
open,
telemetry
version
hasn't
been
released
like
any.
This
is
going
to
be
the
very
first
version.
A
Oh,
I
see
yeah
I
mean
I
I
see
I
guess
I
would.
I
would
recommend
that
if
we're
going
to
be
releasing
it
from
like
using
the
same
account,
we
should
probably
have
the
package
live
in
the
hotel
can
trip
repo,
but
if
they
want
to
continue
releasing
it
from
like
a
separate
repo
that
they
manage,
then
they
should
just
release
it
under
their
name
with
their
credentials.
C
Yeah,
so
this
was
brought
it
up,
so
I
one
of
the
solutions
was
to
you
know,
move
the
code
to
the
instrumentation
libraries
and
then
get
them
released
as
a
part
of
the
regular
open,
telemetry
python
contributions,
but
there
is
uncertainty
in
terms
of
whether
or
not
that
that
whole
projects
moves
in
its
own
direction
instead
of
having
it
coupled
with
the
instrumentations.
C
We
have
so
there's
some
uncertainty
there
and
I'm
not
sure
on
the,
and
it's
also
not
clear
if
the,
if
there
will
be
any
changes
in
the
specs
for
those
people
commented
on
the
process.
What
or
what's
going
to
be,
you
know
getting
it
merged
to
the
open,
telemetry
specification.
C
So
that's
that's.
Why,
like
one
of
the
people
who
is
creating,
that
is
he
he
wanted
me
to
ask
you
know
if
he,
if
he
can
get
the
secret
shared
so
there,
so
that
they
can
release
the
initial
version.
A
Yeah
I
mean
maybe
this
is
something
that's
worth
having
a
discussion
once
in
in
january,
once
the
maintainers
are
all
back,
and
maybe
someone
from
the
sql
commenter
group
can
attend
one
of
these
six
take
meetings
to
talk
about
it.
It
just
feels
like
right
now,
there's
there's
just
this
group
that
we
don't
have
very
much
interaction
with
that
is
planning
on
releasing
something
and
we
have
no
oversight
into
what
what
is
being
released.
So
I
would,
I
would
suggest
we
shouldn't
use
the
same
credentials,
but
that's
my
preference.
B
Yeah,
I
have
that,
will
I
don't
think
that
just
sharing
their
credentials
is
like.
B
C
I
I
I
think
it
may
be,
it
makes
sense
to
you
know,
make
decisions
once
other
two
maintenance.
Also
here
I
I
will
share
this
information
with
him
and
see
I.
I
would
also
ask
him
to
join
in
these
meetings
in
the
next
week
meeting
so
that
we
can
have
a
discussion
on
a
plan
about
it.
How
we,
how
we
go
about
it.
B
Yeah,
that
sounds
that
sounds
great.
Thank
you.
D
Hey
sorry,
I
joined
a
little
late.
Did
you
need
anything
from
the
google
team
like
the
credentials
for
this
people
commenter,
or
was
that
unrelated.
C
So,
like
supra
jyoti,
he
wanted
to
release
the
like
initial
version
of
the
sequel
commenter
on
on
pipeline.
He
asked
me
like
if,
if
we
can
share
the
secrets
by
secret
so
that
and
they
can
release
it
and
the
open
telemetry
simple
carmenter
project
from
this
seek,
so
they
wanted
secret
from
this
scene.
That's
that
that
was
the
request.
D
Okay,
the
other
thing
I
wanted
to
call
out
was:
you
can
also
make
scope
tokens
on
pipe.
I
don't
know
if
you
guys
already
discussed
that,
but
you
don't
have
to
share
the
same
credentials
that
way,
so
you
could
publish
from
the
like
open
telemetry
account,
but
we
don't
have
to
actually
share
the
credentials
and
they
won't
be
able
to
publish
any
of
the
open
telemetry
packages
from
the
with
their
token
they'll
be
able
to
publish
the
sql
commenter
or
whatever
you
want.
C
Are
you
saying
that
we
can
have
a
different
set
of
tokens
under,
under
the
same
account
that
sql
commenter
can
use
okay
so
either
way
the
other
two
maintainers
also
have
to
say
like
we'll,
have
something
to
say,
and
then
they
can.
Then
we
can
design.
What
to
do.
D
B
All
right,
we
don't
have
watching
the
agenda
today.
Aaron.
Is
there
something
that
you're
going
to
talk
about
in
the
metrics?
Probably.
D
D
So
I've
this
was
like
a
little
bit
out
of
date,
so
basically,
what
I
did
was
I
added
two
columns,
just
put
it
by
api
and
sdk,
and
then
I
added
some
more
issues
from
based
on
like
the
design
dock,
so
these
ones
should
in
theory,
be
up
to
grab
in
the
unassigned
columns,
and
then
these
assigned
slash
and
progress,
which
would
be
ones
that
people
are
already
working
on
like
regardless,
whether
you're
working
on
them.
If
it's
a
sign,
it
should
be
in
this
call.
D
Here
we
go
so
this
one
links
to
like
the
dock
and
has
a
little
bit
of
requirements
for
marking
the
issue
as
resolved
so
like
we
can,
should
be
able
to
do
these
up
amongst
ourselves.
Anybody
who
wants
to
work
on
metrics,
but
I'd
recommend
just
like
leaving
leaving
things
unassigned
as
long
as
you
can,
until
you're
ready
to
pick
something
up
so
that
we
so
that
we
have
like
a
big
open
pool
to
be
able
to
choose
from
for
anybody
else
to
work
on
stuff.
B
B
Are
the
columns
updated.
B
D
Regarding
issues,
oh
sorry,
the
issues,
so
they
I
changed
it,
so
these
won't
be
added
automatically
and
unfortunately,
there's
no
way
to
like
make
it
automatically
add
ones.
With
a
certain
tag.
It's
pretty
cool
yeah,
I'm
not
unless
somebody
else
knows
how
to
use
the
github
projects
better
than
me.
It
doesn't
seem
like
you
can
do
that,
but
when
you
do
add
a
pr,
it
will
automatically
show
in
this
review
in
progress
and
then.
D
B
All
right,
great,
hey!
So
so
far
we
have
one
pr
in
progress,
which
is
this
one
with
factory
aggregations
and
addressing
the
last
comments
that
uranus
we
can't
have
it.
I
I
think,
that's
not
too
far
away
from
getting
merged,
and
I
think
that
was
the
last
pr
of
all
the
refactorings.
B
Because
there
are
three
refactoring
pr's
yeah
and
we
have
merged
two
already.
This
is
the
last
one.
So
after
this
one
is
done,
the
pr
in
the
sequence
of
6prs
that
would
follow
will
be
this
pr
that
added
measurement
and
measurement
processor,
which
is
now
named
measurement
consumer.
I
believe
I
think,
after
these
refactorings
we
we
agreed
that
we
will.
B
I
mean
work
with
prs
directly
on
main,
instead
of
trying
to
just
stack
them
all
together,
right
good.
I
saw
some
of
the
issues
here
and
some
of
them,
I
think,
depend
on
other
issues.
D
Yeah,
I
think
a
few
of
them
do
so
that
the
idea
was
to
either
just
tackle
the
ones
that
don't
have
dependency
first
or
to
just
like
do
like
a,
if
possible,
do
like
a
stub
implementation
or
something
like
that
and
then
wire
it
together
in
a
separate
pr.
B
B
Okay
yeah.
I
I
just
want
to
share
this
plan
that
I
have
with
you
to
make
sure
that
these
are
lines.
D
Yeah,
that
makes
sense.
I
think
I
I
try
to
make
these
as
minimal
as
possible,
so
like
this
one
doesn't
require
implementing
the
default
measurement
consumer,
like
the
the
one
that's
documented
in
the
design
dock.
D
It's
more
just
like
create
the
interface
make
like
an
empty
stub
implementation
and
then
adding
it
to
the
instruments
that
the
measurements
flow
into
it,
which
which
that
part
we
can
test
and
then
from
then
on,
like
the
default
one,
we
don't
need
to
test
it
with
regard
to
the
instruments
as
well
already
have
coverage
for
that.
Just
test
that
unit.
B
All
right,
that's
great,
the
when
I
was
developing
these
sequence
of
prs.
I
realized
that
many
times
to
add
a
class
and
to
be
able
to
test
it.
You
need
to
add.
B
A
B
D
Okay,
so
yeah
with
that
said,
I'm
going
to
work
on,
I
think,
after
since
you
have
part
of
it
in
this
refactor
aggregations
pr,
diego
after
that
one's
merged.
I
think
I'm
going
to
tackle.
A
D
D
We
have
exporter,
it's
it's
a
little
bit
confusing
the
spec
honestly
what
they
did
in
java
is
they
made
the
metric
reader,
the
the
poll
exporter,
so
you
would
just
subclass
the
metric
reader
and
use
that
and
then
every
time
like
your
http
endpoint
gets
hit,
you'd
call
collect
and
then
wait
and
then
send
the
metrics
back
and
the
http
response.
D
D
Yeah,
I
think
it's
very
vaguely
defined
in
order
to
like
let
you
have
a
little
bit
of
freedom
with
the
implementation.
So
I
imagine.
A
D
Yeah
all
right
cool.
Do
we
want
to
like
assign
more
of
these
right
now
or
should
we
just
people
can
go
through
online
offline
and
either
comment?
If
you
don't
have
permission
to
assign
yourself
one
or
just
assign
it
to
yourself,
yeah.
B
A
There
was
an
issue
that
was
open
in
the
python
contrib
repo
around
whether
or
not
there's
going
to
be
a
release.
I
don't
know
if
there
was
a
plan
for
a
release
or
if
we're
too
late
for
releases
now,
diego
you
might.
You
might
know
this.
B
A
Okay,
I'll
just
I'll
ping
away
on
the
issue,
then
my
understanding
was
that
he
was
out
as
of
as
of
yesterday.
So
I
don't
know,
I
don't
know
if
he
was
saying
hey,
I
want
to
do
a
release
and
then
I'm
going
to
go
on
holiday
and
hope
that
the
release
happens
or
or
if
it
was
oh,
if
he's
still
around
so
anyways,
it
was
just
an
issue
that
came
up.
So
that's
why.
D
B
Well,
if
not
usually
when
so
far
when
someone
new
joins
the
sick,
we
ask
for
that
person
to
introduce
themselves
and
let
us
know
a
little
bit
about
themselves
and
what
brings
them
to
these?
It's
totally
optional.
I
don't
know
it's.
Sometimes
it
puts
people
on
the
spot,
but
if
you
feel
like
it,
you
can
go
ahead.
E
Sure
my
name
is
rhys,
I
am
with
new
relic.
I
just
joined
the
open
telemetry
team
here
a
few
weeks
ago
actually-
and
I
was
in
support
before
that-
supporting
some
of
our
language
agents,
and
so
I
python
was
one
of
the
languages
I
wanted
to
learn
and
we
don't
currently
have
a
python
engineer
on
a
team.
So
I'm
trying
to
fill
those
shoes
but
yeah.
Just
I
wanted
to
come
in
and
meet
you
all
and
see
what
topics
are
the
hot
topics
at
the
moment.
B
D
B
You
also
need
to
introduce
yourself.
That's
very
sorry.
I
always
forget
hello,
I'm
diego!
I
work
for
lightstep.
I've
been
working
for.
We've
opened
one
two
python
for
a
little
less
than
three
years.
I
think
I'm
one
of
the
maintainers
right
now,
I'm
pretty
much
working
on
the
metrics
part
of
the
project.
B
You
can
contact
me.
Yes,
luck
or
via
github.
A
Hey
I'm,
I'm
alex
I've
been
working
with
open
telemetry
for
a
little
bit
over
two
years,
former
maintainer
of
the
python
project.
Now
I'm
just
kind
of
an
approver,
and
I
hang
out
here
one
once
in
a
while.
I
I'm
also
at
lightstep
and
yeah
feel
free
to
ping
me
with
whatever
questions
you
have,
I'm
always
around
so
welcome.
Thank
you.
D
I
guess
I
can
go
my
name's
aaron.
I
work
at
google,
been
working
on
open
telemetry
for
open
source
python
for
about
a
year
and
a
half.
I
think
I
am
in
a
an
approver,
so
I
can
approve
prs
if
you
ever
need
any
help
and
yeah
that's
about
all,
I'm
also
working
on
the
metric
stuff
a
bit
and
if
you're,
not
on
slack,
you
should.
You
should
join
the
cncf
slack,
because
if
you
ever
need
any
help
between
ziggs
or
something
like
that,
you
can
always
reach
out
there.
E
C
C
Hey,
I
am
also
one
of
the
approvers.
I
have
been
with
this
project
for
about
a
year
and
a
half.
I
guess
I'm
mostly
working
with
the
python
team
on
sometimes
other
successful
and
that's
about
it.
A
And
yeah,
if
you,
if
you're,
if
you're
new
to
python
and
new
to
the
project,
we
we
would
love
your
input
on
how
we
can
make
this
project
better
for
newcomers,
for
even
if
it's
just
like
updating
how
our
contributing
guidelines
are
lacking.
Some
of
the
details
yeah.
Maybe
some
of
us
have
been
in
this
for
too
long
that
we've
forgotten
what
it's
like
to
not
be
in
it,
so
we
just
all
run
all
these
commands
that
we're
familiar
with
and
yeah
anyways
help
is
welcome.
E
I
do
have
a
question:
is
there
an
updated
python
example?
Somewhere?
I
saw
one
from
ted
at
lightstep,
but
it
was
pretty
it
was.
I
don't
think
it
had
been
touched
in
like
over
a
year,
and
I
mean
I
was
able
to
finally
get
my
choice
of
showing
up
in
new
relic,
but
I
don't
know
I
was
like
having
trouble.
I
couldn't
find
like
any
more
update
examples.
B
Yeah,
I
think
we
have
this
with
examples.
I
pissed
the
link
here.
I
I
hope
those
examples
are
working.
E
Okay,
this
yeah,
the
second
one,
was
what
I
was
using.
A
Yeah,
I
think
the
link
that
aaron
sent
to
read
the
docs
is
also
super
helpful.
Hopefully.
B
E
E
I
don't
know,
maybe
it
wasn't
picking
up
my
maybe
I
didn't
set
it.
I
mean
everything's
working
now
so
like
thank
god
but
yeah
for
a
while.
I
was
like
what
am
I
doing
wrong
and
then
I
I
wasn't
sure
how
to
get
logs
to
look
at
what
was
happening
like
if
it
wasn't
picking
up
like
did
I
set
the
wrong
environment
variables
or
what,
and
so
I
don't
know
if.
E
I
think
what
I
have
was
exactly
what
almost
exactly
what
was
in
the
example
on
the
getting
started.
Page
yeah.
E
E
E
A
B
Yes,
there
is
no
meeting
next
week,
all
right
and
the
following
week.
We.