►
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
Hello,
everyone
welcome
to
the
weekly
group
discussion
for
ski
with
threatened
sites.
Today
is
the
18th
or
the
19th
of
january,
depending
where
you
are
and
becca
was
just
saying
how
the
agenda
is
a
bit
sparse
and
I
always
agree-
and
I
was
about
to
say
that
you
know
that
there's
a
lot
of
reliability,
issues
that
the
back
end
are
working
on.
So
we
we're
blocking
a
fair
amount
of
work
and
I
think
the
the
the
front
end
has
has
also
a
fair
bit
on
their
plate
and
it's
going
well.
A
But
in
saying
that,
there's
one
agenda
item
that
matt
put
in
and
he
sent
excuses
he
wasn't
able
to
attend,
but
it's
getting
involved
getting
engineers
involved
with
customer
calls,
and
there
are
three
three
sort
of
angles
to
that:
there's
the
product
angle,
the
the
user,
experience
angle
and
the
support
angle
so
mats
covering
the
product
angle.
I
guess
back
up
if,
if
we
want
to
get
involved
with
user
experience,
probably
be
talking
to
you.
A
And
and
on
the
support
side,
I
was
talking
to
gerardo
like
if,
if,
if
he's
getting
on
a
call
with
customers,
put
a
shout
out
in
the
in
the
channel
or
if,
if
an
engineer
is
interested
in
participating
reach
out
to
her
out
and
you
you
keep
you
in
mind,.
A
A
If
you
do
engage
we'd
like
to
to
know
and
report
on
it,.
A
D
Is
kind
of
on
the
the
user
feedback
side
he's
saying
it'd
be
great
to
hear
user
feedback
regularly,
whether
we
attend
the
calls
directly
or
not.
For
instance,
alexander
on
the
team
keeps
posting
regular
weekend
weekly
update
of
what's
happening
in
our
group
channel.
We
could
do
something
similar
for
customer
feedback.
Posting
feedback
regularly
online
slack
could
help
improve
the
visibility
of
what
the
customer
says.
D
That's
awesome
idea
just
to
be
informed
of
what's
going
on
and
then,
additionally,
in
terms
of
involvement
in
these
customer
calls.
Where
available,
I
had
a
sync
with
matt
earlier
today,
and
I've
seen
it
probably
work
better
or
easier
for
everybody.
If
matt
just
can,
when
he
has
opportunities
in
front
of
him
he's
going
to
meet
with
the
customer
tomorrow
or
next
week,
he
can
just
let
everyone
know
and
those
are
that
are
available
and
interested
could
let
him
know
sign
up
for
it.
D
He
was
a
little
concerned
having
like
10
people,
offer
excitement
and
interest
in
having
a
bunch
of
people
bombard
a
meeting,
so
we'll
probably
have
to
and
still
some
limits,
but
I
I
think
that
might
be
a
little
bit
easier
for
matt
to
manage
rather
than
us,
reaching
out
and
saying
yeah,
I'm
interested,
because
I
think,
for
the
most
part,
most
of
our
department
is
curious
and
I
would
like
the
opportunity
so
I
think
it
just
comes
down
to
will
it
work
for
my
time
of
day
and
what's
the
topic,
so
I
think
he
might
work
too.
D
A
C
I'll
add
something
that
customer
feedback
is
useful,
but
I
think
being
able
to
see
what
the
customer
does
in
a
typical
workflow
would
be
really
valuable
too,
because
right
now
we
don't
really
have
insight
into
how
people
use
the
the
vulnerability
list
and-
and
you
know
the
the
app
we
just
if
we
get
feedback,
we
can
get
feedback
about
their
specific
pains.
C
But
you
know
we
don't
really
see
how
they're
actually
using
it
on
a
daily
basis,
and
so
that
might
give
us
hints
as
to
like
what
we
should
prioritize
in
terms
of
future
work
or
how
we
should
lay
out
the
ui,
depending
on
how
much
the
user
is
scrolling
or
struggling
to
find
various
things
that
they
may
not
necessarily
voice
in
a
concern.
B
B
So
that's
why,
when
we
do
any
kind
of
testing
or
if
we're
doing
a
cms,
to
try
to
graduate
the
maturity,
matt-
and
I
were
just
talking
this
morning
about
going
from
viable-
which
vulnerability
management
is
currently
in
to
complete
potentially
later
this
year,
we
had
it
set
for
july.
But
pending
you
know,
when
the
reliability
stuff
is
going
to
be
completed
and
when
we'll
actually
be
able
to
ship
some.
B
Some
new
features
that
customers
have
been
asking
for,
but
as
part
of
that
cms
that
category
maturity
scorecard
to
get
to
complete
I'll,
have
to
talk
to
customers
and
have
them
complete
some
tasks
and
then
rate
how
easy
it
was
to
complete
those
tasks.
B
So
that's
something
that
I'll
probably
use
a
test
project
for,
but
yeah
I
mean
in
terms
of
getting
them
to
show
us
their
screens
is,
is
always
tricky.
For
that
reason,.
B
Yeah
I
just
wanted
to
you
know
from
my
perspective.
You
know
I
kind
of
took
over
threat
insights
from
andy,
and
I
know
he
already
left
a
backlog
of
design
issues
and
as
matt
and
I
are
talking
about
when
we
might
be
able
to
get
to
that
complete
maturity
level
just
wanted
to
check
in
and
see
how
the
reliability
initiative
was
going.
B
A
It's
been,
it's
been
a
long
road
with
reliability
and
issues
in
back
end,
not
not
only
just
performance
but
but
also
some
overdue
clean
up
and
refactors.
So
the
current
big
thing
is:
this
thing
is
something
called
the
uuid
migration.
It's
it's
it's
an
enabler
to
a
lot
of
the
things
that
we
want
to
do.
That's
on
the
way,
we're
hoping
that
it'll
finish
friday
and
it
was
has
been
a
long
time
coming.
A
The
the
other
reliability
issue
that's
going
on
is
something
called
the
vulnerability
reads:
it's
a
performance
initiative.
It's
basically
improving
the
speed
of
the
variability
report,
the
the
anything
that
reads,
the
the
vulnerability.
So
that's
on
the
way
it
was
blocked
a
little
bit
by
the
uid
that
one
will
probably
finish
next
milestone,
there's
a
couple
of
others
that
are
that
will
go
in
there,
but
the
long.
The
short
of
it
is
that
this
milestone
we're
picking
up
the
developer
security
training
stuff.
A
So-
and
I
know
the
the
front
end
is
already
working
on
it.
Samantha
is
has
been
pairing
with
dave
on
on
those
issues,
and
the
backhand
has
already
started
me
development,
so
the
the
database
and
the
graphql.
A
A
B
From
a
ux
perspective,
yes,
it's
a
lot
of
well.
I've
been
working
on.
Of
course,
the
a
big
one
is
the
inline
findings
in
the
mr
in
the
changes
tab.
I
don't
know
if
your
team
has
come
across
that
yet.
B
But
I'm
happy
to
link
to
that
issue
in
the
agenda
where
people
can
leave
feedback
or
questions
asynchronously,
we're
still
kind
of
ironing
out
the
last
couple
of
details
there
with
the
create
team,
and
but
that's
it's
coming
to
an
kind
of
a
an
end
as
in
terms
of
the
mvc
anyways.
I
think
there's
a
lot
that
could
be
done
there,
but
that
is
to
so
that
developers
that's
kind
of
the
shift
left.
B
It's
a
shift
left
initiative
where
developers
can
start
to
triage
vulnerabilities
that
are
directly
related
to
their
source
code
from
the
changes
tab.
So
that's
one
thing
and
then
other
things
that
we're
looking
at
is
the
on
the
vulnerability
report
customization
so
in
terms
of
like
grouping
or
how
they
want
the
data
arranged,
something
that
I'm
looking
at
is
you
know
how
they
how
they
want
to
organize
this
information?
Do
they
want
to
view
things
in
groups?
B
B
Bit
more
flexible
and
then
there's
bulk
actions
that
I've
been
looking
at
as
well,
so
being
able
to
bulk
select
all
across
pages
right.
A
B
At
a
time
or
something
like
that
right,
yes,
you
don't
have
to
go
page
by
page
what
else
bulk
attached
to
an
existing
issue
and
bulk
create
an
issue
for
multiple
vulnerabilities.
B
There's
been
some
work
that
we're
doing
on
that
and
then
auto
resolve.
I
just.
A
B
Yes,
indeedy
matin
and
I
met
with
daniel
last
week,
and
we
discussed
this
because
there's
a
lot
of
like
little
nuances,
where,
with
the
with
the
checkbox
and
then,
if
this
then
this
and
just
considering
all
the
possible
states
and
understanding
how
the
back
end
works
because,
for
example,
you
can't
daniel
correct
me.
If
I'm
wrong,
you
can't
select
all
and
then
pad
and
then
go
to
another
page,
because
then
it
kind
of
breaks
that
select
all
so
just
like
little
nuances.
There.
B
C
Yeah
we
we,
we
decided
that
we're
going
to
go
with
an
initial
implementation,
just
so
that
we
can
get
something
in
front
of
everyone
that
they
could
look
at
using
production
data,
and
then
it
will
be
behind
the
feature
flag
and
from
there.
We
can
then
discuss
how
we
want
to
handle
the
the
other
features.
We
took
a
look
at
google
or
gmail
because
it
also
has
pagination
with
a
bulk
slick
feature
and
some
of
the
things
that
it
does.
Is.
C
I
guess,
what's
that
word,
it's
non-intuitive
based
on
what
you
would
think
of
doing
mentally,
but
it
makes
sense
from
like
a
technical
standpoint
where
they
avoid
a
lot
of
complexity.
By
doing
it,
the
way
that
they
do
it.
So
we
wanted
to
kind
of
the
the
discussion
was
just
sort
of
like
we're
waffling
between
a
or
b.
So
we
decided
that
we're
just
gonna
do
paging
for
now,
and
then
we
can.
A
C
Yeah
yeah,
it's
it's
switching
from
the
drop
downs
to
basically
a
search
bar
where
it's
like
the
issues
or
the
board
where
you
can
type
in
text
and
it
will
yeah.
C
Areas
as
far
as
I
know,
it's
something
that
we
we
know
it's
upcoming
work,
but
we
haven't
had
any
time
to
really
prioritize
or
discuss
how
it
should
work,
because
it
is
a
fairly
large
refactor,
and
we
also
need
to
kind
of
discuss
like
how
we
want
to
implement
the
like,
which
items
we
want
to
have
in
the
drop
downs
and
how
the
search
could
work,
because
it
will
also
involve
backing
changes.
If
we
do
allow,
say
free
form,
searching
not.
A
A
Image
search
you
can
look
for
for
a
kubernetes
namespace.
You
know
what.
C
Yeah-
and
I
think
I
I
don't
remember-
who
told
me
this,
but
we
were
looking
into
getting
elasticsearch
implemented
first,
so
that
we
can,
you
know,
solve
those
kind
of
like
freeform
searches,
so
that
needs
to
kind
of
land.
First
before
we
can
discuss,
I
think,
but
I
forgot
who
told
me
that
it
wasn't
you
right,
thiago,
no.
A
Maybe
he
was
mad.
Well
I
I
did.
I
did
get
a
shout
from
dylan
back
when
he
was
in
in
global
search
asking
hey:
should
we
ingest
vulnerabilities
into
to
elastic
I'm
like
yeah,
but
then
you
know
it
wasn't
in
anyone's
priority
and
and
we
don't
have
it
yet
so
I'm
curious
to
know
if
if
it's
bubbling
up
again,
okay
yeah,
the
short.
A
A
We've
turned
that
off,
because
there
was
a
discussion
saying
well,
we
really
want
to
keep
the
single
source
of
truth
in
the
vulnerability
report
and
if,
if
the
filter,
if
the
filtering
is
not
good
enough
to
to
to
be
able
to
link
directly
to
a
view
that
shows
us
what
we
need
for
now,
the
the
best
approach
is
to
just
put
a
new
tab.
At
least
it
keeps
everything
under
the
vulnerability
report
and
then
the
second
place
was
was
gonna.
Come
was
in
the
container
registry
scanning.
A
So
if
you
go
to
the
packages
registry,
it
was
gonna
show
up,
there'll,
probably
still
be
some
linking.
You
know
you
can
still
show
hey.
This
image
has
x
vulnerabilities
click
here,
and
then
you
take
it
to
the
report,
but
but
yeah
that
I've
already
forgotten
what
the
component
is
called,
but
the.
B
Yeah
I
mean
we're
looking
at
like
customized
views
where
we
would
essentially
enable
the
user
to
come
up
with
their
own
view.
Their
own
preset
filters
the
source
of
the
scans,
whether
it's
a
ci
cd
scan
on
demand.
What
have
you
and
I,
what
I'm
coming
up
against,
is
that
you
would
that
we
could
offer
this
functionality
in
a
drawer,
but
then,
essentially,
how
do
we
show
that
those
filters
are
being
applied
without
having
those
filters
visible
at
all
times?
B
So,
for
example,
one
of
the
things
that
andy
had
in
there
is
detected
date
and
what
kind
of
date
format
you'd
want
to
search
by,
we
don't
have
date
as
a
filter,
so
that
would
be
another
static
filter
that
we
would
have
to
add
to
the
top
of
the
page.
So
there's
a
lot
of
things
that
are
impacted
by
not
having
the
filtered
search
component
from
on
the
ux
side
of
things,
because
I
don't
want
to
just
have
a
horizontal
scroll
of
static
filters,
so
it
definitely
poses
a
challenge.
A
A
bit
with
that,
we
don't
have
any
other
items
in
the
agenda.
Anyone
else
got
something
to
bring
up.
B
I
have
one
more
thing:
oh
yes
came
across
and-
and
maybe
this
is
more
of
a
conversation
for
matt,
but
I
I
came
across
this
issue
to
provide
a
way
to
mass
delete
vulnerabilities
from
the
vulnerability
list.
I
don't
know
this.
This
issue
has,
it
seems,
to
have
gone
somewhat
stale.
The
last
activity
from
our
team
was
six
months
ago,
but
I
don't
know
if
that's
something
that
is
should
be
part
of
it.
I.
A
Know
about
it
just
because
matt
has
had
reservations
about
implementing
this
okay
and
and
then
what
what
we
ended
up
doing
from
an
engineering
point
of
view
of
engineering
site
was
just
provide.
A
script
say:
hey
run
this
and
you
basically
reset
your
well
something
that
happens.
Is
people
start
playing
with
it
or
they
enable
a
noisy
scanner
like
one
of
the
sas
analyzers
without
tuning
and
then
suddenly
you've
got
50,
000
vulnerabilities
and
then
you'll
go
cool
that
that
looks
nice
now,
let's
start
from
scratch,
there's
no
way
to
do
that.
A
B
B
A
C
C
B
C
B
A
A
good
question:
it
comes
up
every
now
and
then
matt's
free
to
prioritize
it.
If
you
like,
we,
we
pretty
much
have
the
code
at
this.
At
this
point,
it
would
be
a
matter
of
putting
a
create
a
ui
for
it
and
figure
out.
How
many
are
you
sure
pop-ups
we
want
to
do
before
they
we
allow
them
to
click.
It.