►
From YouTube: 2022-02-17 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
B
I'm
so
excited
that
people
are
here.
I
have
not
actually
been
able
to
update
the
calendar,
invite,
and
so
I
do
have
a
doc
started
for
us
to
take
meeting,
notes
and
stuff
it
will
get
in
there
eventually,
but
for
now
I'm
going
to
drop
it
into
the
zoom
chat
so
that
you
can
get
access
to
this.
For
our
initial
working
group,
kickoff.
C
B
Excellent,
I
think
we
should
probably
just
get
started-
I'm
not
sure
who
will
be
joining
us
today,
since
this
is
our
initial
kickoff,
and
so
I
wanted
to
start
with
introductions.
So
if
you
want
to
throw
information
into
that
media
invite-
and
we
can
do
introductions
that
would
be
awesome.
A
Yeah
yeah,
I
don't
mind
going
first,
so
my
name
is
bryce
kaiser.
I
work
with
observe
iq,
so
we've
done
a
bunch
of
work
on
the
logs
side
of
open
telemetry
and
we're
just
looking
to
get
even
more
involved
and
I'm
you
know
I'm
relatively
new
to
open
telemetry.
So
I'm
just
trying
to
figure
out
how
I
can
help
out
and
you
know,
accelerate
the
adoption
of
open
telemetry
from
an
end
user
perspective
really
excited
about
this.
So
thanks
for
organizing
it.
B
D
Yes,
so
my
name
is
henrik
rexed.
I
work
for
danatrace
and
I'm
also
have
a
youtube
channel
called.
Is
it
observable
and
I'm
currently
working
with
the
observer
iq,
because
I'm
trying
to
build
a
plugin
for
stanza
as
well
and
yeah,
I'm
trying
to
educate
the
community
on
how
to
use
open
symmetry?
You
know
in
a
fast
easy
way
and
and
increase
the
adoption.
So
this
is
my
main
goal
here
is
to
try
to
help
quickly
changes.
B
Hey
for
everyone
who
just
joined,
I
threw
in
the
chat,
links
to
the
notes
and
so
morgan.
Do
you
want
to
throw
a
quick
introduction.
E
Yeah,
I
know
almost
everyone
on
the
call
already,
but
my
name
is
morgan
mclean.
I
work
at
splunk.
I've
been
open
telemetry
since
the
beginning
and
open
census.
Prior
to
that,
I'm
also
on
the
governance
committee
happy
to
communicate
more
of
our
end
users
and
make
things
even
better
for
them.
F
Hi
everyone
I'm
punya
biswal.
I
work
at
google
and
I
I
lead
a
team
here,
that's
responsible
for
our
open
telemetry
efforts
and
I've
been
with
open
telemetry
for
about
just
about
a
year
now
very
excited
to
work
on
this
project.
C
G
B
Excellent,
and
so
I
am
char
cruden,
I
work
at
new
relic,
and
so
you
all
work
with
folks
on
my
team.
So
I
lead
the
upstream
engineering
efforts
here.
So
some
of
the
folks
from
new
relic
probably
are
on
my
team,
and
so
in
my
role,
I
get
exposed
to
a
lot
of
early
adopters
of
open
telemetry,
and
so
it's
super
awesome
and
one
of
the
things
that
I
want
to
help
bring
them
is
a
vendor-neutral
space
for
them
to
connect
with
others.
B
I
think
it's
in
the
best
interest
of
the
project
to
like
get
that
cross-pollination
and
not
have
a
vendor
like
slant
on
hey
here
are
the
best
practices,
and
so
I
wanted
to
do
that
for
all
the
end
users
that
are
asking
for
it.
So
I
know
that
there's
a
there's
a
request
out
there
for
folks,
and
so
just
like
working
with
all
of
you.
B
I
think
this
group,
I'm
really
looking
forward
to
helping
this
group
interact
with
the
project
and
are
especially
getting
that
feedback
back
to
the
individual,
cigs
right
and
so
how
we
can
help
coordinate
and
just
bring
the
overall
voice
of
the
end
users
who
can't
participate
as
like
a
a
direct
community
member.
B
So
I'm
very
excited
I'm
so
excited
everyone's
here.
Okay,
so
those
are
introductions,
and
so
this
is
my
first
sig
meeting
that
I
have
run,
and
so
I
think
I
wanted
just
to
confirm
the
agenda
to
see.
Is
there
any
additional
items
on
here
that
you
all
were
hoping
to
talk
through
today
and
let's?
Let's
do
a
quick
review
of
the
agenda
as
written
in
the
meeting
notes
and
if
there's
something
missing,
let's
add
it.
B
If
there's
something
that,
like
we'll
try
to
do
a
prioritized
list,
if
you
will
and
take
it
from
there,
so
we'll
spend
maybe
the
next
one
minute.
If
there's
anything
you
would
like
to
add.
Please
do.
F
B
Excellent,
thank
you
for
that
edition.
Okay.
So
the
next
piece
up
here
is
like.
Is
this
a
good
time
for
all
of
you
to
meet
so
we've
currently
got
these
scheduled
for
30
minutes
every
other
week?
I
don't
know
if
that's
the
right,
frequency
or
duration,
so
does
anyone
have
any
thoughts
on
the
schedule
and
timing.
B
Excellent,
I
also
know
on
opposite
weeks
at
the
same
time
frame
is
the
open,
telemetry
communications
sig,
and
so
I
expect
that
we'll
have
a
lot
of
overlap
and
I
love
the
words
synergy,
but
like
actually
creating
that
synergy
between
the
communications
effort
and
and
those
end
user,
focused
communication
parts,
and
so
I
wanted
to
that's.
Essentially
what
I
picked
this
time
is
that
it
will
just
like
align
with
their
schedule
pretty
well,
and
so
I
don't
expect
unless
there's
something
that
changes
that
in
the
future.
B
B
Okay,
we're
gonna
see
what
happens
with
30
minutes,
and
if
we
have
to
extend
that
over
the
course
of
time,
we
can
do
that
as
well.
Excellent,
okay,
so
next
item
review,
working
group,
scope
and
so
near
the
top
of
the
meeting
notes
is
a
the
github
issue
to
the
original
group
scope
proposal.
If
you
haven't
had
a
chance
to
read
that,
I
would
recommend
reading
that
issue
to
just
get
a
little
bit
of
at
least
my
I'm
working
with
owleta
on
this.
B
Unfortunately,
she
wasn't
able
to
join
us
today,
but
basically
I'll
lead
it
in
my,
like
lightweight
vision,
for
what
we
can
do
with
this
group
and
so
taking
conversations
out
to
github.
If
there
is
anything
you
would
like
to
add
or
challenge
on
that
proposal,
but
the
kind
of
the
tlbr,
if
you
will,
is
that
next
bullet
point
of
potential
work
streams
to
be
prioritized,
and
so
I
think
it
would
be
great
to
use
some
of
this
time
to
set
up
a
backlog
of
what
work
streams
can
should
be
prioritized.
B
But
I
would
also
say
we
can
jump
into
matt
if
you
want
to
do
a
review
of
the
previous
round
of
user
research,
because
I
think
that
for
folks
who
haven't
had
access
to
that
survey
that
was
sent
out
almost
a
year
ago,
that
would
be
a
good.
I
think
grounding
of
some
of
the
things
that
we
want
to
do
is
how
do
we
get
that
that
type
of
feedback
back
into
the
sigs?
How
do
we
engage
with
those
end
users,
so
I
feel
like
we
should
pop
that
one
up
in
the
agenda
list.
B
G
Okay,
so
I'm
gonna
paste
in
three
links
and
the
first
one
is
the
actual
survey
that
folks
are
welcome
to
take
to
get
a
feel
for
it.
The
second
is
the
summary
results
from
from
google
and
the
google
forms,
and
then
the
third
is
the
raw
data,
so
so
yeah.
I
wanted
this
to
be
serve
as
open
and
transparent
as
possible
and
vendor
neutral,
and
so
you
know
so
just
kind
of
you
know
decided
early
on
that.
G
You
should
just
make
the
raw
results
available
to
everyone
to
see,
and
I
think
you
know
where
we
were
successful
in
this
effort-
was
working
with
with
ted
and
the
community
to
put
together.
You
know
what
I
think
is
you
know
a
fairly
high
quality
survey
that
we
were.
G
You
know
able
to
get
at
some
kind
of
key
areas
that
were
useful
to
the
community,
but
then
I
think,
where
we
kind
of
ran.
G
Was
in
getting
this
survey
in
front
of
customers,
so
you
know
we
were
kind
of
getting
ready
to
go
into
phase
two
to
kind
of
get
both.
You
know
a
vendors
to
you
know
to
get
this
to
their
customers.
G
Then
b
get
you
know
language
sigs
to
like
build
this
into
their
their
onboarding
flow.
So
it
was
more.
You
know
like
in
front
of
customers,
and
so
you
know,
I
think
you
know
I
think
we
kind
of
had
a
solid
start,
but
then
you
know
I
was
kind
of
driving
it
alone
and
didn't
didn't
quite
have
the
energy
to
like
push
this
farther.
G
So
I
think
you
know,
I
think
we
got
some
useful
data,
like
with
the
with
the
sample
size
that
we
had,
which
you
know
it
looks
to
be
like
you
know,
16
at
this
point,
but-
and
I
think
the
other
thing
we
had
is
just
you
know-
we,
we
spent
a
lot
of
good
well-used
time,
like
kind
of
thinking
through
how
the
survey
should
flow
and
how
we
wanted
to
phrase
the
questions
you
know.
G
Of
course,
they
could
always
be
improved,
but
I
think
you
know
there's
an
opportunity
to
kind
of
build
on
this
and
take
it
a
step
further,
and
you
know
I
also
kind
of
understand
that,
like
you
know,
a
survey
is
only
sort
of
one
way
to
do
this.
This
is
the
way
that
sort
of
was
able
to
scale
with
the
resourcing
that
we
had,
but
you
know,
there's
certainly
opportunity
for
focus
groups
and
other
ways
to
gather
end-user
feedback
as
well
so
char
did.
Did
I
miss
anything
or
any
other
thoughts.
B
B
So
I
I
connected
back
with
matt
earlier
last
year
and
took
an
action
item
to
update
the
survey
which
I
have
not
done,
and
I
think
one
of
the
challenges,
just
in
general
with
the
survey
is
it.
It
gets
really
good
and
deep
information,
but
I
think
it
also
takes
like
some
level
of
effort
on
the
survey
response,
respond,
bees
side,
and
so,
when
I
think
about
like
what
is
the
next
level
of
this
entire
survey,
type
of
topic
it
comes
down
to.
B
How
can
we
reduce
the
barriers
to
taking
the
survey
and
get
and
also
cross
check
with
the
language
sigs?
What
kind
of
feedback
are
they
looking
for,
and
so
can
we
do
something
that
makes
the
survey
easier
to
take
or
take
up
less
time,
while
getting
the
core
of
what
we're
trying
to
do
and
also
potentially
have
an
option
of
like
hey,
you
want
to
give
us
super
detailed
feedback.
Here's
like
the
long
form
survey.
I
just
I
worry
about
the
time.
B
Investment
for
end
users
on
the
survey
as
it
was
currently
designed,
but
I
think
yeah
I,
that
information
in
there
is
still
relevant
right.
There's
still
a
lot
of
really
good
feedback
and
at
least
getting
that
into
the
hands
of
cigs,
who
have
some.
It's
mostly
around
documentation
was
my
read
through
of
the
survey
responses,
but
I
think
that
would
be
a
good
thing
to
hand
out
if
you
will
to
the
language
sigs.
B
So
is
there
anything
else
that
we
would
like
to
talk
about
with
respect
to
the
16
responses
that
have
already
been
out
there
or.
F
I'm
curious
how
we're
going
to
navigate
that,
especially
given
that
you
know
any
survey
we
create
now
has
to
cover
at
least
traces
and
metrics,
so
it
it
feels
like
we're
getting
to
a
point
where
you
know
even
a
long,
even
if
a
long
form,
if
a
long-form
survey
takes
an
hour
to
complete,
then
maybe
even
that
drops
off
too
much
and
we
need
to
have
a
short
form
survey
and
multiple
kind
of
focused
surveys.
Either
they're
language
focused
or
signal
focused
or
something
right
like.
I
wonder.
F
B
I
think,
philosophically
one
of
the
things
I
want
to
I
aspire
to
do
for
this
end.
User
working
group
is
not
to
put
a
bunch
more
work
on
the
individual
sigs
themselves,
and
so
my
my
approach
of
when
I'm
thinking
through
this
problem,
what
I
wanted
to
do
is
I
wanted
to
show
up
at
probably
the
next
either
maintainers
or
specification
meeting
and
say:
hey
we're,
renewing
efforts
for
surveys.
B
What
are
the
things
that
you
want
to
see
and
give
them
like
a
super
small
survey
for
the
sig
and
maintainer
to
be
like
what
are
you
most
interested
in
and
then
taking
that
and
we
can
craft
it
at
the
potential
expense
of?
How
can
we
help
bridge
that
gap
where,
if
they
had
like,
I
think
we
can
give
them
the
option
and
encourage
them
hey
if
you
have
the
bandwidth
create
your
your
own
survey.
B
But
if
you
don't
like
here
is
the
survey
that
we're
planning
to
send
out
and
our
plan
to
get
you
the
information
back
into
your
sigs,
and
so
I
think,
there's
a
lot
of
surveys,
so
I'm
actually
doing
some
of
the
stuff
inside
new
relic
itself
for
doing
end
user
surveys
and
I've
got
like
the
the
top
level
six
question
survey,
which
is
like
the
the
most
broad
survey,
which
isn't
going
to
get
me
deep
inside
necessarily
probably,
but
what
it
is
going
to
do.
B
Is
it's
going
to
help
me
identify
those
people
who
want
to
give
me
even
more
in-depth
insight,
and
so
that's
how
I
personally
did
this
this,
like
survey
funnel,
if
you
will-
and
so
I
think
that
could
be
a
good
approach
for
the
open,
telemetry
community
itself
as
well.
But
I
just
really,
I
want
to
help
make
sure
that
the
sigs
get
the
feedback
that
they're
looking
for
at
the
right
time
so
like
like,
even
if
they
got
information
about
traces
right
now.
B
Do
they
care
when
everybody's
pushing
for
metric
stability?
Is
that
something
that's
actionable
now?
Can
we
create
a
a
frequency?
If
you
will
of
surveys
over
the
course
of
time
that
says
hey
the
survey
for
this
quarter
is
this.
You
know.
I
think
that
would
be
where
I
think
about
how
to
gather
that
information
in
a
way
that
hopefully
doesn't
overwhelm
end
users.
G
Yeah
I
mean,
I
think,
just
taking
a
step
back
here
too,
I
mean
I
like
I
like,
where
you're
going
sharp.
I
think
one
of
the
things
I
tried
to
do
with
this
survey
is
create
kind
of
a
mix
of
qualitative
and
quantitative
data,
and
so
you
know,
I
think
one
thing
that
would
be
good
to
do
as
a
sig
is
determined
which,
which
key
results
we
want
to.
G
We
want
to
move
over
time,
and
so,
regardless
of
you,
know,
who's
making
the
survey,
whether
it's
short
form
or
long
form,
we
should
have
some
consistency
in
the
quantitative
question
we
asked.
So
we
know
that
we're
moving
the
needle
over
time,
and
we
can
we
can
point
to
that
success.
G
So
so
that's
more
of
like
a
you
know,
like
a
at
some
point.
We
should
probably
step
back
and
think
about
okay,
like
where
are
we
actually
trying
to
move
the
needle?
In
addition
to
getting
you
know,
timely
feedback
to
the
cigs
in
in
qualitative
form
as
well.
B
Absolutely
I
feel
like
that
is
one
of
those
action
items
I'm
gonna
add
there
is
like
taking
that
step
back.
What?
What
is
that
thing
that
we
want
to
measure
over
the
course
of
time,
so
that
we
can
design
a
survey
to
help
with
that.
G
B
Yeah,
so
identifying
what
those
key
results
are
and
then
another
one
of
identifying
what
feedback
the
sigs
want
and
figuring
out
how
to
craft.
All
of
that
together,
I
feel
like
are
the
next
two
most
concrete
action
items
on
this
end
user
survey.
Research
survey
are
there
any
more
that
other
folks
have
identified
from
this
conversation.
B
Okay,
cool,
since
all
of
you
probably
like
interact
with
the
hotel
community
more
than
I
do.
Do
you
think
the
specifications
meeting
or
the
maintainers
meeting
is
the
right
forum
and
are
there
still
maintainers
meetings
there.
E
Are
monday.
E
B
Okay,
excellent
is:
does
anyone
want
to
take
an
action
item?
Are
we
in
a
state
where
we
would
want
to
show
up
next
monday
and
say,
hey
we're
starting
surveys
over
what
are
your
thoughts.
E
B
Good
point:
okay,
so
not
next.
E
That's
the
other
thing
so
that
we
might
not
do
maintainers,
I
suspect,
we'll
have
at
least
one
more,
even
if
we
decide
to
not
have
them
just
to
tell
people
we're
not
having,
but
there's
no
decision
yet
on
that,
but
there's
a
possibility
that
we
make
their
maintainers
meetings
just
turn
them
into
like
a
online.
B
G
G
You
know
just
kind
of
approaching
him
and
saying
hey
like
we're,
starting
something
I
think,
maybe
if
we
could
spend
a
little
bit
more
time,
getting
like
some
kind
of
detail
about
what
we
plan
to
do
and
then
kind
of
share
like
you
know
how
it
how
it
builds
on,
or
does
it
build
on
what
we've
done
in
the
past,
because
I
did
take
time
to
present
to
them
previously
so
folks
who
were
there
might
be
like
okay,
so
last
effort
was
a
dead
end.
G
B
Great
call
out:
okay
yeah
so
too
soon
to
go
to
the
maintainers
meeting.
Hopefully
there
will
still
be
a
maintainers
meeting
when
we
have
want
to
reach
out
to
that
forum
and
also
aspirationally.
B
Maybe
this
is
one
of
the
reasons
that
folks
want
to
go
to
a
maintainers
meeting,
because
if
we
could
essentially
report
out
on
some
of
this
feedback,
I
know
that
primarily,
at
least
for
the
engineers
on
my
team
they're,
most
interested
in
feedback
for
their
particular
sig,
but
anytime,
that
we
can
put
cross
sig
feedback
they've
been
interested
in
that
as
well,
at
least
from
the
new
relic
customer
perspective,
and
so
for
all
end
user
perspective.
B
I
wonder
if
the
other
maintainers
in
the
project
would
be
curious
about
what
feedback
is
happening
elsewhere,
not
saying
they
have
to
have
a
meeting
just
for
that,
but
it
might
be
a
like
a
a
nice
to
have
okay,
so
really
that
that
next
step.
B
So
I
see
that
we're
at
five
minutes,
and
so
I'm
gonna
put
a
a
proposal
that
we
re
re-up
this
conversation
in
slack
and
figure
out
what
what
are
those
key
results
that
we're
trying
to
achieve
with
surveys
and
by
the
next
meeting
that
we
have
in
two
weeks
from
now
that
we
have
at
least
a
little
bit
more
of
a
proposal,
and
we
can
come
back
to
this
synchronous
discussion
with
where
we're
going
from
there
and
then
we'll
figure
out
how
to
engage,
to
get
feedback
about
getting
feedback
from
the
open,
telemetry
community
itself.
F
Sorry
slight
well,
potentially
a
slight
amendment
to
that.
So,
given
what
morgan
said
about
the
maintainer,
the
main
data
meeting,
potentially
going
away,
do
we
want
to
try
to
rush
to
have
something
by
the
potentially
last
maintainer
meeting
right?
So
if
we
meet
two
weeks
from
now
and
that's
the
next
time
we
discuss
and
then
we
present
it,
there
might
not
be.
E
E
What
might
just
go
away
is
the
weekly
sync
just
because
it
was
super
effective
when
we
were
shipping
tracing,
but
but
now
that
we've
sort
of
finished
that
milestone
and
and
and
the
metrics
work,
it's
mostly
being
done
within
the
cigs,
there's
less
need
for
a
weekly
check-in,
there's
still
going
to
be
some
need
for
some
infrequent
ad
hoc
monthly,
something
maintainer
sync.
So
I
I
wouldn't
fret
about
that
too
much.
B
Excellent-
and
so
I
think,
with
our
couple
minutes
that
we
have
left
my
proposal-
is
that
we
have
a
so
we've
got
currently
the
open,
telemetry
you
and
end
user
research,
slack
channel
out
there
in
the
world
today,
and
so
I
think,
that's
the
right
forum
fundamentally
for
this
conversation,
especially
around
surveys
for
sure,
and
so
I
propose
that
we
sort
of
make
that
our
our
home
channel.
B
If
you
will
for
this
topic
and
then
I
also
want
to
get
your
thoughts
on
creating
just
an
overall
end
user
slack
channel
in
open
telemetry
to
eventually
be
populated
by
end
users.
Maybe
we're
not
in
the
state
to
create
that
slack
channel
right
now,
but
I
wonder
if
that
would
be
a
useful
tool
for
end
users
to
connect
with
other
end
users.
B
Instead
of
what
I
have
seen
is
they're
like
oh,
I
saw
somebody
make
a
comment
over
here
and
then
they're
connecting
like
essentially
in
dms
for
some
of
the
customers
I've
been
working
with,
which
is
cool,
but
it
misses
out
the
opportunity
to
like
make
those
conversations
more
public
for
people
who
don't
know
how
to
integrate.
F
Is
a
slack
channel?
There
is
a
slack,
the
right
type
of
forum
for
this
kind
of
like
mutual
support,
or
should
we
be
using,
you
know,
github
discussions
just
like
something
more
like
more
searchable
and
permanent
record-like.
B
D
I
think
I
think
a
stack
overflow
format
makes
more
sense.
I
mean
usually
users.
They
are
going
to
connect
to
this
action
or
just
drop
the
questions
or
their
problems,
and
then
stack
is
not
the
best.
I
think
I
mean
to
search
for
questions,
it's
quite
difficult,
so
I
think,
like
a
forum
or
something
which
will
help
the
users
to
search
for
existing
questions
or
answers
will
make
sense.
I
mean
that's
my
feeling.
F
I
I
do
think
there's
an
opportunity
to
to
have
like
a
central
like
right
now,
if
I'm
in,
if
I
put
on
my
fake
user
hat,
then
I
kind
of
need
to
know
which
of
the
many
repositories
to
use.
So
if
I
come
into
slack,
I
need
to
find
I
need
to
be
on
the
cncf
slack.
I
need
to
find
a
sig
slack
channel
and
then
ask
my
question:
that's
a
significant
barrier
to
entry.
F
On
the
other
hand,
like
anyone,
can
go
and
do
it
or
many
more
people,
I
think,
can
go
to
github
things,
but
then
they
have
this
bewildering
complexity
of
different
projects
to
choose
from,
and
I
want.
I
do
wonder
if
there's
a
a
place
here
to
say:
here's
a
safe
project
to
put
your
user
question
into
as
a
github
discussion.
Maybe
it'll
get
migrated
later,
but
you
can
always
start
here.
This
is
going
to
be
monitored
and
other
users
may
contribute
sick
people
may
contribute.
F
But
you
know
this
is
the
funnel
just
an
idea.
G
Yeah,
just
quick
yeah,
I
mean,
I
think
I
think
we
we
definitely
again
would
need
kind
of
a
proposal
about
kind
of
the
purpose
of
this
and
you
know
make
sure
we
get
all
the
maintainers
on
board
because
yeah.
I
could
see
this
going
a
couple
different
ways
I
mean
yeah.
We
could
become
like
a
central
triaging
service
which
could
get
pretty
expensive
as
things
as
things
scale.
G
As
a
bunch
of
volunteers,
you
know-
or
we
could,
you
know,
scope
it
very
specifically
to
sort
of
what
we're
looking
for
you
know
or
a
third.
We
could
take
a
route
where
we
really
focus
on
documentation
and
making
sure
folks
land
in
the
right
channel.
So
I
think
I
think
we
just
need
to
ask
kind
of
what
our
objective
is
in
doing
this
yeah
go
ahead.
Henry
sorry.
D
D
Where
do
I
get
the
latest
news,
and
this
is
where
I
I
reached
out
to
matt
and
saying
what
don't
we
build
like
a
small
news
like
10
minutes,
podcast
or
video,
just
to
sharing
the
latest
news
about
what
happens
last
few
weeks?
What
is
stable?
What
is
notice,
what
is
in
ga,
what's
coming
in
next,
just
to
yeah,
share
the
news
and
then
share
at
least
the
relevant
links
that
the
community
should
follow.
B
My
apologies-
we
are
here
over
time,
I'd
like
to
take
this
conversation
to
slack
into
our
end
user
research
and
continue
to
like
identify
what
might
be
those
channels
and
what
are
the
challenges
that
end
users
have
with
engaging,
and
so
we'll
do
that
and
then
the
quantifiable
key
results
that
we
want
to
track
over
the
course
of
time
will
be
kind
of
the
topics
over
the
next
two
weeks.
B
So
maybe
we'll
also
talk
about
extending
this
time
meeting.
So
thank
you
for
everyone.
I
appreciate
your
engagement
today
and
everyone
take
care.