►
From YouTube: Ops Section Group Conversation - Preview
Description
This is a recorded preview of content for the Ops Section Group Conversation
Notes - https://docs.google.com/document/d/1zELoftrommhRdnEOAocE6jea6w7KngUDjTUQBlMCNAU/edit
Slides - https://docs.google.com/presentation/d/1-XtXosrDJ6-u-ILCzfmbRQu147QJ1RsVY8A6MwK809k/edit#slide=id.g84a305d6e4_2_17
Issue - https://gitlab.com/gitlab-com/Product/-/issues/1108
A
So
in
particular
slide
from
this
presentation
that
I
wanted
to
highlight-
and
that
is
the
content
highlights,
so
I'll
go
through
those
to
provide
an
overview
and
then
I'm
looking
forward
to
your
questions
and
feedback
tomorrow.
The
first
major
highlight
is
that
the
ops
section
has
been
combined,
it's
hard
to
say
there.
There
are
more
groups
and
more
engineering
investments
and
development
team
members
in
the
former
CI
CD
section,
but
we
used
to
call
them
both
together,
the
ops
section.
A
So
we
call
them
the
Haab
section
again
so
now
verify
package,
release,
configure
and
monitor
are
all
considered.
The
ops
section
I've
worked
to
reorganize
both
this
group
conversation
content
as
well
as
the
direction
page
to
incorporate
that
now,
a
larger
scope
for
the
kind
of
emulate
a
bunch
of
what
we
had
been
a
bunch
of
the
content
that
was
included
in
the
CIC
de
section
previously.
A
But
just
note
that
when
we
say
ops
section,
we
now
mean
what
was
formerly
the
CS
CD
section
and
the
ops
section
combined
next
important
update,
and
this
has
been
provided
in
a
couple
of
other
places.
So
hopefully
it's
not
the
first
time
hearing
it,
but
at
sko
in
January
we
highlighted
that
we
were
working
on
allowing
users
to
shift
from
Jenkins
to
get
lab
and
as
a
result
of
a
bunch
of
investigation.
We've
done.
We
understand
this
is
critical.
A
So
I
wanted
to
make
sure
we
communicated
that
as
part
of
this
ops,
section,
GC
and
I'm
looking
forward
to
you
questions
and
feedback
on
that
content.
The
next
is
that
there
we
have
this
section
in
our
deck
called
exciting
things.
There
are
so
many
exciting
things
that
were
as
a
product
organization
looking
forward
to
being
delivered
in
upcoming
releases
that
I
I
guess
I
could
quickly
highlight
a
couple
of
them,
but
those
would
be
this
adding
of
historical
code
coverage,
data
and
kind
of
a
bubbling
up
of
testing
results
for
higher
tier
users.
A
As
part
of
the
verify
testing
group,
our
Jenkins
wrapper
MBC
as
part
of
the
verified
continuous
integration,
a
bunch
of
work
on
improving
how
we
allow
this
kind
of
quick
adoption
of
runners
in
the
runner
group
fault,
integration
and
release
management's,
deploying
adding
additional
deploy
targets
to
auto
dev
ops
in
the
progressive
delivery
group.
We've
got
great
improvements
in
both
user
experience,
as
well
as
adding
these
kind
of
virtual
repositories
in
the
package
groups,
user
experience
in
terms
of
the
UI
and
being
less
search
and
have
a
different
edition.
Ulm.
A
Netted
data
about
your
packages
right
there
in
context
in
your
when
viewing
your
package
repositories
and
then
in
configure,
we
just
last
week
ran
a
design
sprint,
which
was
really
successful
about
improving
our
crudities
management's,
to
make
it
more
friendly
to
kind
of
enterprise-grade
users
of
kubernetes
and
as
well
as
two
really
important
dog
fruiting
initiatives
and
monitor
work
both
in
terms
of
dog
flirting,
our
metrics
dashboards,
as
well
as
dog
fooding.
Our
instant
management,
Status,
page
and
alert
management
features
here
at
lab
within
the
infra
teams.
A
So
I
said
there
were
too
many
to
summarize
I,
basically
just
read
them
all
and
then,
as
a
product
organization,
we're
also
working
to
adopt
North,
Star,
metrics
holistically,
and
so
there's
a
slide
about
what
North
Star
metrics
are
for
those
who
are
unfamiliar.
We
have
a
great
growth
leader
here
who
have
been
educating
our
whole
organization
on
this,
and
it's
been
super
helpful
for
the
product
groups
to
be
able
to
communicate
with
their
teams.
A
So
there's
some
content
around
the
that
first
meeting
and
a
discussion
of
what
our
North
Star
metrics
should
be
so
as
to
follow
up
issues
to
make
sure
there's
all
get
written
into
the
handbook
and
that
we
are
prepared
for
upcoming
reviews
by
having
implementation
issues
to
implement
our
product
for
those
North,
Star
metrics.
So
I'm
really
excited
about
that.
A
I
think
it
gives
a
really
good
data
focus
to
our
product
groups
and
then,
lastly,
we've
been
having
some
great
think:
big
discussions
in
two
groups
primarily
package
and
release
management,
so
kudos
to
Tim
rosy
and
Jackie
Michelle
for
pushing
those
within
their
groups.
But
it's
been
really
interesting
because
they've
been
talking
about
both
cross
stage
and
cross
section
big
ideas,
bringing
the
kind
of
validated
user
problems
to
their
groups
to
discuss
possible
solutions.
It's
been
a
really
great
way
to
kind
of
embed
design
thinking
into
our
products
group.
So
I'm
really
excited
about
those.
A
Those
are
my
content
highlights.
Last
but
not
least,
this
is
the
first
time
we've
been
doing
this
ops
section
GC
in
the
new,
with
the
new
combined
set
of
stages,
I
tried
to
take
the
best
of
what
Jason
had
been
providing
in
CI
CD
and
combine
it
with
what
I've
been
providing
in
that
ops
section.
But
I
am
interested
in
feedback
on
the
type
of
content
we
provided
and
if
there's
additional
content
we
can
or
should
provide
going
forward.