►
From YouTube: Compliance final planning 16.1 2023-05-18
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
So
this
is
the
16-1
final
planning
we'll
go
over
the
priorities
and
the
plan
for
this
milestone
all
right.
So
just
starting
out
I
wanted
to
look
at
what
the
product
priorities
are
so
I
put
in
here
the
instance
level
streaming
audit
events
as
the
top
priority.
A
That's
since
we
have
done
quite
a
bit
of
work
on
the
compliance
framework
report,
this
is
moved
to
the
top
of
the
list,
because
it's
something
that
is
important
for
gitlab
itself,
as
well
as
our
customers
not
to
start
to
get
these
events
streaming.
So
that
is
the
top
priority
that
I
have
right
now,
looking
at
the
product
level
stuff.
A
The
second
one
is
the
compliance
adherence
report,
so
this
is
a
huge
benefit
for
our
customers.
Once
we
get
it
done.
So
it's
important
for
us
to
nail
down
the
plan
and
how
it's
going
to
be
implemented.
A
Given
the
changes
that
Nate
and
I
have
talked
about
over
the
past
couple
of
days,
I
have
moved
these
two
audit
event
epics
up
in
priority
to
make
sure
that
we
can
finish
those
off
since
it
looks
like
we
will
be.
We
keep
moving
towards
using
audit
events
in
the
adherence
report
to
report
on
how
well
we
are
our
project
complies
with
a
specific
standard.
A
So
getting
these
audit
events
epics
done,
helps
not
just
the
audit
event
category,
but
also
the
compliance
management
category
by
feeding
into
the
compliance
adherence
report.
So
these
three
are
the
next
priority
and
then
I
have
the
compliance
Frameworks
additional
things
in
there,
as
as
the
last
priority
on
the
list.
This
is
just
closing
off
some
of
the
things
that
additional
functionality
that
we
have
sitting
in
there
so
definitely
not
as
high
priority
as
the
others.
A
Since
this
Frameworks
report
is
working
really
well
and
users
really
really
like
it,
but
it
still
is
a
priority
to
you
know:
make
sure
that
we
finish
out
that
epic
and
get
all
the
improvements
and
Bug
fixes
and
everything
that
we
we
think
we
need,
and
just
to
you
know,
as
always,
just
because
something
didn't
make
the
top
five
priority
list.
For
me
doesn't
mean
it's
not
important.
A
Everything
that
we're
doing
is
incredibly
important,
but
we
we
do
still
have
to
have
a
priority
list
so
making
sure
that
everybody
knows
what
the
top
product
priorities
are
in
terms
of
moving
forward
with
our
customers
and
any
major
issues
that
they're
seeing
so
everything
that
we're
doing
is
incredibly
important.
This
these
just
happen
to
be
the
the
top
things
from
my
perspective,
so
that
we
can
move
the
categories
for
it.
A
B
Awesome
thanks
for
that,
Derek
yeah
I'll
just
go
through
a
little
bit
more
detailed
on
what
we're
planning
to
deliver
in
this
milestone.
So
the
instance
level
streaming
ordered
events.
This
was
the
highest
priority.
We
already
have
the
initial
apis
released
in
the
previous
Milestone.
This
Milestone.
We
want
to
add
the
apis
for
headers
and
filtering
and
complete
the
UI,
so
that
will
be
released.
B
The
next
part.
The
next
high
priority
is
the
adherence
report,
and
we,
like
David,
mentioned
we're
still
just
going
through
the
design
and
planning
phase
at
the
moment,
but
we
hope
to
get
them
to
the
development
in
this
Milestone
and
Elise
deliver
some
of
the
initial
apis
to
help
with
that,
we've
got
the
blocking
merge
requests
if
there
are
failed
status
checks.
B
This
just
has
a
couple
of
small
in-flight
follow-up
issues
that
we
just
want
to
tidy
that
one
off
and
close
that
Epic
within
next
have
the
ordered
events,
schema
definitions
and
performance
limits
that
we're
working
on.
These
are
both
maintenance
tasks,
but,
as
they're
mentioned
there
critical
for
helping
a
lot
of
the
other
features
that
we
want
to
deliver
off
the
back
of
it
and
we
hope
to
have
all
of
the
event
type
schemas
added
the
an
API
created
to
produce
that
information
and
some
auto-generated
docs,
which
will
be
fantastic.
B
And
then
we
have
a
list
of
other
small
things
that
are
in
flight
and
the
only
one
that
I
wanted
to
call
out
was
the
instance
level.
Audit
events
we're
hoping
to
get
stuck
into
some
of
those
more
high
priority.
Audit
events
and
start
adding
those
and
the
other
one
was
the
export
feature
for
the
compliance
violation
report,
which
we
think
will
be
very
helpful
for
users
as
well.
A
Yeah
I
think
that
that
one
thing
just
to
mention
from
my
side
going
forward
and
looking
at
the
next,
you
know
few
months-
I
think
that
getting
more
figuring
out
which
audit
events
are
important
for
things
like
the
compliance
adherence
report
or
our
customers
expect
for
just
a
basic
level
of
auditing
is
going
to
become
more
important.
So
I
would
expect
us
in
the
future.
A
You
know
in
the
next
I,
don't
know
two
to
three
months
to
focus
a
little
bit
on
some
missing
a
lot
of
events
and
to
to
look
at
you
know
what
what
we're
doing
there
so
as
we
close
off
some
of
these
I
think
that
it
will
probably
see
some
more
of
that
filter
into
the
into
the
plan
here,
but
yeah,
just
to
kind
of
make
sure
that
we
are
aligned
within
the
audit
events
and
the
compliance
maintenance
categories.