WEBVTT

00:00:00.016 --> 00:00:03.555
three years ago when we had a
submit

00:00:03.699 --> 00:00:07.703
we had a bunch of sessions that identify
the problems with Firefox and Mozilla

00:00:08.099 --> 00:00:11.790
and we had a severe crash in this
instability problem with Firefox

00:00:11.079 --> 00:00:15.151
that time but outside to the summit to
almost exactly the same time

00:00:16.050 --> 00:00:20.070
there was a new contributor to Firefox
and Mozilla he just showed up kinda been

00:00:20.529 --> 00:00:21.240
honestly

00:00:21.024 --> 00:00:24.983
as scuba diver three years ago he filed
his first bug

00:00:25.199 --> 00:00:30.410
it didn't go too well had an
interest in analyzing crash data

00:00:30.041 --> 00:00:35.050
and he was able to plug in to SoCo roark
rationales a system

00:00:35.005 --> 00:00:38.074
he has some programming skills but like
didn't wanna write code anymore

00:00:39.019 --> 00:00:43.042
(he) started filing bugs first
couple were dupes in

00:00:43.042 --> 00:00:47.161
could have been very discouraged and
given up that point but then about the

00:00:47.539 --> 00:00:48.539
fourth bug

00:00:48.539 --> 00:00:53.360
he saw some crash data come in kinda got
on top of that file the bug quickly

00:00:53.036 --> 00:00:56.059
and an engineer spotted it and gave him the
feedback

00:00:56.059 --> 00:00:59.059
that he needed to continue and

00:00:59.059 --> 00:01:03.208
the engineer saw that like it was coded
just checked in

00:01:03.739 --> 00:01:07.080
quickly provided a fix and things got a
little bit better

00:01:07.008 --> 00:01:10.657
scuba diver got more motivated and three
years later

NOTE Paragraph

00:01:10.729 --> 00:01:17.710
scuba diver has filed three thousand
bugs a thousand of those bugs

00:01:17.071 --> 00:01:18.082
have been fixed

00:01:18.082 --> 00:01:21.086
by people who whose who saw his value

00:01:21.086 --> 00:01:25.955
and jumped on his bugs and Firefox is a
lot more stable

00:01:26.729 --> 00:01:30.820
because of the efforts of the scuba diver
and we started to tell us

00:01:30.082 --> 00:01:33.171
tell the story about this man amazing
guy

00:01:33.909 --> 00:01:37.640
me told us you had conversations it
turns out

00:01:37.064 --> 00:01:40.109
that he was also working on Sumo

00:01:41.009 --> 00:01:44.318
and he is the number one contributor on
Sumo he is

00:01:44.399 --> 00:01:48.700
edited five thousand articles consumer

00:01:48.007 --> 00:01:51.216
so we Cairo ago once I'm

00:01:51.909 --> 00:01:55.001
crashed ability he knows that how many
bugs turned up

00:01:55.829 --> 00:01:59.540
out lately filed by scuba diver

00:01:59.054 --> 00:02:02.118
and our wrote him an email asking what
was going on

00:02:03.018 --> 00:02:06.807
and ... so scuba diver on his road back

00:02:06.969 --> 00:02:10.003
Varian honestly said know we've also

00:02:10.318 --> 00:02:13.670
invited into summits we tried to contact
him but like is not

00:02:13.067 --> 00:02:17.120
doesn't respond to that very often tried
sending T-shirts, try to offer him a job

00:02:18.002 --> 00:02:21.011
are and in very quietly he said

00:02:21.209 --> 00:02:24.560
night love my time at Mozilla I had some
life changes

00:02:24.056 --> 00:02:27.093
and I I can no longer contribute

00:02:27.093 --> 00:02:31.141
and so a challenge here is likely if we
set this challenge a million new

00:02:32.041 --> 00:02:33.053
contributors to

00:02:33.053 --> 00:02:37.079
to Mozilla and I'll also said the
challenge

00:02:37.079 --> 00:02:41.278
let's find one new scuba diver let's
find ten new scuba divers

00:02:41.989 --> 00:02:44.992
and let's create systems

00:02:45.019 --> 00:02:50.310
likes the Coro and and and SUMO the
allowed people to plug in

00:02:50.031 --> 00:02:53.062
and contribute in amazing ways that have
impact on our users