►
From YouTube: Frontend maintainers weekly 2020-06-18
Description
In this meeting we talk about some git tricks with reviewing MR's locally. We also talk about the maintainer approval process.
A
I'm
recorded
on
my
computer
and
I
have
the
maintainer
training
topic
and
I
was
just
going
to
show
you
some
things
that
I've
automated
for
me
personally
and
when
I
show
you
them
you're
gonna
think
wow
Paul.
You
haven't
really
automated
a
lot
and
you've
kind
of
just
discovered,
good
and
yeah.
So
I'm,
just
gonna
show
you
some
things
that
I
do
but
I
know
that
there's
lots
of
room
for
improvement,
but
it's
gonna
show
you
one
of
the
things
that
just
helps
me
out
significantly
as
a
maintainer.
A
A
A
B
A
A
Someone
is
working
really
hard
in
this
really
neat
feature
26
file,
Changez,
and
you
look
through
some
of
this
and
sometimes
when
I
look
through
files,
I
didn't
know
if
you
feel
the
same
way,
but
it
I
really
like
to
see
the
whole
context
of
something
or,
if
I
know.
Okay
I
want
this
to
change.
I
want
to
write
a
patch
for
it,
I
just
in
the
gate.
Labview
I,
sometimes
we're
feeling
a
merge
request.
A
I
can't
get
my
fingers
in
it,
and,
and
so
this
this
is
a
little
there's
a
gap
for
me
and
it
hurts
me
as
a
reviewer
part
of
it
is
because
I
don't
get
to
see
full
context
of
files.
I
can't
do
quick
searches
across
the
whole
codebase
I
can't
change
you
to
get
my
fingers
in
it.
So
I
like
to
sometimes
I
like
to
review
locally
and
to
you,
people
that
are
saying:
hey
Paul.
A
What
about
dogfooding
our
product
you're,
bringing
up
some
good
points,
but
how
do
I
review
this
locally
when
there's
42
commits
how
do
I
get
just
the
changes
just
to
check
those
out
locally
and
here's
what
I
do-
and
this
is
also
interesting,
because
this
is
a
community
contribution,
so
we
get
to
use
another
cool,
alias
for
just
checking
out
this
community
contribution.
Omar
do
I,
have
it
here:
oh
I
do
yeah
here's
a
cool
kid,
alias
called
mr,
and
the
way
it
works
is
if
fetches
it
use,
uses
this
ref
path
to
fetch.
A
Just
the
ref
of
this
fork,
so
I,
don't
have
to
like
add
a
new
remote
or
anything,
and
so
all
I
have
to
do
locally
is
just
copy.
This
merger
class,
ID
and
I
go
get
em
our
origin
and
then
the
merge
request
ID,
it's
gonna
fetch
the
latest
ref
from
that
merge
request
and
then
create
a
local
branch
for
me
to
play
around
with
it
here
and
so
now.
I
have
this
local
Mr
origin.
Whatever
that
merging
is
that's
great
I.
Look
at
the
log
and
yeah
we've
done
like
even
like
merging
and
stuff.
A
A
The
only
thing
that
I
have
to
keep
in
mind
of
one
side
effect
of
this
get
review
and
be
it
introduces
a
revert,
commit
that
revert
s--
everything
that's
changed
from
merge
base,
and
then
it
does
reverts
that
revert
so
now,
I
can
view
my
changes
here.
So
you
don't
want
to
push
this
up.
You
don't
want
to
include
this
River
commit
any
kind
of
patch
or
whatever.
So
usually,
if
I'm
gonna
write
a
patch
I'll
then
just
commit
this
and
start
writing
my
patch
or
whatever,
but
yeah.
A
That's
get
review
and
be
I
use
it
often
when
reviewing
merge
requests
locally.
For
the
sake
of
time,
when
someone
else
is
the
another
thoughts
about
cool
things
they
see
in
dot
files,
that's
about
it.
Do
you
guys
any
thoughts
or
questions
or
see
I
may
over
here
at
the
document
and
Andrew
says:
do
I've
them
a
lot.
Have
I
considered
them
fugitive
I.
Do
them
a
lot.
I
have
vias
code
them
because
I'd
them
by
default.
A
I
am
in
a
really
weird
place
where
I
use
vias
code
for
everything,
and
sometimes
I,
won't
even
realize
I'm
envious
code
and
I'll
start
defending
inside
of
here.
So
yeah
them
is
my
main
editor.
I
haven't
used
fugitives,
I,
think
I'm,
using
something
else.
I
haven't
looked
in
my
femme
config
in
a
long
time,
I'll.
A
A
A
A
E
D
A
D
A
C
A
F
Cool
sorry
for
jumping
the
queue
and
I'm
just
taking
one
minute
so
yeah,
so
that
I
can
run
to
the
the
other
meeting
on
family
and
friends
day.
I
built
like
this
little
tool
and
polished
it
over
this
week.
What
am
I
sharing?
Ayats,
okay
and
the
tool
essentially
goes,
gets
almost
requests
pauses.
The
system
nodes
of
all
met,
requests
for
assignment
events,
because
we
don't
have
an
API
for
events
and
then
for
or
maybe
I
don't
know
about
it
and
then
for
each
assignment
of
an
mr.
It
increases
the
count
per
one.
F
It
also
you
know
make
is
able
you're
able
to
hide
or
show
the
maintenance
that
are
there
or
not.
So,
for
the
sake
of
you
know
showing
stuff,
let's
maybe
go
with
this
one,
so
you
would
see
in
one
dashboard
who
is
available
and
you
potentially
can
sort
like
by
how
many
a.m.
as
someone
has
been
assigned
and
now
you're
asking
hey.
Why
assignment
events
is
a
deduplicated
per
maja?
F
No,
it's
not
so
the
idea-
and
you
can
maybe
tell
me
if
it's
the
right
idea
is,
if
you're
assigned
to
one
mr
four
times
this
this
for
assignment
events
and
it
means
like
hey,
you
have
potentially
for
context
switches
right.
Even
if
you
go
back
to
the
same
EMA
so
young,
how
would
you
use
it
on?
You
know?
F
I,
don't
know,
potentially
for
people
or
community
contributions
really
easy
to
pick
a
maintainer,
because
you
can
pick
from
that's
available,
so
it's
like
on-demand
reviewer
elect
or
you
could,
for
example,
if
you're
unsure
who
to
assign
could
have
a
look
or
maybe
as
maintainer
yourself.
You
could
have
a
look
and
be
like
hey.
Let's
look
at
the
the
averages
and
oh
wow
I'm
reviewing
like
20m
hours
per
day
in
the
last
7
days.
Maybe
I
set
myself
to
unavailable.
F
F
C
F
F
B
Cool
thanks,
Lucas
awesome,
so
I
just
wanted
to
spend
a
little
bit
of
time.
Talking
about
this
update
to
the
maintainer
process,
there
was
an
mr
a
little
while
ago
about
how
about
which
changed
the
language
of
how
the
maintaining
process
worked,
and
the
end
result
was
that
it
removed
some
of
the
friction.
I
think
I
think
that
was
the
original
intention,
because
people
want
some
management
wanted
more
maintain
is
to
go
through.
B
It's
become
people
to
come,
maintain
errs,
and
so
there's
mi
just
remove
that
friction,
but
with
a
recent
trainee,
maintainer
issue,
there
was
some
discussion
about
that.
So
Paul
open
this.
Mr
thank
you
for
doing
that,
Paul,
which
I
think
the
basic
idea
is
to
reinstate
that
friction,
because
it's
there
by
design
and
I
happen
to
agree
with
that
and
I
didn't
agree
with
the
original
one,
so
I'm
behind
this.
So
that's.
G
So
as
somebody
who's
here,
who's,
not
a
maintainer,
yet
my
one
thought
is,
it
does
feel
like
it
makes
it
harder
every
single
time
someone
becomes
a
maintainer
to
become
a
maintainer,
because,
if
you're
just
taking
50%,
then
if
there's
eight
maintainers,
you
have
to
convince
four
people.
But
if
there's
20
maintainer
x',
you
have
to
convince
people
and
I
think
that
is
interesting,
I'm
not
saying
we
should
do
it
or
we
shouldn't
do
it,
but
it
seems
to
be
a
kind
of
funny
fall
out
of
that
change.
Yeah.
A
You
bring
up
a
really
good
point,
Sara
and
which
is
why
the
language
of
this
M
R
is
different
than
it
originally
was
where
for
back
end,
that
has
like
I,
don't
know
back
and
just
seems
enormous,
so
I'd
say
50
maintainer
x'
like
that
may
be
overstating
it.
50
percent
is
25
like
that's
a
little
ridiculous
and
I
think
the
idea
is,
and
we
need
50%.
We
just
want
to
have.
You
know
a
good
group
of
maintainer
x'
that
can
give
some
feedback
or
even
just
affirm
them
as
I.
A
Guess,
you're
ready,
let's
go
for
it,
so
this
is
50
percent
or
8,
whichever
is
less
so
to
me,
I
think
8
sounds
like
a
good
round
number
and
represents
some
sort
of
statistically
significant
group,
probably
so
yeah
we're.
This
is
changing
the
original
language,
which
was
50%
cuz
yeah.
It
sounds
weird.
Every
time
we
get
larger,
it
gets
harder.
That's
weird
age
should
be
significant.
E
My
case
I
think
that
the
tine
box
to
be
feedback
is
too
short.
48
hours
is
not
enough
for
for
us
to
to
analyze
all
of
they.
They
a
kind
of
the
candidates
proposal
I,
considering
that
most
of
them
are
pretty
large,
so
I
think
that
we
could
increase
the
time
period
for
a
time
box,
but
at
the
same
time,
I've
seen
in
the
finder
I'm
hoping
working
on
kidnap
several
mares
request
that
that
has
been
lingering
for
months
and
I
think
that
that's
not
fair
for
the
maintainer
can
be
either
and
I.
E
Think
that
the
previous
change
that
created,
like
the
decorum
constraints,
the
current
conditions,
was
trying
to
fix
that.
And
now,
with
this
press
request,
we
are
rebuilding
that
bearing
through
flow
so
I
think
that
we
should
find
after
alternative
something
the
burdens
on
risk
could
give
the
the
maintenance
candidate
feedback.
That
is
timely,
but
we
are
not
just
like
you
know,
living
their
request,
for
which
unattended
there
are
many
ways.
E
H
Well,
I
have
a
strong
objection
about
the
statement
and
Ricky
made,
but
not
voiced
about
if
we
have
two
approvals
and
18
natural
from
20
million
years,
we
should
take
this
as
approval
as
a
person
who
gave
a
negative
feedback.
Probably
it
was
the
only
case
for
the
last
six
months.
I
have
to
say
this
is
extremely
hard
to
get
a
negative
feedback
in
maintainer
issue,
especially
if
everyone
else
approves.
You
feel
like
blue
eared
at
this
moment,
and
it's
really
easier
to
slip
to
neutral,
like
I.
H
Don't
have
a
ground
to
prove
neither
objections
and
right
now,
I,
don't
think
we
are
in
the
urgent
need
of
maintenance
for
the
front
end
like
it
was
three
months
ago.
So,
right
now,
I
believe
we
should
follow
the
same
strategy.
We
have
our
record
nerds
when
we
have
four
interviews
and
if
four
of
them
are
yes,
this
is
not
accepted.
A
candidate
is
not
passed.
We
need
at
least
one
strongest
in
this
case
and
I
believe
for
us.
Strong,
yes,
should
be
some
number
of
maintainer
I
agree
with
Sara.
H
Here
maybe
halls
of
maintenance
with
growing
numbers
is
not
a
good
idea,
but
at
least
some
static
number.
We
should
have
like
a
traffic
to
pass
and
like
if
we
have
to
Provos
an
18-inch
roll.
Something
is
not
really
good
here.
Maybe
we
just
need
to
give
this
train
here
a
bit
more
time
to
prove
himself
a
her
stop
just
my
designs
here.
So.
E
H
For
me,
definitely
yes,
because
sometimes
is
too
scary
to
voice
an
objection,
and
sometimes
it
just
a
gut
feeling,
not
something
you
can.
Oh
hey.
This
is
really
wrong,
but
it's
like
I
have
a
feeling
that
this
is
just
not
enough
to
be
a
maintainer,
but
they
cannot
make
an
objection
here,
especially
strong
one.
So.
A
I'm
not
good
at
like
filling
out
surveys,
and
we
have
to
like
you
strongly
agree,
strongly
disagree
or
feel
indifferent.
I'm.
Usually
there
like
check
in
the
middle
in
different
person,
I
think
for
these
kind
of
things.
I
would
not
interpret
in
neutral
as
any
kind
of
objection
or
any
kind
of
approval,
because
we
have
now
16:17
maintained,
errs
chances
are
unless
I've
actually
sat
down
and
reviewed.
A
A
D
Just
wanted
to
say
that
I'm
I,
don't
believe
we're
even
talking
about
this.
We
should
not
count
those
who
are
neutral
or
like
I,
don't
know
what
a
feeling
now
here,
because
we
are
saying
that
neutral
is
either.
People
are,
don't
feel
comfortable
expressing
negative
opinion
or
some
plugins
really.
What
if
I
just
didn't
have
time
to
get
to
the
issue.
Like
am
I
the
only
one
who
gets
into
this
situation,
I.
D
Just
don't
have
time,
like
you
know,
I'm
getting
into
the
maintainer
issue
at
the
end
of
milestone
is
very
challenging
and
I.
Just
don't
have
time
and
it's
like
that's
why
I'm
neutral?
That's?
Why
I
don't
leave
any
comment?
I
can
write
it
down,
but
you
know
I
don't
have
time
now
it
wouldn't
make
my
comment
any
more
positive
work,
any
more
negative,
but
it
will
just
still
mean
that
I'm
neutral
neutral
right,
but
this
doesn't
mean
that
my
count
should
my
voice
should
be
counted
towards
acceptance
or
rejection.
D
It's
still
neutral,
so
I
think
we
have
to.
We
have
to
base
the
matrix
on
extreme,
like
on
only
on
the
positive
positive
reviews
and
getting
back
to
you
too
and
weakest
point
about
maintainer
is
just
not
not
giving
feedback,
but
the
point
of
stimulating
maintain
is
to
get
to
and
give
the
feedback
either
positive
or
negative,
or
explicitly
say
that
yes,
I'm
neutral
here.
This
is
another
story.
How
we
stimulate
maintain
is
to
get
there,
but
this
should
not
be
covered
by
this
request.
D
A
Enrique
brought
this
up:
I
I
suggested
that
we
could
have
two
things.
Is
one
I
think
when
somebody's
maintained
when
some
of
these
Omar's
come
up
and
everyone
is
busy
and
would
we
definitely
some
bit
of
a
bystander
effect
that
can
happen
where
we're
like?
Oh
well,
the
other
maintainer
will
review
this.
A
A
That
person
can
individually
reach
out
to
individual
maintainer
z--
that
they
know
that
they've
worked
with
and
just
I've
been
reached
out
to
like
hey.
Can
you
review
this
and
it
takes
me
a
couple
of
days,
but
someone
pains
me
on
slack
I'm
gonna
most
likely
get
to
it.
Then,
if
I
was
at
in
a
larger
group
and
so
I
think
that's
one
solution
to
fixing
this
radio
silence
that
can
happen
in
some
M
ours.
The
other
thing
is.
A
Maybe
we
do
need
to
give
a
canned
response
to
maintain
errs
of
a
very
neutral
response
so
that
it's
not
like
there's
just
silence
but
I
agree
with
a
lot
with
Enrique's.
We
can't
accept
just
hey
we're
pings
and
now
nothing
happens.
We
need
to
give
even
just
something
like
hey
I,
haven't,
checked
this
out
and
I'm
a
little
busy
right
now.
Please
ping
me
directly.
If
you
want
me
to
look
into
this
like
that,
giving
a
response
to
maintain
errs
so
that
they
can
be
explicit.
A
That
they're
kind
of
expecting
other
maintainer
so
hop
on
might
be
helpful
for
the
sake
of
time.
I'm
gonna
move
on
to
this
point
and
I'm
planning
on
writing
a
comment
about
it
and
I
appreciate
everyone
to
voice
what
your
concerns
are.
I
appreciate
every
K.
If
you've
commented
on
on
this
marriage
request,
one
of
the
one
of
the
arguments,
those
used
in
the
original
mirja
quest
I
thought
that
so
first
back
going
back,
the
original
logic
was
I
thought
had
this
intention,
but
then
now
I'm
realizing
it
kind
of
didn't.
A
Have
this
intention,
so
we
are
doing
somewhat
of
a
reverting
of
an
intention
and
it
sounds
like
one
of
the
arguments
used
was
that
we
should
trust
each
other.
Therefore,
if
someone
says
oh
they're,
you
think
they're
a
maintainer,
hey,
I,
trust
your
maintained
and
I.
Think.
Yes,
we
should
trust
each
other
I.
Don't
think
this
is
mutually
exclusive,
that
extending
trust
and
going
through
this
process
of
getting
approvals.
A
I
But
it
was
a
like
the
best
part
of
the
journey,
because
I've
got
feedback.
I've
got
reassurance.
I've
got
invited
what
I
should
do
better
so
that
then
I
walk
in
the
maintainer
due
to
certain
confidence.
That
I
was
like
that.
Basically,
the
the
confidence
was
even
built
through
the
mr
into
the
feedback
of
the
other
maintainer.
If,
if
somebody
open
an
NMR
and
it's
merged
by
default,
because
some
sort
of
time
passed,
I'm
not
sure
that
they
are
gonna
walk
into
maintainer
with
the
same
level
of
acceptance
of
the
same
level
of
confidence.
I
Maybe
yes,
maybe
no,
but
I'm,
saying
that
you
should
look
at
this
like
an
opportunity,
receive
feedback
more
than
gatekeeping
things
like
you're
in
you're
out,
alright
and
and
I
wanted
to
work
as
well.
Denny's
Danish
point
that
it
doesn't
take
five
minutes
to
do
one
of
those
review.
If
you
don't
ever
collaborated
with
the
person,
it
I
think
it
can
take
up
to
a
day.
I
need
one
yesterday
in
just
the
review
part
without
counting
the
outward
part.
I
It
took
me
half
a
day,
I
wrote
so
number,
but
I
think
we
could
have
a
process
to
think
people
like
first
general,
pink
pink
after
two
three
days,
whoever
didn't
comment
and
then
assign
the
people
that
didn't
command
and
then
after
two
weeks
three
weeks.
Well,
we
can.
We
can
count
well.
Those
are
my
idea
if
you
wanna
I,
expose
them
better
when.
E
I
A
Yeah
I
think
I
think
that's
a
good
call.
When
one
side
note
and
I
started
doing
this
pattern
with
the
last
handful
of
maintainer
Mars
I
reviewed,
even
no
matter
what
my
gut
feeling
was
or
if
I
worked
with
them
or
not,
I
was
I'm.
Gonna,
look
try
to
look
as
unbiased
ly
as
I
can.
What
is
your
mr
description,
based
on
these
reviews?
Here's
some
praise
and
feedback
that
I
can
give.
Even
if
I
think,
okay
I
know
this
person
gonna
be
a
maintainer.
A
There's
a
I
think
opening
up
the
door
to
where,
even
if
someone's
approved,
we
give
feedback,
I
can't
open
up
to
the
door.
We're
okay,
I,
don't
think
this
person
he's
being
Taner
and
here's.
Why
I
think
we
do
have
a
little
bit
of
groupthink
that
can
be
difficult
to
counteract
when
we
don't
think
someone
needs
to
be
a
maintainer
but
everyone's
approved
and
no
one's
given
any
feedback
that
could
be
a
bit
of
a
challenge,
but
also
even
yeah.
A
A
D
A
B
A
A
So,
if
you
guys
have
any
strong
objections
to
this
wording,
or
maybe
we
need
to
create
a
follow
up
for
some
broader
ideas,
that
would
be
helpful
yeah.
It's
next
meeting
time
thanks
everybody
and
unless
anyone
has
any
other
final
remarks,
I'm
gonna
stop,
recording
and
hop
off.
You
all
have
a
great
rest
of
the
day
and
welcome
Jose
to
maintain
errs
I,
don't
like
being
back
on
vacation.
Thank
you,
yeah,
all
right,
I'm.
Sorry,
we
didn't
say
that
even
earlier
all
right
bye,
it
was
an
interesting
discussion
done
thanks,
hi.