►
From YouTube: Contributor Success FY24Q2 OKR Results overview
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
Welcome
to
contributor
successes
of
Jr's
results
for
Q2,
with
this
video
we're
trying
to
give
you
an
overview
of
what
contributor
success
is
doing
in
order
to
increase
our
wider
community
and
make
sure
that
our
community
is
successful
when
they
are
contributing
to
the
kidlab
project.
Now,
in
summary,
we're
trying
to
improve
contributor
velocity
through
better
tooling
and
content,
we're
trying
to
improve
contributor
recognition
to
improve
processes
and
awards
and
growing
the
community,
Through
leading
organizations
and
events
at
the
top.
A
You
can
see
the
members
of
contributor
success
and
I'd
like
to
welcome
Mike
and
Oksana
in
our
team
in
helping
us
achieve
our
mission.
Now,
if
we
go
into
improving
contributor
velocity
route,
better
tooling
and
Technical
content,
what
we
did
is
we
worked
with
the
remote
development
workspaces
team
to
ensure
that
everyone
can
contribute
system
requirements
can
prevent
local
development
and
GDK
is
not
always
suited
to
be
installed
on
every
machine.
A
Gitbull
is
also
not
always
viable,
so
we
were
produced
a
GDK
and
installing
the
GDK
and
remote
development
workspaces
we
locked
three
Upstream
issues
of
which
two
were
already
implemented:
there's
a
blog
post
and
an
MR.
To
add
to
GDK
workspace
container
that
got
merged
next
up
is
that
we're
investigating
how
to
enable
this
for
the
wider
community
and
for
leading
organizations.
A
We
hope
that
there
are
certain
organizations
that
can
get
enabled
to
contribute
faster
if
they
actually
get
the
environment
set
up
for
them,
instead
of
being
on
their
local
devices
next
up
or
trying
to
improve
contributor
recognition
to
improved
processes
and
awards,
and
our
aim
was
to
roll
out
six
types
of
achievements
to
150
contributors,
I'm
happy
to
announce
that
we
reached
this
goal
and
above
we
awarded
600
wider
community
members
with
achievements
going
from
MVP
to
their
contributor
lifecycle
segment,
but
also
rolled
out
this
achievement
or
the
the
gitlab
team
member
achievement
to
2000
team
members
and
more
automation
was
implemented
to
a
widen
revoke
at
the
above
and
we're
hoping
to
see
the
results
of
this
soon.
A
We
also
imported
a
year
of
issuable
data
into
common
room,
which
allows
us
to
unlock
data-driven
decisions
for
The
Wider
Community.
This
includes
activities
such
as
merge
requests
and
issues,
but
we
don't
have
all
the
comments
there.
We
don't
have
all
the
Emojis.
So
this
is
something
that
we
could
work
on
as
we
go
growing
the
community
Through
leading
organizations
and
events.
What
we
did
here
is
that
we
organized
or
wanted
to
organize
two
contributory
events.
A
The
result
is
that
we
had
six
Community
office
hour
sessions
that
have
over
600
views
and
we
have
a
hackathon
that
successfully
finished.
We
had
over
165
merge
requests
and
over
69
participants.
A
We
want
to
make
sure
that
these
Community
office
hours
could
be
run
independently
from
contributor
success
and
we're
going
to
work
on
how
to
ensure
that
that
can
happen,
and
we
have
other
hackathon
scheduled
on
the
2nd
of
October
until
the
9th
of
October.
We
hope
to
also
try
to
better
leverage
the
water
team
for
promotion
and
Outreach.
So
we
can
grow
the
community
together
in
terms
of
supporting
customers
to
become
a
leading
organization.
We
had
the
aim
to
support
three
customers
that
have
over
100k
AR
with
us
to
contribute
to
10
Mrs.
A
We
did
site
visits
with
two
large
customers
unblocked
another
customer
from
legal
restrictions.
We
have
a
co-working
day
that
we
organized
with
another
customer
and
there
is
a
customer
that
is
performing
an
internal
survey
to
find
contributors
or
find
people
that
are
enthusiastic
to
contribute
back
to
gitlab.
We
have
a
contributor
from
customer
from
a
customer
that
recently
joined
our
heroes
program
and
has
six
recent
merch
requests.
We
consider
this
successful,
but
we
are
not
seeing
tangible
Mr
increases
during
the
quarter.
A
We
do
know
that
we
have
unblocked
and
started
to
move
forward.
It's
just
not
at
the
base
that
we
expected
and
in
terms
of
getting
wider
Community
feedback
on
AF
features.
This
is
another
great
investment
that
we
did
to
get
engagement
from
our
wider
Community.
We
did
a
swag
feed
like
we
got
a
sorry.
We
did
a
contest
that
had
rewards
in
the
form
of
Swag.
A
There
were
19
Community
contributors,
providing
feedback
across
four
issues
and
as
a
follow-up,
there
were
issues
created
by
team
members
to
make
sure
that
we
act
on
that
feedback.
More
insights
can
be
found
at
the
okr
report,
AI
feedback.
Thank
you
for
your
attention
and
we're
hoping
to
see
you
in
the
issue.
Queue
and
help
grow
and
Foster
our
wider
Community
for
gitlab.
Thank
you.