►
From YouTube: 2021-01-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).
A
B
A
Yeah
yeah,
it
is
very
wet,
though
a
lot
of
a
lot
of
moisture.
That's.
B
That's
the
that's
like
that:
classic
stereotype
right
that
portland
is
rainy.
A
Yeah
yeah,
I
mean
it's
it
it's
rainy,
but
it's
like
that
like
that
drizzle,
like
you
know,
not
heavy
rain,
all
the
time.
It's
just
it's
bearable,
it's
just
over
a
long
period
of
time.
It
just
stays
like
that,
but
yesterday
it
dumped
down.
It
was
there's
a
lot
and
I
think
there's
like
trees
like
you
know,
knocked
over
and
it
was
actually
a
proper,
proper
storm.
B
A
Yeah,
that's
it's
a
little
cold
yeah.
Is
it
usually
like
this
time
of
year,
but
like
50
60
over
there.
B
Yeah,
so
we
for
like
a
good
frame
of
reference.
I
normally
play
tennis
all
year
round,
and
the
only
time
we
usually
don't
play
outside
is
pro
is
most
like
from
a
little
bit
before
christmas
to
like
probably
around
now,
so
it
should
get
warmer
here
like
not
this
upcoming
week,
but
next
week
classically.
But
the
weather
patterns
have
been
all
over
the
place
this
year.
A
B
Our
side
will
be
joining
okay.
I
don't
expect
anybody
else.
I
haven't
heard
from
anybody
else
either.
So
I
mean
we
can
keep
this
brief
today.
I
really
appreciated
your
pr.
That
was
great.
I
spent
a
long
time
reading
through
it,
and
I
was
really
really
trying
to
find
something
to
critique,
but
I
just
couldn't
so
I
just
merged
it
in
and
bravo
that
was
good
and
we
had
another
one
another
pr
from
little
x
this
week
and
alex's
was
also
very
good.
B
Just
like
bringing
up
a
new
trace
was
a
new
trace
state
parent.
That
was
the
problem.
Is
things
were
changing
the
specs
so
hard,
and
I
haven't-
I
haven't
done
as
good
of
a
job
as
watching
the
spec
as
I
can,
because
it's
just
like
a
never,
never
ending
moving
target
and
nobody
wants
to
be
involved
as
we
go
through
this
everybody
just
wants
to
like
wait
until
the
end.
So
luckily,
now
the
tracing
spec
is
pretty
much
done.
B
I
was
hoping
that
jody
would
pick
that
up
and
work
on
those
tickets,
but
I
didn't
get
a
response
from
her,
so
I
might
have
to
work
on
that
this
week
because
I
hadn't
heard
from
her,
but
I
like,
where
you're
going
with
this
trace
header
propagation,
because
I
think
that's
something
that
we're
you're
looking
you're
kind
of
looking
into
the
future,
where
you
know
we're
going
to
need
to
be-
and
we're
probably
probably
help
your
company
too.
So
that's
that's
great.
I'm
glad
that
year
you
have
that
foresight,
that's
really
good!
B
So
now
you
just
have
to
stand
up
that
test
implementation,
server
and
test
your
implementation,
I'm
assuming
that's
on
the
docket
for
this
week.
A
Yeah,
there's
actually
a
couple
more
smaller
things
with
the
trace
date.
Yeah,
like
the
more
I
went
through
the
actual,
like
full
w3c
spec,
and
the
more
like
I
looked
at
some
of
the
other
hotel,
like
java
javascript
that
have
already
done
this
there's
just
a
couple
of
smaller
things
that
are
missing
so
yeah.
I
think
I'm
gonna
add
another
pr
at
some
point
this
week
to
just
wrap
up
that
that
other
stuff
and
then
try
and
run
it
through
the
the
test
service.
A
Once
I
have
that
like
fully
running
and
then
whatever
comes
of
that
I'll
make
fixes,
but
the
only
the
only
problem
is,
I
don't
know
how
restrictive
we
should
be
with
the
with
the
trace
date:
validation,
because
the
trace
either
you
can
parse
it
or
you
can't,
but
with
the
with
the
trace
date,
which
is
more
like
a
vendor-specific
thing.
I
wonder
if
we
should
leave
some
control
more
control
to
the
user.
A
Whoever
is
you
know
actually
creating
and
injecting
that
tray
state
header,
because
right
now
you
know
I'm
validating
it
with
the
according
to
the
actual
spec.
So
yeah,
I
I
guess
that's
just
some.
Some
stuff,
I'm
just
thinking
out
loud
and
I'll.
B
A
Work
out
in
a
pr,
but
but
also
what
we
could
do
is
just
do
it,
as
is
with
the
spec,
and
then
decide
later,
how
much
control
you
want
to
give
up
to
the
to
the
user,
and
it
shouldn't
be
too
much
of
a
of
a
change
later
down
the
road
but
yeah.
B
My
my
feelings
on
this
are
php
is
notorious
for
expensive
validation,
especially
with
p
regs
and
like
a
bunch
of
other
stuff
like
that,
because
I
mean
they're
just
expensive
calls
to
php.
So
my
my
opinion
is
like
we
should
try.
We
should
attempt
to
do
the
best
validation
that
we
can.
We
should
probably
come
up.
I'm
not
saying
that
you
should
do
this,
not
even
by
countryman.
B
We
should
probably
come
up
with
some
sort
of
performance,
benchmarking
for
open,
telemetry
php
and
see
as
we
implement
some
of
this
validation,
how
much
it
really
impacts
the
whole
the
service
as
a
whole.
I'm
assuming
that
I'm
assuming
that
when
we
try
your
or
when
you
put
in
that
pr
to
test
it
against
the
the
upstream
server,
we
could
probably
add
some
instrumentation
there
around
performance.
It
probably
wouldn't
be
too
complicated
and
it'd
probably
be
just
like
a
good
to
have
a
baseline
in
general,
because
we
don't
right
now.
B
It's
like
we
recognize
this
as
well
written
code
and
there's
no
double
for
loops
and
there's
no
like
dumb
garbage
like
that.
But
we
don't
like
have
a
baseline
right
now
for
how
well
this
is
performing,
and
we
probably
need
that
at
some
point,
because
we
don't
want
to
implement
that
regression,
especially
with
a
non-compatible
change.
You
know
what
I
mean:
yeah
yeah.
I
know.
A
I
agree,
and
actually
I
think
the
the
test
validation
service
requires
that
you
have
like
a
a
application
which,
basically,
how
it
works
is
like
you
stand
up
the
the
test
service,
you
split
it
and
it's
receiving
on
a
on
a
port
and
you
send
it
it's
either
you
send
it
or
it's
a
post
request
with
you
know
a
number
of
things
that
you
have
to
resend
it
back
and
it
just
tests
how
much
of
that
stuff
got
through
as
as
expected,
yeah.
A
I
don't
quite
remember
the
the
process,
but
there
is
an
application
part
that
we
have
to
create.
So
I
think
we
can
do
some
performance
stuff
right
there
because
that's
like
it
acts
kind
of
like
an
endpoint
and
works
through
the
full
life
cycle
of
of
sending
and
receiving
and
parsing
all
the
the
headers,
as
expected
by
the
test
service
got
it.
That
makes.
B
Sense
so
we
do
have.
We
do
have
a
an
example
service
that
darla
dalibor
wrote
when
he
was
doing
when
he
was
coming
up,
like
writing
all
the
information
back
for
the
document
that
was
like
what
is
missing
from
what
is
missing
from
open,
telemetry
php.
So
that
might
be
a
good
springboard
for
you.
So
you
don't
have
to
like
write
a
boilerplate
code
right,
boilerplate
code
and
then
like
transmogrify,
for
your
needs.
That
might
be
I'll.
A
Yeah
because
the
point
that
I'm
at
right
now
with
it,
I
have
kind
of
like
a
docker
set
up
where
it's
setting
up
the
the
test
service,
and
I
have
that,
like
basically
done
so.
The
part
that
I'm
working
on
is
the
application
where
it
sends
or
receives
the
headers
from
the
test
service.
So.
B
A
B
For
finding
historical
reference
yeah,
well,
you
can't
in
the
in
the
like
standalone
app
you
can't
search,
which
is
crazy
to
me,
but
you
have
to
open
up
the
web.
The
web
version
that's
like
slow
as
molasses.
B
B
See
there's
open
telemetry,
php
user
test.
I
am
going
to
I
pinged
it
to
you
in
getter.
Would
you
rather
me
and
paint
it
to
you
and
zoom?
I
don't
know
it's
easier
for
you.
B
Getter
then
yeah,
it's
called
open,
telemetry,
php
user
test.
It's
like
a
pretty
pretty
baseline
symphony
application.
That
has
a
bunch
of
garbage
that
you
might
want.
B
B
B
Used
that
I
get
it,
I've
used
symphony
exactly
zero
times,
so
I'm
I'm
not.
You
know,
I'm
not
super
well
versed
in
it,
but
that
should
that
should
at
least
give
you
like
a
good
springboard
for
creating
your
dummy
application
for
testing
the
service.
A
Awesome
yeah.
That
sounds
like
it's
gonna,
be
helpful,
so
yeah
I'll
work
on
that
this
week
and
then
after
I
do
the
the
pr
for
the
the
extra
changes
and
then
I'll
try
to
have
something
up
by
my
next
okay.
B
A
A
One
question
I
did
have
is
sure
I
know
we're
not
like
we're
just
like
kind
of
basic
members,
but
what
what's
the
process
on
just
like
you
know
giving
out
reviews
for
pr's
that
we
see
is
it
like?
Can
anybody
do
it,
or
is
it
just
more
like
maintainers
and
approvers
that
can
actually.
B
So
how
so,
technically
how
it
works,
is
you
have
maintainers
who
are
like
the
omnipotent
people
that
can
like
do
everything?
That's
I
am
the
only
maintainer
left,
the
other
one
and
just
he's
he
started
and
just
sort
of
fell
off
the
face
of
the
earth,
and
so
then
the
approvers
have
the
ability
to
approve
prs
and
to
review.
You
know,
review
them
and
like
do
a
lot
more
of
the
scrummy
type
stuff
in
the
project
boards
and
there's.
B
They
have
like
not
super
admin,
privileges
but
admin
privileges
for
the
repo
and
then
like
technically
now,
as
a
normal
member,
you
can
review
pr's,
but
your
reviews
don't
count
against,
like
actually
being
able
to
merge
them,
usually
usually
with
open
telemetry
project
you're
supposed
to
have
two
reviewers
for
every
pr,
but
we
just
haven't
been
able
to
do
that
because
we
don't
have
enough
people
to
review
them
and
it
takes
like
the
two
other
approvers
that
are
around
now.
B
It
takes
them
like
two
weeks
to
even
look
at
read
me
change,
so
it's
I've
been
trying
to
like
weigh
that
and
like
completely
losing
momentum.
So
I've
been,
you
know,
approving
stuff
and
merging
it
myself,
even
though
I'll
probably
get
scolded
for
at
some
point,
but
whatever
it's
better
than
having
absolutely
nothing
so
yeah
it'll
be
nice
to
have
you
in
amber
to
be
able
to
be
quote
unquote,
official,
reviewers
and
stuff
and
be
able
to
have
so
I
know
you
all
have.
B
I
know
it's
annoying
to
have
to
like
say
I'm
working
on
this
in
the
issue
templates
and
then
having
me
have
to
assign
it
to
you
and
it's
just
like
the
restrictions
are,
are
kind
of
difficult,
so
hopefully
we'll
be
able
to
get
some
to
get.
You
all
be
reviewers
or
approvals.
A
Yeah
because
I
mean
I've
been
having
a
look
at,
you
know
a
few
of
the
pr's
that
have
been
put
up
recently,
but
I
mean
I
haven't
like
officially.
You
know
done
a
review,
but,
like
you
know
how
to
look
and
yeah
it's
good
to
know
that
just
anybody
can
have
a
look.
I
mean
it
makes
sense
that
it
wouldn't
count
against.
You
like
an
official
review,
but
but
at
least
like
doing
like
the
the
check
mark
or
and
comments
that
you
see
is,
is
actually
useful.
B
A
A
B
B
Approving
this,
because
nobody
else
is
so-
that's
always
good,
but
I'm
not
asking
you
to
do
that,
because
that's
not
your
role
or
responsibility,
but
if
you're
interested
in
reading
them
to
because
it's
good
for
your
own
notification
or
whatever
feel
free
to
approve
them
or
make
making
comments
about
what
you
would
change
is
also
great.
Like
that's
also
fine.
A
Okay,
cool
yeah,
I
think
I'll
start
doing
that
can't
be
too
harshly.
B
A
Think-
and
I
think
actually
amber
is
probably
in
the
same
boat
too,
because
I
know
she
has.
I
look
at
some
of
the
pr's
and
you
know
she
thanked
me
or
I
pinged
her
with
like
questions
as
we're.
You
know
increasing
our
understanding
of
it
all,
but
but
yeah.
I
think
we'll
try
to
participate
more
officially
in
the
reviews,
rather
than
just
you
know,
being
quiet
members
watching
from
a
distance,
silent
ninjas.
In
the
background.
A
All
right
cool!
Well
I
mean
that's,
that's
really
all
I
have
for
today
so.
B
A
A
Awesome
yeah
have
a
good
rest
of
your
day.
See
you.