►
From YouTube: 2022-01-19 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).
B
A
B
Oh,
I'm
feeling
fine.
Luckily,
the
the
symptoms,
weren't
weren't,
very
bad
hurray
vaccination,
but
we
did
get
just
kind
of
like
stuck
because
you
know
I
couldn't
get
on
an
airplane
to
to
come
home,
but
it
ended
up
actually
being
kind
of
a
good
thing
in
a
weird
way,
because
my
step-dad's
super
old
and
we
were
staying
out
on
his
farm
and
he
turned
out.
He
actually
needed
a
bunch
of
help
with
things.
B
B
I
will
say
so
typical
christmas
dinner
right,
small
family
gathering,
maybe
eight
people
like
we
all
got
it
because
somebody
had
it,
but
then
of
course
like
we
all
got
tested
afterwards
and
only
half
of
us
came
back
testing
positive
on
a
pcr
test,
even
though
we
all
had
symptoms
to
some
degree,
it
was
like
quite
clear:
we
had
all
contracted
covet,
so
I
had
seen
some
other
reports
that
omicron
is
like
not
like.
B
The
pcr
tests
are
not
as
accurate
in
terms
of
giving
back
a
higher
percentage
of
false
negatives,
and
so
that
was
interesting
to
experience.
D
I
mean
that
is
interesting.
Yeah
I
mean
like
my
christmas
was
like.
Basically,
I
was
like
stuck
with
a
sinus
infection,
but
because
the
overlapped
of
symptoms
I
was
like
you
could
have
covert,
so
it's
just
like,
and
the
queues
for
pcr
tests
in
australia
are
like
two
to
seven
hours,
depending
on
where
you
go.
Oh.
B
C
Yeah
we
couldn't
find
any
tests,
so
in
our
case
we
were
just
trying
to
travel
over
the
holidays
and
even
though
our
kids
are
vaccinated,
there's
like
a
waiting
period
before
they
consider
them
to
be
fully
vaccinated.
C
So
we
were
required
to
take
a
test
and
we
couldn't
find
any
so
we
had
to
postpone
over
the
vacation
and
we
still
took
it,
but
it
was
probably
a
good
thing
because
you
know
the
flights
were
getting
canceled
over
the
holidays
and
people
waiting
in
airplanes
and
airports
so
kind
of
lucky
in
that
regard,
but
yeah,
I
heard
the
same
thing
that
the
test
itself
isn't
that
effective
right
now
so
yeah
I
don't
know,
but
I
did
see
some
research
there's
two
compounds.
C
Of
course
someone
has
to
bring
this
up
eventually,
but
I
guess
there's
two
compounds
in
cannabis
and
they're
like
well.
Why
can't
we
use
that
so
somehow,
somehow
cannabis
always
sneaks
its
way
in
somehow.
B
Yeah
but
yeah
yeah,
that's
that's
good!
I
am
trying
to
just
spread
that
awareness,
because
I
don't
feel
like
it's
being
spread
well
enough
that
yeah,
if
you
have
coveted
like
symptoms
and
you
get
a
test
and
it
says
you're
negative-
you
should
probably
quarantine.
Anyways
like
you
may
want
to
just
presume
that
you
have
it
just
because
omicron
really
does
seem
to
be
virulent
so
good
on
you,
sean.
C
All
right
I
was
looking
at
the
10,
looks
like
you
just
created
it.
I
don't
see
any
agenda
items,
I
don't
know.
If
folks
have
anything
to
discuss,
maybe
we
can
just
openly
discuss
things.
The
only
thing
I
have
is
I
was
trying
to
follow
up
last
week
regarding
the
otep.
C
I
did
raise
it
in
the
spec
call,
but
I
haven't
been
able
to
follow
up
because
I've
been
distracted
by
other
things,
but
I'll
try
to
follow
up
this
week
to
see
if
we're
going
to
get
a
couple,
people
from
the
tc
to
review
the
otep
and
try
to
help
us
get
on
block,
so
we
can
move
forward
and
then
the
other
update,
I
think,
dennis,
might
have
worked
with
uten,
I'm
not
sure,
but
for
the
rest
of
the
folks
here
that
well
we're
trying
to
solicit
to
get
some
examples
in
python
and
node.js,
and
so
at
least
that'll
give
us
more
right.
C
B
Yeah,
I
I
raised
the
same
things
again
in
the
spec
meeting
this
this
morning.
So
again
pointed
appointed
people
at
the
at
the
otep
it
turns
out.
There
was
actually
some
confusion
about
what
we
were
requesting
through
the
otep.
So
I
I
kind
of
resolved
that
we
don't.
B
We
don't
actually
tend
to
make
rfcs
around,
like
you
know,
proposing
an
agenda
or
a
plan
of
action,
and
so
they
were
a
little
a
little
confused,
but
I
kind
of
you
know
explain
to
them
that
the
the
reason
we're
producing
this
is
we're
trying
to
understand
what
other
people
think
the
scope
of
work
is,
and
we
believe
this
is
the
scope
of
work.
And
if
we
do
this,
we
can
declare
these
things
stable.
But
do
you
agree
that
that
that
sounds
correct
or
not?
C
If
we
still
have,
you
know,
confusion
around
that
I
mean.
Maybe
we
we
can
always
look
to
update
or
write
a
new
otap
that
follows
something
that
they're
more
used
to
you
know
I
can
work
with
dennis
on
that,
but
let's
see
how
it
goes.
I
guess
this
week.
B
Yeah,
I
I
think
it's
it's
fine.
I
mean
in
a
sense
this
otep.
Well,
I
would
love
to
just
see
it
merged
and
get
approval.
It's
not
actually
a
necessary
step
in,
in
the
sense
that
it's
not
that
otep
does
not
itself
propose
code
changes
of
spec
changes
of
any
kind.
So
it's
not
like
another
kind
of
otep,
where
you're
actually
proposing
a
feature
or
something-
and
everyone
wants
to
see
it
all
spec
out
there
before
you
add
it
to
the
spec.
It
did
confirm.
B
You
know
approval
that
it
is
fine
for
us
to
to
go
ahead
and
be
making
these
changes
to
semantic
conventions
without
having
to
write
oteps
for
every
single
one
of
them,
because
that
would
be
annoying
and.
B
Pushed
for
the
instrumentation
working
group
team,
which
I
posted
a
link
to
it's
in
the
the
meeting
notes
from
from
last
week,
but
we
did,
I
did
put
a
team
together
based
on
who,
in
this
and
the
messaging
working
group
said
they
would
feel
comfortable
being
listed
as
an
approver
and
be
willing
to
do
the
work.
B
If
your
name's
not
on
that
list-
and
you
would
like
to
do
that
work,
you
know
just
let
me
know
I'm
happy
to
to
add
you,
and
so
I
poked
them
about
getting
that
getting
that
added
to
the
spec
as
well,
so
that
we
have
a
wider
range
of
approvers
for
for
getting
this
stuff
in
you
know,
just
with
the
again
the
caveat
that,
like
we
do
need
to
be
responsible
with
that
power.
You
know
if
they
turn
around
and
discover.
B
We've
just
been
alley-ooping
our
stuff
in
there
and
and
something
seems
funky
they'll
get
grumpy
with
us,
but
I
think
we're
doing
a
pretty
good
job
of
hashing
out
the
details
before
proving
these
things.
So
that's
that's
my
update
from
this
morning,
spec
meeting
and
so
I'll
keep
following
up
with
the
tc
to
make
sure
those
those
two
things
actually
happen,
but
in
the
meantime,
this
http
spec
change
for
retries
and
redirects,
which
is
kind
of
the
big
one.
B
I
think
that
maybe
this
is
actually
maybe
my
one
agenda
item
is:
are
there
additional
http
things
we
want
to
conquer?
I
know
we
have
that
written
down
in
that
otep.
B
I
was
just
wondering
if
people
had
any
other
agenda
items
related
to
http,
because
we
had
decided
to
punt
on
a
number
of
things
like
security,
for
example,
as
far
as
like
stability
is
concerned,
so
I
was
just
curious
if
if
there
were
any
other
outstanding
items
or
if
that's
actually
the
last
the
last
one
before
we
can
start
looking
at
declaring
it's
stable.
D
Well,
we
want
to
move
in
the
direction
where
the
semantic
convention
is
this
fast
evolving
process,
rather
than
like
this
slow
moving
thing
because,
like
we
ourselves
having
a
like
a
an
internal
goal,
a
simple
observability
powered
by
a
hotel,
but
we
want
to
make
those
changes
like
like
the
semantic
conventions
in
a
very
early
stages,
that's
subject
to
high
like
fluctuations
and
changes,
and
we
want
to
be
able
to
help
but
not
slow
down
the
simplification
of
adopting
observability,
so
anything
that
we
can
do
that
helps
speed
up
like
even
if
it's
just
like.
D
We
have
thought
about
these
things,
but
we
all
agree
agree
about
these
four
components:
let's
get
these
like
smaller
parts
merged
in
and
then
we
can
look
at
adopting
that.
I
know
it
comes
with
like
high
change,
churn
or
potential
like
redaction
and
like
removing
and
stuff
like
that,
but
I
think
our
internal
goal
of
simplifying
observability
make
like
a
lego,
brick,
dashboards
and
alerts
in
a
sense
where
you
can
pull
and
sort
all
these
things
together
and
build
your
observability
tooling
suite
together.
B
Yeah
totally-
and
I
think
I
think
we're
we
are
pretty
much
there.
The
main
thing
that's
been
slowing
us
down
honestly
is
not,
I
think,
is
just
getting
this
working
group
added
to
the
spec
as
approvers
the
http,
retries
and
redirects
pr
is
is
approved
at
this
point.
Dennis
needs
to
resolve
a
couple
conversations,
but
but
that
one's
in
the
bag-
and
so
my
hope
is
we'll-
be
able
to
knock
down
any
any
further
ones
quickly.
B
There
is
one
piece
of
work,
though,
that
would
make
me
rest
easier
if
it
was
done,
which
is
part
of
declaring
things
stable
means
from
that
point
forwards.
If
we
do
want
to
change
those
conventions,
we
have
to
define
and
implement
a
schema
versioning
for
that
item
in
the
collector.
That's
that's,
that's
the
main
thing
stable
doesn't
mean
we'll
never
ever
change
it,
but
it
does
mean
the
only
changes
we
can
make
going
forwards
are
ones
that
would
be
compatible
with
a
forward
and
backward
schema
versioning.
B
I
guess
a
backwards
schema,
versioning
system
so
that
the
people
who
are
using
the
old
schema
could
ingest
new
stuff
and
just
have
have
it
translated
in
the
collector,
so
their
dashboards
don't
break
when
we
add
or
change
something.
So
one
is.
We
have
to
make
sure
like.
We
actually
do
that,
like
don't,
propose
change
and
two
implement
it,
and
we
have
never
ever
done
that
so
and
there's
currently
not
like
something
baked
into
the
collector
for
doing
that
in
some
straightforward
fashion.
B
B
We
haven't
haven't
done
that
work
yet
so
that
that's
that's
a
place
where,
if
people
do
have
like
code
cycles,
I
think
it
would
be
really
valuable
to
to
figure
out
how
we're
actually
going
to
do
this
for
the
collector,
and
I
think
it's
going
to
be
a
useful
thing
to
have
in
general,
since
we're
trying
to
really
stabilize
a
lot
of
things
in
open,
telemetry.
D
D
B
Yeah,
no,
that's
that's
awesome.
I
mean
the
collect
it's
totally
feasible
to
do
this
like
in
a
sense.
I
don't
think,
there's
anything
where
most
of
the
changes
we
want
to
make
you
could
cobble
together,
essentially
out
of
like
collector
rules
with
existing
plugins.
It's
just
that
like
even
if
it's
implemented
is
that
under
the
hood.
We
don't
want
that
to
be
the
the
end
user
experience.
B
You
know
we
just,
but
I
think
there
are
some
open
questions
about
what
that
end
user
experience
actually
is
so
that
that's
that's
where
I
think
it
would
be
awesome
yeah
if
you
guys,
are
willing
to
take
a
crack
at
it.
B
I
just
suspect
it's
a
can
of
worms
where
you
know
the
dumb
version
is
really
straightforward
and
like
the
version
with
all
the
features
people
actually
trying
to
manage,
schema,
migrations
and
stuff
in
like
a
production
environment
with,
like
you,
know,
rolling
things
out
across
the
board-
and
you
know
like
that's
that's
where
it
gets
tricky
because,
yes,
you
can
down
sample,
you
can
like
downgrade
so
your
old
stuff
doesn't
break,
but
then,
when
you
want
to
make
dashboards
that
use
the
new
stuff
like
like,
how
do
you
manage
that
scenario?
B
Yeah
so,
and
I'm
not
totally
sure
what
the
what
the
interface
looks
like
for
that?
You
know.
That's
both
efficient-
and
you
know
easy
to
use-
has
been
thinking
about
this.
A
lot
so
it'd
be
good
to
hear
what
his
current
data
is.
There
I
think
yeah
yeah,
I'm
sure
he
should
have
a
plan
in
his
mind.
That's
my
guess
so
yeah
he
probably
does.
I
think,
he's
probably
too
busy
to
implement
this,
but
yeah.
B
Reviewer,
who
would
be
able
to
give
you
fabulous
feedback
on
on
the
whole
caboodle.
B
But
great,
that's
awesome.
I'm
glad
to
hear
that
y'all
have
time
sean,
because
that's
that
that
would
make
me
happy.
D
I
have
a
lot
of
things
that
I
would
like
to
add
to
the
collector
some
of
it
internally
from
at
last
season's,
like
rate
limiting
and
like
span
to
metrics
things,
but
I
have
free
time
to
do
things.
It's
just
trying
to
figure
out
what
is
the
most
important
thing
to
help
the
moving
the
needle
forward
that
I
just
don't
know
so
if
this
helps
me
use
the
needle
for
it,
I
can
move
shuffle
what
I
do.
B
I
I
think
this
is
probably
the
most
important
missing
piece,
so
I
would
love
to
see
that
let
me
just
pull
up
as
far
as
like
http
is
concerned.
B
Oh
zoom,
you
don't
have
the
preferences,
never
mind,
I
don't
think
I
can
give
it
these
preferences
without
leaving
sorry.
I
recently
wiped
this
machine,
so
I
can't
share
share
screen.
Maybe
michael,
would
you
mind
sharing
the
the
otep,
maybe
it'd
be
helpful
to
just
review
what
we
said.
We
were
going
to
do
as
part
of
v1
sure.
B
C
B
B
Yeah
and
I
believe,
we're
arrow
status
defaults.
I
believe
that
that
change
has
already
gone
into
the
spec
required
attribute
sets.
This
is
essentially
ensuring
that
these
things
are
all
being
set.
B
We
might
need
to
have
some
spec
language
changed,
but
you
know
the
other
part
is,
you
know
actually
cleaning
up
the
instrumentation,
which
is
maybe
just
in
general,
another
big
bag
of
work.
You
know
once
we
put
this
stuff
in
the
spec,
that's
great,
but
now
it
just
means
all
the
instrumentation
is
update
and
let's
get
updated.
B
I
believe
this
context,
propagation
issue
was
kind
of
about
when
we're
doing
retries,
do
we
use
the
same
span
or
or
do
we
create
new
span
ids
every
time
and
we
opted
for
create
new
span
ids
when
you
can,
I
don't
know
if
anyone
else
has
context
on
this
context,
but
I
believe
that
was
the
one
issue,
so
I
think
we're
done.
I
guess
is
what
I'm
saying.
C
I
think
so
too.
I
think
it
was
just
more
about
making
sure
we
have.
You
know
two
additional
examples
in
other
languages
right.
B
Yes,
for
this
particular
pr
and
marking
it
stable
yeah,
I
think
I
think
that's
really
it
I'll
I'll
double
check
I'll.
Try
to
double
check
whether
this
bit
about
required,
attribute
sets
is
actually
been
implemented
in
spec.
If
not,
it
shouldn't
be
a
complicated
pr
to
get
that
added,
but
yeah
with
some
additional
examples.
I
think
we're
pretty
much
pretty
much
there,
which
is
why
having
this
collector
work
get
moving,
I
think,
would
be
would
be
great.
B
But
then
also,
actually,
maybe
a
question
is:
how
do
we
actually
want
to
approach
dealing
with
instrumentation
because
instrumentation's
now
out
of
date,
around
retries
and
redirects
once
that
gets
in
there,
so
that
could
be
improved
in
pretty
much
every
http
instrumentation
in
the
various
contrib
libraries
that
open
telemetry
has.
B
There's
also
all
these
v-next
things.
If
we
don't
want
to
worry
about
those,
then
I
would
say
updating
all
the
instrumentation
is
probably
the
next
next
big
step.
C
I
would
agree
with
that.
I
think
in
previous
conversations
like
prior
to
the
holidays,
with
that,
let's
try
to
get
to
v1
and,
let's
not
distract
ourselves,
would
be
next.
So
let's
try
to
get
that
done
first
and
if
we
can
get
it
done
in
the
early
part
of
this
year.
C
Well,
first
quarter
at
least,
and
we
can
start
to
address
some
of
these
other
ones
and
as
far
as
like
obtaining
the
instrumentation
libraries
or
whatnot,
I
would
I'm
guessing
that
we'd
want
to
you
know
once
it
once
we
have
everything
stable,
then
we
need
to
make
sure
that
the
respective
sigs
language
sigs
are
aware
and
then
we'll
have
to
find
folks
to
to
update
accordingly,
I
want
to
say.
B
Yeah
one
issue
is
so
some
of
these
libraries
may
have
maintainers,
which
is
nice,
but
I
think
a
number
of
them
were
ports
that
happened
and
essentially
fell
in
the
lap
of
the
core
maintainers,
like
the
sdk
maintainers,
essentially,
and
with
metrics
and
logs
in
full
force.
Right
now
like
they
generally
feel
like
they
don't
have
the
bandwidth
to
also
be
paying
a
lot
of
attention
to
instrumentation.
B
Which
means
there's
probably
a
pile
of
these-
that
if
we
went
in
and
did
the
work,
then
we
could
mark
them
as
stable,
which
is
what
we
want,
but
I
think
there's
a
number
of
them
that
that
that
probably
won't
happen.
Unless,
unless
we
do
it.
B
C
B
Yeah
and
the
registry
could
be
potentially
useful
here,
maybe
as
a
parallel
effort
here,
I've
been
wanting
to
get
the
registry
up
to
date,
open
telemetry's
got
a
registry
on
its
website
which
categorizes
these
things.
So
in
theory,
you
should
be
able
to.
B
You
know,
just
look
search,
do
a
search
for
http
tag
and
see
see
all
the
things,
but
I
think
that
registry
is
like
out
of
date
in
the
sense
that
there's
there's
probably
more
things
out
there
than
what
is
listed.
B
I'll
put
a
thing
I'll,
add
a
modification
to
the
registry
as
well
to
mark
whether
things
are
experimental
or
stable,
and
so,
if
we
can
get
the
registry
filled
out
and
then
just
everything
marked
as
experimental,
then
then
we
could
use
that
as
kind
of
like
our
our
list
of
of
targets
and
then,
as
we
get
them
stabilized,
we
just
update
their
their
registry
entry.
B
B
A
button
up
at
the
in
the
top
next
to
docs
it
says
registry,
and
so
this
is
what
we
have
right
here.
If
you
scroll
down,
which
is
a
fold
issue,
I
want
to
fix.
So
this
is
like
everything
that
we
know
about.
B
So
this
is
in
theory,
if
not
all
the
http
instrumentation,
certainly
a
lot
of
it.
B
As
well
as
like
collector
components
and
stuff
like
that,
so
I
would
love
to
I'm
working
on
the
website
right
now.
It's
like
kind
of
my
other
big
projects
clean
the
website
up.
So
if
we
try
to
make
use
of
the
registries
part
of
this,
that
might
be
a
helpful
run
through
with
the
registry
as
well
to
figure
out
what
about
it
could
be
improved.
Make
it
more
useful.
B
But
and
updating
it
is
super
easy,
it's
just
a
markdown
file
that
that
you
add
to
you,
add
to
the
website
repo.
So
it's
just
a
just
a
pull
request,
copy
paste,
the
markdown
template
and
fill
out
a
couple
fields.
B
Yeah
and
that'll
get
us
there.
We
we
had,
we
did
have
another
line
of
work.
We
were
talking
about
before
break,
which
was
building
tooling
around
instrumentation.
B
I
don't
think
that
should
be
a
blocker
for
just
going
in
and
updating
these
things,
but
you
know
as
part
of
doing
that,
it
would
be
great
to
see
if
we
could
kind
of
port
some
of
the
the
instrumenter
object
stuff
that
they've
been
building
in
java
land
seems
really
useful
and
also
test
harness
figuring
out
how
to
do
a
test
harness
that
could
help
us
identify
whether
or
not
things
are
in
or
out
of
compliance
with
the
semantic
conventions.
B
So
that's
some
some
more
tooling.
I
forget
who
said
they
were
interested
in
that
someone
was
interested
in
working
on
that
harness.
Let's
start
at
the
next
big
thing,
I'd
like
to
work
on
awesome
planning
and
doing
that
this
quarter
awesome,
yeah
and
yeah.
I
don't
want
that
to
like
block
us,
but
but
that
that's
all
of
that
work
is
the
stuff
that's
going
to
make
this
this
stuff
easier
to
maintain
in
the
future.
B
You
just
add
them
to
that
instrument
or
object,
and
then
update
the
dependency
in
all
these
instrumentation
packages,
and
now
they
all
start
producing
that
producing
those
metrics,
or
at
least
in
most
cases,
to
be
able
to
do
that.
B
So
so
that's
that's
just
stuff
that
will,
in
the
long
run,
make
it
easier
to
maintain
these
things
and
hopefully
get
us
more
outside
maintainers
for
for
some
of
them.
A
C
Okay,
cool:
do
you
think
there
anybody
else
has
anything
else
they
want
to
bring
up,
because
I
feel
like
we
have
enough
to
follow
up
on,
and
you
know
just
trying
to
keep
our
focus
on
b1.
So
maybe
a
good
time
to
you
know,
stop
here
and
and
try
to
focus
on
our
respective
areas
and
then
circle
back
next
week.
C
Okay,
all
right,
yeah
ted,
just
ping
me
offline
on,
like
specifically
the
thoughts
that
you
had
like
badges.
Whatever
you
know.