►
Description
The OpenJS Foundation is a member-supported non-profit organization that provides a neutral home for some of the most important project in the JavaScript ecosystem.
Learn more and join us at https://openjsf.org
A
We
have
an
earlier
time
this
week.
We're
gonna,
try
this
time
for
a
couple
of
weeks
and
see
how
it
goes.
It's
a
little
euro
friendly
time
switch
up.
Yeah
so
remember
to
add
yourself
to
the
meeting
notes
and
if
you
can
help
you
being,
everyone
can
help,
add
notes.
B
A
B
Yeah
we
have
the
standards
meeting
later
and
we
also
have
your
open
js
office
hours
meeting
on
thursday,
and
I
think
there's
also
plans
for
on
a
another
meeting
on
the
sponsor
supporter
group
planned
for,
I
think
in
the
next
week
I've
been
out
on
vacations.
I
don't
remember
anymore
and
then
I
meeting
toby
is
organizing
a
meeting
on
the
review
process
for
growth
projects.
B
B
Fun
things
to
blog
and
tweet
about
like
the
message,
format,
essay
or
piece
and
which
was
an
interview
with
emily.
It
was
awesome
and
our
ama
last
week
with
es
lent.
C
C
B
So
we
just
as
always
appreciate
y'all,
taking
a
look
and
sharing
with
your
friends
on
on
those
things.
So
that's
that's
it
that
I
can
remember
I'm
sorry,
I'm
still
fuzzy.
A
No,
no
welcome
back.
I
hope
that
you
had
some
nice
time
off.
The
openjs
project
review
process
is
this
afternoon:
it's
4
p.m,
eastern
time.
So,
if
anybody's
not
on
that
invite,
you
know
feel
free
to
reach
out
to
toby
or
me
or
or
whoever
would
work
it
out.
A
I
don't
see
the
supporter
program
meeting
in
my
calendar,
so
if
that
is
already
booked
sarah,
maybe
you
can
get
me
on
there,
but
otherwise,
if
it's
not,
then
we'll
work
it
out
later.
D
I
have
one
thing:
we
are
on
a
little
bit
of
a
membership
drive
and
we've
been
emailing
folks
who
have
opted
into
our
list.
So
if
you
see
new
people
joining
our
slack
channel,
welcome
I've
been
having
lots
of
nice
emails
with
lots
of
folks
from
around
the
world,
and
so
I
do
see
that
they're
joining
our
slack
channel
and
I'm
having
some
calls
this
week.
So
welcome
for
new
people
who
happen
to
watch
later.
A
Yeah
great,
thank
you
cool,
let's
see
so
I
don't
know
if
I
should
have
asked
this
before,
but
do
we
have
any
private
business
that
we
should
set
aside
time
for
later
the
end
of
the
meeting.
A
That
that
I'm
aware
of
okay,
great
I
don't
I'm
not
aware
of
anything
either,
so
we
can
jump
right
into
the
into
the
agenda.
The
first
item
is
6
30.
This
is
approving
project
charters
in
is
clunky,
and
issues
created
this
issue.
How
long
ago,
a
couple
weeks
ago,
what's
my
last
comment
here?
Oh
yeah!
Oh,
that's
right!
Okay,
so
I
guess
we
discussed
this
in
last
meeting.
So
maybe
I
should
take
the
agenda
item
off
of
this.
A
But
basically,
if
someone
wants
to
make
a
pull
request
and
convert
the
list
of
projects
in
the
cross
project
council
repo
into
a
table,
that
would
be
awesome.
The
idea
is:
maybe
we
could
include
a
little
bit
of
the
you
know:
put
a
logo
in
there:
a
link
to
the
project,
repo,
a
link
to
the
charter
and
a
link
to
a
coc
code
of
conduct
and
maybe
a
link
to
a
contributing
doc.
A
Pr,
the
charter
in
as
a
project
moves
to
out
of
incubation,
so
I
guess
there's
not
much
to
talk
about
here.
I
pulled
the
the
agenda
label
off
of
there.
Does
anybody
have
any
thoughts
or
anything
they
want
to
discuss
here?.
A
And
I
won't
put
anyone
on
the
spot,
but
if
you
really
like
building
tables
and
markdown,
please
jump
on
top
of
this
one.
That
would
be
great.
It's
really
fun.
Next
up,
if
I
am
moving
on
is,
should
we
share
voting,
result
details?
If
so,
how?
I
think
we
talked
about
this
a
bunch
last
time,
toby
captured
the
decision.
A
We
should
document
this
and
I
will
remove
the
agenda
label.
Does
anybody
have
anything
more?
They
want
to
talk
about
this
anything
they
want
to
add
to
this
sorry,
I
guess
I
should
go
through
and
take
labels
off
before
the
meeting
is
created
because
I
think
a
couple
of
these.
B
I
guess
the
one
question
I
would
have
on
this
one
is,
and
since
we
decided
that
some
generic
info
share
about,
for
example,
there
were
15
eligible
voters
and
x,
many
voted
is
that
some
place
you
in
the
in
the
future
we
want.
Do
we
want
to
report
that
back
on
the
issue
when
we
close
it
on
the
election
issue,
or
do
we
want
to
save
that
somewhere
else.
A
That's
a
good
question.
My
thought
was
in
the
issue
is
fine
but
but
but
for
like
data
purposes,
I
don't
know
if
we
should
keep
track
somewhere.
I
mean
I
guess.
If
we
continue
to
use
the
same
tool,
we
would
have
access
to
that
that
data
moving
forward
that
sound
right.
B
A
Yeah,
I
don't
see
any
reason
to
you
know,
create
a
new
place
to
save
stuff.
Like
that,
I
think.
As
long
as
the
staff
has
it,
we
can
go
back
to
it.
It
sounds
good
to
me.
A
Great
welcome
michael
cool,
so
so
next
item
on
the
agenda
is
six
one.
Eight.
This
is
a
pull
request
for
adding
ip
policy
guidance.
This
has
been
around
for
a
little
bit.
I'm
scrolling
to
the
bottom.
Is
there
so
toby's
updated
it
five
days
ago
and
we've
got
a
bunch
of
approvals.
A
I
think
the
last
time
we
talked
about
this,
we
were
hoping
to
get
anton
and
chris
hiller
to
give
their
approval
as
they
have
engaged
in
the
issue,
but
haven't
explicitly
given
approval,
so
I
will
maybe
just
ping
toby
anton
and
chris
and
see
if
we
can
get
this
one
wrapped
up.
A
Next
item
on
the
agenda
is
issue
607,
the
next
steps
for
the
supporter
program.
There
is
a
pr
which
is
6
25
that
is
open,
open
19
days
ago.
Sarah,
I
think
I
saw
you
on
the
call.
Do
you
want
to
chime
in
here?
A
No
well
how
about
we
can
come
back
to
this
one.
If
you
want
to
see
you
know,
troubleshoot
your
audio.
That
would
be
great.
I
know
that
there's
movement
on
this,
so
we
can.
We
can
come
back
to
this
sorry,
sarah,
so
jumping
ahead
for
a
moment.
A
C
Yes,
but
we
can
come
back
to
it.
C
It
works
okay,
so
I
think
that
pr
is
ready
to
be
merged.
Last
time
I
took
a
look
so
I'll
take
a
look
today
and
as
long
as
there's
no
other
feedback.
Okay,
if
I
merge,
I
don't
know
our
policy
on
merging
our
own
pr's.
Is
that
how
we
do
it
or
should
I
wait
for
someone
else
to
do
it.
C
Okay,
great
the
supporter
program
meeting
the
next
meeting
is
this
friday:
the
11th
at
4
00
p.m
est.
C
A
C
Yes,
I
just
sent
out
a
invitation.
Okay,.
A
Excellent
cool
cool
well
looking
forward
to
it
and
I
don't
see
an
invite.
So
if
you
can
just
I
can
message,
you.
A
Great,
thank
you.
Thank
you,
cool
excellent.
So
next,
up
on
the
agenda
is
issue
592.
This
is
the
annual
review
for
projects.
A
I
don't
think
that
chris
or
toby
are
on,
but
I'm
not
sure,
there's
much
to
talk
about
here.
Yet
we
have
the
meeting
this
afternoon
and
if
you
are
not
on
that
meeting
but
want
to
be
on
it
feel
free
to
message
me
or
toby
or
chris
we'll
work
it
out.
Chris
hiller
that
is
so
yeah,
hopefully
there's
there's
more
progress
there.
I
think
I'm
looking
forward
to
that.
A
So
next
on
the
agenda
is
the
issue.
583
updated
the
cla
to
the
apache
style,
cla,
icla
and
ccla
toby
has
an
issue
open,
6
632.
He
opened
this
up
a
week
ago.
A
Brian,
do
you
have
any
context
on
this?
Let's
see
miles.
E
Interview
yeah
this
one's
still,
it
requires
some
work
on
my
end
here
and
you
need
to
put
together
the
guidance
on,
and
this
is,
I
think
this
is
related
to
the
ip
policy
or
sorry
to
the
copyright
guidance
as
well
or
so.
No
I'm
sorry.
Let
me
back
up
ip
policy
guidance
put
together
the
guns
on
tooling
and
things
like
that,
and
then
also
some
considerations
on
dco,
which
is
also
linked
to
this
issue.
A
Yeah
yeah
all
right
cool.
Thank
you,
brian
yeah.
I
think
I
promoted
a
geary
okay,
great
excellent.
So
next
up
is
the
governance
changes
for
collaboration
network
for
quest
547.
You
got
anything
here,
michael.
F
A
Would
that
have
been
in
the
the
document
here?
Michael.
A
Where
would
that
commit
be,
would
it
be
in
in
amidst
your
changes
or.
F
A
F
F
F
E
I'm
not
sure
that
we
typically
go
into
that
level
of
detail
on
something
like
this.
Just
there,
our
maybe
really
for
two
reasons,
one
of
them
being
that
it's
getting
into
the
realm
of
license
interpretation
and
we
tend
to
try
to
leave
a
fairly
wide
lane
around
that.
E
But
the
second
reason
is
really
that
you
know
this.
The
again
getting
back
to
the
reason
for
doing
this
in
the
first
place
was
that
it's
just
a
matter
of
setting
a
default
versus
attempting
to
try
and
steer
people.
G
G
F
E
Okay,
yeah,
that
that
makes
sense.
Let
me
figure
out
something
here
and
make
sure
that
it's
good
to
go,
and
I
don't
like
it.
That's
yeah.
We
can.
A
F
A
Great
cool,
that's
awesome,
okay!
So
moving
on
the
last
one
on
the
list
is
responsible
security.
Disclosures
michael
sorry,
marcin
messaged
me
this
morning.
I
think
maybe
did
he
message
you
to
michael.
I
saw
you
had
some
notes
in
there.
F
It
has
a
few
a
few
approvals,
so
I
think
it
can
progress,
but
looking
at
our
at
our
rules
for
landing,
I'm
not
sure,
but
it
might
change
our
governance
through
some
of
the
files
being
changed.
So
we
should
probably
just
wait
another
seven
days
and
then
it
can
land
yep.
A
Sounds
good
to
me
cool.
So
that
concludes
our
agenda,
which
is
perhaps
a
record
time.
I
wanted
to
just
call
attention
to
a
couple
of
recent
issues.
One
of
them
we
on
the
call
are
all
aware
of
is
that
we're
trialing
this
new
time?
If
you
know
anyone,
that's
you
know
over
in
the
eu
or
anywhere
kind
of
that
this
time
would
be
more
friendly.
To
that
might
be
interested,
maybe
make
your
your
friends
aware
we
can
get
more
faces
and
and
voices
at
the
table
would
be
great.
A
So
that's
issue
634,
we'll
do
it.
We
did
it
today
and
we'll
do
it
again
in
two
weeks.
I
think
the
plan
is
to
do
two
of
them
and
see
how
that
you
know
what
what
it
looked
like
and
or
re-evaluate
after
that,
and
then
the
other
one
I
wanted
to
call
out
to
is
miles
opened
an
issue
six
days
ago
about
the
proposal
process.
A
There
are
several
thumbs
on
this
issue,
but
not
any
comments
I
mean,
I
think
what
miles
is
raising
here
is
is
simplifying
the
I
guess
the
title
simplifying
the
proposal
process
and
some
of
the
suggestions
here
are
good.
So
if
anybody
you
just.
F
A
The
link
in
yeah
sure
sorry,
this
is
issue
635.
I
will
drop
it
in
the
chat.
If
I
can
yep
or
actually
darcy
did
I
pasted
it,
but
I'm
having
trouble
with
the
chat
today.
Oh
no,
we
just
did
it
at
the
same
time.
I
see
it.
A
And
so
yeah,
I
think,
especially
folks
who
have
been
working
through
the
proposal
process
lately.
It
would
be
great
to
have
your
input
on
this.
I'm
thinking
about
the
collaboration
network,
the
supporter
program,
the
security
work.
You
know
any
of
these
things
that
have
gone
through
the
process
recently
it'd
be
great
to
have
some
perspective
and
some
experience
as
to
how
opinions
as
to
how
we
could
simplify
this
and
make
it
easier
and
less
burdensome.
A
So
please
take
a
look
just
peeking
quickly
at
the
prs
it
looks
like
you
know,
this
is
everything's
looking
good
there.
I
encourage
folks
to
take
a
look
at
the
security
reporting
if
you
haven't
yet
I
think
it's
pretty
minor
changes
in
terms
of
moving
it
to
the
last
stage.
So
please
take
a
look
and
and.
F
A
Perfect
yeah,
so
that's
a
quick
review.
If
any
of
you
have
a
moment
beyond
that,
I
think
you
know
I
don't
have
anything
else
to
bring
the
table.
Does
anybody
else
have
anything
they
want
to
discuss
before
we
call
it
around.
A
If
not,
I
hope
to
see
you
in
some
of
these
offshoot
meetings
happening
this
week
and
see
you
in
github
and
we'll
call
it
a
wrap
thanks.
Everybody
cheers
talk
to
you
soon,.