►
From YouTube: 2021-09-29 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
Yeah,
we're
excited
to
have
you
back.
Thank
you.
You've
got
lots
to
catch
up
on,
but
excited
to
have
you
back
all
right.
I
had
the
first
one
up
which
was
okrs.
A
This
is
a
little
bit
complicated
too,
because
we've
been
in
engineering
allocation,
but
we've
also
been
doing
some
work
related
to
these,
but
we
share
and
when
I
say
share,
I
don't
think
ally
really
lets
us
share
these
correctly,
but
the
okrs
that
are
assigned
to
me
are
mergibility
okr
the
merge
widget,
not
the
merge
report
widgets,
but
the
merge
widget
okr
and
the
error
budget,
okay,
all
of
which,
like
I
guess,
I
could
figure
out
how
to
report
on
easier
likely
for,
for
the
two
of
you
to
report
on.
A
But
mine
aren't
linked
to
yours,
an
ally,
and
so
they
all
say,
zero
percent,
and
so
I
wasn't
sure
if
anyone
was
actually
doing
anything
with
those
okrs
or
has
been
updating
them
or
if
we
have
a
way
to
figure
out
who's
like
responsible
and
updating
those,
because
I'm,
I
believe
both
of
you
and
I
know
at
least
matt-
has
them
also
assigned
an
ally.
Andre
you've
probably
got
similar
stuff
assigned
an
ally
as
well.
So
does
anyone
have
any
thoughts
on
this.
C
So
I
have
them
an
ally.
I
also
have
so
I
haven't
linked
to
a
gitlab
issue,
because
then
you
can
automatically
sync
ally
in
gitlab
if
you
put
like
checkboxes
in
the
gitlab
issue,
so
I
did
that
for
all
of
the
well,
not
the
widget
one,
but
for
error,
budgets
and
mergability,
and
so
then
I
just
tried
to
come
up
with
some
tasks
lists
in
gitlab
and
then
I
can
check
them
off
as
they
go
I'll
share
that
in
here.
C
If
when
I
can
find
it
but
yeah,
I
don't
know
like
the
air
budget,
one
for
measuring
it.
Like
we're
green,
we
we
met
our
goal.
So
is
that
100
done?
Is
there
more
stuff
we
can
do?
We
can
talk
about
that
in
my
update
here
in
a
little
bit,
but
it's
hard
to
hard
to
know
if
that's
like
other
okrs,
like
our
large
mro
okr,
it's
like
well,
we
set
a
goal
of.
C
It
was
actually
much
lower
than
99.95,
but
originally
I
think
at
the
start
of
the
quarter,
it
was
like
99.8
or
something
and
now
we
met
that
so
is
the
okr
done.
I
don't
know,
I
don't
know
how
to
measure
that
then.
So
I've
been
kind
of
measuring
like
okay,
here's
all
the
things
we've
been
doing
to
kind
of
get
us
there.
B
Yeah
and
my
my
perception
on
my
question
here
is
on
the
the
merge,
merge
request.
Widget,
we
do
have
one,
I
have
updated
it,
but
it's
it
needs
another
refresh.
I
haven't
checked
in
in
more
than
a
month,
but
they're
not
related
at
all,
but
my
question
is:
how
should
they
be
related?
Because
if
you
make
mind
the
parents
of
yours
or
if
make
mine
this
child
of
yours,
it
won't
be
a
darva's
anymore.
So
it's
like
how
do
we
handle
this?
B
A
Yeah,
it's
part
of
what,
like
I
was
trying
to
figure
out.
I
don't
think
you
can
update
mine
and
I
don't
think
we
can
do
the
complicated
relationships
that
we
need
to
for
shared
okrs
and
ally,
based
on
what
I've
seen
so
far.
I'm
wondering,
though,.
A
C
I
don't
think
so,
an
ally
when
you
set
it
up.
You
just
kind
of
pick
like
the
project
and
the
issue
you
have
to
like
search
which
is
kind
of
clunky,
but
you
when
you
find
it,
you
just
set
an
issue
and
then
it
automatically
syncs.
So
I
don't
know
that
it
cares.
If
it's
that
same
issue
is
linked
to
multiple.
C
A
Yeah,
that
might
be
good,
and
then
I
had
another
question,
which
was:
how
often
are
y'all
updating
sarah's
been
asking
like
every
week
or
every
other
week,
but
at
least
I
haven't
updated
anything
since
the
quarter
started,
and
so
I
I
just
so
we're
aligned
on
a
frequency
just
so
like.
She
knows
that
if
we're
only
updating
once
a
month
or
whatever,
then
then
that's
fine,
I
don't
have
a
preference.
B
C
Yeah
it's
I
do
darva
one
point
said
every
week:
I
don't
know
that.
I'm
doing
that
I,
but
because
I'm
just
updating
issues,
then
it
seems
a
lot
faster
that
I
don't
have
to
actually
go
into
ally
and
pick
a
number.
I
mean
it's.
I
check
a
box
and
I'm
done
so
that's
easy.
I
can
I'll
show
you
what
I'm
talking
about
here.
Yeah,
please
all
right!
So,
okay!
So
this
is
like
the
error
budget.
One
maps
to
this.
C
You
can
see
there's
this
little
git
lab
icon
in
ally,
so
it
syncs
automatically.
C
But
if
I
were
to
go
in
here
and
check
this
I'll
remember
to
go
back
and
uncheck
it
and
then
automatic
sync
it
it
just
will
tick
up
a
little
bit.
The
percentage
automatically
updates.
So
all
it
has
all
you
need-
is
to
have
a
list
of
check
boxes,
and
then
you
just
somehow
in
here
you
link
it
to
I
can.
I
can
share
dharma
created
some
videos
on
it,
but.
C
I
can't
remember
exactly
how
you
do
it,
but
basically
you
set
the
set,
how
it
gets
updated
and
you
just
set
it
to
gitlab.
So
so
now
I
unchecked
that
one,
so
it
should
go
back
to
75
now
yeah.
C
B
But
matt,
so
when
you
specify
the
data
source
it,
I
haven't
gone
through
the
whole
process
of
setting
that
up,
but
you
we
specify
a
connector
like
gitlab,
then
you
probably
give
it
a
link
for
an
issue
right,
mm-hmm
yep.
So
what's
your
suggestion
is
that
we
have
one
issue
for
these
joint
ones
that
we
just
keep
updated
and
then
theoretically
just
update
everyone
online.
Is
that
it?
I
think,
that's
what
kaya
was
suggesting.
B
Yeah
so
that
yeah
yeah
so
action
points,
I
can
take
the
action
of
creating
one
issue
for
tracking
the
ally.
Wrapping
up
the
merge
request,
merge
widget,
that's
the
one,
that's
falling
on
my
my
courtyard
and
then
matt
to
take
care
of
making
sure
that
the
other
ones
haven't.
We
shared
it
with
kai,
and
then
I
can
hook
it
up
with
his
ally.
Okay,
that
sounds
good.
C
Yes,
I
do
have
them
darva
created
a
bunch.
I
will
hunt
them
down
and
share
them.
I'll
put
them
in
the
agenda
here.
B
Or
if
you
give
me
a
second,
I
can
show
you
so
when
you
go
to
the
edit
editing
the
objective
progress
you
have
automatically
from
a
data
source,
I
think
wait.
It
worked
before
it
really
worked
before,
but
give
me
a
second
basically
showed
a
pop-up
and
I
just
had
to
write
gitlab
and
it
showed
me
the
connector
for
gitlab
you
make.
Let
me
just
cancel
this
I'll.
Do
it
again?
More
apologies.
I
thought
live
demos
would
go
well.
B
A
Yeah
it
popped
up
for
me,
so
I
can
there
we
go
fill
it
in.
I
would
not
share
your
screen
and
do
that
only
because
it
shows
at
least
for.
A
B
Okay,
but
yes,
it
should
be
straightforward
to
do
as
long
as
you
have
an
issue
prepared
for
it.
I'll
just
follow.
Can
you
have
you
put
the
link
in
the
agenda
for
that
issue,
that
you're
tracking?
That
would
be
useful.
B
C
B
A
Awesome
yeah:
I
will
try
this
as
well
and
we'll
see
we'll
see
if
this
gets
everyone
updated.
So
I
appreciate
the
conversation
on
it
so.
C
A
C
If
I
was
never
sure
like
what
to
put
in
that
in
the
issue
checklist
to
what
we're
actually
measuring
against
so,
if
we're
going
to
share
these,
then
we
can
definitely
review
revisit
the
checklists
of
things
that
I
have
and
edit
them
as
needed.
C
All
right
should
we
move
on
to
the
engineering
allocation,
or
is
there
more
thoughts
on
okrs
all
right,
the
engineering
allocation
so
we're
down
to
our
last
infradeb
issue,
which
has
been
merged
and
it's
in
verification
just
as
a
couple
days
ago.
So
it's
kind
of
making
sure
it
was
an
n
plus
one
error.
So
we
have
to
do
some
checking
to
see
to
verify
that
we
don't
have
that
problem
anymore,
which
involves
a
little
bit
of
manual
test
setup.
So
that's
what's
happening,
so
that's
good!
C
So
then
the
only
we're
not
sure
what
the
next
steps
are.
In
theory,
we
would
exit
the
engineering
allocation
shortly.
There's
a
couple
complicating
things
there.
One
is
there's
part
of
this
was
to
improve
our
error
budgets,
which
we've
done,
but
most
of
that
was
because
the
threshold
measurement
changed
and
now
we're
talking,
as
the
engineering
group
is
talking
about,
changing
that
back
or
back
either.
C
So
I'm
not
sure
if
that's
going
to
be,
we
added
this
feature
and
now
we're
going
to
change
everyone
back
to
one
second,
which
means
our
air
budgets
would
go
red
and
then
we'd
have
to
go
in
manually
to
certain
endpoints.
If
we
think
that
they
one
second,
is
too
short
and
add
some
code
to
see
to
change
that
threshold.
C
So
we're
trying
to
figure
out
they
just
kind
of
unknown
or
they're
in
the
process
of
making
that
change.
I
guess
they
they
made
the
back
end
change,
but
then
they
are
working
on
documentation
and
the
process.
Those
are
open,
mrs
right
now,
so
that's
happening,
there's
also
a
proposal
which
I
can
share
in
here
around
working
on
security
issues
as
a
next
step,
I'll
find
that
link.
C
So
we
have
some
security
issues,
but
not
too
many,
but
a
lot
of
other
things
in
create
and
dev
have
a
lot
of
open
security
issues
so
trying
to
decide.
There's
a
proposal
to
see
should
the
next
step
be
that
we
work
on
security
issues
and
help
either
work
on
ours
and
then
help
maybe
the
source
code
team,
so
that
is
potentially
a
next
step
too,
but
that's
still
being
discussed.
So
there's
nothing.
Nothing
final.
There.
A
Yeah,
I
don't
think,
there's
anything
else
on
the
yet
that
I
think
we've
talked
about.
I
left
a
comment
on
the
one
piece
that
you
mentioned
about
the
thresholds.
I
just
as
you
learn
more
just
please
keep
us
updated.
Yeah,
I'm
concerned
thresholds
will
magically
change
back
and
then
everyone's
error
budgets
will
slowly
go
around.
A
C
We
brought
that
sorry
to
interrupt.
We
brought
that
up
in
a
meeting
yesterday
with
steve
in
infrastructure.
It's
like
oh
yeah,
wouldn't
be
he
wasn't
super
clear.
It
wouldn't
be
like
a
critical
fcl,
all
of
a
sudden
that
we'd
be
in
because
our
air
budget's
dropped,
which
is
good,
but
I
would
worry
too,
that
would
be
like.
Oh
now,
your
air
budgets
are
red.
There's
a
new
engineering
allocation
that
has
to
happen,
and
everyone
has
to
focus
on
this,
but
that's
going
to
affect,
I
think,
there's.
C
Maybe
they
do
this
air
budget
report
monthly?
I
think
it
is,
and
the
last
one
was
at
the
beginning
of
september,
but
they
had
kind
of
sections
and
there's
a
section
that
we
were
in
that
had
about
10
or
15
groups
in
them
that
all
were
in
the
section
of
the
threshold
is
basically
going
to
move
them
up
into
the
green
section.
So
I
would
assume
all
of
those
groups
are
also
going
to
be
effective
if
they
change
the
threshold
back.
All
at
once,
so
actually
wouldn't
be.
C
All
at
once
would
be
like
over
28
days.
It
would
slowly
filter
in
because
that's
how
we
saw
went
up
a
little
bit
over
the
course
as
the
data
kind
of
backfills
over
that
time.
But
so
it's
going
to
be
a
problem
for
many
teams,
not
just
ours,
which
will
be
interesting.
A
You're,
fine,
I
think
we're
good
on
on
ea
stuff.
I
added
one
more
fyi
and
then
we
can
stop
recording
and
chat
if
we
need
to
the
last.
One
is
just
about
a
proposal
that
could
make
our
group
a
test
group
for
turning
on
the
end-to-end
test,
suite
inside
of
our
group's
merge
request
and
then
making
it
our
engineers
responsibilities
to
fix
potential
end-to-end
test
issues
if
the
merge
request
breaks
them.
So
we
just
if
you
have
thoughts
on
it,
feel
free
to
voice
them.
A
I
don't
know
how
far
this
is
moving
or
where
we're
at,
but
I've
left
a
comment
there.
So
you
guys
can
take
a
look.
I
know
andre
you
were
out
and
that
I
know
you've
been
under
ea
stuff,
so
we
haven't
really
looked
at
it,
but
it's
worth
worth
probably
thinking
about
before
we
get
roped
into
potentially
something
that
could
be
hard.
A
All
right,
I
will
stop
this.