►
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
This
is
just
a
weird
bug.
Okay,
it
looks
like
we're:
recording
apologies
to
those
who
like
to
tune
in
for
the
live
stream,
unfortunately,
which
sometimes
we
get
these
weird
bugs,
where
it
doesn't
Grant
necessary
privileges
whatever
that
means.
So
this
is
the
March
21st
meeting
of
the
openjs
foundation
standards
working
group
with
a
smaller
group
today,
because
there
are
some
different
meetings
happening
so
love
those
meeting
conflicts,
but
that's
okay.
We
record
it
so
we
can
catch
up
later
and
we
take
notes
over
at
the
standards
repo.
A
A
A
A
A
If
you're
planning
to
come
to
Vancouver
for
open
source,
Summit,
North
America
and
the
openjs
World
Conference,
then
we'd
love
to
see
you
a
day
ahead
of
time
for
the
collab
Summit.
That
agenda
is
coming
together,
thanks
to
Claudio,
wonder
who
is
wonderful,
I
might
add,
and
you
can
reach
out
to
him
on
slack.
If
you
have
any
questions
about
the
programming
there.
If
you
want
to
talk
about
something
in
particular
with
your
openjs
friends
and
I,
think
that's
good!
That's
that's!
That's
pretty
much!
It!
A
Okay,
cool
speaking
of
which
issue
205
agenda.
Item
number
one
standards,
group
participation
at
openjs
world,
so
I
I,
opened
this
for
two
different
purposes.
One
is
just
to
get
into
our
minds
that
we
often
as
a
group,
have
nominated
good
folks
to
receive
the
standards
Pathfinder
award
for
the
JavaScript
India
Awards
I'm,
not
sure
that
that
call
for
nominations
has
opened
yet,
but
I
think
it's
going
to
go
pretty
quick
once
it
does,
because
we
don't
have
too
much
time
before
the
conference.
A
So
I
just
want
everybody
thinking
about
folks.
Who've
made
an
impact
for
web
standards
in
the
last
year
and
that
we
can
nominate
really
quickly
and
then
this
group
also
takes
the
special
step
of
recommending
to
the
CPC
who
who
we
think
the
award
winner
should
be
so,
let's
just
be
mindful
about
that,
so
that
we
can
move
quickly.
Yes,
Leia
question.
A
C
B
C
A
A
How
can
we
make
this
a
little
just
bit
more
top
of
mind
for
the
projects
when
they're
thinking
about
weighing
in
on
a
standards
question
you
know,
how
can
they
involve
the
group
and
that
the
standards
working
group,
and
how
can
we
be
more
like
present
for
them?
So
my
proposal
might
be
for
us
to
suggest
something
like
that,
as
opposed
to
don't
imagine,
all
of
our
folks
will
attend,
but
just
want
to
get
your
thoughts
on
that.
B
C
A
A
Okay,
next
up
is
issue
190,
and
this
is
the
concise
guide
to
participating
in
web
standards.
If
you
click
into
that
and
you
Mosey
on
over
to
the
pull
request,
which
is
number
209
and
I'll
pop,
that
into
chat.
I
only
had
one
comment
which
was
on
the
some
some
just
miscellany
kind
of
formatting,
tweaks
and
I've
accepted
those.
So
given
this
has
been
open
for
two
weeks,
you
all
approved
it
as
a
Google
doc.
A
B
A
B
C
C
B
A
A
A
Guy
sent
me
an
email
with
some
suggestions
that
I
haven't
been
able
to
just
follow
back
up
on
so
I'm
gonna
request
that
we
table
this
because
I
don't
have
anything
actionable
to
share
with
you
from
between
the
last
time
we
met
and
today,
but
in
short,
we
were
going
to
kind
of
break
this
up
into
a
couple
of
different
things.
One
is
just
a
refresh
of
sort
of
expectations
and
guidance
for
those
folks
who
are
serving
us
as
as
as
delegates
to
different
organizations.
A
Two,
we
had
also
suggested
some
better
language
and
guidance
for
the
projects.
How
to
use
the
standards
working
group
so
that
we
could
send
that
out
to
groups
like
node
and-
and
you
know,
electron
and
all
of
our
impact
projects,
for
example,
and
help
engage,
help
them
engage
with
us
when
they
are
going
to
or
thinking
about
weighing
in
on
a
on
a
standards,
activity
and
three
just
sort
of
better
clarifying
when
those
terms
for
those
folks
would
would
change.
A
A
B
B
B
A
Well,
I'm
in
support
for
sure,
for
a
wide
variety
of
reasons,
and
let's
see
this
has
been
open
for
remember
from
from
a
process,
standpoint
I
think
I.
Think
I'll
it
takes
is
a
consensus
agreement
of
this
group.
Oh
I
should
open
an
issue
to
clean
up
the
working
group
list
because
we
do
have
some
outdated.
A
Think
we
have
Quorum
in
this
meeting,
but
I
think
we
can
gather
it
async,
so
poking
Brian,
Cardell
and
Mike
champion
and
Mike
Mike,
Samuel
and
Smothers,
but
I
mean
I'm
gonna
go
thumbs
up
the
the
pull
request
and
I
guess
that's.
The
action
item
is
for
the
working
group
delegates
to
thumbs
up.
You
know
approve
this
approve
the
pr
and
and
and
then
we
will
we'll
be
able
to
add
layeth,
but
I'm
super
in
support
of
that
and
yeah.
It's.
A
A
Plus
one,
how
about
that?
All
right
next
item
for
today
is
more
of
an
FYI
I
did
spend
about
45
minutes
yesterday,
going
through
the
repo
and
trying
to
clean
up
outdated
issues
and
and
largely
it's
the
meeting
issues
that
get
created
and
then
they're
not
necessarily
closed
unless
we
open
a
PR
with
notes
or
something
like
that
to
close
them.
So
there's
a
PR
on
the
repo.
A
A
C
I
also
I
updated.
The
YouTube
channel
I
noticed
that
we
had
like
a
hundred
videos
stuck
in
streaming,
but
not
in
the
right
playlist,
so
I
moved
and
updated
wherever
I
found
and
buried,
and
then
I
reformatted
the
home
page.
So
if
you
want
there's,
there
is
a
standards
channel
for
those
who
want
to
catch
up.
Oh.
C
B
C
A
Right,
I
guess
moving
onward.
The
last
issue
for
today
is
again
sort
of
more
of
an
FYI.
We're
really
excited
about
this,
though
issue
number
213
as
the
the
secure
the
web
forward,
Workshop
has
been
announced,
and
this
is
one
we've
been
talking
about
in
the
meeting
over
the
last
few
months,
but
we're
finally
we're
talking
to
acting.
A
This
is
a
w3c
workshop
that
we
are
partnering
with
them,
and
the
open,
ssf
and
O
wasp
Foundation
to
have
a
small
w3c
Workshop
in
London
in
June,
at
the
Microsoft
and
half
reactor
space,
we
are
looking
for
people
to
bring
papers
and
for
those
who
are
not
familiar
with
the
w3c
workshop
format.
It's
definitely
not
a
conference
talk,
you
know,
and
it's
not.
The
workshop
is
in
like
bring
your
computer
and
we'll
teach
you.
You
know
how
to
do
something,
but
rather
you
know,
come
with
a
a
problem
statement.
A
Come
with
a
you
know,
an
idea,
a
solution
to
a
problem
or
experience
that
you've
had
some
challenge.
You
have,
with
the
web
platform
present
for
a
short
period
on
it,
like
you
know,
15
minutes
and
then
there's
usually
kind
of
a
group
of
presentations
that
are
relatively
tight
and
focused,
and
then
they
break
out
into
like
working
sessions
where
all
the
participants
come
together
and
have
a
conversation
and
sort
of
I
think
they
call
an
unconference
style
format
and
dissect
into
some
of
the
the
points
raised
by
who
brought
papers.
A
So
it's
a
very
collaborative
experience,
very
high
level
of
you
know
technical
kind
of
conversation.
So
if
you're
a
developer
that
has
had
a
problem
with
security
on
the
web
platform,
this
could
be
for
you.
The
link
to
the
workshop
is
in
the
issue
213
and
we
are
really
Keen
to
get
some
great
content.
Robin
and
myself,
and
a
number
of
folks
from
our
community
and
from
just
adjacent
to
our
community
are
on
the
programming
committee
for
this,
and
so
we're
looking
for
some
great
presentations
and
Robin
anything
additional
on
that.
C
A
Yeah,
it's
a
very
small
space
like
there's.
They
don't
typically
have
huge
Workshop
sizes
anyway,
at
the
w3c
I
think
this
is
kind
of
a
larger
one.
At
sort
of
The,
100
ish
range,
120
I
think
is
like
the
absolute
Max
for
the
space,
so
yeah
anyway,
we'll
be
reporting
on
on
that
as
as
it
a
it
it
it.
It
goes,
there's
a
w3c
slack,
Community
too.
B
Just
as
a
heads
up
I
think
I
may
have
mentioned
this
before
I
will
probably
need
to
submit
a
request
soon
for
the
upcoming
tag.
Meeting
travel
I
haven't
done
it
soon,
because
I
haven't
looked
at
flights,
yet
it's
like
I
I
need
to
book
some
other
flights
first.
So
it's
it's
complicated
and
there's
a
bit
of
a
catch-22
there,
because
I
think
I
need
a
budget
to
file
the
pull
request.
But
if
I
look
for
flights,
I
would
probably
want
to
book
them
soon.
Otherwise,
prices
increase.