►
From YouTube: Compliance weekly - 2023-05-23
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
B
C
Take
that
as
a
yes
yeah.
C
All
right,
I'm,
not
on
the
right
one
hold
on.
A
C
All
right
update,
streamed
audit
events,
filtering
list.
C
E
That
was
for
clockhouse
I.
Think
title
could
have
been
known
descriptive.
It
was
regarding
the
Google
Cloud
login
configuration
and
we
have
now
a
table
called
audit
events.
E
C
Let's
make
that
clearer
all
right.
Next
one
was
the
Define
audit
event
type
schema
definition
for
project
approval
rules,
events.
C
All
right,
then,
we'll
have
improved
stops
marking
for
the
test,
utilts.
That
one
is
on
ill
yeah.
F
Yeah
this
is
related
to
our
viewfree
migration
I'm.
So
unfortunately,
the
bot
is
labeling
it
with
group
activities.
So
this
is
my
desperated
attempt
to
deal
this
like
to
improve
our
viewfree.
Just
use
compatibility
still
a
long
way
to
do,
because
it's
insane
how
bad
the
old
code
is
in
the
previous
version
of
the
test.
Tutules
sorry
using
this
one
minute
of
Glory
to
complain,
yes,
yeah,
but
anyway,
we
are
moving
somewhere
forward.
C
A
Yeah
we
had
to
wait
for
that
to
be
run
over
the
weekend.
It's
probably
been
run,
but
haven't
actually
verified
it
yet
so
all.
E
B
It's
very
simple:
it's
just
adding
the
accessible
names.
It
came
out
of
the
job
where
we
disabled
the
compliance
pipeline
field
for
premium
users.
So
we
just
added
accessible
names
to
all
of
the
the
fields
in
there.
D
This
is
actually
blocked
on
once
we
close
all
like,
add
all
the
audit
event
type
yml
files,
then
once
we
ensure
that
we
don't
have
any
more
audit
events
that
have
a
missing
yaml
file,
we'll
start
raising
an
exception
if
a
new
audit
event
is
being
added
without
the
corresponding
yaml
file.
So
for
this
we
need
to
create
all
the
existing
arms
and
then
we'll
add
an
instrumentation,
maybe
a
log
line
to
check
if
we
don't
have
any
other
existing
Auditors
and
then
we'll
work
on
this
one.
F
Yeah
I'm
not
sure
why
this
was
not
closed.
I
believe
it's,
it
is
probably
we
are
not.
There
was
an
idea
originally
that
we
filter
also
for
just
protected
branches,
but
I
believe
it
was
renamed
so
I'm
also
thinking
that
this
is
already
implemented
fully.
D
D
Unless
we
have
an
issue
to
track
that
particular
feature
where
we
want
to
filter
by
protective
branches,
we
can
close
this
one.
A
C
Right
or
design
anything
on
there,
Camellia.
G
Oh,
nothing,
special,
the
ux
roadmap,
still
blocked
by
the
research,
need
to
be
done
by
Michael
for
the
job
to
be
done
and
the
adherence
support
they
decide
not
to
use
Sasa
now
and
I'm,
going
back
a
little
bit
on
the
design
for
using
gitlab
checks.
So
I
will,
in
the
following
days,
probably
archive
all
of
us
and
update
the
new
ones.
With
the
new
example
we
decided,
and
with
the
last
one
there
can.
We
go
back
to
the
board.
C
C
B
B
So
you
should
be
able
to
see
it
now,
so
we'll
just
have
a
quick
run
through
the
engineering
dashboard.
So
we've
been
sitting
at
99.99
on
the
era,
budget
availability,
so
great
work,
everyone
that's
been
impressive,
seeing
it
over
the
last
three
Milestones
actually
for
Emma
types,
we
have
feature
actually
get
above
maintenance
again,
which
is
another
good
sign.
So
we
try
to
get
that
60,
30,
10.
I
know
that
we
always
have
a
lot
of
maintenance
issues
for
different
bits
and
pieces.
B
But
Ms
yeah
type
by
Milestone
anyway,
we've
seen
a
slight
decrease
in
the
Mr
rate
from
our
previous
high
of
4.89
down
to
3.3
I'm,
going
to
have
a
look
into
this
because
this
might
be
down.
A
B
Aaron
joining
the
working
group
a
month,
among
other
things,
so
having
extra
people,
but
not
having
people
tagged
on
the
right.
Emails
might
cause
this
because
you
can
see
from
our
graph.
B
Also,
anyone
shout
out
if
you
can
see
anything
to
talk
about
in
here,
feature
Flags,
so
we've
got
five
feature
Flags
currently
listed
here.
D
The
last
one
which
is
introduced
in
157
the
good
protective
advantages.
This
is
like
blocked
by
a
couple
of
bugs
right
now,
so
we
are
unable
to
look
out
and
possibly
in
discussion
with
moving
this
to
Resource
code
team
like
because
they
own
the
actual
feature.
So
that's
why
it's
been
still
stale.
B
Good
point:
does
anyone
know
about
this?
One,
really,
our
protected
branches
for
group.
D
So
I
mean
what
the
third
and
the
fifth
are
both
related
to
each
other,
the
first
one
we
are
unable
to
roll
it
out
because
it's
the
same
name
as
the
future
name,
so
we
created
another
feature
flag
on
top
of
that.
So
it's
like
an
all
condition.
If
either
of
these
are
enabled
the
feature
works,
so
I
guess
these
two
are
linked.
B
No
yeah
I
should
have
seen
it
from
there
yeah
one.
Seven
eight
go
passed
you
bugs
by
severity,
so
we've
got
no
S1
these
two
bugs
that
are
past.
Due
at
the
moment.
It's
good
and
I
know.
We've
got
a.
A
B
C
C
I
can
I
have
a
also
bring
this
up
for
everyone.
We
have
like
a
weekly
pairing
that
we're
trying
to
do.
It's
also
open
for
anyone
else
who
wants
to
join
and
we're
free
to
change
the
time
up
a
bit
right
now.
It's
set
one
UTC,
but
yeah
13,
UTC.
Sorry,.
D
The
this
one
like
set
status,
check,
I
just
got
a
notification
today
and
it's
been
assigned
to
me
for
maintain
a
review
like
I.
Just
got
it
a
couple
of
hours
ago.
So
probably.
A
B
D
Thanks
a
lot
everyone
for
hitting
the
audit
event
paper,
Mrs
special
thanks
to
Hashima
for
creating
that
script
between
like
the
static
and
the
dynamic,
getting
the
events
that
we
have
it
was
that
was
also
pretty
tricky
and
then
net
picking
up
all
the
most
of
the
Mrs
dating
the
yamas.
So
thanks
a
lot
with
that
in
mind,
I've
updated
the
okr
progress
to
sixty
percent
since
you've
now
left
it
only
a
few
enamels
that
need
to
be
able.
E
If
next
one
is
with
me,
so
we
have
completed
the
clickhouse
schema
design
for
audit
events,
which
brings
our
okay
progress
to
25.
A
B
And
next
was
just
a
fire
for
me
around
the
quarterly
kickoff
IMA
was
earlier
today.
So
please
have
a
read
through
that
document
in
the
recording
there
there's
some
really
interesting
stuff
around
the
direction
and
strategy
that
we're
taking
over
the
next
quarter
so
have
a
good
read
of
that.