►
From YouTube: Compliance weekly - 2023-06-06
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
B
A
No
okay,
we'll
jump
over
it.
The
next
one
was
framework
not
supported
in
personal
namespaces,
with
community
at
the
design.
C
I
think
oh
I
think
the
the
design
is
done,
so
it
was
like
about
just
I
think
you
already
created
armor,
for
it
just
remove
the
button
and
leave
the
space
so.
D
E
So
no
insurance
level
audit
events
are
being
admitted
to
external
definitions
which
are
Saturn.
Instead,
there
was
a
bug
in
it,
not
exactly
in
it,
but
why
is
it
destroying
in
non-existent
destination
and
I'll
be
fixing
in
the
coming
Mrs.
D
Yeah
this
was
adding
an
index,
so
it
was
like
this
is
the
think.
Earnest
part,
so
follow-up.
First,
we
had
a
p
index
asynchronously
in
the
background
that
had
a
run,
it
took
I
think
three
weekends.
To
finish
on
all
the
audit
event
partitions
that
finished
was
able
to
merge
in
this.
This
adds
it
to
the
synchronous
so
it'll
be
in
self-managed,
GitHub
and
everything,
and
in
this
schema,
so
yeah,
pretty
small
Bridge
Quest
just
had
a
wait
on
a
while
for
the
asynchronous
stuff
to
run
right.
A
The
next
one
was
the
adherence
report,
the
front
team
technical
implementation
plan,
so
I
can
speak
to
this
one
I
know
Jay
and
I
caught
up
and
went
over
the
fronting
plan
and
creditor
a
pretty
solid
plan
and
I
know.
The
graphql
issue
has
been
updated
on
a
whole
bunch
of
front-end
issues
created
off
the
back
of
it
and
have
been
started
already.
So
that's
into
it.
E
But
this
was
raised
by
a
customer
and
and
that
child
project,
the
pipe
the
compliance
pipeline
was
not
getting
triggered
when
it
was
the
pipeline
of
child
project
was
being
triggered
from
the
parent
projects
pipeline.
The
issue
was
that
the
customer
was
using
child
pipelines
instead
of
using
multi-project
pipelines.
So
after
registering
that
to
use
them,
it
started
working
for
them.
So
there
was
nothing
much
done
in
this.
A
Good
support
in
learning
for
us,
the
next
one
was
auditing
project
token
activity
who's
over.
F
Yep,
so
we
had
a
couple
of
a
couple
of
things
to
be
audited
from
a
project
token
activity
like
creating
issues
or
adding
comments
to
an
issue.
I
created
a
couple
of
Mrs
to
resolve
those
and
I
also
summarized
it
at
the
end
with
the
comment,
so
we
have
I
guess
two
or
three
events
still
left,
but
I've
moved
on
moved
all
of
them
to
the
odds
group,
because
that's
the
group
which
owns
this
particular
feature
so
from
from
us,
it's
closed
Yep.
F
This
is
the
table,
so
we
added
these
events
in
dmrs
and
then
we
have
to
be
still
remaining
three
events,
which
are
deep,
prioritized
by
the
product
team.
So
I
just
created
a
new
issue
and
assigned
the
port
label
to
them.
A
Right
next,
one
was
add
an
option
to
allow
Force
push
to
protected
branches
with
earlier.
G
Yeah,
basically
right
now,
we've
finally
solved
a
very
big
annoyance
when
developer,
who
has
no
main
maintainer
permissions
created
project
into
the
group
in
the
group-
did
not
initialize
it
with
readme,
so
we
have
a
basically
empty
Reaper
and
he
or
she
stuck
in
the
real
situation
where
the
project
is
here.
But
here
she
can't
push.
It
can't
push
anything
because
there
are,
there
is
no
main
branch
and
he
is,
and
it
is
considered
protected
by
default.
G
So,
basically,
right
now,
the
very
first
push
to
the
empty
repository
is
always
allowed,
but
this
setting
is
active,
so
the
developer
could
initialize
a
project
and
after
that
open
merge
requests
there.
So
everything
should
be
more
logical
than
it
was.
A
F
I
reviewed
this
one.
This
was
one
of
the
long
pending
hours
that
we
had
I
created
almost
two
months
ago.
More
than
two
months
I
did
the
final
maintain
a
review
for
this
one.
It's
should
be
in
production
now.
The
thing
was
like.
Even
if
we
were
retrying
the
status
check
a
fail
status
check
on
the
UI.
We
were
not
able
to
see
that
feedback,
so
what
now
happens
is
when
you
click
the
retry
button
for
a
failed
statistic.
F
H
A
And
the
next
one
was
the
framework
bulk
area.
This
was
just
a
UI
update
to
the
framework
report
and
the
Bulgaria
and
just
improving
some
of
the
ux.
There
we've
got
a
end-to-end
test
for
simple
compliance
pipelines,
Now
set
up
as
well,
which
Mark
has
completed
today,
so
it's
great
to
have
that
in
there
and
we've
got
a
okr
to
get
four
more
in
by
the
end
of
the
quarter,
so
got
a
pretty
ambitious
to
keep
the
Quality
app
and
the
compliance
features
and
the
next
one
was
password
controller.
A
So
this
was
an
ERA
that
came
through
yesterday
and
Rod
due
to
Mr
event,
Aaron
had
been
working
on
and
has
been
reverted
back
and
he
just
needs
to
fix
some
tests.
G
A
You
go
next
thing
on
the
list
is
to
go
through
the
planning
issue
and
just
get
an
update
on
all
our
initiatives
and
see
how
we're
going
so.
The
first
one
was
the
instance
level
streaming.
Audit
events
with
Dish.
E
Yeah
I
saw
the
stream
Insurance
level
external
audit
event.
Destinations
have
been
API
is
related
to
those
API
related
to
those
external
destinations
are
already
in
production,
along
with
the
migration
for
streaming
headers
in
them.
Since
the
audit
events
on
an
instance,
level
are
being
emitted
to
the
destinations
data
being
added,
the
Mr
for
creating
and
listing
the
headers
for
those
destinations
is
in
under
review,
and
the
subsequent
Mrs
for
updation
deletion
of
headers,
as
well
as
filters,
are
coming.
F
Yep,
so
we
have
finalized
the
back
end
as
well
as
the
planet
requirements
for
this
one
and
I've
started
working
on
the
backend
part.
The
first
one
was
to
actually
create
a
database
table.
I
have
created
and
I
created
an
alarm
for
this
and
pushed
it
to
review,
while
J
is
also
working
on
this
simultaneously
on
the
front
end
part.
So
this
is
on
track.
A
Right,
the
next
one
was
the
manage
compliance
Frameworks,
and
it's
with
me
so
this
had
been
on
the
list,
but
this
was
before
Elliott's
borrow,
so
this
is
actually
on
hold
now
and
while
we
just
review
the
framework
and
I'll
probably
drop
off
and
the
following
Milestone
planning
next
is
blocking
merge,
requests,
the
theft
failed
status
checks
with
j,
so
the
goal
was
to
complete
two
and
it
looks
like
one
has
been
completed,
based
on
what
we
just
talked
about.
B
Yeah
so
for
this
one.
E
B
Yeah
and
next
is
already
event
type
schema,
so
here
we
have
actually
defined
all
the
static
schemas
and
Dynamic.
F
Whatever
possible,
to
like,
add
tibana
link
to
this
particular
visual,
so
that
we
can
easily
track
that.
D
A
Correct
so
it
sounds
on
track.
Next
was
the
violation
export
feature
with
Sam
yep.
H
That
one
is
in
progress
I'm
in
the
process
of
aspect
down
the
export,
a
bit
to
exclude
filters
for
now
and
we'll
follow
up
with
the
filters
and
once
that
one
is
shipped.
D
D
Everything
got
sorted
out
in
slack,
but
as
part
of
that,
the
Branch
had
to
be
updated,
so
lost
the
back-end
Main
theater
review
and
the
maintainer
kind
of
went
quiet
for
the
last
week
so
recently
assigned
it
to
a
new
maintainer.
D
They
responded
yesterday
so
just
need
they
had
some
spec
suggestions,
I'm
just
updated
to
them.
So
hopefully
we'll
get
that
named,
hinder
approval
and
get
immersed
in.
B
F
B
B
G
Yeah
I've
started
to
dig
the
implementation
plan
for
this,
so
it
is.
We
are
moving
this
from
not
started
to
planning
phase
and
I
expect
to
have
something
next
week.
It
is
a
huge
multi-milestone,
app
effort
because
adding
the
new
level
of
approvals
influence
so
many
parts
of
the
system.
G
So
basically
this
is
in
planning
and
no
issue
is
yet
ready
to
be
started
before
we
flesh
out
the
plan
and
agree
on
them,
because
I
will
need
some
kind
of
back-end
approval
from
the
teams
there,
because
there
will
be
some
back
and
forth
there
also.
C
Still
like
exploring
the
framework
like
manage
framework
levels,
I
will
start
like
start
sharing
design
at
a
later,
like
Thursday
Friday
and
got
initial
feedback,
and
it
will
continue
like
have
a
feedback
session
until
the
end
of
this
Milestone,
so
feel
free
to
jump
in
at
any
stage
like
I.
Just
want
to
say
again,
like
design
is
never
done.
So,
if
you
have
anything
just
like
send
it
my
way.
Thank
you.