►
From YouTube: 2021-08-04 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
Oh,
that's
new.
There's
a
few
read-onlys
at
the
top
about
vacation
time
off
for
people
they'll
make
it
a
bit
of
a
challenge,
probably
for
planning
for
14.3,
but
that's
all
right,
we'll
get
through
it.
B
Yeah
yeah
yeah
I've
finished
building
the
van
I'm
gonna
make
sure
that
I'll
post
some
pictures
when
it's
in
a
more
representative
location
than
just
in
the
garage
next
to
our
apartment,
building
and
yeah.
I'm
gonna
work
from
campus
I'll
see
how
that
goes.
It's
good
that
in
europe
you
can
have
unlimited
internet
around
the
whole
europe,
for
you
know
how
much
it
looks
70,
maybe
not
even
now,
it's
it's
50
50
for
unlimited
4g.
So
I'm
gonna
see
how
that
goes.
I'm
looking
forward
to
it!
I'm
gonna
be
online.
A
Number
two
is
engineering
allocation
impact,
so
currently
it's
up
to
100
david
has
an
openmr
to
bring
that
back
down
to
30,
which
is
like
an
actual
realistic
number
that
the
group
could
achieve,
especially
given
that
40
percent
of
our
engineering
capacity
is
front-end
engineers
who
can't
actually
impact
sort
of
engineering
allocation
work
and,
and
then
we
have
other
things
that
we
we
legitimately
have
to
do
outside
of
this,
and
so
we're
trying
to
bring
that
back
down
to
30..
A
I
know
there's
a
few
issues
in
flight
now,
and
hopefully
it
won't
impact
too
much
of
our
capacity
for
like
the
work
that
we're
actually
planning,
which
is
all
in
the
same
vein
of
this,
so
just
just
bringing
that
back
up
in
case.
Anyone
has
any
more
questions
on
it.
C
I
think
30
is
a
reasonable
amount.
I
think
that's
a
good
balance
between
helping
out
with
these
production
incidents,
which
is
why
this
came
up
and
then
also
keep
working
on
our
the
current
stuff
that
we
had
planned,
which
also
relates
to
it
performance
and
reliability
and
which
is
stuff
that
we
had
planned
on
doing
anyway.
So
it
wasn't
like.
We
were
totally
taken
by
surprise
that
we
needed
to
focus
on
some
of
these
performance
reliability
things.
Those
are
things.
We've
been
working
on
and
plan
to
keep
working
on.
So
that's
good.
A
Cool
and
then
oh.
D
Yeah
hi
everyone
yeah
just
a
question
about
where
the
the
rest
of
the
allocation
will
go.
A
We
have
some
of
this
is
like
a
weird
math
problem.
Where
we
have
eight
engineers,
we
used
to
have
nine,
so
we
and
three
or
four
of
them
are
from
it.
So
three
were
are
now
front
end
engineers,
so
three
of
eight
is
some
percentage.
My
math
is
off.
The
top
of
my
head
for
eights
is
not
very
good.
That's
like
37.
A
Yep
yeah,
so
so
that
takes
40
percent
off
of
it
right
away
so
like
because
in
theory
they
don't
do
engine
none
of
the
engineering
allocation
work,
that's
defined
as
front-end
related
at
this
time.
So
that's
part
of
it
and
then
the
rest
is
that
we're
doing
the
we
have
whatever
security
issues
we
have.
We
have
whatever
bug
fixes
that
we
need
to
do
like
our.
We
have
a.
A
We
still
have
like
a
decent
number
of
s2,
bugs
that
come
up
on
a
fairly
regular
basis
that,
like
take
into
account
usability
in
how
the
thing
works
and
those
are
still
important
to
do.
We
have
security
issues
and
those
things,
and
so
that's
sort
of
where
the
other
percentages
go
is
into
the
regular
work
that
we're
doing
we're
also
still
doing
our
merge.
A
The
mergiability
work,
which
is
in
the
same
vein
of
this,
but
not
explicitly
labeled
along
the
lines
of
this,
and
so
like
that's
part
of
the
capacity.
So
it's
not
that
we're
nothing's
really
changing
with
what
we're
doing
we're
just
trying
to
be
more
explicit
externally
outside
of
the
group
to
what
we're
we're
doing
by
picking
a
percentage
that
is
more
reasonable,
yeah
even
30
percent
seems
probably
high.
But
if
we
count
the
mergibility
work
as
part
of
this
work,
then
it
makes
it
easier
to
say
that
it's
30
percent.
C
A
Yeah
error
budgets
is
the
other
one
that
counts
this,
so
we
were
already
working
on
error,
budgets
and
mergibility
for
q3,
like
those
were
the
focuses
so
like
it's
really
just
saying
explicitly.
This
is
how
much
we're
dedicating
two
and
a
half
engineers
to
those
things
which
we
already
said.
We
were
going
to
do.
A
No
all
right,
the
last
one
is
143
planning
will
need
to
be
finalized
next
week.
I
am
conveniently
gone
next
week.
A
I
think
I'll.
I
I
say
that
I,
although
I
will
be
gone,
I
think
we
know
sort
of
everything
that's
going
to
fit
into
the
milestone
are
all
the
themes
that
need
to
fit
into
the
milestone.
A
On
the
back
end
and
front-end
side,
there
may
be
pockets
of
things
that
we
don't,
but
if
everyone
can
handle
that
and
then
when
I
get
back
on,
the
16th
they'll
probably
get
kickoff
done
if
it
needs
to
get
done,
although
we
may
not
do
that
this
another
milestone,
but
if
we
can
just
make
sure
that
it's
mostly
wrapped
up
by
the
end
of
next
week,
I
just
won't
be
here
to
do
meetings
to
go
through
the
the
board
and
make
sure
it's
done.
A
Yeah
pedro,
I
will
because
my
plan
before
the
week
is
up
to
give
you
give
you
the
rest
of
that.
D
Cool
cool
I
mean,
if,
if
you
don't
I'll
I'll
I'll
pick
it
myself,
so
if
you
just
tell
me,
oh
unfortunately,
I'm
not
gonna
have
the
time.
Yeah
you
pick.
I.
I
won't
have
a
problem
with
that.
Okay,.