►
From YouTube: Maintaining the Rust Community — Arshia Mufti
Description
While many newcomers to Rust come from a systems background, a significant number of them adopt Rust as their first ever systems programming language. Why is this so? In this talk, Arshia explores the components of the Rust community and ecosystem that encourage participation, the implications of a rapidly growing Rust community, and how we can continue to maintain our accessibility and inclusivity in the face of this growth.
---
Arshia is a wary engineer, an excited conference organizer, a tired student, an enthusiastic Rust community leader, a cautious baker, an avid reader, an erstwhile writer, and a frequent tweeter.
A
A
Events
who
here
knows
what
rust
bridge
is:
oh
wow,
okay,
because
I
had
this
whole
spiel,
but
I,
don't
okay,
I'm,
just
gonna,
say
it
anyways,
so
rust
bridge.
Is
this
all-day
workshop
an
introductory
workshop
to
rust
lank,
and
this
is
geared
towards
people
who
are
underrepresented
in
technology?
So
we
run
these
all
the
workshops
and
get
them
started
with
the
rest
language,
but
also
the
rest
ecosystem
and
I've
helped
run
it
twice
and
I
sometimes
contribute
towards
improvements
in
the
curriculum.
A
You
know
the
challenges
that
we
face
as
these
changes
come
up.
So
that's
what
my
what
my
talk
is
gonna,
be
about,
but
I
want
to
start
off
hang
on
how
do
I
switch
slides,
important
question?
Okay
figuring
it
out,
I
want
to
start
off
with
a
story,
a
story
about
me
and
how
I
got
started
off
in
rust,
so
way
way
way
way
way
back
in
2017
I'm
in
my
20s,
so
2017
feels
like
forever
ago.
A
So
much
has
happened
in
early
2017
I
attended
this
conference
that
was
keynoted
by
Ashley,
who
spoke
at
the
the
keynote
this
morning,
and
she
talked
about
this
teaching
operating
system
called
interim
ethos
or
Intermezzo
s
in
the
spa.
Little
language
called
rust.
I
was
like.
Oh,
this
is
fun
because
at
that
time
I
was
taking
an
operating
systems.
Class
and
I
was
loving,
the
heck
of
it
I.
A
But
the
fact
was
that
C
felt
like
it
was
actively
getting
in
my
way,
like
C
had
this
agenda
against
me
and
she
was
like
no,
you
want
to
learn
about
an
operating
system,
well
sucks
for
you,
because
I'm
just
not
gonna,
let
you
let
you
get
to
that
point,
and
so,
like
I
understood
that
learning,
C
and
learning
assembly
would
be
a
bit
of
a
steep
learning
curve
and
sort
of
I
was
trying
to
figure
out
if
it
was
worth
it
right.
Steep
learning
curves
are
great
because
they
challenge
you.
A
A
It's
just
not
physically
possible
and
and
I
sort
of
explored
beyond
C
2,
right,
I,
looked
into
Linux
and
distributed
systems
and
just
sort
of
all
the
communities
that
sort
of
surround
C
which
are
like
grounded
in
low-level
programming,
and
it
made
me
realize
that
even
if
I
mastered
the
language,
what
would
get
in
my
way
after
that
would
be
the
culture
and
the
environment
that
surrounded
these
technologies
and
I
really
felt
like
I.
Didn't
want
to
fight
for
a
place
in
those
spaces
and
I
think
we
can
all
agree.
A
I'm,
not
really
gonna
try
to
convince
you,
you
can
listen
to
Ashley's
talk.
She
does
try
to
convince
you
a
little
bit
that
a
community
is
centered.
Around
low-level
programming
can
be
pretty
gatekeeping
and
I.
Just
didn't
have
time
for
that.
I
was
like
okay
and
so
I,
like
Chuck
trusts,
into
this
bucket
of
things
like
knitting
and
like
baking,
and
all
the
things
that
I
wanted
to
get
really
good
at,
but
I
was
like
nah.
A
It's
like
just
not
gonna
happen
for
me
and
I'm,
just
okay
with
that
in
my
life,
but
back
to
the
keynote.
So
I
was
listening
to
this
keynote
and
like
looking
up
this
operating
system
and
looking
rust
and
I
thought
this
seems
like
this
could
really
work.
For
me.
It
has
all
these,
like
high-level
constructs
that
I
already
am
familiar
with
that
I
knew
from
other
languages.
That
I
could
see
would
make
me
a
better
programmer.
It
had
this
compiler
that
you
know
said
that
it
would
enforce.
A
You
know
my
invariants
for
me
that
would
provide
sanity
checks
for
me
and
would
really
sort
of
help
me
and
guide
me
as
I
program,
and
it
made
me
feel
like
okay.
This
is
this
is
something
that
I
could
work
on,
but
it
wasn't
easy
right.
Once
I
got
the
basics
down,
it
felt
like
a
really
steep
learning
curve.
A
So
like
it
wasn't
easy
right,
but
this
curve
felt
like
it
was
worth
it
and
the
reason
that
it
felt
like
it
was
worth.
It
was
because
of
the
way
that
rust
was
introduced
to
me,
which
was
that
my
introduction
to
rust
was
was
devoid
of
any
sort
of
expectation
that
I
had
to
have
I
had
to
have
like
programmed
in
some
language
for
some
number
of
years,
or
that
I
needed
some
certain
kind
of
background
to
be
successful
and
rest
sidenote.
The
only
side
note
I
will
ever
make
in
this
talk.
A
I
feel
like
this
idea
that
we
perpetuate
that
to
be
a
successful
programmer,
takes
anything
more
than
just
focus
in
practice
like
you
need
some
inherent
magical
skill
to
be
a
good
programmer
is
one
of
the
most
isolating
scams
in
tech,
its
an
isolating
scam,
no
just
a
scam,
it's
an
isolating
scam,
and
it's
it's
so
awful,
and
we
should
do
everything
we
can
just
sort
of
counter
that
mess.
Thank
you.
A
A
No
I'm
going
to
rant
more
now,
nothing,
you
clap
for
me,
okay,
but
this
was
this
was
my
introduction
to
rest
and
over
the
over
the
next
year,
as
I
talk
to
people
on
Twitter
and
as
I
talked
to
you
know
my
peers,
people
as
respiration
ents
I
learned
that
my
experience
wasn't
that
unique
that
a
lot
of
people
had
this
exact
same
experience
with
rust,
where
they
they
heard
of
it.
They
tried
it
out.
They
picked
it
up,
they
liked
it.
A
They
hit
a
wall,
but
they
wanted
to
keep
pushing
at
that
wall
and
that
really
interested
me
and
I
really
feel
like
for
many
people
who
start
off
programming
in
rust.
I
know,
there's
a
fair
number
of
people
who
are
experienced
and
come
in
from
C++,
because
they've
had
their
fair
share
grief
from
those
languages,
but
a
lot
of
people
want
to
understand
systems
and
they
pick
rust
as
their
first
systems
language.
A
So
two
things
that
really
made
me
want
to
stick
with
rust.
The
first
was
this
idea
that
this
gut
feeling
that
the
rust
community
felt
very
intentionally
constructed
to
be
inclusive
and
and
keep
in
mind.
This
is
like
I,
didn't
know
anyone
in
rust.
At
the
time
all
I
had
was
you
know,
access
to
like
their
github,
their
issue.
Tracker
and,
like
you
know,
any
online
resources
that
I
could
see.
A
I
didn't
personally
know
anyone
in
rust,
but
there
were
so
many
big
and
little
things
about
dress
that
I
encountered
like
the
language
used
in
the
official
book,
the
code
of
conduct,
the
way
that
issue
triage
was
done
and
I
like
used,
Twitter
a
lot
and
so
do
rest
people.
It
turns
out
that
was
like
really
great
for
me,
and
so
all
these
little
things
made
me
feel
like
there
was
a
lot
of
care
put
into
sort
of
the
construction
of
this
community.
A
The
second
was
that
in
2017,
rust
was
kind
of
new,
not
like
super
new.
Like
I
know
it
was
post
1.0,
but
it
felt
kind
of
new
to
me
and
many
communities
are
new.
They
have
a
very
different
kind
of
potential
there
in
this,
like
uncharted
territory,
and
all
these,
like
decisions
have
to
be
made
that
are
hugely
relevant
to
the
future
of
that
community.
And
to
me,
a
community
is
really
all
about
its
people
right.
A
It's
like
so
funny
how
they
open
in
keynote
talked
about
like
being
delivered
and
I
was
like.
Oh,
my
god,
I'm
talking
about
intentional
construction.
It's
like
it's
very
nice.
How
they're
complimentary
in
that
way,
yeah
I
could
see
how
this
like
instinct
I
had
about
intentional
construction
ended
up
being
really
true,
because
this
this
approach
was
baked
into
a
lot
of
the
norms
and
a
lot
of
the
processes
in
the
rust
community
and
just
a
simple
example
of
this
I
think
is
the
RFC
process
and
I
know.
A
A
Like
really
listened
and
really
came
back
and
said,
we
have
this
new
rule
where,
if
we
make
a
decision,
it
will
be
based
off
of
you
know,
public
debate
and
threads
that
everyone
can
see
and
comment
on
and
I
just
thought.
That
was
a
really
really
really
profound
example
and,
as
I
was
researching,
this
more
I
came
across
across
this
quote
on
aaron's
website
and
I'm
gonna
read
the
whole
quote
out
to
you,
because
that
is
how
his
words
should
be
treated.
A
Sometimes
the
rest
community
prides
itself
on
being
a
friendly
and
welcoming
place,
but
it
is
going
to
take
constant,
explicit
work
to
keep
it
that
way
and
part
of
that
work
is
being
forthright
about
the
cases
where
things
have
gone
less
than
friendly
pausing
and
working
together
to
figure
out.
Why
so
the
reason
I
love
this
quote
so
much
yes.
Thank
you.
A
The
reason
I
love
this
quote
so
much
is
that
it
doesn't
even
just
apply
to
the
ihcs
dislike
applies
to
so
much
more
than
it
applies
to
sort
of
the
overall
culture
interest
and
as
someone
who
isn't
like
I'm,
not
on
the
core
team
I'm,
not
in
a
working
group,
I,
don't
I'm
in
school
I'm
like
really
not
contributing
to
rest
open
source.
A
lot
so
I
have
a
very
different
view
of
the
rest.
A
Community
and
I
want
to
argue
that
these
top-level
decisions,
this
approach,
that
you
see
at
the
top
level
of
the
rest
community,
has
this
sort
of
like
trickle-down
effects
that
you
can
see,
and
so
it
has
a
positive
impact
on
the
experience
of
someone.
Who's
only
been
doing
rust
for
a
few
hours
or
for
a
few
days
and
I
think
that's
really
great
about
the
rest
community.
A
But
this
is
only
going
to
get
harder,
not
saying
it
hasn't
been
hard.
Yet
it's
been
pretty
hard,
though
the
whole
keynote
this
morning
was
about
how
things
are
not
easy.
People
are
hard
and
working
with
them
is
like
a
non-trivial
challenge,
but
I
think
that
as
more
and
more
people
start
writing
rust
we're
going
to
face
some
new
challenges.
A
The
first
challenge
has
to
do
with
our
values.
Right,
so
I
feel
like
rust,
has
a
pretty
simple
set
of
values
and
we've
done
a
fairly
good
job
of
like
articulating
them.
At
least
you
know
no
gatekeeping
celebrating
our
differences
instead
of
using
them
as
grounds
for
inclusion,
discouraging
zero-sum
thinking,
encouraging
humility
and
empathy,
and
so
on,
but
I
feel
like
as
the
community
grows.
A
So
what
I'm
really
saying
is
that
our
rust
values
are
like
the
colors
of
skittles
in
this,
like
weird
analogy,
so
the
growth
of
a
community
is
a
great
thing
right,
like
it's
good
that
people
are
adopting
rust,
more
and
more,
but
I.
Think,
along
with
that
growth,
we
have
to
think
about
how
we
are
communicating
our
values,
because
subgroups
and
and
sub
communities
and
pockets
will
inevitably
form.
But
we
really
want
to
do
all
that
we
can
to
make
sure
that
those
pockets
are
grounded
in
these.
A
These
basic
values
of
kindness
and
consideration
and
I
was
talking
about
this
with
with
Minnie
she's,
like
a
lot
of
people.
Have
you
know
brainstorm?
Just
like
talk
with
me-
and
he
pointed
out
that
it's
worth
thinking
about
how
the
rest
community
is
changing
now
as
opposed
to
a
few
years
ago
and
the
rest
community
is
no
longer
just
a
group
of
people
who,
like
really
really
like
memory,
safe
programming,
languages
or
whatever
you
know.
A
It's
a
mature
community
that
plenty
of
businesses
and
organizations
have
you,
know,
derived
value
out
of
like
commercial
value
out
of-
and
this
is
great.
But
this
means
that
plenty
of
newcomers
to
the
language
are
learning
rust.
I
mean
a
lot
of
them,
are
learning
rust
out
of
self-interest,
because
they
really
think
that
you
know
they're
really
excited
by
this
new
model
of
like
memory,
management
or
something.
A
But
a
lot
of
them
are
also
starting
to
program
in
rust
because
they
happen
to
join
a
company
in
which
the
code
base
is
in
rust
or
they're,
starting
to
work
on
a
project
on
you
know
which
is
written
in
rust
and
so
on,
and
this
means
that
it
is
entirely
possible
that
people
who
start
programming
in
rust
will
not
necessarily
aligned
with
our
values
they
might.
They
might
in
fact,
disagree
with
our
values
and
be
like
all
right,
I'm
gonna
program
in
rust,
they're,
not
gonna
care,
etc
and
I.
A
Think
that
has
really
interesting
implications
for
the
composition
of
our
community
moving
forward,
and
it's
just
really
important
to
keep
that
in
mind
and
understand
that
dynamic.
The
second
set
of
challenges,
I,
think
we're
gonna
face.
Is
that
of
diversity
so,
like
I
actually
want
to
want
to
ask
all
of
you?
How
many
of
you
think
that,
with
respect
to
like
other
community
rust
does
like
a
really
good
job
of
encouraging
participation?
A
Yeah,
you
like
I,
do
too
that's
great.
How
many
of
you
feel
like
that's
still
not
good
enough?
Okay,
great
I'm,
really
glad
I
don't
have
to
like
do
the
work.
It's
like
convincing.
All
of
you
and
the
state
of
the
rust
survey
provides
some
pretty
good
data
as
to
this
as
well.
This
is
data
from
2017
and,
according
to
the
the
rust
website,
pretty
much
look
like
this
in
2016
as
well,
and
it's
something
that
you'll
notice.
A
If
you
start
to
attend
a
lot
of
rust
events
which
I
do,
which
is
that
we're
a
pretty
homogenous
group-
and
it
would
be
pretty
unfortunate
if
yours
from
now,
we
continue
to
stay
this
homogeneous
I,
think
that
would
really
upset
me
and
it
would.
You
know
it
wouldn't
make
for
a
healthy
participation,
but
it's
also
useful
to
think
about
like
how
did
we
get
here
like
what
happened
like
we
started
off
like
as
a
little.
A
You
know
what
was
the
keynote
like
in
the
beginning,
there
was
the
void
and
then
like
rust,
happened,
and
then
people
started
joining,
and
how
did
we
get
here
like
n
years
later?
Well,
there's
two
reasons:
I
think
the
first
is
that
rust
is
primarily
a
systems.
Programming,
language
and
systems
has
such
a
legacy.
You
know,
starting
from
like
the
70s
or
the
60s
or
whatever,
and
that
does
tend
to
skew
towards
the
the
white
male
demographic
for
another.
A
A
So,
like
I,
said,
I
run
these
rust
bridge
I've
run
to
rest
bridge
workshops
over
the
past
year
and
something
that
I've
noticed
is
that
a
lot
of
the
people
who
come
to
rest
have
a
significant
amount
of
experience
in
some
other
language
like
Java
or
JavaScript,
and
so
on.
So
naturally,
when
they
start
to
learn
rust,
they'll
try
to
map
what
they
know
in
those
languages
to
rust
and
they'll.
Do
this
even
for
features
of
rust.
You
know
that
don't
necessarily
have
an
analogue
like
the
burrow,
checker
and
so
on.
A
A
Oh,
this
is
the
way
garbage
collection
is,
even
though
you
don't
know
like,
even
though
you've
come
from
like
this
language
that
doesn't
have
garbage
collection
at
all,
and
we
were
talking
about
this
a
few
weeks
ago,
just
before
I
took
a
break
from
the
community
team,
and
we
were
thinking
of
this
idea
of
modifying
the
respite
curriculum,
where
we
have
code
examples
for
concepts
like
enums
and
optionals
and
so
on
in
common
languages.
That
people
typically
know
like
JavaScript
or
Java,
and
we
provide
like
analog,
is
code,
examples
and
rest.
A
When
doing
this,
we
really
recognize
that
they
come
from
a
certain
space
and
that
we're
gonna
use
that
space
to
get
them
started
off
and
rest
some
other
great.
Some
other
and
entry
points
interests
that
have
helped
me
that
I
recommend
to
other
people
are
rust
by
example.
The
second
edition
of
the
rust
book,
which
we
all
know
and
love,
but
they
they
don't
have
to
be
the
only
point
of
entry.
So
so
here
is
my
like
call
to
action
for
all
of
you,
create
your
own
point
of
entry
into
rust.
A
Think
about
how
you
first
learn,
trust
think
about
the
way
that
you
would
have
liked
to
learn
dressed
and
teach
people.
That
way,
and
you
know
you
might
be
thinking
that
the
way
you
would
teach
borrows
semantics
or
the
way
that
you
would
teach
the
difference
between,
sell
and
ref
sell,
would
only
make
sense
to
you
and
maybe
a
few
others.
A
A
So
I
love
conferences,
I
love
them
I've,
attended
them
and
I've
been
really
really
lucky
to
get
to
speak
at
them,
I've
and
seed
them
somehow
and
I've,
even
organized
them
and
I
think
that
conferences
per
have
such
an
incredible
amount
of
value
of
you
know
rust.
My
first
introduction
to
rust
happened
at
a
conference.
Some
of
the
closest
people
that
I
I
know
in
the
in
the
tech
space
I
met
at
a
conference
and
I
also
really
love
small
conferences.
Small
conferences
are
the
best
okay.
These
are
some
of
my
favorite
conferences.
A
This
Bank
Bank
on
on
the
on
this
end,
which
is
a
small
conference,
run
in
New
York
check
them
out.
The
one
at
that
end
is
the
conference
that
I
organized,
which
is
in
Canada
by
the
way
and
the
one
in
the
middle
is
this
conference
called
rust,
felt
rust.
It
runs
in
Ann,
Arbor
Michigan
and
as
someone
who
attends
many
conferences
and
workshops,
and
so
on,
I
increasingly
feel
like
small
and
localized
events
have
their
own
kind
of
power
right,
they're,
less
intimidating
to
newcomers.
A
They
make
it
easier
for
people
to
form
connections
and
make
new
friends
and
to
sort
of
get
to
know
each
other.
It
also
makes
for
a
better
learning
experience
if
all
you're
there
to
do
is
to
learn.
You
know
how
a
certain
technology
works
and
they're
also
less
expensive
to
organize
and
since
they're
less
expensive
to
organize.
That
means
we
can
have
more
of
them,
which
is
great,
because
DAC
events
can
be
pretty
inaccessible.
A
A
It's
it's
reasonable
and
maybe
also
a
little
exciting
to
think
of
how,
in
a
few
years,
rust
conferences
will
be,
you
know,
multi-day
will
have
multiple
tracks
and
that's
like,
like
I,
would
love
to
attend
a
conference
like
that,
but
at
the
same
time,
I
don't
want
to
lose
sight
of
the
fact
that
small
events
like
this
have
an
incredible
amount
of
value
and
I
will
keep
it.
Handing
small
conferences
and
Russ
Bridge
is
a
great
example
of
this,
so
most
Russ
bridges
are
like
under
25
to
30
people.
A
The
first
rest
bridge
I
ran
had
like
five
people,
which
was
like
actually
the
best
and
I
really
think
that
the
power
of
Russ
bridge
lies
in
its
size.
We
usually
end
up
with
a
pretty
high
student
2
to
8
to
TA
ratio,
and
so
the
students
end
up
learning
rust,
but
they
also
really
end
up
engaging
with
these
people.
Who've
been
doing
rust
for
a
little
bit
longer,
they
get
to
hear
from
their
experiences
and
they
get
to
hear
about
the
rust
like
ecosystem
and
the
rest
community
as
a
whole.
A
So
it's
like
it's
not
really
like
rust,
the
language,
they're
learning,
but
it's
rust,
the
community
they're
joining
and
I-
think
that's
so
so
valuable,
and
so,
given
that
Russ
bridge
is
so
impactful
and
given
that
the
best
Rest
bridges
are
small,
the
only
way
to
multiply
the
effect
of
rust
bridges
is
to
run
your
own
brass
bridge.
So
here's
my
second
call
to
action,
or
my
third
I
forget
my
second
probably.
My
second
is
to
run
a
respite
in
your
own
city.
Is
you
know
some
basic,
rust
and
I'm?
A
That
would
be
an
incredible
amount
of
work,
but
I
feel
like
that
would
be
so
impactful
and
so
useful,
so
I
would
I
would
love
to
see
someone
organized
that
another
idea.
I
had
was
a
capture
the
flag
event
in
which,
like
each
challenge,
is
like
a
rest,
related
thing
and
it
doesn't
even
have
to
be
programming
related.
It
can
be
like
what
was
the
create
that
it's
used
for
command
line
argument.
Parsing.
A
So
here's
my
second
call
to
action,
for
you
run
a
rust
event
that
hasn't
been
run
before
think
about
the
kind
of
event
that
you
would
like
to
see,
and
it
takes
some
work.
It
takes
some
effort.
It
takes
some
initiative
to
take
some
some
money.
Oh,
but
I
would
really
love
to
see
more
of
this
happening
and
not
just
like
you
know
in
North
America.
A
But
why
stop
there?
Does
anyone
know
where
I'm
going
with
this
I
hope
you
don't
so
it
wasn't
long
ago
that
I
was
at
a
conference
the
same
conference
where
I
was
introduced
to
rust
by
the
keynote
that
Ashley
gave
and
I
was
like
thinking
about
the
program
and
like
how
I'd
improve
it
and
how
you
know,
I
wish
that
things
were
done.
A
That
way,
and
not
not
that
way
and
I
just
turned
to
my
friends
and
I-
was
like
let's
run
a
conference
here
and
they
were
like
okay
and
a
year
later
we
ran
it
and
it
was
great
and
that's
us
right
there
last
year
and
and
we're
running
it
again
in
2019
of
and
we'll
probably
keep
running
it
a
few
more
times.
It's
called
star
con
by
the
way.
If
any
of
you
are
interested,
but
my
point
is
I'm
not
really
trying
to
plug
stock
on
here.
Our
twitter
handle
is
star
ki,
sio
n.
A
By
the
way,
if
you
want
to
follow
us,
but
it
wasn't
a
lot,
it
wasn't
as
much
work
as
I
thought
it
would
be.
It
was
definitely
a
lot
of
hard
work.
It
required
a
lot
of
outreach,
a
lot
of
initiative,
but
we
got
it
done
and
we
were
all
just
undergrads,
so
I'm
sure
some
of
you
can
get
this
done
too.
So
here
is
my
last
call
to
action,
for
you
run
a
rust
conference,
some
basic
things:
okay,
before
you
like
shake
your
head
to
go
like
oh,
my
god,
she
is
like
a
lot.
A
Some
basic
things
you
need
to
run
a
conference
are
a
name.
It's
easy.
It
doesn't
make
like
more
than
15-20
minutes
to
come
up
with
a
solid
name,
a
team
of
really
excited
organizers
who,
like
you
know
just
as
excited
just
as
excited
as
me
about
conferences,
a
venue.
Where
do
you
want
to
hold
your
conference
and
a
date?
A
So
I
really
want
to
wrap
up
by
saying
that
what
attracted
me
to
rest
was
the
language
like
I
cannot
tell
you
what
I
what
went
through
my
head
when
I
was
like
a
systems
programming
language
with
like
match
statements
like
how
even
this
is
so
amazing.
But
what
made
me
want
to
stay
was
the
community
itself
and
it
requires
a
lot
of
non-trivial
work
to
evangelize
our
core
values
and
then
to
follow
up
that
evangelism
with
concrete
actions.