►
From YouTube: Threat Management Staff Meeting Aug 25, 2020
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
Sorry
I'll
grab
the
first
one
and
then
look
for
a
volunteer
to
read
number
two,
so
very
happy
for
zamir
and
alan
yay
on
discretionary
bonuses,
samir
for
the
work
on
the
container
security
demo
setup
and
azure,
which
we
don't
officially
support
yet
and
also
alan
for
your
contributions
on
front-end
issues.
At
the
time
when
we
were
overloading
this
area
so
really
really
appreciate
it.
A
C
So
it's
from
thiago
again
he's
not
present.
He
says
we
have.
We
have
our
first
backhand
contributor
finish
at
fred
inside
issue
and
then
the
issue
is
linked
in
the
announcement.
A
Yeah,
we've
really
seen
a
lot
of
an
uptick
in
community
contributors
for
stuff
we're
working
on,
which
is
great.
I
think,
six
months
ago
we
had
zero,
and
now
we
have,
I
think,
four
something
like
that.
Five.
A
Five,
that's
great
lindsay.
You
got
number
three.
B
And
on
that
note,
I
want
to
give
a
big
applause
to
alexander
for
a
discretionary
bonus
around
collaboration,
which
is
also
centered
around
helping
with
various
community
contributors,
both
testing
a
really
complicated
authentication
flow,
with
another
engineer
and
being
the
buddy
for
one
of
our,
I
think,
maybe
our
our
third
community
contributor,
I
think
you've
actually
helped
a
couple
now
since
then
so
yay,
alexander.
B
D
Yes-
and
this
is
very
exciting
news-
there's
a
new,
easier
way
to
nominate
someone
for
discretionary
bonuses
in
slack,
simply
type
in
forward
slash,
nominate
and
the
person's
name,
and
it
will
nominate
them
so
anytime,
you
see
someone
going
above
and
beyond.
Please
give
them
a
shout
out.
B
E
I
have
to
find
my
meet
button.
First
planning
improvement
do
not
rely
on
engineering
managers
for
refinement
engineers
assign
the
issues
to
another
team
member
to
plus
one.
The
refinement
before
moving
to
a
workflow
ready
for
development
should
streamline
the
workflow
a
little
bit.
B
So
this
is
an
effort
and
try
not
to
refine
in
a
silo
making
sure
that
everyone
agrees,
or
at
least
there's
some
amounts
of
agreement
on
the
refinement
before
we
move
forward.
So
thank
you.
Jonathan.
D
Okay,
jonathan,
I
think
you
get
to
pick
who
he
does
the
next
one.
F
Okay,
what's
happening
with
the
iteration
feature
in
gitlab,
that's
what
thiago
is
asking.
It
seems
like
we're
looking
to
release
more
often
an
example
iterate
quicker,
but
it's
related
to
this
new
feature.
According
to
the
to
the
confusion,
adding
to
the
confusion,
the
term
iteration
gitlab
has
historically
meant
milestone.
E
A
B
So
I
looked
into
this
a
tiny
bit
because
you
know
I
I
think
I've
mentioned
this
to
most
folks
on
the
team
that,
in
the
past,
I've
been
used
to
planning
for
much
more,
it's
much
shorter
sprint,
so
like
a
two-week
iteration
versus
a
month
long,
and
I
think
it
allows
people
to
break
a
milestone
from
a
month
down
into
whether
it
be
two
two
week
iterations
or
four
one
week
iterations
and
have
ways
to
sort
of
bucket
and
track
issues.
In
that
sense
you
know-
and
I've
brought
this
up
in
the
past.
B
The
challenge
becomes
how
we
support
things
like
release
posts
and
release
announcements,
since
everything
does
still
revolve
around
that
month-long
milestone.
But
I
think
this
is
a
way
to
support
other
groups
as
well,
who
are
interested
in
having
smaller
breakdowns
than
just
a
release.
Milestone,
I
don't
know
matt,
do
you
have
any
thoughts
on
that?
Have
you
looked
into
this
from
a
pm
perspective
or
have
any
additional
insights.
H
It
confused
me
as
well.
It
seems
like
it's
a
kind
of
redundant
lightweight
version
of
milestones,
not
really
sure,
because
it
doesn't
look
like
it's
on
an
epic
either.
I
thought
maybe
it
would
be
a
cool
way
to
group
ethics
and
issues
together,
but
yeah
it
just
if
anybody
looks
at
the
feature,
it's
pretty
much.
You
get
to
set
a
date
range
and
then
you
can
tag
or
whatever
you
want
to
call
it
on
the
issue.
H
I
I
don't
the
only
thought
I
have,
and
I
think
I
share
this
with
wayne
last
week
when
we
synced
up
that
the
company
or
specifically
sid,
has
talked
about
moving
us
to
releasing
bi-weekly,
and
I
wasn't
sure
if
this
was
like
the
step
towards
that.
But
again,
like
your
comment
about
milestones
like
you
would
just
make
the
milestone
two
weeks
and
you
wouldn't
need
the
iteration
then
so
I'm
not
100
sure
how
it
all
ties
together.
I
I
B
H
H
The
iterations
give
you
the
flexibility
to
do
that,
but
to
your
point,
like
gitlab's
not
set
up
that
way,
we're
all
working
in
the
same
one
month
milestone.
So
I
think
it's
an
interesting
feature
for
other
orgs
that
are
set
up
a
little
bit
differently,
but
unless
we
get
rid
of
the
milestones
the
way
they
are
now,
I
don't
think
there's
a
whole
lot.
We
can
do.
I
With
them
and
you
kind
of
hit
on
something,
though
that
might
add
value,
if
we
really
wanted
to
do
this
way,
you
could
have
two
iterations
per
milestone,
saying
that
new
development
wraps
up
in
that
first
two
weeks
and
then
the
next
two
weeks,
where
bug
fixing
or
whatever
comes
up
either
with
the
new
features
or
critical
bugs
that
have
come
in.
I
So
it
is
a
way
to
kind
of
stagger
that
and
make
it
a
little
bit
more
explicit,
whereas
today
I
feel
like
we're
not
always
explicit,
I
know
there's
a
cut
off
when
everything
has
to
be
through
the
maintainers,
but
there's
times
where
I
feel
like
someone's
like
calling
up
a
maintainer
being
like.
Can
you
pretty
please
look
at
this
right
now
right,
so
it
kind
of
forces
it
a
little
bit
to
be
a
little
bit
more
rigid.
B
I
I
am
I'm
an
amazing
slide
maker.
I
just
I
five
one
skill,
that's
what
I
need
to
advertise.
A
There
you
go
cool
glad
thiago
brought
this
up
good
discussion
on
this
one.
So
the
commit
conference
is
this
week,
wednesday,
thursday,
if
you
haven't
registered,
suggest
you
do
check
out
the
agenda
to
see
if
you
want
to
attend.
A
You
know,
as
we've
talked
about
a
couple
of
times,
there's
a
talk
by
by
philippe
and
I
and
a
user
nico
that
is
the
14th
most
registered
for
talk.
Currently,
it's
kind
of
neat
nico
actually
somehow
found
that
statistic,
and
thanks
again
to
samir
for
getting
the
environment
working
and
david
you're
doing
a
talk
as
well.
Is
that
right.
I
A
So
it's
free,
encourage
your
friends
and
contacts
and
to
attend,
if
they're
interested
and
do
so
yourself
as
well.
It's
all
recorded
sessions
but
broadcast
at
a
certain
time,
and
then
you
can
ask
the
presenters
via
chat,
to
discuss.
There's
also,
we
have
an
open
house
that
a
number
of
us
are
sitting
in.
Basically,
as
many
users
have,
any
questions
will
be
available
and
the
the
recordings
will
be
available
for
playing
after
the
fact
I
think
not
like
next
week,
but
sometime
in
the
future.
A
So
if
you
can't
make
it,
you
know,
feel
free
to
look
for
the
recordings
as
well
for
the
things
you're
interested
in.
G
B
G
Sure
so
the
first
trade
management
community
of
sea
hours
is
going
to
happen
this
friday
and
there
is
a
link
on
the
how
to
add
that
on
the
google
calendar.
A
B
We
don't
have
it
scheduled,
yet
we
will
be
scheduling
it
at
america.
Friendly
time,
though,.