►
Description
Monthly kickoff for 13.3 for the team: https://about.gitlab.com/handbook/engineering/development/dev/create-source-code-fe/
This is the call where the team discusses assigned Deliverables and their plans for implementation.
2020-07-27
A
B
B
So,
but
we
can,
we
can
do
one
very
impromptu
which
is
like
these
are
slips
sorry.
This
is
slippage
from
the
previous
one.
This
one
by
the
way
has
been
blocked
by
wax,
because
pedro
is
thinking
that
it
might
not
be
that
urgent.
After
all,
he
got
scheduled,
but
pedro
was
like.
I
think
we
have
bigger
fish
to
fry.
We
do
have
one
bug
that
I'll
I'll
mention
to
you
like
the
the
drop
downs
are
showing
up
in
some
scenarios
where
they
shouldn't.
This
is
just
closing
up
from
previous
milestone.
B
This
is
the
enabling
of
the
feature
flag.
This
is
the
editing.
The
comment
should
be
updating
the
scope,
as
you
added
the
the
scope
of
as
you
added
a
comment,
so
it
should
be
just
internal
thing.
This
is
the
one
I
want
to
talk
about,
which
is
one
directly
related
to
the
okrs.
We
have
okay,
so
this
is
where
I'm
expecting
you
to
to
go
deep
on
our
application.
B
Do
some
profiling
and
then
take
the
top
pain
points
of
the
application
in
terms
of
time,
and
this
will
probably
materializes
itself
in
a
series
of
issues.
So
do
take
some
time
for
that
it's
a
spike,
so
I
don't
expect
any
code
to
be
delivered.
It's
kind
of
like
the
audit
that
phil
did
a
couple
of
miles
ago,
and
this
will
guide
our
future
work,
whether
it's
tech
debt,
whether
it's
performance,
oriented
work,
we'll
keep
this
as
a
reference,
but
we
want
to
take
a
snapshot.
B
After
all,
the
work
we've
done,
what
are
still
the
pain
points
that
we
have
on
the
merge
requests
and
yeah
and
then,
if
you
have
after
you
have
like
a
list,
go
send
it
through
review
from
some
of
us
just
hey:
do
you
find
anything
else?
Do
you
remember
anything
else,
sure
all
right,
anything
to
add
no
cool.
A
A
A
Yeah
so
like
the
code
is
one
then
I'll
discuss
some
because
the
data
does
not
exist
in
the
database.
It
exists
in
a
file,
they
need
to
extend
store
it
in
the
database
and
then
the
discussion
of
not
doing
it
through
the
ui
and
do
it
for
the
code
owners
file
so
like.
I
have
no
idea
if
any
ui
is
doing
on
it
at
all.
A
B
Is
it
is
I
we
did
expect
it
to
be
straightforward
from
the
front-end
perspective,
like
the
back-end?
Had
those
things
sorted,
somehow
that
probably
escaped
planning
the
planning
stage,
otherwise
you
wouldn't
have
scheduled
it.
So
I
think
that
the
tip
there,
if
we
do
see
that
we're
completely
blocked
on
the
front
end.
We
can
probably
split
this
out
into
a
separate
issue
and
put
something
in
into
the
milestone
like
a
two-point
weight,
so
oops
wrong
one.
B
A
B
Yeah,
I
I
think
I've
seen
the
discussion
about
this.
I
think
it
was
myra
who
brought
the
problem.
The
the
thing
is,
we
might
eventually
deprecate
this
call
and
not
make
it
visible
on
the
ui,
but
I
feel
like
at
this
moment.
We
have
a
broken
feature.
That's
that's
it.
We
basically
have
a
room,
it's
not
a!
B
So
we'll
still
have
to
support
this
for
a
couple
of
features.
A
couple
of
milestones
and
my
my
understanding
is
this:
milestone-
is
just
to
make
this
element
fix
this
bug
that
it
was
introduced
right
now.
So
I
think,
even
if
we
choose
to
drop
this,
we
still
have
to
ship
this
feature.
I
know
it's
not
the
great
hey,
samantha.
B
But
at
this
point
I
don't
think
we
can
get
around
not
implementing
this
at
the
moment
with
the
draft
yeah
the
the
thing,
the
concept
there
is
just
make
sure
that
we
can
have
a
token
here
that
can
have
a
different
representation
on
the
url,
so
it
can
be
draft
draft
or
whip
will
always
render
a
draft
token
kind
of
thing.
I
know
that
code
is
ugly
and
it
smells
and
it's
old
and
so
yeah.
I
sympathize
and
that
there's
another
thing
you
want
to
talk
about.
This
murderer
real,
quick,
sorry,.
A
B
B
A
Yeah,
it
was
like
the
most
confusedness
thing
for
me
ever
to
understand
what
I
needed
to
do
and
it's
like.
There
are
simplest
of
things
you
just
need
to
change
the
drop
down
to
the
head
and
stuff
yeah
yeah
heads,
but
there's
like
some
issues
with
the
back
end:
you're
actually
doing
it
properly
when
there's
major
conflicts
and
stuff
and
then
yeah,
it's
kind
of
blocked
until
that
gets
fixed.
B
Yeah,
so
basically,
this
is
the
spin-off
issue
that
we
basically
prioritizing.
The
back
end
is
working
right.
Now
is
so
that
the
right
now,
if
we
have
conflicts
between
the
two
branches,
it
doesn't
display
anything,
and
that
was
a
very,
very
bad
user
experience
to
make
it
the
default
so
before
we
can
address
that
default.
We
have
to
address
this
on
the
back
end.
B
A
B
B
This
is
it
I'm
really
looking
forward
to
this.
This
is
this:
is
our
plan
to
duplicate
phil
as
a
reviewer
so,
and
I
this
is
kind
of
a
joke,
but
not.
I
will
encourage
everyone
in
the
team
to
to
follow
the
mr
and
and
once
it's
up
and
to
provide
any
feedback.
If
you
have,
if
you
see
it,
but
also
to
read
the
article
once
it's
published,
because
it
will
make
everyone's
more
acquainted
with
how
phil
does
it
and
will
make
us
all
better
reviewers
interfering
in
theory?
B
B
D
How
are
we
doing
this?
Go
ahead?
Okay,
let
me
share
my
screen
here:
okay,
so
here's
what
I
working
on
this
one
is
about
closing
the
block.
Merge,
request
issue
so
essentially
what
I
need
to
do
for
this
one
is
just
to
remove
the
status
so
that
one's
pretty,
I
don't
think,
there's
any
roadblock
issues.
Yeah.
I
solved
the
roblox
issue,
so
this
one's
good
to
go.
Let.
B
Me
just
let
me
just
say
one
thing
just
because
the
bug
here
is
that
you
can't
change
the
status
of
a
merged
emergency.
You
can
change
the
status
of
a
closed
one
back
to
open,
but
once
it's
merged,
you
can't
bring
it
back
to
open.
So
that's
why
the
bug
is
there?
It's
just
a
simple
bug:
fix
yeah,
go
ahead.
D
D
D
This
is
happening
only
on
the
changes
tab,
so
just
making
sure
those
two
are
matching
up
all
right.
Moving
on
to
the
next
one,
which
is
the
jump
to
next
and
resolve
thread
button
and
the
merge
request
threads
so
right
now
there
are
two
places
that
we
can
click
on
it
globally,
which
is
right
up
here.
So
if
I
I
can't
cover
the
screen.
D
So
this
is
one
view
right
here,
and
this
is
the
second
view
here,
so
you
can
see
we're
trying
to
remove
these
in
the
original
one
and
we're
going
to
do
that
under
a
feature
flag,
so
we're.
How
is
it
being
done?
It's
going
to
be
so
we're
going
to
add
the
feature
flag.
You
have
to
turn
on
the
feature
flag
to
not
display
I'm
getting
those
too
confused.
B
B
Right
because
we
looked
at
the
data
and
the
data
shows
that
not
a
lot
of
people
are
using
that
button,
they
do
use
the
global
one,
which
is
always
fixed
on
the
ui,
always
in
the
same
spot,
this
one
you
have
to
find
them
on
the
page.
So
it's
it's
normal
for
users
to
start
learning
the
path
of
the
global
one.
So
in
order
to
make
the
ui
more
simple
or
simpler,
we're
trying
to
clear
out
the
buttons
that
are
not
being
used,
and
I
wholeheartedly
support
that
effort.
Cool,
carry
on.
D
D
D
How
does
it
work
so
it
keeps
making
that
request
until
it
hits
the
end,
which
can
trigger
kind
of
this
kind
of
response
and
kind
of
render
that
page
to
stop
rendering.
So
what
we're
gonna
do
is
instead
of
let's
say
there
are
like
500
files.
I
know
so
it'll
keep
going
100
first
and
then
just
the
set,
the
second
hundred
and
the
thirds
100
and
the
405.
D
So,
instead
of
doing
that,
we're
just
gonna
load
the
first
hundred
and
then,
if
they
want
more,
then
we'll
trigger
the
second
chunk
of
it
and
hopefully
that
will
improve
from
the
performance
I'm
still
talking
to
pedro
about
hey.
How
is
this
going
to
look
on
the
ux
I?
So
it's
not
this
pagination
that
I
initially
thought
it's
going
to
be
something
else.
So
I'm
going
to
wait
until
pedro
respond
and
see
what
that's
going
to
look
like.
B
Yeah,
I
I
one
of
the
things
you
have
to
discuss
with
peter
as
well
is:
where
will
be
that
cut
competitors?
I
think
github?
Does
it
at
a
thousand,
so
it
stops
at
a
thousand
files,
because
we
don't
want
to
make
it
too
short,
too
shallow.
If
it's
always
showing
up
it's
going
to
be
a
pain,
you
want
to
make
sure
that
this
is
just
stopping
the
browser
from
breaking
that's
the
goal,
and
also
I
wanted
to
clarify
here.
B
This
is
part
of
an
attempt
to
spread
knowledge
on
the
view
file
refactor
amongst
the
entire
team.
Phil
created
it.
He
has
a
ton
of
experience,
but
instead
of
going
with
yeah
phil
knows
about
this
I'll,
just
put
it
on
him.
I'm
spreading
these
issues
around
the
team,
so
samantha
you
got
the
first
draw
and
we're
going
to
have
more
improvements
of
this.
But
just
so
you
understand
why
these
things
are
going
to
go
through.
Different
people
is
exactly
to
spread
that
knowledge.
A
D
To
the
other
one
all
right,
this
is
the
last
one.
This
I
thought
was
this
intense
thing,
this
intense
thing
but
turns
out:
it's
not
we're
this
iteration
we're
just
we're
having
I'm
actually
really
excited
about
this
one,
so
we're
adding
a
reviewer
list
so
right
now
you
have
that
approved,
like
you,
can
sign
users
to
guess
review
your
stuff,
but
it's
not
really
segmented.
Now,
with
this
feature,
we're
gonna
add
in
like
hey,
we
can
actually
specifically
assign
a
sp.
D
We
can
start
a
site
of
bucketing
people
into
this
review
category,
and
so
this
first
iteration
is
you.
Can
I
no?
We
can't
manually
assign
them
it's
gonna,
be
the
back
end's
gonna.
Do
some
magic
and
figure
out
who's
going
to
be
in
a
review
for
this
iteration
and
then
we're
just
going
to
display
the
reviewer
in
this
new
column
and
future
iteration
will
start
being
able
to
you
can
manually
assign
reviewers
but
yeah.
D
D
B
Yeah
I
just
wanted
to
contextualize
this
one,
so
this
is
the
big
effort.
This
is
one
of
the
top
topics
in
ux
at
the
moment
is
to
make
reviewers
a
full
feature
in
the
merge
requests
and
right
now,
yeah
backhand
will
calculate
the
reviewers
like
samantha
said
exactly,
I
think,
they're
thinking
about.
If
you
leave
a
comment
or
an
mr,
you
will
be
considered
as
a
reviewer
for
now,
but
later
on,
you'll
be
able
to
specify
ahead
of
time.
B
So
this
is
another
one
that
I'll
try
to
circulate
across
the
team,
not
not
focus
entirely
on
one
person,
but
this
is
very
exciting
and
I
showed
this
last
thursday
on
a
from
the
engineering
managers
call
and
they
were
very,
very
excited,
namely,
as
this
opens
the
door
to
since
now,
you're
assigning
someone
as
a
reviewer.
Specifically,
they
talked
about
showcasing
the
workflow.
They
have
how
many,
mrs
they
have
assigned
on
their
name
like
display
that
on
the
ui
specifically,
but
anyway,
that's
I'm
rambling.
B
D
C
Away
I'll
be
out
for
five
work
days,
this
milestone,
so
I
have
a
lighter
load.
These
top
three
are
my
new
ones.
This
disabled
simulink
comments
kind
of
rolled
over
from
13
2
it.
There
wasn't
really
any
major
problem
with
it.
It
was
just
really
low
priority
and
slipped
after
work
and
some
other
things.
So
this
is
actually.
A
C
C
Last
time,
so,
there's
there's
not
much
to
talk
about.
Basically,
I
need
to
write
some
tests
and
get
it
get
it
out,
so
that
one
is
pretty
much
just
in
review
right
now.
The
other
three
are
new
stuff,
so
this
is
one
to
just
add
a
little
bit
of
ui
text
to
the
blob.
Viewer.
Basically
just
show
that
hey
this,
this
icon
is
a
symbolic
link,
because
it's
not
really
clear
from
that
icon.
C
If
you're
expecting
a
js
file,
why
is
it
a
little
arrow
just
to
show
that
it's
symbolic
from
what
it
sounds
like
like
from
pedro's
response?
It
sounds
like
we're
literally
just
gonna.
Add
some
text
here
just
like
this,
so
I
think
it's
gonna
be
really
trivial.
I
don't
think
that
the
I
think
that
the
information
we
need
for
this
is
already
available.
It's
like
the
file
mode
is
there,
so
it's
literally
just
a
hammer
like
if
file
blob
mode
is
1000
or
120.
C
000
then
show
this
text,
that's
basically
it
the
only.
The
only
question
on
this
one
is
if
the
the
file
size
and
the
file
name
are
like
somehow
like
intertwined
putting
this
between
them,
but
that's
like
a
really
marginal
edge
case,
which
probably
won't
be
a
problem.
So,
let's
see
which
one's
more
complicated
this
one
is
least
complicated.
C
So
this
is
just
adding
a
little
bit
of
ux
to
to
this
file
diff
stuff,
basically
adding
chevrons,
left
and
right
is
showing
a
tooltip
why
it's
disabled
and
removing
the
pagination.
If
there's
only
one-
and
I
think
that
after
a
little
bit
more
discussion
pages
like
yeah,
be
nice
to
show
like
the
total
number
here.
I
haven't
regrouped
on
this
one
because
it
was
just
this
morning,
but
as
far
as
the
rest
of
this
stuff,
it
all
seems
pretty
easy.
C
About
the
compact
navigation
or
compact
pagination
component,
which
like
renders
a
previous
and
next
button,
the
problem
with
this
thing
is
that
it's
really
really
really
geared
toward
like
actual
pages
of
things
so
like
by
default.
You
get
these
middle
number
things
and
it's
it's
really
difficult
to
use.
When
you
just
want
like
a
next
previous
and
like
that's
it,
it
also
requires
numbers,
so
it
its
interface
is
like
literally
numbers,
so
outputs,
a
one
or
a
two
or
three
or
whatever,
and
using
that
with
like
commits
or
files.
C
C
B
C
The
one
of
the
things
that
I
commented
on
before
with
when
peter
actually
suggested
that
for
the
commitment
commit
as
just
I
don't
think,
of
this
type
of
navigation
as
paging
through
things,
and
so
like
it's
weird
for
me
to
think
of
like
oh,
this
is
the
next
page.
But
it's
that's
just
kind
of
a
scenario.
B
C
Think
is
really
going
to
be
that
complex,
just
just
kind
of
updating
a
little
bit
the
the
most
complex
one,
I
think
is
going
to
be
this
because
it
just
requires
touching
on
a
lot
of
things
when
there's
an
error
in
this
modal.
It
shows
up
here.
In
the
background,
I
think,
I'm
pretty
sure,
because
we
use
that
the
gl
flash
like
helper,
which
just
like
it
knows
where
the
main
div
is
and
adds
a
flash
there,
and
that's.
C
A
C
So
there's
a
lot
of
stateful
stuff,
that's
kind
of
used
to
go
around
in
here.
So
there's
there's
actually
quite
a
bit
of
work
to
to
change
this,
because
right
now,
usually
how
this
works.
Is
we
fire
the
action
into
view
x
and
then
just
kind
of
forget
about
it,
because
the
action
handles
showing
the
gl,
flash
and
all
kinds
of
stuff
there's
a
lot
more
of
like
round
trip
stuff
that
needs
to
happen
and
statefulness
in
the
component
not
really
complex.
Just.
C
I
think
it
just
touches
a
lot,
so
I
weighted
this
a
two
because
it
wasn't
weighted
before
I
think
there's.
I
think
this
is
gonna,
be
the
most
effort
of
all
of
these
things,
so
lots
of
testing
to
do
right,
in
addition
to
all
that,
because
once
you
change
actions
and
change,
components
and
change,
how
component
methods
work
like
a
lot
of
tests
updates,
so
a
lot
of
stuff
to
do
here.
Yeah.
B
There's
definitely
when
I
looked
at
it,
it
seemed
a
little
bit
simpler,
I'll
I'll.
Give
you
that.
Let
me
just
clarify
one
thing,
though:
while
we're
talking
about
this,
we
only
apply
the
front
and
weight
label
when
there's
both
backhand
and
front,
then
on
the
same
issue
when
you,
when
you
see
certain
stuff
like
an
issue
like
this,
where
it
has
front
end
but
then
has
a
weight,
then
the
weight
applies
to
the
front
end.
We
only
apply
those
labels
when
we
want
to
disambiguate
the
weight.
C
Okay,
so
it
doesn't
need
this
light
bulb.
I
just
changed
the
regular
weight
here:
yeah,
that's:
okay,
yeah,
okay,
cool
the
only
thing
kind
of
on
this
is.
I
think
this
is
a
good
use
case,
just
like
in
the
renamed
file
widget,
where
it
goes
through
various
states
to
like
show
errors
or
be
loading,
the
background
content
or
whatever.
This
is
a
good
use
case
for
a
state
machine.
The
there
is
already.
C
I
already
have
a
mr
for
like
finalizing
the
implementation
of
finite
state
machine
based
on
the
rfc,
but
it's
not
merged,
and
so,
if
this,
if
I
work
on
this
before
that,
there
will
be
another
ad
hoc
implementation
of
the
finance
state
machine.
So
I'd
like
to
I'd
like
to
avoid
introducing
as
much
tech
there
as
possible.
B
B
I
totally
agree
with
if
you
want
to
replace
it
later
with
with
a
state
machine
or
something
definitely
a
follow-up
and
mark
and
can
address
that,
but
I'm
I
might
have
missed
something
when
I
looked
at
it
because
we
have
these
cases
in
other.
You
know
the
parts
of
the
application
like
showing
the
error
inside
a
model,
so
you
might
want
to
take
a
look
at
those
examples
and
how
they
do
it,
because
this
seems
like
a
little
bit
overworked
for
the
does.
D
I'm
just
having
first
thought
when
you're
presenting
yourself
this
one's
gonna
be
because
there's
a
lot
of
it's
a
little
bit
that
the
component
there's
a
lot.
I
believe,
there's
a
lot
of
slots
and
stuff
and
yeah
it's
gonna,
be
it's
going
to
be
a
challenging
one
for
sure
I
I
agree
how
you
place
that
highly.
D
Yeah
and
it's
being
used
in
fused
places,
so
so
we
definitely
want
to
play
around
with
the
testing.
I
think
it
appears
in
the
create
the
in
the
settings
as
well,
so
in
the
merge
request,
form
plus
the
sorry,
the
project
settings,
so
you
might
want
to
take
a
look.
I
think
there
are
some
nuances
between
the
two,
so
I'm
not
sure
how
it
will
affect,
but
definitely
have
a
that
one's
a.
B
Might
be
worth
maybe
worth
dropping
a
question
on
the
front
end
channel,
because
this
is
specific
about
a
view
context.
They
have
view
components
and
the
models
where
you
want
to
display
an
error
message
inside
it.
I'm
I'm
pretty
sure
I've
seen
that
on
the
product
somewhere,
so
drop
a
question
early
on
the
front
end
channel
to
see
if
anyone
has
done
this
and
because
this
does
feel
a
little
bit
a
little
bit
too
much
work
for
for
the
yield
of
it.
B
C
B
Yeah,
what
I'm
thinking
is
there
might
be,
it
might
be
a
better
investment
of
our
time
to
tweak
the
the
gitlab
ui
model
to
support
this
easier
in
a
more
easier
way
for
the
authors,
because
we're
going
to
run
into
this
later,
instead
of
trying
to
create
them
up
with
a
pro
a
solution.
For
this
particular
case,
we
might,
we
might
invest
our
time
into
tweaking
the
gitlab
ui
component,
to
make
this
easier
and
just
connecting
with
other
things.
B
C
C
B
To
make
it
simpler,
that's
that's
my
thing,
because
if
we
have
to
do
all
this
weight
lifting
every
time
we
have
a
situation
like
this,
it's
not
practical!
You
know
what
I
mean.
So
if
you
find
ways
to
make
this
a
little
bit
simpler,
all
years,
yeah
yeah
any
any
more
thoughts.
People
on
that
this,
it
seems
simple,
but
I
understand
that
we
have
a
lot
to
unwrap
there,
but
thanks
for
the
heads
up
from
what
you've
described,
I
think
that's
a
little
higher
than
a
two,
the
two.
B
So
basically,
when
it's
a
one
is
like
something
that
it's
100
clear.
What
you
need
to
do,
it's
not
a
lot
of
work.
You
might
have
to
play
the
test
or
two,
but
that's
it.
If
it's
a
two,
then
you
have
to
you
know,
pull
in
a
new
component
tie
in
a
new
test.
That
kind
of
thing
that's
a
two.
The
three
is
more
or
less
like.
B
C
B
C
A
C
B
C
B
B
Awesome
great
to
hear
thanks
thanks
thanks
for
that
justin
all
right,
that's
it!
Anybody
has
any
other
things.
I'd
like
to
discuss
cool!
Oh
good,
awesome!
Some,
since
I
have
you
all
in
the
call,
just
checking
real
quick
show
of
hands
who
has
finished
the
security
training
thing,
so
we've
all
done
them
awesome
what
else
so
the
retrospectives
are
being
changed
and
we
have
to
fill
them
in
by
the
31st.
B
So
by
the
end
of
the
week,
I
need
to
put
the
highlights
of
our
retros
in
the
company-wide
document
and
then
there's
a
process
where
we'll
be
shooting
a
video
before
the
company-wide
retrospective.
That
will
be
shared
ahead
of
the
retrospective
and
then
the
retrospective
will
basically
be
a
discussion
about
the
topic
on
the
video.
So
it's
a
slightly
different
thing:
promoting
more
discussion,
rather
than
just
like
reading
bullet
points,
which
was
what
it
was
which
is
like.
Okay,
it
might
be
a
good
step
forward,
but
that
basically
puts
us
like
tldr.
B
Let's
try
to
wrap
up
our
sharing
of
retrospective
during
this
week,
especially
I
don't
know
if
I
haven't
seen
them
in
the
last
couple
days.
So
I
apologize,
but
the
thing
about
the
rushed
merging
at
the
end
is
probably
something
that
we
want
to
address
and
the
whole
reverting,
because
it
didn't
make
it
in
the
border
deploy.
You
have
to
be
a
little
bit
more
careful
and
that's
more
on
me.
B
Do
not
merge
release
post,
mrs
ahead
of
time,
but
yeah,
that's
kind
of
it
feel
the
the
things
for
the
retro,
and,
apart
from
that,
I
think
we're
done
here.
Any
other
things
you
like
to
share
before
we
go
the
the
milestone.
I
think
I've
told
you
all
of
this,
but
the
milestone
has
a
little
less
smaller
issue,
so
the
throughput
might
be
affected
or
any
or
something
like
that.
So
we're
aware
of
that
time
off
all
that
plays
into
this
thing.
B
We
want
you
to
enjoy
the
time
off
without
added
pressure,
so
that's
all
adjusted
for
the
capacity
of
the
team
and
I'm
looking
for
the
quarter
three
to
address
tech
debt
so
I'll,
be
I'll,
be
picking
you
here
and
there
as
I'm
I'm
crafting
the
okrs
for
the
quarter
three
and
I
might
need
some
help
and
some
insights
so
I'll.
Thank
you.
Throughout
the
week,
but
other
than
that
have
a
wonderful
week,
thank
you.
So
much
for
this
and
yeah
see
you
around.