►
From YouTube: Create:Code Review Weekly UX Sync - 2020-01-13
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
So
it's
like
basically
strategic
things
that
we
do
outside
of
the
milestone
or
outside
of
what
we're
planning,
in
the
short
term,
more
or
less,
and
so
one
of
the
things
that
we
that
I
did
was
finalize.
The
insights
that
came
out
of
the
ux
department's
merch
request
experience
a
syncretic
critique,
and
I
created
that
insight
summary
as
a
way
to
digest
all
of
them
and
I'm
going
to
socialize
those
findings
with
the
broader
audience
and
the
corresponding
stakeholders
from
the
stage
groups
so
that
they
can
act
on
them.
B
So
I
created,
I
created,
I
think,
or
created
or
linked
to
around
50
issues
and
of
things
that
we
can
do
today
to
improve
the
emergency
request
experience
and
next
there
are
two
things
that
come
to
mind
that
I
added
there
one
is
to
research.
The
intention
and
usage
of
the
merge
request
widgets
to
understand
how
each
one
of
them
is
being
used
today,
like
if
they're
instrumented
or
not
what
what
is
the
goal
of
each
widget.
B
Like
we
have
evidences
that
allows
us
to
plan
better
and
understand
what
we
need
to
do
to
improve
the
merge
request
widgets,
because
this
is
a
project
on
its
own
and
the
merge
request
widget.
Since
I've
been
here
at
gitlab
we've,
I
think
every
designer
and
product
manager
has
been
afraid
of
the
merge
request,
widgets.
B
We
were
kind
of
afraid
of
touching
them
and
doing
something
grand
with
them,
and
there
was
only
one
time
where
we
redesigned
the
merge
requests
widgets
into
what
they
are
today.
But
it
was
mostly
a
cosmetic
change,
not
a
significant
experience
change
and
it
has
grown
a
lot
and
it's
the
problems
are
visible
to
everyone
and
so
that
we
can
do
this.
B
Well,
we
need
to
know
exactly
what
we're
dealing
with
and
I
for
one
I
don't
know
exactly
the
whole
extent
of
the
merge
requests
with
it
and
what
all
of
those
widgets
I
know
what
they're
for,
but
I
don't
know
how
they're
used,
if
they're,
useful
or
not,
and
if
they're
well,
designed,
if
they're
well
thought
out
if
they're
well
implemented-
and
I
think
we
need
to
know
all
of
those
things
in
order
to
make
good
decisions
about
like,
for
example,
creating
a
framework
that
allows
us
to
collaborate
with
across
stages.
B
Because,
right
now,
it's
like
everyone
just
puts
in
the
mercury
pass
widget
what
they
want
and
they
kind
of
copy
paste
from
other
places
and
other
widgets
that
they
see
and
it
leads
to
a
dysfunctional
experience.
So
I
think
it's
it's
very
high
priority.
Another
high
priority
is
having
the
jobs
to
be
done,
and
it's
something
that
we
discussed
in
one
of
the
previous
ux
syncs.
B
But
looking
at
those
two,
I
think
the
merge
request,
which
is
much
more
important,
although
the
jobs
to
be
done,
will
certainly
be
helpful
in
grounding
our
map,
making
sure
that
we
are
making
good
decisions
and
prioritizing
things
well
and
linking
them
back
to
the
jobs
to
be
done
and
having
the
whole
team
speaking
that
language,
but
the
merge
request
widgets,
I
still
think
they're
more
important
yeah.
C
Okay,
well
I'll
go
first,
so
basically
this
I
think
I've
been
having
a
parallel
capacity
problem,
especially
the
past
couple
of
quarters,
there's
a
big
competing
competing
priority
of
navigation
and
sus.
But
anyway
I
I
see
a
similar
problem
and
I
know
it's
discussing
designer
capacity,
but
if
there
is
any
research
or
capacity.
C
Might
be
helpful
as
well
for
code
review,
but
nonetheless,
if
we
could
do
well
actually,
maybe
kai
has
insight
on
whether
the
mr
widget
is
kind
of
like
the
number
one
priority,
because
I
know
there
are
some
other
topics
being
discussed
right
now.
But
if
this
is
like
the
number
one
research
priority,
then
I
can
go
kind
of
more
all-in
in
13-9
on
this
topic
and
then
kind
of
provide
a
bit
more
support
for
the
other
topics.
A
I
struggle
a
lot
with
the
mr
widget
and
I
struggle
a
lot
with
the
merge
button
and
I've
been
trying
to
figure
out
how
we
rationalize
capacity
and
time
and
our
design
and
research
and
engineering
efforts
against
those
things
and
how
we
rationalize
them
against
net
new
road
map
feature
product
development
and
the
largest
reason
I
struggle
is
not
because
I
don't
think
that
these
areas
are
like
wildly
confusing
and
important
and
in
fact,
every
time
I
see
a
screenshot
with
these
stupid
arrow
buttons
on
different
sides
of
that
button.
I
wanna
like
I.
A
I
don't
I'm
so
furious
that,
like
it's
a
thing
and
I
wish
I
was
like
intelligent
enough
to
fix
it,
but
I'm
so
furious
that,
like
it's
a
thing
on
the
flip
side,
it's
not
really
my
thing
to
fix,
and
this
is
where,
like
I
get
into
the
ultimate
struggle,
I.
A
Coder,
you
didn't
implement
that
button
and
I
think
what
we're
missing
is
like-
and
this
is
this
trickles
down
to
the
merge
button,
which
is
like
sort
of
that
other
big
insight,
that
pedro
link
that,
like
there's
500
comments
about
the
merge
button,
and
it's
rightfully
there
are
because
it
is
so
confusing
the
code
review
didn't
actually
make
it
confusing.
In
fact,
code
review
has
like
two
states
of
that
button:
merge
or
not
merge
the
ci.
A
That
added,
like
500
other
states
to
that
button
in
all
of
the
additional
conditional
logic
right
and
like
change,
the
button
to
not
say
merge,
it
can
say
like
merge
when
pipeline
succeeds,
add
to
merge
train
when,
like
if
the
reality
is,
is
like
the
user's
doing
a
merge
like.
Why
does
it
say
five
different
things?
It
should
always
just
say:
merge
like
nobody
cares
how
it
got
there.
A
It's
just
a
merge,
but
like
we
didn't
do
that,
and
so
on
the
one
hand,
like
I'm
conflicted
because,
like
these
things
all
directly
impact
the
core
merch
request
experience
on
the
other,
like
I'm
frustrated
that,
like
we're
being
forced
to
solve
them,
because
that
means
we
don't
get
to
go,
develop
new
features
and
we're
sort
of
like
giving
people
a
pass
that
they
broke
the
merge
request,
and
so
I
don't
know
james-
and
I
talked
about
this
yesterday
about
like
how
do
we
get
more
of
our
time
and
focus
on
doing
this?
A
I
don't
I
don't
know-
I
am
personally
trying
to
deal
and
struggle
and
rationalize
these
things,
because
I'd
love
for
pedro
to
be
like
hey.
This
is
what
every
single
merch
request.
Widget
needs
to
work
like
this,
and
these
are
the
things
that
you
can
do
and
if
you
go
beyond
this
scope,
like
you
can't
that's
not
okay
and
blah
blah
blah
like
here's,
here's
the
here's
the
box
play
in
the
box,
can't
go
outside
of
it
and
like
this
is
what
they
all
need
to
look
like
and
do
and
blah
blah.
A
Does
this
full
viewful
report
button
need
to
be
there
and,
like
all
three
of
the
designers,
of
those
different
groups,
sort
of
gave
like
varying
answers
of
like
if
that
button
was
useful
or
like
was
the
right
wording
or
not
and
like
even
like
the
implementation
of
the
same
button
is
sort
of
like
different
depending
on
who
you
talk
to,
and
then
I
think
similarly
for
the
merge
button,
like
I'd
love
for
us
to
spend
all
the
time
and
do
that
but
like
if
we
do
that
pedro's
not
gonna
work
on
this,
like
mr
reviewer
handoff
tracking
file
thing
like
he's
just
not
and
I'd
love,
to
say
that
he
is
but
he's
not
he's.
A
Just
not
that
won't
have
the
time
as
much
as
he
thinks
he
might.
He
won't,
and
so
so
I'm
conflicted,
because
I
want
to
push
our
roadmap
ahead
and
go
do
more
things
but,
like
I
think
these
things
need
to
be
solved,
and
so
I
don't
know
I'm
sort
of
curious
like
how
do.
C
I
feel
like
that's
probably
what
each
of
us
run
into
and
maybe
in
this
particular
case
it
will
make
sense
to
start
with
the
research
of
the
mr
widget
and
then
pedro
is
still
focusing
on
the
current
work
and
then
once
the
mr
widget
research
is
kind
of
wrapping
up.
He
may
have
capacity
to
start
thinking
about
that,
but
it
might
deter
depend
on
what
comes
out
from
that,
but
yeah
in
general.
C
I
think
that
is
like
nail
on
the
head,
the
problem
that
maybe
in
create-
or
I
don't
know
if
it's
specific
to
code
review
if
it's
create
and
a
couple
other
stages.
This
unwieldy
thing
of
people
have
been
kind
of
just
adding
things
and
things
have
been
changing
organically
and
now
one
group
needs
to
fix.
It
has
been
challenging.
I
think
that's
also
what's
happening
in
editor
with
the
navigation
and
settings
and
whatnot.
B
Yeah
yeah
so
another
perspective,
so
I
agree
with
everything
that
both
of
you
said.
Another
perspective
is,
we
could
always
delegate
this
to
another
team
right,
so
we
don't,
as
you
said,
kai
like
it's.
B
We
like
from
all
of
the
things
that
are
there,
we
have
the
approvals
widgets.
We
have
the
one
at
the
top
more
or
less
that
talks
about
checking
out
a
branch,
and
then
we
have
the
merge
one
where
everyone
kind
of
puts
their
things
together.
There
are
so
many
other
widgets
and
they're
all
interacting
together,
and
we
already
have
so
much
work
to
do
so.
B
The
only
reason
why
we
would
do
this
is
because
it's
in
the
merge
request
page
right
if
it
was,
if
you
had
another
page
in
the
product
in
the
the
app
that
said,
I
don't
know,
merge,
requests
things
or
something
like.
Maybe
it
wouldn't
be
our
responsibility,
maybe
it
would
be
a
shared
responsibility.
The
conversation
would
be
different,
so
I'm
not
opposed
to
having
another
team
leading
this
and
it's
something
that
I
haven't
explored
because
we
have
so
many
things
to
do.
B
B
I
think
and
that's
why,
at
the
first
point
that
I
added
there
is
discussing
design
capacity
yeah
and
we're
massively
understaffed
in
also
front
end
and
backhand,
because
yeah
compared
to
other
groups,
we,
the
core
experience,
I
believe,
has
been
highly
neglected
in
favor
of
other
things
where
we're
making
investments
but
yeah
it's
the
way
it
is,
and
but
those
investments
are
reflected
in
the
experience
that
we
have.
Basically.
B
A
B
I
mean,
for
example,
phil
on
the
front-end
side
has
started
that
work
with
the
graphic
ql
approach
to
the
merge
request,
widgets,
which
is
great,
and
I
think
we
need
more
people
to
own
that
and
to
be
the
shepherds
and
to
allow
and
facilitate
the
collaboration
that
happens
on
those
widgets.
B
The
pipeline
there's
a
pipeline
tab
who's,
the
owner
of
the
pipeline
tab
in
merge
requests.
Is
it
us?
I
don't
think
so
in
the
future,
with
the
security
tab,
it's
not
going
to
be
us
as
well,
so
there
are
already
people
that
own
parts
of
the
merge
request
ui
that
are
not
code
review.
So
I
I
wouldn't
be
surprised
if
someone
else
took
this
on
if
they
have
more
capacity.
A
A
C
Yeah,
I
think
I
think
I
can
take
the
baton,
so
pedro
has
started
with
this
really
good.
Well,
it's
awesome
one,
the
layout
of
all
the
mr
widget
parts,
that's
in
figma,
that's
talking
about
the
empty
state
and
things
like
that
yeah.
I
think
so
that
issue
that
I
have
with
the
merge
request,
rigid
widget
research,
synthesis
and
jpbd
outline.
C
I
think
that
should
be
the
next
step
and
then
from
there
we
might
be
able
to
see
what
we
will
ideally
see,
which
groups
have
the
most
things
going
on
in
that
widget,
because
then
they
need
to
be
like
direct
collaborators.
We
need
to
discuss.
Why
did
you
put
this
here?
Maybe
if
they
have
usage
statistics
or
anything
on
it
so
far
and
like
where
they
think
it's
evolving
to?
I
think
there
will
need
to
be
conversations
with
basically
the
stakeholders
of
the
widget
as
it
currently
exists
and
go
from
there.
So
that's
why?
C
Let's
have
a
research
phase
for
the
widget
as
the
next
step,
and
then
we
can
reconvene
once
that
is
that's.
What
I
think
might
might
be
good
as
a
that's
a
setup
right
now
and
then,
maybe
by
that
time,
design
capacity
discussion
would
be
hopefully
making
some
progress,
but
we
can
reassess
at
that
point.
A
Yeah,
I
might,
I
think,
it'd
be
interesting
to
ask
the
other
groups
where
they're
going.
I
might
suggest
that
we
take
like
a
more
benevolent
dictator
approach
and
sort
of
not
care
where
they're
going
to
some
extent
and
and
maybe
making
it
more
fortunate.
I
think
one
of
the
things
that
I
have
seen
is
that
shared
responsibility.
Things
like
this,
don't.
A
A
I
would
like
to
see
a
sort
of
like
here's,
the
thing
and
then
here's
your
hit
list
of
issues
and
then
like
I
can
go
work
with
pms
and
group
pms
and
like
these
need
to
be
fixed
over
like
the
next
90
days
and
it's
sort
of
non-negotiable,
but
like
or
we're
gonna
like
rip
your
widget
out
of
the
merge
request
page
until
you
like
make
the
changes
and
like
I
don't
know
that
we
can
do
that,
but
I
think
like
if
we
go
and
sort
of
try
to
do
consensus
building.
A
But
you
know
someone
in
in
code
review
has
to
look
at
that
and
give
it
an
approval,
like
we
don't
use
code
owners
very
heavily
at
gitlab,
but,
like
maybe
we
start
and
like
we
put
a
required
approval
in
which
would
be
like
one
of
the
first
blocking
required
approvals
in
like
all
of
gitlab,
but
like
this
might
be
an
area
of
the
project
that
needs
it
and
like
we.
I
think
we
need
to
be
more
heavy
handed.
A
B
Yeah
yeah,
I
agree.
I
think
we
we
need
to
be
more
of
a
dictator
in
this
sense.
B
Because,
as
you
said,
the
everyone
can
contribute
approach
is
clearly
not
working
and,
and
it's
I
think
it's
more-
the
everyone
can
contribute
without
oversight
that
is
not
working
basically,
but
oversight's
is
work,
and
I,
when
I
when,
when
I
was
thinking
about
asking
like
the
different
groups,
what
they're
planning
to
do
and
and
also
talking
about
what
they've
done
with
the
widgets,
it
wasn't
so
much
about
the
solutions
it
was
about.
B
The
problems
like,
for
example,
in
the
view
viewful
report
button
discussion
and,
like
I
suggested
like
why
don't
we,
it
was
actually
one
of
the
comments
that
someone
made
in
the
critique
they
said
like.
Why
do
we
say
full
here?
Why
don't
we
just
say
view
report
and
that's
the
question
I
asked,
and
I
didn't
have
a
great
answer.
They
didn't
have
a
great
answer
to
that,
because
actually
what
happened
was
that
they
weren't
showing
when
you
expanded.
It
wasn't
the
full
report.
B
So
when
asking
what
they're
planning
more
than
the
solutions
that
they're
thinking
is
what
kinds
of
problems
would
integrating
with
the
merge
requests
page
help
for
your
group,
I
think
that's
more
than
what
I
was
looking
at,
but
then,
as
more
of
a
dictator
or
very
strong
and
opinionated
shepherd,
we
would
say
hey.
B
This
is
the
box
where
you
can
draw
in
we're
here
to
help
you
and
we're
here
to
help
you
understand
how
the
problems
that
you
have
today
that
your
customers
have
and
that
you're
wanting
to
solve
if
they
fit
this
model
or
not,
or
maybe
you
need
to
find
something
else
or
pivot,
the
problem,
or
I
don't
know
whatever
it
is
rather
than
telling
him
okay,
okay,
we
will
make
it
work,
we'll
make
changes
to
the
merge
request,
widget
so
that
you
that
can
work
so
in
a
way.
B
I
think
it's
we
need
in
the
same
way
that
we
have
the
ux
foundations,
team,
ux
and
front-end
foundations,
where,
like,
for
example,
there
was
this
issue
today
about
hey.
We
we're
we're
designing
a
badge
that
appears
like
a
series
of
badges
that
appear
in
a
list
somewhere
in
the
product,
but
they
don't
have
loading
states.
So
we
need
loading
states
for
badges
and
we
don't
have
them.
And
so
the
first
thing
that
the
ux
foundation's
team
does
is
understand
the
problem
that
you're
solving.
B
B
Well,
I
think,
in
the
end,
we
all
agree
how
how
it
should
play
out.
B
The
the
thing
is:
there's
not
enough
time
for
everything,
but,
but
I
just
wanted
to
to
to
finish
by
saying
that
I
agree
with
what
catherine
was
suggesting
in
terms
of
the
research.
B
C
Yeah,
so
I
I
guess
I
get
the
sense
from
this
now
that
it
still
makes
sense
to
move
forward
with
this.
Mr
widget
research,
now
because
this
isn't
a
problem
that
will
might
go
away
in
importance,
it's
kind
of
like
it's
always
going
to
be
important,
but
what
I
was
initially
referring
to
was
things
like
the
internal
survey
or
the
code
review.
C
B
Milestone,
okay,
yeah
that
clarifies
it
for
me
in
terms
of
solution
validation,
I
mean
I
wouldn't
expect
you
to
do
it,
but
of
course
I
I
really
appreciate
your
feedback
and
and
support
throughout,
but
other
than
that.
Like
these
kinds
of
things,
I
mean
someone
has
to
do
it.
A
A
A
I
would
say
we
have
the
same
problem
with
the
merge
request
button,
which
is
like
my
point
c,
which
is
like
a
totally
different
thing
than
the
merge
request,
widget,
which
we
also
need
to
spend
time
on,
and
so
I
guess
my
question
would
be
like
if
catherine
does
merge,
request
widgets
like
pedro.
How
are
you
feeling
about
like
some
of
the
work
that
you
would
do
for
merch
request?
A
I
think
we'd
all
probably
also
agree
that
that's
very
important
work
that
needs
to
be
done
in
comparison
to,
like
the
other
thing
that
we
sort
of
have
in
flight,
which
is
reviewers
and
handoff
and,
like
that
design
issue
that
you
have.
That
has
all
those
proposals
that,
in
order
for
like
engineers
to
be
able
to
action,
would
sort
of
need
more
things
there
like.
How
are
you
feeling
about
sort
of
those
two
things.
B
B
Most
of
them
have
no
milestone.
B
B
I
didn't
create
any,
I
think
what
you're
getting
at
is
it's
not
just
about
what
we
know
are
like
cosmetic
or
text
issues.
It's
the
merge
button
has
so
many
different
states,
they're
not
mapped.
We
don't
know
what
causes.
What
and
because
of
that
and
over
time
the
experience
itself
has
been
kind
of
disjointed.
So,
even
if
all
of
the
cosmetic
issues
are
solved,
even
if
the
copy
is
perfect
it
it's
still
frankenstein
just
that
merge
area
like
that's,
that's
where
you're
getting
it
right.
B
So
I
think
in
that
sense
there
is
no
comprehensive
look
into
that.
So
that
would
be
another
project
is
to
just
look
into
that
map.
All
of
that
out
see
who
owns
what
and
in
the
vein
of
a
framework,
define
some
guidelines
and
design
what
the
experience
should
look
like
for
that
widget,
specifically
and
adapt
all
of
those
different
states
and
make
sure
that
they
all
work
well
in
a
predictable
way
and
that
it's
scalable
for
the
future.
B
Given
the
current
structure
of
the
merge
request,
widget
because,
for
example,
in
the
future,
what
I
would
hope
is
for
us
to
move
the
merge
button
into
a
much
more
visible
location
and
always
present
kind
of
in
a
toolbar
where
you
have
like
in
the
same
way
that
you're
looking
at
this
agenda-
and
you
have
the
blue
share
button
on
the
top
right
corner.
B
Imagine
having
something
like
that
for
merge,
but
that's
that's
going
forward,
that's
much
more
in
the
future,
but
given
the
constraints
that
we
have,
I
think
that's
something
that
we
need
to
do
is
map
all
of
those
things
and
and
do
what
I
I
kind
of
what
I
said
you
you
were
asking.
Is
there
a
list
of
these
issues?
You
mean
the
issues
that
I
mentioned
in
my
previous
points.
A
A
I
think
similar,
like
we're
talking
about
the
widget
people,
don't
understand
the
impact
that,
like
messing
with
that
button,
has
on
the
merge,
request,
experience
and
don't
treat
it
with
the
priority,
and
so
I
worry
that,
like
even
if
we
socialize
these
issues,
we'll
sort
of
see
what
we
already
see
with
a
lot
of
these
issues,
like
I
know,
of
two
or
three,
since
even
I've
been
here
that
have
like
existed
for
a
year
and
severity
keeps
going
up
and
they
keep
not
getting
scheduled.
A
So
I
wonder
if
like
if
it,
if
it
doesn't
help
to
like
socialize
these,
unless
we've
also
got
this
other,
like
in-state
thing
figured
out
first
and
therefore,
if,
like
you,
should
spend
the
time
on
that
and
like
I
guess
my
my
question
of
that
is
like
you
spending
time
on
that
which
is
like
a
very
extensive
like
project
on
its
own.
A
But
then
I
wouldn't
say
potentially
it
does.
It
absolutely
does
sacrifice
your
ability
to
drive
roadmap
forward
for
a
milestone,
at
least
like
there's
no
question
about
it.
That,
like
you,
cannot
also
be
thinking
about
reviewers
and
like
hand
off
in
this
button
and
like
how
do
you
like,
let's
say
for
13.9,
that's
what
we
do,
because
I
think
like
in
order
to
get
these
issues
done.
Sort
of
this
is
gonna
need
to
be
figured
out.
B
A
B
I
mean
there
are
other
things
to
do,
but
if
I'm
away
so
to
speak,
like
one
or
two
milestones
just
chipping
away
at
this
and
even
doing
solution
validations,
which
we
should,
since
it
would
be
changes
that
we
need
to
make
sure
that
people
understand
what
there
is
no
there's
not
enough
runway
for
engineers
to
work
on
direction
items.
Unfortunately,
so
they
would
yeah.
A
Yeah,
I
don't
know
I,
and
I
also
have
that.
I
know
that
that's
a
true
statement,
but
there
is
not
enough
well
thought
out
work.
I
have
sort
of
two
random
ideas.
One
is,
I
know
there
are
some
like
there's
some
interesting
refactoring
proposals
sitting
around
from
front
end.
I
know
thomas
proposed
just
this
other
day,
like
a
refactoring
to
the
way
we
handle
collapsed
files
to
make
like
that
more
standard
across
the
board.
Justin
has
a
proposal
for.
A
A
The
other
day
phil
is
working
on
like
graphql,
which
is
so
like.
I
feel
like
there's
some
refactoring
work
that
exists,
that,
like
people
want
to
do.
Michelle
has
a
long
list
of
like
performance
stuff.
We've
also
got
a
lot
of
metrics
tracking
so
like.
If
we
were
to
do
it,
you
know
part
of
me
thinks
like
look.
We
just
ship
reviewers,
we
haven't,
we
don't
really
have
a
ton
of
feedback
on
it.
A
Yet
from
like
end
users,
we've
got
some
things
that
we
might
want
to
do
next,
but
like
if
we
were
to
spend
the
next
one
or
two
milestones
today,
working
on
like
refactoring
stuff,
assuming
we
could
get
some
of
this
completed,
which
is
another
big.
If
in
two
or
three
milestones,
when
we're
ready
to
go
back
into
direction,
work
like
you
know,
we
we
wouldn't
have
really
lost
anything,
whereas
I
think
if
we
wait,
maybe
two
more
milestones.
Maybe
we
lose
something,
but
I
don't
know
the
other.
A
The
other
flip
side
to
that
is.
There
are
some
like
things
in
the
mr
reviewer
handoff
that
we,
I
think,
there's
a
general
consensus
that
they're
good
ideas.
They
don't
have
the
most
complete
designs,
like
the
the
request.
Re-Review
button
that,
like
phil,
has
sort
of
partially
implemented
and
people
seem
to
generally
think
andre's
got
like
a
list
sort
of
segment
that,
like
moves
people
up
and
down
in
these,
like
buckets
that
sort
of
say
things
one
of
the
things
we
could
do.
A
You
could
wildly
seed,
mr
review
and
other
things
to
me
for
like
a
month
for
a
milestone
and
trust
that,
like
I
won't,
I
won't
break
anything
that
we
can't
iterate
and
fix
in
the
future,
and
I
can
like
help-
and
we
can
also
sort
of
like
trust,
our
engineers
to
make
some
some
good
decisions
and
we
may
not
catch
everything
but,
like
we
probably
wouldn't
end
up
in
like
oh,
my
god,
we
broke
it
so
bad
because
pedro
wasn't
around
trouble
right.
I
think
that's
a
that
is
also
an
option.
A
Is
that,
like?
I
can
help
take
over
some
of
that
that
immediate
short-term
capacity
for
the
the
couple
small
things
that
we
know
we
want
to
do,
and
not
not
necessarily
the
bigger
things
but
like
so
that
we
don't
sort
of
lose
momentum
across
the
board
and
I
think
that
would
be
challenging
for
all
parties,
but
I
think
I
think
if
we
don't
address
the
merge
button,
it's
going
to
continue
to
be
the
bane
of
our
existence.
It's
I
don't
know.
I
don't
know,
okay
about
that,
either.
B
C
B
So
I
agree
with
that
in
terms
of
delegating
the
image
request,
reviews
to
you,
I'm
I
I
think
if
you're
suggesting
that-
and
I
was
laughing
but
it
was,
it
was
a
good
reaction.
Trust
me:
no,
if
I,
if
what
I
when
I'm
concerned,
is
not
the
quality
of
the
reviews,
it's
your
capacity
being
affected
because
it
takes
a
long
time.
So
I
think
we
can.
We
can
go
with
the
flow,
and
maybe
I
can
pass
on
some
of
the
emergency
requests.
B
Reviews
to
you
like
things
that
are
smaller,
but
the
like
they're,
I
mean
it's,
it's
the
context.
Switching
is
like
changing
branches
setting
it
up.
All
of
that
thing
takes
a
long
time
and
and
again
I
think,
if
you're
suggesting
that
it's
because
you
are
confident
that
you
would.
C
B
B
It's
really
hard
like
we're
talking
about
the
runway
and
engineers
having
things
to
work
on
and
in
the
same
way,
what
I'm
going
to
say
is
similar
to
what
happens.
Also
with
catherine
is
like
the
the
train
has
never
stopped
for
you
to
get
on
it,
you
know.
So
how
can
you
catch
up
with
the
train
and
with
research
is
the
same
thing?
You
research
a
lot
of
things,
but
the
train
keeps
going.
B
Yeah,
I
think
I
think
that
would
be.
I
mean
I
would
love
to
see
one
or
two
release
posts
where
there's
a
lot
of
things
that
are
just
bug,
fixing
and
enhancements
that
we
did
in
code
review
and
we
celebrate
those
and
maybe
even
give
engineers
the
space
for
them
to
pick
what
they
want
to
work
like,
for
example,
phil
is
doing
that
thing
with
the
graphic
ul,
because
he's
clearly
passionate
about
doing
that.
It's
something
that
he
proposed
for
him
to
to
do
himself,
the
same
with
thomas
like
it's.
B
B
And
I
just
I
mean
I
know
we're
way
over
time.
I
just
want
to
quickly
finalize
by
linking
that
to
what
we're
doing
this
milestone.
B
I'm
not
concerned
about
the
request
review
thing:
it's
it's
clearly
like
that
little
button
and
things
that
that
phil
was
already
developing
are
a
way
to
go
there,
I'm
just
going
to
make
one
comment
or
two
there
in
the
merge
request,
but
I
think
it's
something
that
we
should
do.
I'm
a
bit
more
concerned
about
the
like
surfacing
inside
of
the
product,
like
in
the
list
of
merge
requests
and
highlighting
merge
requests
that
you
have
been
re
requested
to
re-review.
B
It's
that's
the
only
thing
that
I
feel
like
we
need
to
do,
or
else
I
mean
we
can
still
do
the
button
and
people
will
get
a
new
notification
and
a
to
do
and
that's
great
and
maybe
even
a
system
note
saying
that
they
were
re-requested,
but
if
they
can't
see
and
if
they
can't
filter
out
the
merge
requests
in
the
product,
it
would
be
at
least
good
to
have
a
plan
of
what
we
need.
A
A
You
know
at
least
the
button
thing,
maybe
some
other
smaller
things
like.
I
think
we
could.
We
could
do
without
too
much
harm.
I
think
you're
right,
the
bigger
one
to
solve
is
the
like,
which
we
talked
about
is
like.
How
do
I
get
to
a
list?
That's
like
mrs.
I
need
to
action
and
what
are
all
the
states
of
that
and
like
yeah,
that
is
a
much
bigger
problem
and
not
something
that
I
would.
A
I
think
we
should
do
without
you,
but
I
think
like
we
could
do
you
know
the
re-review
button
or
potentially
some
of
the
list
stuff
and
like
and
then
maybe
we
do
bring
in
that
other
refactor
work
and,
like
I
think
we
just
maybe
we
do
need
to
take
that
pause,
and
so
I
think
I'd
like
to
like
in
this
discussion
and
say
like
this
is
what
we're
we're
going
to
say.
I
think
we
know
for
the
mr
widget
139
catherine
will
work
on
that'll,
be
like
research
focus
area
for
her
and
we
try.
A
A
You
will
be
present,
but
less
present
and
like
you're
gonna,
go
work
on
merge,
request,
widget
stuff,
because
we
think
that's
the
most
important
thing
to
go,
do
versus
driving
the
road
map
and
it's
and
I
will
deal
with
figuring
out
with
andre
and
michelle
like
what
work
the
engineers
will
do
and
we'll
try
and
figure
out
how
to
help
and
break
the
habit
of
like
pinging
you
for
reviews
and
like
if
they've
got
smaller
stuff
like
ping
me.
A
B
B
B
No!
No!
What
I
was
going
to
say
is
that
I
it
really
needs
to.
We
need
to
reduce
my
involvement
in
things
that
needs
design
and
like
roadmap
things
and
and
even
sometimes
like
issues
that
are
bugs
or
enhancements
or
community
contributions
that
need
design.
That's
what
usually
takes
me
the
most
time
like
doing
like
quick
answers
like
hey.
Have
we
thought
about
doing
this
or
have
we
ever
done
this
in
another
place
in
the
product?
B
And,
and-
and
if
anything
doing
this
is
from
my
end
is
what
I
see
as
the
last
like
looking
at
the
merge
request.
Widget
as
catherine
is
going
to
look
and
me
specifically
looking
at
the
merge
button,
this
work,
at
least
for
me,
it's
what
I'm
missing
see
last
part
remaining
part
for
me
to
have
a
complete
picture
of
the
merch
requests
and
code
review
at
gitlab.
B
That
will
allow
us
to
design
a
better
experience
for
the
whole
merch
requests,
because
I've
been
talking
like
for
months
and
months,
and-
and
maybe
you
haven't
heard
me
that
much
talking
about
this
guy
but
catherine
has
I'm
talking
about
like
the
foundation
and
the
scaffolding
of
the
merge
requests
page
and
it's
not
scaling
it.
B
Has
this
problem
blah
blah
blah,
but
until
we
understand
the
merge
request
widget,
which
today's
known
unknown,
we
can't
solve
the
rest
properly
and
we
need
to
redesign
the
page
as
a
whole
like
that
sidebar,
it's
I
I
kind
of
hate
it.
I
hate
the
merge
requests
widget
with
all
of
the
buttons
always
in
different
locations,
depending
on
in
which
merge
requests.
You
are
the
discussions.
I
hate
them
as
well.
The
threading
model,
the
catching
up.
B
All
of
that
can
only
be
solved
well
and
have
a
good
roadmap
once
we
understand
these
problems,
because
it's
the
only
remaining
parts,
so
it
will
allow
us
to
have
a
better
road
map
in
the
future.
I
believe.
C
A
C
A
C
A
B
All
of
them
are
widgets,
but
I
can
also
understand
that
not
all
of
them
are
widgets
in
the
end
of
the
day,
each
of
those
lines
serves
and
boxes
and
rows
serves
a
different
purpose
and
has
a
different
goal
in
mind,
but
they're
all
designed
as
being
part
of
one
large
component
like
all
of
these
kind
of
work
together
and
visually
they're,
all
similar
and
they're
close
together,
but
maybe
that's
not
the
way
it
has
to
be
in
the
future
and
what
I
think,
what
kai?
B
What
you
are
saying
is
that
what
you
see
as
widgets
is
usually
the
rows
that
pertain
to
how
the
merge
request
changes
are
being
consumed
and
tested
and
checked
somewhere
else.
A
A
I
think
that
is
technically
those
implement,
like
the
mr
widget
api
right
that
exists,
or
that
will
exist
that
phil
is
working
on,
there's
like
and
so
like,
there's
a
technical
like
mr
widget
and
then
there's
like
a
mental
model
of
like
what
do
you
consider
all
of
those
components
of
of
the
mr
and
I
don't
like
approvers-
does
not
use
like
the
mr
widget,
because
it's
obviously
much
more
complex
and
it
was
actually
implemented
by
like
the
source
code
code
review
team.
I
also
think
of
like
the
other
way.
A
I've
I
think
about
it
too,
is
mr
widgets
are
like
an
api
that
other
groups
that
want
to
integrate
with
our
page
sort
of
consume
and
other
things
on
the
page
are
generally
owned
by
us
like
that
that
approver's
box
is,
in
theory
owned
by
like
code
review,
because
that's
the
consumption
of
approval
rules,
so
we
control
that
experience
and
like
we
would
work
on
that.
The
pipeline
box
above
is
was
probably
the
first,
mr
widget.
A
Although
I
don't
know
if
it
consumes
like
the
widget
api
like
like
other
stuff
should
like
it
potentially
maybe
needs
two
at
some
point,
but
but
that
is
how
I
would
think
about
it.
So
it
is
probably
all
those
boxes
but
just
understand
like,
depending
on
who
you
talk
to
there's
a
there's.
A
technical
api
called
the
widget
api
which
doesn't
help
your
situation.
C
This
is
very,
very
interesting:
is
there
a
way
to
see
like
a
list
of
who
would
who
would
be
using
the
mr
widget
api
or
that
whole
thing
versus,
because
I
feel
like
when
I
talk
when
we
when
we
talk
to
designers
and
whatnot
at
gitlab,
the
widget
is
just
all
the
boxes,
but
I
will
look
into
this
more.
This
is
very
interesting.
B
B
I
think
what
we're
trying
to
get
at
is
that
for
the
research,
because
we
own
the
approvals
we
own,
the
the
top
part
that
says,
request
to
merge
source
branch
into
target
branch
checkout
button,
and
we
also
own
in
theory
the
merge
button
area.
All
of
the
widgets
in
between
all
of
the
rows
in
between
is
what
we
would
consider
the
merge
requests,
widgets
that
we
don't
know
very
well
and
what
they're
actually
doing
and
at
which
moment,
they're
consumed
by
users,
if
they're
helpful
or
not.
B
So
it's
basically
the
other
things
from
other
stages.
The
approvals
I'm
I
mean,
there's
a
lot
of
there's
problems
with
it,
but
we're
aware
of
them.
The
checkout
branch
area
at
the
top
also
has
some
problems
and
could
be
improved,
and
the
merge
button
is
what
I'm
going
to
look
into.
So
I
would
focus
research
on
those
in
the
middle,
but
I
mean,
as
you
said,
the
mental
model
is
everything.
B
So
it's
more
than
okay
and
expected
that
throughout
the
research
participants
bring
up
the
other
parts
of
the
of
that
area
and
that
everything
is
connected
at
the
end.
So
in
the
same
way
like
I'm
going
to
focus
on
the
merge
button,
but
to
focus
on
the
merge
button,
I
have
to
look
at
everything,
so
it
will
be
a
continuous
macro
micro
thing
zooming
in
zooming
out
exercise.
C
B
Cool
okay,
I
really
have
to
go,
but
can
we
talk
about
the
data
sync
next
time.
A
Yeah,
I
think
I'll
I'll
give
you
like.
The
30
second
highlight,
which
is,
I
told
you
before,
that
we
thought
there
was
like
a
50
drop
off
between
scm
and
code
review,
looking
at
paid
usage
of
instances
with
more
than
10
users.
That
number
is
higher,
it's
like
in
the
mid
to
low
70s,
so
the
drop-off
is
less
severe
when
you
get
paid
instances
that
have
teams
of
like
a
reasonable
size
which
we
defined
as
like
10
or
more
so
it's
less
concerning.
A
Okay,
you
can
look
at
the
data
issue
and
it
links
to
like
a
dashboard
that
matthew's
put
together.
That's
got
those
charts
that
we've
been
talking
about
in
there.
If
you
want
async
is
fine.
Okay,.