►
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).
B
Do
you
want
to
kick
us
off
sure
and
for
folks
note,
the
two
items
in
yellow
and
notes
here
which
we
will
we
won't
read?
So
are
there
any
questions
about
the
realignment?
We
got
the
issue
there
in
the
ama,
so
we
just
wanted
to
pause
there
and
see
if
there
are
any
questions.
C
B
Let's
see
here,
who
is
it
on
your
team?
Who
else
is
it
on
your
team
and
lindsay?
Who
is
it
on
your
team.
C
It's
chad,
myself
and,
I
believe,
dave
pisick-
am
I
allowed
to
say
if.
C
B
And
then
after
then,
there's
going
to
be
it's
going
to
be
non-confidential
anymore.
All
the
changes
and
david
de
santa
is
going
to
post
in
what's
happening
at
gitlab
and
also
do
a
company-wide
ama.
A
Yeah,
so
just
keep
in
mind,
even
though
this
has
been
announced
to
the
secure
and
defend
engineering
groups
and
engineering
sections,
it
has
not
yet
been
more
broadly
announced.
We
are
planning
to
do
that,
we're
just
obviously
we
needed
to
figure
out
who
is
going
to
move
over,
and
you
know
we
needed
a
little
bit
of
time
there,
where
we
could
have
that
available
to
us
before
rolling
that
out
to
the
rest
of
everyone,
so
we're
still
in
that
period
of
time,
but
it
won't
be
much
longer.
B
Cool,
so
I
wanted
to
do
a
quick
announcement.
So
no,
I
know
you
just
found
out
about
this
meeting
today,
so
glad
you
were
able
to
make
it
today.
You
want
to
do
a
quick
announcement.
How
long
have
you
been
in
gitlab?
What
are
you
been
working
on
something
non-work
related
about
you,
etc?.
C
Sure
my
name
is
mill.
Khan.
I'm
an
engineer.
I
was
an
engineer
on
the
composition
analysis
team
at
git,
lab
I've
been
at
get
lab
since
june
july,
9th
2019.
So
just
over
a
year,
something
interesting
about
me.
I
enjoy
lifting
and
my
partner
and
I
have
been
together
for
19
years
married
for
15
and
we
have
two
children,
ages,
13
and
11.
We're
quite
proud
of.
C
How
heavy
do
I
lift
today,
not
very
heavy
in
my
peak
dead,
lift
405
bench
250
squat,
365,
overhead
press
155.?
These
are
like
three
sets
of
five
and
I'm.
These
are
also.
I
know.
C
Yeah
I
joined
the
thousand
pound
club,
so
that
was
that
was
an
achievement
for
me
and
then
with
the
start
of
well
in
march,
when
jim
shut
down,
I
also
took
a
break
from
strength
training,
so
I
I'm
working
my
way
back
up.
I've
recently
acquired
some
equipment
in
my
home,
so
slowly
working
my
way
back
up.
I
love
it.
I
just
enjoy
it
very
much.
C
B
Cool
again
welcome
and
we'll
hear
from
can
john
and
dave
in
future
meeting.
B
So
let's
see
here,
I
guess
sorry.
I
had
so
many
things
on
the
agenda
so
sam,
based
on
the
changes
to
based
on
the
alignment
how's,
the
roadmap,
changing
for
13.6.
A
Yep,
so
I
updated
our
priorities
list
for
those
of
you
who
are
new
to
that
for
our
group,
and
this
is
unique
just
for
our
group.
Not
everyone
does
the
second
lab,
but
we
have
an
issue
that
we
keep
always
open
and
it
always
has
the
latest
priorities
there.
So
I
update
that
roughly
once
a
week,
I
try
to
update
it
on
mondays
and
I
do
have
that
updated
at
least
a
little
bit
with
with
the
new
changes.
A
I've
been
a
little
bit
busy
because
we've
had
a
there
are
a
lot
of
things
to
update
because
of
these
changes.
So
that's
taken
up
a
fair
amount
of
my
time,
but
you'll
notice.
We
do
plan
to
finish
out
the
alert,
dashboard
work
that
we're
doing
currently
and
the
alert
dashboard
and
the
policy
management
ui.
A
Both
of
those
uis
will
end
up
folding
under
the
new
category
that
we're
creating
it's
still
to
be
determined.
What
the
name
is
right
now,
I'm
leaning
towards
security
orchestration
is
probably
what
it
will
be
called
so
again
that
alert
dashboard
is
going
to
continue
and
we
then
plan
to
start
working
on
for
the
container
scanning
category.
We
plan
to
scan
containers
in
production.
I
know
we've
talked
about
that
the
last
few
weeks
here
in
our
group
conversation
and
then
for
the
security
orchestration
category.
A
We
plan
to
continue
work
in
policy
management,
beginning
with
adding
support
for
daft
scans
death
scheduling
scans
at
the
project
level,
and
the
reason
for
that
is,
it
just
seems
to
be
the
the
lowest
hanging
fruit.
If
we
can
get
it
working
with
daft
and
prove
it
out,
then
we'll
have
a
repeatable
model
that
we
can
extend
out
to
the
other
scanners
as
well.
A
So
I
know
some
of
the
stuff
in
get
lab
is
probably
still
lacking
in
details
on
building
out
those
epics
and
issues
as
much
as
I
can.
I
just
got
done
working
on
an
mri
that
changed.
I
think
157
files
across
our
handbook,
so
there
are
changes
all
over
the
place.
I'm
I'm
sorry
working
with
the
dividers
remaining
to
protect.
Yes,.
E
When
you
you,
you
do
you
have
you
shared
the
issue?
Are
you
going
to
share
it
later
today?
There's
some
engineering
changes
as
well
just
for
cross
visibility
on
the.
B
The
handbook
yeah,
I
posted
it
in
slack-
I
haven't
posted
in
here
yet
and
it's
barely
it's
just
a
skeleton
of.
We
need
to
figure
out
what
we
need
to
do.
Not
what.
B
B
Said,
okay,
which
of
those
things
do
we
need
to
do
this
time?
So,
thankfully,
thankfully,
for
me,
sam,
has
most
of
the
work
on
on
handbook
changes.
Most
of
the
changes
are
not
not
gonna
change
the
engineering
pages,
but
we
can
help
you
sam.
If
you
need
our
help,
of
course,
but
I
think
there
are
like
four
engineering
pages
and
another
300
references
to
ben
in
the
handbook.
E
There's
stuff
in
the
middle
as
well
same
like
the
labels,
if
you
want
to
coordinate
and
and
and
receive
some
help
on
that
with
the
triage
bot,
you
can
use
that
to
relabel
things
across,
so
I
can
help
okay.
A
B
Is
it?
Is
it
ready
to
merge,
or
is
it
still
being
reviewed.
B
A
Yeah,
I
think
that's
I
have
rights
too,
but
I
think
it's
probably
gonna
go
to
said
for
approval.
Okay,.
B
So
I
glossed
over
something
so
arthur
when's
your
last
day,
it's
coming
up
soon,
right.
B
Really
appreciate
all
your
contributions,
it's
been,
it's
been
great
working
with
you,
I
don't
know
if
we'll
talk
again
and
we'll
see
each
other
again,
but
best
of
luck
in
in
what's
next.
G
E
You'll
be
missed
for
the
record.
Your
your
skill,
knowledge
on
on
on
on
that
container
security
area
will
be,
will
be
hard
to
replace
we'll
be
working
harder
without
you.
G
Thanks,
I
think
it's
a.
I
was
a
great
opportunity
with
the
changes
that
happen
right
now,
for
a
team
to
kinda
revenge
and
kind
of
not
rely
on
the
previous
achievements.
So
I
think
it's
a
good
time.
G
B
Cool
again,
I
have
too
much
of
the
agenda
apologies,
but
I
think
it's
probably
the
last
thing
I
added
so
e
here
so
john
spelled
can
is
in
ireland
and
so
now
we'll
have
at
least
one
person
not
in
the
americas,
time
zone
or
apac.
So
probably
like
the
other,
the
threat
insights
meeting,
where
we
have
some
of
them
at
a
good
time
for
mia
and
some
every
other
one,
a
good
time
for
apac.
We
should
start
alternating
the
time
for
this
one.
C
Who
has
it
I'm
now
sure
what
time
zone
dave
is
in
either
dude?
Is
that
dave
isaac.
C
A
I
can
the
only
thing
is
for
some
reason
I
still
don't
have.
I
don't
think
I
have
management
rights
on
the
threat
management
calendar.
We
should
probably
get
that
resulted.
E
Hey
sam
thanks
lindsey,
so
lindsay
with,
with
the
with
your
team,
with
the
front-end
engineers,
they'll
they'll
they'll
pick
and
choose
the
ones
that
they'll
attend.
D
Right
we'll
discuss
as
far
as
a
schedule
for
attending
the
weekly
meetings
and
sharing
that
information.
But
we'll
need
a
couple
of
weeks
to
figure
that
out.
D
B
B
D
That's
correct,
and
so
far
that's
been
our
our
take
for
for
threat.
Insights
as
well,
and
people
do
develop
preferences
and
areas
that
they're
more
comfortable,
so
someone
could
naturally
fall
into
you
know
a
more
consistent
role
in
container
security,
but
we'll
see
how
that
shaped
up
over
time.
I
don't
like
the
idea
of
just
one
person
being
a
bottleneck
if
they
decide
that
they
want
to
take
a
holiday
or
you
know
not
giving
them
people
to
talk
to
if
they
get
stuck.
B
I
noticed
in
the
retrospective
that
the
company-wide
retrospective
that
neil
mentioned
like
how
to
allocate
was
a
challenge
on
on
a
secure
department,
so
just
something
to
keep
an
eye
on.
You
know
like
how
do
we
make
it
about
a
quarter.
D
Yeah
I've
picked
his
brain
on
that
a
little
bit
and
it
sounds
like
it's
only
worked
out
of
sort
of
luck
up
until
now,
so
making
sure
that
we
have
a
process
to
ensure
that
that
25
gets
prioritized
and
that
you
know
people
aren't
context
switching
all
the
time
and
that
we're
not
dropping
the
balls.
B
D
C
I
do
I
do
sorry,
okay
yeah,
so
I
just
wanted
to
update
the
group
since
the
container
scanning
analyzer
sort
of
shifting
ownership
that
dan
is
currently
working
with
the
customer.
He
was
looking
for
some
help
in
terms
of
debugging
an
issue
with
container
scanning.
C
I
wasn't
able
to
make
the
call
earlier
today,
but
he
did
record
the
logs
he's
going
to
share
that
out
as
soon
as
he
can.
So
we
can
try
to
help
get
that
going.
This
customer's
been
great.
They
they
provided
us
with
hands-on
access
to
some
of
their
network,
while
they
were
sorting
out
some
issues
with
dependency
scanning
and
license
compliance
and
just
bringing
it
up
for
awareness
as
we
start
to
increase
our
understanding
of
the
container
scanning
analyzers.
C
I
haven't
spent
too
much
time
with
that
particular
analyzer,
so
I'm
doing
my
best
to
sort
of
learn
the
different
pizza
pieces
of
it
I'll
report
back.
If
I
need
more
help
or
we
need
to
pull
in
resources.
E
It's
it's
awesome
that
you
that
you
went
in
there
and
and
figure
out
the
the
schedule
for
updating
the
image,
thanks
for
doing
that,
adam
and
and
his
manager
and
and
the
leadership
in
the
rest
of
cube,
has
an
expectation
that
adam
will
need
to
help
us
a
bit
with
this.
So
don't
don't
feel
too
bad
for
for
asking
too
many
questions
to
him.
C
All
right
so
then
dan
adam
and
I
or
dan
started
a
thread
that
included
both
adam
and
I
he's
not
online
yet
so
I
I
appreciate
that
he
will
probably
pick
it
up
when
his
when
his
day
comes
in
until
then,
I'm
sure
we'll
sort
it
out
as
we
as
I
believe
this
team
is
starting
to
take
ownership
of
that
is
that
correct,
okay,.
A
Yep
yeah,
that
is
correct.
We
will
be,
and
you
know
we
get
the
maintenance
tail
along
with
the
category,
including
things
like
bug,
fixes
and
whatnot.
If
there
is
an
issue
created
to
track
that
bug,
could
you
send
that
my
way
that
way
we
can
put
that
on
the
priorities
list
as
well?
I
try
to
just
put
everything
there
on
the
priorities
left,
so
we've
got
one
less
to
go
off
of.
C
This
particular
customer
indicated
that
they're
hesitant
to
open
issues,
even
private
issues,
I'll
bring
that
up
just
to
say
if
we
could.
C
Information's
sort
of
been
relayed
to
us
through
through
dan
and
and
that
customer
actually
sent
me
historically
but
I'll,
try
to
convince
them
or
steer
them
towards
private
issues.
If
that's
possible.
A
E
B
C
F
Yeah,
these
guys
from
security
are
talking
too
much
right,
I'm
sure
so
yeah
I
was
just
it's,
which
was
just
that
I
I
came
back
from
vacation
and
I
saw
the
dwarf
is
going
uil
and
I
had
a
couple
of
issues
that
were
kind
of
people.
Picking
me
in
the
issues
about
what
and
then
that's
why.
I
asked
the
question
over
there.
If
we
are
going
to
close
all
of
them
or
or
just
wait
a
little
bit
more.
A
Yep
so
we
will
close
those
out,
but
we
should
probably.
G
A
Like
everything
else
wait
until
next
week,
just
to
align
that
with
the
rest
of
our
communication
out
to
everyone
else
in
the
world,
since
we're
on
that
topic,
I'm
happy
to
shed
a
little
bit
of
a
little
more
light.
On
that
I
mean
waff
has
been
a
challenge
from
the
beginning.
We
it's
a
market
where
there
are
some
very
large,
very
well
established
players
in
the
space,
and
you
know
the
players
that
have
been
here
for
decades
already
and
we're
coming
in
new,
and
so
that's
an
area.
A
Laugh
is
also
tricky
because
oftentimes
there's
the
expectation
of
providing
distributed,
denial
of
service
attack
protection
and
even
load
balancing
capabilities
and
doing
that
from
within
a
single
node
in
kubernetes
is
difficult,
if
not
impossible,
to
do,
and
so
I
don't
know
that
we're
going
to
steer
clear
of
wax
capabilities
for
forever.
I
think
the
proposal
that
we've
talked
about
of
using
psyllium,
to
call
out
to
the
mod
security
daemon
is
a
good
option
for
the
future.
A
But
you
know
we're
also
recognizing
that
there
are
a
lot
of
other
players
that
usually
sit
in
front
of
the
application
because
architecturally
they
sit
in
front
they're,
able
to
do
things
like
that
load,
balancing
and
distributed
denial
of
service
protection
that
we're
just
we're
in
the
wrong
place
to
be
able
to
provide
those
protections.
A
And
so
those
are
really
you
know
just
wanted
to
share
a
few
more
of
the
reasons
about
why
we're
moving
away
from
laugh,
especially
since
I
know
there
are
a
lot
of
people
on
this
call
who
have
worked
on
this,
and
you
know
at
one
point
in
time.
It
was
a
priority.
A
You
know
I
would
rather
fail
fast
and
adjust
and
change
now,
rather
than
try
to
hang
on
to
it,
and
you
know
just
have
it
not
not
work
out
for
us
long
term.
So
this
will
help
reduce
the
amount
of
maintenance
that
we
have
it'll
reduce
our
support,
support
of
maintenance
burden,
which
is
going
to
be
important,
because
we
have
a
lot
of
other
things
that
we
want
to
focus
on.
F
Yeah,
thanks
for
for
expanding
on
that.
E
A
Yeah
yeah
protective
is
helping.
You
know
really
all
of
defense
before
we
were
focused
on
just
that.
You
know.
Security
operations,
persona
and
part
of
that
move
to
protect
as
well
is
about
shifting
the
persona
that
we're
targeting
to
more
of
bridging
the
gap
between
development
and
devops
and
suck
ops,
rather
than
just
targeting
the
secops
persona.
Only
so
there's
kind
of
both
of
those
are
factors
in
that
renaming,
and
I
also
I
put
this
in
the
notes,
but
I
failed
to
mention
it.
So
I
have
an
action
item.
A
Among
the
other,
things
on
my
to-do
list
is
to
figure
out
our
end-of-life
strategy
there,
so
we
will
need
to
put
together
a
deprecation
notice.
I
haven't
even
looked
it
up
yet
what
our
processors
here
at
gitlab,
but
we
will
want
to
make
that
publicly
known
that
we're
going
to
deprecate
it
and
then
I
think
we
have
to
keep
it
around
for
so
many
releases
before
we
actually
to
majorly.
E
A
Not
sure
if
we
have
to
wait
until
14
or
if
it's
just
you
know
like
if
we
announce
it
at
13
5,
then
it'll
be
13,
6
13
7
and
we
can
remove
it
at
13
8..
I
I'm
not
quite
sure.
Like
I
said
I
don't
know,
I
need
to
familiarize
myself
with
our
policy
there.
E
G
I
have
a
similar
question:
what's
the
support
policy
for
the
previous
versions
in
this
case
like
if
you
deprecate
the
product,
there
are
still
people
who
will
be
using
previous
stable
versions
like,
I
think
we're
patching
up
to
12.0
branches
right
now,
so
with
deprecation.
How
is
the
support
is
going
to
continue
working
with
that.
A
C
A
Correct
or
how
would
be
done,
yeah,
okay,
right
time,
yeah,
we
are
at
time
we'll
roll
this
next
one
over
into
planning
breakdown
for
next
week.
This
is
really
just
a
research
spike
to
start
thinking
about
how
we
want
to
architect
our
policy
management
going
forward.
We
did
one
path,
just
to
get
it
out
the
door
for
mvc,
but
now
we're
talking
about
something,
that's
much
broader,
that
spans
lots
of
scanners
and
lots
of
technologies.
A
So
I
just
wanted
to
start
up
the
discussion
about
how
and
where
all
of
that
is
going
to
live,
but
again
we're
at
times.
So
we
can
cover
that
more
next
week.
E
That's
great
thanks
for
for
that.
You
sort
of
answered
the
question
that
I
had
that
the
agenda
was
empty,
so
I
was
looking
for
stuff
to
put
on
plenty
breakdown,
but
then
wayne
won't
fix
the
agenda
problem.
B
That's
thankfully,
mo
just
for
context.
That
is
not
a
common
pattern,
but
it
was
today.
A
All
right
thanks,
everyone
I'll
be
posting
this
to
youtube
shortly
after
have
a
great
day.