►
From YouTube: Community Committee Meeting
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
Awesome:
okay:
we
are
live
on
YouTube.
Thank
you
all
for
coming
into
another
website.
Alright,
another
community
committee
meeting.
We
have
a
fairly
straightforward
agenda
today,
which
is
awesome,
but
we'll
kick
it
off.
First,
with
initiative
initiative.
Check-Ins
will
just
go
down
the
list
here.
I
do
we
have
been
on
the
line?
I
don't
know
if
I
saw
No,
okay,
donate
yeah.
Anybody.
C
A
A
Then
I'll
throw
that
on
my
calendar
and
try
to
make
a
point
to
be
there
I'm,
not
sure
if
I
have
conflicts
yet,
but
I
I'll,
I'll
come
join
and
help
out,
but
I
would
like
to
ask
anybody
else
on
the
call
or
anybody
else
listening
in
I,
if
you
want
to
help
and
come
run
this
thing.
Let's,
let's
do
this
cohort
number
two,
it's
gonna
be
awesome.
Awesome,
yeah,
I,
seen.
C
C
A
Awesome,
I
and
I
can
give
a
website
redesign
update
it's
so
we
had
an
awesome.
Pr
opened
PR,
Aang
and
I'm,
trying
to
find
a
number
for
people,
because
I
want
everybody
to
go
and
dive
into
it.
Pr
number
105
on
website
redesign
I
adds
about
a
fifty
seven
different,
getting
started.
Documentation
pages
I
believe
so.
This
is
Flavio.
A
I
has
very
very
generously
contributed
his
definitive
nodejs
handbook,
article
content,
the
website
redesign
initiative,
and
so
we
now
have
this
giant
dump
of
really
amazing
getting
started
content
that
I
would
love
folks
to
dive
into
help
at
it.
It's
already
been
combed
over
a
few
times
before
he
published
it
over
on
medium,
so
I
just
want
to
make
sure
that
for
reading
it
reading
it
from
the
standpoint
of
new
eyes,
it'll
make
sense
and
it
all
flow
as
well,
but
otherwise
this
this
pushes
us
like
a
light
year
ahead.
A
As
far
as
content
goes
very
excited,
we've
also
good
I
was
just
going
to
say.
We've
also
I
started
to
to
talk
about
a
technical
structure
over
on
the
in
a
github
issues,
still
very,
very
high
level,
but
we've
been
in
question.
I
had
pretty
well.
That
was
that
issue
was
was
breached
and
open
by
two
new
contributors
who
joined
last
session.
Sound
excited
to
see
things.
I
keep
rollin
ahead,
so.
E
A
Great
awesome
and
then
bootstrap,
so
we're
gonna
start
doing
a
regular
update
on
how
the
bootstrap
merger
conversations
are
going.
There
is
a
weekly
so
for
context
for
folks
on
the
stream,
there
is
a
new
repository
that
came
out
of
the
addiction
merger
discussions
over
add
in
the
vancouver
conference.
There's
no
js'
slash
bootstrap
on
the
github.
There
are
a
number
of
issues
in
flight,
we're
still
working
through
a
lot
of
there's,
there's
kind
of
two
branches
that
are
being
discussed,
discussed
right
now,
two
branches
of
conversation,
one
is
how
the
group
itself
functions.
A
How
bootstrap
will
will
operate
day-to-day
and
what's
nice
is
there's
starting
to
converge
on
on
consensus,
there's
a
number
of
PRS
in
flight
right
now
for
a
draft
there's
a
draft
of
a
staging
process,
the
Arden
by
jory
I,
open
open
PR
by
Joey
for
proposing
new
types
of
governance
programs.
This
would
be
things
like
the
like
a
lot
of
the
programs
that
we
ideated
through
a
bunch
of
sticky
notes
on
the
wall
during
the
governance
session
at
the
collaborators
on
that.
A
So
this
would
this
would
not
be
the
process
for
charter
like
things,
but
for
quite
literally
everything
else,
which
is
the
bulk
in
the
meat
of
what's
gonna,
be
developed
here.
There's
also
discussion
around
the
process
by
which
we're
going
to
start
talking
about
bylaws
and
charters
and
I,
forgetting
his
name
rubies
is
his
handle.
Sam
Ruby,
Ruby,
yeah,
yeah
Sam.
Ruby
has
really
been
pioneering
a
lot
of
this
work
and
I'm
very
excited
that
I,
rather
than
this
kind
of
throw
it
over
the
wall
process
that
was
kind
of
proposed
by
the
foundation.
A
A
27
has
this
awesome
dip
of
the
two
foundations
bylaws
and
highlights
areas
where
we're
able
to
where
there's
differences,
which
conveniently
are
also
the
areas
where
we
have
some
flexibility?
A
lot
of
this
is
boilerplate,
that's
required
by
law
from
Delaware,
but
there's
a
couple
places
where
we're
able
to
customize
it
a
bit
and
the
goal
here
is
to
leave
it
open
enough,
so
that
the
governance
documents
that
we
actually
have
the
staging
process
and
the
RFC
process
set
up
for
I.
F
A
A
E
E
Jim
said
+12
office
hours
and
they'd
be
happy
to
help
facilitate
I'm
happy
to
be
Q,
but
I
would
just
like
to
suggest
people
go
look
at
that
and
if
there's
anything
you
know
in
that,
it's
pretty
like.
But
if
there's
anything
in
that
issue
that
you'd
like
to
help
with
or
contribute
to
or
help
get
started,
please
feel
free,
so
yeah,
just
the
general
awareness
thing
of
like
those
are
probably
some
there's.
Probably
some
initiatives
in
there.
A
Awesome
and
I'll
I'll
ping
Jim
I
offline
to
get
office
hours
kicked
off
cool.
Kick
that's
that's
an
awesome
thing
to
just
start
coalescing
around.
Thank
you
for
the
call
out
awesome.
Let's
dive
in
to
our
agenda
will
go
top-down,
I
think
that's
the
best
way
to
do
it.
So
we
still
have
issue
number
239
from
nodejs
admin
on
the
agenda
here,
I
believe
Waleed,
you
were,
you
were
looking
into
this.
Do
you
have
an
update
on
this.
C
B
B
D
A
B
B
D
B
A
B
D
G
G
Maybe
a
github
team
might
be
appropriate
and
then
say,
for
example,
they
reach
out
to
the
emails
that
you've
listed
they
in
your
PR
and
then
the
people
in
the
emails
would
then,
if,
if
they
can't
answer
the
question
or
they
need
more
like
they
drop,
they
drop
a
comment
in
the
github
team
thing
which
everyone
gets
pinged
on.
That
might
be
a
suggestion.
B
G
In
a
note,
but
yeah
I'm,
just
thinking
it's
less
pressuring
everyone
if
everyone
can
be
kind
of
pinged
at
the
same
time,
and
they
can
jump
in
in
like
one
single
tried,
does
zippy
any
thoughts
on
that
like
would
that
be?
Would
that
be
okay?
If,
if
there
were
questions
that
you
weren't
able
to
or
you
don't
have
experience
with,
maybe
with
the
plaintiff
visa
stuff
that
you
could,
you
could
drop
it
into
a
github
team
and
people
could
respond?
Would
that
make
sense
where
this
sort
of
thing
I.
D
Think
so
I
think
the
only
I
think
it
would
make
sense
in
terms
of
if
it's
something
that's
needed,
maybe
outside
of
Linux
Foundation
events
like
if
it's
a
Linux
Foundation
event,
probably
the
best
person,
would
be
internal
Linux
people
that
run
the
events
and
know
all
about
visas
and
what
they
can
do
and
can't
do.
But
if
it's
outside
of
that
I
think
that
would
make
sense.
I
don't
know
I
again,
I'm
kind
of
like
would.
E
B
E
C
A
A
D
E
This
is
more
I
mean
if
three
people
from
the
LF
are
taking
point
on
this.
My
and
I
don't
want
to
speak
for
zippy,
and
you
know
the
other
two
you,
but
my
general
experience
has
been
that
email
is
preferred
and
you
reduce
the
barrier
to
entry
for
them
or
reduce
the
cost
of
maintenance
effectively,
because
this
is
something
they're
doing
to
help
us
and
our
request.
I
think
that
going
down
the
path
of
email
is
the
only
acceptable
thing,
and
these
are
visa.
F
B
Is
that
determines
are
already
open
for
the
issues
information?
The
thing
we
need
the
email
is
that
someone
feels
confident
in
appreciated
some
information
on
the
email.
There's
the
thing
we
are
doing
now
they
can
also
they
can
already
open
a
common
issue.
Some
general
requirements
is
some
extra
benefit
with
the
email
is
that
you
know
you
come
to
this
person
and
then
more
confident
about
sharing
some
issues.
D
G
B
B
A
D
A
A
Awesome
we'll
make
we'll
make
note
of
that
on
that
PR
that
we're
gonna
tweak
a
little
bit
at
an
FAQ
document
and
I
add
the
visas
at
no
js',
alias
awesome.
Any
more
to
add.
On
the
sir,
on
to
the
next
item,
Lord
an
upward.
The
next
two
issues
are
the
Charter
changes
that
have
been
on
here.
I
wish
Tracey
was
able
to
make
this
call
I.
Think
she'll
have
the
most
context
on
here:
I'm,
actually
not
sure
where
we
sent
off
one
of
them
to
be
approved
by
the
board.
A
E
Word
we're
trying
to
we're
getting
the
first
one
approved
getting
that
merged,
and
then
we
will
be
submitting
the
other
mm-hmm
to
be
on,
and
so
the
first
one
I
just
want
to
make
we
you
know,
we've
got
we've
done
this
a
few
times,
so
I
just
want
to
make
sure
everyone's
on
the
same
field
again.
The
first
one
I
believe
submitted
by
me
just
because
I
merged
it
and
then
unmerged
it.
E
The
first
one
submitted
by
me
PR
three,
eight
four
needs
to
be,
as
is
that
is
what
has
been
submitted
to
the
board
and
we,
if
we
keep
changing,
it,
will
keep
having
to
resubmit
it
to
the
board
over
and
over,
and
we
won't
be
able
to
land
it.
The
PR
385
miles
is
that
in
the
PR,
that
is
by
me,
and
it's
originally
by
Tracy
its
Tracy
Content.
E
She
did
a
fantastic
job
with
it,
but
the
PR
385
is
using
three
before
as
a
base
and
then
giving
us
space
to
go
and
build
out
changes
and
additions
to
it.
I
know
this
is
very
atypical
of
how
we
do
things
in
github,
but
this
is
how
we
have
to
do
things
in
this
context
with
our
Charter
in
the
fourth.
So
you
know
please
respect
that.
384
is
needs
to
stay,
as
is,
and
please
put
any
and
all
suggestions
and
commentary
updates
to
385.
F
A
A
F
A
F
E
D
E
A
Let's,
let's
make
this
home
work
for
everybody,
everybody
could
read
the
PR
if
you
like
it
confirm
it.
If
you
don't
comment
on
it,
I
I
want
this
approved
by
next
meeting
at
the
very
latest.
I
two
weeks
is
more
than
enough
time
to
digest
it,
but
let's
do
it
far
sooner
like
if
you
can,
if
you
have
time
today,
just
dig
into
it's
been
open
for
for
a
very
long
time
and
I'd
like
to
get
these
two
results.
I.
A
Awesome
journey,
you
had
us,
add
I,
think
Jamie
drop,
oh
no.
He
was
having
internet
issues.
F
F
A
C
F
A
So
Tracy
is
our
liaison
to
the
board
and,
yes,
we're
able
to
communicate
with
them
with
them
directly,
but
I
would
like
to
use
that
as
a
proper
communication
channel
moving
forward.
So
that's
I
agree
that
they
need
to.
They
need
to
post
minutes
I'm,
not
aware
of
where
they
didn't.
We
post
them
as
well.
F
F
F
A
E
A
E
There's
a
doc
yeah
that
we
created
a
doc
right
now,
I'm,
not
sure
if
it's
edit
mode
or
not,
but
I'd
like
to
it,
is
edit
mode
so
I'd
like
to
see
see
if
we
were
willing
to
make
a
copy
of
this.
That's
like
read-only
that
we
can
kind
of
share
more
broadly
and
try
to
get
more
feedback
on
we're
suggesting.
Oh
I,
don't
know
if
you
can
do
comments
in,
for
you,
it'd
be
nice
to
have
comments,
but
not
editing
so
yeah,
that's
the
just!
E
The
request
here
is
like
it
would
be
nice
to
be
able
to
share
this
outside
of
us
in
our
own
echo
chamber.
What
do
you
think
the
audience
would
be
chanting
I
mean
sharing
it
to
whoever
you
know
each
of
us
or
other
contributors
and
collaborators
think
would
possibly
be
someone
who
would
fit
into
the
profile
that
is
defined
in
this
document.
So
this
could
be
you
know,
co-workers
or
other
friends,
people
that
meet
up
things
like
that
yeah.
B
A
G
A
I
I,
don't
think
the
document,
as
is,
would
make
sense
to
anybody
who
has
a
thing
in
the
meetings
yeah
yeah.
So
we
need
some
massaging.
This
dog
yeah
I
need
you.
You
have
cycles
to
work
with
me
on
getting
this.
You
know
in
a
pretty
state
we
done
probably
take.
We
can
probably
just
take
a
template
from
some
other
RFC
process
and
fill
it
out
as
though
it's
a
proposal.
A
Actually,
this
is
a
good
chance
to
dog
food
I
have
a
over
in
the
bootstrap
repo
I,
have
a
PR
open
for
an
RFC
process
which
I'm
hoping
that
we
can
use
for
stage
0
proposals
for
new
programs
a
great
chance
to
see
if
it
actually
works,
maybe
we
could
write.
We
could
write
it
in
that
type
of
structure
and
I
and
see
if
that's,
it's
actually
an
effective
way
to
communicate
a
program
proposal.
Awesome.
A
Your
number
seven
I'll
link
to
it
in
the
chat
here
there
we
go
yeah
bootstrap,
PR,
number,
seven,
this
I'm
gonna
be
splitting
up
this
PR
and
integrating
it
with
in
three
other
places,
which
will
all
get
slowly
merged
in
to
help
out
with
general
governance.
But
this
adds
a
new
directory
for
stage
their
proposals
and
a
template
for
RFC
like
an
RFC
template
for
a
new
new
program
proposals.
A
So
take
a
look
at
it
and
give
comments.
If
you
want
I'm
gonna
be
great.
If
we
could
like
work
together
to
see
if
this
thing
actually
works,
yeah
might
be
a
good
vehicle
to
share
with
that's
good
possum,
let's
set
up
some
time
just
to
sit
and
I,
didn't
a
collaborative
doc
and
make
that
happen.
So
it's
good
ya
know
well
paying
everybody
and
let
people
know,
and
we
will
remain
if
anybody
else
wants
to
join
it.
A
D
So
a
couple
of
things,
I,
hope,
Ren
I,
think
most
people
on
the
call
know
this
the
nodejs
collection,
which
is
essentially
a
medium
publication.
It's
all
around
publishing
articles
related
to
no
js'
and
I
work
with
a
lot
of
people.
I
work
with
a
few
people
in
the
community
to
help
edit
it
I
know.
Holly
really
helps
me
out
a
lot.
So
thank
you
so
much
for
your
help
and
what
I've
kind
of
discovered
over
the
last
years,
we've
gotten
a
lot
more
content
in
is
we
one?
D
Don't
have
a
really
good
way
of
onboarding
new
editors,
I?
Think
when
I
first
initially
did
it?
I
was
just
like:
hey
I
need
editors
and
now
I'm
getting
some
interest
from
new
editors
that
are
like.
What's
you
know,
what
should
I
be
thinking
about?
What
are
my
expectations,
those
sorts
of
things
so
there's
no
standard
way
to
onboard
new
editors.
B
D
Then
I
think
also
our
review
process
has
gotten
a
little
muddled.
So
when
we
first
started,
people
wanted
everything
to
be
reviewed
on
github
or
Google
Documents
and
all
sorts
of
stuff
like
that.
But
as
an
editor
and
writer,
what
often
happens
is
transferring
from
like
github
or
Google
Docs
to
then
medium
a
lot
of
the
formatting
gets
wonky
and
it's
hard
and
I
think
we
spend
up
spending
a
ton
of
time
dealing
with
formatting
instead
of
using
the
medium
publication
platform
already.
That
makes
it
really
really
easy
to
edit
and
stuff
like
that.
D
So
I
have
created
just
some
recommendations
on
kind
of
ways
to
improve
our
processes
for
just
writers
and
editors
and
I
know,
while
we've
chimed
in.
But
if
anyone
else
on
this
calls
been
an
editor
or
writer
and
has
feedback
on
how
they
think
the
process
can
be
improved.
Please
feel
free
to
say
something.
So
we
can
just
kind
of
get
this
all
cleaned
up
and
squared
away
and
updating
our
documents.
So.
B
D
D
D
C
E
B
D
That's
that
and
then
also
I
haven't
filed
an
issue
in
github
on
this,
yet
I'm
planning
to
do
so,
but
something
I
kind
of
wanted
to
bring
up
with
this
group
because
I
think
it's
worth
discussion.
Another
thing
is
kind
of
as
we
look
into
2019
from
2018
social
stuff.
So
you
know,
I
helped
run
the
foundation.
Whoops
run
a
Twitter
account
the
node.js
Foundation
LinkedIn
page,
and
we
have
a
Facebook
page
and
for
the
Twitter
account
I.
D
Think
something
that
I've
heard
from
a
few
folks
is:
how
can
people
be
more
vocal,
get
more
content
on
the
Twitter
account
and
I
know?
A
lot
of
people
send
me
stuff
just
directly
on
social
but
I'm,
trying
to
figure
out
a
better
way
to
kind
of
manage
and
get
more
voices
onto
our
Twitter
feed
and
ideas
under
our
Twitter
feed.
So
one
idea
that
I
had
was
in
kubernetes
does
this:
they
have
like
a
special
email,
alias
rican,
submit
things
that
you
want
on
social
and
I
could
easily
kind
of
provide.
D
A
So
we
there
was
a
little
bit
of
discussion
in
one
of
the
meetings
about
some
type
of
setting
up
some
type
of
federated
access
to
the
account
so
that
it's
specific,
specific
people
in
the
community
or
interested
by
the
foundation
will
also
have
access
to
the.
So
it's
not
just
all
going
through
you
I.
Is
that
that's
funny
with
that?
That's
was
that
a
more
thought
into
that
and
more
looking
yeah.
D
So
the
one
thing
so
then,
there's
a
an
also,
so
that's
kind
of
one
way
that
we
can
manage
this.
The
other
thing
that
the
Linux
Foundation
networking
projects
do
is
they
actually
have
co-chairs
of
their
social
accounts.
So
again,
it's
kind
of
like
here's,
our
expectations
that
we
want
to
say
you
know,
here's
our
goals
of
the
social
channel,
here's
what
is
performing
well
that
sort
of
thing,
and
then
you
have
people
that
who
want
to
be
co-chairs.
They
can
submit
give
themselves
to
be
co-chairs.
D
So
that's
nice
in
a
way
because
it
helps
you
know
kind
of
have
people
working
with
me
to
do
it,
but
it's
it
doesn't
necessarily
allow
a
lot
of
people
to
help
participate
in
it.
It's
just
more
of
like
a
more
like
yeah.
That
seems
like
the
right
way
to
go
there,
that's
great,
but
if
you
want
more
people
involved,
then
the
alias
might
be
another
way
to
do
it
because
I
know
a
lot
of
people
do
tons
of
working
groups.
They
need
social,
too,
so
yeah,
that's
kind
of.
D
A
I
don't
know
if
it
would
be
wrong
to
have
both
actually
like
there
are.
There
are
some
people
in
the
community
who
I
think
would
be
brilliant
co-chairs
for
social
media
just
generate
great
content,
all
the
time
and
held
having
help
managing
that
would
be,
will
be
wonderful
and
then
some
some
Authority
extra
authority
over
over
social
would
be
great.
At
the
same
time,
yeah
we
could
do
what
we
do
with
with
the
medium
blog
and
accepts
submissions
from
across
the
community,
which
which
then
coaches
could
also
help
help
you
manage.
E
Exactly
like
social,
that's
exactly
what
I
was
thinking
is
like.
The
co-chairs
could
actually
also
be
on
that
alias
to
help
like
reduce
the
burden
on
a
lot
of
people.
Are
they
enough
people
or
whatever
foundation
people
and
get
those
things
queued
up
in
a
way
that,
like
he's
written
accurately,
sorry
I'm,
sick,
yeah
in
a
way
that's
written
accurately
and
like
effectively
and
like
reduce
the
burden
on
the
enough
people?
Okay,.
A
E
E
How
to
get
involved
like
cool
I
met
a
meet-up,
there's
10
people
talking
to
me.
Here's
a
way
you
can
get
involved
right
now,
rather
than
a
more
high
touch.
Well,
you
need
to
go
to
this
repo,
and
you
know
these
issues
that
kind
of
thing
like,
rather
than
needing
to
describe
it.
We
can
share
these
physical
cards
that
kind
of
have
a
lot
of
information
needed.
E
You
know
one
of
us
focusing
on
this
and
building
it
out
so
I'm
gonna
try
to
take
us
some
stabs
at
this
I,
mostly
just
ripped
carbon
copied
what's
on
there,
except
for
a
well
on
the
front
and
then
kind
of
edited
it
to
be
something
that's
more
generic
toward
no
js'
as
a
project
rather
than
specific
to
the
foundation,
see
I
love
feedback.
This
feel
free
to
do
whatever
you
want.
With
this,
we
could
maybe
try
to
do
multiple
versions,
so
you
know
one
for
no
decor
one
for
community
committee
initiatives.
E
E
So
I
mean
you
and
I
have
talked
a
lot
about
how
a
lot
of
conferences
want
a
lot
from
us
and
we
can't
always
provide
it
to
them,
but
we
do
have
you
know
collaborators
and
contributors
going
to
conferences
pretty
often
I.
You
know
I
go
to
conferences,
I
go
to
meetups,
pretty
often
it
would
be
awesome
to
be
able
to.
Instead
of
this
being
you
know,
an
official
thing
or
not
having
anything
to
straight
up
and
to
people
are
kind
of
give
to
people
at
these
events.
G
They've
handed
it
out
and
if
it's
effective.
Secondly,
that
single
point
of
entry,
we
can
choose
exactly
where
like
we
think
it
would
be
best
for
those
people
to
jump
in,
and
those
could
be
changed
over
time,
maybe
based
on
like
where
we
need
people
to
go,
but
that
particular
page
may
be
specific
to
this
is
where
the
card,
the
people
who
see
the
cars
just
jump
straight
in,
and
they
just
get
a
couple
of
options
that
are
tailored
for
them
to
get
involved
rather
than
a
list
of
stuff
that
we
have
already
out
there.
A
How
would
we
go
about
implementing
that?
So
we
just
need
to
make
sure
we
have
ownership
over
the
URL
and
we
can
literally
have
it
redirect
into
everyone.
So
to
begin
with,
because
we
don't
have
this
implement
yet
maybe
it
just
goes
to
good
person
issues,
or
it
goes
to
name
the
main
repo
that
we
want,
and
then
we
can.
G
E
G
I
I
can't
taste,
sorry,
I'm,
you're,
saying
I
was
gonna,
say:
I
can
take
the
task
of
just
creating
a
static
site
and
just
deploying
it.
It
wouldn't.
Take
me
long.
I'll
probably
use
well
yeah.
It
won't
take
me
long
to
do
something
like
that
and
then
we
could
host
it
and
then
it
could
just
actually
be
on
a
URL
as
opposed
to
github
I.
Imagine
github
just
tends
to
put
people
off
yeah.
F
E
For
what
it's
worth
I
realized
I
didn't
necessarily
make
this
entirely
clear,
so
the
foundation
is
already
made
these
cards
that
are
like
images
here.
I
just
pulled
these
out
of
the
PDF
that
Tracy
sent
me
the
ones
that
I
am
proposing
we
make
are
actually
different
to
these
ones.
They're,
not
the
foundation
specific
ones.
I
just
wanted
to
be
sure
that
yeah
I
was
clear.
There.
A
F
G
F
A
E
D
D
Say
let's,
let's
make
these
cards
and
I
think
it
sounds
like
something
we
can
easily
make
into
our
marketing
budget.
So
you
can
just
anticipate
how
much
we
think
we'll
need
how
much
swag
that
is
and
just
make
sure
we
have
like
a
good
range
of
a
number.
So
we
can
just
have
it
as
a
tag
or
an
item
in
the
marketing
budget,
but
I'd
say
just
kind
of
work
with
Tracy
on
that
and
she
can
easily
get
everything
formulated
in
help
out
and
that
stuff
too
yeah
awesome.
A
I
in
Tierney,
do
you
mind
if
I
put
you
put
you
on
the
hook
here
as
project
manager
for
this
and
make
sure
it
moves?
Well
with
we're
doing
that
yeah.
Thank
you
cool.
We
have
two
minutes
left
in
the
meeting,
any
other
things
to
chat
about
no
awesome,
good
conversations,
y'all.
Thank
you,
everybody
over
on
YouTube
and,
let's
see,
if
there's
any
sorry,
I
always
forget
to
do
this.
I.
Let's
see,
if
there's
any
comments
on
the
YouTube
channel
before
signing
off
I,
almost
never
did
it
Natacha.