►
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
A
A
B
C
B
The
project
progression
document
was
approved
on
Friday,
so
that
landed
and
I
think
it
was
already
the
case
last
time,
but
just
in
case
the
there
were
no
concerns
with
the
code
of
conduct
or
sorry
with
the
travel
fund
so
that
actually
landed
there.
There
was
some
discussion
that
you
know
what
landing
that,
as
a
proposal
doesn't
mean
that
it's
fully
transferred.
So
there's
work
on
going
on
that
there
was
the
meeting
last
Friday
I'm
just
trying
to
think.
B
B
D
B
A
B
A
My
last
comments
mentions
that
we
discussed
it
last
week
and
in
terms
of
like
tooling
and
process
and
tracking
and
managing
onboarding
projects,
the
idea
was
to
create
a
public
and
a
private
repository
for
project,
onboarding,
public
or
well,
I,
guess
private
for
anything,
that's
in
the
silent
period
and
needs
to
remain
private
and
then
once
things
move
out
of
the
sound
period,
we
would
move
that
over
to
the
public
board
and
track
things
there.
I
actually
started
working
on
this
I
have
a
public
repo.
A
That's
in
New
York
that
some
projects
are
morning
is
the
repo
and
there's
not
much
there.
I
did
move
over
the
node
onboarding
issue,
just
to
kind
of
get
things
rolling
and
I
started
to
create
a
private
repo,
but
our
board
needs
to
be
upgraded
and
I
believe
that
Brian
has
already
made
the
request,
and
so
once
that's
sorted
out,
we
can
continue
moving
forward.
A
A
A
A
A
B
A
All
right
excellent,
so
we'll
wait
for
more
progress
there
and
discuss
it
here
there,
hopefully
next
week,
thanks
I'm,
not
sure
why
didn't
see
those
in
the
Google
Doc,
but
now
I
see
where
they
are
so
moving
on
to
the
next
issue
is
pull
requests
306.
This
is
at
impact
and
consumers
of
the
project
new
template
this.
This
has
actually
been
open
for
quite
some
time
and
I
think
it
would
be
good
to
land.
A
This
there's
been
some
discussion
and
some
updates
and
such
and
I
was
actually
a
meeting
with
jewelry
last
week
and
I
have
an
issue
open
that
I
hadn't
created
yet,
but
have
open
here
in
one
of
my
tabs.
That
specifically
asks
some
of
these
questions,
so
I
think
it
would
be
good
to
try
and
get
this
landed.
So
if
you
look
at
the
files
changed
here,
it's
basically
impacting
users
of
the
project.
What
is
the
ecosystem
impact
of
the
project
for
the
biggest
users
of
the
project?
A
What
is
the
potential
long-term
impact
of
adoption
and
how
does
it
differ
from
other
projects?
I
think
some
basic
questions
that
we
might
ask
of
a
project
looking
to
join
the
open
pass
foundation.
We've
got
a
few
approvals
already
on
here
and
some
some
comments
made,
but
not
necessarily
resolved.
Does
anybody
have
anything
that
they
want
to
share
here
or
discuss.
A
No
problem:
this
is
a
PR
306
from
August
20th.
This
is
adding
impact
on
consumers
of
the
project
in
an
application.
Template
I
think
he
had
a
couple
of
comments
in
here
miles,
but
I
think
that
some
bill
addressed
them
all
and
it
would
be
good
to
merge
this,
and
so
I
was
just
checking
in
with
folks,
and
you
know
no
need
to
process
this
all
on
the
spot.
I
guess.
G
A
G
A
A
So
you
know
so:
I
dropped
a
link
into
the
project
board
number
three
that
is
post
bootstrap
housekeeping
a
couple
of
things
in
the
in
progress.
The
admin
policy
doctor
that
mentioned
last
week.
I
have
some
of
this
work
already
done
and
I
just
need
to
finalize
it
and
get
a
PRN
basically
pulling
over
policy
docs
from
the
node
org
or
touring
to
transferring
the
repoint
of
the
open
base,
org
goetaborg
management
policy
and
requirements.
So
again,
I'll
try
to
get
that
done
soon.
A
Jori
posted
a
comment
last
week
about
issue
333
infrastructure
improvement.
Follow
up,
there's
been
a
query
meeting
as
well,
so
I
think
there's
work
going
on
here
and
we
will
leave
that
leave
that
issue
open
as
we
kind
of
continue
down
the
process
for
now,
then
we
have
the
waiting
on
the
board,
slash
foundation,
column
here,
I,
don't
know
if
there
are
any
updates
to
any
of
these
Brian
I
guess
I
would
ask
I.
H
H
So
last
week,
in
the
board
meeting,
we
gave
the
updates
that
we
have,
or
the
board
has
approved,
the
new
bylaws
and
membership
agreement,
as
well
as
the
new
IP
policy
and
the
trademark
list
and
the
trademark
policy.
So
we
should
hopefully
be
able
to
get
started
here
on
the
style
guide
and
pushing
a
pushing
an
artwork
repo
that
has
a
style
guide
as
well
as
guidance
on
specifically
how
to
use
the
trademarks
we
have
everything
we
need
for
that.
Just
basically
needs
time
to
do
it.
H
Project
directed
funding
did
come
up
as
a
as
a
topic
of
discussion
in
the
board
meeting
last
week.
We
are
planning
to
have
a
meeting
on
that
sometime
soon.
That's
really
about
all
that
I
can
say
on
it
right
now,
but
we
please
rest
assured
that
this
is
a
topic
which
the
board
is
taking.
You
know
it's
up
at
the
up
at
the
forefront
or
front
of
the
board's
consciousness
right
now,
right.
H
Good
point
CLA
bot
I,
had
discussed
this
last
week
with
the
board.
We
have
a
few
updates
that
needed
to
be
made
to
that
before.
If
you
go
out
for
go
out
for
approval,
it
should
be
going
up
for
a
little
here
soon,
once
the
CLA
is
approved,
actually
both
variances
the
CLA,
because
it
turns
out
for
the
tool
that
we're
using.
We
need
to
have
one
variant
for
individuals,
one
variant,
corporate
signers.
Once
we
have
that
taken
care
of
then
we'll
be
able
to
move
this
forward
as
well.
H
I
H
A
A
Livestream
but
anyway,
okay
great,
so
that
concludes
that
support.
You
know
we're
pretty
good
on
time
here,
27
minutes
after
the
we
were
to
kind
of
go
through
these
boards
really
quickly.
The
items
to
discuss
with
the
board
board
is
empty.
So
if
anybody
has
anything
that
that
needs
to
go
to
the
board
or
any
issues
that
also
need
to
go
there,
they
can
add
that
to
that
board
for
for
their
consideration,
yep.
A
A
A
The
first
one
well,
the
first
column
here
working
from
right
to
left
from
done
backwards
and
swimlanes
is
a
block
column
with
one
ticket
for
project
guidance
up
the
right
guidance
on
how
to
refer
to
the
foundation
and
licenses
/,
copyright
statements
and
I'm.
Looking
at
this,
this
is
July.
17Th
spent
some
conversation,
nothing
since
well.
August
27th
was
the
last
comment.
D
A
D
Ahead,
I
J's-
not
here
so
I
I,
had
talked
to
her
a
week
or
so
ago
on
the
one
of
the
items.
So
not
all
the
items
on
that
checklist
for
nvm
apply
to
nvm
and
so
Jory
was
gonna
annotate
them
about
like
since
I'm,
not
a
impact
project,
I
think
there's
a
few
things
that
aren't
required,
but
then
the
other
one
I
think
was
project
charter,
which
I
believe
she
implied
was
blocked
on
some
board
decision.
That
may
have
already
happened.
I
think.
B
D
Just
have
missed
that,
but
in
general
like
it
would
be
useful
and
I've,
given
this
feedback
to
Jory,
but
it
would
be
useful
to
have
those
checklists
have
more
links
to
instructions
and
actionable
steps
to
follow
for
project
maintainer
x'.
Since
it's
not
super
like,
like.
I
understand
all
the
words
of
each
of
the
checklist
items
to
check
them
on
yeah.
A
D
B
A
Excellent,
so
looking
back
at
the
board
here,
the
first
issue
in
the
to-do
column
is
266.
It
was
create
mock-ups
for
displaying
open,
Jazz
foundation
mark
on
project
websites,
I'm
scrolling
through
the
comments
here.
This
is
also
I
think
a
part
of
that
previous
issue
that
we
just
discussed
number
280,
which
is
Joy's
comment
on
August
27th
as
well.
A
I
I
A
A
A
A
D
It's
for
a
different
item
so
when
I
just
didn't
want
to
I
just
had
a
quick
question
in
relation
to
the
onboarding
stuff,
where
it
says
like
code
of
conduct
is
a
required
file,
should
I
just
duplicate
the
file,
it's
in
the
cross
project,
council,
repo
or
should
I
point
to
it
or
is
there?
Is
there
disabled.
B
I
I
Council,
repo,
which
starts
off
saying
the
open
J's
foundation
and
its
member
projects
used
to
contribute
a
covenant
2001
for
one,
as
its
code
of
conduct,
refer
to
data
for
the
full
text
and
then
there's
date
on
the
reporting,
and
my
understanding
is
that,
given
that
message,
format
is
not
considering
to
do
anything
really
special
about
the
reporting
for
the
the
other
things
there.
It
makes
absolutely
no
sense
for
us
to
have
a
file
code
of
conduct
that
it's
just
that
we
need
to
keep
in
track
track
with
this
right.
B
You
know
I,
think
I,
think
that
makes
sense.
The
only
thing
I
would
add
is
that
you
know
the
way
I
think
it's
written
is
that
it's
you
could
it's
intended
that,
like
each
project
would
have
its
own
reporting
like
first
step
so
that
you
know
what
you
had.
This
is
sounds
perfect,
maybe
with
the
addition
of
like
you
know,
if
you
want
to
report
an
issue
to
the
project,
here's
the
email
or
whatever
the
path
is
for
making
those
reports.
I
Yeah
you're,
actually
right,
I
need
to
update
our
thing,
and
this
actually
may
accept
two
for
issue
of
having
providing
mailing
lists,
because
people
message
for
my
we
didn't
have
one
except
for
private
email
addresses
and
their
reporting
on
the
code
of
conduct
for
the
projects
faces
for
reporting
issues,
interfaces
related
a
member
project.
Please
use
the
email
provided
by
the
project
for
reporting
rank.
D
D
Details
there,
as
well
as
the
github
actually
has
an
integration
for,
like
so
I,
looked
at
message,
formats,
repo
and
it's
a
section
of
the
readme,
but
they
actually
want
you
to
have
a
separate
code
of
conduct
markdown
file
and
then
they
can
like
they
have
like
metadata
that
detects.
If
you
have
a
code
of
conduct
and
tries
to
figure
out
what
kind
it
is
so
I
think
about
that,
and
then
for
nvm,
where
I'm
the
only
current
maintainer.
D
If
there
is
a
report
it
shouldn't
go
to
me
and
but
like
I
guess
it
is
a
report
about
other
people
on
the
project
like
that.
Are
you
know,
conduct
and
the
threads
sure,
but
github
has
mechanisms
for
that
as
well,
and
it's
actually
beta
testing
mechanisms
to
like
surface
reports
directly
to
rebuild,
maintain
errs
so
I'm,
just
kind
of
like
it's
not
super
important,
I'm,
just
kind
of
trying
to
figure
out.
What's
the
best
pattern,
one.
J
Thing
I
would
suggest
here
is
that
having
default
text
in
your
own
repo
is
the
ideal
Avenue,
mostly
because
it's
a
way
to
actually
have
like
a
path
to
true.
Like
say,
this
is
the
real
thing
that
we
care
about.
Instead
of
a
link
is
like
relatively
under
follow
this
thing:
we
don't
really
care
or
pay
attention
to
it,
but
it's
there.
D
J
Would
be
what
I
would
do
there
for
context?
There
is
also
the
I
mean
if
we're
following
the
contributor
covenant.
One
point
for
point:
one
I
believe
there
is
literally
the
coverage
and
mod
module
that
will
just
like
to
yeah
like
that'll.
Just
automatically
do
it.
If
you
put
in
you,
know
empty
X,
cub
gin
and
then
your
email
it'll
go
ahead
and
do
that
for
you
and
set
it
up
as
a.
D
B
Right
I
think
the
thing
I'd
add
to
that
is.
It
would
be
nice
if
you
know,
since,
since
we
said
one
of
the
requirements
is
adopting,
you
know
the
foundation,
one
which
is
a
choice.
It
would
be
good
if
there's
an
indication
that-
and
this
is
you
know,
a
direct
like
we
haven't
modified
anything
from
the
foundation
right,
cuz,
I
I
get
the
point
of
wanting
to
have
the
text
there,
but
also
I
think
it's
it's
better,
not
to
have
10
different
ones.
Unless
there's
you
know
a
reason.
J
B
B
I
B
J
J
B
B
J
B
J
B
B
D
When
I'm
using
the
I'm
using
the
github
template
right
now,
it
starts
out
at
one
point
for
not
one
point
for
one
I,
don't
know.
If
that
makes
a
difference
it
does.
There
is
actually
a
non-trivial
difference.
Okay,
so
I'm
trying
to
see
if
I
can
modify
the
links
tribute.
Maybe
I
can't,
but
the
link
for
one
point
for
at
least
there's
a
translation
sect
like
link
at
the
top
of
that
web
page
and
when
I
click
that
it
lists
a
very
large
number
of
languages.
But
it
still
says
version
1.4.
D
D
It
okay!
So
that's
the
same
so
yeah
it's
it
sounds
like
like
if
it
would
be
so
if
we
think
it's
a
good
idea
for
a
project
to
generally
speaking,
use
github
zoo,
I,
hear
add
in
your
reporting
a
custom
reporting,
email
address
and
then
maybe
add
a
chunk
at
the
top.
That
says,
like
also
see
here
for
the
overall
foundation
code
of
conduct,
like
that
seems
I.
D
B
A
That's
all
I
was
referring
to
was
saying.
Maybe
we
should
make
a
template.
Is
that
you
know
if
we're
template
izing
these
different
aspects
of
onboarding,
and
it
would
be
like
one
sort
of
process
or
a
new
project
like
okay,
I'll
get.
This
template
update
these
variables.
Okay,
and
now
this
one
blah
blah
blah.
B
D
So
basically,
I'm
gonna
follow
I'm
gonna,
try
and
like
make
a
branch
on
nvm
that
adds
in
all
the
you
know,
as
many
things
as
I
can
do
on
that
checklist
and
for
the
code
of
conduct.
I'll,
try
and
come
up
with
some
steps
and
I
guess:
I'll
try
and
come
up
with
some
instructions
to
then
put
in
the
CPC
repo
under
the
assumption
that
they're,
probably
gonna,
be
fine,
and
you
know
I
won't
have
to
make
any
further
changes
to
nvm
cool.
B
A
H
Hey
joke
before
we
do
that.
Yeah
I
have
an
answer
for
Emily,
so
Emily
with
the
with
the
CL,
a
tool
that
we're
going
to
be
using.
If
you
need
to
sign
this,
an
individual
and
also
sign
on
behalf
of
the
company
or
have
your
company
sign
on
behalf
of
you
essentially
you'd
use
to
github
accounts,
so
it'd
be
tied
back
to
the
account
and
then
that
will
allow
you
to
have
be
signed
both
ways.
If
you
need
to
be.