►
From YouTube: RustFest Rome 2018 - Alan Kavishe & Lee Baillie: Increasing Rust's Reach Project Highlight
Description
In our new "Project Highlight" keynote format we selected an important, interesting and successful projects/initiatives and invite their leaders & contributors to talk about their work, experiences, and the things they have learned along the way to benefit the larger Rust community.
In Rome Alan Kavishe and Lee Baillie will be presenting the Increasing Rust's Reach (http://reach.rust-lang.org/) project highlight.
https://rome.rustfest.eu/sessions/project-highlight
https://media.ccc.de/v/rustfest-rome-11-project-highlight
A
Hi
there
how's
it
going.
We
are
here
to
tell
you
about
the
increasing
rusts
reach
program.
I'm
lee
Bailey
I
used
they/them,
pronouns
and
I'm.
Currently,
a
web
developer
at
Tilda
in
Portland
Oregon
in
the
United
States
I've
attended
almost
every
rest
fest,
except
for
the
first
one.
I
spoke
at
roast
fest
Kiev
and
I
attended
the
Paris
Zurich
and
now
Rome.
So
it's
really
awesome
to
be
here
again.
I
was
a
rust
reach,
participant
in
the
first
iteration
in
2017
and
in
2018
I
returned
as
a
partner,
Allen,
hello.
B
Everyone,
my
name,
is
Allen
I
participated
in
Russ,
tweets
2018.
That
was
this
year
for
those
of
you
who
don't
remember
and
I'm,
currently
a
full-stack
developer
in
South
Africa
doing
front-end
and
back-end,
even
though
I
live
in
Namibia-
and
this
is
my
first
West
fest,
my
first
trust
conference,
my
first
software
conference
ever,
but
it
will
not
be
my
last
back
to
Lee.
A
And
she
first
talked
to
you
right,
yeah,
a
lot
of
firsts.
So
what
is
the
increasing
Russ
reach
program
or
rust?
Reach
which
we
call
it
for
short,
increasing
rusts
reach
is
one
of
several
programs
run
by
the
Russ
programming
language
team
to
grow
rusts,
community
of
project
collaborators
and
leaders.
A
The
program
matches
Russ
team
members
from
all
parts
of
the
project
with
individuals
who
are
underrepresented
in
rusts
community
and
the
tech
industry
at
large,
for
partnership
of
three
months
from
mid-may
to
mid
agrees
to
a
commitment
of
three
to
five
hours
about
every
week,
working
on
a
Russ
project.
So,
unlike
a
traditional
mentor,
mentee
relationship,
we
refer
to
the
groups
of
people
in
the
program
as
partners
and
participants
which
reinforces
the
fact
that
we
believe
the
project
has
an
equal
amount
to
learn
from
participants
as
they
have
to
learn
from
partners.
A
So
a
typical
week
will
include
a
one-hour
meeting
with
your
Russ
partner,
a
one
hour
weekly
sharing
meeting
with
a
larger
group
of
pro
program
participants
and
a
few
hours
of
pairing
or
in
two
work
on
your
specific
project.
So
since
partners
and
participants
are
distributed
all
over
the
world
a
lot
of
the
time,
these
weekly
meetings
will
happen
two
times
to
account
for
all
the
different
time
zones.
A
Ashley
was
the
one
who
ran
their
weekly
meeting
most
of
the
time
and
she
often
arranged
for
guests
to
come
and
speak
to
all
the
participants
participants
about
their
role
in
the
RUS
community,
which
was
really
awesome
best
of
all.
By
way
of
thanks
for
participating
in
the
program,
they
offer
a
fully
paid
conference
to
get
travel
and
accommodations
to
every
participant
to
a
one
Russ
conference
of
their
choice.
So
I'm
just
curious.
Does
anybody
here
from
Russ
reach,
or
anybody
come
here
on
Russ
reach
ticket
at
all?
A
There
were
a
lot
of
changes
from
the
first
to
second
year
of
rust
reach,
since
it
was
kind
of
a
big
experiment.
The
first
year
was
a
lot
more
freeform.
Our
partners
and
participants
largely,
would
choose
how
they
wanted
to
approach
the
project
and
they
organized
they
organized
it.
However,
they
wanted
the
only
real
initial
requirement
was
you
have
to
do
like
three
to
five
hours
of
work
on
your
project
every
week
and
you
have
to
check
in
with
your
partner
at
like,
whatever
intervals
you
design
on.
A
So
some
of
the
big
changes
in
2018
was
that
actually
took
over
the
bulk
of
organizing
I
think
the
original
organizer
was
Carol.
She
added
weekly
group
meetings
with
the
time
zone
options
with
guest
speakers.
Everyone
checked
in
with
her.
Every
week
she
made
sure
everything
was
running
smoothly.
Every
time
they
were
hiccups,
you
would
like
work
to
smooth
them
over.
So
basically,
you
know
the
biggest
difference
between
2017
and
2018
was
Ashley.
B
B
I
ran
across
it
a
couple
of
years
back
and
I
thought
it
looked
pretty
cool
at
least
I
look
better
than
C++
at
the
time
we
didn't
have
a
use
case
for
it,
so
the
best
I
could
do
was
follow
a
couple
of
people
on
Twitter
and
star
a
couple
of
github
repos,
and
thanks
to
that,
I
came
across
an
invitation
for
applications
to
rust
reach
on
my
Twitter
I
thought.
What
is
this
thing?
B
I
applied
immediately.
The
application
itself
is
quite
nice.
The
questions
generally
just
try
to
figure
out.
Are
you
using
rust?
Would
you
like
to
use
rust
where
you
come
from?
What
can
you
bring
to
the
table
as
a
participant
in
this
project
and
do
you
have
the
time
to
do
three
to
five
hours
a
week?
I
did
have
a
time,
so
then
I
was
one
of
the
few
lucky
ones
that
got
in
I
did
not
expect
that
happen,
but
it
happened
so
then,
after
that
actually
reached
out
to
us
via
email
and
got
everything
started.
B
So
at
the
beginning,
we
still
had
to
figure
out
how
we're
going
to
communicate.
I
didn't
know
anything
about
the
2017
or
us
to
reach
project.
So
for
me,
the
whole
concept
of
a
conference
being
conference
type
project
being
run
from
America,
while
I'm
South,
Africa
and
participants
are
from
Japan
and
Australia
and
whatever
it
seemed
really
like
a
logistical
nightmare,
but
I
actually
sorted
that
out
in
one
email
and
everything
worked
perfectly
after
that.
So
the
first
thing
they
did
was
give
us
our
project
assignment.
B
So
part
of
the
application
was
a
list
of
projects
that
we
will
be
doing
this
year.
A
trust
reach
and
the
list
included,
I
think
Lee
already
mentioned
a
couple.
Claps
Eli
was
an
and
so
on.
So
you
had
to
choose
a
couple
that
you
were
interested
in
and
once
you
got
into
the
project
they
assigned
you
to
one
of
these
groups
and
I
got
assigned
to
the
Clapp
group
working
with
Kevin
Knapp
who's.
B
One
of
the
few
exceptional
programmers
I've
met
and
it's
been
lots
of
fun
working
with
him.
So
once
I
got
into
my
project,
the
next
meeting
was
to
meet
up
with
Kevin.
So
myself,
Kevin
and
other
participants
in
our
group
met
up
with
him
and
we
just
sort
of
had
a
first
meeting
to
get
to
know
each
other
who's,
Kevin
who's,
Alan
who's.
This.
What
have
you
been
doing
with
rust
and
if
nothing,
what
do
you
want
to
do
with
rust?
B
B
We
get
straight
into
the
work
for
the
project,
so
the
first
month
of
the
project
was
mostly
us
just
getting
our
feet.
Wet,
rust
and
the
rest
of
the
project
was
the
actual
work
for
us
treats
that
we
needed
to
do
and
for
myself,
Kevin
decided
that
we
are
gonna,
try
and
get
clap
to
Version
three,
and
he
had
two
major
things
you
want
to
deal
with.
One
was
yeah
Mille
parser,
so
for
those
of
you
have
used
clap.
B
You
know
that
one
way
of
entering
your
arguments
is
via
a
llamo
file
and
we
wanted
to
move
that.
To
start
using
sterday
yeah
Moe
rather
than
Yammer
rust,
that
was
our
initial
plan
and
we
got
to
a
point
where
we
had
to
stop,
because
one
of
the
ways
that
surly
reads
the
m-files
wasn't
really
compatible
with
what
Kevin
wanted
to
happen
when
it
comes
to
crap
reading
the
file
and
since
we
couldn't
fix
it
on
our
side
was
sort
of
an
issue
in
the
dependency.
B
So
in
amo
we
decided
to
let
it
rest
for
now,
so
I
don't
think
it's
been
changed
yet.
So,
if
any
of
you
is
expecting
that
we're
using
survey
ml
in
version
3,
we
probably
aren't
for
the
second
attempt.
We
decided
to
jump
into
the
other
thing
that
Lori
was
talking
about
today
and
that
is
struct
opt,
so
they
have
been
for
a
long
time.
B
Clap
and
struct
opt
as
the
two
libraries
for
augment
parsing
reinstructive
just
builds
on
top
of
crap
and
adds
prop
macro
to
do
all
the
work
for
you
and
Kevin
spoke
with
the
person
who
wrote
struct
up
and
they
decided
it
would
make
sense
to
merge
the
proc
macro
into
crap
if
possible.
So
that
was
our
second
task
and
I
never
used
the
prop
macro
at
all.
I've,
never
seen
the
code
for
a
block
map
read
obviously
never
debugged
a
prop
maker
either.
B
So
this
was
a
hugely
new
experience
for
me,
but
thankfully
I
had
wanted
two
hours
every
week
sitting
with
Kevin
on
video
chat
with
code
open
and
he
would
walk
through
the
code.
I
would
actually
drive
and
he
would
say,
okay
jump
to
this
file
and
in
this
file
is
this
going
on,
and
this
is
what
happens
when
this
changes
and
so
on
and
so
forth.
So
it's
a
huge
learning
experience
for
me
and
it
also
gets
Kevin
himself
to
think
about
his
code
as
he
writes
it.
B
So
a
lot
of
we
had
quite
a
bit
of
refactoring
happening
just
because
Kevin
couldn't
easily
explain
what
was
going
on
here
or
there,
and
so
together
we
got
through
quite
a
bit
of
the
code
up
until
one
point
where,
while
we
were
missing
a
comma
which
happens
all
the
time
and
finding
a
comma
in
a
macro
is
a
problem,
we
use
a
lot
of
cargo
expand
that
didn't
really
help.
It's
a
great
tool,
though
fantastic
tool,
but
in
our
case
it
didn't
help
a
little
after
a
bit
of
checking
out
github
code
and
water.
B
We
found
the
comma.
We
deleted
it
and
yeah
everything
tests,
past
goals,
achieved
and
yeah,
so
I
think
we
have
a
working
derive
for
clap
now,
which
might
be
in
version
3,
so
you
might
not
have
to
use
drop
table.
Maybe
I,
don't
know,
after
that,
we
had
we
kept
having
these
meetings
that
actually
every
week
and
at
the
end
of
everything,
was
mostly
just
a
winding
down.
So
for
me,
what
was
rust?
Fest
increasing,
rust
reached
2018?
B
Sorry,
it's
a
fantastic
way
to
build
this
community
there's
a
lot
of
people
who
would
never
have
got
an
interest
that
were
there
and
I
know
quite
a
few
people
that
I've
spoken
to
about
this
and
they're
really
excited
about
rust,
even
though
they
are
never
used
it
before.
So
that
I
think
is
a
great
thing
about
increasing
rust
reach.
It
was
extremely
well
organized
and
handled
right
from
the
very
first
application,
all
the
way
up
until
the
very
last
meeting.
B
It
was
fantastic
for
me
at
least,
and
I
think
it
was
so
for
all
the
other
people
who
were
involved.
I
would
like
it
to
be
a
bit
more
public
during
the
project.
There's
not
a
lot
of
people
outside
of
the
project
that
could
follow,
along
with
what
we
were
doing
and
I
think
that
would
be
better
just
for
the
communities
as
a
whole
and
again
because
I
liked
it
so
much
I
want
more
people
to
experience
it.
B
A
A
The
first
round
in
2017
and
I
was
chosen
to
work
on
redesigning
rustling
org
with
another
participant
overall
I
had
a
positive
experience,
but
if
I'm
being
honest,
since
it
was
the
first
iteration
of
the
program,
it
was
a
little
bit
rocky,
it
seems
like
your
experience,
really
depended
on
who
your
partner
was
and
how
much
structure
they
put
on
it
and,
in
my
case
there
just
wasn't
really
that
much
structure
beyond
like.
Oh,
we
want
a
new
design,
but
I.
A
A
I
learned
a
lot
because,
in
spite
of
my
background,
I
actually
had
never
built
a
website
from
scratch
from
the
ground
up,
so
that
was
kind
of
cool
to
experience,
even
though
the
none
of
the
work
that
I
did
during
that
time
ended
up
getting
used
for
anything.
I
was
still
really
useful,
because
I
learned
a
huge
amount
of
stuff.
A
My
name
and
I
look
different,
but
like
not
that
different,
so
I
already
been
involved
in
the
rest
community
before
I
was
in
Russ
reach
I
had
spoken
at
Rose,
fest
Kiev,
so,
like
some
people
knew
me,
but
it
wasn't
really
that
short
like
it
was.
It
was
very
nerve-wracking
showing
up
to
that
Rose
fest,
so
I
knew
the
community.
You
know
wasn't
that
diverse.
A
In
spite
of
all
you
know
our
best
efforts,
so
I
really
wasn't
sure
how
it
was
gonna
go
or
how
I,
if
I'd
feel
comfortable,
but
I
ended
up
meeting
a
bunch
of
other
people
who
were
also
participants
who
turned
out
to
be
other
members
of
underrepresented
groups,
and
it
was
one
of
the
best
parts
of
the
conference.
For
me.
A
So
as
I
mentioned
in
2018,
the
rest
reach
program
made
some
big
changes.
Some
of
the
organizers
switched
hands
and
the
program
became
a
lot
more
structured.
This
time
around
I
also
made
the
switch
from
being
participant
to
partner
and
I,
had
two
really
talented
designer
slash
developers
working
with
me
to
implement
a
new
design
for
the
rest,
Lang
worksite,
which
is
obviously
not
like
out
there
yet.
A
But
I
can't
speak
for
the
participants,
obviously,
but
for
me,
I
tried
really
hard
to
ensure
they
had
a
positive
experience
and
I
used
my
time
as
a
participant
in
2017
as
a
model
for
what
not
to
do,
which
is
like
still
worthwhile.
So
I
thought
about
all
the
things
I
wished.
I
had
and
I
just
tried
to
make
those
things
a
reality
for
them.
So
some
things
that
were
important
to
me
were
to
set
out
achievable
goals,
make
sure
I
was
extremely
communicative,
make
sure
to
give
feedback.
A
A
My
biggest
advice
from
my
experience
as
a
partner
to
other
people
who
maybe
are
working
with
people
who
are
underrepresented
or
just
like
really
shy
or
maybe
not
very
confident,
which
is
the
experience
I
had
with
my
participants,
is
that
you
cannot
be
too
nice.
You
cannot
be
too
friendly
anytime,
you
feel
inclined
to
reach
out.
You
should
reach
out.
A
You
should
check
in
on
people
and
see
how
they're
doing
and
just
be
proactive
about
offering
to
help
or
to
pair,
if
they
don't
feel,
if
you
seem
like
they're,
not
making
a
lot
of
progress.
Don't
expect
that,
just
because
they're
quiet
that
they're
fine,
you
know
a
lot
of
the
time
people
get
blocked
by
things
that
are
more
psychological
than
skills-based.
At
least
in
my
experience
with
my
participants,
they
were
really
talented.
They
were
capable
people,
but
they
would
just
psych
themselves
out
of
things
because
they
just
didn't
have
a
lot
of
confidence.
A
A
It
was
just
really
like
magical
to
watch
them
experience
that
so
anyway,
if
you
want
to
find
out
more
about
the
rest
reach
program,
you
can
check
out
the
site
at
reach,
rusts
lang,
org,
and
if
you
know
anyone
who
might
benefit
from
participating
in
the
program
they
don't
already
have
to
know
rust.
You
can
feel
free
to
send
them
a
link
to
the
site
and
encourage
them
to
apply
the
next
time.
Applications
are
open.