►
From YouTube: Secure & Protect Stage Weekly Meeting June 23 2021
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
happy
wednesday,
everybody
is
so
or
fake
thursday,
depending
upon
how
you
would
like
to
view
it
so
we'll
go
ahead
and
get
into
the
announcements
so
reminder
friday
is
family
and
friends
day.
So
hopefully
everyone
can
take
advantage
of
that
or
or
find
a
time
where
you
can
so
next
is
highlights
from
engineering
week
in
review.
So
first
one
is
engineering
specific.
A
There
is
a
there's,
a
usage
of
get
of
of
limiting
features
to
justgitlab.com,
there's
a
proposal
to
ban
its
usage
and
to
change
it
to
be
more
granular,
feature
checking,
and
so
there's
more
information
about
in
that
issue.
If
you
want
to
know
what
what
is
being
discussed
and
what
proposals
are
on
the
table
within
get
lab
rails,
there's
been
a
ci
job
added
to
verify.
Our
classes
are
loaded
correctly
with
the
with
the
auto
loader,
and
there
are
class
names
file.
A
Names
that
are
following
rail
are
being
asked
to
strictly
follow
rails
conventions,
documentation
on
what
those
conventions
are
is
available
in
that
link
from
the
from
the
ruby
on
rails.org
website.
A
Next
is
about
performance
targets
and
endpoint
response
times,
and
these
are
in
lab
conditions.
This
is
not
production
conditions,
it's
going
down
from
500
milliseconds
to
200
milliseconds,
so
the
there's
more
information
about
what
they're
doing
as
well
as
why
is
available
in
that
link,
and
that's
that's
item
c
and
item
d
from
the
week
in
review
was
an
announcement
or
a
reminder
about
regulation,
fair
disclosure
or
regulation
fd
training
that
we
are
all
being
asked
to
take.
The
training
has
been
assigned
to
everyone.
A
He
asked
as
it's
being
that
it
is
completed
by
the
end
of
july
and
so
there's
a
link
available
to
the
announcement,
as
well
as
a
link
to
the
training
estimated
time
investment
is
about
30
minutes
it
is.
It
is
a
series
of
videos
followed
by
multiple
choice,
questions,
fair
warning
that
you
cannot
watch
the
videos
on
1.5
speed
so
once
you're
in
yeah,
you
you're
in
for
it
you're
in
for
the
whole
thing.
B
I
also
left
a
tip
on
them
because
they
unfortunately
trick
you
one
of
the
slides,
looks
clickable.
It's
not
clickable.
You
have
to
click
next
and
then
get
the
radio
buttons
to
click.
So
I
put
a
hint
below
in
the
comments.
But
if
you
missed
the
comment
and
you're
clicking
something
and
nothing's
happening
just
hit
the
next
button
and
then
do
the
radio
button.
A
And
finishing
off
the
announcements,
what
we
have
every
week
features
and
high
priority
bugs
closed
in
the
past
seven
days.
Here's
our
list,
it's
a
pretty
good
list,
and
so,
if
you
want
more
information
about
what
was
closed
and
how
it
was
closed,
please
click
through
for
information.
A
Error
budget
is
related
to
production,
that
is,
production
observations.
This
is
these
are
lab
conditions,
so,
if
they're
doing,
if
they're
doing
benchmarking
or
cluster
size
recommendations
for
self-managed
customers
for
for
given
endpoints,
I
think
this
is
why
that
place.
So.
C
Alrighty
mark
floor's,
yours,
sir.
Thank
you.
I
wanted
to
ask
about
whether
we
have
a
testing
group
in
production,
and
I
can
see
that
olivier's
already
responded,
that
we
have
a
gitlab
org
security
products,
slash
tests,
but
it
looks
to
me
like
that
is
specifically
about
projects
built
to
test
a
specific
analyzer.
B
C
B
There
is
a
separate
demos
link.
I
will
hunt
my
bookmarks
folder
for
it
never
mind,
you
are
faster.
Thank
you.
C
Great-
and
I
can
probably
investigate
this
myself,
but
another
use
case
is
that
do
we
do
so
quick
question?
Is
this?
Is
that
namespace
under
ultimate
or
do
we
have
like
a
free
tier
version
of
this
and
a
premium
tier
version
of
this?
D
So
I
I
guess
I
was
going
to
ask
initially
what
is
this
for
because,
like
I,
I
would
just
test
things
in
my
personal
name
space,
but
if
we
actually
rely
on
like
using
the
groups
like
the
group
dashboard
or
something
like
that,
then
it's
probably
worth
having
like
a
dedicated
project.
C
Yes,
perhaps
I
mean
in
reality,
maybe
just
doing
something
in
in
staging
would
be
better
and
just
leaning
on
secure
team
test.
Doing
it
in
production
is
not
always
necessary,
it's
just
something
that
came
up
recently
regarding
a
flipping,
a
feature
flag
and
handing
out
to
designers,
saying
you
know
how
does
this
look
and
other
people
as
well
for
their
impressions?
So
I
think
staging
maybe
is
the
best
place
for.
C
A
Yeah
I
hate
to
ask
this
question,
but
but
I'll
I'll
ask
anyway
out
of
my
own
ignorance.
Does
anyone
know
when
will
is
back
from
paternity
leave.
A
D
August
august
10th
is
what
his
slack
profile
says:
no
math
needed.
A
Just
clicking
through
to
get
the
information,
okay,
that
that
would
be
the
other
person
that
I
would
ask
if
we
need
to
do
things
along
different
license
tiers
and
if
you're
looking
for
end-to-end
tests-
and
I
know
he's
done
that
hand-off
and
done
a
good
job
documenting
all
of
these
things.
So,
but
that
was
my
other
instincts
is
maybe
look
for
if
we
needed
something
in
production.
B
Also,
breaking
your
use
case
in
half.
If
we're
testing
a
feature
flag,
flip,
I
100
agree,
that's
got
to
be
in
staging
and
probably
also
production,
so
we
probably
need
some
kind
of
test
project
set
up
with
the
free
tier,
if
that's
necessary,
but
for
the
showing
feature
to
another
team
member.
I
just
yolo
and
throw
it
in
my
personal
sass
like
I'll,
go
to
demos
and
I'll
make
a
fork
or
a
mirror.
B
C
Yeah,
that's
what
I've
been
doing.
It
was
just
a
pain
recently
because
I
had
to
actually
present
it
to
several
people,
so
I
had
to
add
people
and
so
on
and
so
on,
but
if
it
was
in
a
group
with
which
which
already
had
everyone
as
members
yeah
anyway,
I
think
I
have
the
answer.
So
I
think
fabian
has
the
next
point,
but
he's
not
present.
A
Yeah
I'll
cover
for
so
there's
been
a
fair
amount
of
work.
That's
going
on
in
composition,
analysis,
and
I
I
I'm
presuming
composition.
Analysis
is
larger
than
fabian
and
they're
investigating
integration
tests
and
it's
based
on
our
spec.
A
It
is
local
to
the
analyzers
themselves
as
opposed
to
fully
relying
on
the
downstream
integration
tests
that
we
have
within
that
test
group,
and
so,
if
this
is
something
that
grows,
he's
declaring
ready
enough
for
other
groups
to
utilize,
and
so
he's
provided
a
mountain
of
links
available
to
us
for
issues,
mrs
documentation,
ci
jobs,
how
adding
it
to
the
qa
process
and
so
forth.
So
this
is.
This
is
a
good
thing,
because
permissions
and
downstream
tests
are
a
joy
to
maintain,
and
I,
as
with
tong,
firmly
planted
in
cheek.
A
B
A
A
All
righty
thanks
everybody
for
your
time
and
attention
have
a
good
rest
of
your
week
have
a
fantastic
extended
weekend.
I
will
go
ahead
and
stop
the
recording
so
that
we
can
proceed
to
coffee
chat.
So,
thank
you
see
ya.