►
From YouTube: OpenJS Foundation Standards Team - May 4th
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
Sorry
y'all,
oh
we're
live
on
youtube,
hey,
hey,
so
we're
live
and
you're
live
great.
Okay,
so
minor
technical
difficulties.
Welcome
to
the
standards
working
group
meeting
on
tuesday
may
the
4th
be
with
you
and
each
of
you
we
are.
We've
got
a
lot
of
stuff
to
talk
about
today,
but
we're
going
to
start
with
announcements.
A
B
A
You
might
be
editing
a
previous
meeting
documents.
Let
me
oh
no!
No,
I
think
oh
yeah
you're
definitely
editing
the
previous
document.
Sorry,
I
don't
see
you
in
there
hold
on
so
minor
issue
with
the
agenda
creation
tool
again
today,
so
joe,
it's
that
second
and
all
that's
it's.
That
second
link
is
the
where
I'm
gonna
take
notes,
but.
A
No
thank
you
for
for
raising
that.
That's
great,
so,
okay,
yeah
so
schedule,
oh
yeah,
the
working
meeting
and
then
the
other
thing,
a
quick
announcement
that
the
w3c
of
which
we
are
a
a
a
member
has
announced
the
the
candidates
for
the
advisory
board
election
so
I'll,
be
sending
that
out
to
our
group.
That's
all
public!
You
can
view
their
statements
and
stuff,
but
and
we'll
want
to
think
about
who
would
like
to
vote
for
and
the
advisory
board
election
coming
in.
A
That's
so
that's
a
fyi
anything
else.
I
think
we're
pretty.
The
foundation
staff
were
pretty
heads
down
on
on
on
the
event,
so
we've
got
some
other
things
that
are
coming
up
as
well,
but
that's
sort
of
like
the
top
priority.
We've
got
like
a
month
to
get
our
not
even
a
month
less
than
a
month.
Wow
june
will
be
here
fast,
cool,
all
righty.
C
D
Hi,
I
am,
I
represent,
google
on
the
board.
I
do
some
standards
work
on
behalf
of
google
or
I
did
my
job
descriptions
changing
a
little
bit,
but
I'm
glad
to
to
be
here.
I've
been
only
for
seven
months.
So
that's
why
I
haven't
been
dialing
in
into
any
of
the
meetings,
but
I'm
officially
back
to
work,
so
I'm
happy
to
jump
in
or
review
or
take
a
look
or
whatever
I
can
do
to
help
in
this
process.
A
All
right
so
on
the
docket
today
we
have
three
items:
we're
going
to
continue
discussing
the
education
and
onboarding
resources
that
we've
been
pulling
together
and
kind
of
what
we
want
to
do
with
that.
As
a
next
step,
we
have
been
talking
about
our
joint
statement
with
with
other
groups,
and
then
we
also
have
been
talking
about,
or
I
should
say
I
have
to
report
on
a
meeting
that
I
had
very
very
very
early
in
the
morning
with
marcos
caceres
from
the
w3c
who's
in
australia.
A
A
A
A
A
As
am
I
about
sort
of
defining
kind
of
some
learning
paths
for
for
folks
looking
to
get
into
this
work-
and
I
think
that's
also
something
that
our
group
could
weigh
in
on
quite
a
bit,
especially
if
we
want
to
make
it
something.
That's
that's
more
general
and
sort
of
well-rounded
and
everything.
So
it
was
a
great
and
very
fun
conversation.
A
I
think,
because
of
the
fact
that
just
there's
a
big
time
zone
difference,
a
lot
of
this
is
going
to
just
carry
out
in
github
and
occasionally
via
the
email
list
so
and
I
think,
there's
also
a
very
real
possibility
that
the
work
that
they
come
up
with
the
tutorials
and
stuff
stuff
that
we
might
want
to
include
in
our
resources
and
our
resources
list.
So
that's
kind
of
the
overview,
but
you
know
I
think
a
lot
of
you
were
excited
about
that
too.
So
you
know
questions
or
anything.
B
E
A
A
A
Culture
as
mike
champion
calls
it
and
kind
of
get
sort
of
the
bigger,
broader
context
of
what
standardization
activities
do,
what
they
mean
and
not
not
necessarily
focus
on
a
specific
organization's
process
or
rules
but
sort
of
like
a
broader
framework
around
it,
and
we've
put
a
call
out
for
resources
that
help
people
understand
that
and
as
we're
pulling
that
in,
I
think
we
kind
of
want
to
figure
out
also
what
to
do
with
it.
Right
like
how
to
curate
that
and
present
that-
and
I
think
that's
really
where
we're
at
now.
A
We
have
an
opportunity
to
kind
of
pull
together,
just
an
mvp
static
website
or
a
page
on
the
openjsf.org
domain,
that
sort
of
pulls
the
stuff
together
or
you
know
we
can
think
of
something.
That's
like
more
complex
and
dynamic
or
whatever,
and
I'm
just
I'm
I'm
curious
what
y'all
would
like
to
see
if,
if
it
were
you
young
newcomer
to
the
standards
world
like
what?
What
would
be
most
like
useful
from
from
your
journeys
and
from
your
point
of
view.
C
F
I
mean
jerry
if
you
were
asking
for
like
opinions
as
to
what
sort
of
content
would
be
helpful.
I
feel
like
it
there's
a
lot
of
different
directions.
People
would
approach
standards
from
or
come
to
it
from
and
for
some
people
they
may
need
an
understanding
of
the
a
deeper
understanding
of
the
thing
that
they're
that
this
that
is
being
standardized,
whether
it's
like
the
javascript
language
or
web
browsers
or
whatever.
F
For
some
people,
they
may
need
a
better
understanding
of
the
constraints
under
which
the
standard
had
evolved,
because
a
lot
of
people
show
up
with
really
a
lot
of
enthusiasm
and
a
lot
of
great
ideas
on
their
own,
but
that
those
most
of
those
ideas
are
often
non-starters
because
of
the
existing
constraints
and
those
constraints
are
rarely
well
documented
and
understood
and
and
then
there's,
of
course,
the
whole
minutia
about
like.
How
do
you
approach
a
contribution
right?
Like
you
know,
tc39
has
its
own
way.
We
try
to
funnel
people
through
to.
B
F
You
know,
and
each
project
and
standard
probably
has
its
own
slightly
different
way
of
of
trying
to
triage
incoming
content
to
make
it
manageable
for
those
maintaining
the
standard
so
kind
of,
like,
I
don't
think,
there's
a
single
silver
bullet.
I
think
there's
just
a
lot
of
facets
that
could
stand
to
be
better
explained
and
documented.
A
B
I
was
going
to
say,
I
think
you
know
as
something
like
this
is
built
out.
The
needs
will,
you
know
hopefully
kind
of
reveal
themselves
in
terms
of
you
know,
whichever
standards,
body
or
whatnot.
You
know
we
can
have
a
way
to
ask
questions
or
faqs
or
something,
and
then
you
know
when
people
do
ask,
we
can
either
update
the
documentation
or
update
an
faq
or
I
don't
know
yeah
I
feel
like
it
might
grow
organically,
but
obviously
you
gotta
cultivate
a
garden.
A
All
right,
I'm
like
trying
not
to
sneeze
on
the
camera.
So
sorry
that
was
me
hitting
my
mute
button
several
times
yeah.
I
think
that
perhaps
in
terms
of
like
organ,
because
these
the
resources
that
we
have
so
far
kind
of
like
like
a
lot
very
different,
some
of
it
is
you
know:
here's
like
here's,
a
list
of
all
of
the
standards,
developing
organizations
and
kind
of
their
areas
of
focus
and
others.
It's
like
you
know,
here's
how
to
read
the
javascript
spec,
and
you
know
that
kind
of
thing.
A
So
it's
those
are
obviously
answers
to
very
different
questions,
so
perhaps
maybe
like
organizing
the
content
in
a
way
that
you
know
thinks
it
tries
to
predict
what
the
question
is
and
then
provides
some
of
the
answers.
That
seems
really
sound.
So
maybe
maybe
that's
a
thing
worth
trying
to
document
is
like
what
what
are
those
questions.
B
C
F
A
Yeah-
and
I
think
it
this
also
seems
very
practical
right
like
because
we
want
to
if,
if
these
specific
groups
like
tc39-
and
you
know
the
and
w3
they've
got
their
documentation
and
down,
and
the
best
thing
we
can
do
is
say
if
you
get
to
the
point
where
you're
ready
to
go
participate
because
you
feel
like
you've
got
enough,
go
read
their
documentation.
Let's
not
duplicate,
you
know
so.
A
C
B
C
A
Yeah
definitely
and
yeah
growing
the
pipeline,
and
also
just
helping
folks
who
you
know
frankly,
there's
lots
of
people
who've
been
in
this
for
a
while
and
still
aren't
sure
which,
which
end
is
up,
because
it
is
very
confusing.
So
I
think
yeah
that
sounds
good,
so
questions
wise,
I
think
people
might
be
asking
like.
Where
do
I
find
info
about
blanks
process
where
blank
is
w3c
or
tc39
or
whatever?
A
F
F
Sometimes
it
is,
but
like
very
rarely,
and
it's
very
tricky
to
explain
to
them
why
their
idea
is
not
valid
or
viable
without
extinguishing
that
enthusiasm
in
the
first
place,
and
I
it
would
be.
I
don't
have
an
easy
answer
for
how
to
preserve
that
enthusiasm
while
and
redirect
it
to
a
better
idea,
but
anything
that
would
help
with
that.
F
That
would
help
people
who
show
up
enthusiastically
with
the
idea
to
like
adjust
their
expectations
and
to
like
push
them
less
towards
make
this
thing
happen
and
more
towards
assume
it
might
not
be
viable
like
let's
get
excited
about
figuring
out.
Why,
like
you
know
something
like
that,
because
I
the
other.
F
F
Let
me
explain
this
basic
of
the
language
or
this
constraint
or
like
this
thing
like
this,
you
know
and
it's
and
it
makes
it
even
harder
to
be
friendly
and
warm
to
these
people,
because
you're
burned
out
by
having
to
do
it
so
much
and
so
kind
of
there's
like
a
double-edged
problem
here.
That
would
be
nice
to
address.
D
Yeah,
I
think
it
just
to
echo
it's
like
setting
expectations,
realistic
expectations
from
both
sides.
You
know
standards
takes
a
while,
and
so
newcomers
coming
in
may
not
sort
of
understand
that
the
length
of
it
all
of
the
constraints
and
then
everything
basically
jordan,
said
so.
That's
something.
We've
seen
on
google
site
as
well
developers
get
really
excited
and
then
there's
so
much
red
tape.
D
They
have
to
go
through
just
to
be
able
to
participate,
and
then
it's
such
a
long
process
that
we
have
internal
issues
in
terms
of
getting
credit
for
the
work
that
they
do.
So
I'm
just
echoing,
I
think,
setting
realistic
expectations
so
that
users
understand
what
they're
getting
into
and
how
to
approach
it.
A
A
C
A
We're
just
working
on
coming
up
with
like
questions
for
that.
We
think
new
people
to
this
world
might
ask
and
kind
of
thinking
about
organizing
information
around
those
questions,
and
then
I
think
we
had
also
decided,
although
I
didn't
record
this,
so
I
should
that
as
an
action
item,
we
will
make
a
repo
for
this
website
project.
F
Yeah
I
mean
for
for
tc39,
there's
a
forum
you
have
to
fill
out
that
basically
says
that
any
contributions
you
are
assigning
any
relevant
patents
to
those
two
ecma
and
you
know
the
effective
license.
Otherwise
is,
I
think,
ecma
has
a
license.
I
don't
actually
know
exactly
what
it
is,
but
it
it's
not
so
much
that
they
don't
work.
It's
that
they
don't
really
apply.
F
I
Is
it's
actually
really
scarce
and
it?
It
means
that
if
there
is
anyone,
okay,
so
so
the
the
specific
context
in
which
this
came
up
was
a
was
a
standard
or
a
specification
that
is
not
under
any
of
the
it's.
Basically
currently
it's
copyrighted
by
a
couple
of
people
and
it's
still
a
widely
used
standard
or
specification
more
like
so
now
when,
when
you
start
working
with
that
spec,
how
does
it
really
work?
I
How
how
so?
I'm
thinking
that
there
is
an
opportunity
here
for
us,
through
a
resource
like
this
or
otherwise,
to
provide
ways
for
people
who
want
to,
for
whatever
reason,
come
together
with
a
standard
or
a
specification
to
to
be
able
to
achieve
that
and
not
cause
issues
for
themselves
or
their
users
or
their
collaborators
or
contributors,
because
it,
my
sense,
is
that
it's
mostly
yeah.
I
A
So
it's
a
question:
that's
a
good
question
for
an
attorney
I
mean,
I
think,
there's
there's
sort
of
the
patterns
that
people
have
been
following
to
sort
of
get
the
ipr
clearance
that
the
member
or
organizations
are
comfortable
with
and
then
there's
and
and
sort
of
understanding
that
and
then
there's
the
other
question
which,
to
your
point,
emily
is
like
I'm
starting
a
new
project.
How
do
I
make
sure
that
I'm
setting
things
up
you
know
properly
from
the
get-go
such
that
people
can
use
the
project
that
I.
A
K
C
H
How
do
we
make
it
simpler
for
folks
to
understand
what
the
spec
is
saying
when
they
don't,
and
the
other
challenge
I
see
is
when,
when
folks
come
up
with
a
proposal,
there
are
high
chances
that
a
similar
proposal
or
the
same
proposal
was
proposed,
say
like
six
years
back
and
was
rejected
for
few
many
reasons,
and
it's
not
easy
to
discover
that
hey.
This
was
proposed
like
a
few
years
ago
and
it
was
discarded
for
these
reasons.
A
A
A
So,
just
because
there's
this
one
other
topic
on
our
agenda
today,
I'll
wrap
this
one
up,
we're
going
to
make
a
new
repo
for
a
website
we're
going
to
transfer
the
current
issue
on
this
topic
over
to
that
repo
and
we're
going
to
continue
to
collect
resources,
so
just
another
call
out
for
if
you
have
favorite
resources,
blog
posts,
etc.
That
help
answer
these
questions
or
videos
or
anything
like
literally
anything
just
adam
adam
and
we'll
we'll
get
them
organized
around
these
questions.
A
A
A
Last
time
we
did
discuss
this
in
private
session
because
we're
it's
a
secret,
not
really,
but
we
want
to
surprise
people,
so
I
think
unless
there's
any
other
business
to
go
before
public.
I
might
then
turn
off
our
live
stream.
So
we
can
talk
about
and
work
on
this
sound
good
anything
any
other
public
business.