►
From YouTube: 2020-01-28 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).
B
A
Yeah,
I
don't,
I
can't
see
the
button
in
on
gitlab.com,
it
doesn't
exist
so
and
users
haven't
said
anything
I
would
have
expected.
I
guess
at
this
point
that
we
would
have
gotten
like
an
issue
report.
If
someone
was
like
this
button,
doesn't
do
anything.
C
So
I
did
a
quick
search
when
I
saw
this
on
the
agenda
and
I
did
get
the
ping
and
I
did
reply
there,
but
I
guess
it
just
slipped
off
my
mind
since
then.
I
thought
it
had
been
handled
by
someone
apparently,
but
no
so
it's
disabled
in
production.
So
I
checked
on
chatbots
just
now.
I
checked
the
yaml
of
that
feature
flag
and
it
says
that
it's
the
fault
enabled
true.
C
B
C
Default
enabled
now,
I
think,
yeah
self-hosted
instances
are
getting
this
enabled
by
default,
but
we
don't
see
it
on
gitlab.com
now.
The
reason
why
we're
probably
not
getting
complaints
is
that
it's
ignorable,
like
you,
can
totally
ignore
that
button.
It's
just
something
that
shows
on
the
commits
tab
and
you
just
ignore
it.
If
you
don't
want
to
use
it,
but
from
pedro's
feedback
it's
broken
so
now.
B
C
I
don't
think
it's
a
p1
s1,
but
it
might
be,
might
be
a
an
s2,
p2
or
something.
So
the
thing
is
it's
a
feature
that
is
broken.
I
need
to
get
to
the
bottom
of
exactly
what
is
broken,
because
I
can't
remember
from
the
top
of
my
head,
but
it
has
been
enabled
since
13
30.
C
A
I
just
it
feels
like
nothing
worked
like.
Why
would
we
do
it
if
no
like
it's
sort
of
yes,
there's
something
broken
in
reality,
that
contributors
working
on
the
mr
that
would
like
unbreak
this
and
then
we'd
have
to
go
back
and
like
do
another,
mr
to
like
default
it
back
on
at
some
point
in
the
future,
like
it
just
feels
like
sort
of
busy
work
for
no
reason
like
okay,.
B
C
Okay,
I
think
I
know,
what's
up
so
basically
there's
a
the
feature
of
adding
commits
works.
The
model
works,
selecting
commits
works,
everything
it
just
doesn't
show
the
changes
them
so
basically
we're
leading
them
in
a
so
basically,
people
that
are
trying
this
button
are
probably
like,
but
I
don't
get
what
this
does
and
ignores
it.
C
A
B
A
And
like
we
all
know
how
that
goes
yeah,
so
I
would
just
I'd
err
on
the
side
of
like
you
could
just
drop
it
to
like
a
p4s
for
it
and
like
if
it
comes
up
then,
like
we
know
it's
a
simple
like
one
line,
mr
to
like,
go
and
disable
it,
and
do
that
but
or
tell
someone
how
to
turn
it
off.
Given
that
the
feature
flag's
still
there
like,
we
could
tell
someone
how
to
turn
it
off
if
they
were,
like
crazy
impacted,
yeah.
Clearly,
we've
turned
it
off
on
gatelab.com,
so.
B
It
should
be
a
simple
list
for
front
end
and
ux,
and
then
backend
just
needs
to
do
a
normal
review.
My
problem
is:
it's
been
simple,
this
whole
time,
and
yet
it
still
takes
weeks
to
turn
around
so
there's
a
new.
They
hired
a
new
developer.
To
pick
this
up,
and
as
soon
as
I
posted
that
comment,
I
saw
that
he
started
working
on
it
already.
B
C
B
B
Who's
made
it
okay,
not
me.
Here's
the
next
one-
and
this
is
great
news,
so
it's
been
over
a
year.
I
think
that
we've
just
been
missing:
security
deadlines
left
and
right
and
after
this
release
we
will
finally
be
within
our
slos
and
done
with
missing
deadlines.
Release
after
release.
That's
pretty
good
news.
It
took
a
long
time.
C
B
B
One
thing
that
patrick
said,
the
last
thing
that
anybody
said
was
patrick
and
he
said
he
doesn't
really
see
a
problem
with
keeping
the
old
stand-up
format.
While
we
try
a
new
format-
and
I
thought
that's
true-
that's
how
we
would
do
it
if
this
was
like
a
code
conversation.
So
I
wanted
to
pick
your
brains
on
this
and
see
if
we
want
to
do
it.
A
I'll
be
honest
and
say
my
motives
were
not
for
a
traditional
stand-up.
They
were
for
to
like
move
the
social
section
into
the
code
review
channel
to
help.
A
Help
with
team
spirit,
I
guess
is-
is
like
a
simple
way
of
saying
that
I
was
trying
to.
I
was
trying
to
use
it
as
a
way
to
get
the
team
to
interact
more
and
which
I
know
people
do
in
the
stand
up
and
sort
of
like
cross,
but
I
think
the
stand-up
channel
is
noisy
because
there
are
so
many
people
that,
like
you,
may
not
notice
like
what
your
immediate
team
is
doing.
A
You
might
just
notice
what
the
people
in
your
time
zones
are
doing,
or
what
they're
up
to
and
sort
of
what
their
lives
are
like.
So
I
was
I
I
was
positioning
it
as
that
I
didn't
necessarily
care
sort
of
what
the
content
was.
I
was
trying
to
to
garner
interactions
of
our
team
in
slack,
which
I
see
not
many
of
so
I
am
I'm
content
to
not
do
it.
It
didn't
seem
like
there
was
an
overwhelming
like
want
to
do
it
so,
like
I
don't
know,
I'm
fine
with
not
doing
it.
C
Yeah,
a
plus
one
on
the
not
needing
a
stand-up
for
work
more
traditional,
because
we
already
have
the
status
updates
for
weeklies.
I
think
the
reason
why
we
didn't
do
that
in
the
first
place
was
that
we
we
encourage
people
to
if
you're,
if
you're
blocked,
don't
wait
for
the
stand-up
to
tell
that
you're
blocked
just
go
and
act
on
it
and
try
to
get
them
blocked
immediately.
So
yeah,
I'm
okay
and
keeping
it
as
it
is
right.
C
D
We
do
yeah,
so
my
opinion
is
actually
I
am
in
agreement
with
andre.
However,
there
have
been
a
number
of
people
who
have
expressed
that
they
want
a
more
like
a
less
social
way
to
report
things
and
like
and-
and
I'm
also
thinking
of
like
team
day
stuff,
where
they
also
want.
They
want
like
a
less
social
team
day
too.
They
want
to
like
do
team
building
stuff
like
can
like
like
how
can
we
improve
our
team
dynamics?
D
So
it
does
seem
like
there's
some
appetite
for
something
for
some
people.
The
problem
is
that
I
probably
wouldn't
participate
in
that
so
like
if
other
people
also
don't
participate
in
that,
like
it
reduces
the
value
for
those
people.
So
I
don't
know
what
the
solution
is,
but
I
don't
want
to.
I
don't
want
to
like
alienate
those
people
by
like
saying
yeah.
D
Aren't
your
needs
aren't
necessary
we're
not
going
to
do
that,
we're
just
going
to
stay
social.
So
I
don't
know
what
the
right
answer
is,
but
I
I
like
the
this
kind
of
the
more
social
thing
we've
got.
B
C
Yeah
and
my
my
question
to
that
is,
since
you
know
just
started
with
the
weekly
status
updates
and
nothing
stops
you
from
giving
more
than
one
a
week,
the
minimum
is
one
a
week,
but
if
you're
really
adamant
and
you
have
something
to
share
post
another
comment
or
something
so
I
would
give
that
a
try
as
an
answer
to
that
need.
So
it's
not
that
we're.
Not
it's
not
that
we're
ignoring
those
needs.
C
Good,
I
was
writing
a
new
one,
so
we
we
set
up
a
reminder
on
the
channel
on
slack
for
the
front-end
team,
for
the
weekly
statuses
and
what
we
discussed
was
that
we
didn't
need
to
have
a
one
special
day
for
everyone
to
post
as
long
as
they
did
once
a
week.
C
But
having
a
reminder,
one
of
the
days,
whether
it's
friday
or
monday,
kind
of
kicks
them
off
into
action,
probably
if
they've
forgotten
or
something
if
they
delayed-
and
I
think
it
was
yeah
gary
said
that
he
wanted
that
for
his
channels
as
well,
and
why
not
the
general
channel
just
wanted
to
check
whether
the
general
channel
has
more
people
than
engineers.
So
I
want
to
be
very
mindful
that
we're
nagging
the
right
audience
so
to
speak.
C
So
my
question
is
michelle:
do
you
want
to
set
it
up
for
your
channel,
or
should
we
set
up
this
for
the
group
code
review
channel
reminder.
B
B
So
I
put
like
last
week
I
put
a
slack
reminder
in
the
group
channel.
I
have
to
say
it's
very
weird,
putting
my
friday
updates
in
the
group
channel,
but
I'm
going
to
keep
doing
it
anyway.
So
if
you
want
to
just
put
it
in
the
group
channel,
I'm
okay
with
that,
even
though
sometimes
it
feels
importantly
weird.
C
Okay,
I
from
my
perspective
I
saw
that
update.
I
know
I
noticed
that
some
of
those
weren't
exactly
for
me
for
my
people,
but
no
harm
so
yeah
I'll
I'll
I'll
move
the
reminder
then
to
the
group
channel
and
then
it's
just
a
reminder.
It
doesn't
ping
anyone,
so
it
shouldn't
be
that
noisy.
C
A
I'm
fine
with
with
all
things
in
the
the
main
channel,
because
then
I
feel
like
everything's
in
one
channel
and
that's
where
people
talk.
I
mean
I
think
I've
said
that
before
about
front
end
and
back
in
channels
that
I
find
it
them
sort
of
weird,
because
they
they
end
up
siloing
conversations
away
from
like
the
whole
of
people
who
are
interested
in
code
review,
but
yeah,
I'm
fine
with
that
in
the
main
channel.
I
also
liked
your
friday
updates
michelle
for
what
it
was
worth.
A
D
I
I'm
sort
of
lost
on
on
the
slack
channels.
There
are,
there
are
some
fb
channels
and
not
there
aren't
matching
back-end
channels.
So
so
you
tell
me
where
to
go
and
I'm
fine
with
whatever.
C
Okay,
I'll
think
about
it
right
now
most
of
the
discussions,
the
communications
we
have
there
is
just
like
tim
internal.
What
do
you
call
it
announcements
to
the
team
like
the
ones
you
do
michelle
like
the
for
the
specific
actions
they
need
to
take
surveys.
That
kind
of
thing,
that's
what
I
use
the
channel
for,
or
checking
capacity,
so
yeah
I'll
I'll
see
if
we
start
doing
them
on
the,
but
so
you
don't
use
it
but
backhand
channel
at
all
anymore,
interesting.
B
C
C
Thought
you'd
just
stay
with
the
same
channel
or
something
for
the
overlap,
but
but
okay
I'll
think
about
what
that
means
for
us,
because
we
do
have
one
manager
and
for
us
managers
is,
I
find
it
useful
to
have
a
way
to
communicate
with
just
them,
but
they
can
also
do
that
on
the
group
channel
and
ping
them
so
I'll
I'll
think
about
it
and
I'll
take
a
connection
on
that.
But
for
now
I'll
just
set
up
the
reminder
on
the
main
channel
which
is
sort
of
the
agreement
there.
I
will.
A
Say
something
that
you
could
do,
which
is
maybe
not
like
get
lab
appropriate,
but
I
know
that
there
are
groups
yeah,
because
I
am
in
one
that
have
private
channels
for
the
team,
because
the
team
is
like
a
cross-functional
group
and
that
prevents
sort
of
like
other
people
from
going
to
that
channel,
but
allows
you
a
way
to
communicate
but
like
doesn't
make
it
a
place
that
like,
if
someone
thinks
they
have
front-end
code
review
questions
that
they
go
there
to
try
and
talk
to
front-end
engineers.
A
But
they
come
to
like
the
group
channel
to
talk,
and
so
you
could
consider
like
a
private
channel.
My
team
members,
which
is,
I
know,
not
widely
accepted
as
good
at
gitlab
but
is,
is
a
way
to
like
get
conversations
in
the
right
place.
C
Okay,
I
think
I
I
have
to
let
that
simmer
a
little
bit
to
see
what
the
and
also
talk
to
my
people
to
see
what
they
think
I'll.
Have
my
people
reach
your
teeth,
no
reach
your
people
all
right!
That's
it!
For
that
point
thanks.
My
next
one
is
just
something
that
came
from
a
discussion
actually
with
thomas,
so
I'm
glad
he's
on
a
call
and
as
we're
looking
to
revise
everything
in
a
process
to
make
us
more
reliable
in
delivering
and
everything.
C
One
of
the
issues
that
we
had
that
thomas
suggested
was
that
when
you're
doing
weights,
it's
very
hard
to
distinguish
a
three
from
a
four
from
a
five
and
that's
why
we
use
fibonacci,
sometimes
for
this,
to
make
sure
that
you
don't
get
distracted
by
those
splitting
hairs
between
a
three
and
a
four
so
and
I've
used
that
in
the
past
to
great
success.
Michelle
do
you
use
fibonacci
for
the
weights
in
the
back
end.
B
C
Okay,
yeah,
okay,
so
basically
the
change
is
that
we
do
stop
using
a
four
because
it's
really
what's
a
three
words
or
four.
What's
a
five,
so
kai
nope,
more
than
five
or
no
more
five
or
more.
C
C
It's
not
gonna
happen,
yeah
all
right.
I
just
want
to
run
this
past.
You
all
just
make
sure
that
we
don't
have
any
objections,
but
that
makes
sense
to
me
too
like
if
it's
a
five,
we
could
totally
break
it
down
and
we'll
we'll
kick
that
off
from
the
next
milestone.