►
From YouTube: 2021-07-21 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
B
A
B
A
B
B
D
E
B
F
E
We
can
cool
okay,
real,
quick
before
we
get
started.
I
just
want
to
say.
I
know
that
I
haven't
been
very
responsive
over
the
last
two
weeks.
I've
had
some
complications
related
to
some
dental
work,
and
I
had
a
bunch
of
time
off
of
work
unexpectedly,
so
I
think
things
are
going
better
now
and
I
should
be
more
responsive
and
I'm
trying
to
catch
up
on
the
backlog
a
little
bit,
but
just
so
you
guys
are
aware.
E
I
I
know
that
I
haven't
been
all
that
responsive
over
the
last
week
or
so.
First
item
on
the
agenda
that
I
have
today
is
release
version
24..
I
was
going
to
make
the
pr,
but
before
I
did
that,
I
just
wanted
to
make
sure
that
everybody
was
okay
with
that.
Nobody
has
a
reason
that
I
shouldn't
or
some
pr
that
I
should
be
waiting
for.
E
I'm
sure
that
it
probably
does
it's
been
a
while,
since
we've
released,
it's
been
yeah
almost
20
days,
so
I'm
I'm
sure
that
it
probably.
E
E
Okay,
so
it
sounds
like
nobody
has
any
objections.
I
want
to
say:
welcome
to
rono
as
an
approver.
You've
been
doing
a
great
job,
helping
us
out,
and
I
fully
support
promoting
you
to
ruber.
So
welcome
and
congratulations.
E
E
E
The
so
valentine
the
the
last
message
that
you
posted
that
was
more
or
less
what
I
was
thinking.
It's
fewer
packages
and,
in
my
opinion
the
names
are
a
little
bit
less
confusing
the
the
message
that
bark
sent
is
roughly
the
same,
also
slightly
different
names.
E
I
think
I
would
be
fine
with
either
of
these.
I
probably
would
prefer
what
valentine
listed
here,
but
I
would
be
fine
with
either
of
these
renames
does
anyone
else
have
strong
feelings
about
this?
I
know
that
the
original
package
names
rauna,
you
suggested,
so
I'm
not
sure
if
you
have
strong
feelings
in
this
area
or
if
you've
been
paying
attention
to
this
conversation,.
B
I
have
a
bit-
and
I
was
confused
in
the
beginning
when,
when
I
was
first
introduced
to
in
telemetry,
but
now
it's
kind
of
difficult
for
me
to
relate
to
the
roano
three
months
ago,
but
as
explicit,
we
can
make
it
it's
probably
easier
for
the
for
the
newcomers.
B
Yes,
it
might
be
more
typing,
but
hopefully
we
can
kind
of
solve
that
better
by
actually
creating
meta
packages,
or
you
know
like
bundles
that,
basically,
like
the
end
user,
has
to
only
install
one
or
two
of
them
at
most.
I
think
it's
it's
in
those
cases.
It's
fine.
If
it's
a
couple
of
characters,
more
of
typing.
E
Yeah,
I
completely
agree
with
that
last
point.
Right
now,
users
have
to
install
like
four
or
five
packages
just
to
like
the
basic
use
case,
and
I
think
that
that
is
definitely
not
ideal.
I
think
installing,
like
one
package
for
the
sdk
and
one
package
for
all
the
instrumentations
is
probably
all
most
users
should
have
to
do,
plus
any
additional
instrumentations
that
they
want
to
add.
But
in
terms
of
the
sdk
itself
it
should
be
installable
as
like
a
single
package
for
the
average
use
case.
B
But
yeah
I
would
actually
make
the
main
packages
very
explicit
and
then
maybe
republish.
I
don't
know
whether
it's
feasible
or
not.
Maybe
it's
too
much
work
and
even
more
confusing,
but
basically
have
aes
like
shorter
aliases
on
the
actual
like
long
named
packages,
maybe
but
maybe
you're
just
over
engineering.
It.
E
E
Bart,
it
looks
like
you
responded
to
this
yesterday.
Did
you
disagree
with
the
the
naming
scheme
that
that
valentine
put
here,
or
was
this
just
an
additional
option?
What
what
are
your
thoughts
at
the
moment.
C
I
mean
basically,
we
are
basically
keeping
this
to
be
sorted
also
so
like
we
don't
have
collector
exporter
who
have
exported
collector
and
so
on
sort
of
exporters,
so
the
same
with
tracing
tracing,
something
and
so
on.
So
that's
the
idea
behind
that.
C
C
F
I
didn't
hear.
Oh
so
sorry.
I
said
I'm
totally
agree,
I'm
fine
with
with
both.
So
so.
If
it
makes
more
sense
to
have
the
signal
at
the
beginning,
then
so
be
it.
E
Okay,
do
you
agree
with
sort
of
the
the
comments
that
I
had
here
or
do
you
like
the
naming
scheme
that
you
used
in
the
initial
pr?
I
was
trying
to
find
it
here.
It
was
in
a
comment.
E
I
guess
this.
What's
which
boss
in
general,
like
the
having
shorter
names
versus
longer
names,
I
guess.
F
Oh,
I
I
mean
I
will
be.
I
personally
prefer
explicit
names,
but
I
I
will
not
fight
this.
I
mean
I
I
don't.
I
don't
have
a
strong
feeling
about
this,
so
if
you
prefer
to
remove
the
base
the
base
prefix,
I
will
be
fine
with
it
too.
C
F
One
of
the
problems-
sorry
yeah.
I
was
going
to
say
that
one
of
the
problems
that
we
have
if
we
want
to
have
shorter
names,
for
example,
if
we
are,
we
want
to
have
like
just
node
or
web
for
the
for
the
sdk,
that
old
all
sdk,
like
that
stability
thing.
So
the
last
package
in
my
email
comments,
so
sdk,
not
all
if
we
just
want
to
name
it
node,
there
will
be
a
big
blocking
chain
for
user
because
they
actually
use
it
right
now
for
having
a
low
level
implementation.
F
So
I'm
not
sure
if,
if
that's
that's
blocking
or
not,
I
mean
that's,
that's
why
we
are
doing
this
pre-pre,
ga
but
yeah.
I'm
not
sure
about
this.
E
C
But
if
we
have,
if
we
have
like,
but
then
we
have
the
sdk
for
matrix,
yes
and
then
yes,
if
the,
if
we
have
more
package
with
sdk,
then
tracing
then
put
the
sdk
first.
B
B
E
Yes,
it's
shared
components
that
are
used
by
both
the
node
and
the
web
package.
It
has
like
the
tracer
provider
that
the
basic
tracer
provider
and
like
the
span,
processors
and
things
like.
E
That
separate
from
this
pr,
I
think
as
a
follow-up
in
the
like
the
sdk
node
tracing
package,
for
instance,
if
you
want
to
do
tracing
this,
should
be
the
only
package
you
have
to
install
to
get
the
sdk
set
up.
So
I
think
it
should
export
the
span
processors
again
even.
B
E
They're
exported
from
the
base
tracing
package,
I
don't
think
end.
Users
should
have
to
install
all
of
the
component
packages.
If
that
makes
sense,
I
don't
think
that
would
be
done
in
this
pr.
It'll
be
a
follow-up,
but
I
was
just
looking
at
our
examples
and
like
having
even
for
the
the
the
simplest
example
which
there's
a
pr
to
update
the
readme
for,
like
the
simple
getting
started,
example
and
there's
like
six
imports
at
the
top
of
the
file
which
to
me
that
seems
like
a
broken
experience.
G
E
C
B
E
So
I
guess
just
the
decision
that
we
made.
E
B
B
B
Yeah,
I
think
it's
better,
even
even
better
like
that.
E
E
C
H
H
E
Yeah,
so
this
would
be
the
package
that
an
end
user
would
install
and
if
you
know
in
the
default
case
and
then
if
they
say,
I
only
want
tracing
and
I
don't
want
metrics,
then
they
would
install
this
package
but
getting
started
the
the
simple
explanations
we
would
tell
them
to
install
node,
sdk
or
sdk
node.
E
Okay,
severin,
and
where
do
you
have
any
updates
that
you
want
to
talk
about
related
to
the
docs
and
examples.
E
They're
not
I'll
reach
out
to
them
separately.
I
guess
I
didn't
see
any
prs,
so
I
think
the
answer
is
probably
still
working
on
it,
but
I'm
not
sure.
E
Okay,
just
a
quick
update
on
browser
stack.
I
am
still
going
through
the
process
emailing
their
open
source
team.
They
they
keep
forwarding
me
to
sales
people,
so
I
I'm
trying
to
to
go
through
that
process,
but
it
should
be
done
anytime
or
any
day.
Now
I
I
hope
I
thought
it
would
be
done
by
now,
but
just
so
you
know
I'm
not
forgetting
about
this
next
question.
We
had
is
related
to
documentation.
E
Specifically,
severin
updated
the
website
docs
and
added
a
link
to
a
logs
io
example.
Under
a
heading
called
community
resources.
E
So
we
have
here
level
two
heading
community
resources
and
then
level
three
headings.
We
have
a
tempo
example
and
a
logs
io
example
that
he's
adding
valentin
commented
here
that
he
was
concerned
that
it's
a
proprietary
solution
and
not
an
open
source
solution
where
tempo
is
an
open
source
offering
that
happens
to
have
a
hosted
offering.
E
My
question
is
in
in
examples
specifically
community
resources.
How
do
we
feel
about
linking
to
examples
that
use
proprietary
offerings.
C
E
F
Well,
not
not
really
against.
I
was
just
making
sure
that
we
addressed
these
issues.
Actually
I
don't
much
care
about
this.
It's
on
the
community
side
on
the
community
side.
I
just
don't
want
vandal
to
start
adding
more
examples
like
that
linked
to
their
solution,
so
it
just
cannot
become
an
advertising
space
in
the
official
websites.
That's
that's
one
thing
that
worries
me
about
it.
E
I
I'm
fine
with
removing
it
on
the.
I
am
I'm
the
author
of
this.
D
So,
but
if
open
telemetry
javascript
is
interested
in
examples
like
that,
because
loksio
has
a
very
little
impact
on
this
example,
it
is
simply
one
section
and
the
title
is
not
reflecting.
Actually.
What
is
this
example
about?
I
can
remove
it.
I
mean
the
title
of
luxio
and
the
two
words
that
speaks
about
lokshu.
But
again.
D
The
purpose
of
my
of
this
example
of
this
repository
that
is
linked
here
is
for
my
personal
experience
with
urban
telemetry
and
to
contribute
back
to
the
repository.
E
D
Yes,
thank
you.
Thank
you
to
try
to
learn
and
to
make
this.
I
do
support
you
also
with
contributions.
E
Okay,
I
think
that
that
is
much
more
definitive
than
I
expected.
Thank
you
for
for
bringing
that
up.
That
was
the
last
agenda
item
that
I
had
added.
I
just
wanted
to
quickly
mention
if,
if
people
have
things
that
they
want
to
discuss,
they
can
feel
free
to
add
things
to
the
agenda.
I
don't
feel
like
you
have
to
wait
for
me
to
add
something.
If
you
want
to
talk
about
it,
you
know
I
it's
fine.
E
If
you
don't
have
something,
but
if
you
do,
please
feel
free
to
add
things
to
the
agenda
throughout
the
week
other
than
that.
Please
review
the
the
pr's
in
the
list
below
and
if
nobody
has
anything
else.
E
E
E
If
nobody
has
anything
else,
then
I
will
talk
to
you
all
next
week.