►
From YouTube: 2022-09-28 Code Review Weekly
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
I
think
Pedro
had
the
first
read
only
he
has
a
coverage
issue,
he'll
be
out
for
a
while
family
needs
anything
go
to
the
coverage
issue
or
I.
Guess
we'll
go
find
Annabelle
Amy's
got
the
the
next
one,
which
is
also
read
only
we'll
just
she'll,
also
be
out,
and
then
Matt.
A
Let
us
know
about
the
last
read
only
which
is
there's
a
new
help:
code
review
label.
I
think
this
is
a
new
support
process.
I
had
seen
it
before,
where
they
like,
instead
of
coming
into
a
slack
Channel
asking
for
something
they
now
create
an
issue
and
tag
us
to
ask
for
something:
I
guess
we'll
see
how
this
goes
and
yeah
I
subscribed
to
the
label
and
moved
to
see.
A
Fourth
is
a
sort
of
read
only
because
now
this
is
sort
of
picked
up
so
I'll
just
blow
these
through
this
one
too,
which
is
the
triaging
of
bugs
older
than
three
years
it
seemed
like
it
had
slowed
down
and
I.
Guess
it's
maybe
cyclical
with
like
the
Milestone,
like.
Maybe
people
did
it
at
the
beginning
of
the
Milestone
and
then
towards
the
end.
We
we
trailed
off,
but
over
the
last
week
or
week
and
a
half,
it
seems
like
a
bunch.
A
More
issues
have
been
checked
off
the
list,
so
I
think
progress
is
going
well.
I
think
we've
got
like
another.
We've
got
this
all
of
15.5,
and
you
know
the
first
couple
weeks
of
15
6
to
get
through
a
lot
of
the
list
and
we're
probably
we're
over
halfway
there.
So
yeah
I
think
it's
good
progress.
So
far.
A
Mn5
is
sort
of
the
first
of
the
big
discussions
and
I
want
to
plant
this
idea,
because
if
we're
gonna
do
something
in
Q4,
we
need
to
to
start
discussing
it
now,
and
so
performance
is
coming
back
around
in
sort
of
various
ways
to
us,
I
think
and
there's
nothing
as
direct
as
we
get
as
we
had
sort
of
the
last
time
we
looked
at
this
effort,
but
there's
a
lot
of
I.
A
Think
little
things
and
virtual
scrolling
is
starting
to
feel
like
it's
degraded
in
some
ways
and
some
use
cases
that
makes
it
not
a
great
experience
and
then
just
general
usability
and
focus,
and
so
I
don't
know,
what's
feasible
for
Q4
I.
Actually,
don't
think
I
want
to
put
something
on
the
books.
It's
like.
Oh
we're
going
to
accomplish
XYZ,
but
I
think
we
should
expend
a
significant
amount
of
time.
A
Researching
and
potentially
implementing
in
Q4,
if
that's,
if
that
makes
more
sense
like
if
we're
gonna,
do
something
in
Q4.
What
are
the
things?
What
are
the
research
paths
we
need
and
like
how
much
space
do
we
need
to
allow
for
those
research
paths
in
terms
of
like
engineering
effort,
I
say
that
also
knowing
that,
like
will
likely
have
some
of
the
restructuring
effort
Landing
in
Q4
that
we'll
need
to
start
working
on
as
that
comes
out
of
research
and
design,
and
so
like
there
is
a
work
stream.
A
That
also
will
be
happening.
That's
pretty
significant!
Thank
you
for
is
tough,
because
people
go
on
lots
more
holidays
than
than
they
normally
do
too.
A
So,
like
we're
shorter,
shorter
on
capacity,
so
it
might
be
a
good
researchy
time,
but
that's
so
that's
my
that's
my
start
of
like
what
do
we
need
to
do
now
to
be
in
a
position
to
like
have
those
things
in
Q4
and
like
how
much
space
should
we
be
making
in
15.5
there's
not
really
space
to
be
made,
but
like
early
15-6
to
like
give
people
time
to
think
about
these
ideas
so
that
when
they
come
to
Q4,
they
can
actually
spend
time
researching
a
particular
area,
and
then
how
do
we
coordinate
that
across
front
end
and
back
end
to
make
sure
that
we're
not
doing
not
that
the
last
effort
wasn't
great,
but
that
we're
not
doing
like
a
front
end
Focus
thing
and
a
back
end.
A
Focus
thing
like:
how
do
we
get
a
better
like
here's,
some
things
we
think
we
can
do
in
the
back
end
that
we
need
the
front
end
to
like
help,
support
us
on
or
the
other
way
like
the
front
end,
we
could
do
X,
Y
and
Z
if
we
had
this
from
the
back
end
like
how
do
we
sort
of
make
sure
that
we're
thinking
about
both
sides
of
the
puzzle
as
we
go
into
this
and
then
I
will
stop
no.
B
That's
great
thanks
for
mentioning
I'll
Briefly
summarize
what
Santa's
approach
he
has
some
ideas
about:
writing
on
a
more
complete
content
for
streaming
things
like
initial
and
lots
of
streaming
on
the
plugin
stream
streaming,
rendering
components
on
the
front
end
I
was
under
the
impression
that
there's
a
couple
of
blockers
in
terms
of
like
compatibility
with
film
components
you
might
want
to
dig
around
to
see.
Do
we
have
a
clear
path
for
implementation,
or
is
there
any
hurdles?
B
B
We
also
need
this
if
we
go
to
streaming
route
and
so
there's
a
couple
of
discussion
there
for
the
navigation
on
that
issue,
with
possible
solutions
live
Road,
do
we
have
server-side
rendering
we
well
I,
think
he
means
using
rails
templates,
not
JavaScript,
server-side,
rendering
we
do
have
a
proof
of
concept
and
try
to
dig
that
down.
B
B
We've
got
some
hurdles
a
little
like
shipping
that,
because
that
requires
a
note
server.
The
one
that
that
status
live
is
talking
about,
doesn't
require
node
server,
but
it's
more
limited.
It's
basically
like
a
rails
code,
server-side
rendering
the
parts
that
we
need
I
think,
but
we
we
I
can
I
can
help
him
and
support
him.
I
have
a
101
with
him
tomorrow.
B
I
can
drill
deep
in
hear
what
it
means
and
try
to
find
a
way
forward,
see
for
a
block
or
anything
but
but
yeah
I
think
we're
I
think
you're
right
on
the
money
about
us
trying
to
talk
about
this
as
soon
as
possible.
So
we
can
have
a
cool
picture
of
what
we
should
build.
B
Yeah
there's
a
couple
of
discussions
from
other
groups
that
I
want
to
get
on
top
of
now
that
I'm
back
I
heard
some
things
about
people
leveraging
index
DB.
Remember
that
research
that
Thomas
Randolph
did
a
couple
of
years
ago
or
a
couple
months
ago
or
index
DB
client-side
caching,
more
structure,
there's
some
possibility
that
that
can
be
reused
to
have
good
impact
on
data
loading
and
like
immediately
getting
all
the
data
rendered.
B
C
B
Help
sure,
thanks
from
my
perspective,
I
think
that
once
we
have
pocs
and
everything,
definitely
the
user
research
will
be
part
of
validation,
of
that
to
make
sure
that
we
don't
miss
anything.
But.
B
I,
the
part
of
the
restructuring
of
the
merger
Quest
definitely
will
have
its
own
validation.
I.
Think
that's
part
of
the
violation
of
the
concepts
for
the
implementation.
I,
don't
think
we'll
have
really
need
it
ahead
of
time,
preemptive,
research
or
like
once,
we
build
it,
but
I
think
before
it's
been
into
how
it
goes,
but
maybe
even
if
we
have
a
complete
concept
and
I
want
to
run
those
do
some
testing
so
we'll
keep
you
in
the
on
the
think
of
you.
If
you
ever
need
I
guess.
E
Is
on
that
sorry,
I
was
just
going
to
add
that
yeah
I
agree
with
what
you
said
in
there
and
Maybe
one
possibility
is
to
have
some
of
these
enhancements
behind
a
feature
flag
or
in
some
way
that
we
can
then
ask,
even
if
it
is
internal
users
to
test
drive
either
on
gitlab.com
or
in
another
instance,
with
a
large
merge
requests
or
something
like
that,
just
to
get
people's
feedback
and
impression
from
real
usage
so
but
yeah
it
will
depend
I,
guess
on
what
we
do
and
how
well
we
can
test
it
with
the
fewest
resources
possible,
but
I
think
yeah,
putting
this
in
hands
of
more
people
that
are
outside
of
this
group
before
we
release
something
I
think
that
would
be
great.
B
Definitely
makes
sense
moving
on
to
my
point,
if
somebody
has
any
other
sub
points
here,
cool,
so
we've
talked
about
this
in
the
past
and
I
always
feel
like.
We
make
some
advancements
on
the
calls
and
then
kind
of
just
lingers
to
have
any
movements.
B
We
don't
have
any
movement
for
a
while
and
I've
been
thinking
whether
well,
we
just
had
the
experience
of
the
working
group
for
the
marketplace
report
widgets
I'm
not
proposing
to
set
up
a
working
group.
That's
not
what
I
mean
with
that
repeating
weekly
discussions,
so
I
think
we
can
try
or
I
was
wondering
if
it
would
be
useful
to
have
like
set
up
a
call
with
aim
that
ICS
to
discuss
this
potential.
B
Poc
Concepts
invite
the
pack
anyic
link
by
the
front
and
I
see
even
have
them
go
at
it
and
see
what
they
come
up
with
as
a
ground
up
idea
of
brainstorming
exercise,
so
I
I
could
set
that
up.
If
somebody
has
any
objections,
I
know
they
will
take
a
bit
of
time
from
there,
but
I'm
thinking
about
I,
don't
know
30
minutes
to
an
hour
each
week
in
the
afternoon
of
Europe,
so
we
can
have
the
the
US
people
in
China
and
then
we
can
see
if
nobody
shows
up
after
two
weeks.
B
D
I,
like
Kai
verbalize,
his
point
I,
think
sure
I
I
think
I
have
the
same
point
as
him,
but
I'll.
Let
him
explain.
First,.
A
I
think
it
relates
to
potentially
0.6
about
trying
to
figure
out
how
we
increase
collaboration
on
the
team,
anyways
I
think
the
challenge
is
probably
overlap
of
team
members
and
whether
or
not
people
have
enough
interest
and
time
to
like
set
aside
half
an
hour
an
hour
every
week
which
I
don't
I.
Don't
know
if,
like
that,
on
top
of
what
we
already
have
planned
is
like
feasible
and
I
know
two
of
the
back
end.
Engineers
are
in
aipac
so
like.
A
So
I
think
like
that
it
could
be
that
we
needed
like
two
of
them,
which
may
just
mean
that,
like
doing
something,
sync
is
not
necessarily
appropriate
yet,
and
maybe
we
should
do
that
like
in
Q4,
but
I,
don't
know
worth
a
shot
either
way.
I
think
I
think
we
can
try
it,
but
just
be
aware
of
that.
D
Yeah,
that's
what
I
was
thinking
about.
Yeah
I,
don't
want
to
exclude
the
APAC
back-end
team,
which
is
Patrick
and
David,
because
I
think
they
would
probably
have
a
lot
to
to
add
to
this
conversation,
but
I
think
we
do
I
think
they
would
be
happy
to
have
a
synchronous
call
if
we
can
find
find
a
time
that
works
and
I.
Think
yeah,
I,
don't
think
capacity
for
a
you
know
or
meeting
or
whatever
it
is,
should
be
a
problem,
at
least
in
the
back
end.
B
Okay,
no
that
definitely
makes
sense,
I,
think
you're,
right,
I,
think
you're
onto
something
Kai
there
that
may
be
starting
right
away
with
only
sync
might
not
be
the
best
way,
but
we
start
you
can
think
of
a
format
where
we
give
a
heads
up
when
we
ask
people
to
have
to
crazy
ideas
in
the
upcoming
days.
To
the
meeting
then,
have
an
alternative
alternate
schedule:
try
to
make
try
to
find
something
that
is
includes
it
for
everybody,
yeah,
we'll
give
it
a
shot.
B
Will
kill
it
when
somebody
yeah
the.
E
The
reason
I'm
asking
is
because
I
think
that,
ideally,
we
would
include
ICS
from
other
groups
as
well-
not
everyone,
of
course,
because
we
have
to
control
the
amount
of
feedback
that
we
get,
but
I'm
sure
that
there
are
a
lot
of
great
people
around
the
company
that
have
had
great
experience
with
performance
issues
either
outside
of
gitlab
or
in
gitlab
itself.
So
I
think
just
keeping
this
within
our
group
is
kind
of
I.
Think
it's
a
missed
opportunity
in
terms
of
finding
ideas.
B
B
Factors
probably
are
of
other
people
like
that,
so
we'll
we'll
get
the
the
center
of
the
focus
on
our
team,
but
openly
for
everybody
who
wants
to
join.
Put
it
on
front-end
calendars.
Put
it
on
all
those
sort
of
things
to
make
it
visible
for
everybody
who
wants
to
join.
Make
it
clear
that
it's
open
for
everybody
wants
to
join
we're
not
going
to
be
requesting
feedback
through
an
issue
right
now,
just
because
that
would
be
a
very
like
a
swarm
of
feedback
without.
E
A
B
Of
knowledge
of
what
we're
trying
to
do,
but
yes,
we'll
include
that
in
the
setup
I'll
get
something
set
up
for
next
week
and
we'll
get.
E
B
E
Yeah
yeah
I,
think
that
makes
sense
and
in
terms
of
the
how
people
participate,
I
think,
at
least
for
me
when,
when
doing
these
things
a
mix
of
async
and
sync,
is
the
the
best
to
give
everyone
an
equal
opportunity
to
participate
and
doing
these
brainstorming.
And
you
know
Affinity
grouping
and
things
like
that
in
new
role
or
a
similar
tool
is
sometimes
more
effective
than
trying
to
do
that
inside
of
gitlab.
And
then,
of
course,
we
can.
E
We
can
take
the
discussions
more
detailed
discussions
to
gitlive
itself,
but
yeah
I
just
wanted
to
suggest
using
something
like
that
for
people
to
contribute
async
kind
of
a
boards
tool
and
and
yeah.
There
are
many
different
ways
to
approach
this,
to
be
the
most
effective
and
get
out
the
most
of
collaboration,
I'm
sure
that
yeah,
Ben
and
Marcel
and
Annabelle
can
help
you
set
that
up
to
make
sure
that
you
get
the
best
out
of
that
collaboration.
E
Mural
we
have,
we
have
seats
in
murals,
so
we
can
use
that
internally.
It's
usually
our
go-to
tool
for
this
kind
of
collaboration
and
yeah.
So
you
can.
You
can
use
that
okay.
A
Yeah
I
think
this
one
is
sort
of.
If
people
had
comments
they
wanted
to
Voice
or
discuss
further
than
outside
of
the
issue,
then
I
I
wanted
to
make
sure
they
were
space
to
do
that.
If
no
one
has
anything
outside
of
what's
already
written
on
the
issue,
then
I'll
take
a
look
at
it
later
today
and
figure
out
what
the
next
steps
are.