►
From YouTube: Core team meeting 2019-08-14
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
A
C
Just
want
to
quickly
race.
Last
week
we
have
the
situation
that
we
have
a
checker
meeting
and
all
most
of
the
issues
that
block
the
async/await
stabilization
this
week
have
already
been
known,
and
we
kinda
had
a
look
at
them
and
where
I
is
this
moving?
No
one
from
corn
Lang
we're
there,
though,
though
this
is
no
accusation,
the
we
could
also
have
followed
up
with
them,
but
we
didn't
so
which
led
to
this
week,
everything
becoming
unclear
and
a
little
bit
in
a
rush.
C
So
I
would
just
like
to
raise
this
as
an
a
thing
that
we
could
use
to
inspect
what
we
actually
want
some
percent
meeting
and
what
are
expecting
what
we
expect
around
what
is
discuss
and
what
information
should
flow.
And
how
do
we
react
if
we
feel
like
something?
Some
information
is
missing.
Do
we
follow
up?
What
is
the
extra
we
get
out
of
that?
So
it's
not
particularly
on
ice
in
Kuwait.
It's
just
I
think
this
is
a
good
good
point
to
investigate
what
we,
what
do
you
want
from
it?
I.
B
D
That
meeting
its
to
be
short
and
tiny,
so
whenever
a
bigger
concern
is
falling
out
of
the
meeting,
people
should
talk
about
it
later,
potentially
scheduling
another
meeting.
We
can
also
like
encourage
people
to
keep
that
time
slot
after
that
free,
so
that,
if
you
want
to
do
this,
you
can
really
do
this
like
that,
if
necessary.
Oh.
C
It's
not
about
how
we,
unless
about
how,
if
we
want
to
change
the
meeting
or
if
you
want
to
extend
it
or
whatever
it's
just
that
I
think
there
was
this
interesting
thing
of
people
have
noticed
that
and
didn't
follow
up
and,
on
the
other
hand,
people
that
could
have
informed
us
that
next
week,
probably
we're
not
going
to
hit
the
deadline
that
message
didn't
get
through.
I,
don't
know
if
it
was
even
like
people
even
had
that
in
their
head,
but
yeah.
So,
oh,
it's
more
like
what
do
we
do
if
certain
patterns
arise.
B
Do
we
follow
up
in
general,
I
think
it
would
have
been
ideal
like
there.
The
information
sort
of
available
to
it
would
be
nice
if
we
were
just
posting.
These
updates
in
general,
not
just
through
the
meeting,
perhaps
and
more
regularly
of
like
here's,
the
number
of
bugs
I
think
I
in
particular
I'm
a
little
bit
unsure
about
how
we
should
implement
I.
Think
one
of
the
challenges
around
async/await,
especially,
was
that
kind
of
very
early
on.
B
C
C
Or
do
we
want
to
people
to
make
an
effort
to,
for
example,
use
the
same
meeting
to
warn
people
ahead
that,
oh
by
the
way,
async/await
might
not
happen
so
prepare
for
that
if
you're
on
reddit
or
whatever
I
don't
know
so
that
you
know
about
it,
there
was
just
a
I
think,
a
lot
of
us
and
clarity
in
the
room
and
I
believe
in
marki
were
in
the
meeting
as
well.
I
believe
we
could
have
caught
that
with
with
a
little
more
effort,
yeah.
E
F
I
I
think
it's
not
worth
really
litigating
exactly
what
happened
at
last
week's
meeting,
but
I
think
the
larger
point
that
this
is
the
kind
of
thing
we
want
to
get
out
of
this
meeting
is
very
true,
like
I
think.
This
is
a
perfect
example
of
the
kind
of
cross
team
interaction
that
has
been
missing
a
bit
in
the
roast
project,
and
this
is
a
the
meeting
is
a
good
opportunity
for
that
to
happen.
F
Means
of
communication,
but,
like
you
know,
given
the
the
meets
that
we've
only
had
a
few
issues
of
the
meeting
and
people
have
been
like
away
and
teams
haven't
figured
out
who
is
going
to
be
their
representative
every
week,
including
the
core
team
like
I
I,
think
this
is
kind
of
the
learning
pains
that
we
should
expect.
I.
B
My
takeaway
would
be
flurry,
and
also
that
so
it
would
have
been
good
to
highlight
that
it
matters
a
lot
to
you
like.
If
you
were
starting
to
depend
on
this,
and
you
would
like
to
know
both
both
directions
and
I
mean
this
person
thing,
of
course,
but
like
when
you're.
We
should
try
to
keep
people
abreast
of
what's
happening
in
the
meeting,
but
also
on
the
other
side.
If
we're
coming
to
rely
on
something.
Let
them
know
that
we're
relying
on
that
so
that
they're
aware
that
we
would
like
updates.
B
C
F
Just
to
bring
this
back
up
to
the
meta
level
being
conscious
of
the
time,
I
think
what
we
want
to
get
out
of
this
is.
We
probably
want
some
guidelines,
we're
going
to
send
four
to
the
teams
and
that
will
come
up
with
those
I
think.
Yes,
that
sounds
good.
Does
that
sound
like
a
good
conclusion,
sounds.
A
Great,
thank
you
very
much.
Okay,
the
action
items,
tasks
to
check
in
on
section
I'm,
seeing
a
couple
crossed
off
things,
so
the
cross
off
governance,
I,
don't
think
we
need
to
discuss,
and
you
see
a
note
for
Steve
and
he's
not
here.
We
just
talked
about
the
team
wines
stand
up
meeting.
The
only
note
there
is
that
there's
a
note
that
Nikko
is
to
invite
secure
code
in
gaming
working
groups
and
get
them
on
the
website.
I
did.
B
A
C
Quick
updates,
I
talked
to
some
grief,
quick
this
today
and
they've
got
gdpr
and
at
the
MCA
stuff
done.
They
also
went
a
little
further
and
came
up
with
the
GDP
our
policies
for
everything
that
we
have
also
websites
and
all
these
kind
of
things
boy,
it
seems,
there's
been
like.
Let's
just
do
this
in
one
go,
so
it
isn't
crossed
off,
but
it
has
made
a
lot
of
progress.
C
That's
why
I
would
quickly
get
started
with
that
and
take
that
over
it's.
It
doesn't
help
to
get
that
into
another
discussion
about
what
people
believe
how
open-source
licenses
work
yeah,
so
I
would
maybe
check
up
on
that
after
was
gone.
I'm
pretty
sure,
I
can't
do
that
before
anyone
else
wants
to
take
it.
C
C
A
C
D
It's
going
fine,
we
added
some
more
trainings
stuff
is
going
good.
Yeah
Oh.
Remember
that
there
there
are
a
bunch
of
production
users
meeting
on
this
on
the
training
day
in
the
same
venue.
So
if
any
of
you
want
to
hang
out
there,
we
can
like
set
that
up.
Okay,
they're
just
going
to
be
talking
about
their
needs
and
stuff
and
like
probably
coming
up
with
something
to
bring
to
the
rust
teams
eventually,
but
I'm
gonna
just
be
there
to
listen
and
yeah.
A
C
Longer
I
gave
them
some
time
until
well.
Deadline
was
tomorrow,
I
gave
them
a
little
more
time
until
the
weekend,
but
they
we
got
50
people
that
responded
and
the
responses
are
unsurprising,
I'm,
just
not
sure
if
everyone
has
filled
the
form,
but
I
would
expect
the
All
Hands
to
grow
like
at
the
rate
that
it
was
growing
another
10
to
20
people
or
something
about
so
we
can
definitely
get
started.
Talking
to
venues
and
I
have
made
it
very
clear
in
the
second
email.
F
D
Oh
just
one
thing
about
the
venue
planning:
we
should
be
fast
given
that,
like,
if
we're
gonna
be
talking
to
other
companies,
for
this,
we
probably
will
need
some
egg-like.
We
will
probably
need
to
get
something
to
set
quickly,
but
on
the
plus
side
at
least
the
companies
I
talked
to
it
did
not
seem
like
like
it
was
like
the
number
of
people.
We're
thinking
is
much
smaller
than
the
number
of
people
where
they
actually
need
to
care
about.
D
C
Okay,
I
guess,
eighty
to
ninety:
if
they
have
space,
for
that
will
be
good.