►
From YouTube: Foundation Conversation - Live Broadcast 1
Description
Members of the Rust Core team will be discussing the upcoming Rust Foundation and questions we've been fielding from the community during the Foundation Conversation Q&A sessions.
A
Hello:
everyone-
this
is
the
rust
core
team
starting
the
first
live
broadcast
of
the
foundation
conversation
so
first
off.
I
want
to
kick
off
by
thanking
everyone
for
being
here
and
answering
all
or
asking
all
of
your
questions.
It's
been
great
to
give
that
feedback
and
narrow
in
on
some
of
our
thinking.
A
As
we
sort
of
announce
all
of
this-
and
the
first
thing
I
want
to
do
is
talk
about
sort
of
where
you
can
find
all
of
the
details
here.
So
we
have
the
project
sort
of
repository,
which
is
the
foundation
faq
repository.
Actually,
is
there
a
chance?
We
could
get
a
link
on
somewhere.
A
While
we
get
the
technical
details
here
figured
out,
I
want
to
give
us
a
chance
to
introduce
ourselves,
so
I
am
mark.
I
am
on
the
court
team
and
release
team
and
I've
been
sort
of
helping
out
with
some
of
the
communications
around
this
effort.
Nico.
C
Hi
so
yeah,
I'm
nico
mutsakis,
I'm
on
the
core
team
laying
team
and
compiler
team.
I've
been
helping
set
up
the
foundation
and
I've
been,
you
know,
involved
in
rust
for
a
long
time
now
going
since
2011
so
been
a
while.
C
Group
in
particular,
maybe
that's
what
you're
looking
for
and
I
and
yeah
that's
that's
what
I'm.
B
B
Hi
I'm
ashley
williams.
I
I'm
on
the
ros
core
team.
I've
been
a
member
of
many
teams
over
the
years,
but
at
this
point
my
role
on
core
takes
up
almost
all
of
my
time,
and
I've
also
been
working
on
the
at
the
rust
foundation
project
group.
A
Okay,
well,
I
don't
know,
I
guess
we
can
get
started
so
the
first
thing
I
want
to
do
is
ask
ashley.
So
a
lot
of
people
have
been
sort
of
interested
in
this.
What
is
the
foundation
for?
What
are
we
doing?
Why
are
we
even
you
know,
setting
up
a
foundation?
Who
are
we
doing
it
for
so
I
you
know-
and
let's
talk
about
that-
I
guess
let's
start
off
with
sort
of
this
more
broad
question
of.
Why
are
we
setting
up
a
foundation.
B
Well,
there's
there's
a
lot
of
answers
to
that
that
involve
many
strange
things
that
happened
over
the
course
of
2020,
but
I
I
think
that
the
the
really
positive
answer
here
is
rust
is
growing
really
really
rapidly
and
we've
kind
of
gotten
to
the
point
where
it's
it's
time
for
us
to
kind
of
own,
our
own
independent
kind
of
structure,
and-
and
this
is
this-
is
partially
because
you
know
we're
seeing
a
lot
of
attention
from
a
lot
of
folks
wanting
to
to
use
rust
and
we're
because
of
our
team
structure,
we're
like
incredibly
large
and
distributed
set
of
teams
that
kind
of
management
and
operations
necessary
for
the
type
of
project
like
for
us
is
just
incredibly
huge,
and
so
I
I
don't
know
if
this
is
perhaps
what
you're
getting
at.
B
But
from
this
you
might
gather
that
we
are
not
setting
up
a
foundation
to
drive
adoption
of
rust.
We
we
have
the
really
lucky
problem
that
rust
is
getting
adopted
completely
on
its
own,
and
so
the
real
goal
of
the
foundation
is
to
help
the
project
cope
with
that
exponential
growth
and
adoption.
C
D
C
I
think
one
of
the
things
I'm
really
excited
about
with
the
foundation
is
we've
seen
a
lot
of
adoption
of
rust
and
what
I'm
really
excited
to
see
is
have
us
go
from
a
phase
of
companies
using
rust
the
companies
getting
involved
in
us
at
a
deeper
level
right
and
that's
been
happening
kind
of
slowly
slowly.
Slowly
and
I
think
we're
going
to
see
it
pick
up
a
lot
with
the
foundation
and
I'm
pretty
excited.
I
think
that's
going
to
bring
a
lot
of
you.
D
C
Lot
of
lots
of
things,
a
lot
of
resources,
but
a
lot
of
people
and
a
lot
of
interaction
and
more
collaboration,
and
I
think
it's
gonna
be
good
for
us.
A
Yeah,
so
to
lead
up
on
sort
of
follow
up
on
that
sort
of
a
lot
of
us
have
been
on
the
project,
and
I
know
myself
thinking
sort
of
how
is
this.
You
know
big
effort
going
to
touch
on
my
work
in
the
project
and
I'm
wondering
ashley.
If
you
can
sort
of
talk
a
little
bit
about
how
sort
of
the
individual
people
working
in
rust
and
sort
of
making
pull
requests
or
translating
or
moderating
and
sort
of
all
the
great
work.
Those
teams
do
what?
What?
What
can
they
expect.
E
B
Well,
I
think
it's
interesting.
It's
definitely
not
going
to
be
like
the
flick
of
a
light
switch
right
like
it's
not
going
to
be
like
we've
incorporated
a
foundation
and
then,
like
everyone
goes,
oh
and
it's
like.
Suddenly
I
don't
know
everything
that
we
type
is
covered
in
glitter
or
something
I
mean.
That's
not
that's,
not
a
bad
idea
actually
I'll
I'll
pose
that
to
the
foundation.
B
Yeah,
we
just
got
to
send
glitter
bombs
to
all
of
the
the
two
maintainers,
but
I
I
would
say-
and
I
I
think
to
any
of
the
maintainers
out
here
listening.
I
think
I
think,
over
the
particularly
the
last
two
to
three
years
as
as
rust's
community
has
grown
tremendously.
B
B
The
cost
of
that
value
is
something
that
we've
been
feeling
pretty
hard,
and
it's
it's
tough,
because
it's
hard
when
something
that
you
like,
really
love
so
much
kind
of
ends
up
hurting
you
and-
and
so
I
think,
what
we've
seen
with
our
maintainers
is
that
they're
really
feeling
this
really
classic
kind
of
asymmetrical
power
structure
that
open
source
shows
up,
which
is
that,
to
a
certain
extent,
success
can
lead
to
like
some
really
intense
failure.
B
Failure
moments,
because
you
can
end
up
with
so
many
more
users
and
you
have
maintainers
and,
and
so
what
I
would
say
is
as
you've
been
working
on
rust.
You
have
almost
certainly
been
feeling
some
pinches
as
as
you've
been
participating
and-
and
I
think
it's
really
the
goal
of
the
foundation
to
help
us
identify
those
pinches
and
and
try
to
alleviate
them.
This
is
a
a
very
blunt
kind
of
example,
but
you
know
I
I
think
we've
talked
about
having
rfcs,
with
with
300
comments
on
them
and
we
go.
B
Oh,
my
goodness
300
comments
on
an
rfc
and
I
go
with
the
way
we're
seeing
russ
grow
today,
like
we're,
going
to
end
up
with
an
rfc
with
3
000
comments
and
we're
not
we're
not
ready
to
handle
that,
and
I
don't
want
our
maintainership
to
have
to
handle
that
with
no
resources
on
its
own,
and
so
I'm
I'm
really
excited
because
I
think
figuring
out
how
to
scale
that
open
consensus
like
value
in
rust,
is
like
really
going
to
be
one
of
the
biggest
charges
of
the
foundation.
A
I
know
I'm
excited:
do
you
want
to
talk
about
some
of
these
pinches,
that
you've
been
feeling
and
how
excited
you
are
about
getting
them
solved?.
C
C
One
thing
that
people
ask
for
a
lot
when
they
come
to
contribute
to
the
compiler.
The
first
thing
they
notice
is
like.
Oh,
it
takes
a
really
long
time
and
stuff
like
that,
and
they
notice,
yeah
or
or
or
it
takes
a
lot
of
memory
and
things
like
that
and
one
of
the
things
we've
picked
around
is
I
wonder
if
we
could
set
up
like
some
way
to
help
people
get
bills,
and
I
don't
know
if
we'll
do
that
in
the
foundation
or
not,
but
it
seems
like
with
a
foundation.
C
We
can
have
that
conversation
and
we
can
start
looking
around,
for
maybe
you
can
do
cloud
builds
or
something
like
that
right.
But
that
kind
of
thing
is
like
the
obvious
level,
and
I'm
I'm
pretty
excited
about
it.
I
think
we're
going
to
probably
find
a
lot
of
those
little
things
we
can
do
with
resources
that
we
didn't
have.
That
will
make
a
big
difference.
C
What's
going
to
be
a
little
bit,
the
next
level
up,
let's
say,
is
really
focusing
on
the
pathway
from
beginning
contributor,
all
the
way
up
to
like
sort
of
team
lead
or
whatever
and
and
seeing
at
each
point
in
that
step,
are
there
kind
of
organizational
things
we
can
do
or
blockers
we
can
remove
that
were
that
were
limiting
us
before
and
it's
something
we've
we've
put
energy
into,
but
I
think
we
found
it
hard
to
keep
that
sustained
focus,
and
I
think
the
foundation
will
help
us
do
that
and
I'm
pretty
excited,
I
think
that's
gonna,
be
like
I.
C
I
keep
having
the
feeling
that,
with
all
the
excitement
and
all
the
people
who
are
coming
in
to
rust,
we
if
we
can
find
ways
to
kind
of
capture
more
of
that
and
take
advantage
of
more
of
that
we're
going
to
be
able
to
do
a
lot
of
stuff
and
that
that's
sometimes,
I
feel
like
we
lose
some
of
it
on
the
side.
So
we
just
can't
get
it
organizationally
together
to
take
advantage
of
people
and
they
wind
up
getting
frustrated.
A
A
So
ashley
one
thing,
I'm
wondering
sort
of
nico
has
talked
about
how
we
can
sort
of
utilize.
This
infrastructure-
and
I
think
we
sort
of
have
talked
a
little
bit
about
sort
of
the.
I
don't
know
more
mundane
infrastructure,
but
one
thing
we
haven't
really
touched
on
is
sort
of
the
more
human
side
of
like.
A
B
I'm
just
imagining
like
a
parachute
that
has
the
rust
logo
on
it
and
it's
like
really
good,
like
a
maybe
even
a
ferro-shaped
parachute
that
sounds
awesome.
Someone
who's
a
balloon
maker,
get
on
that.
But
yeah
I
mean
the
the
metaphor.
The
core
team
often
uses
in
their
rust
comp
keynote
is
like,
like
people
systems
like
we're
people
systems
programmers
to
a
certain
extent,
and
I
think,
to
the
same
way
that
we
can.
B
We
can
look
forward
to
the
foundation
being
able
to
to
to
be
able
to
you
know,
support
and
and
produce
some
some
infrastructure
that
is
sorely
needed
for
maintainers.
I
I
also
when
I
think
about
the
sk,
the
sheer
scale
of
the
people.
We
have
there's
also
a
fair
amount
of
people
infrastructure
that
I
think
would
really
benefit
from,
and
so
one
of
the
effects
of
the
extremely
distributed
team
structure
that
we
have
that.
I
think
a
lot
of
people
don't
think
about
a
lot
is
because
we
have
so
many
independent
teams.
B
That
means
that
the
rust
organizational
structure
actually
demands
significantly
more
contributors
that
are
managers
than
ever
like
in
in
many
open
source
projects
and
being
a
manager
is
a
real
skill.
You
can't
just
kind
of
like
wake
up
one
day
and
do
it
I
feel
like
management
is
kind
of
like
design
and
teaching
where,
like
kind
of
at
first
glance,
you're
like
oh,
I
could
probably
do
that
and
then
you
start
doing
it
and
you're
like.
B
Oh,
my
goodness,
there's
a
lot
of
subtlety
here
and
so
as
as
we
continue
to
think
about
having
to
to
scale
the
growing
rust
project.
B
I
I
we
see
a
lot
of
people
stepping
up
into
leadership
roles
and
they
kind
of
step
up
into
like
a
void,
and
I
I
think
that
it
would
be
really
helpful
if
there
was
more
of
a
like
a
guided
moment
where
we
could
offer
leadership,
training
management,
training
and,
and
like
also
just
resources
for
for
helping
manage
these
things
from
basic
things
like
project
management,
to,
I
think,
potentially
more
interesting
things
if
you
think
about
like
product
management
management
and
like
even
design
work
like
there's,
there's
a
lot
of
really
fascinating
organizational
research
out
there
about
how
to
do
that
and
well.
B
B
I
I
look
forward
to
one
being
able
to
bring
in
sponsors
who
have
like
a
depth
of
knowledge
there
that
we'll
be
able
to
learn
from,
but
also
just
to
be
able
to
gain
resources
and
and
help
to
distribute
those
to
to
the
folks
that
are
kind
of
find
themselves
as
the
leader
in
a
way
that
they
might
not
have
expected.
C
Yeah
I'll
chime
in
and
say
one
of
the
things
that
you
made
me
think
of
there
actually
is
in
the
compiler
team.
You
know,
we've
set
up
a
bunch
of
working
groups
and
so
on
and
one
of
the
observations
we
made
kind
of
coming
at
the
I
don't
remember
when
this
was
last
time
we
we
had
like
a
retro
or
something
we
were
discussing.
C
What
the
what
was
our
experience
and
and
one
of
the
biggest
problems
was
yeah,
basically
being
the
lead
of
a
working
group
is
really
hard
and
that
there
was
just
you
know:
it
takes
a
lot
of
energy,
of
course,
and
and
keeping
on
top
of
things,
but
also
that
there's
a
need
to
kind
of
guide
people
and
give
them
more
structure
of
how
to
do
it
of
how
you
know
help
maybe
help
to
break
down
well.
This
is
the
task
you
want
to
achieve.
C
Another
thing
that
I
was
just
thinking
about
is
that
I
think
would
be
great
is
getting
you
know
this,
this
product
management
that
you
mentioned,
getting
help
in
kind
of
assessing
people's
needs
and
making
sure
we're
doing
a
really
good
thorough
job
of
that.
So
we
can
figure
out
what
to
prioritize.
C
C
E
C
I'm
I'm
talking
about,
so
what
am
I
talking
about?
I'm
talking
about
all
the
needs.
I
think
we
should
assess
everyone's.
I'm
talking
about,
I
think
maintainers
could
use
help
in
assessing
users
is
actually
what
I'm
saying.
So
there
is
a
maintainer's
need
at
the
root
here,
but
it
is
related
to
end
users
and
things
like
that
as
well.
So
I
think
we
we
do
things
like.
We
use
the
survey
and
well
anyway,
we
have.
We
make
a
lot
of
attempts
and
we
do
really
work
at
it.
A
So,
along
those
lines
of
sort
of
survey,
work
and
and
others
sort
of
figuring
out
how
do
end
users
fit
into
the
foundation
and
and
there's
this
question
to
some
extent
of
sort
of
we're
focusing
so
much
on
maintainers
and
and
maintainers
definitely
want
to
focus
on
end
users
too.
A
But
I
think
at
least
for
me
one
of
the
questions
I've
had
is
sort
of
how
do
we
fit
this
structure
of
maintainers,
focusing
on
end
users
and
foundation
and
sort
of
what
is
the
relationship
we're
looking
there
for,
especially
as
we
think
about
sort
of
our
purpose
being
maintainers,
but
then
sort
of
feels
like?
A
Why
are
we
focusing
on
maintainers
and
users
right?
We
want
to
drive
people
to
be
enthusiastic
about
rust,
not
not
about
rust
development.
So
much.
B
Yeah
it,
it
definitely
could
seem
maybe
somewhat
backwards
to
have
a
foundation
that
is,
is
focused
on
the
maintainers,
like,
maybe
not
even
backwards,
maybe
even
worse,
like
maybe
selfish,
like
oh,
the
rust
project
wants
to
create
a
foundation
for
itself,
and
I
I
know,
at
least
for
me,
like
part
of
this,
is
motivated
by
what
I've
seen
as
as
trends
kind
of
in
what
I'd
call
like
the
economics
of
open
source
where
there
there's
these
these
affordances
for
expectations,
where
in
in
many
circumstances,
like
especially
I'd,
say
like
commercial
software
like
the
users
are,
are
often
the
the
least
well-served
constituency
they're,
given
the
the
least
power,
the
least
visibility,
and
I
I
would
say
in
open
source,
open
source
maintainers,
don't
really
hit
the
top
of
the
list
for
any
of
those
things,
either
and
and
part
of
that's,
because
many
people
have
kind
of
aliased
open
source
to
be
free
and
there's
there's
like
just
an
expectation
that
the
project
is
there
and
it's
there
for
the
taking
and
that
those
people's
time
they
they
owe
you
like,
they
owe
their
users
stuff,
and
so
there
there's.
B
That
kind
of.
In
the
background,
there's
been
some
some
really
interesting
writing
on
it.
I
think
nadia
engball
kind
of
bringing
about
like
the
the
un
unspoken
infrastructure
of
open
source,
but
I
don't
know
there's
some
stat
about,
like
most
people
maintain
open
source
out
of
guilt,
and
I
think
that
that's
like
just
really
really
sad
and
I
gotta
be
honest.
B
I
have
absolutely
felt
that
way
before
and
and
what
I
realized
is
that
with
foundations,
if,
if
the
goal
of
the
foundation
is,
is
to
to
support
adoption
and
support
end
users,
there's
there's
a
weird
distrust
there,
whereas
we
need
an
organization
to
center
the
users
and
tell
the
developers
what
to
do
and
that
I,
I
think
that's
just
not
really
aligned
with
rust
values
at
all.
B
I
think
that
I
think
that
if
we
keep
the
folks
who
are
working
on
rust,
well
resourced,
well
supported
and
happy
they're
gonna
build
the
best
rust
for
end
users.
That's
possible,
and
I
don't
think
a
separate
organization
is,
is-
is
going
to
to
really
be
able
to
move
the
needle
on
that.
I
think
the
folks
that
are
are
working
on
the
projects
really
understand.
B
The
problems
and
are
incredibly
motivated
to
build
something
that's
powerful
and
ergonomic,
and
that
what's
really
just
getting
in
their
way
is,
is
are
these
systems
that
that
I
mean
these
systems
that
that
make
their
job
incredibly
difficult
to
do
because
they
are
but
one
person,
and
there
is
an
intensely
large,
growing
number
of
people
using
rust.
So
to
kind
of
balance
that
equation,
I
think,
having
the
foundation
on
those
folks
side
is,
is
going
to
be
how
we
end
up
with
with
the
absolute
best
trust.
A
C
Curious,
the
answer
is
largely
no,
but
we're
not
the
the
role
of
foundation
is
not
to
directly
hire
people,
let's
say
to
hire
everyone
who
works
on
rust
and-
and
we
there's
a
lot
of
reasons
for
this
I
mean,
I
think,
a
big
part
of
it
is
we
we
just
couldn't
do
a
very
good
job
like
there's
a
lot
of
people
working
on
rust
and
it
would
take
a
lot
of
managerial
infrastructure
and
it's
it's
a
hard
thing
to
to
hire
and
really
maintain
someone
very
well
right
and
what
we
would
do.
C
A
much
better
job
of
doing
is
incentivizing
people
who
work
like
companies
that
rely
on
rust
and
helping
them
and
getting
them
to
hire
developers
and
support
those
developers
which
they're
already
geared
up
to
do
right,
and
I
think
that
has
a
side
benefit,
which
is
that,
where
rust,
how
rust
will
work
best?
How
open
source
works
best
in
my
opinion,
is
when
you
have
kind
of
a
lot
of
companies
coming,
not
just
companies
really
a
lot
of
people
and
contributors
from
different
backgrounds,
which
may
include
companies
coming
together
to
work
and
solve.
C
We
did
that
because
we
knew
that
we
needed
input
from
all
kinds
of
people
if
we're
going
to
make
these
designs
good
or
else
they're,
just
going
to
be
tailored
to
like
the
side
of
the
problem
that
you
see
you,
the
youth
designer
and
not
the
other
constraints
that
you're
not
aware
of,
and
I
think
if
we
tried
to
just
pay
everyone
from
one
central
source
that
would
step
right
into
that
trap,
not
to
mention
that
it
just
wouldn't
work.
It's
not
to
say
we.
D
C
D
C
C
A
tool
that
everyone
uses,
but
yes,
we
will
be
picking
and
choosing
very
carefully
the
rules.
I
think
that
make
the
most
sense
for
the
foundation
to
do
specifically.
B
Yeah,
I
want
to
go
back
to
the
thing
that
you
touched
on
about
incentivizing
companies
to
to
hire
folks
who
are
working
on
rust.
So
one
of
the
things
that
you
see
a
lot
when
an
open
source
technology
starts
getting
really
popular
is
so
you
start
out.
You've
got
a
programming
language,
there's
kind
of
the
early
adopters,
the
early
hackers
that
are
like
getting
really
into
it,
working
directly
on
it
and
slowly.
That
becomes
something
that
that
folks
are
really
excited
about,
and
companies
start
going.
B
I
want
to
write
my
software
in
this
and
they
go
who
better
to
write
this
software
than
the
person
who
wrote
this
language.
That
would
be
a
really
great
idea,
and
it
is
a
really
amazing
idea,
but
what
can
happen
if
you're?
Not
careful
is
that
then
all
the
people
who
are
working
on
the
language
suddenly
head
on
out
to
all
of
these
companies
to
work
on
that
product
and
there's
nobody
left
working
on
the
language.
B
B
Instead,
I
think
that
that's
really
difficult,
and
so
I
I
think
it
is
the
the
russ
foundation's
responsibility
and
and
the
folks
who
are
participating
in
it
to
make
sure
that
we're
able
to
keep
working
on
rust
itself,
not
working
in
rust
and
a
really
attractive
option,
because
I,
what
you'll
often
see
is
you
you
have
that
that
language
everybody
leaves
to
go
work
in
that
language
and
then,
eventually,
that
language
starts
kind
of
losing
that
awesome
value
that
made
everybody
want
to
write
stuff
in
it.
B
In
the
first
place-
and
so
this
is
really
a
critical
moment
to
like
make
us
like
that-
we're
we're
to
pass
like
we're,
really
gonna
need
to
figure
out
how
to
do
that
retention,
and
I
think
it's
really
interesting
but,
like
I
see
it
as
one
of
the
the
most
important
roles
for
the
foundation
to
really
focus
on
making
sure
that's
the
case
and
and
if
it's
not
we're
going
to
fix
it.
C
B
Yeah,
I
I
I
it's
speaking
to
the
rust
community
out
there.
I,
I
don't
think
you
know
how
intimidating
to
a
certain
extent,
you
are
you're
like
the
the
values
driven
like
community
that
we've
built.
I
folks
really
respect
it
and
they
are.
They
are
they're,
they're,
they're,
cautious
about
making
sure
they
participate.
They
really
want
to
make
sure
that
we
preserve
it
as
we
go
through
this
kind
of
like
next
moment
for
rust.
A
Now
so,
we've
talked
quite
a
bit
about
sort
of
the
more
concrete
benefits
in
some
sense,
but
we
haven't
really
talked
or
a
lot
about
the
sort
of
shape
of
how
the
foundation
is
going
to
maybe
influence
decisions
or
sort
of
make
changes
in
the
project
and
sort
of
the
systems
like
if
I'm
a
maintainer.
Who
do
I
go
to?
How
do
I
make
this?
You
know
proposal
or
whatever
nico
do.
C
There's
not
that
much
to
say
I
mean
I
think
the
foundation
is
there
to
support
this
teams
that
we
have
built
not
to
sort
of
replace
them
or
change
the
way
that
they
work
right.
It's
not
going
to
change
the
way
the
rfc
process
works,
so.
C
I
I
think
yeah,
like
certainly
like
technical
decision
making,
but
not
just
technical,
just
the
decision
making
the
teams
have
been
doing
stays
with
the
teams,
but
what
they
now
have
that
they
didn't
have
before
is
kind
of
more
more
resources
that
they
can
draw
on
right
and
they
have
a
new,
a
new
kind
of
way
to
enable
them,
and
I
think
that
you
know
exactly
how
much
and
how
we
lean
on
it
will
depend
team
to
team
and
it's
something
we're
going
to
be
figuring
out.
B
Like
russ
has
built
out
a
really
fantastic
set
of
governance
and,
honestly,
with
my
experience
with
foundations
and
boards,
like
a
a
single
board
on
a
foundation,
wouldn't
be
able
to
make
all
the
decisions
that
the
rust
project's
able
to
make
like
if
it
meets
like,
say
once
a
month,
even
like
the
number
of
decisions
that
our
our
governance
is
making
due
today.
Even
if
we
were
to
somehow
decide
that
we
wanted
that
to
happen,
I
I
think
it
would
be
impossible.
B
So,
but
that's
that's
really
not
the
the
type
of
decision
making
that
that
that
the
foundation
will
be
making.
I
think
instead,
it's
gonna
be
a
lot
more
about
thinking
about.
How
can
we
make
strategic
investments
in
in
the
organization
so
that
that
that
folks
can
feel
like
that?
Contributing
to
rust
is,
is
improving
and
is
is
like
a
joy.
I
think,
as
nico
likes
to
say,.
C
E
B
Yeah
I
mean,
I
guess
one
thing
I
feel
like
nico
and
mark
can
be
like
ashley.
Why
are
you
doing
this
here?
Okay,
I'll,
do
I'll
just
do
it
yeah.
I
know
right.
So
one
of
the
really
interesting
things
about
our
extremely
distributed
governance
system
is
that
decision
making
is
a
is,
is
again
distributed
to
a
large
number
of
teams
and
and
the
strength
of
rust
is
in
the
strength
of
those
teams
and
and
as
we
scale
and
as
we
see
adoption
of
rust.
B
I
I
think
that
we've
already
been
feeling
pressure
on
that
governance,
and
so
I
think,
if
you
want
to
be
worried,
I
think
the
thing
to
be
worried
about
is
not
necessarily
that
the
foundation
is
going
to
take
things
over,
but
that
rus
governance
is
not
going
to
have
the
support
and
the
resources
it
needs
to
be
able
to
scale
to
the
amount
of
people
that
are
are
coming
in,
like
one
of
the
things
that
open
source
projects
usually
like
to
see
is
like.
B
Oh,
my
gosh,
like
let's
get
more
and
more
contributors,
let's
see
that
contributor
graph
go
up,
and
I
have
to
assume
that
if
I
were
to
show
a
graph
like
that,
there
would
be
a
not
insignificant
number
of
our
maintainers.
Who
would
go?
B
Oh,
my
goodness,
and
that's
really
too
bad,
because
I
think
in
our
hearts
we
really
want
contributing
to
recipes
something
that
everybody
can
do,
but
our
current
governance,
structures
and
management
structures
are
are
really
not
ready
to
be
able
to
like
handle
that
influx
yet,
and
so
what
I'm
really
looking
forward
to
is
getting
to
a
place
where
we
can
beef
up
is
a
horrible
metaphor
for
someone
who
is
vegetarian
to
say
and
but
I
feel,
like
we've
been
using
a
lot
in
the
core
team
lately
I
don't
know
who
started
that
but
anyways
like
really
looking
to
to
mature
our
our
governance
process.
E
D
B
What
I'm
trying
to
say
is
that
the
the
the
chronic
problem
that
we
should
be
worried
about
when
we
think
about
decision
making
in
the
rust
project
is
I
or
the
thing
that
we
should
be
worried
about,
is
not
the
idea
that
the
foundation
is
going
to
decide
to
introduce
a
new
keyword.
It's
that
our
our
governance
structures
are
not
going
to
scale
at
the
rate
that
they
need
to
and
mature
in
a
way
that
will
be
able
to
maintain
our
values,
and
so
I
feel
like
everyone's
going
to
be
like
ashley.
B
B
How
are
we
gonna,
keep
these
teams
operating
and
and
give
them
the
capacity
that
they
need
for
like
the
next
five
years
of
rest,
and
so
that's
why,
when
I
think
about
decision
making
the
foundation
doesn't
make
me
as
scared,
because
I
see
it
as
a
way
to
help
us
solve
the
other
problem.
I'm
worried
about.
D
C
C
A
rising
and
growing
challenge,
I
think
it
is
something
I
mean
it's
a
place.
We
put
a
lot
of
energy
and
we
will
continue
to
do
so
and
I
think
we're
making
a
lot
of
progress
at
adapting
our
processes
to
the
to
the
sort
of.
C
Maybe
it's
just
my
my
perspective
where
I'm
coming
from,
but
I
like
the
part
of
russ
that
I'm
working
on
the
most,
but
I
feel,
like
you
know,
for
one
thing:
as
the
margin
as
rust
is
getting
more
and
more
used
in
production,
we
have
to
kind
of
ensure
we
keep
the
quality
higher
on
a
constant
basis
and
we
have
we
have
to
meet.
C
We
have
to
make
sure
we're,
considering,
as
we
are
designing
these
newer
features
and
so
on,
like
taking
into
account
all
the
different
ways
people
might
use
them.
I
think
the
async
design
is
a
good
example.
It
just
had
an
enormous
number
of
constraints
trying
to
be
met.
It
was
very
complicated,
a
long
time
and
had
a
lot
of
back.
C
That
that
was
a
big
challenge
that
really
that
I
think
we
we
met
very
well,
but
that
was
harder
than
other
kinds
of
designs.
We've
had
to
do
where
we
were
smaller
and
had
been
able
to
move
more
nimbly.
B
Yeah,
I
think
that
makes
sense
as
as
we
think
about
like
making
rust
ergonomic,
like
I
always
say,
like
ergonomics,
is
familiarity,
and
so,
as
the
user
base
of
rust
grows
and
diversifies,
and
the
types
of
things
that
people
are
using
rust
for
grows.
The
number
of
constraints
on
designs
like
that
are
going
to
become
more
and
more
complex,
and
so.
A
D
A
Well,
definitely,
an
interesting
area.
I
guess
one
thing
that
I'm
sort
of
wondering,
as
you
say,
sort
of
this
async
problem
and
and
sort
of
going
in
that
direction.
I
know
that
we
have
sort
of
a
number
of
sort
of
features
in
the
language
pipeline,
but
there's
also
this
aspect
of
sort
of
rust
community
at
large
and
sort
of
how
we're
thinking
about
sort
of
conferences
and
all
of
these
people
who
are
forming
meetups
and
and
so
forth.
A
I'm
wondering
actually,
if
you
want
to
talk
about
sort
of
how
we're
thinking
the
foundation
is
going
to
interact
with
you
know
a
community,
that's
literally,
and
probably
at
this
point
every
country
in
the
world.
You
know
thinking
about
rust
or
even
meeting
and
and
so
forth.
B
My
first
thought
was:
is
antarctica
a
country
anyways.
If
someone
has
brought
russ
to
antarctica,
please
tweet
at
me,
but
yeah.
So
I
think
something
that's
really
exciting
about
rust
is
like,
as
as
a
project
kind
of
without
its
own
legal
entity.
It
it
has
already
built
out
the
functionality
that
is,
is
often
kind
of
like
the
first
task
of
like
a
early
open
source
software
foundation.
So
I
I
think
this
kind
of
comes
from
the
fact
that,
from
early
on
I
don't
know
the
origin
of
this,
maybe
nico
you
do.
B
But
there's
always
been
this
thought
that,
like
we
treat
rust
like
a
product,
and
so
unlike
maybe
other
groups
of
engineers
like
marketing,
was
less
of
a
bad
term
for
us
and
it's
something
that
we
kind
of
actively
leaned
into,
and
I
think
those
kind
of
early
attitudes
helped
shape
like
I
would
just
I'd
say,
like
a
really
mature,
particularly
events
ecosystem
that,
like
I
guess,
the
foundation
could
events,
but
we
really
don't
need
that.
I
mean
I
russ
fest
just
announced
it's
its
own
organization
to
help
incubate
and
run
events.
B
I
I
won't
summarize
that
more
because
I
don't
want
to
get
it
wrong,
but
check
out
check
out
the
new
russ
fest
initiative
that
they're
doing,
but
we
we've
seen
so
so
many
independent
conferences
pop
up-
and
I
mean
even
some
of
the
meetups-
that
we
have
that
call
themselves
meetups,
like
probably
shouldn't,
because
they're
on
the
scale
of
like
more
than
100
people
attend.
So
these
are
like
these
are
basically
mini
conferences
that
people
are
calling
meetups
and
I
think
I
think,
trying
to
make
a
foundation.
B
The
foundation
at
least
the
way
I
would
hope
to
see
it
would
be
a
player
in
the
community
right
like
there's
a
large
ecosystem
of
rust
and
like
the
foundation
is,
is
but
a
part,
and
so
when
I
look
to
how
how
the
the
foundation
might
might
support
a
community
like
I
I
I'm
recalling
I
I
don't
know
if
it
was
an
all
hands
or
an
impul
days,
but
yeah,
I
remember
being
in
in
the
mozilla
office
in
paris
and
folks
from
the
event
team
were
running
kind
of
like
a
teach,
the
teachers
event
except
it
was
for
event,
organizers,
and
I
I
think
things
like
that
are
really
critical.
B
I
know,
as
a
teacher
myself
like
teach,
the
teacher
events
are,
are
such
you
know,
force
multipliers,
and
so
I
think,
instead
of
necessarily
seeing
the
foundation
spin
up
its
own
events.
Potentially,
I
I
definitely
see
it
doing
more
of
the
facilitation
like
treating
our
community
members
like
the
maintainers
they
are
and
helping
facilitate
their
ability
to
to
do
the
knowledge
sharing
that
they've
been
doing
over
the
past
couple
of
years.
A
Yeah,
so
to
follow
up
on
that,
I
know
we've
sort
of
talked
a
little
bit
about
this
before,
but
one
of
the
things
that
we've
sort
of
been
thinking
about,
especially
this
year.
I
know
we
didn't
manage
to
run
a
all
hands
and
and
sort
of
there's
lots
of
reasons
for
that,
and
in
some
sense
it
was
actually
good
because
you
know
it
was
scheduled
for
when
the
pandemic
was
already
sort
of
in
in
high.
A
C
Oh,
I
I'm
kind
of
excited
about
this.
I
have
to
say,
because
one
of
the
things
that
came
out
from
the
all
hands,
the
fact
when
it
didn't
happen
was
disappointing,
but
it
was
also
a
moment
where
we
we
spent
a
little
time
thinking
about.
Like
you
know
next
year,
we
should
think
about
what
the
all
hands
like
ought
to
look
like.
C
Actually
because,
as
you
know,
as
ashley
was
saying,
like
rust
has
been
growing
and
growing,
and
it's
not
clear
whether
the
all
hands
as
it
was,
is
exactly
the
right
structure
as
we
get
larger
and
larger.
Maybe
we
want
to
have
more
targeted
ones.
Maybe
we
want
to
do
different
formats.
No,
no.
I'm
excited
to
see
us
experiment
here
a
little
bit
and
try
different
things.
C
I
think
it's
really
critical
that
we
introduce,
let's
say
more
in
high
bandwidth,
sync
modes
of
interaction
for
the
teams,
and
I
don't
know
at
what
point
like
whether
that's
going
to
be
flying
to
the
same
place
or
you
know.
I
don't
know
that.
There's
a
lot
of
question
marks,
but
I'm
really
excited
about
doing
that.
But
I
think
we
should
look
and
experiment
with
exactly
what
that
actually
means.
It
may
not.
A
B
B
If,
if
I
got
to
decide
what
the
board
did
in
some
magical
world
where
that
might
happen
like
when
I
was
evaluating
a
proposal
like,
I
would
just
continue
to
ask
myself
the
question
like
how
does
this
help
maintainers
do
their
job
better,
and
so
I
I
definitely
think
something
that
could
would
definitely
help.
B
Maintainers
is
like
being
able
to
help
support
them,
particularly
like
I
think
that
the
high
bandwidth
like
high
sync
communication,
as
someone
who
has
probably
been
like,
I
like
working
remote
forever,
it's
so
critical-
and
I
think,
especially
over
this
year,
like
we,
we've
really
felt
felt
that
pain
of
just
like
missing,
that,
like
social
touch
from
folks
and
the
these
teams
are,
are
solving
really
high
problems,
hard
problems,
and
I
think
it's
important
that
that
folks
have
like
a
social
connection.
B
So
I
I
could
imagine
that
those
things
would
be
in
scope
like
really
just
if
you
ask
yourself
like.
Does
this
help
maintainers
get
their
their
work
done?
That
would
be
that's
at
least
the
first
bar
in
my
mind,.
C
Yeah,
I
think
I'm
thinking
about
how
I
don't
know.
I
think
something
like
I
think.
We've
talked
about
doing
things
like
supporting,
maybe
helping
conferences
to
organize
adjacent
events,
and
things
like
that.
That
might
be
an
interesting
way
to
go.
I
don't
I
I,
when
we've
done
that,
I
think
it's
always
been
really
great.
So
it's
something
I.
B
E
C
You
know,
I
think,
can
I
say
that
we
were
talking
earlier
about
that
conversion
up
the
ladder
and
so
forth,
and
I
think
what
sometimes
that
is.
It
is
easier
to
help
pull
someone
along
when
you
have
just
just
some
face
time
to
get
to
know
them
better
and
like
pay
them
concentrated
attention.
So
if
we
can
do
more
to
enable
that,
I
think
it'll
be
really.
C
A
Yeah,
I
I
mean
I
would
love
more
sync
time
with
all
of
core.
At
least
I
know
that
much
and
you
know
everybody
on
the
rest
project
is
really
great
to
spend
time
with.
I
have
fun
memories.
D
C
D
E
B
B
B
A
Yeah,
so
I
guess
sort
of
as
as
we
close
out
sort
of,
we
have
roughly
15
minutes
left.
So
I
want
to
pivot
a
little
bit
to
sort
of.
We've
talked
a
lot
about
how
maintainers
and
towards
the
beginning,
we
talked
a
little
bit
about
how
sort
of
we
see
maintainers
being
empowered
to
do.
You
know
better
work
or
sort
of
more
work
in
some
sense
and
more
maintainers,
giving
us
a
better
access
to
a
better
us.
A
A
So
I
I
don't
know
yeah.
I
guess
I
guess
to
get
back
to
this
idea
of
sort
of
empowering
maintainers,
giving
us
a
better
rest
being
able
to
do
more
for
our
sort
of
primary
constituency
of
the
foundation.
A
One
of
the
things
that
I
think
we
sort
of
have
talked
a
little
bit
about,
but
haven't
talked
a
lot
about,
is
sort
of
if
I'm
an
average
rest
user.
Maybe
I've
never
contributed
a
patch
sort
of
what
kind
of
help
are
we
looking
for?
What
are
we
looking
for
from
people
in
you
know
this
week
and
in
the
coming
weeks?
A
A
C
B
How
how
can
folks
help
out
with
the
foundation
everybody
who's
been
asking
really
thoughtful
questions
on
the
github
repo?
I
think
that
that's
been
really
helpful
like
because
of
that
we've
been
able
to
draft
an
faq
that
I
think
is
has
turned
out
much
better
than
if
we
had
sat
down
to
write
it
with
like
just
a
blank
page
and
we're
like
what
do
we
think
people
want
to
know.
B
So
I
know
it
sounds
like
extremely
cheesy,
probably,
but
like
keep
asking
questions
like
it
is
actually
incredibly
helpful
and
then
yeah
like
as
far
as
it
like
helping
with
the
foundation.
Long
term
goes
like.
I
don't.
B
I
don't
think
that
we,
we
know
yet
really
like
what
those
opportunities
might
be,
but
what
I
would
expect
is
that,
like
the
foundation
is,
is
going
to
be
working
on
initiatives
that
are
going
to
be
with
the
project
and
so
just
participating
in
rust
and
having
a
desire
to
make
rust
better
and
wanting
to
show
up
and
invest.
Time,
like,
I
think,
that's
probably
the
best
way
to
help
like
at
the
end
of
the
day.
B
B
B
E
C
I
think
this
this
last
point
that
ashley
was
raising
is
really
good
right,
and
it's
like
that
that
we
want
to
have
kind
of
the
foundation
and
the
project
working
together
and
it's
not
like.
There
are
two
separate
entities
each
going
their
own
way,
so
you,
but
you
maybe
become
a
contributor
to
the
foundation
or
something
it's
like
they're
working
on
shared
goals
like
the
when
the
project,
and
so
when
you
want
to
get
involved
in
rust.
C
C
Right,
I
don't
know
how
visible
exactly
we'll
see,
but
that's
the
way
we
should
think
about
it.
B
E
B
I
don't
want
us
to
have
necessarily
any
dead
air.
I
can
ask
you
mark
being
rmc.
What
are
you
most
excited
about
for
the
foundation
like
personally
personally.
A
I
think,
honestly,
with
my
like
infra
hat
on,
I
think
the
most
exciting
thing
for
me
is
for
people
to
like
actually
give
us
a
budget
and
like
hold
us
to
it.
I
know
that
sounds
probably
very
weird
and
like
it
seems
weird
that,
like
we
want
limits,
but
I
know
that
a
lot
of
my
work
has
been
sort
of
designing
various
systems
around
rust
and
like
especially
as
we
work
on
like
the
perf,
collector
and
sort
of.
A
We
need
this
dedicated
hardware
being
able
to
sort
of
figure
out
like
how
do
we
get
it
and
who
do
we
go
to
to
even
ask
for
you
know,
budget
or
grants
or
whatever
has
has
been
really
difficult
and
sort
of
as
a
another
part
of
that
being
able
to
do
things
like
run
surveys
more
often
to
sort
of
figure
out
like
what
is
actually
the
thing
that
users
want.
A
We
run
a
yearly
survey
and
that's
like
really
amazing
data,
but
it
is,
you
know
once
a
year
and
has
steadily
been
growing
for
from,
like
maybe
20
questions
at
the
beginning.
Now
I
think
we
have
probably
hundreds
of
questions
just
across
like
multiple
different
instantiations,
so.
D
C
I
I
I'm
actually
really
excited
about
this
kind
of
data
collection
resources.
I
think
there's
one
thing
I
I
know
on
the
survey.
Interesting
feedback
was
like.
Basically
someone
saying
that
we
should
doing.
C
One
big
survey
is
really
great,
I'm
glad
we
do
it,
but
we
should
also
consider
doing
more
like
targeted
surveys,
and
I
think
that
is
an
interesting
thing
to
pursue
for
one
thing
as
well
as
data
to
crunch,
but
you
know
just
to
look
like
I'd
like
to
follow
up
on
the
survey
and
say:
oh,
this
was
an
interesting
data
point.
Can
we?
What
can
we
do
to
understand
better
like
why
people
gave
that
thing
7
out
of
10
or
something?
C
And
that's
a
that's
a
really
interesting
thing,
and
I
don't
know
it's
been
hard
to
follow
up
on
those
kind
of
ideas.
I
think
we'll
have
more
room
for
that.
One
thing
I
do
wonder
about,
I
don't
know
if
you've
ever
talked
about
this,
but
I'm
curious
is
also
like
studies,
because
we're
going
off,
we
got
the
last
five
minutes.
We
might
as
well
go
off
script.
C
Script,
I
know
we've
been
on
script,
the
whole
time,
people
user
studies-
like
I'm
interested
in
what
more
we
can
do
to
to
see
sort
of
people
using
the
language
and
get
kind
of
a
better
understanding
of
the
pitfalls
and
things
that
they
encounter
or
like
what
kind
of
error
messages
are
most
confounding
which
my
dream,
that
would
be,
we
would
be
able
to
be
to
see
like
the
I
don't
know,
to
get
more
insight
into
that
and
just
see
this
message
seems
to
always
lead
people
down
a
a
a
bad
bad
chain.
C
Let's
see
if
we
can
improve
it,
that's.
B
C
It's
interesting,
I
think
these
are
both
all
these
things.
We're
talking
about
are
like
now.
This
is
exactly
that's
what
we
were
saying:
the
project
and
the
foundation
not
being
like
fully
independent,
but
working
together,
they're
both
going
to
take
work
on
both
sides
right,
so
the
maintainers
designing
and
thinking
about
what
kind
of
information
they
need
and
the
foundation
helping
to
coordinate
those
resources
and
store
that
data
in
a
sensible
way
with
sensible
privacy
policies
or
whatever
else
we
need.
B
Yeah,
I
know
at
least
I
don't
know-
sometimes
I
think,
a
lot
about
the
work
set
in
front
of
all
of
the
rust
teams
and
that,
like
I'm,
I'm
excited
for
the
for
the
foundation,
because
I
think
the
foundation
works
on
like
a
slightly
different
time
scale
than
the
teams
does
and
that
it
it's
it's
well
designed
to
have
the
time
and
space
to
like
actually
look
at
like
I.
I
really
want
to
dig
into
like
the
github
api
and
like
you're
talking
about.
B
Which,
I
think
would
be
awesome,
but
classically
I'm
like.
What's
the
maintainer
like
experience
like
what
are
the
the
kinds
of
things
I
when
I
was
running
some
data
for
for
a
presentation
I
had
to
do
gosh
I
wish
I
could
remember
where's
pho
anyways.
We
were
like
trying
to
figure
out
how
many
individual,
like
unique
github
accounts
had
had
participated
on
an
rfc.
B
B
But
yeah
I
don't
know,
there's
a
lot
of
cool
stuff,
we're
doing
and
the
opportunities
to
get
meta
about
it.
I
think,
are
great.
A
Yeah-
that's
definitely
true,
so
I
guess
we
have
like
two
minutes
left,
so
I
don't
want
to
close
this
out
too
abruptly,
but
I
guess
one
thing:
ashley:
can
you
actually
put
up
the
blog
post
link
so
that
we
can
point
people
at
the
next
session
times
and
and
so
forth,
because
I
think
one
of
the
things
that
probably
a
lot
of
our
viewers
are
thinking
is
like.
How
can
I
ask
a
question?
A
You
know
you've
talked
about
all
these
things,
and
maybe
you
have
follow-ups-
or
you
know-
want
to
talk
to
us
about
one
of
these
things
in
more
detail
and,
as
we've
said,
it's
actually
like
really
interesting.
We've
had
these
really
long,
zoom
calls
which
are
both
sort
of
tiring,
but
also
actually
really
exciting
to
you
know,
dig
into
these
details
and
talk
to
each
other,
and
I
know
at
least
I've
really
enjoyed
them,
even
if
it
does
mean
waking
up
at
like
very
early
times.
B
D
C
D
B
A
D
E
E
B
I
was
gonna
say
I
I
I
should
have
been
paying
more
attention
to
how
many
people
were
actually
watching
but
they're
still
hanging
in
there.
We
have
a
15
seconds
left
in
theory.
If
we
want
to
go
the
full
hour
but
yeah
I
I
was
told
that
we
shouldn't
just
abruptly
end
it
that
we
should,
you
know,
kind
of,
say,
bye
and
then
hold
off,
because
otherwise
the
video
is.