►
From YouTube: OpenJS Foundation Standards Team
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
so
it
looks
like
we
are,
live
hello.
Everyone
welcome
to
tuesday
august
24th
session
of
the
openjs
foundation
standards
working
group
meeting.
We
have
a
quiet
group
today
kind
of
getting
some
folks
out
for
last
minute
vacations
and
dental
appointments
unexcitedly.
A
So
good
luck
with
that
joe.
We
start
with
our
announcements,
any
any
announcements
from
you
all
before
I
give
you
my
deluge
of
hey,
remember
this
and
that
and
the
other
upcoming
meetings,
something
cool
that
happened.
A
A
I
don't
that's
surprising
at
all,
and
you
know
hey
jordan.
Do
you
want
to
tell
people
where
they
can
go
check
out
the
agenda
in
case
they're
curious
what
the
what
the
tc
will
be
covering.
B
Absolutely
github.com
tc39
agendas
always
has
up-to-date
and
historical
agendas,
and
you
can
take
a
look
at
what
will
be
talked
about
in
the
meeting
and
10
days
before
the
meeting.
All
the
things
that
are
seeking
advancement
are
supposed
to
be
on
there.
So
if
you
wait
until
then,
then
you
don't
have
to
check
more
than
once
general.
A
Cool
all
right
so
check
it
out,
it's
extremely
thorough.
I
often
go
back
and
look
at
stuff.
She
just,
I
think,
it's
great
just
amazing
record
keepers,
so
yeah
tc39
meeting
next
week
this
week,
just
a
couple
of
things
that
are
foundation
related
so
thursday.
This
thursday
is
the
the
openjs
world
programming
committee
meeting.
A
So
for
those
who
are
interested
in
getting
involved
with
the
conference,
we'd
love
to
have
you
there's
like
just
a
load
of
excitement
around
the
possibility
that
this
could
be
an
in-person
event
and
we've
got
a
lot
of
things
that
we
are
planning
and
I
would
love
to
have
you
another
fyi.
A
Ordinarily,
we
would
have
a
a
a
board
meeting
as
as
the
last
friday
of
the
month
and
but
due
to
vacations
and
absences
we're
doing
that
asynchronously.
A
So
we
won't
have
the
public
board
meeting
as
we
normally
do,
because,
because
folks
will
be
out
but
fyi
on
that
and
then
another
fyi,
because
this
will
happen
before
we.
We
see
each
other
again
here
in
the
standards
group,
if
you're
interested
in
the
book
club,
just
like
my
second
favorite
group,
because
this
is
definitely
my
first
favorite
group,
the
book
club
and
we'll
be
meeting
on
september
7th
and
we're
talking
about
a
couple
of
books
that
you
all
might
really
like.
A
One
is
called
how
to
do
nothing
which
isn't
literally
about
how
to
do
nothing
but
more
about
like
how
to
be
like
focused
and
intentional,
and
the
things
that
you
are
doing
and
kind
of
build
awareness
and
the
other
book
is
braiding
sweetgrass,
which
mike
champion
read
and
we'll
leave
a
discussion
on,
which
is
an
ecological
book.
But
it's
also
about
sustainability
and
like
systems
and
stuff
like
that.
And
so,
if
you
want
to
nerd
out
about
books,
book
club
is
september
7th.
So
there's
that
oh
and
then
after
this
call.
A
A
After
this,
I
think,
that's
all
the
announcements
robin
is
not
here
to
tell
me
what
I'm
missing,
because
she
is
in
she's
on
vacation.
So
sorry,
robin
if
I've
missed
anything
and
you're
watching
this
later
or
now,
cool
anything
else.
Did
that
prompt
any
did
that
jog
any
memory
for
any
of
y'all
about
other
things
that
are
happening,
that
we
want
to
talk
about
announcement-wise.
A
I
talked
with
dom
this
morning
at
the
w3c
and
the
t-pac
planning
is
underway
and
so
they're
really
starting
to
think
about
tpack
sessions.
I
think
our
group
might
want
to
consider
tpack
sessions,
so
we
should
put
that
on
a
future
agenda.
That's
sort
of
another
tangent
thing,
and
so,
okay,
all
right.
So
we
jump
to
our
agenda,
which
is
light.
You've
said
you
have
to
leave
a
little
early,
so
I'd
like
to
start
with
the
the
ed
site
and
there's
just
like
really
two
things
after
the
last
meeting.
A
The
action
was
that
we
were
going
to
kick
off
conversation
with
with
lf
on
getting
started
with
the
creative,
because
we
had
this
like
brainstorm
about.
A
But
the
the
the
suggestion
was,
on
their
part,
let's
get
started
with
sort
of
like
the
brand
identity
and
then
kind
of
go
from
there
with
the
with
the
site
user
experience,
and
so
this
creative
brief
is
meant
to
more
help
us
like
hone
the
brand
identity
piece.
A
I
took
a
first
stab
at
you
know
just
describing
like
the
purpose
and
the
background
and
like
some
of
that
sort
of
stuff,
but
I
think
we
as
a
group
probably
want
to
refine
like
the
perception
section.
So
this
is
where
they're
asking
us
like
what
like
what
kinds
of
insight
can
we
provide?
A
That
might
be
like
really
useful
the
ideas
that
we
want
to
communicate
in
like
the
in
the
brand,
if
it's
a
mascot
or
if
it's
a
like
mark
or
whatever
and
terminology
or
things
we'd
like
to
reference
or
things
we'd
like
to
specifically
avoid
you
know
that
that
sort
of
that
and
then
of
course,
target
audience
and
the
stakeholders,
which
is
something
like
mike
and
we've
all
kind
of
like
been
trying
to
get
as
specific
as
we
can
about
so
anyway,
I
figured
it's
worth
our
while
to
take
a
look
at
what's
here
for
a
few
minutes
and
discuss
and
iterate
a
little
bit,
so
we
can
send
this
back
to
them
and
get
get
started
with
some
examples
and
just
as
a
heads
up
how
they
normally
work
is
like
we
would
send
this
to
them.
A
They
would
come
up
with
a
couple
of
directions
based
on
what
we
say,
and
then
we
go
through
two
or
three
passes
of
iterating
on
like
directions
that
we
like
or
providing
feedback
or
whatever.
So
it's
a
pretty
collaborative
process,
it's
not
like
we're
going
to
give
them
this.
One
document
and
they're
going
to
say:
okay
well
here
it
is
yeah.
C
The
document
looks
detailed,
but
I'm
not
sure
if,
as
you
said,
it
should
just
convey
the
message
for
them
to
come
up
with
the
desired
output.
We
are
asking
we're
requesting
them
for
an
png
and
svg,
but
also,
if
you
decide
to
have
a
landing
page,
it
would
be
great
if
there
are
some
designers
who
can
give
perspectives
and
ideas
on
what
the
landing
page
could
be,
given
that
they
go
through
this
document
and
understand
the
chest
and
what
is
required
from
this
site
definitely
go
for.
That.
D
E
I
was
just
wondering
if
julia
starts
off
has
kind
of
weighed
in
on
on
this.
A
E
Yeah,
I
think,
if
I
recall
correctly,
she's
done
a
lot
of
she's
done
quite
a
bit
of
contribution
to
you
know
like
the
how
we
work
stuff
on
dc39
and
she
also
runs
a
occasional
call
on
like
a
b
testing
in
language
design
and
how
to
make
languages
accessible
to
newcomers.
E
So
I
think
she's
she's
got
interests
in
kind
of
you
know
how
how
how
to
you
know,
process
mechanisms
to
bring
people
into
you
know,
standards
work,
but
also
you
know
kind
of
how
how
you
know
how
pedagogy
combines
with
language
design
to
make
for
learnable
standards
and
systems.
A
It
it
happens
that
I
think
tomorrow
or
thursday,
I'm
gonna
chat
with
her
I'd,
be
happy
to
like
show
her
this
stuff
and
be
like.
So
you
want
to
help.
A
Yeah,
I
think,
but
but
the
how
we,
I
think,
the
how
we
work
page
is
specifically
was
a
source
of
inspiration
for
us
in
the
sense
that
it
was
really
clear
and
trying
to
kind
of
funnel
people
through,
so
that
I
feel
like
that,
should
kind
of
that
should
come
in
here
somewhere.
We
should
reference
it
as
a
thing
we
like
or
a
thing
we
like.
We
want
to
kind
of
strive
for
where
to
put
that,
maybe
under
like
maybe
under
perception.
A
Just
so
it's
like
highlighted,
we
like
and
take
inspiration
from
the
pc39.
A
A
A
My
question
is
like
the
the
two
that
are
listed
right
now
mid
to
senior
web
developers
who
want
to
learn
to
get
involved
in
standards,
development
and
then
developers
currently
participating
in
or
following
standards.
Development
who
need
more
context,
are
those
the
right
categories
or
is
there
a
different
group?
We
want
to
try
and
hit
with
like
v1
of
this.
C
Yep,
I
mean
at
least
to
start
with.
We
can,
if
you
look
around
people
who
are
interested
or
people
who
land
on
this
page
will
basically
be
looking
for
understanding
how
the
standards
work
or
want
to
contribute,
which
I
presume
wouldn't
be
like
absolute
business.
But
there
might
be
exceptions,
but
I
hope
someone
who
reaches
this
page
would
already
have
a
certain.
A
So
that
that
certain
amount
of
background
knowledge
do
we
assume
that
it's
like?
I
know
that
javascript
is
a
standardized
language
and
that
tc39
does
that
work
or
is
it
that
I
know
javascript
is
a
web
standard
and
I
don't
have
any
other
knowledge
beyond
that.
Like
it's
like
it's
like
it,
they,
I
guess
so
so
it's
the
differentiation
between
like
the
system
that
created
it.
C
Yeah,
I
think,
there's
no
harm
in
adding
more
details
about
what
the
process
is
for,
but
still.
D
C
E
C
In
mentioning
that,
and
if
someone's
already
aware,
they
would
probably
just
skim
through
or
escape
through
those
and
get
into
what
they're
looking
for,
I
feel
having
that
landing
page,
to
give
clarity
on
what
this
ed
site
is
and
then
having
a
page
with
like
set
of
links
or
post
that
links
that
take
to
the
post,
which
we
go
and
blog
about.
C
E
Yeah,
I
guess
you
know,
as
far
as
the
you
know,
kind
of
how
much
experience
you
have
at
you
know.
E
I
think
kind
of
one
thing
that
when
you're
learning
about
standards
is
like,
what's
in
scope
and
what's
not
like,
what's
the
difference
between
javascript
and
jquery,
for
example-
and
I
recall
that
you
know-
I
think
it's
maybe
10
or
15
years
ago
now,
but
there
was
an
idea
that
if
we
held
a
tc39
meeting
alongside
you
know
a
w3
meeting
that
might
lead
to
a
bunch
of
of
kind
of
synergy,
and-
and
you
know
we
were
in
plenary
and
and
in
walked
some
folk
and
it
turned
out-
you
know
like
it
became
apparent
that
they'd
just
been
walking
the
halls,
because
they
were
very
interested
that
you
know
they
were
very
concerned
that
the
you
know
web.
E
E
You
know
how
you
know
how
how
can
we
help
like
people
with
those
accessibility
needs?
In
tc39-
and
it
wasn't
immediately
apparent-
and
they
didn't
have
specific
answers,
because
of
course
you
know
they
didn't
know
how
the
standards
processes
worked
and
what
tc39
worked
on
versus
what
w3
worked
on
and
and
they
didn't
they
didn't
have
a
I
think,
arya
was
was
fairly.
You
know
nascent
at
that
point,
and
so
you
know
kind
of
that
that
level
of
of
you
know
bringing
interest
groups
like
that
up
to
speed.
E
You
know
takes
work,
but
it
seems
like
it
seems,
like
kind
of
a
at
least
a
little
bit
in
scope
like
you
know,
you
know
how,
if
you
have
this
interest-
and
you
have
this
expertise
in
you
know,
like
accessibility
concerns,
for
example,
how
would
you
what
kind
of
research
would
you
do,
and
what
would
you
need
to
understand
so
that
you
could
figure
out
what
levers
to
you
know
what
levels
are
available
for
you
to
exert
force
on?
E
So
you
know
I
I
guess
the
answer.
Is
you
know
to
tie
that
back
to
the
thing
you
know
a
a
description
of
like
you
know
it
kind
of
here's
examples
of
how
you
know.
If
you
have
this
concern,
how
might
you
identify
the
standards
bodies
and
whether
or
not
it's
standards
bodies
or,
for
example,
open
source
projects
that
that
are
the
best
place
to
try
to
to
try
to
achieve
the
change
that
you
want.
A
I
like
that,
and
because
I
think
that's
both
perhaps
a
a
target
audience
and
then
also
kind
of
a
stakeholder
group
at
the
same
time,
right
like
because
one
of
the
things
we
want
to
do
is
make
sure
that
this,
the
activities
that
were
like
the
standardization
activities
that
we're
involved
with
are
considering
those
concerns
right
and
and
including
them,
if
it's
accessibility,
your
security,
your
internationalization
or
whatever.
So
I
I
like
the
idea
that,
like
that,
should
be
a.
A
E
You
know
these
these
people
they
had
they
had
practical
experience
with
you
know,
screen
readers
and
with
alternative
input
methods
and,
with
you
know,
the
windows
mechanisms
for
like
making
buttons,
bigger
and
and
and
for
slowing
down
the
the
double
click
mechanism,
and
they
were
finding
that
you
know
like.
Oh
now,
people
are
implementing
their
own
double
click
based
on
set
timeout
with
timeouts
that
work.
E
For
you
know,
and
and-
and
so
there
was
these-
you
know
like
there
were
these
concerns
that
they
clearly
had
and
they
they
could
describe
their
problem,
but
they
couldn't
they,
they
didn't
they.
They
they
didn't,
have
transparency
into.
Oh,
you
know
like
I,
I've
got
this
problem.
Who
do
I
describe
it
to,
but
I,
but
I
also
think
like
that
also
bears
on
the
that
also
bears
on
the
magnetic
idea.
E
Maybe
standards
development
can
be
fun.
It's
never
actually
been
fun
for
me,
but
I
worry
that
you
know.
E
Element
of
like
it's,
the
friends
you
meet
across
along
the
way,
not
necessarily
the
processes
to
get
shot
down,
but
you
know,
but
but
you
know,
I
think,
if
you
go
in
thinking,
it's
going
to
be
fun,
you're
going
to
fall
along
the
wayside
very
soon,
and
I
think
you
know
these
people
they
they
were
coming
in,
expecting
they
had
a
slog
ahead
of
them
to
get
the
changes
they
wanted
and
they
were
there
because
they
they
wanted
a
particular
change
in
mind.
E
A
D
C
Most
of
the
time
we
cross
post
saying
that
hey,
this
is
more
like
a
double
equation
and
folks
in
w3,
like
hey,
you
should
probably
reach
out
to
tc39.
So
there
is
it
it's
a
bit
difficult
or
there
is
no
like
straightforward
line,
saying
that
these
are
the
things
that
belong
to
this
particular
committee,
so
probably
adding
more
clarity
on
that
would
definitely.
A
Cool,
so
I
tried
to
capture
some
of
that
in
now,
just
like
the
the
target
audience
and
a
little
bit
in
the
magnetic
idea
section
about
just
like
solving
difficult
problems
on
a
higher
impact
level,
and
then
I
think
I
think
also
yeah.
A
The
zen
of
lj
harp,
okay,
okay,
anything
else.
We
want
to.
Like
kind
of
add
to
this
brief
I
mean,
I
think,
to
everyone's
point,
where
maybe
you're
not
necessarily
giving
them
enough
to
go
off
of
from
like
a
design
direction
standpoint
we
I
I
did
bring
that
we
liked
the
wisteria
idea
and
the
wist,
and
that
kind
of
thing
that,
like
that,
we
responded,
but
we
just
were
not
so
passionate
about
any
specific
direction,
the
wisteria
p.
I
think
we
also
kind
of
liked
libraries
as
a
concept.
A
D
A
That's
okay,
if
well
so
so
why
don't
we
take?
You
know
the
rest
of
the
week
the
to
if
you
think
of
stuff
like
pop
it
in
there
and
then,
if
by
friday,
I'll
I'll
turn
around
and
send
this
back
to
creative
and
then
I
think
from
there,
they'll
probably
suggest
some
early
sketches
or
either
that
or
they'll
schedule
schedule
a
call
with
us
which
I'll
just
invite
them
to
this
meeting
for
ease's
sake,
okay,
cool!
A
D
A
All
right,
thanks,
see
ya,
so
the
other
thing
that
that
I
worked
on
in
the
interim
of
our
last
meeting
was
getting
him.
45
minutes
templates
going
and
I
could
just
take
45
minutes
I've.
I
pulled
that
and
I
started
adding
some
content
to
it.
A
I
haven't
committed
anything
yet,
but
one
of
the
things
we
were
talking
about
was
kind
of
how
to
organize
content
and
whether
to
just
like
have
a
page
of
listed
links
or
to
to
like
make
use
of
the
like
nested,
markdown
files
and
tags
and
stuff
like
that,
and
I'll
be
honest,
I
think
the
group
originally
was
like.
Let's,
let's
do
more
of
the
do.
A
Latter,
where
it's
a
list
of
links,
but
the
more
that
I
played
with
this
the
more
I
kind
of
liked,
the
idea
of
like
having
each
piece
of
content,
be
a
markdown
file
and
using
tags,
and
so
like
here.
Here's
just
like
I
added
one
from
alan
right
so
using
like
how-to
guides
as
a
category
paper
type
like
it's
a
paper
as
a
category,
and
this
is
kind
of
also
referencing.
That
link
I
sent
y'all
in
in
slack
about.
A
That's
what
it
was
here.
Let
me
copy
that
and
pop
it
in
chat
here
too.
A
So
anyway,
I
don't
know
not
that
there's
anything
really
here
to
see,
but
just
showing
you
the
fact
that
I
I
think
I
think
that
this
I
think
using
the
built-in
sort
of
content
management
system
is
probably
the
way
to
go
actually
for
long
term.
A
But
and
that's
that's,
that's
the
the
link
I
just
sent
it's
thedocumentation.devio.com.
A
A
E
Is
there
a
plan
to
hire
kind
of
a
professional
copy
editor
to
organize
this
stuff
or
what?
What
is
that
you
know
like,
I
guess,
there's
people
contributing
content
and
how
what's
the
plan-
and
I
guess
your
question
is:
do
we
want
to
try
to
slot
things
into
the
right
place
early
or
do
we
want
to
kind
of
gather
content,
and
then
you
know
impose
some
kind
of
structure
on
it.
A
I
I
don't
think
we're
at
the
point
right
now
where
we're
like.
Oh,
yes,
let's
go
like
hire
that
person
today
because
I
don't
think
we're
far
enough
along,
but
I
think
that's
something
that
we
can.
We
can
do
and
pursue,
but
I
also
think
we'd
always
intended
to
let
people
like
share
through
this
site
resources
that
are
helpful
right
and
you
know
so
if
you
know
the
site
launches
and
somebody
publishes
something
or
finds
something.
That's
particularly
useful
and
helps
speak
to
a
question
that
our
audience
has
then
like.
A
A
E
E
But
if
it's
mostly
going
to
be
hey
you're
a
contributor,
why
don't
you
figure
out
where
your
stuff
best
goes
then
having
that
structure
in
place
ahead
of
time
would
make
that
easier
right
and
I,
but
I
do
think
the
the
the
the
the
django
documentation
that
you
found
you
know
seems
like
a
great
structure
to
me
from
from
what
I
can
see
of
it.
But
I
have
a
little
practical
experience
in
this.
A
Yeah,
I
I
don't
have
a
ton
of
experience
myself,
it's
actually
something
I
would
love
to
get
and
the
mdn
team's
feedback
on
you
know
because
that's
another
group,
that's
got
a
lot
of
experience,
organizing
content
and
you
know
I
can
actually
see
them
potentially
helping
out
a
little
bit
with
this,
because
they
also
on
mdn,
maintain
a
lot
of
data
about
specs
and
that
kind
of
stuff,
so
it'd
be
worth
sort
of
getting
their
feedback
too.
E
I've
also
been
really
impressed
with
the
rust
rust
docks
people
and
their
ability
to
kind
of
you
know,
maintain
you
know,
kind
of
parallel
systems
of
documentation
with
good.
You
know
kind
of
linkages
between
them.
A
Yeah,
that's
a
good
good
idea
too.
So
I
mean.
A
I,
and
I
think
that
the
reality
is
there's
probably
gonna,
be
like
a
little
bit
of
both
where
we're
getting
a
lot
of
input
from
the
community
about
what
should
be
there
and
what
information
they
want
and
what
would
be
helpful
and
here's
like
again
like
contributions
of
resources,
we
think
would
be
good
on
one
hand
and
then,
on
the
other
hand,
there's
probably
going
to
be
like
one
or
two
people,
you
know
maybe
a
copy
person,
maybe
a
community
person
who's,
just
like
making
sure
that
you
know
that
that
it's,
it
is
actually
quality
content
that
the
links
work.
A
You
know,
that's
you
know
that's
taking
a
vetting
step
to
make
sure
that
the
content
remains
high
quality.
E
In
that
case,
it
sounds
like
the
low-hanging
fruit
is,
you
know,
get
the
structure
in
there
so
that
somebody
who
wants
to
write
a
how-to
has
a
place
to
put
it.
You
know,
and
somebody
who
wants
to
write
a
theory.
Article
has
a
has
a
place
to
put
that
too,
and
then
you
know
as
if
we
have
some
kind
of
you
know.
Post-Commit
actions
or
you
know
like
review
actions
that
identify
dead
links.
That'll
give
us
some
level
of
protection
against.
E
You
know.
Errors
from
you
know
reorgs,
so
that
somebody
who
does
want
to
come
in
and
reorganize
reorganized
documents
can
can
do
so
without
you
know,
with
with
some
level
of
without
you
know,
worrying
about
breaking
tons
of
things
and
not
knowing.
A
Yeah
that
sounds
good.
I
I
just
like
the
idea
of
there
being
some
like
minimum
viable
structure
to
help
people
like
see
what
we're
trying
to
do,
especially
as
we
get
started
and
and
that
structure
is
not
so
firm
or
so
precious
or
so
integral
that
it
can't
be
changed
by
someone
who
really
knows
what
they're
doing.
A
So
what
what
I
can
do
or
would
do
if
this
would
be
helpful,
is
to
kind
of
continue
on
the
path
of
taking
some
of
the
content.
That's
already
been
submitted
to
us
and
adding
it
up
to
the
site,
like
maybe
starting
a
branch
for
this,
and
we
can.
A
A
Okay,
so
I
think
that's
the
the
the
site
is
really
the
biggest
like
current
activity
that
we
have
the
next.
I
think
thing
to
brainstorm
about
which,
which
I'll
just
make
an
issue
for
this,
and
we
can
talk
about
it
and
at
our
next
meeting,
which
would
it
is
just
t-pac
like
do
we
want
to
have
a
session
at
during
the
developer
days
of
tpack
around
our
projects
and
maybe
invite
some
of
our
projects
to
come,
engage
with
the
w3c
developer
community.
A
I
think
that
would
be
cool
but
and
then
there's
also,
I
think,
opportunities
to
get
them
involved
with
their
resource
site
too.
A
But
I'll
put
that
on
our
agenda
for
next
time,
but
I
guess
this
is
another
point.
If
there's
any
specific,
any
additional
topics,
our
group
would
like
to
cover
or
suggest
at
tpac.