►
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-
this
is
mack
citri
vp
of
quality,
and
this
is
the
group
conversation
video
preview
for
our
next
up
and
coming
up
and
coming
group
conversation
on
june,
the
7th.
As
always,
we
will
try
to
provide
you
a
high-level
overview
of
what
the
status
is.
Please
feel
free
to
skip
watch
forward
fast
on
on
our
recording
to
save
your
time,
but
we
will
try
to
be
as
brief
as
possible.
A
A
We're
also
welcoming
a
new
team
in
equality,
which
is
the
new
engineering
analytics
team,
going
in
top
of
mind
that
this
has
changed
a
bit
since
the
last
time
we
talked
first
off
is
always
raw.
So
that's
our
three
year
goal
and
a
wider
community
efficiency
engineering
metrics,
the
third
that's
new
on
the
list
is
pipeline
efficiency
and
when
I
group
efficiency,
I
see
three
things:
stability,
duration
and
time
difference.
Failure
we'll
be
drilling
down
to
more
details
about
where
the
state
of
those
are
in
a
bit
as
well.
A
A
Five
and
six
is
a
newcomer,
so
we
have
matured
or
improved
our
risk
map
process.
I'm
very
happy
to
see
our
scts
coming
up
with
a
more
lightweight
process
to
to
identify
risk
maps
and
number
six
is
a.
We
have
contributions
to
our
gitlab
environment
toolkit,
which
is
very
exciting
grading
our
last
quarter,
okrs
ar
overall
54
we
did
well
in
in
raw.
I
believe
we
hit
our
highest
goal,
our
highest
point
at
15,
18.5
million
in
our
dollars.
A
We
did
well
paving
the
way
for
for
gu
contribution
process
with
which
we
will
are
adding
momentum.
This
quarter,
however,
we
we
failed
short
of
it
on
adding
three
new
mr
coach
specialties,
and
that's
because
we
didn't
have
enough
bandwidth
to
take
this
on
on
the
product
side,
improving
quality,
we
ended
up
76,
we
evolved
our
our
slo
pi
into
a
new
pi,
so
this
is
now
rated
at
50
and
things
are
improving
there.
A
We
implemented
the
first
iteration
of
failure
of
pipelines,
time
to
time
to
failure
and
also
added
a
number
of
test
coverage
as
well
on
the
last
okr
on
team.
This
is
where
we
scored
the
highest.
A
For
I
believe
this
is
under
ar
increasing
community
coefficiency
and
engagement.
We
have
a
slow
start
on
raw
because
of
a
we.
We
prioritize
to
put
our
efforts
to
a
key
business
opportunity.
Hence
the
slow
start.
A
We
are
making
progress
on
implementing
gu
reposing.
I
believe
we've
done
one
out
of
three
already
and
that's
moving
on
well
and
we
added
more
things
to
get
which
is
our
gitlab
environment
toolkit
improving
product
quality.
Things
are
moving
along.
This
is
the
adding
of
new
test
infrastructure
and
new
test
coverage
with
performance
of
large
and
mars
being
our
top
priority.
This
quarter.
A
We
also
want
to
have
a
performance,
chicken
and
career
development
conversation
with
everyone
in
the
department
and
we
look
to
iterate
our
career
metrics
yet
another
time
another
round
this
quarter
as
well,
and
I
believe
we
are
tracking
well
here,
moving
up
to
the
key
performance
indicators,
I'm
just
going
to
give
a
highlight,
feel
free
to
dig
into
the
slides
and
also
our
handbook
page
as
well
again,
as
I
said
before,
raw
slowed
down
with
a
slow
start,
because
we
are
prioritizing
a
key
business
opportunity
first,
with
something
that's
new
going
forward,
is
the
percent
of
community
mrs,
which
is
now
kpi
and
we'll
be
whole
working
together
with
the
community
relations
team.
A
On
this
as
well
on
pipeline
duration
target,
we
have
revised
this
to
45
minutes
we're
making
progress.
I
believe
this
is
one
of
the
key
areas
that
we
may
change.
The
tile
color
soon
master
pipeline
success
rate
is
at
the
90
plus
percent
for
the
past
two
consecutive
months.
I
believe
this
target
is
pretty
high
at
95
percent,
so
we
haven't
hit
95
percent
as
a
sustained
progress,
yet
we
hope
you
to
be
there
soon.
A
This
is
where
we
inten
are
intentionally
keeping
the
bar
high,
because
this
is
a
key,
crucial
piece
of
productivity
for
all
r
d
review.
Apt
took
a
brief
hit
because
we
are
intentionally
expanding
the
usage.
We
are
very
embarrassed
and
ambitious
of
making
rewraps
running
for
every,
mr,
so
that
will
also
help
us
test
the
maturity
of
our
cloud
native
installs
and
also
making
sure
that
the
test
environment
is
available
for
every
mr
in
the
monorepo
going
forward.
A
A
We
are
rebranding
it
to
be
shorter,
more
concise
with
the
messy
fuel,
so
open
bug,
h,
short
for
oba,
and
we
have
a
bit
of
an
update
here
as
well,
where
we're
tracking
more
on
the
open
things,
and
we
call
it
the
open
things
philosophy
in
our
engineering
metrics
for
the
gearing
ratio,
I'm
keeping
this
as
spread
intentionally.
We
we
did
get
some
improvements
here
by
hiring
two
scts,
as
mentioned
before,
we
have
three
opened
one
in
ecosystem,
another
italy
and
lastly,
in
runner
as
well
so
deep
dive
and
dubrovn.
A
As
I
said
before,
the
highest
point
was
18.5
in
march.
However,
with
a
slow
start
in
may,
we
are
unfortunately
at
four
point:
54
million
in
our
dollars.
We
hope
this
will
pick
up
again
once
we
have
sco
a
step
back
from
this
key
business
opportunity.
A
The
partnerships
with
the
because,
with
customer
success
and
tams
have
been
yielding
results.
This
has
helped
increase
awareness
and
improve
the
moral
accuracy,
and
we
will
continue
that
the
eb
team
kyle
also
has
done
a
great
job
of
improving
how
we
track
organizations
and
contin
and
contribute
contributors
as
well.
A
A
A
However,
the
spike
is
because
the
team
members
were
closing
out
old,
bugs,
hence
the
mean
time
to
close
increase,
but
that's
the
behavior
we
want
to
encourage
because
we
want
to
close
out
all
the
bugs,
no
matter
old
or
new.
If
we
continue
on
verifying
just
the
mttc,
we
will
incentivize
only
closing
out
of
new
bugs
and
the
older
bugs
will
be
there
indefinitely.
A
So
the
action
we
took
is
that
we
change
this
immediately
as
from
hearing
our
feedback
and
we
want
to
measure
the
most
impactful
indicator
and
encourage
the
behavior
towards
that
which
is
closing
out
all
open
bugs.
So
we
switch
to
measure
average
age
of
open
s,
minus
twos
and
it
aligns
with
our
values
as
well.
The
the
average
age
would
be
high
and
that's
okay,
because
we
have
a
low
level
of
shame
and
we
have
we
champion
transparency.
A
We
want
to
improve
our
focus
on
the
one
thing
that
matters
the
most
and
globally
optimized
for
that,
so
this
align.
This
change
aligns
very
well
with
our
values.
I'm
also
very
proud
to
say
that,
as
a
whole
engineering
organization,
the
leaders
have
decided
to
do
a
shift
of
our
pis
and
we
call
them
the
fa.
The
pi
families
of
open
things
philosophy,
so
most
requests
will
be
opened.
Murrah
through
quest
h,
merciful
is
oma
to
pair
with
that.
We're
also
measuring
the
efficiency
of
open
motion,
quest
review
time
omra.
A
For
short,
on
the
bug
side,
we
have
oba,
which
is
open,
bug
h
and
lastly,
in
this
iteration,
the
open
community
mrh,
and
that
is
agma.
That
is
this.
The
a
pair
to
open,
merge,
request
age.
However,
this
is
specifically
geared
towards
community
contributions,
because
we
care
about
our
community,
our
computer
contributor
efficiency
as
well.
A
We're
also
working
closely
with
the
cdo
ceo
shadows
to
write
a
blog
post
to
share
this
knowledge
broadly,
and
I
think
I
missed
one.
We
are
also
looking
into
the
ux
debt
as
well
to
to
align
into
the
open
things
philosophy
it's
already
there,
but
we
do
want
to
have
a
same
branding
and
alignment
to
to
make
a
bigger
impact
together
as
a
collective
unit.
A
Lastly,
on
the
highlights
of
the
departments,
gitlab
cn
or
jihoo
very
proud
of
the
progress
by
the
whole
team,
we've
completed
the
process
and
the
groundwork
to
sync
the
repos
with
documentation
in
the
handbook.
We've
also
have
improved
the
reporting,
so
our
team
can
review,
commute
contributions
from
ghoul
faster.
We
got
feedback
from
maintainable
and,
lastly,
I'm
very
excited
about
this.
The
geoteam
contributed
ali
cloud
and
also
tencent
cloud
support
and
get
dmr
link.
That's
attached
is
very
exciting
as
well.
A
Next
steps
we're
going
to
help
gu
validate
their
new
50k
sas
environment,
we're
going
to
scale
the
code
review
process
to
other
satellite
projects.
That's
our
okr
for
q2.
The
gu
team
are
also
setting
up
runners
they're
going
to
practice,
dr
with
with
geo,
and
they
will
continue
to
improve,
get
because
that's
their
method
of
deploying
their
sas
environment
so
overall,
very
very
exciting.
On
on
our
part,
I'm
gonna
spend
a
bit
of
time
diving
into
the
new
engineering
analytics
team.
This
is
we.
A
We
welcome
two
new
founding
members
lily
and
and
davis
into
the
team
and
we're
making
a
lot
of
progress
here.
The
team
here
is
the
core
workforce
on
on
improving
and
iterating.
On
the
whole,
our
engineering
pi
as
a
whole
division,
deep
diving
into
the
key
efficiency
pis
for
our
pipelines
and
for
our
r
d
org,
proud
to
say
that
our
pipeline
is
more
efficient.
The
ep
team
has
lowered
the
irish
time,
duration
from
55.7
minutes
down
to
45
minutes.
A
That's
a
very
great
progress,
and
I
do
want
to
celebrate
that
and
recognize
the
team
on
their
work.
Stability
has
also
improved
from
89
before
now
we're
hitting
the
the
border
of
the
target
of
95,
and
we
will
keep
it
here
for
for
a
while
and
demonstrate
sustained
progress.
I
do
think
this
will
be
the
closest
one
that
we
will
hopefully
turn
the
color
on
the
tile.
Soon
on
the
review
app
deployment,
I
told
before
this
the
dip
here
was
intentional,
because
we
were
stretching
out.
A
We
were
still
stable
before
we
do
want
to
use
review
apps
for
everything
and
every
mr
going
forward,
also
to
add
the
maturity
of
our
our
cloud
cloud
native
installers.
A
So
it
has
dipped
and
we
are
improving
it.
It's
recovered
to
83
and
then
our
scts
and
ep
engineers
are
working
together
on
this
part
as
well.
A
Before
I
end
the
preview,
I
do
have
a
few
call-outs
from
the
team
in
our
ops,
qe
team,
we're
working
on
a
working
group
to
improve
ops
quality
overall,
and
the
team
here
has
has
general
generalized
our
risk
mapping
framework
to
make
it
more
available
to
our
product
groups.
That
is
something
to
look
forward
to
as
this
working
group
ends
and,
lastly,
which
is
the
get
maturity.
A
So
we
we
have
added
a
geo
deployment
with
no
downtime
and
no
playbook
for
no
downtime
upgrades
and
also
we
are
very
excited
on
the
contributions
to
get
as
well
and
that's
it
for
our
preview
overview
of
our
group
conversation.
Please
join
us
on
monday,
please.
If
you
watch
the
recording
at
your
com.
Add
your
questions
ahead
of
time,
we'll
be
happy
to
jump
in
and
I
will
see
you
there
soon
have
a
good
have
a
good
day
good
night,
wherever
you
are.