►
From YouTube: 2020.01.28 - Defend Staff Meeting
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
So
getting
started
so
so
ever
moved.
First
I'd
ever
move
be
from
the
agenda
from
this
meeting.
The
individual
features
and
things
for
specific
teams
and
instead
they'll
be
discussed
in
the
great
feature
and
individual
team
meetings.
We
already
have
one
for
first
class
vulnerabilities,
we'll
be
creating
one
for
a
container
nap
and
application
team.
You
know
we're
laugh
and
container
network
security
will
be
discussed,
I'm
kind
of
similar
to
what
we're
doing
for
that
first
class
bones
meeting
any
feedback
on
this
ideas
to
improve
good
idea,
a
bad
idea.
A
C
Will
recognize
that,
instead
of
writing
it's
we
should
keep
in
mind
that
we
are
seeing
fair.
So,
as
I
said,
the
only
program
that
is
other
people
like
Cindy
or
other
people
outside
of
the
team
might
have
issues
follow
me
up,
what's
really
happening,
so
it
should
be
issues
first
and
this
sequence
session
points
if
needed,
but
not
of
the
world.
Okay,.
A
So
async
is
the
async
is
the
first
choice
that
people
should
make.
You
know
issues
first,
slack
second
and
weight,
and
you
know
meeting
is
last:
it's
good
to
sync
up.
You
know
get
it
in
periodically,
but
it
shouldn't
be
what
people
depend
on
primarily
absolutely,
and
you
know
it
it's
also
gonna,
be
we
don't
have
everybody
in
that
first
class
phones
meeting
who's
working
on
it
every
time,
but
so
people
can't
make
it.
We
have
most
people,
but
probably
not
everybody,
it's
just
using
that
as
a
base
and
that's
working
out
quite
well.
A
So
people
come
when
they
can
when
they
have
something
interested
interesting
to
discuss.
They
listen
to
the
recording
and
read
the
notes.
If
they
can't
make
it,
you
know,
etc,
etc.
So,
with
all
those
good
best
practices,
I.
D
Just
want
a
note
on
that.
One
I
think
we
created
that
meeting
series
specifically
because
it
was
a
called
a
bhp,
a
big
hairy
problem,
and
it
was
something
that
was
dragging
on
so
I
think
that
meeting
series
in
general
was
kind
of
the
exception,
not
the
rule,
and
it
does
have
an
end
date
on
it.
Yeah.
A
It's
a
good
point
is
probably
will
probably
be
creating
a
separate
meeting
that,
since
that
team
is
primarily
working
on
your
you
know.
Your
team
met
primarily
working
on
first-class
bones.
It's
gonna
turn
into
from
a
first-class
bones
meeting
to
a
meeting
for
the
team.
First-Class
phones,
anything
else
the
team
wants
to
discuss,
and
this
would
be
a
separate
one,
and
this
meeting
in
particular
this
defense
staff
meetings-
you
get
to
be
much
shorter
as
we
do
this
is
that
that
reasonable,
it's
that
make
sense
so.
B
A
Well,
I'll
get
it
scheduled
and
then
and
put
it
on
the
calendar,
and
you
know
this
is
not,
of
course,
in
concrete.
Nothing
is,
you
know,
will
change
things
over
time
to
make
it
more
efficient.
Anything
else
on
this
Lindsay
over
to
you,
I.
B
Think
it's
a
great
transition
to
the
second
topic
as
well.
If
we
do
have
more
synchronous
meetings,
we
need
to
have
ways
for
people
who
are
sleeping
at
night
or
not
able
to
attend,
to
learn
that
information
as
well
as
show
our
general
community
have
a
defend
teamwork.
So
we've
been
starting
to
get
better
about
posting
our
videos
to
unfiltered,
especially
the
defend
playlist
on
there,
and
this
is
just
remain
I,
don't
think
we
should
have
I
think
it
should
be
the
default.
We
should
plan
on
always
posting
our
meetings
to
my
filter.
B
Unless
something
comes
up
in
the
course
of
the
conversation
around
a
candidate
or
a
customer
and
I
want
to
encourage
anyone,
who's
doing
the
meaning
themselves,
have
you
owned,
or
you
start
the
meeting
and
own
a
Zune
link.
You
can
set
it
up
to
do
the
live
streaming
or
just
I
mean
to
upload
a
recording
which
saves
you
a
lot
of
time
and
effort,
and
you
don't
have
to
go
hunting
down
someone
to
say.
B
Could
you
get
that
recording
of
that
meeting,
because
I've
been
doing
a
lot
of
policing
people
for
posting
or
sharing
meeting
recordings?
So
this
is
just
a
friendly
reminder
and
everyone,
this
isn't
just
for
the
staff
meeting-
or
you
know
individual
meetings
but
in
general
to
benefit
the
rest
of
the
team,
try
and
make
that
your
standard
practice
yeah.
A
Cool
I
definitely
agree
and
I'd
say:
ISM
I
went
through
all
the
unfiltered
videos.
I
just
searched
for
the
word,
defend
and
added
them
to
the
defend.
Playlist
very
few
were
in
there.
Some
of
them,
probably
don't
belong
exactly
they're
from
a
long
time
ago,
but
it's
still
it
it's.
When
secure
independent
combined
it
some
of
them.
You
know
going
back
a
long
long
time
ago,
but
we
can
edit
it.
But
you
know:
there's
now
good
lists
out
there
and
it's
been
added
to
our
team
page.
The
people
can
easily
find
it.
A
It
was
last
week's
video
posted
it
to
unfilter,
I.
Think
Philippe.
You
did
that
you
initiated
the
recording.
That
doesn't
mean
this
early.
You
need
to
post
it
unfiltered,
but
how
do
we
better?
We
just
make
sure
it
gets
posted.
How
do
we
make
sure?
First
last
week's
meeting
gets
posted.
Who
can
do
that.
B
B
B
A
All
right
so
working
to
get
all
the
M.
Our
stats
and
number
three
here
we're
gonna,
get
all
the
merge
request.
Statistics
correct
for
the
defend
team
and
I
updated
a
couple
different
things:
I
updated
the
query
that
pulls
in
which
people
are
on
the
team.
That's
actually
a
sequel,
query
and
periscope
and
done
some
other
research
and
the
defend
project,
watch
I,
guess
I'm
getting
ahead
of
myself.
A
So
the
first
thing
is:
we
want
to
make
sure
we
have
the
right
tags
on
the
mrs,
so
they're
listed
far
key,
which
is
not
not
a
hard
and
fast
rule.
Some
things
or
a
judgment
call
so
everybody's
went
back
and
confirmed
about
the
tags
that
they've
done
that,
except
for
Lukas,
Phillipe
and
Daniel.
So
if
I
don't
think,
Lukas,
Lukas
and
Daniel
are
not
on
so.
A
Look
at
that
and
Thomas
and
Lindsey
nudge,
Lukas
and
Daniel
on
that
no
rush
on
that.
But
if
you
could
do
that,
you
know
today
I
do
that
today,
tomorrow
or
this
week,
that'd
be
great.
You
know
and
thanks
you
for
everybody
else.
The
only
guys
we're
almost
at
the
end
of
the
month,
I
saw
a
message
from
my
boss,
Christopher
earlier
today
saying
we're
almost
over
the
number
on
the
most
M
ours
ever
at
gitlab
in
a
month
across
the
whole
company.
So
the
more
we
get
the
tags
right
and
other
things
right.
C
A
C
B
To
the
link
to
Philippe's
point
as
long
as
we
have
resources
who
aren't
dedicated
to
defend
these
metrics
aren't
going
to
have
the
same
meaning
that
we'd
like
them
to
have
right.
Cuz,
you're
gonna
have
one
person
who's,
putting
time
towards
defend
as
well
as
secure
in
other
areas.
So
you
say:
you've
got
em
ours
per
person,
but
you're
only
showing
affection
of
that.
So
I
feel
like
we're
starting
to
understand
these
metrics
and
get
them
correct
so
that,
as
the
team
grows,
that
trend
becomes
something
we
can
rely
on
right
now.
A
Agreed
which
goes
into
the
second
topic
here,
related
one
nexor
so
which
projects
should
be
part
of
defend
metrics,
so
I've
got
an
M
R
that
is
waiting
on
approval.
The
defend
project
is
not
included
yet
at
all
in
the
EMR
metrics.
It's
so
I've
got
a
merge
request
in
there
to
add
that
working
with
the
data
team,
they
have
a
CSV
file
where
they
list
what
projects
are
quote
unquote.
Part
of
the
project
like
the
handbook
is
not
part
of
the
project.
A
C
A
Yeah,
that's
good
that,
in
my
opinion,
just
my
first
minute
for
sure
our
demo
project
should
be
included,
for
example,
where
we're
showing
customers
how
to
enable
cilium
and
how
to
use
it,
how
to
unable
to
laugh
and
how
to
use
it
all
right.
That's
probably
you
know
one
on
the
fence
thing,
though,
if
those
should
be
included
or
not
so,
ok,.
A
So
the
only
our
cilium,
mr,
are
changes
to
psyllium
itself:
the
open
source
project
we've
got
the
mrs
in
thanks,
Lucas
and
Arthur,
and
Philippe
in
and
others
that
work
on
that.
Getting
that
in
there
as
a
way
to
track
those
they're
not
merged
yet
I,
don't
know.
Is
it
yet
or
if
there's
no
there's
no
nod
today,
I,
don't
think
so
to
focus
today,
yeah
did
you
say
you
can
merge
them
really.
A
C
Whatever
project
it
is,
and
we
would
labor
every
single
of
this
Nadja
quest
with
the
specific
labor
so
that
we
can
track
that
in
add
the
metric
in
the
end,
so
that
we
can
put
that
somewhere
and
the
GC
or
and
I
don't
know,
okay
chuckling.
So
we
need
to
add
this
laid
back
and
I
was
waiting
for
the
guests.
You
answer
that's
efficient
through
tomorrow.
I
can
create
a
global
today
if
you
want
or
or
wait
forecast
I.
A
B
So
there's
been
a
lot
of
conversation
going
on
about
ways
to
improve
our
predictability:
ways
to
be
able
to
have
better
insurance
that
when
we
believe
that
we
have
our
scope
of
a
release
that
we
can
hit
that
goal,
so
you
know
for
Cindy
who's
on
the
call
for
pmm
who's
marketing.
What
we
have
upcoming
in
our
roadmap.
We
want
to
be
able
to
be
as
accurate
as
possible,
so
she's
not
becoming
a
liar.
You
like
Cindy,
no
I,
don't
make
her
a
liar.
B
The
secured
team
started
a
document
that
I
kind
of
hijacked
when
we
try
to
give
them
credit
where
credit's,
due
so
Olivier
and
Thomas
and
folks
women,
secure
team,
started
an
analysis
of
their
planning
process
in
areas
of
improvement
and
I
agree.
So
all
heartedly,
with
their
first
step
that
I
plagiarize
it
completely
and
I
made
this
document.
The
idea,
being
first
of
all,
I,
went
and
looked
at
what
our
process
was,
and
you
can
just
review
the
document
yourself
in
your
own
time.
B
I'm
not
asking
anyone
to
start
this
process
today,
I'm
just
trying
to
explain
the
thought
behind
it
and
see
if
everyone
is
on
board
or
has
feedback
after
looking
at
our
process,
one
area
that
I,
really,
we
really
thought
that
we
could
improve
at,
is
helping
the
p.m.
team
and
earlier
phases
of
planning,
as
they
start
to
break
down
their
ideas
into
issues.
So
by
having
engineering
participating
and
the
work
breakdown,
planning
I
think
it
solves
a
lot
of
problems.
B
It
gives
the
engineering
team
more
insight
into
what
Pam
is
thinking
as
they
start
to
groom
stories
they're,
not
just
looking
at
them
cold.
It
gives
the
p.m.
team
sort
of
better
advice
on
how
to
better
break
down
stories
into
logical,
smaller
sub
issues,
and
it
also
will
just
ask
these
kind
of
big
hairy
questions
earlier,
so
we're
not
waiting
until
like
the
week
or
right
before
execution.
That's
supposed
to
be
given
a
milestone
that
we've
committed
to
the
scope
of
the
milestone.
So
we
talked
earlier
about
having
group
wide
meetings.
B
The
hope
is
that
a
portion
of
those
group
wide
meetings
can
be
dedicated
to
this
planning
breakdown.
Where,
as
a
team,
we
can
go
through
the
upcoming
issues
in
the
next
milestone
and
ask
these
questions
and
it's
committed
here
in
this
in
this
page
I,
don't
need
to
go
through
for
you
guys
over
time.
The
hope
would
be
that
we
don't
have
as
much
of
a
backlog
of
these
issues
to
break
down
and
it's
more
on
a
as
they're
created
basis
and
we've
kind
of
we're
just
doing
housekeeping
right
now.
B
You
know
12
HRT
in
flight.
We're
not
gonna,
make
a
lot
of
changes
there,
because
we
know
that
folks
have
already
started
working
on
things.
Hopefully,
if
there's
something,
that's
not
clear.
You've
already
raised
that
to
the
appropriate
p.m.
or
you're
in,
but
for
12
nine.
We
would
like
to
try
this
process
on
and
see
if
it
if
it
helps
people
or
if.
B
A
B
Exactly
right,
Wayne
I
took
the
two
links
that
you
can
see
here.
The
product-moment
workflow
tower
defend
panic,
planing
pages
to
try
and
kind
of
summarize
how
those
two
things
create
a
schedule
for
us,
so
I
guess,
as
you
review
this
document
of
any
of
that
seems
totally
wrong.
Let
me
know
because
I
might
have
misinterpreted
something.
A
B
Starting
the
conversation
earlier
and
including
engine
other
thing
that
I
one
of
the
things
that
I
I
was
uncomfortable
with
the
fact
that
we
assign
off
grooming
to
individuals
and
that
those
individuals
are
not
necessarily
the
people
that
end
up
working
on
the
issues.
So
you
might
end
up
getting
even
an
issue
aside
to
yourself.
You've
never
seen
before
I'd
like
to
avoid
that
at
least
give
people.
Some
insight,
start
the
conversation
or
likely
raise
red
flags.
A
A
B
That's
something
that
needs
to
be
set
up,
and
we
talked
earlier
in
this
call
about
how
we
currently
have
this
first
class
vulnerabilities
weekly
meeting
that
wasn't
intended
to
be
a
feature
meeting.
It
wasn't
intended
to
be
a
ongoing
group
level.
Meeting
like
Matt
said
it
has
an
end
date.
What
we're
proposing
is
introducing
these
meetings.
What
I
wasn't
sure
of
is
given
the
size
of
the
team
and
the
scope
of
our
groups
right
now.
B
Does
it
make
sense
to
have
two
meetings
or
one
we
talked
earlier
about
having
two
I
know
as
the
team
grows,
and
these
groups
become
more
solidified.
It
definitely
makes
sense
to,
but
you
know
that's
up
for
discussion
whether
we
split
the
two
groups
right
now
or
sort
of
have
another
stage
right,
immediate
least
initially,
for
this.
F
So
I
mean
I,
know
I
put
that
week.
We
think
meeting
for
product
management
and
the
engineering
managers
on
the
calendar.
I
don't
know
that
that's
necessarily
the
best
place
to
do
all
of
grooming,
but
I
at
least
envisioned
some
of
those
initial
discussions
that
you're
talking
about
happening
as
part
of
that
meeting.
B
B
G
Think
any
any
issues
going
forward
or
more
gonna
be
along
the
lines
of
individual.
You
know
Goethe
groups
and
projects.
So
as
far
as
my
thoughts
is
yeah,
I
think
I
think
we
can
go
ahead
and
cancel
that
and
have
you
know,
ad
hoc
sync
ups
as
necessary,
but
you
know
keeping
things
in
this
light.
Channel
also
works.
E
Yep
I'll
concur
and
confirm
yeah.
The
original
intent
of
this
is
we
had
so
many
people
having
the
same
problems
on
development
environment,
set
up
instance
that
we're
all
happening
at
the
same
time
let's
get
together
and
support
each
other,
we're
past
that
problem
now.
So,
let's
I
think
you'd
agree
it's
time
to
cancel
it.
So
if
engineers
are
ready,
we
can
do
so
and.
G
I
think
one
of
the
other
things
that
we
had
set
it
up
for
was
kind
of
a
coffee
chat,
type
thing
like
slash
thing,
but
we
also
have
the
secure
and
defend
coffee
chat
at
8:30
on
Monday
837
a
three
month,
Central
Time
on
Monday
morning,
which
I
don't
know.
If
you
know
this
is
kind
of
like
a
tangent
but
I
don't
know
it's
a
lot
of
our
team
really
can
make
that
because
I
know
we
cut.
We
have
Zamir
and
and
Daniel
out
west
further
Arthur's
asleep
at
that.
I'm
he's
asleep.
A
G
A
G
G
E
So
what
I
would
like
to
do
is
okay,
so
it
sounds
like
there's
consensus
that
there's
consensus,
we've
outgrown
office
hours,
we
can
cancel
the
series
and
what
I
would
like
to
do
is
claim
that
time
next
Monday
for
a
different
conversation,
so
pod
logs
Vantage
applications
in
the
pod
logs
is
something
that
we're
currently
blocked
on.
There's
a
question:
if
is
there
anything
we
can
do
in
an
interim
basis
that
would
unblock
that
particular
feature
and
there's
like
to
claim
that
time
for
a
brainstorming
session.
E
It's
it's
time
reserved
on
the
calendar
already.
So,
let's
wine,
why
not
take
advantage
of
it?
The
item
that
is
not
written
here,
because
it's
late-breaking
edition,
so
in
other
words,
so
this
is
breaking
news
so
from
our
live
field
reporter
out
in
security
named
intentional,
is
that
they
are
working
on
it.
They
have
been
working
on
a
project
by
the
name,
adèle
key
that
involves
ingesting
logs
from
production,
various
different
production
environments
and
into
an
elastic
search
cluster,
and
so
they
have.
E
They
have
volunteered
to
demo
the
work
that
they
have
done
and
maybe
that
might
spur
some
thoughts
or
it
might
provide
us
a
launching
point
for
this
type
of
feature.
So
it's
a
so
anyway
they're
volunteering
to
come
and
show
their
work
as
well
and
also
participate
in
our
brainstorming
sessions
with
their
with
their
experience.
E
What's
the
perfect
code
in
terms
o
ki
te
lke
part
of
the
invite
will
be
a
link
to
their
readme,
as
well
as
their
issue
board.
So
we
can
see
the
work
they've
been
doing
as
well
as
the
work,
that's
on
their
current
roadmap
or
wealth,
their
issues,
they're,
chasing
and
and
what
Jason's
requested
and
I
agree
with
his
we'll
have
a
dedicated,
Google
Doc
for
an
agenda
where
people
can
post
specific
questions
in
advance
and
that
agenda
doc
will
include
links
to
those
two
resources.
A
Well,
can
you
put
a
link
to
their
stuff
in
the
notes,
I
put
a
line
item
in
their
charter,
but
yeah
if
you
put
a
link
so
deal
with
it
later
cool,
that's
great
and
I
another
thing
on
the
item,
but
we're
out
of
time,
and
it
wasn't
high
priority
to
it
in
saver
for
next
week
and
Phillipe.
Remember
you
got
the
job
of
posting
last
week's
in
this
week's
meeting
to
the
YouTube
soo
awesome.