►
From YouTube: Quality: Engineering Productivity Weekly 2020-06-23
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
B
B
I
say
we
jump
into
it,
we'll
catch
him
up.
I
know
it's.
B
All
right
we'll
go
ahead
and
get
started
with
the
social
discussion.
I
thought
this
would
be
a
nice
change
of
pace
from
last
week's
what
olympic
sport,
so
this
one.
B
If
you
had
a
time
machine
what
time
period
would
you
like
to
travel
to
and
rules
forward
or
backwards,
so
you
can
go
either
direction
for
me,
I
I
think
it
would
be
pretty
cool
to
see
like
go
back
to
ancient
egypt
and
kind
of
see
like
the
construction
of
some
of
the
pyramids
and
just
some
of
the
massive
buildings
that
they
were
able
to
construct
with
way
less
technology,
just
just
to
observe
how
that
was
done.
D
Yeah
yeah
and
enchanted
egypt
is
is
a
good
one,
because
it's
still
a
mystery
how
they
build
the
pyramids
yeah.
I
don't
know
for
me.
Maybe
I
would
like
to
travel
like
in
the.
D
Future
don't
know
why
just
to
see
how
it
would
be,
but
then,
if,
if
I
would
travel
in
the
future,
I
think
I
would
choose
like
very
far
in
the
future,
like
not
in
a
few
hundred
years,
but
a
few
thousand
years,
and
maybe
I
will
be
alone,
like
the
only
human.
D
But
yeah
I
don't
know
because
so
either
I
would
be
alone
because
humanity
would
have
been
like
disappeared
from
from
her
or
maybe
humanity
would
have
gone
into
space
yeah.
D
I
don't
know
frankly
yeah
that's,
but
that's
yeah,
that's
a
fun
question
mark.
Isn't
here
I
guess
so.
Maybe
alberto
is
a
good
answer
to
to
that.
C
I
don't
know,
I
guess
for
me,
probably
like
the
middle
ages
like
one
year,
1000
ish,
because
I
feel
like
in
asia
there's
not
a
lot
of
history
that
goes
back
to
that
period.
C
So
I'm
curious
like
what
happened
in
those
years
like
in
asia
or
like
australia,
even
like
the
entire
asia,
pacific,
australia,
new
zealand.
I
don't
know
what
what
happens
there
like.
We
read
a
lot
about
like
the
european
medieval
ages,
but
not
so
much
about
asia.
A
I
think
I'm
mostly
curious
about
the
future
that
two
things
one
is
that
how
the
tech
will
evolve
into
life
if
those
sci-fi
stories
could
be
true,
can
this
can
those
tag
be
true
or
there
will
be
some
other
different
texts
and
the
other
is
how
text,
how
tag
impacted,
how
people
live
like
now?
B
That's
interesting
awesome
I
this
this
is
probably
one
of
the
better
questions
in
a
while
that
was
that
was
pretty
fun.
I
appreciate
everybody
sharing
moving
into
the
announcements
just
a
few
few
quick
ones.
There's
two
updates
two
department
updates
this
week
to
be
aware
of,
and
I
I
think
pretty
much
everybody's
provided
feedback,
but
the
group
conversation
is
tomorrow
and
the
engineering
key
review
is
today.
I
link
to
the
agenda
as
well
as
the
mr,
with
a
lot
of
the
api
updates.
B
So
please
review
those
as
you
have
time
and
as
always
everything's
kind
of
in
draft,
so
you
can
always
just
make
changes
and
make
it
better.
B
Next
item
is:
please
try
to
prioritize
or
work
with
me
if
you
need
extra
time
to
find
a
diversity,
inclusion
and
belonging
activity
that
you're
interested
in
this
does
tie
to
our
q2
okrs
for
the
department.
B
I've
been
trying
to
figure
out
how
I
can
do
like
a
big
brother
program
locally
with
kovid
and
then
looking
for
a
backup
just
of
a
dni
brg
here
at
the
company.
So
please
try
to
find
something
that
aligns
with
what
you
feel.
B
It
so
it
doesn't
have
to
be
local.
I
think
what
some
of
the
other
department
members
are
doing
is
just
joining
an
erg
that
aligns
with
their
interests.
I
I
wanted
to
do
something
local,
just
to
kind
of
connect
a
little
bit
more
with
the
community.
B
That's
why
I
chose
that
program,
but
because
of
kobit
like
I
had
kind
of
started
those
discussions
in
march
and
they
were
like
we're
not
taking
anyone
because
pandemic
and
now
they're
trying
to
figure
out
how
to
change
it.
So
so,
if
you
have
an
opportunity
locally,
you
feel
passionate
about
it.
I
support
you
do
it
if
not
an
erg
erg
is
an
option
to
look
at
within
gitlab
and
then
anything
else
on
that.
B
Yeah
so
there's
meetings,
it's
an
employee
resource
group,
so
it's
just
like,
like
they'll,
have
meetings
usually
once
a
month
or
once
every
few
months,
that's
kind
of
related
to
I'll
add
a
link,
that's
related
to
the
what
the
employee
resource
group
kind
of
represents.
A
B
Okay,
another
another
week,
another
360
feedback
update.
I
saw
this
morning
that
the
peer
review
period
actually
got
extended
to
wednesday.
B
So
another
short
term
extension,
if
you
haven't
provided
feedback
and
and
are
still
looking
for
the
opportunity
to
please
feel
free
to
leverage
that
the
next
few
steps
are,
that
I'll
be
reviewing
and
sending
results
by
friday
of
this
week.
So
releasing
the
surveys
to
you
after
it
makes
after
I
go
through
them,
and
then
I'll
set
up
an
additional
discussion
from
our
normal
one-on-one
during
the
week
of
the
july
6th
through
the
the
weeks
of
july
6th
through
the
20th.
A
B
To
review
and
discuss
feedback
with
you
all,
I
was
happy
this.
I
wasn't
happy,
but
I
woke
up
this
morning.
Thinking
like
I
wonder
if
they
extended
the
deadline
and
sure
enough
it
was
I
I
kind
of
chuckled
when
I
saw
that
so.
Lastly-
and
I
mentioned
the
team
on
this
this
earlier
today,
I
opened
a
documentation,
mr
for
deprecating,
backstage
it's
currently
in
draft.
B
Can
you
use
review
and
feedback
remy?
Thank
you
already
for
the
review
and
feedback
I'm
trying
to
target
wrapping
this
wrapping
up
all
of
our
team's
feedback
for
thursday
and
then
broadcast
it
further.
So
please
try
to
get
me
feedback
before
then,
if
possible,
otherwise,
we'll
just
take
it
whenever
we
can
get
it.
So.
Thank
you.
B
All
right
moving
into
the
agenda,
I
did
want
to
talk
about
mra
because
it
kind
of
came
together
a
little
bit
faster
than
what
I
anticipated
we
were.
We
were
like
reviewing
and
then
it
was
like,
let's
just
ship
it,
so
I
did
want
to
bring
it
to
everyone's
attention.
I
know
it
was
talked
about
in
the
department
call
as
well.
B
I
want
to
reiterate
that
this
is
not
an
individual
measure
but
kind
of
a
department
level
measure
and
apologize
for
not
making
the
team
aware
that
this
was
even
happening
until
it
was
done.
So
that's
something
I'll
look
to
do
better
in
the
future
and
then
just
wanted
to
open
up
for
questions.
A
B
Yeah,
so
I
I'm
not
sure
the
way
that
that
part
works,
and
I
I
know
you
were
in
an
earlier
one
because
I
confirmed
all
of
the
team
members
are-
and
I
just
think
once
the
last
adjustment
was
made.
I
I
must
have
missed
this,
but
my
understanding
is,
you
should
be
in
there.
It
looks
at
employees.
It
looks
at
mrs
that
are
authored
by
employees
that
have
a
department
of
quality
it's
coming
in
from
banff,
so
I
will
track
that
down.
I
really
appreciate
you
pointing
that
out.
D
So
I
do
have
another
question.
I
didn't
wrote
it,
but
yeah
is
I'm
wondering
if
the
the
department
is
the
right
level
for
viewing
this
data
like?
Basically
we
don't
have
the
same.
D
Responsibilities
as
it
is,
and
we
are
not
like
we're
not
working
on
the
same
things
and
and
maybe
having
this
high
level
quality
department.
Mr
rate,
is,
I
don't
know
he
is
blurring
he's.
Maybe
it's
too
averaged
and
like
let's
I
I
didn't
look
at
the
numbers.
So
let's,
let's
take
the
assumption
that,
for
instance,
our
team
has
an
mr
rate
of
10,
let's
say,
but
the
average
is
five,
then
we
could
decide
to
take
actions
for
the
whole
department.
D
Even
if,
like
our
team
is,
is,
is
already
at
a
good
pace.
Let's
say
yeah
I
will
stop.
I
will
stop
there
talking
and-
and
let
you
like
answer
me
because
I
don't
want
to
talk
too
much
but
yeah.
B
B
Yeah
yeah,
I
so
the
thing
I'll
call
attention
to
is
this
is
really
the
first
iteration
of
this
with
the
development,
mr
rate,
they
look
at
that
as
that
that
gets
drilled
down
further
to
section
groups.
I
think
we
will
look
to
evolve
the
same
just
to
help
get
that
insight,
so
as
we're
starting
to
look
at
what
are
some
corrective
actions
that
we
can
do
to
raise
this,
how?
How
does
it
look
across
all
the
teams,
so
we
can
try
and
identify
bottlenecks,
I'll
say
or
like
or
different
areas.
B
I
agree
with
your
the
general
assumption
there
that
the
way
that
we
would
influence
increasing
our
mr
rate
is
going
to
be
quite
different
than
the
rest
of
the
department,
I'm
not
sure
aligning
to
the
development.
Org
is
the
right
workaround,
but
I
kind
of
look
at
it
as
getting
insight
to
each
of
the
the
teams
within
quality
will
kind
of
help
reveal
more
information
to
ask
better
questions.
D
Yeah,
I
think
it
should
be
grouped
by
teams
like
yeah
teams,
basically
because
in
the
end,
it's
the,
I
think
it's
like
the
manager
who
is
kind
of
driving
this
ammo
rate,
I
would
say
like
trying
to
understand
what
can
be
improved
and
all
of
that,
because
the
manager
has
the
high
level
view
of
of
the
team
and
yeah
the
at
the
department
level
like
and
the
opposite
example
that
I've
gave
just
before.
D
Is
that,
for
instance,
if
we
decide
in
the
engineering
productivity
team
to
if
we
want
to
increase
our
rate,
maybe
we
will
manage
to
increase
it,
but
if
we
it
will
not
reflect
at
the
department
level
if
the
rest
of
the
department
doesn't
do
anything.
B
Yeah
yeah,
I
I
think
this
is
good
good
discussion,
good
good
thoughts.
Looking
ahead,
I
don't
have
a
really
good
answer
for
you
at
the
moment,
other
than
we
need
more
information
to
help
identify
identify
better
areas
to
focus,
and
I
definitely
agree
that
what
you're
saying
that
the
way
that
different
teams
can
influence
increase
in
their
mr
rate
is
going
to
be
different,
especially
when
you
look
at
our
team
compared
to
the
rest
of
the
department.
D
B
D
B
Yeah
yeah
and
the
other
thing
I
call
attention
to
is
like
we
can
support.
C
Yeah
just
curious,
so
I
saw
some
private
projects
in
the
list
so
like.
If
we
contribute
to
other
projects
like
personal
private
projects
or
other
other
groups,
do
we
need
to
exclude
them
manually
or
something.
B
B
This
is
looking
at
all
mrs
authored
by
everyone
who's
in
scope
and
that's
why
these
these
private
projects
are
showing
up.
I
don't
think
they
need
to
be
excluded.
I
don't
know
I'm
not
going
to
say
that
work
needs
to
be
done
differently,
but
they're,
not
they
in
general.
They
likely
aren't
being
counted
anyways.
C
Not
quite
so,
I
think
my
question
is
so.
If
let's
say
I
were
to
contribute
to
another,
like
a
private
project,
do
I
need
to
specifically
list
down
like
these
other
projects
that
need
to
be
excluded
from
this
calculation.
B
Nope
yeah,
so
we
we're
looking
at
all
all
projects
that
are
is
part
of
product
true,
and
that
list
was
actually
expanded.
As
a
part
of
this,
mr,
like
the
creation
of
this
mra,
to
add
some
of
the
quality
projects
that
we
that
we
generally
work
in
so
like
gitlab
qa
is
an
example.
There's
a
constrained
list
of
projects
that
feed
into
the.
D
D
Fine
having
this
personal
project
instead
here,
even
if
it's
just
for
information,
but
I
don't
want
everyone
to
see
that
yeah,
even
if
the
problem
the
project
is
public,
yeah,
just
a
side
note.
B
D
Okay,
because
this
is
like
all
the
all-
the
dashboards
will
have
the
same
patterns
right.
B
Yeah
yeah,
so
this
is
happening
at
every
department
under
engineering
and
engineering,
so
we're
all
all
these
dashboards
are
getting
developed.
Quality
just
happened
to
be
first
because
since
we
worked
with
the
development
mra,
we
thought
it
would
be
a
good
candidate
to
try
burst
and
ux.
I
think
ux
just
finished
theirs,
we'll
have
security
infrastructure.
Every
every
single
department
will
have
this
it'll
be,
and
I'm
as
these
dashboards
are
being
created.
C
B
Yeah
I'll
open
an
issue
to
discuss
and
mention
the
team
I
I
agree.
The
other
thing
to
consider
is,
is
I
I
you
know.
I
know
this
might
be
a
hot
topic,
but
I
know
that
there's
work
to
being
done
to
kind
of
split
like
personal
and
work
usage
of
git
lab
away
from
your
user
id.
So
if
it's
associated
with
personal
work
might
be
something
you
want
to
consider
moving
towards
a
different
gitlab
user,
I'm
not
telling
you
to
do
it,
I'm
just
saying
that's
something
to
consider
as
well.
B
Or
just
discussion
in
general,
okay,
moving
on
to
team
refinement
activities,
I
merged
the
mr,
that
was
I'll,
say
the
first
iteration
of
documenting
prioritization
activities
and
linked
to
it
here
last
week
I
was
going
to
try
to
do
this
for
13-2,
but
I
think
we
were
just
a
little
just
a
little
too
late,
so
I'm
going
to
target
13-3
for
trying
to
follow
those
schedules
and
see
where
there's
friction
or
see
where
it
breaks
and
I'm
as
a
part
of
this,
I'm
experimenting
in
sisense
and
the
product
to
see
how
we
can
better
identify
the
amount
of
planned
versus,
unplanned
work
that
we
do
within
a
release,
because
I
think
that'll
help
inform
how
full
should
the
release
be
right.
B
Now,
it's
it's
more
guest,
it's
more
of
an
art
than
a
science,
and
I
that's
not
the
world
that
I
like
to
live
in
if
I
can
avoid
it.
So
any
questions
on
that.
D
Yeah
so
yeah,
I
have
a
first
version
of
time
zone
based
review,
roulette
suggestions.
So
you
can,
you
can
see
in
the
merge
request
below
an
example.
D
For
now
the
strategy
is
to
choose
someone
for
which
the
local
hour
is
between
6
a.m
and
2
p.m,
so
that,
hopefully,
the
person
will
will
get
to
the
merge
request
in
their
working
day
in
their
work
day
and
so
yeah
any
any
feedback
on
that
is
welcome
and
you
can
see
in
the
in
in
the
roulette
message.
I
I
display
also
the
time
zone
of
the
reviewers
and
the
the
difference
compared
to
the
hotter
deodorant
time
zone
like
two
hours
ahead
or
before
the
auto
so
yeah
any
any
feedback
on
that.
A
D
A
B
And
maybe
that's
a
a
next
iteration
is
figure
out,
there's
a
way
to
signal
my
working
hours.
I
know
that's
something
that
can
be
added
in
slack,
but
I
think
it's
a
free
form
text
field
so
something
that
we
can
improve
on
in
the
future.
B
B
C
D
Yeah
or
maybe
we
could
so
right
now,
I
I
did
that
like
the
duplicates
and
maybe
we
could
either
like
default
like
show
the
time
zone
based
one
and
then
put
the
legacy
one
in
like
a
detailed
block.
A
B
B
And
just
to
add
some
more
detail
here,
I
didn't
want
to
just
go
all
in
on
time
zone
and
overload
for
viewers
and
maintainers
in
certain
time
zones
until
we
have
a
better
idea
of
how
this
up,
how
this
change
kind
of
impacts,
the
metrics
that
are
that
are
there.
C
Another
feedback,
I
think
it's
about
communicating
this
change
and
the
reason
behind
it,
like
I
think
I've
heard
quite
a
few
feedback
about
people
are
not
clear
why
they
are
being
recommended
by
roulette.
So,
like
one
was
the
backend
engineer
being
recommended
for
the
test
category
so
and
then
also
similarly
for
a
maintainer
for
ep
so
yeah,
I
think
we
need
to
inform
in
advance.
D
Yeah,
I
should
I
will
update
the
documentation,
also
and
probably
link
to
it
like
document
the
the
strategy
that
that
is
used
and
but
yeah.
I
will
also
communicate
but
yeah
for
the
moment
yeah
I
haven't
communicated
because
we
haven't
chosen
the
solution,
but
yeah.
Definitely
that's
a
really
good
point.
B
I'll
I'll
leave
it
up
up
to
you.
Okay,
on
that,
should
we
handle
the
format
of
the
message
just
async
on
the
issue.
Just
add
add
the
feedback
or
the
mr
add
the
feedback
to
the
mr
and
then
see
what
see
what
makes
sense.
The
reason
why
I
specifically
brought
that
up
is,
I
looked
at
it
and
it
just
seemed
very
long
like
like
a
long
message
so.
D
Yeah
I
yeah,
let's
take
take
it.
I
think,
and
I
will
try
to
gather
a
few
feedback
from
a
few
people
just
to
get
a
like
an
idea
of
what
other
people
think
yeah
I
will
but
yeah.
Let's,
let's
continue.
I
think,
thanks
for
the
feedback.
B
Yeah,
I
I
thought
it
was
really
good
how
it
came
together.
So,
like
a
lot
of
the
everything
behind
it
looks
really
really
good.
I
think
it's
just
kind
of
putting
the
final
touches
on
it
unless
I
might
be
missing
something,
but
that's
the
impression
I
got
this
morning.
B
B
B
B
So
the
two
problems
it
looked
like
were
happening
was
pulling
the
image
failed
because
of
the
way
that
the
docker
config
json
secret,
with
with
with
that
having
username
and
password,
they
were
being
used
for
every
single
image
poll
and
it's
likely
that
those
credentials
were
either
rotated
or
something
changed
with
the
credentials.
Recently
that
made
that
that
part
fail
and
then
the
second
thing
that
failed
was
that
the
cert
expired.
B
I
think
it
was
on
the
third
of
july,
so
when
the
serverless
function
was
getting
created,
the
istio
sidecar
container
in
the
in
the
pod
was
failing
to
talk
back
to
istio
because
of
https
errors,
so
we
regenerated
shenzhen,
and
I
regenerated
that
cert
on
friday
and
things
started
to
behave
again
and
after
I
think,
like
a
minute
or
so
everything
getting
healthy.
B
B
D
Yeah
I
mean
my
point:
is
it's
actually
probably
the
same
as
you
I'm
just
confused
by
these
state
deployments?
D
I
I
looked
at
the
logs
and
like
maybe
half
of
them
are
like
the
last
log
is
like
the
the
board
is
shut
down
like
it's
showing
a
goodbye
message.
So
it's
really
not
used
anymore,
like
I
think
it
was
on
19th.
D
So
it
was
last
week
probably
when,
when
you
fixed
the
problem
and-
and
there
are
other
deployments
that
that
actually
have
the
their
error
from
last
week
like
couldn't,
find
spec
helper
file
or
something
like
that,
and
there
is
only
one
deployment
that
I
think
one
deployment
that
is
actually
doing
work
and
yeah.
I'm
also
confused,
because
just
because
I
I
don't
I'm
not
familiar
with
this
serverless
setup,
I'm
confused
that
these
state
departments
so.
B
Yeah
I'm
I
share
that
confusion.
I
was
unsure
as
to
why
these
deployments
stay
out
if
it
was
something
that
we
have
to
programmatically
say:
tear
everything
down
when
we
deploy
something
new
that
was
handled
as
a
part
of
the
deployment
process
where
it
brings.
Everything
brings
the
old
version,
the
old
pod,
the
pods
tied
to
the
old
version
of
the
function
down
when
the
new
deployment's
there
so.
B
The
other
thing
I
did
want
to
call
attention
to
this
was
probably
buried
that
spec
helper
error
that
that
you
saw
last
week.
I
think
that
was
from
a
very
old
version.
B
So
when
I
looked
at
those
pods,
the
version
of
the
serverless
function
it
was
using
was
like
a
year
old,
so
there
are
deployments
that
have
been
okay
that
were
like
the
deployment
object
themselves
and
I'll
I'll
try
to
tie
that
in,
but
that
xd
lvm
deployment.
I
think.
B
I'll
have
to
try
and
hunt
through
that,
but
I
was
I
had.
I
had
identified
the
version
just
by
getting
a
remote
promoting
into
the
the
pod
and
seeing
what's
going
on
so.
B
Okay,
yeah
and
I
guess
what
concerns
me
is:
I
don't
understand
the
service,
the
service
layer
well
enough
to
know
when,
when
a
web
hook
is
processed,
if
we
have
these
old
deployments,
could
an
old
version
of
the
serverless
function
actually
be
handling
those
web
hook?
Events
and
not
necessarily
doing
all
the
reactions
that
we're
looking
for
that's
the
thing
that
I
would
say,
I
was
most
concerned
about
and
unsure
how
to
figure
it
out.
C
B
Yeah
I'll
ask
nick
just
because
serverless
kind
of
everything
got
consolidated
into
the
configure
group.
So
there
was
talk
like
talks
of
things
being
split
out,
but
now
everything's
in
the
configure
groups,
I'll
ask
the
em
and
say.
C
B
D
B
A
B
B
I'll,
take
a
look
at
everything,
I'll
work
with
nick
to
find
to
get
support
from
the
configure
group
to
just
be
able
to
provide
us
some
some
insight
versus
interrupting
the
team,
like
we
did
last
week
when
it
was
down,
and
then
I
don't
know
what
to
do
about
the
gitlab
ktl
namespace
stuff.
I
think
we
do
need
to
clean
them
up,
but
maybe
a
lower
priority.
B
I
wonder
if
this
is
a
cluster
that
someone
in
configure
is
using
so
like
if
it
was
originally
created
under
gitlab
qa
resources
as
a
part
of
creating
triage
serverless.
But
now
it's
used
for
a
different
purpose.
So.
C
D
Oh
yeah,
sorry,
oh
yeah,
I
didn't
realize
the
workloads
weren't
filtered
like
yeah
on
the
cluster
yeah.
It
makes
sense.
D
B
I
would
agree
there
cool
okay,
so
I
I
will.
I
will
look
to
do
look
to
have
a
little
bit
more
specific.
Ask
the
other
thing
I
would
ask
of
you
all
is
if
you
have
ideas
on
how
we
can
prevent
triage
serverless,
like
essentially
being
down
for
an
unknown
amount
of
time,
like
checking
the
up
time
beyond
what
we
have
today.
B
D
Yeah,
could
we
have,
could
we
have
like
a
function
that
just
replies
okay,
something
like
that,
and
that
will
be
very
wrong.
A
B
Yeah
any
any
boring
solution
here,
I
think,
would
be
good
so
something
that
is
simple
and
can
give
us
more
confidence
than
what
we
have
today.
I'm
I'm
all
for
figuring
out
the
right
path
forward
there.
If
we
can
dog
food
some
of
the
features
eventually,
that
doesn't
have
to
be
like
the
first
iteration,
but
if
we
work
towards
dog
fooding
monitor
even
better
but
yeah.