►
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
A
B
I
guess
the
the
most
exciting
thing
is
that
I'm,
integrating
more
with
the
ECMO
for
to
you,
I've,
been
trying
a
couple.
Their
meetings
now,
so
we're
getting
a
little
bit
more
understanding
and
around,
however,
think
how
our
internationalization
actually
works.
You
know
within
the
standards
and
and
that
sort
of
thing,
so
I
guess
that's
the
most
exciting
thing
other
than
that.
No
significant
updates,
you
know
for
the
we
go
for
the
thirteenth
awesome.
C
Oh
we're
winding
our
way
through
our
second
cohort.
We
have
begun
outreach
to
our
mentors.
We
with
this
second
core
will
not
be
doing
a
two-sided
matching
process.
This
time
we're
going
to
be
gathering
inputs
from
are
available
mentors
and
then
based
on
the
number
of
mentors
that
we
have
available
match
with
our
community.
C
C
C
D
C
So
the
last
little
bit
of
user
feedback
is
the
general
feedback.
Sessions
were
working
with
some
local
meetups
to
align
with
the
current
and
healthiest
released
Windows
so
marked
April
timeframe.
When
were
shipping
the
the
next
major
version
release
and
then
in
October,
when
we
have
the
LTS
release
awesome,
that's.
C
A
A
Iterating
on
new
site
is,
as
we
keep
keep
doing,
the
build
out
between
now
and
June,
which
I
am
psyched
for,
and
it's
awesome
that
miles
is
able
to
get
us
that
opportunity
and
help
us
out
with
getting
it
yeah,
getting
it
on
its
way
out
so
I'm
psyched
about
progress
there,
it's
gonna
be
good
yeah
I,
and
we
had
one
of
the
item
right
now
in
this
update,
because
it
was
basically
gonna
be
an
update
anyway,
since
I
switched,
it's
a
label,
but
on
issue
316
should
come.
Come,
oh
the
node
foundation
website.
A
We
did
also
talk
about
that
a
little
bit
in
the
website
redesign
meeting.
We
actually,
you
know,
turned
out
the
livestream
and
did
some
you
know
invited
anybody
else
to
call
him
and
from
the
livestream.
He
wanted
to
come
and
chat
about
it,
but
actually
sat
down
with
Rachel
for
a
little
bit
walk
through
the
foundation
site
ia
and
see
you
know
post-merger
what
type
of
content
would
we
want
to
get
onto
the
new
site?
Probably
in
the
second
half
earlier
after
after
we
get
after
we
get
the
the
bulk
of
the
site
finished
up.
A
So
book
I'm
gonna
I
commented
in
the
ticket
I'm
gonna,
get
that
into
a
proper
proposal
structure
and
open
up
an
issue
in
website
redesign
for
how
we
want
to
shim
in
that
content,
keep
talking
with
the
foundation
folks
to
to
push
that
forward.
So
once
I
get
that
take
it
up.
We'll
transition
conversation
out
of
Comic
Con,
we
go
into
website
redesign,
develop
and
keep
chatting
over
there.
A
Yeah
awesome
any
other
initiative,
dates
or
goings,
ons
that
the
group
needs
updates
on
before
we
dive
into
agenda
topics,
no
cool
awesome,
then
we
will
get
right
into
it.
This
is
first
thing
on
the
agenda
is
issue
number
444
in
calm.
Calm
drop
drop
the
link
in
there,
so
this
was
asked
to
be
added
to
the
agenda
by
Amanda
earlier
earlier.
Today
she
has
an
update
on
the
social
media
community
collaboration
that
we
talked
about
I
believe
before
the
winter
break,
but
yeah
pop
open
that
PDF
and
I'll.
Let
Amanda
take
it
away.
Perfect.
E
Thank
you,
Adam
I,
appreciate
it
and
absolutely
I
also
shared
a
direct
link
to
the
Google
Doc.
It's
the
same
document.
So
if
anybody
wants
to
click
on
that,
I
will
touch
base
on
a
few
of
these,
and
this
is
an
initiative
that
happened
was
to
be
previously
Sara
myself
and
Rachel
have
worked
really
hard
on
this
and
I
hope
that
you
guys
are
super
excited
about
it
as
well.
So
the
intention
here
has
three
objectives.
E
We
really
want
to
provide
more
community
involvement
and
build
a
technical
content
around
our
community
involvement
and
also
help
build
out
more
job
help
opportunities
via
via
LinkedIn.
So
how
do
we
do
that?
What
is
the
best
way
to
get
involvement
through
this
process?
And
what
we
came
up
with
was
a
solution
to
have
community
involved
co-chairs
have
a
to
specific
social
media
co-chairs
that
would
be
providing
technical
content.
E
And/Or
suggestions
via
a
social
media
platform
which
we
were
suggesting,
may
be
doing
social
at
nodejs
org
and
we
would
have
them,
have
direct
access
to
our
sprout
social
and
be
able
to
actually
post
out
we'd
work
together
as
a
mini
SWAT
team.
The
four
of
us,
and
by
the
four
of
us
I
mean
Rachel
myself,
plus
these
two
co-chairs
to
make
sure
that
we're
reaching
our
social
media
experience
with
our
community.
E
One
of
the
things
I
have
noticed
since
I've,
taken
over
social
media
for
nodejs,
is
that
our
community
is
super
involved
and
specifically
likes
to
have
thought-provoking
content.
So
by
having
somebody
that
is
well
versed
in
the
technical
side
of
things
plus.
Our
experiences
I
think
that
this
can
make
it
really
exciting
enriched
social
media
experience.
So
I'm
not
going
to
go
over
every
single
line
item,
but
you
do
have
options
here
to
look
over.
Our
thought
process
is
to
have
some
guidelines.
E
E
So
the
co-chair
position
will
last
for
about
a
quarter
and
then
we
can
open
up
to
switch
out
so
that
there
is
an
ever
going
community
involvement.
So
if
you
can't
save
old
yourself
to
a
for
an
entire
year,
you
don't
to
worry
about
that.
It's
a
three
month,
commitment,
I
know:
a
lot
of
us
have
full-time
jobs
and
side
projects
so
having
a
three
month
commit,
and
it
makes
it
a
little
bit
easier
tasks
to
swallow,
and
we've
also
been
talking
about
offering
some
incentives
in
terms
of
this.
E
So
maybe
some
customized
swag
and
we're
open
up
to
some
ideas
of
what
you
might
think
might
be
a
great
incentive
to
become
a
coach
other
than
just
the
recognition
and
the
excitement
to
be
able
to
share
out
their
social
media.
But
you
know
what
are
some
ideas
that
you
would
like.
We
were
thinking,
maybe
some
badges
and
some
really
cool
specific
swag,
so
I'm
gonna
pause
there
and
see
if
Sarah
and
Rachel
want
to
add
anything
to
this.
E
We're
only
asking
for
the
time
that
you
can
offer
so
the
thought
process
honestly
Michael
is
to
have
them
assist,
Rachel
and
I,
and
it
will
be
specifically
Rachel
and
ice.
You
know
main
objective
to
run
the
social,
but
to
provide
content
to
provide
ideas.
Just
somebody
that
we
can
go
to
and
say
hey.
We
really
want
to
run
this.
Is
this
relevant
or
maybe
they
have
some
ideas
like
this
might
be
a
relevant
idea
to
post
out,
or
this
would
be
a
great
poll
question.
F
E
They
will
have
direct
access
to
so
to
sprout
social,
which
will
have
social
media
accounts,
which
is
what
I
have
I.
Don't
have
direct
access
to
the
Twitter
itself.
I
think
it's
smart
that
everybody
has
access
to
sprout
social,
so
we
can
hold
each
other
accountable
and
make
sure
things
are
getting
posted
in
a
proper
manner.
Awesome.
A
Would
be
on
these?
These
coaches,
we
talked
a
little
bit
before
the
break,
about
being
able
to
kind
of
solicit
social
media
posts
from
the
the
general
public,
but
really
have
this
kind
of
gatekeeper
to
make
sure
that
the
content
that
we're
putting
out
there
I
you
know
aligns
with
with
what
node
wants
to
see
on
their
social
media
accounts
and
our
guidelines.
Would
it
be
on
this
co-chair
too?
You
know
if
they
wanted
to
take
up
that
response,
ability
to
solicit
content
from
others
and
be
that
funnel
absolutely.
E
And
then
we
have
social
at
nodejs
network,
so
the
community
can
always
share
to
that
and
that
would
be
funneled
to
myself
Rachel
those
of
us
on
the
linux
foundation
team
and
the
co-chair,
so
they'll
have
access
to
that
that
email
address
and
we
can
filter
through
what
will
work
for
the
social
team,
social
channels.
At
that
point
in
time.
F
E
That's
the
overall
thought
process.
We
really
wanted
to
be
fully
fleshed
out
tweets
and
articles
not
just
links
to
articles
some
ideas.
But
yes,
the
idea
assist
sends
like
your
suggestions.
It's
like
a
suggestion
box.
Send
your
suggestions,
there's
social
social
out,
nodejs
that
work
and
the
team
will
take
it
and
run
with
it,
so
that
we're
making
sure
that
everybody's
voice
is
being
heard.
That's.
A
A
A
E
A
E
My
hope
is
to
have
them.
If
you
look
down
at
the
bottom,
we
have
a
process
of
becoming
my
hope
is
to
have
them
fill
out
the
form
and
then
from
there.
We
can
discuss
internally
how
we
want
to
select
based
upon
our
overall
processes,
so
I'm
thinking,
Rachele
myself,
Sarah.
Anybody
from
calm,
calm
that
like
to
join
that
conversation,
maybe
we
we
figure
out
who's
gonna
have
the
best
opportunity.
E
He
has
the
most
time
within
the
remainder
of
this
first
quarter,
because
I
know
we
have
what
about
a
two
and
a
half
month
left
in
the
remainder
of
this
first
quarter.
So
whoever
has
the
the
most
available
time
to
devote
to
this
might
be
to
personally
choose
overall
we'd
like
to
have
to
every
quarter
so
that
they're
sharing
duties
and
that
that
nobody's
feeling
overwhelmed
with
too
much
information
or
too
much
responsibility.
E
So
my
thought
process
is
to
to
choose
based
upon
who's
available
and
who's
willing,
to
really
grab
this
and
run
with
it
and
help
us
kind
of
flesh
out
guidelines
because
it'll
be
a
live
and
learn
situation
where
we're
learning
as
we're
going
and
and
the
first
couple
of
co-chairs
are
gonna,
be
the
ones
that
are
really
gonna.
Help
us
divulge
and
and
put
together
guidelines
for
future
co-chairs.
A
E
F
Is
really
good
the
one
the
one
other
question
I'll
ask
is
in
terms
of
social
guidelines.
You
mentioned
like
what
kind
of
scope
did
you
have
in
mind,
for
that
is
it
for
the
people
participating
as
the
co-chair
or
for
people
participating
in
the
project
or
like
hell
bro?
Did
you
think
you
were
going
to
smoke
that
we're.
E
Probably
gonna
do
it
very
general,
just
some
general
best
practices
guidelines
and
then
we
can
scale
depending
upon
issues
that
arise,
I,
think
being
general
in
terms
of
just
somebody
who's
not
familiar
with
running
social
media.
Maybe
they
don't
understand
best
practices,
so
I'm
just
putting
together
really
good
best
practices
document,
and
we
can
scale
it
down
on
an
individual
basis
as
needed.
Okay,.
E
A
H
So
yeah
I
I
put
some
more
information
into
the
initial
issue
and
the
feedback
that
we
got
from
the
last
calm
calm
was.
We
just
need
a
little
bit
more
process
and
a
little
bit
more
guidance
around
how
we
want
the
working
group,
/
team
update,
you
know,
updates
to
work,
and
so
so,
basically,
what
I've
done
is
just
kind
of
given
a
general
overview
of
what
we're
hoping
to
accomplish.
H
I've
included
an
example
that
we
have
with
the
security
working
group
and,
just
you
know,
general
guidelines.
As
far
as
how
long
we
would
like
it
to
be
specific
topics
that
we
would
want.
Each
update
to
cover
that
we
felt
you
know
would
be
helpful.
Obviously
this
is
open
to
feedback
and
discussion.
I
wanted
to
give
a
clear
guideline
on
how
a
person
could
submit,
and
so
we
took
the
feedback
to
try
a
Google
Form,
which
is
linked
in
the
issue
with
it's
got
a
list
of
questions.
H
H
So
then
some
expectations,
what
one
can
expect
after
you,
you
know
some
would
be
in
touch
with
you
and
we
would
start
the
process
of
getting
it
drafted
and
you
know,
get
all
the
review
process
together
and
then
another
ask
of
this
group
was
sort
of
expectation
around
the
content
calendar
and
maybe
you
know
who
the
contacts
would
be
for
those
different
pieces
of
content,
and
so
I
have
that
link
as
well
in
a
spreadsheet,
and
so
that's
that's.
Basically,
that's
basically
the
rundown.
You
know
also
based
on
the
last
time
we
talked.
H
H
C
H
H
D
The
thinking
is
that
some
people
might
want
to
submit
the
draft
post
and
write
it
from
start
to
finish
the
way
the
security
working
group
did,
some
working
group
leads
might
not.
So,
if
that's
the
case,
we're
trying
to
give
them
a
halfway
point
where
we,
if
they
give
us
enough
information,
we
can
get
a
draft
together.
Yeah.
F
Is
there
any
way
to
have
these
Google
Forms
like
I'm,
just
thinking
the
first
time
great
somebody
comes
to
do
it?
The
second
time?
Is
there
a
way
to
have
some
of
the
stuff
prefilled
in
so
that,
like
you
know
the
objective
and
people
don't
have
to
re-enter
all
that
information?
Each
time
I
mean
I,
know
some.
H
H
From
on
the
back
end,
it
wouldn't
you
know,
be
much
for
whoever's,
editing
it
on
the
foundation
side
or
the
editor
side
to
copy
and
paste
that
information
and
so
I'm
not
sure
how
it
could
be
prefilled
necessary,
but
I
mean
you
know.
Maybe
it's
one
of
those
things
where
the
person
says
see
previous
submission,
yeah
Dawson.
A
F
A
Yeah
I
think
that
would
probably
be
a
concern
if
we
were
like
hoping
for
each
working
group
to
submit
more
than
once
a
year.
But
you
know
this
from
the
from
the
spreadsheet
that
I
just
shot
a
link
to
there.
It
looks
like
the
cadence
were
hoping
for
is
like
one
major
update
with
you
know,
social
ask
you
know
social
ck's
right
okay
per
year.
A
F
I
was
thinking
more
yeah,
monthly
or
whatever,
like
the
security
working
group,
does
but
yeah
in
the
context
of
once
a
month
and
I
think
actually
focusing
on
that
makes
sense
to
me
too
so,
yeah,
okay
got
it
in
that
context.
Yeah.
A
F
F
A
A
Okay
in
a
similar
vein,
I
kept
this
on
the
agenda,
since
I
still
have
a
tag
on
it,
I
want
to
make
sure
they
just
weren't
any
extra
updates
if
there
I'll
take
the
tag
off
for
next
week.
This
is
number
four
39,
no
js'
collection,
next
steps,
which
was
a
placeholder
I,
believe
yeah
last
meeting,
just
to
get
an
update
from
you
Rachel
and
where
this
is
heading.
If
you
have
any
significant
updates
here,
should
we
save
this?
For
when
we
take
off
the
jacket.
H
H
To
just
to
just
to
update,
one
of
the
asks
was
to
come
up
with
a
sort
of
a
job
description
for
what
an
editor.
You
know
what
we
would
require
of
an
editor
and
I
have
I'm
trying
to
get
in
touch
with
with
Tierney
and
I've
had
a
chance
to
chat
with
McNeill
and
so
I'm,
trying
to
put
together
just
a
little
bit
of
guidance
around
the
ask
of
what
we
would
want
from
an
editor
and
then,
in
addition
to
that
I'm
going
to
put
together
a
reader
survey
that
I
would
like
to
get
feedback.
H
You
know
from
y'all
on
and
just
to
kind
of
make
sure
that
were
gathering
the
right
information
so
that
we
know
what
our
readers
would
like
to
read
in
the
node.js
collection.
So
those
are
the
two
updates
of
where
that's
at
and
I'm
hoping
to
be
able
to
cook
something
a
little
bit
more
formal
here
in
the
next
Oh
week.
Your
tailor
beautiful.
A
Let's
post
that
when
you,
when
you
get
it
on
the
issue
here,
on
4:39
I'm,
gonna,
remove
the
label
and
we'll
bring
it
back
for
conversation
if
and
when
we
need
it.
I'd
love
to
see
the
deliverable
same
thing
like
same
as
with
the
social
media
collaboration
process,
I'd
love
to
see
that
whatever
whatever
process
our
governance
talks
here,
the
art
into
into
compound
after
we
all
drafted
and
happy
I
yeah.
So.
A
Cool
chugging
right
along
issue
number
423
so
end
of
last
year.
We
got
a
recommendation
together
for
individual
membership
and
it
kind
of
ended
up
with
Tracy
bringing
it
to
the
board
for
for
conversation
and
us
trying
to
figure
out
what
next
steps
look
like,
what
what
needs
are
from
come
come
what
we
need
to
and
how
we
need
to
represent
in
its
traffic
at
all,
and
you
know
where
this,
where
this
process
takes
us
in
2019
it
so
Tracy.
A
I
So
the
culmination
of
a
lot
of
work
from
folks
this
past
year
had
us
at
a
draft
for
the
individual
membership
program,
as
well
as
a
recommendation
for
the
individual
member
Director
moving
forward
that
draft
those
drafts
were
presented
to
the
board,
but
that
was
discussion
right,
not
resolution.
So
it
wasn't
us
modifying
the
bylaws
and
charters
of
the
node
foundation
just
yet
for
those
programs.
But
what
I've
done
from
that
time
with
the
board,
because
there
weren't
any
when
I
say
there
was
no
major
objection
when
that
was
presented.
I
As
you
know,
just
like
find
replaces
for
foundation
versus
no
foundation,
so
would
love
y'all's
input,
there's
a
lot
of
context,
I
think
in
these
proposals.
There
is
a
lot
of
history
and
a
lot
of
lessons
learned.
So
if
you
have
questions
about
things
and
why
they
were
proposed
the
way
they
are
I'm
all
ears
and
and
happy
to
answer,
provide
context,
at
least
as
to
why
that
was
drafted,
but
also
input,
I.
Think.
I
You
know,
as
as
I
think
I've
said
in
the
PR.
It's
the
individual
membership
program
does
not
have
to
run
without
a
director
or
sorry.
The
individual
membership
program
can't
exist
without
a
director,
but
our
recommendation
was
that
a
director
would
best
support
the
groups
that
we
are
trying
to
help
with
individual
membership
program.
I
There
is
I
will
say
some
some
discussion
around
what
it
means
to
sort
of
be
like
a
member
program
versus
a
membership
class
in
the
foundation,
and
so
I
forgot
to
highlight
that
in
that
proposal,
because
that's
a
discussion
that
we
need
to
have,
but
is
certainly
not
like
assault.
You
know
solid
in
any
way,
and
we
need
input
to
make
sure
that
when
we
talk
about
that
at
the
board
level
that
we're
representing
what
everyone
feels
is
vital
to
the
outcomes
right
for
us
further
for
the
vision
that
we're
trying
to
build.
J
I
Well
and
the
reason
that
I
didn't
move
forward
with
omitting
or
note
by
laws
in
charter
first
was
that
that
is
a
lot
of
work.
I
mean
it
takes
a
later
time,
and
it
was
my
personal
belief
that
if
I
worked,
if
I
spent
more
energy
on
that,
instead
of
us
working
on
this
in
the
bootstrap
repo
that
we
would
sort
of
see
a
pause
right,
because
if
we
build
this
out
just
the
future
iteration
just
in
node
when
we
are
at
what
seems
to
be
moving.
F
I
C
I
Class,
which,
in
my
mind
in
some
ways
right,
is
a
good
thing
because
there
is
accountability
baked
in
depending
on
what
you've
written,
but
we
also
don't
want
to
have
like
unnecessary
burden
on
the
foundation.
If
the
majority
of
what
we're
doing
is
you
know,
project
perks,
you
know
that's
sort
of
right,
yeah,
yeah
I
mean
I,
would
love
to
hear
people's
opinions
on
it.
I
do
think.
Accountability
is
important
from
the
foundation
to
the
project
and
vice
versa,
but
figuring
out
how
we
do
that.
You
know
in
a
healthy
sustainable
way
is
something
I'm?
C
I
F
K
A
It
kind
of
gets
to
the
the
core
question
of
what's
the
intent
of
the
program
and
if
it's
to
drive
engagement
and
a
feeling
of
co-ownership,
then
you
don't
need
a
separate
membership
class.
If
it's
too
literally
like
legally
give
some
ownership
away,
then
then
it
should
be
a
membership
class.
So,
like
answering
a
question
with
the
larger
group,
especially
yeah.
I
Well,
I
think
a
little
more
than
that
is
like
you
know.
If,
if
a
member
program
is
more
of
a
customer
customer
service
challenge
versus
like
what
you
had
just
said,
then
that's
one
thing,
but
I
do
want
to
make
sure
that
we
are
held
accountable
for
the
individual
member
program
and
like
how
our
members
feel
towards
that
right.
I
Like
I,
think
one
thing
that
we've
seen
clear
it's
been
acknowledged
publicly
is
that
you
know
no
one's
very
happy
with
the
individual,
the
prior
individual
member
program
and
I
think
there's
a
fair
amount
of
like
we.
There
could
have
been
more
accountability
sooner,
but
yeah
I,
don't
know
if,
like
you,
if
the
membership
process
exists
for
that
to
be.
A
Yep,
so
getting
getting
a
little
more
out
of
the
weeds
on
program.
Details
I
want
to
talk
for
a
second
about
path
forward
and
just
make
sure
it's
like
so
Tracy
and
and
and
I.
We,
we
both
kind
of
things
like
they're
the
right
place
for
this
process
to
continue
forward
seems
to
be
in
bootstrap,
especially
given
you
know
the
impending,
the
impending
merger
coming
up,
and
so
what?
A
What
that
would
mean,
though,
is
we're
we're
holding
off
on
executing
on
the
program
in
node
like
the
node
project,
proper,
correct,
Tracy,
so
we'd
be
shifting
shifting
conversation
with
the
kind
of
proposal,
there's
I
I'll,
admit,
I,
haven't
gotten
a
chance
to
look
at
the
PRS
myself
since
I
posted
them,
but
giving
them
it
looks
like
it
does.
Look
like
a
direct
lift
of
what
was
in
our
like
articles
on
our
documents
but
yeah,
because
to
me
that
sounds
like
the
right
path
forward.
That.
I
I
think
that's
something
too.
That
needs
to
be
worked
on.
More
certainly,
Dawson
is
the.
How
do
we
support
the
individual
projects
right
like
from
membership?
Perspective?
Is
like
talk
about
the
CPC
and
how
the
work
is
going
to
be
concentrated
in
various
areas.
Right,
there
are
going
specific
things
that
are
gonna
have
to
be
subcommittees,
because
the
group
overall
doesn't
need
to
or
care,
but
like
with
the
foundation
I'm
sure
there
are
going
to
be
people
who
are
passionate
about
the
specific
projects
and
want
to
support
them.
F
Of
the
things
we
talked
about
like
because
I
think
it
comes
back
to
you
know,
I've
heard
the
foundation
described
as
just
a
place
to
host
great
projects.
So
it's
like
the
real
interest
is
in
the
projects.
So
you
know
some
of
the
things
we
talked
about
is
like
you
know,
for
example,
a
channel
to
talk
to
the
TSC
members
or
the
kumkum
members,
or
something
right
that
people
might
not
be
so
interested
to
talk
to
the
CPC
members
because
they're
not
necessarily
tied
to
a
particular
project
similar.
F
I
A
To
me
this
it,
it
strikes
me
as
more
of
a
marketing
problem
as
well
like
how
you
want
you
want
something
to
be
proud
of,
supporting
the
project
that
they
care
about
right.
So
how
do
you
make?
How
do
you
make
them
feel
as
though
what
they've
contributed
to
the
individual
membership
program
is
going
to
help
out
the
project
and
the
foundation
that
they
care
about
and
not
the
foundation
the
whole?
A
I
F
Some
of
them,
one
of
the
perks
we
discussed
as
well,
was
being
listed
as
a
you
know,
as
a
supporter
on
you
know,
and
one
of
the
repos
within
the
node,
the
node
project
and
and
a
repo
there
where
people
could
who
members
could
talk
about
things
right,
I'm,
not
sure
that
works
as
well
as
they
at
the
foundation
level
right,
because
you
want
part
of
it,
was
like
the
you're
excited
about
the
project.
How
do
I
support
the
project?
F
So
you
know
the
the
King
and
choosing
it
obviously
doesn't
have
to
be
mandatory,
but
they
build
you
know.
Maybe
when
you
join
the
individual
membership
program,
it's
like
and
I'm
a
supporter
of
these
projects.
You
know
choose
one
or
more
and
then
that
flows
through
to
what
the
benefits
you
get
out
of
it
I.
You
know
I'm,
not
sure.
F
A
So
it
sounds
like
this
may
warrant
a
spin
out
discussion
specifically
on
how
to
translate
the
proposal
into
this
more.
You
know
this
larger
umbrella
that
will
probably
be
kind
of
like
a
joint
effort
between
the
bootstrap
group
and
the
the
old
individual
membership
subgroup
that
we
had
working
on
this
proposal.
F
A
Awesome
anything
else
to
add
on
the
individual
membership.
Otherwise,
we'll
see
you
in
the
next
meeting
port
yeah
meeting
awesome
and
we
covered
issue
316
and
the
website
update,
so
that
the
exhausts
are
written
agenda
which
is
awesome.
There
was
one
more
thing
that
Michael
mentioned
in
the
beginning.
This
is
issue
number
eighty
in
bootstrap,
where
we're
kind
of
iterating
on
what
the
initial
code
of
conduct
for
for
bootstrap
should
be
actually
might
want
to
give
a
quick
yeah.
F
F
And
I
think
there
is
one
thing
we
talked
about
that
the
comb
comb
can
maybe
think
about
and
help
so
it
came
out
of
you
know
some
discussions
around.
Should
there
be
a
requirement
on
a
code
of
conduct
for
projects
joining
the
foundation?
There
was
some
discussion
about
like.
Should
we
allow
projects
to
have
their
own
code
of
conducts?
You
know
it
could
potentially
be
like
something
which
is
stronger
or
whatever.
F
We
did
have
some
discussion,
though,
that
in
terms
of
the
foundation
supporting
code
of
conducts
and
the
enforcement
and
escalation
process,
there
is
some
advantages
to
having
just
one
for
all
the
projects.
So
I
wrote
up.
You
know
this
is
not
baked,
not
agreed,
not
kin.
You
know
just
a.
It
was
really
just
to
get
the
discussion
going,
but
it's
written
from
the
position
that
there's
a
single
Code
of
Conduct,
adopted
by
you,
know
that
we
expect
projects
to
adopt
as
they
joined
the
foundation.
F
I
think
I've
said
you
know
within
three
months
joining
it's
the
contributor
you
know
I've
written
it
in
is
the
contributor
the
contributor
covenant,
since
that
seems
to
have
a
fairly
wide
adoption
enforcement
is
I've
tried
to
break
it
down
into
there's,
going
to
be
spaces
which
are
the
foundation
spaces
and
the
CPC
is
sort
of
responsible
for
those
and
then
there's
projects
bases.
So
if
people
want
to
report
an
issue
in
the
foundation
spaces,
it
would
be
the
CPC
that
would
have
responsibility
for
that,
and
the
projects
would
be
responsible
for
their
own
spaces.
F
F
Adding
to
that
there's,
it
captures
an
escalation
process.
That
says,
you
know.
If
somebody
has
a
report
and
they're
not
comfortable
reporting
it
to
the
CPC
or
to
the
leadership
of
the
project
for
some
particular
reason,
maybe
it's
a
member
of
one
of
those
groups.
They
are
complaining
about
they
can
or
if
they
are
not
happy
with
the
outcome
of
the
process
in
one
of
those
two
places.
F
There's
an
escalation
path
in
that
escalation
path
is
to
you
know
what
I've
called
a
code
of
conduct
panel,
which
is
basically
a
group
of
people
from
the
foundation
from
the
board
and
from
the
project's
themselves
for
and
they're
you
know
people
have
been
trained
and
who,
basically,
you
know,
stepped
up
to
participate
in
that
escalation
process.
Take
those
reports-
and
you
know,
investigate-
and
you
know,
make
a
report.
F
You
know
the
key
things
really
is
that
the
projects
you
know
it's
written
in
that
the
project's
need
to
support
that,
like
you
know
that
as
part
of
joining
they've
agreed
to
have
a
code
of
conduct
and
they've
agreed
to
participate
and
support
that
escalation
process
and
then
I've
come
up
with.
You
know
my
first
cut
at
what
the
membership
of
that
panel
might
be,
which
is
you
know,
the
foundation
executive
director,
a
member
from
the
board
or
a
member
from
the
CPC
and
then
I
said.
F
You
know
a
member
from
each
of
the
projects
and
one
from
the
top
level
projects,
and
that's
because
there's
been
some
concern
that
we
don't
want
to
have
too
high
expectations
and
all
the
projects
just
because
your
top
level
project
doesn't
mean
you
have
somebody
you
can
send
to
this
panel,
but
that
the
project's
can
have
our
presentation
if
they
want
to
and
I
included,
even
optionally
us
inviting
an
outside
expert.
So
you
know
I
one
areas
we
struggled
is
there's
some
special
expertise
and
knowledge
that
you
know
a
lot
of
our
our
regular
contributors.
I
F
I
I
No
I
know,
but
it
just
yes,
so
there
will
be
interesting
discussions
because
that
can
feel
like
you
know.
I
can
certainly
make
people
feel
like
they're
losing
agency
over
their
work
or
what,
if
they
don't
have
the
you
know,
they
haven't
really
enforced
much
of
a
code
of
conduct
in
the
past
and
now
they
have
to
and
what
happens
if
they
just
don't
like
what
happens.
I
A
F
Not
a
I'm
happy
with
whatever
I
just
I
didn't
want
board.
Is
I
didn't
want
to
get
joke.
How
can
confused
with
board
members?
So
that's
why
I
choose
chose
panel,
but
yeah
I
think
about
jump
in
it
because
it
is.
You
know,
like
Tracy
said
there.
This
could
be
quite
controversial
in
terms
of
a
requirement,
but
the
discussion,
the
bootstrap
committee
is,
you
know
it
felt
I
think
that
there
was
a
fairly
strong
consensus,
that
a
code
of
conduct
would
be
a
requirement
yeah.
F
I
I
think
it's
just
executing
more
I
think
I'm
worried
about
just
like
once
this
gets
adopted
because
I
think
it
is.
It
does
seem
like
there's
been
plenty
of
conversation
around
the
need
for
this,
but
it's
certainly
around
like
if
you're
gonna
make
peep
we'll
do
this,
which
we
think
is
important,
and
then
we
also
probably
have
some
responsibility
in
helping
everyone
get
prepped
and
understand
what
it
takes
to.
You
know,
enforce
CSE
and
have
there's.
C
I
just
wanted
to
call
it
and
maybe
I'm
not
seeing
it
through
the
the
poll
request
that
you
know
having
gone
through
this
journey
several
times.
I
think
it'll
be
really
important
to
make
sure
that
you
are
getting.
You
know
some
non-white
males
in
the
mix
early
and
you
know
making
sure
that
you
have
good
representation
as
you're
rolling
this
out.
That
was.
F
Exactly
the
other
thing
I
wanted
to
mention
was
that
in
the
in
the
bootstrap
meeting
there
was
there
was
two
things
we
want
to
validate,
one
that
you
know
this
would
be
okay
with
projects
and
you,
the
communities
that
are
most
affected
and
most
need.
The
protection
give
us
some
feedback
that
this
is
satisfies
their
their
needs
right,
and
so
that's,
where
a
calm
come
I
think
might
be
able
to
help.
In
terms
of
you
know,
how
do
we
get
that
feedback.
A
Okay,
I
gotta
drop,
awesome,
yeah
and
we're
coming
up
on
time.
Thank
you,
Michael
for
surfacing
that
y'all
pile
into
the
the
bootstrap
repo
exactly
to
get
engaged
there.
Where
I.
You
know
it
directly
affects
what
this
group
is
tasked
with
over
on
the
node
side
of
things,
so
I
think
it's
important.
What
part
of
that
process
awesome
any
other
quick,
last-minute
points
before
we
wrap
it
up.
Two
minutes
I'll
take
silence
as
a
resounding
no
and
thank
you.
Everybody
was
calling
in
over
on
YouTube.
We
will
see
you
next
week,
woohoo
all
right.