►
From YouTube: Friday Plenary: Rust and the Community
Description
Dave Herman describes how "The Great Int Debate" taught the Rust team an important lesson in community building on the way to releasing an exciting new systems language.
Help us caption & translate this video!
http://amara.org/v/2Fhq/
B
For
the
last
few
years,
the
rust
team
has
actually
been
doing
just
that
I've
learned
a
lot
from
them.
They've
learned
a
lot
from
the
process
of
building
a
project
built
for
community
built
by
community.
The
cool
thing
is
this
is
not
just
abstract.
This
isn't
just
values
for
us.
Community
is
actually
helping
the
rust
team
win
when,
when
the
rust
project
got
started
at
Mozilla,
when
Mozilla
was
first
interested
in
it,
it
was
really
for
a
pretty
self-serving
internal
goal.
B
We
just
wanted
to
build
tools
to
help
our
C++
programmers
be
more
productive,
but
with
community
we
found
that
there
was
value
that
was
far
bigger
than
just
that
local
goal.
The
community
helped
the
rust
team
discovered
that
rust
wasn't
just
a
better
C++
for
the
C++
Wizards
out
there.
By
eliminating
some
of
the
hardest
pain
points
of
C++
some
of
the
barriers
to
entry.
It
was
appealing
to
JavaScript
developers,
Ruby
developers,
Python
developers.
B
Programmers
were
saying,
I,
never
dared
touch
C++,
but
rust
is
the
first
time
I
feel
like
I
too,
could
do
systems
programming,
so
this
was
powerful
and
inspiring
to
us,
but
that's
also
strategic.
For
us.
That
means
we're
not
just
trying
to
eat
a
small
piece
of
the
pie
that
the
C++
market
has.
It
means
we're
building
an
entirely
new
market
and
it's
actually
working
so
rust.
One
point
o
came
out
this
year
and
we're
seeing
a
tremendous
amount
of
excitement.
There
were
over
a
thousand
community
contributors
to
the
one
point
o
release.
B
B
So
the
rest
community
is
excited,
but
community
is
not
always
easy.
I'm
going
to
tell
you
a
little
story
about
the
great
int
debate
now
I
know
not
everyone
in
this
room
is
technical.
What
this
debate
was
about
was
what
to
name
integers
in
rust,
so
I
think.
Even
if
you're,
not
technical,
you
can
imagine
that
naming
something
that
can't
be
too
deep
of
a
question
right,
that
that
shouldn't
probably
be
the
most
difficult
technical
problem
for
the
developers
in
the
room.
B
They
understand
that
every
developer
loves
to
argue
about
names,
so
it
started
innocently
enough
in
October
of
2013
with
a
bug
on
file.
That
said,
let's
rename
it
to
some
other
names
and
the
core
team
was
busy.
They
were
writing
software.
They
were
trying
to
ship.
They
were
worried
about
market
windows.
They
had
other
fish
to
fry
bigger
fish
to
fry,
so
they
would
periodically
check
in
and
try
to
help
the
discussion
along
and
time
passed
and
people
argued.
B
This
will
want
this
one
on
for
months.
Eventually
it
got
to
the
point
where
the
core
team
felt
like
something
has
to
happen.
We
need
to
help
resolve
this.
So
they
got
together,
they
met,
they
discussed
it.
They
tried
to
come
up
with
some
some
good
rationale
and
they
carefully
wrote
it
right
up
that
they
thought
this
is
a
solid
case
everyone's
going
to
get
this,
we
can
finally
put
this
to
rest
and
move
on.
B
They
posted
this
on
the
rust
discourse
in
December
of
2014,
so
439
days
and
71
comments
later
they're
finally
able
to
put
this
to
bed.
Naturally,
this
is
when
all
hell
broke.
Loose.
I
am
really
disappointed
to
hear
the
core
team
made
a
wrong
decision
of
leaving
in
ten
you
ain't
as
they
are.
It's
a
huge
mistake
that
can't
be
fixed
in
the
future.
B
B
So
why
wasn't
I
consulted
is
a
question
that
I
first
encountered
as
the
the
tagline
of
a
blog
post
by
a
blogger
named
Paul
Ford
in
2011,
and
he
described
this
as
the
fundamental
question
of
the
web.
He
said
the
web
is
fundamentally
about
communities
and
communities
are
about
participation
and
about
being
heard,
and
when
people
start
feeling
like
they're
not
being
heard
that
becomes
a
source
of
almost
all
conflict.
We
ever
see
an
open
source.
B
So
at
this
point
the
team
was
at
a
crossroads.
They
could
go
in
one
of
two
directions.
They
could
say
we
have
stuff
to
do.
We
can't
afford
to
drag
every
single
member
of
the
community
along
every
single
decision,
they're
going
to
have
to
learn
to
start
accepting
our
decisions
and
we're
going
to
have
to
just
start
making
them
faster,
or
we
could
try
to
actually
deal
with
this
and
figure
out.
What's
going
wrong
and
to
their
great
credit,
they
took
the
harder
road.
They
did.
B
A
scary
and
courageous
thing:
they
work
through
this
issue
with
the
community
not
solely
on
the
technical
level,
not
just
discussing
integers.
They
actually
discussed
what's
going
wrong
here.
What's
not
working?
How
can
we
work
more
effectively
together
as
a
community,
and
in
that
discussion
they
synthesized
a
new
rule
that
they
realized
that
they
had
been
violating
an
errant
Iran
of
the
core
team
called
this,
the
no
new
rationale
rule.
What
this
rule
says
is
once
it
comes
time
to
hand
down
a
decision.
B
B
Every
piece
that
goes
into
a
decision
needs
to
be
something:
that's
been
publicly
discussed,
but,
as
we
saw
in
the
gray
tint
debate
that
went
on
for
over
a
year,
if
there
isn't
leadership
there
to
help
provide
alignment
to
help
actually
move
towards
a
common
decision,
it's
never
going
to
go
anywhere.
So,
armed
with
this
knowledge,
the
core
team
did
the
unimaginable.
They
took
the
great
in
debate
that
had
raged
on
for
over
a
year
and
they
started
it
all
over
again.
B
The
thing
is
with
lack
of
engagement
without
community
leadership,
without
an
understanding
of
what
makes
community
stick.
It
took
439
days,
but
this
second
round
by
being
present
by
actually
listening
to
the
emerging
consensus,
helping
articulate
it
back
to
the
community
and
discover
the
shared
values
they
actually
managed
to
bring
this
whole
conversation
to
a
close
in
less
than
a
week,
yeah.
B
And
I
should
mention
the
outcome
was
better
for
the
technical
people.
The
answer
is
sighs
instead
of
int,
and
you
can
see
that
the
community
was
really
happy
not
just
with
the
outcome,
but
with
comments
like
this.
This
was
a
pretty
impressive
example
of
community
and
put
in
collaboration
nicely
done,
and
they
lived
happily
ever
after
seriously.
What
they've
learned
as
a
leadership
team
has
really
been
incredibly
powerful
and
they've
gone
on,
to
have
many
productive,
often
difficult
debates
that
come
to
really
good
outcomes,
so
Tim
berners-lee
the
inventor
of
the
web.
B
He
knew
this
too.
He
knew
that
this
wasn't
just
about
values
that
this
stuff
actually
works.
What
he
said
was
had
the
technology
of
the
web
in
proprietary
and
in
my
total
control
it
would
probably
not
have
taken
off
well.
The
web
took
off
and
the
good
news
is
rust
is
taking
off
too.
So
it
I
believe
that
what
the
rust
team
is
doing
with
community
and
with
leadership
is
actually
a
game
changer
for
how
open
source
can
work,
and
my
challenge
to
all
of
you
is
to
try
it
too.
Thank
you
very
much.