►
From YouTube: 2021-02-09 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
Yeah,
the
the
first
point:
it's
just
fyi.
I
don't
think
it's
required
to
read,
but
we
could
expect
amy
to
be
joining
the
next
calls
because
of
a
transition
that
is
happening
or
a
bigger
restructure
in
the
technical
writing
team.
I'm
I
don't.
I
don't
have
a
lot
of
information
about
that,
but
yeah
you
can
check
that
issue.
If
you,
if
you're
interested.
B
Last
time
that
we
talked
about
this,
katherine
were
you,
I
was
okay,
okay,
yeah,
so
you're
already
aware
of
what
this
is
and
kai
was
going
to
follow
up
with
a
noob
to
understand
if
everything
is
is
okay
and
if
it's
really
something
that's
moving
on
and
everyone's
aware
or
not
so,
okay,.
A
Yeah,
I
I
had
asked
any
to
follow
up
and
he
and
I
have
spoken
since
then
he
still
hasn't
followed
up,
but
I
think
the
impression
I
got
was
that,
like
this
was
the
change
and
in
order
to
convey
the
intent
like
that's
why
it
was
done.
I
think,
there's
things
that
need
to
be
addressed,
but
largely
the
other
groups
that
are
the
other
groups
that
are
significantly
impacted,
ci
right,
like
they're,
the
ones
that
are
probably
most
impacted
by
this
change,
and
then
us,
I
guess,
but
I
think
people
are
aware.
A
I
don't
I
don't
know
what
it'll
change
for
us.
I
have
seen
I've
seen
some
like
issues
get
triaged
and
like
it's
just
sort
of
automatically
because
of
this
like
someone's
like,
oh
well,
it
has
to
be
an
s2
now
and
I'm
not
I'm
not
quite
sure,
that's
the
intent
we
wanted.
So
I
don't
know,
I
think,
we'll
just
see
see
how
it
goes,
but
I
would
say
we
treat
it
as
it's
there
and
then
sort
of
make
some
judgments.
B
Yeah,
do
you
think
it's
it
would
be
worth
bringing
it
up
in
the
in
one
of
the
products
communication
channels,
so
not
necessarily
in
slack,
but
what
I
don't
know,
what
do
you
think.
A
B
Yeah,
I
just
want
to
make
sure
that
we're
not
the
only
I
mean
the
only
group.
That
is
aware.
I
know
that
other
product
managers
were
commenting
in
the
merge
requests,
but
this
I
mean
this
is
important.
It's
going
to
be
automated
someday,
not
sure
when.
A
A
Particularly
we
liked
the
way
our
automation
works,
like
I
think
the
goal
was
really
that,
like
the
merge
button,
like
things
that
impact
sort
of
like
that
are
very
serious,
like
the
ability
to
like
get
your
changes
merged,
I
think
was
sort
of
where
we
were
coming
from,
and
it's
now
like
got
this
all-encompassing,
like
everything
on
the
merch
request.
Page
is
that
which
is
not?
A
B
All
right,
okay,
so
I
have
the
next
point
about
the
review
process.
Problems
and
we've
had
37
finished
responses,
and
I
say
finished
here
because
I
think
three
of
them
are
three
or
more
of
them
are
not
completed.
So
it's
people
that
have
left
halfway
or
something
like
that
and
out
of
the
finished
responses.
34
are
for
people
that
identify
themselves
as
engineers.
B
B
B
Yeah,
what
what
do
you
think
should
we
keep
this
open.
B
A
C
A
B
C
Oh,
I
mean
it,
it
depends
it
depends.
I
think
it
would
be
nice
to
get
up
to
around
50.
I'd
actually
also
say
it
depends
on
what
the
rankings
are
looking
like.
If
there
are
patterns
starting
to
come
out
from
it,
if
they're
kind
of
still
all
over
the
place
and
there's
not
really
a
cohesive
thing
there,
then
you
would
want
to
keep
collecting
more
until
you're,
starting
to
see
a
clear
trend
that
you
can
actually
draw.
Some
conclusion
from,
I
think
that's
another
part
of
it
if
you're
starting.
A
B
B
B
No,
I
think
it's
only.
The
only
question
that
has
personal
details
is
the
email
address,
and
I
I
can
hide
that
yeah
I
already
I
do
so
yeah
I
can
share
my
screen.
Give
me
a
second.
B
All
right,
so,
okay,
so
this
is
the
first
question.
This
is
the
role
question.
What
is
the
job
title
and
then
okay
rank
these
problems
with
merge
requests
in
order
of
severity,
one
being
the
most
impactful?
So
this
is
the
amount
of
times
that
someone
placed
these
problems
as
the
top
problem.
We
can
see
that
this
purple,
one
which
is.
C
B
A
Anyone
I
have
a
question
like
I
I
don't
know
if
this
is
like
okay
to
do,
can
we
modify
the
survey
if
we're
gonna,
send
it
out
again
and
add
an
additional
question.
I
think
I
asked
about
this
in
slack
but
or
the
issue.
A
Has
such
like
a
focus
on
small,
merge,
requests
and
like
that
is
the
thing
that
we
champion
and
say
that
we're
great
as
a
development
org,
and
yet
many
of
these
people
are
saying
like
they
have
struggles
dealing
with
larger
mars,
and
so
what
I
want
to
know-
and
I
don't
know
if
this
like-
complicates
the
survey
or
baits
it.
But
I
want
to
know
what
people
are
defining
as
a
large.
Mr,
I
don't
know
how
to
like
ask
that,
but.
C
C
A
C
So
I
guess
I
would
say
to
minimize
any
impact
to
this
existing
survey.
I
would
put
the
question
after
the
ranking
just
so
that
everyone
had
seen
the
same
things
up
until
the
ranking,
and
then
I
guess
whatever
happens
afterwards
is
fine
and
you
can
go
with
a
open
text
or
you
could
do
a
multiple
choice
that
has
like
a
defined
range
of.
I
don't
know,
changes
or
something
like
that,
and
then
they
could
just
select
that.
B
C
Might
be
an
option
but
and
then
like
another,
if
they
have
something
else
to
say
about
it
but
yeah.
I
think
I
guess
to
keep
things
relatively
the
same.
I
would
add
a
question
like
that
after
the
ranking,
and
it
would
make
sense
since
they
had
already
seen
dealing
with
large,
mrs
as
an
option,
then
it's
like
okay.
Well,
what's
an
a
large
mr
to
you
something
like
that.
B
Yeah,
so
I
I
think
yeah,
I
think
it's
fine.
If
we,
if
we
add
another
question,
although
I
don't
know
if
one
question
like
how
do
you,
what?
How
do
you
classify
something
as
being
a
legend,
I
don't
think
it
might
be
enough,
because
okay,
we've
narrowed
down
the
definition
and
maybe
a
lot
of
people
think
it's
a
lot
of
files
or
maybe
a
lot
of
people
think
it's
just
scope.
B
That
is
very
big
or
maybe
a
lot
of
people
think
that
it's
no
it's
just
one
file,
or
usually
it's
just
with
a
lot
of
different
lines
that
can
change,
or
maybe
it's
a
lot
of
commits.
So
maybe
we
can
hone
down
hone
in
on
what
exactly
is
the
definition
for
each
person,
but
we
would
still
need
to
do
more
research
right
to
understand
how
how
people
get
to
that
state
and
especially
at
gitlab
like
yurasenkai.
B
C
A
Yeah-
and
I
don't
I
don't
necessarily
think
I
want
to
know
the
why
yet
I
want
to
know,
I
want
to
be
able
to
like
understand
what
people
are
talking
about
just
to
make
like.
We
need
a
shared
definition
of
large,
mr
and
I
don't.
I
guess
we
don't
have
a
shared
definition
as
sort
of
what
I
want.
What
I'm
hoping
like
a
question
gives
us
is
like
the
ability
to
to
then
say:
okay,
this
is
what
people
think
is
a
lot.
A
This
is
like
what
people
think
is
a
large
amar,
and
maybe
that
is
significantly
smaller
than
what
we
think
of
as
large,
mrs
today
and
sort
of
like
that
whole
performance,
workflow
and
like
how
you
deal
with
those
files
and
like
we
need
to
refocus
back
down
to
like
maybe
it
is
like
five
files
and
a
hundred
line
changes.
People
consider
to
be
a
large,
mr
and
like
we
need
better
tooling
for
that
right,
that's
a
very
different
problem
than
then.
A
If
everyone
comes
back
and
says,
oh,
a
large,
mr,
is
20
files
and
2
000
line
changes
right,
like
I
think,
we'd,
say
yeah.
That
is
and
like
we
don't
have
a
good
answer
for
that
other
than
like.
You
should
probably
have
a
smaller,
mr,
but
if
it's
something
that
we
think
is
like
small
and
they're
that
they
think
it
is
large
and
hard
to
deal
with
then
like,
I
think,
that's
sort
of
what
I
want
to
know.
A
C
Okay,
that
makes
sense
to
me
yeah.
It
seems
like
okay,
just
get
the
information
on
what
is
a
large
amr
and
see
how
common
the
problem
is,
and
then
you
could
follow
up
afterwards
if
to
go
deeper
into
why
it's
challenging
working
with
that
largemour.
How
you
even
got
to
the
point
of
having
that
largemouth.
That
makes
sense.
A
A
That
structuring
it
in
a
way
where
you
say
lots
of
files
or
change
lines
or
lots
of
commits
or
a
large
scope
or
any
combination
of
those
things,
is
like
not
going
to
be
what
someone
thinks
in
their
head
right
like.
C
A
C
C
A
B
B
Right,
okay
sounds
good
to
me:
yeah
yeah,
I'll
I'll,
put
it
as
an
optional
question
because,
like
some
people
might
not
know
how
to
answer
that,
like,
for
example,
I
I
mean
I
could.
I
could
say
what
a
large
mr
is
to
me.
But
I
when
I
I
actually
responded
to
the
survey,
because
I
I
mean,
if
we're
doing
this
internally,
I
think
we
should
also
be
open
to
answering
it,
and,
but
I
placed
I
think,
almost
at
the
bottom,
dealing
with
a
large
amount,
because.
C
B
Not
something
that
impacts
my
efficiency
in
the
reviews
that
I
do
right
so
for
me
defining
what
the
large
mr
is.
B
I
don't
know
where
I
would
start
you
know,
so
it's
not
something
that
is
top
of
mind
for
me,
but
I
would
imagine,
like
the
people
that
have
placed
it
at
the
top,
would
know
immediately
what
their
response
would
be
to
what
a
largemouth
is.
You
know.
A
B
I
think
easier
way,
although
I
completely
understand
what
you're
saying
and
that's
what
makes
most
sense.
I
think
when
you're
prioritizing
the
responses
is
to
look
first
at
the
people
that
have
ranked
the
problem
higher.
But
if
we
keep
the
question
optional,
we
can
still
filter
by
the
responses.
So
we
can
say
I
only
want
to
see
the
people
have
placed
at
the
top
five
of
dealing
with
rj
mars,
and
then
we
look
at
their
responses.
So
we
can.
We
can
also
do
that
with
with.
A
B
All
right,
okay,
so
let's
do
that
I'll
reach
out
to
andre
and
michelle
to
see
how
what
they
think
could
be
good
ideas
to
get
more
responses
and
I'll
wait
for
their
response.
B
I
mean
the
last
as
a
last
resort.
We
can
just
do
another
round
of
pushing
out
the
message
via
the
engineering
we
clean
review,
the
back
end
and
front
engine.
I
didn't
publish
it
in
the
what's
happening
at
gitlab,
because
I
I'm
really,
I
really
hate
spam
and
I,
and
sometimes
even
like
the
messages
that
people
put
there.
They
they
don't
mean
anything
to
me.
So
it's
not
what's
happening
at
gitlab.
It's
what's
happening
in
your
department
or
something
like
that.
So
I'm
really
wary
of
putting
something
there.
C
C
A
There's
two
there's
development
and
there's
evpe
like
eric
johnson,
has
a
channel
right.
The
evpe
channel
that
you
could
use,
which
also
like,
does
not
get
a
lot
of
like
posts
in
it
right
like
it's,
a
very
low
traffic
channel
but
high
visibility
channel.
So
it
might
be
like
a
good
way
to
like
amplify
that
and
in
theory.
A
Probably
worth
tagging
eric
and
like
christopher
in
that
post
and
just
be
like,
we
need
your
support
to
like
push
this
out,
like,
I
don't
think,
there's
an
issue
with
like
even
attacking.
B
Yeah
yeah,
exactly
that's
what
I
was
thinking
yeah.
I
was
just
concerned
about
just
going
there
and
out
of
the
blue,
like
as
a
bloodsucker
just
using
their
channel
to
put
out
my
message.
You
know
so
yeah
a
lot
of
people
on
this
channel.
I
don't
never
post
here,
it's
your
channel,
but
I'm
gonna
use
it
but
yeah.
So
I
I
think
yeah
reaching
out
to
to
eric
to
amplify.
The
message
is
a
great
idea.
B
C
C
B
C
B
B
That
that's
exactly
right
and
if
someone
answers
never
to
both
the
the
survey
and
scene.
C
B
A
Sort
of
like
merge,
request
dependencies
and
auto
retargeting
branches.
I
just
like
your
your
product
hat
thoughts
on
it
and
how
it
fits
into
sort
of
that.