►
From YouTube: Core Team Meeting 2020-05-28
Description
Core Team Meeting 2020-05-28
B
Let
me
do
this
hold
on.
Let's
see,
if
I
can
figure
it
out,
can
I
do
it?
No!
No!
I
can't
oh
yeah
here
we
go,
proposes
this
sort
of
flowchart
for
lane
team
contributions,
the
idea
being
that
you,
you
start
out
by
filing
an
issue
with
your
motivation
and
your
high
level,
some
details,
but
not
too
many
of
what
you
plan
to
do
and
that
might
go
straight
to
a
pr.
C
E
So
I
don't
know
if
this
is
something
we
want
to
check
in
on
every
week
or
if
we
want
to
have
like
a
sub
crew
of
core
team
reps
to
like
be
checking
in
on
this
and
like
when
we
hit
a
spot
where
we
feel
like
we
want
to
grow
this
or
look
at
for
another
team
to
bring
it
up.
That
way
like.
I
do
still
think
we
have
larger
goals
and
plans
for
this
project
and
we're
on
step.
One
so
weekly
seems
like
too
much,
but
I
don't
want
to
let
it
drop.
B
B
No,
I
think
that
would
be
fine.
I
think
the
there's
a
next
waypoint
which
we,
which
we
will
reach,
which
is
basically
like
the
plan
with
this
rfc,
is
we're
going
to
try
this
for
a
while
and
then
and
then
we're
going
to
look
at
all
the
existing
rfcs
like
if
it's
working
well
we're
going
to
sort
of
try
to
bring
those
existing
rfcs
into
this
scope
and
that's
probably
a
place
where
we
could
check
in
on
how
it's
working
and
talk
about
like.
Is
there
another
team
that
might
want
to
experiment
with
this?
A
F
A
B
I
don't
remember
what
yeah
the
main
up.
I
guess
there's
an
update
yeah,
which
is
that
I
talked
to
the
basically
I'm
in
communication
and
we
haven't
with
was
illegal
to
talk
about
the
ram.
You
know
how
realistic
is
it
to
change
this
text
and
what
do
we
want?
I
have
to
get
back
to
them
now
that
we
have
some
idea
of
like
what
we're
looking
for,
that
we
don't
get
from
the
current
terms,
which
seems
to
be
primarily
about
making
it
easy
to
copy
and
paste
into
rfcs
and
other.
B
I
guess
other
places
within
the
re
sort
of
rust
issues
or
other
places
where
you
know,
licensing
terms
might
come
into
play
and
I'll
I
have.
I
haven't
actually
responded
with
that.
So
once
I'll
do
that
today
and
we'll
see
what
they
have
to
say,
they
did
bring
up
that.
You
know
there's
a
lot
of
comments
that
were
ostensibly
written
under
the
old
terms
that
we
have
to
think
about.
I
don't
know
if
that's
as
simple
as
saying
all
comments
before
this
date
are
under
this
terms
and
everything
else,
but
I
don't
know.
B
No
major
updates,
except
that
I
followed
up
a
little
bit
with
the
illamos
lumos
or,
however,
you
pronounced
that
people
in
pilot
team.
They
were
requesting
to
go
to
tier
two
and
that's
not
really
about
the
rsc
exactly,
but
in
the
area.
I
think
we
talked
about
it
last
time.
The
yeah,
oh
one,
other
thing
that
is
relevant
is
it's
sort
of
relevant.
E
D
D
So,
like
basically
like,
we
probably
should
add
more
like
we
should
investigate
that
in
metrics,
explicitly
to
see
how
many
pages
are
viewed
by
targets
or
by
like
getting
some
more
statistics,
probably
before
making
the
change
but
like
most
of
the
crates,
don't
really
change
their
content.
If
you
are
on
linux
or
windows
or
macos
like
or
the
only
the
low-level
platform,
crates
should
have
a
difference.
E
B
Probably
I
do
suspect
you
know,
the
outcome
will
be
the
same,
but
there
might
be
some
improvements
along
the
way.
Like
maybe
a
better
way
to
I
don't
know.
I
have
no
idea
better
way
to
opt
in
or
whatever,
plus
that
you
can
point
at
the
rfc
later
and
say:
yeah.
We
decided
in
rfc
xxyz
that
we're
going
to
make
this
change,
which
is
important.
D
Okay,
like
yeah,
we
started
with
our
really
lightweight
rfc,
plus
inside
the
doctor's
repository
just
for
internal
changes,
to
dress
much
like
the
major
change
proposal.
The
compiler
team
is
doing
but
yeah
this
impacts,
the
all
like
impacts
more
like
I'm,
not
the
one
proposing
it
this
change.
It
was
from
the
other
dress
khalid
and
one
of
them
the
members
of
the
team,
and
they
were
asking
whether
you
should
post
on
their
blog.