►
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
Grates
we
are
live
thanks.
Everyone
for
joining
this
week's
cross-project
Council
meeting
today
is
the
11th
of
February
thanks
everyone
for
joining
again
I'll
remind
folks
to
draw
up
their
github
handle
and
their
name
and
the
meeting
notes
there
is
the
dock
for
folks
to
easily
get
at
it
and,
as
usual,
please
help
us
by
maybe
taking
some
notes
and
welcome
to
a
couple
of
the
new
faces.
I
see
new
names,
I
see
a
call
here.
There's
another
person
on
the
github
issue
too.
That
mentioned
he
was
going
to
join.
A
A
So
the
we
have
a
collaborator
summit
meeting
immediately
after
this
call-
or
at
least
you
know
at
the
top
of
the
hour.
So
if
you
have
an
interest
in
helping
on
the
next
open
J
s
collaborative
summit
feel
free
to
join
that.
If
let
me
actually
check
while
we're
here
to
see
if
it
is
on
the
open,
J
s
calendar,
it
is
great.
So
if
you
go
to
calendar
open
j,
SS
org
you'll
see
the
meeting
at
1:00
p.m.
A
Eastern
Time
with
all
of
the
details
for
zoom
and
what
happened
or
what
have
you
so
please
feel
free
to
join
us
if
you're
interested
in
that
we
had
a
scheduled
meeting
for
after
that
2:00
p.m.
today,
Eastern
Time
for
the
open,
J's
Foundation
standards
team,
but
we
had
a
conversation
in
slack
and
most
of
the
regular
folks
who
the
folks
who
regularly
attend
couldn't
make
it.
So
we
decided
to
cancel
this
week's
meeting.
So
we'll
pick
things
up
in
two
weeks,
I
believe,
and
we
can
talk
more
about
standards
work
there.
A
There
are
a
few
things
that
are
in
flight.
That's
looking
forward
to
discussing
so
feel
free
to
join
us
then,
and
that,
let
me
just
take
a
quick
look
is
on
the
meeting
is
on
the
calendar
as
well.
So
in
two
weeks
the
standards
team
meeting
the
details
are
there,
let's
see
on
the
18th
which
I
don't
see
on
the
calendar
and
maybe
Rachel
or
someone
from
the
foundation
can
help
us
there.
But
I
was
alerted
that
there
is
a
PR
/
marketing
meeting
on
the
18th
of
February
at
11:30
a.m.
Eastern,
Time
yeah.
A
If
you
have
any
interest
in
that,
that's
please
feel
free
to
join
there.
That's
that's
a
good
place
to
get
involved
with
any
of
the
event
brilliant
stuff
for
content
or
what-have-you
lots
of
good
stuff
happening
there
and
then
one
more
meeting
announcements
is.
We
have
the
code
of
conduct.
Team
initial
meeting
is
happening
tomorrow
at
2:00
p.m.
Eastern
Time.
That's
the
12th
tomorrow
on
the
12th
of
February.
A
So
we'll
maybe
touch
on
this
briefly
in
the
agenda,
but
this
is
basically
a
team
that
is
not
the
moderation
team
per
se,
but
a
team
that's
working
to
further
flesh
out
what
a
code
of
conduct
would
look
like
at
the
open,
J's
foundation
level.
So
that
is
our
first
meeting
tomorrow
at
2:00
p.m.
Eastern,
Time,
so
I
think
that's
all
the
announcements
I
have
does.
Let
me
let
some
more
people
in
to
be
panelists
here.
B
A
quick
one
we
do
have
our
open
Jas
world
CFP
is
open
through
February
21st.
So
if
you
are
interested
in
submitting
a
talk,
please
do
so
and
in
addition,
if
you
see
any,
if
you
wouldn't
mind
giving
us
some
amplification,
so
any
sort
of
retweets
or
anything
like
that
on
social
media
to
get
the
word
out
with
the
CFP
is
open,
and
we
are
looking
forward
to
everybody's
wonderful
submissions
right.
A
You
yeah
perfect
Thank,
You,
Toby,
cool
and
then
also
I'll
just
say
a
you
know.
The
collab
summit
meeting
is
happening
after
this
meeting.
If
you
have
any
interest
whether
you
want
to
join
the
meeting
or
not,
there
is
a
summits,
repo
and
we'll
start
well.
We've
already
started
to
post
issues
there
around
sessions
and
ideas
and
starting
to
work
on
collaboration
between
projects
and
just
generally,
to
make
an
awesome
event.
So
you're
interested
check
that
out
as
well
cool
all
right
so
jumping
into
things.
A
I,
don't
think
we
have
anyone
from
the
board
here
and
I.
Don't
think
that
you
know
haven't
been
any
meetings
or
anything
so
we'll
skip
over
the
board
updates
a
bit
of
the
agenda
here
and
jump
into
actual
agenda
items,
so
the
first
one
on
the
list
is
issue
445.
This
is
the
meta
around
where
she'll
certain
resources
live.
We've
discussed
this
a
few
times.
I
actually
went
in
here
today,
because
Jory
had
a
pull
request
open,
which
is
pull
request.
A
Four
five:
six,
which
basically
just
creates
a
directory
in
the
cross
project
council
repository
as
a
place
that
we
will
have
different
resources.
So
such
as
the
infrastructure
menu,
the
member
travel
fund
and
the
open,
JSF
marketing
services
PDF
so
we'll
have
that
for
now
is
a
place
to
drop
in
any
sort
of
resources
for
projects
and
the
community
and
we'll
iterate
on.
You
know
if
that's
the
best
place
for
it
for
now
so
I
merge
that
PR
this
morning,
which
closes
that
issue.
A
A
A
We
have,
as
I
mentioned
and
as
Jory
commented
in
the
issue
a
couple
hours
ago,
that
we
have
a
meeting
scheduled
for
tomorrow,
so
I'm
gonna
leave
this
open
until
we
sort
of
get
the
ball
rolling
and
then
I
can
close
this
issue
probably
next
week.
Once
we
have
that
meeting
started
and
spun
out
also,
if
anybody
notices
anyone
join
as
an
attendee,
let
me
know,
and
either
myself
or
Rachel
I
think
maybe
can
promote
them
to
panelists,
not
always
watching
the
resume
app,
so
sometimes
I
miss
that
cool
next
up
is
the.
A
C
A
No
pressure
I
know
everybody's
got
some
crazy
schedules,
I'm
noticing
to
you
that
you
have
a
checklist
in
one
of
your
comments
here.
So
that's
helpful.
Thank
you
and
there's
a
bunch
of
things.
I
need
to
happen,
okay,
all
right
cool,
and
if
anybody
has
an
interest
in
this
and
wants
to
help
she'll
be
out,
you
know
let
us
know
and
might
be
a
good
place
to
get
involved
cool.
C
A
C
A
A
Cool
alright,
so
moving
on
the
next
issue
or
actually
pull
request
is
379.
This
is
the
move
Code
of
Conduct
proposal
to
stage
three
this
this
has
been
on
hold
for
a
while.
The
short
story
is
that
this
is
on
hold.
As
we
spin
up
a
code
of
conduct
team,
two
number
one
I
get
a
an
MVP
of
the
code
of
conduct
merged
in
and
then
iterate
on
that
for
further
context.
We
had
some
conversations
at
the
collaborator
summit
in
December
and
Montreal,
and
you
know
a
number
of
things
were
were
brought
up.
A
As
you
know,
questions
as
to
how
we
handle
code
of
conduct,
moderation,
where
we
have
a
foundation
and
projects-
and
you
know
there
were
a
number
of
things
that
were
discussed
there-
that
we
need
to
work
through
as
well.
But
the
initial
thing
we
need
to
get
done
is
an
MVP
of
the
code
of
conduct,
and
then
we
can
kind
of
go
from
there
and
that's
yeah,
so
so
I
don't
think
we
have
anything
really
to
add
on
that.
A
A
A
That
Marcin
has
has
done
some
great
work
on
the
node.js
package:
maintenance
team,
where
there
was
a
draft
security
guideline
in
place
there
and
has
also
started
to
capture
current
security
practices
for
the
open,
Jas
projects,
and
it
just
there's
that's
a
comment
on
on
the
issue
itself
and
then
Toby
as
well
has
started
the
conversation
in
the
amp
project.
So
I'll
turn
it
over
to
you
to.
If
you
want
to
share
a
little
bit
more.
D
Hi,
so
this
is
this-
is
this
is
marching
here
so
indeed,
what
we
plan
to
do
is
to
build
on
the
work
that
we
have
done
with
with
the
node.js
and
package
maintenance,
working
group
and
kind
of
recommend
some
baseline
practices
for
foundation
projects
when
it
comes
to
security,
reporting
and
and
publishing
security
security
policies.
So
we've
had
a
lot
of
good
discussion
on
the
original
document
in
the
node.js
space.
D
So
I
think
this
will
this
will
just
build
on
that
and
and
suggest
something
that
will
be,
that
would
be
actionable
pretty
easily
for
for
foundation
projects
as
if
I
think
a
couple
of
days
ago,
we
also
have
the
security
channel
on
the
foundation
slack.
So
if
you
want
to
discuss
this
I
think
that's
currently
the
best
place
the
best
place
to
do
it.
A
C
And
on
my
side,
amp,
my
understanding
is
that
amp
is
relying
on
a
hacker.
One
two
was
a
lot
of
its
security
issues
through
a
contract
that
Google
has
they're
a
close
hacker
hacker
one
and
well,
as
you
know,
as
the
project
moves
one
completes.
Onboarding
I
would
like
to
have
that
situation,
sort
of
clarified
and
I'm
right
now,
trying
to
figure
out
who
owns
that
contract
internally
at
Google
to
see.
C
D
Bug
bounty
program
were
a
vulnerability
disclosure
program.
If
you
will
on
hacker
one
and
in
practice
it
doesn't
normally
focus
on
nodejs
projects,
we
we
would
accept,
or
it
would
accept
submission
agains
pretty
much
any
JavaScript
project
at
this
point,
I
think
so,
potentially,
if
you
wanted
to
move
out
out
of
Google
hacker
one
project
to
somewhere-
and
it
was
not
like
certain
like-
where
would
we
move
to
with
amp
I
think
this?
This
is
one
of
the.
This
is
one
of
the
solutions
we
could
consider.
C
E
A
A
A
Moving
on
trying
to
get
back
to
my
dock
here,
great
excellent,
all
right
cool,
so
moving
on
the
next
item
in
the
agenda
is
issue.
185
has
been
around
for
a
long
time
where
this
is
add.
Admin
policy,
Doc's,
Ben,
Mitchell
and
I
are
working
on
this
I've
got
a
draft
PR
open
e
and
I
keep
threatening
to
actually
finish
it,
and
that
should
happen
sometime
soon.
C
A
A
A
A
I,
don't
think
Emily
is
on
this
call
as
well,
but
Chris
says.
An
hour
ago,
Chris
Porter's
mentions
per
discussion.
Last
week,
CPC
meeting
I
have
sent
a
message
to
the
board
asking
for
their
input
and
will
report
back
if
there
any
questions
or
guidance
on
how
to
proceed.
This
is
on
joining
the
Unicode
consortium,
as
Emily
has
requested.
I.