►
From YouTube: Compliance weekly - 2023-07-26
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
Welcome
to
the
compliance
weekly
sync
for
the
26th
of
the
seventh.
The
first
order
of
business
is
to
walk
the
Milestone
board,
so
I'll
share
my
screen
and
we
can
go
through
the
closed
issues.
A
A
Yes-
and
this
was
to
win,
a
new
stream
was
added,
it
was,
or
new
header
was
added
to
a
stream.
It
was
being
added
to
the
bottom,
so
now
they're
being
added
to
the
top
of
the
list
rather
than
the
bottom,
which
makes
it
easier
for
users
to
see
the
next
one
was
with
hadish.
B
So
this
issue-
this
issue
was
created
a
year
ago
and
we
are
not
able
to
recreate
it.
So
after
some
analysis,
we
have
closed
it
up
for
now,.
A
No
next
one
was
improved
disabling
of
ordered
event,
streaming
destinations.
So
now
Lorenz
has
done
some
great
work
on
when
adding
new
streams
or
editing
streams
when
the
save
button
was
randomly
being
enabled
and
disabled,
so
that's
been
updated.
Now
the
next
was
the
correct,
graphql
API
for
adherence
report.
That
was
josefa
I,
don't
know
if
you
can
speak
to
it.
Jay.
C
Yeah
so
josefa
had
created
the
new
graphql
endpoints
for
the
adherence
reports
and
they
included
filtering
and
I
verified
it
well.
Production
and
I've
integrated
it
with
the
UI
for
the
front
end
and
that
front
NMR
is
just
on
the
maintainer
review,
so
hopefully
there'll
be
a
full
end-to-end.
A
Awesome
next
one
was
another
one
from
Lawrence
which
was
UI
alignment
of
streaming
order.
Events,
follow-up,
I
verified
this
one
is
small
ux
follow-up
to
adjust
the
headers
for
extreme,
oh
cool.
A
A
This
was
the
header:
Heights
of
the
inputs
was
slightly
off,
but
this
is
actually
to
do
with
the
gitlab
UI
component
tree
and
Firefox.
So
we've
created
a
new
task
within
that
project
and
close
this
one
out.
The
next
one
was
hitesh
would
don't
create
external,
ordered
events
when
there
is
no
change.
B
So
yeah
it's
part
of
a
data
big
pitch
and
make
sure
that
no
add
audit
events
are
being
generated
if
there's
no
change
in
the
updation
of
their
use.
So
there's
five
group
level
external
audit
event,
so
I
created
an
MR
for
adding
aspects
for
checking
whether
events
are
being
created,
so
they
were
not
getting
created.
So
just
left
it
with
that.
B
B
This
as
name
suggests
so,
for
instance,
level,
external
audit
event.
This
API
deletes
the
event
filters.
B
A
Think
right,
the
next
one
is
with
Jay
the
compliance
report
to
compliance
Center.
C
Yeah,
so
this
one
finally
got
merged
in
just
the
update
tune,
rename
that
Tab
and
Page
headers
to
compliance
center
from
compliance
report.
C
A
That,
yes,
any
changes
to
the
menu
need
to
go
through
the
approval
process
which
we
lived
about,
and
so
we
can
oh
I'm
not
in
there
anyway,
and
the
final
one
was
the
Samoa
authentication
for
based
approval
rules
with
Sam.
This
was
just
closed
because
it
was
promoted
to
an
epic
and
more
issues
were
built
underneath
that
epic,
as
it's
going
to
take
a
little
bit
longer
than
that
to
get
through
foreign.
A
C
Yeah,
so
the
basic
structure
for
16.3
looks
like
it's
in
place.
The
back
end
with
the
graphql
queries
are
working
as
intended,
and
the
front
end
is
just
going
through
the
or
phase
one
of
the
front
is
just
going
through
reviews
right
now
and
it's
on
track.
B
With
this
one,
the
major
thing
that
is
remaining
is
for
cleaning
up
of
the
feature
flag
other
than
that
there
are
several
Mrs
created
for
adding
audit
events
for
either
Predators
or
headers,
and
they
are
under
review
or
just
at
the
final
stage
other
than
that.
There
are
several
follow-ups
added
to
this
sorry.
A
I
won't
just
add
to
that.
The
filtering
UI
EMR
is
in
final.
Maintainer
review
had
just
gone
through,
so
you
can
round
to
feedback,
so
hopefully
that
gets
merged
the
next
one
was
the
streaming
audit
event
filtering
with
the
UI,
so
the
name
field
Emir,
is
in
final
review.
So
hopefully
we
can
do
that
and
the
filtering
by
project
and
API
has
not
been
started,
but
that's
on
track.
A
B
Yeah
for
this
I
recently
created
a
Mr.
You
can
do
a
POC
locally,
so
you
can
take
a
pull
and
try
to
actually
integrate.
C
A
Awesome
I
just
wanted
to
call
that
that
was
a
great
PSA
that
you
did
with
the
email.
This
looks
really
good.
Next
one
was
the
ordered
event:
type
schema
definition
NBC
with
who's
afer.
So
does
anyone
have
an
update
on
this
I
know
a
tissue
might
have
been
looking
at
the
era
reporting
from
the
yamls.
B
Sorry,
yeah
I,
I
reviewed
it
and
there
was
I
had
some
different
opinion
regarding
the
Mr
related
to
raising
an
error
or
exception
or
showing
a
5x
exercise
while
testing
it
out
so
yeah.
That
is
under
review
right
now.
A
Oh
and
I
know
who's
over
had
been
working
on,
adding
the
undefined
yamls
and
there
has
been
basically
a
week
without
any
undefined
ones
coming
through.
So
I
think
we're
captured
everything
at
the
moment
and
so
we're
on
track
for
closing
that
the
next
one
was
the
recruit.
Retry
failed
external
status
checks
with
Jay.
C
Yeah,
so
this
one
also
on
track
how
smart
had
some
good
feedback
to
move
their
code
to
a
worker
so
I'm,
just
in
the
middle
of
getting
that
done
and
pushing
that
one
and
then
continuing
with
the
Mr
that
was
already
created
a
few
weeks
ago.
A
Fantastic
and
I've
got
a
update
from
Sam
on
the
violation
report
export,
so
he
has
had
some
additional
database
maintainer
feedback
on
the
final
Emma
that
is
taking
into
consideration.
But
it's
on
track
to
be
finished
this
week,
slash
early
next
week
and
the
next
one
was
the
replace
drop
down
selection
with
hasima.
B
Yeah,
so
in
this
issue
we
are
actually
trying
to
use
a
new
column,
which
is
a
Json
B,
so
Trend
strategies
we
have
some
issues
completed
and
backfilling
of
the
data.
I
have
created
two
Mrs
for
backfilling
of
the
data.
Once.
D
C
A
The
next
one
was
the
SEMO
SSR,
as
I
mentioned
before.
That's
been
promoted
to
an
epic
and
Sam
is
currently
planning
this
out
and
still
reading
more
of
the
code
to
understand
where
changes
needed
can
be
made.
The
final
one
for
this
group
is
the
stream
of
order
event
requirements
with
the
Tish.
B
So
I
started
working
on
one
of
the
issues
in
this
and
I
found
out
that
there
are
already
audit
events
being
streamed
for
that,
and
we
just
need
to
make
minor
changes
in
it.
So
accommodate
the
issue.
B
Have
one
thing
I
forgot
to
add
in
my
replace
the
drop
down
selection,
there
is
a
one
issue
in
which
we
actually
will
start
using
the
new
column,
but
because
backfilling
is
being
done
in
16.3,
the.
A
Yeah
I
can
say
the
date
speed
pushed
it
up
to
the
September
here
on
that
one
and
we
don't
have
QA
or
designed
on
here
at
the
moment.
So
move
on
to
the
next
item,
which
was
the
engineering
dashboard
which
we
have
here.
So
we
have
availability
sitting
at
99.97,
so
great
work,
everyone
keeping
it
tight.
A
We
have
features
at
50
maintenance
at
42
and
bugs
at
eight,
which
roughly
lines
up
with
our
60
30
10,
so
we're
tracking
quite
well
for
our
our
cross-functional
prioritization.
A
Yes,
yes,
so
our
mr8
has
been
sitting
at
just
over
six
for
the
last
couple
of
Milestones,
which
is
fantastic
work
as
well.
I'm
still
not
sure
about
the
10
member
count,
but
I
might
have
to
look
into
that
because
it
might
race
our
in
my
account
even
more.
But
we'll
have
a
look
at
that.
So
last
Milestone
we
had
76
merged
Mrs,
fantastic
and
80
closed
issues,
so
I'm
tracking
really
well
compared
to
the
previous
Milestone.
A
I
like
that
personally,
not
tying
ear
Master
issues.
We've
got
a
couple
of
six
feature
Flags
in
here.
A
I
think
those
bottom
three
have
all
been
moved
to
source
code,
so
I
will
look
into
those
ones
and
to
the
source
code
group
and
look
at
how
we
can
move
those
on.
But
we've
got
external
audit
events,
adherence
report
and
compliance
adherence
report-
those
are
all
really
recents,
I,
think
we'll
be
on
track
there
and
external
audit
events
has
been
turned
on.
So
we
just
need
that
cleanup.
A
Open
sus
impacting
issues.
There
are
all
these
four
and
Below,
which
is
fantastic.
It
passed
you
severity
bugs.
We
only
have
S3s
and
Below,
which
I
know
that
we're
on
targeting
as
part
of
our
okr
for
our
customer
bugs
it's
great
and
the
final
thing
we've
got
here
is
open
emails
and
just
looking
through
here,
we
have
two
at
the
bottom,
from
Sam
and
Aaron
on
refactor,
ordered
events
for
user
adjacent
services
and
back
end
for
the
merge
request,
violation,
export
any
comment
there,
Aaron.
D
A
No,
it's
going
to
take
too
long
move
on
to
the
next
item:
business,
all
right.
So
next
up
we
have
okay
hours
with
the
progress
and
blockers.
So
I
just
wanted
to
shout
out
that
we've
made
a
couple
of
big
docs
restructures
to
the
audit
event
streaming
docs.
You
can
see
both
of
them
there
for
the
UI
and
API.
This
okr
for
or
updating
the
compliance
stocks
is
now
100
and
a
big
shout
out
to
Evan
for
his
fantastic
work,
pushing
us
and
helping
us
get
there
across
the
line.
A
So
thanks.
Evan
next
item
was
with
me
as
well,
so
Q2
is
only
one
week.
D
A
Before
the
end
of
July,
so
please
update
any
okay
hours
with
progress
and
also
well
next
week
we
can
up
I'll
start
a
new
issue
about
okay
us
for
the
following
quarter
and
we
can
start
discussing
what
we'll
want
to
carry
over
and
what
went
well
didn't
in
the
current
locations.
B
B
The
progress
updated
to
83
percent-
that's
some
issues,
trending.
A
A
Here
was
the
hackathon
Jay
I,
don't
know
if
you
wanna
yeah.
C
Yeah
I
can
talk
on
the
hackathon.
The
hackathon
I
believe
Nate
for
a
message
for
August
10th
and
11th
Thursday,
Friday
and
I
was
going
to
put
some
more
details
and
some
example
ideas
in
the
probably
a
table
which
can
be
edited
and
added,
add
some
ideas
and
then
from
there
we'll
decide
if
it'll
be
if
anyone
wants
to
pair
up
or
if
we
want
to
do
something
more
for
time
zones.
So
it's
easier
to
work
together,
but
yeah
I'll
put
more
info
in
the
next
week.
A
Awesome
looking
forward
to
it
yeah
was
there
anything
else
anyone
wanted
to
go
through.