►
From YouTube: Core team meeting 2019-07-10
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
B
C
Thought
it
went
well
one
thing
that
came
up:
there
was
a
little
bit
of
confusion
around
sort
of
who
should
be
invited
in
laughs
and
how
and
when
and
I
think
I
had
planned.
Perhaps
that's
due
to
my
original
email
being
a
bit
unclear
topic
but
I
think
what
I
think
we
came.
We
discussed
in
the
meeting
and
I
think
I'll
try
to
clarify
it
is
that
we
should
really
try
to
have.
C
It
doesn't
necessarily
have
to
be
the
team
lead,
but
it
should
be
someone
in
a
leadership
role
and
that
we
should
try
to
have
a
stable
person
and
really
just
one
person
over
most
of
the
meetings
or
at
least
a
sort
of
stable
small
group
of
leaders
and
like
in
the
case
of
the
embedded
team.
There
was
a
few
and
the
reason
for
this
being.
We
want
to
try
to
use
this
to
encourage
like
building
rapport
and
more
open
dialogue
and
making
it
easier
for
people
to
talk,
and
essentially
people
will
be
less
guarded.
C
If
that's
the
case.
One
other
question
that
came
up
that
I
were
having
a
into
post
the
minute
somewhere
I'm
going
to
I'll.
Be
right,
some
kind
of
brief
message
describing
what
we
did
and
put
them
somewhere
or
just
post
I,
don't
know
any
thoughts
on
exactly
that.
There's
a
best
location,
I
think
we
have
some
minutes.
We
probably
have
used
years
ago
put
in
there,
but.
D
That's
all
I
realized
I
had
one
thought
so:
we've
like
lifted
the
moratorium
on
working
groups,
but
we
have
not
invited
all
of
the
working
groups
to
that
meeting
and
so
I
think
there's
a
question
of
like
one:
should
we
and
two
like
how
do
we
decide
who
gets
invited
not
to
like
add
more
policy
things
I
swear,
I,
don't
love
that
stuff,
but
yeah
I
can
imagine
that
people
will
see
these
notes
and
want
to
join.
The
meeting
want
to
know
why
their
group
cares.
That's.
C
C
D
C
It
hard
I'm,
not
yeah,
I,
don't
know
we'll
see.
I
found
it
hard
to
figure
out
like
where,
in
the
structure,
to
draw
the
line,
I
think
we
can
to
some
extent
leave
it
up
to
like
I,
asked
the
dev
tools
team
if
they
thought
it
made
sense
for
individual
tools
to
apply
attend
and
they
thought
it's
not
worth
it,
and
we
can
probably
play
with
that
a
little
bit,
but.
A
C
E
C
A
It
in
its
time,
like
with
dev
tools,
I,
don't
keep
my
finger
on
the
pulse
of
all
the
teams
at
illegally
Kadence
I.
Keep
my
finger
on
the
pulse,
have
a
monthly
Cannes,
and
so
it
might
be
useful
for
that
or
we'll
have
to
like
figure
out
our
own
sake
mechanism.
So
it
still
might
be
useful
totes,
dev
tool,
sub
teams,
sometimes
at
end
yeah.
C
I
mean
I
think
part
of
it
is
that
all
the
goals
of
this
meeting
will
probably
evolve,
but
I
think
we're
hoping
to
use
it
as
much
for
surfacing
kind
of
complex
leadership
issues.
As
for
just
knowing
what's
happening,
it's
not
Morse
I,
guess
I'd,
say
more
so
for
that
than
for
knowing
what's
happening,
though
both
are
important,
and
so
in
that
sense
like
it's,
probably
not
the
cadence
at
which
you
get
updates
from
the
dev
tools
to
me,
not
the
most
relevant
thing.
C
B
D
C
C
Don't
have
this
conversation
relative
to
that,
and
also
just
in
general,
how
like
it
kind
of
bootstraps
a
lot
of
our
own
problems,
because
it's
not
clear
what's
the
best
forum
for
us
to
have
asynchronous
threads,
if
I
put
it
in
internals
I
know,
I'll
come
back
and
there'll
be
50
comments,
I
haven't
seen
if
they
put
it
in
whatever
so,
but
I
think
we
do
want
to
have
some
sort
of
conversation
starting.
So
if
people
have
thoughts
on
that,
I
don't
know,
I
was
thinking
about
trying
to
I,
don't
know
what
I
was
thinking.
C
I
was
planning
to
do
is
to
basically
talk
about
really
focus
on
the
link
team
and
a
specific
way.
Lincoln
can
approach
it
just
to
keep
it
concrete
and
kind
of
avoid
stepping
on
toes
and
also
because
I
think
it
makes
sense
to
start
from
a
specific
area
and
then
range
it
out
to
other
parts
of
the
project.
They
can
adapt
it,
how
it
makes
sense.
Some
of
the
stages
may
or
may
not
make
sense.
C
For
example,
although
I
think
they're,
pretty
Universal,
but
so
I
was
thinking
of
proposing
it
as
a
proposed
link
team
process
and
taking
it
to
the
link
team
and
then
also
asking
others
for
feedback.
Basically
roughly
like
that.
This
is
the
kind
of
thing
I'm
interested
in,
so
I
might
be
happy
to
I.
D
Think
that
sounds
super
good.
My
thought
was
that
if
it
was
gonna
be
for
a
larger
thing
that
we
might,
we
might
do
better.
All
of
the
governance
working
group
kind
of
shenanigans
to
maybe
have
a
more
complete
thing
that
we've
all
worked
through
a
fair
amount
before
we
publish
it,
because
otherwise
it
could
be
a
lot
of
yak
shaving
that
can
be
really
complicated,
but
I
think
the
idea
of
scoping
it
down
just
the
single
team
is
like
even
better
like
wait.
I
think
that's
a
super
good
idea.
We've.
C
C
It's
just
part
of
the
link
team.
That's
been
talking
about
this
and
I
think
we've
kind
of
we
kind
of
got
lost
a
few
weeks
because
of
travel
and
we're
kind
of
at
the
point
where
we
were
ready
to
start
bringing
in
outside
of
our
circle.
I
thinking,
we
didn't
actually
have
a
proposal
yet
was
the
problem
that
was,
we
would
have
be
there
I
think
we
can
get
there
so
yeah,
I'm,
gonna
scope,
it
down
I
think
it's
good
to
start
getting
people
involved
in
the
conversation
I
also.
D
F
B
C
F
F
Papers,
I'm,
sorry
whew
from
ping
cap,
there's
still
a
couple
of
things
missing
in
it:
I'm
scheduling
a
phone
call
tomorrow.
F
We're
trying
to
get
someone
instead
of
Manish
and
me
to
actually
write
bright
and
the
announcement
and
plan
a
meeting
for
website
team.
We
have
talked
to
people
in
the
chat
that
we
want
to
do
this.
F
Also,
the
thinking
behind
it
is
actually
to
get
a
couple
of
other
people
to
take
point,
especially
on
the
on
the
trauma,
translation
site,
because
putting
everything
on
me
and
Manish
just
doesn't
scale
so
putting
out
like
having
someone
write
the
announcement
instead
of
us
pushing
pushing
that
all
the
time.
This
way
to
know
I'm.
C
F
D
F
D
I
say
about
the
website:
I
think
is
probably
worth
just.
Okay,
Steve
put
something
kind
of
like
cryptic
in
the
track,
but
it
is
worth
knowing
that
it
has
become
I
have
become
aware
and
I
guess.
Some
of
us
already
knew
the
final
slogan
we
ended
up.
Shipping
for
rust
is
the
same
as
goes
basically
the
I.
My
brain
didn't
see
any
difference.
We
might
want
to
consider
that
I.
C
D
D
So
it's
kind
of
the
core
team's
problem
right
now
and
the
core
team
was
in
charge
of
the
slogan
and
our
marketing
I
think
it's
worth
us
like
knowing
about
it
and
yeah
open
up
that
other
can
of
worms.
But
the
reason
it's
timely
is
go
released.
A
new
website
that,
like
makes
it
a
lot
more
prominent,
it's
Logan,
so
yeah
I
just
wanted
to
share
insofar
as
like.
B
C
B
Right,
that's
coming
off
planning
update
for
the
latam
all
hands,
I'm
flooring,
you
weren't
at
the
meeting
last
time,
but
I
think
we
are
blocked
waiting
for
you
to
send
an
email
to
all
asking
for
interests.
I'm.
B
Bit
yeah.
F
C
For
it,
I
think
that's
the
most
interesting
question.
I
think
we
will
work
out
the
budget,
probably
I
would
maybe
we
can
get
it
from
Mozilla
part,
hopefully
maybe
from
some
other
sponsors
and
many
made
great
progress
on
hosting
possibilities,
but
it
would
be
awesome
if
we
were
able
to
like
build
a
group
of
people
organizing
it
that
can
persist.
That's
I,
don't
know
if
that's
plausible,
what
that
might
mean.