►
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
How
about
that?
Okay,
trying
this
again
hi
everyone?
It
is
time
for
our
open,
JS
standards.
Working
group
meeting
yay
today
is
February
21st,
2023
I'm,
saying
that
because
I'm
recording
this
and
having
to
upload
it
later,
because
the
YouTube
stream
thing
is
broken.
Our
issue
today
is
issue
206
for
today's
agenda
and
there's
really
three
items
on
it.
But
first
let
me
ask
if
there
are
any
public
announcements
or
news
anybody
would
like
to
share.
It's
been
kind
of
a
quiet
couple
weeks,
so
I
personally,
don't
have
anything.
I
usually
do.
B
A
Great
so
I
guess
I
mean
that's
one
thing:
if
anybody
has
questions
or
topics
or
wants
to
learn
more
about
some
of
the
proposals
about
a
five-week
period
to
get
get
caught
up
to
speed
or
die,
poke
around
or
ask
questions
and
then
and
provide
feedback,
but
between
now
and
the
next
plenary,
so
I
don't
think,
there's
been
any
w3c
news.
I
did
have
an
action
item
to
follow
up
with
the
the
w3c's
new
management
team,
virtual
to
find
out
more
about
our
term
length.
A
They
said:
they'd
have
to
get
back
to
me,
so
I
think
there
might
be
some
just
processor
of
like
kind
of
onboarding
and
everything
they're,
not
quite
quite
quite
ready
to
answer
that
question
for,
but
my
takeaway
is
that
we're
we're
still
members
in
good
standing
and
that
they're
not
there's
not
much
more.
We
can
do
at
this
point
from
being
good,
good,
good,
w3c,
members
and
and
supporters.
So
we'll
we'll
wait
to
hear
back
from
them.
C
C
I
I'm,
not
sure
something
stands
out
from
that,
like
we
did
a
bunch
of
design
reviews.
We
closed
a
bunch
of
issues
but
like
no
I'm,
not
sure
off
the
top
of
my
head.
I
can't
remember
something
that
stands
up
like
to
stands
out
to
bring
to
this
group,
and
but
we
do
have
an
actual
face-to-face
in
Tokyo
in
April
and
I'm,
very
optimistic
that
we're
gonna
do
also
like
a
lot
of
productive
work
there
because,
like
you
know,
virtual
face-to-face
meetings
are
nice
and
they're
they're
better
than
the
regular
weekly
breakouts.
C
A
C
A
A
Okay,
well,
I,
don't
think
I
have
any
other
updates.
I
guess
there's
been
a
couple
of
things
on
the
blog
that
are
kind
of
interesting
that
we
like
for
folks
to
know
about
the
the
foundation's
been
really
involved
with
them:
improving
security
for
a
number
of
its
projects.
So
the
the
jQuery
and
node
teams
have
been
releasing
security
work
updates
on
the
blog
so
check
those
out
if
y'all
are
interested.
Otherwise
we'll
move
to
our
regularly
scheduled
agenda.
A
They
haven't
launched
that
nomination
call
just
yet,
but
you
know
it's
never
too
early
to
start
thinking
about
who
you
might
want
to
to
honor,
and
so
just
I
guess.
The
correct
request
out
to
the
group
right
now
is
to
continue
to
think
about
people
that
you
would
want
to
recognize
and
then
two.
We
have
also
asked
the
new
person
running
the
collab
Summit
and
I.
B
A
Claudio
yeah
I
think
it's
Claudia.
Thank
you
so
much
his
running,
the
collab
Summit
and
we
want
to
find
out.
You
know
from
our
work
and
group
here
if
there'll
be
enough
folks
in
attendance
to
maybe
set
some
time
aside,
or
maybe
it's
not
a
work
full
working
group
meeting,
but
an
opportunity
for
a
couple
of
us
from
the
working
group
to
do
some
brainstorming
or
some
collaborate
collaborating
with
with
the
projects
and
with
the
broader
CPC.
A
A
C
A
Okay,
so
we
need
to
put
a
pin
on
that
idea.
Obviously
two,
if
there's
opportunity
for
the
tag
or
for
tc39
to
co,
to
do
something
with
us
when
we're
we're
having
an
event,
we
would
love
to
to
do
that
next
year.
But
that's
why
we
have
that
new
calendar,
the
new
calendar?
Oh
there's
a
public
calendar
for
our
standards,
events
and
it's
it
should
be
I,
think
it's
linked
off
of
the
or
it's
it's
copied
into
the
openjs
public
calendar
too.
A
So
if
you're
subscribed
to
the
open,
JS
public
calendar
you'll
see
also
now
you
know
the
w3cac
meeting
and
tc39
plenaries
and
other
what
the
winter
CG
meetings
and
things
like
that
that
are
groups
participate
in
so
anywho,
so
bringing
it
back
to
to
openjs
World,
though
we
could
have
an
hour
or
two
for
working
session
or
for
presentation
session
to
the
to
the
openjs,
collab,
Summit,
Community
and
I.
Guess
the
question:
is
you
know
what,
if
anybody
feels
like
yeah
I'll?
Be
there?
A
A
All
right:
well,
obviously,
we
got
a
little
bit
of
time
and
we
have
to
find
out
from
Claudio
how
much
time
we
could
potentially
have
so
just
keep
that
in
the
back
of
your
of
your
Noggin
and
we'll
I'll
find
out
a
little
bit
more
I
think
it's
programming
committee
meeting
tomorrow,
all
right,
so
no
no
further
update
there
all
right.
The
main
topic
for
today,
which
I
made
a
commitment
to
and
I'm
pleased
to
share
that
I
have
largely
met.
A
So
after
last
week,
I
said
that
I
would
take
a
a
a
big
hard
stab
at
this
and
reviewing
all
of
our
notes
and
our
comments
from
you
know
previous
sort
of
components
that
we've
talked
through
I
kind
of
took
to
a
took
to
heart.
The
the
call
that
maybe
what
we
needed
to
do
is
break
this
down
into
a
couple
of
different,
concise
guides
and
so
I
I
wrote.
A
I
I
pulled
from
our
draft
the
the
version
of
the
concise
guide,
which
is
the
the
the
guide
to
fixing
a
platform
bug
the
the
kind
of
the
I
am
a
developer.
I
have
run
into
an
issue.
What
is
it
that
I
can
do
about
it
or
what
should
I
do
about
it?
So
the
total
page
it's
about
just
about
a
thousand
words.
So
that's
just
around
three
minutes
for
someone
to
read
so
that
kind
of
fits
the
I
think
the
conciseness.
A
A
I
imagined
it
might
be
nice
to
also
add
a
graphic
in
here
like
just
to
kind
of
illustrate
how
this
is
a
dynamic
problem.
Where
you
know
the
browsers
are
and,
and
the
platform
is
evolving
and
that's
all
updating
user
needs
are
updating
our
developer
tools
and
our
Frameworks
and
all
that
are
updating
constantly
so
I
thought.
A
A
D
I,
like
the
direction
it's
gone,
it's
in
English
rather
than
bullet
point
speak,
which
was
I
thought
the
the
marching
orders.
You
know
when
I
was
editing
it,
but
I
think
this
is
I
like
it
better.
This
way,
I
like
English
hate,
PowerPoint,
speak
so
yeah
I
think
it's
I
think
it's
going
in
the
right
direction.
Definitely.
A
A
That
so
my
friends,
Simon
Peters,
uses
this
a
lot
Simon's
a
big,
his
his
really
big
on
the
what
WG
and
and
and
Mozilla,
and
all
that
so
I
I'm,
not
sure
exactly
how
frequently
but
I
think
it
also
is
very
it's
kind
of
a
helpful.
You
know
distinction
in
a
way
because
you're
you're
there's
there
either
is
a
compatibility
issue
or
there's
an
issue
where
it's
not
clear
what
should
be
yeah.
Oh.
A
B
Because
cc39
has
the
same
thing
right
where
we
like
you,
know,
I
think
we
call
it
like
web
reality,
but,
like
obviously
that's
I,
don't
know
if
that
applies
the
same
for
web
standards,
I
just
yeah
yeah,
as
long
as
as
long
as
I
think
either
the
reporters
or
the
recipients
of
the
reports
are
going
to
know
the
term.
Then
it's
fine
to
Define
it
here
right
but
like
it's,
it's
probably
not
going
to
be
super
effective
to
try
and
introduce
your
new
terminology.
B
B
A
B
A
B
B
A
A
B
A
Then
we
can
that
kind
of
unblocks
us
to
think
about
more
Focus
guides,
for
you
know
like
we
could
say,
concise
guide
to
you
know,
preparing
a
proposal
for
tc39
or
something
very,
very
kind
of
like
concrete,
as
the
next
step.
I
think.
Another
question
that
I
just
wanted
to
get
agreement
on
or
get
thoughts
on
from
the
group
related
to
the
guides
in
general
is:
do
we
want
them?
Where
do
we
want
them
to
live
and
I
was
just
thinking?
A
If
we
follow
the
open,
ssf
pattern,
they've
been
doing
both
they've
been
putting
putting
the
Source
in
a
repo
but
then
also
making
a
page
on
their
on
their
site.
So
people
can
go
find
resources
and
then
that's
one
of
the
places
they
navigate
to
and
I
like
that,
just
as
a
pattern,
because
it
kind
of
provides
more
visibility
for
the
for
the
work
and
then
but
it
keeps
Source
still
on
on
GitHub.
A
A
Well
so
I
think,
then
we
give
y'all.
You
know
the
rest
of
today
or
this
week
to
add
any
more
comments
and
I
will
I,
will
add
links
and
and
refresh
and
and
incorporate
Leia's
feedback
here
and
then
maybe
ideally
next
week
we
can
call
for
a
plus
one
on
a
final
document
and
ship
it
in
what
Debbie,
though
I
guess
March
7th
would
be.
Is
that
our
next
meeting
wow
March,
this
year's
going
so
fast,
March,
7th,
so
cool.
A
All
right,
then,
I'll
move
us
to
our
next
topic,
which
is
also
really
timely.
So
one
of
our
openjs
delegates,
guy
reached
out
to
me
last
week,
I
think
it
was
to
say
you
know
that
the
the
TC
chairs
tc39
shares
would
like
to
get
some
clarification
for
from
us
on.
You
know:
who's
who's,
participating
on
behalf
of
the
openjs
and
sort
of
what
our
goals
for
those
folks
may
be,
and
just
chatting
with
guy.
A
You
know
we
feel,
like
it's
generally
pretty
clear
among
us,
but
it's
not
necessarily
clear
among
the
other
TC
participants,
kind
of
what
we
do
and
what
our
process
is,
and
that
kind
of
thing,
and
so
he's
asked
if
we
can
make
a
little
bit
more
Headway
on
the
on
issue
173,
so
that
the
TC
chairs
have
more
like
that.
They
can
point
to
to
to
understand
again.
A
You
know
when
our
group
is
participating
when
those
folks
are
participating
on
behalf
of
the
foundation
or
in
the
case
that
they
may
also
be
a
member
of
a
organization.
That's
a
a
member
of
the
TC
how
how
how
that
kind
of
squares
up
so
I've
asked
guide
to
come
to
our
our
next
meeting
the
on
the
seventh
and
he
is
able
to
make
time
to
do
so.
So
we
will
see
guy
on
March
7th
to
talk
about
173.
A
But
that
is
well
timed,
quite
frankly,
so
March
7th,
we'll
have
guy
and
then
hopefully
we
can
get
something
to
them
for
for
their
meeting
by
the
end
of
March,
which
last
week
I
had
said
this
would
fit
on
my
plate
in
March
and
so
again,
good
timing,
but
I
guess
that's
a
good
opportunity
to
ask
Richard
and
Jordan
as
well.
You
know,
in
the
intervening
time,
since
you've
kind
of
filled
this
role
for
us
is
there.
A
B
The
position
of
the
standards
group
is
that
our
delegates
are
not
to
withhold
consensus
for
anything
unless
the
standards
group
has
agreed
on
it.
First
and
that's
the
only
caveat
that
yeah
but
beyond
that,
like
I,
mean
guys
participated
in
239
for
a
while.
So,
like
my
assumption
is
that
he
will
continue
to
participate
in
the
same
manner.
A
Looking
for
any
kind
of
guidance,
we
can
provide
on
the
types
of
matters
that
our
team
are
going
to
be
coming
in
and
bringing
in
perspectives
that
they
might
be
bringing
and-
and
you
know
so,
okay
cool.
Well,
we
might
try
and
paper
something
up
a
little
bit
before
the
March
7
meeting
so
that
we
have
kind
of
something
we
can
discuss
and
kind
of
update
together
on
our
our
call
next
time
and
then
hopefully
be
able
to
polish
that
up.
A
You
know
there's
other
things
Richard
or
or
Jordan
that
you
think
would
be
helpful
for
us
to
document
I
mean
one
thing
is
like
a
like:
an
expectation
of
term
I
find
I
find
that
kind
of
hard,
because
if
we
were
to
say
support
one
of
the
members
of
our
community
who
had
a
proposal
that
they
were
championing.
You
know
that
might
happen
within
a
year,
but
it's
more
probable
than
not
that
it
won't,
and
so
it
might
just
be.
B
My
one
I
mean
I
think
that
in
if
an
open,
JS
delegate
stops
participating
like
doesn't
attend
and
has
nothing
to
bring
in
like
it
should
be
fluid
to
be
able
to
not
have
them
be
delegates
and
then
rehab
them
be
delegates
later.
But
if
an
open
JS
delegate
wants
to
continue
attending
it's
seen,
even
if
they
have
nothing
specific
to
talk
about,
it
seems
like
a
good
thing
to
allow
for
that.
A
A
In
terms
of
conversation,
continuing
this
conversation
and
documenting
TC
39
participation
with
with
guy
Bedford,
then
hopefully
buttoning
up
the
concise
guide,
we'll
probably
have
a
little
bit
more
info
on
the
JavaScript
Landy
Awards,
and
that
kind
of
thing
lots
of
things.
So
I
guess
in
the
interim.
Do
you
file
an
issue?
If
you
have
something
you
want
to
bring
up
or
talk
about?