►
From YouTube: 2020-09-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
A
C
No,
it's
a
product
off
site,
so
once
a
year
they
do
it.
I
just
started
in
april,
but
apparently
once
a
year,
every
september
they've
got
a
big
product
off
site
where
everyone
comes
together
and
they
just
synergize.
I
guess,
is
the
point
of
it,
but
it's
all
online
this
year,
obviously.
A
C
A
C
So
I
had
taken
some
time
off,
but
previously
I'd
been
at
intel
on
a
small
company
called
veriwave
who
is
later
bought
out
by
oh,
I
forget
who
they
were
bought
out
by,
but
yeah
yeah.
I
was
with
intel
about
seven
years
and
then
the
other
company
about
a
year.
A
You
yeah
amber
that's.
Printer
drivers
are
the
worst.
C
C
So
no
users
would
buy
it.
It
had
three
ports
on
it
like
it
was
so
long
ago
that
it
had
the
two
parallel
and
the
one
serial
port
nice
yeah.
A
But
I
my
degree
is
in
computer
engineering,
but
I
never
got
to
work
in
the
hardware
hardware
space,
except
for
I
worked
at
an
automation,
engineering
company
as
a
co-op,
and
then
I
realized
I
never
ever
want
to
do
this
ever
so.
Then
I
was
like
software
only
and
changed
to
computer
engineering
from
electrical,
and
that
was
it
great.
C
A
A
A
They
open
telemetry
exporters
like
the
open,
telemetry
format
has
been
finalized
and
the
exporter
is
pretty
much
finalized.
So
I'm
gonna
start
working.
A
I've
started
working
on
that
this
week
and
I'm
going
to
continue
working
on
it
next
week,
it's
going
to
take
putting
in
a
new
it's
going
to
take
putting
in
some
new
logic
into
our
tracer
and
eventually,
probably
our
metrics,
and
when
we
have
them
logging
and
after
we
have
all
I'm
going
to
focus
solely
on
the
tracing
portion
first,
because
I
think
that's
the
most
important
one
for
us
to
drive
through.
A
It
also
uses
grpc
by
default,
which
is
very
annoying
in
php.
I
don't
know
if
y'all
have
tried
to
deal
with
grpc
and
php
before
it's
just
it's
a
battle
uphill,
so
I'm
starting
with
the
http
spec,
even
though
that
isn't
the
default.
A
I
think
that'll
help
me
to
learn
a
lot
about
how
this
particular
part
of
the
spec
works
and
then
it'll
help
with
the
grpc
adoption
later
and
then
we
can
sort
of
build
on
the
http
spec,
and
I
also
put
together
the
two,
the
two
project
boards
this
week,
the
one
for
there's
one
for
tracing
and
one
for
metrics.
If
you
go
to
our
github
project
project
and
then
you
click
on
the
projects,
tab,
there's
two
projects,
one
for
tracing
one
for
metrics,
and
if
you
have
anything
on
that
board,
we
can
move
it
around.
A
A
So
if
you
click
on,
if
you're
in
our
in
our
project-
and
you
click
on
the
projects
button
at
the
top
of
the
screen,
you
can
see
a
metrics
and
tracing
it's
two
metrics
and
pricing
tracing
boards.
Obviously
the
tracing
one's
a
little
bit
more
full
because
it's
a
little
bit
more
full-fledged,
there's
four
statuses
that
you
can
have
on
for
a
ticket
to
do.
These
are
all
the
definitions
that
I
use
at
my
work.
So
I
just
happily
dragged
them
over
here
because
it
was
convenient
for
me.
A
If
anybody
wants
to
change
them,
that's
fine,
but
we
have
a
to
do
status,
which
means
that
something
needs
to
be
done,
but
is
not
actively
being
worked
on.
We
have
an
in-progress
status,
which
means
that
somebody's
actively
working
on
that
particular
item.
We
have
a
pending
review,
which
means
you've
either
opened
up
a
draft
or
a
little
pull
request
and
you're
soliciting
feedback
or
you're
waiting
on
something
else.
For
this
to
be
able
to
be
merged
and
then
done
is
completed,
everything's
done
the
code
is
merged
and
we're
all
ready
to.
D
A
Yeah,
you
can
move
either
way
on
this
project
board.
So
if
you
have
something
that's
pending
a
review
and
you
want
to
get
back
to
working
on
it,
you
can
drag
it
back
to
in
progress.
If
you
have
something
that's
in
to
do,
and
you
want
to
start
working
on
it,
you
can
move
it
to
progress.
So
I'm
going
to
leave
this
as
is
for
now,
so
if
you
want
to
pick
up
any
work,
that's
on
this
board.
That's
completely
fine!
This
is
just
going
to
be
a
really
great
way
to
communicate
it
across
the.
A
C
Yeah
thanks
for
putting
those
boards
up
bob,
I
think
that
will
help
a
lot,
especially
to
you
know,
make
sure
everyone
is
working
on
one
thing
and
they
see
what
other
people
are
working
on
so
yeah.
I
haven't
had
time
to
look
at
it.
We've
been
I've
been
in
the
off
site
all
day,
but
I'll
look
and
see.
Is
there
anything
that's
like
higher
priority?
You
think,
since
I
am
not
quite
into
any
of
those
issues
yet.
A
So
I
think
that
there
is
one
that's
called
the
finish
is
remote
function
would
be
a
good
one.
I
know
that
family
was
talking
about
using
looking
at
the
w3
w3c
trace
context,
so
maybe
you
could
communicate
with
that
with
him
and
see
if
he's
still
planning
on
working
on
that
and
implementing
the
samplers
is
also
a
pretty
good
one,
but
that
might
be
a
good
one
for
shove,
nick
because
he
was
working
on
the
probability
sampler.
That
would
be
like
a
good
next
natural
extension
and
then
associating
spans
with
their
tracer
providers.
A
Another
one
that's
like
a
very
narrow,
scoped
and
not
blocked
ticket.
So
any
of
the
ones
that
are
into
doing
the
trade
on
the
tracing
board
would
be
fine.
I
would
say
amber
for
you
that
is,
is
remote
or
that
w3
c
trace
contact
spec
would
be
priority
just
because
those
seem
like
they
would
fit
into
your
wheelhouse.
C
A
And
see
yeah
anything
that's
in
the
in
to
do
would
be
perfect.
I
don't
know,
I
actually
don't
know
the
answer
to
this,
and
maybe
you
could
help.
Can
you
if
you
go
to
that
board,
can
you
move
things
on
that
board
or
is
that
something
that
I'm
only
simple.
C
C
A
A
A
That's
a
bummer
okay!
I
will
follow
up
with
the
with
the
other
maintainers.
If
not
I
know,
jody
is
also
helping,
so
she
can
and
she's
a
an
official
triager
now,
so
she
should
be
able
to
move
stuff
across
the
board
too.
That's
really
annoying,
but.
C
I
was
working
on
it
and
also
what
the
status
of
it
is
like.
A
I
think
that
I
think
that
that
would
be
more
than
sufficient.
It's
just
like
it's
or
talk
about
and
get
it
just
some
way
to
communicate
that
you're
working
on
something
I'm
happy
to
move
things
around
on
the
board
too.
If
I
need
to,
but
because
we
don't
want
to
get
into
that
state
where
somebody
else
starts
working
on
something
that
you're
planning
on
working
on
that's
frustrating
for
everybody.
D
A
Can
you
can
you
pronounce
your
name
for
me?
I
was
looking
at
it.
I
didn't
want
to
mispronounce
it
yeah.
A
D
A
A
D
A
So
I
think
that
I
will
my
plan
for
your
pr
is
I'll,
let
benjamin
I'll
probably
get
better
until
friday
to
review.
I
know
he
was.
I
think
he
was
really
busy
with
his
normal
day-to-day
work,
so
if
he
doesn't
merge
it
by
friday,
I'll
just
or
if
he
doesn't
review
it
by
friday,
I'll
just
merge
it,
because
we
can't
just
like
wait
for
wait.
Wait
for
weeks
on
people,
that's
like
sort
of
the
mentality
we've
been
taking.
A
What
yeah
yeah
well
welcome
to
the
project
and
welcome
to
the
corporate
world?
I
guess
we
yeah
the
other
thing
that
we're
going
to
talk
about
at
the
end
of
our
meeting
today
is
the
compliance
matrix,
and
that
will
give
you
a
lot
of
really
good
ideas
of
things
to
work.
On
too,
that's
going
to
be
really
nice
because
it
will
give
you
the
ability
to
work
on
things
that
are
in
your
wheelhouse.
A
E
Yeah
so
over
the
last
week
I
checked
out
in
homes
elementary
and
I
was
working
on
some
issues
on
naming
updates,
but
then
I
fit
a
blocker,
I'm
actually
finding
this
real
difficult
to
see
how
things
come
together
to
make
the
system
work.
So
I'm
still
trying
to
look
around
and
see
what
I
can
learn.
A
Cool,
if
you,
if
you
as
you're,
figuring
out
the
docker
bits
and
if
you
have
any
additional
questions,
feel
free
to
reach
out
in
the
channel,
we
try
and
be
helpful
in
there.
So
if
you
have
any
questions
or
want
to
talk
about
through
any
implementations,
I
appreciate
your
pr's
with
the
name
changes
that
was
very
helpful.
A
Cool
all
right,
the
last
thing
that
I
had
on
the
agenda
for
today
was
the
spec
compliance
matrix.
Has
that
have
you?
Has
anybody
seen
this
yet
or
is
this
or
is
this
something
that's
new
to
everybody.
A
Okay,
posting
it
in
the
chat,
so
this
spec
compliance
matrix
is
a
matrix
of
all
of
the
implementation
details
that
we've
either
completed,
or
we
need
to
complete
it's
for
every
language,
there's
a
column
for
php.
It's
really
sort
of
a
goofy
display
culture
for
this
plus
means
that
the
future
has
been
implemented.
A
Minus
means
that
the
language
is
not
planning
on
supporting
it,
and
a
blank
cell
means
that
it's
not
known
and
most
likely
the
way
that
I've
dealt
with
that
in
php
is
I'm
pre,
I'm
almost
certain
that
it
has
not
been
implemented.
A
So
if
you
are
interested
in
looking
at
anything
in
particular
on
this
board,
we
can
make.
I
was
planning
on
making
tickets
for
all
of
these,
but
that's
a
lot
of
tickets
to
make,
and
I
think
that
things
change
quickly.
So
if
you
would
like
to
look
at
anything,
that's
on
this
compliance
matrix,
we
can
bring
it
up
in
our
channel
and
we
can
create
separate
tickets
for
it
or
we
can
talk
through
implementation
strategies
or
whatever,
but
I
just
think
it's
a
good
thing
for
people
to
see
that
c
available
because
it
lets.
A
You
know
what
the
state
of
the
open
telemetry
php
is.
Currently
what
things
still
need
still
need
some
work
or
have
not
yet
been
introduced
yet
so,
if
you
haven't,
if
you
want
to
review
that
and
have
any
questions
about
it,
I'm
more
than
happy
to
talk
through
it.
A
A
I
think
we're
getting
to
a
point
now
where
we
have
all
the
things
that
are
required
for
a
0.0.1
alpha
release,
but
I
wanted
to
make
sure
that
we
had
consensus
among
that
or
a
consensus
on
that
before
we
just
pushed
that
into
the
wild.
So
I'm
planning
on
talking
through
that
in
the
getter
channel,
so
that
we
can
get
people
there
in
other
time
zones
and
that
have
conflicts
with
this
meeting
or
whatever.
A
Let
them
talk
through
whether
or
not
we're
ready
for
an
alpha
release,
because
there
have
been
a
lot
of
contributors
on
this
project,
and
I
want
to
make
sure
that
everybody's
on
the
same
page
before
we
do
that
the
release
notes
for
that
are
in
the
open,
telemetry
specification
repo.
If
you're
curious
about
it,
it
has
all
the
success
criteria
that
you
need
for
an
alpha,
0.0.x
release
and
then
beta
and
then
a
ga
release.
A
So
if
you
have,
if
anybody
has
any
questions
or
concerns
on
that,
I'm
also
happy
to
talk
through
that
too.
But
it's
that's
really
exciting,
because
it's
something
that
we've
been
sludging
towards
for
a
while
and
now
I
finally
get
to
do
some
sort
of
public
release
and
get
some
feedback.
I
think
the
public
release
with
feedback
is
how
we're
going
to
be
able
to
start
rapidly
iterating
that
our
project
will
come
to
a
crossroads
where
it's
difficult
to
maintain
any
momentum,
because
we
don't
have
any
real
users
and
we
don't.