►
From YouTube: Compliance weekly - 2023-05-30
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
All
right
welcome
to
the
compliance
weekly
sync
for
the
30th
of
May,
so
the
first
thing
is
just
to
walk
through
the
Milestone
board,
as
anybody
want
to
do
that.
Otherwise,
I
can
do
it.
B
Oh
share
them
all
right
here
we
go.
Are
we
just
doing
our
I
know?
We
proposed
some
changes,
but
are
we
just
doing
the
regular
walkthrough
that
we
normally
do
this
this
time,
yeah
just
a
normal
okay.
B
See
where
have
we
left
off
and
close.
B
This
one
right
here:
okay,
this
one
back-end,
filter
compliance
violations
by
Branch
names.
As
anyone
know
about
this.
One.
A
B
Perfect
all
right,
let's
see
these
next
few
are
from
hitesh.
We
have
we're
defining
audit
event
type
schema
for
various
things,
and
we
know
we
have
a
quite
a
few
of
the
I
I.
Don't
I,
don't
know
how
many
of
those
are
still
out,
but
I
know
that
we've
been
working
on
those.
B
A
Hatish
has
done
an
investigation
into
the
Euro
budget
implications
in
there
is
a
very
small,
the
basically
addition
to
our
Euro
budget,
which
is
good
and
we've
updated
all
the
documents,
so
all
the
documentation,
so
I
think
we've
closed
out.
That
issue
now
yeah.
B
Okay
and
the
next
two
above
those
are
ux
issues,
so
solution,
validation,
adherence
reports
and
does
anyone
want
to
talk
about
this
one
and.
A
Yes,
great
I
think
the
solution
validation
has
been
closed
with
the
change
in
approach.
The
this
is
the
number
in
Need
for
solution,
validation
and
who's
over
has
completed
the
back
end
technical
implementation
plan
and
created
a
whole
bunch
of
issues
and
started
into
that
already,
and
then
the
next
part
is
the
front
end
from
the
designs.
B
B
Framework
from
compliance
framework
form,
sorry
form,
add
accessible
names.
A
Yeah,
that
was
another
tiny
yeah
and.
B
So
there's
nothing
else
to
talk
about
there,
we'll
just
slide
over
to
review.
B
C
Yeah
so
right
before
PTO,
that
one
was
got
the
final
approval
from
a
maintainer
and
then
the
maintainer
had
to
get
another
reviewer
because
they
were
now
an
author.
So
they
couldn't
be
the
final
one.
So
now
there's
some
new
feedback
that
I've
addressed
it
in.
Hopefully
that
will
get
merged
in
because
it
was
ready
from
the
previous
last
minute.
B
Perfect:
okay:
let's
see
I
I
kind.
B
A
So
with
do.
A
No
I
can
talk
about
them
when
they
close
they're,
pretty
small
things.
Okay,.
B
Yeah,
okay,
that's
what
I
was
wondering.
Okay,
this
is
the
big
one
that
I've
been
working
on.
I
have
two
Mrs
that
are
in
review
right
now.
One
of
them
was
because
of
some
tech
best
problems
that
I
that
took
me
a
little
bit
longer
to
finish
last
week.
They
were
just
kind
of
tedious,
because
I
had
quite
a
few
tests.
B
The
the
gist
of
it
is
that
we
we
changed
a
lot
of
things
to
use
the
newer
audit
method
and
in
our
specs
we
have
expectations
in
the
specs
for
receiving
that
audit
method.
Once
for
this
specific
service.
B
For
that
audit
event,
I
updated
emails
to
use
the
new
audit
method,
also,
which
means
that
a
lot
of
those
other
services
were
getting
the
audit
method
an
additional
time,
and
that
was
breaking
a
lot
of
the
tests,
because
it
was
expecting
audit
to
be
called
once
and
then
it
was
being
called
an
extra
time
because
of
the
emails,
I
went
back,
I
changed.
B
B
A
couple
times
I
haven't
heard
anything
back
yet,
but
that's
that's
where
that
went
as
well.
So
we
can.
We
can
talk
about
that
later.
I'm,
not
sure
why
I
can't
merge
it,
but
that.
C
B
All
the
Mrs
at
this
point,
or
at
least
in
review
or
done
so
we
have
that's
for
Ilya
and
we
have.
B
A
few
more
from
Michael
and
any
any
updates
on
on
anything
else.
At
this
point.
B
Sorry,
I,
don't
I
don't
get
to
walk
the
board.
I'm
always
worried
that
I'm
going
to
after
missing
something
so
feel
free
to
jump
in.
If
there's
anything
that
needs
to
be
discussed.
A
No
at
least
just
one
thing
on
and
Dave
with
the
instance
level
audit
events
UI
stuff
I,
don't
know
where
that
issue
is
yeah.
Sorry
that
second
one
there,
the.
B
A
Yeah
and
the
crud
operations
for
destinations
to
the
UI
has
been
merged
and
that's
all
behind
a
feature
flag
at
the
moment,
and
there
is
a
Mr
up
for
the
back
end
for
the
headers
and
one
for
the
UI
as
well.
So
we're
just
waiting
for
those
to
be
confirmed
before
we
move
that
to
verification.
So
that's
on
track,
though
excellent.
A
Okay,
because
it's
not
the
first
weekly
and
not
the
last,
we
can
skip
all
that.
The
next
item
was
for
me,
which
was
congrats
to
hitish
and
Jay
as
well
for
one
year
anniversaries
over
the
last
couple
of
weeks,
but
Milestone
so
congrats
guys
and
the
next
one
was
I've,
created
an
issue
to
discuss
improvements
to
this
meeting,
it's
more
about
how
we
go
through
and
discuss
our
the
items
that
are
in
progress
and
how
we
better
align
that
with
the
goals
that
we're
trying
to
get
out
of
the
Milestone.
A
C
Yeah
sure
I
think
Sam
noted
that
there
is
a
weekly
parking
session.
He's
gonna
have
all
of
the
engineers
to
the
event.
Oh,
it's
the
pairing
session.
Sorry,
not
the
parking
session!
That's
why
I
was
a
little
confused
yeah!
So
Sam
and
I
have
been
meeting
every
Thursday
I
guess
the
time
is
13
UTC
and
I
was
going
to
expand
that
to
you
other
reason,
I
forgot
to
make
an
order
of
it.
Last
compliance
meeting
so
I'm
glad
Sam
did
I'm.
C
Just
open
pairing
I
used
to
do
that
with
a
previous
team,
and
it
was
helpful
to
just
debug
a
bit
just
talk
whatever
yeah.