►
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
Okay,
we
appear
to
be
live
on
youtube,
welcome,
youtubians
to
our
meeting
of
the
openjs
foundation
standards
working
group
group.
We've
got
a
smaller
group
today,
no
big
deal,
we
start
with
announcements
as
usual
announcements
for
today
anybody
got
any
hot
news
from
you
know
the
world
or
from
their
project
at
least.
B
I
mean
tc39
was
last
week,
so
a
bunch
of
things
happened.
A
few
proposals
got
stage.
Four
a
few
proposals
got
stage.
One
and
pipeline
operator
got
stage
two.
I
think
that's
yeah
there
you
go
hey
months,
link,
that's
a
good
summary.
A
We'll
pop
that
into
pop
that
into
the
notes.
A
All
right
so
things
to
celebrate,
then
advancements
congrats
to
everybody
who
had
their
work
move
forward
and
thank
you
amanda
for
the
recaps,
as
always,
they're
very
helpful
yeah.
C
Samantha,
if
you
once
you've
published
those,
give
me
a
shout
and
we
can
tweet
them
out.
We
can
still
do
that
as
well.
D
C
A
Awesome
other
news
or
cool
cool
hats
cool
happenings:
there's
a
book
club
meeting
today
at
3
p.m.
I'm
super
excited
to
talk
about
braiding,
sweet
grass
with
the
michael
champion
and
also
how
to
do
nothing
which,
as
I've
said
many
times,
is
like
pretty
much
right
up
my
alley
so
join
us
at
3
eastern,
so
in
just
about
2
hours.
D
Also,
we
have
the
web
directions
conference
happening
from
17
a
lot
of
interesting
talks
and
I
think
it's
one
of
the
very
first
pwa
only
conference
like
a
lot
of
pwa
talks
and
great
speakers
and
awesome
content,
and
I'm
also
speaking
in
that,
like
just
like
running
through
the
web
almanac
chapter
of
pwa,
going
through
the
stats
and
graphs
a
nice
conference.
D
D
A
A
So
if
there's
anything
and
y'all
want
to
bring
up-
or
you
know,
suggest
or
ideas,
or
things
like
that
for
with
the
our
peers
at
w3c
that
that
office
hours
is
coming
up
on
on
tuesday,
the
14th.
A
That's
one
thing
and
of
course
w3c
is
also
gearing
up
for
tpack
in
october,
which
is
going
to
be
here
before
we
know
it.
So,
if
you're
interested
in
either
attending
or
getting
involved
in
any
of
like
the
the
developer
and
meetings
that
that
come
on
with
tpack,
let
us
know
because
be
sure
to
share
that
agenda
too,
with
you
all
as
it
as
it
comes
out.
A
All
right
cool
all
right,
that's
a
lot
of
announcements
that
moves
us
into
our
agenda,
which
is
really
pretty
much
just
focused
on
the
on
the
the
the
web
resource
project
and
that's
kind
of
the
hot
hot
topic.
A
Last
week
we
covered
the
brief
that
creative
services
asked
us
to
fill
out
together
and
we
kind
of
added
to
that
and
suggested
that
we
give
ourselves
basically
the
couple
weeks
between
meetings
to
reflect,
make
any
additional
suggestions
and
then,
if
we
liked
how
it
went,
we
would
just
send
it
back
on
over
to
them.
So
I
guess
let
me
start
by
asking
if
there
were
any
additional
comments-
or
you
know
notes
to
add
to
that
I'll
pull
it
up
for
us
really
quick,
realizing
it's
in
the.
A
Okay
should
be,
let
me
pop
it
in
the
zoom
chat,
real
quick
for
you,
so
zoom
chat's
got
the
link
there.
A
A
But
those
folks
may
not
have
the
the
knowledge
or
the
framework
of
standardization
to
help
them
be
as
successful
as
they
want
to
be
and
may
not
have
all
of
the
knowledge
to
understand
like
what's
in
scope
for
one
specification
but
not
in
scope.
You
know
what
what
is
and
isn't
in
scope
so
that
that
was
our
sort
of
primary
target
for
the
mvp
yeah
and
then
magnetic
ideas-wise.
A
We
had
a
great
conversation
about
the
danger
of
over
commuting
communicating
that
standards
can
be
fun
because
it's
not
alway,
like
lots
of
people,
find
it
fun,
but
it
like
the
goal
in
and
of
itself
is
not
to
have
fun
it's
to
like
make
an
impact,
and
so
that
was
actually
quite
useful
so
that
the
magnetic
idea
was
sort
of
redrafted
from
a
fun
and
enjoyable
angle
to
something
that's
a
little
bit
more
concretely
rewarding
and,
if
not
challenging,
so
those
those
are.
A
If
I
am
not
mistaken,
the
ideas
that
we
kind
of
summarized
last
time
jameth,
I
don't
know
if
you
you
were.
You
were
part
of
that
too.
If
there's
anything
else,
you
want
to
add
to
that
and.
D
Yeah,
so
previously
we
had
this
thought
of
you
know
talking
to
the
designers
and
kind
of
getting
a
landing
page
design.
We
thought
it
made
sense
to
have
a
landing
page
and
then
have
a
link
that
would
have
links
to
posts
or
useful
resources
and
also
over
the
long
weekend
looks
like
derrick.
Did
some
research
on
what
could
our
landing
page
look
like
on
the
slack?
D
There
is
a
thread
that
he
initiated
where
it's
just
an
ideation
phase,
but
he
had
like
a
few
few
many
ideas
on
what
the
landing
page
could
be,
but
I'm
not
really
sure
if
we
were
able
to
talk
to
the
the
design,
the
designers
from
the
other
streams,
if
and
check
if
they
were
available
and
if
they
had
any
ideas
for
the
landing
page.
A
So,
just
to
summarize
really
briefly
the
lf
creative
services
team,
we
we
sent
a
request
for
support.
They
want
to
get
started
first
on
sort
of
like
the
brand
identity
and
then
move
from
that
into
the
other
aspects
of
the
project
which
would
be
you
know
like
the
layout
and
stuff
like
that.
I
do
think
that
those
things
can't
can
happen
in
parallel.
If
we
have
community
support
to
do
it,
but
their
first,
their
first
step
is
going
to
be
to
help
us
with
that
brand
component,
and
then
we
can.
D
D
Yeah,
I
would
hope
to
have
a
placeholder
landing
page
and
like
get
the
rest
of
the
things
in
place
sorted
out
and
then,
once
the
landing
page
design
arrives,
we
could
just
bake
it
and
make
it
live.
A
A
Over
complicate
things
over
over
shoot,
but
rather
start
with
something
that
we
can
expand
on
and
grow.
A
Anything
else
anybody
would
add
to
this
brief.
If
not,
I
will,
I
will
send
it
back
to
the
the
designers.
C
I
would
just
say,
based
on
my
experience,
they
move
very
fast
and
so
yeah
the
more
specificity.
We
can
give
them
the
better
this
you
know.
Unless
because
then
they
can
more
iterate
on
one
idea.
That's
really
great
that
we
feel
like
we
have
a
vision
for,
as
opposed
to
like
throwing
mud
on
the
wall
for
a
variety
of
things,
so
yeah.
D
I
think
just
the
dock
description
would
make
it
pretty
overwhelming
for
the
designers
to
kind
of
get
the
crux
of
the
idea,
and-
and
I'm
sure
we
are
probably
some
of
us
would
probably
meet
the
designers
and
talk
to
them
and
and.
D
A
That
that's
part
of
what
they
want
to
do.
I
think,
as
a
next
step
once
we
send,
this
back
is
to
have
a
brief
like
call.
Maybe
they
can
come
to
our
standards
meeting
or
we
can
get.
You
know
a
smaller
group
of
folks
who
are
available
to
come
talk
with
them,
but
that's
absolutely
that's
part
of
their
process
for
sure.
A
Cool
all
right,
so
this
is
the
brief
then,
and
if
we're
good,
we'll
we'll
send
it
back
and
set
that
time
to
chat
and
rock
and
roll
there.
A
That
feels
good,
okay,
all
right.
So
I
guess
the
other
thing,
and-
and
I
know
this-
a
lot
happened
over
the
weekend
the
holiday
weekend,
but
there
was
some
updates
in
in
slack
and
matthew
were
just
sharing
on
the
the
page
layout
itself.
It
sounds
like
we've
had
one
of
our
community
members
kind
of
come
and
add
some
thoughts
and
some
ideas
in
terms
of
shaping
that
related
to
the
information
architecture
architecture.
A
We
also
talked
about
this
format
last
week
that
and
and
talked
about
whether
we
wanted
to
kind
of
start
to
adopt
that
as
just
a
useful
structure
moving
forward
and
I'll
see.
If
I
can
quickly
find
this
again
in
slack
just
to
refresh
everyone's
memories,
but
there
was
a
a
system
that
the
django
project
used
to
kind
of
break
down
documentation
into
a
quadrant,
which
I
personally
thought
was
just
very
very,
very
helpful,
and
I
thought
it
could
be
useful
for
us
to.
A
Maybe
like
use
this
on
a
basic
level
just
to
get
started,
so
I
just
dropped
it
into
dropped
it
into
our
zoom
chat
here,
but
it
basically
says:
okay,
you
know,
thinking
about
your
readers.
A
What
are
their
goals?
Is
their
goal
to
like
really
get
deeper
context?
Is
their
goal
to
just
like
learn
the
procedure
for
how
to
do
something
and
and
kind
of
using
that
user
goal
based
approach,
break
things
down
into
either
a
tutorial,
a
how-to
guide,
a
discussion
or
a
reference
material,
and
I
again
I
thought
that
was
very,
very
useful
and
that
it
would
be
potentially
very
helpful
as
we
adopt
and
add
new
content
to
our
site
that
we
tag
it.
Okay,
this
is
a
you
know,
a
discussion
item.
D
A
D
That
layout
kind
of
reminded
me
of
doxorus
and
just
pasted
the
length
in
the
chat
so
that
that
tool
kind
of
helps
us
to
create
a
similar
structure
like
what
you
showed
in
the
django
documentation.
D
So
it's
it
also.
Basically,
it
also
gives
us
the
landing
page
and-
and
you
can
scroll
off
from
the
landing
page,
and
it
takes
you
directly
to
the
documentation
page
where
you
have
the
sidebar
with
search
and
it
can
be
tagged
into
categories
and
you
could
click
on
those
and
it
will
reflect
the
resources
related
to
that
just
bringing
it
up.
It
doesn't
mean
that
this
is
the
right
candidate,
but
a
potential
one
for
sure.
A
Yeah
I
like
docusaurus
a
lot
actually
and
that's.
I
have
a
friend
of
mine
who
actually
works
on
docusaurus
and
hence
I'm
a
fan,
but
I
also
saw
it
as
being
maybe
not
necessarily
like
I
also
kind
of
thought
well,
we
should
do
or
a
framework
like
docusaurus
not
like
not
like
both,
because
it
seems
unnecessary
to
do
both.
But
that's
my
two
cents.
D
Absolutely
yeah:
if
we
all
vote
for
this,
we
could
kill
eleventy
and
just
use
this,
but
yeah.
We
can
discuss
further
on
what
our
use
case
would
really,
but
we
are
not
really
sure
where
it's
gonna
evolve
right.
So
eleventy
kind
of
gives
us
that
flexibility
to
have
our
own
design-
and
you
know,
keep
changing
it
as
we
progress,
but
with
docusaurus
we're
kind
of
we
just
have
that
base
template.
That's
there
right,
it's
we
can
extend
but
bit
of
an
effort.
So
just
a
potential
candidate.
There.
A
A
A
Any
other
thoughts
on
docusaurus
or
the
documentation
system
are
we
okay
kind
of
proceeding
with
at
least
some
basic
concepts
of
like
tagging,
and
that
that
will
be
another
sort
of
thing
as
we
start
to
get
new
pieces
of
material
and
how
do
we
categorize
and
and
that
that
could
be
a
whole
topic
for
discussion
at
a
future?
Call
it's
just
like.
Okay,
let's
go
through
all
the
lists
of
materials
that
we
have
so
far
as
this.
How
do
we
categorize
it.
D
And
I
would
like
to
order
it
to
be
more
like
how
dev.2
dev2
is
like
anybody.
Could
you
know,
come
and
suggest
and
add
you
know,
content
to
it
or
probably
it
could
also
be
a
simple
edit.
This
page
link,
which
kind
of
takes
it,
takes
us
to
the
github
repository
for
that
particular
markdown
file
and
folks
can
edit
or
add
more
links.
A
You
know
open
an
issue
or
open
a
pr
and
say
you
know,
add
such
and
such
reference
and
like,
let's
just
do
it
that
way
to
get
started
and
then
maybe
add
things
like
commenting
or
additional
context
for
that
resource
later.
C
A
Cool
right
well,
it
sounds
like
there's,
probably
no
more
we're
happy
with
the
that
framework.
For
now
we
can
kind
of
keep
evaluating,
as
this
goes
on
sticking
with
docus
or
sticking
with
11t
or
moving
to
something
that
allows
us
to
do
a
little
bit
more
later.
We
have
creative
services.
Brief
that
we'll
send
off.
I
don't
know,
I
mean
what
else
on
this
particular
project
at
the
moment.
A
Do
we
feel
we
want
to
dive
into,
because
I
think
we've
we
finally
kind
of
got
it
very
action
focused
which
is
awesome
unless
there's
more
stuff
and
there's
more
content
that
people
have
found
recently,
which
is
always
possible.
C
A
Yeah
right
now
it
feels
like
it's
the
idea
and
it's
the
name
that
we
got
most
excited
about,
but
it
it.
It
still
may
not
be
like
the
right
thing,
and
I
think
you
know,
even
in
slack
derek,
had
suggested
something
was
a
little
bit
more
concrete,
which
is
a
lot
at
least
more
useful
to
people
who
are
not
us.
C
A
Yeah,
I
I
think
I'm
leaning
more
toward
we
pick
something-
that's
very
descriptive,
but
like
there's
something
in
the
brand,
that's
a
nod
to
like
the
creative
part
and
and
the
ideas
that
we
liked
and
responded
well
to
here,
were
you
know
the
idea
that
it's
this
is
a
resource
for
growth.
It's
a
resource
for
education
and
so
sort
of
like
the
gardening.
C
A
A
All
right,
so
I
think
that's
it
on
this
topic
there's
I
have
a
somewhat
long
standing
to
do
to
wrap
up
142,
which
was
still
tagged
on
the
agenda,
but
I
meant
to
take
it
off
so
unless
there's
other
business
today,
I
think
we
are
we're,
probably
good,
actually
any
other
business.
A
Shaking
the
head
now,
okay,
in
which
case
we'll
remind
everyone
to
go,
check
out,
hemant's
notes
that
summarize
all
of
the
excitement
from
the
last
tc39
meeting
just
of
last
last
week,
so
fresh
off
the
presses
so
give
give
that
a
look.
Also
encourage
you
if
you're
watching
today
and
you're
interested
in
this
kind
of
stuff
join
us
in
our
slack
channel,
and
you
you
too
could
pontificate
on
what
we
name.
A
This
website,
which
is
our
favorite
pastime
and
get
of
course,
updates
on
things
like
the
office
hours
or
other
standards
related
events
that
are
coming
up,
but
and
also
on
himans
talk
that
will
be
coming
up
soon.
So
I
think
I
think,
that's
all
I
got
anything
else.
Y'all.