►
From YouTube: Foundation Conversation - Live Broadcast 2
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
Welcome
to
the
second
live
core
team
broadcast
streaming
to
you
from
very
early
in
the
us
here.
So
some
of
us
are
still
you
know
partially
here,
but
we're
ready
to
get
started,
and
you
know
excited
to
talk
to
all
of
you
this
time
we're
going
to
have
live
questions
starting
probably
10
or
so
minutes.
So
you
know
start
tweeting.
We're
excited,
let's
start
with
the
round
of
introductions,
especially
for
florian,
who
is
new
to
this
stream.
B
Yeah,
hello,
I'm
flooring
over
here
in
berlin,
where
it's
noon
and
not
that
early
in
the
day,
and
I'm
very
looking
forward
to
this
conversation
about
a
little
bit
about
of
the
thinking
behind
a
lot
of
the
things
that
we
that
we
were
doing
with
this
foundation.
I
wanted
to
be
on
this
the
last
event,
but
my
internet
disagreed
and
failed.
The
moment
we
went
live
so
I'm
happy
to
be
here
for
the
second
try
and
hopefully
it
all
holds.
A
C
Yeah
so
I'm
niko
I
introduced
myself
before,
but
I
didn't
say
I'm
gonna
say
right
now:
I'm
a
member
of
the
foundation
project
group
last
time
mark
kind
of
prompted
me
about
to
make
sure
I
pointed
that
out,
but
I'm
also
a
member
of
the
core
team
and
co-lead
of
the
language
team
and
as
of
last
night,
I
am
no
longer
co-lead
of
the
compiler
team,
but
I
was
for
a
very
long
time
and
I'm
super
psyched
that
leslie
is
now
taking
up
that
banner
and
I've
been,
you
know,
really
involved
in
this
foundation
planning
and
everything
else
and
super
excited
to
see
that
work
coming
to
fruition.
A
D
Hi,
I'm
ashley.
I'm
really
excited
to
have
a
really
in-depth
conversation
about
editor
preferences.
It's
going
to
be
great.
I
use
vim
highlighting
have
you
yeah?
No,
it's
really
early
and
this
coffee
is
not
complete,
but
I'm
ashley,
I'm
on
the
core
team.
I've
been
doing
a
lot
of
work
on
this
foundation
situation,
which
I
guess
is
another
name
for
it.
Yeah
and
I'm
very
sleep
dependent
I'll
leave
it
at
that.
C
B
Currently,
yes,
for
the
reason
that
due
to
us
having
to
sink
a
lot
of
having
to
spend
a
lot
of
swing
time
and
the
evenings
being
better,
my
current
work
life
is
a
little
shifted
towards
more
the
afternoon
towards
the
evening
to
to
spend
the
high
intense
time
on
the
foundation
on
the
foundation
in
the
evenings.
But
in
in
general,
I've
got
a
normal
rather
normal
sleep
schedule.
So
coming
back
in
january,.
B
A
Yeah,
let's
get
started
so
before
we
head
into
live
questions
which
I
I'm
not
seeing
any
yet
so
you
know
keep
asking
keep
tweeting,
but
let's
start
with
this
sort
of
question
for
each
of
you.
So
what
excites
you
in
particular
about
the
foundation
and
sort
of?
If
there's
some
problems,
you're
interested
in
solving
or
you
know
thing
you
want
to
tackle
first
thing
or
have
the
foundation
tackle,
as
the
case
may
be,
and
let's
start
with
florian.
B
So
what
excites
me
the
most
about
the
foundation,
a
certain
kind
of
independence,
in
that
the
foundation
is
a
part
and
the
tool
of
the
project
to
to
grow
and
work
on
its
own
and
set
its
own
workflows
around
all
the
things
that
were
previously
handled
by
externally,
particularly
by
mozilla
very
greatly,
and
the
other
thing
I'm
enjoying
a
ton
is
the
ability
to
collaborate
with
organizations.
E
D
All
right
nico
has
already
cursed
on
the
broadcast,
so
it's
been
a
success.
Amazing.
Did
you
call
on
me
mark
for
what
excites
me
most
about
the
foundation?
Sure,
oh
I
wasn't
trying
to
like
jump
in
live
nico
said
that
foreign
to
think.
I
think
the
thing
that
excites
me
the
most
about
the
foundation
is
that
I
don't
know
I've
been
doing
open
source
for
a
long
time.
D
At
this
point,
which
is
weird
because
I
used
to
say
it
was
a
short
time
and
time
passed
and
sometimes
it's
been
my
job
and
sometimes
it's
been
as
a
volunteer,
but
I
don't
know
it.
It's
been.
I've
been
really
frustrated
with
the
general
like
economic
and
organizational
model
of
it,
and
to
continue
to
try
to
do
the
same
thing
and
expect
different
results
is
kind
of
a
very
silly
thing
to
do
and
to
a
certain
extent,
when
I
was
participating
in
open
source.
D
I
feel
like
that's
what
I
was
doing
in
my
attempt
to
avoid
burnout,
and
so
it
feels
really
exciting
and
powerful
and
energizing
to
feel
like.
We
might
be
trying
to
move
that
needle
and
come
up
with
structures
that
that
that
can
help
change
that
that
situation,
where,
like
maybe
you
know,
burning
out,
isn't
isn't
just
the
natural
like
path
and
that
that
we
can
really
come
up
with
with
ways
to
like
establish
sustainability
for
both
individuals
and
projects.
D
So
I
feel,
like
that's,
maybe
a
little
a
little
heady
for
me
at
6
00
a.m.
But
that
is
what
really
excites
me
because
I
don't
know
I've
many
times
over
the
last
couple
years
I've
been
like.
Should
I
keep
doing
this
stuff
like?
Is
this
a
good
idea,
and
sometimes
it
feels
like?
The
answer
is
like
no
and
also
don't
recommend
other
people
do
this
either.
So
I
don't
know
I'm
excited
to
to
try
and
try
and
turn
turn
that
page.
C
Have
an
answer
now
well
so,
for
I
won't
deny
having
asked
myself
that
question,
but
I'm
happy
to
say
the
answer
is
yes
still,
but
it
is,
it
is
tricky,
but
the
thing
I
I
wanted
to
say
the
thing
I
was
going.
The
answer
I
was
going
to
give,
which
I
think
is
similar
to
what
florian
said,
but
different.
Maybe
is
that
what
excites
me
the
most
about
rust
is
collaboration.
I
guess
about
rust
and
open
source,
and
I
feel
like
rust,
has
done
a
really
good
job.
C
I
mean
we
have
our
problems,
but
we've
done
a
really
good
job
at
enabling
collaboration,
but
mostly
at
an
individual
level,
and
I
feel,
like
the
foundation,
gives
us
a
chance
to
take
that
up
to
an
organizational
level
and
I'm
pretty
excited
to
see
what
comes
out
of
that,
and
I
think,
there's
going
to
be
like
a
feedback
loop
like.
I
think,
if
you've
been
listening
to
what
we've
been
saying
about,
supporting
the
maintainers
and
and
the
mission
of
the
foundation
the
whole.
C
The
sort
of
goal
of
this
organizational
collaboration
is
to
come
back
and
support
the
individuals
and
the
individual
collaboration
that
has
worked
so
well
that
it's
begun
to
suffer
problems
of
scale
and
I
think
that's
a
really
exciting
feedback
loop
and
I,
like
one
of
the
challenges
that
I
think
comes
out
of
open
source.
Is
that
there's
a
kind
of
tragedy
of
the
commons
where
it
the
great
part
about
it?
Is
it
belongs
to
no
organization,
no
single
organization?
C
The
bad
part
is
that
means
no
single
organization
is
tending
to
it
and
tending
to
like
all
of
the
managerial
and
organizational
needs
that
come
up
in
it.
I
think
I
think
actually
it
was
ashley
and
florian
who
first
pointed
out
to
me
that,
like
we
have
300
individual
contributors
and
zero
managers
in
the
rest
project-
and
I
was
like
oh
that.
C
Yeah
yeah,
it's
true
and-
and
I
mean
I
see
myself
as
playing
a
managerial
role
in
other
things,
at
least
at
times,
but
like
it's
true
that
we
have
a
lot
of
people
working
and
that's
really
awesome.
But
it
is
true
that,
like
there's
a
need
to
to
strengthen
the
structure
that
they're
working
in-
and
I
think
it's
really
cool
and
I'm
excited
to
see-
if
we
can
do
that.
B
I
have
a,
I
have
a
question
there
for
you
niko
the
words
that
formed
in
my
head
in
in
what
you
were
talking
is:
do
you
think
the
foundation
will
bring
bring
a
certain
simplicity
to
two
things
that
were
more
complex
before.
C
Making
some
things
first
class
that
we're
like
not
first
class,
like
I
mean,
if
nothing
else,
having
like
it's
definitely
true,
that
having
a
legal
entity
that
can
sign
contracts
and
take
actions
on
behalf
of
the
project
will
simplify
a
lot
of
things
operationally.
I
don't
think
that's
not.
A
B
Yeah,
those
were
the
things
I
was
was
kind
of
getting
at,
because
that's
what
I
try
to
to
express
like
this.
This
is
what
it
means
to
be
in
the
the
the
value
of
independence
for
me
like
making
it
easier
to
actually
have
all
on
the
roof,
and
these
concerns
under
under
one
roof,
together
with
the
project
and
making
sure
that
there's
a
constant
it's
easier
to
have
constant
conversations
under
with
the
same
mission
and
under
the
same
same
roof.
B
So
for
me,
the.
C
C
I
had
a
thought
about
this,
something
that
you
were
saying:
oh
well,
what
you're
just
saying
both
of
you
just
kind
of
sparked
another
another
thing
that
I'm
excited
about
in
the
foundation
actually,
which
is
that
I
think
it's
it's
opening
up
kind
of
another
avenue
for
us
to
bring
and
promote
like
more
leadership
from
within
the
rest
organization,
different
kinds
of
leadership-
and
maybe
that's
just
on
my
mind.
C
After,
like
the
blog
post,
I
was
just
working
on
and
so
on,
but
I
but
I
think
I
think
that's
going
to
be
a
really
cool
theme
and
I
think
that's
going
to
help
with
this
problem
that
actually
was
raising
like
yeah.
We
have
new
questions,
but
we're
going
to
have
like
new
venues
and
more
leaders
and
more
ways
for
people
to
tackle
those
questions.
That's
going
to
be
great.
D
Yeah,
I
think,
that's
particularly
exciting.
Like
I
don't
know,
I've
always
been
against
designing
things
from
first
principles
and
one
of
the
best
ways
to
avoid
that
situation
is
to
make
sure
that
people
who
have
experience
doing
these
types
of
things
and
like
have
done
them
before
are
like
in
the
room,
and
it's
just
been
hard
to.
D
I
think
it's
always
been
in
the
spirit
of
russ
to
invite
folks
to
that
room,
but
we've
just
kind
of
lacked
the
the
overhead
and
the
scaffolding
to
like
make
being
in
that
room
with
that
set
of
skills
like
pleasant,
and
so
I'm.
I.
I
think
that
that
the
opportunity
there
is
is
going
to
be
really
great.
B
I
I
definitely
agree
on
the
not
inventing
some
first
principles
design.
I
definitely
enjoyed
a
lot
of
the
things
that
around
looking
at
what
other
foundations
do
and
see
like.
Where
does
our
plan
like
fit,
what
others
do
or
con
consciously
choosing
between
their
standard
solutions?
For
this?
Let's
pick
a
standard
solution
and
spend
time
on
things
where
what
we
feel
we
can
find
improvements
like.
A
I
guess
one
question
sort
of
that
has
sparked,
in
my
mind,
from
sort
of
what
you've
talked
about
is
sort
of
we've
talked
about
how
you
know,
there's
new
problems
to
tackle
maybe
new
venues
to
tackle
them
in,
but
to
some
extent,
I
think
one
of
the
things
we've
been
sort
of
aiming
for
with
the
foundation
is
that,
while
we
sort
of
create
these
new
venues,
the
sort
of
inflow
of
information
and
and
people
into
the
project
is
still
going
to
be
fairly
unified.
A
C
I
was
trying
to
bail
you
out
because
I
knew
you
were
have
still
working
on
your
coffee.
But
if
you,
if
you
were
just.
D
Like
that
now
I
I
mean
I
drank
all
the
coffee
in
this
cup
and
the
other
coffee
is
like
over
there
and
I'm
just.
I
know
it's
a
huge
mess,
but
no
I
mean
I.
I
think
that
that
the
point
mark
is
bringing
up
is
really
important.
So
I
think
there's
like
an
interesting
balance
here
to
strike
about
how
the
foundation
and
the
project
potentially
relate,
but
as
it
as
it
comes
to
like
folks
participating
like
I
don't
think
we
want
to
have
a
sense
of
project,
volunteers
and
foundation.
D
Volunteers
I
mean
I
would
even
go
so
far
as
to
say,
like
I
don't
know,
project
staff
versus
volunteer.
This
is
like
they're
they're.
It's
rust
people
like
rust
volunteers
and
I
think
it's
really
critical
to
keep
that
unified.
C
Yeah
the
foundation
is
the
project,
is
the
foundation
or
we're
together.
B
That's
what
that's
precisely
where
I
have
this
model
in
my
head
of
under
one
roof.
I
think
it's
a
it's
a
huge
problem
if
those
things
are
seen
as
as
is
different
and
there's
an
artificial
barrier,
a
barrier
between
it
between
the
foundation,
people
and
the
and
the
the
project.
B
People
and
the
the
thing
that
I
enjoyed
most
is
working
in
organizations
where
the
plane
doesn't
matter
because
we're
we're
working
towards
the
same
goal,
making
rust
better
in
many
different
ways
and
with
slightly
different
focus,
and
that's
like
just
like
because
of
the
work
you
can
do
in
certain
spaces,
and
we
agreeing
with
what
actually
was
mentioning
that
this
gives
us
the
ability
to
do
more
kinds
of
work,
which
also
makes
things
more
complex.
C
I
mean
I
think
when
so
when
I
said
the
foundation
is
the
project
and
the
project
is
the
foundation.
I
think
the
really
interesting
question
is:
what
is
what
does
the
word
project
even
actually
mean
right?
I
think
what
a
lot
of
us
have
in
our
heads,
or
at
least
what
I
I
think
when
we
use
that
word.
We
are
often
meaning
the
rust
teams
existing
west
teams
and
those
are
not
equal
to
the
foundation
any
sense
those
teams
are,
they
exist
and
the
foundation
is
like
there
to
enable
them
and
help
them
work.
C
That
is
its
mission
and
or
enable
the
people
on
them.
I
think
and
support
those
maintainers
who
are
members
of
them,
but
but
at
the
same
time,
like
you
know,
we've
talked
on
the
in
the
frequently
asked
questions
about
some
of
the
structure
and
we'll
we'll
be
going
more
into
that
in
the
coming
weeks
and
so
on.
But
like
they
have
we're,
you
know
the
foundation
board
will
include
a
number
of
members
from
the
teams
and
there's
representation
going
there
and
there
we
are
kind
of
working
all
together
towards
the
same
goal.
D
Yeah,
I
think
I
I
kind
of
want
to
riff
on
this
idea
that
you
said
like
the
foundation
is
the
project.
The
project
is
a
foundation
and,
like
that's
scary-
and
I
think
one
of
the
reasons
that
can
be
scary
is
just
the
foundation-
is
a
new
entity
and
it
can
be
really
weird
to
feel
like
there's
a
new
entity.
D
That's
like
put
into
potentially
a
position
of
like
power
and
control,
and
one
of
the
things
that
we
talked
about
a
lot
with
the
the
project
group
as
we're
thinking
about
the
foundation
and
kind
of
how
it
plays
into
like
just
the
whole
kind
of
like
ecosystem
of
rust,
and
I
do
think
ecosystem
almost
makes
more
sense
than
project.
Since
there's
a
lot
of
little
projects
inside
of
rust.
Is
that,
like
the
the
foundation
is,
is
a
player
within
that
ecosystem?
D
It's
also
really
important
to
just
like,
say
out
loud
that
we
know
that
there's
going
to
be
a
period
of
trust
earning
that
has
to
happen
and,
like
the
the
no
matter,
what
we
say
today
or
you
know
in
the
faq
like
the
foundation,
is
going
to
need
to
be
like
a
a
part
of
the
community
and
we're
going
to
have
to
see
how
those
types
of
things
play
out-
and
I
I
think
that's
really
important,
but
I
I
do
think
it's
it's.
D
B
But
I
I
also
think
there's
a
chance
in
this,
so
the
foundation
is
a
little
bit
of
a
blank
sheet
of
paper
currently,
and
I
think
this
is
what
some
some
of
the
unease
may
come
just
from
that,
because-
and
this
is
why
we're
having
this
conversation
and
talking
about
our
plans
for
what's
right
on
that
piece
of
paper.
B
But
there's
also
a
lot
of
chances
in
this,
because
we
can
open
up
new
conversations.
We
can
open
up
new
new
ways
of
conversations
new
ways
of
engagement,
new
ways
of
working
in
our
project,
new
ways
off
transforming
the
project
growing
growing
over
the
next
years,
ensuring
that
growth.
So
I,
like
I'm,
super
happy
about
starting
to
write
on
that
piece
of
paper
so
and
let's
hope
it
ends
up
being
not
I'm
sure
that
it's
going
to
be
a
good
story
and
I'm
very
much
looking
forward
to
that.
B
A
C
C
Can
I
steal
that
can
can?
Can
I
steal
the
mc
role
and
pivot
to
a
to
a
question?
There
was
this
question
that
was
raised
in
the
fact
of
like
what
was
one
of
the
hardest
parts
of
designing
the
foundation,
and
what
I
was
going
to
say
was,
I
think,
the
question
of
what
to
define
and
what
to
leave
for
the
future
actually
is
one
of
the
more
subtle
and
hard
questions.
That's
what
I
thought
about
when
I
heard
the
blank
paper
reference,
because
you
know
I
think
we've
tried
to
be.
A
Yeah-
and
I
think
one
one
thing
I'll
note-
nico's
sort
of
I'm
not
part
of
the
like
foundation
group,
though
lately
I've
been
doing
a
lot
more.
There.
A
The
thing
I
was
going
to
bring
up
is
that
sort
of,
as
we
sort
of
one
of
the
reasons
we
want
to
provide
this
initial,
like
structure
and
framework
for
like
the
foundation
and
to
some
extent,
sort
of
more
broadly
sort
of
these
interactions,
with
the
teams
and
so
forth,
is
to
sort
of
design
intentionally,
not
just
for
like
the
next
year
of
the
foundation,
but
also
for
like
the
next
10
years
or
20
years,
so
that
we
sort
of
can
grow
into.
A
You
know
that
shape
and
fill
that
structure
without
having
to,
like
you
know,
break
new
ground
or
whatever
every
year
as
we
grow
as
a
project
and
community.
B
Yes,
yes,
what
I
found
really
the
hardest.
The
hardest
part
in
this
process
was
also
staying
focused
on
having
all
the
important
conversations
on
what
is
what
is
the
goal
of
this?
Instead
of
we're
just
setting
up
a
legal
structure,
thinking
like
we
had
a
lot
of
conversations
around.
What
are
the
goals?
What
are
things
we
probably
better,
not
do
what
have
we
seen
fail,
especially
in
our
own
experiences.
B
A
lot
of
the
people
in
the
foundation
working
group
have
done
this
before
in
other
communities.
I've
been
part
of
a
a
ruby
non-profit
over
here
in
berlin,
or
actually,
you
still
am
so
taking
all
those
experiences
and
and
critically
investigate
on
what
can
we
do
to
make
this
like
something
for
2020
and
not
for
20,
20
11
or
something
like
that
was
was
an
enjoyable
path.
C
Trust
I
heard
20
2011
and
that's
like
a
really
long
time,
but
I
hope
russ
is
still
in
use.
You're,
like
20
000
years
from
now.
D
This
process,
which
I'm
sure
these
other
three
are
like
so
sick
of
hearing
me
say,
is
like
systems
of
affordances.
So,
like
one
oh
yeah,
there
we
go
nico's
laughing
at
me,
perfect
one
of
the
things.
I
think
that
we
like
don't
pay
as
much
attention
to
that.
I
wish
we
did
is
like
kind
of
like
the
this.
D
The
way
we
set
up
incentives
that
have
like
these,
like
chronic
effects
over
long
periods
of
time-
and
they
are
like
by
far
the
hardest
things
to
see,
but
they
are
the
things
that
over
long
periods
of
time
really
shape
like
what
your
organization
and
group
can
do,
and
I
think,
as
an
open
source
project,
rust,
actually
got
a
lot
of
these
incentives
right,
and
so,
when
I
think
about
like
designing
the
foundation
like
there's
bylaws,
I
expect
the
bylaws
to
change,
even
though,
like
every
foundation
is
like
afraid
of
having
to
change
their
bylaws
like
so
much
they're
gonna
change,
I
actually
think
the
more
agile
we
can
be
about
changing
those
the
better
not
to
use
like
people
are
grumpy
about
agile
right.
D
I
don't
know.
I
shouldn't
have
said
that
anyways
I
just
meant
flexible,
but
but
but
coming
up
with,
like
like
really
understanding
what
the
like
key
vision
and
values
are
like
is
kind
of
what
sets
up
those
like
affordances
and
incentives
that
like
drives
things
forward.
So
that's
that's
been
something
I've
been
like
really
excited
about.
I'm.
C
I
think
I'll
note
that
it
was
me
who
injected
that
whole
thing
and
not
poor
mark
was
like,
don't
don't,
but
I
think
florian's
I
think
florian's
answer
gets
at
that
right
like
there
was
definitely,
I
will
confess,
on
my
part,
a
desire
to
like,
or
at
least
a
tendency,
let's
say,
sometimes
to
just
drop
in
at
the
lowest
level,
and
we've
all
seen
that
whenever
you're
doing
design
that
can
happen
right,
you're,
just
like
here's,
how
the
code
should
look
instead
of
dialing
back
or
whatever
it
is
here's
how
the
by-laws
should,
instead
of
dialing
back
to
be
sort
of
what
are
the
big
picture?
C
What
is
the
goal?
Not
just
how
kind
of
majority
do
you
need
to
make
a
decision,
but,
like
you
know,
what
are
they
trying
to
decide
and
why
and
that
that
is
really
useful
to
have
someone
remind
you
to
pull
back
and
look
at
that.
B
It's
I
mean
it's
a
it's
a
process
of
actually
like
what
do
we
push
off,
because
we've
already
also
had
the
conversation
of.
Can
we,
as
this
small
group,
decide
certain
things
that
should
should
be
decided
later,
so
the
conversation
of
we
actually
think
that
should
be
decided
for
the
that
should
be
a
decision
for
the
people
doing
the
work
later
and
implementing.
That
has
been
a
constant
thing
and
like
separating
things
into
into
goal,
setting
and
also
oh
no.
B
This
is
this
would
be
a
detailed
decision
where
we
would
actually
take
away
take
that
away
from
from
the
person
that
would
actually
do
do
that
later
and
what
we
don't
think
it's
it's
it's
good
to
make
this
decision
now
so,
and
that
is
a
that
has
been
an
effort
to
separate
these.
These
things
strongly.
I
enjoyed
that
for
effort
a
lot,
because
it
also
means
thinking
about
how
the
organization
may
work
later.
A
Yeah
it
I
don't
know,
I've
been
sort
of
increasingly
involved,
as
ashley
will
tell
me.
I've
always
been
involved,
but
you
know
it's
been
in
the
last
like
three
weeks
or
so,
but
as
sort
of
we've
been
getting
that
involvement,
ramping
up
sort
of
from
just
a
project
group
to
a
wider
set
of
folks
on
the
core
team,
it's
been
really
interesting
to
see
sort
of
this
transition.
A
I
think
from
sort
of
diving
into
ideas
and
sort
of
working
out
all
these
sort
of
details
that
we
need
for
the
foundation
to
even
like
exist
to
sort
of
shifting
a
little
bit
to
these
sort
of
broader
ideas
of
like.
Why
do
we
exist
or
sort
of
why
you
know
do
we?
C
D
The
the
thing
that
I
want
to
say
about
the
hardest
part
of
this
is
is
to
kind
of
like
pull
out
of
the
heady
answers
and
just
go
to
a
certain
extent
when
we
announced
that
we
were
going
to
do
this
in
august
right
like
basically,
what
we
were
proposing
is
that
as
a
hobby,
we
were
going
to
speed,
run
starting
a
new
company.
D
That's
that's
what
we
said
that
we
were
gonna
do
and
if
I
think
about
what's
the
hardest
part
of
it,
it's
just
the
thing
that
we
did
was
the
hardest
part
like
the
idea
that
we
thought
that
we
could
pull
that
off
at
all.
I
have
been
I'll
say
like
every
morning
I
wake
up
and
kind
of
go
like.
Oh.
What,
if
we
like?
D
Don't
do
this
like
what,
if
this
like,
doesn't
happen
and
like
the
the
difference
between
this
happening,
and
it
not
happening
is
like
me
doing
stuff
today
and
like
every
day,
there
is
stuff
that,
if
I
don't
do
it
like,
this
doesn't
happen
that
that
was
the
hardest
part
and
it's
not
over.
Yet
we're
still
going
so
yeah.
I
think
my
friend,
luis
via
when
he
was
when
we
announced
the
the
faq
on
twitter.
C
This
one
first
of
all
I
want
to
apologize.
I
decided
I
was
going
way
too
far
with
my
systems
of
affordances
jokes,
but
I'm
all
into
it,
but
secondly,
I
think
you
nailed
it
with
that
by
the
way
that
is
totally
true.
B
I
want
to
share
one
thing
talking
about
about
that.
B
I
I
got
a
couple
of
feedback
sessions
with
with
some
people
actually
outside
of
the
russ
community
before
we
started
this
endeavor
or
at
the
beginning,
and
one
quote
that
stuck
out
to
me
from
someone
was
the
thing
I
always
find
interesting
when
seeing
the
rust
project
from
the
outside
is
that
you
take
theory
like,
as
you
say,
the
heady
stuff
and
you
put
it
into
action
like
you,
you
pick
what
you
want
and
then
you
put
it
into
then
you
actually
actually
build
it,
and
that
was
I
think
that
that
that's
the
thing
that
has
connected
me
to
this
process.
B
A
lot
of
this
is
actually
an
idea.
I
had
my
head
with
all
of
my
experience
and
whatever,
but
what
can
we
do
out
of
it
like?
How
can
we
actually
make
that
make
that
thing
happening
and
yeah
so.
A
D
Will
there
be
changes
in
teams
and
community
projects
structurally?
I
just
totally
took
your
job
mark,
I'm
the
worst.
Oh.
A
No,
no,
it's
it's
good,
so
I
guess
I
don't
know.
Are
we
splitting
the
question
apart?
Are
we?
I
guess
we
can
just
answer
it
as
a
whole?
I
don't
know:
let's
go
with
florian
since
you're
most
awake
of
any
of
us.
You
can
take
a
stab
at
the
question
I'll.
B
I'll
not
split
the
the
question.
No,
I
think
one
one
thing
that
sets
the
worst
project
apart
and
that's
also
feedback.
I
got
a
lot
is
that
the
rest
project
has
always-
and
that's
particularly
the
reason
why
I
am
in
the
ros
project,
always
seen
things
like
community
interaction
and
all
the
things
you
need
to
do
around
the
code
as
a
core
function
of
this
project.
B
You
can
see
that
in
our
yearly
surveying,
in
that
we
have
a
community
team
from
the
beginning
and
and
that
a
lot
of
the
teams-
also,
it's
not
just
the
community
team
that
a
lot
of
the
teams
are
very
community
minded
and
are
taking
community
feedback.
I
said
a
lot
all
of
them,
sorry,
all
of
them
and
then-
and
we
have
substantial
projects
outside
outside
of
the
project
and
outside,
like
the
boundary,
is
floating
there.
B
Some
people,
for
example,
are
individually
part
of
the
rust
project,
but
they
do
also
have
something
on
the
side
and
that,
where
they're
running
a
meet
up
or
something
like
that-
and
I
think
that
system
works
well
and
it
I
it
would
be.
Oh,
we
will
make
that
better.
B
I'm
sure-
and
we
will
find
ways
to
make
that
better
in
the
next
years,
but
I
I
think
it's
a
strong
point,
so
I'd
be
very
cautious
with
choices
that
don't
come
out
of
this
system
already
so
long
story
short
changes
always
happen,
but
not
out
of
this
conversation
I
have
the
feeling.
A
C
The
thing
I
was
going
to
say
is
yes,
there
will
be
changes
in
teams
and
community
projects,
but
not
directly
as
a
result
of
creating
the
foundation
like
because
the
project
is
always
evolving
and
we
like
are
going
to
make
changes
because
we're
going
to
do
things
better,
but
creating
the
foundation
itself
is
not
it's
not
res.
It's
not
like
we're,
also
adjusting
a
bunch
of
team
changes.
At
the
same
time,
I
I
said
directly
because
I
think
that
the
foundation
is
going
to
have
unforeseen
and
wonderful
impacts
over
time.
D
Jump
in
and
say
that
which
is
like
I,
I
do
think
that
this
foundation
conversation
and
like
the
conversation
doesn't
stop.
Once
the
foundation
gets
kicked
off
right.
It
will
continue
to
be
a
dialogue,
but,
like
the
I,
what
I
am
excited
about
is,
I
think
I
don't
know.
Nico
also
is
probably
irritated
with
me
saying,
like
I'm
so
excited
about
the
opportunity
to
look
at
like
data
and
stuff,
because
I
am
but
I
I
okay
I'll
have
to
like
keep
a
list
of
which
ones
nico
likes.
D
D
Maybe
is
not
the
right
word,
but
like
it,
we're
not
as
efficient
about
growing
and
changing
based
on
our
like
changing
needs,
as
as
we
might
want
to
be-
and
I
I
see
the
foundation
as
an
opportunity
to
like
get
better
at
that
and
like
to
be
able
to
again
like
bring
support
and
resources
into
thinking
about
how
we
do
those
types
of
things
so
yeah,
no,
the
foundation
isn't
going
to
be
like.
D
We
declare
that
there
is
a
space
communism
team
now
just
a
suggestion,
just
throwing
that
one
out
there
but
like
if
the
foundation
said
that,
like
everyone
would
be
like
no
foundation,
that's
like
not
your
job,
but
I
think
there's
an
opportunity
to
go
like
man
like
we
have
so
many
space
communism
initiatives.
It
would
be
really
great
if
we
could
create
some
scaffolding
around
that
portion
of
the
project
and
be
able
to
support
it.
That
might
be
more
of
the
shape
that
we
would
see
that
happen
in
anyways.
D
B
That
was
particularly
the
reason
why
I've
actively
searched
for
people
from
pretty
much
outside
even
outside
of
the
community
or
who
are
a
little
bit
more
more
distant
from
for
for
getting
feedback
that
being
in
the
thick
of
it
for
now,
roughly
five
years
means
that
you
see
a
lot
of
the
problems
very
dominantly,
and
people
from
the
outside
can
give
you
feedback
on
the
things
that
work
and
seeing
that,
particularly
that
people
highlight
oh,
the
interaction
between
the
project
and
the
community
like
that,
has
a
wide
to
it,
like,
particularly
that
that
that
has
a
wife
that
radiates
also
points
to
well.
B
This
white
must
continue
to
exist
and
because
it's
a
good
thing,
it's
it's
a
strong
point.
So
thinking
so,
my
thinking
has
turned
a
lot
towards.
How
can
we
make
this
in
increase
and
and
ride
that
wave
essentially.
A
Yeah,
so
I
think
we've
talked
sort
of
a
little
bit
about
how
the
foundation
is
going
to
interact
with
the
community,
but
sort
of
this
question
I
think,
brings
us
sort
of
closer
to
that
and
I'm
wondering
florian.
If
you
want
to
talk
a
little
bit
about
sort
of.
If
there's
you
know,
we
said
that
there's
probably
structural
changes
that
are
going
to
happen
just
as
a
result
of
rust
growth
not
really
foundation
directly,
but
I
think
people
are
probably
also
interested
in
this
question
of
like
well.
B
So
what
it's
going
to
change
is
a
good
question
for
for
something
that
doesn't
exist
yet
like
it's
going
to
exist,
it
will
be
like
I
still
see
it
as
it
will
be
a
an
additional
component
to
the
project
to
make
to
enable
new
kinds
of
interactions
and,
for
example,
work
together
with
teams
like
the
community
team
to
come
up
with
with
actions
and
programs
and
and
and
support
them.
So
this
will.
This
will
always
be.
B
I
don't
even
want
to
say,
joint
effort.
This
will
be
an
effort
under
the
same
same
roof,
with
with
new
approaches
that
we
that
we
can
take
that
weren't.
B
I
don't
want
to
say
possibly
before
that
weren't
as
easy
before,
and
we
have
had
a
community
interaction.
We
had
a
community
ground
programs
and
all
of
these
as
the
project,
all
the
time
and
the
foundation
will
be-
and
we
have
this
with
together
with
partners
always
and
the
foundation
will
be,
will
help
us
that
will
help
us
making
programs
happen.
E
D
I'm
sorry,
I
learned
a
new
thing
about
stream
yard
by
accident
in
the
middle
of
florian's
answer,
which
is,
I
can
take
questions
from
the
comments
and
if
I
accidentally
click
them,
they
will
just
show
up
on
the
screen,
which
is
like
really
useful.
This
is
a
very
complicated
way
of
just
saying.
There's
a
new
question.
D
It's
a
it's
kind
of
a
big
one,
but
it's
I
I
think
it's
a
great
question.
We
have
like
18
minutes
left
in
the
stream
and
so
how
we
answer
a
question
like
this
in
18
minutes
will
be
hard,
but
I'm
excited
to
address
it.
A
Yeah,
I
guess,
let's,
let's
start
with
this
sort
of
how
teams
and
foundation
will
be
in
sync,
I
think
so.
I
guess
one
of
the
things
we
can
talk
about
there
is
this
idea
of
sort
of
relationships
and
and
sort
of
how
the
you
know,
teams
will
be
able
to,
or
you
know
willing
to
talk
to
people
on
the
foundation
and
vice
versa.
Nico
do
you
want
to
take
us
off
there.
C
Yeah,
I
mean,
I
think
so
I
mentioned
already
that
the
project
has
some
representatives
and
things
that
will
be
part
of
the
foundation,
but
I
think
the
question
of
how
teams
will
will
talk
to
the
foundation.
I
mean
the
way
we've
been
thinking
of.
C
It
is
mostly
that
to
start
the
simplest
answer
is:
if
teams
have
ideas
you
know
for
what
they
would
like
to
see
done,
they
should
take
them
to
the
core
team,
and
the
core
team
has
representatives
on
the
foundation
board
that
can
kind
of
think
about
those
ideas
and
bring
them
up
and
that's
kind
of
a
natural
flow,
and
the
nice
thing
about
that
information
is
that
it
may
be
that
the
team
has
an
idea
of
something
they
want
to
do.
C
You
may
not
actually
need
to
like.
It
may
not
actually
require
the
foundation
right
or
maybe
there's
another
way
to
go
about
it,
that
that
that
someone
and
the
core
team
has
an
idea,
and
so
we
kind
of
wanted
to
keep
that
flow,
going
up
through
the
through
the
existing
teams
and
then
to
the
foundation
and
not
so
much
like
everybody's
talking
to
everybody
and
it
gets
a
little
overwhelming.
But.
C
D
C
D
Yeah,
so
I
I
do
think
one
of
the
ways
that
the
project
and
like
the
teams
will
interact
with
the
foundation
is
proposing
initiatives,
but
I
I
think
one
of
the
critical
first
things
to
say
is
that
the
teams
and
the
foundation
are
not
entirely
separate
at
all
like
the
the
foundation
board
is
it
has,
is,
is
going
to
have?
Oh,
my
gosh.
Sorry,
my
dog
just
woke
up
there.
He
goes.
D
D
So
it's
it's
not
like.
There's
two
black
boxes
and
we
need
to
like
create
some
sort
of
channel.
Yes,
one
of
the
key
directors
for
the
project
on
the
board
will
be
my
dog.
He
has
some
serious
collaboration
issues
though
that
are
concerning,
but
as
we
talk
about
like
an
overseeing
structure
like
I
definitely
like
this
second
word
you
use,
which
is
meld.
D
I
definitely
think
that
it's
it's
more,
that
the
foundation
extension
is
the
wrong
word,
but
it's
part
of
one
large
organization,
not
two
separate
ones
that
are
kind
of
chatting,
and
so,
of
course,
with
my
dog
stopping
barking.
I
will
let
other
folks
talk
down
gosh.
B
Yeah,
that's
there's
this
one
part
of
that
I
want
to
address
is
like
the
the
part
overseeing
the
foundation.
Will
not,
I
don't
see
them
as
like
overseeing
the
project,
but
again
this
thinking
of
will
be
a
resource
to
the
project,
an
additional
thing
that
we
plug
on
and
participate
in
the
collaborative
structure
that
the
the
rust
project
has
but
be
responsible
for
for
tasks
that
we
didn't
have
before,
and
the
rust
project
already
has
a
strong
tasking
of
teams.
B
So,
for
example,
things
that
the
release
team
doesn't
sign
off
on
all
of
the
other
teams
can
complain
as
much
as
they
want
to.
If
the
release
team
says,
this
is
not
a
sufficient
high
quality,
it
doesn't
get
too
stable
and
in
that
level
the
foundation
will
also
play
some
of
these
critical
roles
where
it
has
to
oversee.
For
example,
it
will
definitely
oversee
a
budget,
because
that's
what
what
part
of
that
structure
is
there
for.
B
So
that
will
be
the
thing
that
it
brings,
but
also-
and
this
is
one
thing
that
I'm
very
happy
about
in
the
rust
project-
is
that
we
have
a
lot
of
upstanding,
self-confident
teams,
and
that
is
a
good
way
on
how
these
teams
can,
because
they're
already
self-confident
can
interact
with
the
new
part
that
we
plug
on,
and
the
foundation
in
that
case
will
be
part
of
this.
E
B
System
of
performances,
groups
of
self-confident
teams,
whatever
you
you
may
want
to
have-
and
I
think
this
is
like
how
we
should
how
we
need
to
to
approach
this
as
like.
This
is
a
this
is
a
chance.
This
is
these
are
people
that
want
to
do
that
particular
piece
of
work
and
they
have
their
needs,
the
things
they
can
bring
and
and
the
resources
they
can,
they
can
add
to
the
project.
So
the
melding
is,
I
think,
that's
the
that's.
I
I'll
pick
the
melt
from
that
question.
A
Yeah,
I
I
do
think
so.
Maybe
one
thing
that
I
might
touch
on
is
that
sort
of
we've
talked
about
this
melding,
but
I
think
a
critical
element
here
is
that
the
foundation,
I
don't
know,
sort
of
how
you
see
melding
exactly
but
there's
not
going
to
be
like
a
foundation
person
sitting
on
every
team
or
anything
like
that.
It's
sort
of
melding
in
the
org
chart
sense
not
in
the
like
team
people
sense.
I
don't
know.
D
B
C
One
thing
we've
toured
around
with,
but
I
found
it
a
helpful
way
of
thinking
about
things,
even
though
it's
not
exactly
right
is
sort
of
the
foundation
as
another
team.
I
don't
think
they
are
exactly
a
team,
but
I
think
there
is
like
a
because
I
know
you're
not
gonna
lie,
but
I.
D
D
C
D
So,
like
that's,
that's
kind
of
like
worth
calling
out,
and
so
I
guess
to
a
certain
extent
like
I,
I
really
think
the
spirit
of
it
is
that
they
will
meld
but
like
if
there's
a
team
that
wants
to
like
do.
Crimes
like
the
foundation
is
gonna,
probably
oversee
that
so
like
maybe
not
so
much
with
the
doing
crimes
but
and
like
you
know,
if
you're
gonna
try
and
do
something
that
might
potentially
like
financially
bankrupt.
D
The
organization
like
I
think,
that's
where
you'll
start
seeing
stuff
step
in,
but
like
otherwise
there's
like
such
a
strong
culture
of
delegation
within
the
rust
organization.
Like
I
don't
know,
I've
sat
on
foundation
boards
before
they
don't
want
to
to
be
like
you
know
deciding
what
the
new
cargo
command
is
like.
That's
not
like.
We
don't.
There's
no
worry
there
that,
like
they're
gonna,
be
supervising
something
like
that.
C
But
I
think
that
I
get
like
what
florian
said
about
the
release
team,
for
example.
Right,
like
that
we
I
agree,
the
foundation
has
a
special
role,
but
I
also
think
it's
not
unique
to
the
foundation
that
the
teams
have
sort
of
checks
and
balances
amongst
each
other
and
some
amount
of
authority
over
one
another
right
and
that's
kind
of
cool
and
makes
sense.
B
Yeah
that
was
kind
of
where
he
was
getting
it.
People
always
see
like
this,
this
kind
of
research
allocation
and
and
budgeting
as
a
bad
thing,
which
will
certainly
be
something
that
the
foundation
will
be
part
of,
but
I
actually
like
that.
That's
a
core
part
of,
for
example,
what
I'm
trying
to
teach
conferences
that
their
budgeting
is
very
important
and
that
their
budgeting
in
the
end
says
what
they'll
be
able
to
do.
B
The
reason
why
a
lot
of
the
conferences
in
the
rust
world
are
able
to
like
it's
common,
that
our
conferences,
pay
speakers,
which
is
a
huge
debate
in
other
communities
and
now
as
it
is,
and
for
the
reason
that
a
lot
of
the
conferences-
and
we
have
a
already
have
good
ties-
that
these
conversations-
that
these
conversations
happen.
That
conferences
talk
about
by
the
way.
B
The
first
thing
you
need
to
have
is
budget
and
need
to
be
clear,
clear
about
money
and
the
reason
why
I'm
pulling
that
experience
in
that
strongly
is
because,
while
there's
a
lot
of
projects
in
the
open
source
space
that
don't
think
a
lot
about
money,
conferences
actually
do
because
otherwise
they're
breaking
bank
very
hard
and-
and
that
might
have
impact
like-
and
this
is
why
I'm
talking
to
a
lot
of
these
people,
because
that
might
have
impact
to
volunteer
organizers
if,
if
they
didn't
make
their
budget
right.
B
But
you
can
make
a
lot
of
things
happening
with
careful
planning.
And
this
is
the
this
is
the
role
that
I
see
there
and
of
of
making
sure
that
we
that
we
use
our
resources
effectively
because
they
fit
it.
That's
like
that's
the.
They
will
always
be
in
some
way,
definite.
D
Well,
I
mean
I
would.
I
would
argue,
though,
like
you're
you're
right
that
the
economics
of
a
conference
are
like
really
obvious
and,
like
you,
can
quickly
like
break
bank
very
easily,
to
use
your
words,
but
I
think
that's
true,
of
building
software,
also
like
we're
just
like
breaking
bank
in
like
way
more
insidious
ways.
Yes,
I'm
still
going
off
about
the
economics
of
open
source,
I
feel
like
mark
is
rolling
his
eyes
at
me.
D
But
yes,
I
am,
and
I
think
that
that's
really
important
and
so
having
a
foundation
means
that,
instead
of
like
implicitly
like
participating
in
this
kind
of
open
source
economy,
we
can
start
trying
to
like
actively
participate
in
it
and
like
be
a
lot
more
deliberate
about
that
stuff,
which
I
think
is
really
important.
D
A
Okay,
so
let's
see
any
new
or
more
complete
learning
resources
for
rust.
So
actually
this
is
something
we
talked
about
quite
a
bit
sort
of
before
the
stream
started
sort
of
on
this
idea
of
sort
of
providing
educational
programs.
So
I'm
wondering
ashley
if
you
want
to
kick
that
off.
D
D
This
kind
of
goes
back
to
like
the
there's,
not
a
difference
from
the
foundation
in
the
project,
but
I
I
do
know
that
the
project
has
always
like
really
cared
about
learning
resources,
but
we
have
kind
of
sometimes
struggled
with
those,
because
creating
really
good
learning
learning
resources
can
often
take
a
lot
of
resources
and
support,
and
so
I
I
do
think
that
the
foundation
would
be
like
very
eager
to
help
support
maintainers
create
those,
and
in
particular
it's
interesting
here,
because
when
we
talk
about
learning,
there's
so
many
different
dimensions
of
what
learning
can
possibly
mean
within
the
rust
project
and
ecosystem,
like
learning
could
be
like
how
do
I
learn
rust
and
that's
kind
of
the
like
kind
of
first
kind
of
sense
of
it?
D
But
there's
also
like
how
do
I
learn
to
contribute
to
rust?
How
do
I
learn
how
to
run
a
rust
conference?
How
do
I
learn
how
to
advocate
for
my
company
to
give
me
open
source
time
to
work
on
rust,
there's
so
many
different
levels
of
learning
there,
and
I
am
excited
to
kind
of
infuse
this
kind
of
area
with
some
resources,
because
I
think
I
I
think
that
there's
a
lot
of
really
neat
opportunity
for
the
rust
project
to
start
generating
some
of
those
resources.
D
So
I
guess
there's
like
a
yes
answer
in
here,
but
again
with
that
sense
of
mediation,
where,
like
the
foundation,
isn't
like
gonna
write
a
book.
The
foundation's
gonna
help
the
project
right
once.
B
Yeah,
so
one
thing
that
that
popped
up
in
my
head,
when
you
were
like
covering
all
those
subjects,
is
these
are
a
lot
of
high
context,
things
where,
for
example,
we
have
the
compiler
dev
guide
and
how
you
hack
on
the
compiler
it's
a
book,
and
this
can
only
be
written
by
people
that
have
deep
knowledge
of
the
compiler,
how
it
works,
how
the
build
process
works
and
and
what
the
flaws
are
currently.
So
it
would
be
very
hard
for
just
saying
like
say
we
hire
a
person
who
does
this.
B
This
is
just
not
possible
because
the
person
you
won't
find
a
person
that
has
all
these
contacts
and
has
all
these
knowledges,
and
that
comes
back
to
the
idea
of
supporting
maintainers.
How
can
we
make
sure
that
maintainers
can
work
on
these
resources,
especially
as
we
have
a
lot
of
people
that
are
very
eager
to
write
these
kind
of
things
and
there's
a
culture
of
it?
But,
for
example,
I
have
never
learned
technical
writing
or
I
had
like
a
weekend
seminar
on
technical
writing
before
I
wrote
my
master
thesis.
B
There's
still
always
people
that
ask
me
like.
Could
you
write
this
down
like
this
is
so
like?
This
is
a
hard
thing
for
me
and
I
think
improving
the
situation
where
people
think
about
do.
I
want
to
write
a
book
on
this.
Oh
no,
like
I'm
making
to
say
do
I
want
to
write
a
book
about
it.
Yes,
I
can
do
that,
and
I
have
support
for
that.
I
know
how
it
works,
and
this
and
there's
help
for
this.
B
That's
I
think
that
will
improve
that
situation
and
organizing
these
kind
of
things
like.
I
think
that
oregon.
That
was
one
of
the
feedbacks
that
I
also
got
is
like
there's
a
lot
of
things
around
and
there's
so
much
produced
every
day.
That
organization
of
this
is
becoming
an
effort
like
the
constant
of
organization,
and
these
are
my
rough
thoughts
when
I,
when
I,
when
I
hear
that
question
about
like
especially
more
complete,
what
is
complete
is
complete.
You
can
find
them
all.
C
C
Longer
I
I
was
going
to
say
two
things
about
learning
resources.
The
first
one
is
like
about
the
rusty
dev
guide.
That
florian
was
mentioning
and
organization.
One
of
the
really
interesting
things
we
tried
to
do.
There
was
having
sort
of
people
who
know
that
area
of
the
compiler
will
get
sort
of
interviewed
by
other
people
who
are
going
to
work
on
the
rusty
dev
guide,
and
we
would
record
that
interview
or
do
it
like
over
text,
so
that
the
interview.
C
A
resource
that
you
can
learn
from
immediately
and
then
it
provides
the
raw
material
that
people
who
who
want
to
learn
can
use
to
like
write
the
text
and
that,
but
but
making
that
kind
of
thing
happen
is
is
a
lot
of
organizational
work.
C
You
have
to
like
schedule
that
you
got
to
find
the
people
who
are
excited
and
really
you
need
to
edit
the
content
that's
coming
out
of
it
and
that
that
might
be
a
place
where,
like
there
might
be
a
role
for
the
foundation
to
help
enable
that
organizational
work
and-
and
I
think
it's
super
exciting-
and
I
love
that
idea
because
it
just
worked
like
it
just
helps
everybody
in
so
many
different
ways.
C
But
the
other
thing
I
would
say
is
that
I
want
to
see
some
of
that
learning
going
the
other
way.
I
I've
mentioned
this
a
few
times,
but
I
think
it's
pretty
exciting
for
my
wearing
my
laying
team
hat
to
think
about
learning
from
people
who
teach
rust
and
that's
an
example
where
again,
there's
sort
of
organizational
relationships
and
organization
needed
to
bring
that
knowledge
in.
C
But
I
you
know
I'd
like
a
much
more
detailed
look
at
what
are
the
kinds
of
things
that
people
find
really
hard
to
learn
and
how
can
we
address
them
and
I
get
that
by
doing
one-on-one
mentoring
from
time
to
time.
But
there
are
people
who
do
that
all
the
time
and
they
they
have
probably
a
much
better
picture,
not.
E
A
D
D
For
this,
when
I
was
an
invited
guest
on
on
tc39,
but
I
I
think
particularly
for
a
language
right
like
rust,
which
has
this
kind
of
like
notorious
learning
curve.
D
I
mean
the
other
nice
thing
about
having
a
like
teachers
committee
or
something
is
that
I,
as
someone
who
used
to
be
a
teacher,
we
don't
have
a
culture
of
like
rewarding
and
like
lifting
teachers
up
into
leadership
positions
and
like
saying
your
experience
is
important,
so
important
that
we
think
it
is
critical
to
like
elevate
your
position
and
like
this,
like
one
of
the
most
important
core
conversations
in
in
a
programming.
Language,
I
think,
is
super
useful,
there's
only
so
many
ways
to
say.
D
B
I
can
definitely
agree
teaching
rest.
My
myself
on,
for
example,
workshops
this.
The
one
of
the
one
of
the
things
is
that
there's
there
not
many
places
where
you
can
exchange
what
other
teachers
on
what
is
hard
for
you
what's
hard
for
me,
there's
some
things
that
are
really
really
hard
for
me
to
explain
in
rust,
and
then
I
talk
to
someone
else
and
they're
like
I
got
a
five-minute
explanation
here.
B
This
is
this
is
how
I
do
it
and
then
it
sticks,
and
so
that
will
I'm
trying
to
work
around
the
word
multiplier
here.
B
Making
sure
that
the
this
knowledge
travels
will
improve
that
situation,
that
situation
a
lot.
D
D
So
we
got
a
question
on
the
hashtag
and
I
know
we're
a
little
over
time,
but
it
is
a
question
that
I
actually
haven't
heard
anybody
ask
us
yet
and
it
gives
us
an
opportunity
to
talk
about
an
aspect
of
the
foundation.
I've
wanted
to
talk
about
it's
really
long,
which
means,
I
think,
if
I
put
it
on
the
screen,
it's
gonna
like
mask,
but
let's
see
it's
not
gonna
match.
D
Okay,
that
actually
wasn't
too
bad,
so
I
don't
know
mark
if
you
want
to
intro
the
question.
A
Yeah
so
sure
has
been
sort
of
under
maintained
for
a
while,
while
folks
are
free
to
fork
it
without
official
backing.
Forking
might
just
make
matters
worse.
Any
thoughts
on
that
so.
D
Well,
I
always
have
thoughts
it's
true,
so
the
thing
I
want
to
say
is
I
I
don't
want
to
give
any
sort
of
definitive
or
non-definitive
answer
about
the
maintenance
status
of
surday,
but
what
I
I
can
call
out
is:
I
have
rust
crates
that
have
extremely
questionable
maintenance
and
we
can
use
those
to
talk
about
it
instead
of
potentially
calling
out
on
surveys.
D
So
we
can
talk
about
ashley's
crates
and
how
completely
under-maintained
they
are,
and
I
think
what
this
talks
about
is
so
a
thing
we
haven't
said
about
the
russ
foundation
is
that
the
rust
foundation
is
going
to
kind
of
have
the
rust
project
and
the
rust
project
contains
multitudes,
and
one
of
those
multitudes
is
craze.
Io
and
cargo,
and
I
love
package
management.
D
I'm
gonna
retire
and
become
a
ups
driver,
probably,
but
like
that
one
of
the
key
decisions
with
releasing
rust
was
that
we're
gonna
have
a
first
class
package
manager
and
that
what
a
first
class
package
manager
really
means
is
that
your
ecosystem
of
packages
is
also
a
first-class
feature
of
the
language,
which
means
you,
if
you're
not
trying
to
figure
out
how
to
better
support
your
ecosystem
authors
and
like
focusing
not
just
on
the
project
sustainability,
but
like
understanding
that
the
ecosystem
sustainability
is
part
of
your
project.
D
Sustainability
like
if
you're
not
doing
that,
you're
making
a
huge
mistake.
So
for
the
very
first
like
when
we
open
the
doors
to
the,
not
physical
foundation
in
in
january,
this
will
not
be
fully
established.
But
I
100
believe
that
being
able
to
focus
on
supporting
ecosystem
authors
here
in
the
foundation
is
is
going
to
be
a
really
critical
thing.
There's
some
models
out
there
that
exist
like
one
of
the
things
that
I
think
would
be
a
huge
mistake
and
completely
not
in
the
spirit
of
rust,
would
be
to
have.
D
Our
ecosystem
packages
have
to
compete
with
the
rust,
like
language
itself.
For
resources,
that
is
not
an
alignment
of
incentives
that
I
am
interested
in,
and
I
don't
want
that
to
happen
because
these
things
work
together.
They
don't
work
without
the
other,
and
so
I
think
that
we
need
to
create
an
affordance
of
supporting
these
things.
That's
aligned
how
you
pull
this
off
is
is
always
very
interesting.
D
I
think,
and
we
want
to
be
able
to
maintain,
obviously
the
independence
of
ecosystem
authors
and
things
like
that,
but
it's
something
I'm
really
excited
to
to
kind
of
work
with
the
foundation
to
figure
out
how
to
design
just
because
I
think
it's
really
important
and
the
last
thing
I'll
say
is
here:
it
says
you're
free
to
fork
it,
but
that
just
might
might
make
matters
worse.
D
Yeah
I
I
talked
about
space
communism,
but
earlier,
but
like
yes,
you
can
always
fork
and
forking
is
not
always
this,
like
huge
evil
thing
that
I
think
a
lot
of
people
talk
about,
but
it's
always
been
the
vibe
of
rust,
at
least
in
my
opinion,
that
in
situations
where
we
can
work
together,
we
would
prefer
to
work
together
and
it
just
turns
out
that
sometimes
working
together,
it
takes
a
lot
of
effort.
D
Like
I
know,
I
have
some
crates,
for
example,
where
they
are
under
maintained
and
folks,
there's
folks
who
want
to
help
and
it's.
It
actually
takes
a
lot
of
work
to
try
and
set
up
a
system
where
folks
can
work
to
help
together,
and
it's
also
that
type
of
support
that
I
could
imagine
the
foundation
could
help
off
like
offer
maintainers.
But
I
think
there's
a
lot
of
stuff
here,
but
just
to
say
like
yes
like.
This
is
a
key
thing,
at
least
top
of
my
mind.
B
So
I'll
pick
up
the
ball
and
talk
about
my
own
crates
as
well,
because
I
I
actually
have
a
own,
a
crate.
That
is
the
seventh
fork
where
someone
dropped
out
of
maintenance
and
it's
it's
in
the
exec
ecosystem.
B
So
it
had
to
be
forward
port
edge
due
to
new
things
until
finally,
in
2018
that
that
whole
thing
called
down
and
was
possible
to
write
stable
crates
in
any
case,
and
I've
tried
to
research
ways
on
how
this
project
evolution
goes
and
how
the
handover
goes
and
found
that
there's
not
a
lot
of
structure
in
open
source
project
currently
and
not
a
lot
of
public
writing
or
support
writing
around.
B
How
do
you
evolve
a
project
up
on
to
yourself,
leaving
the
project
a
lot
of
there's
a
lot
of
writing
on?
How
do
you
enter
open
source?
There's,
not
a
lot
of
writing
on
how
you
evolve
and
how
you,
for
example,
move
personally
out
of
it
and
one
of
the
big
problems
why
I'm
currently
not
handing
over
maintainership
is
for
the
reason
that
I
don't
want
the
next
person
to
fall
into
the
same
trap,
and
that's
my
that's.
B
My
main
fear
is
like:
will,
I
just
be
out
and
the
next
person,
just
being
the
person
that
doesn't
have,
that
does
not
have
enough
time
for
for
this
grade.
So
there's
a
lot
of
subtlety
around
this
issue,
but
I
also
think
there's
a
lot
of
opportunity
to
to
fix
that,
and
there
have
been
a
number
of
studies
recently
that
that
exactly
talk
to
what
the
exact
problem
there
is
and
project
reference
are
actually
one
of
the
big
problems.
B
These
are
things
that
currently
people
basically
have
to
solve
by
themselves,
without
a
lot
of,
without
a
lot
of
reference
to
be
had
so
also
again,
without
talking
talking
about
any
specific
things.
We're
also
seeing
this
within
within
the
rus
project,
a
little
in
where
I
think
talking
about
about
support
structures.
B
How
do
we
support
people
in
the
whole
travel
through
the
rust
project
and
and
yeah,
and
help
them
making
sure
that,
for
example,
they
compare
their
components
they
maintained
when
they
move
out
and
that
there's
a
conscious
process
around
all
of
these
things
and
that
will
both
give
the
project
resilience
and
people
safety.
B
C
Is
such
a
good
pose
about
consciously
stepping
back
from
things.
D
I
was
gonna
say
you,
gotta
say
what
it
is.
Maybe
I'll
try
and
post
it
up
on
the
screen.
D
C
I
remember
the
name
is
the
problem,
so
yeah,
if
you
can
find
it
that'd
be
awesome,
but
I
have
just
one
thing
to
add,
which
is,
I
think,
you
guys
pretty
much
nailed
it,
but
I
wanted
to
add
that
this
is
like
the.
This
is
a
good
example,
I
think
of
something
that
we
did
not
try
to
solve
now,
but
that
we
wanted
to
create.
C
We
totally
think
is
in
scope
and
we
want
to
have
a
structure
that
is
able
to
address
it,
but
there's
no
way
we
could
have
done
it
up
front
right
and
some
of
the
things
that
ashley
was
talking
about
about.
You
know
supporting
maintainers
and
we
definitely
think
the
foundation
has
a
role
there,
but
it's
it's
going
to
be
up
to
the
foundation
to
and
project
you
know
to
work
together
and
figure
out
what
that
is,
and
the
best
way
to
do
that
is.
A
Okay,
so
let's
close
out.
D
Wait
I
just
wanted
to
quickly
say
this:
is
the
blog
post,
emily
dunham?
The
title
is
thoughts
on
retiring
from
a
team.
I
would
say
this
is
like
one
of
the
healthiest
open
source
perspectives.
I
have
read
in
a
while
it's
from
2018
and
it's
like
just
as
relevant
today,
so
I
think
anybody
who's
tuning
in
give
it
a
read
shout
out
to
eden,
which
is
great
all
right.
I'm
done
interrupting.
I'm
sorry.
Okay,.
A
So
to
close
this
out
since
we're
a
little
overtime
already-
and
you
know-
probably
some
of
us
need
to
get
started
with
our
day,
which
is
sort
of
awkward,
but
you
know
it's.
It's
only
been
an
hour,
let's
see,
okay,
so
what
does
success?
Look
like
for
the
foundation.
D
And
the
javascript
conferences
would
always
take
sound
bites
from
my
conference
socks
and
like
put
them
into
songs.
But
not
tell
me
so
it'd
be
like
a
surprise
like
when
the
conference
kicks
off
anyways.
B
So,
for
me,
success
of
the
rest
foundation
would
actually
look
like
that
at
some
point.
In
the
near
to
mid
future
people
will
be
able
to
see
our
practices
check
them
and
adopt
them
as
much
as
we're
adopting
other
practices.
The
worst
project
has
always
adopted
a
lot
of
practices.
From
our
background
and
for
me,
a
successful
foundation
and
like
the
the
checking
point
for
this
is
successful,
is
other
projects
looking
at
what
we
do
taking
that
and
take
putting
it
into
their
own
structures
like
not
carbon
copy,
but
be
like
this
is
good.
B
I
really
want
that.
I
think
this
is
a.
This
is
a
good
thing
and
that's
for
me,
like,
I
think,
the
most
approachable
way
to
check
a
is
the
successful.
D
Like
I,
I
want
there
to
be
a
future
where,
where
people
who
are
interested
in
contributing
to
open
source
end
up
wanting
to
contribute
to
the
rust
project
in
particular,
be
because
being
a
contributor
is
like
potentially
a
career,
it's
it's
so
well
resourced.
It's
like
why
you
might
you
know,
pick
one
airline
over
another,
which
is
just
like
the
the
rust
project
like
being
a
contributor
to
there
is
just
like
it's
nice
I
want.
D
I
want
it
to
feel
really
good,
and
I
think
that,
to
a
certain
extent,
like
we
kind
of
already
have
that
I
mean
there's
a
lot
of
like
understanding
that
the
attitude
that
our
our
leaders
and
our
our
maintainers
have
is
really
positive.
But
I
I
see
so
much
more
room
for
growth
there
and
so
yeah.
D
I
mean
this
is
the
just
very
long
version
of
nico's,
soon
to
be
auto-tuned
response
about
happy,
joyful,
maintainers,
but
like
also
yes,
happy,
joyful,
maintainers
in
a
way
that,
like
people
want
to
be
doing
it,
I
I
forget
exactly
what
it
was,
and
this
is
like
a
quote
me,
quoting
florian,
quoting
nadia
engball,
but
the
idea
that
most
maintainers
maintain
their
open
source
out
of
guilt.
Like
I
know,
I
said
this
in
the
last
room
too,
but,
like
I
feel
this
so
hard,
I
talked
about
my
unmaintained
crates.
D
It's
like
a
constant
source
of
anxiety.
I
guess
I've
said
this
a
lot.
I
have
an
anxiety
problem,
but,
like
I,
I
want
there
to
be
a
different
future
there
and
I
think
that
the
rust
foundation
gets
to
be
a
player
in
building
that
and
so
the
closer
we
get
to
that
future.
Like
the
more
it
feels
like
success
to
me,.
A
I
yeah
that
all
sounds
great
to
me
anyway.
I
guess
I
don't
know.
How
are
we
closing
this
out?
Officially,
we
don't
have
like
a
next
session,
so
I
can't
reference
anything.
I
guess
you
can
ashley.
Can
we
get
the
like
faq
link
on
the
screen
so
that
people
can
read
more
background
information.
B
The
final
content
is
not
the
closing
of
music.
The
final
countdown
is
actually
the
video
that
needs
to
be
posted
five
minutes
before
the
community
meeting.
D
I
was
explaining
this
to
nico
the
other
day
that
we
used
to
do
that
before
every
community
team
meeting
we'd
do
a
little
countdown
and
everyone
would
post
not
just
the
final
countdown
but,
like
weird
covers
of
the
final,
I,
like,
I
feel
like
I
learned
like
we
sat
solved
that
song,
like
all
the
different
possible
permutations
of
presenting
the
final
countdown.
That's
a
good
good
thing,
so
I
mean
I
guess
we
can
say
a
couple
things
about.
D
So
we
have
at
least
maybe
a
few
blog
posts
that
we're
gonna
come
out
with
next
week,
and
then
we
kind
of
hit
this
golf
of
holiday
season,
but
we're
gonna
kick
off
and
we're
gonna
be
right
back
on
this
conversation
with
a
bunch
of
announcements
and
more
details,
so
we'll
be
kind
of
closing
things
out
with
blog
posts
in
the
upcoming
week
and
then
get
ready
in
january.
D
I
will
say
that,
with
at
least
the
one
blog
post,
we
will
be
announcing
a
survey
to
ask
you
all
like.
Do
you
like
this
format?
Was
this
fun
for
you?
So
you
all
were
so
great
about
answering
the
temperature
survey,
and
so,
if
you
are
watching
and
are
excited
or
maybe
not
excited
to
take
another
survey,
we'd
love
to
hear
what
you
thought
about
the
activities
that
we've
done
this
week,
so
that
we
can
figure
out
ways
to
make
them
better.