►
From YouTube: March 23 2021 OpenJS Foundation Standards Team Meeting
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
and
we
are
live
on
youtube.
Welcome
to
the
march
23rd
edition
of
the
openjs
foundation's
standards.
Working
group
and
meeting
we've
got
a
small
collection
of
of
committee
members
with
us
today,
and
hopefully
you
all
are
dialed
in
and
watching
on
on
youtube.
If
you
want
small
issue
with
the
issue
that
creates
our
agenda,
so
I've
shared
that
in
the
in
this
chat
with
us
and
here
and
we'll
get
that
fixed
for
next
time.
A
A
I
think
the
biggest
fyi
or
oh
tomorrow
is
our
is
our
book
club
meeting.
If
you
want
to
come
to
book
club
and
talk
about
the
we're,
gonna
just
mostly
shoot
the
breeze,
but
also
attempt
to
talk
about
a
book
called
working
in
public
by
nadia
eggpla,
that's
tomorrow,
at
3
p.m,
and
eastern
and
it's
on
our
calendar.
A
The
other
fyi
announcement
is
just
that
you
know
we're.
We've
moved
the
conference
day.
I
think
that's
that's
old
news
at
this
point
or
june
june
2nd
and
we're
hoping
to
have
the
announcements
of
all
of
the
speakers
in
the
next
couple
of
weeks,
so
just
be
on
the
lookout.
For
that
that's
the
other
kind
of
like
I
have
one
thing:
oh
yeah,
okay,
yeah.
B
Our
wonderful
joey
burson
was
featured
in
a
github.
Read
me
article.
If
you
missed
it
last
week,
encourage
you
to
read
it
about
open
source
and
open
standards
and
how
some
of
the
experiences
she
had
in
her
path
and
her
journey.
So
it's
pretty
awesome
and
we're
super
proud
of
jory.
A
All
right
thanks!
Thank
you.
Thank
you,
cool
all
right,
let's
dive
into
our
agenda
and
actually
maybe
before
before.
I
forget
it.
Let's
start
with
the
one.
That's
actually
not
an
issue
that
that
robin
raised
to
me
just
prior
to
the
meeting
so
recall.
If
you
will
are
our
many
different
strategic
directions
and
the
fact
that
we've
been
having
these
very
interesting
and
fruitful
conversations
with
the
w3c
about
how
we
can
collaborate
and
do
more
together.
A
That's
going
really
well.
We've
got
a
few
concrete
things
that
we'd
like
to
move
forward
together
on
some
of
which
we'll
talk
about
today,
but
one
of
one
of
the
things
that
kind
of
percolated
was,
you
know
a
perhaps
building
a
shared
principle
statement.
You
know
we're
members
of
the
w3c
the
w3c
are
considering
joining
us,
it's
sort
of
like
a
you
know.
We
love
each
other.
It's
sort
of
the
way
to
go
about
it
because
there's
not
not
real
money,
changing
hands,
but
it's
a
yeah.
That's
that's
the
thing.
A
Memberships
all
the
way
down,
it's
actually
web
rings
and
we're
all
just
sort
of
like
enjoying
them
subscribe
to
my
web
ring.
So
anyway,
one
of
the
one
of
the
ideas
was
was
kind
of
like
a
principal
statement
and
and
robin
I
don't
know
if
you
want
to
kind
of
expand
on
that
a
little
bit
more.
But
we
really
like
this
as
a
general
idea.
B
Yeah,
I
think,
there's
some
things
that
we
all
just
assume
that
we,
you
know,
have
shared
principles
on
I've,
done
it
a
couple
of
times
and
you
think
it's
just
sort
of
you
know
it's
just
kind
of
assumed
that
we
all
share
these
principles.
But
once
you
get
folks
from
across
the
industry
to
sort
of
sign
a
shared
statement,
it
does
really
have
impact.
B
So
I've
done
this
a
couple
of
times
once
on
cloud.
Interoperability
once
on
health,
I.t
and
standards,
and
it
is
a
really
nice
way
to
sort
of
be
crisp
on
some
kind
of
core
elements
of
that,
and
I
think
you
all
have
probably
have
similar
experiences.
So
we
have
our
conference
coming
up,
of
course,
on
june
2nd,
and
if
we
had
something
that
we
could
issue
at
that
time,
we
sort
of
had
that
moment
in
time
where
we
could,
you
know
amplify
it
much
in
a
stronger
way.
A
And
I
think
to
be
a
little
bit
more
specific
on
like
what
the
shared
principles
are,
and
this
connects
to
this
bigger
conversation
that's
happening
in
and
among
the
different
international
standards
and
software
organizations
about
what
the
relationship
is
between
open
source
and
standardization
activities
and
sort
of
like
that
vision
for
how
these
things
operate
together
for
the
benefit
of
like
you,
know,
businesses
and
developer
communities-
and
you
know
all
of
that.
A
And
the
w3c,
you
know
among
the
traditional
standards,
orgs
is
often
seen
as
a
real
leader
in
terms
of
doing
things
in
a
modern
way,
and
so
that
should
give
you
some
insight
as
to
how
some
of
the
others,
actually
you
know,
operate,
but
anyway,
they're
a
real
leader
in
in
that
open
source
standards
or
doing
open
source,
and
I
think
we
are
emerging
leaders
in
an
open
source
or
doing
standards
participation
and
I
think,
that's
sort
of
like
the
genesis
of
this
idea.
B
C
B
A
It
okay,
so
I
think
then,
maybe
as
next
step
robin
we
should
just
draft
something
and-
and
the
other
kind
of
stakeholder
in
this
is
obviously
is
the
w3c
and
dom
and
jeff
over.
There
are
the
folks
that
we
would
collaborate
with
on
this,
but
I
think
it's
probably
prudent
for
us
to
start
first
and
give
them
something
to
look
at
okay.
C
A
All
right
cool
story
to
finally
issue
all
right
next
thing
on
our
list
is
issue
130.
Actually
you
know
what
I'm
gonna
save
that
for
last,
because
that's
more
of
an
open-ended
discussion
and
the
others
are
hopefully
more
tactical,
so
skip
130
for
128
128
is
the
nominations
for
designated
w3c
ac
rep.
A
A
A
A
Okay-
oh
that's
a
good
point.
We
do
need
to
so
nominations.
Let
me
let
me
note
that
really
quick
nomination
issue
that
was
issue
number
128,
so
we're
going
to
kill
cpc
sign
up
jewelry.
A
Blog
great
next
agenda
item
is:
let's
just
checking
in
on
114
the
strategic
planning
and
goal
setting
issue,
and
I
think
I'd
like
to
figure
out
how
to
transition
now
from
this
sort
of
discovery
phase,
which
is
what
we've
been
first
off.
Does
anybody
need
like
a
quick
context,
refresher
of
where
we're
at
with
this
particular
project?
A
A
The
one
big
change
is
that
we
talked
to
node
the
node
tsc
and,
unsurprisingly,
got
a
different.
You
know
other
other
perspective
and
other
feedback
and
interest.
Primarily,
I
believe
in
number
five
also
number
two
number
two
strategy.
Number
two
was
that
discussion,
space
and
number
five
was
the
educational
resource
development.
B
A
But
as
we
look
at
sort
of
like
the
the
data,
that's
come
in,
I
think
we're
really
kind
of
driving
more
and
more
toward
two
and
five
being
the
predominant
choices.
But
again
many
people
are
saying
they
like
all
of
them
and
number
six,
which
is
the
no
jerk
strategy.
A
I've
given
all
of
these,
like
short
code
names,
so
number
six
is
no
jerks,
everybody
likes
no
jerks,
but
they
see
it
as
something
that
we
can
do
as
we
or
something
that
we
can
promote
as
we
are
working
toward
another
objective,
which
I
kind
of
you
know,
and
I
get,
and
I
think
that
that
we
should
take
that
there.
So
two
is
two:
is
the
discussion
forum
and
five
is
education.
A
This
also
actually
fits
well,
potentially
with
some
things
that
the
jdf
wants
to
do
with
regard
to
educational
resources
for
people
learning
about
standardization,
and
so
I
think,
there's
going
to
be
partners,
we
can
work
with
to
get
some
of
these
things
accomplished,
which
will
be
great
because
we're
such
a
small
group,
you
know
comparatively.
A
A
You
know,
for
example,
two
and
five,
and
and-
and
here
are
the
atomic
projects
that
we
want
to
try
and
build
for
two
and
five,
for
example,
are
we
are
we
comfortable
like?
Are
we
there?
Are
we
ready
to
say
okay,
let's
close
that
issue
and
now
focus
on
those
projects
or
and
brainstorming
some
some
some
projects
for
that
or
do
we
do?
We
feel
like
we
need
to
do.
A
E
A
Okay,
well,
I
guess
the
biggest
thing
is
taking
a
decision
on
which
of
those
strategic
directions.
We
want
to
go,
go
with
I,
so
I
guess
that's
the
that's.
That
is
the
thing
right.
Do
I
want
to
say:
yes,
it's
two
and
five
or
do
we
want
to.
E
B
A
Yep
yeah,
oh,
if
robin
you've
got
that
that
can't
be.
C
A
A
F
A
A
One
was
the
space
for
polyfills,
two
is
discussion,
and
so-
and
you
know
I
think,
just
to
map
this
to
stuff
that
looks
like
that
looks
familiar
if
you
recall
a
few
weeks
ago.
I
guess
it's
been
a
couple
months
ago
at
this
point,
you
know,
for
example,
guy
bedford
came
and
talked
a
little
bit
about
a
proposal
that-
and
he
was
considering
championing-
and
this
is
that
space
where
proposal
authors
can
come,
get
feedback
and
input
from
community
stakeholders,
which
is
you
know,
something
that's
quite
valuable
all
the
way
around.
A
We
don't
have
a
super
defined
process
for
this,
except
for
on
occasion
you
know
folks
go
oh
yeah,
we
let's
go,
ask
these
folks,
you
know
for
input
and
I
think
we
could
do
more
if
we
put
some
rigor
around
this
and
and
maybe
operationalize
it
a
little
bit
and
so
that
we
are
getting
more
awareness
out
there
that
there's
a
topic
that
may
impact
you
know
such
and
such
projects
in
the
foundation-
and
you
know
this
is
the
kind
of
feedback
that
the
the
proposal
author
is
looking
to
get
and
that
kind
of
thing.
A
So
I
think
it's
pretty
useful.
It
was
one
of
the
ones
that
was
most
interesting
to
a
number
of
our
projects
they
that
kind
of
weighed
in
on
this.
So
this
is
two.
E
A
Yeah,
I
I
don't,
I
don't
think
we
would
and
then,
in
fact,
one
of
the
in
the
later
calls
that
we
had
wicg
and
what
wg
were
two
groups
that
we
don't
have
like
this
formal
relationship
with,
but
for
which
the
project
said.
They'd
like
to
learn
more
about
and
have
more
opportunity
to
interact
with.
So
I
would.
I
would
think,
yes,
that
we
would
great
yeah.
B
A
And
then
five
was
this
onboarding
space
right,
so
we
identified
that
a
number
of
the
standards
bodies
may
have
some
materials
that
help
people
understand
their
process,
that's
specific
to
them,
but-
and
there
are
also
lots
of
other
resources
out
there,
that
may
describe
generically
sorry,
I'm
eating
these
chocolate
light
up
generically
how
which
group
does
which
standards
and
that
kind
of
thing.
But
there
aren't
a
lot
of
resources
for
people
who
really
want
to
like
get
in
and
grow.
Perhaps
a
part
of
their
career
in.
A
So
this
would
be
creating
more
of
a
resource
that
we
helped
curate,
that's
not
specific
to
any
one
web
standards
body,
but
rather
helps
one
be
prepared
for
participation
in
multiple.
B
D
B
If
there's
a
little
more
transparency
and
openness
just
across
the
board,
I
think
it
helps
on
multiple
fronts.
A
So
these
were
the
two
that
I
think
and-
and
I
think
four
was
another
one
which
is
one
just
before
here
and
four
is
the
strategy
of
supporting
individual
projects
that
have
standards
related
goals
so,
for
example,
amp
getting
more
involved
with
cat
at
the
w3c
or
in
other
types
of
of
format,
standards
that
kind
of
thing
and
providing
them
resources
and
support,
perhaps
to
advance
their
own
spec,
using
the
jdf
templates
or
going
to
work
with
a
group
and
helping
to
onboard
them
and
say
a
working
group
or
something
as
they
may
need,
and
we
kind
of
are
doing.
A
C
E
E
C
E
If
you
say
that
number
four
is
maybe
lighter
on
support,
but
still
pretty
high,
I
would
propose
that
we
have
zero
of
these
kind
of
right
now
and
starting
with
two
seems
like
a
good
place
to
start
and
like
not
bite
off
more
than
we
can
chew.
Let's
pick
two
and
try
to
do
a
really
good
job
with
two,
and
it's
just
my
opinion.
I
don't
know.
C
A
B
A
Others
so
it
sounds
like
so
if
we
said
I'm
focusing
on
two
and
five
as
first
order
of
business
and
scoping,
then
taking
time
to
scope
some
specific
sub
projects
to
achieve
under
two
and
five.
Would
we
be
pretty
happy
at
the
end
of
the
year?
If
we
have
accomplished
maybe
a
couple
of
projects
that
fed
each
strategy?
A
Okay,
all
right,
I
think
at
this
point
you
know,
everybody
here
seems
excited
about
all
of
them.
Actually,
that's
the
problem
right
when
you
have
all
of
them
and
you
like
all
of
them.
What
do
you
do,
but
it
feels
like
we
have
consensus
to
start
with
two
and
five
and
we
can
start
brainstorming
projects
for
two
and
five
and.
C
A
All
right,
so
I'm
going
to
record
that
we
raised
consensus
to
move
forward
on
two
and
five
and
and
we'll
create
new
issues
now
for
the
projects
focused
on
that
and-
and
I
think
I
I'm
hoping
that
this
actually
becomes
useful.
This
work
becomes
useful
to
us
over
like
a
longer
term
right.
So
even
next
year,
we're
going
back
to
this
and
going
okay.
A
Is
there
a
project
we
want
to
execute
under
these,
because
this
feels
like
many
years
worth
of
opportunities
frankly
for
us,
so
then
on
that's,
that's
one
114
we're
moving
on
to
the
next
step,
and
that
actually
takes
us
really
well
into
the
discussion
issue
for
today,
which
is
number
130
and
that's
standards,
education
and
onboarding
project
ideas.
A
So
if
we
take
five
as
a
given,
what
do
we?
We
need
to
perhaps
flush
out
some
of
those
specific
things
that
we
could
build
to
support
people,
learning
and
onboarding
into
standards,
development
and
activities,
and
so
I'd
love
for
us
to
like
brainstorm
on
that.
A
Yeah
here
let
me
pop
this
issue
in
the
chat
just
so
you
all
have
it
there.
You
go.
A
All
right,
if
we
were
going
to
build
some
resources
for
people
to
onboard
into
standards,
development
and
like
understand,
slash
change,
standards,
culture.
What
would
what
would
we
want
that
to
be
like
what
would
have
been
helpful
to
you
when
you
were
new
in
this.
E
I
think
something
about
expectations
is
really
helpful.
Like
there's,
a
w3c
gives
guidance
like
when
you
join
a
working
group
of
like
half
a
day
per
week.
E
Is
the
commitment
that
you're
making
or
something
like
that,
but
like
it
actually
varies
quite
wildly,
depending
on
the
working
group
that
you're
joining
and
why
you're
joining
like
so
like
one
thing
is:
like
people
become
really
hesitant
if
they
feel
like
they
can't
understand,
what's
expected
of
them,
I
think
it
keeps
a
lot
of
people
out
of
contributing
at
all
or
joining
or
whatever,
but
then
also,
I
think,
there's
a
sort
of
a
different
thing
here.
That's
for
people
who
are
put
into
an
ac
role
that
they
really
they
have.
E
They
have
that
kind
of
in
spades
like
that
plus
plus
that
it
would
be
really
helpful
to
like.
I
don't
know,
write
something
about
that
or
give
something
provide
a
resource.
I
think,
even
just
like
a
slack
channel
that
people
could
join
or
something
and
ask
sort
of
daft
questions.
I
know
like
people
I
reach
out
to
because
of
voting
things
like
frequently
say
hey.
Well,
I
have
you
on
my
company
thrust
me
into
this
role
and
I
really
don't
know
what
to
do
so.
I
think
that
could
be
really
helpful.
A
So
that's
a
great
point
like
there's
some
leadership,
specific
knowledge
that
I
think
is
hard
to
gain
like
you
know.
What's
expected
of,
and
what
does
it
look
like
to
chair
a
working
group
or
a
tc?
A
What
does
it
look
like
to
be
the
spec
editor
and
you
know
thinking
this
is
like
years
ago
I
feel
like
jordan
and
I
we
talked
about
like
yeah,
you
heard
your
name
once
you
eat
your
food
jordan
and
I
talked
about
like
how
can
we
potentially
make
it
easier
first
for
a
person
to
learn
and
kind
of
get
support
to
become
a
co-editor
or
something
because
it's
a
lot
of
lift
to
edit
to
be
an
editor
and
it's
hard
one
knowledge
in
many
cases,
so
you
know,
is
there
necessary,
mentorship
or
education
expectation
thing?
D
Well,
I
think
one
of
the
challenges
is
everyone's
got
different,
like
in
the
introvert.
Extrovert
sense
like
everyone's
got
different
personalities
and
responds
differently
to
advice,
to
different
advice.
So,
for
example,
in
tc39
a
former
you
know,
editor
and
delegate
wrote
a
pdf
about
how
to
participate
in
standards.
D
You
know
specifically
tc39
but
like
as
a
general
thing
and
the
one
of
the
paragraphs,
the
rough
gist
is
basically
show
up
and
listen
and
be
like
for
a
while
before
you
try
to
like,
say
anything
because
then
you'll
get
a
lay
of
the
land
and
be
able
to
participate
more
effectively
right
and
more
than
a
few
people
have
interpreted
that
as
like
shut
up
until
you've
achieved
the
appropriate.
D
But
people
have
read
it
that
way,
and
so
what
I
take
from
that
is
that,
even
though
I
think
that's
good
advice
in
every
situation
in
life
period
to
just
like
you
know,
it's
the
the
parable
about
like
don't
take
the
don't
uproot
the
fence
until
you
know
why
it's
there
right
the,
but
I
think
that
it's
really
difficult
to
word
the
advice
in
a
way
that's
going
to
achieve
the
desired
effect
on
different
kinds
of
people
right
because,
like
someone,
who's
very
outspoken
will
who
it
heeds
that
advice
is
going
to
probably
benefit
somebody
who's,
very
quiet
and
doesn't
need
any
discour
or
any
encouragement
to
stay
quiet
right
and
who,
who
actually
needs
encouragement
to
speak
up.
D
That
person
might
react
in
a
way
that
we
don't
want
just
to
the
same
advice.
So
I
don't
know
I
like
I.
I
think
I
think
that
for
me,
that's
the
challenge
is:
how
do
you
like,
because
there's
people
at
all
you
know,
there's
multiple
spectrums
and
people
at
all
ends
of
those
spectrums
and
like
how
do
you
avoid
excluding
some
of
them
while
giving
the
other
ones
useful
advice
for
them?
You
know.
B
Would
it
be
helpful
to
think
about
what
sort
of
audience
you
we
all
want
to
prioritize?
You
know
the
oh,
my
gosh
I've
been
thrust
into
this
role.
I
don't
know
what
to
do
to
you
know
a
new
person
just
getting
started
to
boy.
I
think
this
is
pretty
cool.
I'd
love
to
be
a
you
know,
I'd
love
to
be
an
editor
someday,
yeah.
A
A
Combo
I
don't
know
was
that
it,
depending
on
also
the
age
of
the
of
the
group
so
like,
for
example,
tc39
has
been
around
for
many
many
years
is
pretty
well
established
in
terms
of
its
process
and
expectation
for
what
the
role
does,
but
there's
all
the
time
new
community
groups
or
interest
groups,
and
even
sometimes
new
technical
committees
at
ecma,
for
example,
which
are
much
younger
and
haven't
figured
this
out
and
so
they're
more
likely
to
have.
A
You
know
because
it's
a
new
committee,
a
participant
in
put
into
a
leadership
role
who
may
not
have
had
that
prior
experience
and
there's
this.
So
so
I
think
that's
a
great
question
because,
like
not
just
like
experience
of
the
person
but
also
possibly
like
supporting
new
work
areas,
that
may
be
popping
up.
A
Like
on
a
on
a
general
sense,
is
there
any
preference
for
like
what
we
want
to
focus
on?
Is
it
like
here's,
here's
some
established
things
and
the
way
it
works,
and
some
of
the
established
flora
versus
like
here's
resources
for
like
the
the
the
new,
the
new
crew.
E
C
B
E
Yeah,
I
think,
like
partially
beginning
to
assemble
some
kind
of
I
don't
know
center
on
the
web.
Where
a
lot
of
these
things
can
you
can
come
to
find
them
and
then,
like
also,
I
assume
they
will
link
to
other
even
existing,
really
good
content
that
exists
on
the
subject
like
there
are.
There
are
some
good
talks.
There
are
like,
I
think,
boku's
document
that
they
made
is
actually
really
good,
includes
a
lot
of
good
stuff.
E
In
one
place
you
could
link
two,
but
then
also,
I
think,
importantly
like
rather
quickly
get
to
where
we
have
a
link
to
like
a
slack
channel
or
an
irc
or
something
where
you
say.
E
This
list
lacks
a
lot
of
nuance
and
details
that
will
flesh
out
over
time,
but
you
know
in
the
meantime
drop
by
and
ask
your
question:
there's
no
sort
of
no
bad
questions
here
that
I
think
that
would
also
like
maybe
help
inform
like
where
to
prioritize,
because,
like
based
on
the
kind
of
questions
that
people
are
dropping
by
to
ask
and
stuff,
you
would
say
well
clearly,
there's
a
need
for
this
thing,
because
six
people
asked
about
this.
B
June,
2nd,
we
will
have
a
hub
on
our
website
and
a
slack
channel,
so
we
can
go
but
work
do
a
work
back
from
there
on
existing
and
what
we
can
accomplish
with
new.
Perhaps.
A
E
A
Okay,
so
it
sounds
like
some
concrete
things
here:
we
need
to
kind
of
put
a
call
out
to
our
squad
about
standard
squad.
Yes,
okay,
making
a
t-shirt.
A
To
just
share
their
favorite
like
helpful
bits,
you
know
and
we
can
at
least
throw
all
of
that
spaghetti
in
a
bowl
and
then
we'll
organize
it,
and
then
I
think
we'll
want
to
probably
figure
out.
I
mean
for
now
it's
fine
for
folks
to
come
in
to
our
standard
slack
channel.
We've
got
like
500
people
in
that
channel
and
it's
like
12
of
us
that
ever
talk
too
much
but
and
it's
quite
a
bit.
A
B
B
A
A
Cool
all
right.
Well,
you
know
I
realized.
Actually,
while
we
were
chatting
that
I
forgot
one
standing
item
for
our
agenda,
because
our
agenda
didn't
make
the
way
it's
supposed
to,
and
I
think
we've
got
some
clear
sort
of
things
we
can
document
and
move
on
this
issue.
So
I'll
close
it
out
unless
there's
any
other
comment
on
the
educational
piece.
A
Cool,
so
the
the
standing
issue
that
I
forgot
about
was
hey.
We
had
a
tc39
meeting
between
the
last
time
we
met
and
today-
and
we
love
to
hear
from
our
reps
with
any
interesting
news
or
bits
from
the
meeting
and
jordan
and
richard
was
there
in
the
assumed
both
of
y'all
went
joe.
I
don't
know
if
you
went
any
news
to
share
anything
exciting
fun
worth.
Should
we
be
wading
into.
D
Yeah,
I
mean
the
big
one.
I
think
there's
there's
a
few
things,
but
the
the
big
one
is
that
temporal
got
stage
three.
So.
D
Yeah,
so
that's
that's
great.
All
of
the
engines
are
going
to
ship
it
behind
a
flag
for
now,
because
there's
some
unresolved
questions
and
but
yeah
moving
to
stage
three
is
a
big
deal.
A
few
other
proposals.
Advanced
error
cause
is
stage
three,
so
you
can
now
pass
an
optional
options
bag
to
the
second
argument
of
any
error:
constructor
that
includes
a
cause
property
and
that
will
get
attached
to
the
error
and
then
presumably
browsers
and
node
and
stuff
will
will
have
friendlier
displays
of
that
information
when
available
and
then
a
few
things.
D
And
our
class
static
blocks
also
move
to
stage
three.
So
that's
like
inside
a
class
body,
you
can
say
static
and
some
curlies,
and
then
you
can
do
some
stuff
and
it'll
like
run
once
as
part
of
defining
the
class.
A
So
popping
back
to
temporal,
because
I
think
that's
one
that's
near
and
dear
to
openjs
as
moments
in
our
you
know.
The
moment
team
have
obviously
announced
they're
they're
moving
on
from
maintaining
it
and
yet
they
have
played.
I
think,
a
important
part
in
this
feature
over
time.
I
wonder
if
we
want
to
as
a
group
do
something
to
celebrate
that
connection,
or
you
know,
a
lot
of
people
are
excited
about
this
for
sure.
D
Yeah
I
mean
the
the
moment:
maintainers
had
a
different
idea
than
I
did
about
pr
strategy.
What
I
personally
think
would
have
been
most
effective
is
for
a
production-ready
polyfill
for
temporal
to
exist
after
it's
stage
three
and
to
simultaneously
recommend
one
or
more
of
them,
while
deprecating
moment
and
sort
of
in
one
fell
swoop,
pushing
the
ecosystem
to
this
better
pattern.
But
moment
did
its
depth.
You
know
sort
of
not
deprecation
but,
like
its
moment,
is
done
blog
post
last
year
and
there
aren't
any
production
ready,
polyfills
ready.
D
Yet
so
you
know
you
all
don't
have
to
agree
with
my
pr
strategy
philosophy
there,
but,
but
if
you
did,
then
we
would
wait
and
like
we'd,
probably
want
to
wait
until
one
or
more
of
those
polyfills
exist
and
then
so
because,
like
the
anyone
who
migrated
from
moment
to
like
one
of
the
moment,
competitors
is
now
going
to
have
to
suffer
a
second
migration,
because
as
soon
as
there
are
temporal
polyfills,
everything
else
is
immediately
obsolete
and,
like
so
yeah
those
are
just
my
thoughts
in
general
about
how
to
address
it.
D
A
D
Mean
I
certainly
have
that
on
my
list
of
things
to
build.
You
know
I
have
an
ecosystem
of
polyfills
that
temporal
would
need
to
be
part
of,
but
whether
that
will
be
you
know
it
is
highly
unlikely
that
will
be
the
only
and
possibly
not
even
the
first
one
that's
available.
So
I
imagine
that
if
we
give
it
enough
time
there
will
be
probably
three
major
implementations,
mine,
core
js's
and
then
the
one
that
grew
out
of
the
proposal.
D
Polyfill
that's
going
to
be
decorate
deprecated
and
there
may
be
more,
but
there
I
expect
at
least
those
three
to
be
viable
at
some
point
in
the
next
coming
months.
A
Got
it
okay?
Well,
we
should
keep
on
our
eyes
open
and
on
this,
and
just
because
I
like
to
highlight
where
we
can,
where
our
projects
and
our
our
community
members
have
been
adding
to
the
space
anything
else
from
standards
you
from
or
one
of
our
affiliations,.
B
F
Last
time
we
discussed
that
someone
shared
that
another
group
was
already
providing
summaries.
I
don't
remember
who
that
was.
A
I
don't
remember
who
shared
that,
but
it's
I
think
the
person
is
hyman,
who
typically
does
those
what,
after
maybe
they
sometimes
they
take
about,
is
samantha
and
a
galleon.
D
No
month
works
for
paypal.
A
Paypal
does
and-
and
I'm
remembering
that
right,
it's
samantha
right.
That's
doing
this.
D
Yeah,
I'm
pretty
sure
I
mean
there's
a
there's
a
few
folks
that
do
it
a
lot
of
people
do
their
little
blog
posts
with
the
updates,
but
hey
month
in
particular,
does
as
well.
So
I
don't
know
if
he
realizes
that
we
might
be
relying
on
him
to
do
it.
A
Yeah
awesome
and
I
I've
always
kind
of
preferred
his
write-ups
to
others.
Sorry,
not
I'm
not
playing
favorites
with
anybody
on
the
in
the
ecosystem,
but
I
just
I
rather
like
how
he
writes
so
I
can
reach
out
and
just
confirm
that
he's.
Okay
with
that.
F
The
reason
that
came
about
has
has
to
do
with
what
we
thought
participation
would
look
like.
I
was.
F
I
was
actually
planning
to
create
those
until
it
was
pointed
out
that
someone
already
was
so
yay
and
then
instead
have
it
have
it
as
a
goal
of
mine
to
produce
the
preliminary
materials
like
here's.
What's
on
the
agenda
reach
out,
if
you,
if.
F
And
I
I
really
like
that
division
of
responsibility,
but
but
it'd
also
be
nice
to
have
both
sides
aware
of
it.
A
I
I
I
think
that
would
be
great,
I
mean,
and
I
think
also
richard,
to
the
extent
that
we
can
kind
of
make
a
connection
for
those
who
may
be
too
busy
to
make
it
themselves
is
like
this
might
affect
you.
If
you
know
you're
you're,
like
you
know,
you're
building
a
tool
that
does
xyz.
You
know
that
would
be
because
I
think
that's
one
of
the
critiques
of
following
this
material
is
like
okay.
But
how
do
I
figure
out,
which
is
relevant
to
me
and
which
isn't
so.
D
B
A
All
right,
well,
it
is
three
o'clock-
may
do
a
call
for
any
other
business.
With
the
30
seconds
we
have
remaining.