►
From YouTube: Compliance weekly - 2023-06-20
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
20th
of
June,
the
first
order
of
business
is
just
to
walk
through
the
Milestone
board
and
go
through
the
closed
issues
here.
My
screen.
A
And
hopefully
you
can
see
the
close
issues
there.
Last
one
we
talked
about
last
week
was
the
new
Json
B
column
that
Michael
had
completed
the
next
one
up
was
roll
out
of
a
feature
flag
with
asthma.
B
A
A
D
Talking
is
yeah,
I
think,
like
other
most
Mrs
are
down.
There
are
some
slow
follow,
apps,
like
with
the
UI
update
and
also
I,
think
the
active
inactive
is
also
in
the
follow-up.
So
that's
not
not
finished
yet.
A
And
mix
two
were
with
Michael
and
I
believe
these
were
closed
issues
after
we
discussed
last
week,
the
API
to
retrieve
all
ordered
events
for
a
group.
It
didn't
quite
work
out
how
we
planned
it,
so
those
two
migrations
were
canceled
at
the
stage.
The
next
one
was
two
with
asthma.
B
Yeah
next
one
related
to
the
Google
Cloud
logging
integration
with
audience
streaming.
This
is
now
on
live
and
working
on
production.
A
It's
awesome,
another
feature
flag,
I,
think
that
was
to
do
with
the
other
work
that
Michael
was
working
on
the
next
one
was
hitesh
with
fix
internal
server
era,.
E
So
there
was
an
issue
with
external
audit
event,
destinations
API
for
updating
this
one
where
the
past
ID
is
non-existent
and
it
will
throw
in
500.
So
I
fix
that
in
this.
A
All
right
next
one
was
the
database
tables
for
adherence
report,
so.
A
Nice
update
streaming
ordered
events
UI
to
use
collapsible
component
I
think
there
was
the
other
part
of
the
UI
update
for
the
streaming
audit
events
that
you
discussed
before
the
Camellia.
A
F
Yeah,
basically,
it's
just
a
lot
of
follow-ups
of
minor
spec
violations,
which
is
our
verb
towards
viewfree
compatibility.
Nothing
makes
me
happy
to
see
other
people
contributing
to
it,
especially
in
our
group.
So
I
just
heard
everything.
Each
of
them
is
pretty
straightforward,
yet
time
consuming
so
yay
for
external
support.
E
So
we
have
so
there
were
two
feature:
Flags
one
for
backend
and
one
for
current
time.
We
have
merged
them
into
one
and
basically
we
have
closed
the
front
end.
The
feature
flag,
which
was
controlling
the
front
end
of
instance,
streaming
audio.
A
A
A
And
final,
one
at
the
top
was
just
a
small
ux
update
to
remove
the
remove
the
default
pill
from
whatever
you
want
to
call
Little
badge
next
to
the
compliance
friendly
name
and
move
it
into
the
compliance
framework.
Badge
itself
and
also
mixed
up.
I
just
want
to
go
through
the
plan
and
we'll
start
off
with
a
16-2
plan.
Since
we're.
B
B
I
can
also
talk
about
the
the
one
that
is
assigned
to
me
at
the
border,
monitor
Cabana
logs
to
catch
audit
events
creation,
so
we've
enabled
like
We've
added
a
logging
for
catching
any
audit
events
that
are
being
emitted,
but
they
don't
have
a
yaml
file
created
for
them
for
the
event
type.
B
So
I've
created
a
dashboard
which
is
I
mean
the
link
to
the
dashboard
is
in
the
issue
where
we
are
capturing
the
event
names
which
are
still
missing
so
we'll
be
monitoring
this
particular
issue
for
a
while.
Maybe
this
Milestone
or
even
next,
if
we
have
some
some
new
occurrences
and
then
we'll
add
the
We'll,
add
the
missing
Diablo
files
and,
let's
close
this.
A
Yes,
please
do.
B
B
No
I
think
it
created
the
first
MMR.
It
was
most
and
then
the
heated,
the
second
one
directly
rename
just
renaming
the
tab
from
compliance
with
violations
to
complaints,
Center
and
the
one
which
was
linked
in
the
update
today
by
net.
So
it
has
a
couple
of
reviews
required
so
yeah,
that's
the
effect.
A
Yeah
I
think
he
deserves
a
some
sort
of
badge
for
that
I
think
it
was
like
eight
reviewers
or
yep
anyway.
The
next
one
was
the
instance
level
streaming
audit
events,
a
dish.
E
So
their
API
is
for
streaming
headaches
for
listing
listing,
updation
and
creation
is
deployed
and
production.
The
destroy
header,
API
Mr
has
been
reviewed
by
the
backend
maintenance,
depending
on
compliance
review,
and
then
that
we
have
the
UI
ready
for
the
uimr
for
streaming
headers
being
developed
by
nate2,
and
we
are
now
planning
ahead
with
the
event
type
filters
apis
for
this.
A
B
Yeah,
so
for
this
current
status
is
we
have
the
implementation
plan
and
schema
design
completed?
So
now
we
have
to
dig
up
SQL
queries
from
the
word
base.
Manually
I
asked
the
database
team
if
there
is
a
logging
of
sqls
available
on
a
particular
table,
but
sadly
we
don't
have
a
complete
list
of
SQL
queries.
B
Yeah
for
the
replacement
drop
bombs
like
yeah,
so
this
is
actually
a
new
issue
which
was
assigned
to
me
and
I
have
gone
through
the
issues
which
are
only
for
the
protected
Branch
one,
and
they
are
currently
in
blog
stage,
because.
B
B
Next
one
is
streaming
audit
events
to
Google
Cloud,
so
this
one,
the
back
end
part
for
this
is
complete.
D
A
Right
and
the
final
one
was
the
the
violation
export
with
Sam.
C
Yeah
I
have
the
Mrs
for
the
backend
and
front
end,
currently
open
I'm,
going
through
review
comments,
so
that
should
be
shipped
shortly.
The
documentation
change
still
needs
to
be
done
now.
A
Yeah,
that
was
it
from
engineering
Camellia.
Any
design
update.
D
I'm
collecting
feedback
for
the
moving
the
compliant
framework
to
the
framework
session,
like
under
security
and
also
like
I,
did
some
more
written
design.
So
if
you
still
have
feedback
anything
or
if
you
haven't
have
time
to
check
it
out,
I
think
this
week,
I
will
keep
refunding
it
collecting
feedback
and
the
next
week
I
will
start
building
up
like
the
detail
of
the
research
plans.
So
please
leave
a
comment
if
you
have
anything
this
week.
Thank
you.
A
Right,
that's
it
from
that
plan.
The
next
thing
was
to
go
through
the
compliance
engineering
dashboard.
Since
it's
technically
the
first
weekly
of
the
milestone,
I
think.
E
A
It's
great
work
and
I
think
it's
been
sitting
around
that
same
value,
all
of
June
as
well.
So
far,
so
looking
great
Mr
types,
we
have
got
about.
45
features
to
43
maintenance
for
sitting
around
the
same
which,
when
you
compare
it
to
the
overall
company,
is
looking
pretty
good,
which.
F
A
F
A
Sense,
yeah,
yeah
and
again
there's
here
to
see
a
little
bit
of
a
uptick
there.
So
you'll
see
that
this
one
I
did
want
to
call
out,
though,
for
the
last
month
of
May
we,
our
previous
Mr
rate,
was
3.3
and
it
almost
doubled
to
6.2
so
great
work.
Everyone
I
know,
there's
been
a
lot
of
changes
and
stuff
like
that
as
well.
So
it's
good
to
see
you
on
the
upward
Trend.
There
should
probably
double
as
a
graph.
A
Actually
that
would
cool-
and
you
can
see
from
here
we're
looking
at
some
pretty
tall
buildings,
especially
what
I
like
is
the
comparison
of
the
shoes
to
emails
as
well,
so
at
work
time.
A
There's
a
few
feature
Flags
in
here,
but
I
went
through
them
just
before,
and
it
looks
like
a
lot
of
them
have
been
moved
out.
Like
the
group
protected
branches
group
level,
merge
checks,
these
have
all
been
moved
to
other
groups,
I'm,
not
sure
why
they're
showing
up
here
whether
they've.
B
Because
the
in
the
yaml
files,
they
must
have
the
free
Tech
practically
set
to
complaints
management.
Like
someone
something
related
events,
we
can
probably
okay.
B
Can
do
that
if
I
know
the
list
of
events
that
have
been
looked,
I
know
the
fifth
and
the
seventh
one
have
been
moved,
not
sure
about
the
sixth
one.
A
Past
due
I
need
to
fix
that
one
but
past
due,
but
it's
by
severity.
They're
all
is
three
always
four,
which
is
fantastic
and
I
know
we're
doing
a
great
amount
of
work
on
the
customer,
specific
ones
with
our
car.
So
that's
looking
fine
and
open
Mrs
that
we
have
at
the
moment.
So
there
was
one
at
the
bottom.
That's
now
over
60
days
and
I
know,
Aaron
is
working
out
I'm,
giving
that
one
through
so
I've
caught
up
with
them
before.
So
that
looks
all
good.
A
A
C
You
yeah,
we
changed
the
verification
process
to
remove
the
distinction
between
backend
and
front
end.
C
Because
it
was
making
it
hard
to
distinguish
who's
to
pick
next,
it
was
very
biased
towards
front
end
yeah.
So
it
might
be
that
you're
asked
to
verify
front-end
issues,
but
in
the
sense
of
how
verification
goes,
I,
don't
think
it's
a
big
hindrance.
F
A
F
B
I
forgot
to
add
that
in
the
agenda,
so
I
I
had
a
catch
up
with
need
in
the
morning
and
I
was
thinking.
Hey
I
just
realized
that,
since
I
joined
compliance
almost
two
years
ago,
we
I
haven't
seen
anyone
in
our
group
being
nominated
for
a
discretionary
bonus
for
the
things
that
they've
been
working
as
part
of
the
compliance
group.
B
So
I
was
wondering
if
it's
either
related
to
like
the
work
that
we're
doing
is
not
eligible
for
a
discretionary
bonus
or
is
it
because
we're
not
actually
nominating
people
for
and
not
acknowledging
their
efforts
for
the
work
that
they
are
doing.
So,
in
my
opinion,
if
it's
the
second
case,
then
we
should
probably
start
thinking
around
and
probably
nominate
people
for
their
work
and
the
other
idea
of
having
a
discussion
around
this
I
was
thinking.
B
If
you
can
add
this
as
an
agenda
item
to
either
the
weeklies
or
the
Retro
parole
that
we're
planning
to
add
an
item
where
we
can
discuss
is
there's
like
just
reminding
people
to
go
through
the
discretionary
process
handbook
and
seeing,
if,
like
in
the
previous
Milestone,
they
think
someone
within
the
team
needs
to
be
nominated
or
should
be
nominated.
B
F
C
C
Can't
nominate
direct
who,
who
directly
reports
them
so
I,
think
there's.
B
F
Like
one
I
was
actually
thinking
the
same
way,
but
before
in
my
previous
team,
I
unexpectedly
I
received
a
bonus
from
being
nominated
by
my
EMA,
or
is
it
against
rules
so
I
went
and
check
it
and
suddenly
realized
that
I
was
reading
this
as
long
like
forever.
A
Have
a
look
but
no
I
like
the
idea
of
adding
it
to
the
Retro
personally
I
know:
we've
already
got
that
what
praise
do
you
have
section?
That
might
be
a
good
idea
just
to
update
that
question.
F
F
C
B
F
I
just
wanted
to
say
that
right
now,
I'm
in
borrowette
state,
like
you
know,
in
the
rust
language,
parowat
to
AI
team
and
I,
really
miss
the
level
of
details
at
the
level
of
planning
we
are
having
here,
just
want
to
say
huge,
thank
you
and
to
execution
yeah
like
can't
wait
to
get
back.
To
be
honest,
because
this
level
of
execution
empowers
me
to
understand
that
I'm
doing
big
things.
A
A
Very
much
the
same.
All
right
then
I'll
stop
the
recording.