►
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
B
Great
yeah,
I
put
a
comment
on
it
this
morning.
I
think
it's
the
first
issue
on
the
agenda
and
we
are
live
now
so
welcome
everyone
and
thanks
everybody
for
joining.
I
know
the
time
is
a
little
tough
for
some
of
us,
but
but
yeah.
B
So
I'm
also,
I
may
be
a
little
slow
because
I
just
woke
up.
Everybody
add
yourselves
to
the
minutes,
which
I
can
add
to
the
chat
again.
Do
we
have
any
announcements?
Let
me
let
sarah
in
the
announcements
at
all
this
week.
B
I
mean
the
one
that
we
have
is
that
the
election
is
open,
but
I
think
maybe
there's
an
issue
for
that,
so
we'll
get
to
that
all
right.
Let
me
double
check
yep
anything
else.
Anything
going
on
this
week
is
the
board
meeting
public
session
later
this
week.
Yeah
right
that
happening
on
friday.
C
We
have
a
board
meeting
on
friday.
We
also
have
a
marketing
meeting
later
today.
Is
that
right,
rachel.
D
Meeting
today
at
noon,
pacific
and
that's
3
p.m.
Eastern.
E
I
guess
the
in
terms
of
the
the
collaboration
network
there's
some
discussion
about
the
suggestion
of
a
default
license.
That's
probably
going
to
hold
that
up
a
bit,
but
I
think
those
are
the
two
things
that
we're
on
the
take
to
the
board
list.
B
B
There
are
some
links
that
mateo
has
in
the
description
to
see
the
onboarding
checklist
and
the
fastby
charter.
Emily
pointed
out
a
couple
of
questions
about
making
decisions,
but
you
know
otherwise
it's
a
it's
a
short
charter.
It
can
be
easily
reviewed.
Folks
could
take
a
look
at
it
and
add
their
thoughts.
That'd
be
great,
like
mateo,
said
they're
hoping
to
wrap
this
up
soon.
B
No
cool
next
up
is
the
nominations:
have
been
closed
for
the
community
board
seat
for
the
openjs
foundation
board
of
directors.
This
is
issue.
616.
jory
has
a
great
description
here
with
lots
of
details.
We
have
a
few
people
who
excuse
me
who
self-nominated
james
snell,
michael
dawson,
dylan
simon.
I
don't
know
if
I've
ever
said.
Your
last
name
dylan.
Is
that
how
you
say
it
yeah,
this
german
german.
You
say.
B
Vowel
yeah,
okay,
yeah
and
toby
and
sarah
and
so
that's
closed
and
the
the
you
know,
election
email
from
opavote
went
out
yesterday
and
that
goes
to
voting
members
as
we
had
decided,
and
so
that
is
in
process.
So
that's
great.
B
B
So
you
didn't
get
that
one,
oh
okay,
so
I
think
the
decision
was
that
it
would
be
voting
members
who
would
vote
partially.
The
the
okay
so
was
there.
Was
that
a
question
or
sorry
a
five
minutes?
It
was
a
statement.
F
B
Got
it
so
is
that
you
requesting
feedback
from
folks
for
your
vote
is
that
that
what
you're
saying
effectively
yes,
great
great,
fantastic,
all
right
well,
thank
you.
C
B
Yeah,
you
know
cool,
so
yeah,
that's
going
any
anything
else
on
that
that
we
want
to
talk
about
or
anything
no
cool.
Next
steps
for
supporter
program
issue
607
is
up
next
sarah
led
a
meeting
last
week
that
I
think
went
well.
So
sarah
do
you
want
to
give
us
an
update
here.
G
Yeah
we
had
a
meeting
last
friday,
I'm
compiling
our
notes
into
a
pull
request,
some
exciting
suggestions,
just
moving
things
forward
and
adding
some
more
details,
so
stay
tuned
sometime
this
week.
B
Great,
so
we'll
look
for
an
update
later
this
week
or
talk
about
more
next
week
or
something.
B
Excellent
great
great
cool,
any
questions
or
anything
anybody
talk
about.
I
mean,
I
guess
we'll
talk
about
it
when
the
pr
lands
or
everybody's
good
cool
next
up
is
develop
annual
review
process
for
projects
emily
open
this
up
mid
july.
We've
had
some
conversation
here
was
it
that
toby
and
chris
were
going
to,
I
think,
take
the
lead
on
drafting
some
stuff
around
non-impact
projects.
I
can't
remember
where
I'm
trying
to
catch
up
on
the
I.
F
B
I
think
they're
both
working
right
yeah,
I
think
so
krista's
last
comment
is
says,
he's
going
to
split
this
into
multiple
issues,
but
I
think
I
think
I
even
saw
in
slack
chris
asking
toby.
You
know
how
they're
going
to
split
it
up.
I
think
they're
both
working
on
it,
so
we
will
catch
up
with
them
soon.
I
I'm
excited
about
this,
so
hopefully
we
you
know
we
make
some
progress
here,
have
a
meeting
whatever
we
need
to
do
and
start
to
have
this
take
shape.
B
I
think
the
whole
360
review
thing
would
be
really
healthy,
so
I
look
forward
to
that
anything
else.
You
want
to
talk
about
on
that.
One.
B
We're
really
blowing
through
this
agenda,
which
is
pretty
great
where
so
next
up
is
doc.
Governance
change
for
collaboration
network.
Did
I
see
michael,
you
started
to
type
something
there.
E
Yeah
there's
some
discussion,
so
the
the
last
thing
was
around
like
when
we
took
it
to
the
board
in
the
first
place.
The
suggestion
was
that
we
asked
the
foundation
legal
and
get
a
suggested
default
license
which
bry
did,
but
it
seems
like
there's
some
some
disagreement
of
whether
that
makes
sense
or
not.
They
recommended
apache
too,
and
I
guess
there's
some
suggestions
that
default
for
most
open
source
projects
today
is
mit,
so
that
discussion
for
javascript
right.
F
F
F
E
H
I
mean
I
added
my
commentary
to
the
ticket,
which
is
sort
of
my
perspective
on
why
people
choose
mit
over
bsd
or
apache.
Mostly,
it's
people
don't
like
to
read
and
it's
longer
I'm
serious
like
it
used
to
be,
like
you
had
to
embed
the
copyright
notice
on
top
of
every
file
and
the
apache.
One
was
like
two
pages
of
text
and
mit
was
like
a
paragraph,
and
so
you
could
fit
at
the
top
of
a
file
more
easily.
I
Yeah-
I
guess
I
I
have
not
haven't
had
time
this
last
week
to
see
this.
I
will.
I
will
take
a
look
at
this,
but
my
initial
guess
is
that
I
I
would,
if
we're
suggesting
apache
I
would,
I
would
recommend
mit
just
because
that
is
what
literally
the
majority
of
the
ecosystem
has
done,
and
I
think
it's
strange
for
us
to
break
the
pattern
that
our
the
ecosystem
we
exist
in
and
like
is
our
namesake
represent,
has
taken.
F
I
I
don't
think
that
mit
is
generally
used
more
than
apache
too
in
sufficient
reason.
Yeah,
I
don't
know,
I
don't
disagree,
it
is,
it
absolutely
is
most
of
the
stuff
I
do
I
I
do
mit
or
isc,
which
is
effectively
the
same,
and
but
if
there's
actual
good
reason
for
us
to
recommend
apache
2,
then
I
think
it's
entirely
valid
for
us
as
as
a
foundation
for
because
the
projects
within
the
foundation
are
legally
in
a
different
position
than
many
other
projects
are
to
recommend
a
different
default.
I
Yeah,
I
I
think
well
so
I
mean
I,
I
think
that
a
lot
of
the
goal,
though,
with
our
prod
or
our
foundation,
is
like
we,
we
want
to
be
a
neutral
home
for
javascript,
which
then
kind
of
pushes
toward
well
like
large
projects
that
are
owned
by
corporations
would
generally
end
up,
like.
I
think
our
goal
as
a
foundation
is
to
get
them
into
us
into
our
project
or
our
foundation,
and
I
mean
those
are
all
licensed
mit.
I
E
So
it's
not
saying
it's
not
adding
any
more
guidance
to
like
the
ip
policy
or
anything
like
that
right.
It's
simply
saying
for
the
collaboration
network,
where
you
know,
if
we're
going
to
start
from
fresh
in
in
many
cases,
you
know
if,
if
there
isn't
a
preference
for
some
other
license,
this
is
the
one
that
I
guess
from
the
legal
perspective
is
the
strongest.
I
H
Preferred
for
things
where
you
have
different
companies
collaborating
because
it
does
spell
out
patent
issues
and
there
are
companies
that
kind
of
default
to
it
so,
like
I
know,
like
microsoft,
defaults
to
it
when
they
open
source
things
like
typescript
or
babylon,
or
other
things
like
that,
and
google
has
expressed
a
preference
for
it
for
stuff
they
contribute
to.
H
So
I
think,
like
when
you're
looking
at
a
license
for
hey
we're,
creating
a
collaboration
group
with
a
bunch
of
different
people
coming
together,
it's
nice
to
have
that
spelled
out,
but
I
don't
think
it's
a
strong
enough
reason
like
we're,
not
saying
hey.
Every
project
that
joins
the
foundation
should
be
you
know,
apache
or
whatever.
I
E
The
the
suggestion
just
was
like
there
is
a
preference
for
this
and,
as
emily
says
like
when
you
know,
companies,
especially
if
they
come
together
to
collaborate
on
things,
apache
is
and
from
our
legal
advice.
Apache
is
the
one
that
would
be
preferred,
but
it
doesn't
say
you
can't
use
anything
else
either.
I
F
As
I've
understood,
the
situation
fundamentally
using
apache
makes
it
significantly
more
difficult
for
any
of
the
participants
in
any
of
the
code
around
a
a
project
that
that
way,
it
depends
on
the
license
to
be
able
to
weaponize
any
of
the
ip
that
they
might
own.
That
is
somehow
associated
with
that
project,
or
that
could
be
weaponized
to
hinder
later
developments
or
changes.
H
F
F
I
would
argue
that
if
we
do
have
a
a
reason
to
prefer
apache
2,
I
would
be
surprised
if
the
scope
of
that
preference
would
really
only
extend
to
the
collaboration
network
and
therefore
it
might
make
sense
to
actually
include
this
preference
in
the
ipr
policy
document,
where
we
basically
state
the
case
that
if
you
are
deciding
between
these
and
you
have
no
further,
no
no
other
reasons
to
pick.
One
pick
apache
two,
because
these
reasons
or
something
like
that.
F
E
That
that's,
that
would
be
the
reason,
maybe
is
that
do
we
want
to
get
into
the
like
in
this
case,
if
it's
it's
more
likely
to
be
new,
I
think
new
content
versus
like
it's
certainly
not
projects
bringing
their
existing
project
in
which
already
probably
has
its
own
licenses.
B
Interesting
all
right:
well,
should
we
should
we
get
some
of
this
thought
documented
in
the
issue
or
pr
and
and
then
we
can
have
a
just
discuss
it
further
later
or
what
do
we
want
to
do.
J
A
run
at
that
sure
sounds
good
great,
just
adding
I
I
think
the
the
trick
here
is
just
to
add
just
enough
so
that
it
provides
some
context
without
getting
too
prescriptive.
So
we
don't
get
into
the
point
where
we
say
well,
you
can
choose
any,
but
here's
like
11
reasons
why
you
should
choose
one
over
the
other.
You
know
we're
trying
to
avoid
that
so
yeah
I'll
try
to
keep
it
tourist
and
if
it
ends
up
being
continues
to
be
two
terse,
then
we
can
certainly
add
more
around
it.
B
E
J
J
E
B
We
was
that
all
around
the
governance
changes
for
collaboration
network
is
that
what
we're
talking
about,
because
next
up
is
the
foundation-wide
copyright
guidance,
which
is
pull
request,
414,
which
is
completely
translated
into
pull
request
618,
which
is
toby's
stab
at,
I
think,
did
he
call
it
a
simpler,
taking
the
the
comments
from
that
pull
request
and
pulling
it
into
a
new
pr
toby's,
not
on
the
call,
but
I
I
think
brian
you've
got
a
lot
of
comments
in
here.
Do
you
want
to
kind
of?
J
Yeah,
so
I
had
written
the
first
one
and
then
toby
had
had
crunched
it
down
a
bit
to
make
it
a
bit
more
consumable.
J
There
are
a
couple
of
places
where
we
are
still
trying
to
figure
out
what
the
you
know.
What
the
right
level
of
guidance
would
be.
One
of
those
areas
is
around
adopting
the
dco
versus
a
cla
for
inbound
code,
and
basically,
at
this
point
I
think
I
think
we
have
about
it.
We
have
it
to
the
point
where
it's
about
as
minimal
as
we
would
want
it.
J
It
seems
that
there
are
some
other
things
which
do
need
to
get
broken
out
into
some
more
general
guidance,
and
one
of
those
items
would
be
effectively
if
your
project
wants
to
use
the
dco.
What
do
you
actually
need
to
do
in
order
to
do
it?
We
have
fairly
concise
guidance
on
how
to
adopt
the
cla,
which
is
basically
somebody
reaches
out
to
me.
We
get
the
assuming
they're
using
one
of
the
pre-approved
cla
texts.
We
get
them
loaded
into
the
tool
and
then
that's
it.
J
Dco
is
very
simple
to
adopt.
It's
meant
to
be
very
lightweight
process,
but
I
I
guess
from
various
discussions
I
it
sounds
like.
Maybe
there's
not
a
a
high
level
of
comfort
with
what
exactly
is
required
and
that's
something
we
can
definitely
fix
and
that's
pretty
much
where
that
is
right.
Now
great.
B
There
are
comments
on
the
issue
here,
but
you
know
I
I
encourage
folks
to
take
a
look.
If
you
haven't.
Does
anybody
have
any
comments
or
questions
here
in
the
meeting.
K
Sorry
for
my
background
noise,
so
the
the
discussion
about
changing
overall,
the
cla
text
to
an
entirely
different
one.
That's
a
separate
issue
from
this.
J
F
Sure
I
mean
at
least
in
my
case
it's
hard
for
message-
format
which
we're
still
using
the
js
foundation
cla
to
switch
now
to
something
which
we
might
end
up
needing
to
switch
to
something
else
very
soon
afterwards.
F
So
it's
all
a
little
bit
tight
together,
because
I
I
it's
hard
for
me
as
a
maintainer.
L
B
B
J
I
would
definitely
not
at
this
point,
recommended
anybody
go
to
the
current
one
that
we
have
simply
because
of
the
reasons
that
you
mentioned
there
I
mean
switching
to
apache
is
the
best
move,
long
term
and
it's
most
likely
to
be
stable,
so
I'd
say
maybe
put
that
on
ice
just
for
a
little
bit
longer.
J
Yeah
so
I
mean
it
was:
it
was
stabilized
for
about
a
year
until
we
decided
to
take
a
look
at
the
it's
switching
over
from
the
custom
one
to
the
to
the
apache
one.
So
I
I
really.
J
I
think
I
need
to
go
back
and
see
where
we
are
in
terms
of
getting
feedback,
but
really
the
board
deferred
voting
on
it
until
they'd
heard
kind
of
all
the
different
perspectives
here,
including
you
know,
from
the
cpc,
if
the
cpc
is
generally
ready
to
say
to
the
board
yeah
we're
good
with
this
apache
style
text.
You
know
this
seems
workable
or
maybe
it
seems
more
workable
than
the
previous
text.
E
Yeah,
I'm
trying
to
remember
I
I
think
jory
had
sent,
you
know,
requests
for
feedback
to
the
projects
and
I'm
just
not
100
sure
it
was
this
topic,
but
I'm
thinking
it
might
have
been.
M
E
I
think
the
the
separate
issue
of
you
know
do
you
need
to
offer
both
the
cc
corporate
cla
and
the
individual
cla.
That's
that's
the
discussion
that
was
continuing
and
we
met
with
toby
chris
and
I
did
the
other
day
to
better
understand
and
we
can
sort
of
discuss
that
in
the
upcoming
board
meeting.
F
K
F
C
F
J
J
And
see
what
it
would
take
to
update
that,
I
know
we
certainly
can
do
custom
text
in
the
tool.
That's
not
that's
not
really
an
issue,
and
I
I
the
reason
I
don't
want
to
say
yeah,
let's
go
ahead
and
do
this
I'd
like
to
just
double
check
it
with
legal,
make
sure
we're
not
changing
any
meanings
inadvertently
or
if
we
need
any
additional
definitions
or
something
like
that.
I'd
like
for
them
to
weigh
in
on
that
it.
B
So
let
me
ask
because
we're
almost
done
with
our
agenda
and
would
be
wrapping
up
soon.
What
what?
What
should
we
should?
I,
first
of
all,
should
I
put
the
label
back
on
this
particular
issue.
The
updating?
B
C
Cool
can
I
just
flag
one
thing
on
that
issue:
brian
created
an
easy
way
for
you
all
to
add
a
footer
to
your
project,
and
I
think
we've
noticed
in
doing
an
inventory
of
projects
that,
during
the
merger
and
some
of
the
bootstrapping,
that
not
all
projects
have
adopted
the
openjs
foundation.
Footer
so
really
encourage
you
all
to
check
out
your
projects
and
if
you
see
others
flag
for
us,
we'll
get
that
get
that
sorted
out.
C
B
Cool
all
right,
so
moving
on
the
last
issue
and
final
issue,
I
guess
that's
the
same
thing
is
responsible
security,
disclosures,
which
I
know
martin
has
a
pr
open.
I
think
the
last
thing
is
he
was
gonna
update
with
some
comments,
I'm
assuming
he
hasn't
had
a
chance
to
yet
do
you
have
any
update?
B
Michael?
I
don't
have
any
update.
No
sorry,
no
worries.
This
is
the
pull
request
that
marcion
has
open.
This
is
moving
security
reporting
to
stage
three
there's
a
few
comments
in
there
that
martin
said
that
they
would
work
on
so
maybe
we'll
ping
them
in
slack
and
see.
If
there's
any
movement
here
or
what
we
should
do
to
wrap
this
one
up,
I
think
relatedly.
There
was
a
twitter
question
as
well
that
chris
hiller
mentioned,
I
think
rich
trot
was
had
brought
up.
B
Anyway,
all
right
cool,
so
that's
that's
it
for
the
agenda.
Does
anybody
have
anything
else
that
they
want
to
discuss
we've
37
minutes
after
so
we
got
a
little
bit
of
time.
B
Yeah,
that's
a
good,
that's
a
good
point
in
my
thought
about
this.
First
of
all,
I
I
don't,
I
feel
a
little
guilty
about
this.
I
don't
think
it
was
promoted
extensively
or
and
and
maybe
even
like
doing
it.
A
few
times
would
wouldn't
end
a
in
and
of
itself
kind
of
spread.
Some
awareness.
B
B
C
Agreed
personally,
reaching
out
to
folks
and
time
zones
might
be
the
way
to
go.
We
do
have
a
pretty
broad
reach
on
twitter,
but
if
you
missed
it,
you
know,
or
the
slack.
B
Channel
yeah,
it
seems
to
me,
like
it,
wouldn't
be
bad
to
do
this
for
a
few
sessions
and
then
kind
of
judge.
If
it's,
if
it's
helpful
or
hurtful
or
or
maybe
we
think
the
times
overall
and
if
we
did
do
that,
I
think
you
know
alternating
maybe
with
the
2pm
slot
is,
is
good.
But
I'm
you
know
I'm
open
to
whatever.
M
But
didn't
we
also
have
one
more
time
slot
that
we
were
going
to
try
out
an
alternative
times.
Remember
we
had
three
and
after
out
of
that,
we
said
we
were
going
to
do
two
of
them.
B
Well,
we
were
doing
the
other
two,
the
noon
and
2
p.m.
Eastern
time,
sorry
to
be
eastern
centric,
but
I
think
if
we
were
to
try
the
9
a.m
time
again,
eastern
that's
trying
to
rotate
between
the
three
might
be
too
challenging.
So
maybe
just
my
thought
was
the
extreme,
not
not
extremes
in
a
bad
way,
but,
like
you
know,
early
and
afternoon,
for
for
me,
might
be
the
most
the
widest
spread
of
time
to
to
to
get
a
wide
variety
of
people
able
to
join.
E
B
H
B
Yeah
makes
sense:
what
do
you
think
robin?
I
saw
you
unbeaten.
C
Yeah
but
I
don't
mind
and
if
it
you
know
again,
I'd
like
to
make
it
easier
for
other
folks
as
well,
so
I
wondered.
B
B
I
don't
know
how
much
of
a
difference
it
makes
in
in
those
areas,
but
I
wondered
about
even
like
just
one
hour
like
10
o'clock.
Eastern
time
might
be
a
little
bit
easier
for
the
west
coast
folks,
but
might
still
be
acceptable
for
time
zones
out
that
direction.
I
don't
know.
E
I
Yeah,
did
we
reach
out
to
the
folks
who
are
in
european
and
asian
time
zones
or,
like
you
know,
gmt,
0
and
beyond?
Did
we
reach
out
to
those
folks
outside
of
the
ones
who
would
normally
attend?
Who
are
here
still
and
like?
Let
them
know
or
did?
Are
there
no
others.
B
Yeah
and
frankly
I
don't
I'm
not,
I
don't
know
if
we
have
a
list
or
an
idea
of
of
who
we
would
be
reaching
out
to,
but
I
think
maybe
for
folks
who
would
know
we.
B
On
them,
I'm
not
sure
how
we
would
do
it
to
best
raise
awareness
and
and
encourage
involvement.
B
F
B
But
I
was
primarily
thinking
about
our
west
coasters.
I
know
it's
quite
early
for
engineers
aren't
known
for
getting
up
early.
At
least
software
engineers.
F
B
B
That's
what
I
feel
too,
I
I
don't,
I'm
not
hearing
a
lot
from
tyranny
and
shelley
and
that
maybe
because
they're
asleep,
I
don't,
I
don't
know.
B
Do
you
do
you
two
have
any
thoughts
I
mean.
I
call
you
out
specifically
because
I
saw
the
twitter
thread
this
morning,
which
I
know
was
you
know
I
assume
was
in
jest,
but
but
I
thought
I'd
ask
since
you
might
have
thoughts.
N
N
I
normally
get
up
at
like
7
30,
probably,
but
I
would
say
like
do.
We
know
like
how
often
this
time
would
repeat.
B
Well,
we
were
talking
about
doing
it
every
other
week
for
a
few
weeks
to
see
if,
if
it
folks
in
in
other
time
zones
that
we
fear
may
not
be
participating
because
of
the
you
know,
u.s
centric
meeting
times.
N
B
C
B
Well,
maybe
maybe
that's
the
suggestion,
maybe
we
move
it
an
hour
later
and
and
and
then
try
it
every
other
week.
For
you
know
a
little
bit.
I
I
I
think
one
thing
that
you
know
we
could
do
is
if
you
know
we
do
end
up
getting
asia
from
or
not
I'm
tired.
If
we
do
get
end
up
getting
interest
from
apac,
I
think
we
can
adjust.
Then
it
seems
like
we
haven't,
had
any
engagement
today
and
I
don't
know
if
there
has
been
interest
not
trying
to
exclude
but
more
trying
to
make
sure
that
we're
not
necessarily
like
optimizing
for
something
that
we
don't
have
like
changing
the
thing
and
then
hope,
like
kind
of
crossing.
I
Our
fingers
that
people
will
come
is
maybe
the
less
optimally
optimal
way
to
do
it
rather
than
like,
when
people
ask
or
explicitly
asking
for
feedback
and
then
optimizing
toward
that
seems
like
a
little
bit
of
a
better
path.
There.
B
I
I
I
guess
like
another
thing
is:
I
think
this
also
speaks
somewhat
to
to
general,
like
welcoming
in
the
the
cbc
stuff
is
like.
Are
we
open
to
literally
anyone
showing
up?
Is
that
how
we
are
framing
this,
because
that
that
hasn't
necessarily
been
my
understanding
and
generally
the
at
least
in
the
node
stuff?
That's
not
necessarily
how.
E
We
have
a
we
have
observers,
so
anybody
can
join
as
an
observer
and
then
anybody
can
join
as
a
regular
member.
If
they're
you
know
active
in
the
projects,
I
think
I
think
you
know
joe's
point
is
it
can
be
a
self-fulfilling
prophecy?
If
the,
if
people
look
at
things
and
say
I'm
going
to
have
to
get
up
early
every
week,
you
know
then
they're
not
going
to
be
interested
in
participating
or
just
can't,
because
they've
got
personal
commitments
right.
I
Yeah,
no,
I'm
very
totally
aware
yeah,
like
I
totally
understand
that
I
I
guess
like
it
is
largely
just
like
a
thing
of
like.
Do.
We
have
members
of
projects
who
are
in
apac
I
I
know
we
have
a
couple
people
in
australia
and
I
I
know
of
like
one
or
two
I
can
think
of
two
people
in
like
asia,
but
that's
the
extent
of
the
people
and
the
ones
I've
talked
to
have
like
the
ones
I
I
know
of
there
have
zero
interest
in
participating
in
this.
I
So
you
know
I
could
be
wrong,
but
like
yeah,
I
guess
that's
just
what
I'm
getting
at
is
like.
Are
we
optimizing
for
something
that
we're
not
gonna,
see
happen?
Yeah
just.
F
As
an
observation
to
current
optimization
has
definitely
not
really
been
for
a
back
at
all,
it
has
been
for
the
benefit
of
of
europe,
where
the
meeting
times
that
we
previously
had
were
clearly
very
much
evening
meeting
times.
It
works
for
me
personally,
because
this
falls
in
with
all
of
the
other
meeting
times.
F
I've
got
with
americans
and
the
way
that
I'm
not
doing
this
really
as
a
part
directly
of
of
my
daily
work,
but
a
little
bit
on
the
side,
so
it
kind
of
works
for
me,
but
for
many
of
you
that
are
participating
in
this
from
the
us
or
canada,
you
are
participating
this
as
a
part
of
your
actual
work
day
in
one
way
or
another
and
the
dynamic
there
is,
shall
we
say,
a
lot
more
common,
and
this
dynamic
is
not
really
possible
with
the
previous
meeting
times
that
we've
had
for
european
participants
who
are
forced
into
participating
in
this
outside
of
their
normal
work
hours.
F
So
if
we
do
continue
this
for
a
couple
of
iterations
with
well,
I'm
I'm
up
10
hours
ahead
of
california.
F
So
it's
I
I'm
on
the
the
extreme
case
of
this,
but
but
certainly
an
hour
later
from
this,
would
much
more
easily
enable
participation
from
central
or
western
europe,
for
instance
near
the
end
of
their
work
days,
but
not
like
clearly
after
the
end
of
their
work
days,
as
we've
had
up.
Until
now,
at
least.
I
Yeah,
so
I
mean,
if
we're,
if
we're
not
necessarily
trying
to
optimize
for
apac
in
in
this
in
this
specific
time
zone,
then
I
think
moving
it
back.
An
hour
is
fine.
If
our,
if
our
stated
goal
there
is
european
friendliness,
I'm
I'm
fine
with
that,
and
I
I
think
that
that's
a
fine
optimization
to
make
there.
B
B
I
Are
you
potentially
doing
the
same
kind
of
spreadsheet
that
we
do
in
node
and
having
that
be
open,
openly,
editable,
and
that
can
be
your
interest
of
like
here?
Here
is
what
I
want
to
do,
and
here's
like.
I
am
interested
in
participating.
Here's
my
the
times
I
can
participate,
because
then
that
would
help
us
and
like
include
time
zone.
So
then
that
would
help
us
kind
of
optimize
in
that
way
and
like
make
sure
we
can
hit
as
many
time
zones
if
we
do
try
to
do
something
different
like.
F
F
Oh
okay,
yeah,
sorry,
yeah
and
then
that's
one
decision
that
we
could
make
and
then
another
one
is
that
we
open
up
an
issue
in
order
to
get
feedback
via
github
comments
or
or
entries
on
a
spreadsheet
somewhere
about
potential
interest
from
people
who
are
interested
in
participating.
F
But
who
are
unable
to
do
so,
given
our
current
times
that
we're
operating
in,
I
think
we
can
do
either
or
both
or
neither
if
we
so
feel
like.
B
F
B
Two
issues
I
will
work
on
the
one
that
is,
you
know
doing
an
hour
later
than
this
time
and
rotating
it.
You
know
so
in
two
weeks.
We
would
do
this
again,
but
an
hour
later,
and
if
somebody
wants
to
pick
up
the
other
one,
that
would
be
great.
F
B
I
Yeah,
just
just
make
the
issue
it's
well,
we
can
figure
it
out.
Then
I
I
don't
know
if
we
need
to
keep
mostly
digging
into
this
yeah.
I
F
I
I
So
the
I
would
normally
say
yes,
I
have
a
lot
of
things
that
I'm
trying
to
knock
out
this
week.
If
you're
fine
waiting
a
week,
I
could
do
it,
but
if
you
want
to
get
it
done,
I
would
recommend
someone
else
taking
it.
B
B
Great
great
I'll
I'll,
save
it
and
maybe
share
it
in
slack
too
cool
all
right.
Well,
that's
great!
I
appreciate
everyone
taking
a
few
minutes
to
talk
about
that
stuff.
B
So
we
have
a
plan
on
that
and
we
can
take
the
comments
and
conversation
to
the
issue
issues
and
go
from
there,
so
cool
and
we're
you
know
just
about
out
of
time.
So
I
guess
now
is
a
good
time
to
call
it
around
thanks
everybody
for
joining
appreciate.
It.
C
O
B
Sure
I
can,
I
can
talk
with
you
for
a
minute,
if
other
folks
want
to
drop
or
stay
as
as
you
like,.
N
B
Oh
yeah
great
yeah,
so
so
you
know
maybe
tell
me
about
yourself
and-
and
I
I
guess
I'll
tell
you
about
me
first,
you
know
my
name
is
joe
sepi,
I'm
the
the
chairperson
of
the
cross
project
council's
lacrosse
project
council,
which
is
the
kind
of
top-level
technical
and
advisory
committee
at
the
openjs
foundation,
where
we
have
a
number
of
open
source
projects,
maybe
you're
familiar
if
you're
here
in
the
meeting.
What
is
it?