►
Description
To learn more about critical open source JavaScript projects like Appium, Dojo, jQuery, Node.js, and webpack, and 27 more checkout The OpenJS Foundation: https://openjsf.org/
A
B
We
have
some
exciting
news:
we
have
a
new
security
engineering
champion
at
the
openjs
foundation.
Your
one
and
only
Jordan
harband
Hey,
so
Jordan
will
be
supporting
the
work
of
The
Sovereign
Tech
fund
that
big
investment
from
the
German
government
for
security
and
infrastructure.
So.
A
Yay
very
exciting
that
is
really
wonderful
and
just
really
exciting,
to
see
how
all
of
this
investment
is
going
to
help
upgrade
infrastructure
for
all
of
the
openjs
projects,
which
is
desperately
needed
and
well
not
desperately
it's
needed
to
maintain
and
sustain
our
project.
So
thank
you,
Jordan
and
everybody
other
announcements,
any
other
shares
project
related
shares,
we'll
get
into
the
plenary
reports
if
there
aren't
any
and
if
there
are
any
this
week,
unless
there's
big.
C
Project
announcements,
the
next
tc39
plenary-
is
in
July,
so
there's
some
time
for
it.
A
D
D
Talk
at
JS
Nation
last
week
on
what's
new
on
node
and
then
I
did
I
did
just
block
a
week
before
that
on
yes,
2023
just
about
what
are
the
new
things
that
we
have
and
and
some
of
the
code
samples
and
likes.
A
Also
render
Atlanta
's
we're
we're
done
there,
so
good
energy
happening
in
these
community
events
lately,
so,
okay,
cool,
no
other
announcements
will
go
into
really
quickly.
Some
plenary
reports
so
tc39
meets
next
week.
You
just
said
Jordan,
so
nothing
this
week.
A
Next
month,
yeah
and
yeah
Rick
is
pointing
out
that
the
general
assembly
meeting
for
for
ecma
is
in
in
about
two
weeks
so
end
of
this
month,
really
cool
so
and
I.
Also
really
cool
I,
don't
know
if
we
mentioned
this-
that
Samina
Hussein,
the
new
Secretary
General,
was
at
and
attended
several
of
our
open.js
world
sessions
at
Vancouver.
So
hopefully
you
all
got
sent
it
to
me
here,
Donovan's,
not
on
from
tc53,
so
we'll
get
that
async
from
him.
A
Anybody
want
to
update
on
winter
yeah
I
mean
we
can
any
updates
from
winter.
F
Sorry,
no
I,
don't
think,
there's
anything
actual
to
share
right
now
we
are
looking
forward
to
the
node.js
next
10
serverless
event
and
from
a
standards
perspective.
I,
don't
think
there's
anything
else
happening.
Oh
actually,
there
was
there's
a
cool,
a
pull
request
for
the
runtime
Keys
proposal
is
being
merged
into
node.js,
which
is
cool
in
our
node.js
docs.
There
was
some
discussion
around
like.
F
Is
it
stable,
yada
yada,
like
it
says,
it's
a
draft
and
it's
like
well,
it
can
only
ever
be
a
draft
because
we're
winter
CG
we're
just
a
community
group.
We
don't
actually
have
the
I
guess
like
permissions
to
to
like
publish
it.
I
guess
you
know
we
can
publish
it.
We
can't
Market
as
like.
Not
a
draft
language.
Nuances
are
weird
I
would
say.
Maybe
another
time.
F
Let's
like
let
me
talk
about
this
I
went
to
CG
first,
but
maybe
in
the
future
we're
going
to
discuss
what
some
of
the
future
of
that
looks
like.
If
we're
going
to
start
getting
adoption
in
projects
like
you
know,
JS.
F
A
Our
w3c
process,
X
experts,
aren't
on
the
call
they,
but
they
could.
They
could
probably
provide
a
a
good
overview
and
kind
of
historical
understanding
of
why
why
CGS
are
only
able
to
publish
draft
documents,
but
that's
exciting,
though,
it's
really
exciting
to
see
a
lot
of
community
groups
at
w3c
they
get
together
and
they
do
a
lot
of
discussion
and
and
sort
of
just
kind
of
mind-melding,
but
not
necessarily
to
the
point
where
documents
are
are
produced.
A
So
it
is
really
cool
to
see
owner
CG,
having
impact
so
quickly
and
and
all
that
so
congrats
to
to
the
winter.
Seeking
group.
D
A
You
w3c
nothing
at
the
big
top
level
other
than
you
know
we're
keeping
an
eye
on
on
the
TPAC
event.
Robin
and
I
have
also
been
working
with
w3c
a
wasp,
open,
ssf.
A
Somebody
else
I
think
sorry
that
on
the
on
the
secure
the
web
forward
and
have
some
plans
to
do
rather
than
an
in-person
session
virtual
kind
of
topic
focused
things
and
I
think
once
we
have
a
better
thematic
kind
of
point
of
view,
I
think
we're
going
to
be
asking
this
community,
in
particular
to
help
Source
great
people
to
come
and
kind
of
share
and
and
be
part
of
that
and
Jordan
is
I.
Think
this
is
your
job
now
so
Jordan.
A
Yeah
you'll
be
part
part
of
that
as
well,
so
I
think
that's,
but
the
TPAC
event
is
I.
Think
the
the
thing
that's
most
Salient
coming
up
from
w3c
anything
Toby's
not
here
for
OSI
I,
think
that's
our
all
of
our
groups.
Yes,
cement.
D
Are
there
folks
here
who
are
who
are
interested
or
work
with
policies,
because
I
was
at
a
closed
panel
discussion
last
evening
with
folks
from
Google,
where
they
are
working
with
individuals
from
different
communities
and
falls
and
Open
Standards,
specifically
for
government
Affairs
and
public
policies?
A
B
We've
signed
some
things:
we've
signed
and
supported
like
the
industry
effort
around
the
Cyber
resilience
act
with
open,
Forum
Europe
and
the
LF
we
haven't
really.
You
know
dug
deep
on
any
other
big
policy
issues.
Do
you
know
what
it's
kind
of
centered
on.
D
It's
it's
pretty
open
and
at
this
point
of
time,
because
MLA
is
kind
of
the
Hot
Topic,
the
discussions
were
around
that
and
also
some
of
the
web
standards
and
how
we
can
kind
of
bridge
the
gaps
between
them
and
what
and
what
basically
works
in
the
free
and
open
world
and
how
the
policies
that
might
eventually
you
know
shape
the
new
technologies
still
adhere
to.
Some
of
the
philosophies
of
free
and
openness
is
what
was.
D
A
Y
okay,
I
think
that's
all
of
our
and
Emily's,
usually
the
updater
for
Unicode
I.
Think,
though,
that's
it
for
the
folks
that
are
on
the
call,
let's
dive
into
our
our
agenda,
unless
there's
any
other
announcements
or
shares
sharing
is
caring.
A
So
we
have
some
new
member
pull
requests,
three
of
them
to
be
exact
and
I'm
very
excited
about
all
of
them.
I
think
all
of
these
have
been
open
for
what
I
will
call
a
hot
minutes
and
I
just
like
to
take
time
during
the
call
to
welcome
and
plus
one
and
merge
these
in
first
Rick
Martin's
hi
Rick,
we're
thrilled
that
you're
here
and
so
grateful
you
got
involved
and
I
got
plugged
in,
especially
as
part
of
the
opengs
world.
A
Y'all,
likewise
next
up
is
Darcy.
Clark
Darcy
has
often
been
on.
The
calls
doesn't
look
like
Darcy's
here
today.
His
his
co-founder
Luke
is,
however,
LOL.
That's
a
joke.
A
Darcy
I
just
realized
like
this
is
recorded,
and
people
might
not
understand
that
if
that
was
a
joke,
so
Darcy
has
been
certainly
really
a
valuable
contributor
and
participant
in
certainly
in
recent
conversations
about
node
and
and
npm
and
then
package
conversation
so
I
think
Darcy
also
was
I
met
Darcy
on
the
jQuery
project
like
100
years
ago.
So
that's
kind
of
funny.
G
G
G
I,
don't
know
if
there's
any
standards,
email
lists,
but
we
should
add
folks
to
that
and
I
kind
of
am
bringing
this
up
in
the
sense
that
if
anybody
has
any
thoughts
on
how
to
make
some
of
this
stuff
work
better,
because
I've
had
in
the
CPC
members
added,
because
other
folks
just
go
in
and
merge
oh
great
yeah.
Let's
add
you
know
Jordan
or
whatever,
and
then
we
forget
to
like
do
all
the
other
things.
G
A
Let's
definitely
make
a
note
in
here,
like
as
part
of
like
our
our
process,
to
make
sure
that
these
folks
are
added
to
a
our
slack
Channel.
If
they're
not
already,
there
I
think
everybody
here
is
and
then
also
to
your
point.
The
standards
team
group
in
which
I
think
Jordan
helped
to
somebody
did
I
think
it's
Jordan
helped
to
organize
for
us
and
and
tidy
up
which
folks,
who
are
added
to
the
standards
team,
just
have
elevated
permissions
on
the
standards
repo,
because,
obviously
that
makes
sense.
A
I
don't
think
we
use.
If
we
have
a
standards,
distro
list
I,
don't
think
it
is
used,
I've
never
used
it.
A
We
could
if
this
group
wanted
to
have
a
discussion
list
outside
of
the
slack
Channel
but
I
frankly
kind
of
like
the
slack
Channel
and
I,
don't
know
that
we've
had
a
great
need
for
a
list,
but
that's
you
know
my
my
two
cents
but
of
course
I
could
be
convinced.
Otherwise,.
C
I
hadn't
only
looked
into
it
briefly
when
I
was
doing
similar
stuff
for
openssf,
and
but
it
would
be
pretty
easy
to
define
a
single
source
of
Truth
for
arbitrary
teams
and
then,
when
you
edit,
that
file
it
just
the
GitHub
action
goes
out
and
updates
the
GitHub
team.
It
updates
the
readme
list,
it
you
know,
and
so
then
we
just
don't
have
to
think
about
it.
If
this
is
a
a
problem,
we.
B
B
E
Hey
sorry,
I
was
kind
of
chatting
it
in
there
because
I
didn't
want
to
derail,
but
I
posted
that
you
know
we
utilize.
We
built
a
tool
that
managed
GitHub
Works,
because
we
have
a
few
across
the
the
Good
Eye
Spectrum,
when
we
require
folks
and
whatnot
that
we
manage
it
via
these
comma
files
and
use
this
sort
of
a
CLI
and
we
use
actions
and
stuff
to
automate
it.
E
E
Do
you
have
organizations
so
just
something
to
consider
yeah?
Let's.
A
Let's
file
an
issue
to
just
how
you
know
that
you,
Rick
and
and
Jordan
can
just
like
kind
of
zero
in
on
options
there
I
do
think
it'd
be
great
just
to
be
able
to
merge
something
in
and
ban.
You
know
have
that
have
that
problem
solving
we
don't
have
to
worry
about,
like
oops
I
didn't
give
Darcy
right
access.
My.
G
A
Sounds
good
action
open
issue
all
right
now
back
to
you,
know,
thanking
and
praising
Darcy
who
is
not
here.
So
maybe
his
ears
will
burn
I'm
in
hit.
Merge,
pull
request
on
Darcy's
PR
welcome,
Darcy
to
the
the
fun
Club.
A
That's
what
we
call
ourselves
right,
okay
and
then
last
but
not
least,
cindil
cindil
has
also
been
oh,
like
a
long
contributing
member
to
the
openjs
community.
A
What
I
love
about
Sundial
is
just
like
you
know.
All
of
us
have
you
know
the
times
where
we
are
peaking
and
we're
here
a
lot
and
then
stuff
happens
at
work
and
then
we're
a
little
less
available.
But
sindel
is
always
like.
We
just
pick
up
right
where
we
leave
office
until
he's
he's
always
following
and
and-
and
you
know,
keeping
in
touch,
even
if
he's
not
able
to
make
it
so
really
grateful
that
he
is
here.
A
We
got
some
merge
conflicts
on
this,
but
I
will
fix
the
the
the
conflict
on
his
PR
and
get
him
merged
in
so
I
just
want
to
say,
welcome
some
Bill
cool
all
right.
So
those
are
our
new
members
other
like
just
housekeeping
bits.
There's
some
housekeeping
PRS
as
well
a
meeting
a
couple
of
meeting
minutes.
A
A
Okay,
hearing
none
I
will
get
those
in
now
and
then
that
brings
us
to
a
the
topic
that
has
been
tabled
for
the
last
couple
of
weeks,
but
has
been
I.
Think
really
important
for
this
group
to
sort
of
be
able
to
better,
articulate
and
and
support
the
community
members
who
want
to
interact
and
contribute
with
us,
and
this
of
course
is
issue
number
to
what
I'm
sorry
173
terms
for
subject
matter
and
expert
participation.
A
I
was
able
to
spend
a
couple
of
hours
a
few
weeks
ago
and
add
added
some
PRS
to
address
173..
If
you
recall
from
our
conversations
with
Leia
with
guy
and
with
with
many
others,
this
sort
of
like
Hey,
we're
so
glad
you're
here,
but
we
just
need
to
understand
a
little
bit
better.
A
You
know,
what's
what
is
this
group
doing
and
how
can
we
better
explain
to
like
the
our
our
fellow
participants
in
the
working
groups
and
to
our
fellow
community
members
within
our
projects,
how
it
is
that
this
group
supports
and
serves
so
I
opened,
two
PRS
and
I
think
I
might
ask
us
to
look
at
PR
number
239.
A
And
this
was
a
file
that
we
created
to
start
to
just
document
where
people
who
are
present
and
participating
in
the
standards
working
group
or
really
maybe
they're,
not
here
all
the
time,
but
they're
very
active
within
standards
in
the
web.
You
know
World
writ
large,
where
are
those
folks
participating
so
that
if
our
community
members
have
questions
want
to
meet
someone,
you
know
make
a
network
connection,
ask
a
question,
get
some
mentorship.
All
of
that
kind
of
thing.
Where
are
these
resources
within
our
community?
A
And
so
we
started
this
this
file
and
I
made
some
changes
that
I
hope
maybe
organize
it
a
little
bit
better
and
also
Express
kind
of
a
little
bit
further,
where
the
openjs
foundation
has
some
formal
relationship
either
you
know
as
a
member
or
as
a
liaison
so
yeah,
that
is
this
PR
and
I
would
love
your
thoughts.
Sorry
Jordan.
C
No,
that's
fine,
I
I,
try
not
to
interrupt
so.
Obviously
this
is
great.
It
looks
better.
The
thing
that
I
think
we
need
to
preserve
is
that
this
does
not.
This
is
not
a
list
of
official
openjs
representation.
This
is
like
a
list
of
the
official
participation
that
openjs
Affiliated
people
happen
to
have,
and
so,
if
you
see
someone's
name
on
this
list,
that
does
not
mean
necessarily
that
they
are
an
openjs
rep
or
something,
but
it
does
mean
that
they
are
part
of
opengs
and
also
are
part
of
that
group.
A
Yeah
and
so,
and
you
made
that
point
and
I
realized
I,
didn't
update
it
also
on
TC
on
another.
One
I
think
that
it
might
be
helpful
then
to
maybe
in
parents
or
something.
A
The
affiliation
so
that
it
can
be
a
little
bit
more
clear
for
for,
because
I
think
it's
a
very
valid
point
that
we
wouldn't
want
the
Assumption
to
be
that
like
openjs
has
signed,
you
know,
IP
agreements,
we.
C
Could
even
do
something
as
trivial
as
as
stick
a
tiny
openjs
logo
in
front
of
each
name
where
that
relationship
is
is
official,
as
opposed
to
like
simply
overlapping,
and
you
just
put
a
little
Legend
at
the
top.
This
denotes
such
and
such
like
some.
Even
that
would
be
fine
if
you
want
to
do
stuff
in
parens.
That's
fine
too!
Like
it,
you
know,
I,
don't
have
a
strong
opinion
about
how
it
looks.
A
I
like
that
proposal
and
and
also
help
actually
I
like
that
I
like
the
little
edition
of
the
icon,
as
as
it
means
to
do
that
because
then
it
still
permits
us
to
add
if
there
is
a
company
or
corporate
affiliation
that
as
well,
which
I
think
is
is
is
good.
So
let's
do
that.
A
Oh
yeah
yeah
that
that
is
true,
I
just
again
want
to.
In
some
of
these
cases,
people
might
be
sensitive
that
you
know
they're
they're
there
and
they're.
They
can
be
part
of
any
conversation
that
impacts
an
openjs
project
but
they're
actually
there
wearing
on,
because
Microsoft
has
sent,
for
example,
sending
them
to
participate.
C
A
Our
members
really
appreciate
that
so,
okay,
so
great
suggestion
we'll
make
that
Improvement
and
then
you
know
my
thought
was
just
too
like
then
as
a
process
from
a
process
standpoint,
if
there's
a
new
organization
that
openjs
projects
or
community
members
think
that
we
should
be
affiliating
with
you
know,
it's
a
poorer
question
to
you
know
this
file
and
a
discussion
of
like
who
is
going
to
be
kind
of
interfacing
with
the
organization
on
our
behalf
and
but
I
I.
A
Suppose
one
thing
we'll
we
can
do
is
an
ongoing
basis.
Make
sure
there's
nobody
missing
from
this.
The
other
thing
this
can
we
can
do
is
look
at.
Some
of
this
is
is
kind
of
old
and
I'll
point
to
like
the
w3c
category.
A
By
way
of
example,
we
have
a
lot
of
Affiliated
accounts,
people
who
were
part
of
the
I
think
most
a
lot
of
these,
like
Ann
and
and
Scott
Gonzalez,
for
example,
from
the
jQuery
Community
back
in
the
day
like
eons
ago,
and
these
are
affiliated
on
the
w3c
Registration
site
with
openjs.
But
you
know,
frankly,
probably
we
need
to
unaffiliate
right
as
a
matter
of
housekeeping,
because
they're
they're
no
longer
with
the
project
and
so
just
kind
of
helps
us
surface.
That
too.
A
A
So
this
document
tried
to
capture
some
of
the
bigger
conversation
that
we've
had
with
with
the
group
over
the
last
several
weeks.
About
sort
of
you
know
what
are
we,
who
is
this
group
of
people?
What
are
they
sort
of
tasked
with
doing
who
can
come?
A
A
Oh
goodness,
it
was
a
big
exchange.
I
didn't
see
five
days
ago,
sorry
about
that
Toby
and
Jordan.
So
this
one
looks
like
it
might
be
open
for
a
little
bit
more
more
discussion.
C
Actually,
Toby
and
I
I
think
resolved.
Our
our
misunderstanding,
I
think
we're
both
on
the
same
page
and
Toby
was
unaware
of
the
previous
discussion.
We'd
had
on
issue
84
around
this
stuff.
So
it
sounds
like
it's
not
going
to
be
controversial,
to
lay
lay
things
out,
as
indicated
in
that
discussion
thread,
but
there
was
just
some
confusion
about
the
terminology.
C
You
know
I
think
we
can
bike
shed
that,
but,
like
the
specific
name
for
subject
matter,
expert
or
invited,
expert
or
I,
don't
know
whatever
the
you
know,
a
person
who's
like
a
delegate,
an
official
representative
versus
a
person
who
is
merely
overlapping
right,
like
we
just
I,
don't
think
we
have
true
like
the
only
terms
I
have
for
those
are
tc39
terms
and
I,
don't
think
they
have
Universal
ones
and
the
way
Toby
was
using
terms
was
confusing
to
me
initially.
C
A
Yeah
so
I
think,
given
the
open
comments
from
Toby,
we
should
probably
which
I
should
kind
of
comment
back
on
some
of
his
questions
and
make
sure
that
my
responses
kind
of
satisfy
the
concerns.
I
I.
A
Guess
since
he's
not
here
to
discuss,
let
me
just
take
it
up
a
level
and
for
those
of
you
who
have
had
a
chance
to
review
the
pr,
and
particularly
those
of
you
who
are
like
you
know,
Ethan
and
others
who
are
who
are
really
approaching
this
group
from
the
standpoint
of
as
a
XYZ
project
member,
you
know
how
can
I
best
interact
with
and
engage
this
group
of
people?
Does
the
document
begin
to
start
in
in
its
revised
shape
is?
A
F
This
is
the
the
document
in
I'm
following
along,
we,
the
member
representation,
one
in
particular.
A
Yeah
and
two
240
is
the
pr
so
the
and
the
and
the
file
change
is.
There
are
I
think
two
files
changed.
One
is
members
member
expectations
and
the
other
is
governance,
governance
basically,
and
that
file
I
I
just
brought
some
stuff
out
of
governance
and
sent
into
the
member
expectations
where
I
thought
that
was
a
more
accurate
place
for
that
content
to
be,
for
example,
you
know
around
participating
in
standards,
working
group
meetings
out
external
meetings
and
then
yeah
and
and
then
just
sort
of
better.
A
You
know
clarification
around
some
of
the
language
that
we've
been
using
to
describe
how
we
work
and
what
our
group
does
I'm
going
to
leave
this
open
a
few
more
days
for
folks
to
just
make
sure
that
they
have
had
a
chance
to
to
review
again.
The
overall
goal
here
is
to
clarify,
hopefully,
simplify,
hopefully,
and
make
make
it
a
bit
more
straightforward
for
project
communities
under
the
openjs
wing.
To
say
we
have
a
thing
that
we
would
like
to
intersect
with.
How
can
we
use
this
group?
A
How
can
we
engage
with
this
group
or
how
can
we
best
on
our
own
go
intersect
with
XYZ?
You
know
technical
committee
and
and
know
that
we're
we've
got
the
support
of
the
foundation
and
the
and
the
resources
here
so
I
then
I
said
so
especially
to
to
the
newer
attendees
this
P.
This
PR
is
for
you.
Let
me
know
how
to
make
it
a
little
bit
more
or
let
us
know
how
to
make
it
a
little
bit
more
useful.
F
Sounds
good
I
will
yeah
I'll
take
a
look
at
this
and
and
if
I'll
leave
any
feedback,
if
I
find
anything
necessary.
A
Yeah,
the
member
yeah,
so
let
me
go
back
then
into
issues
and
let's,
since
the
package
Json
folks
are
here,
233
was
not
tagged
for
the
agenda
today,
but
we've
got
a
few.
We've
got
several
minutes
left
in
in
this
meeting
and
there's
been
a
lot
of
conversation
on
that
issue
thread.
A
So
let
me
invite
Ethan
if
you'd
like
to
maybe
give
us
a
summary
of
where
that
discussion
is
and
kind
of
what
next
steps
are,
so
we
can
kind
of
either
create
a
ticket
or
help
facilitate
the
next
set
of
things.
Ethan
you
wanna.
F
Check
yeah,
we
I,
guess
I,
guess
sort
of
a
seat
of
Affairs.
F
We
have
we
just
previous
to
this,
call
we're
on
the
CPC
working
working
session,
oh
yeah,
and
we
discussed
a
new
approach
and
some
new
objectives,
essentially
under
the
ethos
of
standardizing
and
specifying
package
Json
we're
looking
back
on.
Where
did
it
come
from,
and
why
was
that
a
problem
or
like
sort
of
like?
Where
was
The
Prompt
for
everything?
F
And
then
we
took
that
and
we
started
designing
more,
outlining
new
objectives
towards
that
goal
and
those
objectives
are
no
longer
as
simply
just
standardizing
or
specifying
package
Json.
F
We
have
more
smaller
goals
that
we're
going
to
be
working
towards
and
things,
but
all
in
all,
it's
it's
still
under
the
the
umbrella
of
that
is
that
we
want
to
help
solve
some
of
the
pain
points
around
the
fact
that
the
document
is
used
to
configure
and
specify
our
JavaScript
projects
all
across
the
industry.
F
The
the
ecosystem-
and
there
is
very
little
consensus
on
how
tools
handle
certain
things,
mainly
because
of
just
historically
npm
and
node
existing
for
longer
than
everyone
else
and
just
not
having
to
having
to
consider
alternatives,
because
they
were
the
only
two
tools,
but
we
are
now
in
a
future
where
there
are
more
than
just
node
and
npm,
and
so
working
slowly
and
carefully
towards
a
better,
a
better
collaboration
will
be,
will
be
good
directly
for
the
standards
working
group.
I,
don't
know
what
process
we
want
to
follow.
F
I
could
post
this
similar
kind
of
of
a
status
message
on
these
on
that
issue
and
on
other
similar
issues
like
the
one
in
the
CPC
group,
I,
don't
know
if
it's
better
to
have
long
opened
issues
or
try
to
close
things
and
reopen
things
when
relevant.
So,
whichever
is
preferred.
A
That's
a
great
question
and
kind
of
speak
speak
to
the
fact
that
we've
never
quite
figured
out
how
we
want
to
what's
what
sword
I'm
looking
for
like
track
state,
if
you
will
of
these
different
initiatives
that
people
have
come
and
and
spoken
with
us
about,
because
frankly,
I
would
see
that
as
sort
of
the
metric
of
success
for
this
working
group
for
the
standards
working
group
here
you
know,
are
we
helping
projects
like
this
like
launch,
slash,
find
successful
outcomes,
and
you
know,
and
things
like
that,
we
had
conversations
about
polyfills
we've
had
conversations
about
other
efforts
from
other
projects
or
testing
and
that
sort
of
stuff,
but
I,
don't
think.
A
We've
done
a
great
job
with
kind
of
tracking
those
things
over
time
and
checking
in
and
and
seeing
where
the
support
we
can
provide
might
be
I.
Think
I
speak
for
everyone.
I
shouldn't
say
that
I
shouldn't
my
personal
preference
is
not
to
have
a
400
issue.
Comment
long
thread.
That's
five
years
old,
for
example,
I
I
tend
to
prefer
issues
that
are
fairly
tightly
scoped.
D
A
So
I
I'm
I'm
for
I'm
foreclosing
this
issue
finding
a
way
to
better
keep
abreast
of
what
you
guys
are
doing
and
then
also
having
you
open
additional
issues
when
there's
time
when
it's
when
the
time
is
ripe
for
better
conversation
but
I'm
Keen
for
Jordan
or
Luke
or
Rick,
or
anybody
to
advance
anybody
to
and.
F
I
I
am
plus
one
on
that
jewelry
I.
Think
one
thing
I
forgot
to
mention
is
that
we
do
intend
to
share
like
an
update
of
of
what
we're
doing
next
in
two
weeks
time
at
this
meeting,
because
of
we
wanted
to
have
a
reasonable
deadline,
essentially
for
ourselves
of
what
work
are
you
doing?
What
can
you
present,
and
so
we
tried
to
find
the
best
meeting
that
suits
that
need,
and
that
would
be
two
weeks.
The
standards
call
whether
or
not
we're
defining
a
standard.
F
No,
but
like
are
we
doing
work
within
the
bucket
of
standardizing
package
Json,
yes,
so
I
will
go
ahead
and
I
will
communicate
some
of
that
on
the
current
issue
thread
I'll
close
that
out
and
then
maybe
we
all
will
definitely
will
open
a
new
one
that
we
can
then
add
an
agenda
label
to
and
yeah.
We
can
try
and
be
a
little
more
Atomic
with
the
use
Communications.
A
Brilliant
I
like
that
and
then
we'll
also
I,
think
again
try
and
think
about
ways
to
I
mean
I.
Think
I
think
we
all
want
to
do
things
that
are
impactful
right
and
that
drive
support
and
outcomes
for
our
projects
and
for
for
our
community
members
and
I.
Think
I'd
love
to
figure
out
how
to
just
lightweight
right,
I,
don't
love
putting
process
or
extra
steps
on
people
I.
A
Think
that
sucks,
because
I,
don't
like
it
on
me
personally,
but
lightweight,
keep
track
of
like
you
know
how
things
are
progressing
and
ways
in
which
we
can
either
offer
help,
or
you
know,
review
or
pull
in
more
people
or
whatever
you
need.
You
know,
that's
that's
kind
of
the
one.
One
of
the
goals
of
this
group
is
to
make
standards
development
like
a
fun
thing
to
do,
and
an
easy
and
and
pleasant
thing
to
do
so.
A
A
Okay,
my
reminders
are
that
we
got
a
couple
of
holidays
coming
up
in
the
next
month,
Juneteenth
and
that's
next
Monday.
A
If
you
have
project
meetings
on
the
19th
of
June,
you
may
consider
rescheduling
as
that
is
a
holiday
that
is
increasingly
observed
by
our
community
and
then
also
July
4th,
which
is
a
Tuesday
this
year.
That'll
be
here
in
like
a
hot
minute
and
and
that's
Tuesdays
are
big
open,
JS
meeting
days.
A
So
that's
another
day
to
just
bear
in
mind
you
may
it
won't
impact
standards
working
group
because
we're
on
sort
of
the
off
week
so
we'll
see
everybody
on
the
27th
before
that
holiday,
but
just
as
an
FYI,
a
couple
of
holidays
coming
at
me
impact
your
your
community.
Calls
to
before
that
surprises
you,
you
can
preemptively
go
cool,
I
can
move
this
yes,
50
of
the
year
is
done
and
I
cannot
believe
it
like.
That
is
wild
wild
cool
all
right.
A
Well,
if
there
is
no
other
business,
I
will
adjourn
us
for
today
and
I
want
to
thank
everybody
for
joining.
Oh
Luke,
sorry.
H
Sorry
yeah
I'm,
just
new
to
looking
at
these
calendars
I
wanted
to
make
sure
I
have
the
right
thing.
Ethan.
You
said
where
our
package
Json
update,
is
in
two
weeks
I
see
a
CPC
meeting
on
that
day
and
a
standards.
H
F
No,
so
the
CPC
is
a
working
session
which
would
get
which
would,
as
far
as
I
understand
will
be
defined
the
week
prior.
F
F
If
maybe
next
week,
at
the
CPC
meeting,
we
determine
if
there's
nothing
other.
If
nothing
else
is
needing
a
working
session.
Maybe
we
can
use
and
schedule
that
working
session
for
package
Json
work
I
didn't
want
to
to
bog
that
down,
but
you
are
looking
at
the
right
calendar.
There
are
two
meetings:
it's
just
it's
a
working
session
meeting
which
I
didn't
want
to
preemptively
take
for
package.json,
and
so
we
can
discuss
that
next
week.
A
Oh
yeah
and
we
do
have-
we
do
have
another
calendar
that
I
think
I've
even
copied
it
into
the
the
public
calendar,
but
we
also
maintain
a
calendar
and
I'll
drop
a
link
to
that
soon.
A
That
has
all
of
the
events
that
are
standards
related
events,
so
the
tc39
plenaries,
for
example,
w3c
meetings,
conferences,
TPAC,
the
winter
CG
of
meetings
are
in
there
as
well,
and
that's
just
to
ideally
help
us
be
planful
and
and
if
we're
lucky
avoid
meeting
conflicts
which
are
sometimes
a
plenty
in
this
in
this
space,
let
me
hit
get
shareable
link
copy
link,
and
it
is
here-
and
you
know
maybe
make
sure
that
that
is
actually
sourceable
from
the
readme
on
the
main
on
the
GitHub
repo
too.
A
So,
if
you're
ever
curious
like
when
is
the
next
tc53
meeting
well,
we
got
a
whole
like
a
calendar
for
that.
A
It
also
helps
us,
like
then
think
of
like
oh,
is
there
an
opportunity
for
us
to
co-locate
an
event
with
that
and
just
bring
more
people
together,
so
all
right
super
productive
session.
Thank
you
all
very,
very
much.
Please
file
Atomic
issues
and
tag
them
and
welcome
again
to
our
newcomers
and.