►
From YouTube: Core Team Meeting 2020-07-30
Description
Core Team Meeting 2020-07-30
B
B
I
didn't
get
an
answer
yet
so
I
didn't
post
it
yet
I'll
have
to
remind
them,
but
the
what
I'm
leaning
towards
right
now,
at
least,
is
that
we
would
keep
the
current
set
up
but
add
a
line
that
says
if
something
is
quoted
from
an
from
another
source
which
is
cited,
then
it
retains
the
license
of
that
original
source,
which
of
course,
you
know,
must
permit
reproduction
in
this
forum
and
that
I
think,
addresses
sort
of
the
problem
of
like
well.
B
I
copied
and
pasted
some
code
from
the
linux
kernel
and
I
didn't
have
the
rights
to
do
that,
because
it's
gpl
and
can't
be
re-licensed
as
mit
or
whatever,
which
is
one
of
the
hazards,
and
I
think,
there's
I
think,
that's
probably
the
right
outcome,
but
I'm
going
to
post
that
proposal
at
least
and
see
what
people
have
to
say
about
it.
I'm
also,
the
reason
I
wanted
to
make
sure
is.
I
think
I
had
some
proposed
phrasing
and
I
want
the
legal
team
to
double
check
it,
but.
B
Yes,
I
could
do
that
in
more
detail,
but
that
it
does
try
to
do
some
of
that.
Maybe
I'll
add
common
scenarios.
C
I
mentioned
that
only
because,
if
you
don't
do
it
in
the
post,
they
will
try
and
do
it
in
the
comments,
and
they
might
not
do
it
with
the
clarity
that
you
have
from
talking
to
people.
So
it
could
be
a
good
way
to
help
steal
the
combo.
B
Right
right,
I
think
it's
good
to
like
to
help
drive
the
conversation
which
I
already
tried
to
do,
but
explicitly
around.
Let's
come
up
with
like
case
story
like
scenarios
and
we
can
define
the
outcomes
we
want
and
not
worry,
not
try
to
write
the
rules.
B
The
thing
that's
not
explicitly
satisfied
by
this
is
the
request
of
like
I,
I
post
a
comment,
and
I
don't
want
my
thoughts
being
used
for
commercial
game
that
has
to
be
explicitly
disclaimed
but
as
a
side
effect.
We
can
post
things
in
rfcs
and
you
can
put
things
on
wikipedia
and
there's
some
other
like.
B
C
B
E
B
I
was
gonna
post
it
in
the
issue-
I
guess,
but
okay
I'll
put
it
somewhere.
We
side
note
that,
along
the
way
when
discussing
this,
we
had
originally
been
thinking
about
something
like
a
tri
license
where
it's
like
licensed,
also
under
creative
commons,
and
then
we
were
like
okay.
This
is
a
little
overkill.
Let's
just
let's
keep
it
simple.
A
B
A
Okay
sounds
good
any
update
on
the
compiler's
licensing,
stuff,
florian.
A
Okay,
russ
survey,
nico.
D
D
The
problem
is
that
the
online
editor
for
word
is
not
able
to
to
deal
with
the
whitepaper
document,
so
you
need
a
real
word
license
which
I
own,
but
anyone
else
who
wants
to
collaborate
also-
and
it's
already
filled
for
like
three
four
pages.
D
D
C
C
C
C
B
Longer
term
nice
liner,
it's
just
just
a
separate
one.
I
have
a
question,
though:
where
is
that
or
like
you,
you,
you
were
collaborating
with
nick.
I
think
on
that
or
something
is
that.
Is
there
a
link?
Where
is
it.
D
So
I
quickly
put
that
on
my
share
drive
on
my
sharepoint,
because
I
use
it
currently.
I
gave
nick
access
to
it
because
we
were,
we
too
were
editing
it
anyone
else
who
wants
access
or
if
you
feel
like,
I
should
give
access
to
anyone
for
core.
I
can
do
that
later
today
or
tomorrow.
D
C
C
F
It's
better
okay,
yeah,
so
like
on
the
actual
licensing
like
there
was
an.
I
think
I
wanted
to
work
on
eventually
on
the
infrastructure
team,
which
was
to
actually
set
up
a
collaboration
platform
like
basically
office
365
or
google
og
suite
for
the
last
team
to
get
a
google
document
processing
with
actual
permissions
due
to
the
permitted
to
the
team
repository
and
also
like
having
eventually
maybe
email
address
so
like
actually
getting
that
license
could
be
part
of
that
effort.
If
we
actually
start
on
the.