►
From YouTube: Engineering Productivity Weekly update 2022-03-07
Description
Review the previous week and week ahead for EP team
A
Hey
engineering
productivity
team,
it's
kyle
here
with
the
march
7th
2022
team
overview.
I
wanted
to
try
recording
this
this
week,
instead
of
just
talking
through
it
in
the
team
meeting,
so
we'll
see
how
well
this
works.
This
will
be
the
first
time
first
off.
I
want
to
talk
about
last
week,
I
think.
Last
week
the
team
did
a
great
job,
making
progress
on
some
research
items,
collaboration
with
community
contribution,
workflow
automation
and
prep
work
for
the
work
type
transition
which
I'll
talk
about
here
in
a
bit.
A
We're
also
inundated
with
high
severity
reactive
work
last
week,
mostly
related
to
some
danger
bot
token
leaks.
So
we
had
this
cert
issue
2011
and
then
later
in
the
week,
2071,
where
we
rotated
the
danger
bot
toke
group
token
twice
and
on
the
second
time
we
reduced
the
permissions,
which
was
a
recommendation
from
security
coming
out
of
the
first
one
to
develop
from
admin
to
developer.
So
if
the
credentials
leaked
it
has
minimal,
it
has
less
permissions,
but
that
created
a
problem
with
danger.
A
A
What
happened
is
review
apps
deployed
between
those
two,
mrs
essentially
were
had
their
secrets
corrupted
and
could
not
be
restored
based
on
how
our
review
apps
work,
so
we
had
to
go
through
and
clean
them
up.
We
believe
cleanup
has
happened,
I'm
we're
going
to
continue
monitoring
throughout
the
week,
but
these
were
two
really
urgent,
unplanned
things
that
came
up
and
impacted
our
plan.
A
One
of
the
things
that
we
changed
coming
out
of
that
was
the
work
that
we're
doing
to
support
mr
type
classification.
I've
decided
to
push
a
week.
Originally,
it
was
targeted
to
rename
labels
and
implement
two
link
this
week
and
just
with
the
amount
of
disruption
we
had
last
week,
we're
going
to
push
that
to
tentatively
march
16th
I'll
talk
more
about
that
here
in
a
bit
now
I
want
to
go
through
and
just
review
the
normal
things
we
we
talked
about
so
looking
at
our
current
milestone
priority
one
work.
A
A
Some
of
these
have
a
question
mark
and
just
need
some
review.
I
think
everything
that
is
pipeline
common
will
actually
use
the
latest
version
of
danger
by
default.
But
I'll
ask
a
question
to
confirm
the
other
thing
that
became
urgent
is
we
found
that
we
are
not
compliant
with
gitlab.com,
webhook
standards
and
I'll,
say?
Enforcement
of
that
policy
is
gonna
start
over
the
coming
months.
A
So
I
we.
I
prioritize
this
issue
that
remy
had
created
higher
and
he
had
started
a
proof
of
concept
for
shifting
all
of
our
event,
processors
to
be
async,
we're
going
to
need
to
refocus
on
that,
and
this
will
probably
be
remy's
top
priority
when
he
returns.
But
this
will
be
something
as
a
team.
We
need
to
stop
merging
any
new
event
processors
so
that
we're
not
getting
further
out
of
compliance
with
the
guidelines
of
how
quickly
we
should
respond
to
the
web
hook
event.
A
Lastly,
ash
is
out
on
pto
the
next
few
weeks.
I
we're
gonna
need
some
help
on
this
gdk
fresh
install.
This
is
blocking
new
installs
of
the
gdk
on
mac
os
x,
so
gdk
maintainers
are
helping
out
here,
but
this
is
something
I
and
other
people
on
the
team.
Please
jump
in
here
when
you
can
and
I
believe
this
gdkhs
on
mac
runners
is
going
to
move
into
1410
looking
at
priority.
2
work,
pretty
good
progress
here
on
a
lot
of
these
items.
A
A
The
one
thing
that
looking
for
help
here
is
documenting
default
issue
and
merge
request
template.
There's
a
number
of
projects
in
here.
I
think
eight
that
we
can
go
through
and
at
and
we're
identified
to
add
this
to
this
would
be
a
good
way
to
dog
food,
a
new
community
contribution
that
landed
in
the
last
milestone,
I
think,
14-8
and
then
looking
ahead
here
we
have
23
issues
most
are
signed
out.
A
So
so,
if
I
go
to
none,
we
have
four
issues
that
someone
can
pick
up
here
and
if
and
so,
if
you're
looking
for
for
more
work,
this
would
be
a
good
place
to
start.
If
there's
nothing
that
that
is
available
on
the
priority
one
or
priority
2.
next,
I
want
to
talk
through
mr
rate
for
our
team.
So
we
closed
out
february
at
13.2,
which
was
a
little
bit
higher
than
I
expected
based
on
our
team
pto,
and
that
we
had
team
member
onboarding.
A
You
can
see
here
in
february
we're
already
at
five
and
we're
down
to
four
team
members
that
are
included
in
the
denominator,
so
how
many
people
on
our
team,
so
I
kind
of
expect
this
to
be
back
around
17
to
20,
like
we
had
previously
had
going
back
to
september
in
most
months,
where
there's
not
a
lot
of
pto,
actually
I'll
say
we
do
have.
I
still
have
a
fair
amount
of
pto
this
month,
so
maybe
15
to
20.
I'll
change
my
mind
on
that.