►
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
welcome
to
our
container
security
group
meeting
just
to
kick
it
off
alexander.
I
think
you've
got
the
first
one.
B
Yes,
I
was
just
mentioning
that
the
mr
to
turn
the
feature
flag
on
by
default
is
up
for
review
and
I
had
some
concern
that
if
it
didn't
get
merged
today
we
might
not
make
13.9,
but
then
I
just
opened
it
and
it
is
merged.
A
Excellent
yeah,
that's
great!
Congratulations!
Everyone!
I
know
that
has
been
this
whole
alerts.
One
has
been
a
really
big
one
to
tackle
it's,
not
one.
We
could
handle
easily
in
a
highly
iterative
way.
So
it's
been
a
number
of
releases,
but
congratulations,
I'm
really
excited
with
where
we're
at
and
that
we're
able
to
get
this
one
out.
A
It's
going
to
be
a
huge,
huge
value
to
users,
and
it's
something
that
I
know
right
now
we're
starting
with
just
network
policies,
but
eventually
that
alert
dashboard
is
going
to
be
used
for
a
lot
of
other
things
as
well,
including
our
scanning.
You
know
any
kind
of
scanning
things
that
we
want
to
have
generate
alerts
or
even
like
get
lab.
You
know
access
type
alerts
inside
our
thread
alerts
like
hey
someone
logged
in
from
clear
across
the
world
when
they
logged
in
from
you
know
their
their
normal
country
five
minutes
ago.
A
That's
really
odd
right.
So
there
are
a
lot
of
security
alerts
that
we
can
have
in
get
lab
and
I
think
we're
just
you
know,
starting
scratching
the
surface
at
the
types
that
we're
going
to
have
show
up
there
in
the
future.
B
Yeah,
so
I
have
been
working
with
the
operations
team
to
reuse
their
alert
details
page.
As
all
of
you
know,
the
operations
has
an
alert
list
just
like
similar
to
us
and
when
you
click
on
the
alert
it
takes
you
to
this
detail
page.
My
browser
just
signed
me
out,
so
I
can't
walk
us
through
that
exactly,
but
we
I
was
able
to
reuse
most
of
their
code
and
generalize
it
and
work
to
get
that
to
work
for
our
alerts
as
well.
B
So
now,
if
you
go
to
our
alert
list
and
you
click
on
the
title,
it'll
take
you
to
the
details
page
just
like
the
operations
details
page,
and
that
gives
us
not
only
a
url
for
the
user
to
share
with
other
users,
but
incidents
can
be
created,
alerts
can
be
assigned
now
and
they
can
be
added
to
the
to
do.
And
so
this
got
us
a
lot
of
bang
for
our
buck
and
I'm
very
excited.
It
was
able
to
happen.
A
Awesome
yeah!
Congratulations
on
that
as
well!
I'm
as
excited,
I
am
about
the
alerts
working.
I'm
equally
excited
about
all
the
the
ui
improvements
we
have
coming,
and
so
this
is
great
that
we're
able
to
get
this
one
in
in
39
as
well.
So
that's
that's
great.
A
B
It
was
just
a
minor
point:
there
was
some
issues.
This
would
have
gotten
us
the
status
change
on
this
page
as
well,
but
we
call
our
statuses
something
different
than
they
do
and
so
there's
a
little
bit
of
additional
work
needed
for
that,
but
it
will
be
coming
shortly.
Okay,
awesome.
B
It's
it's
a
lot
of
me
I
just
like
talking.
There
is
a
last
last
session.
We
talked
started
to
talk
about
the
end-to-end
test
for
this
feature
and
we
sort
of
ended
up
pushing
that
off,
because
not
that
many
people
looked
at
it.
So
here
it
is
again.
B
Setting
this
up,
you
know
saying
in
there
it
says,
set
up
alerts
and
that
is
sort
of
a
lot
a
little
bit
harder
than
one
may
think.
But
so
there's
gonna
be
some
like
difficulty
here,
but
I
think
we
can
do
it.
B
Breakdown,
I
can't
remember
what
the
questions
were
is
lindsay.
Can
you
help
me
out
with
this
or
the
three
refinement
or
playing
breakdown,
questions
yeah.
C
C
C
B
That's
a
great
question
hello.
I
will
we
should
ask
someone
about
that.
C
Maybe
even
code
that
we
could,
I
would
say,
leverage
but
reference
that
would
be
helpful
and
then,
if
we
were
ignoring
everything
else
that
we
were
taking
on
in
an
iteration.
Would
this
be
small
enough
to
complete
in
one
iteration.
B
Maybe
I
don't
know,
no
one
here
has
written
end
tests
before
so
we
don't
know
actually
how
difficult
it
is.
But
I
think
the
with
my
experience,
the
the
top
the
toughest
thing
about
and
then
the
time
is
setting
up
the
data,
and
you
know
there's
going
to
be
some
sort
of
like
automation
to
set
up
kubernetes
and
psyllium
and
stuff
like
that,
and
I
don't
know
how
difficult
that
is
going
to
be.
C
Vinci's
gonna
advise
she's
already,
given
us
a
lot
of
information.
If
we
get
sexually
answered
questions
but
she's
one
person
and
she's
a
manager
and
her
and
her
two
direct
reports
are
also
covering,
I
think
at
least
one
other
stage
of
the
product,
so
we're
working
on
getting
better
coverage
there.
But
right
now,
she's
just
there
to
unblock
us.
D
My
suggestion
is
that
there
is
an
integration
with
the
kubernetes
on
the
qa
side.
I
think
they
use
key
3d
for
that.
So
if
this
is
going
to
be
a
high
priority
task,
maybe
like
I
could
I
could
try
to
cover
the
p3d
part.
While
lexander
gets
together
with
the
monitor
team,
to
see
what
they
have
from
the
front
end,
and
then
we
would
be
able
to
have
like
a
kind
of
a
two-way
approach
for
them.
C
Samia,
could
you
add
a
comment
to
the
issue
saying
that
other
thing
to
call
it
is:
we
do
have
a
similar,
related
issue
around
load
testing.
I
know
that
end
in
testing
and
load
testing
are
different,
but
just
calling
it
out
that
we
do
also
want
to,
at
some
point
figure
out
how
to
load
test.
These
alerts
too.
D
For
load
testing
alerts,
the
monitor
team
has
squeezed
a
lot
of
resource
for
cass
and
agent
k.
They,
I
think
they
test,
like
5
000
agents
for
single
cast
or
things
like
this,
because
they
it's
a
requirement
for
them
to
be
able
to
run
that
on
gitlab.com.
D
So
I
think
which,
as
long
as
we
have
this
end-to-end
test
for
our
feature,
detail
for
the
details
within
our
feature,
I
think
we
should
be
good
in
terms
of
load
testing.
Otherwise
we
would
be
doing
the
same
thing
with
them
and
then
I
don't
know
how
that
would
be
in
terms
of
the
resource
for
the
other
tasks.
A
C
That
makes
sense
well,
it
sounds
like
based
on
this
conversation
we're
going
to
move
the
end-to-end
testing
issue
into
scheduling,
and
I
think
it
sounds
like
alexander
and
zamir
are
gonna,
be
the
lucky
owners
of
getting
this.
A
All
right
so
yeah,
I
think
we
can
probably
move
that
one
to
refinement
and
move
forward
with
it
thiago's
not
here,
but
this
create
ruby
based
container
scanning
tool
based
on
trivi.
So
the
question
here
would
be
the
same
thing
right
planning
breakdown
is
this:
is
this
ready
to
move
into
refinement?
Do
we
understand
the
requirements
here?
A
Are
there
you
know?
Is
it
small
enough,
and
I
don't
remember
the
last
question:
do
we
know
the
dependency
of
the
seas
of
the
work
to
be
accomplished?
We've
gone
through
a
lot
of
spikes
already,
so
I
think
we're
in
a
pretty
good
place,
but
I
wanted
to
open
it
up
to
the
team.
How
are
you
feeling
about
the
moving
this
one
to
refinement.
D
I
I
have
been
stuck
in
a
couple
of
things
for
alerts,
so
I
haven't
had
time
yet
to
dig
deeper
on
the
container
scanning.
So
that's
on
me,
but
I'm
not
sure
about
other
guys.
A
So
from
what
I've
seen
it,
it's
spelled
out
pretty
well,
I
know
adam
did
a
pretty
heavy
research
spike
in
figuring
out
what
needed
to
be
done,
and
so
I
think,
we're
in
a
good
place,
but
maybe
zamir
will
give
you
a
chance
to
look
over
it
before
we
officially
move
it
to
refinement.
D
Yeah,
and
can
I
ask
a
question
related
to
this,
what
would
be
the
priority
between
the
end-to-end
test
and
this.
A
A
A
All
right
so
this
next
one
we've
made
a
lot
of
changes,
obviously
to
the
project
level.
Dast
scan
execution
policies,
epic
we've
not
really
had
a
chance
to
talk
through
all
of
that
synchronously,
but
I
wanted
to
just
you
know
open
that
up
for
discussion.
I
know
there's
been
a
lot
of
asynchronous
discussion
on
this
topic
specifically
for
today
I
wanted
to
present
just
the
first
epic.
A
I
actually
should
say
epic,
not
issue
that
I
believe,
is
ready
for
planning
breakdown,
which
is
just
the
mvc
of
moving
things
into
support
for
pipeline
policies
for
dast.
I
think
there
is
one
outstanding
question
in
this.
Let
me
share
my
screen.
A
A
A
big
part
of
this
is
allowing
an
application
security
analyst
to
enforce
the
das
scans
to
be
run
according
to
the
configuration
that
they
want
it
to
run
in.
So
if
it's
linking
to
as
to
scan
profile
or
a
site
profile
that
can
then
be
edited
by
by
any
developer.
A
You
know
that
doesn't
meet
that
requirement
there.
So
we
also
need
to
make
sure
that
users
will
not
be
able
to
edit
or
delete
any
scan
profiles
or
site
profiles
as
long
as
they're
referenced
by
an
active
policy,
it's
probably
not
the
greatest
solution,
but
it
is
going
to
be
the
most
iterative
solution,
and
so
for
that
one
we
do
have
an
open
question.
A
A
Then
everything
down
here
is
in
a
disabled
state
where
you're
not
able
to
edit
it
an
alternative
to
this
mock.
Basically,
the
second
option
here
is
just
to
make
it
a
little
bit
simpler,
where,
instead
of
naming
the
exact
policies
that
are
using
it,
we
just
show
a
generic
message.
It
says
this
profile
is
being
used
by
a
policy,
so
annabelle
wasn't
sure
how
much
work
it
would
be
to
get
the
names
of
those
policies
included
in
here.
A
A
Otherwise
I
believe
we
have
most
of
this
worked
out
and
we're
ready
to
move
it
to
refinement.
Although
john,
I
see,
you've
got
some
concerns
here
that
you've
raised.
If
you
want
to
go
ahead
and
voice
those
over.
F
Yeah,
I
just
want
to
voice
my
concert,
you
know
it's
just
my
opinion
and
you
know.
Maybe
other
developers
thinks
different,
but
I
see
like
you
know
like
we
will
have
some
unplanned
work
coming
ahead
of
us
from
a
point
of
view
and
like
forces,
we
couldn't
finalize
our
approach
with
the
ci
team.
You
know
we
had
a
lot
of
change.
We
were
talking
about
schedules
first,
then
we
realized
us
isn't
doing
the
same.
F
Then
we
changed
to
the
other
thing
and
now
that
we
also
had
some
discussions
with
the
compliance
team
approach,
and
so
that
thing
there
could
be
a
lot
of
on
unseen
problems
on
there.
You
know
the
ux
design
front-end
didn't
check
ux
from
if
they
checked
you
know
they
can.
Let
me
know
that
we
don't
have
front-end
issues
on
that
and
ux
like
forces
to
be
dropping
down
and
you're
choosing
a
project,
and
today
alan
also
raised
some
things.
F
A
F
Yeah,
okay,
so
then
we
will
have
a
warning
and
so
little
this
kind
of
thing.
No.
A
F
There
are
no
policies.
Okay,
it's
good
to
know,
you
know
and
maybe
like
what
you
know
we
you
know
we,
the
pm
from
compliance
team
was
on
the
leave
and
he
came
back
and
but
we
haven't
discussed,
you
know
what
could
be
if
we
could
some
do
something
together,
you
know
and
so
those
kind
of
things
I'm
concerned,
you
know
that
we
will
have
achieve
what
we
want
to
achieve
in
these
milestones
and
I'm
just
raising
my
concern.
A
Yeah,
so
I
think
some
of
this
is
done
during
refinement
like
the
front
end
issues,
there
are
no
front
end
issues
yet
because
those
are
normally
created
during
the
refinement
process
and
as
far
as
the
approach
that
you're
taking
with
the
ci
team
again,
I
I
don't
know
if
that
would
be.
A
C
F
Yeah,
so
I
like
ellen,
had
some
mrs.
You
know
that
we
said
that
we're
gonna
send
it
to
ci
team
for
review,
but
you
never
know
what
will
come
back
from
that
review.
You
know
it
would
be.
It's
great
go
ahead
and
you
know
it's
like.
Oh,
this
approach
is
completely
wrong,
so
I
just
want
to
point
out,
like
you
know,
if
you
want
to,
we
are
planning
for
everything
to
be
done
in
this
milestone.
F
You
know
it
could
not
be
the
case
because
of
this
of
you
know,
changes
and
unforeseen
things,
and
we
also,
you
know,
touching
a
very
important
part
of
gitlab.
So
you
know
this
one
raised
that.
A
E
Yeah,
okay,
so
yeah.
What
we!
What
we
want
to
have
is
quick
feedback
loop
like
it
either
from
ci
team
or
from
the
customers.
So
that's
why
we
started
working
on
this
one,
even
though,
like
not,
everything
was
polished
and
not
everything
was
clarified
in
terms
of
requirements
and
so
on.
So
we
already
have
something
already.
E
I
I
believe,
like
30
of
the
work
is
merged
right
now
and
now
we're
working
towards
like
another
step,
and
we
agreed
with
the
ci
team
that
as
soon
as
we'll
have
something
for
them
to
to
show
and
ready
to
be
immersed.
We
should
just
ask
them
for
review
and
so
on.
I
believe
for
them
we
see
especially
that
we're
behind
the
feature
flag
and
so
on,
like
even
though
our
approach
might
not
be
like
the
best
one.
I
believe
they
will
agree
and
then
we'll
just
enhance
that
in
the
like
next
milestones.
E
E
I'm
not
worried
about
that
because
I
truly
believe,
like
we
have
two
approaches
ready
like
we
need
to
choose,
which
one
we're
going
to
take
the
one
thing
I
have
back
to
to
our
questions
from
the
planning
breakdown
back
to
the
mock
that
was
prepared
by
ux
team.
We
have
either
either
simpler
approach.
I
believe
that
could
fit
for
our
mvc
better.
E
Instead
of
showing
the
warning
that
oh,
this
profile
is
already
used
by
someone
in
active
policy.
We
could
just
respond
with
our
message.
E
I
know
that's
not
really
a
super
like
convenient
from
the
ux
point
of
view,
because,
oh
you
modify
something,
then
you
click
save,
and
then
you
see
that
oh,
you
cannot
modify
it
because
it
is
already
assigned
to
different
to
different
thing
and
different
policy,
but
that
will
be
the
simplest
approach
like
we
can
have
that
really
quickly,
like
in
terms
of
warning
and
rendering
that
and
preparing
all
the
things
for
the
front,
and
that
might
be
a
little
take
a
little
bit
longer.
E
So
if
you
want
to
find
the
easiest
path,
I
would
go
with
this
one.
A
A
Normally
once
we
move
it
from
planning
breakdown
to
refinement.
That's
when
it
goes
to
you
to
refine
and
create
all
of
the
issues
for
implementation,
and
then
we
start
doing
the
development
work
right
so
we're.
I
think
we
may
have
skipped
some
steps
earlier
on
or
or
maybe
alan's
just
coded
things
really
fast,
but
in
any
case
like
right
now
we're
just
trying
to
make
sure
that
the
requirements
are
clear
and
that
we
don't
have
any
outstanding
concerns
about
what
we're
doing.
F
Okay,
also
ellen,
you
said
30
percent
right,
not
90
percent,.
F
E
Just
just
to
clarify
the
text
there.
F
C
So
if
the
big
dependency
around
the
ci
team
is
handled
to
a
degree
because
they're
aware
that
we're
making
these
changes,
we've
already
got
a
connection
with
people
on
this
on
the
team.
Who
can
give
us
that
quick
turnaround?
I
guess
the
only
one.
The
only
question
that's
still
sort
of
unclear
to
me
is:
does
everybody
understand
the
requirements?
I
think
that's
the
main
question.
C
F
F
C
Punish
alan
for
wanting
to
move
quickly
get
something
out
there
to
be
seen,
but
it
does
sort
of
change
our
process
a
little
bit.
So
I'm
not
sure
what
to
say
about
that
alan.
Do
you
want
to
talk
about
how
far
you've
coded
this
you
know
how
this
relates
to
our
refinement
and
planning
breakdown,
your
thoughts
on
how
we
should
move
forward
in
our
existing
planning
process,
given
the
progress
that
you've
made
already.
E
So
we
with
such
big
changes
and
big
epics
that
touches
many
parts
of
gitlab.
I
believe
the
best
approach
is
to
first
try
to
code
things,
even
though,
like
it's
not
fully
working
like
happy
path,
because
otherwise
we
are
really
not
sure
how
to
develop
other,
like
think
how
to
split
it
into
implementation
issues
and
so
on.
So
that's
why
I
first
started
with
some
embassy
with
being
able
to
do
something,
because
I
was
not
aware
like
how
I
can
you
know
work
on
things.
That
is.
That
is
why
I
did
that.
E
Maybe
we
could
think
about
the
improvement
to
the
process.
If
we're
talking
like
talking
about
big,
epics
and
big
things,
that
we
are
unsure
about
like
the
code
base,
because
we're
we're
not
doing
like
something
that
we
used
to
do
because
that's
something
new,
maybe
we
should
spend
like
one
milestone
just
to
try
to
code
it,
even
even
though
it's
not
perfect
just
to
get
some
answers
from
from
other
teams
and
from
the
from
the
code
itself
as
well.
So
that
that's?
E
Why
that's
why
the
process
looked
a
little
bit
different,
because
I
had
to
get
those
answers
first
and
from
from
the
code,
and
now
that
I
know
already
what
I
know
I
can
move
on
with
implementation
issues
and
so
on
and
and
yeah.
It
looks
like
the
work
is
done
and
then
like
we're
trying
to
adapt
those
issues
to
the
work
that
was
that
was
done,
yeah.
Sometimes
it's
the
best
approach,
in
my
opinion,.
A
C
And
we've
seen
this
pattern
a
few
times
recently
and
alan's
been
involved
in
a
lot
of
them
between
the
generic
report
schemas
and
the
issue
creation.
I
like
the
idea
of
addressing
this
in
our
process,
so
I'm
going
to
take
a
note
on
that
and
we
can
always
add
comments
in
the
retrospective
issue
and
we
can
look
at
adding
an
optional
research
spike
poc
to
the
early
phases
of
planning
breakdown,
refinement,
epic
creation,
yeah.
E
F
A
A
So,
john,
I
know
you've
had
a
lot
of
concern
about
the
overlap
with
the
compliance
team,
and
there
definitely
is
some
overlap
here,
especially
with
the
mvc.
You
know
I
keep
asking.
Please
give
me
at
least
until
today.
Actually
our
product
manager,
there
is
having
blackouts
because
of
the
snow
in
in
texas,
so
it
might
actually
be
tomorrow,
but
give
me
a
chance
to
talk
with
him.
I've
talked
with
him
before
you
know,
so
this
is
not
a
new
conversation
for
us
we've.
A
Actually,
you
know
I
posted
the
video
of
when
we've
talked
about
it
before
we've
actually
talked
about
it
months
before
that,
as
well
and
much
more
depth.
It
just
wasn't
recorded
so
we'll
go
through
we'll
explore
it
in
more
depth.
I'm
going
to
keep
an
open
mind
and
see
if
there's
somehow
that
some
way
we
can
easily
combine
our
work
here,
but
you
know
I'll,
let
you
know
at
the
end
of
today
or
tomorrow
whenever
I'm
able
to
talk
with
him,
but
I
I
don't
think
that
things
will
change.
A
I
just
really
don't
we've
looked
at
it
in
the
past.
I
think
the
problems
that
we're
trying
to
solve
are
different
enough
and
the
the
people
that
we're
solving
them
for
are
different
enough.
That
I,
I
think
it's
going
to
be
hard
for
us
to
try
to
do
the
exact
same
thing,
but
but
maybe,
and
if
there
is
a
way
for
us
to
combine
our
work
on
the
front
end,
that's
great,
but
I
don't
expect
that
to
be
the
outcome
now.
A
That
being
said,
if
you
want
to
reuse
things
on
the
back
end
kind
of
like
what
we
did
with
monitor
is
a
great
example,
because
you
know
the
monitor
team
is
targeting
a
very
different
persona
from
us
right,
they're
talking
a
network
operations
center
that
keeps
the
cluster
up
and
running,
whereas
we're
targeting
a
security
user,
so
they're
two
very
different
people
very
different
jobs,
but
we
could
reuse
the
back
end
code.
If
there's
a
way
to
do
that
on
the
back
end,
then
you
know
that's
great,
I'm
very
supportive
of
that.
A
F
Yeah,
I
think
this
alert
was
like
a
good
example.
You
know
like
we
could
have
like
a
different
experience,
user
experience.
You
could
have
a
different
ui,
but
in
back
end
you
could
do
the
same
thing
so
like
what
I
was
thinking,
but
maybe
there
is
an
overlap
like
like
this
versus
you
create
a
a
security
compliance
thing
with
a
completely
different
workflow
from
user's
point
of
view,
with
the
complete
like
ui
at
the
back
end
is
just
a
compliance
policy,
but
you
don't
reflect
that
on
compliance
ui
as
well.
F
You
know
you
have
this,
you
know
and
they
we
at
that
back
end.
We
use
the
same
code.
You
know
so
yeah
that
kind
of
overlap,
because
a
lot
of
the
things
that
we
want
to
solve,
they
are
working
on
it
like
two
steps:
verification
inheritance
of
groups.
You
know
those
are
big
problems,
they're
already
working
on,
so
you
know
we.
F
A
Yeah,
please
do
look
for
those
overlaps
on
the
back
end,
I
mean,
I
think,
that's
separate
from
the
product
requirements.
You
know
that
that
responsibility
falls
on
you
as
engineers
to
make
sure
that
we're
not
you
know,
building
the
exact
same
thing
twice,
but
you
know
on
the
product
side,
I'm
I'm
worried
about
the
end
user
experience
and
what
they're
exposed
to
so
as
long
as
you're
able
to
meet
those
end
product
requirements
like
it's
up
to
you,
how
you
go
about
doing
that.
A
E
E
Why,
like
this
path,
would
be
even
though
we're
gonna
have
some
duplication,
just
do
just
two
separate
ways
and
at
some
point,
if
we
decide
oh,
we
should
reuse
that,
because
we're
duplicating
our
work,
then
we'll
spend
some
time
on
refactoring
that
well
maybe
one
milestone
like
we're
in
the
nbc
phase.
We
don't
know
what
really
will
be
the
feedback
from
the
end
users,
because
maybe
they'll
love
it
they'll,
maybe
they'll
say:
oh,
we
don't
need
like
fancy
ui.
I
love
the
yaml
file
creation
or
something
like
that.
E
B
Yeah-
and
I
was
gonna,
add
sam-
you
were
mentioning
about
the
the
work
of
like
seeing
what
other
teams
are
doing
on
the
engineering
side
and
bringing
into
what
we
can
use
is
falls
on
the
engineer,
and
I
don't
necessarily
agree
with
that,
but
I
also
don't
know
what
I
think
it
falls
on
the
team
as
a
whole,
because
you
know
us
as
engineers
we're
working
on
our
code
base.
B
We're
working
on
features,
we're
doing
our
thing
and
like
there
are
other,
are
other
channels,
we're
listening
to
we're
listening
to
the
development
front
and
back
end
whatever,
and
I
think
you
know
I
think
john
found
this
overlap
of
compliance
by
chance.
I
think
he
just
randomly
there's
an
opportunity
to
use
code
here.
I
think
with
the
and
so
it's
it's
hard
for
engineers.
There
is
no
good
way
right
now
for
any
of
us,
I
would
say
to
like
get
a
scope
of
everything
that's
going
on
in
the
in
get
lab
and
be
like.
B
Oh
we're
doing
something
similar
to
that
to
that
to
that,
and
so
I
think
it
falls
on
the
whole
team
if
you,
if
anyone
gets
a
whiff
by
probably
by
chance
of
like
oh
this
team's
doing
something
similar.
This
team
is
doing
something
similar
to
like
ping,
the
entire
team,
as
soon
as
you
find
out
about
it
in
the
channel
being
like
hey,
they're,
doing
something
similar,
and
then
that
alerts
everyone
puts
down
our
radars
and
whereas
it
might
not
have
been
originally
so.
A
That's
that's
fair
and
I
I
agree
with
that.
I
think
you
know
in
saying
that
it's
incumbent
on
the
engineers
I'm
referring
to
like
not
identifying
the
potential
overlaps
necessarily.
I
agree
with
you
that
that's
a
shared
team
responsibility,
but
then,
once
that
something
is
identified
right,
working
out
the
details
of,
are
we
going
to
share
code?
Are
we
not
going
to
share
code?
I
mean
that
falls
pretty
squarely
on
the
engineers.
A
You
know
just
it.
As
far
as
this
compliance
issue
goes
like.
I
was
aware
that
they
were
going
to
be
working
on
it.
I
actually
thought
it
was
going
to
be
quite
far
into
the
future,
so
I
think
matt
left
on
paternity
leave.
They
ended
up
working
on
it.
I
I
don't
know
the
exact
timing.
I
wasn't
under
the
impression
that
we
were
ahead
of
them
turns
out
they're
ahead
of
us,
so
I
was
not
trying
to
withhold
that
information
from
the
team.
I
just
thought
that
you
know
we
were.
A
B
Yeah
and
you
know-
and
you
alert
like
when
I
first
joined
this
team-
you
alerted
me
that
monitor
had
something
very
similar
and
I
I
definitely
agree
like
what
sharing
whether
we
can
share
a
code
falls
on
the
engineer,
and
you
know
it
didn't
work
out
for
the
list,
but
now
I
knew
they
have
this
thing
and
ended
up
working
out
for
the
details,
which
is
excellent,
and
so
thank
you
for
that
and
we'll
just
all
keep
an
eye
out
from
that.
One.
A
Okay,
so
with
those
clarifications
I
mean
granted,
there
is
a
chance
that
all
of
this
will
change
after
I
talk
with
matt
gonzalez,
but
assuming
for
the
moment
that
that's
unlikely
you
know,
do
we
feel
comfortable
moving
this
to
refinement
where
we
start
creating
issues,
implementation
issues
or
are
there
still
concerns
and
and
it's
okay
either
way,
I'm
just
you
know,
I.
I
want
to
kind
of
close
this
conversation
out
and
have
some
defense
definite
action
items.
If,
if
we're
not
comfortable,
we
need
to
identify,
you
know
what
needs
to
change
before.
E
Well,
I
can
tell
like,
from
from
my
point
of
view,
maybe
I'm
too
optimistic
with
all
of
that.
You
know
for
me,
like
we
already
have
something.
That's
working
I
mean
it's
like
happy
path
is
working.
We
need
to
work
on
some
details
with
jan.
We
already
have
the
connection
with
ci
team
john.
E
Did
the
great
work
like
talking
with
compliance
and
like
getting
to
know
where
we
can
overlap
in
terms
of
requirements,
everything's
clear
from
my
side,
if
there's
anything
like
where
every
single
day
we
we're
learning
something
new
about
that
so
you're
trying
to
ask
those
questions
in
the
issues
or
epics,
but
as
far
as
you
can
tell
like,
like
I'm
pretty
confu
like
confident
that
it's
all
clear.
F
Now
like
for
me,
is
you
know
what
we
need
to
do
is
clear,
but
I'm
just
pointing
out
there
could
be
a
lot
of
unforeseeable.
You
know
things
that
we
have
to
deal
with,
like
we
already
like.
You
know,
had
this
lot
of
change
during
the
refinement,
so
I'm
just
pointing
out
that
you
know
it
might
not
fit
into
our
planning.
A
That's
it
and
that's:
okay,
like
I
said
we're
not
committing
to
release
this
in
13
9
by
moving
into
refinement,
we're
just
moving
it
on
to
the
next
stage
of
development.
C
A
Zamir,
I
know
you
had
a
comment
in
here.
I
didn't,
I
don't
think
you
had
a
chance
to
voice
it
over.
What
are
your
thoughts.
D
I
think
it
it
has
been
discussed
already.
It
was
just
the
balance
of
if
we
would
move
back
a
little
bit
to
make
sure
that
we
are
going
the
direction
that
we
expect
to
be
because
in
the
very
beginning
I
didn't
know
that
we
had
something
compliance
already,
like
all
the
other
guys
and
then
now
that
we
have,
I
was
not
sure
how
would
fit
that
overlap
in
our
in
our
process.
So
it's
it
has
been
discussed
already.
A
And
lindsay,
I
don't
know
if,
if
you've
had
a
chance
to
talk
with
thiago
on
who's,
going
to
take
the
front
end
items
you
or
alexander,
are
you
both
comfortable
moving
this
to
refinement
or
do
you
have
other
concerns?
C
He
was
an
innocent
bystander
in
this
conversation
anyways,
but
to
be
clear,
sam,
you
told
me
last
week
and
we
talked
that
this
is
a
higher
prior.
The
front
end
work,
for
this
would
be
a
higher
priority
than
the
follow
on
work
for
the
alerts.
Is
that
correct?
C
Yes,
so,
alexander,
given
that,
whether
you
end
up
picking
it
up
or
maybe
zumer
or
somebody
who's
working
full
stack?
Does
it?
I
don't
think,
there's
a
harm
in
you
know
us
moving
forward
with
that
planning
breakdown
or
sorry
refinement.
Are
you
comfortable.
B
Yeah
sounds
great
and
sam,
I
think
you
you
eloquently
put
or
explain
the
designs
and
the
path
forward
will
probably
be
no
policy
names.
As
you
said,
iteratively.
A
Yeah,
I
just
added
a
comment
to
that.
So
we'll
we'll
get
that
mock
posted
on
the
epic
today,
it's
there
in
the
design
issue,
but
we'll
finalize
that
today
so.
B
A
Follow-Up
great
well,
I
know
we've
gone
way
over
time
at
this
point,
let.
C
Me
ask
a
quick
question
before
you
wrap
up
sam
as
far
as
next
steps
for
ensuring
that
this
epic
gets
broken
down
into
implementation
issues
and
those
imitation
implementation
issues
get
refined.
What
we've
been
doing
is
assigning
the
design
issue
to
a
front-end
and
back-end
bri
to
create
those
implementation
issues.
So
I
know
alexander
will
be
doing
the
front-end
implementation
issues,
who
would
be
the
back
end
dri
for
creating
the
back
end
implementation
issues,
because
I
can
go
ahead
and
assign
that
design
issue
off
this
morning.
A
A
C
All
right
so
it'll
be
between
allen
and
john
and
adam
and
adam
right,
all
right
I'll,
just
I'll
sync
up
with
thiago
and
let
him
decide
or
about,
but
that
will
use
the
design
issue
to
handle
that
assignment,
and
we
won't
close
that
design
issue
out
until
we've
got
those
implementation
issues
created.
A
Yeah,
that
sounds
great.
I
don't
know
what
he
has
planned
for
adam,
so
it's
entirely
possible
that
he
assigns
him
to
this
as
part
of
his
internship.
But
I
I
don't.
A
Know,
okay,
so
I
I
think
we
can
skip
the
we're,
not
really
worrying
about
that
at
the
moment.
Thiago
brought
it
up,
but
it's
not
ready
for
planning
breakdown
and
it's
it's
not
a
current
priority.
A
A
I
just
added
a
note
there
that
person,
so
this
person
was
actually
hired
to
be
part
of
a
single
person
group
working
on
approvals,
so
this
person
will
probably
be
doing
approvals,
a
hundred
percent
of
the
time
when
they
are
hired.
So
I
just
wanted
to
add
that
clarification
that
that
allocation
is
like
strictly
for
approvals,
most
likely
at
least
the
way
I
envision
that
it's
going
to
be
that
person
working
on
scan
results,
policies
and
in
the
scan
results
policy.
You
can
require
approval,
so
it
be
it's
a
rather
complex
job.
A
It's
not
like
you
know.
Some
of
this
isn't
going
to
be
bigger
than
one
milestone
for
one
person,
because
we
already
have
mr
approvals
in
the
product
today,
so
there
they
would
need
to
find
a
way
to
migrate.
The
existing
mr
approvals
into
our
policy
editor
anyway,
there's
a
lot
there
there's
a
lot
more
that
we
can
discuss.
I
know
we're
short
on
time,
but
I
just
wanted
to
add
a
little
bit
of
clarification
about
what
that
role
will
be
doing.
A
A
Yeah
absolutely
and
just
a
reminder
to
the
team.
You
know
my
my
calendar
is
open
to
you
so
anytime
that
I'm
available
you're
welcome
to
to
book
something
on
my
calendar.
If
you
ever
want
to
talk
separately
awesome.
Well,
thanks
everyone
for
the
good
discussion
today
and
we'll
chat
again
next
week,
bye
friends.