►
From YouTube: Core Team Meeting 2019-11-27
Description
Core Team Meeting 2019-11-27
A
A
Legal
issues,
discussion
status,
has
moved.
The
licensing
guidelines
are
currently
with
a
compiler
team
to
check.
If
it's,
okay
or
not
seems
like
there
was
not.
Everyone
had
a
good
bearing
of
what
our
current
issues
are,
especially
with
regards
to
our
the
other
general
and/or
specific
issues
we
have
both
and
so
I
had
a
longer
discussion
with
Felix
o'clock
on
what
would
be
a
good
way
to.
A
To
address
these
issues,
specifically,
if
compiler
team
should
have
a
full
meeting
on
that
or
if
a
group
of
individuals
should
start
working
on
this
currently
looks
like
we,
it's
going
to
be
a
group
of
individuals
with
regular
that
has
a
regular
conversation
with
the
whole
team.
Instead
of
having
full
hour
meetings
with
anymore.
A
B
So
the
key
team
is
sorry
there's
some
noise
from
somewhere.
The
community
team
is
basically
figuring
out
how
to
structure
itself
and
I.
Think
the
idea
of
Florian
had
a
pretty
good
proposal,
which
was
a
whole
bunch
of
which
is
basically
looking
at
the
work.
The
community
team
is
actually
doing
formalizing
that
as
teams
and
also
structuring
the
community
team
itself
is
like
more
of
a
community
leadership
team
where
it's
less
high
volume
but
ties
all
the
sub
teams
together,
which
this
is
similar
to
how
dev
tools
is
doing
its
thing.
B
Bridge
and
rustlings
are
probably
not
really
a
community
team
thing
and
the
question
was:
should
there
be
a
top
level
team,
a
WG
or
maybe
like
I,
brought
up
that
really
this
this
overlaps
with
Docs
as
well
a
lot
of
the
doc
stuff
that
is
kind
of
unloved
right
now
it
would
be
nice
if
we
could
have
a
separate
place
for
all
this,
but
right
now,
I
think
they're
gonna
go
with
the
results
of
like
a
low
volume,
top
level
WG
and
then,
like
figure
stuff
out
things,
move.
B
C
B
Thing
it
it
feels
well,
at
least
Marissa
thinks
it's
not.
It
seems
to
be
more
of
a
learning
kind
of
thing,
I'm,
not
really
sure
I
completely
agree,
but
I
do
feel
that
it's
a
bit
different
from
the
other
community
team
things.
That's
it
I
think
the
community
team
in
general
is
a
grab
bag
of
stuff.
So
I'm,
not
a
hundred
percent
convinced
like
people
interested
in
the
website,
are
not
necessarily
going
to
be
interested
in
the
other
community
team,
stuff,
etc,
and
that
is
fine.
B
B
So
I
do
think
that
having
a
rough
community
org
over
all
these
small
teams
or
having
some
kind
of
umbrella
over
all,
these
small
teams
doesn't
need
to
be
the
community
leadership
team
or
whatever,
is
a
good
idea,
because
without
that
most
of
these
will
get
forgotten
as
like
people
move
on,
etc
and
I'm.
Not
convinced
that
like
rustlings
and
the
learning
team,
as
a
top-level
team
would
survive
if
it
without
like
this
kind
of
thing.
But
whatever
I.
B
A
B
B
I
think
that,
like
half
the
things
the
community
team
has
under
its
umbrella
right
now
are
very
unrelated
to
the
other,
speaks
like
the
website
as
well.
That's
like
I
mean
the
same
argument
can
and
should
be
made
for
the
website,
but
like
it
is
under
community
because
that's
a
convenient
place
for
it
to
be,
because
there
is
less
desire
for
an
overarching
web
properties
team
right
now
and
that
might
not
do
well.
A
A
So
a
lot
of
these
things
are
basically
around
overlap
with
other
parts
of
the
organization
where
we
might
feel
something
does
not
fit
under
that
umbrella,
but
it
I
think
the
biggest
discussion
in
the
meeting
we
just
had
it's
two
hours
ago
was
really
on
those
edges
where
oh
this
could
be.
This
could
be
there
or
this
could
be
on
this
side
or
and
that
side
and
so
yeah.
D
C
E
C
E
A
A
B
A
A
We're
all
on
the
same
page
as
they're
saying
well,
then,
don't
bend
over
backwards
to
make
sure
everything
works.
It's
more
like
don't
willfully
break
things
just
before
going
into
holidays,
so
pretty
subtle
thing
and
release
agrees
there.
If
anyone
has
any
other
team
meeting,
maybe
please
ping
me
and
I
can
send
you
that
that
small
piece
of
of
blurb
that
I
brought
it's
more
to
make
sure
that
people
keep
in
the
back
of
the
head.
I'll
check
it
off
because
I
know
that
have
been
discussions
around
this.