►
From YouTube: 2022-03-03 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
Good
morning
or
good
afternoon,
where
you
may
be
welcome
to
our
second
and
user
working
group
discussion,
there
are
notes
in
the
meeting
invite
if
you
haven't
seen
them
so
it
looks
like
we've
got
a
few
items
on
the
agenda
already.
Let's
take
a
moment
to
review
the
agenda
and
make
sure
that
there's
nothing
else
that
we
want
to
try
to
hit
on
in
our
short
30
minutes
today.
A
Okay,
I
know
that
wasn't
quite
a
minute,
so
the
first
piece
up
on
the
agenda.
I
know
we've
got
a
couple
new
folks
here
who
have
not
showed
up
before,
because
this
is
our
second
one.
So
obviously
you
know
we're
all
here.
If
you
haven't
had
an
opportunity
to
attend
the
one
last
week,
will
you
just
do
a
quick
introduction
of
yourself.
B
All
right
sure
my
name
is
ted.
I
work
at
lightstep,
I'm
on
the
governance
committee
for
open
telemetry
and
I'm
also
helping
out
with
the
consig
getting
our
website
and
all
of
our
other
assets
in
order.
C
I'm
I'm
kirk
haynes,
I'm
with
new
relic.
I
am
on
our
developer
developer
relations
team
here
at
new
relic
and
also
in
my
spare
time.
I
am
building
a
open,
telemetry,
complete
set
of
tooling
for
open
telemetry
for
the
crystal
language.
D
Right
now,
one
of
the
co-founders
of
lightstep
I'll
stop
talking
good
to
be
here.
E
Hi,
my
name
is
ruthwick,
I'm
a
new
joining
the
aws
observability
team,
so
nice
to
be
here.
F
Yeah,
hey
everyone,
I'm
dustin
posey,
I'm
a
product
manager
for
observability
at
a
company
called
workkiva
and
we've
just
started
down
the
path
of
developing
an
open,
telemetry,
dart
implementation
and
I'm
just
looking
to
help
in
any
way
possible
with
with
adoption
and
maybe
providing
some
input
from
our
own
adoption
of
open
telemetry.
A
Great
welcome
dustin
all
right
excellent,
so
we've
got
introductions
all
the
way
if
I've
missed.
You
has
your
chance
to
speak.
G
Yeah
hi
everyone.
My
name
is
kaushik,
I'm
a
new
grad
joinee
at
aws,
observability
team.
So
nice
meeting
you
all.
A
Great
thanks,
kelsey,
okay,
so
review
action
items
from
the
previous
meeting,
so
we
had
two
three
action
items
technically,
but
our
meeting
notes
are
now
in
the
invite.
So
whoever
did
that
many
thank
yous.
The
second
was
quantifiable
trendable
themes
from
surveys
so
to
catch
people
up
to
speed
kind
of
the
goal
is,
as
we
create
an
open,
telemetry
survey
and
create
the
next
generation
of
end
user
surveys
to
provide
feedback
into
the
open,
telemetry
community
on
how
things
are
going
priorities,
etc.
We
want
to
try
to
figure
out.
A
Are
there
any
stable
questions
that
we
want
to
check
in
on
a
regular
frequency
that
are
trendable?
One
idea
was
brought
up
the
idea
of
looking
at
satisfaction
with
documentation,
but
that
was
the
only
one
so
far
that
has
really
been
identified.
A
A
Okay,
so
I
just
wanted
to
put
a
pin
in
that.
I
haven't
attended
too
many
working
group
sessions
in
the
past,
so
my
question
is:
what's
the
best
way
for
us
to
collaborate
outside
of
these
meetings?
Does
anyone
have
any
preferences
on
how
do
we
have
that
conversation
about
quantifiable
or
trendable
themes.
H
So
one
thing
that
I've
seen
work
in
other
in
other
groups
is
someone
takes
the
lead
and
creates
a
doc,
a
document
that
may
be
a
straw
man
with
things
to
be
torn
down
and
then
back
and
forth
happens
in
common
threads
on
the
document.
I
think
that
that
works.
You
know
that
or
its
equivalent
in
in
issue
or
pr
discussion
tends
to
work
better
than
slack,
because
it's
a
lot
more
asynchronous.
A
Does
anyone
have
any
feedback
on
that
way
of
working.
I
I
So
I
will
definitely
agree
on
puny
on
on
the
suggestion.
A
Absolutely
okay,
so
I
will
start
a
google
drive
doc
for
quantifiable
trendable
themes
from
surveys
and
the
second
one
of
end
user,
funnel
audit
of
like
how
are
end
users
finding
their
way
to
open
telemetry.
What
areas
do
we
want
to
focus
on
from
an
awareness,
enablement
standpoint
for
end
users,
so
I'll
get
those
documents
started
unless
anyone
wants
to
have
a
discussion
right
now
about
kind
of
the
funnels
in
or
trendable
things.
I
A
I
don't
think
we've
gotten
that
far
on
like
how
to
get
the
survey
out
into
the
hands
of
people.
What
we
kind
of
have
discussed
previously
is
there
is
an
end
user
survey.
If
you
look
at
the
notes
from
last
week,
there
are
a
couple
links
in
there
and
at
least
the
folks
from
microsoft
have
embedded
this
user
survey
into
their
documentation,
they're
getting
started
documentation,
but
it's
really
kind
of
hard
to
find.
A
Also,
the
survey
is
pretty
long,
and
so
that's
been
the
historical
way
that
I
think
there's
been
less
than
20
responses
in
total
to
that,
and
so
I
I
think
we
need
to
determine
what
what
are
the
right
levels
of
questions
for
that
we're
trying
to
bring
the
feedback
into
the
community
and
what
are
the
channels
to
get
that
so
kubecon
being
a
great
example
of
a
way
to
do
that.
B
I
also
think
it
it
makes
sense
to
to
push
it
out
to
customers
kind
of
actively
right.
If
various
vendors
could
you
know,
actively
request
customers
or
recent
pocs
to
fill
it
out
as
part
of
their
feedback.
Loop.
J
Yeah
ted,
I
think
that's
a
great
suggestion
we
can
certainly.
I
can
certainly
help
yeah.
A
Yep,
just
taking
a
note
here,
so
I
think
there's
a
lot
of
benefit
of
engaging
with
the
vendors
who
are
working
in
this
space
to
get
that
feedback
back
into
the
community
oftentimes.
At
least
in
my
work
day
to
day.
A
lot
of
the
feedback
should
go
to
the
community,
but
they
don't
know
how
to
engage
or
they
don't
have
the
resources
to
like
go
open
up
issues
on
github
as
an
example.
B
Yeah,
I
have
one
other
thing
to
potentially
track.
Possibly
we
could
do
it
through
a
survey
and
if
this
is
like
out
of
bounds
of
where
you're
trying
to
take
the
discussion
right
now
sure
we
can
talk
about
it
later.
But
besides
documentation
and
things
like
that,
there's
also
just
this
concept
of
how
long
does
it
take
an
average
developer
to
set
up
open
telemetry?
B
So
when
you
have
an
application
and
you're
trying,
you
know
to
get
that
application
bootstrapped
with
open
telemetry.
That
specific
part
of
the
process
is
probably
the
most
critical
for
a
good
user
experience,
and
it
would
be
great
to
know
how
long
that
tends
to
take
people
in
different
languages
and
what
the
the
failure
rate
is.
B
A
E
I
We
take
quarkx,
for
example,
I
see
a
lot
of
people
are
challenging,
are
challenged
by
quarkx
to
instrument
it.
So
I
think
it's
it's
java,
but
it's
specific
framework
of
java,
so
I
think
we
should
even
go
on
which
fla,
which
framework
they
to
try
to
instrument
as
well.
For
us.
A
We
can
take
to
a
google
doc
on
the
survey
from
from
last
time,
we
chatted
about
how
to
also
get
engagement
of
surveys
and
how
to
try
to
keep
them
lightweight
and
digging
in
in
different
forums
and
different
surveys,
because
having
like
one
survey
to
rule
them
all
is
awesome,
but
also
may
take
somebody
the
last
survey
somewhere
around
half
an
hour
to
fill
out,
which
might
you
know
it
lowers,
increases
information
and
quality
of
information
provided,
but
also
lowers
folks's
ability
to
engage
with
that,
and
so
having
different
targeted
surveys.
J
Yeah,
I
mean
the
other
thing
sure
I'd
like
to
add.
There
is
that
and
punya,
and
I
were
discussing
a
bit
about
you
know
like
what's
the
best
way
to
do
surveys
here
right
because
again
the
longer
the
surveys,
the
more
fatigue
you
know
kicks
in
right
from
any
any
standpoint,
and
you
know
perhaps
having
a
more
innovative
approach,
which
I've
seen
work
quite
well
in
user
communities
is
having.
J
You
know,
just
no
more
than
two
or
three
questions,
and
you
know
just
choices
that
people
can
select
as
a
pull
and
just
you
know,
kind
of
doing
that
on
a
regular
basis
on
different
topics
through.
Perhaps
you
know
different
channels,
including
such
a
meeting
right
so,
but
but
keeping
it
precise
keeping
it.
You
know
focused
on
a
particular
area
and,
and
just
you
know,
collecting
feedback
continuously.
H
The
other
thing
I'd
add
to
that,
which
I
I
think
isn't
maybe
like
a
a
side
benefit
we
could
think
about,
is
if
you,
if
we
decided
to
use
twitter
and
have
a
poll,
then
you
also
get
the
organic
conversation
that
springs
up
around
the
poll
in
a
way
that
isn't
possible
with
a
google
with
a
form.
G
H
J
J
B
One
thing
we
should
consider
is
also
like,
like
the
world's
simplest
survey,
like
basically
a
feedback
form
that
we
can
attach
to
the
website.
That's
you
know
how
short
can
we
make
it
while
having
it
still
be
useful
to
us
that
that
could
be
also
private,
so
people
can
just
have
a
shouting
box
to
tell
us
what
they
really
think.
A
A
A
Okay,
so
we
got
about
15
minutes.
The
next
agenda
item
here
is
a
dedicated
slack
channel.
So
we
had
a
little
bit
of
a
discussion
last
week
or
the
last
meeting
about
this.
So
somebody
added
this
who
wants
to
advocate
for
dedicated
slack
channels.
B
Is
this
a
slight
channel
for
us
to
communicate
as
a
group,
because
I
think
that
would
be
great
as
far
as
like
a
place
to
direct
like
end
users
to
give
us
feedback?
I
think
the
the
standard,
open,
telemetry
slack
channels
is
where
we
should
send
send
those
people.
J
Yeah,
I
think
that
was
what
was
decided
right,
that
we
would
use
the
standard
hotel
channel
for
standard
discussions,
but
then
have
a
specific
channel
for
just
you
know
us
all
actively
discussing.
J
A
So
so,
to
summarize
for
end
users
who
are
asking
to
provide
feedback,
have
them
post
that
in
the
open,
telemetry
channel
they'll
probably
get
potentially
redirected
to
specific
channels,
but
I
think
one
of
the
challenges
there
is:
how
do
we
make
sure
that
that
feedback
is
accessible
and
searchable
for
people
off
of
cncf,
and
so
I
think
a
some
type
of
process
needs
to
be
created
to
take
that
feedback
from
cncf
slack
and
put
it
into
the
project
for
that's
more
accessible.
J
J
You
know
formally,
you
know
at
least
taking
responsibility
for
making
sure
that
you
know
people
are
able
to
address
questions
or
you
know
if
they
need
any
help,
they're
directed
to
the
right
channels
or
right
folks,
and
then
that
you
know
feedback
also
being
captured,
someplace
right,
so
that
that
is
always
the
case
and
that's
why
mailing
lists
have
been
popular.
J
D
D
That's
just
not
the
right
medium,
I
think
of
it
as
like
snapchat,
you
know
like
after
it's
an
hour
old
forget
about
it.
Who
knows,
like
that's
my
two
cents,
for
the
open,
telemetry
channel
itself,
like
I'd
rather
just
declare
bankruptcy
on
slack
than
trying
to
clean
it
up,
or
I
don't
know,
who's
going
to
do
the
work.
J
B
And
the
goal
with
slack,
I
think,
should
always
be
to
to
direct
people
first
to
the
right
channel
where
they
can
get
like
the
proper
response
and
but
from
there
it
should
always
be.
You
know
the
resolution
should
be.
You
know
you
should
file
either
they
get
an
answer
and
they're
done,
or
they
should
file
a
github
issue
on
like
the
appropriate
repository,
and
maybe
if
it's
just
like
literally
just
generic
feedback,
that
we
want
to
make
sure
we
record.
B
I
Sometimes
we
organize
what
we
call
customer
advisory
boards
and
I
think
now,
because
we
have
several
vendors,
several
ip
scalar
part
of
the
project,
if
we
are
all
try
to
at
least
get
four
customers
that
are
currently
in
the
journey
of
implementing
open,
telemetry
and
then
invite
them
that
a
board.
And
then
we
have
one
of
the
customer
sharing
their
story
and
then
let
the
customer
discuss-
and
we
just
moderate-
that
would
be
just
amazing-
to
get
feedback.
D
I
totally
agree.
That's
I
put
this
at
the
end
of
the
agenda
today.
I
honestly,
I
have
no
objection
to
any
of
the
stuff
we're
talking
about
around
having
lightweight
feedback,
but
I
think
we
desperately
need.
I
mean
if
you
look
at
considering
this,
the
end
user
meeting,
the
ratio
of
end
users
here
and
this
call
is
pretty
dire.
I
would
rather
that
the
folks
coming
from
vendors
or
open
source
projects
involve
the
space
like
we
should
just
rotate
and
like
bring.
D
It
doesn't
have
to
be
a
customer
but
like
bring
bring
like
a
real
scaled
out.
End
user
to
this
call
and
then
like
basically
do
discovery
around
problems.
I'd
find
that
to
be
a
lot
more
valuable
than
than
trying
to
triage
slack
or
whatever.
Just
in
terms
of
like
getting
to
the
heart
of
where
the
current
roadblocks
are,
as
we
did
that
we
had,
I
think
it
was.
Last
summer
we
had
atlassian
come
to
the
hotel
gc
for
like
a
meeting,
and
I
found
that
to
be
incredibly
useful.
D
We
set
up
like
a
separate
session
around
that
and
and
a
lot
of
good
stuff
came
out
of
that
because,
like
actionable
things,
so
I
I
like
that
idea.
A
lot.
F
Yeah,
I
mean,
I
think,
the
idea
of
having
someone
in
person
who
you
can
for
lack
of
a
better
term
interrogate
and
dig
into
you
know,
pain,
points
and
rough
patches
and
and
the
better
parts
of
hotel.
I
think
I
think
you're
gonna
you're
gonna
mine
a
lot
more
value
in
just
speaking
on
behalf
of
you
know,
the
the
teams
that
are
implementing
hotel
here,
99
of
them,
would
attend,
if
asked,
and
to
give
feedback.
A
D
Yeah
I
mean
we
don't
have
to
call
that
sounds
great,
but
I
mean
I'd
be
happy
if
we
just
like
had
assigned
assignments
where
every
other
one
of
these
meetings
were
going
to,
I
don't
know
just
rotate
around
and
I
think
we
all
know
people
who
would
probably
be
happy
to
participate
in
that
yeah.
I
mean,
I
think.
J
In
advance
I
mean
I
even
if
we
have
you
know
one
detailed,
you
know
discussion,
every
iteration,
that's
very
valuable
and,
and
we
all
can
take
you
know,
responsibility
and
making
sure
that
there
are.
You
know
I
mean
we
all
interact
with
different
customers
who
are
using
hotel.
You
know
in
in
in
their
environment.
So
that
could
be
something
that
we
just
have
a
schedule,
and
we
can
just
add.
You
know,
folks
that
hey
you
know
like
this
week.
It's
my
responsibility
or.
A
I
wonder
if
this
is
the
right
form
to
do
that
versus,
for
example.
I
would
hope
that
various
maintainers
in
the
project
would
be
really
interested
and
engaging,
and
so,
if
that
was
like
a
separate
entity,
if
you
will.
J
If
it
happens,
I
should
I
don't
know
whether
that's
an
accurate
statement,
because
you
know
in
our
discussions
in
the
maintainer
meetings.
I
don't
think
maintainers
are
necessarily
interested
in
the
end
user
feedback,
but
all
of
us
certainly
are
on
the
gc
as
well.
As
you
know,
other
folks
who
are
you
know
coming
in
with
that
perspective,
but
typically
I
mean
it's
tough,
for
you
know
the
lead
engineers
on
the
project
to
be
super
involved.
B
I
think
it
would
be
nice
to
let
the
maintainers
know
like
like
keep
them
in
the
loop
when
these
kinds
of
things
are
scheduled
out,
so
they
can
come
if
they
want,
but
I
kind
of
agree
with
alita
that
I
think
part
of
the
job
of
this
group
is
taking
in
that
raw
data,
and
then
you
know
titrating
it
down
into
feedback
that
we
can
give
to
maintainers
in
a
way,
that's
like
consumable
to
them.
A
Okay,
great
so
what's
our
next
steps
for
organizing
this
customer
advisory
board
to
somebody
want
to
take
an
action
item
to
put
together
a
lightweight
proposal
of
like
what
would
that
look
like
what
are
the
frequency
and
schedules
that
we
can
all
comment
on,
and
then
we
can
start
filling
up
with
end
users.
I
know
a
lot
of
end
users
would
love
to
participate.
D
J
B
Step
one,
the
thing
ben
suggested
is
we
we
can
just
start
by
asking
people
to
come.
Give
us
feedback
right
like
it.
Doesn't
we
don't
need
to
have
an
official
advisory
board
or
something
like
that
to
yeah.
D
We
need
us,
we
need
a
calendar
of
people
who
are,
you
know
dedicated
to
hotel,
like
you
know,
majority
time
to
like
have
an
assignment
to
go
and
find
an
end
user
for
such
and
such
date,
and
just
to
understand
that
we'll
need
to
have
lead
time.
For
that,
that's
like
the
essence
of
the
test.
Is
that
what
you're
getting
it?
Oh.
D
A
Yeah,
I
think
we
need
some
organization
around
that
and
also,
I
think,
if
I
were
to
go
to
an
end
user
they'd
be
like
what
is
this.
So
if
we
had
some
consistent
language
about
what
the
intent
is
to
have
them
come
and
talk
to
the
open,
telemetry
group
here,
I
think
that
would
help.
B
I
can
totally
write
down
a
pitch
pitch
for
that,
but
yeah.
Another
reason
why
I
mean
we
can
use,
I
think
the
thing
about
calling
it
a
board
is
that
implies
it's
the
same,
like
group
who
are
coming
back
again
and
again
and
for
a
for
a
product
that
that
makes
sense
because
you
have
like
long-term
users,
but
my
experience
with
like
open
telemetry
is
where
you
want
to
catch.
J
J
B
Like
like,
if
we
were
a
database,
it
would
make
sense,
because
you
have
like
long
term
users
database
for
like
using
it
every
day
and
want
features
and
have
feedback,
but
like
just
just
the
nature
of
the
open,
telemetry
project.
I
found
we
want
like
feedback
from,
like,
ideally
lots
of
different
customers,
but
also
like
that
feedback
is
fleeting
like
like.
B
To
it's,
if
you
don't
catch
them,
while
they're
in
their
rollout
phase
or
kind
of
shortly
after
then,
like
their
memory,
is
gonna
fade
to
something
vague
like
yeah,
that
sucked
or
it
was
fine.
H
Is
someone
signing
up
to
capture
the
feedback
like?
Are
we
going
to
record
a
video
and
get
consent
for
recording
a
video
and
then
make
the
video
available
to
to
sigs?
Are
we
going,
you
know,
transcribe
the
feedback
and
make
it
available?
What
are
we
thinking?
I.
J
E
J
And
you
know
again,
maybe
char
you
and
I
can
work
on
kind
of
a
format
that
works
and
and
then
propose
it
back
to
the
same
group
here
next
time
we
can
review
it
and
and
then
have
a
schemes
schedule.
A
Yeah
that
sounds
great
we're
here
over
time.
So
I
want
to
thank
everyone
for
your
participation
and
attending
today.
There
will
be
some
docs
being
released.
We
didn't
get
to
needs
for
communicate
to
us
as
a
group,
so
for
right
now,
if
people
will
use
the
end
user
research
channel
in
cncf
slack
to
particip
to
communicate
in
this
group,
we
will
do
that
until
we
figure
out.
Should
we
have
something:
that's
not
called
end
user
research
sounds.