►
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
So
this
is
our
team
members.
All
people
are
super
helpful
and
then
they
are
really
interested
in
this
design
change.
So
that
helps
me
a
lot
and
if
you're
interested
in
you
can
just
hit
the
handbook
link
later
and
we
have
this
global
search
category
as
viable,
but
actually
there
are
a
couple
of
more
so
if
you
haven't
used
this
feature
so
I
I
know
that
some
of
folks
never
use
this
feature.
So
I
prepared
this
screen
already.
A
A
A
So
if
I
just
go
back
to
the
screen
like
this
is
like
issue
which
it's
just
a
list
view,
so
I
just
name
it
here
as
a
general
view,
which
is
just
the
common
list
like
issue
and
mr
comments,
this
this
looks
really
similar
to
each
other.
So
if
you
see
the
merge
request
page,
it
takes
a
while
to
load
this
page
and
yeah.
It
looks
really
similar
to
each
other,
but
if
you
hit
the
okay
comment
button,
it's
also
another
type
of
a
list
view
but
looks
a
little
bit
of
different.
A
Of
course,
it's
a
search
result
of
the
comment
and
if
you
are
going
through
the
wiki
tab,
which
is
quite
like
similar
to
the
code
search,
it
looks
like
a
code
box
and
also
with
some
title
of
the
file.
So
I
kind
of
categorized
with
this
three
type
of
view.
Just
to
understand,
okay,
this
is
the
information
structure
inside
of
this
page,
and
then
I
I
know
what
I
have
to
do
for
the
next
step,
so
also
just
before
this
milestone
started,
we
started
the
this
design
discussion.
A
So
for
this
time
I
started
to
using
the
figma
as
the
single
source
of
true,
like
symmetry.
You
mentioned
a
lot
before
so
I
just
put
my
initial
draft
and
proposal
in
this
feed
my
file
and
then
just
paying
the
team
they're
like
hey,
just
give
me
the
feedback
when
you're
free,
so
they
just
jump
in
and
I
actually
never
expect
this
much
of
feedback.
A
So
if
you
see
the
comments
like,
I
got
so
many
valuable
feedback
from
the
engineers
and
the
pm,
so
it
was
really
helpful
for
me
and
after
that,
I
had
to
rework
on
this
design
based
upon
their
feedback,
and
we
made
some
synchronous
design
discussion
together
with
the
engineer
and
also
with
the
pm,
because
I
think
for
the
search
performance
is
quite
important
factor.
So
I
also
like
to
hear
their
perspective
and
I
also
want
to
deliver
something
makes
our
performance
better.
A
So
actually,
this
was
the
type
a
that
I
came
up
with
at
that
time.
So
what
I
had
in
mind
at
that
time
was
just
like
if
you
just
imagine,
google
search
is
like
the
title
and
the
description,
and
it
has
some
some
space
and
I
also
want
to
show
some
status
indicator
if
it
is
about
issue
and
the
merge
requests,
because
I
think
it's
important
to
show
them,
and
this
was
a
type
b,
because
I
got
a
really
valuable
feedback
from
my
manager,
jackie
and
then
like
yeah.
A
Actually,
we
have
this
type
of
similar
view
in
the
issue
board
and
also
the
merge
request
board
and
I
feel
like
yeah.
Maybe
we
can
reuse
this
component
if
it
works.
So
I
provided
this
two
different
types
of
the
layout
and
I
also
made
some
noise
in
the
ux
co-working
channel
because
I
wasn't
sure
like
which
type
of
font
style
do.
A
A
So,
and
this
is
the
other
thing,
so
I
just
also
want
to
share
with
the
engineering
team
and
the
product
team
that
okay,
maybe
it
should
work
like
this.
If
we
have
the
left
rails
faucet
as
advanced
filter,
then
I
think
it
should
really
work
that
was
just
based
upon
my
imagination.
I
didn't
have
a
really
like
tough
research,
so
that
was
just
from
my
gut
feeling.
A
So
I
came
up
with
this
design
and
I
asked
several
different
designers,
including
my
peer
designer
hyanna
and
the
ux
researcher
lori,
and
then
I
got
so
many
valuable
feedback,
so
the
left
one
is
the
first
version,
and
this
is
like
the
version
four
or
something.
So
I
decided
to
go
for
this
last
proposal
and
the
team
like
this
version.
A
So
this
is
how
iteration
like
changes
in
the
design
look
like
and
just
before,
planning
for
the
implementation
planning
like
we
are
thinking
about
like
which
component
should
go
first
and
I
suggest
to
focus
on
this
red
area,
because
it's
more
flexible,
I
mean
in
terms
of
front-end
structure.
I
think
it
should
be
more
flexible
if
you
just
start
with
this
design
and
for
this
type
of
left
rails
faucet.
I
I
wasn't
sure
it's
a
big
design
changes
and
it
also
includes
some
behavioral
changes.
A
A
So
I'd
like
to
keep
that
area
in
my
backlog,
so
we
are
working
on
the
very
first
iteration
as
the
first
part.
So
I
think
our
pm
john
created
this
issue
and
we
are
going
to
working
on
this
so
after
this
issue
is
delivered.
So
this
is
the
current
design
and
the
right
one
will
be
the
expected
changes.
So
if
you
see
that
like
we
have,
we
can
show
a
lot
of
more
different,
a
lot
of
contents
than
before,
because
it
now
is
aligned
with
our
latest
pajama
design
system.
A
Thanks
to
that,
I
can
just
deliver
this
in
a
really
quick
quickly
and
also
we
will
have
a
small
status
indicator
in
front
of
each
issue
and
also
the
merge
request
title
and
for
the
part,
two
first
iteration.
We
are
going
to
introduce
this
advanced
filter,
which
is
part
of
sorry
part
of
this,
but
I
I
was
really
hesitant
to
deliver
this
faucet
as
it
is,
so
we
are
agreed
that
to
deliver
like
this
type
of
just
using
the
default
drop
down.
A
So
this
is
for
the
future
iteration
and,
of
course
I
need
to
spend
more
time
on
make
this
more
like
visionary,
crazy
changes.
I
I
think
I
should
spend
more
time
to
do
that,
but
before
that,
like,
I
would
like
to
validate
with
user
if
this
makes
sense
to
them
and
also
what
we
are
missing
currently,
because
I
just
like
dive
into
this
team
and
this
design
ticket.
A
So
this
was
the
progress.
It
was
a
really
quick
turnaround,
but
I
I
could
do
it
thanks
to
the
team's
help
and
I
think
for
the
future
iteration
I
I
will
take
a
look
also
the
admin
area
to
for
the
system,
administrators-
and
I
just
like
to
share
with
you
that,
like
we
have
pretty
strong
features,
so
this
was
from
our
team's
demo
that
it's
a
custom
search
feature,
I
think,
which
is
quite
quite
famous
for
the
developers,
and
this
is
also
internal
link.