►
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
First
off
department
updates
happy
to
say
that
we
have
onboarded
three
new
team
members
into
the
three
new
software
engines
and
tests
into
the
quality
engineering
top
department
and
then
a
huge
congratulations
to
tanya
for
taking
on
our
leadership
role
as
director
of
quality
engineering.
A
Next
up
is
our
last
quarter's
okr
very
healthy.
Ambitious
year.
We
ended
overall
at
72
percent
a
little
bit
shy
of
the
the
intended
75
percent
for
overall
ambitiousness
I'll
go
over
deep
down
in
each
okay.
In
a
second
and
I'm
aware,
we
are
doing
okay
as
an
ally,
so
I'm
giving
you
a
full
screenshot
for
full
context
of
our
krs.
A
First
is
a
contribution
efficiency.
Unfortunately,
we
were
not
able
to
drive
raw
up.
We
ended
up
at
4.5
average,
4.5
million
average
mr
dollars
for
last
quarter.
It's
proven
to
be
volatile.
We'll
still
aim
to
increase
this.
This
quarter
going
forward.
We
will
want
to
step
back
and
make
sure
the
foundations
of
coaches
and
contributors
are
increasing,
and
you
will
see
an
action
in
the
current
quarter
okr
to
address
it.
A
I
believe
that's
the
monorepo,
omnibus
and
runner
also
an
update
on
the
maturity
of
get
here
as
well
on
improving
product
quality
side
happy
to
say
we
have
made
progress
on,
lodge
and
mark
test
coverage
and
also
mobile
browser
test
coverage
and
the
first
iteration
of
this
is
based
on
ios.
A
We
were
not
able
to
make
progress
on
performance
tests
on
the
package
group
because
we
have
aligned
more
last
quarter
on
shared
product
okayrs,
which
was
a
pilot,
and
this
would
be
delivered
in
the
follow-on,
iteration
good
progress
here
on
on
tests
coverage
on
our
our
customers,
dots
and
then
payment
system
payment
experience.
A
Lastly,
on
the
team
side,
we
completed
diversity,
inclusion,
training
at
100
percent,
we're
happy
to
see
that
this
is
a
committed
kr.
We
also
took
an
extra
credit
of
having
a
performance
check-in
and
career
development
conversations
with
everyone
in
a
team,
and
we
ended
this
at
96.
A
We
were
able
to
make
some
progress
on
another
iteration
of
the
career
matrix.
We
did
conduct
a
survey
earlier
on
and
we
captured
the
feedback
from
our
team
members,
and
this
will
still
continue
on
next
up.
Is
our
current
quarter
okrs
the
same
theme
so
contribution
efficiency,
product
quality
and
team?
A
A
That's
the
next
target,
we're
going
to
build
a
performance
indicator
for
the
gu
code,
sync
to
make
sure
that
the
code
base
con
are
moving
close
moving
forward
alongside
each
other
and
they're,
not
diverging,
and
this
would
be
a
performance
indicator
we'll
be
watching
in
addition
to
the
contributors
we
als.
We
also
will
be
increasing
in
our
coaches
as
well.
A
Moving
on
to
product
quality,
we
made
progress
on
tiff
a
a
sneak
peek
in
a
sneak
peek
preview.
We
are
going
to
continue
on
this
charter
going
forward
and
then
the
goal
in
this
part
is
to
lower
it
down
even
further
to
to
10
minutes.
A
There
are
some
corrective
actions
you
want
to
sign
up
and
help
shore
up
reliability
for
people.com.
There
are
seven
huge
items
that
we
are
tracking
in
terms
of
test
test
gap
and
we
we
want
to
deliver
this.
A
We
are
continuing
on
browser
mobile
testing,
which
is
an
align
tr
with
ux
and
a
new
staging
to
make
sure
we
we
catch
mixed
deployment,
test
cases
first
and
then
move
further
into
make
sure
we
have
a
symmetry
of
data
and
gates
before
it
hits
production
on
the
team
side,
we're
planning
three
new
job,
family
performance
indicators,
we're
going
to
hire
the
plan
and
then
complete
the
360
review
for
everyone
in
the
department.
A
A
Community
mrh
is
now
kpi.
This
continues
on
our
philosophy
of
measuring
open
things
and
encouraging
the
one
behavior
that
is
going
to
provide
value,
which
is
to
close
out
fix
all
the
open
things,
review
them
and
merge
them
open.
Community
mras
is
short
and
that's
now
promoted
to
a
kpi
master
pipeline
is
doing
well.
We
upgraded
it
to
green.
It's
been
sustained
above
90
percent,
there's
some
volatility
at
the
top
of
the
curve,
but
we're
overall
very
happy
here.
Hence
the
upgrade
tiff
our
time.
The
first
failure
is
also
improving.
A
A
Next
up
is
bugs
and
defects
open,
bug,
h,
oba
over
s1s2
s1
is
doing
good.
We
upgraded
this
to
green
the
average
time
of
openness.
One
has
lowered
due
to
the
refinements
the
the
charging
and
fixing
the
older
bugs
s2
we
are
holding
the
line
on
the
average
h,
although
the
backlog
is
is,
is
picking
up
so
that'll,
be
our
next
focus
going
forward
in
in
the
bug,
refinement
and
tragic
venues,
highlighting
two
new
kpis
for
on
the
people
side.
One
is
team.
A
The
sct
gearing
ratio
is
kept
at
red
intentionally,
but
we
have
new
staffing
approval
and
we
are
very
confident
that
this
will
improve
going
forward
and
to
our
products
counterparts
a
very
a
very
appreciation,
very
much
appreciated
on
your
collaboration
too,
to
get
those
staffing
approved
alongside
us.
So
thank
you
for
that.
A
So,
on
the
topic
of
raw
contributors
and
coaches,
we
have
set
up
a
daily
stand-up
with
our
counterpart
in
marketing,
which
is
the
community
relations
team.
On
our
side,
we
want
to
track
the
three
key
metrics
that
are
aren't
in
a
good
state.
At
the
moment
one
is
raw.
The
second
is
unique:
contribute
contributors
per
month.
We
want
to
bring
this
back
up
to
a
high
point
again
and
then
increasing
the
mr
coaches
per
month.
A
A
We
have
three
keyword
streams
listed
here
and
also
on
the
board
link
below
legal
materials,
outreach,
recognition,
tracking
and
tooling.
A
Next
up,
we
will
be
working
on
a
an
outreach,
a
contribution,
experience
survey
to
understand
any
seasonality,
any
friction
for
for
contributors
and
especially
raw
contributors
on
when
they
contribute
back
to
us
when
they
improve
recognition.
There's
an
idea
on
raw
awards,
there's
also
other
ideas
on
the
rookie
of
the
quarter,
bessmar
contributions
and
best
manager
of
a
contributor
and
those
are
in
in
the
works
as
well.
A
Also
on
on
the
backlog
is
a
page
written
by
by
lawyers
on
our
site
for
for
other
contributing
organizations,
lawyers
to
ensure
we
abide
by
illegality,
it's
it's
it's
compliant
and
there's
there's
less
friction
in
contributing,
and
the
next
up
is
we'll
plan
to
assign
dris
between
our
two
collaborative
groups
in
this
work
stream
and
and
drive
forward
an
update
on
igu
guillaume
cn
the
team.
A
The
gut
must
set
up
a
a
environment,
and
it's
up
and
running
it's
going
through
internal
testing
for
hitler.
Cn
is
based
on
the
50k
reference
architecture,
some
key
achievements.
We
have
agreed
on
a
an
iteration
going
forward
for
reasoning,
and
the
decision
is
not
to
implement
the
whole
full-blown
regioning
framework.
We
just
need
to
focus
on
the
addition
so
c-e-e
and
j-h,
and
that's
a
smaller
iteration
that
the
team
came
up
with
came
up
with.
A
The
gu
team
also
worked
on
upstreaming
tencent
cloud
provider,
docker
machine
driver
and
that's
used
to
to
power
their
runner
fleets
on
gitlab
cn
release
certification
report
is
closely
done.
The
ownership
has
now
transferred
to
application
security
and
we
will
be
providing
a
release
certification
report
for
all
the
releases
that
she
who
has
contributed
upstream
to
us
next
up,
as
I
said
before,
we're
going
to
work
on
the
coasting
performance
indicator
in
this
quarter
and
layering,
making
sure
the
the
strategy
of
layering
and
the
duplicating
test
is
there.
A
The
goal
is,
if
jihoo
picks
up
a
green
master
on
outside.
They
do
not
need
to
rerun
the
test
on
their
side
and
they
should
only
have
to
focus
on
the
tests
that
touches
the
test,
the
touch
points
and
the
features
that
they're
building
in
their
edition.
A
A
brief
update
on
ally,
okay,
rollout,
so
engineering
pilotless
last
quarter.
This
quarter.
We
are
rolling
it
out
to
r
d,
so
product
and
engineering.
A
We
have
made
progress
on
an
integration
piece
where
team
members
can
link
multiple
issues
to
drive
progress
of
a
a
single
kiwi,
solid
ally.
There
are
guidelines
on
aspirational
chaos.
Aspirational
trials
are
the
ones
that
we
are
ambitious
by
default,
which
is
aiming
to
complete
at
75
some
training.
Videos
already
handed
around
in
engineering
and
we'll
make
it
broadly
available.
Next
up
is
making
sure
we
are
transparent.
A
A
This
shows
a
view
of
the
current
current
quarter,
okrs
in
the
quality
department
handbook
page
moving
back
to
the
slide,
oh
and
the
integration,
the
handbook
embedding
itself
is
going
through
application
security.
At
that
moment,
one
of
the
next
things
I
want
to
highlight
delivered
by
the
engineering
analytics
team.
A
So
the
past
weeks,
we
have
realized
that
the
thing
that
will
improve
reliability
of
gitlab.com
is
to
work
on
the
backlog
of
our
infradab
issues,
specifically
s1
s2s.
In
the
immediate
short
term.
A
We
also
applied
our
knowledge
learnings
of
open
things
philosophy
here
and
the
metric
we
align
on
is
open,
infradev
age,
and
this
is
divided
by
s1s
and
the
seuss,
and
this
is
this
chart
is
now
available
in
in
size
sense.
It's
also
available
in
our
handbook,
and
you
were
able
to
drill
down
from
each
section
station
groups
in
addition
to
that,
we're
also
providing
a
view
of
the
merged
in
mars
and
work
types,
so
much
merge
and
mars
with
the
type
bug
or
feature
or
tooling
or
security.
Is
there
as
well.
A
So
this
gives
the
engineering
leaders
a
a
holistic
view
of
efforts
being
put
and
the
burning
down
of
the
backlog
of
open
infrared,
s1s
and
s2s
you'll
see
some
of
the
screenshots
here,
but
I'm
going
to
go
straight
to
the
habit
to
show
you
what
it
looks
like.
So,
in
addition
to
the
top
view
of
open,
infradeb
h
s,
one
s,
twos
leaders
can
scroll
up
and
you
see
the
the
effort
being
made
for
that.
A
That
scope-
and
this
is
the
the
example
here-
is
the
dev
section
you
can
scroll
down
to
every
stage
in
that
section
and
if
you
click
on
the
stage
page,
for
example,
create
you're
also
able
to
drill
down
to
every
product
group
as
well,
and
it
follows
the
same
pattern:
the
same
gauges
throughout
the
whole
structure.
This
is
now
live
and
available,
and
it's
built
for
every
engineering
match
every
product
section
being
being
drilled
down,
and
the
next
step
I
wanted
to
highlight
is
an
achievement
by
the
engineering
productivity
team.
A
So
tiff
has
has
gone
down
to
from
17.5
to
12.8
minutes.
We
are
we've
reduced
the
target
down.
We
aim
to
make
more
progress
here
in
our
target,
is
10
minutes
in
in
the
upcoming
quarter
and
then,
lastly,
the
state
of
oba
s1s2
in
quality
engineering,
oba,
s1
8,
has
gone
down
as
you
see
here,
but
s2
is
is
increasing.