►
From YouTube: 2021-04-21 Create:Code Review Weekly 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).
A
A
Okay,
michelle's
big
announcement
is
I'm
leaving
the
code
review
team
on
monday.
I
will
officially
transfer
over
to
manage
and
matt
is
going
to
take
over
as
acting
em
for
code
review
on
monday
as
well.
But
I've
just
done
this
before
with
sean
not
that
long
ago,
and
I
did
it
before
that
with
marin
as
well
and
I
think
both
of
those
times
those
transition
periods
went
very
smoothly.
A
So
I'm
working
with
matt
this
week
to
make
sure
the
transition
is
super
smooth
and
nobody
should
notice
too
much.
Of
course,
there
will
be
a
learning
curve
for
matt,
but
I'm
also
going
to
keep
in
touch
with
matt
and
anything
he
needs
as
well.
So
I'm
still
going
to
be
available,
but
I
guess
first
any
questions
or
concerns
from
anybody
about
that.
Hey
sarah
sarah's,
on
the
call.
Congratulations
to
sarah!
B
Congrats
michelle,
I'm
I'm
concerned
about
you
leaving,
but
I'm
happy
for
you.
A
Well,
no,
no
need
to
be
concerned
about
that.
Like
I
said,
matt
is
gonna.
Do
great
he's
had
at
least
three
teams
that
I'm
aware
of
and
they've
all
given
him
great
feedback,
but
my
biggest
question
to
everyone-
and
you
still
all
have
a
few
days
to
think
about
this-
is
what
do
you
need
me
to
wrap
up
this
week
before
monday
and
if
you
have
anything
put
it
in
the
agenda?
That
would
be
great,
but
if
not
just
sit
on
it
and
think
about
it
and
send
me
a
slack
message.
C
Michelle,
I
have
a
question:
do
you
think
it'd
be
worth
having
a
session,
the
three
of
us
just
to
talk
about
engineering
things
that
we
have
been
talking?
It's
kind
of
like
a
shared
knowledge
and
things
you
already
know
instinctively
that
we
have
in
the
in
the
plan
and
it
could
be
useful
to
have
front
end
as
well
there,
or
are
you
good
in
just
doing
the
handover
with
matt?
A
A
A
A
E
I'm
very
happy
for
you,
congratulations
michelle
and
I
think
it's,
it's
always
sad
of
course,
but
at
the
same
time
these
changes
help
us
reflect
and
look
at
things
in
a
different
way.
So
I
hope
that
you
can
do
that
for
manage
and
matt
will
do
that
for
us
coming
in
and
looking
things
with
new
eyes
could
be
helpful.
So
congratulations
and
yeah
you're
still
going
to
be
pinged
in
a
lot
of
things.
So
you're
not
going
to
get
rid
of.
E
C
G
G
E
Yeah
I,
for
me,
sharing
in
slack,
is
good
because
for
these
cases
I
believe
that
we're
looking
for
timely
responses-
and
maybe
people
in
social
media
are
not
so
used
to
synchronous
communication
as
we
are
waiting
for
people
to
reply.
So
I
think
in
slack
is
good,
because,
if
someone's
online
they
can
jump
on
onto
it
and
if
it's
something
that
we
can
work
from,
we
can
always
create
issues
afterwards
and
not
everything
deserves
an
issue.
I
think
there
was.
G
Okay,
that's
that's
helpful.
I
think
it
was
one
of
the
like
it's
a
negative
tweet.
So
if
you
open
it,
it's
more
like
talking
about
everything
is
broken,
but
I
think
it's
a
good
entry
point
to
say:
hey.
G
E
Now
one
of
the
things
that
I
yeah,
one
of
the
things
that
I
personally
try
to
do
every
week
is
spend
at
least
30
minutes
looking
at
mentions
from
gitlab
and
merge
requests
in
twitter,
specifically
and
so
I'll.
I
haven't
gotten
to
this
tweet
yet
so
if
it
comes
up
I'll
I'll
respond
to
it
and
see
what
we
can
do
for
them,
but
thanks
for
for
raising
this.
G
Thanks
for
taking
care,
I
also
have
the
next
point,
so
I
was
apply
a
batch,
applying
review
suggestions
from
a
blog
post
and
I
kind
of
I
have
a
collision
somewhere
and
I
couldn't
figure
it
out,
and
so
I
was
looking
for
an
issue
and
couldn't
find
anyone
but
created
one
now,
and
I
was
wondering
if
this
like
this
is
like.
F
Yes,
that's
a
question
for
me:
there's
no
work
planned
to
do
anything
else
with
probably
batch
suggestions,
not
in
the
near
future.
I
think
if
we
do
anything
in
the
near
term,
it'd
be
custom.
Commit
messages
are
still
not
supported
in
batch
suggestions,
so
that
would
be
the
last
sort
of
piece
that
we're
looking
at
in
suggestions.
F
I
honestly
haven't
seen
anyone
run
across
the
issue
that
you
have
before,
but
it's
also
in
the
code
review
explicitly
code
not
pros,
which
is
what,
where
suggestions
are
heavily
used
in
gitlab,
but
when
you're
looking
at
code
review,
most
people
do
not
actually
apply
suggestions
based
on
the
data
that
we
have,
and
so
we
don't
run
into
this
as
much
like
we
see
suggestions
being
offered
but
they're
not
necessarily
used
in
that
way.
F
So
so
I
don't
know
if
it
it's
an
interesting
bug,
I
don't
know
that
we'd
get
to
it
anytime
soon.
I
guess
is:
maybe
the
way
to
think
about
that.
G
Yeah,
I'm
not
sure
if
it's
a
bug
I
I
probably
would
wish
that
the
ux
or
the
the
error
message
is
more
like
providing
me
the
action
to
unselect
the
colliding
suggestion,
but
probably
it's
a
special
use
case.
The
way
we
use
it,
but
it's
also
an
interesting
point
that
our
users
are
maybe
not
using
the
feature
enough.
So
I
can
think
about
like
putting
this
out
in
a
workshop
or
promoting
this
even
more.
G
C
I
I
would
actually
say
that
this
is
a
very
hard
problem
to
solve
once
you
reach
this
state
of
having
54
suggestions
in
a
long
file,
so
maybe
maybe
we
can
try
to
avoid
getting
them
into
the
situation
in
the
first
place,
by
limiting
when
they're,
adding
a
suggestion
that
collides
with
anyone,
that's
already
in
the
bundle
in
the
batch,
just
not
allowing
them
just
saying
that
hey,
you
cannot
add
the
suggestion,
because
it
conflicts
with
something
that's
already
there
or
actually
point
to
the
suggestion.
C
I
think
maybe
we
can
rewrite
that
issue
in
that
direction.
It's
still
I'm
with
kai.
I
think
this
is
a
very
like
complex,
deep
nested
experience
bug,
but
I
think
if
we
point
it
in
that
direction,
who
knows
maybe
some
contributor
will
step
up
and
build
it
yeah,
just
my
thoughts
peter.
Do
you
have
any
thoughts
on
that.
G
Yeah
thanks.
That's
really
helpful.
I
will
think
about
updating
the
issue
and
moving
this
into
this
direction.
C
Right,
I
have
the
next
point,
so
I
just
wanted
to
check
in
since
we're
all
here.
This
is
something
that
came
from
a
ic
led
suggestion.
C
They
they
will
find
the
time
they'll,
they'll
they'll
work
without
affecting
the
deliverables,
and
since
we
have
a
10
part,
this
came
up
in
a
discussion
and
I
wasn't
entirely
sure
if
we
completely
abandoned
this
idea.
It's
not
a
priority,
I
know,
but
I
just
wanted
to
get
the
pulse
on
this.
Is
this
something
that
we
don't
know
exactly?
How
we're
going
to
be
building
it?
Or
is
it
just
missing?
Maybe
a
ux
review
yeah
anybody
has
thoughts
on
this
topic.
The
topic
is
saved
replies
for
comments.
F
F
I
would
say:
plan
means
to
review
it
and
sort
of
sign
off
on
it
like
we
treat,
I
don't
think
we
treat
other
group
contributions
like
community
contributions,
but
almost
like
that
right,
like
we
just
need
to
get
it
on
their
radar
enough
that
they
do
the
reviews,
and
I
can
I
can
ping
gabe
and
holly
as
well,
but
I
mean
holly's
been
pinged
in
the
issue.
So
right.
C
So
sh,
maybe
just
a
matter
of
like
raising
this
again
with
them,
for
their
feedback.
Okay
and-
and
I
think
it's
fine-
if
we
get
the
ux
guidance
from
project
project
management
and
then
our
engineer
builds
it
so
it
doesn't
really
so
we're
not
asking
for
prioritization
from
products.
I
guess
because
we
understand
this
is
like
a
like,
not
a
huge
thing
on
our
road
map,
but
it
would
be
nice
for
us
to
have
it
in
the
product
if
possible,
if
acceptable.
C
So
will
you
ping,
kai
someone
or
a
sign
reviewer
yeah?
Maybe
maybe
it's
just
a
matter
of
dropping
a
comment
then
do
you
want
me
to
take
care
of
that.
E
Okay,
yeah
just
just
very
quickly
yeah.
I
just
wanted
to
say
that
I
actually
love
that
feature
and
I
would
use
it
a
lot
but
yeah,
given
everything
that
we
have
in
code
review
and
since
we
have
a
team
that
could
also
leave
this,
I
would
prefer
to
hand
it
over
to
them,
not
necessarily
in
engineering
capacity,
but
because
I
think
this
falls
very
strong
to
that
10,
rule
or
initiative
that
we
have
going.
So
I'm
really
happy
to
see
phil
doing
this
but
yeah.
D
H
Yeah
I
had
a
we
had
a
brown
out
about
two
minutes
ago:
okay,
okay,
cool
I've
been
sort
of
punishing
andre
with
my
technical
writer,
pretending
to
be
a
front-end
engineer,
mr
slightly,
and
I
would
like
to
expand
the
group
of
people
who
I
bother
and
everybody
else
is
frozen.
This
does
not
bode
well.
We
can
still.
H
I
would
like
to
make
more
friends
in
that
so
that
I
can
ask
questions
about
these,
mrs
that
I'm
creating
that
blur
the
line
between
technical
writing
and
front-end
engineering,
but
I'm
very
hesitant
to
bother
people.
So
if
you
are
interested
willing
to
answer
some
questions
here
and
there,
I
would
love
to
spread
these
out,
because
andre
has
been
answering
a
lot
of
questions
and
I
still
want
him
to
speak
to
me.
Two
milestones
from
now.
C
No,
I
was
thinking,
maybe
so
it
might
be
off
my
my
working
hours
and
for
you
not
to
be
blocked.
I
think
one
one
suggestion
would
be
to
drop
in
through
our
amazingly
named.
I
hope
hope
that
I'm
called
is
this.
Is
this
correct
front.
C
It's
not
so,
if
create
source
code,
front-end
teams
channel
it's.
Basically
my
direct
reports
and
whoever's
there
online.
We
have
a
good
span
of
time
zones
and
yeah.
We
have
tamash
on
the
call
so
just
drop
in
there
and
ask
for
help
hey
anyone
around
that
can
help
me
and
I'll
I'll
pass
along
the
message
that
for
you
to
be
expected
and
to
be
treated.
H
C
C
Right
right
so
yeah,
so
that's
because
something
that
we
me
and
tommy
already
talked
about
some
some
things
that
would
not
have
visibility.
When
we
change
the
front
end
and
the
code,
we
break
some
things
on
qa.
It's
it's
like
sort
of
a
something
we're
working
on
to
improve,
but
it
it
fools
everyone
is,
is
definitely
not
a
wait.
What's
the
acronym,
I'm
not
a
front-end
engineer
case,
but
yeah
please
reach
out
to
the
team.
There
they'll
be
glad
to
help.
H
C
Know
we
at
one
of
the
contributes
in
cape
town,
no
in
cape
town,
we
had
a
session
where
we
used
some
glasses,
like
that,
would
blind
you
and
using
the
the
website
using
the
screen
reader,
and
we
did
all
several
front-end
engineers
do
that
and
it
was
humbling.
We
know
there
is
trouble.
C
I
wanted
to
I
want
to
welcome
sarah.
I
don't
want
to
put
you
on
the
spot,
but
I
I
I
saw
the
announcement
on
linkedin,
so
I
know
why
you're
here
welcome.
Is
there
anything
you
want
to
say
to
the
group
anything
that
we
can
help
anything
at
all.
I
Thank
you
for
the
welcome.
I
appreciate
it
and
you
put
a
coffee
chat
on
my
calendar,
so
I
also
appreciate
that
I'm
just
here
to
listen
and
observe
and
try
to
get
up
to
speed
on
the
four
groups
in
the
create
stage.
I
If
there's
something
particularly
interesting
about
the
team,
something
you're
working,
you're
working
on
an
opportunity,
if
you
want
to
cc
me
and
your
team
channel,
I
feel
like
that'd,
be
a
good
way
for
me
to
continue
to
learn
and
then
also
not
to
inconvenience
everybody
else's
actions,
and
I
can
follow
along
in
that
channel.
So
thank
you
for
the
welcome.