►
From YouTube: 2021-05-26 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
C
I
think
that
was
when
you
are
on
holiday.
Also,
oh.
B
A
A
Whenever
I
hear
somebody
say
good
day,
did
you
ever
watch
what
what
was
that
show
the
one
that
70s
show
all
right
would
always
go?
I
said
good.
A
A
E
A
A
A
All
right
so,
first
on
the
agenda,
we
don't
have
any
open
new,
open
pr's
that
are
new
or
crazy,
pretty
much
the
same
ones
as
before.
There
is
a
there's,
a
couple
for
like
little
documentation,
updates
or
whatever
amber.
I
think
you
saw
that
udp
and
thrift
pr2
did
you
have
a
chance
to
look
that
over
if
that
was
totally
cool.
D
Yeah
I
looked
it
over.
It
seemed
pretty
good,
but
like
the
point,
you
made
a
couple
tests,
so
I
put
a
couple
of
links
in
to
sean's
pr
where
he'd
put
tests
for
that,
so
they
could
see
an
example.
Sometimes
it's
just
easier
with
an
example.
A
Yeah
agreed,
I
think
I
think
that
pr
is
okay,
but
it's
like
they
took
out.
They
took
out
8.0
a
while
ago,
but
I
think
that
we
should
be
okay
to
use
8.0,
I'm
not
sure
but
we'll.
Hopefully,
that
person
will
come
back
and
fix
the
rest
of
their
pr.
If
they
don't,
then
we'll
just
leave
it
for
a
little
bit,
that's
good,
and
then
we
don't
have
any
new
open
bugs.
A
I
think
I'm
just
going
to
make
a
hard
line
of
after
I
fix
the
baggage
pr
I
replaced
the
I
did
find
and
replace
on
the
wrong
word
for
the
baggage,
pr
that
you
reviewed
for
me
amber
so
I'm
going
to
go
back
and
revert
that
and
then
push
out
the
right
one
I
just
like.
I
guess
it
got
documented
and
it
took
it
incorrectly
and
I
didn't
was.
I
was
too
dumb
to
check
the
spec.
So,
however,
it
didn't
push
out
the
right
version.
I'm
sorry
about
that.
A
On
sorry
about
that
yeah,
so
the
I
they
all
the
maintainers
are
working
on
a
security
decision
for
each
of
the
six.
They
gave
us
a
couple
examples
of
security
solutions
that
we
could
use
in
our
repo.
They
just
want
us
to
have
something.
I
was
going
to
ask
y'all.
If
you
had
any
opinions
on
what
sort
of
security
solution
we
should
use
to
audit
our
code,
do
you
all
use
anything
that
you
find
really
helpful
or
anything
because
they
gave
up?
Let
me
pull
up
what
they
gave
us
like.
D
A
Yeah
snake
stick
was
one
of
the
solutions
that
they
offered.
I
haven't
used
it
before,
but
I've
heard
decent
things
about
it.
So
that's
the
issue
that
I'm
talking
through
now,
so
it's
nick
or
I
guess
som-
has
a
song
technically,
has
a
security
skin
as
well,
which
might
be
our
best
solution,
because
we
already
use
all
in
our
repository
and
then
that's
like
a
little
bit
less
cognitive
overhead
to
deal
with.
A
But
I
was
just
curious
to
see
if
anybody
had
any
thoughts
or
prescriptions
here,
because
I
was
gonna
go
through
and
try
some
of
this
out,
but
I
just
didn't
want
to
like
go
too
far
down
the
rabbit
hole
until
unless
some,
if
in
case
somebody's
like
oh
yeah,
that
would
be
great.
D
A
C
A
Okay,
so
I
think
it's
gotten
enough
approval,
so
I'll
merge
that
this
afternoon
too,
so
once
that
gets
merged
and
my
baggage
change
gets
fixed,
then
I'll
cut
the
release.
Today,
I
think
you
made
some
release
notes
for
that,
so
we
can
add
those
in
and
then
we'll
be
off
to
0.0.2
amber.
I
think
you
asked
not
to
I
think
you
might
have
asked
the
last
meeting
about
it
being
like
talking
about
a
pre-release
or
pre-alpha.
Release
versus
an
alpha
release.
Is
that
right.
D
A
That's
a
really
good
question.
I
think
it's
kind
of
ambiguous.
I
think
that's
our
like!
That's
a
determination
that
we
can
make
as
a
group,
I
think
pre-alpha
versus
alpha
can
often
be
very
ambiguous
because
both
of
those
indicate
not
perfectly
production-ready
software,
so
I
don't
really
have
a
strong
feeling
if
you,
if
you
have
particular
examples
of
wanting
to
push
it
to
alpha,
I
can
just
make
this
release
an
alpha
and
not
pre-release
version.
If
that'll
help
to
garner
some
more
feedback
or
get
more
people
using
it
or
whatever.
D
A
Okay,
so
yeah
I
mean
we.
If
the
if
that
pre-alpha
versus
alpha
distinction
makes
that
big
of
a
difference,
then
we
could
definitely
just
release
it
as
alpha.
I
have
no
problems
with
that.
I
think
the
software
is,
it's
definitely
not
production
ready,
but
it's
definitely
alpha
quality.
Now,
in
my
opinion,
does
anybody
else
have
strong
opinions
other
way,
otherwise.
A
Well,
that's
good
and
then
yeah.
I
know
sean
mentioned
that
he
wants
to
pick
up
the
otlp
hgp
exporter,
which
I
didn't
think
anybody
else
would
care
about,
picking
that
up
a
week
before
him.
I
think
that
he
already
has
a
lot
of
context
and
I
should
be
able
to
do
that.
Pretty
you
know
famous
last
words.
He
should
be
able
to
do
that
pretty
easily,
but
I
just
figured
I'd.
Let
everybody
know,
does
anybody
else
have
anything
they
want
to
discuss?
Is
anything
on
the
table?
E
I
had
the
sorry
for
the
background
noise.
I
don't
know
if
y'all
hear
that
it's
like
construction
right
across
the
street
but
yeah,
I
I
have
the
the
test
failures
for
the
the
trace
context,
test
service
that
I
had.
I
know
I
was
gonna
put
up
a
pr
like
two
weeks
ago,
but
I
was
on
call.
E
So
I
haven't
really
worked
on
the
last
two
weeks,
but
what
I
discovered
is
there's
two
strictness
levels
that
the
tests
run
on,
so
what
we
had
it
on
was
like
the
highest
one.
So
the
level
two
which
just
runs
all
the
tests
and
a
lot
of
those
ones
that
are
failing,
were
the
trace
date
ones
and
it's
basically
just
that
those
tests
were
a
little
too
strict
for
for
us.
E
So
I
started
running
them
on
the
level
one
and
that
reduced
down
to
about
six
failures,
and
I
fixed
like
three
of
them
and
I
think
that's
as
good
as
we're
gonna
get
without
just
doing
way
too
much.
You
know
checking
in
there
and
making
it
a
bit
too
too
tough
for
the
for
the
users-
and
I
looked
at
all
the
other
ones.
E
Like
that
javascript
java
c
plus
plus
they
all
do
it
on
the
level
one
strictness
level
and
the
c
plus
plus
one,
I
think
they
actually
even
have
a
lot
of
the
trace
date,
ones
failing
because
they're
just
a
lot
more
open
on
the
trace.
They
just
give
a
lot
more
control
to
whoever's
using
it.
So
I
think
that's
probably
the
best
we
could
do
right
now.
It's
just
leave
it
at
the
the
three
failures
after
the
pr
that
I
put
up,
fixes
that-
and
I
guess
later
on.
E
If
things
change
we
can,
we
can
always
do
some
more
work
there,
but
that
should
be
fine.
For
now,
the
important
bit
is
the
trace
parent
header
one
and
all
those
tests
should
be
passing
after
the
pr
occurred
up
so
yeah.
I
was
wondering
what
y'all
think
about
that.
If
that's
all
right.
A
I
think
the
answers
to
that
family
is
it's
good
enough
for
government
work,
and
I
would
I
guess,
like
an
extension,
I
have
of
that
question.
You
don't
want
to
add
this
to
our
cicd
pipeline
correct.
You
just
want
to
have
this
be
available
as
a
test
because
it
doesn't
seem
like
it
would
make
sense
to
do
it
for
every
pr
or
merged
or
whatever.
So.
E
Yeah
now
because
it's
the
test
like
takes
a
little
bit
to
spin
up
because
you
know,
sets
up
the
whole
symphony
application
and
then
running
of
the
test
actually
takes.
You
know
a
couple
seconds,
so
I
don't
think
that
makes
sense
to
do
it
for
every
run.
But
we
should
probably
put
something
in
the
readme
that
you
know
if
anything
is
changed
on
the
trace
context.
Work.
It's
good
to
run
this,
because
these
tests
are
kind
of
buried
in
there
and
it
has
its
own
readme.
E
But
we
should
put
something
a
bit
more
on
the
surface
level,
and
I
guess
I
can.
I
can
do
that
as
well
with
this
pr.
A
A
E
Its
own
directory,
but
I
mean
there's,
there's
a
lot
of
places.
You
can
change
that
affects
the
the
trace
context,
the
propagation.
So
I
wonder
if
we
can
choose
like
specific
files
like
the
tray
state,
one
for
sure
and
the
trace
context,
one
those
are
where
the
core
of
it
happens
so
yeah.
I
guess
we
can
do
a
github
run
for
those
ones.
But
if
anything
changes
on
some
of
the
other
ones,
then
I
guess
we'll
just
have
to
catch
it.
Whenever
it's
like
run
manually.
A
Either
that
or
like
we
could
just
go
the
blunt
route
here
and
just
say
like
make
that
note
that
you
were
just
talking
about
in
the
readme
and
then
just
if
you
know,
if
we
see
anything
just
we
can
always
go
back
and
fix
it.
It's
like
you
know,
that's
one
of
those
build
it
before
build
it
before
you
need
two
things.
We
probably
don't.
It's
probably
not
that
important
to
build
right
now,
as
opposed
to
in
the
future.
Maybe.
E
Yeah
yeah,
okay
yeah.
I
guess
we
can
just
revisit
that
one
later
on,
but
I'll.
Just
I'll
put
the
note
in
the
readme
for
now
yeah
cool.
E
Cool
yeah,
that's
all
I
had
as
far
as
like
new
work.
After
I'm
done
with
this,
I
guess
I'll
just
look
through
the
issues
later
there
and
grab
one,
but
is
there
anything
like
specific
that
we're
targeting
for
the
next
few
weeks.
A
I
think
pretty
much
anything
that's
got
a
release
required
for
ga
tag
would
be
a
good
one
to
work
on.
I
think,
there's
or
sorry
label
is
required
from
ga.
We
have
what
22
of
those
open.
So
you
can
probably
find
something
pretty
cool
to
work
on
in
that
realm,
and
I
think
that
those
are
probably
our
highest
priority
tickets
right
now,
yeah,
sorry
I'll.