►
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
I'm
doing
okay,
I
just
finished
taking
a
look
at
all
these
issues,
all
these
repos
and
it
really
doesn't
seem
to
be
that
much
so
I
was
about
to
call
this
one.
A
Okay,
yeah
it
it's
just
one
open
issue
on
the
rename
default
branch
domain
on
the
proto
repo
everything
else
is
taken
care
of.
I
think
we
punted
on
some
metrics
issues,
I'm
going
to
speak
with
j
macd
later
this
afternoon
about
tracking
the
metrics
issues
following
on
a
conversation
from
the
metric
sig.
So
I
was
going
to
take
care
of
that
specifically
later
cool.
A
B
B
A
B
This
is
one
of
those
ones
where
the
spec
change
was
kind
of
pushed
through
pretty
quickly.
I
think,
before
everyone
actually
got
a
chance
to
really
give
it
thought
and
then,
as
soon
as
the
follow-up
happened
to
rename
things
everyone
was
like
this
is
terrible.
We
need
to
rethink
this
so
we'll
see
how
that
falls
out.
B
A
Okay
and
then
this
one
is
a
pr
as
well.
B
B
C
B
A
A
And
this
this
small
one,
I
think
bagnan's
already
got
a
pr
on
it.
Open,
proto,
just
ringing
branch
out.
Yes,.
C
B
My
opinion
on
the
second
one,
so
the
one
on
this
name
I
prefer
trace
instead
of
traces,
I'm
not
going
to
hold
it
up,
though
I
mean
in
the
end,
it's
a
name
whatever
I
don't.
I
don't
care
a
huge
amount,
but
it
is.
It
is
a
weird
change
and
it's
unfortunate
that
the
collector
chose
a
poor
name
in
the
first
place.
C
Yeah
yeah,
so
I
guess
that
that
that
makes
sense,
and
I
I
support
what
tigran
has
been
saying.
But
now
I
just
realized
something
well
not
today,
not
now
earlier
today
that
I
don't
know
whether
this
is
actually
something
something
that
I
know
that
the
collector
is
using
traces
internally
and
some
for
some
configuration
stuff.
But
I
am
not
sure
that
it's
using
these,
you
know
in
environment
variables,.
B
C
B
Yeah
yeah,
I
don't
know
how
they.
C
B
B
Yes,
and
I
don't
from
what
I
remember-
and
this
is
a
couple
years
old-
the
ruby
grpc
implementations
are
not
very
good,
so
they're
going
to
be
kind
of
stuck
with
the
default.
That's
not
what
the
community
wants.
B
B
C
And
I
am
worried
also
that,
for
example,
let's
say
that
ruby
wants
its
default
to
be
some
transport,
but
they
implemented
another
one,
and
so
it's
like
they
already
know
which
one
they
want
to
go
for
with
default,
but
that
can
what
they
can
to.
They
cannot
use
it
because
they
don't
have
it
yet.
So
it's
like
these
kind
of
situations.
You
know
it's
like.
B
C
B
C
Yeah
yeah,
okay,
let
me
think
about
that
and
probably
try
to
follow
up
yeah.
Okay,
thank
you!
So
much
for
the
information.
Let's
see
what
happens,
let's
see
if
we
can
come
to
an
agreement
yeah
we.
I
think
that
not
only
you
also.net
wants
to
release
it.
You
know
to
release
tracing
like
asap
acip.
So,
let's
see
what
happens
all
right.