►
From YouTube: 2021-03-24 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
B
I
can
see
you,
you
must
use
dslr
as
your
webcam.
B
B
C
D
B
That's
good,
it's
20
degrees
c
here
right
now,
so
it's
absolutely
spectacular
out.
So
I'm
like
ready
for
the
day
to
be
done,
so
I
can
go
and
spend
some
time
outside.
D
No
he's
in
the
other
corner
by
the
by
where
the
food
is,
I
guess,
he's
waiting
for
his
lunch.
B
D
B
B
B
D
B
Sweet,
I
don't
expect
anybody
else
to
come,
so
we
can
get
rolling
if
somebody
else
comes
in,
we
can
catch
some
speed.
All
right.
I
have
my
agenda
laid
out
for
today
we
got
about.
We
had
a
couple
of
prs
opened
and
closed,
we
closed
the
sampling
behavior
and
then
we
merged
your
fixed
cruise
contact
header
extraction
right
after
the
meeting
last
time
funny,
so
I
think
we're
still
making
progress
forward.
B
Let's
see
what
else
I
got
there,
we
have
a
couple
open
bugs,
but
nothing
that's
a
show
stopper,
and
I
think
I
looked
through
them
this
after
this
afternoon
and
it
looks
like
most
of
the
open
bugs
are
just
parts
of
features
that
haven't
been
developed
yet
or
they
have
something
open.
That
is
probably
gonna
be
closed
soon.
B
So
I'm
not
gonna
put
like
a
ton
of
stock
into
like
actively
triaging
about
conditions
for
an
alpha
project,
really
the
juice
ain't
worth
the
squeeze,
but
we'll
get
we'll
get
through
it,
and
then
one
I'm
like
trying
to
keep
a
attentive
eye
on
them
just
so
that
when
they
do
like
when
we
do
have
a
pr
that
gets
open
that
fixes
one
of
them
all
with
the
I'm
trying
to
let
that
bug
reporter
know
that
something's
fixed.
B
I
think,
founded
that
I
tested
that
that
bug
that
we
looked
at
about
the
parent
spans
with
the
current
active
version
in
prod,
it
seems
to
work
okay,
so
I
think
it
was
lelex's
bits
and
pieces.
C
Good,
are
you
here
for
the
open
planetary,
php
meeting,
I'm
here,
so
this
is
the
dot
net
meeting.
I'm
sorry,
I
think
you
have
the
wrong
room.
I
have
the
wrong
room.
That's
interesting.
I
followed
the
link
that
I'm
always
in
so
I
have
the
link
bookmarks,
okay,
yeah.
A
C
Didn't
recognize
the
faces,
so
thanks
and
I
guess
I'll
see
you
later
bye.
B
Okay,
the
other
thing
that
the
other
open
things
that
we
had
to
talk
about
where
the
website
docs
are
going
to
get
published
soon.
So
in
the
maintainers
meeting
this
week
we
talked
about
it
they're,
going
to
they're
going
to
on
the
open
telemetry.
I
o
website
they're,
going
to
have
a
space
for
us
to
add
sort,
all
sorts
of
documentation
that
we
want
to
about
our
particular
project.
B
B
So
austin
parker
is
going
to
open
a
pr
to
our
repo
that
has
like
a
boilerplate
template
that
he's
designed
for
this
hugo
thing
and
then
I'm
going
to
add
some
of
our
examples,
some
of
our
readme
information
and
the
things
that
we'd
want
to
most.
We
want
to
most
happily
communicate
to
the
community
about
how
to
get
started
with
optometry
php,
where
to
look
for
docs
all
that
kind
of
stuff
sean.
You
want
to
talk
about
your
otlp
grpc
implementation,.
A
Yeah,
I
can
run
through
that.
Okay,
so
I
think
I'm
making
reasonable
progress
on
it
currently
getting
a
bit
stuck
currently
on
the
right
test
for
the
exporter,
because
I'm
using
on
a
mac-
and
I
haven't-
got
jrpc
installed
on
that-
which
I'm
gonna
figure
that
out.
But
there
was
in
reply
to
some
of
the
comments
that
I
did
have
on
that
pr.
C
A
Yeah
yeah,
it
replied
to
amber
on
the
span
converter,
where
I
temporarily
put
in
foo
but
as
yeah
as
the
comment
says,
I
kind
of
dug
down
that
rabbit
hole
and
found
that
none
of
the
other
sdks
specify
a
service
name
on
kind
of
within
the
exporter
code.
As
couple
of
examples
of
how
lightstep
have
done
it
in
an
a
example
and
with
honeycomb
for
python,
so
I
think
the
idea
is
that
normally
you
would
specify
service
name
as
an
attribute
within
a
resource
on
the
tris
provider.
A
I
tried
to
do
that,
but
I
found
that
the
constructor
for
our
result
in
full
passing
in
information.
There
is
private,
so
it
doesn't
let
that
yeah.
It
doesn't.
Let
you
construct
that
with
that
information
there,
but
it
seems
to
work
reasonable
when
I
just
edit
that
temporarily.
A
A
Yeah
so
making
the
I
forget,
which
I
I
didn't
link
to
the
line
of
code,
because
this
is
in,
I
think,
sdk
resource
resource
info.php
yeah.
The
constructor
function
is
private.
B
Let's
see
oh
yeah,
I
see
yeah,
I
see
okay,
so
yeah.
That
is,
I'm
actually
not
sure
why
those
attributes
are
private.
I
would
think
that
that
would
be.
B
That
feels
like
a
bug
that
feels
like
it
should
be
public
to
me,
because
you're
going
to
need
to
pass
in
attributes
to
the
resource
info
class
to
be
able
to.
I
don't.
I
don't
think
that
you're
not
going
to
get
those
by
default
just
from
the
resource
info.
So
that
feels
that
feels
like
a
bug
to
me,
but.
A
Okay,
so
yeah
that
that
was
one
bit
that
I
ran
into
so
that
kind
of
removes
parts
of
I
need
to
be
in
the
exporter.
I
think
just
reading
from
some
notes
amber
did
pr
my
repo
to
add
some
bits,
and
I
think
I
can
port
those,
because
currently
the
github
action
tests
are
failing
because
we're
missing
grpc
within
php
and
the
other.
The
other
thing
is
that
we're
missing
the
proto-generated
files,
which
I
went
through
some
history
on
that.
A
B
A
And
yeah,
I'm
not
sure
if
we
wanted
to
kind
of
yeah
continue
on
doing
that,
generate
them
just
in
the
tests
or
somehow
make
it,
so
you
can
include
them,
but
they're
just
generated
separate
to
this
mid.
I
don't
know
how
you
do
mono
recalls
with
packagist,
where
we'd
have
the
product
things
as
a
separate
package.
In
effect,
I
don't
know.
B
B
Generate
the
protofi,
I
know,
there's
a
make
proto
make
file
definition,
so
we
could
always
go
that
route
and
like
we
could
even
have
the
github
action
do
that
when
pr
is
generated,
if
we
really
wanted
to,
but
to
me
those
those
protos
aren't
going
to
change,
hardly
ever
if
at
all,
so
I
would
say
just
like
we
should
just
maybe
we
should
just
merge
that
like
we
should
generate
those
proto,
those
protobuf
definitions
and
merge
them
to
the
code
base.
I
don't
think
at
least
to
me:
that's
not
a
big
problem.
Yeah.
A
B
Foresee
any
any
doom
and
gloom
with
that.
A
Yeah,
I
think
other
other
languages
have
when
they've
generated
the
profiles.
They've
put
them
basically
in
the
same
area
as
the
exporter
for
grpc,
because
they're
not
really
necessary
outside
of
any
other
areas,
and
then
the
last
bit
on
that
is
the
passing
of
headers.
I've
almost
got
that
ready.
I've
read
this.
I've
read
the
spec
a
bit
closer
and
the
yeah
splitting
things
with
commas
and
then
is
is
in
spec
on
how
this
is
meant
to
be
done
so
that
works
for
the
environment
variables.
However,
I
was
thinking
for
the
constructor.
B
A
So
from
my
kind
of
from
my
point
of
view,
I
kind
of
in
if
I
was
to
write
an
application
chances
are
I'd,
have
a
config
file
a
bit.
This
is
partly
like
from
the
laravel
side
of
things.
If
it
was
integrated
there
I'd
be
passing
that
in
through
a
laravel
config,
which
would
support
a
passing
passing
an
array
directly.
A
B
It's
almost
to
me
like
you
could
do
you
could
like
make
a
simple
if
statement
there
like
if
it's
passing
those
array,
explode
the
array
and
get
the
comma
separated
values
and,
if
not,
then
just
take
it
as
a
copy
separated
or
a
comma
separated
string
right.
Okay,
at
least
that's
that's
how
I'm
thinking
about
it.
Does
that
does
that
seem
reasonable.
A
Basically,
support
both
support
yeah.
I
can
do
it
that
way,
because
yeah,
if
we
just
need
to
check
that
that
the
array
is
the
correct
shape,
that's
been
passed
in
and
that
should
be.
A
A
Yeah,
that's
pretty
much
all
of
the
questions
that
I
had.
I
might.
I
should
probably
add
kind
of
some
of
these
questions
onto
the
comments
on
the
pr
just
so
they're
a
bit
more
in
the
open,
rather
than
being
in
stuck
in
video.
B
Yeah,
I
also
don't
want
to
be
the
definitive
source
for
all
of
those
yeah,
but
I
think,
though,
all
of
those
seem
like
very
like
very
clear
and
concise
changes
to
me
and
as
long
as
you
agree
with
all
them.
That's
that's
those
all,
like
all
of
those
seem
very
reasonable
and
logical
to
me,
like
that
private
variable
is
definitely
a
bug.
B
Getting
a
raise
versus
a
string.
A
string
of
commas
like
people
are
going
to
pass
them
to
raise
a
few.
That's
just
how
it
goes.
So
we
have
to
be
prepared
for
that
and
yeah.
This
you're
doing
a
spectacular
work
on
this.
I'm
really
glad
that
you
picked
this
up
because
riddick
sort
of
got
a
third
of
the
way
down
and
just
like
dumped
it.
So
it's
really
been
sure
to
see
you
pick
it
back
up
thanks.
B
A
Yeah
I
already
ran
through
yeah,
make
style
on
things,
try
and
make
that
a
habit.
When
I
push
things
and
yeah.
Basically,
tests
are
the
next
thing
to
solve.
I
think
I'm
going
to
spin
up
a
ubuntu
virtual
machine
to
basically
develop
the
rest
of
this
on,
because
it
should
make
life
a
little
bit
a
little
bit
easier.
B
You
said
you
were
having
a
problem
with,
maybe
I'm
disconnected
from
what
the
problem
is.
You
said
you're
having
a
problem
with
getting
grpc
running
on
your
mac.
A
Yeah,
so
I
think
macs
by
default
come
with
php
7.3
and
you
need
to
install
all
the
page.
You
need
to
get
the
php
header
files
for
pekkl,
install
jrpc
to
work
nicely
and
it's
a
bit
of
a
it's
more
of
a
hassle,
and
I
don't
really
want
to
pollute
my
machine
with
this
stuff.
I
want
it
contained
somewhere.
A
Yeah,
I
think
I've
been
doing
that
a
bit.
The
reason
why
it
didn't
quite
work
is
the
as
I'm
not
a
proper
php
developer,
like
the
suggestions
in
vs
code
didn't
play
nicely
when
you're
developing
cross
into
yeah,
and
I
just
rely
on
the
yeah,
the
ide
telling
me
what
code
I
need
to
write.
B
D
Cool,
I
I
use
a
vagrant
box
with
a
ubuntu
on
it
to
do
my
php
development,
so
that
might
be
useful
and
a
bit
quicker
than
than
docker.
B
B
A
So,
just
a
last
bit
on
that
you're
on
a
trip
resource
info
kind
of
bug
should
I
leave
that
for
you
to
fix,
or
should
I
just
change
that
in
my
pr.
B
D
Yeah,
so
the
test
service-
pr,
I
haven't
been
able
to
work
on
it
this
past
week
because
I'm
on
call
it's
really
busy
but
I'll
get
to
it
this
weekend.
Thank
you
for
that
that
comment
for
the
suggestion
of
how
to
get
around
copying
over
the
the
files
locally.
Once
I
do
that
and
then
also
there's
some
errors
that
I'm
getting.
Oh.
D
Yeah,
it's
because
symphony.
Isn't
there
it's
it's
set
up
dynamically
and
then
I
copy
over
the
controller
file,
and
you
just
run
the
test
servers
that
way,
and
some
is
basically
you
know
yelling
yelling
enough
saying
you
know
symphonies
these
symphony
included
files
are
not
there,
so
I
might
just
add
a
suppression
for
those
errors.
D
That
might
be
the
way
to
go
so
once
I
do
those
two
things
that
pr
is
basically
ready
to
go
and
for
a
review
and
emerge
because
the
errors
are
fixed
separately
in
a
different
pr.
The
test
service
should
run
through
perfectly
fine
yeah.
So
that's
that's
where
I'm
at,
but
I'll
get
to
that
this
weekend.
After
my
on-call,
it's
done
because
yeah,
it's
always
pretty
busy.
B
Hi
you're
preaching
to
the
fire.
For
me,
I
very
much
know
and
yeah
the
suppression
for
that
is
totally
cool
by
me.
Like
that's,
there's
nothing.
You
can
really
do
there
besides,
suppress
that
because
those
files
won't
be
there
until
they
actually
get
there.
I
would
just
make
like.
I
would
make
a
comment
about
why,
when
you're
doing
that
suppression
just
so
that
future
follow
me
doesn't
go.
Why
not
do
this
yeah.
D
No,
I
totally
agree
yeah,
it's
an
easy
one
to
forget,
but
yeah
I'll
add
a
comment
in
there.
In
this
impression
I
haven't
looked
into
how
to
do
that.
Hopefully,
it's
just
a
really
quick,
like
doc
block
type
of
thing,
but.
B
Yeah
I
haven't,
I
don't
know
that
I've
done
it
with
some
lately.
I
don't
know.
I
think
I
did
a
while
ago.
It's
like
yeah,
just
like
it's
sort
of
like
the
same
with
python,
like
just
a
very
simple
comment
for
suppression.
It's
like
solemn,
colon,
blah
blah
blah
or
something
like
that.
Oh
all,
right,
perfect,
yeah!
B
B
B
Oh
all,
right,
that's
cool!
Let
us
know
if
you
need
any
help
with
that
feel
free
to
tag
me
in
that
I'm
going
to
be
away
from
my
keyboard
from
like
friday
through
monday,
but
I
may
just
still
review
your
pr
because
I'm
excited
about
it
anyway.
B
No
news,
I
don't
have
anything,
no
news
is
good
news.
All
right
well
I'll
be
around
if
y'all
need
anything
looking
forward
to
seeing
about
these
pr's
come
through
sorry,
huge
milestones
in
this
project
and
y'all
are
rockstars
for
working
on
them.