►
From YouTube: Compliance weekly - 2023-08-15
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
B
A
B
Earlier
yeah,
no,
no
problem
just
making
sure
that
I'm
sharing
is
the
correct
tab.
So,
as
the
last
one
we've
discussed
previous
week,
was
this
one
don't
create
feature
flag
updates?
B
So
let's
see
what
do
we
have?
Oh,
not
that
much
we
have
on
the
table.
So
the
first
one
is
don't
create
feature
flag,
update
audit
events
once
Reese
no
change
so
and
if
you
increase
anyone
would
like
to.
C
B
Yeah,
actually,
we
have
like
these
two,
which
are
very
connected,
I,
believe
that
they
should
share
the
same.
No,
no
yeah.
C
B
C
Missing
yeah
we'll
raise
an
error
if
audit
events
recall
that
we
don't
have
audit
type
audit
event
types
for
mm-hmm,
we've
been
well
as
I've
just
been
tracking
that
the
errors
for
a
while-
and
we
didn't
see
any
more
so
now
we're
we've
turned
this
on,
and
we
also
have
a
pre-flight
check
with
left
hook,
that'll
check
for
the
the
docs
and
everything.
C
So
that's
in
conjunction
it
does
I
think
those
two
things
should
should
keep
everything
yamalyzed
for
audit
events.
B
Yeah,
let's,
let's
hope
so
that
everything
will
work
as
expected.
So
the
next
one
is
add
check
quite
entry
for
viewers
and
two
approvals.
B
Oh
that's!
Actually,
nice
I
just
read
the
description
thing
yo.
That
makes
sense
any
one
involved.
I,
don't
know
who
was
verifying
it.
It
was
J.
Okay,.
B
A
I
think
yeah
I
think
this
is
the
final
check
for
the
adherence
report.
So
this
is
the
final
for
the
for
the
MVC
so
step
for.
B
That
yeah,
so
this
is
a
back-end
one,
so
we
should
complain
it
just
curious
if
it
is
complain
it
on
front
end.
Just
just
curious,
like
you
know,
let's
see
it
says
that
you
can
validate
using
the
dashboard,
so
it
is
just
changing
the
stage
from
fail
to
success
so
yeah.
The
front
end
is
here
also,
you
know
when
your
meeting
is
run
by
front-end
persons.
This
is
the
other
thing
which
I'm
always
curious.
B
A
Yeah,
so
we
had
a
instance
where
the
last
week
with
a
compliance
framework,
but
there
was
a
a
bug
where
the
a
value
wasn't
being
evaluated
as
a
billion
properly,
and
so
it
allowed
the
functionality
to
add
edit
compliance
Frameworks
at
the
sub
project
subgroup
level,
so
I
had
so
I
added
in
some
functionality
last
week
to
ensure
that
it's
a
Boolean.
This
was
just
adding
in
a
test
to
ensure
that
it
will
never
be
a
non-billion.
So
it's
just
a
speed
change.
There.
A
Filtering
where,
when
you
select
all
of
the
select
start,
selecting
the
event
types,
you
can't
unselect
them,
so
this
I
discussed
it
with
fluorines
and
it's
a
bug
in
the
gitlab
UI.
So
we've
added
a
we've
closed
this
and
opened
up
a
new
issue
in
the
gitlab
UI
project.
B
B
Oh
sorry,
one
second
scrolling
yeah,
let's
see
let's
go
for
for
for
the
planning
issue
like
let
me
share
it.
Any
yeah
I'm
still
missing,
like
I
I've,
complained
to
your
Nate
I'm,
still
missing,
being
the
part
of
compliance
and
yeah
being
involved.
It
is
a
compliance,
and
you
know
this
one,
sorry
it
this
is
the
it's
a
draft
planning
I
believe
this
is.
This
should
be
yeah.
A
Yeah,
so
we're
just
going
through
this
and
just
explaining
how,
where
we've
got
to
on
each
of
the
items,
so
we
just
go.
B
B
Yeah
but
I
believe
I
believe
it's
a
bit.
It
is
the
wrong
one,
because
we
already
know
I
just
just
linked
the
wrong
one,
because
we
already
have
the
actual
planning
issue.
This
one
should
be
the
relevant.
A
B
Sorry,
no,
no!
It's
just
I'm
thinking,
yeah
yeah,
if
I'm
yeah,
this
is
our
priority
list
planning,
so
anything
to
mention
or
discuss
here
we
should.
Oh
it
is
it
and
I'm
wrong
again:
I
believe
it's
16.5
for
planning
for
compliance,
this
one
sorry
yeah.
A
Still
16-3
for
this
one.
B
Oh
I
I
thought
that
we,
so
we
are
just
because
this
is
my
first
time,
maybe
I'm
missing
something.
Should
we
go
through
current
issues
on
the
planning
board
yeah
this
one
yeah.
A
C
Currently
it's
on
the
back
burner,
because
it's
no
longer
prioritized
at
grid
within
eight
we're
gonna
move
it
to
16
4.,
so
it
won't
be
shipped.
This
release
the
saml
SSO
author,
merge
requests.
I've
opened
a
few
issues
for
the
planning
So.
The
plan
has
been
written
out
so
to
say,
and
in
the
next
Milestone
we
can
start
tackling
those
issues.
B
Yeah
Okay
so
yeah.
This
is
it
for
everyone.
We
have
the
content.
We
have
on
board
now
yeah
so
like
what
what
we
do
next
is
talk
about:
release
pause
blockers.
It
is
a
final
weekly
of
the
Milestone
and
I
believe
it
is
so,
let's
see
what
we
have
of
so
merge
so
Nate.
Could
you
give
us
give
me
a
hand
here
because
yeah
sure
are
we
aware
about
any
blockers,
because
this
is
a
partial,
total
out
of
context
here.
A
A
The
default
heated
branches-
that's
416,
for
instance,
is
all
streaming
ordered
event
filters.
Yes,
that
has
been
finished
and
should
be
released.
The
export
same.
C
Yeah
that
that
one
needs
to
be
held
for
an
extra
Milestone
at.
A
B
A
Yeah,
it's
a
big!
It's
a
big
change
for
the
compliance
group
to
change
from
just
reporting
to
management
and
as.
B
We
move
message
the
message
we
are
sending
to
the
world:
yes,
yeah
events
for
feature
Flags.
B
B
A
I
think
this
is
all
of
the
US,
adding
closing
that
epic
for
all
of
the
audit
event,
information
and
the
that
feature
flag,
that
we
just
just
discussed
that
whose
effort
is
turned
on.
A
B
Is
still
still,
there
are
some
at
least
this
one
issue
opened
and-
and
this
is
yeah
it
is
not
yet
delivered
right.
Yeah,
that's.
C
B
So
probably,
oh
and
there
are
a
bunch
of
of
stuff
there,
so
probably
this
will
not
work
to
make
it
to
the
16.3
yeah.
B
Okay,
great,
so
the
next
part
of
our
flow
is
design
QA
as
a
update.
Oh
sorry,
just
all.
B
The
order
yeah,
sorry
and
the
okrs
for
for
4K,
free
and
I
think
we
would
like
to
take
a
look
and
discuss.
B
B
A
B
C
Can
give
some
update
on
we
have
currently
two
events
of
the
30
we
want
to
add
are
in
Mr
state.
C
If
anyone
this
is
for
people
watching
the
recording
afterwards,
if
anyone
has
new
Mrs
that
add
audit
events,
please
ping
me
on
them,
so
I
can
track
them
within
the
key
result.
There
yeah.
B
C
C
A
C
Have
to
oh
yeah
I
have
yeah
the
key
results
there
yeah,
so
I'll
I
still
need
to
update
that
one
as
soon
as
it's
merged
I'll
update
the
percentage
on
there.
Okay
I
think
the
100.
So
there's
that
scale
with
the
sub
I.
A
A
C
B
B
Nice
yeah,
but
we
have
so
many
stuff
that
video
nobody
knows
how
it
works.
B
Yeah,
so
any
other
stuff.
We
would
like
to
take
a
closer
look.
B
A
B
A
The
one
of
the
reiterate
that
it's,
the
almost
the
end
of
the
Milestone
so
final
emaster,
we
merged
by
Thursday
I-
think
so.
If
you've
got
anything
outstanding,
please
you
know
reach
out
to
anyone
else.
The
group
to
get
them
pushed
through
and
the
Retro
issue
is
up
as
well.
So
please
start
adding
your
thoughts
in
there
if
you've
got
any.
B
Yeah
and
thank
you
for
reminders
that
it
would
be
great
to
have
enrich
or
how
did
the
hackathon
goal.
We
say
shamelessly
missed
yeah,
okay,
so
let's
stop
the
recording
as
it
is
written
here.
So
let's
wait
for
someone
who
is
looking
recording.