►
From YouTube: 2021-03-16 Code Review Weekly UX Sync
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
I
don't
know
if
you
see
it's
training
or
not,
but
I
already
discussed
this
with
sanjiang,
so
there
should
be
a
lot
of
new
things
for
her
and
we
were
talking
about
the
ux
priorities
and
I
copy-pasted
something
from
our
one-on-one
doc
to
to
expedite
the
discussion
here
and
so
basically
going
one
by
one,
I'm
not
going
to
explain
the
the
issues
and
the
the
epics,
but
I
can
of
course
answer
any
questions
if
you,
if
someone
has
them,
but
basically
the
framework
for
other
merge,
requests
widgets,
it's
the
research
came
back
with
open
questions
and
we
need
to
resolve
them.
A
Yes,
yeah
you're,
you're
you're
on
time,
dory
we're
in
the
point
one
a
still
so,
but
my
idea
with
that
is
to
try,
as
as
soon
as
possible,
to
delegate
the
work
to
other
groups
so
that
they
either
start
doing
their
own
research.
Instrumenting
things
whatever
it
takes
for
us
to
have
more
knowledge
and
make
more
informed
decisions.
A
But
of
course,
the
code
review
group
will
be
there
to
support
and
and
guide
them
through
all
of
this
and
facilitate
collaboration
between
all
of
these
groups,
and
that
would
be
my
my
role,
which
I
hope
I'll
have
more
time
to
to
do.
A
C
I
do
have
a
question
so
so
thinking
of
the
research,
the
follow-up
research
plan
and
how
that's
more
around
the
workflow
and
when
and
how
users
are
using
it.
Would
you
say
that,
or
what
would
you
say,
the
role
of
that
research
would
be
in
terms
of
the
framework
like
this?
Is
that
blocking,
or
is
that
just
kind
of
information
we
want
to
gather
in
general,
but
doesn't
necessarily
block
the
framework
for
other
widgets.
A
A
Well,
the
I
think
the
framework
should
be
solving
something
and
yes,
we
have
inconsistencies
today
that
we
can
solve
in
terms
of
the
experience,
but
the
merge
request.
Widgets.
I
don't
think
I
think
they're
usable
right.
They
they
like
a
user,
can
go
in
and
I
can
see
widgets
that
talks
about.
I
don't
know
securing
vulnerabilities.
I
can
expand
the
widget,
I
can
see
the
vulnerabilities.
A
I
can
use
the
widgets
in
each
one,
I'm
sure
we
can
make
some
tweaks
here
and
there,
but
that
I
don't
think
that's
at
least
my
focus.
That
should
be
more
the
focus
of
the
groups
themselves.
A
What
I'm
more
concerned
is
how
helpful
the
current
design
of
the
widgets
and
how
they
are
presented
and
in
in
the
location
that
they
are
and
the
emphasis
that
they
have
if
they
help
users
solve
their
problems.
So
I
think
one
thing
is
being
efficient
and
usable.
The
other
thing
is
being
helpful
and
effective
in
solving
their
problems,
and
I
don't
think
we
have
information
to
say
that
they're
helpful
and
that
they're
effective
in
addressing
their
needs.
A
So
that's
more
what
I
want
to
to
learn
so
that
we
can
then
take
all
of
that
and
decide
hey.
Is
this
the
current
design?
Is
this
current
design?
What
we
want
for
the
merge
request?
Widgets!
Do
we
want
to
shove
all
of
them
into
a
tab?
A
You
know,
or
do
we
want
to
put
them?
I
don't
know
I'm
just
saying
it's
like
put
them
in
the
sidebar,
or
only
show
the
blocking
widgets
so
only
show
like
if
security
security
vulnerability
is
blocking
the
merge
requests
from
being
merged.
We
highlight
that,
but
everything
else
is
optional
and
not
shown
by
default.
So
there
are
many
things
that
we
can
do
here.
C
That's
what
I
was
thinking
too,
because
I
was
like
they
could
make
all
the
changes,
but
if
we
were
to
find
out
something
that
made
us
think
we
might
want
to
display
the
information
somewhere
else,
then
I
would
I
wondered
if
that
would
be
seen
as
negative,
since
I
already
like
aligned
everything
to
the
framework.
So
thank
you
for
providing
that
context.
A
Yeah-
and
I
really
appreciate
that
you're
willing
to
take
this
on
and
if,
if
anything
this,
this
part
about
the
merge
request,
widgets
can
be
framed
terms
of
cross-stage
collaboration
and
increasing
the
stages
per
organization
in
stages
per
user.
So
if
you
need
to
argument
that
with
adam
and
others,
these
are
things
these
are
kpis
that
everyone
is
looking
at
and
will
help
the
groups
have
more
paid
users
will
help
the
experience
be
better
for
everyone
for
this
single
platform.
C
A
Cool
yeah
and
then
we
will
both
of
us.
We
will.
We
will
talk
about
this
async
and
and
sync,
if
needed,
then
the
merge
requests
that
require
my
attention,
so
we
already
have
a
direction
for
this.
What
we
want
to
to
do
breakdown
is
happening.
A
A
I
would
love
if
sunderland
could
review
the
work
that
I
did
here
and
potentially
one
of
us
either
sanjiang
or
me
would
do
the
solution,
validation
just
to
iron
out
some
of
the
things
to
make
sure
that
we
are
thinking
well
about
this,
in
that
the
must-haves
are
real
must-haves
and
then
nice
to
haves
are
real
nice
to
haves
and
just
so
you're
aware
that
the
solution
validation
shouldn't.
A
Take
that
long
so
because
we're
using
in
the
platform
that
we
use
for
testing
for
usability
tests
right
now,
moderate
usability
tests,
it's
called
usertesting.com
and
in
one
of
the
last
testing
sessions
that
was
about
the
navigation,
but
that
targeted
gitlab
and
github
users.
A
We
had
the
tests
done
in
three
hours,
so
we
had
five
users
going
through
the
test
and
we
had
all
the
results
in
three
hours
and
that's
amazing,
that's
much
better
than
what
we
had
before
usertesting.com.
A
So
I'm
confident
that
if
we
have
something
in
just
a
few
days,
we
have
the
results
of
the
tests
and
we
can
can
make
some
informed
decisions
about
the
finer
details
of
the
designs.
A
Yeah
yeah,
it's
okay,
guys!
If
you,
if
you
want
to
voice
that.
A
A
Okay,
so
basically
what
kai
said:
I'm
gonna
revise
it.
So
what
kai
said
is
that
that
maybe
we
won't
get
a
lot
of
this
prioritize
for
1311
and
that
we
have
some
time
here
to
iron
out
things
for
14.
A
14.00,
okay
and
then,
after
that,
what
I'm
was
thinking
that
sanjing
could
work
on
and
that
ties
in
nicely
with
the
previous
points.
So
a
and
b
is
the
consolidation
of
the
global
mr
actions
and
information.
So
we
don't
have
a
specific
issue
for
this.
We
have
scattered
issues.
We
have
one
for
actions,
another
one
for
a
sticky
heather,
another
one
for
always
displaying
the
branch
information
in
a
visible
location,
and
I
think
this
can
be
something
that
sanjiang
could
drive
through
the
time
that
she
is
with
us.
And
I'm
again
I
don't.
A
I
don't
know
how
long
it
would
take
for
us
to
have
a
validated
design,
vision,
designs
that
are
user
validated
and
that
we
can
break
down
for
implementation,
but
I'm
confident
that
it.
This
fits
within
the
three
milestones,
and
I'm
also
confident
that
by
working
on
this,
so
the
goal
of
consolidating
them,
the
actions
and
informations
and
having
them
in
a
visible
and
easily
accessible
location,
regardless
of
the
merge
request,
would
allow
us
to
move
a
lot
of
the
actions
and
information
that.
A
So
I
think
this
could
help
us
distance
ourselves
from
it
and
at
the
same
time,
it
can
tie
in
nicely
with
the
merge
requests
that
require
my
attention,
because
one
of
the
problems
with
that
design
direction
is
that
the
actions
for
review
for
a
reviewer
are
scattered.
So
we
would
have
wait
for
assignee.
A
Okay
and
then,
finally,
the
last
two
one
of
them
restructuring
the
merge,
requests,
merge,
widget,
it's
something
that
we're
already
breaking
down
and
fuel
is
creating
issues
for
it.
I
don't
think
there's
a
lot
of
capacity
needed
from
us
here
and
the
last
one
is
catching
up
on
emerge
requests,
and
this
is
something
that
I
had
initially
thought
that
sanjong
could
take
the
leads,
but,
as
kai
rightly
mentioned
in
one
of
the
previous
calls,
there
is
no.
A
We
don't
know
what
is
the
ideal
end
state
for
this
now
we're
aware
it's
a
problem
or
better.
Yet
there
are
many
similarly
related
problems,
but
we
need
to
do
to
synthesize
the
existing
research
and
see
what
we
have
before.
We
can
start
understanding
what
would
be
the
best
place
for
us
to
start
working
on
this.
A
On
yeah
so,
and
with
this,
I'm
opening
it
to
the
discussion.
If
you
agree,
disagree,
if
you
think
not
only
from
the
ux
research
side,
but
also
from
the
product
side,
and
also
from
the
technical
writing
from
what
you've
also
seen
in
documentation
and
in
issues,
if
there
are
other
things
that
could
be
more
important
or
other
ways
for
us
to
break
down
this
work.
D
I'm
good
I'm
it's
planning
finalization
day.
I
have
to
get
planning
done,
so
I'm
just
okay.
I
am
supportive.
I
think
this
is
a
good,
a
good
plan.
I,
like
the
two
things
that
you
have
highlighted
here
and
I
think
those
are
those
are
both
actionable
and
completable
or
more
doable
than
some
of
the
other
things
here.
So
I
think
I
think
this
makes
a
ton
of
sense.
So
thank
you.
E
I
think
for
me,
it
would
help
when
we
get
closer
to
time
that
I
can
get
an
issue
assigned
to
me
to
track
the
changes
to
the
documentation,
because
I'm
I'm
beating
the
capacity
planning
drum
really
hard
with
the
technical
writers
they.
They
are
just
going
to
get
on
board
with
this,
and
I'm
trying
to
make
sure
that
I
can
actually
plan
for
my
milestones.
Instead
of
just
you
know,
reacting
when
something
shows
up
in
my
to-do's,
which
is
what
I'm
doing.
A
A
Okay,
and
and
what
about
you,
catherine,
in
terms
of
yeah
all
of
the
body
of
research,
that
we
have
anything
else
that
you
think
could
be
a
higher
priority.
C
Half
at
the
moment,
I
think
these
make
sense.
I
think
the
widget
in
general,
the
mr
overview
page
and
kind
of
figuring
out
the
information
hierarchy.
I
think
that'll
be
really
important,
that'll
be
a
really
great
win
and
then
also
these
other
areas
align
with
what
we've
seen.
So
I
think
you
you
hit
the
nail
on
the
head.
A
Okay,
cool
awesome.
That's
that's
great
to
hear.
A
Okay,
yeah!
That's
that's
what
I
had
in
my
mind
that
I
wanted
to
share
with
you
today
and
to
hear
your
thoughts
on
so
that
I
can
then
relate
this
to
marcel
and
also
to
jackie,
sanjung's
product
design
manager,
so
that
everyone
is
aware
of
what
this
partnership
is
aiming
to
achieve
anything
else.
On
your
mind
that
you'd
like
to
talk
about
any
concerns.
D
So
I
added
a
question
and
then
it
was
just
going
to
ask
you
offline
because
it
didn't.
We
didn't
need
to
have
a
meeting.
So
I
could
ask
my
question,
but
since
we're
here
when
is
the
external
survey
going
out.
A
Well
great
question:
I
have
the
same
question
because
yeah
everything
is
ready
for
quite
some
time,
but
it
looks
like
we're
we're
tweaking
how
many
people
we
would
need,
and
then
I
I
so
caitlyn
she
is
our
ux
research
coordinator.
A
She
told
me
that
we
needed
to
increase
the
incentive
of
the
gift
cards
and
I
updated
that
and
yeah
it's.
I
think
it's
on
her
to-do
list
at
the
moment,
so
I
don't
know
and
she
will
get
to
it.
I
can
try
to
get
an
estimate
of
when
it
will
go
out,
but
I
yeah.
To
be
honest.
I
was
hoping
that
it
was
already
out
and
we
already
had
the
results
so.
B
Would
you
mind
sharing
the
link
for
that
research?
I
I
cannot
find
it
on
the
google
search
now.
A
D
For
reference,
we
ran:
that's
this
almost
the
exact
same
survey
internally,
which
is
why
we're
now
running
it
extra.
We
ran
it
internally
to
get
that
feedback,
and
there
were
some
things
that
I
still
had
questions
about,
and
so
we
decided
we
would
ask
people
that
might
have
different
pain
points
than
what
our
team
has
so
there's.
Another
version
of
that.
That's
probably
the
link,
is
related
issue
that
you
can
go
through
the
the
internal
results
as
well.
A
A
E
E
A
Yeah,
that
makes
a
lot
of
sense.
I
think
this
feedback
is
actually
better
to
relate
to
andrei
and
michelle
and
also
the
rest
of
the
engineering
team,
so
I'll
I'll
copy.
This
point
to
our
weekly
sync.
That
should
happen
tomorrow.
Yeah.
C
A
D
Cool
thanks
pedro
for
putting
all
this
together
again
and
good
to
see
everyone
enjoy
the
rest
of
your
week.
13
11
starts
thursday.