►
From YouTube: 2022-02-16 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
Building
our
team
up:
are
you
you've
gotten
a
couple
new
employees
on
your
team.
B
Yeah
yeah
yeah,
you
see
me
cal,
there
he's
just
joined
our
team.
A
Amber
and
amber
miguel,
the
brett
is
an
australian
contingent,
a
new
maintainer
on
our
project.
So
it's
5
30
am
your
time
and
he's
gracious.
A
A
A
Okay,
there's
good
news
so
on
my
agenda
today
we
have,
we
have
an
open
wreck
for
a
cncf
sponsored
intern,
so
we
might
st
we
what
always
happens
when
we
start
seeing.
This
is
we'll
get
a
couple
pr's
from
new
people
saying
I
want
to
join.
I
want
to
join.
I
want
to
join
it's
because
they're
trying
to
get
the
internship
like
they're,
trying
to
get
the
internship
because
it's
paid
by
the
cncf,
so
we
get
a
lot
of
like
scraggler
crossroad
buys
so
just
trying
to
be
the
internship
is
paid.
Yes,.
A
D
A
I
don't
know
how
much
I
know
that
I
know
the.
B
A
A
So
I'm
assuming
it's
a
pretty
significant
amount
of
money
for
somebody
that
lives
in
the
third
world
country,
because
we
don't
get
a
lot
of
us
nationals
or
like
first
world
country,
people,
country
country,
people
applying
for
it's
been
mostly
third
world
country
people
applying
for
it.
So
just
taking
a
stab.
A
B
A
So
it
turns,
and
then
we
have
it.
We
have
a
couple
open
floor
requests
right
now,
there's
one
that
is
about
the
passing
url
and
headers
to
the
constructor
of
the
otl
phdp
explorer
by
mark
flann
brad.
I
think
you
were
working
on
this
with
him
and
timo.
You
also
were
working
with
this
on
him,
but
that
was
about
three
weeks
ago.
Should
we
just
bump
that
and
say
hey
you
playing
continuing
on
this.
A
I
think
that
eventually,
we'll
probably
want
to
have
a
bot
that
closes
prs
after
about
a
month
or
so,
because
I've
noticed
that
we
end
up
getting
like
scraggler
pr's
all
the
time
and,
like
you
know,
it's
easy
enough
to
reopen,
but
just
that's
something
that
I
will
take
the
action
out
of
of
doing
that.
A
I
know
that
there's
a
lot
of
those
I
know
there's
a
lot
of
those
bots
freely
available,
so
we'll
probably
see
how
we
can
throw
that
in
adding
the
event
and
listener
pr.
That
is
one
that
both
brett
and
teemo
have
commented
on.
Do
y'all
wanna
talk
about
that
one.
D
Yeah,
I
actually,
I
have
read,
raise
this
pr.
So
oh.
D
Had
yeah,
so
I
had
some
discussion
points
with
both
tidal
and
commented,
so
I
wanted
to
discuss
few
things
regarding
this.
So
first
comment
that
I
wanted
to
ask
was
titles
commented
that,
like
the
present,
implementation
is
coupled
thoroughly
with
span,
thus
the
span
class,
like
it's
a
lot
dependent
on
span
class.
So
my
question
was
like
when
the
the
listener
wants
to
change
something
or
tinker
something
with
whatever
it
wants
the
log
or
there
is
a
feedback
loop.
D
So
the
thing
the
base
class
of
the
part
where
here
or
secret
can
change
should
be.
What
I
is
the
span
only
like
the
span
has
got
all
the
information
which
can
be
tinkered
to
change
the
content
of
this,
the
information
he
wants
to
see
on
the
zipkin
or
higher
dashboard
right.
So
that
part
the
span
is
the
one
thing
that
should
be
given
to
the
listeners
like
the
api
should
provide
the
listener.
C
Span
would
certainly
be
a
major
one,
is
the
only
is
it
the
only
event?
I'm
not
I'm
not
sure
I
mean
anything.
Could
you
know
in
theory,
anything
could
could
could
fire
an
event
spans,
probably
the
most
important,
but.
C
I
could
imagine
a
tracer
starting
up
or
shutting
down
could
could
trigger
an
event
as
well,
or
there
are
other
things.
D
Okay,
so
okay,
okay,
either
like
the
tracer
or
the
exporter.
Okay,
I
get
that
another
thing
was:
I
was
there
like
when
the
you
we
are
giving
the
user
the
option
to
set
events
and
the
listeners
and
the
events
like
which
listener
he
or
she
wants
to
map
with
which
event.
D
So
this
data
has
to
be
given.
This
data
has
to
be
given
to
our
module
in
some
way
so
presently,
like.
I
have
included
this
data
whenever
the
listener
gives
an
array
or
a
key
value
pair
of
listener
and
events.
So
this
this
span
has
got
another
array
in
which
this
data
is
inputted
or
put
it.
So
timo
commented
that
this
this
will
couple
the
listener
data
with
the
span,
but
do
we
have
got
any
other
option
of
decoupling
like
span?
C
C
A
lot
of
sort
of
event
programming
before
I'm
not
even
sure
how
other
other
libraries
do
it,
but
I
would
imagine
that
we
would
have
like
we
would
expose
a
list
of
events
that
we
can
trigger
somewhere.
C
Don't
we
so
yeah.
So
if
an
event
anytime,
an
event
is
immediate:
it
has
a
for
one
of
a
better
word,
a
key
or
an
identifier.
C
C
Speak
to
it
properly,
but
but
I
guess
what
I'm
saying
is
that
that
the
netcode
would
expose
a
list
of
these
are
all
of
the
events
that
they
can
be.
That
can
be
triggered
and
therefore
subscribe.
D
To
my
line
of
questioning
was
more
that
when
the
user
provides
the
key
value
pair
of
listener
and
event
which
part
of
the
module
do
we
store
it
like
we
have
to
have
a
data
stored
somewhere
so
that
whenever
there
is
event
called,
it
could
be
mapped
to
a
listener.
So
presently
I'm
storing
it
in
span
only,
but
both
of
you
told
that
this
is
quite
a
lot
coupled
with
this
would
couple
provide
a
tight
coupling
with
span
so
which
part
could
be
stored.
D
Like
more
than
I
implemented
with
the
symphony
and
la,
and
both
of
them
have
done
it
type
of
like
laravel,
has
a
global
api
for
everything.
There's
a
global
structure,
running
parallel
to
the
laravel
application,
so
they.
D
Yeah
so
like
build
global
okay,
let
me
raise
a
pr
with
the
global
one
implementation.
Let's
see
so
like,
don't
we
don't
have
anything
like
specification
wise,
which
prevents
global
like
we
had
a
global
blogger
pr
march
few
days
back
so
there's
nothing
preventing
no,
no,
not
no!.
C
B
C
D
Okay
sure
yeah
those
right
my
questions.
Okay,
so
I
think
teemo
is,
has
some
internet
issues
so
whenever
he
is
online,
he
will
have
also
some
comments.
A
All
right
next
pull
request
after
that.
One
is
talking
about
scaffolding,
the
jager,
thrift,
http
exporter.
I
think
bruno
isn't
here
today,
and
I
know
timo
had
mentioned
that
we
should
talk
about
this
when
we're
together.
So
maybe
we
can
do
that.
We
can
have
that
discussion,
async
I'll,
open
up
a
new
thread
in
slack
to
talk
about
that,
just
so
that
we
can
keep
momentum
moving
on
that
pr
and
then
resource
attributes,
resource
input,
attributes
the
span
attributes
which
was
kishon.
A
Who
was
I
thought
sean
was
here,
but
maybe
he
left,
but
that
one
looks
like
it
has.
It
looks
like
it
has
a
recent
activity
and
we're
in
a
good
state,
so
I
think
we're
making
progress
on
that.
After
all
these
get
merged.
A
I
will
I'll
cut
a
new
release
because
there
was
a
there
were
some
people
asking
for
a
new
release
and
that
would
be
release
0.0.6.
A
There's
something
in
the
chat:
sean
has
internet
issues.
He'll
come
back.
Okay,
thank
you!
So
are
there
any?
I
don't
think
there's
any
open
pull
requests
in
the
contrib
repo
right
now,
except
for
one
on
forcefully
setting
service
name
option
on
any
exporter
and
title
is
working
and
our
team
was
working
on
that
with
him.
So
I
think
that
we
have.
A
They
have
good
momentum
there,
no
new
outstanding,
open
bugs
or
discussions.
So
those
are
all
the
main
agenda
topics
that
I
had
for
today,
amber
and
mikhail.
I
know
that
you
both
are
here
after
you
know
new
or
not
attending
for
a
while.
Do
you
have
anything
that
you
wanted
to
bring
up
or
talk
about.
B
No
we're
just
trying
to
get
in
the
cadence
of
attending
again
and
catching
up
on
everything.
That's
been
happening,
so
we're
excited
to
be
here.
A
A
You
know
that's
a
good
question.
I
think
we
have.
Let's
let
me
take
a
look
at
our
project
board
in
our
project
board
under
tracing.
We
currently
have
six
in
progress
and
two
and
four
to
do
tickets.
A
So
we
have,
we
have
a
tag,
that's
called
release
required
for
beta
and
I
think
that
there
so
we
have
probably
about
10
issues
that
we
need
before
we
do
a
beta
release,
but
time
frame
is
very
difficult
to
understand,
especially
since
we
don't
know
how
long
these
are
going
to
take.
A
Yeah
no
spot,
oh
and
thanks
for
the
stale
bot
recommendation
amber.
I
appreciate
that.
A
A
All
right:
well,
if
there's
no
other
agenda
items,
then
we'll
pick
it
back
up
on
slack
good
to
see
everybody.