►
From YouTube: 2021-10-12 Code Review 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).
B
So
first
I
might
have,
is
now
I'm
trying
to
get
more
clarification.
I
I
believe,
based
on
conversations,
I've
had
the
back
end
will
be
re-entering
the
engineering
allocation
at
100,
although
based
on
the
emrs
that
are
open
and
some
of
the
comments,
it's
not
entirely
clear.
B
If
that
should
be
true,
I
guess
for
now
I'm
going
to
work
on
the
assumption
that
it
is
true,
and
so
with
that
in
mind,
like
I
know,
we're
we're
doing
a
lot
of
research
about
things
that
we
want
to
do,
but
we
also
have
a
backlog
of
things
that
we've
wanted
to
do
for
quite
a
while
and
haven't
been
able
to
get
to,
and
so
are
there
other
things
that
might
be
smaller
or
different
areas
of
research
that
maybe
we
didn't
prioritize?
B
We
thought
we
would
get
back
in
engineers
back
that
we
want
to
go
look
at
sooner.
That
might
be
front
and
only
efforts-
and
one
of
those
like
a
good
example-
was
the
merge
the
merge
button
widget
the
merge
widget.
I
think
I
don't
merge
button,
which
is
the
one
I'm
going
to
go
with,
but
because
that
was
like
frontend
only
to
sort
of
re-do
the
work
based
on
pedro's
designs,
new,
updated
designs
there,
and
that
was
all
front-end.
Only
workers
weren't
changing
functionality
or
doing
anything.
B
A
Yeah,
I
added
a
link
there
to
something
which
is
to
improve
the
hidden
difference
in
merge
requests,
and
it's
not
very
impactful,
but
it
is
front-end
only
work.
I
believe,
and
we
improved
the
design
for
diffs
that
are
hidden
or
auto
collapsed,
but
only
certain
types
there
are
others
we
which
we
haven't
improved
yet
and
the
designs
are
ready.
A
A
So
yeah
design
for
consistent,
commenting
states
that
annabelle
was
starting
to
work
on
in
the
last
milestone,
but
that
we
the
prioritized-
and
it
should
be,
I
believe,
fairly
quick-
to
get
a
design
ready
and
have
front-end
work
on
that.
But
again
it's
not
very
impactful.
A
I
think
all
of
the
impactful
things
are
yet
to
be
designed
and
validated,
and
we
today
we
also
discussed
in
the
prioritization
session.
We
discussed
the
merge
requests
that
need
my
attention,
but
I
was
under
the
impression
that
we
wouldn't
be
able
to
achieve
everything
of
that
epic
just
with
fontaine,
so
so
yeah.
B
Okay,
are
there
other
areas?
I
know
we
talked
about,
which
I
think
is
ongoing.
Research
like
something
had
done,
the
like
the
top
bar
and
sort
of
the
the
nav
all
being
contained
moving
controls
up
there.
I
think
annika's
working
on
some
of
that
now.
A
Yeah,
I'm
working
on
that,
because
the
work
that
I
was
doing
for
this
quarters
okr
in
the
ux
department,
which
was
related
to
improving,
merge
requests,
reviews
by
designers
that
took
longer
than
what
I
was
expecting,
and
so
I
haven't
had
the
time
to
sit
down
and
work
on
that
and
and
yeah.
C
C
I
don't
know
if
this
really
falls
in
line
with
what
you're
thinking
or
if
it
should
have
been
an
issue
for
like
the
prioritization
prioritization
session,
but
what
you
just
commented
on
kai,
why
we
don't
have
the
sidebar
on
the
merge
request,
creation
page.
That
would
be
a
really
quick
mock-up.
C
C
Just
linked
to
it,
sorry,
when
I
was
going
through
the
other
products
that
you
suggested
for
viewers
most
of
them,
when
I
was
looking
at
the
like
pull
request,
merge,
request
creation
page,
you
add
the
suggest
you
add
the
reviewers
and
all
of
the
metadata
in
the
sidebar,
just
like
we
do,
but
for
some
reason
we
don't
have
the
sidebar
on
the
creation
page.
A
Yeah
yeah,
I
think
it's
it's
worth
creating
an
issue
for
that
and
also
involving
and
sharing
that
with
holly
the
product
designer
from
project
management,
because
they
are
thinking
about
a
new
create
and
edit
ui
for
issues
that
they're
experimenting
under
the
the
term
work
item
and-
and
it's
a
very
it's
very
different-
at
least
visually.
It's
a
visual,
different
visual
experience
and
we
don't
have
to
do
what
they
do.
Actually,
let
me
see
if
I
can
share
that.
A
So
let
me
get
to
the
desktop
experience
so
yeah,
so
this
would
be
the
creation,
the
create
work
item,
ui
and,
as
you
can
see,
it's
very
bare
bones
and
it's
it
will
be
the
same
as
editing
in
line.
So
this
is
already
created,
and
this
is
when
you're
creating
and
then
you
can
add
assignees
there
and
then
the
metadata
for
assignees
is
here
instead
of
being
in
a
sidebar.
A
It's
a
different
thing
that
they're
experimenting
with,
and
we
again
we
don't
have
to
do
what
they
do
because
merge
request
is
a
different
object,
but
we
should,
you
know,
see
if
we
can
learn
anything
from
this.
A
I
believe
it
will
replace
issues
in
the
end
it
it
will
allow
you
I
think,
to
have.
C
So,
historically,
merge
requests
and
issues
have
looked
almost
exactly
the
same
to
where
you
have
to
look
at
the
url
a
lot
of
the
time
to
figure
out
what
it
is
were
I
don't
have
well.
I
don't
really
like
that.
I
never
really
have,
but
is
that
something
that
we
are
cool
with
doing
then
like
at
this
big
split
in
between
them,
so
that
they
look
very
different.
A
Yeah,
I
we're
not
sure
yet.
I
asked
holly
to
keep
us
posted
want.
They
find
they
still
have
to
validate
it
and
understand
if
it's
something
better
than
what
they
have
today,
and
we
will
learn
from
that
as
well
and
see
if
it's
something
that
we
will
apply
to
merge,
requests
or
not
yeah,
I
think
those
are.
They
are
different.
A
Yeah,
I'm
more
concerned
about
the
work
that
you've
been
doing.
Concern
in
terms
of
you
know,
curiosity
and
how
much
impact
it
could
create.
I
think
that's
that's
where
we
need
to
put
our
money
on
is
just
the
navigation
in
general
and,
for
example,
if
what
kai
shared
some
some
calls
ago
of
not
having
any
tabs,
for
example,
or
not
showing
the
sidebar
at
all
times
and
just
showing
on
one
tab
or
having
the
metadata
in
a
different
location.
A
That
said,
I
would
love
for
us
to
move
to
a
you
know,
a
seamless
experience
where
you
go
into
the
creation
mode
of
emerging
quests
and
you
can't
easily
say
if
it's
already
created
or
not
in
a
way
that
you
know
it's
a
seamless
transition
and
it's
created
and
wow.
It's
just
no
page
reloads.
No
anything,
it's
just
a
beautiful
experience,
but
I
don't
think
we're
there
yet.
B
I
also
agree
that
we
should
talk
to
plan
and
I
didn't
know
about
work
items,
but
I
was
just
those
screens
have
historically
looked
the
same
and
I
don't
I
don't
know
why,
but
they
have-
and
I
don't
have
strong
opinions
on
why
the
other,
if
they
should
look
the
same
or
look
different
so
I'd,
be
I'd,
probably
be
more
hesitant
to
experiment
there
and,
like
add
our,
I
have
the
sidebar
there
when,
like
you,
go
to
an
issue
and
then
the
sidebar
is
not
there,
I
think
that
experience
is
sort
of
disjointed
would
be
like
different
and
disjointed
for
people,
because
then
issue
creation
has
sort
of
very
similar.
B
I
think
fields
down
below.
So
I
think
it's
worth
having
the
conversation
and
talking
to
plan.
I
think
this,
that's
one
of
those
ones,
that'll
be
harder
right
now.
If
they
go
down
a
path,
though
that's
totally
different,
that
might
give
us
more
freedom
there.
I
just
I
don't.
I
don't
know
yet
sort
of
where
I'm
at
yeah
I
mean.
If
we
have
cycles,
though,
and
plan
seems
supportive,
then
it's
certainly
something
that
we
could
do.
I
guess
would
be
also
also
possible.
A
Are
those
examples
that
I
shared
in
the
beginning?
Is
that
something
is
it?
Was
this
something
like
this,
that
you
were
looking
for
or
more
impactful
things.
B
I
think
these
are
good,
I
think
the
hidden
disc
one
is
interesting,
because
that
work
is
like
ready
to
go.
I
wasn't,
I
guess,
expecting
us
to
have
necessarily
ready
to
go
work
for
engineering
that
was
sort
of
fun,
and
only
it's
good
that
we
do
because
that
means
we
should
look
at
pulling
that
in
is
sort
of
similar
like
if
we
spend
some
time
and
have
that
ready,
then
that's
probably
a
good
to
have
in
our
ready
to
go
backlog
because
it
it
is
easy.
B
So
maybe
we
should
spend
the
time
on
there.
I
was
wondering
I'll
say
these
are
different
from
what
I
was
thinking
of.
I
was
wondering
if
there
were
like
bigger
things
that
we
didn't
research,
because
we
were
spending
the
time
researching.
B
But
given
that
like,
if
we
do
all
that
work,
we'll
still
be
behind
on
work,
that
we
thought
we
would
have
done
by
the
time
that
research
was
done
right,
like
just
in
that
that
work
might
sit
on
the
shelf
for
several
months
after
it's
completed,
and
so
I
was
wondering
if
there
was
something
that,
instead
of
having
that
work,
sit
on
the
shelf
for
several
months,
was
there
something
else
that
we
could
spend
time
researching
now
that
we
thought
we
would
be
able
to
then
come
back
with
and
then
have
implemented.
B
B
A
Have
an
idea
figure
out
what
else
we
can
do
to
improve
performance
in
the
front
end
that
can
always
fill
performance.
Sorry
front-end
capacity,
even
if
it's
just
spikes
and
everything
yeah.
B
Yeah
and
that's
also
a
possibility
too
so
yeah,
I
think,
there's
such
things
I
was.
This
is
good.
This
gives
us
more
to
put
out
there
and
see
what
we
can
do.
Then
we
need
to
see
how
the
view
the
front
end
decides
you're
going
to
take
on
view
two
to
view
three.
We
want
to
see
what
the
impact
of
their
the
capacity
is
on
that
as
well.
B
A
B
A
Well,
so
so
we're
going
we're
looking
just
make
sure
I
heard
right
so
we're
looking
to
upgrade
to
the
latest
version
of
vue
is
that.
B
Yeah
front
end
has
been
discussing
it
and
it
got
re
sort
of
put
on
the
list
as
part
of
that
other
issue
front
end
opened
an
issue
of
like
what
are
sort
of
if
all
of
the
back
end
across
the
dev
section
was
in
allocations.
B
What
could
the
front
end
go
and
do
as
a
section
like
if
you
took
front-end
capacity
across
the
whole
organization,
like
what
are
sort
of
front-end
things
that
all
the
engineers
could
do,
because
it's
not
just
our
group,
that's
struggling
trying
to
find
not
that
we're
necessarily
struggling
but
like
trying
to
fill
capacity
for
front
end.
There
are
many
groups
that
have
been
in
allocations
for
several
months
that
are
continuing
to
sort
of
like
hit
this
wall,
where
suddenly
they
have
no
more
fun
and
only
work.
That's
super
meaningful.
B
They
might
have
fun
and
only
work
that
they
could
do.
But
like
is
there
something
that
front
end
across
the
entire
section
that
we
could
go
and
do
that
we
normally
you
know
that
we
might
be
more
hesitant
to
do
and
view
two
to
view.
Three
is
one
of
those
that
there
is
on
this
long
list
I'll
actually
share
this
issue.
A
Another
thing
would
be
pajamas
migrations,
so
if
there
are
other
things
that
we
can
do
to
integrate
pajamas
in
code
review
form
fields,
I
think
buttons
are
all
covered,
but
I
don't
know
yeah.
B
That's
on
their
list,
so
migrate.
Handle
components
to
pajamas
is
on
the
list.
Removing
jquery's
on
the
list.
Yeah
those
those.
A
B
Migrations
from
and
view
migrations
are
on
the
list,
so
it's
like
sort
of
bigger
things
or
things
that
help
standardize
us.
There
are
also
things
that
they're
looking
at
and
so
weighing
those
against
what
our
group
might
have
as
group
specific
things
is
something
we'll
have
to
like,
potentially
do
where
we
say
well,
yeah.
We
think
it's
better
if
our
engineers
just
work
on
one
of
these
larger
sort
of
get.
Why
get
lab
wide
projects
versus
our
efforts.
A
Yeah
yeah
anything
that
you'd
like
to
discuss
more
about
this.
This
topic.
B
No
not
right
now,
I
think
I'm
good.
I
think
I
appreciate
the
ideas
that
you
had
and
if
either
of
you
have
more
ideas
or
more
thoughts,
I'd
say
keep
it
in
mind.
I
know
we're
short
up
on
time
against
fourteen
five,
but
I
would
expect
that
we
will
be
in
this
position
for
fourteen
six
14
7,
probably
as
well
without
back-end
engineers,
just
based
on
the
size
of
the
backlogs
that
are
that
exist.
So.
A
Yeah
yeah,
it
is,
I
just
added
a
point
about.
A
A
B
B
B
A
Strictly
ux
work
we
are
discussing
in
the
main
issue
of
create
q4
okrs,
the
possibility
of
code
review
and
source
code
collaborating
more
closely
on
the
framework
for
source
code
rules
and-
and
today
I
chatted
with
marcel
about
the
idea
of
piggybacking
on
the
work
that
annabelle
is
doing
of
looking
at
the
user
flow
in
code
review,
specifically
the
author
and
reviewer
roles
and
the
whole
point
of
that
would
be
ideally
to
create
a
user
journey
map.
A
Yeah,
so
that
we
can
have
a
more
detailed
view
of
the
cross
group
moments
that
we
can
enhance
and
make
more
lovable
yeah
and
just
have
a
better
shared
sense
of
of
everything,
because
today
I
was
looking
at
the
create
direction
page
and
there's
not
a
single
direction.
Item
or-
or
you
know-
or
maybe
I
I
didn't
interpret
it
correctly,
but
I
couldn't
find
anything
that
talked
about
cross
group
work.
It
was
every
much
everything
was
related
to
hey.
A
A
Because
that's
what
we've
been
hearing
over
and
over
again,
you
know
one
platform
stage,
adoption
people
start
and
and
with
create
and
then
adopt
verify
and
then
the
other
stages,
but
we
don't
have
a
good
sense
of
how
all
of
that
ties
together.
So
that's
an
idea
that
that
came
up
today
and
I'm
going
to
create
an
issue
for
it.
I
I
didn't
share
that
with
you
before
yeah,
because
it
just
came
up
today.
B
B
Unlike
most
other
stages,
we're
not
related,
we
just
happen
to
be
a
collection
of
things
that
very
exist
and
create
for
reasons
that
organizationally
made
sense.
They
all
sort
of
relate
to
source
code,
but
but,
unlike
most
stages,
we
don't
actually
overlap
inside
of
groups
like
plan
is
very
interrelated
like
issues
and
ethics,
they're
sort
of
the
same
thing,
and
they
talk
to
each
other
and
do
those
things,
whereas
our
groups
are
are
less
like
that.
B
So
I
I'd
be
curious,
yet
to
see
see
what
that
work
is
and
how
that
comes
out,
and
I'm
happy
to
help
support
in
any
way
that
you
need
support
there.
So
I
think
that
makes
sense.
I
think
that
is
something
that
sarah's
been
asking
as
a
stage
like.
B
A
Yeah
and
that's
that's
what
I
wanted
to
share
anyway.
I
really
hope
that
we
can
dedicate
some
time
to
or
keep
working
on
performance,
even
if
it's,
if
it's.
A
Painful
but
yeah,
I
don't
know,
let's
see
cool.
A
A
B
Okay,
cool,
I
think
the
last
one's
a
read
only
so
I'm
excited
to
see
what
you've
discovered
and
what
you,
what
you
come
back
with
tomorrow,
the
suspense.