►
From YouTube: 2020-12-09 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
Doctor
strange,
is,
I
don't
know,
what's
it
what's
he
call
that
building
in
new
york,
where
he
hangs
out
yeah
anyhow,
the
window
is
super
cool.
So
that's
why
it's.
B
C
Sorry,
I've
been
mostly
missing
here
bob
I
I
my
role
at
new
relic
expanded
like
exponentially,
and
I
am
yeah
and
you
know
I've
been
a
little
bit
underwater.
A
A
C
A
Okay,
so
a
couple,
a
couple
like
very
very
top-level
things:
we're
going
to
use
major
minor
and
patch
versions
for
open
telemetry,
just
like
normal
december,
are
y'all
used
them
for
your
places
of
business
cool
all
right.
So
the
plan
is
to
implement
version.
One
point
x,
point
x
that
will
include
that,
like
when
we
go
live
with
ga
in
the
distant
future.
That
will
include
the
trade,
the
tracing
package
as
stable,
and
then
it
will
include
the
matrix
packages
experimental
and
we
don't
have
logging
yet.
A
So
I
want
to
include
that
so
the
major
there's
no
plan
to
increment
the
major
version
at
this
time.
The
maintainers
have
come
up
with
this
concept.
They
call
them
signals
and
what
a
signal
is
is
log
logging,
metrics
and
tracing
are
all
different.
They
call
those
signals
and
we
won't
increment
the
major
version
of
this
package
until
another
signal
is,
is
developed
like
tracing
v2
or
whatever
other
cool
telemetry.
A
The
industry
decides
to
start
using
next
to
do
some
work,
so
the
goals
of
our
this
versioning
and
release
document
are
to
talk
about
how
we
want
to
handle
api
and
sdk
stability,
and
then
the
methods
that
we're
going
to
use
are
going
to
be
we're
going
to
leave
them
in
here.
So
we
were.
I
was
talking
with
the
other
maintainer
about
how
they're
doing
it
in
java
and
javascript,
and
we
were
talking
about
how
to
segment
mature
signals
from
experimental
signatures
signals
in
the
api.
A
So
we
talked
about
doing
that
with
an
api
experimental
folder
because
we
feel
like
that
might
be
a
good
way
to
explicitly
delineate
stable
from
things
that
are
that
we're
currently
experimenting
on.
Does
anybody
have
a
preference
on
that?
Does
anybody
have
any
experience?
I
don't
have
any
experience
trying
to
move
trying
to
move
packages
around
in
php
from
experimental
to
non-experimental
places.
I
don't
know
how
you
all
have
done
this
previously
either.
D
Yeah,
I
don't
really
have
too
much
experience
with
that
either.
Okay,.
A
All
right,
that's
that's
totally
fine.
I
was
just
curious
to
see
if
anybody
had
any.
I
can
just
like
I'll
ask
again
once
in
the
channel
and
then
I'll
come
up
with
a
fine
like
a
final
idea
for
this
and
see
what
other
people
think,
but
that
idea
right
now
is
just
to
have
an
experimental
api
folder
and
then,
when
something
moves
out
of
experimental
and
into
general
availability,
we'll
just
move
move
that
item
from
one
folder
to
another
and
change
its
reference
points.
A
The
other
thing
that
we
were
talking
about
was
transitive
dependency
resolution.
Does
anybody
have
to
deal
with
transitive
dependency
resolution
php,
because
this
is
something
that
was
like
making
my
brain
hurt
a
little
bit
while
I
was
trying
to
think
about
it.
B
No,
no
yeah.
A
Okay,
well,
then,
we'll
leave
this
as
is
for
now
this
isn't
set
in
stone,
but
this
is
ju
we're
just
gonna.
I
think
we're
just
gonna
sort
of
follow
that
pattern
of
experimental
folder
to
not
experimental
and
then
we'll
just
deal
with
the
dependencies
as
they
come.
I
don't
think
we'll
have
any
hard
dependencies.
A
I
think
this
becomes
a
much
more
difficult
for
problems
with
languages
that
are
compiled
rather
than
interpreted
because
they
have
to
like
publish
a
binary
that
has
all
these
individual
bits
and
pieces
and
they
like
it
makes
it
a
lot.
They
have
to
ship
the
whole
thing
wholesale
all
the
time
which
is
different
than
what
we
have
to
do
so
anyway.
That's
that's.
That
was
that
the
other
thing
that
I've
been
working
on
is
dallabor.
Karlavik
did
a.
A
A
Yeah
yeah
so
there's
this
document
that
was
done.
He
created
us
a
separate
project
and
ran
through
using
our
libraries
in
the
way
that
he
he
expects
a
normal
end.
User
would
attempt
to
use
them,
and
he
gave
us
lots
of
feedback
on
these
on
our
library,
based
on
the
things
that
he
was
trying
to
implement
from
scratch.
A
So
from
that
I
came
up
with
it.
I
made
a
new
project
board
for
they
use
user
research
feedback
improvements.
So
the
all
of
these
things
in
the
to
do
column
are
things
that
were
explicit
criteria,
explicit
callouts
from
his
ex
his
test
run
of
our
library.
So
those
would
be
really
great
new
things
for
people
to
work
on,
because
they're
all
pretty
they're
all
pretty
siloed
and
they're
all
pretty
small
chunks
of
work.
A
So
that's
that's
where
most
of
the
new
issues
came
from,
I
cleaned
up
some
of
the
old
issues
a
little
bit
a
little
while
back
and
I
started
working
on
php8
support
and
I
think
that
I'll
probably
have
a
pr
for
that
up
this
week
or
maybe
next
does
anybody
else
want
to
talk
about
anything
that
they
were
working
on?
Are
they
any
blockers
or.
D
Anything
I
can
give
a
quick
update
on
what
I'm
working
on
so
the
trace
date.
Stuff
is,
is
all
done.
I
haven't
put
up
a
pr
yet
I'm
working
on
the
the
testing
service
and
I
just.
D
D
Yeah,
just
testing
it
a
bit
more
than
the
unit
tests
right
now,
because
that
doesn't
catch
all
the
edge
cases
yeah.
I
haven't,
got
the
test
service
up
and
running.
Quite
yet,
I'm
just
doing
it
like
locally
before
I
actually
incorporate
it
into
a
make
type
thing
in
the
repo,
but
I
think
once
I
finish
that
up
I'll
put
both
of
them
up
as
sprs
so
yeah.
I
haven't
actually
been
working
on
it.
D
The
last
couple
weeks
because
of
the
holidays,
and
I've
been
on
on
call
rotation
on
our
team
but
yeah
I
can
get
to
it
this
week
and
and
hopefully
try
to
wrap
something
up
by
next
week.
Nice
I'll
be
around.
If.
A
You
have,
if
you
want
to
bounce
ideas
or
if
you
won't
need
a
pr
review
or
whatever.
A
B
So
what
do
you
think,
which
project
do
you
think
is
most
in
need
of
attention
at
this
point?
Is
it
the
user
feedback
improvements,
one
or
one
of
the
other
project
boards?
What
should
I
look
at
to
pull
issues
from.
A
So
I
would
either
say
the
user
feedback
improvements
or
tr
or
anything.
That's
on
the
anything
that's
in
the
tracing
board,
but
it
doesn't
look
like
there's
a
ton
of
stuff
on
the
tracing
board
right
now,
so
yeah
anything
from
the
user
feedback,
user
user
research
feedback
would
be
really
great
amber
that
there's
those
are
all
really
like.
I
had
spent
a
lot
of
time
making
sure
that
those
were
very
well
scoped
and
very
well
documented
tickets,
so
they
should
be
relatively
straightforward.