►
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).
A
A
The
actual
measure
for
that
was
99.98
and
that
is
great
to
see.
There's
been
so
much
going
into
reliability
across
all
of
engineering,
including
infrastructure.
A
Over
a
number
of
months,
and
for
quite
a
few
months,
we
have
not
been
meeting
the
target
of
the
99.95
availability,
and
so
it's
great
to
see
that
reached
for
october,
and
we
look
forward
to
being
able
to
reach
that
more
often
as
we
go
forward
and
have
the
additional
changes
in
our
process
and,
of
course,
in
the
underlying
infrastructure
that
we
continue
to
work
on
month
over
month
to
support
this
important
goal
for
our
gitlab.com
customers.
A
There's
a
lot
of
things
that
have
gone
into
that
some
links
in
here
to
to
read
some
more
about
that
and
then
I'll
move
on
to
our
okrs.
We
have
established
our
key
results
for
q4
that
we
will
be
working
on
and
we're
for
each
one
of
these
working
on
refining
the
individual
scope
of
each
one
of
the
items.
A
So
we've
got
three
different
areas
around
reliability
and
tech,
debt
reduction
and
objective
for
that
contributing
to
new
revenue
opportunities
and
then
the
third
objective
around
our
team
effectiveness
and
the
team
member
experience.
So
there
are
key
results
in
each
one
of
these
areas
linked
to
ally.
If
you
want
to
take
an
additional
look
at
that,
and
certainly
if
there
are
questions
we'd
love
to
have
those
in
the
in
the
group
conversation
tomorrow.
A
So
a
few
different
discussion
topics
that
we
welcome
you
to
ask
about
and
learn
some
more
about.
The
first
is
around
corrective
actions.
We've
had
a
group
of
individuals,
basically
one
of
our
squads,
working
on
both
refining
and
also
closing
out
corrective
actions,
because
we
had
quite
a
backlog
of
those,
and
so
they
have
been
very
focused
on
that
activity
and
they've
had
some
great
results
over
the
past
couple
of
months.
So
there's
more
information
in
the
in
the
deck
about
that
and
again,
we'd
love
some
questions
about
it.
A
Another
focused
topic
has
been
around
the
work
that
the
delivery
team
has
been
doing
along
with
the
registry
team
in
supporting
the
new
container
registry
database,
and
so
this
has
been
work
going
on
over
the
past
few
months
to
basically
ensure
that
this
new
container
registry
databases
is
with
is
integrated
within
the
rest
of
our
delivery
pipeline
and
that,
for
you
know,
each
new
release
as
well
as
migrations
going
forward.
A
A
We
we
have
implemented
this
concept
of
squads
within
infrastructure,
basically
to
result
in
a
more
manageable
number
of
projects,
also
see
some
better
better
velocity
and
quality
come
out
of
those
projects
and
and
ultimately
allow
us
to
tackle
more
of
a
backlog
as
as
well
as
the
the
new
requests
that
that
come
in
for
various
sorts
of
reliability
work.
A
So
additional
details
in
here
and
in
in
the
links
off
of
off
of
this
slide
and
then
finally,
a
note
about
our
incident
manager.
Expansion,
that's
been
happening
over
the
last
month.
We
currently
have
this
new
schedule
going
where
we've
expanded
from
just
four
people,
filling
the
incident
manager
role
and
doing
that
on
a
24x7
basis
to
now
a
set
of
shifts
that
that
bring
in
24
people.
So
we're
definitely
approaching
this
from
a
many
hands,
makes
light
work
approach
and
but
also
looking
for
some
better
results.