►
From YouTube: 2021-08-04 Development Group Conversation
Description
The Development Group Conversation for 2021-08-04
A
Hello,
my
name
is
christopher
loveholtz,
and
this
is
the
development
group
conversation
pre-video
presentation.
I
am
the
vice
president
of
development
and
I
will
unfortunately
not
be
able
to
attend
the
meeting.
Tim
zellman
will
be
there
to
answer
questions
associated
with
that.
I
have
been
in
jury
duty
for
actually
the
past
several
weeks
and
because
of
that,
tim
has
been
filling
in
as
my
dri
for
the
development.
A
As
always,
we
start
off
the
group
conversation
with
what's
top
of
mind.
The
big
thing
is
that
we've
been
finishing
up:
q2
and
q3
and
q
finish
up
q2,
okrs
and
then
starting
on
q3
okrs
and
getting
those
kind
of
planned
out
we've.
Definitely
in
the
past
month
been
more
focused
on
our
reliability
and,
as
such,
we've
been
participating
at
the
height
stand
up
around
gitlab.com
availability,
which
has
turned
into
a
daily
stand
up
where
development
is
taking
on
a
number
of
initiatives.
A
Several
other
things
listed
below
there,
narrow
rate
retention,
hiring
culture
amp
and
the
database
decomposition
error,
as
well
as
consider
reporting
of
a
test
to
postgres
sql.
Most
of
those
are
standard
things.
The
last
one
is
something
that
stan
has
been
thinking
about
and
I'm
trying
to
actively
participate
in
moving
forward.
A
We
also
focus
on
how
we're
doing
as
an
organization
from
a
headcount
perspective,
we've
been
grown
in
the
last
eight
weeks
from
270
to
275,
we're
still
tracking
to
grow
the
team
to
roughly
3
15
by
1st
of
february.
Because
of
that
we
have
several
positions
open
and
we
look
to
hire
and
grow
past
attrition.
So
that's
one
of
the
areas
of
focus
that
you'll
see
in
the
coming
quarter.
A
Other
kpi
metrics
that
we
keep
an
eye
on
our
maintainers
and
engineering
to
maintainers.
We
continue
to
grow
the
number
of
maintainers
associated
with
overall
efforts,
as
well
as
looking
at
our
maintainers
per
mr,
where
we
want
to
get
those
numbers
above
a
certain
threshold.
We
start
just
we're
starting
to
see
cases
where
we're
actually
getting
above
that
threshold.
That's
a
little
bit
due
to
a
little
bit
slower,
mr
rate,
so
we'll
continue
to
focus
on
adding
additional
maintainers,
as
I
mentioned
before
july,
has
been
a
slower
mr
rate
month.
A
This
is
due
to
a
number
of
things.
In
particular,
we
have
definitely
seen
pto
rising
pretty
steadily
in
the
past.
Several
months
july
and
august
are
historically
months
that
folks
take
a
vacation
and
because
of
lowering
of
restrictions
related
to
the
pandemic,
we
definitely
have
seen
additional
vacation
be
taken.
We've
also
are
starting
to
see
our
facing.
You
know
the
friends
and
family
day
if
we
look
year
over
year,
so
that
affects
our
numbers
by
about
four
to
six
percent.
A
A
Other
kpis,
oma
and
omar,
which
have
been
instituted
in
the
past
couple
months.
Our
review
efficiency
looks
pretty
solid.
From
that
perspective
below
target
age,
open
mrih
is
another
area.
We've
been
focusing
on
a
little
bit,
but
not
as
much
as
we
need
to
to
get
it
below
the
30-day
target.
A
Essentially,
we
have
changed
to
basically
cloudflare
is
our
single
caching
provider
and
that
helped
reduce
our
threshold
looks
like
we
can
make
her
target
somewhere
between
one
and
a
half
and
a
second
from
that
perspective
and
we'll
make
that
adjustment
here
in
the
coming
month
for
okrs
looking
pretty
solid
overall
for
q2,
as
you
can
see,
overall
we're
between
the
60
to
80
mark.
For
most
cases,
only
one
that
technically
is
behind,
which
was
the
culture
amp,
that's
mainly
because
we
just
have
some
final
pieces
to
do
around
our
audit.
A
Basically,
we
have
a
heavy
focus
on
reliability,
which
is
part
number
two,
that's
around
a
lot
of
the
gitlab.com
stand-up
items
and
then
also
we
do
have
a
little
bit
of
arr
focus
as
well
around
cloud
licensing
workspaces
and
then
making
sure
that
our
our
database
can
scale
through
functional
decomposition.
A
We
also
will
continue
to
build
a
better
team
through
360
reviews,
completing
our
hiring
objectives
and
we're
looking
to
also
get
the
team
to
take
technical
writing
training
during
this.
During
this
quarter,.
A
Just
a
little
additional
information
for
this
particular
group
conversation
around
the
availability
and
scalability
and
the
things
that
we're
doing
and
development
around
this.
You
see
the
items
listed
here,
pretty
heavy
focus
on
the
first
two,
which
is
fixing
the
infra
dev
issues.
We
actually
get
a
head
count
reset
associated
with
that
in
item
six
and
then
also
looking
at
implementing
error
budgets
fully
during
this
current
quarter
and
making
sure
that
our
slos
are
I'm
saying
toothy.
A
That's
an
american
colloquialism
for
meaning
that
we're
much
closer
to
the
slo
results
than
a
way
than
a
objective
that
we're
not
even
close
to
meeting.