►
From YouTube: 2022-05-05 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
C
D
D
Backflow
from
no
one's
told
me
about
inspecting
backflow,
yet
this
is
yeah
random.
So
I
think
it's
one
of
those
funny
things.
I
think,
if
you
don't
install
a
backflow
device,
then
you
don't
have
to
get
one
inspected,
but
so
basic
idea,
we've
got
a
tiny
farm,
large
garden
and
we
run
the
irrigation
for
that
off.
Of,
like
oh.
D
A
It's
on
my
it's
on
my
sprinklers.
E
D
A
C
Glad
to
be
here
all
right,
that
said,
let's
let
me
pull
up
the
agenda.
A
I'm
super
far
behind
on
everything
on
reviews.
Couple
notes,
patrice
is
gonna,
I
don't
think
I
don't
know
if
he
posted
but
patrice
is
out.
A
Excuse
me
he's
out
till
may
9th
and
then
he's
kind
of
50
time
in
may
and
june.
A
So
all
out
of
office
first
week
of
may
tail
end
of
may
keep
posting
anything
changes,
so
yeah
less
less
patrice
time
working
on
the
site.
So
I
think
what
we
should
focus
on
is
trying
to
tackle
stuff
that
doesn't
need
site
changes
basically
and
really
get
started
on
content
or
content.
Rework
that
sound
reasonable
to
folks.
A
Cool,
so
I
know
I
owe
a
lot
of
people
reviews
I
will
get
around
to
that,
although
I
think
ted
you're
also,
you
are
able
to
review
things
right,
who
I.
F
A
E
Perhaps
yeah
I
mean,
assuming
like
nothing,
weird
happens
with
honeycomb
and
they're,
like
hey,
open,
telemetry,.
E
Yeah,
I
I
think
they're
they're
definitely
gonna
want
to
sponsor
my
work
and
then
even
outside
of
that,
I
think
I'm
going
to
want
to
spend
some.
A
A
A
D
A
E
A
Then
I
will
add
you
as
an
approver
because
I
think
I
think.
E
It
might
need
to
be
yeah,
it
might
need
to
be
reset,
because
I
think
you.
A
G
Would
would
work
for
me,
I
mean
I
do
this
also
a
little
bit
on
this
side
so
because
I'm
more
a
product
manager
now,
so
I
try
to
keep
out
of
the
coding
stuff
a
little.
B
G
Not
getting
in
the
way
of
my
engineers
so
yeah,
I
will
be
on
pto
next
week,
but
but
after
that
I
mean
I
I
try
as
everybody
else
to
to
bring
in
a
few
hours
per
week
to.
A
A
Yeah
and
to
be
like
super
honest,
I'm
really
strongly
starting
to
think
about
trying
to
find
another
maintainer
or
two
because
them
now
that
I
am
like
people
manager
and
have
more
people
to
manage,
like
my
time,
is
getting
super
split
up
yeah,
especially
if
patrice
is
going
to
be
out
yeah.
So,
let's.
A
So
if
yeah
so
think
about
it,
if
it's
something
you
would
be
if
you
might
be
interested
in
becoming
a
maintainer
for
this
think
about
it.
Let
me
know.
Second,
big
topic
I
wanted
to
cover
was
introducing
adriana.
A
F
A
A
And
will
be
working
on
open,
telemetry
docs
as
one
of
her
first
big
things
so.
D
A
F
G
A
Ted
and
I
kind
of
we
got
white
boar,
we
got
so
we
got
sort
of
a
white,
but
the
people
that
were
already
at
light
stuff.
When
the
acquisition
closed,
I
think
we
all
kind
of
got
like
a
white
board
or
a
white
white
glove.
Why
did
I
say
whiteboard
white
glove
on
boarding,
so
it
was
a
little
less
honor
us,
but
it
seems
like
new
people
are
getting
the
whole.
F
That's
true,
that's
true.
I
keep
getting
added
to
more
and
more
online
training
every
day.
It
seems.
A
Yep,
okay,
but
yeah,
I
think
the
biggest
thing
will
be
hopefully
or
hopefully
the
ideal
thing
will
be
to
have
adriana
kind
of
start
working
from
our
side,
at
least
on
kicking
off
that
conceptual
docs
consolidation
issue.
A
I
forget
what
you
should
know.
It
is
another
good
thing
would
be.
A
Where's
you're
get
you're.
Are
you
still
working
off
of
that
google
sheet
philip
for
the
like
gaps.
E
Ish,
I
I
feel
like
the
most
of
the
important
gaps.
Are
there
I
feel
like
some?
E
Some
of
them
are
kind
of
like
more
on
the
active
question
side
of
things
like
there's
questions
around,
like
oh
configuration
with
environment
variables,
but
then
it's
like,
oh
well,
that
can
lead
down
towards
a
bit
of
a
rabbit
hole
about
like
well
should
should
it
be
like
a
best
practice
to
do
it
for,
like
certain
things
versus
other
things
and
like
they're,
just
some
trade-offs
that
are
not
fun
and
so
I've
I've
since
sort
of
pivoted,
then
to
be
like
okay.
E
Well,
the
issue
that
we
have
on
getting
started
and
severn's
proposed
like
here's,
how
the
general
flow
should
look
like.
I'm
like,
okay,
let's,
let's
get
every
language
sort
of
into
that
shape.
A
Yeah,
so
I
guess
on
that,
so
the
thing
that
I
would
like
for
us
to
walk
away
from
this
meeting
with
is
kind
of
a.
A
Like
a
next
steps
or
like
a
next
area
of
focus,
my
conception
was
at
least
in
the
short
term
that
the
the
well
the
thing
that
we
can
do
right
now,
because
it's
the
thing
that
is
done
and
exists
is
the
conceptual
con
like
consolidating
all
the
what
is
tracing.
What
is
metrics
like
that
stuff
right,
because
that
content
all
exists,
it's
not
going
to
change,
and
the
sooner
we
do
it.
The
sooner
we
can
kind
of
start
proving
out
this.
This
idea
does
that
strike
everyone
as
sane.
G
So
so
you
talk
about
especially
the
things
that
different
vendors
have
created,
where
you
said
like:
let's,
let's
bring
bring
all
this
content
home
and
and
and
consolidate
it
into
into
into
a
single
place
right.
A
G
Yeah
the
only
question
I
have
and-
and
I
think
that's
so
where,
where
do
we
distinguish
conceptually
if
we
say
like
hey,
this
is
part
of
the
docs,
and
this
is
maybe
something
that
should
be
even
part
of
the
specs,
because
it's
let's
say
some
kind
of
definition
where
we
say
like
hey.
This
has
to
be
this
in
that
way.
Otherwise
we
we
get
into
trouble.
G
So
I
opened
up
these
discussions
a
while
back
with
the
glossary
that
there's
a
glossary
in
this
back,
there's
a
glossary
in
the
on
the
website
and
yeah.
This
led
me
down
into
the
service
name
discussion.
I
don't
know
if
anybody
remembers,
which
then
clashed
with
the
client
side,
telemetry
group
and
yeah.
So
so
that's
should
we
just
put
in
this
conceptual
stuff
and
then
see
like
what
happens
with
that
or
is
there?
Is
there
some
caution
to
to
take
with
with
the
spec.
D
Well,
the
the
spec
is
canonical
right,
so
if
something's
in
the
spec
and
on
the
website
and
it's
different
than
the
spec
wins,
and
we
need
to
update
the
website
and
I'd.
D
Unless
the
spec
is
wrong,
but,
generally
speaking
like
you
know,
if
it's
what
what
it
says
in
the
spec
ghost,
so
you
know
in
on
a
certain
level
like
we
can't,
we
can't
really
screw
that
up
by
writing
things
down
on
the
website.
We
do
just,
I
think,
want
to
make
sure
when
we
are
explaining
things
that
we
aren't
misinterpreting
what
the
spec
maybe
means
on
on
some
subject.
G
Okay,
so
is
it
at
the
moment
you
say
like
hey,
let
me
introduce
a
concept,
so
I
don't
know.
Let
me
update
everything
on
tracing
that
at
least
we
we
do.
Some
sanity
checks
and,
like
haste,
is
also
in
accordance
with
what
what
this
back
is
saying-
and
I
mean
errors
will
happen,
mistakes
will
happen,
but
at.
D
Least,
do
some
exactly
some
some
sanity
checks
there,
but
potentially,
if
we
may
discover
some
ambiguity
in
the
process
of
trying
to
explain
things
deeper
than
is
in
the
spec,
in
which
case
you
know,
opening
a
spec
issue
or
bringing
it
up
with
the
spec
community
and
be
like
what
what
did
you
actually
intend
here?
You
know
we
could
provide
some
feedback
there,
but
I
also
want
to.
A
Caution,
though,
that
we
try,
I
think,
if
I
do
think,
there's
a
balance,
though,
in
terms
of
like
the
spec
is
extremely
dry,
like
it's
technically
correct,
but
in
its
correctness
it
is
like,
maybe
so
that
arguing
from
example
right.
So
I
was
on
twitter,
so
I
I
follow
the
like
hotel
on
twitter
or
not.
I
mean
I
look,
I
I
have
a
tweetdeck
column
for
open
telemetry
and
there
was
someone
in
there
that
I
saw
a
conversation
in
there
where
someone
was
saying
like
I
want
to
pass.
A
Contact
like
I
want
to
trace
through,
like
what's
the
conventional
api
like
do
context
prop
through
something
that
isn't
http
or
like.
If
I
want
to
go
through,
like
a
pro
like
a
p
invoke
or
through
a
pipe
or
a
channel,
or
something
right
like
I'm,
trying
to
pass
context
in
a
way
that
doesn't
seem
to
match
anything,
I'm
seeing
in
the
apis
or
sdks,
and
I
pointed
them
to
equinix
to
the
hotel
cli,
where
it's
like.
Well,
it's
using
it's
using
mvars
to
kind
of
do
it
he's
like
well
where's.
A
The
specific
you
know
like
how
do
you
do
like
is
that
actually
specified
anywhere
and
it's
like
well.
No,
because
the
spec
and
the
actual
like
w3c
is
written
like
w3c
trace
context
is
written
with
the
explicit
assumption
that
you
are
passing
trace
parent
through
an
http
text,
map
right,
yeah
and
there's.
No,
so
I
don't
want
us
to
get
what
I'm
trying
to
avoid
is
that
we
get
so
bogged
down
in
making
sure
that
what
we
say
is
like
100
into
the
spec.
A
Like
word
for
word,
what's
in
the
spec
that
we,
like
close
off
corridors
of
thought
for
people
like
there's,
no
reason
that
you
can't
use
a
trace
to
represent
like
a
trace
can
be
a
profile
right
like
what
is
a
profiling
dump
other
than
a
trace.
Just
with
you
know,
and
I
would
rather
us
be
broad
enough
in
the
conceptual
documentation
to
try
to
encompass
the
the
necessary
variety
of
telemetry
without
being
like.
Oh,
this
is
only
for
kubernetes
apps
using
spring
that
talk
over
grpc
right,
like
that's.
D
I
would
say
another
thing:
is
you
know
the
the
spec
is
intended
for
people
implementing
open,
telemetry
stuff,
it's
not
intended
for
end
users,
and
so
it
really
doesn't
contain
a
lot
of
docs
right
like
so
like
what
would
be
helpful
for
that
person
who
wanted
to
write,
you
know,
send
context
through
some
new
mechanism
might
be
to.
We
could
write
up
a
thing
around
like
how
to
write
your
own
propagator.
D
You
know
the
spec
doesn't
care
how
you
know
the
spec
shows
you
what
the
propagator
interfaces
look
like
if
you're
going
to
have
it
bind
to
a
propagator
in
a
language
right,
but
they
don't
get
into
like
well.
How?
How
should
you
propagate
this
stuff
over
something
we
haven't
defined
here,
because
spec
doesn't
care
how
you
do
that?
D
So
that's
that's
kind
of
like
where
I
see
like
all
this
end
user
documentation
being
really
helpful,
is
explaining
how
to
use
all
the
stuff
that
we
built
essentially
like
if
we
could
get
through
that
that
pile
of
stuff
first,
because
the
spec
doesn't
tell
people
any
of
that,
and
it's
just
not
very
helpful
for
end
users.
A
Yeah,
so
I
think
for
our
next
steps
like
let's
so
maybe
adriana
if
you
could
like,
I
think
we,
the
thing
that
I
can
control
is
the
light
step
conceptual
stuff
like
so
my
thought
was.
We
can
start
with
that.
We
can
pull
that
in.
We
can
try
to
like
do
against.
B
A
A
merge
basically
the
stuff,
that's
missing,
we
the
stuff
that
the
net
new
stuff
just
gets
added
in
the
stuff
that
already
kind
of
exists.
Then
we
we
try
to
merge
it
together
and
then
just
we'll
go
through
knock
that
out
and
then
we
can
look
at
every
and
then
we
can
start
going
through
other
people's
stuff
like
there
is
a
list
on
that
on
12.01.
D
So
so
I
I
have
like
a
specific
request
here,
which
I
think
mostly
gets
solved
by
porting
over
the
light
step.
Hotel
docks,
which
is
most
of
the
docks
written
by
the
cigs,
focus
very
heavily
on
like
how
to
use
the
api,
like
here's,
how
you
start
a
span
and
to
span,
but
that's
actually
not
the
docs
people
need
when
they
get
started.
The
getting
started.
D
A
So
yeah,
if
we
can
have
that
as
like
the
one
hotel
demo
system,
then
like
that's
something
that
we
can
say
from
a
doc's
perspective
like
okay,
here's
the
like
the
the
tippy,
the
tippy
top
of
the
the
tippy
toppy,
yes
canonical
copy
paste
source.
The
tippy
toppiest
of
the
iceberg
is
like
a
complete
functioning
hotel
system
right
and
then
one
layer
down
is:
let's
you
know
if
I'm
in
this
javadocs
or
I'm
in,
like
the
instrumenting
for
yeah
instrumenting
with
python.
A
Let's
say
then
it's
like
okay
go
to
this
thing,
and
now
I'm
going
to
break
down
I'm
going
to
show
you
how
it's
configured
right,
we're
going
to
explain
through
the
docs
like
how
did
we
add
hotel
to
this
thing
that
you
can
go?
Look
at
the
finished
code.
You
can
see
how
it
all
fits
together
and
then
another
step
down
is
okay
for
sort
of
a
generic
thing.
Here's
how
you
install
auto
instrumentation
and
then
a
step
down
is
here's
how
you
do
manual
instrumentation
and
then
that's
kind
of
it.
D
Yeah,
I
guess
I
just
want
to
emphasize
that
I
think
the
the
first
thing
people
land
on
needs
to
be
the
thing
people
are
trying
to
do.
The
most
is.
I
need
to
get
this
stuff
installed
in
my
app,
not
necessarily
take
a
tutorial
or
go
look
at
a
demo
app
like
I
just
I
I
have
my
app
here.
I
have
to
get
this
stuff
installed
in
it
so
that
I
can
get
it
hotel
into
production
and
like
yeah.
What
are
the
snippets
that
I
need
to
paste
into
my
app
and
then
like?
D
How
do
I
troubleshoot
this
thing?
If,
like
I'm,
not
if
I
like
paste
this
stuff
in-
and
I
don't
see
data
like
you
know,
how
do
I
enable
console
logging?
How
do
I
like
do
various
crap
just
to
to
troubleshoot
that
my
experience
is
like
that's.
That's
that's
like
the
stuff.
We
are
missing
the
most
and
actually
the
thing.
D
Yeah,
the
in
our
end,
users
like
really
need
that,
and
I
think
tutorials
are
great
and
like
demo
apps
are
super
great.
We
definitely
need
all
of
those,
but
they
aren't.
They
aren't
like
a
substitute
for
making
sure
we
have
a
getting
started
guide.
That's
that's
just
just
focused
specifically
on.
A
A
A
A
G
And
I
made
a
proposal
to
to
the
javascript
community
to
also
come
up
with
something,
let's
say
agent-like,
so
to
speak.
I
mean
it's
a.
I
think
they
did
the
challenges
that
lots
of
people
come
over
from
apm
solutions
that
say
like
hey:
here's,
a
java,
agent.net
agent,
node.js,
h
and
whatever
agent
throw
this
in
your
app
and
all
the
magic
happens
and
a
lot
of
people
I
think,
come
or
not
a
lot
of
sin,
but
but
a
certain
kind
of
people
come
in
and
say
like
hey
this.
G
A
There's
a
third
question,
which
is:
what
should
we
as
a
project,
encourage
people
to
do,
because
I
think
we
as
a
project
should
be
encouraging
like
that.
You
should
import
all
this
stuff
yourself
and
you
should
be
doing
every
you
should
be
like
creating
trace.
First
instrumentation.
As
you
write
your
code
to
help
you
do
observability.
A
B
A
These
kind
of
three
distinct
models
of
how
should
people
use
this
and
there
are
different
end
users
or
there
are
different
stakeholders
that
will
prioritize
them
differently.
Right,
like
vendors,
are
going
to
prioritize
the
I
just
want
the
one
line
to
line
like
as
quick
as
possible,
like
our
employers
would
certainly
love
if
hotel
was
just
like
you
run
a
command
in
the
shell
and
boom.
You
have
all
this
instrumentation
and
that's
the
kind
of
documentation
they
want
because
they
want
to
make
it
as
unscary
as
possible.
A
I
think
there's
also
like
a
fourth
category
here.
In
addition
to
so
it's
the
like,
I
want
totally
auto.
I
want
library
I
want
manual
and
then
there's
also
I'm
writing
something
for
someone
else,
and
I
want
to
know
how
to
integrate
this
right.
I'm
writing
a
library
or
a
framework,
and
I
need
to
know
how
to
implement
hotel
yeah.
For
my
end,
users
and
customers.
G
But
but
then
maybe
the
very
first
thing
as
a
getting
started
page
before
every
other
getting
started
page
should
be
like.
Are
you
a
developer?
Are
you
an
itops
person
that
just
wants
to
drop
in
this
thing,
or
are
you
a
library
developer
and
then
maybe
point
them
from
that
at
some
point?
So
maybe
this
should
be.
A
D
I
would
suggest
go
because
no,
no
you
hear
me
up
because
go
is
the
hundred
percent?
You
don't
get
any
shortcuts
ones
like
the
the
other
languages
basically
have
have
a
version
of
it
where
it's
like
here.
Here's
the
shortcut
like
just
you
know
like
in
python
or
like
in
ruby,
where
there's
like
step
one
just
just
haul
in
the
install
everything
package
and
and
then
you
know,
make
sure
that
works,
and
then
you
can
go
on
to
this
more
nuanced
version.
Where
you
know
you
don't
take
a
dependency
on
everything,
but.
A
A
A
E
No,
no,
I
I
still
have
it
out
in
a
branch.
It's
a
lot.
A
A
I
also
think
just
in
general,
looking
at
like
philip,
you
posted
if
people
didn't
see
it,
philip
posted
was
it
last
30
of
the.
A
Yeah,
let
me
share
this
real
quick.
Oh
I
got
it.
It's
11..
I
got
it
right
now.
Actually,
I
will
say:
go
check
out
this
in
the
hotel,
comms
channel,
you
can
see
the
traffic
and
it
like
java
go.net,
like
java,
is
really
popular.
G
A
Let's,
okay
yeah
the
meat
we're
out
of
time.
Let's,
I
think
we
need
to
get
to
the
point
where
we
can
actually
figure
out
concrete
next
steps
and
be
able
to
put
this
into
like
some
issues
and
like
really
focus
on
something
because
we're
a
little
we've
been
talking
around
this
issue
for
a
couple
months
I
feel
like
and
not
really
making
a
lot
of
headway.
So,
let's
yeah,
let's.
D
A
About
this
async
in
the
comms
channel
on
slack
and
try
to
figure
out
what
at
least
the
next
30
days
is
going
to
look
like
in
terms
of
work
for
it
and
start
and
start
on
starting.
D
Yeah
I
I
have.
I
do
have
a
concrete
suggestion,
which
is
for
for
each
one
of
these
installation
approaches
and
you're
right.
You
might
have
several
in
each
language
just
write
a
two-parter.
The
first
part
is
like
how
to
install
the
sdk
and
the
instrumentation
with
this
approach.
Just
like
what
copy
pastes
do
you
need
to
make
and
then
a
section
that
section
two
is:
how
do
I
troubleshoot
this
installation
yeah
and
the
the
that
will
start
to
collect
all
the
information
that
that
we
need
for
for
each
one
of
these?
These
approaches.
A
Yeah,
let's
talk
about
it,
async
a
little
and
try
to
get
something
also
messaging
for
cue
cuny.
U
we
can
talk
about
that
async
and
reese.
If
you
had
something
that
you
want
to
talk
about,
I'm
sorry
that
we
didn't
get
to
it.
B
No
worries
it
was
the
the
messaging
for
your
kubecon
since
the
slides
are
due
tomorrow,
but
I
can
just
follow
up
with
y'all
and.