►
From YouTube: SES Meeting: Promise.ownProperties &c
Description
This session had a short quorum. We deferred the topic of Records and Tuples a week and Alex Vincent posted a call for contributors for new promise combinators.
A
Welcome
to
the
tess
meeting,
we
have
a
light
agenda
today.
The
the
topics
we're
deferring
the
topic
of
records
and
tuples
to
next
week
on
account
of
not
having
a
full
quorum
and
other
than
that
we
have
a
convert.
Alex,
has
asked
for
a
conversation
regarding
his
proposal
for
promise,
properties
and
yeah.
That's
that's
all
we've
got
so
go
ahead.
Go
go
ahead,
alex.
B
B
It
is
stage
zero,
basically
stage
minus
one
really.
This
is
just
a
very
first
draft
and
I
was
really
looking
okay,
who
wants
to
come
on
board
with
this
in
terms
of
co-authoring,
slash,
championing
slash
contributing
to
this
proposal
and
what
the
heck
did.
We
call
this
darn
thing
in
terms
of
naming
the
repository
and
that's
all
I
have
really
is.
I
just
want
to
hear
what
people
think.
A
B
B
A
I
think
that
the
only
thing
procedurally
is
with.
I
think
that
the
prevailing
convention
is
for
the
repositories
to
begin
with
the
name
proposal
dash
or
possibly
tc39
proposal
dash,
I
don't
recall
which
but
yeah
I
I
think
that
there
isn't
much
to
say
until
until
you
put
it
up
to
the
group
or
presented
to
tc39,
it's
a
it's,
a
very
small
proposal
right.
C
B
A
D
C
C
C
All
of
that
is
the
longest
possible
way
of
me
saying
that
I
have
like
a
really
fresh
context
of
of
promises
and
the
combinators
in
general,
like
in
in
brain,
still
pretty
much
good
to
go.
So
I
think
I've
changed
my
mind
and
will
try
as
best
as
possible,
to
participate
in
like
an
authorship
capacity,
at
least
to
help
keep
things.
I
think
consistent
with
the
the
existing
promise
apis
with
regard
to
the
combinators
and
also,
I
think
it's
super
cool.
I
think
it's
a
cool
proposal
and
I
want
it
so.