►
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
so
for
the
first
item
here
I
just
wanted
to
make
sure
that
I
called
out
with
the
team
some
changes
I
made
to
our
priorities,
most
notably
I'm
hearing
from
customers
increasingly
that
vulnerability
scanning
is
a
key
purchase
decision
and
that's
something
that
we
need
sooner
rather
than
later.
A
So
I
really
wanted
to
find
a
way
to
move
that
up
before
we
had
planned
that,
like
way
out,
it
was
going
to
be
like
six
months
from
now
before
we
got
around
to
it.
So
I
pulled
that
up
into
the
backlog
list
and
I
also
moved
a
few
items
down
because
of
that.
B
So
one
question
I
had:
I
know
we
have
it
in
the
notes
and
thanks
for
answering
in
advance
sam,
I
didn't
see
it
till
just
now,
but
thank
you
but
verbalizing.
So
the
vulnerability
scanning
one
was
looking
for
more
detail
in
the
epic
and
you
know
we'll
want
to
plan
for
time
in
the
schedule,
discover,
validate
and
then
decide
on
which
open
source
project
or
projects
we
want
to
leverage
and-
and
we've
already
done,
a
research
spike.
It
looks
like
you
want
to
verbalize
the
notes
on
that.
A
A
But
it's
still
on
my
backlog
of
things
to
do.
The
initial
plan
was
to
use
claire
or
clark
and
just
leverage
the
scanners
that
are
on
the
secure
side
and
have
those
run
against
containers
in
production.
But
you
know
as
long
as
really
the
goal
here
is
to
be
able
to
do
a
package
scan
and
compare
that
against
known
vulnerabilities
but
again
I'll
add
in
all
add-in
requirements
there
in
more
detail
later.
A
So
for
this
again,
you
know
trying
to
take
things
a
little
bit
more
iteratively
and
I
think
thiago
suggested
doing
like
a
port
scan
as
well.
This
initial
effort
would
really
just
be
packages
so
starting
with
a
basic
package
listing
with
the
versions
and
comparing
that
against
known
vulnerabilities,
which
I
believe
is
what
I
forget.
If
it's
claire
or
both
I
get
those
two
mixed
up,
but
I
I
think
they
both
handle
that
pretty
well.
A
B
Is
it
just,
I
know,
I
know
we're
months
we're
many
months
out,
but
it
jump
says
this
would
be
a
case
where
perhaps
defend
will
be
creating
vulnerabilities
rather
than
alerts
like
this.
B
Makes
sense
cool?
No
thanks
for
all
the
updates.
The
only
other
question
I
had
is
actually
is.
I
just
saw
on
the
list
not
the
changes
that
sam
that
you
made
on
the
priorities,
but
unless
we
have
allen
listed
as
primary
on
one
of
the
items,
I
think
it's
a
small
one
fixing
a
bug.
So
it's
priority.
Three.
Are
we
planning
to
have
alan?
Do
that
or
have
somebody
else
do
that
since
alan.
C
I
can't
answer
that
wayne.
He
he
was
already
doing
it
before
we
switched
and
he
he
wanted
to
stay
on
it.
So
I
I
let
him
it's
taking
a
bit
longer
than
than
expected.
He
might
be
having
trouble
getting
to
it.
So
thanks
for
the
reminder,
I
I
should
ask
him
I'll
check
with
him
if
he,
if
he
still
thinks
he's,
got
bandwidth
and
if
not
I'll
reassign
one
thing,
sam
just
to
call
out
as
well
the
the
the
change
in
priorities,
the
the
falco
side,
side,
car
installation
with
access
response.
C
That's
now
like
way
down,
it
was
kind
of
up
there
on
the
on
the
bright
side,
it's
well
scoped
and
it's
got
it's
a
good
candidate
for
for
community
contributors.
So
we'll
see
if
we
can
promote
that
it's
somebody
wants
to
pick
that
up.
A
Yeah,
that's
a
good
one
to
call
out,
you
know,
that's
something
we
definitely
want
to
have
done
and
want
to
do
you
know
moving
it
down
on
the
backlog
is
not
any
indication
that
we
don't
want
to
do
it
anymore.
It's
just.
We
have
two
developers
and
a
lot
of
priorities.
So
it's
it's
a
balancing
act.
C
Is
that
1c
about
the
demo.
A
C
Cool,
thank
you.
So
we
we've
we've
taken
up
a
challenge
this
this
iteration
of
delivering
the
the
policy
ui
functionality.
C
I
am
getting
concerned
now
concerned
now
that
helping
with
the
demo
is,
is
taking
significant
time
from
from
samir,
and
I'm
wondering
so
one
we
were
already
taking
into
account
yeah
that
that
that's
that's
get
in
the
way,
but
I'm
wondering
if,
if
it's
more
efficient,
if
we
could
bite
the
bullet
wayne-
and
I
guess
that's
the
question
for
you
and
dedicate
zamir
lets
me
finish-
the
work
and
then
hand
it
over
to
philippe.
Would
that
be
a
more
efficient
way
to
go
about
it.
C
C
B
One
thing
is
that
xamir
doesn't
have
access
to
the
clusters
at
the
same
level
that
philippe
does,
and
I
now
philippe
doesn't
manage
that
it's
actually
niko
one
of
our
users,
who
does
he
created
the
environment
up
at
azure,
so
nico's
on
vacation
this
week,
but
he's
still
watching
things,
unfortunately,
which
is
actually
really
taking
vacation,
but
I
asked
nico
to
grant
zamir
accent,
give
zimmer
access
the
same
same
access
that
felipe
does
to
the
environment
that
might
help
as
well.
B
We
are
recording
that
demo
mid
next
week
and
okay,
like
every
day,
we
like
make
five
steps
forward
and
one
step
back
so
we're
making
a
good
progress.
There's
that
one
step
back
where
philly
tends
to
get
get
roadblocked
like
he
does,
he
tries
really
hard.
B
He
doesn't
know
what
to
do
next
and
needs
help,
but
we
are
making
great
progress
so
the
demos
next
week,
the
recording
next
week,
so
by
this
from
that
perspective
and
like
if
we
can't
get
something
to
work,
we'll
probably
just
remove
it
from
the
demo
not
and
and
and
that'll,
be
okay.
But
I'm
definitely
very
cognizant
of
arthur
and
zamir's
time
working
on
helping
fully
put
that
demo
versus
creating
features
for
customers.
Yeah.
C
It's
definitely
slowing
us
down
now
so
I'll
I'll.
Take
that
I'll
take
that
action
to
to
ask
if,
if
we,
if
we
can
do
that,
thank
you
it's
it's.
A
Okay
and
then
I
have
two
items
here
for
planning
breakdown
both
of
these
are
relatively
small,
so
let
me
go
ahead
and
share
my
screen
and
we
can
talk
through
these.
Let's
see
here.
A
A
It's
not
really
a
feature
that
would
be
tracked
as
an
at
the
epic
level.
For
this,
all
we're
really
doing
is
just
reorganizing
these
tabs.
So
we
want
alerts
to
be
the
first
tab
that
users
land
on
we
actually
do
want
to
keep.
A
We
want
to
have
an
overview
tab,
or
you
know
an
initial
dashboard
at
some
point
in
the
future,
but
the
reality
is
that
our
current
overview
tab,
you
know,
doesn't
have
a
lot
of
really
deep
data,
and
especially
for
users
who
are
triaging
these
alerts
on
a
daily
basis,
that's
likely
to
be
the
first
tab
that
they
actually
want
to
see.
So
all
this
does,
is
it
reorders
it
a
little
bit?
It
moves
alerts
up
to
the
front
and
this
new
statistics
tab
is
actually
the
old
overview
tab.
A
It's
just
renamed
to
statistics,
at
least
for
now,
so
any
questions
about
this
issue,
I'm
hoping
this
one
is
relatively
small.
C
A
A
A
So
really
this
would
just
be
adding
one
more
checkbox
here
and
when
it's
enabled
we
would
send
all
of
the
container
host
security
logs
out
tsm
and
when
it's
not,
we
would
not
again.
I
know
we
have
lots
of
technologies
that
we're
using
as
part
of
our
container
host
security
solution,
we're
trying
to
simplify
this
for
the
end
user.
So
this
would
be
an
on
off
switch
for
everything.
A
B
A
Okay,
great
well,
I
will
move
those
two
epics
into
the
refinement
state
and
at
that
point
I
think
we
should
at
least
have
a
pretty
solid
backlog
of
work.
That's
ready
to
pick
up
in
134.
C
Cool
and
and
as
an
fyi
for
for
everyone,
I've
been
sitting
on
some
of
this
refinement
to
give
arthur
and
zamir
a
bit
of
focus
on
on
the
challenge
that
they
doing
the
intent
is
to
refine
them
before
the
before
sam
goes
out
to
to
his
ceo
shadow
program.
So
he
has
he's
available
to
answer
any
questions
which
is
the
16th
sam
or
17th
17th,
yeah
yeah.
So
from
from
next
week.
Probably
I'll
stop
pinging
you
arthur
and
zami
for
for
some
refinement.
Please.
B
So
vinci
and
I
caught
up
earlier
today
so
and
vince
was
able
to
make
it
today,
which
is
great,
so
we
talked
about
what
are
the
top
quality
risks
from
my
perspective
and
how
vinci
and
her
team
can
help
and
where
we
landed,
which
is
not
necessarily
the
team
that
I
put.
The
notes
in
here
is
performance
and
reliability
of
things
that
are
inline
like
wife
and
cns.
So
if
something
can
break
the
customer's
application
that
unrelated
to
security,
that's
important.
B
Second,
is
user
experience
with
installing
and
initially
configuring
components
we
had
some
philippe
had
some
experiences
with
organizing
the
dog
fooding
with
the
operations
teams,
and
also
with
the
demo
that
we
talked
about
earlier,
and
it's
not
as
easy
to
install
and
initially
configure
as
it
could
be,
some
of
that's
a
documentation
that
we
need
to
improve,
and
some
of
it
is
people
learning
the
open
source
projects
we're
integrating,
which
is
not
really
on
us
necessarily,
but
you
know
maybe
pointing
people
in
the
right
directions,
and
some
of
it
might
be
might
be
code
changes
as
well
to
make
it
simpler.
B
A
Yeah,
so
I
discussed
this
with
vinci
over
a
a
chat
earlier
last
week,
but
my
absolute
number
one
priority
is
load,
testing
and
long
running
tests.
Just
because
I
feel
like
those
are
the
areas
that
we
have
the
least
coverage
today
and
then
basically
zero
and
it's
very
hard
for
our
development
team
to
do
that
kind
of
testing.
It's
not
an
area
that
we
can
just
ask
the
mirror
or
arthur
to
come
in
and
help
out
without
significantly
taking
away
from
their
ability
to
work
on
new
features.
A
We're
just
not
set
up
to
do
that
today.
You
know
real
world
scenarios
that
customers
have
a
lot
of
loads.
That's
going
through
these
applications
and
they're
up
for
a
long
time.
You
know
bugs
like
we
have
with
with
mod
security,
where
we
have
the
memory
leak,
you
know
or
the
kinds
of
bugs
that
terrify
me
that
you
know
we
might
have
introduced
or
might
exist
and
we're
just
not
aware
of
them.
A
So
you
know
anything
that
could
crash
a
customer's
production
environment
should
be
our
top
priority
to
make
sure
that
we're
running
those
kinds
of
tests
to
prevent
that.
B
What
are
your
thoughts
vincy
did?
I
did
I
get
the
notes
correct
from
our
previous
discussion
and
what
do
you
think
of
sam's
feedback.
F
F
Yes,
performance,
reliability
and
user
experience,
but
three
main
areas
that
we
discussed
when
in
our
coffee
chat
earlier
today,
and
with
my
conversation
with
sam
too
there's
a
main
thing
that
I
had
too
from
him,
that
was
performance,
testing,
load
testing,
the
two
main
categories
that
we
need
to
look
into
to
his
point.
These
are
not
something
that
you
expect
the
development
team
to
be
able
to
do
it,
because
most
of
our
testing
would
happen.
F
Honestly,
you
are
trying
to
build
out
a
performance
to
it.
We
do
in
gitlab,
have
a
performance,
kit,
gpk
gitlab
performance
kit,
which
I
believe
we
are
using
it
to
test
gitlab.com
performance,
but
I
don't.
I
don't
think
that
is
used
for
security
purposes,
just
to
see
how
it's
going
to
impact
our
performance.
So
that
is
something
maybe
we
can
try
to
look
into,
and
if
that
is
some-
and
we
have
a
lot
of
documentation
on
that
too.
F
So
maybe
we
can
work
together
to
because
I
do
not
have
any
sats,
unfortunately
dedicated
to
defend
and
I
don't
have
anyone
to
pull
into,
but
maybe
we
can
come
up
with
a
plan
and
a
strategy
and
maybe
work
out
in
the
future,
milestones
to
pair
up
with
the
engineer
and
see
if
we
can
implement
that.
So
that's
what
I
am
focusing
on
take
these
bullet
points
see
what
are
the
ones
that
are
easy
ones,
for
example
the
user
experience
with
installing
and
our
configuration
components.
F
F
The
second
one
would
be
the
performance
one
gpk,
since
we
already
have
it
maybe
plan
it
in
the
future
milestones
and
maybe
have
it
running
in
the
background
we
can
look
into
it
so
that
way,
at
least
by
time,
when
we
get
an
sct
hope,
it's
going
to
be
probably
20
21,
I
mean,
let's
be
realistic.
D
No,
I
I
generally
agree
with
what
sam
said
in
this
areas
that
he
mentions,
probably
where
we
can
do
the
list
right
now
and
other
stuff,
like
automated
testing
for
dashboards
and
ui,
and
just
a
basic
unit
testing.
We
definitely
can
handle
ourselves
so
yeah.
That's
I
will
side
with
simon
on
that
cheers.
Arthur.
C
No
visa,
you
know-
and
I
think
you
have
just
just
having
being
in
touch
with
you
and
and
having
the
the
channel
open,
is
already
being
helpful.
I
just
learned
about
the
gpk,
I
didn't
know
it
existed
if
it
helps
even
better
and
the
question
about
k3s
that
I
didn't
know
who
to
ask
now.
I
can
ask
you
so
it's
already
helpful
and
rest
assured
we.
We
have
no
expectations
that
you're
gonna
go
in
and
deliver
everything
because
you
won't.
You
won't
be
on
you,
but
thank
you.