►
From YouTube: 2022-05-03 Compliance Weekly
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
A
Our
smarter's
got
replacing
approved
with
passing
api
responses,
which
is
a
review
and
then
max
you've
got
the
max
too.
Yes,.
A
Nice
I've
got
the
status
check
ad
status
field
feature
flag,
which
is
an
another
feature
flag
to
try
to
roll
out
this
week.
I
just
want
to
double
check
that
it's
not
conflicting
with
one
of
the
other
breaking
changes.
That's
going
on.
I
know
there
was
some
concern
from
utsava
there,
so
I
haven't
double
checked
on
that
and
hey
sasha.
A
Welcome
to
the
welcome
to
the
party
cool,
so
yeah
I'll
be
rolling
this
one
out
and
I'll,
hopefully
I'll
roll
it
out
a
little
slower
than
the
previous
one
as
well.
So
after
after
we
do
get
labor
and
com
we'll
be
using
a
percentage-based
actor
there.
So,
hopefully
nothing
too
crazy
goes
on
there.
A
All
right,
yeah
and
you've
got
filter
compliance
violations
like
all
protected
branches.
E
A
Got
it
well
sounds
good
and
then
rob
you've
got
the
next
two.
A
All
right,
so
I
think
I
understood
most
no
you're,
not
sasha
rob's,
having
sound
issues
so
you're,
not
the
only
one.
So
it
sounds
like
it's.
It's
heavily
dependent
on
the
safest
work
getting
merged
in
so
which
seems
to
be
a
good
state.
So
we'll
keep
an
eye
on
that
which
is
the
next
issue
which
is
still
currently
in
death,
but
it's
if
it's
out
on
holiday,
so
we'll
get
back
to
that.
A
E
Yeah,
that's
correct
at
least
the
front
end
that
was
blocking.
It
is
validated
and
done
so
it's
just
the
back
and
left
awesome.
A
D
Yep
so
I
made
a
start
on.
D
Hasemar
quite
rightly
pointed
out,
I
had
missed
out
something
fairly
obvious
in
the
way
that
we
can
implement
it.
So
I've
made
those
changes.
When
I
finished
my
p1
work
today,
I'm
going
to
validate
those
and
get
them
back
into
review.
A
Awesome
then
we're
looking
like
pretty
good
shape
as
far
as
priority
ones
and
priority
twos
are
concerned.
I
guess
the
only
thing
well
that
I
definitely
plan
to
follow
up
on
once
we
say
for
returns
to
see
if
there's
any
help,
we
can
do
here
as
far
as
the
inactive
project
deletion
stuff.
Since
there's
three
issues
in
p1
that
are
gonna
resting
on
that.
So
as
far
as
every
the
lower
priorities
is
there
anything
anyone
would
like
to
bring
up
as
far
as
p3
p4.
A
All
right,
then,
we
will
move
on
to
refinement.
I'm
not
sure
if
we
have
a
whole
lot
assigned
here,
one
for
eon,
not
sure
if
there's
any
movement
here
is
for
the
drop
down
selection.
E
Yeah
I
started
looking
at
that
again
today,
but
I
still
need
to
continue
with
the
implementation
plan,
so
nothing.
A
A
Sounds
good
the
other
one's
assigned
to
harsamar?
This
is
what
this
one's
related
to
the
this
one's,
the
bug
related
to
treatment
operations
which
hasn't
been
estimated
yet
so
I
don't
know,
perhaps
we
might
be
able
to
pick
this
up
later.
This
will
be
good
for
some
customers
to
get
used
that
are
actually
interested
in
get
fetch
operations
so
yeah
all
right.
It's
not
the
final
weekly
of
the
milestone,
so
I
don't
think
we
need
to
cover
police
post
blockers
yet
so
sam.
I
think
it's
probably.
E
Yes,
I
think
we
still
have
closed
issues
all
right,
yeah.
A
Yeah,
I
missed
the
bookmark
from
last
time,
so
I'm
not
sure
how
far
we
got
last
week.
I
don't
think
I
covered
any
last
week.
All
right,
then
it's
gonna
be
a
fun
time.
Let's
see
what
our
live!
Well,
I
guess:
do
we
have
a
bookmark
at
all
because
of
the
new
milestone?
Probably
not
so
they
just
start
from
the
beginning
or
31
issues.
A
There
we
go
all
right,
you
could
say
if
it's
got
the
first
one's
moved
required
pipeline
configuration
ultimate,
so
it's
an
upturning
one
that
we
actually
simplified.
So
that's
great.
We
got
that
customer
unable
to
configure
event
streaming
on
gitlab.com
max,
not
sure
if
you
want
to
speak
to
this
one
yet.
D
I
won't
go
into
detail
because
it's
confidential,
but
it
was
a
an
interesting
bug
for
a
subset
of
ultimate
customers
that
we've
now
resolved.
E
Yeah,
so
the
project
filter
used
by
also
some
analytics
dashboards,
overflowed
and
then
fit
to
containers
for
projects
with
very
long
names,
so
that
was
caught
by
elena
during
a
review
and
yeah.
It
was
just
a
small
fix,
so
it's
now
working
better
right
across
the
board
and
the
next
one's
also
related
to
that.
A
Awesome
cool
and
then
our
smarter's
got
the
next
five
so
feature
flag.
Sorry,
okay,
I'll
go
in
order,
a
lot
of
events,
so
this
one's
from
14
10..
It's
a
two-part
change
in
terms
of
auditing
and
merge
request,
setting
changes.
So
those
look
like
they've
all
made
it
over
got
some
breaking
changes
as
well
in
terms
of
removing
the
default
status
for
api
requests.
A
Now
that
we're
failing
that
and
we
have
a
new
application
setting
as
far
as
what
the
front
end
needed
in
terms
of
cleaning
up
that
ui,
the
improving
the
ux
around
settings
around
delayed
group
deletion
and
then
the
feature
flag,
I'm
not
quite
sure
which
ones
clean
up
the
repository.
Oh,
yes,
yes,
yes,
yes,
we
were
adding
repository,
push
audit
events
to
our
normal
audit
event
log
and
that
was
causing
performance
issues
and
site
degradation.
Things
like
that,
and
so
we've
actually
just
removed
that
entirely.
A
E
A
B
Right,
let
me
go
ahead
and
share
my
screen.
Links
are
in
our
agenda
doc,
so
maybe
a
little
bit
of
context
on
some
of
the
like
higher
level
priorities.
We're
thinking
about
and
dennis
is
going
to
talk
about
this
a
little
bit
more
in
the
agenda
with
okrs,
but
really
one
of
our
key
focus
areas
for
the
next.
Several
releases
is
going
to
be
around
streaming
audit
events,
we've
gotten
really
good
positive
feedback
from
all
the
customers.
B
I've
talked
to
with
our
initial
iterations
and
there's
lots
of
edges
and
opportunities
for
us
to
add
new
features,
new
enhancements
to
really
get
it
to
something
to
the
point
where
it's
something
that
they
rely
on
as
a
critical
piece
of
you
know,
running
their
organization,
a
couple
of
the
bugs
that
were
on
the
board
that
we
talked
about
there.
People
are
are
very
interested
in
seeing
resolve,
so
they
can
adopt
it.
Things
like
get
fetch
events
and
what
you're
going
to
see
is
15
1
will
have
a
number
of
items
in
it.
B
Let
me
find
the
share
button,
but
that
should
really
reflect
that
sort
of
streaming
audit
events
being
a
critical
area
of
focus.
For
us.
We
are
a
couple
of
weeks
away
from
having
this
finalized,
so
this
is
still
in
draft
as
always
open
to
feedback.
If
you
see
something
that
shouldn't
be
here
or
something
that's
not
here,
that
should
but
one
of
the
the
key
sort
of
feature
things
if
we
can
get
it
through
refinement
weight,
looks
good.
B
I
would
rather
just
only
receive
the
event
types
I
care
about
if
you're
interested
in
a
little
bit
more
detail
about
this,
I
wrote
up
the
customer
report
in
the
pm
standup
channel,
and
that
has
customer
names,
as
well
as
specific
data
points
that
that
might
be
interesting
there,
as
always
as
well
we're
going
to
focus
on
if
we
have
any
removals
deprecations
breaking
changes
that
are
critical
security
issues,
any
bugs
that
come
up
as
well
as
any
carry
over
from
the
15.0
release
before
we
move
into
that
sort
of
feature,
work,
there's
also
a
collection
of
other
new
audit
events.
D
Yeah
just
raising
the
chat
but
I'll
work
close
it
because
51
is
not
a
major
change,
we
won't
be
doing
any
removals,
but
there
may
be
deprecations
of
their
top
priority.
B
So
I
have
the
next
one
as
well,
so
I
wanted
to
give
you
all
an
update
on
our
partnership
with
pipedream.
They
were
formerly
known
as
requestpen
we've
been
working
with
them
the
past
couple
of
weeks
to
actually
build
an
integration
into
their
product
for
streaming.
Audit
events,
one
of
the
pain
points
customers
have
talked
about
is
you
know
the
audit
events
are
great,
but
I,
the
customer
have
to
build
this
sort
of
glue
layer
that
connects
to
all
these
other
tools
that
I
care
about.
B
B
So
I'm
in
pipe
dream
right
now
the
integration
will
allow
people
to
just
add
a
new
gitlab
source
and
they
can
select
that
they
want
to
start
receiving
streaming.
Audit
events
this
integrates
directly
with
their
git
lab
accounts.
B
You
can
see
all
the
groups
that
you've
got
access
to
and
then
this
is
going
to
automatically
configure
the
streaming
audit
events
for
that
group
that
I
selected
here
and
start
sending
events
directly
to
it.
So
I'm
really
optimistic.
This
is
gonna,
help
a
lot
more
people
get
onboarded
more
quickly
with
streaming
audit
events
and
start
to
take
advantage
of
it.
B
So
I
wanted
to
give
you
all
that
update
and
certainly,
if
you
use
pipedream,
feel
free
to
try
it
out
see
see
if
there's
any
room
for
improvements
or
or
if
there
are
any
bugs
in
it.
B
Correct
so
they
previously
had
a
get
lab
integration
that
they
built
at
some
point
before
they
were
an
official
technology
partner.
I
have
been
working
with
them
the
past
couple
of
weeks
to
add
the
graphql
queries
for
the
new
streaming
audit
events
specifically,
but
all
of
that
oauth
and
the
other
infrastructure
was
already
there.
B
That's
very
cool,
so
our
sort
of
next
steps
on
this
I'm
gonna
start
plugging
it
in
customer
conversations,
but
we'll
also
likely
try
and
put
either
a
blog
post
together
with
more
about
it
or
a
video
demo
or
some
sort
of
exciting
go
to
market
collaboration
with
these
folks,
which
should
hopefully
drive
more
adoption
of
our
features
as
a
result.
A
Alrighty
very
exciting
stuff,
we're
gonna,
expand
on
that
and
the
for
the
major
kind
of,
and
then
the
shadow
care
that
that
sounded.
I've
been
working
on
preparation
for
this
next
quarter.
A
So
speaking,
yeah
on
that
topic,
it
is
officially
a
fiscal
year,
23
quarter,
two,
and
so
with
that
we
have
a
new
batch
of
okrs,
which
are
mostly
finalized,
actually
there's
only
a
couple
that
are
requiring
a
little
bit
more
information,
but
going
off
of
what
sam
had
mentioned
in
terms
of
in
terms
of
trying
to
be
able
to
get
more
or
drive
more
adoption
for
streaming
audit
events.
A
We
have
a
goal
here
to
see
if
we
can
onboard
10
customers
that
involves
a
variety
of
things
and
then
demo
as
sam
is
already
just
giving
us
a
quick
demo
of.
How
can
we
expand
on
that?
To
potentially
illustrate
a
good
example?
In
terms
of
you
know,
perhaps
some
permission,
level
changes
or
emerge
request,
setting
changes,
and
that
gets
piped
over
into
pipe
dream.
A
A
In
addition
to
that,
we've
got
an
epic
in
terms
of
integrating
with
third-party
storage
systems,
because
right
now,
with
the
current
http
endpoint,
a
lot
of
customers
have
been
requesting
really
more
specific
integrations,
but
the
kind
of
step
towards
that
in
specific
integrations,
meaning
with
specific
product
products
like
microsoft
sentinel.
But
I
think
integration
or
we
think
integration
with
third-party
storage
systems.
Putting
this
in
a
s3
bucket
or
things
like
that
is
kind
of
an
intermediary
step
and
an
alternative
option
from
http
endpoints.
A
So
it'll
be
interesting
to
see
how
customers
respond
to
that
additionally
and
there's
another.
A
This
is
also
tied
to
another
okay,
alright
down
further
below,
but
we
want
to
add
three
new
streaming
audit
events
and
also
see
if
we
can
solicit
three
contributions
from
outside
the
group
to
help
drive
kind
of
usage
of
streaming
audit
events
or
out
events
in
general
and
then,
as
sam
mentioned
already
in
the
15-1
planning,
introducing
some
form
of
filtering
to
help,
simplify
the
amount
of
data
or
reduce
the
amount
of
data
that
customers
are
getting
since
it's
a
literal
firehose
at
this
point
in
time.
A
I've
left
it
broad
because
I
think
from
community
and
outside
the
team
within
gitlab
are
both
applicable,
and
I
can.
I
can
speak
to
that
in
a
bit
with
point.
Well,
I
can
jump
to
it
real
quickly
as
to
why
so
for
number
five
here,
so
document
shift
responsibility
of
auto
event,
implementation
to
the
groups,
this
one's
as
far
as
context
goes
about
probably
a
year,
maybe
even
longer.
A
Now
we
were
talking
about
how
we
needed
to
refactor
audit
events
and
how
we
were
kind
of
making
improvements
to
other
events
as
from
an
implementation
standpoint,
but
as
we
saw
in
and
as
you've
seen
as
maintainers
are
reviewers,
we
often
get
merged
requests
that
add
audit
events
to
features
that
we
don't
actually
own
and
that
and
we're
kind
of
the
first
ones
to
field
those
reviews,
and
sometimes
we
don't
actually
even
include
include
the
group,
because
it's
just
you
know
from
the
code
perspective,
it's
just
not
an
event
implementation,
but
sometimes
we
do
miss
edge
cases
because
we're
not
as
familiar
with
the
group,
but
also
we,
I
think,
we've
made
enough
improvements
and
the
the
data
tables
have
been
partitioned
and
we
have
good
sufficient
documentation.
A
As
far
as
how
how
normal
audit
events
as
well
as
streaming
audit
events
are
implemented,
that
I
think
we
can
safely
make
the
recommendation
for
groups
that
they
are.
They
are
responsible
for
at
least
kind
of
doing
that
initial
review,
and
if
they
have
questions
around
how
audit
events
are
implemented,
then
we
can
help
support
that
and
so
really
what
what
has
to
happen.
A
There
is
a
documentation,
a
bit
more
of
like
announcement
that
you
know
groups
are
going
to
be
more
responsible
for
for
auto
event,
implementations
and
we're
just
the
domain
experts
to
provide
support
there.
That
gets
into
a
couple
of
different
other
things
in
terms
of
like
product
like
category
maturity,
thing
scoring
that
we
want
to
try
to
change,
and
I
don't
want
to
speak
for
sam
here,
but
he's
leading
the
conversation
there.
A
In
terms
of
you
know,
what
can
we
can
we
kind
of
refine
the
the
definition
of
done,
especially
when,
when
when
groups
want
to
move
their
feature
from
like
to
complete
in
terms
of
the
maturity
scoring
and
part
of,
that
would
possibly
require
making
sure
that
they
have
all
the
audited
events
they
need
there.
A
All
right
cool
a
couple
other
okrs
dog
footing,
value
stream
analytics.
So
for
those
that
aren't,
you
aren't
familiar,
you
can
kind
of
measure
the
different
times
through
various
parts
of
the
workflow,
with
our
issues
and
merge
requests,
and
so
one
thing
that
the
managed
stage
wants
to
do
is
to
try
to
dock
through
the
value
stream
analytics
to
see
how
how,
if
there's
value
we
can
get
out
of
it
for
the
compliance
group,
you
can
define
custom
stages.
A
So
if
we
have
different
workflow
states
that
we
want
to
track
to
start
as
far
as
starting
stop
endpoints,
we
can
I'll
include
a
link
in
terms
of
what
value
analytics
looks
like
so
so
it
makes
a
little
bit
more
sense.
But
basically
we
want
to
try
to
use
it
to
see
if
there's
value
we
can
get
out
of
it
as
a
group.
A
So
this
is
very
loose
right
now
in
terms
of
what
we
actually
want
to
measure
and
I'm
open
to
ideas.
It
could
be
around
streaming
a
lot
of
events
as
well
to
just
kind
of
keep
it
thematic.
Basically,
this
workflow
is
from
create
in
terms
of
going
to
a
repository,
navigating
through
a
couple
folders
opening
a
file
and
then
going
back
to
the
repository
page
and
then
just
analyzing,
what's
taking
the
longest
in
terms
of
load
times.
A
Obviously,
this
is
using
site
speed,
so
you
have
waterfall
graphs
in
terms
of
just
the
entire
workflow
or
the
entire
process,
and
what's
you
know,
taking
the
most
amount
of
time
resources
things
like
that,
there's
even
a
video
for
it
as
well
film
strip,
and
so
obviously
there's
all
the
typical
site,
speed
goodness,
and
so
basically,
we
want
to
try
to
see
how
we
can
implement
something
for
that
to
just
monitor
to
start
one
workflow
in
the
compliance
space.
A
Maybe
compliance
would
probably
be
a
good
one.
There
there's
a
lot
here.
So
please
interrupt
me
if
there's
any
questions,
so
this
one's
still,
this
one's
definitely
one
that
I'm
still
waiting
on
some
more
data
from
specifically
from
ecosystems
in
terms
of
migrating,
more
pajamas
components,
we
did
really
well
last
quarter.
I
think
we
migrated.
I
think
we
had
terms
of
pajamas
issues.
We
migrated
definitely
over
over
10
and
then
system
usability
score
issues.
A
We
had
an
original
goal
four
and
I
think
we
ended
up
shipping
16
of
those,
so
we
did
really
well
last
quarter.
So
as
basically,
we
just
want
to
continue
migrating
pajamas
component
servers.
So
as
soon
as
I
have
more
information
there,
I'll
fill
that
one
out,
I've
already
walked
over
the
the
shift
of
responsibility
for
other
event,
implementations
this
one's
just.
You
know
your
mid-year
performance
review
cycles
are
coming
up
this
one's
the
less
formal
one,
but
still
an
important
milestone
in
terms
of
talking
having
performance
and
career
development.
A
Conversations
so
I'll
be
looking
to
complete
those,
and
then
I've
been
talking
about
this
already
and
you
may
have
been
paint
on
summer
requests
sam
and
I
just
want
to
take
a
look
at
our
group
page
and
make
sure
that
everything's
up
to
date
there
and
then
I
have
one
around
just
increasing
psychological
safety
around
future
flags
and
production
changes
across
not
just
the
group
but
the
entire
engineering
organization.
In
terms
of
just
documenting
the
process
involved.
A
I
had
some
really
good
conversations
with
people
during
instant
review
in
terms
of
how
to
make
sure
people
are
aware
of
what
things
to
look
at
when
feature
flags
are
being
rolled
out
and
making
sure
our
documentation
is
up
to
date
there
and
seeing
what
improvements
we
can
make
around
that
just
generally
making
people
feel,
because
I
know,
we've
all
posted
messages
in
slack
saying:
oh
well,
I'm
about
to
slip
on
a
flag.
So
this
the
sweating
has
begun.
A
So
I
just
wanted
to
try
to
like
drive
more
awareness
around
that
that
it's
it's
okay
to
flip
these
things
as
long
as
we're
prepared
to
to
monitor
them
and
then
to
wrap
things
up
thanks
for
listening
for
me,
ramble
for
this
long,
but
building
up
the
team,
there's
still
one
back
in
engineering
wreck
that
I'm
hiring
for
and
then
at
the
same
time
strengthening
our
reviewers
across
engineering
org
and
trying
to
drive
some
more
database
reviewers,
since
that
is
an
area
in
need
of
more
reviewers
and
especially
maintainers.
A
That
was
a
lot
there's
a
link.
So
if
you
want
to
look
through
them,
the
descriptions
are
a
little
bear
right
now,
but
I
will
be
working
on
adding
more
details
to
them
more
context
about
why
they're
important.
But
if
there's
no
other
questions,
then
we
can
end
the
call.
A
All
right,
then
good,
seeing
everyone
and
have
a
good
day
and
rest
of
your
week.