►
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
Hey
everyone,
so
my
name
is
austin.
I'm
a
product
designer
here
at
git
lab
and
today,
I'm
gonna,
be
presenting
on
the
category
for
compliance
management,
talk
about
kind
of
where
it
is
today
and
where
we're
trying
to
take
it
in
the
future
and
this
all
kind
of
falls
under
the
compliance
group
to
provide
a
little
more
context,
the
compliance
group
falls
into
the
managed
stage.
A
We
have
a
couple
other
categories
as
well
that
we're
responsible
for
like
audit
events
and
audit
reports,
but
today's
talk
to
me
just
focused
on
compliance
management
as
a
tie-in
to
that
our
main
persona
that
we're
trying
to
solve
for
is
cameron
the
compliance
manager.
A
unique
attribute
about
cameron.
Is
this
role,
isn't
necessarily
like
a
job
title.
So,
unlike
maybe
like
sasha
the
software
developer,
you
don't
really
see
anybody
carrying
necessarily
a
compliance
manager.
A
It's
something
that
comes
up
like
quarterly
semi-annually
in
a
regular
pattern
for
companies
as
they're
building
out
their
software
products,
and
they
just
have
to
produce
these
audit
reports
and
be
ready
at
any
moment
to
show
whether
or
not
they're
ready
to
go
in
terms
of
their
regulations
that
they
have
to
meet,
and
so
with
that
there's
been
a
lot
of
excitement
in
the
industry
in
terms
of
checking
out
what
our
competitors
are
doing.
Microsoft
recently
announced
the
general
availability
for
their
compliance
manager.
A
This
caught
some
of
our
leadership,
detention
eric
was
bringing
up
questions
about
it.
Talking
about
how
this
is
what
I
see
like
for
compliance
management
within
git
lab
in
terms
of
just
like
the
visual,
aesthetic
and
whatnot
of
it,
and
so,
while
we
are
very
excited
to
see
a
bunch
of
competitors
and
different
companies
trying
to
help
solve
problems
for
compliance,
it
helps
validate
our
position
to
try
and
also
help
solve
it.
We're
also
trying
to
start
with
the
building
blocks
to
get
there.
A
So
daniel
was
a
designer
on
compliance
before
I
joined
gitlab
in
june,
and
he
opened
up
an
epic
time
to
cast
his
vision
for
where,
like
the
compliance,
dashboard's
going
a
key
component
of
compliance
management
and
matt.
My
product
manager
and
I
are
continuing
to
work
together
to
try
and
show
how
we're
going
to
progress
that
through
this
epic.
A
So
why
not?
Just
like
make
the
thing
something
that
I
love
to
do
just
when
I
feel
like
I've
gotten
stuck
in
the
weeds,
maybe
think
about
things
at
a
higher
level.
Try
and
like
tie
together
a
bunch
of
cool
ideas
that
I
see
in
the
industry
just
to
kind
of
play,
with
some
of
the
options
that
we
have
as
a
way
to
bring
a
little
excitement
to
the
team
and
look
at
things
in
a
way
that
we
haven't
necessarily
thought
about.
Before.
A
A
lot
of
these
things
already
exist
today
in
gitlab.
Let's
say
at
the
project
level
like
you:
can
you
can
customize
your
push?
Rules
emerge,
request,
approvals
and
protective
branches,
and
so
on
so
forth,
but
some
of
those
things
aren't
as
extensive
at
the
instance
and
group
level,
and
so
a
big
effort
we've
been
trying
to
do
is
to
like
create
some
parity
across
the
different
levels
within
gitlab.
So
you
can
provide
more
flexibility
to
those
compliance
managers
that
are
trying
to
administrate
their
git
lab
spaces.
A
So
those
building
blocks
are
super
crucial
and
today,
like
I
said,
compliance
management,
it's
it's
quite
minimal.
You
can
go
in
and
you
can
add
a
label
to
a
project.
If
there
are
five
that
we
get
out
of
the
box,
they
don't
do
anything
necessarily
they
just
you
just
kind
of
can
say
hey.
This
project
has
to
abide
by
the
sox
regulations,
but
gitlab's
not
forcing
you
to
do
anything
a
way
you
can
leverage
these
labels
to
start
administrating.
A
A
So,
besides
kind
of
like
setting
up
the
compliance
management
for
git
lab,
you
can
monitor
somewhat
how
your
projects
are
abiding
by
or
not
abiding
by
the
compliance
that
you
set
forth.
So
the
compliance
dashboard
today
shows
you
just
the
most
recent
merge
requests
for
each
project,
and
you
can
imagine
how
like
seeing
that
at
a
group
level
like
yeah
I'm
going
to
miss.
You
know
some
merge
requests
if
they're
very
active,
like
gitlab's,
a
very
good
example
of
that
we
have
merge,
requests
coming
in
all
the
time.
A
A
So
talking
a
little
bit
about
how
that
evolution
is
unfolding,
the
left
side
shows
you
the
current
view
of
our
merge
requests
page
on
the
compliance
dashboard.
It
tells
you
a
little
about
each
about
each
of
those
merge
requests,
but
what
we've
really
been
hearing
from
some
of
our
customers
and
a
few
other
people
we've
been
interviewing
their
jobs
to
be
done.
Is
they
really
want
to
see
the
information
in
terms
of
like
a
chain
of
custody?
A
A
Cameron
would
have
to
go
into
each
project
and
check
out
all
these
things
individually,
and
what
we've
heard
is
that's
very
painful,
especially
for
companies
that
have
like
thousands
of
projects
in
gitlab
or
even
hundreds
to
click
into
each
one
have
to
get
pinged
on
a
bunch
of
different
merge
requests.
It
can
be
very
cumbersome
and
easy
to
get
lost
in
the
mess
and
trying
to
understand
like
what
is
our
holistic
view
of
compliance
today,
so
we're
trying
to
refine
what
we
currently
have,
but
we're
also
trying
to
investigate
what
we
have
in
the
future.
A
This
way
like
a
new
page
and
just
demoing
it
a
little
bit
with
some
of
our
customers,
we've
been
able
to
get
some
really
great
feedback
just
by
showing
them
things
and
doing
like
just
a
quick
gut
check
like
does
this
make
sense
to
you?
How
would
this
help
you
in
your
workflow,
and
sometimes
you
hear
things
like?
Oh
my
gosh
yeah,
if
I
could
have
this
one
thing,
show
me
like
yeah
my
there
are
these
violations.
A
That
would
be
super
helpful
for
me
to
know
exactly
where
I
need
to
go
fix
projects,
or
they
might
say
things
like.
You
know
the
security
step,
it's
nice
to
know
that,
but
it's
not
super
helpful
to
me.
In
this
instance,
I
could
just
go
somewhere
else
to
find
that
information
getting
just
a
little
bit
of
that
direction.
That
helps
us
better
understand
what
exactly
we
want
to
do
in
terms
of
prioritizing
what's
important.
Next,
I
wanted
to
highlight
a
few
questions.
A
Actually,
that
mike
had
actually
asked
me-
and
I
thought
they
were
really
good,
so
the
first
thing
he
was
asking
was
like:
how
do
you?
How
are
you
using
this
to
better
inform
your
solution?
Validation,
like
I
was
saying
getting
that
quick
feedback
from
customers
and
some
of
our
sales
calls
like
it's
been
helpful
because
cameron's
not
an
easy
persona
to
identify
and
get
feedback
from,
and
so
getting
that
direct
feedback
from
the
customers
that
are
using.
A
It
also
feels
like
that
gives
them
a
voice
into
the
product
itself,
so
it's
been
really
cool
to
see
them.
Vocalize
that
and
we've
also
gotten
really
great
feedback
in
terms
of
seeing
like
we've
got
25
customers
that
want
this.
This
many
licenses
want
this
type
of
feature
and
that
helps
us
guide
the
conversation
better
within
issues
as
we're
moving
through
the
validation
track.
A
The
right
hand
side
shows
a
little
bit
more
of
a
refined
nbc
that
we
took
from
the
inspiration
on
the
left.
So
one
thing
that
we're
identifying
is
push
rules
at
an
instance
level.
They
don't
necessarily
get
inherited
down
all
the
way
to
a
project.
So
what
do
you
do
if
you're
cameron
and
you've
set
these
instance
level
settings?
But
now
you
have
thousands
of
projects
and
they're
all
doing
something
different.
A
Another
really
interesting
question
that
mike
was
asking
me
was
so
how
do
you
like
make
sure
compliance
doesn't
get
in
the
way
of
everything?
And
I
think
it's
really
two
things,
the
first
thing
being
that
we
try
and
embed
it
so
that
it's
more
seamless
into
the
process.
We
don't
want
it
to
feel
super
cumbersome
that
teams
are
having
to
be
compliant
and
like
a
better
like
term
like
I
just
wanted
to
feel
like
you
can
continue
doing
your
work
and
be
compliant
without
knowing
it.
So
by
gentle
guidance
along
the
process.
A
We
can
help
teams
make
sure
they're
abiding
by
it,
without
necessarily
feeling
they
have
to
read
thousands
and
thousands
and
thousands
of
pages
of
documentation
around
controls
and
policies
and
make
sure
you're
meeting
everything.
A
great
example
of
this
is
a
lot
of
teams
require
that
emerge,
requests
have
an
issue
or
a
jira
issue
or
like
a
servicenow
ticket
to
be
associated
with
the
merge
request
in
order
for
it
to
be
merged.
A
That's
not
something
that
is
enforceable
today
in
gitlab,
but
we
would
really
love
to
continue
moving
towards
that
direction.
So
we
have
like
an
issue
out
there
right
now.
That
would
allow
you
to
enforce
some
sort
of
relationship
to
be
linked,
and
if
that
linkage
doesn't
exist,
then
you
can't
merge
just
yet
so
as
soon
as
you
create
that
linkage
great,
you
can
merge
and
you
don't
have
to
worry
about.
Knowing
all
the
policies
gitlab
is
helping
you
be
compliant.
A
The
other
thing
is
trying
to
keep
compliance
a
little
bit
isolated
from
the
rest
of
the
workflow.
We
know
that
for
developers
they
don't
necessarily
care
about
knowing
about
compliance.
That's
for
a
different
persona.
That's
for
cameron!
That's
for
sydney,
so
we
want
that
to
be
a
little
bit
different
from
how
everybody
else
is
experiencing
gitlab.
It's
just
the
boundaries
and
guidelines
that
we're
trying
to
put
in
place
to
make
it
a
safe
place
to
build
and
ship
software.
We
don't
want
to
become
the
hurdle
that
prevents
people
from
shipping
software.
A
We
just
want
them
to
feel
safer
doing
it
so
that
way
that
pain
they
might
feel
later
on
in
an
audit
won't
necessarily
happen
for
just
a
little
bit
of
effort
up
front.
If
you
knew
earlier
on
that,
you
needed
to
attach
a
merge
request
and
link
it
to
a
jira
issue,
or
something
like
that
before
you
merge.
That's
a
lot
better
in
terms
of
just
solving
that
quick
pain.
A
A
B
Thank
you
austin.
I
actually
have
a
question
and
sorry
I
didn't
pop
it
into
the
chat
before
it
seems
to
be
that
you
are
touching
on
some
of
the
functionality
that
other
teams
are
also
working
like
the
dashboards
or
like
them.
Mr
widget,
are
you
collaborating
with
with
the
other
stage
groups
around
those.
A
Yeah
definitely
I
have
found
that
a
lot
of
our
issues
that
we
have
opened.
It's
like,
there's,
usually
some
sort
of
other
category
or
other
group
that
we're
touching
on
and
it's
been
really
fun
for
me
to
get
to
collaborate
like.
I
think
of
some
really
great
conversations.
We've
had
with
pedro
and
marcel
around
the
merge
requests
view,
because
we've
been
trying
to
introduce
a
couple
of
compliance
features
in
that
page
and
while
we
have
opinions
on
where
we
think
things
make
sense.
C
Or
yeah
I'll
make
a
comment
which
is
so
first
of
all,
thank
you
for
the
collaboration.
I
also
really
enjoyed
hearing
you
talk
about
how
you're,
looking
at
that
larger
vision
and
getting
it
in
front
of
customers
in
a
seems,
like
kind
of
a
minimal
low
fidelity-ish
way
to
say,
like
hey.
Is
this
even
what
you
want
so
that
way,
y'all
can
work
backwards
from
what
what
what's
actually
going
to
be
useful?
C
I
think
the
more
of
that
we
can
do
the
better,
because
it
saves
us
a
lot
of
time
and
resources,
building
things
out
that
people
may
not
want
to
put
some
reality
around
this.
I've
worked
places
where
development
every
year
would
have
to
stop
for
a
month
for
manual
compliance
audits,
and
that
was
so.
People
could
go
through
and
literally
manually.
Look
at
everything
that
happened
in
the
other
11
months
of
the
year
and
go.
Are
we
compliant
yes
or
no?
C
And
then
I
mean
not
only
is
that
time
consuming
and
tedious
and
it
kills
the
company's
velocity
for
a
month,
but
it's
also
not
super
accurate
right.
I
mean
now
you're
relying
on.
Have
I
seen
everything
I
needed
to
see
have
I
made
the
connections
that
I
needed
to
make
so
automating
this
building
into
the
regular
workflows
to
where,
like
you
talked
about
it's
like,
I
need
to
know
here,
the
information
is
there
there's
nothing
else.
I
need
to
do.
That's
really
really
powerful,
for
especially
for
larger
enterprise
customers.