►
From YouTube: Becoming a Contributor — Chris Krycho
Description
So, you’re new to the Rust community. (Or any community, really!) And you want to help, but, well, you’re new. So how exactly do you start contributing? What kinds of contributions are valuable? We’ll talk about everything from asking questions to writing documentation, from pitching in on forums and chat to writing blog posts, and from starting your own projects to contributing to other open-source projects.
A
Hello,
everyone
I
am
as
I
was
just
introduced,
Chris
Cry
Joe.
Some
of
you
will
know
me
as
the
host
of
new
Russ
station
of
the
podcast.
We
have
a
little
more
time
than
a
normal
new
raw
station
episode,
but
we
also
have
a
boatload
to
cover
so
I
will
let
you
stare
at
this
picture
of
my
hilarious,
adorable
family
for
a
moment
longer
and
then
we'll
go.
So
there
are
two
big
ideas.
I
hope
all
of
you
get
from
this
talk
idea
number
one.
A
Anyone
can
contribute
meaningfully
number.
Two
people
can
contribute
in
a
variety
of
ways,
a
stunning
variety
of
ways.
I
dare
say.
The
theme
here
is
becoming
a
contributor,
because
I
know
for
many
of
us.
For
me
that
can
be
an
intimidating,
a
challenging,
a
scary
process.
It
can
also
be
a
process
that
can
seem
very
limited
in
what
it
means
and
I
hope
to
dispel.
A
lot
of
that
today,
in
particular,
with
these
two
ideas.
A
I
want
you
to
come
away,
recognizing
that
not
just
even
you,
but
perhaps
especially
you
can
be
a
contributor
to
rust,
to
whatever
other
tools
you
use.
There
are
things
you
might
have
to
offer,
particularly
if
you're
new
or,
if
you're
an
outsider
or
if
this
is
your
first
time
doing
this
style
of
programming.
A
There
are
things
you
have
to
offer
that
someone
who's
been
doing
systems
programming
for
20
years
and
contributing
and
open
source
the
entirety
of
that
time
doesn't
have,
because
we
all
have
blinders
that
we
get
over
time
things
that
we're
just
in
nerds
to
and
blinded
to
so
everyone
here
has
something
to
contribute
and
your
outsider
Ness
is
actually
valuable.
So
anyone-
and
perhaps
especially
you
and
then.
Secondly,
there
are
so
many
ways.
So
many
ways
you
can
contribute.
A
It's
become
almost
a
cliche
in
this
particular
community
to
say
that
code
isn't
the
only
thing
that
matters
but
I
want
to
come
away
from
this
talk
with
you,
seeing
how
true
that
is,
and
you
seeing
how
many
other
ways
there
are
and
how
many
other
needs
there
are
for
contributions
that
aren't
code
and
I
want
to
preface
all
of
this
by
asking.
Why
why
this
talk?
Why
should
you
care
and
why
do
I
care?
Because
there
are
a
lot
of
things
to
be
passionate
about
in
life?
A
There
are
a
lot
of
things
to
be
passionate
about
in
the
world
of
software
development,
and
the
answer
comes
down
to
something
that
we
could
phrase
as
a
dichotomy,
humanism
or
technology
ISM,
and
to
to
borrow
that
language
from
a
developer.
I
admire
immensely
Scott
vulajin
is
a
developer
in
the
at
Short
community
and
he'll.
Talk
in
this
way
and
until
say,
I'm,
a
humanist
more
than
I
am
a
technologist.
A
The
technologies
are
interesting,
I'm
kind
of
turning
into
a
programming
language,
nerd
and
I
blame
rust,
but
I'm
at
the
end
of
the
day,
much
more
a
humanist
I
care
about
rust,
not
just
because
type
systems
are
cool.
They
are
but
fundamentally
in
line
with
other
talks.
We've
heard
today
because
they
help
people
accomplish
their
goals
and
they
help
people
solve
problems,
and
in
this
case
they
help
people
do
that
safely.
That
matters
and
as
software
developers
I
think
we
should
care
about
how
the
tools
we
use
help
us
serve
people
more
effectively.
A
So
it's
not
one
or
the
other,
but
for
me
it's
more
about
the
humanism
so
again
going
back
to
those
two
big
ideas
that
anyone
can
contribute
meaningfully
and
that
people
can
contribute
in
a
stunning
variety
of
ways.
Maybe
let's
mute
that
so
that
I
don't
get
another
text
message
from
a
family
member
do
not
disturb.
A
So
with
that
is
background.
Let's
talk
about
the
talk
for
a
moment,
so
you
know
where
we're
going
because
I'm
going
to
cover
a
lot
of
ground
we've
done
the
introduction
now
I'm
going
to
say:
why
bother
contributing
then
I'm
going
to
say
who
is
a
contributor
anyway,
then
I'm
going
to
ask
what's
a
contribution?
How
do
you
contribute
and
there's
so
many
things
in
that
category
that
they
literally
would
not
fit
on
this
slide
and
still
be
readable,
so
I
didn't
put
them
on
this
slide.
A
Why
and
how
and
hopefully
that'll
give
you
a
way
to
hang
your
hats
on
it
as
we
cover
a
lot
of
material
you'll
also
note
that
I
took
them
out
of
order
to
be
convenient
and
do
what
I
want
so
you'll
have
to
deal
with
that.
Why
should
you
bother
contributing
some
of
us
feel
very
comfortable
just
sitting
and
consuming
the
code,
and
the
answer
I
have
is
that
there
is
more
work
to
be
done.
Then
there
are
hands
to
do
it
and
that's
always
true:
it
doesn't
matter
what
project
you
look
at.
A
You'll
find
lots
of
open
issues
on
git
lab
or
github
or
bitbucket
or
wherever
else,
because
there's
a
lot
of
work
to
be
done,
and
there
are
a
lot
of
things
that
can
be
better
and
that's
always
true
for
any
project.
Any
open-source
maintainer
can
tell
you
the
truth
of
this
I've
done
a
little
bit
of
that
in
the
last
six
months
and
Wow.
There
is
a
lot
to
do
that.
A
I,
just
don't
have
time
to
get
to,
I
would
love
to
help,
and
so
the
people
who
make
the
tools
that
you
use
every
day
could
probably
use
your
help
and
you
can
help
them
more
than
you
think.
So,
then,
if
you're
persuaded
that
yeah
there's
work
to
do,
people
need
help
and
I
really
cut
out
to
be
a
contributor,
but
who
is
a
contributor
anyway?
Is
it
someone
who
has
commitment
and
the
repository?
Is
it
someone
who's
a
glowing
beacon
of
glorious,
open
source
community
work
who
ships
a
billion
lines
of
code
every
year?
A
Someone
who
files
an
issue
instead
of
just
suffering
in
silence
through
that
problem
or
making
a
local
patch.
So
it
works,
but
not
up
streaming
it
like,
even
if
you
have
legal
reasons
why
you
can't
you
know
actually
upstream
a
patch,
you
can
file
an
issue
that
gives
someone
enough
information
that
they
can
solve
it.
That's
contributing
all
of
these
things
are,
and
in
fact
everything
else,
we're
going
to
talk
about
today.
A
That's
what
makes
you
a
contributor
is
anyone
who
improves
a
project
and
I'm,
not
really
exaggerating
when
I
say
that's
how
I
got
started.
You
can
see
here
what
my
first
contribution
to
the
russ
community
is.
This
is
a
commit
to
rust
by
example,
and
there
was
a
copy
and
pasted
example
from
iterator
any
into
iterator
find
and
sorry.
A
This
is
not
rust
by
example,
it's
docs
for
the
api's
and
it
had
the
wrong
word
in
the
description,
so
I
literally
fixed
one
word
in
the
description
and
then
I
got
the
awesome,
rust
high-five
bot
that
came
out
and
said:
here's
we're
so
happy
you're
here
and
it
got
merged
and
I
said:
I
can
actually
contribute
something
to
this
community.
This
is
barely
over
two
years
ago,
I'm
a
relatively
well
known,
voice,
literally
voice
from
the
podcasting
in
the
community.
The
reason
I
felt
like
I
could
do.
A
That
is
because
of
this
commit
I
got
to
contribute
to
rust
and
hopefully
smooth
the
path
for
a
few
people.
Because
of
that
commitment.
So
again,
who
is
a
contributor?
Well,
it's
all
of
us.
If
we
are
chipping
back
in
and
adding
things
and
improving
things
in
the
tools
we
use,
I,
don't
think
most
of
you
who
are
already
open-source
contributors,
probably
have
stories
very
different
from
mine.
You
found
a
small
thing
to
fix
somewhere
and
you
did,
and
now
you
might
be
particularly
skilled
at
that
thing.
A
If
you're
looking
around,
you
might
see
someone
who's
particularly
skilled
at
that
thing,
but
this
is
how
everyone
starts
small,
you
see
a
need,
you
fill
it
and
then,
ultimately,
by
keeping
at
it
for
a
long
time
you
get
somewhere
and
particularly
an
open
source.
When
you
do
that,
you
get
this
feeling
of
helping
people.
That's
good
and
I
think
there's
a
reason
for
that.
We're
meant
as
humans
to
help
each
other
and
we're
broken.
So
we
don't
always
do
that,
but
we
should
aspire
to.
We
should
help
each
other,
it's
good.
A
Sometimes
we
want
to
quibble
with
that
definition,
but
I
think
the
main
reasons
we
tend
to
quibble
are
ego
their
turf
defending
their
wanting
to
prop
up
ourselves
and
make
our
own
contributions
feel
like
the
most
important
or
the
most
valuable
I
like
the
way.
Someone
famous
put
it
in
something
I
read
recently,
which
is
anyone
who
would
be
first
must
be
last
must
be
the
servant
of
all
and
I
hope.
A
I
evinced
that
attitude
and
I
would
encourage
all
of
you
to
have
insight
attitude,
be
servants
of
the
people
around
you
when
we
stop
worrying
about
turf
marking
and
building
up
our
own
prestige
and
start
rejoicing
in
the
ways
that
we
can
help
each
other,
even
if
they
look
and
sometimes
perhaps
especially
if
they
look
different
from
our
own
ways.
Our
projects
get
better
and
in
small
ways,
but
real
ways
the
world
gets
better.
A
The
last
thing
I
hope
this
encourages
you
to
remember:
there's
no
magic
to
being
a
contributor
again
you
just
chip
in
where
you
have
skills
that
can
help,
and
all
of
you
have
skills
that
can
help.
So
what
and
how
can
you
contribute?
This
is
a
very,
very
long
list
and
we're
not
going
to
spend
a
lot
of
time
on
any
particular
detail,
but
I
hope
it
helps
you
come
away
from
here.
Feeling
like
I,
can
do
one
of
the
things
on
this
list.
We'll
start
with
the
obvious
one.
A
You
can
write
code
and
there
are
a
lot
of
ways
you
can
write
code,
you
can
fix
bugs
you
can
implement
features,
you
can
look
for
open
issues
and
go
after
it
and
you
should
write
code
is
fun.
That's
why
most
of
us
are
here
because
we
like
doing
that,
and
we
want
to
empower
each
other
to
do
that.
You'll
find
tags
like
this.
A
So
even
if
it's
your
first
time
contributing
you
look
for
an
e
mentor
tag
or
an
e
ez
tag
on
other
non-core
rust
projects,
you'll
see
things
like
good,
first
issue:
if
you've
never
written
a
line
of
open-source
before
pick
these
go
into
the
mentoring
ones
and
say:
look
I
would
love
to
contribute
to
rust
itself.
Will
someone
teach
me
how
and
it's
got
a
mentor
tag
on
it?
The
answer
is
yes,
we
will
teach
you
how
I
also
want
to
emphasize.
A
We
don't
swear
it
people
or
call
them
names
in
this
community
when
we
make
mistakes,
because
you
know
what
we're
all
humans
and
we
all
make
mistakes
and
it
doesn't
matter
how
long
you've
been
doing
this
I've
been
writing
software
for
about
a
decade.
I
make
mistakes
every
day,
and
we
don't
insult
each
other
over
that
and
that's
a
big
deal
so
don't
feel
intimidated
like
that's
how
it's
going
to
go.
We
want
to
help
you
we've
got
these
tags
here,
because
we
want
to
help
you
contribute.
A
We
want
you
to
recognize
that
you
can
do
this,
but
I'm
going
to
caveat
all
of
that
as
good
as
it
is
by
saying
code
is
not
the
only
thing.
It's
not
even
necessarily
the
most
important
contribution
you
can
make
in
any
given
project.
It's
just
the
most
obvious
one,
because
what
we're
talking
about
is
software,
so
here
are
all
the
other
things
that
you
can
do
to
contribute
and
sometimes
they'll
be
more
important.
I
mentioned
this
earlier.
A
I
opened
this
to
rip
grep
and,
as
it
turns
out,
I've
never
actually
run
into
a
bug
with
rip
grep
I'm
sure
there
are.
Some
I
saw
some
open
issues,
but
I
opened
this
one
intentionally
because
it's
one
that
I've
never
had
to
file
an
issue
on.
But
you
know
what,
if
I
run
into
a
bug
with
rip
grep
well
burnt.
A
Sushi
wants
me
to
file
an
issue
and
tell
him,
so
he
can
fix
it
to
docs
and
we're
gonna
spend
a
little
while
on
this
one,
you're,
probably
as
a
developer,
all
on
board,
with
the
importance
of
documentation,
at
least
in
principle,
because
undocumented
or
badly
documented
projects
are
terrible
to
use.
You
show
up-
and
you
say
what
what
do
I
do
with
this
and
then
you
say
I,
don't
know,
presumably
I
connect
to
a
database
with
it,
but
there's
no
documentation.
A
A
The
code
is
because
it's
all
about
communicating
now
why
you,
rather
than
the
implementer
and
the
answer,
is
that
the
explanation
of
how
things
work
under
the
hood
is
something
an
implementer
is
probably
always
going
to
be
relatively
good
at
they
implemented
it.
They
know
how
it
works,
but
that
doesn't
necessarily
mean
they're
the
best
at
explaining
how
to
start
with
it
because
they
already
have
it
all
in
their
heads.
It
doesn't
necessarily
mean
that
they're
the
best
at
writing,
API
Docs
for
the
same
reason,
learning
materials.
A
For
the
same
reason,
sometimes
someone
coming
in
trying
to
use
the
project
is
actually
better
equipped
to
help
communicate
those
things
because
they're
going
through
the
process
of
learning
it
themselves.
They
know
what
the
pain
points
are.
So
if
you
feel
like
yeah,
bye,
I
have
no
idea
how
to
write
documentation.
Well,
there
are
actually
three
easy
steps
to
write,
good
basic
documentation
for
anything
one
as
you're
going
write
down
the
things
you
don't
understand.
A
Now.
In
the
realm
of
documentation,
there's
a
lot
more
than
API
Docs.
There
are
API
and
we
should
write
those,
and
we
should
be
grateful
that
a
lot
of
Russ
projects
have
API
Docs
and
you
should
turn
on
the
lint
that
will
make
the
compiler
error.
If
you
don't
have
documented
items,
and
then
you
shouldn't
lie
to
the
compiler
by
just
putting
a
documentation
item
on
it,
even
though
it's
empty
document
your
stuff,
please
but
reap
meas,
read
meas
our
documentation
and
they're,
usually
for
people's
first
encounter
with
your
code
tutorials.
A
If
you
can
write
a
good
tutorial
that
shows
someone
that,
even
just
the
very
basics
of
how
to
get
going
with
your
code
base.
That
takes
you
a
long
way
toward
people
being
able
to
actually
build
something
with
it.
Api
Doc's
don't
tell
me
how
to
fit
the
pieces
of
the
API
together.
A
tutorial
does
books,
books
sounds
scary
and
intimidating,
because
they're
long
and
that's
true,
they
are,
they
are
hard.
But
not
every
book
is
the
russ
programming
language
version.
2O
a
lot
of
books
are
much
smaller.
A
I
see
you
looking
at
me
back
there
Steve.
You
can
do
like
Daniel
keep,
did
and
wrote
the
little
book
of
rust
macros
in
rust,
1.0,
that's
a
great
guide.
If
you
want
to
learn
how
to
write
macros,
you
can,
if
you're
sitting
down
and
writing
and
finding
that
you
have
a
lot
to
say
or
an
area
where
there
isn't
a
lot
of
documentation.
A
Finally,
and
this
one's
dear
to
my
heart
and
in
2018
as
part
of
the
push
for
Russ
2019
I'm,
going
to
be
hammering
at
this
chipping
on
the
rust
reference,
there
are
a
lot
of
parts
of
the
language
that
are
only
documented
in
RFC
s.
That
stinks
it's
really
hard
to
know
about
them.
If
you
have
to
go
trolling
through
rfcs
to
figure
them
out
so
chipping
on
things
like
the
rust
reference
and
you'll
find
similar
things
in
other
communities
in
other
projects
in
other
languages.
A
A
Let
me
say
that
backwards.
Most
people
in
the
world
don't
speak
English
and
for
an
awful
lot
of
those
who
do.
English
is
a
second
language
and
it's
a
lot
of
work.
So
if
you
can
provide
a
localized
version
of
documentation,
that's
an
enormous
win.
It
makes
it
far
more
accessible
to
more
people
and
by
the
flipside.
There
are
brilliant
developers
who
speak
every
language,
and
a
lot
of
them
have
to
learn
enough
English
to
get
by.
A
But
look
if
you
speak
amharic-
and
you
know
some
ethiopian
developers
who
are
turning
out
fabulous
libraries
but
they're,
not
that
comfortable,
writing
english
translate
for
them
and
all
of
a
sudden
you're
making
you're.
Taking
advantage
of
the
fact
that
English
is
this
sort
of
lingua
franca
to
popularize
things
out
of
other
language
communities
to
make
them
broadly
accessible.
Those
kinds
of
things
are
huge
and
we
don't
do
enough
of
it.
A
The
language
in
this
slide
is
very
precise
for
a
reason.
I
gave
a
version
of
this
talk
before
it,
and
someone
thought
I
was
talking
about
the
language
design.
I
was
like
no,
no,
no,
no,
the
visual
design
for
a
lot
of
our
things
needs
work.
The
language
design
is
great,
but
the
visual
design
for
things
like
the
landing
page
or
documentation
I
was
having
conversation
with
someone
earlier
today,
who
said
it's
just
kind
of
a
wall
of
text.
A
I,
don't
know
what
to
do
with
it,
because
he
was
just
getting
started
and
I
think
that's
a
feeling.
Many
of
us
have
had
it's
also
a
problem
that
people
are
actively
working
on
Russ
talk.
The
next
is
coming,
but
I
mean
it's
a
lot
of
work
to
do
this
kind
of
stuff,
so
you
can
help
and
you
can
perhaps
especially
help
if
you
have
some
talent
for
visual
design,
because,
let's
be
honest,
most
systems
programmers.
A
Historically,
it's
not
what
they're
interested
in
they're
interested
in
like
how
kernels
work
and
while
there's
sometimes
some
overlap,
that's
not
historically
how
it's
been
likeliest
to
be,
but
we
don't
have
to
let
that
be.
The
final
say.
Carol
said
in
the
keynote
earlier
that
rust
can
be
an
enabling
technology.
I
agree
with
her
about
that.
So
what
we
ought
to
do
is
instead
of
saying
well
or
just
system
programmers
we
don't
care
about
that.
A
We
should
instead
do
what
we
try
to
do
all
the
time
here
and
bend
the
curve
and
make
rust
stand
out
in
this
area.
Make
things
easy
to
access
easy
to
understand.
So
how
do
you
do
that?
Well,
if
you're,
a
person
who
does
actually
have
some
affinity
for
design,
whether
you're
an
expert
who's
coming
in,
because
your
background
was
designed,
but
you
decided
to
switch
careers
and
Russ
looks
interesting
or
you're
just
a
talented
amateur
pitch
in.
We
could
really
use
help
in
this
area.
There's
an
imperial
rust,
2017
project
to
improve
the
homepage.
A
We
need
your
help
if
you've
got
good,
HTML
and
CSS
chops,
please
chip
in
and
if
you're
just
flat
bad
at
design-
and
you
know
what
it's
okay
to
be
just
flat
bad
at
design.
Please
don't
let
that
be
an
excuse
to
put
up
something
in
Times,
New
Roman
with
no
styles,
that's
impossible
to
read,
use
something
like
bootstrap
or
use.
One
of
these
frameworks
I
poked
around
a
little
yesterday,
they're
very
minimal
CSS
frameworks.
Some
of
them
don't
make
you
even
write
any
classes
on
your
HTML.
A
It
makes
it
more
or
less
comprehensible
to
people
so
think
about
how
you
put
stuff
together.
That
will
go
a
lot
longer
and
a
lot
further
than
you
might
realize.
Next,
up,
let's
talk
about
blogging.
I
know
no
one
blogs
anymore.
We
tweet
thread.
Please
blog!
Please,
code
samples,
work,
a
lot
better
in
blogs.
Just
saying
I
know
blogging
feels
hard
to
people,
because
writing
is
hard
work
and
writing
words
to
communicate
to
people
is
not
the
same
thing
as
writing
software,
even
to
communicate
to
other
people.
A
There
are
different
skills,
and
so
this
may
feel
really
hard
at
first,
but
it
doesn't
have
to
be
amazing.
You
can
just
start
and
you'll
get
better
with
practice.
You
may
never
be
TS
Eliot,
but
you'll
get
better
with
practice.
I
want
to
describe
blogging
on
easy
mode,
and
it's
basically
something
I've
already
said,
but
I
want
you
to
take
away
that.
It
really
is
just
this
simple
write
down
what
you're
learning
and
so
that
process
that
you
use
for
writing.
A
Docs
and
sending
pull
requests
is
the
same
write,
a
blog
post
in
which
you
say,
I
didn't
know
this
thing
now,
I
kind
of
know.
This
thing,
here's
my
summary
of
it
and
even
if
you
get
some
friendly
correction
from
people,
you'll
have
helped
others
process
that
same
new
idea
and
you'll
get
some
Google
foo
and
people
will
go
searching
for
answers
to
that.
Question
and
you'll
have
helped
other
people
through
that
process
and
I
want
to
give
you
two
good
examples
to
go.
Look
up
of
totally
different
styles
of
doing
this.
A
One
of
them
is,
and
I
hope,
I
say
her
name
right,
apologies
if
I
don't
vitae,
he
Joshi
who's
written
a
series
called
base
X
on
her
medium
site,
and
this
is
basically
just
introduction
to
concepts
in
computer
science,
algorithms,
data
types
etc.
This
has
been
really
helpful
for
me
in
part,
because
I
don't
have
a
computer
science
background.
I
have
a
physics
degree
I've
learned
this
all
as
I
go.
A
This
kind
of
stuff
is
awesome
for
me
and
it's
very
detailed
and
it's
great
review,
even
if
you
have
a
CS
degree,
but
it's
20
years
old,
also
Julia,
Evans
who's,
probably
the
best.
What
I
just
learned
writer
I
have
ever
read
and
she's
hilarious,
and
she
has
great
comic
illustrations.
You
don't
have
to
be
as
good
as
either
of
them.
A
Suffice
it
to
say,
there's
a
lot
of
ways
you
can
do
this,
you
can
do
one
off
things
or
you
can
write
like
I
did
an
eighteen
part
series
comparing
rust
and
Swift
from
the
perspective
of
a
beginner
at
both
there's
flexibility.
Here
you
can
talk
about
a
particular
technology.
You
can
introduce
it.
You
can
do
a
deep
dive
on
using
it.
You
can
explain
how
it's
built
you
can,
and
this
is
actually
really
really
valuable,
especially
when
you
do
it
kindly.
You
can
critique
and
highlight
problems
with
things.
A
I
know
that
one
of
the
things
that's
been
helpful
for
Tokyo's
iteration
and
its
design
is
getting
helpful,
critical
feedback.
We
need
that.
Nothing
is
perfect
when
we
first
ship
it
so
critique
kindly
with
the
intent
to
help
rather
than
to
beat
down,
we
need
that
you
can
demonstrate
how
to
integrate
different
parts
of
the
ecosystem.
One
of
the
rusts
reach
projects
ended
up,
including
a
blog
post
that
says,
here's
how
you
use
rocket
and
diesel
to
build
a
blog
that
was
great
and
it
answered
questions
I
had
about
how
to
do
exactly
that.
A
You
can
also
use
blog
posts
to
invite
feedback
on
your
own
projects
and
say
here's
something.
I
did
what
do
you
think
and
people
will
give
you
good
input,
one,
that's
very
near
and
dear
to
my
heart,
audio
and
video
people
like
getting
things
in
ways
that
aren't
just
words.
We
need
noises
and
pictures
too
I'm
gonna
talk
specifically
about
podcasts
I
get
critiques,
sometimes,
if
I
just.
Why?
Don't
you
just
write
this
as
a
script
and
for
one
thing
the
scripts
are
out
there,
but
for
another
not
everyone
learns
the
same
way.
A
Some
people
hearing
things
that
makes
it
click
and
also
lots
of
people
have
commutes
and
I
can't
read
on
a
commute.
Now
some
people
can
because
they're
on
a
subway
and
they
can
look
at
their
phone
or
whatever,
but
for
a
lot
of
people
they're
stuck
in
traffic
in
a
car
for
20
minutes,
and
you
can
listen
to
a
podcast
there
too,
which
you
might
say,
but
they're
all
already
podcasts
and
I
would
say.
Yes,
there
are
there's
mine,
but
you
know
what
one
podcast
really
isn't
enough.
A
There's
a
lot
of
stuff
going
on
in
rust.
You
say
yeah
but
look.
There
are
two
there's
also
requests
for
explanation,
I,
say
yeah,
but
really
there's
a
lot
going
on
in
rust.
Two
podcasts
is
not
enough.
Vodcast,
you
say:
look
Jonathan
Turner
just
started
rusty
spike.
There's
three
podcasts
already
and
I
say
you
know
what
these
cover
a
lot
of
ground.
We
need
more
podcasts,
try
doing
tutorials
for
all
sorts
of
things,
try
doing
nan
tutorials,
try
being
the
most
awesome
interview.
Podcasts
there
are
options.
A
Please
podcast
same
thing
with
video
again
people
have
different
learning
styles,
I
heard
often
from
people
that
rails
cast
was
amazing.
This
is
how
I
got
started
with
rails.
We
could
use
Rails
casts
for
rust.
So
if
you
have
skills
with
video,
please
use
them.
We
need
them
and
again
there
are
options
here
you
can
make
screen
casts.
You
can
livestream
yourself
working
on
open
source
shelling.
Griffin
has
done
that
for
diesel
a
couple
of
times
and
it's
neat
pair
with
somebody
and
stream
that
I'm
sure
you
can
think
of
more.
A
The
point
is
make
video
and
share
it
around.
It's
really
helpful
as
a
resource,
and
we
don't
have
a
lot
of
it
for
rust,
yet
not
least
talk
to
people.
You
can
do
that
online,
IRC,
Gitter
discourse,
you
name
it
slack
etc.
Do
it
online
Russ
does
a
lot
of
this,
but
also
do
it
in
person.
Do
it
at
meetups
in
conference,
because
physicality
matters
and
you
all
are
already
persuaded
of
this
you're
at
a
conference.
A
But
if
anyone
out
there
is
watching
online,
be
persuaded
of
this
meetups
and
conferences
helped
a
lot
and
they
especially
helped
a
lot
of
making.
You
feel
like
okay,
I'm,
not
alone,
because
as
great
as
the
internet
is
sometimes
it's
isolating,
go
to
a
meet-up
found
a
meet-up
help
a
meet-up
star
founder.
The
last
thing
I
want
to
say
is
to
those
of
you:
who've
been
doing
this
for
a
while
and
in
the
rust
community.
I
see
this
mostly.
All
of
you.
A
You
can
do
a
lot
more
by
helping
10
people
get
up
to
speed
and
be
productive
than
you
can
yourself,
even
if
you're
one
of
those
magical,
10x,
wizard,
unicorn,
programmers,
the
last
thing
I
want
to
say,
is
when
and
where
do
you
contribute
and
I
want
to
put
this
two
ways?
Where
are
you
in
the
process
of
being
comfortable
with
contributing?
A
Are
you
just
getting
started,
or
are
you
already
comfortable
if
you're
just
getting
started
again,
look
for
these
and
pick
big
projects,
because
they're
the
ones
most
equipped
to
help
new
people
get
started,
believe
it
or
not?
Servo
and
rust.
C
are
probably
easier
places
to
chip
in
in
some
ways
because
they
have
the
in
structure
to
help.
A
You
then,
if
you're
already
experienced
the
website
is
the
case,
find
smaller
projects
and
pick
something
that
just
looks
interesting
to
you,
which
could
use
the
help,
because
you're
going
to
be
able
to
contribute
and
help
with
a
lot
less
of
the
mentoring,
and
you
can
add
the
most
value
there
remember,
there's
always
more
work
than
hands,
so
projects
need
you
and
then
the
other
question
to
ask
is
about
project
life
cycles.
Where
is
a
given
project?
Look
if
it's
a
small
project,
that's
basically
done
pick
something
else
to
work
on.
A
If
something
is
really
solid.
That
needs
a
lot
of
Doc's
right
Doc's.
If
there's
big
projects
which
have
a
billion
needs,
think
about
your
talents
and
the
things
you
enjoy
and
find
a
way
to
chip
in
there
back
to
where
we
started,
anyone
and
I
do
mean
anyone
can
contribute
meaningfully.
I
hope
everyone
in
this
room
running
through
that
list
has
thought
at
least
once
you
know.
That
is
actually
a
thing
I
could
do.
A
Here
are
a
short
list
of
places
that
you
might
go
to
find
more
info
on
places
to
contribute
the
Imperia
Dizz
going
on
right
now
for
rust,
and
it
is
a
great
time
with
a
lot
of
focus
on
people
contributing
so
I
hope
you
go
contribute
if
you're
flying
home
fine
find
a
project
to
see
what
its
state
is
and
maybe
write
some
Doc's
on
the
plane.
Thank
you.