►
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
So
we
had
a
big
release
to
our
navigation
experience,
and
one
of
the
things
I
wanted
to
highlight
was
how
we've
been
embracing
feedback
from
our
wider
community
and
what
that
also
looks
like
as
a
designer
on
the
other
side
of
receiving
set
feedback
and
like
what
do
you
do
about
that,
as
well
as
towards
the
end?
A
I'll
try
and
highlight
a
few
things
that
we're
working
on
a
16-2,
and
maybe
we
can
talk
about
some
things
moving
forward,
but
I'd
love
to
kind
of
hear
even
your
own
perspective
around
how
you've
taken
in
feedback,
maybe
stuff,
that's
hard
stuff
that
you
found
has
worked
well
for
you
so
think
about
that
as
I'm
kind
of
going
through.
My
quick
slide
show
here.
A
First
thing
I
wanted
to
highlight:
there
are
lots
of
feelings
about
change.
If
you
go
to
our
feedback
issue,
there
are
tons
of
emoji
reactions.
I,
don't
know
how
to
take
the
cactus.
You
know
it
could
mean
something
could
mean
something
else
who
knows
I'm
not
going
to
read
too
much
into
it.
All
this
really
tells
me.
Is
there
a
lot
of
people
that
have
a
lot
of
feelings?
But
if
you
look
at
the
summation
of
these,
it's
still
a
pretty
small
percentage
of
our
user
base,
either.
A
There's
a
few
hundred
users,
that's
a
very
small
number
in
comparison
like
the
magnitude
of
the
gitlab
user
base.
So
take
it
with
a
grain
of
salt
that
some
of
the
feedback
in
here
is
more
or
less
the
vocal
minority
and
I
wanted
just
to
highlight
a
few
quotes
not
necessarily
to
put
the
spotlight
on
them,
but
to
just
highlight
that
there
are
just
unkind
elements
of
feedback
that
is
part
of
being
a
transparent
company.
That
is
part
of
opening
ourselves
up
to
feedback,
and
it
can
be
hard
to
hear
sometimes
and
that's
okay.
A
It
can
be
hurtful
even
at
times.
Tori
helped
me
appreciate
that
fact
what
I
have
been
encouraged
by
just
having
been
a
git
lot
is
lots
of
team
members
have
reached
out
been
encouraging
to
me
and
some
of
it's
not
even
directed
at
the
feature
itself,
like
maybe
they're,
just
frustrated
about
the
pricing
scheme,
whatever
it
might
be.
That's
not
where
we
want
to
focus
so
just
a
friendly
reminder
from
great
movie
of
Fight
Club
like
you're,
not
your
job.
A
So
what
everybody
in
this
feedback
thread
don't
have
the
perspective
of
is
like
what
it's
like
to
build
a
git
lab
the
challenges
that
we
have
to
work
through
the
trade-offs
that
we're
encountering
and
the
fact
that
we
have
short
toes
and
we
share
our
work
early,
and
these
are
things
that
improve
the
product
over
time,
but
maybe
feel
uncomfortable
up
front.
So
don't
take
harsh
feedback,
even
unkind,
or
hurtful
feedback
personally,
as
best
you
can,
because
on
the
other
side
of
that
you
know
there
are
hundreds
of
comments
and
there's
been
some
really
great.
A
Constructive
feedback
and
I've
been
really
appreciative
to
focus
on
those
elements
and
have
that
as
the
topic
of
conversation
with
the
product
manager
or
engineering
team
and
looking
for
like
okay,
which
of
these
things,
should
we
prioritize
first?
Where
can
we
dive
deeper?
What
can
we
maybe
put
out
a
quick
solution
for
and
that's
where
we're
kind
of
starting
off,
so
we
launched
this
experience
more
or
less
in
16.
A
we
use
16
1
to
kind
of
sit
back
and
back
all
right
like
let's
let
the
floodgates
open,
let's
expose
more
users
to
it.
Let's
get
some
feedback
in
and
now
we're
starting
to
figure
out
in
16-2.
What
can
we
do
next?
How
can
we
take
action
and
focusing
on
those
constructive
feedback
bits
we
put
a
disclaimer
in
there.
A
We
could
not
respond
to
every
comment,
and
you
know
you'll
find
that
sometimes
responding
to
comments
leads
down
a
unproductive
path,
but
I
did
query
a
few
people
on
a
few
of
their
thoughts,
because
I
thought
they
were
constructive
and
they
were
helpful
in
Illuminating,
their
mental
model
or
understanding
their
user
Journey,
or
maybe
the
pain
points
they're
experiencing.
So
that's
given
a
lot
of
great
inspiration
and
a
great
launching
point
to
move
off
into
what
worked
well
for
me.
A
Just
in
this
experience,
because
I
have
not
been
a
part
of
we'll
say
a
feedback
issue
that
is,
has
highly
active
as
this
one
has
been
it's
just
like
taking
bits
of
verbatims,
throwing
them
into
an
issue
and
just
lightly
jotting
down
like
what
could
maybe
be
a
solution
here
that
helped
me
compartmentalize
my
thoughts
and
separate
my
emotions
from
their
reactions.
Maybe
I
was
feeling
at
times
when
people
would
leave
certain
tidbits
of
comments
and
then
beneficially.
It
just
gave
me
a
starting
point
for
a
conversation
with
our
product
manager.
A
So
if
you
have
tips,
I'd
love
to
hear
them
as
well
and
then
for
what's
next
I
would
say:
keep
an
eye
on
the
label.
Navigation,
remove,
toggle
right!
A
That's
where
we're
trying
to
aggregate
all
the
issues
that
we
feel
we
have
to
complete
before
we're
comfortable,
considering
when
we're
ready
to
essentially
deprecate
the
older
navigation,
when
you
no
longer
can
turn
off
the
new
navigation
and
go
back
to
what
you
had
before,
and
that
list
seems
to
be
growing
ever
so
slightly
at
you
know
each
Milestone,
we
discover
new
things
that
need
to
be
addressed
as
we
have
greater
exposure
to
this
future
and
more
users
are
playing
with
it
and
finding
out,
maybe
there's
a
bug
here
or
maybe
we
need
to
catch
up
to
the
design
Vision
we
had
set
out
the
beginning
year.
A
We
hadn't
quite
finished
yet,
but
in
16-2,
what
I
can
say
you
could
look
forward
to
is
like
I.
What
I'm
most
excited
about
specifically
is
how
we're
supercharging
the
the
modal.
The
way
you
search
and
the
way
you
move
around
gitlab,
so
some
cool
things
is
we're
trying
to
make
it
more
discoverable
to
find
search,
but
also
making
it
easier
to
switch
your
context
as
well
as
bringing
in
a
like
several
month,
if
not
year,
old
idea
around
the
command
palette.
A
This
will
help
you
do
things
like
jump
to
a
page
inside
a
project
without
having
to
even
search
through
the
sidebar
or
apply,
hopefully
in
the
future,
we'll
be
able
to
do
things
like
quick
actions
or
be
able
to
find
files
like
we're
finding
ways
to
bring
in
easy,
wins
there
and
then
integrating
that
all
into
the
same
feature
set
so
that
it
becomes
more
useful
and
less
having
the
spirit
options
around.
A
So
hopefully
that
gets
you
excited
as
well
for
some
of
these
we're
working
on,
but
there's
a
lot
of
stuff
that
we
got
going
on
in
the
navigation.
So
with
that
I
mean
I,
hope
that
gave
you
a
little
perspective
on
where
I'm
at
taking
in
that
feedback
learning
how
to
address
it,
as
well
as
some
of
the
things
that
we've
got
focused
on
16-2,
but
I
would
love
to
hear
any
questions
that
you
might
have,
or
even
tips.
You
might
have
for
me
as
I'm
continuing
to
venture
down
this
track.
B
I
have
the
first
comment,
which
is
neither
of
those
things:
okay,
I
wanted
to
give
a
big
shout
out
to
you
Austin.
B
This
is
a
really
cool
approach
to
your
ux
showcase
in
my
four
and
a
half
years
at
gitlab,
I
have
not
seen
anything
get
as
much
feedback
as
navigation
has
gotten
you've,
gotten
internal
feedback,
external
feedback,
positive
feedback,
negative
feedback,
you
name
it.
You
were
gracious,
you
were
generous
throughout
all
of
it.
You
had
a
great
attitude,
the
mental
model
you
used
for,
like
you,
said
compartmentalizing
that
I
think
was
really
effective,
so
great
role
model.
B
C
Yeah
yeah
I
was
just
wondering
how
the
experience
of
collecting
feedback
from
the
community
through
an
issue
differed
from
other
methods
that
you've
maybe
used
in
the
past.
For
when
we
release
a
new
feature.
A
Oh,
that's
a
great
question,
okay,
so
in
the
past,
let's
say
when
I
was
working
in
the
compliance
group,
we're
releasing
very
specific
features,
usually
geared
towards
a
customer
that
put
in
a
specific
request,
or
we
were
targeting
a
specific
Persona.
So
when
we
would
open
a
feedback
issue,
I
would
try
and
like
get
feedback
there.
A
But
generally
you
don't
get
a
ton
of
traction
unless
it's
like
really
controversial
so
where
I
actually
found
some
of
the
most
feedback
that
was
beneficial
to
hear
was
connecting
with
our
sales
team
and
figuring
out
like
where
there
were
struggles
for
them.
Communicating
like
the
new
feature
where
they
were
having
challenges
with
their
own
customers,
trying
to
set
it
up
or
configure
it
or
like
maybe
the
road
bumps
they're
running
into,
and
then
they
would
serve
as
a
place
to
be.
Oh,
hey,
yeah,
go
share
with
our
git
lab
team
members.
A
Your
feedback
in
this
issue
that
kind
of
helped
kind
of
create
a
pipeline
to
that
feedback.
What's
what's
unique
about
this
is
because
we
put
in
gitlab
a
link
directly
in
the
navigation
to
provide
feedback.
I
think
that
like
gave
a
very
easy
target
for
them,
I
don't
know.
A
If
that's
a
pattern,
we
necessarily
want
to
reproduce
everywhere,
but
in
the
past
what
was
helpful
for
me
for
getting
that
wider
feedback
from
maybe
more
Niche
audience
was
connecting
more
with
our
customer
success
or
sales
team,
or
the
people
that
were
interfacing
with
the
users
that
were
consuming.
Let's
say
like
an
ultimate
feature
specifically.
C
Okay,
yeah,
that
makes
sense,
I,
feel
I,
totally
I'm,
understand
and
agree
that
our
customer
success
team,
slash
sales,
helps
us
a
lot,
but
I
also
saw
like
the
feedback
issue
as
being
really
successful
in
getting
feedback
and
I've
done
that
in
the
past,
as
well.
Using
an
issue
for
feedback
and
again
I
had
the
question
of.
Should
we
be
using
that
as
a
pattern
everywhere
or
like
what
method
should
we
be
using
for
collecting
feedback,
but
it's
helpful
to
feel
effective
on
it.
Thank
you.
A
Yeah
sure
thing
I'm
sure
it's
on
a
case-by-case
basis,
but
yeah
anything
that
helps
someone
get
closer
to.
A
Where
do
I
need
to
provide
said
feedback,
I
think
that
always
helps
giving
them
that
shortcut
so
I
definitely
seen
it
sometimes
appear
in
those
alerts
on
pages
or
banners,
or
in
this
case
we
put
a
navigation
specifically
because
it's
related
to
navigation,
but
yeah
I
personally
love
the
fact
that
we
are
open
to
feedback
from
The
Wider,
Community,
I,
love
talking
to
the
wider
community
and
getting
to
have
that
dialogue,
because
I
think
it
is
what
makes
our
product
unique
and
the
way
that
we
are
an
open
core
platform.
A
D
Yeah
I'm
not
really
sure
how
to
ask
the
question,
but
I
think
I
might
figure
it
out.
Okay,
so
for
for
the
AI
stuff,
we
want
to
allow
people
to
give
feedback
on
the
quality
of
the
responses.
D
Yeah
I've
been
feeling
that
this
mechanism
could
be
used
as
a
component
across
all
of
our
UI
in
general
for
for
what
you're
talking
about,
for
instance,
yeah,
but
then
I'm
also
wondering
if
that
would
take
away
from
the
openness
that
an
issue
has
so
I
was
wondering
if
you
had
any
thoughts
on
that,
because
because
the
feedback
component
is
very
I,
don't
know
compartmentalized,
I,
guess
yeah.
A
That's
a
good
question
because
I've
I've
interacted
with
the
gitlab
chat
experience
just
a
little
bit
and
the
feedback
portion
of
that
also
just
a
little
bit
part
of
me
is
distrusting
in
the
sense
of
being
user,
not
a
Get,
Loud
employee,
but
just
as
a
user
of
like
if
I
hit
this
Thumbs
Up
Button
like
what
does
it
do
like
I
have
no
idea
like
where
this
goes
or,
if
I
thumbs
down
like
what
is
it
doing,
he's
a
training,
a
model,
or
is
it
just
going
and
like
linking
to
some
sort
of
API
request
and
dumping
it
as
like
a
thumbs
up
to
some
issue
somewhere
I
like
the
Forum
type
of
discussion
around
features,
because
I
think
it
allows
people
to
elaborate
further,
but
especially
if
we're
just
kind
of
helping
I'm,
assuming
the
benefit
of
having
the
thumbs
up
thumbs
down
in
that
chat,
is
to
help
train
a
data
model
around
if
the
responses
are
going,
the
right
direction
or
not
so
I
think
it's
two
like
there
are
two
sides
of
that
coin.
A
D
D
So
that's
where,
if
you
click
on
the
issue,
you're
seeing
iterations
to
help
get
away
from
that
and
allow
more
for
verbatim
type
stuff,
but
that
those
verbatims
don't
go
into
an
issue,
and
you
can't
have
a
conversation
like
you
might
be
able
to
in
an
issue
right.
You
know
you're
just
getting
a
data
dump
and
then
you
have
to
figure
it
out.
So
it's
an
interesting
dichotomy
to
figure
it
out.
Yeah
for
sure,
for.