►
From YouTube: 2022-06-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
Hi
everyone
weekly
for
code
review.
The
first
point
I
have
here
is
just
I
wanted
to
have
a
brief
discussion,
and
this
is
very.
This
is
very
loose.
But
this,
I
feel
like
there's
multiple
threads
of
interest
in
this
topic,
and
I
wanted
to
kind
of
like
since
we're
preparing
for
for
a
string
of
less
available
from
from
ukai.
A
I
wanted
just
to
like
get
everybody
on
the
same
page,
so
there
seems
to
be
a
consensual
struggle
with
the
current
to
do's,
not
just
within
code
review,
but
we
think
it
as
a
whole,
and
I
wanted
to
check
if,
if,
if
we
have
any
particular
plans
taking
shape
that
we
can
prepare
for
or
if
we
can
start
talking
about
cosmetic
updates,
like
just
like,
we
did
for
the
beautifying
ui,
just
kind
of
tweaking
the
current
to
do's
into
shape
or
if
we
were
preparing
for
a
major
overhaul
yeah.
A
That
was
kind
of
my
question.
What
are
the
threads
that
are
currently
ongoing
and
is
there
anything
that
we
can
do
to
prepare
for
for
to
help
in
this?
In
this
regard,
I
know
that
they're,
not
within
our
code
review
team,
they're
kind
of
like
stale
or
sitting
down
not
being
prioritized
in
other
groups
but
yeah
any
thoughts
there.
B
That's
a
good
question.
I
have
a
meeting
right
after
this
about
to
do's,
okay,.
B
About
to
do's
as
well
sort
of
kind
of
here's,
what
I
I
mean,
maybe
this
is
the
best
way
to
say
this.
There
is
nothing
concrete
that
we're
thinking
about.
I
think
what
we
do
need
to
do
is
put
together,
probably
like
some
ideas
that
we've
got
and
things
that
we
think
we
can
do
that.
Aren't
that
aren't
so
big
that
we
need
to
go
talk
to
gabe
and
plan
and
the
whole
company
integrations
and
all
these
other
people
the
whole
company
and
sort
of
what
are
the
things
we
can
do.
B
We
started
having
all
these
conversations
during
attention
request
pieces
and
we
came
out
of
attention
requests
sort
of
saying.
We
think
we
want
to
do
something
small
here,
but
we
we
don't
have
anything
concrete
and
we
haven't
put
any
issues
or
proposals
together
so
that
I
would
say,
there's
nothing.
B
Super
concrete,
yeah,
an
anabolic
terror
issue,
so
I
I
think
we
need
to
spend
some
time
in
design
and
research.
Maybe
I
don't
know,
but
this
is
probably
a
good
question
for
you.
Annabelle.
C
C
Can
we
just
try
anything,
and
I
just
think
that
the
first
not
simple,
because
we
don't
store
notifications
right
now
in
the
database,
but
the
most
obvious
step
to
get
to
like
a
complete
notification
experience
would
be
to
store
them
in
the
database
and
show
them
with
the
to-dos.
So
every
email
notification
that
you
get
you
can
see
it
in
the
current
to-do's
area.
C
So
my
proposal
is
to
do
that,
rename
it
notifications
and
remove
the
word
to
do
from
the
entire
product
and
basically
change
it
into
notifications,
and
then
it
would
be
like
a
really
basic
experience
where,
if
you're
looking
notifications
so
and
so
mentioned
you-
you
click
on
it.
When
you
go
to
that
issue
or
whatever
it
is,
there's
a
button.
That's
like
scene,
so
kind
of
like
the
mark,
as
done
right
now
to
do
as
a
concept
is
really
useful,
but
ours
are
not
to
do's.
C
So
then
I
open
this
other
issue
for
a
dashboard
where
maybe
you
can
create
a
proper
to-do
list
where
you
can.
You
know,
create
a
list
link
into
issues
and
it
doesn't
show
up
in
the
activity
in
the
way
that
it
does
now.
It's
just
your
personal
to-do
list,
and
maybe
maybe
on
every
page
there's.
You
know
like
added
to
do
from
the
ellipsis
icon
and
everything
like
that.
But
anyway,
I
think
that
we
need
to
rename
it
notifications,
remove
to
do's,
put
it
behind
a
feature
flag
and
see
what
happens.
B
Yeah
I'll
say
adding
on
to
that,
because
I
mentioned
my
meeting
after
this
is
with
grant
to
talk
about
slack
notifications,
which
is
another
huge
piece
of
this
that,
like
we
probably
need
to
be
very
cognizant
of,
which
is
why
this
gets
very
messy
very
quickly,
and
my
I
will
say
my
very
first
question
to
grant
is:
why
do
people
use
the
slack
integration?
B
If
people
have
a
different
notification
experience
in
slack
than
they
do
in
gitlab,
like
that's
just
sort
of
problematic
across
the
board,
so
yeah,
I
think
I
I
think
that
just
points
to
there's
a
lot
of
conversations
that
we
need
to
have,
and
I
think
it
I
think
it's
fair
to
just
create
proposals
or
issues
and
and
work
with
pedro
and
annabelle
and
figure
out
like
what
makes
sense
to
do
and
what
is
so
big
that
we
don't
want
to
do.
B
The
thing
that
I
don't
want
to
inadvertently
do
is
commit
us
to
owning
to
do's
by
accident.
So
if
we
make
a
substantial
change
potentially
like
the
one
annabelle
is
proposing,
someone
might
decide
that
we
now
own
to-do's
and
we
will
yeah.
We
will
get
it
for
life
and
need
to
spend
lots
of
capacity
on
that,
and
maybe
not
other
things
that
we
think
we
need
to
be
working
on.
So
we
need
to
be
mindful
of
the
get
labs
as
amy.
So
correctly
pointed
out,
you
break
it.
C
If
we
did
manage
to
do
that,
just
just
showing
notifications
in
the
to-do's
area
and
basically
the
rough
outline
of
what
I
proposed
there,
there
are
so
many
people
who've
contributed
to
this
issue
and
all
the
other
issues
like
gabe
is
already
aware
of
this
and
mildly
on
board.
I
think
it
was
hard
to
kind
of
gauge
and
then
matthew
on
the
design
team
has
done
all
kinds
of
stuff
on
that,
and
we've
been
kind
of
going
back
and
forth
on
some
ideas,
so
it
already
feels
a
little
bit
more,
not
global
crosstalk.
A
C
A
A
Because
we
just
had
just
had
an
experience
about
the
a
very
hot
contentious
area
of
co-owned
code,
which
is
the
widgets
one
of
the
experience
we've
had
with
the
report.
Widgets
is
that
it
was
an
example
of
an
area
that
many
groups
have
invested
interested
on,
have
code
code,
that
they
wrote
themselves
and
then
we
were
able
to
get
them
on
board
into
writing
a
cohesive
code
base
to
follow
an
architecture
that
we
proposed.
A
I
don't
know
if
that's
a
model
for
to
do's
or
not,
but
what
I
like
there
was.
There
was
a
full-on
ux
research
effort
at
the
front
identified
all
of
the
needs
that
all
the
groups
had
and
came
up
with
the
framework
that
it
addressed
all
those
needs.
So
by
the
time
that
we
were
brought
in
onto
onto
the
the
picture,
he
was
implementing.
A
That
framework,
with
help
from
those
engineers
that
model
worked
remarkably
well
from
my
perspective
in
terms
of
like
I
don't
need
to
during
implementation,
going
to
check
what
the
groups
need,
so
that
that's
definitely
adding
value
to
this
exploration
of
ux
and
up
up
front
so
yeah.
I
wanted
to
share
that
in
case
it's
meaningful
for
this
particular
point.
A
The
ownership
can
be
kept
where
it
is
right
now,
but
we
can
help
multiple
groups
contributing
to
a
whole
process
through
the
process
of
a
working
group.
So
maybe
we
don't
have
to
own
it.
If
we
just
participate
in
a
working
group
as
a
vested
interest
to
that
point,
then
we
can
share
the
workload
and
all
that
stuff,
which
is
something
for
us
to
think
about.
C
Format
also,
hopefully
like
to
scope
it
way
down,
and
maybe
not
do
so
much
upfront,
design
and
research
purely
because
every
time
that
happens,
don't
actually
that's
that
example
an
example
of
this
actually
the
dashboard.
I
was
like,
oh
what
a
great
idea.
Of
course,
there
are
already
dozens
of
issues
for
a
dashboard,
and
I
saw
some
like
fully
fleshed
out
designs,
they're
amazing,
that
mate
did
and
no
one's
touched
it
in
eight
months
and
every
time
that
happens,
which
is
pretty
frequent.
C
It's
just
very
frustrating,
and
I
hope
that
when
it
comes
to
something
like
this,
we
could
just
do
something
in
maybe
a
shorter
amount
of
time,
because
I
think
any
improvement
is
going
to
be
big
and
it
can't
really
be
cosmetic
because
there
isn't
really.
I
mean
it
could
look
better,
but
that's
not
going
to
change
anything.
A
Fair,
so
just
so
that
I
can
expand
on
what
I
meant
by
cosmetical.
A
It
would
be
something
like
grouping
to
do's
of
the
same
item
or
expanding
some
of
the
drop
downs
to
not
be
a
drop
down
and
be
like
an
easily
usable
filter
button
or
something
that's
the
kind
of
like
cosmetic
things
not
like
rewording
to
lose
into
notifications,
not
reworking
notifications
as
a
whole,
but
more
like
using
the
features
we
have
right
now,
but
presenting
them
a
bit
better.
That's
the
cosmetic
level
that
I
was
thinking
about,
which
is
to
be
honest.
A
We
have
a
staff
on
our
team
that
would
be
extremely
happy
to
just
just
jump
in
and
with
some
guidance
kind
of
like
follow.
The
beautifying
efforts
example
that
you
and
enfield
did
you'll
be
happy
to
jump
in
in
next
quarter
and
improving
some
of
those
struggles.
While
the
more
long-term
thing
is
happening.
C
A
C
Did
I
did
chat
with
him
a
little
bit
about
it
and
it
did
seem
like
it
was
something
he
was
interested
in,
which
is
fantastic,
the
the
like
the
additional
filtering,
the
smaller
updates
that
can
be
made.
C
Sometimes
I
I
wonder
if
that's
more
like
I
keep
talking
about
like
nbc
in
this
thread
that
I
linked
to
and
the
filtering
based
on
like.
Was
it
a
direct
mention
or
was
it
a
group
mention
or
like?
Is
it
a
pipeline
or
is
it
a
review
request?
Those
are
things
that
I
think
are
like
need,
design
and
research
and
that
doesn't
really
fit
into
just
kind
of
showing
everything
right
now.
You
know
what
I
mean
I
mean
I
haven't
thought
that
much
more
than
friday,
so
that's
not
really
fair
to
say
so.
A
A
This
is
just
so
that
you
can
keep
that
in
mind.
In
case
you
have
a
short
list
like
of
things
that
could
potentially
have
a
good
impact
on
it.
We
could
take
a
look
at
it
and
just
run
with
it.
While
we
have
bigger
discussions
just
keeping
that
out
there,
we
don't
need
to
have
any
specific
right
now,
but
do
keep
those
in
in
our
realm
of
visibility.
So
we
can
take
a
look
at
it.
A
So
moving
on
to
my
second
point
I
want
to
be,
I
wanted
to
be
ready
for
the
upcoming
weeks
we're
going
to
have
to
cover
for
kai,
and
I
know
when
I
have
a
planning
of
the
milestones,
and
I
know
that
I'll
sync
up
the
pedro
I
know
about
who,
but
is
there
any
knowledge
that
I
would
like
to
get
on
on
the
team's
like
head,
just
to
be
prepared,
like
anything
in
in
specific,
or
should
we
just
wing
it.
B
That's
an
interesting
question.
I
I
thought
about
this
a
little
I'm.
B
B
B
As
much
as
possible
stay
out
of
it
entire,
like
I
don't,
I
don't
really
want
to
direct
the
work,
which
sounds
weird.
I
think
you
know
like.
B
Like
merge
ability
right,
like
you,
know
the
big
things,
but
I'm
sort
of
I'm
sort
of
hoping
that
I
go
away
like
pedro
did
when
he
was
on
paternity
leave
and
he
went
away
and
the
beautifying
effort
came
back
and
lots
of
things
changed
and
it
was
different
and
good
and
like
there
was
like
new
feedback
and
thought
into
how
the
process
works
and
what
we
should
do.
And
so
that's
why
I
want
to
stay
distant.
B
If
I
can
and
let
you
and
pedro
and
annabelle
and
jay,
although
I
don't
think
jay
will
be
involved
quite
yet,
but
like
I
want,
I
sort
of
want
to
see
like
how
this
goes
as
an
experiment
to
know
like
what
are
we
missing
like
what
is?
What
are
the
inputs
that
we're
missing
that
because
you're
doing
this
with
different
people
that
we're
finding
and
we're
we're
bringing
in
right
and
there's
not
there's
nothing
that
we
have
like?
B
That's
really
the
only
big
thing
that
we
need
to
make
sure
we're
continuing
to
drive,
and
so,
as
long
as
that
is
happening-
and
you
know
this
from
planning-
we
only
pick
up
a
very
small
number
of
those
issues
every
milestone
and
then
it
becomes
sort
of
what
are
the
other
interesting
things
we
want
to
work
on,
like
I
sort
of
want
to
see
what
that
looks
like
with
other
people,
taking
a
look
at
the
stuff
so.
A
Okay,
if
I
want
to
say
thank
you
for
the
trust,
but
I
like
I
like
where
your
head's
at
we
definitely
know
about
the
top
topics,
basically
so
no
much
surprise
there,
but
that
that
helps
me
get
into
your
frame
of
mind
and
how
we
should
approach
this
time.
So
that's
helpful
yeah.
I.
B
Think
I
would
say
think
about
it
as
two
milestones
where
I
don't
know,
you'll
get
even
more
say
than
you
normally
do
and
what
goes
into
it.
A
A
Makes
perfect
sense
and
we'll
we'll
definitely
make
sure
that
we
follow
the
whole
with
great
great
power,
comes
great
responsibility,
kind
of
thing,
uncle
ben.
B
B
Trust
the
people
that
are
going
to
be
covering,
I
think,
yeah,
I'm
excited,
I'm
actually
genuinely
excited
to
like.
B
Sport
and
stay
out
of
it,
because
I
think
that
was
hard
on.
A
I
I
have
some
ideas
and
also
speaking
to
what
I
mentioned
in
that
issue.
By
the
way
I
do
plan
on
taking
some
time
off,
but
I'm
still
planning
that
around
your
availability,
the
milestone
planning
math
coming
back.
All
that
stuff
is
built
being
factored
in,
so
I'm
very
flexible
cool.
That's
it
amy.
You
have
the
next
point.
D
He
is
in
standard
technical
writing,
fashion,
begging
for
things
to
do
and
not
wanting
to
wait
until
the
end
of
his
onboarding.
So
we
know
what
has
to
happen.
We
teach
him.
D
D
D
A
I'll
clip
this
bit
and
send
it
to
them.
It's
it's
sami's
fault.
No,
we
will
do
that
thanks,
amy
and
amy,
and
and
kai
enjoy
your
time
off.
It's
very
well
deserved
and
do
take
the
time
off
to
just
disconnect.
If
you
can.
A
E
Guess
yeah,
but
the
cms
interviews
are
wrapping
up
this
week.
Finally,
and
I
should
have
a
report
for
you
guys
next
week.
E
D
A
E
E
There's
an
editor
extension
for
vs
code,
where
we
sort
of
integrate
a
little
bit.
Some
of
the
workflows
get
lab
workflows
there,
I'm
evaluating
it
according
to
a
process
that
is
called
category
maturity,
scorecard
interviews
are
almost
done
or
sessions.
Really
it's
more
like
a
usability
so
yeah,
it's
mixed
reviews.
B
I'm
excited
I
it's
like
the
first
major
research
we've
done
on
vs
code
stuff
at
all,
or
even
that
category
sort
of
in
general.
So,
like
I'm,
I'm
sort
of
excited
to
see
how
it
comes
back.
I'm
now
incredibly
nervous
that
it
sounds
not
super
positive
across
the
board,
but
we'll
see
how
it
goes.
E
What
it
is
is
you've
got
enough
there
that
people
like
but
they're,
expecting
to
see
parody
right
from
like
what
they
can
do
from
the
web
interface
or
from
the
command
line,
and
so
that
doesn't
exist.
Yet,
for
instance,
you
can
see
the
suggestions
that
someone
has
made
to
like
an
mr,
but
you
can't
accept
them
right.
So
that's
like
frustrating.
A
B
Yeah,
it
impacts
category
maturity
so,
like
we
measure,
maturity
is
measured
on
a
category
basis,
and
while
this
is
the
code
review
group
code
review
is
a
category
of
the
code.
Review
group
and
editor
extension
is
a
category
of
the
code
review
group,
and
so
it
measures
maturity
there.
B
We
now
have
cli
and
starts
of
you
know
working
on
jetbrains
things,
and
so
it's
not
clear
how
we're
ultimately
going
to
need
to
distinguish
like
maturity
across
each
of
these.
B
If
that'll
need
to
be
like
separate
categories
or
some
average
for
like
a
global
category,
I
don't
know,
but
that's
a
future
problem
that
we'll
have
to
figure
out.
The
goal
is
to
sort
of
just
move
this
up
now.
Based
on
what
we
said,
we
would
do
you
know
nearly
a
year
ago
at
this
point,
so
thanks
ben
for
taking
care
of
that.
B
Awesome
well,
there's
nothing
else
on
the
agenda
thanks,
everyone
enjoy
the
rest
of
your
week.
I'll
see
you
all
next
week,
bye.