►
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
A
I'm
going
to
just
share
our
notes
document
here
for
the
call
so
the
first
one
scan
policies.
Ui
is
up
behind
a
feature
flag,
so
the
back
end
is
still
coming,
but
it
looks
like
the
front
end
is
fully
there.
So
if
you
turn
the
flag
on
it
gives
you
the
scan
policies,
menu
item
and
you
can
go
ahead
and
pick
a
security
policy
project
again
we're
still
waiting
on
a
back
end.
Mr
for
that
one,
but
it's
getting
close
at
least
the
front
end
is
done.
Also
part
of
that
front.
A
End
work
was
making
sure
that
when
a
security
policy
had
was
referencing,
a
das
scan
profile
or
site
profile
that
those
profiles
were
not
able
to
be
edited
or
deleted
by
users.
So
that
way
you
had
full
separation
of
responsibilities
and
developers
were
not
able
to
change
the
parameters
and
the
settings
for
those
das
policies,
and
it
looks
like
that's
in
as
well
so
now
the
delete
option
in
the
in
this
menu
is
grayed
out
it's
disabled
and
it
gives
you
a
message
saying
this
profile
is
currently
being
used
in
a
policy.
A
Also,
if
you
go
in
to
edit
it
all
of
those
fields
are
disabled.
Along
with
the
save
profile
button
is
disabled
and
you
have
a
message
at
the
top
that
says
it's
currently
being
used
in
a
policy.
So
if
you
want
to
edit
one
of
these,
you
have
to
remove
it
from
the
active
policy
or
disable
the
policy,
and
then
you
can
make
your
changes
and
again
that
way,
there's
full
separation
of
duties
there.
A
B
A
A
milestone
kickoff
for
1311.
tiago,
don't
put
you
too
much
on
the
spot?
Do
you
want
to
walk
through
any
of
that
today,
or
should
we
handle
that
when
I
sing.
B
I
think
I
prefer
to
do
it.
You
think
I
do.
I
do
have
the
the
backlog,
so
there's
no
one
else
on
the
call
to
ask
questions
which
was
part
of
the
point
of
this,
but
I
suppose
they
can
watch
the
the
video
and
and
then
ask
questions
asynchronously.
So
let's
do
it,
we
got.
We
got
time
I'll
share
my
screen.
B
B
B
B
B
B
Cool
this
issue
here
is
pending
decision
on
the
on
the
ci
merge
request,
which
is
one
of
the
back
end
things
that
you
mentioned
before
that
were
they
were
waiting
on
until
that's
done,
it's
very
hard
to
to
figure
out
how
this
was
going
to
be
broken
down,
but
we
do
intend
to
work
on
it.
B
They
are
all
in
the
epic
for
for
the
trevi
container
scanning,
so
the
ruby
based
container
scanning
tool
not
expecting
any
trouble
finishing
refinement
for
these
in
order
to
to
work
on
them.
B
So
that's
the
first
and
the
second
one
then
there's
a
follow-up
cleanup
from
from
the
work
on
the
on
the
alerts
that
we
showed
you
now
we
want
to
get
to
these
sort
of
quickly
so
that
the
maintainers
don't
start
thinking
that
we
we
don't
do
follow-ups
again,
another
one
for
for
the
new
content
scanning
tool,
analyzer
about
stopping
root
use.
B
Then
we
have
a
sev3
bug
related
to
container
scanning.
We
might
hold
this
because
we
do
believe
the
new
tool
won't
be
affected
by
it.
So
we
don't
want
to
go
back
and
fix
claire
unless
we
have
to.
There
were
some
low
testings
that
they
were
postponed
from
1310.
B
B
This
is
around
performance
for
database
and
there
are
some
solutions
in
discussion
there,
but
basically
it
has
to
do
with
the
fact
that
when
you
select
when
you
have
a
ci
pipeline
running,
it
needs
to
query
for
all
the
potential
profiles
in
there
and
if
there
are
infinite
profiles,
that
query
could
just
go
on
for
as
many
as
you
have
so
we'll,
probably
just
put
a
limit
in
there.
A
A
But
your
screen
is
not
updating
if
you're
down
it.
B
It's
okay,
there
was,
there
was
the
last
one.
There
was
one
one
last
which
was
end-to-end
test
framework
which
alexander
has
taken
on
to
do
his
part.
I
don't
know
if
we'll
get
to
it
on
the
back
end
side
and
in
ready
for
development
that
hasn't
been
refined.
Yet
there
are
a
couple
of
issues
for
the
container
scanning
too,
and
that
is
it
around.
B
There's
not
a
lot
in
there
around
around
the
dust
policy
scans,
but
that's
because
we,
depending
on
the
merge
requests,
but
we
we
will
work
on
these
as
soon
as
we.
We
have
this
definition
of
what's
happening
with
that
measure
quest.
A
Awesome
yeah
that
sounds
good
and
the
front
end
ones.
Are
there
as
well
in
that
board,
please
feel
free
to
review
those
asynchronously
at
a
super
high
level.
My
understanding
is
that
we're
addressing
a
number
of
bugs
and
then
also
continuing
work
on
the
alert
dashboard
just
working
through
some
of
those
follow-up,
ui
issues
and
also,
as
you
mentioned,
thiago,
I
think
alexander
was
going
to
start
working
on
that
and
test
framework
too.
A
There
could
be
more
than
that
or
things
that
I
didn't
cover.
That's
just
for
my
high
level
understanding
as
I
skill
the
list
cool
anything
else
to
cover
for
to
this
week's
discussion.