►
From YouTube: 2022-06-08 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).
B
All
right,
pedro
and
animal
you've
got
the
first
one
up.
C
Yeah
animal,
do
you
wanna,
do
you
wanna
talk?
I
mean
I
was
just
presenting
in
the
ux
showcase
about
the
beautifying.
Why?
So?
I
think
you
have
a
momentum
going
about
this
topic,
so
you
want
to
want
to
talk
about
this.
A
Sure
I
added
it
to
the
agenda
because
you
said
you
couldn't
make
it,
but
I
feel,
like
I
don't
know
what
the
actual
action
point
here
was.
Everyone
knows
that
I
love
doing
that
work
and
the
benefits
are
clear
and
the
negatives,
but
I
don't
know
specifically
what
your
goal
was
with
this
comment.
So
perhaps.
C
Yeah,
I
can
talk,
yeah,
don't
worry
yeah
I
mean
in
the
end,
is
you
know,
just
keep
doing
it
and
it's
the
way
that
we
kind
of
used
to
work
back
in
the
day
at
gitlab.
You
know,
especially
with
smaller
things.
You
know
just
to
it
not
a
lot
of
you
know,
prior
validation
and
and
things
like
that
for
smaller
changes
that
we
could
revert
or
easily
adapt
so
yeah.
C
I
was
just
thinking
that
the
yeah
that
beautifying
ui,
seeing
you
know
annabelle
and
phil,
pushing
out
all
of
those
changes.
It
gave
me
this
feeling
of
nostalgia
and
and
and
also
like
a
positive
vibe
of
we're
actually
shipping
things
in
an
area
of
the
product
where
there
are
so
many.
C
You
know
invisible
constraints,
we
know
about
them,
but
it
just
can
sometimes
constrain
us
to
do
certain
things
so
yeah.
We
want
to
start
allocating
time
each
milestone,
at
least
for
me
and
annabelle,
to
do
more
of
this
type
of
work.
It
could
be
any
part
of
the
product
or
documentation,
although
of
course
you
know
code
review
issues
are
you
know
top
of
mind
and
because
we
think
about
them.
Every
day
so
yeah
it's
something
that
we
wanted
to
do.
We
couldn't,
you
know,
do
it
alone.
C
You
know,
ideally
with
an
engineer
to
pair
with
us
here
and
there
and
yeah.
I
commented
there
that
staff
engineers,
you
know,
usually
have
this
kind
of
autonomy
and
are
expected
to
you,
know
allocate
this
amount
of
time
to
do
whatever
they
want
more
or
less
so.
C
Phil,
of
course,
was
a
natural
first
choice
because
he
was
also
involved
in
beautifying
ui,
but
we
wanted
to
involve
more
engineers
and
include
you
know
if,
if
reasonable
so
yeah,
I
think
that's
the
first
point
about
yeah
what
what
is
the
appetite
from
the
engineering
side
to
work
more
like
this?
You
know
for
smaller
things,
yeah,
that's
the
preface
and
then
what
I
would
my
my
intention
with
this
point
and
well
I
don't
know
if
there's
anything
you'd
like
to
add.
A
C
D
Great
pause,
great
delivery,
that's
good!
I'll!
Just
add
my
point
here:
yeah
we've
talked
about
this
in
the
past.
Within
the
team
as
well
and
stan
is
love
you're
on
the
call.
So
if
you
want
to
speak
up,
do
us
mention
what
you
think
about
it,
but
yeah?
I
would
totally
put
stanley's
love
also
for
rotation
on
this
topic.
I
think
it
would
be
great
edition.
D
Blink
twice,
if
it
wasn't
exactly
now,
this
is
good.
This
is
this
is
really
good.
So
going
on
to
my
second
part,
which
is
the
thoughts
and
concerns
yeah,
just
wondering
how
much
capacity
were
you.
Thinking
could
be
beneficial
here
and
like
useful
to
have
allocated
from
an
engineer
perspective,
because
as
long
as
it
doesn't
block
us
from
preceding
other
stuff,
I
think
it's
totally
fine
and
kai
had
a
similar
concern.
D
B
Well,
I
think
it's
just
every
milestone
feels
like
a
lot,
and
we
need
to
be
cautious
about
how
we
define
capacity
here.
I
know
from
watching
this
happen
in
15.
It
was
a,
I
think
it
was
more
capacity
than
I
expected
out
of
both
phil
and
annabelle
were
like
used
for
this
effort
and
so
like.
If
we're
talking
about
that
level
of
capacity
in
every
milestone
that
doesn't
seem
reasonable,
necessarily
and
then
we
also
have
which
I
put
in
here.
B
Like
another
concept
currently
like,
we
have
a
thing
that
we
call
10
percent
time,
which
is
sort
of
for
engineers
to
go
and
do
what
they
want
to
do.
That
is
like
part
of
their
planned
capacity
and
undirected
time,
and
so
I
think,
if
engineers
want
to
use
it
for
this,
that
makes
sense
if
engineers
want
to
use
it
for
something
else
like.
I
think
that
makes
sense
if
we're
talking
about
10
time
and
then
another
10
time
for
beautifying
the
ui
like
we,
we
need
to
have
like
maybe
a
different
conversation.
A
B
It
was
something
we
did
like
last
year.
We
we
opted
to
provide
that
as
a
space
to
go,
explore
versus
trying
to
direct
all
of
the
time,
be
more
deliberate
about
it.
A
It
would
be
cool
if
we
should
go
and
update
the
handbook
with
some
examples
of
what
people
have
been
doing
it.
I've
seen
some
things
like,
I
think,
phil
added
that
about
me
section
for
the
pro
for
your
personal
page.
I
think
that
was
that
is
that
that
ten
percent
time
you're
talking
about.
B
A
B
A
B
He
gets
an
abnormal
amount
of
time
to
do
things,
but
he's
productive
in
all
forms
and
yeah.
D
But
like
directly
and
it's
very
complicated
to
define
it's
just
like
he
has
a
looser
defined
scope
of
work.
Let's
put
it
that
way
and
that
just
comes
from
like
being
more
senior
and
being
more
comfortable
in
complexity
of
the
code,
so
ships
more.
That's
that's
proportionate
to
the
maturity
in
the
team
but
yeah
I
linked
there
amy,
where
we
define
that
in
the
handbook.
It's
a
broad
thing,
but
yeah
we
don't.
We
don't
keep
track
explicitly,
but
we
do
encourage
it.
D
I
would
I
would
go
to
maybe
when
the
engineers
are
participating
on
the
beautifying
effort,
then
they
would
allocate
those
10
to
those
efforts
they
won't
be
forced
to
it.
So
I
would
feel
like
the
impact
would
be
a
little
bit
less
big
in
that
sense.
D
So,
but
we
can
try
it
out
and
see
how
it
goes
outside
of
that
normal
form
beyond
phil,
I'm
I'm
more
interested
about
rotating
beyond
phil
and
not
just
keeping
it
within
the
staff
just
for
more
satisfaction
and
more
experience
in
like
touching
this,
because
it's
it's
the
garden
right
we
all
want
to.
D
We
should
all
be
gardeners
of
our
own
garden
and
helping
improve
that
so
yeah
thomas,
I
don't
know
if
you'd
be
up
for
it,
because
I
feel
like
you're
more
comfortable
in
the
back
as
we
talked
about
often,
but
this
wouldn't
be
a
mandatory
or
anything.
It
would
be
something
that
you'd
be
stepping
up
if
you
want
to
but
yeah
I'll.
Take
it
a
try
and
we'll
we'll
keep
the
location
reasonable
so
to
speak
and
see
how
it
goes
from
there.
A
It
might
be
easier
to
figure
out
time
spent
and
allocation
if
people
knew,
or
at
least
had
an
idea
of
what
they
could
be
working
on
so
part
of
the
the
last
beautification
effort.
We
had
this
issue
where
everyone
was
just
kind
of
dumping
ideas,
and
if
someone
wanted
to
participate,
they
could
just
go
and
look
at
that.
You
know
code
review,
beautification
issue
if
they're
passionate
about
any
of
them
or
if
they
have
any
ideas
of
their
own
post
them,
and
then
we
can
not
schedule
it.
A
D
Okay,
that's
helpful
yeah
having
a
having
that
work
prepared
is
definitely
helpful
in
figuring
out
what
to
pick
and
from
our
perspective,
in
terms
of
planning,
we'll
just
assign
a
buffer
capacity,
and
for
that
person
on
that
milestone
and
then
they'll
figure
out
what
I
want
to
work
on.
Let's
wing
it
I
would
say.
C
Yeah,
I
think
annabelle's
suggestion,
which
seems
that
it
also
worked
well
in
the
last
milestone
for
that
initiative.
I
think
it's
great
that
we
can
maybe
start
there
and
just
dump.
You
know
some
existing
issues
or
just
random
ideas
of
things
that
we
could
do
me
and
annabelle.
We
could
do
that
and
I
mean
anyone
could
participate,
but
we
could
start
and
and
then
see
how
we
can
go
from
there
and
see
everyone's
appetites
and
capacity.
C
D
All
right
then,
move
on,
so
I'm
I'm
pulling
the
topic
that
has
been
discussed
on
the
ux
calls.
I've
been
catching
the
recordings
about
the
the
future
of
attention,
request,
feature
and
I
think,
I'm
up
to
date
with
the
latest
thing.
So
I
see
that
we're
in
the
verge
of
starting
to
test
this
with
like
external
users,
whatever
that
really
means.
D
What
I
wanted
to
like
ask
here
is
whether
there's
some
things
that
you'd
like
to
improve
in
the
in
like
technically
in
the
future
that
we
already
know
and
that
we
already
know
it's
a
problem
before
we
go
proceed
with
the
testing,
because
sometimes,
as
you're
doing
the
tests
you're
so
you're,
seeing
like
repeating
feedback
repeating
feedback.
Yes,
we
know
about
this.
We
know
about
this,
and
usually
those
are
small
cosmetic
things
that
we
can
improve
to
have
a
better
results
on
the
tests.
D
E
Well,
we
had
some
hypotheses
from
the
the
prototype
testing,
but
from
from
talking
to
the
giddily
folks,
they
didn't
seem
to
have
this
quite
the
same
issues
that
that
we
thought
they
might
the
one
there's
a
couple
things
that
I
could
suggest,
but
I
don't
know
how
how
feasible
or
what
the
appetite
is.
There
was
some
confusion
about,
for
instance,
whether
merged
or
closed
mrs
should
generate
an
attention
request.
E
E
D
That
was,
and
it
isn't
it
isn't
the
big
hurdle
that
it
could
be
yeah.
Then
that
probably
makes
sense
to
continue
the
test
as
it
was
and
we'll
reformulate
what
we
need
to
reformulate.
Once
you
have
more
concrete
conclusions,
thanks.
D
C
In
front
of
the
mirror,
no,
I
I
think
yeah.
I
think
what
ben
said
makes
a
lot
of
sense.
There
are
yeah,
the
icon
is
not
the
deal
breaker,
it's
not
the
thing
and
and
as
ben
said
like
it
wasn't
mentioned
that
much
or
almost
at
all,
as
an
issue
with
the
goodly
team.
C
But
again
you
know,
the
galileo
team
is
just
a
few
users
that
are
internal
users
that
are
used
to
how
we
build
kit
lab
and-
and
just
you
know,
the
user
experience
of
it.
So
it's
it's
great
that
we're
planning
on
you
know,
including
other
kinds
of
users.
I
think
yeah.
My
concerns
right
now
are
other
foundational
issues
that
I
have
highlighted
in
the
the
issue
about
future
of
attention,
requests
which
I
can
drop
the
link
there.
C
If
it's
not
there
already
and
so
yeah,
let's
see
how
that
goes,
but
I
have
to
reinforce
that
there
are
lots
of
great
things
about
what
we
built.
Okay,
so
it's
not
like.
Oh
it's
all
bad.
There
are
positive
things,
and
that
is
also
again
reflected
on
the
feedback
that
we
got
from
the
get
elite
team
about.
You
know
knowing
who
needs
to
take
the
next
action.
C
That
is,
you
know
crystal
clear,
of
course,
once
you
understand
the
icon
and
all
of
that,
so
when
you
have
when
you
learn
it,
it
works
well,
and
you
know
the
lists
focus
on
what
you
need
to
do
next,
not
having
to
filter
your
to-do's
to
know
what
margin
requires.
You
need
to
take
a
look
at
so
yeah.
There
are
positive
things
for
sure,
or
else
we
wouldn't
have
gotten
this
far.
I
think.
D
Yeah,
no,
I
think
that
was
clear
from
the
from
the
calls
that
I
watched
it
just
feels
from
from
my
perspective.
It
feels
like
we're
being
extremely
careful
about
rolling
a
feature
that
is
global
and
it's
not
it's
not
as
fragmented,
like
not
as
scopeable
as
our
usual
features.
I
feel
like
that's
where
the
care
and
concern
comes
from
so
anyway
anyway,
that
we
can
support
just
let
us
know
we'll
happy
to
jump
in
and
do
a
few
tricks
if
you
need
to.
D
All
right,
just
as
just
a
quick
fyi,
so
one
of
our
front-end
engineers,
tomasz
he'll,
be
borrowed
for
three
milestones
to
the
editor
group
to
help
out
with
an
effort
that
they
have
about
remote
development,
and
this
is
integrated.
There's
an
epic
there
describing
what
they're
trying
to
do
in
a
nutshell,
like
the
tlvr,
is
going
to
help
validate
the
technical
viability
of
having
the
web
ide
connect
or
remote
remote
dev
environment.
D
What
whatever
that
looks
like
there's,
also
the
web
id
vs
code
project
going
on
so
there's
a
bunch
of
things
that
tomasz
can
help
out
figure
out
he's
going
to
be
joining
other
people
in
editor
and
yeah
he'll
be
you'll,
be
focused
on
that
for
three
milestones,
but
he's
still
providing
some
backup
for
vs
code
as
we
onboard
more
people
on
to
that
stannislav.
I'm
looking
at
you
so
we'll
talk
about
it
for
15
too.
D
Probably
gonna
start
some
small
issues
to
get
started
there
and
that's
a
separate
topic,
but
yeah
we'll
still
be.
You
should
be
able
to
provide
some
support
there,
but
he
won't
be
focused
on
that.
His
focus
will
be
entirely
on
that
other
project.
D
Move
so
no
hires
will
be
done
so
again.
This
is
basically
a
focused
effort
of
validation.
If
you
remember
what
paul
slaughter
about
fia
wait.
B
Should
I
think
it
depends
on
what
the
outcome
of
that
like
effort
is
like
hamas
is
going
for
three
months
and
then,
depending
on
what
the
outcome
of
that
effort
is
that'll
help
the
product
team
figure
out
how
to
build
or
not
build
a
business
case
for
like
what
it
would
actually
take
to
staff
a
full
team
to
go
and
deal
with
this
on
a
long
term
basis.
D
A
I
just
wanted
to
remind
anyone
who
wants
to
post
feedback
on
the
sidebar
update.
The
sidebar
has
been
updated
on
merge
requests
on
gitlab
project,
there's
an
issue
with
a
ton
of
comments.
So
if
you
have
any
feedback,
please
post
them
there
and
also
kai
wrote
up.
Should
we
put
this
also
on
the
marketing
site,
and
I
just
thanked
phil
to
see
if
we
could
do
that.
A
I
was
waiting
for
the
the
sidebar
to
be
sticky,
which
it
now
is,
and
also
just
for
your
information,
I'm
still
working
on
the
sidebar
like
it's
it's
there,
but
it's
still
not
even
close
to
perfect
there's
so
many
changes.
We
still
need
to
make.
So
I'm
still
working
on
that.
B
Well,
thanks
for
the
update,
I
think,
all
of
the
as
clear
all
of
the
effort
and
thought
that
you
and
phil
have
put
in
there
has
has
been
well
and
the
feedback
is
generally
positive
and
minor
things.
I
think
it's
much
like
the
beautifying
effort,
where
we're
feeling
things
are
overall
good
and
there's
little
things
here
and
there
that
we're
we've
got
to
catch,
and
that's
that's
super
positive
to
see.
So.
Thank
you.
C
A
We
got
a
lot
of
feedback
that
people
do
miss,
seeing
certain
read-only
items
from
the
sidebar
across
other
tabs.
We
can
explore
adding
reviewer
and
assignees
potentially
into
the
header
in
some
way,
I'd
like
to
see
if
we
could
do
something
like
issues
due
with
that
sticky
header.
Maybe
we
could
put
some
of
that
information
up
there,
so
it's
always
available
in
a
small
little
bar
the
to
do.
Button
needs
to
move
out
of
the
sidebar
and
be
available
globally
again,
probably
in
the
sticky
header,
probably
the
tab
bar,
it's
already
sticky.
A
I
keep
saying
sticky
though,
and
I
don't
want
to
add
more
sticky
stuff,
so
I'm
also
playing
around
with
making
the
top
nav
not
sticky.
That's
a
huge
change
that
will
not
be
happening
anytime
soon.
Just
just
another
idea,
I
just
don't.
I
don't
want
to
have
all
that
fixed
stuff,
but
yeah,
I
think
we're
getting
close
to
having
it
maybe
available
more
globally.
It's
just.
It
needs
a
few
more
tweaks.
C
Yeah
thanks
thanks
for
sharing.
I
think
that
makes
sense.
That's
also
what
I
assume
would
be
the
issues
to
try
to
address.
I
think
it
will
be
challenging
at
least
the
first
one.
You
know
what
what
are,
what
are
the
items
that
people
miss
and
would
like
to
always
have
a
bill
available
in
other
tabs,
and
how
can
we
yeah
put
them
in
probably
the
header,
which
is
the
only
thing
that
is
common
across
all
tabs?
C
How
can
we
place
them
there
and
not
overloaded,
even
more
and-
and
you
know,
for
example,
assignees
and
reviewers,
I'm
just
thinking
upload,
you
know
those
two
things:
would
they
be
editable
or
not?
Only
re
read
only
yeah,
so
I
think
it's
very
interesting
challenge
to
solve.
Nonetheless,
I
think
the
big
the
biggest
benefit
I've
seen
with
this
is
the
change
itself
as
a
trigger
to
have
these
conversations
and
to
have
that
feedback
in
the
issue.
A
I
agree
especially
just
what
I
just
said
about
adding
fixed
elements.
It's
like,
I
don't
want
to
add
more
fixed
elements.
We
already
have
many,
so
can
we
remove
others
and
then
putting
the
to
do
button?
Do
we
need
to
move
the
to-do
button
globally?
Do
we
need
to
put
it
in
a
more
like
special
location
so
that
it's
the
same
across
all
pages?
Are
the
to-do's
kind
of
broken
yeah
like
do
we
need
to
deal
with
to
use
notifications
before
we
touch
all
this
kind
of
stuff?
So
it's
like
it
snowballs
very
quickly.
C
E
Yeah,
it
was
a
lengthy
recruiting
process
to
get
the
personas
we
needed,
but
invites
are
out
and
yeah
we're
getting
some
schedules
for
yeah
the
the
category
maturity
scorecard
for
the
editor
extension
that
will
start
next.
B
Week
since
we
have
like
I
don't
know,
30
seconds,
what
is
the
one,
is
it
all
internal
people
or
is
it
internal
and
external.
B
E
Page,
I
was
trying
to
read
it
all
carefully.
C
That's
okay.
We
had
the
same
question
a
few
months
ago
me
kai
and
I
think
adam
and
yeah.
We
weren't
sure,
because
there
was
there
was
some
contradiction.
It
was
ambiguous
about
at
this
level
of
maturity.
If
you
needed
internal
and
external
or
only
internal,
but
you
could,
you
could
do
only
internal.
I
think
that
was
a
conclusion,
but
external
is
is
even
better.
So
if,
if
we're
able
to
pull
that
off,
we
might
even
you
know,
jump
two
levels
of
maturity.
I
don't
know.
E
Yeah
and
yeah,
if
any
of
you
have
commentary
about
the
scorecard
process,
I've
also
been
asked
by
my
team
to
look
at
that.
I
haven't
done
it
yet,
but
it's
open,
I
guess,
for
debate.
If
there's
improvements
they're
talking
about
whether
or
not
this
can
align
with
a
benchmarking
process
that
we
do
since
they
are
pretty
similar.
B
Well,
thanks
everyone,
it's
great
to
see
everyone
enjoy
the
rest
of
your
week
and
we'll
chat
again
soon.