►
From YouTube: Core Team Meeting 2020-07-02
Description
Core Team Meeting 2020-07-02
B
There's
slow
movement
on
all
of
this
we're
working
through
a
couple
of
questions,
so,
for
example,
some
people
have
asked
us
if
they
can
actually
assign
copyright
to
their
employer.
Questions
like
this
and
slowly
ongoing.
C
The
goal
and
plan
like
we're,
I'm
trying
to
page
back
in
some
context,
rebuilding
like
we
were
talking
about
addressing
some
of
the
code
of
questionable
origin
or
where
we
weren't
sure
of
its
license
provenance
that
may
have
snuck
into
rusty,
or
we
also,
and
we
had
built
a
sort
of
document
telling
people
like
here's
a
place.
You
can
reach
out
with
questions.
C
B
Yeah,
that's
a
good
point
that
document
we
wanted
to
push
out
in
the
next
couple
of
weeks,
one
or
two
after
everyone
from
the
working
group
has
read
to
it
and
reviewed
it,
because
it's
almost
done
to
make
sure
that
it's
actually
helpful
to
reviewers
and
not
like
hey,
if
you're
not
looking
for
that,
then
so
that
it
actually
has
a
good
tone.
A
helpful
one.
C
Okay,
do
you
do
you
feel
like
you've
kind
of
got
this
in
hand
so
to
speak,
or
would
you
like
to
hand
off
some
of
the
efforts
here.
B
I've
got
that
enhanced
in
the
sense
of
felix
and
josh
are
really
helpful
there.
So
yeah
we've
got
a
group
going.
That's.
A
C
C
Okay,
yeah
sorry,
I
didn't
know
if
that
was
a
separate
bullet
or
the
same
bullet,
so
I
think
we've
kind
of
agreed
on
some
text
that
basically
says
as
of
this
date,
we
changed
the
likes.
The
implied
license
to
be
that
you're
licensing
it
under
mit,
slash,
apache
2
same
as
rfcs
and
code
and
the
rest
repo,
which
means
you
can
sort
of
comment.
Unless
otherwise
stated,
I
guess,
extract
comments
and
so
on.
C
I
think
the
main
next
step
is
to
actually
execute
on
this,
which
my
plan
was
to
create
a
thread
on
each
forum.
First
of
all
update
the
text
with
some
future
date,
which
is
probably
a
week
or
two
away
or
something
like
that,
and
then
post
a
notice,
saying,
hey
heads
up.
The
licensing
terms
will
be
changing
as
of
this
date
and
then
I
guess,
monitor
and
answer
any
questions
that
arise
in
the
course
of
that
thread.
E
Hold
one
second,
so
we
like
have
gone
through
and
like
hit
the
white
papers
like
a
bunch
of
times,
and
we
haven't
really
had
any
movement
on
it,
and
last
I
can
tell
there
is
this
tick
v
white
paper
that
had
action
like
a
year
ago?
Do
we
still
want
to
keep
checking
in
on
this?
Like
I
don't
know
florian
if
you
want
to
keep
owning
this
or
not,
but
I
it
makes
me
feel
bad
that
we
like
hit
it
every
time
and
there's
like
nothing
so
like.
Maybe
we
can
get
out.
B
It
is
currently
hinging
on
me,
but
I
would
actually
like
to
follow
through
with
that.
So,
let's
see,
okay
can.
B
B
E
That's
cool.
I
was
just
looking
at
the
comments
and
they
all
the
ones
that
I
at
least
had
like
scanned
had
seen
said
like
a
year
ago.
So
I
I
think,
I'm
on
team
like
get
the
chickpea
like
white
paper
over
the
finish
line
would
be
good
but
like
long
term
for
ownership
of
the
white
papers
like
florian,
were
you
saying
you
also
want
to
like
long
term
own
that
effort
or
just
own
getting
that
one
over
the
finish
line.
A
Okay,
I
will
update
the
agenda
later.
I.
E
Okay,
it's
not
like
urgent,
but
I
was
hoping
that
we
could
kind
of,
like
I
don't
know,
fix
this
section
because
I
feel
like
we
just
like
fly
by
every
time.
A
C
E
C
I
mean
okay,
we
should
keep
going,
but
I'll
just
throw
out
that
this
seems
like
something
where
a
public
issue
tracker
may
well
help
by
shining
some
light
on
what
we're
thinking
about,
and
we
could
even
do
things
like
you
know,
call
for
help
on
the
inside
rust
blog
like
hey.
We
want
to
do
more
white
papers
who
calling
all
writers
yeah.
C
C
Yes,
what
good?
I
think
he
mainly
plans
to
go
over
the
existing
comments
and
update
the
text,
and
then
we
were
gonna
like
review.
What
what
was
that,
but
I
think
we're
making
some
motion
on
actual
targets
that
is
sort
of
the
same
as
what
I
said
last
time,
not
sure
pietro,
go
on.
G
C
It
me
too
well,
one
thing
I
want
to
say
is:
we
do
seem
to
have
some
perennial
confusion
around
things
like.
Oh,
this
is
in
the
weeds,
I'll,
take
I'll
text
peter.
A
C
I
don't
know
if
I
plan
to
type
something,
but
we
did.
We
had
an
interesting
discussion
in
the
compiler
team.
That
hinted,
I
impacted
around
this,
and
I've
been
turning
it
over
in
my
head.
We
were
talking
about
setting
up,
we've
been
talking
about
adding
more
structure
to
the
team,
especially
around
like
areas
of
the
code,
which
kind
of
has
latent
structure.
Now,
like.
C
Oh,
you
know,
if
you
want
to
edit
that
file,
you
should
ping
so,
and
so
they
know
it
pretty
well,
but-
and
I
was
floating
this
structure
of
that
I
had
loaded
last
time
of
like
team
is
more
permanent
and
project
groups
are
focused
on
achieving
a
specific
task
as
a
helpful
structure
there,
and
one
of
the
things
that
got
proposed
was
instead
indexing
on
sort
of
the
level
of
activity
and
organization
where
the
idea
was
like
we
set
up
the
areas
of
the
compiler.
C
Those
are
just
there,
they
just
exist
right,
but
but
you
can
kind
of
categorize
them
by
the
ones
that
don't
have
a
lot
of
leadership
happening
right
now.
Those
are
what
we
call
notification
groups
where
you
just
they're.
Just
you
just
put
your
name
on
and
you
can
get
pinged
when
stuff
comes
up,
but
there's
no
like
central
organization
around
it
and
then
there's
like
active
project
groups
might
be
more
okay,
there's
a
lead,
but
it's
sort
of
new.
C
It
may
go
away
if
there's
not
as
much
activity,
it
might
drop
back
down
to
a
notification
group
and
then
teams
like
really
an
established
thing
that
we're
trying
it's
still.
It
also
can
go
away.
But
you
know
it
has
the
trappings
of
a
team
and
makes
independent
decisions
and
so
forth,
and
I
thought
that
was
an
interesting
angle,
because
the
primary
goal
here,
which
is
definitely
true
for
me,
one
of
the
primary
goals-
is
to
really
help.
C
E
I
actually
just
realized
nico
with
you
saying
that
there's
some
things
I've
been
thinking
about
in
creating
teams
in
engineering
orgs
and
like
companies,
I
just
posted
it
in
the
core
team
channel,
but
it's
this
structure
around
pioneers
settlers
and
town
planners
anyways.
I
would
be
really
curious
to
see
because
again
framing
structures
around
what
the
expectations
of
people
want.
Like
I
don't
know,
I
think
that
there
might
be
something
interesting
here
so
now
now,
like
things,
I'm
thinking
about
at
work
and
now
and
rest
are
coming
together.
E
E
C
C
E
C
One
thing
I
would
bring
up
is
that,
while
we're
here-
and
I
guess
not
to
take
too
much
time
but
that
to
me
another
big
element
of
this-
that
we
haven't
hasn't
been
much
discussed,
but
is
how
we
can
communicate
it
to
people
so
like.
I
should
touch
base
with
aaron
who's
been
involved
in
a
lot
of
this,
and
it's
obviously
else
has
a
lot
to
do
with
the
web
page
and
so
on.
A
The
next
is
the
mac
os
arm
target
jake
made
a
tracking
issue.
I
just
wanted
to
make
sure
everyone
is
aware
of
that.
Any
other
discussion
on
that.
C
I
reached
out
to
some
people
at
apple
and
I'm
waiting
for
response
pietro
was
cc.
D
I
I
applied
for
hardware
did
not
get
hardware,
but
a
friend
of
mine
is
on
the
compiler
team
zoolop
and
has
been
working
on
getting
a
bootstrap
going
for
last
couple
days.
So
yeah.