►
From YouTube: Compliance weekly - 2023-03-14
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).
B
A
A
A
A
Yeah,
that's
right,
so
the
next
one
was
sync
compliance
report
parameters.
So
this
was
a
feature
that
Alwyn
has
done
to
Excel
One,
we're
switching
the
tabs
and
the
oh,
it
doesn't
show.
But
when
you
switch
tabs
and
do
the
pagination
and
the
new
framework
report,
the
URL
updates
as
well,
so
that
you
can
copy
paste
the
URL
and
use
that
to
link
to
certain
pages
on
the
framework
report.
A
Oh
yes,
so
because.
B
C
So
we
do
have
a
like
documents
for
every
table
in
the
database.
I
created
a
background
migration,
where,
like
we
create
a
new
class,
whenever
we
have
to
write
a
migration,
we
don't
depend
on
the
existing
code
base
because
we
don't
we
never
know
when
the
migration
is
running.
We
we
don't
even
might
not
have
that
model.
So
when
I
created
the
model,
the
scoping
was
like
it
caused
some
issues,
so
it
thought
like
we
have.
C
We
have
a
new
table
in
the
database,
so
it
created
a
new
diff
in
the
DB
docs,
but
I
fixed
it.
It's
now
close,
so
yeah.
A
D
A
E
Yeah
so
I
investigated
it,
and
so
what
we
have
written
was
using
previous
changes
provided
by
rails
and
it.
B
A
Make
it
clear
when
a
project
is
missing,
gitlab,
cim
or
file
and
make
it
fix
easy
finally
managed
to
complete
this
one?
It's
taken
me
two
three
Milestones
to
get
through
in
multiple
emails
that
were
closed,
but
now
there
is
a
button
in
the
pipelines
when
there's
a
failure
for
this
particular
era
and
allow
the
users
to
create
a
well
update
the
pipeline.
A
A
All
right
links
does
the
verification
column,
so
it
looks
like
we've
got
a
few
issues
and
verification
and
a
lot
with
Sam
on
it.
I
was
actually
wondering
I
noticed
the
backing
changes
seem
to
pick
up
Sam.
Quite
a
lot.
I
might
test
that
out
with
some
other
issues
just
to
see
if
it's
always
going
to
yourself
Sam
but
yeah,
anything
that
would
go
through
there.
C
I
think
also
like
the
even
if
they
bought
a
sign
someone
we
we
can.
We
could
perhaps
like
reassign
it
to
someone
else
in
the
team,
if
you
think
we're
at
capacity
like
manually
asking
them
if
someone
else
could
really
play.
C
F
A
One
thing
to
call
out
as
well
that
I
remembered
after
doing
having
your
one
today
Michael
was
the
it
has
to
have
that
back
end
or
front
end
label
on
it
as
well.
To
pick
up
for
the
back
end
or
front-end
engineer,
to
have
a
look
at.
C
The
first
one
in
the
dev
that
is
assigned
to
me
will
probably
slip
this
Milestone,
we'll
we'll
have
to
complete
this
in
15.
11.
I
am
still
working
on
this.
F
Get
the
CI
Runner
I
haven't
done
another
work
on
that,
yet
so
I'm
not
sure.
If
it'll
make
it
or
not
I'm
guessing
with
Mr
review
times,
it
probably
will.
G
Yeah
I
think
that
will
definitely
make
it
I
expect
to
open
the
merge
request
today
and
I
think
that
we
will
have
it's
not
that
much
complex,
front-end
change
that
we
will
have
enough
time
to
make
it
in
business.
Milestone
of.
B
A
Blocked
so
there's
the
filtering
compliance
framework
report,
which
is
blocked
by
the
filtering
back-end
customer.
Any
update
on
that.
E
Yeah,
so
that's
one
in
review:
I
have
two
Mrs
Right
Now,
one
of
them
id1
should
get
interested.
A
C
Not
necessarily
like
I
mean,
if
you're,
confident
enough
like
this
is
the
proposed
solution.
You
could
probably
tag
someone
you
think
is
should
review
the
plan,
someone
who
who
has
previously
worked
on
the
issue
or
someone
who
was
involved
in
the
issue
or
like
just
nominate
someone
from
the
team
tagging.
C
Everyone
in
the
team
seems
like,
like
I,
feel
like
it's
a
noise
unless
we
we
are
doing
something
extremely
big,
like
the
thing
that
her
similar
is
currently
working
on,
like
moving
from
postgres
to
elasticsearch
or
clickhouse.
That's
a
that's
an
architectural
decision,
so
things
like
that
must
like.
We
must
take
reviews
from
everyone
on
such
a
decision
that
this
is
like
a
normal
thing.
I
would
say.
A
C
Unless
there's
a
I
mean
there's
a
doubt,
even
if
you
like,
even
if
the
implementation
plan
is
not
reviewed
and
you
create
an
Amazon
it'll,
definitely
get
reviewed
by
someone.
So
if
there's
a
there's
a
huge
gap
or
a
very
technically
like
if
things
are
not
technically
correct,
then
that
would
get
caught
in
the
Mr
itself,
but
yeah
that
we
should
avoid
doing
that,
because
that
that's
the
latest
stage,
it
should
have
happened
earlier
during
the
implementation,
but
for
for
smaller
issues,
I
haven't
seen
tagging
everyone
or
asking
reviews
from
everyone.
C
B
C
This
issue,
I,
would
I
mean
just
my
opinion.
I
would
suggest
if
harassment
has
time.
You
could
take
a
look
on
this
because
he's
worked
a
lot
on
the
audit
events
like
refactoring
recently,
but
I'm
not
sure
like
if
he
has
capacity.
E
Yeah
I've
I
think
I've
added
my
comment
on
it,
but.
D
A
And
sorry,
just
to
come
back
so
like
rough
rollathon
like
a
wasting
of
one
or
two,
you
sort
of
just
let
it
go
through
and
get
a
cheat
to
Nema.
Three
and
above
you
sort
of
ping,
somebody
that
you
think
might
be
from
the
team
that
might
be
able
to
help
review
it
and
anything
sort
of
bigger.
You
know
those
big
architectural
decisions.
We
get
the
whole
team
to
look
into.
A
Was
there
anything
else
and
solution,
validation,
planning
breakdown?
Anyone
wanted
to
go
through.
A
C
C
Do
we
need
the
release
for
the
compliance
report
that
we
have
right
now?
Yes,
we
do
are
the
third
one
I
guess
this
is
the
one.
Oh,
no,
that's
21.,
that's
for
the
that's
what
that
was
something
that
we
haven't
even
started:
working
on,
yeah.
A
C
We
could
probably
even
have
I,
don't
know
that
we're
just
adding
the
audit
event,
but
we
but
I
remember
we
had
previously
we
had
released
posts
for
new
audit
events,
I'm,
not
sure
if
we're
doing
it
anymore
or
not,
like
we
had
a
small
section
where
we
just
added
like
these
are
the
new
audit
events
added.
This
milestone,
I
think
where
we
added
two,
like
the
one
I
thought.
The
first
closed
issue.
A
And
also
next
on,
the
agenda
was
okay,
as
progress
and
blockers
earlier.
You've
got
the
first
item
there
yeah.
G
Sorry,
my
camera
got
1K
again
actually,
since
I'm
actually
participating
in
viewed
free
migration
working
group-
and
this
is-
we
have
a
development
right.
Okr
related
to
this
one
I
will
be
updating
a
few,
probably
B,
weekly
on
the
progress
on
the
occur.
Probably
we
should
include
a
link
to
it.
G
I
will
do
this
right
now,
so
we
are
at
the
early
start
and
we
are
understanding
that,
like
we
are
figuring
with
the
rest
of
the
team
of
what
will
be
the
dimensional
number
of
merge
requests
and
right
now,
I've
committed
to
have
like
30
merge
requests,
offer
this
okr
in
this
quarter
and
from
this
30
merge
request.
I've
already
have
seven
of
them
open
three
of
them
merged.
So
it's
something
like
10
to
20
progress,
depending
on
how
you
measure
it.
G
A
A
Yeah
so
I'll
be
asking
everyone
to
create
a
demo
over
the
next
few
things.
So
we've
got
the
NTN
tests
that
you
might
have
seen
come
out
of
the
RCA.
So
Mark
is
creating
an
end-to-end
test
for
every
feature
in
the
compliance
feature
set,
as
he's
doing
that
to
be
nice
to
create
a
demo
of
all
that.
So
I'll
just
tag
hu,
randomly
to
see
if
you're
able
to
create
a
demo
and
upload
it
to
YouTube.
A
And
yeah
after
a
couple
of
discussions
and
different
issues
that
introduce
in
the
purification
process,
we've
realized,
we
need
to
reassign
the
issue
back
to
the
original
engineer.
Afterwards.
Listen
up
here
to
update
a
handbook,
but
just
to
make
sure
everyone's
aware.
A
So
we
put
it
into
verification
and
assign
it
from
yourself
and
it'll
randomly
grab
another
engineer.
But
then,
when
it
moves
to
close,
it's
still
got
that
Engineers.
We
need
to
switch
it
back,
otherwise
they
don't
yeah.
So
we
know
to
ask
about
in
these
and
do
any
release
posts,
follow-ups
all
that
sort
of
stuff.
F
Seems
like
something
that
can
potentially
be
forgotten
right.
Yes,.
A
F
Is
it
easier
to
assign
to
people
on
the
issue
for
verification,
so
add
an
additional
assignee
for
the
verifier
and
then
you
can
unassign
himself
and
then
it's
just
back
to
the
original
person.
A
Yes-
and
there
is
another
EMR
I've
got
up
to
do
that
as
well,
not
to
reassign
but
just
to
assign
another
person,
so
we'll
start
with
yeah,
hopefully
to
them.