►
From YouTube: Community Committee Meeting
Description
A
Who
we
are
lives?
Everyone
thanks
going
to
be
talking
about
no
Jess
today,
specifically
the
community
committee,
so
we
go
ahead
and
get
started
so
quick
reminder
if
everyone
would
add
themselves
to
the
agenda
the
present
list,
everyone
who's
in
the
Xoom
could
add
themselves
so
the
present
list
that
would
be
swell
I,
just
put
it
in
these
zoom
chat
so
to
get
started.
Let's
kick
things
off
with
initiative,
updates
any
updates
from
initiatives
I.
B
A
B
So
I
guess
the
things
that
I'm
involved
in
the
collapse
omit
we
are.
We've
got
a
lot
more
submissions
that
we
did
last
time.
So
thanks
everybody
for
sharing
that
CFP
I
really
appreciate
it
and
if
you
see
places
to
put
it,
please
continue
to
do
that.
We
are
doing
two
tracks
just
to
kind
of
give
you
a
reminder.
The
idea
is
that
we
for
the
community
quarter
track,
which
will
run
parallel
to
the
conference.
B
We're
gonna,
do
more
workshop
style
talks
and
then
for
the
collapse
on
itself
would
do
more
collaborative
style
conversations
around
particular
topics.
I
talked
to
Kristen
this
week
and
I
think
that
we
are
gonna,
go
ahead
and
do
away
with
code
and
learn
for
this
year.
There
just
isn't
enough
interest
and
it's
a
ton
of
work
for
everybody
to
put
it
on
so
I
think
we're
gonna
use
that
space
to
do
more
collapse
on
that
stuff.
Could.
B
B
If
you'd
like
to
run
it,
we're
happy
to
have
you
like
pull
stuff
in,
we
just
Christians
that
a
lot
of
outreach
work
and
just
didn't
get
the
responses
back.
That
he
needed
to
put
something
together
is
what
it
comes
down
to
okay,
so
we
figured
we'll
give
it
a
rest
this
year,
maybe
they'll
be
more
interest
next
year
and
we
can
go
from
there
and
in
the
meantime,
people
seem
somewhat
excited
about
having
that
half-day
to
work
on
more
clever
collaboration.
B
Okay,
so
we
are
also
Rachel
and
I
are
running
the
ask
me
any
things
they
have
been
wildly
successful:
I
have
them
booked
out
I,
think
to
like
next
October
with
topics
so
we're
doing
them
once
a
month
we're
trying
to
do
them
mid
month
and
the
next
one
is
actually
kong-kong.
So
that
should
be
really
interesting.
We've
got
some
good
questions
in
from
the
audience.
We've
had
good
participation.
It's
been
a
good
conversation,
so
I'm
really
excited
about
those.
B
If
anybody
wants
links
or
anything
like
that,
please
just
don't
hesitate
to
ask
and
then
I
guess
the
other
thing
that
I
have
been
involved
in
the
don't
see
anybody
from.
But
if
I'm
missing
you
please
speak
up
is
the
mentorship
committee.
We
have
been
working
on
figuring
out
how
to
go
into
the
next
cohort.
So
looking
at,
do
we
want
requirements?
Do
we
not
want
requirements,
kind
of
figuring
out
what
we
want
that
cohort
to
look
like,
so
that's
what
we're
working
on
for
that
I
think!
That's!
That's
all
my
updates.
B
A
C
C
C
Like
onboarding
process,
we've
had
a
few
board
approvals
recently
in
terms
of
the
code
of
conduct
that
we're
working
through
like
the
whole
process,
and
everything
excuse
me,
as
well
as
the
travel
fund,
moving
to
the
Open
Jazz
foundation
and,
additionally,
like
you,
know,
IP
policy
and
Trademark
and,
like
you
know,
style,
guide,
kind
of
related
stuff,
I
think
there's
progress
there
as
well
I'm
trying
to
think
of
one
else,
Brian
Tierney.
What
else
menacing
something
important
highlight:
I.
C
Good,
we,
you
know,
we
have
weekly
meeting
so
I
always
feel
like
there's
so
much
going
on.
Yeah
yeah.
A
A
A
A
One
thing
that's
not
on
the
agenda,
but
I
do
want
to
make
sure
we
talked
about
Tracy
Hines
CUDA,
to
PR,
to
move
herself
to
emeritus
I.
Do
want
to
thank
Tracy
for
the
immense
amount
of
time
effort
and
passion
that
she's
in
compassion
that
she's
put
in
to
the
compound.
An
ode
to
the
open
G
has
foundations
various
aspects
of
the
projects
overall
success
if
y'all
could
go
and
if
conga
members
and
others
it
go
and
review
and
approve
that,
and
also
you
know,
leaving
a
nice
comment
of
it
would
be,
would
be
Thanks.
A
So
you
know
that's
something.
That's
currently
open
I
am
going
to
be
merging.
That
I
realized
that
now
I
have
a
meeting
immediately
after
this,
but
after
that
meeting
I
will
be
merging
it
and
also
making
the
additional
necessary
changes
to
move
Tracy
out
of
the
kumkum
team
on
github
and
also
the
email,
alias
cool.
A
So
this
is
I
believe
its
kind
of
along
the
lines
of
what
of
what
Evo
was
suggesting
earlier
around.
You
know
a
link
to
kind
of
drive
the
collaborate
summit
and
and
kind
of
get
people's
interests
engaged.
So
I
think
this
is
more
of
a
status
kind
of
checking,
rather
than
a
actual
to
do
here,
and
it
doesn't
look
like
any
of
the
people
involved
who
tagged
it
are
here
so
I'm
just
gonna
leave
it
at
that.
Any
comments,
questions,
thoughts,
concerns
I,.
A
A
C
You
know
work
through
any
things
that
we
need
to
work
on
issues
and
updates
and
think
about.
You
know,
membership
and
such
but
also
a
place
for
mentoring,
for
notes
to
be
a
resource
for
current
and
potential
new
members,
and
also
you
know
if
there's
any
collaborative
work
or
discussions
that
may
need
to
happen
around
the
initiative.
Work
or
anything
like
that,
but
generally
speaking,
kind
of
happen
to
have
an
open
office
hours
time
slot
where
we
can
be
available,
but
also
get
some
progress
on
other
things.
C
And
what
are
the
driving
factors
for
me
here
is
the
the
mentoring
and
looking
to
get
new
members
interested
non
boarded
and,
to
kind
of
you
know,
just
generally
freshen
up
things
around
here
and
so
I
actually
commented
about
20
minutes
ago
that
maybe
we
can
do
the
1800
UTC
time
slot
on
off
weeks
for
calm
calm,
so
that
would
be
Thursdays
at
2:00
p.m.
Eastern
time.
For
me,
I
think
you
know,
as
that
that's
the
week
that
they
have
there's
the
redesign
meeting
at
noon.
C
That
is
directly
the
same
timeslot
as
the
comm
meeting
on
hours,
so
I'm,
proposing
that
we
started
at
2
hours
after
they
start.
So
it
would
be
like
an
hour
gap
between
those
two
meetings,
so
yeah
I,
just
thought
it'd
be
a
good
place
to
you
know,
get
some
work
done
and
try
and
get
your
people
interested
in
involvement
in
the
work
that
we
do
and
it's
all
sounds.
A
C
Would
be
great,
they'll,
be
really
great:
yeah
I,
don't
have
a
everything
like
clearly
can't
planned
out
and
send
some
agenda,
or
particular
things
to
work
on,
but
I'll
start
working
on
that
and
plan
for
for
next
week
and
focus
probably
on
some
of
the
mentoring
aspects
and
like
the
membership
aspects.
And
you
know
if
anybody
wants
to
chat
about
this
particularly
journey
about
like
membership
and
membership
progression
and
membership.
Overall,
we
can
kind
of
flush,
some
of
that
out
to
them
and
I
think
like
so
these
PR
to
be
an
observer.
C
A
D
D
So
I
guess
we
had
for
the
past
two
weeks,
just
the
pair
of
suggestions,
and
you
know
a
lot
of
feedback
and
basically
I'm
going
to
share
the
link
in
the
chat.
I
can
also
paste
it
in
the
doc,
but
you
know
the
suggestions
led
to
you
know,
refinements
suited
to
the
questions,
and
we
really
landed
on
the
set
of
questions
that
we
are
hoping
to
get
into
the
survey
at
this
point.
D
I
think
the
purpose
of
these
questions
is
just
to
gauge
what
what
an
initiative
can
look
like
and
as
as
we
went
through,
building
those
questions
and
trying
to
understand
where,
where
the
open
source
community
in
general
is
there
definitely
is
you
know
a
lot
to
be
wanting
to
you
know
to
get
to
in
the
future,
and
a
lot
of
communities
are
struggling
with.
Let's
call
it
understanding
how
to
go
about
inclusive.
D
D
D
D
A
D
A
D
Actually,
there's
that
one
question
that
I
would
like
to
just
reiterate
again:
yeah
I
know
that
a
survey
question
about
how
people
feel
about
when
they're
contributing
elsewhere
in
the
project,
which
is
a
domain
that
you
know,
is
under
the
control
of
the
people
who
are
leading
these
efforts.
How
we
phrase
a
question
about
satisfaction
from
work.
Other
people
are
doing
I
just
it's.
It's
really
hardly
fair
for
me
to
to
decide
on
how
raise
that
question.
A
So
I
don't
know
from
from
at
least
my
perspective,
so
we're
talking
just
for
context
in
the
improving
odds
survey,
questions
document
we're
talking
about
question
number
six
this,
and
this
is
linked
from
issue
number
five.
Three
eight
in
the
calm,
calm
repo
just
for
posterity.
So
the
specific
though
the
specific
question,
thank
you,
I
I
think
is
very
valuable
in
the
context
of
it's
an
agnostic
question
that
people
can
answer
and
people
can
get
like
context
out
of
that,
whether
it's
you
know
I
I,
don't
think
it's
biased.
A
I
guess
is
what
I'm
trying
to
get
at
here.
It
doesn't
seem
like
there's
a
level
of
bias
in
this,
which
is
good
and
I.
I.
Think
that
it's
generic
enough
that
that's
okay
and
it's
saying,
okay,
to
include
that
my
specific
question,
it's
the
specific
context
I
was
asking
about
about,
was
employed
by
no
gist
communities.
A
You
participate
or
engage
this,
so
I
personally
participate
with
the
note
school
in
New
York
I
also,
you
know
attend
various
meetups
in
New
York
and
speak
good
speak
and
attend
a
lot
of
conferences
around
node
and
JavaScript
I.
Wasn't
the
the
question?
I
had
here
was
more
of
a
clarifying
one
of
noches
communities.
Is
that?
D
So
let
me
zoom
in
a
bit,
so
it's
legible
yeah,
so
I.
How
would
how
would
we
trace
this
so
that
it's
clear
American
can
just
can
connect?
Can
I
get
everybody's?
Take
like
I
know
it's
watery.
I
have
a
you
know
a
knack
for
being
very
watery
when
I
try
to
speak.
So
if.
A
A
D
A
D
Yeah
and
as
soon
as
I
can
keep
away
that
coloring
in
the
background
which
I
I
know
I
used
one
of
the
buttons
to
put
there.
It
will
be
more
legible,
hopefully
for
everyone,
but
if
that
was
how
you
wanted
to
go
about
this
from
you
know,
as
a
suggestion,
uncommon,
definitely
you
know
I
definitely
real
recognize
that
it
was
not
very
clear
okay.
So
so
thank
you.
Yeah.
A
Noise,
so,
given
that
context,
I'm
relatively
okay
with
this
and
I
I-
think
that
you
know
the
community
committee
has
and
given
ample
ability
to
object
to
this.
If
this
is
something
that
they
would
like
to
object
to,
so
perhaps
just
for
good
measure,
you
could
ping
one
more
time
and
then
say
you
know
we're
gonna
be
sharing
this.
Do
you
mean
end
of
November
end
of
October.
A
In
that
case,
I
would
just
comment
in
that
and
say:
hey
we're
going
to
be
sending
these
two
XYZ
people
to
be
included
in
the
survey.
You
know
and
then
that
may
spark
more
discussion.
I
doubt
it
but
yeah
you
you're
more
than
welcome
to
send
those
over
and
if
we
need
to,
we
can
adjust,
but
I
I.
Don't
think
we
will
so.
D
You
know
position,
but
also
be
able
to
rely
on
the
tools
that
we
need
to
use
to.
You
know
affect
inclusivity
in
a
way
that
is
inclusive
to
everyone,
not
just
those
who
need
accessibility
aspects
and
not
just
those
who
don't
think
you
know
they
can
happen
without
getting
in
wait.
So
so
this
is
going
to
be
a
long-term
initiative
and
it's
going
to
take
you
know
open
source
and
people
in
the
tools
that
we
use
all
right.
Thank
you.
Yeah.
A
D
D
A
A
A
A
Basically,
TLDR
is
I.
Recently
was
able
to
join
the
electron
collaborator
summit
in
New
York
and
had
the
opportunity
to
kind
of
learn
about
how
they
they
do
things
they
set.
Ok,
ours,
which
is
very
interesting
for
open
source
projects,
but
I
also
think
how
they
approach
is
really
valuable
of
theirs.
This
well
kind
of
defined
framework
for
setting
kind
of
measurement
of
success
and
being
able
to
tweak
when
things
aren't
going
as
planned
and
kind
of
course
craft.
A
So
this
you
know
in
the
case
of
hey,
I,
want
to
spin
up
an
initiative
being
able
to,
at
the
outset,
set
up
your
goals
and
say
this
is
what
we
want
to
do
is
a
good
Avenue
to
make
sure
that
there's
like
value
and
no
not
value
but
ability
to
execute
in
a
path
forward
right
for
new
initiatives.
So
that's
kind
of
my
goal
here
and
also
for
existing
issues,
like
has
pretty
clear,
clearly
defined
goals,
and
so
you
know
they're.
Okay,
ours
would
be
relatively
easy
or
relatively
straight
forward.
A
A
This
is
something
I'd
like
to
see
us
try
to
implement
and
if
there's
no
objections
that
we,
you
know
can't
overcome,
I
think
that
this
would
be
a
valuable
thing
for
everyone,
especially
because
we
don't
have
the
kind
of
element
of
we're
writing
code
and
there's
very
obvious
progress
where
it's
is
less
obvious
progress
I.
You
know
people
ask
me:
what
is
the
calm
calm
doing?
A
Is
it
successful
and
there's
not
you
know
outside
of
commits
randomly
I
there's
nothing
I
can
explicitly
point
you
easily
and
have
them
go
find
themselves
that
enables
them
to
find
that
out,
rather
than
me,
having
to
kind
of
go
into
massive
detail
about
what
we
do
and
how
we
find
success
and
how
we
define
success.
So
you
know
I
think
this
is
an
overall
benefit
in
in
many
ways,
and
something
I'd
like
to
see
us
do.
A
I
might
hope
here
is
that
we
can
have
a
session
at
the
collaborator
summit
to
actually
sit
down
for
me,
Heat's,
like
I
I,
don't
think
we
can
do
okay,
ours
in
an
hour,
so
it
might
need
to
be
or
maybe
sue,
and
then
the
third,
but
you
know,
setting
at
least
cares
for
calm,
calm
and
enabling
initiatives
to
set
their
own
or
help
us
working.
You
know
as
initiative
members
setting
up
defining
those
and
setting
those
up
I'm
tearing
them.
A
A
I
think
that
it
would
be
extremely
valuable
for
us
to
be
able
to
have
that
kind
of
end
up
there
and
move
forward
there
so
yeah
and
for
context.
This
is
issue
five
for
second
on
the
compound
repo,
so
yeah.
If
you
have
thoughts
on
this
positive
negative
I
try
to
get
feedback
from
full,
simple
beforehand,
just
to
make
sure
I
was
kind
of
not
moving
away
from
what
I
would
expect
or
what
others
would
expect
from
the
project
and
from
something
like
this,
but
yeah
I.
B
A
A
B
A
E
A
Ongoing
so
let's
see
the
required
updates
to
the
Charter
I
went
through
and
updated
all
of
the
comments
there
addressed
everything
that
was
kind
of
coming
to
down
responded
to.
We
mostly
have
LG
TMS,
Plus,
Ones
I
think
we
are
at
a
place
where
this
can
be
merged.
Please
don't
forget,
but
this
is
at
a
place
where
I
have
created
the
issue
in
the
open,
JSC
BC,
which
is
Foundation
CPC
issue
or
repo,
and
it
doesn't
look
like
there's
any
comments
there,
but
this
should
be
theoretically
an
agenda
item
for
the
next
meeting.
A
A
The
Charter
reflects
a
bunch
of
things
that
we
don't
do
and
if
you
know
whether
we
want
to
begin
doing
those
or
whether
we
want
to
kind
of
strike
those
and
make
it
reflect
more
of
what
we
currently
do
is
up
to
us,
but
I
would
like
to
kind
of
move
in
one
direction
or
the
other
just
so
that
it
reflects
the
state
of
the
comp.
So
yeah,
that's
a
you
know,
update
on
that.
We
should
be
seeing
this
merge
sooner
so
I'm
happy
about
that.
Any
comments.
Questions
thoughts,
concerns
that
one.
A
A
Our
meeting
went
well,
we
kind
of
moved
things
forward.
There
are
some
additional
things
that
were
unexpected
to
me
that
came
down
or
came
through,
but
I
will
be
reaching
out
to
folks
about
that
shortly.
Here,
perhaps
it's
worth
having
a
quick
private
session
if
we
have
time
like
still
keeping
in
the
time
frame,
but
this
should
be
moving
forward.
A
Relatively
soonish
I
just
need
to
spend
some
time
with
regional,
let's
sit
down
and
actually
get
through
the
editing
of
the
blog
post,
update
this
and
ship
it,
given
that
additional
context,
I'm
sorry
for
being
big
I,
just
don't
want
to
over
commit
to
things
before
anything
has
been
discussed
broadly
and
I.
Don't
want
to
prematurely
discuss
it
problem,
so
yeah,
that's
that's!
Coming
up!
E
I
can't
talk
about
it,
so
I
was
busy
in
last
week's
I
was
traveling,
couldn't
catch
up
with
the
PR
I'm,
not
turning.
You
submitted
review
on
the
on
the
PR
and
I
wanted
to
get
in
touch
with
Rachel
first
to
see
what
changes
we
want
to
do
in
the
process
and
then
like
some,
we
make
the
changes
after
the
review,
but
she
was
also
busy
with
the
foundation
things
and
in
some
conferences
also.