►
From YouTube: 2021-09-22 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
As
we
come
out
of
engineering
allocation
work,
which
it
feels
like
we're
getting
closer
and
closer
to
every
week,
then
we'll
start
moving
back
into
planned
work
or
previously
ideated
and
sort
of
feature
work
and
one
of
the
places
we
want
to
start
with
that,
and
what
we
had
you
know
it's
well
researched
and
designs
are
basically
done
is
what
we're
calling
attention
requests.
I
don't
know
if
that'll
be
the
file
name,
but
what
we
need
in
order
to
understand
that
work
and
then
prioritize
it
against
sort
of
everything
else.
A
A
But
anyways,
so
we
need
someone
we
need.
We
need
engineers
to
break
this
down
and
come
up
with
a
list
of
issues
and
get
them
attached
to
this
sort
of
the
epic,
so
we
can
get
weights
and
start
roughly
planning
timelines.
So
the
ask
is,
while
we're
still
in
engineering
allocation,
while
everyone
is
very
busy,
do
we
think
we
have
time
to
sort
of
have
someone
from
back
end
and
the
same.
A
Ask
this
for
andre
someone
from
front
end
to
start
looking
at
this
and
breaking
it
down,
so
we
can
get
those
issues
created.
I
think
there's
some
comments
in
here
already
in
both
the
issue
and
the
epic
that
provide
like
high
level
overviews
but
specific
issues,
I
think,
would
be
good
and
we
want
engineers
to
have
some
stake
in
this.
In
terms
of
looking
at
the
work
asking
any
questions,
they
have
up
front
making
sure
that
we're
addressing
concerns
and
have
answers
to
those
questions.
So
we're
not
stuck
later
or
we
don't.
A
B
Seems
reasonable,
yeah
yeah,
I
looked
it
over
a
little
bit
yeah,
it
must
been
before
me
or
it
was
around
when
I
started.
I
think
this
couple
months
is
when
we
we
brought
it
up
again.
It
was
in
july,
but
the
initial
thing
was
before
that,
but
yeah
it
seems
yeah
seems
reasonable
that
we
could
have
somebody
start
kind
of
looking
at
it
and
breaking
it
down
and
look
at
the
epic
too
closely,
but
there's
so
many
couple
issues
in
there
already,
but
I
think
it's
mostly
just
the
planning
parts
of
it.
A
Yeah,
I
think
there
were
there's
like
two
issues
that
are
in
there
that
sort
of
are
ideas
and
not
necessarily
implementation
issues,
and
then
one
of
the
issues-
that's
still
there
is
the
one
that
says
like
would
be
the
issue
that
you
would
assign
for
like
planning,
if
you
needed
to
assign
it
in
that
way,
but
yeah.
C
A
Perfect
yeah,
I
think
everyone
should
have
all
the
access
and
there's
a
ton
in
here.
This
will
also
be
good.
I
think
sun
jun
had
done
a
lot
of
the
work
on
this
too
and
so
be
able
to
consult
her
as
well.
If
we
need
to
probably
if
there
are
some
unclear
things
still
so
cool
and
I
think
the
ex
the
ass
from
us-
and
we
can
figure
this
out
in
engineering
fourteen
fours
effectively
just
started
it's
a
few
days
in.
A
A
So
potentially
we
would
start
working
on
this
in
14
5,
but
that's
also
pending
caching
work
and
merge
ability,
work
and
work
in
progress.
Draft
work
that
all
also
needs
to
be
like
wrapped
up
that
is
related,
but
not
engineering
allocation
work,
and
so
we,
we
sort
of
just
need
to
know
how
much
we
could
fit
this
in.
So
ideally,
we'd
like
to
potentially
start
on
something
in
14.5,
but
but
we
need
to
know
what
that
looks
like.
So
we've
got
basically
the
milestone
to
get
it
broken
down.
B
Yeah,
that
sounds
good.
It
kind
of
goes
something
I've
been
thinking
about
too,
is
trying
to
get
more
of
these
issues
investigated
early
before
the
week
of
the
milestone
starts
or
the
week
before.
So
this
is
a.
This
will
be
a
good
case.
Study
of
that
because
sounds
like
I'm
not
sure.
Maybe
we
used
to
do
that
a
little
bit
better.
B
C
This
is
a
theme
coming
up
in
the
technical
writing
team
as
well.
You've
been
mostly
shielded
from
it
because
you're
on
engineering
allocation
we
weren't
doing
anything,
so
I
didn't
have
to
tell
you
about
it:
they're
trying
to
figure
out
what
it
would
take
to
turn
the
team
from
reactive
to
proactive
and
step.
One
is
starting
to
examine
issues
like
these,
so
as
we're
starting
to
work
out.
How
should
this
work
for
this
team?
C
Because,
let's
just
say
that
when
they
ran
the
numbers
of
planned
versus,
unplanned
my
manager
just
about
had
a
heart
attack
for
for
14.3,
because
I
had
the
about
the
usual
amount
of
work
and
nothing
was
planned
anyway.
A
Yeah,
I
think,
as
we
come
out
of
engineering
allocation
and
as
we
get
back
into
a
more
regular
rhythm
of
planning,
we
probably
do
need
to
revisit.
A
What's
up
next
and
what's
not,
we
haven't
it's
been
several
months
now,
since
we've
thought
about
more
than
next
week,
so
we'll
have
to
revisit
that
as
well,
but
yeah.
This
is
sort
of
a.
This
is
one
of
those.
This
is
a
huge
huge
one,
which
is
why
we're
bringing
it
up,
but
yeah.
B
So
I
could
talk
a
little
bit
yeah.
Like
I
mentioned,
we
have
one
infrared
of
issue
left
that
one
hopefully
will
get
merged
in
the
next
day
or
two
here,
there's
an
mr
that's
in
maintain
a
review
now,
so
that's
good
and
then
our
air
budgets
are
green
for
now
at
least
there's
some
discussion
and
confusion
about.
B
What's
the
next
step
for
error
budgets
and
those
if
they're
going
to
be
tuning
them
back
from
five
seconds,
the
threshold
back
lower
or
if
we
have
control
over
that,
so
that's
still
ongoing,
but
at
least
for
now
they're
green
for
the
first
time
in
months.
I
don't
know
since
that
dashboard
was
created.
I
think
so,
that's
good!
So
yeah,
then
the
question
is
on
something
I've
been
talking
to.
We
talked
about
it
a
little
bit
in
the
engineering
allocation
meeting
yesterday
kind
of
how
do
we
what's
the
next
steps?
B
How
do
we
get
out
of
this
so
yeah
that
that's
a
hot
topic,
so
I'm
working
with
darva
on
that
this
week?
We've
had
a
couple
conversations
about
it
already,
but
yeah,
probably
yeah.
There's
not
it's
not
well
defined.
We'll
say
that
it's
the
process
for
for
exiting,
partly
because
there's
not
we
never
really
defined
like
exit
criteria.
So
we've
just
been
going
on
the
assumption
that
exit
criteria
means
finishing
informative
issues
and
error
budget
work
which
we're
close
to.
So
that's
good.
A
I
was
gonna
say
I
saw
your
response.
A
B
Yeah
right,
the
the
best
I've
been
able
to
figure
out
is
when,
when
so,
there's
that
epic,
that
I
link
to
here
when
that,
when
everything
in
there
is
done,
then
we
can
create
an
mr
to
just
get
us
off.
That
list
seems
like
it's,
not
very
official,
but
we
couldn't
do
that.
So
I
was
planning
on
just
doing
that.
B
I
guess,
but
and
then
seeing
what
christopher
and
others
have
to
say
about
that,
but
yeah,
it's
yeah,
the
that
was
kind
of
the
message
that
I
got
when
I
had
been
asking
around.
It's
just
yeah
once
once
because
there's
a
column
in
the
on
the
handbook
in
the
engineering
allocation
section
that
says
like
the
criteria
or
something
and
ours
just
links
to
this
epic,
and
so,
when
we're
done
with
that,
then
I
been
thinking
that
will
be
the
end
of
this
engineering
allocation.
B
B
So
I
just
wanted
to
be
a
little
proactive
that
in
case
we're
asked
about
it
have
we
know
we
know
what
the
status
is
at
least,
but
that
focus
is
mostly
on
like
s1
and
s2
issues.
B
A
Yeah,
I
think
that
makes
sense.
I
think
it's
it's
good
to
get
back
on
the
security
ones.
I
know
we
had
bumped
sort
of
milestone
over
milestone.
We
bumped
a
lot
of
those
because
of
not
everything
gets
to
be
a
p1
yeah.
B
A
B
B
A
Yeah
and
I
there's
a
comment
on
that
issue
too,
I
think
we
just
need
to
figure
out
how
we
want
to
approach
addressing
those,
because
we
do
still
have
performance
and
we
have
we've
got
some
like
usability
bugs
that
have
creeped
back
in
lately
and
that
we're
going
to
need
to
start
dealing
with
again
as
well,
so
we'll
just
have
to
figure
out
a
balance
for
those
and
and
maybe
be
firmer,
on
keeping
those
s3s4
security
issues,
and
then
we
happen.
Historically,
that's
fine.
B
A
Time
and
enjoy
the
rest
of
your
week,
I'm
off
thursday
friday
this
week,
fridays,
friends
and
family's
day.
So
I
assume
everyone's
off
so
I'm
off
tomorrow,
but
I'll
be
back
on
monday.