►
From YouTube: Compliance weekly - 2023-07-04
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
A
B
A
Awesome
the
next
one
is
adding
a
section
of
the
admin
settings,
for
instance,
level
streaming
headers.
B
A
B
Yeah
pretty
much
nailed
it,
so
we
now
have
I
know
we
had
a
list
previously
of
all
the
events
in
our
groups
by
the
FHA
category,
which
makes
it
a
lot
easier
for
users
to
be
able
to
find
particular
ordered
events
and
I
know.
We
have
a
follow-up
issue
around
searching
for
those
feature
categories
as
well.
A
A
C
So
I
have
created
one
Mr
for
this
for
adding
test
cases
and
there
was
no
null
events
getting
generated.
A
So
we'll
go
through
the
planning
issue.
This
is
the
planning
issue
for
16-2
and
yeah
I'll
start
off
the
first
one
is
assigned
to
me,
which
is
the
compliance
adherence
for
both
MVC.
This
structure
is
complete,
I've
also
implemented
one
check.
A
The
Mr
is
in
the
fine
stages
of
interview
with
the
backend
maintainer
they've
added
some
comments,
I'll
be
addressing
them
and
probably
this
should
get
merged
this
week,
I
also
updated
the
okr
for
this
one
to
35
percent,
seeing
the
work
that
we've
done
on
the
back
end
as
well
as
the
front
end
side.
However,
we
might
not
be
able
to
release
the
MVC
by
end
of
July,
which
means
we
might
spill
this
with
the
next
quarter.
A
I
can
also
talk
about
this
one
which
is
assigned
to
me
monitoring
the
kibana
logs,
so
I've
been
monitoring
the
this.
This
dashboard
daily
I
I
also
created
an
MR
for
adding
the
missing
events.
Missing
yaml
files
this
morning,
I
encountered
another
event
which
had
a
missing
Yahoo
file
that
was
related
to
the
recent
Mr
that
we
created
for
Google
Now,
Google,
gcp,
login,
Google,
Cloud
login.
A
So
for
that
one
we
did
add
and
add
a
new
audit
event,
but
somehow
missed
adding
the
ml
file
for
it
so
kudos
to
our
monitoring,
which
catches
these
things
so
yeah
I'll
go
back
to
the
adherence
report.
Ui
it's
with
Jay,
I'm
I,
don't
have
an
update
Nate.
Do
you
have
an
idea
where
we
are
on
this
one?
Okay,
no
problem,
I'll,
probably
sync
up
with
Json
sometime.
C
Yeah,
so
we
are
going
to
release
the
feature
flag
for
this,
as
well
as
the
apis
for
event.
Filterings
are
under
review
or
under
development
right
now,
and
as
well
as
the
I
have
also
created.
One
Mr,
which
we
discussed
last
time
for
creating
the
instance,
go,
for
instance,
level.
Audit
events,
and
that
is
also
under
review
for
similar
found
out
an
issue
with
that
and
I
have
fixed
it
and
I
am
about
to
push
the
changes,
but.
A
That's
also
second,
video
I.
Think
smriti
from
the
Arts
team
is
also
relying
on
that
Mr
yeah.
C
And
the
other
ish
and
the
other
epic
trust
and
safety
streaming
audit
events
that
that
is
assigned
to
me,
the
fourth
one
from
the
down
bottom:
okay
yeah.
So
there
is
also
dependent
on
that
Mr.
So
I'm
writing
this
prioritizing
that
Mr,
so
that
Smithy
pencils,
audit
events
and
this
epic
all
gets
unlocked.
A
C
C
B
This
is
close
yeah,
so
that's
the
one
that
we
just
talked
about.
The
two
biggest
parts
of
this
was
the
well
three
Buddhist
Parts
was
adding
the
listing,
adding
the
grouping
and
being
able
to
search
which
are
all
now
live.
So
we
can
turn
on
the
release
post
for
this
as
well,
which
is
awesome,
there's
a
couple
of
more
follow-ups
that
we
that
we're
going
through,
but
most
of
them
are
all
will
all
be
completed
in
16
too.
So
we're
on
track.
A
B
D
A
A
I
already
talked
about
this
one,
then
the
next
one
is
with
some
converting
the
compliance
touch
put
into
any
second
report
and
I
guess:
Sam
had
some
issues
some
database
issues
with
this
one
I
was
reviewing
one
of
the
Mis
structure.
We
explored
the
CSP,
but
then
it
was
firing
an
N
plus
one
query:
we
still
don't
have
a
solution
to
that.
I'm,
not
sure
where
Sam
is
at
right.
Now.
D
Yeah
next
door
with
me,
so
first
one
is
related
to
the
called
brand
protection.
So
last
week,
I
had
a
call
with
Michael
to
get
the
understanding.
What
we're.
A
D
To
do
so
currently,
this
APK
is
I,
think
seven
second
issues
out
of
them.
We
have
completed
one
so
understanding
the
current
status.
The
completed
one
and
one
is
another
verification,
and
best
of
them
are
logged
on
the
second
issue
in
this
Milestone
I'm
planning
to
deliver
the
second
one:
okay,
that's
probably
the
rest
of
them
16.3
and
the
last
one
which
is
actually
removing
the
old
APA
would
go
to
the
next
major
release.
So
that
is
just
because
it's.
D
A
D
A
A
E
Yeah
I
just
saw
Courage
the
issue
today,
so
we're
waiting
for
the
approval
and
I
gave
enough
information.
I
hope
is
there.
Anything
I
will
just
follow
it
up.
So,
based
on
how
design
thing
is
also
like
in
the
research
phase,
so
I'm
doing
the
Prototype
and
hopefully
like
a
run,
the
research
next
week.
Okay,.
A
Awesome
thanks:
this
was
something
new
to
my
I
was
not
aware
like.
If
we
change
anything
on
the
site
navigation,
we
all
have
to
get
some
additional
approvals.
It's
not
just
as
easy
as
just
renaming
the
tabs.
B
Yes,
that's
just
currently
on
hold
with
all
of
the
changes,
so
nothing
being
done
there
I.
B
It
I
think
that
we're
yeah
we're.
B
A
Now
the
next
one
is
to
review
the
engineering
dashboard,
but
this
is
not
the
first
week
leave
of
the
Milestone
release
posts.
Not
the
final
weekly
I
see
two
items
being
added
by
unit
and
the
requires.
B
Yeah
sure
the
first
one
is
just
around
the
feedback.
I've
created
an
issue
from
the
engagement
survey
survey
that
we
recently
had.
So
please
have
a
read
through
there
and
add.
Your
comments
is
around
some
of
those
results
and
the
second
one
was
Sam
had
raised
a
great
point
in
our
retro.
Around
compliance
pipelines
and
I
know
that
we're
getting
a
lot
of
support
requests
through
slack
and
issues
and
stuff
like
that
at
the
moment
and
I
know,
you
all
has
been
pushing
the
support
side
of
things.
B
B
I
guess
that
there's
two
major
initiatives
that
are
happening
at
the
moment,
which
is
so
compliance
pipelines,
are
moving
over
into
security
policies,
which
just
means
that
there's
a
little
bit
of
a
hold
on
the
work
that
we're
doing.
We
don't
want
to
do
any
improvements
until
that
works
done
and
the
other
one
is.
We
are
talking
with
pipeline
authoring
group
around
trying
to
make
sure
that
we
have
captured
all
of
the
known
issues
that
we
have
and
look
at
a
holistic
approach
to
solving
them
for
compliance
pipelines.
B
A
B
Yeah
so
I
know
we
talked
about
updating
the
Retro
I,
don't
know
if
we
want
to
record
this
or
if
we
should
stop
the
recording
now
and
then
we
can
go
through
that
quickly.