►
From YouTube: 2022-09-27 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
A
I
yeah
this
I
chatted
with
Annabelle
and
Ben
about
using
this
meeting
to
have
a
recurring
topic
about
the
okr,
just
as
a
a
way
for
us
to
sync
and
provide
updates
not
only
between
ourselves
but
to
to
Kai
into
anyone
else
who
is
attending
this
meeting
or
watching
the
recording
and
yeah
as
I'll
be
off
for
a
good
period
of
time
of
this
opr
Annabelle
will
be
leading
the
effort,
and
the
goal
as
it
is
written
there
in
the
okr
title,
is
to
create
five
planning
breakdown,
issues
to
restructure,
merge
requests
and
the
number
five
is
a
aspirational
goal.
A
So
that's
what
we're
trying
where
we're
trying
to
go
and
the
planning
breakdown
is
the
workflow
workflow
phase
or
step
that
we
would
like
to
have
those
issues
on
yeah,
I
added
a
point
there
about
the
the
research
but
I'll
stop
to
see
if
anyone
has
any
questions
or
if
they
want
to
add
anything.
As
part
of
this
sync
as
a
sub
point.
A
Yeah,
that's,
okay!
The
idea
is
to
not
use
the
meetings
in
in
full.
I
mean
it's
just
a
point
to
sync
on
this:
if,
if
we,
if
we
I
mean
I,
I
I
won't
be
present
on
the
the
next
meetings,
but
I
think
that,
if
a
certain
points,
this
topic
fills
up
the
all
meeting,
we
should
create
a
separate
calendar
events
just
for
this
meeting,
so
that
we
don't
yeah,
as
you
were
saying
like
some
for
some
people,
this
is
just
FYI
and
they
don't
participate.
A
So
we're
we're
starting
the
validation
efforts
and
to
split
the
work
into
more
manageable
pieces
were
not
only
focusing
on
one
of
the
key
ideas
that
is
most
related
to
code
review
and
that
we
feel
can
have
the
most
valuable,
which
is
the
comments
Tab
and
the
more
minimal
activity,
log
or
feed,
but
we're
also
splitting
this
validation
into
two
rounds,
the
first
one
being
a
internal
validation
rounds
with
so
in
with
internal
users
and
we'll
do
concept
testing
and
in
the
second
round
it
will
be
more
usability
testing
and
we
will
flesh
out
the
details
more
in
higher
Fidelity
and
yeah
I
want
to.
A
We
made
that
split,
I
created
two
or
created
an
issue
for
that
and
repurpose
the
first
one
and
the
old
care
was
reflected
for
that
and
yeah
I
think
I'm
good
about
the
the
script
that
Annabelle
put
together
and
the
Prototype
Ben.
If
you
could
take
a
look
at
that,
I
know.
I
know
you
already
did,
but
you
know
just
the
last
look
to
see
if
anything
pops
up
that
would
be
helpful
and.
A
Tentatively
scheduled
to
sessions
for
tomorrow,
one
in
my
morning
and
the
other
in
my
afternoon,
see
how
that
goes,
but
yeah.
If
we
need
to
make
some
tweaks
to
the
script
or
prototype
and
if
it's
not
ready
in
time,
I'll
move
those
sessions
to
Thursday.
Maybe.
D
Just
to
make
sure
I
I'm
clear,
so
the
the
next
step
is
the
internal
concept
testing.
That's
what
you're
working
on
now.
C
A
Six
people
in
total
three
new
users
and
three
experienced
users,
so
yeah
we're
sourcing
for
the
new
users,
I
we're
starting
them
from
the
new
team
members,
slack
Channel
and
all
of
them
have
started
this
month
at
gitlab
and
except
for
one
of
them
all
of
them
started
using
gitlab
this
month.
So
I
think
it's
yeah,
it's
good!
It's
just
like
really
really
new
users
and
the
other
ones
more
experienced
have
been
here
for
longer
period
of
time.
D
Okay
and
you're
walking
them
through
in
the
internal
concept
issue,
there's
like
a
prototype
sort
of
in.
A
Yeah
yeah,
it's
it's
a
basic
prototype,
that's
Annabelle
put
together
that
builds,
builds
upon
what
was
already
shown
and
that
you've
already
seen
and
adds
a
few
interactions
here
and
there
and
we
have
a
script
just
to
show
them
the
Prototype
and
just
have
more.
There
are
specific
questions,
but
I
think
will
be
more
of
just
unstructured
conversation
about
their
perception
of
the
ideas,
what
they
would
expect
to
see
here
and
there,
because
we
can't
really
use
that
for
detailed
and
fine
usability
testing.
A
You
know
for
time
on
task
or
errors,
or
things
like
it's
just
like
a
conversation
about
the
concepts.
B
A
Okay,
okay,
I'll
I'll,
invite
you
as
optional,
and
also
Kai,
at
least
to
the
ones
that
I
I
have
scheduled.
We
have
this
so
I'm,
not
gonna
share
my
screen
with
the
the
spreadsheet,
but
we
have
a
participants.
A
B
Yeah
I
can
take
sessions
if
they
are
not
okay,
it
looks
like
I
see
you
have
a
scheduled,
got
it
yep,
so
the
ones
where
my
name
is
in
the
column.
A
Yeah,
one
of
them
is
in
yeah
I,
think
both
of
them
are
in
the
America
yeah
both
are
in
the
Americas
time
zones,
one
in
South
America,
but
yeah
in
America's
time
zones
in
one
of
those
people
is
newer
to
the
product
and
the
other
is
more
familiar
with
the
product
and
yeah.
B
A
Ideally,
it
would
be
during
this
week
so
that
we
could
start
and
try
to
have
the
the
insights
wrapped
up
by
early
next
week,
but
but
but
it's
okay,
it's
it's
already
Tuesday.
So
it's
not
like
we're
planning
this
a
lot
of
in
advance.
So
whatever
works
for
you,
okay,.
B
A
A
Any
other
thoughts
or
questions
and
people
want
to
share
about
the
the
okr.
A
All
right
I
mean
we're
too
down,
but
so
I'll
assume
that
everything
is
okay.
So
moving
on
to
the
next
point
about
the
applied
ml,
anti-abuse,
I,
don't
know
if
this
has
been
publicly
shared,
but
I
mean
it
has
been
publicly
shared,
but
maybe
not
in
a
broader
setting
but
Katie
McCoy.
A
She
was
the
product
designer
from
package
and
she's
moving
to
the
applied
ml
anti-abuse
groups,
so
they
will
have
a
dedicated
product
designer
and,
as
I
wrote
there,
she
will
begin
onboarding
to
those
groups
in
Milestone,
15-6
and
I
think
it
would
be
valuable
to
share
with
her
what
we've
done
in
code
review
related
to
suggested
reviewers
and
how
we've
been
working
with
them
just
to
hand
over
that
part,
and
it
won't
be
a
complete
Handover,
because
we
will
still
be
involved
and
need
to
be
involved
in
the
suggested
reviewers,
because
likely
most
of
the
feedback
will
be
targeted
at
us.
A
Because
code
review
is
the
face
of
merge,
requests
for
the
good
and
the
bad
so
but
yeah,
it's
really
good
to
have
finally
a
product
designer
there,
so
that
me
and
Annabelle,
and
mostly
Annabelle,
is
not
overloaded
with
things
related
to
suggested
reviewers.
But,
as
I
said,
we
will
still
need
to
be
there
in
a
Consulting
role
and
yeah
Amy.
You
added
a
point
there.
You
can
voice
that
I
think
we
have
time
sure.
D
C
Katie
was
and
where
she's
going
and
she's
had
two
of
our
newest
Tech
writers.
Admittedly,
that's
a
that's
going
to
be
a
bigger
problem
for
the
next
few
months,
because
we
just
got
a
large
cohort
of
new
tech,
writers
and
I.
Don't
know
how
closely
she
wants
to
work
with
her
Tech
writer.
I,
don't
know
if
she
realizes
how
closely
she
can
work
with
her
decorator
but
showing
her
that
good
relationships
are
possible
and
that
you,
you
can
bug
your
Tech
writer
all
the
time
for
stuff
they
like
that
yeah.
A
Yeah
I
agree,
and
to
you
are
you
going
to
be
involved
in
this
process
somehow
or
nope?
A
C
C
And
actually
that's
important
to
note.
I
am
giving
up
editor
as
of
15.5,
so.
A
A
C
A
And,
and
vice
versa,
you're
going
to
keep
us
busy
as
well
being
more
demanding,
perhaps
who
knows
or
giving
more
even
having
more
time
to
provide
eloquent
and
thoughtful
comments.
A
C
A
But
but
yeah
I
think
so
I
don't
know
yeah
how
much
the
the
working
applied,
ML
and
ntapus
will
overlap
with
code
review
other
than
what
we
know
today
of
suggested
reviewers.
A
So
but
yeah
thanks
thanks
for
for
bringing
that
up,
Amy
and
yeah.
Let's,
let's
make
sure
that
we
encourage
that
kind
of
behavior
and
relationship
when
Katie.
A
Yeah,
so
both
Annabelle
and
Kai
I,
don't
know
if
you
heard.
What's
we
were
on
the
third
point
about
Katie
our
existing
product
designer
joining
the
applied
ml,
anti-abuse
groups-
I,
don't
know
if
you
heard
any
of
that.
A
Yeah,
so
I
won't
be
here
during
that
time
that
she's
on
boarding
so
I,
don't
also
don't
know
how
it
would
be
best
to
do
this
Handover
or
sync
on
suggested
reviewers
from
a
design
and
product
management
perspective
and
how
the
groups
have
been
collaborating
and
what
are
the
expectations
so
Katie
I
don't
know
if
she's
traveling
but
I
believe
she
is
based
in
Australia.
A
So
yeah
I'll
leave
that
up
to
you,
it
was
just
you
know,
part
FYI,
hey.
We
have
a
dedicated
product
designer
for
those
groups,
but
at
the
same
time
you
know
have
the
group
think
how
it
would
be
best
to
sync
up
with
her
on
that
matter,
because
those
groups
have
been
just
engineering
engineering
engineering
and
have
reached
out
to
us
and
maybe
other
groups
when
they
need
some
kind
of
design
work
which
has
been
on
our
plates.
So.
B
A
Okay,
you.
D
D
Added
has
anyone
seen
this
feature
because
I
think
it's
it's
live?
It
was
in
the
release
post
as
live
like
in
the
drop
with
the
drop
down,
and
everything
and
I
was
just
curious.
If
anyone
had
actually
seen
it.
A
I
mean
I,
know,
I
haven't
seen
it
yet
it's
not
showing
up
for
me
in
the
drop
down
and
the
suggest
reviewers
comments
is
still
I,
think
being
applied
to
merge
requests.
D
A
D
D
So
it's
been
reviewed,
I
I
added
the
image
to
the
release
post
from
a
design.
Not
you
know
real
life,
so
I
don't
know.
Okay,
cool.
A
All
right,
that's
all
I
had
I,
don't
know
if
I
don't
know
if
there
are
any
other
comments
or
thoughts
about
this
point
or
anything
else
that
people
would
like
to
discuss.
D
I
think
we're
good
Pedro
you'll
be
missed,
but
we'll
see
you
we'll
see
you
back
in
time
for
everyone
to
take
time
off
for
the
holidays.