►
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,
hi,
everyone
welcome
to
the
tuesday
april
13
re
edition
of
the
standards
meeting.
We
moved
from
last
week
to
this
week
due
to
a
schedule,
conflict
and
stoked
to
see
this
worked
out
for
everybody
from
the
schedule
perspective
announcements
as
usual,
we
start
with
there
were
a
couple
from
earlier
robin.
Do
you
want
to
share
a
couple
earlier
to
share
the
lyft
scholarship.
B
All
right
right
today,
the
linux
foundation
is
offering
scholarships
for
training
and
certification
across
the
whole
catalog
of
content.
But
for
us
it
also
applies
to
our
node.js
training
and
certification.
So
that's
pretty
cool.
So,
if
you're
interested
interested
in
that
go
check
it
out,
we
did
a
blog
and
tweeted
from
openjsf
as
well.
A
Other
quick
announcements,
obviously
we
are.
We
are
the
standards
meeting
so
yeah.
I
was
usually
I'm
like.
Oh
there's
a
program
committee
meeting
on
thursday
for
openjs
world
kind
of
moving
into
the
topics
of
like
execution
for
breakouts
and
like
how
we
want
to
handle
slack
and
q
and
a
and
stuff
with
the
speakers,
because
we
should
be
announced.
We've
sent
out
announcements
to
the
people
we
selected,
which
so
that'll
all
be
live
on
the
website
here
in
a
week
or
so
so
do
come
to
that
if
you're
interested.
A
The
other
thing
that
I
shared
in
slack
this
morning,
which
is
cool
the
w3c,
has
a
this-
is
obviously
very
relevant
to
our
interests.
The
w3c
has
a
new
spec
editor
community
group
that
they
have
opened.
I
am
super
jazzed,
it's
chaired
by
marcos,
caseros
who's,
the
author
of
respec
and
bike
shed,
which
are
two
awesome,
spec,
editing
tools
and
the
focus
of
this
community
group
is
on
like
tutorials
and
mentorship,
and
you
know
just
things
that
you
might
need
or
benefit
from
in
order
to
be
a
great
spec
editor.
A
So
I'm
I
think,
wow!
That's
awesome!
That's
certainly
something
that
I
think
we
want
to
support,
and
so
I
encourage
you
all
if
you're
interested
to
go,
join
that
community
group.
It's
open
to
anybody
too.
So
there's
that
and
there's
also
a
new
charter
out
for
the
web,
editor
working
groups,
if
you're
interested
in
like
document
or
text,
editing
or
anything
like
that
on
the
web.
The
w3c
has
this
new
working
group
charter
out
as
well.
A
Yeah,
that
is,
that
what
was
was
there
any
there?
No
there
was,
there
hasn't
been
a
tc39
meeting
since
the
beginning
of
march,
so
we're
we're
good
on
that
front.
Unless
I'm
missing
any
richard.
Am
I
missing
one,
no
cool
cool,
and
I
also
want
to
welcome
hemanth
here
from
tc39
hello,
who
writes
all
of
the
awesome
like
recaps
of
tc39
meetings,
and
thank
you
for
joining
us.
A
All
right
cool
moving,
then
into
our
into
our
topics.
For
today.
First
up
we
have
issue
132
on
our
repository,
which
is
joint
statement
on
open
source
and
standards
with
the
w3c.
So
if
you'll
recall,
we
talked
about
this,
you
know
as
part
of
a
like
further
alignment
with
the
w3c.
What
are
some
things
we
can
be
doing
to
help?
A
You
know,
learn
from
that
community
and
to
help
support
that
community,
and
vice
versa,
and
one
of
the
things
that
we
thought
would
be
great
would
be
to
sort
of
express
more
of
our
intent,
and
so
that's
something
that
robin
is
leading
and
hopes
to
kind
of
have
something
to
share
or
state
more
publicly.
But
she
wants
our
feedback
and
our
input
on
this.
So
take
it
away
robin.
B
Yeah
hoping
to
have
more
of
a
working
session,
and
I
think
if
we
have
a
joint
statement,
it
could
be
something
that
we
start
with
w3c
and
then,
as
we
get
something
we
like
and
that's
harmonized.
We
could
take
it
to
some
other
standards
groups
as
well
and
talk
about
sort
of
our
shared
principles
and
a
pledge
at
our
conference
on
june
2nd.
So
that
is
sort
of
around
the
corner.
B
Some
things
that
I
think
that
we
all
who
work
in
standards
and
open
source
may
be
super
obvious,
may
not
be
obvious
to
the
outside
world,
who
aren't
tracking
all
the
great
work
happening
in
the
community.
So
thinking
if
we
could
have
a
little
bit
of
a
brainstorm
working
session
on
some
sort
of
key
shared
principles
that
we
have
between
open
source
and
open
standards
and
how
they
work
better
together
and
how
the
communities
overlap
and
how
we
can
grow
sort
of
that
next
kind
of
almost
like
the
pipeline
and
next
generation
of
people.
C
I'd
be
happy
to
join
that
working
session,
but
also
we
could
start
to
you
know
collaborate
on
a
document
or
something
if
that
was
of
interest.
B
Yeah
that
makes
a
lot
of
sense
yeah.
I
said
I
don't
know
if
it
makes
sense
to
have
a
separate
working
session
to
sort
of
start,
brainstorming,
some
themes.
Now,
if
we
see
any
any
sort
of
obvious
areas,
let
me
see.
A
I
think
one
of
the
obvious
areas
is
in
like
the
creating
inclusive
communities
like
that,
like
there's
a
lot
to
be
shared
and
learned
from
and
and
we
already
kind
of,
are
seeing
spaces
where
the
communities
are
getting
together
and
and
and
workshopping
things.
There's
also
like
the
educational
thread
of
like
making
sure
people
understand
the
value
of
open
source
and
the
value
of
standards
and
and-
and
so
it
seems
like.
Those
are
easy
wins.
If
you
will.
B
D
B
I
think
I
had
yeah,
I
was
sort
of
I
actually
had
simplifying
in
my
sort
of
my
own
personal
brainstorm,
which
I
I
think
again
it's
when
joey
talked
about
the
educating
piece
too
and
with
what
you
were
talking
about
yeah,
so
how
to
read
how
to
understand
what
was
that
third
piece
you
mentioned.
B
D
D
So
I'm
running
this
video
cast
called
with
us
where
we
pick
up
parts
of
this
pack
and
try
to
read
it
and
give
some
code
examples
and
then
try
to
iterate
through
the
spec.
Again,
that's
just
an
effort
to
start.
We
have
picked
up
the
ecmascript
specification.
D
B
I
know
it's
been
sort
of
a
long-standing
effort
right
in
a
variety
of
ways.
D
Some
of
the
interesting
pieces
I
have
observed
is,
I
think
I
saw
it
in
one
of
the
node
words
the
way
they
made
the
github
projects
open,
where
they
had
all
the
milestones
and
roadmap
out
in
the
public.
Where
people
could.
You
know,
comment
on
the
issues
and
it
which
kind
of
helped
them
to
prioritize
what
features
that
folks
are
looking
for,
and
the
project
board
and
the
milestone
the
roadmap.
D
Everything
was
open
and
folks
could
see
it
and
they
got
a
better
idea
on
where
the
project
was
heading
next
and
thereby
they
were
able
to
contribute
more
meaningfully
on
what
they
felt
the
the
problem
was,
and
what
were
they
that
helped
to
prioritize
the
solutions
too.
B
A
Other
things
we
would
want
to
highlight-
I
mean
I
guess
in
terms
of,
and
obviously
we're
this
as
a
shaping.
Some
of
these
ideas
into
a
statement
means
necessarily
that
it's
going
to
be
kind
of
high
level,
but
but
I
think
maybe
there's
other
like
themes
we
can
speak
to,
and
let
me
just
ask
that
I
mean
dramatically
when
y'all
think
about
open
source
and
open
standards
and
being
going
together
like
robin,
says
motherhood
and
apple
pie
or
two
sides
of
the
corn,
a
coin
or
peanut
butter.
Jelly
or
you
know
whatever.
B
E
And
that
I
think
that
the
the
stakeholders
in
the
in
the
in
the
standards
process
include
not
just
the
industry,
stakeholders.
A
E
Not
not
just
you
know,
corporate
entities
within
the
industry.
F
F
Most
of
the
people
participating,
are
industry
in
one
way
or
another
and
are
effectively
being
paid
to
participate
and
are
there
representing
more
or
less
some
amount
of
corporate
interest?
And
it's
I
don't
know.
What
really
is
the
lesson
to
take
away
from?
Oh
the
experience,
but
but
it
took
me
a
while
to
realize
that
some
people
are
more
equal
than
other
people
and
that
in
order
to
to
to
really
fit
in
and
to
make
make
a
good
positive
effort
in
standards
work.
D
Absolutely,
and
in
contrast
to
that,
if
we
can
look
it
to
look
into
the
tc39
community
process,
we
also
have
this
concept
of
invited
experts
right.
So
it
need
not
be
that
they
are
part
of
the
paid
members
group
for
the
the
tc39
itself.
The
ecma
script,
the
foundation,
but
rather
they
can
be
like
an
invited
expert,
given
that
they
had
an
a
good
proposal
to
present
and
they
have
a
champions
for
it.
D
They
could
be
invited
to
the
standard
body
in
in
the
meetings
and
they
could
be
part
of
the
presentation,
even
though
they
are
not
part
of
the
paid
members.
Clan.
A
You
know,
and
I
also
kind
of
wonder
I
have
to
kind
of
go-
do
some
like
historical
digging
but
to
what
extent
open
source.
Actually,
I
think,
probably
answers
a
lot,
because
my
first
recollection
of
invited
experts
at
w3,
not
w3c
at
tc39,
was
from
jquery,
and
you
know
I
like.
I
think
that
that's
a
way
that
the
open
source
community
has
influenced
standardization
activities
for
the
better.
You
know
by
helping
them
to
open
up
doors,
to
invited
experts
who
aren't
necessarily
backed
by
megacorp
dot
inc.
A
That's
interest,
that's
a
great
and
interesting
question.
I
think
standardization
people
would
say
absolutely
not
that
they
have
way
more
neutrality
because
of
the
formality
of
their.
B
B
G
Right
right,
yeah,
sorry,
I'm
late
last
track
time.
What
is
there
a
draft?
I
could
look
at
to
see
what
I've
missed.
B
B
B
B
We've
talked
about
sort
of
being
sort
of
that
invited
expert
like
emily,
often
and
others
are
sort
of
these
invited
experts,
and
maybe
that's
where
a
lot
of
the
open
source
folks
have
contributed
back
as
opposed
to
being
sort
of
one
of
the.
Where
were
you
talking,
the
mega
corp
participants.
C
B
G
How
about
how
they
complement
each
other?
Have
you
talked
about
that,
like?
I
suspect
that
standards
are
somewhat
more
approachable
by
end
user
types
than
you
know
code,
but
you
need
end
users
in
the
conversation
as
well
as
implementers.
In
the
conversation.
D
Yes,
from
the
again
going
back
to
the
tc39s
perspective,
we
we,
when
we
get
consensus,
it's
it's.
It's
obviously
like
we
have
the
implementers
as
well
as
the
champions
or
folks
who
have
proposals
who
might
not
be
implementers.
Sometimes
they
are
too,
but
that's
like
the
crucial
points
that,
because
they
would
they
could,
they
could
foresee
a
few
things
that
a
champion
or
a
guy
who's
presenting
might
have
missed
based
on
their
experience.
D
They
would
say:
hey
this
might
cause
an
issue
or
this
the
whole
idea
is
not
to
break
web
right,
so
there
are
again
cases
where,
even
after
all,
folks
being
vigilant,
there
are
a
few
cases
where,
for
some
of
the
proposals
they
did
break
and
it
was
amended
quickly.
But
the
implementers
would
have
insights
on
things
that
folks
who
are
non-implementers
might
not,
and
they
would
say
hey
this
might
be
a
performance
bottleneck
or-
and
they
might
say
hey.
D
This
is
not
really
feasible,
given
these
constraints
and
and
unlikes,
and
the
the
interesting
part
that
I
normally
hear
about
when
in
public
is
like
the
fundamental
questions
that
people
ask
hey.
I
have
an
idea
of
what
a
proposal
and
then
how
do
I
go
about
it?
Then
they
learn
that
hey
there
is
this
set
of
members
who
are
part
of
the
community
who
who
get
the
you
know,
ability
to
vote
for
proposals
and
there's
this
meeting.
D
That
happens
where
there's
this
consensus
that
is
being
asked
for,
and
we
arrive
at
a
concern
saying
that
hey
do
we
approve
for
this
proposal
to
go
from
a
stage
say
one
to
two
unlikes
and
that's
that
that
feels
like
a
bottleneck
for
a
few
minutes
saying
that
hey,
I
do
have
an
idea,
but
how
do
I
get
it
in?
D
Should
I
just
go
ahead
and
create
an
issue
or
we
do
also
have
a
a
repository
which
is
more
like
a
template
for
proposal,
which
you
can
fork
and
fill
in
your
proposal
details-
and
we
do
have
this-
this
discus
discussion
forums
where
people
would
go
ahead
and
post
their
ideas
and
tag.
D
It
as
potential
proposals
and
some
champion
might
say:
hey
I
like
this
idea
or
most
of
the
time
the
discussions
would
be
long
saying
that
hey
does
this
idea
really
work,
or
most
of
them
might
have
appeared
in
the
past,
and
there
might
be
references
saying
that
hey
this
is
why
it
didn't
work
and-
and
some
champion
might
agree
upon
that
hey.
I
would
like
to
vote
for
a
champion
for
this
idea
and
that's
when
it
kind
of
kicks
into
the
process.
D
So
a
few
few
many
folks
feel
that
there's
a
bottleneck
of
entering
into
this
era.
It's
like
the
channel,
where
I
have
an
idea,
but
how
do
I
go
about
it
like
that?
That
kind
of
is
is,
is,
is,
is
kind
of
laid
out
in
the
in
the
site
where
we
talk
about
how
the
process
works
and
all
of
it,
but
it's
not
clear
for
everyone
and-
and
I
think,
giving
more
clarity
on
such
things
would
be
useful
for
a
wider
set
of
audience.
B
A
I
think
that
actually
touches
a
lot
on
one
of
the
things
that
we
have
identified
as
a
goal
for
the
standards
working
group
this
year
is
to
kind
of
help
with
the
proposal,
feedback
and
discussion.
That
seems
like
super
connected
and
matthew
also
made
me
think
about
the
fact
that,
like
in
open
source,
that
is
a
fairly
clear
process.
You
know
like
oh
I'm
using
this
library,
and
I
found
the
bug
or
I'd
like
for
it
to
do
this.
A
It's
a
archaeology
journey,
if
you're,
if
you're,
trying
to
do
trying
to
figure
out
what
that
means
for
for
a
standard,
yeah.
B
B
A
Robin
will
follow
up
with
a
draft
all
right.
So
next
topic
issue
number
130.
A
A
We
identified
this
as
an
opportunity
for
our
standards
working
group
to
make
a
difference,
because
lots
of
sdos
may
have
their
own
process
tutorials
or
resources,
but
there's
not
really
a
great
set
of
resources
that
have
been
curated
to
help.
People
generically
understand
like
what.
A
What
is
this
whole
landscape
all
about,
and
we
want
to
pull
some
of
those
things
together
to
help
new
developers
who
may
be
learning
about
this
whole
system
that
affects
their
livelihood
from
like
a
just
sort
of
informational,
getting
started,
dipping
your
toes
in
the
water
standpoint
and
hopefully
find
the
common
grounds
across
lots
of
different
orgs
like
ecma,
and
what
wg
and
w3c
and
so
on
so
forth.
A
So
we
have
put
out
a
call
for
everyone's
favorite
things
like
if
somebody
were
to
ask
you:
where
would
I
go,
learn
like
what
would
you
share
with
them?
So
that's
one
part
of
the
brainstorm
and
the
second
part
of
the
brainstorm
is:
what
do
we
want?
A
What
like
do
we
want
to
make
a
web
page
for
this
information
like
how
do
we
want
to
present
it
and
contextualize
it
for
people,
so
derek
and
myself
have
put
a
couple
of
things
on
the
issue
so
far,
but
this
is
a
this
is
a
time
of
link
sharing
a
time
of
you
know
if
you
like
yeah.
What
would
we
want
to
in
an
ideal
world
say
here,
new
person
is
our
art
gallery
of
standards,
crap.
D
That's
that's
very
interesting
question,
so,
if
you
for
most
of
the
folks
out
there
like
twitter,
is
some
kind
of
the
main
source
where
they
just
follow,
hash,
javascript
or
tc39
and
try
to
you
know,
get
the
updates,
but
having
a
one
page,
which
is
more
like
a
showcase
of
all.
These
entities
would
be
very
interesting
as
a
part
of
the
tc39
educators
group.
We
had
this
twitter
handle
called
standards
in
two
minutes
where
we
were.
D
The
idea
was
like
or
is
to
have
a
post,
which
should
be
like,
say,
500
words
or
less
and
has
been
minimal
code
examples
of
a
particular
proposal,
which
is
a
stage
three
or
greater
and
would
explain
the
proposal
in
simple
terms
and
would
give
an
code
example
or
a
sample
saying
that
hey.
This
is
how
the
proposal
makes
things
better
and
then
we
would
go
ahead
and
share
it.
So
the
the
things
that
this
account
is
tweeting
is
across
the
board.
It
might
be
some
dev
to
our
article.
D
D
We
have
es5
es6
when
it
was
called
so
now,
it's
more
like
yes,
28,
2018,
2019
and
2020
likes
and
saying
that
these
are
the
new
things
that
came
in
as
part
of
as2020,
for
example,
and
these
are
how
the
code
snippets
for
each
of
these
features
look
like,
and
this
is
what
is
it
about,
but
that's
more
about
educating
on
the
features,
but
how?
How
would
one
contribute
to
the
to
the
proposal
itself
or
how
does
the
the
life
cycle
of
a
proposal
looks
like?
D
We
do
have
things
like
that
on
the
dc39,
the
the
main
website
itself,
but
I
I
feel
taking
it
as
an
use
case
and
trying
to
explain
it
in
a
quick,
maybe
a
five
minute
or
less
of
a
video
and
and
giving
an
example
would
would
reach
a
wider
set
of
audience.
I
presume,
as
of
today,
we
have
a
huge
page
which
talks
about
each
of
the
stage.
What
is
the
requirement,
and
at
this
particular
stage,
is
it
production
ready
at
this
particular
stage?
D
We
are
like
seeking
for
feedback
from
developers
and
at
this
particular
stage,
it's
under
a
flag
and-
and
it
has
a
lot
of
details
in
it-
it's
I'm
not
saying
that
we
don't
have
enough
documentation
or
content.
We
already
have
all
of
it,
which
is
pretty
good,
but
how
do
we
simplify
it
and
increase?
The
radius
of
reach
is
something
that
we
need
to
think
through.
A
Cool
muted,
I
think
about
a
lot
of
like
the
standards
and
two
minutes
stuff.
A
lot
of
like
the
tc39,
like
just
education,
like
your
work,
you
know
is,
is
really
helping.
People
get
the
what
and
that's
kind
of
what
they
subscribe
on
twitter
to
the
hashtags
and
stuff.
But
I
think
in
some
cases
what
is
missing
is
the.
Why
or
the
how
and
that's.
A
I
think,
our
group's
intent
to
help
answer
more
because
there's
this
growing
question
of
like
well.
Why
should
we
do
x,
y
or
z
project
as
a
standardization
activity?
Why
not
just
do
it
in
github
super
legitimate
question?
If
you
don't
understand
the
purpose
of
a
standardization,
you
know
activity
or
you
just
haven't
been
introduced
to
it,
and-
and
I
think
I
don't
have
the
book
with
me
right
now,
but
there's
this
there's
etsy
put
out
this
like
mega
collection
of
slides
and
materials.
A
So
so
you
know
I'm
kind
of
like,
and
it
was
also
very
like
skewed
to
the
etsy
point
of
view
of
the
world,
so
the
question's
like,
what's
what's
the
view
of
why
and
how
that
encompasses,
tc39s
work
that
encompasses
w3c's
work
so
that
people
can
go.
Oh
okay,
this
makes
sense
to
me
and
I
now
I
want
to
get
involved
in
blah.
B
I
mean
yeah,
I
mean
this
team
could
create
a
custom
initiative
right
for
like
a
one-stop
shop,
it
doesn't
have,
it
could
be
under
open
js
or
it
could
be
broader
than
that.
So
I
mean
totally
open
to.
However,
this
group
thinks
it
would
be
most
useful.
A
A
I'm
confused,
and
so
what
I've
been
chasing
ever
since
then
is
sort
of
like
the
view
that
helps
make
that
this
mess
make
more
sense,
and
I
don't
and
and
like
help
somebody
sort
of
like
find
the
onboarding
path
into
that
morass
of
stuff.
D
This
is
the
visualization
is
great,
because
the
the
most
common
question
we
see
on
the
discussion
groups
is
hey
this.
This
is
a
good
thing,
but
this
is
not
really
part
of
dc.
This
is
more
like
a
w3c
thing,
so
you
should
probably
go
to
here
and
put
your
proposal.
So
at
the
entry
point
few
many
folks
would
be
confused
that
hey.
Where
do
I
put
this
proposal?
Does
it
say
I
have
to
enhance
fetch?
D
Okay,
that's
the
fetch
api
go
to
w3c,
or
is
it
pc39
like
so
some
few
many
folks
get
confused
of
the
entry
point
itself
on
which
in
a
working
group
or
a
standard
committee
that
they
need
to
express
their
thoughts
and
opinions
towards.
A
I
would
love
to
have
a
website
for
people
like
that.
We've
we
maintained
as
as
the
standards
wg
like,
and
maybe
it's
linked
off
the
openjs.org
site
which
we're
doing
something
like
that
for
jslandia.
So
it
feels
like
just
kind
of
wash
friends
repeat
the
template
and
bada
bing
bada
boom.
We've
got
a
website
that
we
can
add
to
that.
That
I
think,
would
be
a
nice
like
easy
way
to
get
started
if
we
have
things
that
we
want
to
share.
I
don't
know
other
thoughts,
though
mike
samuel
richard
mike
champ.
A
A
I
guess
the
question
is
like:
how
much
do
we
need
to
can
can
do
we
need
to
like
contextualize
it
all
or
can
we
just
say
here
is
a
list
roughly
categorized?
You
know
if
you're
looking
for
information
on
this,
try
these
links
and
that's
how
we
get
started.
I
don't
know.
B
Yeah,
I
think
you
don't
let
like
say:
don't
let
perfect
get
in
the
way
of
good
and
start
with
something
you
know
start
with
something,
but
I
think
the
most
important
thing
is
you're
right
to
to
curate
it.
So
it's
simplified
a
little
bit
and
then
open
to
have
contributions
from
outside
this
group
as
well.
So.
G
It'd
be
probably
useful
to
to
think
about
what
problem
it
solves
or
what
the
you
as
user
avatar
is,
or
you
know
what
what
the
you
know.
Users
user
story
is
all
the
stuff
we
used
to
talk
about
at
microsoft,
eh
robin
you
know
just
so.
We
have
a
fairly
concrete
idea
of
who
the
target
audience
for
this
is
so
it
doesn't.
Just
you
know,
get
get
overwhelming.
E
I
wonder
whether
I
know
joe
has
done
has
organized
an
awful
lot
of
office
hour
kinds
of
things,
and
I
wonder
whether
using
this
you
know
kind
of
having
a
feedback
loop
between
some
kind
of
office
hours
where
we,
you
know
some
people
answer
standard,
related
questions,
and
we
use
that
to
update
kind
of
you
know
these
explanatory
things,
and
maybe
they
also
channel
people
who
have
further
questions
to
the
office
hours.
I
wonder
whether
that
would
be
worthwhile.
B
And
I
think
joe's
I
mean
joe.
Your
goal
was
also
to
help
diversify
our
participants
too,
and
maybe
we
partner
with
a
university
or
something
like
that
to
bring
in
you
know
a
pipeline
just
just
like
sort
of
the
chaos
project
did
at
the
linux
foundation
by
partnering,
with
the
university
on
on
diversity,
research
that
maybe
we
we
do
the
same
thing
in
the
standard
space
right.
C
Yeah,
that
sounds
great.
I,
the
the
the
the
challenge
I
was
running
into
was
just
getting
enough
interested
parties
on
the
call
to
really
kind
of
dig
into
things,
but
I
think
if
we
did
partner
with
someone
or
did
more
outreach
and
promotion
than
that,
that
could
work.
E
If
we're
having
trouble
getting
people
on
the
line
from
the
answering
question
side,
you
know
fielding
questions.
I'm
happy
to
you,
know
kind
of
set
aside
some
time
to
help.
C
Maybe
we
start
with
an
ama
sorry
reddit
a
question
session.
Whatever
we
call
it.
A
B
D
Disseminate
so
I'm
part
of
the
developer
students
commit
club
in
like
that
google
is
running,
so
there
are
a
lot
of
folks
if
you're
looking
for
creating
a
pipeline
from
universities
and
students
alike,
we
can
get
connected
there
with
the
dse.
D
So
that's
a
pretty
huge
effort
from
google
in
terms
of
bridging
the
gap
between
like
developers
and
students
and
and
something
that
just
echoed
in
my
mind,
was.
I
haven't,
haven't
really
seen
the
google
summer
of
code
having
you
know
a
category
for
standards
per
se,
because
the
focus
is
always.
There
are
a
lot
of
free
and
open
source
softwares,
but
the
focus
is
more
on
how
you
go
and
write
code
or
make
the
piece
of
application
better,
but
not
really
in
terms
of
standard.
So
we
could
try
to
get
in.
D
You
know
a
segment
for
standards
per
se
and
try
to
see
how
we
could
folks
could
ideate
and
contribute
it
need
not
be
just
enhancing
the
spectral
likes.
It
could
also
be
just
like
improving
the
standard
bodies
website
and
making
it
better,
adding
more
content,
making
adding
more
visualizations
and
unlike
stuff.
A
So
not
sure
you
know
we
got
I'm
not
sure
what
like
how
to
turn
turn
this
conversation
into
like.
A
What's
the
next
small
step
as
y'all
were
sharing
things,
I
was
popping
them
into
the
issue,
so
we
can
keep
track
of
stuff,
but
I
think
it
sounds
like
one
next
small
step
might
be
to
set
up
like
the
office
hours
ish
with
joe,
that,
like
joe
had
and
to
like
mike
samuel's
point
we
can,
we
can
invite
mike
we
can.
We
can
invite,
oh,
professor
andrew
what
the
heck
is
his
last
name.
A
So
there's
a
professor
who
I'm
twitter
friends
with
who
does
a
lot
of
research
and
standards
and
like
he
would
be
great
like
you
know,
so
we
could
maybe
do
these,
but
then
invite
some
guests
or
something
by
guests
from
ietf
or
whatever
that'd
be
good.
A
Yeah,
yes,
all
kinds
of
things:
yeah
we
have
known
yeah,
that's
a
good
point
and
that
feels
very
much
connected
with
the
discussion
thing
and
with
with
the
discussion
strategy
too,
which
we
haven't,
we
haven't
got
to
and
we're
basically
almost
out
of
time
for
today.
So
emily,
can
I
put
this
on
our
agenda
for
next
time.
B
A
Yeah
actually
quickly
save
chat
because
there's
so
many
good
links
in
here
yeah.
Definitely
I
was
just
thinking
the
same
thing.
A
So
so
that's
that
and
then
I
think
we
should
keep
to
my
champion's
point
thinking
about,
like
the
the
use
case
for
a
website
that
displays
this
this.
This
content
that
we're
sharing
cool.
Well,
let's
keep
thinking
about
it
because
I
think
there's
a
lot
of
stuff
here,
there's
a
lot
of
good.
A
A
All
right
I
I
did
want
to
because
I
realized
in
the
note
stack
there's
a
missing
issue
that
I
had
tagged
and
that
is
the
recurring
meeting
time
conflict
that
we
periodically
have
because
of
the
cpc
working
group.
I
think
we
can
solve
that
by.
Let
me
go
double
click
into
this
link
here,
because
I
think
there
was
a
good
proposal.
A
Yeah
either
have
the
meeting
two
hours
earlier
on
conflicting
days,
which
sometimes
airs
with
with
jordan,
but
you
know,
or
or
also
just
shifting
it
a
week,
and
I
think
that
would
possibly
solve
our
problem
as
well.
C
C
A
I'd
be
fine
to
move
it
an
hour
earlier.
I
don't
think
that
would
interfere
with
any
ongoing
meetings.
Emily
would
that
work
for
you.
C
Yeah
I'm
looking
at
my
schedule.
I
I
don't
have
anything
at
one
o'clock.
You
know
for
that
time
slot
for
me,
so
it
works
great
for
me.
C
A
Okay,
well
I'll,
send
a
poll
in
slack
and
because
that
seems
to
be
the
place
where
most
people
are
likely
to
see
it
and
just
say
hey.
If
we
did
it
one
hour
earlier,
would
that
cause
great
difficulty
for
anyone.
C
I
I'd
have,
of
course,
I'd
recommend
opening
an
issue
just
so
that
it's
there
in
addition
to
the
poll
doodle
whatever
I
mean
a
doodle's,
probably
overkill,
but
yeah,
the
question
and
an
issue
would
be
good.
C
C
Promote
the
cult,
the
the
the
the
idea
of
collab
spaces
and
kind
of
make
it
I
feel,
like
collab
spaces,
are
more
oriented
towards
outside
people
getting
more
involved
too,
and
I
think
that
we
have
brought
more
folks
involved
into
the
standard
space
and
it
seems
like
it
feels
more
like
a
collab
space.
In
some
ways
I
don't
mean
to
be
like
semantic,
but
my
thinking
is
that
if
we
promote
it
as
a
collab
space
and
it's
another
cool,
collab
space
that
we're
we
have
at
the
openjs.org
just
an
idea.
A
I
think
it's
a
good
idea,
I
think
maybe
some
of
our
like
programs,
that
we
like,
for
example,
you
know
discussion
spaces
and
that
kind
of
stuff
could
be
instances
of
collab
spaces.
One
challenge
is
that,
with
the
standards
working
group,
we
are
like
chartered
by
the
cpc
and
delegated
for
decision
making
purposes
in
a
way
that
we
do
not
do
with
collab
spaces.
So
I
can
see
that
being
a
little
weird
from
like
a
but
it's
worth
chewing
like.
I
think
we
should.
We
should
kick
on
that.
A
bit
yeah
yeah.
C
A
Cool
all
right.
Well,
I've
got
some
stuff
to
follow
up
with
in
our
issues.
We
will
take
up
some
of
the
proposal.
Discussion
related
topics
that
emily
and
jamanth
brought
up
today
in
our
next
call
and
we'll
keep
we've
got
the
draft
that
we'll
be
collaborating
on
update
to
the
time
and
then
looking
at
days,
slash
options
for
office
hours.
A
Query
me
this
ama,
whatever
the
long
acronym
that
mike
provided
in
chat,
is-
and
I
think
we'll
I
think
I
think
we've
got
lots
of
good
stuff.
So
thanks
everyone
for
a
super
productive
meeting.