►
From YouTube: 2022-03-21 Cross Team Collaboration Fun Times (CTCFT)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
let's
try
that
again
so
hello.
This
is
nico
matsakis.
Welcome
to
the
march
21st
ctcft
before
we
get
started
just
a
couple,
brief
things,
as
always:
we're
governed
by
the
rust
code
of
conduct,
which
I
will
briefly
summarize
in
this
context
as
be
polite
and
respectful,
but
you
can
read
it
for
the
full
details
and
these
are
our
moderators,
the
members
of
the
ctcft
team
and
you
can
email
the
rest
mods.
A
If
you
have
any
concerns
beyond
that
in
general,
we
usually
stick
to
camera
and
audio
muted,
if
you're
not
talking,
but
if
you'd
like
to
speak,
you
can
turn
on
the
video
as
a
kind
of
signal
and
that's
always
kind
of
nice
to
have
the
the
people
who
are
actively
speaking
having
their
video
on
if
you're
not
comfortable
with
that
or
you'd
rather
not
speak,
you
can
leave
notes
in
the
chat
to
join
the
queue.
So
I
have
a
few
announcements
before
we
get
into
the
meeting
proper.
A
One
of
the
things
we're
trying
to
do
is
get
more
structured
in
the
way
that
we
pick
topics
for
the
ctcft,
and
so
what
we
plan
to
do
is
every
meeting
like
this
one
will
announce
a
theme
for
the
next
meeting,
as
well
as
the
date
and
time
and
then
we're
hoping
that
you
all
will
submit
talk
ideas.
So
the
idea
is
next
meeting
april.
The
theme
is
going
to
be
learning,
which
is
a
pretty
big
broad
theme.
A
That's
intentional,
so
you
can
interpret
that
in
many
ways
and
if
you
have
some
thoughts
of
something
that
might
be
a
nice
fit
for
that,
you
can
open
an
issue
here
on
the
ctcft
repo
and
you
see,
there's
a
custom
template
just
waiting
for
you.
A
My
talk
idea,
okay
and
we
will
assemble
a
theme
or
we'll
assemble
an
agenda
based
on
the
ideas
people
suggest,
I
think,
we'll
probably
assemble
it
next
week.
If
we
get
any
enough
ideas,
so
do
it
soon,
if
you
have
one,
but
also
you
can
suggest
themes
for
future
months
and
if
you
just
have
some
talk
ideas
that
don't
fit
that's
fine,
you
know
the
remedy.
Is
the
same
no
matter
which
of
these
things
you'd
like
to
suggest
open
an
issue,
you
can
always
chat
on
the
ctcft
stream
on
zulip
as
well.
A
So
on
that
note,
this
is
the
next
meeting
it's
in
a
much
later
time
slot
than
this
one,
because
it's
the
more
asia
friendly
time
slot.
So
here
it
is
the
third
monday,
as
ever
nine
nine
pm.
My
time
here
are
some
select
other
other
times
and
the
theme
will
be
learning
all
right,
great.
So
well,
I
guess
any
questions
on
that
before
I
go
forward.
A
Hearing
none,
okay,
so
here's
the
agenda
for
this
meeting.
It's
pretty.
I
got
a
pretty
exciting
lineup,
especially
the
second
half,
in
my
opinion,
so
first
opening
remarks.
That's
what
you're
hearing
right
now
then
josh
chiplet
and
I
are
going
to
talk
some
about
the
lang
team,
road
map
and
the
part
I'm
excited
about.
We
have
beck
the
executive
director
of
the
russ
foundation,
rebecca
rumble
who's,
going
to
present
kind
of
an
overview
of
what
the
rust
foundation
is
up
to
this
year.
A
So
with
that,
I
guess
from
there
I
will
we'll
lead
right
into
the
roadmap
discussion,
any
comments
or
things
before
I
do
that
last
chance.
Okay,
great
now,
I
just
realized.
I
don't
have
the
slides
set
up.
So
let's
do
that.
A
Okay,
josh!
Are
you
ready?
Look
good,
okay,
so
yeah
we
have
this.
We
josh
triplett
and
I
as
well
as
other
people
on
the
laying
team,
have
been
working
on
a
kind
of
draft
roadmap.
You
can
see
it
here
as
well
that
we
would
like
to
get
some
feedback
on.
The
idea
of
this
roadmap
is
to
help
define
our
you
know,
help
focus
ourselves.
A
What
are
the
things
we're
going
to
be
paying
attention
to
guide
the
decisions
that
we
make,
but
also
to
steer
external
contributors?
Who
would
like
to
support
rust
into
areas
where
we
would
really
like
to
see
support
and
to
help
us
think
kind
of
long
term
right
so
part
of
we
started
out
with
with
a
2022
roadmap
but
realized
that
at
least
it
made
sense
to
think
about
2024
as
kind
of
the
next
rust
edition.
A
What
are
the
things
that
were
most
important
for
us
to
do
to
set
ourselves
up
in
a
position
that
we're
having
a
good
story
then
about
what
we
want,
and
so
I
just
wanted
to
talk
a
little
bit
about
the
way
that
I
at
least
have
thinking
about
this,
and
you
know,
I
think
we
all
know.
Russ's
mission
is
kind
of
empowering
everyone
to
build
reliable,
efficient
software,
but
you
can
go
a
little
deeper
and
ask
yourself
sort
of
for
rust,
where,
where
is
rust,
the
best
choice
right?
A
We
know
it's
not
going
to
be
the
best
choice
everywhere.
No
one
language
could
be
that.
So,
where
does
rust?
Where
will
we
endeavor
at
least
to
make
rust
the
best
choice
or
one
of
the
best
choices?
And
I
would
say
that
you
know
rust's
key
area
is
environments
where
research
resource
usage
security,
those
things.
These
are
the
top
considerations
right.
If
those
are
your
top
considerations,
rust
is
hands
down
an
excellent
choice
for
that
I
like
to
think
of
it
as
like.
A
stitch
in
time
saves
nine.
A
If
that's,
if
that's
your
attitude,
rust
is
going
to
help
you,
because
we're
going
to
bring
a
lot
of
concerns
up
front
and
make
sure
you
address
them.
Well,
on
the
other
hand,
you
know
if
your
attitude
is
like.
I
need
to
get
this
out
the
door
as
quickly
as
possible.
I
don't
care
if
it
has
some
bugs.
A
Maybe
a
rust,
isn't
the
right
choice
for
you
and
I
think,
that's
a
perfectly
legitimate
way
to
feel
about
your
code
right,
and
so
I
think
we
can
see
that
we've
had
a
lot
of
success
with
rust
in
these
areas
where
one
of
those
three
things
is
really
important.
Right.
Like
networking
cloud
infrastructure,
it's
reliability,
it's
performance,
those
things
are
key.
A
Embedded
development
is
kind
of
getting
access
to
these
controlling
resources
really
tightly
and
having
access
to
the
full
capabilities
of
the
machine
same
with
kernel,
I
think
cli
applications
have
been
pretty
cool
area
for
us,
which
is
a
little
bit.
Maybe
they
don't
quite
fit
into
that
framework,
but
I
think
they
actually
do
like
the
reason
that
we've
had
so
many
great
cli
applications.
A
lot
of
it
is
stuff
like
rip
grap
or
whatever
that
end
up,
even
though
you
think
a
cli
application
might
be
more
like
a
toy
actually
right.
A
A
So
that's
really
good
and
I
think
rust
is
doing
really
well
in
those
areas
where,
like
we
have
a
niche
and
we're
doing
really
well
in
that
niche,
and
it's
a
big
one
and
an
important
one.
So
I'm
happy
with
that.
At
the
same
time,
it's
good
for
us
to
think
about.
A
Okay.
We
know
we
do
well
when
resources
or
whatever
are
the
most
important,
but
what
about
when
they're
really
important,
but
maybe
not
the
most
right?
Maybe
time
to
market
is
like
equally
important
or
something
and
how
far
down
can
we
stretch?
How
much
can
we
make
it
so
that
rust
is
how
much
can
we
brought
in
that?
That
range,
where
rust
is
a
really
good
choice?
A
A
This
is
sort
of
scaling
out
continuing
to
push
on
the
boundaries
of.
Can
we
make
rust
easier
to
use
so
that,
even
if
you
don't
care
as
much
about
reliability,
you
probably
would
you
might
still
pick
rust
right
and
we
push
that
boundary
out.
As
far
as
we
can
go
and
then
the
other
one
is
is
really
focusing
on
enablers
for
the
ecosystem,
because,
as
josh
will
talk
more
about
one
of
the
things
that
we've
seen
is
you
know
in
rust?
A
Such
a
big
part
of
our
success
comes
about
because
we
have
so
many
great
people
building
great
libraries,
and
what
can
we
do
to
make
it
possible
on
the
language
side?
But
I
guess
in
the
project
overall
to
build,
make
building
libraries
and
maintaining
them.
You
know
even
easier
and
even
more
powerful
and
finally,
we'll
kind
of
never
be
able
to
do
either
of
these
things.
If
we
don't
do
a
good
job,
organizing
our
open
source
contributors
and
our
organization
and
helping
the
rus
project
itself
scale
up.
A
So
in
a
way,
this
is
actually
the
most
important
focusing
on
our
parts
of
our
process
and
other
things
where
that
turn
people
away
so
that
they
don't
come
and
contribute
or
just
don't
guide
them
as
effectively
towards
the
places
where
they
can
make
an
impact.
B
A
A
This
is
my
my
ascii
art
of
saying
you
know
we
want
to
make
sure
at
the
same
time
we're
serving
existing
users
really
well,
that's
kind
of
this
angle
going
from
rough
to
polished,
and
I
think
we
definitely
have
some
rough
areas
where
we
need
to
get
better,
but
we
also
want
to
be
broadening
out
on
this
way
as
well
to
get
as
much
area
in
this
chart
as
possible,
and
this
is
what
I
wanted
to
get
at
and
I
was
missing.
We
believe-
or
at
least
I
I
do.
A
I
think
I
speak
for
josh
here-
that
this
roadmap
is
like
a
start
for
what
a
rust-wide
product
roadmap
would
be
right.
A
In
many
cases
right,
it
may
have
more
to
do
with
tooling
or
or
compiler
team
robustness.
Things
like
that,
okay,
so
the
last
thing
I'll
say
is
this
is
kind
of
an
initial
roadmap.
I
think
it's
kind
of
a
combination
of
what
do
we
think
we
can
do
for
2024,
but
also
what
do
we
need
to
focus
on
the
most
right
now?
If
we
only
got
to
do
one
year's
worth
of
work,
what
would
it
be
so
there
we
go
with
no
further
ado.
A
Let
me
dive
into
those
three
themes
that
we
talked
about.
A
But
I
think
these
categories
are
kind
of
the
four
big
groups
that
at
least
of
things
that
I'm
thinking
about
right
now,
right
one
is
taking
the
analyses
that
we
do
and
making
them
more
precise
and
just
kind
of
lowering
the
the
rigmarole
of
writing
rust
right.
So
that
might
mean
making
polonius
more
accurate
or
sorry
making
the
borrow
checker
more
accurate
so
that
it
accepts
more
code.
A
It
might
mean
things
like
implied
bounds
that
we've
been
thinking
about
for
a
while,
so
you
have
to
write
fewer
where
closes
basically
places
where
there's
redundancy
in
the
system.
That's
not
actually
helping
us.
Redundancy
can
be
useful
for
reliability,
but
sometimes
it's
just
kind
of
red
tape
trying
to
find
those
places
and
remove
it
and
let
the
compiler
figure
out
more
stuff.
A
The
next
section
is
kind
of
express
yourself
more
easily,
so
here
there's
there's
just
parts
of
rust.
I
think
let
else
is
a
classic
example
of
a
release.
Sort
of
small
scale
feature
that
could
have
a
big
impact
where
you
have
to
learn
a
certain
workaround.
If
you
want
to
do
this
thing
in
rust
right,
it's
totally
doable,
but
you
have
to
learn
the
way
to
do
it
and
then
maybe
you
have
to
get
some
external
crate.
A
It
may
mean
you
have
some
pattern
and
until
you
know
that
you
can
often
just
kind
of
get
stuck
and
not
realize
the
trick
for
it
and
so
trying
to
find
ways
to
either
eliminate
that
trick
or
or
just
directly
express
it
so
that
it's
more
obvious
can
help
rust.
Feel
more
productive
and
feel
natural
and
easier
to
learn.
A
Next
thing
would
be
async.
I
think
this
kind
of
overlaps
with
some
of
the
others,
but
you
know-
we've
been
working
on
async
fn
for
a
while.
We
have
this
async
roadmap
and
we
went
through
this
async
vision
dock
process
and
we
need
to
support
that
and
keep
it
moving.
A
And
finally,
one
of
my
pet
peeves
at
least
is
working
a
lot
on
din
trait,
because
I
think
din
trait
gets
a
lot
of
usage
and
it
has
a
lot
of
rough
edges
hasn't
really
gotten
a
lot
of
love
since
it
was
first
created
and
there's
there's
a
lot
of
just
ergonomic
challenges
here,
like
there
are
things
you
can't
do
in
traits
that
use
dynamic
dispatch
that
it
would
be
nice
if
they
worked
like
by
value
self
or
taking
infiltrate
parameters,
and
we
can
make
them
work
and
then
there's
also
kind
of
some
soundness
conditions
to
resolve
and
just
in
general,
some
work
to
do
there,
and
I
think
that's
going
to
be
a
focus
area
for
us.
A
So
I'm
going
to
skip
past
this
slide,
because
I
kind
of
did
it
in
in-house,
but
here
are
some
examples
of
things
that
are
underway
that
fit
this
category
and
I'll
highlight
the
one
I
didn't
mention
explicitly
so
far.
Then
upcasting
is
an
example
of
something
we
can
make
work
better.
So
if
you
have
a
subtrait
today,
you
can't
easily
convert
it
into
a
din
of
a
super
trait.
We
have
an
initiative
mostly
done
that
lets
that
work
and
hopefully
that
will
stabilize
soon.
A
So,
if
you're
interested
in
hacking
on
that
kind
of
stuff,
you
can
check
out
the
ongoing
initiatives.
If
you
have
ideas,
there's
a
zoolop
stream
which
josh
will
give,
which
is
in
the
slides
later,
where
you
can
come
in
and
bring
up
kind
of
float
new
ideas
in
that
vein.
But
at
this
point
I'm
going
to
hand
it
off
to
josh
to
talk
about
the
other
two
themes.
C
You
are
excellent.
Okay,
I'm
josh
triplett,
I'm
gonna
walk
through
the
two
remaining
themes,
helping
users
help
each
other,
as
well
as
helping
the
rust
project
scale
so
that
we
can
get
any
of
these
things
done.
So,
first
of
all,
we've
talked
about
rust,
empowering
people
and
that's
not
just
about
our
end
users.
C
It's
a
team
effort
in
that
a
big
part
of
what
we
do
in
the
language
is
to
help
the
standard
library
and
the
huge
rust
library
ecosystem
on
crates
I
o
and
elsewhere,
to
continue
to
be
a
great
strength
of
the
rest
language,
and
we
want
to
scale
that
further.
We
want
to
empower
the
standard
library
authors
as
well
as
authors
of
libraries
in
the
ecosystem.
C
C
We
want
to
provide
some
richer
abstractions
that
make
it
easier
to
express
common
patterns
that
happen
in
libraries.
C
We
want
to
make
it
easier
to
migrate
things
into
the
standard
library
or
migrate
things
from
experimental
libraries
into
more
foundational
libraries
in
the
ecosystem,
and
there
is
a
proposal
underway
from
jane
lesby,
specifically
to
support
disambiguation
of
methods
on
the
basis
of
what
rust
edition
your
crate
comes
from.
This
is
something
that
typically,
the
language
has
gotten
huge
mileage
out
of
the
edition
system
for
allowing
us
to
evolve
the
language
without
backwards
compatibility
issues
by
allowing
you
to
opt
into
three
years
worth
of
language
changes
at
a
time.
C
The
library
ecosystem
and
even
the
standard
library
have
gotten
very
little
success
out
of
editions
because
we
haven't
made
the
facilities
available
to
tie
things
to
rust,
editions,
so
we're
wanting
to
fix
that
and
make
it
so
that
we
can
add
something
to
the
standard
library
that
is
used
from
an
incredibly
widely
used,
rust
crate
without
breaking
all
of
the
users
of
that
widely
used
rust
crate.
We
want
to
make
it
so
that
a
popular
foundation
framework
can
add
things
that
an
experimental
crate
showed
were
valuable
without
breaking
the
users
of
that
experimental
crate.
C
We
also
want
to
improve
our
story
for
interoperability
between
crates,
so
right
now,
we've
built
async
await.
We
made
that
available.
Many
many
people
built
libraries
and
foundations
and
whole
frameworks
around
this,
and
this
is
in
and
of
itself
part
of
the
problem
now,
where
higher
level
libraries
trying
to
build.
On
top
of
those
now
face
a
choice
of
well:
what
do
I
build
on?
C
There's
too
many
different
possibilities,
so
we
are
looking
to
improve
async
portability,
first
of
all
of
pulling
things
into
both
the
library
and
the
language
that
will
make
it
possible
to
write
code
that
doesn't
care
what
async
runtime
you
run
on
or
what
frameworks
you
use
we're.
Also
looking
at
adding
global
or
scoped
capabilities
which
will
allow
you
to
have
code
that
needs
an
async
runtime
that
can
depend
on
the
properties
of
some
trait
that
provides
an
async
runtime
without
having
to
pass
that
async
runtime
to
every
single
function
in
your
program.
C
Just
so
that
you
can
call
it
in
case.
You
need
it
so
kind
of
an
ambient
capability
mechanism
for
give
me
the
current
runtime,
please,
and
then
we
want
to
improve
some
things
in
coherence
which
I
will
get
to
in
a
little
bit.
But
in
general
we
want
to
make
it
possible
to
glue
libraries
together
in
more
interesting
ways
without
being
limited
by
the
properties
of
the
type
system
that
make
it
difficult
to
extend
crate,
a
or
crate
b
from
outside
of
either
crate
a
or
crate
b.
C
So
some
future
work
that
we
would
like
to
work
on.
That
does
not
yet
have
an
owner,
but
we're
very
excited
about.
Nonetheless,
the
standard
library
has
the
ability
to
provide
stability.
Markers.
This
feature
is
stable.
You
can
use
it
from
stable
rust.
This
feature
only
works
in
nightly
rust.
We
want
to
give
a
similar
facility
to
users
of
libraries
in
the
ecosystem.
You
can
mark
your
apis
as
unstable
and
people
currently
already
do
this
using
cargo
feature
flags.
They
might
have
an
unstable
this
or
unstable
that
feature
flag,
but
this
is
non-standard.
C
It's
kind
of
custom
done
using
features,
which
means
it's
not
standardized
in
a
way
that
we
could
add
more
tooling
around.
So,
for
instance,
you
should
have
control
at
your
top
level,
crate
or
intermediate
libraries
about
whether
your
dependencies
are
opting
into
nightly
features
of
their
dependencies,
so
that
you
know
you
won't
break
with
a
new
upgrade.
Otherwise
you
lose
control
over
stability.
You
feel
like
you're
using
stable
rust,
but
you
get
a
worse
experience.
C
We
also
want
to
give
libraries
the
ability
to
tailor
the
developer
experience
with
custom
diagnostics,
with
lints
with
tools
to
say,
hey,
here's,
how
you're
doing
a
common
misuse
of
our
api.
This
is
a
facility
we
have
in
the
standard
library
all
the
time,
but
we
don't
have
it
in
the
library
ecosystem.
So
we
get
complex
error
messages
instead
of
much
more
straightforward
ones
that
we
could
have,
and
then
we
want
better
tools
for
interoperability.
C
Things
like
right
now.
If
you
want
to
glue
crate
a
together
with
crate
b,
you
need
to
be
either
part
of
crate
a
and
depend
on
crate,
b
or
part
of
crate
b
and
depend
on
crate
a
that's,
not
a
process
that
scales
well,
when
there
are
too
many
different
ways,
people
might
want
to
glue
things
together
and
a
database
shouldn't
need
to
depend
on
a
random
library
just
to
make
that
library's
types
usable
within
the
database
select
statements.
C
That's
the
kind
of
thing
where
you
should
be
able
to
have
a
third
party
glue,
crate
that
puts
the
two
of
them
together,
but
things
like
coherence
in
our
type
system.
Don't
let
you
do
that,
so
all
sorts
of
features
we
want
to
add
there,
then,
as
nico
said,
there's
very
little
we're
going
to
be
able
to
get
done
if
we
cannot
scale
our
ability
to
develop
the
rust
language
so
going
on
to
this
next
slide
yeah,
we
know.
Oh.
A
C
Might
work
no
apparently
not
apparently
not
okay,
all
right,
so
we
we
want
to
help
the
rust
project
scale
within
our
team
and
provide
processes
that
other
teams
may
be
able
to
adopt
or
adapt
as
they
see
fit
and
part
of
the.
This
is
actually
one
slide
too
far
ahead.
Can
you
go
back?
C
Thank
you.
Part
of
the
issue
is
that
the
rust
community
is
growing
very
rapidly,
but
for
logistical
reasons,
teams
don't
grow
at
the
same
rate.
You
watch
rust
communities
grow
faster
than
linearly.
C
Our
three
big
goals
here
are
that
we
want
to
make
it
easier
to
see
what
we
are
doing
and
what
other
teams
are
do
and
sub
teams
and
working
groups
are
doing
at
a
glance
figure
out.
Hey
there's
this
particular
work
that
I
care
a
deep.
I
care
deeply
about
that.
My
software
is
going
to
depend
on
it's
currently
nightly.
C
When
is
it
going
to
stabilize,
or
is
it
ever
going
to
stabilize
at
all?
How
can
I
help
you
should
be
able
to
see
that
very
easily?
We
want
to
make
sure
that
every
initiative,
every
effort,
every
experiment-
has
a
clear
owner-
has
regular
communication.
It's
easy
to
figure
out
who
you
should
talk
to
and
who
you
should
work
with
and
we're.
C
Looking
to
build
processes
with
better
tooling
support
that
make
it
easier
to
quickly
experiment
and
similar
and
going
on
to
what
I
think
is
the
last
slide
here
we
have
a
number
of
things
underway
in
this
area.
We
have
an
initiative
system
that
we've
talked
about
before
that
we're
very
excited
about.
C
We
have
a
project
board
linked
here
when
we
send
out
the
slides,
we're
doing
a
regular
backlog,
bonanza
effort
that
allows
us
to
get
hold
of
our
backlog
and
close
out
things
that
aren't
ever
gonna
stabilize
and
get
other
things
on
a
track
to
actually
stabilize
we're
doing
more
work
to
stabilize
and
ship
features
that
people
are
using.
People
are
excited
about,
but
had
just
stalled
out.
C
We
have
a
whole
new
consensus
process
and
tooling
that
we're
using
to
augment
and
replace
the
rfc
bot
process
that
will
help
us
improve
the
ability
to
quickly
make
decisions
that
can
just
as
easily
be
reversed
things
that
aren't
committing
to
stabilization
stabilization
for
the
foreseeable
future,
enable
more
experimentation
make
it
easier
and
lower
friction
for
people
to
raise
concerns
and
dissent.
This
is
easily
something
we
could
give
a
whole
talk
on
all
on
its
own
and
we're
also
starting
a
couple
of
new
sub
teams.
One
of
them.
C
The
types
team
is
helping
to
concentrate
the
expertise
around
deep
type
type
system
and
trait
theory,
and
how
to
put
all
of
those
together.
Niko
is
driving
a
lot
of
that
effort
and
we're
also
reviving
the
old
style
team
to
help
make
sure
that,
as
we
add,
new
language
features
how
to
format.
Those
in
a
standard
way
is
something
we
check
and
scale
and
don't
just
leave
by
the
wayside
to
catch
up
after
we've
shipped
a
feature.
C
C
And
if
you
want
to
help
us
with
any
of
these
things.
If
you
want
to
head
up
an
item,
if
you
see
an
item
that
you
want
to
work
on,
or
if
you
want
to
add
to
this
list
within
these
themes,
then
there
is
a
lang.
Road
map,
2024,
zulip
stream
and
you're
also
welcome
to
private
message,
either
nico
or
myself
on
zulip.
If
you
want
to
chat
about
these
privately
before
starting
a
public
discussion.
A
A
Thanks
josh,
so
I
would
love
to
take
questions,
but
I
also
want
to
make
sure
we
have
enough
time
for
back.
So
what
I'm
going
to
do
is
say
if
you'd
like
to
talk
about
this
either.
That's
and
I
totally
want
to
hear
what
you
have
to
say
and
any
thoughts,
especially
on
where
other
teams
might
fit
in
or
if
there's
something
missing
from
this
just
for
the
laying
team.
A
Let's
talk
about
it
in
the
social
hour
or
on
zulip
afterwards,
but
for
now
I'd
like
to
turn
over
to
beck
and
go
from
there
beck.
Are
you
gonna
share
anything
or
do
you
just
wanna
chat.
D
B
I
I
will
do
just
very
quickly.
It's.
A
Mostly
that
I
will
have
to
give
you
permission,
so
let
me
do
that
in.
C
A
I
I
will
turn
off
my
video
and
hand
it
over
to.
B
Don't
worry,
I
I
didn't
put
a
big
thing
together
anyway,
because
I
thought
it'd
be
easier
just
to
start
through
okay.
Well,
firstly,
thank
you
very
much
for
for
inviting
me
along
today.
It
was
actually
really.
I
found
it
really
useful
sitting
in
on
on
the
first
half
and
hearing
about
your
plans,
one
of
the
the
things
that
we're
really
interested
in
is
are
the
kind
of
road
maps
that
the
teams
are
putting
together
so
really
useful
to
see
what
what
your
priorities
are.
B
Obviously,
I'm
here
to
talk
about
the
rest
foundation
and
our
kind
of
plans
for
2022
what
we
think
our
work
programs
and
our
priorities
should
be
and
what
we've
been
doing
so
I'll,
probably
only
talk
for
about
10
minutes
or
so
at
most
and
obviously
enable
people
to
answer
questions
so
our
key
priorities.
I
think
one
of
the
most
asked
questions
that
I've
had
since
I
started
from
people
is
well
what
is
the
best
foundation?
B
What's
it
for,
and
I
think
we're
starting
to
get
better
at
answering
that,
but
I
think
we
still
have
a
little
way
to
go.
So
one
of
our
kind
of
key
priorities
is
to
actually
develop
the
the
narrative
around
the
foundation
around
rust.
You
know
niko
kind
of
said
at
the
beginning
here
I
think
everyone
understands
what
kind
of
rust
is
for
and
what
the
kind
of
mission
and
vision
is
there.
I
think,
as
the
foundation,
we
need
to
kind
of
hone
a
little
bit
more.
B
What
our
role
is
in
that
so
figuring
out
kind
of
the
narrative
of
what
the
foundation
is
going
to
do,
how
we
are
going
to
steward
the
rest
programming
language
and
how
we
work
with
other
people
to
do
that,
and
indeed,
where
we
think
we're
going
with
it
as
well
and
again,
a
lot
of
them.
A
It
seems
like
we
lost
beck's
connectivity,
hopefully
she'll
be
back,
I'm
trying
to
come
up
with
something
entertaining
in
the
short
in
the
meantime.
A
A
B
Sorry
internet
excited
break
up
that.
I
can't
remember
I
don't
I
don't
know
exactly
where
I
got
booted
off.
I
think
you
said
what
did
I
say.
A
Figuring
out
where
the
rust
foundation
fits
in
to
russ's
overall
mission
and
and
so
forth,
that's
the
last
thing.
B
So
yeah
identifying
the
problems
and
gaps
in
our
priorities
is
is
kind
of
key.
You
know
we
don't
want
to
invest
in
areas
that
actually
need
no
help.
We
want
to
make
sure
that
we're
kind
of
shoring
things
up
as
and
where
things
are
necessary,
and
how
that
you
know
how
that
builds
into
to
achieving
that
narrative
that
I
was
talking
about.
B
Obviously
providing
support
is
one
of
the
big
ones.
We
want
to
make
sure
that
we
are
providing
the
right
support
to
the
community,
to
the
project
teams,
to
the
working
groups
and
figuring
out
how
we
can
do
that
best,
and
we
also
obviously
have
stakeholders
and
members
we're
looking
at.
B
You
know
prioritizing
how
we
can
support
cooperation
and
collaboration
to
deliver
what
stakeholders
need,
but
also
to
make
sure
that
we're
leveraging
as
much
benefit
as
possible
from
the
corporate
that
want
to
support
rest
and
and
the
community,
so
those
are
kind
of
our
key
priorities
in
terms
of
how
that
translates
into
work
programs.
B
I've
kind
of
broken
these
down
into
three,
so
there's
our
there's
our
infrastructure
support.
So
obviously,
these
are
kind
of
big
structural
things
like
negotiating
and
displaying
the
credit.
We
need
the
crates
dot
io
on
call.
We
are
working
to
identify
what
kind
of
ongoing
human
resource
needs.
There
are
so,
for
instance,
we're
working
with
the
infrastructure
team
at
the
moment
to
figure
out
potentially
what
what
kind
of
higher
might
be
useful
for
them.
B
There's
also
the
cloud
compute
program,
which
is
now
kind
of
getting
up
and
running,
so
the
infrastructure
support
is
trying
to
obviously
shore
up
the
kind
of
things
that
hopefully
should
just
tick
over
and
make
make
life
easier
for
everyone
there's
also
the
the
explicit
financial
support
now.
Obviously,
the
community
grants
program
is
something
that
we've
talked
about
a
lot.
B
There's
ongoing
subscriptions,
there's
potentially
specific
fundraising
for
discrete
pieces
of
work.
We
understand
that
the
financial
support
is
a
huge
thing
and
it's
something
that
some
people
are
desperate
for.
We
also
understand,
though,
that
actually
just
throwing
money
at
things
doesn't
necessarily
solve
all
problems,
that
there
are
much
much
bigger
problems
than
just
throwing
money
at
things.
B
So,
there's
a
big
role
for
us
to
kind
of
identify
where
those
gaps
are
and
understand.
Okay,
and-
and
we
already
know,
the
community
grant
program-
is
not
going
to
solve
everything,
but
what
we
do
hope
is
that
it
will
solve
some
things
and
hopefully
provide
the
people
that
do
need
it
with
with
time
and
resources
to
to
support
their
work.
B
And
thirdly,
as
I
said,
membership
development
is,
I
think,
a
really
good,
a
really
good
thing
for
us
to
be
doing.
There's
a
lot
of
love
for
us
out.
There
there's
a
lot
of
corporates,
both
big
and
small,
that
are
really
excited
about
rust
and
they
really
want
to
do
something
in
the
space
and
they
want
to
support
the
project
and
the
foundation.
Currently,
they
don't
really
know
how
a
lot
of
them,
but
they're,
very,
very
willing.
B
So
it's,
I
think,
a
priority
for
us
over
the
next
few
months
to
try
and
figure
out
how
we
can
harness
all
of
that
enthusiasm,
potentially
funding,
potentially
awesome
in-kind
donations
and
resources
to
figure
out
how
we
can
kind
of
diversify
the
benefits
for
the
project
for
the
maintainers
for
the
community.
At
large
and
to
ensure
that
you
know
we
are
also
meeting
the
needs
of
our
corporate
members
as
well.
B
You
know
figuring
out
what
their
interests
are
as
well,
because,
as
the
foundation
is
a
steward
of
the
rus
programming
language,
we
need
to
make
sure
that
we
understand
the
needs
of
everyone
using
it.
So
those
are
our
kind
of
very
key
priorities
and
the
work
programs
that
we're
focusing
on
at
the
moment
over
the
next
year
or
so
what
I'd
like
to
do
by
the
end
of
the
year
is
actually
have
a
strategic
plan
that
takes
us
through
the
next
kind
of
three
to
five
years,
that
that
is
a
far
more.
B
In
addition
to
that,
I
think
what
we'd
really
like
to
do
is
just
kind
of
deepen
the
links
between
the
foundation
and
the
project
and
the
community
we'd
like
to
diversify
a
lot
as
well.
One
of
the
things
that
we've
that
I've
been
hearing
on
some
calls
with
some
of
the
groups
around
the
world
is
that
you
know
they'd
really
like
to
be
involved,
but
they
don't
know
how
so
it'd
be
great
to
see
you
know
an
increase
in
diversity,
potentially
in
the
teams
or
in
the
community
at
large.
B
B
Since
I
came
in
sort
of
mid-november,
the
priority
has
kind
of
been
internally
organization-building,
so
making
sure
that
we
have
the
right
legal
frameworks
in
place
that
we
are
meeting
our
legal
obligations,
that
we
have
the
staff
to
actually
manage
some
of
these
priorities
and
work
programs
and
making
sure
that
you
know
we
are
financially
accountable
and
meeting
those
kind
of
obligations.
B
As
well
so
there's
been
quite
a
lot
of
things
that
that's
been
going
on
in
the
background
that
are
not
terribly
exciting
to
to
people,
but
that
have
been
necessary
to
get
the
foundation
in
a
position
where
we
can
actually
do
a
lot
of
this
work
with
confidence
and
the
fact
and
be
a
sustainable,
well-run
organization
that
is
going
to
be
around
into
the
future
to
provide
the
kind
of
support
that
we
want
to.
B
So
you
know,
that's
been
a
lot
of
writing
policies
talking
to
accountants,
talking
to
lawyers,
thinking
about
trademarks,
all
things
that
need
to
be
done,
but
aren't
obviously
of
benefit
to
everyone.
So
I
hope
that
within
the
next
couple
of
months,
the
work
that
we've
been
putting
in
you
know
preparing
the
community
grants
program
and
the
cloud
compute
some
of
these
other
things
that
that
we've,
these
other
ions,
that
we've
got
in
the
fire.
B
I
hope
that
those
will
be
a
lot
more
publicly
visible,
so
that
people
can
actually
now
point
to
things
and
say:
oh
that's
what
the
foundation's
doing
we're,
not
just
not
just
sitting
in
the
background
so
yeah.
I
think.
That's
probably
everything
I'm
happy
to
answer
any
questions
or
if
people
have
comments
or
if
people
don't
want
to
talk
up
right
now,
if
you
want
to
email
me
or
set
up
another
call,
I'm
happy
to
do
all
of
those
things.
A
Thank
you
very
much
beck
and
thanks
for
the
inside
look
also,
I
just
enjoyed
it
until
kind
of
all
the
hard
things
that
go
into
setting
up
an
organization
so
that
it
actually
runs
in
addition
to
the
flashy
stuff.
I
I
want
to
open
the
floor.
If
people
have
questions
feel
free
to
come
on
or
post
them
in
the
chat,
I
know
beck
will
not
be
here
for
the
social
hour.
She's
got
a
conflict,
but
so
this
is
a
good
time.
If
you
have
something.
A
And
actually
to
kick
it
off.
I
have
one
question
suppose
I'm
a
project
team
member.
I
work
on
rust
and
I
have
an
idea
of
something
I
think
the
foundation
should
do.
A
B
Come
talk
to
me
or
joel
marcy,
who
is
also
on
the
call
I
think
we
are.
We
are
very
very
happy
to
have
a
conversation
about
any
ideas
that
people
have
or
anything
that
they
think
the
foundation
should
be
doing.
I
don't
believe
that
we
are
all
knowing
and
I
there
are
many
many
things
that
that
we
don't
know.
That
would
be
great
to
do,
but
no
one
has
suggested
so
yeah.
B
Don't
assume
that
if
we're
not
doing
something,
it's
because
we
think
it's
a
terrible
idea
or
we
don't
want
to
do
it.
If
you
haven't
suggested
it
to
us,
then
we
can't
consider
it
so
definitely
talk
to
us.
I
can't
promise
that
we
can
do
everything
immediately,
but
certainly
we're
always
happy
to
have
a
chat.
A
Great,
so
send
you
an
email
or
something
like
that.
B
A
A
question
in
the
chat
from
from
remy
or
lqt.
He
says
I
have
a
question
or
it
says
thanks
a
lot
for
the
update
and
a
question.
Are
there?
Is
there
any
news
about
the
cloud
compute
program
for
contributors.
B
I
believe
it
is
practically
up
and
running.
Do
you
know
we
have
joel
and
hughes.
E
So
yeah
I
can
answer
that
a
little
bit
so
yeah
modulo
one
technical,
glitch
right
now
and
maybe
one
procedural
change
we
need
to
make.
As
far
as
the
terms
of
service
the
program
is
ready
to
basically
get
started
beta
testing
right
now,
we're
focusing
primarily
on
maintaining,
I
guess
the
definition
of
contributors.
Maybe
I
want
to
make
sure
I
understand.
E
I
assume
you
mean
contributors
outside
the
maintainer
realm
like
community
members,
but
if
that's
the
case,
we're
focusing
primarily
on
maintainers
to
start
just
because
we
need
to
make
sure
this
thing
is
working
right
and
and
actually
structured
correctly
before
we
open
it
up
very
much.
You
know
more
broadly,
but
the
goal
is
to
open
it
wider.
Once
we,
you
know,
sort
out
all
the
you
know,
kinks
in
in
the
program
with
the
maintainers
themselves.
So
hopefully
that
answers
the
question.
E
Oh
yeah,
you
met
maintainers,
then.
Yes,
we
are
about
to
launch
launching
with
the
maintainers
really
really
quickly
here,
just
a
couple
of
hurdles
that
we
need
to
get
over.
So.
A
F
Yeah,
just
what
I
wrote
in
chat
is
in
addition
to
talking
to
beck
and
joel
which
of
course
are
awesome,
resources
and
feel
free
to
reach
out
to
them.
If,
for
whatever
reason,
it
makes
more
sense
to
talk
to
the
project,
directors
on
the
foundation
board
were
also
happy
to
talk,
so
I
listed
out
who
those
are,
but
that's
me,
jane,
josh,
stone,
tyler,
mandry
and
mark
similacrum
so
feel
free
to
reach
out
to
us
as
well.
If
that,
for
whatever
reason,
makes
more
sense,.
D
Additionally,
hi
everyone,
I'm
nell,
a
lot
of
you
know
me
as
the
lead
maintainer
and
this
week
in
rust,
and
I'm
also
microsoft's
member
director
on
the
rust
foundation
board
feel
free
to
reach
out
to
me
anytime.
A
I
was
interested
in
back
when
you
were
talking
about
kind
of
connecting.
A
You
know,
potent
members
or
potential
members
in
terms
of
with
the
project,
in
terms
of
I'm
always
interested
to
make
sure
that
we
are
we're
spending
our
energies
well,
that
we're
meeting
people
meeting
the
needs
of
people
who
want
to
use
rust
and,
I
think,
there's
a
lot
of
research
that
could
be
done
there,
sort
of
to
make
sure
that
we're
better
informed.
A
So
I'm
wondering
like
is
that
the
kind
of
thing
you're
thinking
of
or
have
you
thought
much
about
that
how
to
kind
of
help
bridge
between
project
and
corporations
or
people
using
rust?
You
know
one
both.
B
It's
something
that
we
haven't,
we
haven't
got
an
answer
to
yet
we
are
definitely
definitely
trying
to
think
about
it
and
we're
hopeful
that
so
we're
inviting
the
corporate
members
to
to
come
to
rest
conf,
for
you
know
a
little
session
of
their
own
and
hopefully
they
will
stay.
They
will
kind
of
meet
people
throughout
the
conference.
Then
the
other
thing
that
we're
thinking
is
hopefully,
as
time
goes
on,
you
know,
especially
with
the
grants
program
and
other
other
potential
work
programs.
B
Those
companies
might
be
able
to
provide
either
resources,
employment
or
mentorship
to
people
coming
into
the
community
as
well.
Obviously
it
depends
on
their
own
resources,
but
I
think
that
there's
lots
of
potential
stuff.
I
think
we
can
do
we'd
like
to
make
sure
that
we're
doing
the
right
things
not
just
for
them,
but
for
you
all
and
the
end
users
as
well,
so
there's
lots
of
ideas
in
the
pot.
If
anyone
has
ideas,
please
come
to
us
and
let
them
let
us
know
we're
open
to
anything.
B
We
just
want
to
make
sure
that
we're
not
asking
too
much
of
anyone
on
any
side
but
yeah.
I
think
there's
like,
as
I
said,
there's
so
much
enthusiasm
from
a
lot
of,
and
I
mean
a
lot
of
the
companies
are
quite
small
as
well,
but
there's
a
lot
of
enthusiasm
there
and
it
would
be
foolish
of
us
not
to
try
and
harness
that
in
some
way
to
for
the
benefit
of
the
white
community.
B
I
suppose
it
really
depends
how
much
money
it's
gonna
cost
like
you
know.
Obviously,
obviously
I
don't
know
what
people
have
in
mind
here.
We
have
the
grants
program
opening
next
month,
that's
for
things
that
have
cost
potentially
that
are
one
off
or
that
are
more
of
an
individual
sponsorship
kind
of
situation.
B
If
it's
something
that
is
more
of
a
kind
of
ongoing
cost,
you
know
things
like
subscriptions
like
zoom
or
or
like
this.
We
can
rest
that
you
know
these
are.
These
are
things
that
we
kind
of
consider
internally
as
part
of
our
kind
of
budgeting
process?
B
You
know
we
don't
want
to
create
a
dependency
where
we
might
not
be
able
to
kind
of
continue
supporting
something
but
yeah
we,
you
know
any
reasonable
requests,
certainly
for
for
relatively
low
low
cost
things
where
we
can
decide
that
internally
and
you
know
we
get
the
advice
of
the
project,
directors
and
the
board
as
well.
B
So
in
terms
of
yeah
big
big
ticket
items,
then
that's
kind
of
grant
program
territory,
but
relatively
small
things
that
are
of
very
clear
benefit
that
we
think
you
know
are
ongoing
costs
that
that's
more
of
a
kind
of
conversation
internally
and
with
the
board.
Okay,.
A
C
Yeah
I
was
really
interested
in
earlier.
You
mentioned.
The
foundation
has
been
spending
a
lot
of
time
kind
of
getting
legal
structure
in
place,
getting
making
sure
all
of
the
izer
dotted
tees
are
crossed
that
type
of
thing,
and
I
completely
understand
that
a
lot
of
that
is
more
procedural.
Internal,
not
the
kinds
of
things
that
merit
a
rust
foundation,
blog
post
for
those
of
us
who
are
interested
in
how
the
sausage
is
made
and
want
to
see
what
the
foundation
is
working
on.
C
What
would
be
the
best
way
to
follow,
along
with
the
kind
of
infrastructure
that's
being
put
in
place,
the
kind
of
processes
that
are
being
nailed
down
for
things
that
are,
you
know
more
boring
than
the
average
rust
foundation
blog
post,
but
still
potentially
of
interest
to
hey.
What's
the
project
might
want
to
know
what
the
foundation's
working
on.
B
Sure
yeah,
I
totally
get
that
we
are
hopeful.
Well,
not
hopeful.
We
are
going
to
put
an
awful
lot
more
information
onto
the
website.
You
may
already
have
noticed
a
few
changes
on
there,
but
we
want
to
be
a
lot
more
transparent
in
terms
of
our
policies,
our
processes
yeah.
B
What
money
we're
spending
those
kinds
of
things
so,
as
time
goes
on,
you
know
we
are
hopefully
going
to
be
publishing
just
a
lot
more
of
that
information,
so
that
you
can
see
it
as
and
when
you
want
to
equally
I'm
happy.
You
know
I'm
very
happy
to
write
a
blog
post
talking
about
these
things.
I
just
didn't
think
anyone
would
read
it,
but
yeah
I
mean
I,
you
know
it's
coming
up
to
the
end
of
quarter
one.
B
Now
I'm
going
to
be
doing
a
performance
report
for
the
board
anyway,
I'm
quite
happy
to
to
tidy
that
up
and
and
put
it
into
a
blog
post,
the
links
to
a
lot
of
this
stuff.
That's
that's
no
problem
at
all.
You
know
if
you
want
these
kinds
of
things,
I'm
very
happy
to
to
do
them.
C
So
two
thoughts.
First,
I
would
love
to
see
that
in
general,
the
project
has
the
structure
of
kind
of
a
two-level
blog
where
they
have
the
general
rust
blog,
that
is
of
widespread
interest
and
often
gets
reported
in
the
press
or
the
tech
press
or
similar,
and
then
the
inside
rust
blog.
That
is
very
much
more.
If
you
really
want
to
know
the
details
of
how
rust
is
developed
and
how
the
sausage
gets
made,
and
that
sometimes
makes
smaller
scale,
tech,
press
or
rust,
reddit
or
similar,
and
it's
a
narrower
audience.
C
I
think
it
would
completely
make
sense
to
have
a
similar
two-level
structure
for
the
foundation
blog
of
things
of
widespread
interest
to
the
community
and
beyond
versus
things.
You're
only
really
gonna
care
about.
If
you
want
to
know
the
nitty-gritty
details,
but
it
would
still
be
huge
help
for
transparency
for
like
hey
what
have
you
been
up
to
the
other
half
of?
Why
I'm
asking
is
this
also,
I
think,
helps
the
foundation
and
the
project
know
what
each
other
are
doing
to
the
point
of
what?
C
If
there
is
something
going
on
where
you
know
some
way
that
the
project
does
things
makes
life
a
little
more
difficult
for
the
foundation
and
the
foundation
spending
time
figuring
out
ways
to
put
a
structure
in
place
to
make
that
work.
When
that
may
have
been
a
historical
accident
of
how
we
work
and
hey
the
easier
solution
may
be,
is
there
a
way
you
could
change
this
process
and
that
would
make
it
easier
to
work
with
hey
sure.
Let's
talk
about
that,
that's
the
kind
of
thing
where
working
together
rather
than
you
know.
C
B
B
Yet
in
terms
of
the
communication
between
the
the
project
teams
and
the
foundation
at
the
moment,
you
know
we
have
the
I'm
relying
very
much
on
the
project
directors
who
are
being
fantastic
at
keeping
us
updated,
but
there's
probably
a
better
way,
I'm
just
not
sure
what
it
is
yet
so
yeah
figuring
out
how
we,
how
we
communicate
better
is,
is
a
definitely
a
big
one
that
I'd
like
to
to
crack.
A
Great
and
we're
at
time,
so
I'm
going
to
call
this
meeting
thanks
to
everyone
for
attending
and
thanks
to
beck,
especially
for
coming
and
talking
and
joel
and
other
foundation
members
and
I'm
gonna
end
the
recording.