►
From YouTube: Core Team Meeting 2020-02-26
Description
Core Team Meeting 2020-02-26
A
C
A
C
C
D
E
D
E
Questions
or
both
the
initial
one
would
be
the
suggestion
of
let's
even
find
out
his
interesting
talk.
It
was
interested
in
talking
about
something
in
our
project,
so
a
small
bar
who
is
even
interested
in
talking
what
the
license
file
says
and
how
it
relates
to
code
and
making
sure
this
is
clean
and
who
actually
cares
about
the
problem
I'm.
Instead
of
making
this
a
discussion
group.
D
E
No,
no,
no,
not
at
all.
So
we
have
found
a
couple
of
measure
of
license
issues
that
need
to
be
remedied
where
we
probably
have
to
do
something
currently.
Isn't
the
super
super
critical,
but
we
need
to
move
towards
something
where
we
make
sure
that
our
licensing
is
sound
and
stay
sound.
We
don't
want
to
change
it.
We
just
might
want
to
make
sure
that
our
house
is
in
order.
E
I
want
to
get
get
the
people
together
that
care
on
the
level
of
I
actually
want
to
I'm,
actually
interested
in
figuring
out
all
the
problems
and
fixing
them
one
by
one
that
kind
of
mode
no
changes.
No
like
no
real
product
policy
except,
for
example,
the
policy
like
what
is
the
document
that
we
put
into
people's
hands
to
God?
Is
this
equestrian
licensing?
Can
we
accept
that
library
or
something
as
a
support.
E
A
D
One
thing
I
would
say,
is
I've
been
talking
a
lot
to
like
to
Felix
a
little
bit
yesterday
and
so
on
about
a
compiler
team
road
map
trying
to
drill
a
little
more
there
and
get
maybe
there's.
Maybe
we
should
just
leave
it
as
a
question
mark
for
now,
and
it
might
be
helpful
if
we
had
a
little
more
from
other
teams
to
to
pull
in
there.
I
don't
know,
but
we
could
certainly
write
one
based
on
what's
what
we
published.
D
I
made
an
outline
I,
don't
recall
if
I
had
link
to
it
before,
but
I
mean
Derek's
there
and
I
had
hoped
that
today,
I
would
try
to
flush
that
outline
into
a
blog.
Oh
did
you
all
hear
that
my
screen
was
frozen,
but
I
hope
to
flush
that
into
actual
post,
but
that
hasn't
happened
am
I
trying
to
find
someone
else.
Who
wants
to
do
that?
D
It's
just
because
I
feel
like
it's
gonna
I'm
moving
slow,
but
that's
where
we're
at
okay.
D
Don't
think
I'm
a
little
out
a
little
behind
I,
don't
think,
there's
been
any
major
updates
in
aiding
tomorrow.
I
know.
One
thing
that's
maybe
worth
mentioning
is
that
Aaron
was
going
through
the
list
of
folks
who
have
R+
rights
but
aren't
really
associated
with
any
team
and
trying
to
kind
of
slowly
change
that
so
that
we
don't
have
just
like
an
ad-hoc
list
of
people
with
just
our
plus
but
like
right
to
right
access
to
the
repo.
D
A
lot
of
the
people
on
that
list
were
pretty
dated
in
case,
but
not
all
so.
You
may
have
gotten
some
emails
and
and
so
forth,
she's
been
trying
to
bring
that
under
control.
A
A
F
F
C
A
B
A
Okay.
The
next
item
is
a
short
announcement
on
night
me
see
you
mom,
nice.
B
A
B
So
yeah
I
should
have
put
this
in
the
announcement
section.
I
just
realized
that,
but
basically
so
they
start
off.
As
discussions
between
Google
and
Mozilla
on,
we
were
already
doing
internationalization
of
stuff
and
rust,
and
we
we
were
like.
We
should
collaborate.
So
there's
this
like
giant
C++,
Java
library
out
there
that
Unicode
maintains
called
ICU.
That
does
all
the
internationalization
stuff
like
it
does
pluralization
all
the
good
stuff,
and
basically
it's
the
only
thing
out
there.
That
does
this,
but
there
are
now
a
lot
of
rust
crates
that
leg.
B
Do
parts
of
this
and
Google
wants
something
modular.
We
want
something
modular
people
want
rust,
so
we've
people
are
working
together
and
what
happened
was
Unicode
also
got
involved.
So
now,
there's
an
official
Unicode
project
whose
main
goal
is
to
create
a
modular
ICU,
but
there's
a
very
good
chance
that
it
will
be
written
and
rust.
So
I
just
want
to
like
mention
this.
So
Unicode
is
now
on
the
rust
strain.
B
They
thought
it's
a
big
ICU
user.
It's
not
like
a
hundred
percent
certain.
If
the
implementation
language
will
be
rust,
it
might
also
be
a
DSL
that
we
compile
to
different
languages.
It
will
definitely
be
something
that
you
can
use
from
rust
because
that's
a
hard
requirement
from
for
many
of
us,
but
yeah.