►
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
All
right
well
we're
live.
Thank
you,
everyone
for
joining
joining
the
call
joining
the
live
stream
wherever
the
case
may
be.
Thanks
for
participating
thanks
to
native
script,
for
coming
by
today,
too,
please
feel
at
home
and
come
by.
You
know
often
early
and
often
vote
early
and
often
before
we
get
into
agenda
items.
Do
we
have
announcements?
I
see
things
popping
up
in
the
in
the
dock.
There.
B
We
do
we,
you
know
it's
been
for
a
summer
quite
a
busy
summer.
One
important
thing
to
just
note.
For
today.
After
these
messages,
there
will
be
a
marketing
committee
meeting.
So
if
you're
interested
in
joining
our
marketing
beauty
call
and
that
rachel
leads
that's
at
3
eastern
so
and
stick
around
and
that's
on
our
public
calendar
we've
also
been
looking
at
the
programming
committee.
That's
that's
going
to
keep
going
for
openjs
world.
B
We
have
some
pretty
exciting
and
ambitious
things
we
want
to
do
for
2022
because
it's
the
first
time
we're
going
to
get
back
together
in
person.
Hopefully
fingers
crossed
knocking
on
wood.
You
know
saying
all
the
prayers.
So
if
you
would
like
this
is
a
open
invitation
to
any
of
our
community
members
who
want
to
help
us
populate
that
conference
with
great
content,
great
keynote
ideas,
other
programming,
we'd
love
to
have
you
weigh
in
to
that
and
so
we're
going
to
start
by
a
meeting
bi-weekly.
B
So
the
next
meeting
is,
I
think,
next
week
on
thursdays
at
11
eastern.
So
that's
those
two
things.
We've
got
some
exciting
project
news
that
will
be
coming
out
and
we
love
the
cpc
support,
highlighting
that
when
those
articles
are
ready
so
be
looking
for
those
weekly
emails
from
rachel
that
help
us
kind
of
promote
things
that
are
coming
out
of
out
of
our
awesome
projects
like
no
red
and
jquery
all
have
cool
stuff,
not
happening
other
projects.
B
Yeah
we're
percolating
on
a
new
book
club
meeting,
so
this
is
not
a
not
a
frequent
thing,
but
we're
we're
going
to
organize
a
book
club
call
to
discuss
a
couple
of
related
books
how
to
do
nothing.
B
So
that's
a
book
that
I
think
we
can
all
get
behind
and
a
book
called
braiding
sweetgrass,
and
this
is
maybe
like
a
it's
like
a
more
philosophical.
I
think
book
club
set
of
selections
so
anyway.
Those
are
great
check
out
that
convo
in
in
book
club,
if
you're
interested
so
and
do
nothing
interested
in
doing
nothing.
Go
to
the
book
club.
A
My
favorite
I'm
reminded
too
because
I
think
it
was
kind
of
mentioned
there,
but
you
know
node
red
has
a
version.
Two
release
just
went
out.
I
think
today,
so
that's
cool
boost
that
find
it
on
the
twitter
cool.
E
This
friday,
I
think,
is
the
word
meeting.
I
don't
think
there's
anything
on
the
list
unless
I'm
forgetting
something
that
we
should
be
bringing
to
the
board.
So
if
there
is
remind
me
but
yep
the
board
meetings
this
this
week,
people
can
follow
the
public
session
as
per
the
calendar.
A
Great,
thank
you
cool,
so
getting
into
the
agenda.
The
first
item
here
is
something
that
I
created
a
little
bit
ago.
This
is
the
chairperson
election
should
be
happening.
A
What
am
I
saying
here
yeah?
I
think
my
suggestion
was
that
we
would
open
up
nominations
today
and
have
those
nominations
be
open
until
the
next
official
meeting
so
two
weeks,
which
would
be
july
20th
to
august
3rd
and
then
hold
the
election.
You
know
after
that
nomination
period
closes
and
have
that
open
for
two
weeks
as
well
that
that's
essentially
is
a
month.
I
think
in
the
past
we've
only
done
one
week,
but
you
know
I
don't
know
what.
A
B
A
Assuming
we
get
people
who
nominate
yeah,
that
would
be
great.
That
makes
sense
to
me.
I
imagine
we'll
just
use
this
issue
for
folks.
To
I
mean
I
guess
we'll
do
we'll
do
private
nominations
first,
and
then
we
can
do
candidate
statements
in
that
issue.
Once
we
open
things
up
or
what
have
you.
A
I
have
a
doc
that
I
wrote
last
year
and
I
think
it
largely
applies,
except
when
I
say
weekly
meetings.
We've
now
actually
moved
to
bi-weekly,
but
I
think
everything
else
is
still
fairly
the
same
in
terms
of
like
commitments
and
expectations
and
and
and
things
like
that,
I'm
happy
to
talk
with
anyone.
A
If,
if
they're
interested,
I
I
will
run
again
but
I'm
happy
to
to
help
folks
out
or
even
you
know,
if
somebody's
like
well
I'd
like
to
run
next
time
or
whatever
I'd
mentor
them
through
the
year
or
whatever
happy
to
to
help
folks
get
involved.
A
All
right!
Well,
that's
that
so
yeah,
I
guess.
Maybe
we
should
put
a
note
in
there
or
comment
in
there
jewelry
that
people
can
reach
out
to
you.
B
Yep
I'll
I'll
go
at
it
now.
A
A
If
we
had
something
in
place
that
would
have
created
that
issue
for
us,
but
hopefully
soon
it's
something
that
I
want
to
work
on,
as
is
getting
something
like
this
put
together,
but
I
just
haven't
had
the
time
yet,
but
definitely
if
anybody's
interested
I
mean,
I
think
you
know
some
sort
of
cron
job
github
action
thing
that
we
could
configure
for
for
creating
issues
for
certain
things
that
we've
dropped
into
this
issue
here,
like
the
elections
and
whatnot,
would
be
great.
E
F
Oh,
alternatively,
I
mean
we've
got
currently
automation
running
that
generates
the
recurring
calendar
from
the
calendar,
from
what
I
understood
for
the
issues
for
the
agendas
for
this
and
others,
because
we
use
that
same
automation.
C
That's
that's
what
michael
that's!
What
michael
michael
is
the
one
who
runs
that
and
that
automation
is
extremely
old
and
something
that
we
should
probably
try
to
avoid
using
more
than
we
have
to.
A
E
A
Yes,
yeah,
that's
what
I
think,
michael
and
tierney
are
saying
that
there's
something
in
place.
That's
good
enough
to
start
using
for
for
this
purpose,
it's
not
fully
fleshed
out.
I
think
to
really
do
the
meeting
issues
yet
where
we
have,
you
know
the
calendar
and
everything
all
put
together,
but
in
terms
of
just
like
creating
an
issue
based
on
some
sort
of
time
frame
that
that
is
available
to
us
already
and
tierney
and
I'll
take
a
look
at
it
right
then,.
B
I
was
gonna
say
I
said
tierney,
I
think
a
long
time
ago
you
may
remember
these
glitch
apps
that
that
ada
rose
had
made
for
the
ar
working
group,
and-
and
I
wonder
if,
if
maybe
those
are
an
interesting
starting
point
too-
that
it
does
something
very
similar.
A
I'm
kind
of
the
same
all
right
cool.
Well,
if
you
I'd
be
happy
to
work
on
it
with
you,
either
live
or
not.
We
can.
We
can
do
something
next
week.
Maybe
yeah
sounds
good
cool
thanks
tony
appreciate
it
rock
and
roll
well
moving
on
the
next
item
is
the
community
fund?
A
Do
we
want
to
talk
about
this
now
or
do
you
want
to
save
it?
For
last
and
and
since
we
don't
have
a
long
agenda,
we
could
get
people
up
to
speed.
I
I
wasn't
able
to
attend
last
week's
meeting
and
then
we
could
use
the
remaining
time
to.
You
know
talk
more
about
it
and
such.
B
I
would
support
saving
that
one
for
last
and
that
way
we
cover
the
other
items
in
our
agenda
and
we
can.
A
Yeah
great,
let's
do
it.
I
will
look
at
this
next
issue,
the
dco
cla
issue
to
see,
if
there's
any
updates,
I
don't
see
anything.
I
know
you
know
this
is
on
brian's
radar
and
there's
been
conversations
in
the
node
space
and
stuff.
So
I
presume
that
you
know
it
hasn't
fallen
off
the
radar
and
that's.
D
E
F
Ahead,
in
addition
to
the
actual
execution
of
of
getting
the
dclcla
stuff
working,
I
think
we
do
have
a
a
real
issue
here
about
the
communication
about
it,
where
it's
not
really
clear
in
in
places
whether
it
is
actually
a
requirement
or
not,
and
when
you
actually
then
look
at
what
our
current
projects
are
doing.
F
I
think,
from
from
what
I
could
find
everyone
that
has
some
sort
of
cla
bot
is
using
the
js
foundation.
Cla
still.
B
At
this
point,
the
js
foundation's
instance
of
the
cla
assistant
tool
is
about
three
years
out
of
date
and
we
we
looked
at
like
okay,
can
we
can
we
temporarily
patch
it
and
make
it
work,
but
it's
just
it's
just
too
much
work,
so
we'd
rather
switch
everybody
to
easy
cla.
B
So
that's
we'd
like
for
everyone
using
every
every
project
that
chooses
to
use
a
cla
to
use
the
easy
cla
tool
and
you
know
for
the
dcos.
We
have
a
handful
of
projects
that
are
using
that
and
they're
all
using
different
things,
and
so
the
thought
here
with
probot
dco
was:
let's
help
the
project
sort
of
adopt
the
same
dco
tooling.
So
whenever
there's
a
support
issue,
there's
only
one
thing
that
we
have
to
you
know
muck
with,
and
so
that's
also
kind
of
the
background.
F
Think
I
mean
my
next
question
here
is:
are
we
actually
tracking
cla
or
dco
usage
of
the
status
thereof
across
the
projects,
because
I'm
not
aware
that
we
are?
I.
B
B
Yeah
I
mean
it's
just
basic.
Unless
I
mean
I
don't
think,
we've
made
that
public
because
I
didn't
think
anybody
cared.
But
if,
if
that's
something
that
we
want
to
track,
we
can.
F
Nothing's
new,
basically
I'm
saying
that
as
a
project
maintainer,
I
have
been
harassed
far
far
too
little
about
getting
my
act
together
and
getting
the
cla
stuff
updated,
and
I
would
like
more
harassment
for
me
and
others
like
me
who
have
just
you
know,
given
that
it
works
and
it
doesn't
seem
to
be
causing
active
issues
being
stuck
with
just
foundation.
Cla.
B
No,
I
I
I
I
hear
you
you
know
for
what
it's
worth.
We
started
a
a
project
board
and
trello
for
our
p
internal
pm
and
one
of
the
top
items
is
jsf.
B
Cla
bot
migrate,
everyone
to
eccla.
So
this
is
one
of
those
projects
that
is
going
to
take
some
kind
of
longer
term,
more
intensive
effort,
but
and
we're
trying
to
knock
some
things
off
of
our
plates
so
that
we
can
focus
on
it.
E
F
B
That's
a
good
question
I
mean
so
it's
obviously
not
mandatory.
We
don't
mandate
that
projects
use
the
cla
and
we
don't
mandate
that
projects
use
dco.
They
could
choose,
neither
that's
an
option
we
would
like
for
them
to
use
the
same
tooling,
because
it
does
make
supporting
the
projects
much
much
easier
and
faster,
and
but
I'm
not
sure,
if
we,
I
think
it
may
be
a
very
strong
encouragement
that
they
use
the
same
tool.
They
do
have
to
use
the
same
text
of
the
cla
if
they're
adopting
the
cla.
B
That
text
has
to
be
the
same,
but
if
the
function
is
a
through
a
different
bot
because
they
prefer
a
different
bot,
you
know-
or
they
have
yeah.
E
Different,
the
question
is
like:
if
you
have
to
choose
one
or
the
other,
then
it
would,
it
would
make
sense
for
us
to
have
a
table.
That
says
we
know
which
one
they've
chosen
and
they've
implemented
it
and
do
we
have
you
know
like
these.
The
migration
is
there
something
we
need
to
do
to
to
help
them
implement
it
successfully
kind
of
thing.
C
And
yeah,
I
I
think
the
more
broadly
the
specific
question
in
that
issue
is:
is
this
a
requirement
yes
or
no,
and
having
one
or
the
it's
not
having
a
dco
or
having
a
cla?
It's
is
having
one
of
them
a
requirement.
I
think
the
answer
is
yes.
C
I
I
think
I
like
I.
I
also
think
it's
documented
somewhere,
like
I
think
that
is
in
our
documentation,
there's
assertions
in
some
pr
node
making,
which
I
think
are
incorrect-
that
we
got
referred
to
there
that
yeah
it's
it's
a
requirement
like
there's
assertions,
saying
it's
not
a
requirement.
C
D
I'll
I'll
look
for
it
after
the
call,
unless
you
find
it
before.
E
E
B
I
think
that'd
be
great
to
have
the
just
to
point
to
the
source
of
the
policy,
and
so
then
you
know
just
to
clarify:
that's
that's
the
requirement,
but
the
requirement
to
use
tool
a
for
your
cla
implementation.
B
A
If
I
understand
correctly
too
just
to
make
sure
I
do,
it
is
a
requirement
to
use
either
a
clo
a
cla
or
dco,
and
there
is
a
requirement
on
what
the
text
says
specifically
but
the
tooling.
While
we
would
encourage
folks
to
use
common
tooling
that
the
openjs
foundation
recommends
that's
not
a
requirement.
A
D
And
I
think,
if
you
choose
to
have
an
exception,
for
example,
amp
has
an
exception.
That
was
a
thoughtful
decision
just
because
from
a
support
perspective
on
a
bigger
project,
so
just
keep
up
with
the
movement.
E
E
C
Never
I
I
think
our
recommendation
should
be
easy
cla
and
we
could
support
that
and
if
other
projects
want
to
do
their
own
thing,
that's
cool.
They
can
do
that
and
we're
not
going
to
so
like
they
can't
expect
support
from
us
if
they're
going
to
use
something
other
than
the
the
foundation
tool
like,
I
think
that's
a
fine
thing.
D
A
Cool
michael,
will,
you
worry,
do
you
want
to
respond
on
the
issue
you
want.
E
A
It
might
be
worth
saying
in
here
as
well
that
if
that's
not
clear,
we
should
update
the
onboarding
checklist.
I
suppose.
F
F
Does
that
then
mean
that
if
a
different
project
uses
a
different
cla
tool
that
those
would
get
synced,
somehow
or
if
another
project
uses
a
dco
approach
that
this
person,
because
this
on
the
cla
doesn't
need
to
follow
the
vco
flow,
or
do
they
still
need
to
do
that?
Or
are
we
just
presuming
that
these
corner
cases
are
going
to
solve
themselves
or
are
rare
enough
in
practice
that
we
don't
worry
about
them?.
B
I
think
we're
we
want
to.
Maybe,
since
those
corner
cases
are
corner
cases,
we
will
take
those
as
they
they
pop
up,
as
opposed
to
like
at
least
this
is
my
sense
as
opposed
to
trying
to
like
figure
out
what
they
are
in
advance
and
determine
how
to
solve
them
at
that
time.
I
I
don't
know
what
the
corner
cases
would
be
at
this
moment.
D
A
Cool,
well,
I'm
glad
that
we
worked
through
that.
Thank
you
moving
on.
If,
if
I
may,
the
final
issue
is
the
community
fund
issue.
I
wasn't
able
to
attend
last
week's
meeting,
so
if
anybody
can
give
a
summary,
that
would
be
great.
D
D
I
can
discuss,
I
can
recap
what
where
we
are
in
community
fund
and
then
marie
can
talk
about
what
we
talked
about
on
our
last
working
session
and
I'm
losing
track
of
who's
who
in
our
community
fund,
michael,
I
believe
you
were
in
there.
Sarah,
I
believe,
was
in
the
call
just
in
we.
D
The
linux
foundation
has
something
called
lift
scholarships
and
they
have
a
really
sort
of
great
model
for
applications,
and
so
we
are
recommending
that
we
follow
that
process
and
perhaps
even
the
brand,
because
it
has,
it
has
some
already
identity
and
brand
within
and
among
the
open
source
communities.
There's
also
a
web
developer.
D
Lyft
scholarship
and
some
of
those
web
developers
may
choose
to
take
the
node.js
certification,
but
we
are
recommending
that
we
start
with
20
scholarships
and
we
look
at
doing
it
either
half
yearly
or
quarterly,
depending
on
how
that
first
20
goes
and
from
a
criteria
we
would
love
to
make
it
needs
based
on
an
honor
system
with
an
eye
toward
underrepresented
communities,
including
geographies.
D
There's
a
couple
of
categories
of
the
lf.
We
thought
were
interesting
that
we
thought
we
would
sort
of
combine
one
is
on
diverse
communities
and
then
another
one.
It's
a
category
called
do-gooders
and
how
what
you're
working
on
or
how
these
skills
would
help
you
do
more
things
that
benefit
your
community
or
society.
D
So
the
next
action
item
is
for
us
to
one.
I
was
going
to
draft
some
proposed
language
for
an
application.
Two,
I'm
working
with
our
training
and
certification
team
just
to
get
the
process
in
place
for
executing
and
then
the
other
piece.
I
think
that
we
all
need
to
figure
out
on.
This
call
is
how
the
cpc
would
have
its
review
process.
D
The
lf
found
that
just
having
two
people
on
that
initial
cut
was
super
helpful
before
it
went
to
the
broader
team
to
do
a
review,
and
so
we
thought
we
would
do
something
similar
have
a
small
committee.
Perhaps
two
people
on
point
to
make
recommendations
and
then
the
final
approval
would
be
a
cpc
private
vote.
A
Great,
so
so
we
can,
we
can
talk
about
that,
but
I
feel
like
jory
did
you?
Was
there
something
that
you
we
were
waiting
for
you
to
talk
to.
B
Now
excuse
at
the
appropriate
point,
I
can
recap
the
working
group
session
of
last
week
and
but
obviously
robin
has
got
all
the
updates
from
the
community
fund
combos
in
the
last
couple
of
weeks.
So
we
can
stay
on
this
topic
for
now
and
just
at
the
end
do
a
quick
update.
D
On
last
week's
working
session-
and
so
I
think
what
we
had
looked
at-
how
the
cpc
implements
the
how
the
how
they
had
implemented
the
travel
fund,
that
was,
I
think,
a
little
bit
more
public
on
the
issues
on
who
was
applying
and
not,
I
think,
just
one,
the
sheer
quantity
that
we
may
receive
and
just
maybe
the
confidential
nature
on
why
they
would
they're
requesting
it.
We
thought
it
would
be
more
appropriate
to
be
private.
D
So
yeah
and
then
we
can
see
how
that
goes,
and
then
we
should
have
another
working
session
as
well,
because
this
would
just
take
a
small
little
piece
of
the
community
fund,
so
obviously
the
community
fund's
much
larger
than
that.
So
I
would
encourage
this
group
to
think
of
some
other
ways
to
spread
the
love
from
the
community
fund
to
the
to
folks.
C
A
Okay
sounds
good.
I
I
both
those
things
that
I
think
are
kind
of
up
for
debates.
Not
the
right
word
but
discussion,
I
guess
being
private,
makes
sense
to
me.
I
think
two
people
on
initial
review
make
sense
to
me
too.
So
I'm
a
thumbs
up
on
both
those.
B
We
also
wanted
to
just
as
an
fy.
There
were
a
number
of
different
things
we
were
talking
about
using
the
community
fund
for
and
the
sponsorship.
Scholarships
were
one
that
we
decided
was
worth
diving
into
at
first,
because
it
has
perhaps
the
greatest
impact,
and
it
certainly
helps
with
social
issues
that
we
care
about
more
so
than
than
some
others.
So
we
thought
that
was
maybe
you
know
the
start
with
what
might
be
the
most
important,
even
if
it's
one
of
the
more
difficult
to
work
through.
B
So
that
was
maybe
one
of
the
the
reasons
why
we're
starting
there.
First,
you
might
have
a
question,
oh
cool.
F
Yeah
in
the
in
the
chat
I
just
asked,
because
I
realized
that
I
might
end
up
wanting
to
file
a
request
for
the
travel
fund
that
I
thought
I'd
ask
do.
Are
we
open
for
business
effectively
on
that.
B
I
think
so
I
mean
I
think
you
know
until
even
until
we
get
the
documentation
of
like
the
the
comm,
the
community
fund
model
working,
we
can
safely
continue
to
use
the
existing
travel
fund
application
process.
So
I
think
you're
good
emily.
A
Okay,
I
was
kind
of
under
the
assumption,
but
you
know
assumptions
are
never
great.
B
That
was
my
assumption
too
yeah.
It's
it's
a
it's.
It's
part
of
the
whole
community
fun
kitty
and
we're
we're
thinking
about.
Who
says
that
I
don't
know
some
people
say
that
it's!
Oh,
it's
a
kitty.
Why
is
it
a
kitty?
Why
do
people
call
that?
I
don't
know
anyway.
Sorry,
it's
yeah,
it's
part
of
that,
but
we're
adding
to
you
know
the
the
fund
in
a
in
a.
A
Way
now
now,
I
feel
compelled
to
look
up
kitty
in
the
sense
of
pot
of
money
at
stake
in
the
game.
First
appeared
in
the
late
19th
century
interesting.
A
A
A
You
know
oh,
never
mind,
because
their
name
just
totally
escaped
me.
E
Anyway,
but
I
think
jory
you
were
talking
about
some
of
the
other
programs
that
were
discussed
in
the
last
meeting.
B
Yeah,
so
this
was
now,
I
think,
a
couple
more
than
a
couple
of
working
sessions
ago
when
we
were
sort
of
talking
about
the
the
scope
of
the
community
fund
and
what
would
we
kind
of
want
to
see
those
monies
be
used
for
obviously
travel
for
things
like
what
a
million
suggesting
was
one,
and
you
know
scholarship
or
sponsorship
of
people
to
you
know,
take
a
class
or
get
the
node
certification,
for
example,
was
was
another
and
you
know
there
was
two
other
sort
of
paths
that
are
suddenly.
D
B
B
A
Great,
so
do
we
want
to
what
what
we
still
got
15
minutes.
B
So
to
to
wrap
that
up,
I
don't
think
there's
any
so.
Robin's
got
the
action
on
the
language.
We
don't
have
another
working
session
for
specifically
for
for
the
community
fund
currently
like
on
the
books,
so
just
as
an
fyi.
B
Our
next
working
group
meeting
is
next
tuesday,
the
27th
and
we're
going
to
be
talking
about
new
collaboration
spaces.
B
So
obviously
we've
got
the
the
package,
security
vulnerability,
working
group,
which
is
a
mouthful
to
say,
and
that's
one
that's
kicked
off,
but
we
talked
about
having
a
brainstorm
session
around
other
potential
areas
for
collaboration
spaces,
and
so
that's
the
topic
of
next
week's
the
week
of
august.
10Th
is
a
working
session
with
the
package,
security,
vulnerability
working
group
and
then,
after
that,
we
don't
so
so
I
guess
my
follow-up
question
is:
do
we
want
to
put
a
community
fund
a
specific
working
session
on
the
books
for
in
august.
A
D
B
D
A
I
just
want
to
ask
really
quickly
before
we
get
to
that.
I
do
want
to
hear,
but
I
assume
jory
you're,
updating
that,
like
meta
issue
doc,
what
do
you
think
it's
great?
I
am.
B
One,
maybe
then
tvd
and
I'll
we'll
confirm
with
wes
and
darcy
darcy
and
all
and
see
if
that's
okay.
So
so
we
could.
We
could
say
that
for
now
and
if
not
the
community
fund
yeah.
A
Cool
so
jori,
you
want
to
update
us
on
that.
B
On
tech
strategy,
yes,
I
do
great
and
I
will
do
that
while
I
also
dig
up
the
notes
from
that
meeting,
really
quick,
which
isn't
hacking,
the
hello
itself,
give
me
two
shakes.
Sorry
will
I
sign
in
to
my
account.
My
memory
is
not
what
it
used
to
be.
B
I
just
have
room
for
jingles
now,
apparently,
okay
yeah,
so
this
was
the
third
meeting
to
talk
about
like
a
generalized
tech
tech
strategy.
B
If
you
may
recall
from
our
like
our
second
meeting,
we
came
up
with
this
great
sort
of
rough
schema
of,
say,
solution,
domains
and
how
each
of
our
projects
kind
of
fits
within
those
those
components
and
domains.
B
And
then
we
started
in
discussion
three
to
articulate
like
how
we
might
like
to
use
that
information
either,
for
you
know
helping
to
describe
to
the
the
public,
and
so,
if
you'll
recall,
one
of
the
reasons
we
have.
This
is
because
robin
frequently
gets
questions
from
analysts
and
reporters
about
our
our
projects
and
they
want
to
know
sort
of
like
what
kind
of
projects
are
can
be
found
at
the
openjs
foundation
and
how
do
they
all
fit
together.
B
So
we
want
to
make
some
sort
of
version
of
this
available
so
that
that
can
be
useful
for
people
to
understand
who
we
are
and
what
we
do.
But
we
also
don't
want
to
dissuade
potential
projects
from
joining
our
squad
because
they
see
oh
well,
they've
already
got.
You
know
project
x
y
z,
and
that
fits
the
same
solution
that
my
project
does,
so
they
may
not
be
interested
in
supporting
us.
That's
obviously
not
the
case
either.
B
So
what
robin
is
going
to
do
is
draft
a
she
felt
like
she
had
enough
she's
sitting
right
here,
but
I'll
tell
you
what
she
said
enough
information
to
be
able
to
have
some
kind
of
canned
responses
and
share
that
with
us.
For
for
the
analyst
questions
like
the
press,
questions
that
she
might
get
and
that
solves
one
one
need
for
this
discussion
and
then
for
for
the
others
we
we
didn't.
B
Quite
I
mean
because,
like
the
landscape
was
another
way
of
looking
at
this
data
too,
but
we
felt
that
that
was
not
not
quite
right.
We
don't
really
have
a
plan
for
how
we
could
make
this
like
a
public
display
type
at
the
moment.
B
Other
discussions,
though,
that
we
had
were-
and
this
was
quite
a
fun
conversation,
understanding
the
like
types
of
projects
that
we
have
so,
for
example,
the
types
of
projects
that
fit
within
those
components
that
are
you
know,
supported
by
or
brought
forth
by,
a
larger
company
and
so
like,
like
loopback,
was
largely
supported
by
ibm
early
on
it's
now,
a
big
open
source
project,
but
like
that
kind
of
type,
the
type
and
also
the
type
of
what
we
call
the
nebraskan
in
honor
of
the
xkcd
comic
about
the
soul,
maintainer
of
in
nebraska,
supporting
an
important
project
and
and
what
those
projects
needs
and
how
we
serve
them
are
different,
so
kind
of
understanding
the
value
exchange
and
what
the
benefits
are
and
how
we
can
best
help
those
projects
take
advantage
of
the
benefits
yeah,
so
that
kind
of
summarizes
what
was
a,
I
think,
largely
wide-ranging
discussion.
B
B
Talking
points
to
answer
those
tough
press
questions
and
then
be
being
able
to
communicate
to
our
projects,
how
they
take
advantage
of
services
from
the
foundation
and
how
they
see
the
value
of
joining
emily.
What
am
I
missing,
because
you
brought
a
lot
to
that
conversation
too.
F
The
only
thing
I'm
thinking
of
is
indeed
figuring
out
how
much
exactly
we
want
to
to
support,
said
nebraskans,
and
what
can
we
really
offer
them?
And
is
it
our
place
to
offer
them
anything?
Which
is,
I
think,
a
whole
discussion
that
I
think
we
ought
to
have
in
the
cpc
in
some
form
about
whether
it
makes
sense
to
because
currently,
what
we
support
really
well
are
communities
that
together
build
projects
and
either
small
communities
or
large
communities.
But
then
we
have
a
in
the
javascript
ecosystem.
F
We
have
a
lot
of
projects
that
are
really
significant,
where
there
is
really
just
a
sole
maintainer
behind
it
and
and
for
those
the
sort
of
perceived
at
least
cost
of
of
applying
and
joining
the
foundation.
F
B
I
think
one
of
the
things
you
said
too,
which
was
very
like
kind
of
no
dodge
or
but
eye
opening
for
me,
was
just
like
the
burden
of
managing
an
application
process
when
the
need
for
the
maintainer
is
that
sort
of
like
insurance
policy,
that,
if
something
happens
to
me,
someone
is
going
to
make
sure
that
my
my
project
and
its
users
are
okay
and
so
the
lift
of
doing
the
whole
openjs.
B
H
E
F
Yeah,
so
so,
basically,
I'm
for
this
question,
I
I'm
myself
thinking
of
it
as
as
the
maintainer
of,
for
example,
yaml
a
decently
widely
used
product
library,
but
I'm
the
sole
maintainer,
and
you
know
I'm
doing
it
for
fun
and
and
going
through
the
whole
application
and
writing
a
bunch
of
of
text
and
figuring
things
out
again,
even
though
I've
kind
of
done
all
of
that
already
once
for
message,
format
or
at
least
got
mostly
grandfathered
in
it
just
feels
like
yeah,
not
gonna
bother.
F
E
F
Maybe
something
like
that,
I
I
don't
know
what
the
criteria
might
be,
whether
it
would
be
more
push
rather
than
pull
in
terms
of
of
these,
these
memberships
or
whatever.
We
call
them
happening
or
progressing,
but
I
don't
know.
F
B
B
Know
how
do
we
perhaps
like
signal
that
so
that
such
a
maintainer
out
there
feels
like
we
can
and
will
and
that
we
think
that
they're
important
and
how
do
we
also,
as
emily
put
it
like
lower
their
burden
to
entry?
B
You
know,
I
think,
is
another
great
question,
so
so
maybe
that
in
and
of
itself
is
worth
carving
out
into
a
working
session
for
ways
that
we
can
streamline,
process
or
create
like
a
a
faster
track
sort
of
which
is,
I
think
one
at
one
point
we're
like.
Are
we
talking
about
a
new
membership
like
our
project
level?
You
know
now
that
we've
gotten
rid
of
growth,
we'll
we'll
add
the
nebraskan.
B
You
know
layer,
you
know
so
so
maybe
we
do
a
a
session
of
discussion
on
like
like
marketing
and
catering
to
that
group,
so
just
mostly
so
that
they
know
that
we
we
are
here
for
them.
E
D
I
think
finishing
what
michael
was
saying
is
a
different
type,
because
you
know
one
of
our
key
benefits
is
marketing
so
and
rachel
is
just
a
part
of
a
person.
You
know
just
one
person,
so
if
we
brought
on
100
that
would
that
were
very
critical
and
we
could
protect
them
and
their
ip
and
their
project
and
provide
assurance
and
peace
of
mind.
But
we'd
have
to
probably
take
a
look
at
our
marketing
services
and
start
creating
some
tiered
sort
of
offerings
right
now.
D
It's
we
feel
like
we
can
fully
support
everybody
pretty
much
so.
B
All
right
we're
two
minutes
over
mr
chair.
C
A
Point
of
order
cool,
well
yeah,
we're
we're
over
time,
so
I
guess
we'll
we'll
call
it
her
out
and
we
should
talk
more
about
this
stuff.
I
even
wonder
if
we
should
have
like
a
working
sessions
label
on
issues
and
then.
B
We
should
the
last
two.
Maybe
even
three
working
sessions
didn't
get
an
issue
created
because
I
was
on
vacation
or
just
back
from
vacation,
so
I
I
didn't
make
them
manually,
so
I
think
we
sh
we
should
that
does
help
raise
the
issue
for
people
to
remember,
to
attend
and
stuff
they're
also
on
the
public
calendar
for
those,
but
the
calendar
doesn't
necessarily
say
what
the
meeting
is
going
to
be
focused
on
that's
another
thing
I
can
do.
I
can
update
the
title.
A
Yeah
and
I'm
thinking
about
too,
like
our
agendas,
have
been
a
little
light
lately
for
the
cpc.
So
if
we
have
a
list
of
things
that
we
can
jump
into
once
we
get
through
the
agenda,
like
we've
been
doing,
that's
helpful
too
yep
agreed
cool
all
right.
Well,
thanks
to
native
script
for
joining
too
great
to
have
you
all.
A
Sure
cool
without
further
ado,
I
will
bid
you
adieu.