►
From YouTube: 2021-07-14 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).
B
I
I
think
I
I
just
noticed,
and
I
mean
there
was
a
meeting
going
on
for
open
television,
accommodate
open,
telemetry
internal
microscopy.
A
B
Yeah,
okay,
I
think
I'll
probably
just
share
my
screen.
I've
put
I
had
couple
of
agendas.
I
put
that
I'll
just
share
my.
B
B
Okay,
one
minute
or
you
can
compare,
I
think
you
can
just
note
on
your
arena
points
whether
you
can
start
discussing
meanwhile.
So
one
one
thing
which
I
was
just
just
thinking
about
today
was
that,
should
we.
B
Move
the
monday's
meeting
time
this
same
as
that
for
witness
day,
because
I
mean
I
just
I've
been
seeing
the
current
current
number
of
attendees.
I
mean
I
just
feared
that
probably
next
monday
I
mean,
if
max
is
saying
that
max
is
also
going
to
move
out
of
the
team
and
he
may
not
be
joining
he
may
or
may
not
join.
We
don't
know
the
status
we
should.
B
A
C
A
B
And
yeah,
I
think
you're
right
I
mean
that
we
may
not
be
covering
the
time
zones
fully,
but
I
mean
I'm
just
concerned
that
we
should
not
have
any
week
where
there
is
no
meeting
really
happening
nobody
joining
and
then
we
are
just
missing
out
any
discussions.
So.
C
B
Going
forward,
probably
if
we
see
more
attendance
people
asking
for
the
change
in
the
time
zone
and
once
I
move
there
hopefully
next
month,
if
all
goes
well,
then
probably
we
can
always.
We
can
change
that
into
different
time
zones
as
it
is
there
right
now.
A
Yeah
for
this
one
yeah,
I
saw
you
updated
the
zoom
link
right.
The
meeting
link
in
our
repo
yeah
there's
another
another
link
showing
up
in
the
google
cart
public
calendar.
That's
open,
telemetry
public
calendar.
Usually
I
I
get
the
meeting
link
there.
I
think
this
one
has
not
been
updated
and
I
think
we
will
better
update
it.
B
So
when
did
you
see
because
I
did
update
it
so
mondays
was
updated.
All
I
mean
I
didn't
update
mondays
with
the
same
link
so
today
I
think
more
today,
probably
your
early
morning
time
I
would
have
updated
this.
I
think
somehow
I
missed
out
this
week
wednesdays.
So
right
now
I
see
the
updated
one.
I
mean.
C
A
Link
and
we
went
to
another
meeting
yeah.
B
C
B
A
That's
right,
but
I
think
I
tried
the
last
one
right.
The
last
link
connect
to
the
meetings
that
one
should
we
update
that
as
well.
B
C
C
B
A
Yes,
I
can
see
your
screen,
yes,
and
I
think
there
are
two
meeting
links
right,
the
first
one
and
also
the
the
start,
the
last
one,
the
third
one.
I
think
that
one
needs
to
be
updated,
because
the
last.
B
A
That's
reunion,
you
know
just
in
the
dialogue,
not
this
one,
they
all
pop
the
pop-up,
that's
three
url
in
the
pop-up,
the
last
one
is
connect
to
the
meeting
connect
to
the
meetings,
above
just
about
a
a
little
down
description
in
description
section,
the
second
one
this
one.
B
B
B
Okay,
let
me
do
it
for
all
the
meetings
just
to
make
sure
I
don't
send
it,
but
let's
send
it
so
let
people
know-
and
it's
just
a
second
and
probably
in
that
case
I
may
have
missed,
because
this
is
the
meeting
also
I
changed
more
details.
C
B
B
B
B
B
B
B
B
Yes,
that's
for
internal
development,
it's
purely
for
internet
logging.
So
that's
what
I
kept
the
macros
and
internal
log
error
and
all
these
things.
Okay.
So
the
thing
was
that
initially,
it
was
only
for
the
error
handling,
but
max
wanted
it
more
as
a
log
handler,
and
then
you
want
you
wanted
me
to
add
so
earlier.
It
was
just
dumping
the
errors,
but
now
you
wanted
to
have
log
debug,
log,
log
warning
and
everything
all
those
standard
logging
macros,
which
we
have
for
normal
serious
vlogging.
B
So
I
did.
I
did
some
part
of
those
things
I
already
covered
that
covered
it,
and
I
mean
most
of
the
max
comments
are
already
taken
care
in
this.
The
only
thing
which
was
left
was
that
he
wanted
to
have
more
of
a
c
style,
c
style
logging.
This
uses
the?
U
this
uses
o
stream
for
the
logging,
so
just
like
how
the
way
we
do
it,
logging
for
hddc
out
the
same
thing,
the
same
same
syntax,
same
formatting.
It
will
use
for.
B
That
was
a
personal
choice,
so
I
think
he
max
already
was
so
that's
how
the
cpp,
the
1ds
c,
plus
plus
sdk,
does
has
the
c
style
logging
and
he
has
his
own
inclination
preference
for
that
which
makes
sense,
but
I
think
probably
this
is
more
of
a
sequence
practice.
B
B
Hd
log
api
in
sdk,
where
we
log
it
using
key
value
pair,
so
even
that
is
also
added,
so
it
works.
Fine
max
had
wanted
to
make
it
more
closer
to
how
1ds
cpu
express
works
its
most
is.
It
was
his
most
of
a
personal
choice
which.
C
B
B
B
A
Yes,
yeah
because
I
saw
it
it
shows,
I
think
almost
identical
code
ratios
up
a
few
times.
B
A
Compiled
as
a
as
a
library
so
and
the
update
one
library
may
may
miss
to
update
the
other
one,
so
I
think,
could
we
just
extract
it
into
a
separate
library,
the
full
library
it
doesn't
involve
any
in
any
open
telemetry
configuration
codes
just
like
normal
normal
example
code
and
all
their
configuration
codes
and
shows
up
in
their
main
menstruals
of
their
for
each
example.
I
think
that
would
be
helpful.
B
A
B
And
yeah-
and
apart
from
that,
I
think
probably
you
can
just
look
into
if
there
is
any
other
pr
which
is
pending
or
any
issues
which
probably
we
need
need
some
attention
and
there
was
one
more
we
are.
I
think
this
reminds
me
the
semantic
convention
attributes
for
traces.
B
B
B
B
A
B
Yeah,
I'm
just
waiting
for
him
to
close
it.
Otherwise,
I'm
just
being
him
and
this
one
I'm
not
sure
what
exactly
we
have
to
do,
the
second
one
he
was,
I
mean
I
think
he
just
said
that
he's
not
able
to
just
so
this
person.
B
He
says
that
he,
even
though
he
has
this
vc
package
as
this
volt
chain
file,
and
that
vc
package
has
already
installed
that
the
thrift
package
is
already
installed
through
vc
package,
but
still
is
still
I
mean
our
build
is
not
able
to
recognize
that
package,
which
is
strange
because
it
works
fine.
B
B
B
B
A
Both
issues
are
from
the
same
same
user,
right.
A
B
B
B
A
Does
it
block
our
ga
release
or
face
oh.
B
The
problem
is
right
now
that
we
cannot
top,
we
cannot
upgrade
okay,
so
we
did.
We
did
discuss
last
time
to
start
supporting
to
drop
support
for
the
gcc
photo
date.
Yeah
as
max
was
saying
and
then
we'll.
If
we
stop
support
for
that,
we
can
easily
increase.
B
A
I'm
thinking
I
think
we
discussed
on
this
already
an
option.
Is
we
probably
make
the
increase
our
default
grpc
version,
but
if
the
user
is
detected,
if
the
user
is
building
with
gcc
4.8,
we.
B
A
B
Yes,
the
problem
is
that,
if
we
do
that,
that
means
that
we'll
we'll
start
supporting
the
the
latest
version
of
grpc,
so
okay
yeah.
So
if
we
start
supporting
that
the
problem
is
again
the
basal
version.
That's
what
we
need
some
expertise
for
for
weasel
in
that.
So
because,
if
we,
if
we
increment
the,
if
we
increment
the
grpc.
B
So
so
yeah,
so
I
mean
we
have
to
decide.
If
we
have
to
support
different
versions
of
grpc,
then
there
is
a
dependency
of
bazel
version,
also
with
grpc,
so
like
bazel,
four
work,
so
the
older
version,
so
bazel
four
does
not
work
for
the
lower
version
of
grpc.
B
Somebody
has
to
take
care
of
basal
build
also
other
will
either
when
we
want
to.
We
don't
increment
the
basal
build
the
basal
version,
but
but
anyway
we
need
expertise
and
basal,
because
in
this
kind
of
conditional
grpc
version
also
somebody
else.
Somebody
should
help
us
how
to
delete
configure
that
in
bazel
we
can
do
it
in
cmake,
but
how
to
configure
that
in
bazel.
We
don't
know.
B
Yeah
so
yeah,
I
got
your
point.
I
think
that's
a
good
solution
to
have
a
conditional,
grpc
version
built
based
on
the
type
of
based
on
the
compiler.
We
are
using.