►
From YouTube: 2021-06-23 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
A
Okay,
we
usually
just
go
through
open
pr's.
Let's
look
at.
A
C
Yeah,
so
that
I've
got
a
few
more
fixes
to
put
on
that
bob
put
some
comments
on,
but
yeah
it's,
I
think,
very
close
to
be
ready
for
a
review,
and
I
think
he
mentioned
it'd
be
good
to
get
to
reviewers
to
look
at
that
before
approving,
but
before
merging.
A
A
A
B
Yeah
I
got
one
so
for
the
php
control
repo.
B
We
need
to
decide
a
folder
structure
for
it
once
so
that
we
can
migrate
everything
over
currently
in
the
contrib
folder,
in
the
open
telemetry
or
in
the
php
like
core
repo.
B
Each
individual
like
service,
has
its
own
folder,
but
in
normal,
like
other
contributors
that
are
more
set
up,
they
they
do
it
such
that
they
have
like
their
detectors,
their
exporters
and
their
other
general
components
separate
and
then
in
each
one
of
those
there's
like
a
folder
for
the
for
the
for
the
services.
So
I
can
actually.
I
can
share
real,
quick,
a
dock
of
kind
of
like
two
suggestions.
B
So,
like
the
first
currently
like
it's
set
up
like
we'll,
have
the
definitely
the
docker
all
the
these
different
folders
that
are
necessary
in
some
miscellaneous
files
in
the
top
level
and
then
the
first
proposal,
which
is
like
how
ever
like
how
every
other
repo
has
it
as
well,
is
like
they
have
detectors,
and
then
your
different
services
in
there,
your
propagators,
your
exporters,
other
packages,
an
alternative
name,
would
also
be
instrumentation
package.
B
It,
the
only
one
that
calls
it
packages,
is
the
js
repo
like
python
and
go
call
it
instrumentation,
then
like
an
examples,
folder
in
like
the
test
folder,
so
this
test
folder
will
still
let
us
to
do
everything
with
the
make
file
like
run
everything
by
just
running,
make
test
and
then
the
second
proposition,
obviously
not
normal
to
how
everything
else
is
set
up
in
open
source
where
you
have
like
your
different
services
and
then
your
test
folder
and
then
just
each
of
the
components
inside
for
that.
B
So
those
are
like,
essentially
the
the
two
like
ideas.
This
one
is,
I
think,
what
bob
and
I
were
talking
about
yesterday
doing
and
I
think
that's,
I
guess
the
safest
bet.
What
do
you
guys
think
about
this.
B
Okay
for
sure,
so
any
I
guess
opinion
on
whether
it
should
be
called
packages
or
instrumentation
or
that
specific
folder.
I
guess
it
could
also
be
left
out
until
we
actually
need
it,
but.
B
Let's
see
if
we
look
at
the
js
contrib,
this
one
has
packages,
so
it's
just
like
here,
for
some
reason
is
the
id
generator
in
this
package,
but
js
has
always
been
a
little
bit
off
in
terms
of
like
it's.
Let's
look
up.
B
B
B
Okay,
well,.
B
A
B
B
Oh
god,
okay,
give
me
a
give
me
a
minute.
You
guys
can
move
on
to
the
next
thing
for
some
reason
this,
because
it's
on
like
a
private
thing,
so
I
have
to
move
it
over
to
a
google
drive
doc.
So
I'll
do
that
right
now.
C
So,
on
the
open
damage
open,
celebratory.js
repo,
it
looks
like
what
I'd
assume
would
go
into
the
normal
instrumentation
directory.
They
put
theirs
in
slash
plugins,
node
and
then,
for
example,
inside
of
there,
they've
got
open
telemetry
instrumentation
express
for
an
example.
Web
framework
that'll
be
instrumented
which
looks
less
like
it
goes
into
packages
but
yeah.
I
agree.
There's
it's
a
bit
confusing
where
other
people
have
used
just
the
instrumentation.
B
Of
adding
core
repo
dependency
for
the
control
repo,
so
that,
like
look
because
like
for
my
project
currently,
I
need
to
use
some
of
the
files
in
the
core
repo.
I
don't
know
like
if
we
decided
on
what
we're
gonna
do
for
that
or
if
there's
a
plan
to
do
that
somewhat
soon.
B
Okay,
I
guess
I'll
talk
to
bob
about
it,
we'll
see
what
he
says.