►
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
Hi
everyone-
I
am
max
citri,
director
of
quality
engineering
and
I'm
recording
a
video
preview
for
a
group
conversation
tomorrow.
A
A
We
also
completed
our
dog
fooding,
building
directly
into
git
lab
initiatives
and
also
contributed
to
building
load
testing
as
a
as
a
feature
indicate
lab
using
k6,
and
it
has
moved
this
category
of
load
testing
into
survival
and
plus
a
number
of
reference
architecture
improvements.
Here,
however,
we
haven't
completed
our
team
okr.
A
We
have
reviewed
some
of
the
ic
compound
worksheets.
We
still
get
to
do
the
the
management
combo
worksheets,
but
we
have
factored
in
our
values,
competencies
and
a
number
of
improvements
there.
We
aim
to
continue
the
momentum
here
in
q3.
A
We
also
raise
our
handbook
frequency,
which
is
great,
and
then
our
team
members
have
been
participating
in
in
the
diversity
and
inclusion
initiatives
moving
on
to
q3.
So,
as
you
can
see
in
acv
efficiencies,
leaning
on
that
momentum,
what
we
made
progress
in
q2
we're
doing
the
same
for
for
q3.
A
We
want
to
enable
the
team
to
move
faster
with
migrating
components,
adding
more
components
to
the
reference
architecture.
So
when
customers
install
a
large
scale
the
deployment
these
are
guidelines
that
just
come
out
of
the
box
and
also
increase
the
efficiencies
of
of
sign
up
and
the
customer
flows
there
for
for
for
the
product.
Okr
we're
dog
fooding,
there's
a
number
of
dog
fooding
efforts
here,
both
building
into
good
lab
directly
and
also
using
more
of
our
features
for
project
management.
A
We
want
to
implement
the
test
file
finder
and
use
this
to
even
lower
down
the
cost
per
pipeline
even
more
for
the
team.
Okr
there's
a
number
of
initiatives
here.
We
want
to
ensure
that
our
managers
attend
the
diversity,
inclusion
and
belonging
training
and
have
a
career,
a
growth
conversation
with
our
team
members,
and
this
is
a
continuation
of
of
our
compound
career
matrix
that
we
have
done
in
q2.
A
We're
also
improving
a
number
of
internal
processes.
Our
on-call
process
has
a
number
of
manual
steps
right
now
that
we
want
to
automate
and
then
also
help
improve
the
wider
community
productivity,
with
that
I'll
jump
to
slide
six
one
of
the
to
highlight
that
there's,
a
new
regular
performance
indicator
rpi.
A
This
is
the
quality
department
member
mr8.
So
we
have.
We
have
established
this
recently
and
set
a
target
to
to
10,
which
was
our
previous
historical
high
and
I'm
happy
to
say
that
we
actually
reached
10
in
july,
so
a
huge
shout
out
and
applause
to
to
the
rest
of
team
to
everyone
in
quality.
Next
steps
is
to
increase
our
maintainers
even
more
and
and
maintain
this
rate
of
10
10
mrs
per
month,
and
see
where
we
can
go
from
here:
slice,
7
and
8.
A
A
Mostly
here
I
want
to
highlight
the
the
work
we're
doing
with
the
certified
group.
We
we
want
to
move
quality
management
from
nbc
to
to
viable
and
and
and
mature.
We
are
incorporating
feedback
from
our
workflow
to
implement
test
case
and
test
sessions,
as
a
a
first
class
object
in
good
lab
and
a
huge
shout
out
to
felipe
mark
woods
and
nick
brandt
for
for
our
discussions
and
solution.
A
Validation,
if
you
want
to
check
it
out,
feel
free
to
check
out
the
youtube
recording
here
and
the
feedback
and
the
prototype
that
we
did
in
quality
is
also
linked
here
as
well
for
the
slide
8
a
number
of
collaboration
which
we're
doing
for
all
all
the
departments
in
engineering
we
developed
with
development,
we're
working
on
handbook.
A
First,
bug:
defects
for
all
the
engineering
teams,
drilling
down
from
section
stage
and
groups
with
ux
we're
improving
our
bug,
categorization
and
improving
the
severity,
so
they
can
be
charged
faster
with
infrastructure.
We
are
improving
staging
to
catch
more
defects
at
scale.
A
So
if
you
want
to
catch
performance
and
scalability
issues
that
happens
in
production,
we
need
to
treat
staging
the
same
way
as
we
treat
production
and
increase
the
workload
there
with
security
compliance
and
also
providing
data
with
test
results
and
actually
want
to
call
that
the
the
solution
validation
with
the
certified
group
captures
what
we
have
been
discussing
with
security,
so
test
session
reports
that
needs
to
be
customer
facing,
and
public
friendly.
A
We
need
to
move
in
that
direction
if
you
are
to
be
a
mature
company
with
that
I'll
jump
to
slide
20,
which
is,
I
want
to
call
out
really
great
backstop
test
coverage
that
the
dev
qe
team
has
been
adding
a
really
clear
traceability
here,
you
can
feel
free
to
take
a
look.
The
team
has
been
shoring
up.
A
number
of
defensive
measures,
for
so
we
don't
incur
more
defects.
A
A
For
now,
the
feature
is
temporarily
disabled,
because
the
project
is
small.
This
feature
actually
ended
up,
adding
more
wall
time
or
ci
runtime
to
to
the
project.
We
we
have
our
next
steps
online.
Here
we
want
to
restructure
the
jobs
a
bit
more,
so
this
feature
is
adding
value
and
we're
working
closely
with
the
the
testing
group
to
implement
the
next
iteration
as
well.
A
A
Lastly,
for
the
the
enablement
team,
this
is
where
I
called
out
earlier
that
the
team
has
has
contributed
to
building
the
maturity
of
our
load.
Testing
category
and
now
we
can
run
load
tests
from
gitlab
ci
jobs
and
it's
using
using
k6.
A
The
team
has
also
built
a
new,
secure
group
or
feature
category
pipeline,
so
the
secure
test
projects
now
being
being
running
with
regression
tests.
So
that's
exciting
news
with
that
I'll
move
on
to
highlighting
challenges
the
bush's
slide
56.
A
So
there
were
two
nodal
incidents
this
past
month.
One
is
the
gitlab
pages,
and
also
the
ci
render
flags
we're
working
closely
with
the
engineering
teams,
development
and
infrastructure
for
corrective
action.
So
there's
some
tests
that
we
need
to
to
add
for
pages
and
also
a
backwards
flag
compatibility
for
runners.
A
One
challenge
here
I
want
to
highlight:
is
these
two
areas?
We
actually
don't
have
a
software
engineering
test,
so
we're
looking
to
at
least
help
and
also
see
where
we
can
improve
the
gearing
ratio
here
and
lastly,
with
the
challenges
we
still
are
behind
our
intended
staffing,
gearing
ratio,
and
we
also
want
to
continue
to
improve
our
core
planning
process
and
working
closely
with
product
management
and
giving
our
feedback
into
the
survey
and
also
looking
to
build
deeper
collaboration
with
our
counterparts.
A
So
that's
it
for
highlights
of
the
quality
department.
I
hope
that
you
join
us
for
more
conversations
tomorrow
and
hope
that
you
have
a
good
day
good
evening,
wherever
you
are.
Thank
you.