►
From YouTube: 2021-07-28 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
B
C
Roano,
I
did
finally
get
around
to
reviewing
the
sjspr,
so
thank
you
for
that.
D
Like
for
a
while,
not
happy
about
that
at
all,
but
but
I
actually
just
like
wrapped
it
up
today
and
kind
of
finished
it
so
no
reason
to
feel
better
about
it.
D
B
You
know
try
to
dedicate
more
time
to
those
yeah
I
sort
by.
I
I've
been
talking
around
now
about
like
github
power,
user
stuff,
and
that's
one
of
the
things
I
do.
I
I'd
sort
by
oldest
pretty
frequently
or
sort
by
what
was
what
was
the
longest
since
it
was
last
updated.
Was
this
is
a
sort
option.
I
love
that.
C
C
C
Let
me
share
my
screen.
C
C
C
Right
so
not
a
particularly
long
schedule
today,
but
that's
okay,
because
I
actually
have
limited
time
today
anyway,.
C
So
the
first
few
things
are
mostly
housekeeping
api
had
a
bug
fix,
so
we
need
to
release
the
1.0.2.
C
C
C
C
It
would
be
nice
to
do
it
today,
but
I
probably
can't
promise
that,
but
sometime
this
week
I
wanted
to
talk
about
the
sdk
package
renaming,
but
valentine's,
not
on
the
call.
So
I
think
we
probably
won't
have
much
to
say
about
it
other
than
for
those
that
have
not
been
following
it.
All
of
the
sdk
packages
are
going
to
be
renamed
or
not
all
of
them.
C
Some
some
subset
of
them
will
be
renamed
with
a
slightly
different
naming
scheme
so
that
the
packages
will
be
named
using
their
signal
and
whatever
platform.
If
they
target
a
particular
platform,
so,
for
instance,
the
tracing
package
is
being
renamed
to
I
think
tracing
base.
I
can
actually
find
the
pr.
C
I've
art
bart
since
you
missed
it
earlier
just
so,
you
know,
there's
a
pr
open
on
the
api
for
a
patch
version
release.
So
whenever
you
get
a
moment.
C
So,
like
tracing,
for
instance,
is
renamed
sdk
trace
base.
C
Trace
node
because
it
was
only
handling
tracing
before
and
similarly
for
web.
We
have
sdk
trace
web
in
the
future.
As
we
develop
the
metrics
sdks,
we
will
also
have
similar
metrics
packages
and
then
the
node
sdk
name
is
just
switched
to
the
sdk
node
in
order
to
fit
the
naming
scheme
of
these
other
packages.
C
I
know
we've
been
talking
about
this
for
a
while
and
you
guys
are
probably
sick
of
hearing
it,
but
it's
it
is
finally
going
to
be
done.
I
think,
sometime
in
the
very
near
future
here.
C
C
I
know
that
you're
you've
been
asking
for
that
for
a
long
time,
still
mostly
just
waiting
on
them,
if
I
haven't
heard
from
them
I'll
check
my
email
after
this
meeting
I
haven't
worked
today,
but
I
maybe
send
them
a
ping
to
make
sure
that
they
haven't
forgotten
about
us.
C
This
next
item
I
haven't,
actually
started
working
on
yet
I
just
noticed
today
there's
a
few
dependable,
pr's
or
renovate
pr's
that
are
pinning
various
packages
and
updating
some
others,
and
I
don't
think
we
have
anywhere
documented
what
our
dependency
strategy
is
in
terms
of
what
should
be
pinned.
What
should
be
a
peer
dependency
and
stuff
like
that.
We
follow
a
relatively
consistent
set
of
rules,
but
as
far
as
I
know,
it's
not
documented
anywhere.
C
So
I
will
be
documenting
that
in
the
contributing
markdown
file
for
each
of
the
three
repositories.
D
Yeah,
actually
a
comment
by
you
on
the
nest
chest
pr
reminded
me
of
a
struggle.
I've
had
implementing
instrumentations
with
the
dest
utils
package
because
it's
not
published,
especially
when
you
make
changes
to
it.
There
is
some
weird
limbo
you
have
to
go
through
with
linking
it.
D
C
Future
yeah
I
mean
I,
I
don't
see
a
reason
not
to
publish
it.
I
know
that
I
think
we
just
said
it
as
private.
Originally
we
only
had
one
repository
at
that
time,
so
we
didn't
really
run
into
this
problem,
but
now
that
we've
split
a
little
bit,
I
can
definitely
see
that
and
I
don't
see
a
reason
not
to
publish
it.
C
I
think
the
name
is
obvious
enough
that
it
should
people
should
know
that
it's
for
you
know
internal
and
test
usage,
and
I
think
even
some
external
externally
hosted
instrumentations
may
want
to
take
advantage
of
it.
I
don't
see
any
reason
to
to
prevent
them
from
doing
that.
C
I
don't
know
if
anyone
else
has
reasons
not
to
but
yeah,
I'm
not
against
it
at
all.
D
No,
it's
not.
I
also
posted
a
discussion
just
below
the
the
item
in
the
in
the
meeting
notes
about
someone
asking
about
that,
and
I
had
a
very
similar
issue
when
I
first
started.
D
No,
you
kind
of,
depending
on
what
your
work
kind
of
processes.
D
You
have
to
do
extra
steps
not
to
have
errors
when
you
are
running
tests
or
or
doing
npm
install
so
you're
going
to
have
to
be
aware
that
there
is
a
such
a
special
case
unless
you
do
everything
by
the
book
and
and
kind
of
work
on
the
whole
people
at
once
and
use
all
the
right
yarn
commands
and
everything
I
mean.
I
was.
E
Using
because
I
mean
we
are
also
having
like
a
launchers,
and
I
never
saw
any
any
errors
to
be
honest
with
regards
to
missing
this
package
or
something
like
this.
C
Yeah,
the
error
that
you
run
into
is,
if
you
run
in
a
particular
dependency.
So
if
I'm
working
on
one
instrumentation
like
the
pinot
instrumentation,
or
something
like
that,
if
I
cd
into
that
directory
and
just
run
npm
installed,
all
of
its
dependencies
are
external
dependencies,
so
they
install
just
fine
except
for
the
test
details
one
so
that
one
okay,
because
it's
not
published.
So
I
never
worked
like
this
okay
yeah,
I
don't
either,
which
is
why
I've
never
run
into
this
either.
C
But
that
said,
the
contrib
repo
is
huge
and
it's
getting
bigger
and
the
bootstrap
takes
forever
and
I
think
most
people
contributing
to
it
are
just
working
on
one
instrumentation
at
a
time.
So
I
think
that
that
probably
makes
more
sense
to
focus
on
that.
You
know
it's
a
quality
of
life
improvement,
I
suppose,
for
those
users
or
for
those
contributors.
E
And
I'm
sorry,
I
don't
understand
what
you're
saying
I
mean
this.
This
package
is
missing,
read
me,
it
doesn't
have
to
need
me.
So
I
would
say
you
should
probably
read
me
and
then
we
can
publish
this.
No
just
say
it.
It
will
be
completely
empty
once
we
publish
so
no
one
knows
what
what
is
that.
C
C
C
Here's
to
review
what
is
this
one
here:
sjs
instrumentation?
Yes,
so
this
is
the
28
day
old
pr
that
is
only
actually
two
hours
old
or
something
like
that
yeah.
So
people
please
review
when
you
get
time.
C
B
Up,
I'm
just
I'm
still
working
my
way
through
getting
involved
and
like
dropping
my
head
around
the
project
and
been
reading
through
docs
and
running
examples.
I
just
haven't
been
very
productive.
The
past
couple
weeks,
while
I've
been
focusing
on
other
stuff
but
yeah,
I'm
still.
If
anybody
has
things
they
want
someone
to
take
a
look
at
or
if
they
want.
You
know,
reviewed
or
like
I
like,
going
over
docs
and
examples
of
the
fine
tooth
comb
and
finding
little
things.
B
C
Thank
you.
I
appreciate
that
and
for
those
that
don't
know
his
github
username
is
john
church.
I
think
documentation
and
sort
of
first
run.
Experience
is
a
combination
of
extremely
important
and
extremely
overlooked,
a
lot
of
the
time
so
yeah.
I
we
appreciate
that.
C
Okay,
then,
I
hope
everybody
have
a
good
rest
of
your
week
and
I
will
talk
to
you
next
week.
See
you.