►
From YouTube: 2022-05-17 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
All
right
yeah,
so
I
was
I'm
still
kind
of
catching
up
on
everything.
I
think
I
I'm
caught
up
on
the
most
important
things
and
one
of
the
big
things
that
was
discussed
at
length
and
we
had
some
research
work
done
on.
It
was
the
attention
request
and
yeah.
I
read
through
a
little
bit
of
the
the
issues,
not
all
of
them
in
detail,
but
I
just
wanted
to
hear
from
you
well
in
this
case
from
everyone
on
the
call
and
also
amy
hello
and
yeah,
but
perspective
a
summary.
B
So
we
don't
talk
at
length
about
this,
but
your
perspective
on
things
and
what
do
you
think
could
be
the
next
the
best
way
forward
with
what
we
know
today
and
caillou
added
a
few
there
ben?
I
would
also
like
to
hear
your
thoughts
specifically.
A
Yeah
I
just
I,
I
tried
to
leave
it
objective
as
best
as
possible,
so
I
think
you
were
still
here
when
it
got
disabled
due
to
the
production
incident
and
we.
A
On
some
other
stuff,
we
did
some
additional
research
trying
to
test
other
designs
and
other
sort
of
questions
and
tried
to
address
sort
of
concerns
that
were
expressed
in
the
feedback
issue
in
other
places,
and
then
we've
gotten
through
the
work
that
we
had
agreed
to
get
through
in
terms
of
the
updates
to
the
the
way
we
handled
the
automatic
assignment
and
the
additional
like
toast
notifications
that
came
along
with
that
patrick
also
got
through
the
work
for
some
of
the
header.
A
Caching
inconsistencies
that
we
saw
with
the
count
and
that
that
not
being
properly
reflected,
we
made
a
few
other
changes,
and
then
we
turned
it
back
on
we.
I
turned
it
back
on
for
the
giddily
group
in
an
effort
to
sort
of
get
more
real-world
feedback
by
assigning
it
to
a
group.
So
they've
had
it
for.
A
About
a
week
now,
maybe
not
even
quite
a
week
but
close
to
a
week-
it's
been
back
on
for
them,
so
they're
continuing
to
pilot
it
and
then
there's
another
customer
at
least
one
two
potentially
that
have
reached
out
and
asked
for
it
to
be
turned
back
on.
So
there
are
options
outside
of
gitlab
internal
to
to
sort
of
turn
the
feature
back
on
for
people
to
to
test
and
continue
using
it.
B
Okay
thanks
and
what
do
you
think
from
your
perspective,
do
you
have.
B
Yeah,
what
are
we
waiting
for?
Basically,
if,
if
there
are
are,
are
there
any
concerns
that
you
think
we
should
iron
out
or
is
it
just
a
matter
of
time
until
we,
you
know,
get
some
feedback
from
giddily
team
and
and
enable
it.
A
I
do
not
believe
that
that
is
a
widely
held
opinion
amongst
people
who
have
participated
in
conversations
about
the
feature,
and
so
I'd
be
open
to
turning
it
back
on
for
everyone.
A
I
think
in
an
essence,
in
in
a
in
the
spirit
of
trying
to
make
sure
we've
handled
everything
that
we
could
possibly
think
we
need
to
handle
before.
Turning
this
over
to
a
broad
group
of
users,
spending
some
more
time
with
the
kiddily
group
and
potentially
one
to
two
other
customers
gives
us
a
way
to
sort
of
get
real
feedback
from
teams
about.
A
What's
working
well,
what's
not
working
well
and
what's
confusing
because,
as
as
we
both
know
that
changes
to
code
review
workflows
are
disruptive
and
complicated
for
people,
and
so
we
want
to
make
sure
that
we're
not
rolling
out
something.
That's
like.
I
want
to
make
sure
that
we've
adequately.
I
think
for
me
that
we've
adequately
covered
off
on
sort
of
concerns
out
of
ux
and
ux
research
and
other
places
that
that
there's
not
something
that
we're
just
glaringly
missing
or
that
is
totally
broken.
B
Okay
ben:
what
are
your
thoughts.
C
I
don't
think
that
what
we're
doing
right
now
is
the
worst
course
of
action.
I
actually.
I
think
this
is
totally
a
valid
way
to
go.
I
think
I
also
wasn't
privy
to
you
know
a
lot
of
the
sort
of
background
and
impetus
for
this
effort
to
begin
with,
so
I
I'm
sure
that
I'm
missing
some
nuances
here,
but
you
know
doing
the
the
research
and
re-looking
at
the
solution.
Validation
definitely
uncovered
a
few
things
that
that
seemed
to
be
problematic
and
been
doing.
You
know
another
round
of
research
uncovered
a
few
things.
C
I
believe
that,
like
the
larger
issue
is
actually
with
our
entire
notification
system
and
that
the
existence
of
attention
requests
is
actually
like
an
effective
band-aid
on
a
much
larger
problem
like
you,
shouldn't
have
to
get
a
to
do
notification
and
an
email
and
to
do
when
somebody
like
adds
an
attention
request
for
you.
That's
like
just
a
broken
thing.
C
And
so
I
think
you
know
we're
getting
to
a
place
where
attention
requests
as
a
band-aid
is
looking
pretty
good.
I
think
there's
like
some
unresolved
stuff
that
I
think
is
probably
unlikely
to
get
fixed
anytime
soon.
That
has
to
deal
with
how
we
handle
notifications
as
a
product.
C
So
yeah
I
mean
not
sure
what
to
do
about
that,
but
we
did
get
some
like
sus
comments.
Actually
about
that
attention
requests
were
helpful.
C
I've
swung
my
swung
more
towards
towards
kai's
point
of
view
than
I
used
to
be.
It
does
seem
to
actually
be
be
serving
a
real
need
for
our
customers,
and
so
I
think
there
are
far
worse
choices
than
to
just
turn
it
back
on,
but
at
some
point
in
the
future
I
think
we're
going
to
have
to
reconcile
the
fact
that
we're
not
doing
notifications
in
a
great
way
and
there's
room
for
improvement.
There.
B
Okay,
yeah
thanks
ben
at
this
point,
I'm
I'm
just
trying
to
hear
people
out
because
I
was
a
month
away
and
even
though
I
was
here
from
the
beginning
and
sketching
out
what
this
could
be,
I
want
to
hear
everyone
out
before
I
I
give
my
opinion.
I
want
to
reflect
on
everything
that
has
happened
so
so
thank
you
for
that.
I
was
I'm.
B
I'm
surprised
that
we
got
positive
feedback
about
it
in
in
in
the
sus.
Is
that
what
you
said.
A
C
A
B
Okay,
that's
cool
yeah.
For
me,
what
I
what
I
can
say
right
now,
that
is
on
my
mind,
is
that
for
me,
the
glaring
issues
that
the
solution-
validation
that
we
did
was
had
flaws
and
we
were
relying
on
that
solution.
Validation.
You
know
almost
blindly,
because
we
were
trusting
it,
that
the
process
went
well
and
that
the
results
were
good,
and
so
that's
that's
how
we
build
our
confidence
like
we
need
confidence
to
move
forward
and,
and
we
have
doubted
that
solution
validation.
B
So
to
me,
that's
what
I
can
say
right
now.
Is
this
declaring
issue
what
we
do
with
that?
I
still
have
to
think
a
little
bit
and
and
that's
why
I'm
also
I
wanted
to
hear
your
your
thoughts
as
well.
A
D
I
think
that
I
probably
have
made
my
stance,
maybe
known
I
don't
know
I
I
still
prefer.
I
don't
love
attention
requests.
I
don't
like
that.
It's
got
a
name.
It's
got
a
name
like
that
when
it
doesn't
really
describe
necessarily
what
it
does.
I
don't
like
that.
We
add
to
the
sidebar
and
I
don't
like
that-
there's
an
extra
manual
action
that
is
a
completely
new.
D
C
C
B
C
B
We
can
is
to
I'd
like
to
think
about
this,
a
bit
more
just
to
impact
all
of
this
and
reflect
on
everything
that
has
happened
and
and
and
see
what
we.
C
B
And
I
think
we
can
all
agree
that,
whether
we
like
the
name
or
not
or
how
it
is
executed
and
how
it
is
used,
the
feature
is,
is
valuable,
even
if
it
is
in
this
state
there
is
value.
What
we
can
say
is
that
it's
perhaps
not
the
most
integrated
with
the
current
flow,
that
it
is
disruptive
and
other
things,
but
anyway.
B
So
yeah,
that's
what
I
would
like
to
do
and
I
and
I
hope
to
have
some
more
concrete
thoughts
during
this
week
to
share
with
you
later.
A
There's
nothing
planned
for
it
in
15
1,
because
the
only
work
that
we
still
had
to
finish
up
was
the
the
notification
piece
which
is
done
and
there's
caching
work.
That's
like
behind
a
feature
flag,
but
but
all
like
active
development
is
sort
of
in
a
in
a
stable
point
right
now.
A
A
A
Do
you,
I
guess,
let
me
rephrase
this:
do
you
think
it
would
be
beneficial
to
wait
until
you've
gone
through
that
thought
process
to
turn
this
on,
for
people
outside
of
get
lab?
It's
a
little
more
like
effort
to
turn
this
on
for
for
external
customers.
If
we
were,
if
you
want,
if
we
want
that
sort
of
additional
feedback
or
if
we,
if
we
did
push
ahead
with
that,
are
you
comfortable
with
that?
I
guess
that's
my
question.
A
C
B
I
don't
need
I'm
not
even
sure
if
we
need
more
feedback
or
or
not
like
his
fee,
is
the
the
quantity
of
feedback.
The
problem
is
it
the
quality?
Is
it
do?
We
need
to
do
more
solution,
validation
with
what
we
have
today.
Do
we
need
to
go
back
to
the
drawing
board?
Is
it
just
specific
aspects,
or
do
we
actually
need
to
put
all
of
this
in
pause
and
and-
and
you
know,
go
back
and
try
to
build
the
foundations
for
this
before
going
to
this?
B
So
there
are
many
things
that
we
can
do,
I'm
trying
to
put
all
of
that
together
in
my
head
and
also
I'll
try
to
not
only
my
head
but
I'll
try
to
write
all
of
this
down
in
the
most
concise
way.
I
can
so
that
you
can
all
understand
my
my
thought
process,
but
then
again,
I
want
to
make
sure
that
I
hear
all
of
your
voices
before
yeah
before
sharing
mine.
D
I'm
jumping
in
sort
of
to
the
next
point
about
15.1.
Could
we
just
make
a
decision
to
to
prioritize
looking
into
a
potential
alternative
review
rounds,
come
up
with
some
sketches
and
see
if
that
would
in
fact
solve
the
same
problem
before
we
make
any
decisions
about
turning
this
on
for
other
people,.
B
Yeah,
as
I
said,
I
don't
I
don't
know,
if
maybe
maybe
that's
the
way
to
do
it,
I'm
not
sure.
Yet
I
mean
I'm
saying
review
rounds
but
is
is
redesigning
this
and
having
another
concept
the
way
forward.
That's
what
I'm
not
sure
about,
and
unfortunately
we
have
like
we're
almost
starting
the
new
milestone,
but
I
don't
think
we
should
commit
ourselves
to
okay.
Let's
invest
some
time,
even
if
it's
short
time
with
a
new
concept.
D
B
Okay,
okay,
so
what
what
we
can
do
is
if
you
haven't
already
ping
me
directly
there
and
I'll
I'll,
take
a
look
at
it
and
and
see
what
we
can,
how
we
can
move
forward,
because.
B
A
F
E
It
was
enough
that
managers
were
involved
in
transcripts
were,
or
recordings
were,
listened
to
and
apologies
were
issued.
It
was
that
kind
of
meeting,
so
they
just
they
just
did
not
like
that.
They
were
angry
at
the
features
existence,
so
this
is
secondary
to
whatever
decisions
are
made.
B
Yeah,
what
I
was
going
to
ask
is:
is
that
feedback
represented
in
the
internal
feedback
issue
that
we
have?
Oh.
C
B
B
B
Okay,
would
you
mind
linking
to
the
the
feedback
itself
so
just
to
make
sure
that
I
I.
B
What
you're
talking
about
yeah
thanks
thanks
for
bringing
that
into
our
attention.
B
Right-
and
this
was
was
feedback
from
a
a
user
perspective,
not
about
the
work
that
they
would
have
to
do
in
the
documentation
or
as
a
technical
writer,
but
as
a
user
of
gitlab,
those
technical
writers
were
okay,
yeah
cool
yeah.
If
you
could
link
to
that,
that
would
be
very
helpful
and
thank
you
for
bringing
that
up.
I
will
take
a
closer
look
at
it.
D
This
isn't
necessarily
related,
but
I
have
seen
some
other
feedback
coming
specifically
negative
feedback,
coming
specifically
from
the
tech
writing
team
about
changes
that
I
mean
I'm
not
on
the
team,
so
I
have
no
idea
when,
when
does
it
become
like
a
tipping
point?
Like
you
know,
we
used
to
have
all
of
our
ux
research
captured
in
gitlab
before
it
became
kind
of
ridiculous,
and
then
we
moved
to
dovetail
and
now
we
kind
of
keep
everything
there,
because
there
are
better
tools
for
that.
I'm
wondering
when
the
tipping
point
is
for
tech.
D
A
To
answer
your
question
for
number
three
pitcher,
I
don't
know
if
you
want
to
voice
it,
but
just
to
answer
it,
the
the
only
things
that
I
think
are
really
like
explicitly
scheduled
are
anything
related
to
restructuring.
That's
been
ongoing
from
annabelle
right.
I
think
we've
been
working
on
or
she's
been
working
on
hypothesis
stuff
with.
A
I
wanted
to
say
holly,
but
then
I
was
like
it's
alexis
and
then
outside
of
that,
I
think
the
only
other
thing
is
there
had
been
some
conversation
in
the
automatically
assigned
mr
review,
based
on
approvers
issue
and
annabelle
was
potentially
going
to
take
a
look
at
that
in
1501
marcel
sort
of
volunteered.
A
A
And
then
and
then
the
rest
is
like
open
and
I
think
we've
got
space
and
I
think
part
of
that
was
a
lot
of
the
features
that
are
in
flight
had
had
design
work
done
like
the
submit
comment,
when
you
finish
a
review
thing,
add
the
approval
that
work
is
already
done,
the
uis
and
stuff
for
like
enforcing
notification
like
forcing
authorization
on
uploads
and
email
death.
A
Suppression
stuff,
like
all
of
that
work,
is
done
so
there
might
be
some
review
work,
but
there's
not
anything
like
big
design
work
and
then
the
rest
of
the
space
is
sort
of
there
because
you
were
coming
back
and
attention
request
has
been
this
sort
of
looming
thing
that
been
slowly
pushing,
but
no
one's
really
pushing
pushing.
I
think
I
think
we
all
knew
we
wanted
to
wait
for
you
to
get
back
to
c.
So
there's
a
lot
of
space
for
that.
B
Okay,
and
thanks
for
for
that,
the
the
deliverables
for
the
next
milestone
are
they
kind
of
locked
in
yes,
the
board
is
up
to
date
and
and
locked
in
okay,
cool
I'll.
Take
a
look
at
that,
and
yes,.
B
Aware
of
annabelle
looking
into
the
machine
learning
for.
A
A
We've
resisted,
but
I
think
there.
A
B
Okay
ben,
you
have
the
last
point.
C
Just
starting
the
the
cms
for
editor
extension
soon,
the
recruitment
was
done
while
I
was
out
of
office
last
week.
So
I'm
gonna
pick
that
up
this
week,
hopefully
done
by
15
1,
but
it
might
not
be
we'll
see.
B
Cool
great
news,
thanks
for
doing
that
and
yeah,
I
think
that's
that's
it
for
this
meeting
thanks.
Everyone.