►
From YouTube: OpenJS Foundation Standards Team 2020-08-11
Description
The OpenJS Foundation is a member-supported non-profit organization that provides a neutral home for some of the most important project in the JavaScript ecosystem.
Learn more and join us at https://openjsf.org
B
A
A
B
A
Sorry
standards
working
group
meeting
for
today
august
11th
2020..
A
We
have
several
of
our
friends
from
the
cpc
who
are
interested
in
standards,
and
that
can
be
you
too,
my
dear
watchers,
on
the
youtubes,
if
you're
interested
in
getting
involved
just
head
on
over
to
our
slack
channel
and
join,
join
the
standards
working
group
channel
in
slack
and
we'll
help
you
get
onboarded
anyway.
Any
any
announcements.
C
An
announcement
that
is
exciting,
node
14.8.0
went
out
today
and
with
it
came
an
unflagged
version
of
top
level
await
from
a
standards
perspective.
This
is
exciting
for
me
personally,
because
it's
something
that
I
was
the
champion
of
over
at
tc39
and
it
think
it's
in
and
around
the
three
year
anniversary
of
like
getting
work
started
on
that.
C
The
other
thing
that's
exciting
is,
like
you
know,
dino
as
a
javascript
platform,
I
believe
was
the
first
platform
to
have
top
level
away
available
without
a
flag,
and
now
you
know
node
is
following
up.
Also.
We
had
worked
closely
node
with
the
dino
team
to
give
them
feedback
on
their
implementation,
because
there's
kind
of
some
subtleties
what
we
were
waiting
for
and
why
node
didn't
have
it
come
out
sooner?
We
were
really
waiting
for
stability
of
the
feature
itself.
C
So
the
way
in
which
chrome
does
this
v8
is
the
javascript
engine
that
implements
the
features
top
level
weight
has
actually
been
implemented
in
v8
for
quite
a
little
while
and
you've
been
able
to
use
it
in
node
for
a
bit
with
the
dash
dash
harmony
top
level
await
flag,
although
that
just
turned
on
top
level
weight
in
v8,
and
there
were
some
implementation
details,
we
needed
to
do
a
node
to
make
sure
that
failures
and
asynchronicity
was
being
handled
properly,
and
I
believe
it
was
in
one
of
the
earlier
versions
of
14
that
we
introduced
an
experimental
top-level
await
flag
that
actually,
like
wired
everything
up
properly.
C
C
Going
to
wait
until
chrome
unflagged
it
before
landing
in
a
node
dino
is
a
little
bit.
More
experimental
doesn't
have
the
same
kind
of
level
of
legacy
support,
so
it
makes
a
lot
of
sense
that
their
support
contract
is
different,
but
for
us
we
wanted
to
just
make
sure
like
this
thing
was
stable.
It
was
ready
for
production.
We
weren't,
taking
on
a
lot
of
extra
work
over
in
node,
turns
out
that
the
integration
into
the
html
spec
is
taking
a
little
bit
longer
than
expected,
so
the
future
actually
exists
in
v8.
It's
stable.
C
It's
been
running
against
their
fuzzers
for
a
couple
months
now
too,
so
like
they're,
pretty
confident
in
the
stability
of
it,
and
the
only
things
that
we're
kind
of
stopping
it
from
getting
like
fully
stable
is
like
these
html
integrations,
which
are
completely
out
of
scope.
So
one
of
the
things
a
lot
of
context.
Sorry
about
that,
but
the
reason
I
think
that
this
is
like
exciting
and
cool
is
like.
C
This,
I
think,
is
one
of
the
first
language
features
that
node
participated
in
from
like
the
founding
of
the
feature
and
we're
actually
shipping
it
before
browsers
are
even
able
to
ship
it
and
not
doing
it
in
a
way.
That's
like
you
know
not
without
the
blessing
of
like
the
upstream
folks,
so
it's
pretty
cool.
It's
pretty
exciting.
I
think
it's
going
to
unlock
a
lot
of
use
cases
and
usability,
and
so
overall
you
know
I'm
kind
of
gushing.
So
I'll
stop
talking.
A
A
That's
awesome,
well
anything
else
we
should
be
celebrating
today.
I
feel
like
so
that's
that's
great
any
other
exciting
announcements.
E
A
A
The
13th
so
two
days
from
today
is
the
last:
is
the
deadline
to
get
any
working
group
session
meetings
or
you
know,
proposals
for
for
breakout
sessions
and
stuff
like
that
into
the
team?
So
if
you
or
someone
you
know
and
and
or
love
want
to
do
a
working
group
session,
that's
there's
only
two
more
days
to
get
that
that.
F
A
Please
do
that
anything
else.
Brian,
do
you
have
any
any
fun
news,
announcements
things
to
share.
G
A
G
I
haven't
sent
an
update
about
this.
I
don't
have
any
concerns
myself.
It's
most
of
it
is
making
things
sort
of
more
efficient,
but
maybe
that
would
be
worth
having
some
larger
conversation
about.
G
I
don't
know
if
you
have
concerns,
definitely
reach
out
to
me.
If
you
are
interested
in
discussing
it
reach
out
to
me,
I
don't
know,
I
guess
other
interesting
things
since
we
had
talked
about
the
open
prioritization
thing
about
a
month
ago.
We
posted
a
30-day
update
on
that
and
that's
interesting.
If
you
want
to
take
a
look
at
that
yeah,
that's
I
think
all
I
have.
A
A
E
B
And
before
we
jump
into
the
agenda
ben
just
joined
nice
to
see
you
ben.
D
D
Everybody
yeah
joe.
Thank
you
for
the
introduction.
I
am,
I
think
what
you
wanted
me
to
introduce
was
that
I'm
working
on
a
blog
correct.
So
just
if
you're
cool
with
that,
I
don't
mean
new
yeah
yeah.
It's
not
done.
I've
been
in
the
middle
of
a
few
interviewing
pipelines,
but
I
have
a
blog
introducing
the
the
unicode
standards
body
to
openjs
and
see
if
I
can
find
it
real
quick.
So
I
can
share.
D
I
got
it
handy
for
you.
Oh
okay,
cool
yeah,
just
throw
it
in
the
chat
there
so
not
done
yet,
but
kind
of
introduces.
You
know
the
topology
of
what
unicode
looks
like
giving
people
a
better
understanding
of
where
our
footprint
mixes
with
theirs
and
how
it
can
grow
over
time
together
in
a
relationship
but
most
solely
for
most
for
the
purpose
of
helping
us
understand
what
the
heck
is
the
consortium
and
how
do
we
meaningfully
engage
with
the
organization
over
time.
B
Great
awesome,
so
should
people
just
comment
on
there
if
they
have
any
thoughts
or
or
what
have
you.
D
Yeah
yeah,
like
I
said
you
know
I'll,
be
expanding
on
it
probably
early,
hopefully
get
that
out
early
next
week,
so
that
we
can
kind
of
finalize
a
draft,
I'm
sort
of
in
the
middle
of
a
lot
of
interviews
right
now,
but
I
think
early
next
week
I
can
probably
finalize
it
and
then
have
draft
ready,
for
you
know
at
you
know,
edits
or
whatever
I
I'm
not
particularly
of
a
style
of
you
know.
Writing
where
I
feel
like.
I
have
to
have
the
final
say
on
everything
I
write.
D
I
appreciate
any
changes.
Anybody
likes
to
you
know
would
like
to
add,
or
or
whatever
so
feel,
free
to
take
ownership
as
well
cool.
A
All
right,
well,
we've
got
a
lot
going
on.
This
is
awesome.
A
Anything
else
all
right,
let's
dig
into
ye
old
agenda,
then
so
issue.
102
is
our
one
tag
item
for
discussion
today.
This
was
opened
by
debsneck
who's,
a
member
of
tc39,
and
that
is
a
request
to
I
believe
what
they
are
asking
is
to
advance
two
proposals.
A
Two
separate
proposals
under
the
auspices
under
the
umbrella
of
the
open
js
foundation,
there's
been
some
discussion
about
the
proposals
themselves,
which
is,
of
course
interesting,
but
I
think
it
is
worth
taking
a
step
back
to
just
re
to
check
in
on
whether
this
is
actually
an
intended
type
of
activity,
whether
we
actually
mean
to
be
proposing
these
through
the
foundation
itself
or
more
whatever,
okay
miles.
Yes,.
A
Okay,
sorry.
C
H
My
headphones
there
we
go,
so
I
think
that
it's
a
great
idea
for
any
time.
Anyone
has
something
to
bring
to
a
standards
meeting
that
they
circulate
it
as
early
as
possible
with
our
group
to
get
feedback.
H
I
hope
that,
regardless
of
any
of
our
feelings
on
these
specific
proposals,
one
of
which
I
love
and
the
other
which
I'm
unconvinced
by
that,
we
would
never
deprive
the
wider
standards
committee
of
hearing
the
proposal,
so
I
I
think
it's
I
I'll
be
very
happy
if
the
outcome
of
this
is
that
we
get
a
pulse
from
this
group
of
our
opinions
on
his
proposal,
I
would
not
be
happy
if
we
decided
not
to
push
one
forward
or,
if
we,
even
I
I'd,
even
be
skeptical
if
we
convinced
gus
not
to
continue
suggesting
one,
because
I
in
the
past,
I
have
not
been
pleased
when
I
have
heard
about
proposals
dying
within
a
member
company
before
they
reach
discussion
in
a
wider
committee.
A
C
Hello,
so
two
things
that
I
wanted
to
add.
Gus
would
like
to
join
this
meeting.
They
were
just
not
aware
of
the
timing
because
of
the
issue
thing
that
we
were
talking
about
earlier,
not
being
created,
I've
pinged
them,
they
have
the
link
and
they're
to
try
to
join
asap.
So
that
was
just
one
point
of
order
I
wanted
to
make
is
that
if
we
have
another
topic
that
we
can
talk
about
to
burn
some
time,
we
can
wait
for
gus
to
show
up
separately
from
that.
C
C
C
Also
because
that's
like
a
precedent
that
can
be
pointed
towards
about
like
why
certain
things
aren't
being
worked
on
not
to
be
super
repetitive,
but
talking
to
top
level
await,
for
example,
one
of
the
reasons
why
I
felt
confident
and
comfortable
to
bring
it
up
to
the
committee,
despite
the
fact
that
it
was
a
rather
controversial
feature,
was
the
fact
that
going
through
all
the
previous
notes,
there
was
no
like
prior
art
and
saying
we
won't
do
this
and
in
fact
there
was
a
bunch
of
work
carving
out
space
for
it.
C
So
I
think
to
jordan's
point
bringing
ideas
to
committee,
even
if
we
don't
have
consensus
in
this
group,
definitely
feels
reasonable
to
me.
The
only
thing
that
I
would
maybe
want
to
push
back
on,
like
the
tiniest
bit,
would
be
whether
or
not
like
the
standards
group.
This
working
group.
This
meeting
in
particular,
is
the
appropriate
venue
to
be
having
that
discussion
to
me,
like
these
meetings
tend
to
be-
or
at
least
the
intent
has
been
for
them
to
be
like
much
more
administrative.
C
For
you
know
like
the
foundation
to
hold
some
sort
of
like
pre-meeting,
where
all
of
the
different
projects
can
participate,
that
we
help
to
facilitate
and
pick
a
time
that,
like
works
best
for
the
schedule
of
all
the
people
who
have
said
they
want
to
participate
just
as
an
example,
and
I
think
to
the
point
that
jordan's
making
there
you
know
similar
to
an
objection,
perhaps
not
to
pull
too
much
from
the
past,
but
simply
because
two
groups
within
our
foundation
don't
agree
on.
C
Something
is
not
necessarily
a
reason
to
not
move
forward
with
it.
So
I
think
that,
like
maybe
where
we
can
like
our
role
to
play
here
as
like
a
facilitator,
is
to
think
about
like
how
do
we
ensure
that
we
are
not
wasting
committee
time
not
to
be
too
harsh
and
making
sure
that
also
we're
being
like
respectful
of
the
ideas
that
that
groups
are
coming
up
with?
But
like
this
specific
meeting,
I
don't
think
is
like
the
best
venue
for
the
technical
side
of
the
conversation
it's
more
like.
C
We
should
be
thinking
through
the
procedural
side
now
with
that
being
said:
if
we
have
a
time
where
we
don't
have
a
meeting,
maybe
it
is
better
to
just
keep
this
as
a
recurring
time,
but
at
the
risk
of
being
too
repetitive
I'll
stop
talking,
because
I
see
that
brian
had
their
hand
up
and
hello
guys.
G
Yeah,
so
I
just
want
to
make
sure
that
I
understand
what
miles
is
saying,
because
I
think
actually
that
I
am
fully
in
agreement.
I
think
what
you're
saying
is.
This
is
an
appropriate
venue
for
us
to
like
flag
a
topic
and
see
if
there
is
interest
in
us
helping
organize
the
larger
discussion,
but
the
the
larger
discussion
itself
should
be
not
here.
G
B
A
I
E
A
So
guess
we
were
just
talking
about
and
just
really
getting
started
about
how
to
best
support
and
kind
of
proceed.
This
is
still
a
new
newer
group
within
the
foundation,
procedurally
like
what
our
group
can
do
from
a
scope
and
management
and
administrative
perspective,
and
then
I
guess,
conversely,
it'd
be
great
to
hear
like
what
you
would
like.
You
know
to
see
in
terms
of
support,
and
you
know,
input
and
that
kind
of
thing
for
your
proposals,
so.
I
Yeah
so
from
my
perspective,
I'm
just
kind
of
taking
this
from,
like
I
I
you
know
as
as
someone
who
works
on
you
know
node
and
javascript
things
in
in
a
general
sense.
I
You
know
what
kind
of
things
can
either
improve,
specifically
our
projects
that
we
work
on,
or
just
you
know,
everything
of
the
entire
language
in
general,
and
you
know
by
proxy
with
our
projects
and
then
using
the
standards
group
to
be
able
to
you
know,
get
get,
get
those
things
presented
to
the
relevant
bodies,
and
you
know
that
whole
process,
so
I'm
not
sure
like,
like
I
don't
have
very
you-
know
clear,
cut
criteria
on
what
those
individual
items
are.
I
You
know
like
the
things
I
posted,
or
neither
of
them
are
specific
to
any
of
our
projects
or
anything
they're.
Just
things,
I
think,
would
improve
the
language
of
the
javascript
language
so,
like
yeah,
I
don't
really
have
a
well-defined
criteria
in
that
regard.
I
J
Maybe
one
thing
we
we
all
kind
of
want
to
make
clear
to
each
other
here
is
that,
in
other
words,
if
I've
understood
correctly,
this
discussion
is
not
looking
for
permission
or
anything
from
this
standards.
Body
standards
working
group
to
do
anything,
it's
just
saying
hi.
This
is
an
interesting
couple
of
ideas.
I'd
like
to
push
forward.
What
do
you
guys
think
or
have
I
misunderstood
something
well.
I
C
So
hand
up,
because
I
can't
use
the
interface
because
I'm
set
up
as
a
co-host.
C
I
guess
throwing
out
some
ideas
here.
I
would
imagine
that
some
of
the
process
here
is
probably
similar
to
process
around
like
wanting
to
bring
an
objection,
although
I
would,
I
would
say
it's
probably.
The
bar
is
a
lot
lower.
C
To
be
honest,
because
we're
talking
about
like
bringing
things
and
presenting
things,
I
think
that
it
would
be
reasonable,
and
this
is
something
that
our
group
can
help
facilitate
to
like.
Do
a
call
to
projects
to
get
feedback
in,
like
particular,
to
make
sure
that
if
there
are
discussions
that
can
happen
prior
to
plenary,
that's
like
definitely
like
a
preferable
like
to
use
that
time
in
advance.
C
If
you
want
to
get
feedback
outside
of
our
organization
potentially
connecting
with
other
organizations,
that's
also
something
that
that
I
could
see
us
helping
to
facilitate.
If
you
wanted
to
hold
a
meeting,
that's
something
we
could
facilitate.
I
know
that
there's
the
like.
I
figured
with
the
name
of
shoes
program
that
he's
now
running
in
tc39
for
kind
of
like
out-of-band
meetings.
That's
going
on
is
another
venue
where,
like
this,
could
be
presented
in
advance
of
plenary.
C
If
you
wanted
to
get
more
feedback,
but
I
I
would
say
like
in
general,
like
you
know,
this
seems
like
the
role
we
can
play
is
helping
to
facilitate
these
discussions
that
you
want
to
have.
C
J
I
think
we
need
to
deal
slightly
differently
with
people
who
are
official
representatives
of
of
open
js
in
various
bodies
and
the
ideas
that
they
or
opinions
that
they
are
voicing,
as
opposed
to
cases
where
it's
a
lot
fuzzier
where,
yes,
a
person
may
well
be
working
with
or
be
working
based
on
some
work
within
an
open,
js
project,
but
are
not
advancing
this
representing
the
opengis
foundation.
J
A
A
I
don't
think
that
that's
what
we
want
to
do,
but
I
think
what
we
do
want
to
do
is,
if
say,
the
node
project
or
any
other
project
or
even
gus,
is
a
member
of
our
a
beloved
member
of
our
community
and
has
a
proposal
has
proposals
that
they
want
to
see
furthered
that
we
are
here
to
help
them
do
that
effectively,
but
we're
not
we're
not
bringing
it
under
like
we're,
not
advancing
ip
under
our
banner.
Is
that
that's
clear,
I
think,
to
everyone.
I
I
If
I
want
to
bring
a
proposal
there
under
ecma's
rules
of
how
that
works,
I
would
be
bringing
it
as
a
representative
of
the
openjs
foundation,
sort
of
speaking,
like
speaking
for
the
open.js
foundation,
not
myself,
because
that's
just
kind
of
how
pc39
works
so
that
so
the
the
the
the
maybe
it's
just
sort
of
optics
but
like
that
was
the
the
concern
I
had
was
like
how
or
how
is
like
do.
I
need
just
making
sure
that
that's
like
everybody
is
cool
with
that.
C
So
I
think,
like
historically
there
and
other
folks
who
have
experience
from
tc39
can
can
shine
in.
I
think
that
there's
definitely
like
prior
art
here
in
organizations
not
necessarily
being
on
the
same
page
or
a
single
person
like
an
organization,
the
size
of
google,
for
example,
or
microsoft.
C
You
can't
have
one
person
represent
the
whole
organization.
I've
definitely
seen
cases
and
you've
seen
it
too.
I
think
where,
like
one
google
representative
is
presenting
a
proposal
and
another
one
is
like,
has
objections
and
concerns
with
it.
So
like
yeah,
it's
like
presenting
it
on
behalf
of
that
organization,
but
it's
still
like,
like
delegate
x
on
behalf
of
y,
is
presenting
it.
C
So
I
think
it's
like
not
to
get
two
in
the
weeds,
like
the
the
individual
delegate,
is
still
important
as
far
as
the
cash
key
is
concerned
about
where
it's
coming
from.
H
H
E
Yeah,
I
think
we're
unique
in
that
we
represent
so
many
member
companies
and
also
so
many
community
projects
that
may
have
differing
points
of
view.
As
miles
mentioned.
Many
companies
have
differing
points
of
view
just
because
they
have
multiple
products
that
may
implement
things
differently.
So
right,
I
think
there
has
to
be
an
if
and
when
you
go
advocate
for
something
you
have
to
go
through
just
extra
rigor
in
informing
your
stakeholders
and
getting
feedback
before
doing
so.
So
I
do
love
the
idea
of
using
this
body.
E
This
working
group
is
sort
of
a
sounding
board
to
figure
out
how
to
have
that.
How
to
do
that
exercise
right
so.
C
I
think
one
of
the
primary
differences
that
I
would
see
here
is
like,
if
like
what
we're
talking
about
here,
is
like
a
net
positive,
someone's
bringing
work
to
be
done
if
it
does
get
objected
to
either
from
someone
else
from
someone
in
the
foundation
or
someone
externally
like
that,
sets
a
precedent
towards
it.
But
then
it
just
kind
of
like
doesn't
go
anywhere
and
I
think
like,
as
far
as
like
foundation,
reputation
in
our
relationship
with
ekma,
it's
very
different,
because
that's
not
us
coming
and
like
stopping
progress.
C
H
I
mean
either
way
I
see
them
as
just
as
largely
distinct
cases.
I
think
that
that
the
to
your
point,
robin
our
foundation,
represents
a
lot
of
member
companies,
but
that
doesn't
mean
that
every
member
company
has
to
approve
of
a
proposal.
C
I
do
think,
like
you
know,
perhaps
having
some
sort
of
process
where
hey
I'm
bringing
this
just
fyi
and
then
a
mailing
list,
maybe
that
you
send
it
to
that
people
can
subscribe
to
who
care
about
this.
So
there
can
be
discussion
and
feedback
can
be
given
jordan.
C
I
think
for
like
the
case
that
you're
bringing
up
let's
say-
and
I
much
prefer
to
think
about
this
as
like
projects
rather
than
member
companies
here,
to
be
more
specific,
because
member
companies
can
become
members
of
ecma
on
their
own
right
and
like
the
purpose
here,
is
not
to
utilize
in
my
personal
thing,
in
the
foundation
to
allow
member
companies
to
to
have
representation
there,
but
rather
to
allow
like
individual
contributors
of
projects.
C
So
if
individual
projects
have
an
extreme
problem
with
a
proposal
like
you
know,
to
bring
up
top
level
await
again,
webpack
had
problems
with
that,
like
we
should
help
be
able
to
facilitate
that
discussion,
and
if
I
were
a
delegate
of
openjs
as
opposed
to
a
delegate
of
google
that
I
was
at
the
time
of
this,
I
should
likely
have
been
coming
and
making
sure
that
I
was
representing
the
breadth
of
opinions
of
the
constituents
that
I
represented,
which
can
be
hard
to
speak
out
of
books,
both
side
of
your
mouth,
both
sides
of
your
mouth,
but
I
think
that
that's
at
least
the
challenge.
I
A
Do
you
feel
guessed
that
that
it's
clear
to
you
like
what
like
your
next
steps,
need
to
be
slash?
You
know
what
we
as
a
committee
need
to
do
to
help
advance
that
with
you.
I
Yeah,
the
one
thing
I
would
say
would
be,
I
don't
know
I
was
just
I
was
reading
over
the
the
you
know,
the
documentation
we
have
in
our
repo
recently,
and
I
didn't.
A
A
Okay,
so
I
think
we
can.
We
can
say
that
one
is
done
for
today
that
we
can
move
on
to
let's
go
down
to
number
97
pull
request,
97,
that's
a
dill.
K
F
A
97
update
member
expectations
on
handling
potential
conflicts.
Cynthia,
do
you
want
to.
F
Sure
so.
F
The
conversation
that
we
had
before
during
a
meeting
it
was
very
long
time
ago
and
I
also
opened
the
full
records
after
a
very
long
time
and
it's
open
for
a
long
time
now.
So
it's
like
really
really
long
time,
but
it's
based
on
the
conversation
that
miles
and
jordan
has
and
also
like.
It
also
includes
a
few
things
that
we
decided
on
that
meeting.
So
just
like
minor.
F
A
Do
we
all
want
to
take
a
second
just
for
those
who
may
have
missed
it,
because
you're
right,
it
has
been
open
for
a
while,
certainly
would
mean
that
the
length
of
time
that
we
tend
to
a
lot
for
these
to
stay
open?
Would
there
be
any
issues
with
merging
this,
especially
since
it's
going
to
go
into
stage
one.
K
F
F
A
D
A
A
All
right,
any
other,
open
pr's
that
we
need
to
take
a
look
at.
Let
me
go.
Do
that
actually
really
quick
meeting
notes.
Thank
you,
sendel
for
doing
those
and
adding
a
new
working
group
member.
That's
then
we
should
definitely
get
those
in
as
well.
Somebody
want
to
we
had
two
plus
ones
and
it's
been
open
for
a
while.
So
I
think
that
one
can
be
closed.
This
is
93.
A
All
right,
so
that's
getting
merged
in
right.
Now
I
love
the
inclusion
of
the
photo
ben.
D
D
A
And
then
we
also
have
a
number
98,
which
is
ad
representation
in
unicode
message,
format,
working
group,
and
we
have
two
approvals
on
those
on
that
as
well.
This
is
closes.
E
E
A
The
space
I'm
in
an
office
space
right
now,
so
that's
where
that
came
from
okay
cool
and
then
the
last
issue
that
I
had
for
us
today
was
a
chore
wheel,
which
is
that
that
attempt
for
us
to
collectively
take
on
the
responsibility
of
ensuring
that
there's
a
meeting
issue
and
ensuring
that,
if
there's
nothing
tagged
for
the
agenda
that
we
cancel-
and
you
know
that
we're
we're
actually
going
through
the
the
pr
open,
pr's
and
stuff.
A
And
so
I
think
what
needs
to
happen
is
that
we
just
we
need
to
like
actually
do
this
or
change
our
mind
about
what
we're
doing,
which
is
also
fine,
any
ideas
for
how
to
create
a
chore
wheel.
A
A
B
I'd
love
to
have
a
system
where
the
people
that
are
involved
are
in
a
list.
The
people
who
are
doing
more
of
the
work
are
kind
of
deprioritized
a
little
bit
and
we
could
kind
of
spin
a
wheel
too
to
be
like
oh
miles,
you're
you're
up
next
on
on
on
this
bit
of
voluntold
work,
but
that's
kind
of
a
different
different
need.
I
guess,
but
maybe
they
could
be
the
same
tool.
I
don't.
A
Probably
pr
review
just
going
through,
I
said:
that's
like
four
things,
and
or
maybe
is
there
a
slack
bot
for
this?
That's
what
we
need
like
a
little
slack
thing
to
go
through
the
roulette
of.
J
A
J
Maybe
maybe
that's
the
one
that
sort
of
adds
in
an
animated
gif
as
a
sort
of
action.
G
D
A
A
K
I
just
wanted
to
ask
how
often
the
the
chores
will
be
reassigned
now
you
know
I
I
know
it's
it's
nice
to
just
to
to
do
something
new,
but
also
once
you've
started
doing
something
you
can
do
it
more
quickly,
the
second
third
and
fourth
time.
So
that
would
be
a
question
I
have.
A
Meet
every
other
week
right
and
then
there's
yeah.
So
maybe
it's.
A
G
A
Okay,
anything
else,
that's
it
on
the
agenda
so
and
we're
ten
minutes,
eight
minutes
to
the
top
of
the
hour.
I
think
we're
good.
I
thank
god.