►
From YouTube: Grafana UX Feedback Session 2020-12-16
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
B
Okay,
great!
So
what
I'm
going
to.
C
D
B
Okay,
so
to
give
you
some
context
of
what
I'm
showing
I'm
going
to
be,
showing
an
alerting
section
of
a
check
creation
form
in
grafana
cloud
synthetic
monitoring,
and
while
we
have
the
alerting
ui
in
grafana
cloud,
we
have
decided
to
put
a
gui
into
the
check
form
of
synthetic
monitoring
so
that
users
can
create
an
alert
alongside
a
check
and
it'll
be
very
easy.
There
will
be
a
couple
of
inputs
where
they
can
define
conditions
and
then
that
alert
will
be
created
in
prometheus
and
appear
in
the
alerting
ui.
B
So
it's
almost
like
another
option
or
another
avenue
to
create
an
alert
and
the
reason
we're
doing
this
rather
than
just
direct
everyone
to
the
alerting
ui
is
because
we
are
migrating
worldping
customers
to
synthetic
monitoring
and
many
of
them
are
unfamiliar
with
prometheus.
They
may
not
be
able
to
write
promql.
B
The
alerting
ui
is
being
improved
as
we
speak,
so
we
wanted
to
give
them
sort
of
like
an
interim
solution
to
be
able
to
easily
create
an
alert
for
some
context.
This
is
what
the
old
alerting
section
in
world
ping
looks
like,
so
we
were
trying
to
basically
replicate
this
and
make
sure
that
we
have
parity
between
world
ping
and
synthetic
monitoring
and
we
have
not
really
maintained
the
service.
B
So
we
looked
into
the
work
to
sort
of
like
fake
this,
basically
in
synthetic
monitoring
and
create
these
conditions,
but
then
the
alert
will
be
built
on
promql
and
appear
in
the
alerting
ui
so
for
the
first
iteration
and
I'm
I'm
looking
for
ui
feedback,
but
I'm
going
to
walk
through
sort
of
like
the
progression
of
iterations
that
we're
going
to
make
because
we're
trying
to
ship
value
right
away
and
then
we're
going
to
like
slowly
and
iteratively
improve
it.
B
So
the
first
iteration
will
look
like
this,
so
this
is
the
synthetic
monitoring
check
form
if
you
have
not
seen
it,
and
here
the
user
can
define
different
settings
for
their
check.
There
are
different
expandable
sections,
they
can
configure
advanced
settings
and
then
for
every
check
type.
There
will
be
an
extra
setting
or
an
extra
section
down
at
the
bottom
called
alerting,
and
we
begin
by
saying
you
can
set
up
alerts
for
check
here,
but
you
must
visit
the
grafana
cloud,
alerting
ui
to
edit
this
alert
and
add
receivers.
B
So
this
points
to
like
one
of
the
technical
limitations
that
we're
getting
around.
We
wanted
to
ship
this,
perhaps
but
force
the
user
to
have
to
go
to
alerting
ui
to
edit
it
and
set
up
receivers,
because
we
currently
cannot
do
that
in
the
gui
here.
So
this
is
basically
what
it
looks
like.
You
can
set
a
name
to
identify
the
alert
rule,
and
then
this
expression
is
very
similar
to
what
I
just
showed
you
in
the
world
ping
mockup.
B
But
we
say
please
visit
the
alerting
y
to
create
a
receiver
and
associate
it
with
this
alert.
So
those
are
like
the
two
options
I'm
playing
with
either
hiding
the
receiver
section
altogether
or
showing
this
and
telling
them
basically
directing
the
user
to
the
alerting,
ui
and
then
the
evolution
of
this
would
eventually
be
that
the
user
can
visit
the
alerting
ui
to
create
a
receiver.
But
then
they
can
select
a
receiver
from
a
drop
down
here.
B
So
they'll
have
to
first
visit
the
alerting,
ui
create
something
and
then
they
can
select
it
here.
So
it's
making
it
a
little
bit
better
and
then
eventually
we
want
to
get
to
the
point
where
they
can
either
choose
an
existing
receiver
or
create
a
new
one
right
here
in
this
form-
and
this
is
basically
like
similar
to
what
it
would
look
like
in
the
alerting
ui.
But
we
just
put
it
here
as
well.
B
So
that's
one
area
of
feedback
that
I
would
like
is
just
like
the
ui
for
receivers
and
also
the
progression
like
if
that
makes
sense,
and
then
the
other
area
of
feedback
that
I'm
looking
for
is
this
promql
preview.
So,
as
I
mentioned,
the
users
of
this
form
are
most
likely
not
familiar
with
promql,
so
it
may
be
difficult
for
them
to
create
alerts
in
the
alerting
ui.
B
That's
why
we're
including
this
in
the
check
form
and
giving
them
inputs
rather
than
having
them
write
problem
ql,
but
in
order
to
have
them
learn
we
wanted
to
give
a
preview
of
what
this
check
would
look
like
in
promql,
and
this
would
allow
them
to
better
associate
this
alert
with
what
it
would
look
like
in
prometheus
and
then
also
be
able
to
find
that
in
the
learning.
Why
so?
B
This
is
a
preview
and
awana
gave
me
some
good
ui
feedback
on
this,
but
I'm
also
open
to
any
other
suggestions
that
anyone
else
has.
F
So
yeah
just
the
usual,
please
be
sure
to
talk
to
one
of
the
writers
for
help
with
the
ui
text.
When
you
get
close
to
done,
okay,.
G
B
Okay,
see
that's
what
I
didn't
understand,
because
I
come
from
the
incident
response
management
world,
where
you
could
have
many
different
escalation.
Types
like
send
a
notification
to
slacks
and
set
up
like
a
text.
Message
call
me
things
like
that.
So
I
figured
I
just
made
the
assumption
that
you
would
want
to
like
select.
G
G
G
F
F
Okay,
yeah:
it's
just
messing
with
my
sense
of
visual
hierarchy
here,
because
it's
like,
I
almost
can't
see
the
the
severity
and
prom
ql
preview
and
receivers
because
those
other
things
are
just
so
it
has
a
it's
higher.
B
I
want
to
quickly
go
back
to
daniel's
point,
so
I
wonder
so.
I
think
that
makes
sense.
Maybe
there
wouldn't
be
a
need
to
set
up
a
receiver
here,
but
we
some
of
the
users
that
were
migrating
to
grafana
cloud
and
setting
them
up
with
synthetic
monitoring.
They
were
running
grafana,
open
source
and
then
running
world
ping
on
prem,
and
so
they
may
not
have
receivers
set
up
before.
G
It's
a
balance
between
new
users,
and
you
know,
users
that
are
using
all
the
time.
So
I
think
it's
totally
valid
choice
to
have
it
here,
make
it
easy
for
new
users
and
it's
just
whatever
a
section
that
the
other
people
just
skip.
I
think
that's
fine,
so
I
think
in
grafana
we
chose
the
wrong
balance
initially,
so
you
have
something
similar
where
you
actually
have
to
go.
You
know
a
totally
different
place
and
create
your
your
sort.
G
We
call
the
notification
challenge,
but
so
it's
everything
and
then
you
have
to
you
know,
go
back
to
your
alert
rule
and
add
them.
There
was
no
way
to
create
them
directly
from
the
from
the
alert
row
and
and
it
is
a
pain
for
new
users-
and
you
know
existing
once
you've
been
using
it
for
a
while.
Then
it
doesn't
matter,
but
it
is
hard
for
new
users,
so
yeah.
I
think
it's
could
be
a
good
idea
to
have
it
here
anyway.
B
Yeah,
I
think
that's
an
interesting
debate
is
like
whether
we
allow
users
to
create
stuff
everywhere
and
then
there's
just
so
many
avenues
to
do
an
action
or
a
task
versus
having
it
sort
of
like
siloed
to
one
part
of
the
app.
But
then
there's
an
order
of
operations
that
you
must
follow.
That
requires
more
learning
so.
F
G
F
A
I
A
Yeah,
so
I
think
we
can
just
drop
the
ui
part
and
all
in
all,
I
really
like
the
accordions
and
the
way
they
work
here.
I'm
just
wondering
because
you
said
in
the
beginning:
it
just
like
guides
you
to
go
through
through
cloud
alerting
to
set
everything
up
but
later
on.
If
you
set
up
stuff
here,
will
it
still
appear
in
cloud
alerting
and
if
you
set
up
stuff
into
out
alerting,
it
will
also
appear
here
like
how
are
those
two
places
connected.
B
Yes,
so
if
you
were
to
create
a
receiver
here,
the
idea
is
that
this
would
also
appear
in
the
alerting
ui
too
and
again
we're
building
this
for
users
who
may
not
be
using
the
grafana
cloud
alerting
like
they're,
not
familiar
with
it,
so
we're
giving
them
the
option
to
do
it
here,
instead
of
forcing
them
to
go
somewhere
else.
B
Eventually,
when
we
get
to
this
point
and
then,
if
you
set
up
receivers
in
the
alerting
ui,
you
can
choose
them
here
and
all
all
alerts
that
you
create
here
will
also
appear
in
the
alerting,
ui
and
they'll,
be
given
the
same
name
space,
so
that
eventually,
when
we
add
like
filters
potentially
to
the
alerting
ui
for
grafana
cloud,
they
could
filter
to
view
only
or
exclude
all
synthetic
monitoring
alerts
based
on
the
namespace.
B
Does
anyone
have
any
feedback
here,
so
I
this
was
my
first
attempt
to
show
like
the
prom
ql
preview
awana
had
a
good
suggestion
to
make
this
a
bigger
header
so
that
it
doesn't
look
like
it
almost
is
like
a
separate
section
and
almost
sections
that
off
so
that
the
user
doesn't
think
they
can
edit
it.
But
does
anyone
have
any
other
suggestions
for
this
preview
if
it's.
E
H
Yeah,
I
would
also
play
with
a
different
background.
This
is
too
close
to
an
active
input
there.
It's
unclear,
though,
what
you
could
do.
Maybe
you
could
go
in
the
other
direction
of
lighter
than
the
background
or.
E
C
C
B
E
E
D
Yeah
so
good
work
study
for
just
to
add
on
the
expression
section
like
that,
if
statement
you
know
from
a
ux
perspective,
you
know
it's
very
hard
for
me
as
a
user
to
even
like,
like
see
that
that
word,
so
I'm
suggesting
probably
maybe
if
all
of
them
could
probably
be
in
one
line
so
like
if
the
text
works
and
then
the
text.
B
D
E
F
F
Then
I
would
suggest
making
the
second
one
read
like
a
sentence
as
well
like
if
three
more
probes
report
connection
errors
for
five
minutes,
then
alert
is
fired
or
something
like
that
or
then
synthetic.
B
I
played
around
with
some
concepts
of
this
like
almost
sentence:
editing
because
that's
what
it
looks
like
in
world
thing,
it's
just
like
an
inline
sentence
and
you
can
edit
these
boxes
and
the
reason
I
went
with
this
is
because
it
was
a
bit
more
consistent
with
grafana
cloud
alerting.
B
B
Alerting,
I
agree
it's
a
little
funny.
I
can
show
you
some
I'll
I'll
have
to
scroll
around
to
find
it
where
I
had
like.
This
is
an
example.
If
these
conditions
are
met-
and
it
just
looks
funny
in
general
and
not
that
consistent
with
like
the
rest
of
grafana,
I.
A
A
There
are
some
other,
but
I
mean
that
could
also
be
a
just
a
form
sales
issue
because,
like
these
designs
is
where
we
are
really
doing
sort
of
the
edge
case
testing
for
these
styles
and
seeing
right
all
the
potential
issues
with
them.
So
it's
good
that
that
stuff
is
coming
up.
I
think.
C
A
F
Also
consider
who
so
in
terms
of
consistency,
you're
trying
to
be
consistent
with
grafana
cloud
alerting,
but
I
think
we
need
to
think
about
our
audience
here,
because
the
people
who
are
using
grafana
cloud
alerting
are
not
necessarily
going
to
be
the
same
kinds
of
people
using
synthetic
monitoring,
especially
at
first
so
from
what
I
understand.
The
people
who
are
using
grafana
cloud
alerting
are
a
bit
more
sophisticated
and
likely
to
have
been.
F
You
know
to
have
already
done
this
sort
of
thing
in
the
prometheus
alert
manager
and
so
we'll
be
more
familiar
than
synthetic
monitoring,
people
or
the
world
ping
users
coming
into
synthetic
monitoring,
so
you're
you're,
aiming
at
least
initially
at
a
different
level
and
and
type
of
user.
So
you
might
think
about
how
appropriate
it
is
to
try
and
be
consistent
with
both
sets
of
of
users.
B
Yes,
that's
a
good
point.
I
think
we'll
have
to
make
some
decisions
just
to
figure
out
how
consistent
we
should
be
here.
F
Yeah
I
mean
in
general
I
like
consistency,
but
sometimes
it
does
not
make
sense
so
because
we
gotta,
you
know,
meet
the
users
kind
of
where
they
are
here
but
yeah
anyway.
This
is.
This
is
great.
I
I
agree
with
sorry
I
blanked
on
who
who
said
it,
but
I
think
just
that
the
accordions
are
really
nice.
A
All
right
awesome,
I'm
gonna
cut
off
the
discussion
here
because
teddy
has
gotten
a
lot
of
time
and
we
still
want
to
see
charcoal's
project.
So
edit
query
name
charcoal.
The
stage
is
yours:.
E
Let's
see
so
just
some
background,
queries
in
graphon
number
always
had
these
letter.
One
letter
names
abc-
and
this
was
added
very,
very
early
on
to
support
to
support
actually
kind
of
being
able
to
refer
to
another
query
inside
another
query,
to
sort
of
have
like
nested
queries
or
have
like
reuse
a
query
as
part
of
another
query.
I
don't
know
how
many
other
data
sources
that
actually
do
this
beyond
graphite,
so
there
I,
I
actually
don't
know
how
many,
but,
for
example,
here
we
have.
E
This
query
here
actually
refers
to
the
the
first
query
and
sums
that
one
with
the
with
the
with
the
b
query
here,
so
I
can
refer
to
them.
There
are
other
use
cases
for
query
names,
there's
also
a
transforms
you
can
filter
by
by
query
name.
If
you're
reusing
the
query
result
in
another
panel,
we
don't
have
an
override
for
so
you
can
sort
of
match
this
sort
of
display
settings
for
a
particular
so
results
from
a
particular
query,
but
that's
something
we
could
add
very
lightly
in
the
future.
E
So
that's
kind
of
use
cases
for
query
names.
There
is
another
query.
Also
another
use
case,
which
is
actually
why
we're
introducing
this
now
and
that's
also
for
a
common
feature,
called
expressions
where
you
can
kind
of
add
a
new
type
of
expression
in
in
the
query,
tab
to
transform
your
query
result,
which
is
going
to
be
used
for
alerting
and
can
be
used
in
the
dashboard.
E
E
The
reason
I
kind
of
went
for
something
like
a
hover
state
here
is
that
this
is
going
to
not
be
like
an
edge
case,
use
case
or
power
use
case
and
not
something
you
will
do
kind
of,
or
every
sort
of
every
time
you
you
you
edit
panel,
the
queries,
it's
going
to
be
like
a
an
edge
case
use
case,
so
I
don't
want
to
have
like
a
persistent
drop
down
here
for
query
name
or
an
input
field.
That
is
always
there.
So
that's
why
I
sort
of
want
to
explore
this.
E
Having
having
this
be
like
a
hover
state
and
then
you
click
and
it
turns
into
an
real
input-
and
in
this
case
I'm
using
our
normal
input
styles
and
we
only
have
one
input
size
as
well
with
our
kind
of
core
input
component.
So
this
is
using
and
no
custom
styles
here
as
well,
and
you
can
just
change
the
name
and
new
name
and
hitting
enter
or
tabbing
away
or
clicking
away.
E
Anything
will
will
kind
of
jump
you
out
of
this
edit
mode,
so
that
was
the
kind
of
the
the
the
start
mode,
the
start
kind
of
idea.
For
this
feature,
I
wasn't
super
happy
with
this
kind
of
big
input
and
and
focus
state
it
just
feels
sort
of
it
feels
a
bit
so
unelegant
or
something
so
I
explored
a
different
hover
state
as
well.
That
makes
it
almost
almost
look
a
little
more
like
a
button,
but
I
don't
know
it's
just
a
and
a
dashed
line.
I'm
not
sure
it
can
pick.
E
You
can
pick
that
up.
So
this
is
and
and
and
a
bit
different
hover
state
here.
The
input
state
is
input.
Styles
is
a
bit
sort
of
smaller
and
the
focus
state
is
it's
not
as
big
so
so
it's
using
not
our
cost
or
not
our
our
normal
input,
input
focus
here.
E
So
that's
one
option
oops
the
other
one.
Then
I'm
exploring
sort
of
more
subtle
states
here
that,
where
it's
just
a
border
and
where
we
have
the
same
background
as
as
the
element,
this
is
on
new
name.
Oh,
there
is
a
of
course
a
tooltip
here
that
sort
of
says
what
that
you,
you
can
edit
this
or
what
your,
what
you
will,
what
what
this
is
doing.
Edit
current
name.
E
Of
essential
for
this,
this
version
so
yeah
there.
E
There
is
one
last
thing
that
I
I'd
like
to
input
on:
it's
a
if,
if
clicking,
if
sort
of
when
going
into
the
edit
mode
here,
should
the
should
the
text
be
selected,
so
they're,
I'm
not
so
if
you,
when
you
start
typing,
you
can
replace
that
at
night,
the
the
name
or
or
should
it
just
cur
the
cursor
start
at
the
end,
so
there's
kind
of
two
different
kind
of
ways
of
going
into
sort
of
auto,
focusing
and
input
the
benefit
of
having
ever
having
it
selected
is
that
you
can
start
typing
and
it
will
sort
of
remove
the
current
name
and
you
can
type
in
a
new
name.
E
E
F
I,
like
the
selection
option
myself,
if,
for
some
reason
I
want
to
to
just
edit
it,
then
I
just
have
to
hit
an
arrow
key
to
to
unselect
it
so
by
the
way,
what
happens
to
the.
F
So,
if
I'm
querying
a
different
query
and
what
happens
if
the
name
of
the
first
query
is
changed,
will
it
auto-update.
L
E
No,
I
don't
think
that
that
could
be
something
that
we
we
potentially
add
as
a
as
an
kind
of
polish
or
or
extension
feature,
we
don't.
The
grafana
doesn't
really
know
how
data
sources
are
using
this.
So
that's
gonna
be
a
little
bit
tricky
to
do
kind
of
generically
across
across
all
kind
of
use.
Cases
of
the
query
name.
L
E
It's
not
really
sure
yet
so,
because
we're
usually
potentially
using
this
in
in
expressions
so
there
could
be
a
could,
be
an
argument
to
sort
of
not
allow
white
space,
but
but
I'm
not
sure
yet
we
should
probably
we
will
have
validation
or
kind
of
ensure
that
they
are
unique,
because
you
cannot.
You
should
have
two
queries
that
are
the
same
name
which
we
can
currently
because
I
don't
validate
against
that.
But
that's
that's
something
we
need
to
have.
I
With
hoovering
states,
the
only
concern
I
have
is
around
accessibility,
so
I
wonder
if
we
can
make
sure
to
have
aria
on
that
entire
area,
so
it's
keyboard
accessible
and
the
second
thing
would
be
the
dotted
lines
on
their
own
once
entering
edit
mode.
I
don't
think
they
are
visible
enough
for
a
vast
majority
of
our
users,
so
I
wonder
if
we
can
combine
the
two
options
like
on
whoever
keep
as
it
is,
what
you're
saying
right
now
and
in
edit
mode
just
display
a
regular
focused
input
like
we
have
everywhere
else.
M
A
question
is
this:
something
that
we
think
the
user
is
gonna
use
a
lot
like.
Is
this
like
renaming?
The
query?
Is
that
something
that
you
have
to
do
often
and
like
on
multiple.
E
It
could
be
for
alerting,
it
could
be
something
that
is
common
for,
for,
for
I
mean
maybe
not
sort
of
something
that
is
sort
of
every
alert
rule
will
use,
but
some
of
the
more
advanced
alert
rules
will
definitely
want
to
use
this
to
make
to
make
kind
of
the
rule.
The
learning
rule
more
more
expressive
and
understandable.
E
E
M
F
If
I
was
going
to
edit
it,
I
would
expect
to
just
be
able
to
yeah
to
click
on
that
and
change
it,
but
that
pop-up
with
the
white
border.
I
find
that
kind
of
hard
to
read
yeah
that
one
the
dwight
border.
E
M
F
Yeah
well
just
in
general,
by
the
way,
I
think
that
this
is
a
great
usability
feature
I
mean,
even
if
we,
if
people
are
not
referencing
them,
then
I
think
it
it'll
be
helpful
for
people
to
actually
name
the
queries,
something
helpful
so.
L
E
A
I
have
one
tiny
thing,
though,
but
I
feel
like
if
you
activate
the
input
editing
or
even
if
you
hover
over
the
name,
the
clickable
area
is
very
close
to
the
carrot
yeah,
so
I
feel
like.
Maybe
it
would
be
nice
to
have
a
bit
more
margin
in
between
those
so
that
if
you
are
trying
to
move
through
the
carrot
and
you
cross
over
the
editing
you,
you
click
on
the
right
thing
and
don't
hit
the
wrong
one.
E
E
So
now,
right
now,
you
have
to
hit
this
toggle
to
to
toggle
it,
but
and
that's
more
like
an
architectural
reasons
and
sort
of
where
the
click
areas
are
and
and
the
hover
area
for
this
that's
also
kind
of
the
hover
area
is
really
big,
so
you
can
clearly
see
that
it's,
but
it's
also,
maybe
too
big
that
and
you
could.
We
could
have
a
delay
for
the
whole
but
yeah
I'll
I'll.
We
can
maybe
it's
a
bit
tricky
to
sort.
E
I
don't
want
to
move
the
name,
because
the
name
should
align
with
these
labels.
F
What
about
expanding
the
clickable
area
to
say.
C
F
Yeah
like
so,
you
see
how
that
dotted
line.
Actually,
when
you,
when
you
clicked
in
there,
have.
C
C
F
E
F
E
I
tested
having
like
a
whole,
but
I
tested
having
like
edit
query
name.
C
E
On
hover,
but
it
was
really
distracting
and
I
mean
maybe,
if
you
have
a
delay
on
it,
but
I
mean
I
feel
I
feel
like
this
is
like
distracting.
So
I
want
to
have
like
some
kind
of
delay
here,
so
it
doesn't
flicker
as
much.
A
B
E
So-
and
this
is
oh
no
sorry
that
was
the
same-
this
is
just
yeah
that
norm
norm.
This
is
using
normal
input
background,
but
not
the
normal
input
focus,
but
it's
using
and
a
different
input
height,
and
this
is
using
our
every
everything
kind
of
normal
input.
B
E
Yeah
yeah,
oh
it's
it's
a.
I
mean
this
is
the
easiest
one
I
mean
that's
the
one
I
started
with
so
well
and
if
we
just
them,
then
focus
on
the
on
the
highlights
on
the
sort
of
on
the
highlight
styling,
dark
versus
kind
of
raised,
highlight.
E
E
So
yeah
I'll
try
to
tweak
the
the
hit
areas
here
a
little
bit
so
that
this
one
is
not
as
effective.
I
think
it
would
be
this
something
I
really
don't
know
how
much
people
actually
kind
of
minimize
queries,
how
common
that
is,
but
and
and
and
and
and
if
we
should
have
like
collapse
or
expand.
All
that's
another
interesting
question,
but
yeah
that
the
way
it
works
now
is
a
bit
it's
a
bit
small
yeah.
A
E
E
No,
I
I
think,
you're
right.
I
think
that's
why
I
mentioned
that.
I
think
collapsing
at
least
how
how
it
works
now
is
quite
of
an
uncommon
action.
I
think
it
could
be
more
common
if
you
had
like
collapse
all
and
then
it
would
maybe
easier
to
find
the
car
you're
looking
for,
and
then
you
expand
that
but
yeah,
I
don't
know
it's
cool
thanks.
This
was
should
be
useful.
M
Quick
addition,
I
think
you
mentioned
that
we
might
not
have
override
for
the
selecting
field
from
our
query,
I
think
we
have
it
shouldn't,
be
added.
E
Oh
field's
return
by
query:
yeah
you're
right.
Yes,
so
so.
M
We
can
select
yeah,
so
I
think
we
have
the
possibility.
E
Yeah
so
there's
more
to
come
on
on
this
I
mean
a
query
row
I
think
get
related
to.
Maybe
I'm
not
sure.
Yes
have
you
presented
any
of
the
alerting
stuff
yet.
A
Not
yet
because
today's
session
seemed
too
full,
I
guess
we,
we
still
have
a
few
minutes
left,
but
I
don't
want
to
present
without
a
proper
discussion.
So
probably.
E
N
A
A
Yes,
lots
to
come,
yes,
yeah.
We
are
way
over
the
time
talking
originally
booked.
So
it's
no
problem
because
we
don't
have
a
packed
agenda
today.
Luckily
yeah,
but
as
always
thank
all
of
you
so
much
do
you
have
any
feedback
how
we
can
make
these
sessions
better.
B
A
Yes,
it's
also
usually
helpful.
If
your
comment
is
not
just
it
looks
great
or
a
joke
or
something
to
also
address
this
in
the
conversation,
because
then
it's
easier
for
others
to
notice
and
otherwise
it
might
just
get
lost,
even
if
you
do
add
it
to
the
notes.
So
I
encourage
you
to
not
just
write
stuff
in
the
chat,
but
please
discuss
stuff
and
participate.
F
Yeah,
I
agree
with
all
of
that,
but
thank
you
for
everyone
showing
up
it's
really
great,
to
have
a
diverse
group
of
people
having
people
from
different
squads
and
different
places
to
to
in
different
levels
of
familiarity,
to
discuss
this,
because
it's
really
helpful
both
for
for
the
ux
people
and
for
the
writers
who
will
eventually
be
writing
about
what
the
ux
people
are
designing
to
get
to
find
out
what
people
think
about
this,
and
you
know
what
what
your
views
are
on
this
so
yeah
keep
it
coming,
keep
coming.
A
Yes,
very
true,
since
most
of
the
ux
team
is
already
off
next
week.
There
probably
won't
be
anyone
facilitating
this
session,
so
the
ux
team
would
probably
just
cancel
the
upcoming
sessions
until
2021.
A
But
if
you
feel
like
you
have
a
lot
to
present-
and
you
really
want
to
use
the
slot,
then
we
don't
want
to
stop
you,
but
someone
will
have
to
take
over
facilitating
because
we
won't
be
here.
So
if
you
want
to
have
sessions
next
week
or
later
in
2020,
do
approach
the
ux
team.
Otherwise
we
will
cancel
them.