►
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
A
Excellent
looks
like
we're
live,
I'm
gonna,
I'm
gonna
assume
that
we
are
live
there.
We
go
redirecting.
Thank
you.
Everyone
for
joining
another
episode
of
the
openjs
foundation's
cross
project
council
meeting
today
is
a
day
today
is
october
12th,
there's
the
the
recording
link
yeah.
So
let's
get
started
with
announcements.
B
Right
announcements,
yes,
so
let's
see
what's
going
on
this
week,.
C
This
week,
thursday
thursday,
we
have
our
program
committee
for
openjs
world.
We're
getting
serious
folks
need
all
hands
on
deck
to
start
start
finalizing
our
keynotes,
because
we
want
to
send
out
invitations
at
the
end
of
the
month.
I
think
we're
gonna
have
a
good
short
list
and
then
we'll
bring
it
to
the
cpc
for
some
stack
ranking.
I
think
which
would
help
us
so
many
good
ideas.
A
B
B
B
So
that's
one
other
thing
and
also
thursday,
thursday.
Yes
thursday,
our
colleague
emily
will
be
speaking
at
the
unicode
conference
on
message.
Format
2.0
so
give
give
your
best
to
emily
and
and
other
open
friends
of
openjs
actually
he'll,
be
out
at
the
unicode
conference
and
as
part
of
like
the
standards
and
open
source
work
that
we
do
so.
C
D
B
A
A
Well
then,
we
can
jump
into
the.
I.
B
So
also
the
w3c
has
published
its
tentative
schedule
for
the
working
meetings
and
developer
days
coming
up
not
next
week
but
the
week
after
so
the
week
of
the
18th
so
for
community
members
who
are
interested
in
in
checking
out
different
w3c
related
programs
that
is
online
I'll
pop
a
link
to
it
in
our
in
our
notes
doc.
So
you
all
can
take
a
look
at
any
anything.
You
want
to
check
out
meaning
wise.
A
Excellent.
Thank
you.
When
do
we
talk
about?
I
guess
I
hope
this
is
on
the
agenda
and
we
really
didn't
do
anything
last
week,
but
the
working
sessions.
B
So
maybe
we
should
kind
of
move
those
up
or
something,
because
those
are
really
fruitful
conversations
and
I
always
feel
like
they
end
up
coming
at
the
end.
So
it
might
be
great
to
make
those
more
systematically
part
of
like
the
top
of
the
top
of
the
agenda.
A
Yeah,
that's
a
good
idea.
I
can
make
an
update
to
the
template
for
the
meeting
meeting
doc.
However,
with
that
being
said,
I
don't
think
we
really
did
anything
last
week.
Right
was
it
just
me
and
you
robin
and
we
chit-chatted
and
called
it
a
wrap.
C
Yeah,
I
think
we
need
to
yeah
get
ahead
of
our
agenda
a
little
bit
more
to
help
folks
determine
whether
or
not
the
you
know
it's
something
that
they
would
be
interested
in
participating
in
or
we
didn't
know
if
we
were
just
coming
off
this
summer
kind
of
a
quiet
time.
So
we
we
do
have
some
work
to
do
there.
A
C
A
Yep,
I
think
that's
a
good
idea
and
then
I
think,
maybe
after
this
meeting,
you
know
these
regular
meetings.
We
can
maybe
message
the
group
in
slack
as
to
what's
the
working
session
next
week
and
try
to
encourage
folks
to
help
move
the
work
along.
B
Yeah,
so
you
know
we
can
check
in
really
quick
on
the
last
week's
conversation
was
on
the
coc
to
see
to
see
or
see.
If
there's
anything,
we
can
improve.
B
And
you
know
one
one
thing
we
acknowledged
is,
quite
frankly,
there's
there's
nothing
so
there's
nothing
pressing
from
like
an
issue
standpoint
to
to
drive
the
conversation
specifically
about
like
oh
well.
This
is
happening.
You
know,
here's
some
context.
B
Let's,
let's
look
at
you
know
things
we
can
do
it
to
address
that
particular
issue.
One
of
the
things
that
we
discussed,
though,
was
the
fact
that
the
contributor
covenant
is
getting
a
an
aversion
upgrade,
and
so
we
should
be
reviewing
and
reading
the
new
version
of
the
contributor
covenant
to
determine
if
that's
a
rev
we
want
to
adopt.
B
So
that
was
one
of
the
take-home
pieces
of
homework
for
the
group.
Other
topics
that
we
covered
included,
training
for
for
moderators
and
making
more
concrete
recommendations
beyond
what
we
have
so
far.
You
know
perhaps
even
scheduling
time
to
run
those
things
for
folks
on
moderation,
teams,
community
moderation,
teams.
B
We
talked
about
general
auditing
and
cleanup
of
which
it's
sort
of
a
evergreen
kind
of
project
where
we're
constantly
just
going
through
and
checking
out
project
websites
to
make
sure
the
information
is
up
to
date
like
in
their
on
their
websites,
they
can,
we
can
find
their
cocs
and
that
kind
of
thing
yeah.
B
C
So
joe,
I
think
you're
confusing
program
committee,
which
I
think,
oh
that's
what
rachel's
transitioning.
I
think
we
was
rescheduled
but
yeah
tierney
was
on
and
others.
So
that's
a
good
good
follow-up
thanks,
jory
yeah!
Thank
you
yeah
next
week
it's
on
technical
strategy,
follow-up.
That
is
the
topic,
and
what
was
I.
E
A
Likely
me
as
well:
okay.
F
Well,
we'll
we'll
see,
should
we
should
we
cancel
next
week
then.
A
E
Yeah
yeah.
That
would
make
sense
to
me
and
then
push
push
that
technical
discussion
to
the
next
working
session.
Yeah
great.
A
Thank
you,
jory
much
appreciated
cool
anything
else
before
we
get
into
the
agenda.
A
If
not,
I
will
start
with
the
first
item
here.
This
is
whoops
pull
request,
789
start
listing
documents
maintained
by
the
cpc.
A
This
is
listed
as
a
work
in
progress
and
a
draft,
but
maybe
it's
the
sort
of
thing
where
we
maybe
have
an
issue
open
and
use
that
to
keep
open
and
and
merge
this
in
and
just
try
to
move
things
forward,
or
I
don't
know
what
people
think.
A
Oh,
and
I
see
there
is
an
issue
746,
this
issue
is
tagged
to
close
it,
although
maybe
if
we
don't
think
it's
got
everything,
maybe
we
leave
the
issue
open,
I'm
not
sure.
G
Yeah,
I'm
I'm
happy
to
either
merge
this
in
now
or
actually
at
some
point
due
to
work
to
complete
this.
It's
not
a
huge
amount
of
work,
but
I've
been
very
busy
with
personal
stuff
over
the
course
of
the
last
six
weeks
which
weren't
not
really
planned,
so
I'm
kind
of
like
a
bit
under
the
water
at
the
moment.
So
it's
really
up
to
you
all
or
or
if
someone
actually
wants
to
start
listing
their
stuff.
One
could
do
that
too.
I
don't
really
have
it's
really
up
to
you.
Okay,.
G
Yeah,
I'm
just
essentially
concerned
that
like
having
like
two
things
listed
as
this
is
what
the
cpc
does,
instead
of
like
the
15,
that
we
have
it's
just
going
to
create
more
confusion
than
actually
help
anything,
and
so
that's
kind
of
what
I
find
a
bit.
You
know
it's
not
a
lot
of
work.
That's
my
point
yeah.
So.
A
Why
don't
we
leave
it
open
for
now?
Let's
take
a
look
back
at
it
in
two
weeks.
If,
if
either
you
or
or
I
or
anyone
else
hasn't
kicked
that
one,
you
know
put
put
put
more
documents
in
there
then
we'll
make
a
decision.
Then.
A
Yeah,
that
sounds
good.
I
think
you're
the
thinking
that
you're,
having
makes
sense
to
me
all
right,
cool
the
thinking
that
you're
having
yeah
okay,
that.
A
Yeah,
I
don't
know
where
my
brain
is
today
or
at
all
really
lately
yeah,
apparently
cool,
so
we'll
do
that.
Moving
on
clarify
requirements,
around
coc
violation,
toby
opened
this
up
on
august
3rd.
G
A
Yeah
well,
my
world
has
gotten
really
busy
over
the
last
several
weeks
as
well.
So
I
understand,
that's
that's
open
source.
Is
you
know
you
do
what
you
can
when
you
can.
C
I'm
halfway
through
the
alphabet
of
our
projects,
just
doing
an
inventory
of
where
everybody
is
all
the
projects
on
our
on
the
codes
of
conduct
so
I'll
get
there.
A
G
A
G
Sub
threads,
okay,
so
there's
like
the
yeah.
It's
if
you
actually
like,
read
it
through
it's
pretty
clear.
It's
just
like
not
obvious,
and
I
don't
think
you
can
do
it
indented
to-do
lists,
so
you
might,
but
I'm
not
sure.
A
Yeah,
okay,
now
that
makes
sense.
I
sometimes
read
issues
from
the
bottom
up,
so,
okay,
all
right
cool.
So
we'll
leave
this
one
open
as
well
and
continue
to
try
and
make
progress
on
this
unless
anybody
has
any
other
thoughts
or
whatever.
A
No
okay
cool,
so
we
will
move
on,
although
I
will
mention
jordan
popped
into
the
chat.
Nvm
had
a
release
recently
and
so
that's
something
to
celebrate
as
well
and
announce
so.
Congratulations,
emil.
H
The
the
important
things
in
it
are
that
it
will
ins
it
will
avoid
installing
npm
eight
in
node
versions
that
doesn't
work
in
and
also
it
adds
theoretically
adds
windows
support,
not
just
in
wsl
but
in
powershell,
git,
bash
and
siege.
A
Yeah,
that's
great
good,
good,
good
cool!
Thank
you,
jordan,
awesome!
So
moving
along
this
is
issue
756
create
proposals
for
the
community
fund.
I
suspect
this
is
kind
of
ongoing.
You
know
we
talked
about
the
lift,
lift
scholarship
earlier.
C
Yeah,
I
think
we
had
two
other
big
ideas.
One
was
a
thank
yous
for
maintainers
and
the
other
one
was.
How
do
we
support
meetups
around
the
world?
So
I
think
this
group
probably
needs
to
determine
how
much
you
want
to
allocate
of
the
travel
fund
to
those
pieces
and
which
program
you
want
to
prioritize,
and
we
can
just
start
on
execution
so.
B
Also
we
had,
we
decided,
you
know
the
staff
were
taking
action
to
go
kind
of
look
into
different
cost
models
for
like
a
thank
you
program.
So
that's
that's
one
concrete
thing
that
that
we're
working
on
but
to
robin's
point.
We
need
more
input
from
the
cpc
on.
You
know
how
kind
of
what
we
want
to
start
with
for
either
of
those
sort
of
buckets
at
a
higher
level.
E
C
I
did
find
a
vendor
that
dropped
ships
to
individuals,
so
I
can
maybe
pull
a
few
ideas.
Would
that
help?
Okay.
A
Also,
I'm
just
wondering
that
you
know
we're
we're
nearing
the
end
of
the
year.
I'm
wondering
you
know
what
what
sort
of
money
we
have,
how
we
want
to
spend
it
entirely
all
those
kinds
of
things.
Oh.
B
Yeah,
we've
spent
a
nominal
amount
and
so
like
you
know
that
that's
unfortunate
and
that
the
current
virus
kind
of
prevented
some
of
this
from
being
put
to
better
use
earlier.
But
you
know
it's
there
right
now.
E
E
There's
nothing
that
says:
we're
gonna
set
the
budget
to
zero
next
year.
If
we
didn't
spend
it.
If
I
mean
there
is
some,
there
is
some
feedback
that
if
over
the
years
in
a
regular
year,
if
we
hadn't
spent
the
travel
fund,
you
know
over
a
number
of
years,
we
might
say
well,
we
should
adjust
it
to
reflect
what
makes
sense.
I
Okay
sounds
good
yeah.
My
my
understanding
was
slightly
more
urgent
than
that
which
was
like
nonprofits,
basically
can't
turn
a
profit
or
something
like
that
and
so
have
to
go.
Like
I
don't
know,
I
don't
know
how
stuff
works,
but
that
was
my
understanding
in
the
past.
Yeah
yeah.
I
B
Have
we
had
any
illustrations,
no
applications
at
all
we
had
we
had
like
we've
had
like
two
people.
We
supported
it
on
the
travel
that
we're
supporting
on
the
travel
fund
and
and
that's
that's.
It.
C
Yeah
we've
had
a
lot
a
lot
of
interest
on
the
scholarship.
We've
had
lots
of
applications,
so
that
may
be
something
that
we
want
to
repeat
in
a
month
or
two,
because
there's
so
much
interest
and
once
we
start
reading
those
applications,
we
can
even
make
more
of
an
argument
that
yeah
we
do
it
again.
E
D
A
J
A
Well,
in
terms
of
that,
that
last
point
is
that
something
that
we
will
discuss
at
some
point
or
what's
the
plan
on
evaluating
the
scholarships
and
stuff.
C
A
B
I
would
just
say
on
this
and
it'd
be
lovely
to
hear
you
know:
we've
got
a
lot
of
you
know
me,
I'm
always
happy
to
give
you
a
million
and
one
ideas,
but
we'd
love
to
hear
from
the
community
any
any
specific
feedback
on
like
you
know,
recognition
or
you
know
things
that
would
better
support
their
local
meetups,
that
kind
of
thing
and
it's
easier
to
kind
of
reason
about
concrete
proposals.
B
A
All
right
and
with
that
we
will
move
along
going
once.
That's
all
you
get
just
once
next
up
is
pull
request
728.
This
is
ci
automation,
ad
link
checking.
This
has
actually
been
around
for
a
long
time.
Look
at
this
sorry,
I'm
scrolling,
tierney,
you,
okay,
14
days
ago,
you
say
this
could
be
merged
now,
which
pr
is
this
728
ad
link
checking.
I
Yeah
I
I
would
run
it
again
like
I
don't
know
I'll.
I
can
run
it
again,
but
if
it's
green
again,
then
it
should
be
fine.
I
spent
a
decent
amount
of
time
going
through
and
fixing
all
the
links
thanks
to
jordan
for
going
through
and
changing
some
some
things
that
I
changed
to
main
to
head,
but
yeah.
This
will
help
us
one
make
sure
we're
merging
markdown
that
works
and
is
like
usable
like
there
was.
I
You
know,
a
number
of
very
old
things
that
were
like
linking
to
xx
as
like
a
placeholder,
and
then
we
didn't
fill
that
in
and
then
just
a
lot
of
things
that
have
died
over
the
over
time
and
like
either
got
moved
to
a
different
page
or
are
just
forever
dead
and
addressing
that
and
making
sure
that,
like
you
know,
we
have
a
repository
that
is
fully
useful
and
like
we
don't
have
to
deal
with
one-off
issues
about
oh
hey,
I'm
trying
to
read
this
and
it
didn't
work
or
oh
hey.
I
Like
I
noticed
you
know,
I
was
trying
to
try
to
learn
about
this
thing
and
it
doesn't
work
or
in
the
case
of
one
of
the
cocs
like
the
link
was
just
dead
and
it
had
been
dead
and,
like
that's
an
important
thing
of,
we
want
to
make
sure
we
have
reporting
working
so
yeah,
that's
generally,
the
purpose
of
it
seems
to
be
working
pretty
well
huge.
Thank
you
to
justin
beckwith
for
fixing
things.
As
I
poke
him
saying:
hey
this
doesn't
work
or
hey.
I
This
isn't
like
doing
what
I
think
it
should
and
him
agreeing
with
me
he's
been
super
helpful
on
that
very
good
tool.
Thank
you.
A
Excellence,
jordan,
it
looks
like
you
still
have
a
hold
on
this.
I
don't
know
if
that's
just
left
over
from
previous
I'm
trying
to
switch
on
this
pull
request.
728
in
the
cpc.
I
can
drop
a
link
in
the
chat.
If
that's
helpful
there,
it
is,
I
suspect,
it's
just
from
previous
change
requests.
A
Oh
yeah
cool,
so
yeah
cool
once
we
get
that
we'll
squash
emerge.
Thank
you
journey.
Thank
you,
jordan.
Thank
you,
justin
excellence.
A
All
right.
Moving
on
the
next
item
on
the
agenda
is
issue.
645.
dojo
report
link
in
code
of
conduct
is
broken.
G
Dylan,
I
was
just
looking
at
this,
and
this
is
something
attorney
had
brought
up
like
a
long
time
ago
that
I
brought
up
again
recently
that
dylan
fixed
that
you
emerged
two
weeks
ago,
but
that
conflicted
with
the
other
coc
thing.
That
was
also
emerged
roughly
at
the
same
time,
and
so
I
think
we
need
a
new
poll
request
to
actually
re-include
that
full
request
in
the
current
code
of
conduct.
A
G
I
think
the
the
merge
of,
like
my
pull,
request,
overwrote
that
merge
or
something
where
it
happened.
I'm
not
sure
why
I'm
not
sure
how
it
conflicted
and
when
and
it
wasn't
there
for
like
a
couple
of
weeks,
so
I
don't
know
like
yeah
something
happened,
and
so
we
just
need
to
fix
it.
Okay,
will
you.
A
If
you
open
up
a
pull
request,
will
you
link
this
issue
and
and
call
that
one
around?
I
will
do
that
yeah
excellent.
Thank
you.
Toby.
A
Beautiful
so
moving
on
this,
our
perennial
issue
here:
providing
implementation
guidance
for
dcocla
today's
meeting
yeah.
So
I
see
tierney's
last
comment
on
august
17th.
C
Yeah
we
had
an
an
update.
We
saw
today
from
gregor
on.
Github
looks
like
that,
but
may
be
shutting
down
unless
somebody
else
picks
up
maintenance.
Somebody
has
offered
to
pick
up
maintenance
from
berlin.
Oh
looks
like
brian
just
commented:
oh
brian
was
commenting
and
getting
more
clarity
here.
I'll
drop
it
in
the
chat.
Oh.
C
Little
concerning
brian
has
spent
a
lot
of
time
on
this
yep,
maybe
I'll,
take
a
look
so
looks
like
it
will
be
shutting
down.
There'll
be
a
grace
period
of
four
weeks,
if
no
one
steps
up
and
off
and
offers
to
take
on
ownership.
C
Awesome
great
yeah
cool,
well
we'll
connect
with
him
as
well,
because
that
was
two
thoughts
one
can
we
escalate
with
github
and
then
I
was
gonna.
Do
the
same
with
the
linux
foundation
as
well,
so
we'll
try
to
connect
the
dots
and
see
what's
happening
with
gregor
and
then
that
company
in
germany,
as
well,
who
looks
like
they've
taken
a
dependency
okay.
C
C
B
Yeah,
we
should
think
robin.
We
should
sync
with
ryan
and
mike
dolan,
because
this
I
mean
ryan
works
for
hyper
ledger
and
so
our
when,
when
we
initially
approached
lfit
about
taking
this
on,
they
were
like
no.
C
B
C
G
It
might
be
worse
also
commenting
in
in
that
thread
of
the
thing
itself
that
we
actually
rely
on
this
stuff.
When
I
know
brian
sort
of
mentioned
it
kind
of
like
up
in
the
well,
you
know
manifested
interest,
but
I
think
that
mentioning
that
open
gsf,
actually,
like
would
really
need,
would
really
want.
This
is
a
good
sign
to
be
in
that
thread
too.
A
Fun
all
right
well,
keep
us
posted.
Thank
you.
We'll
leave
this
long
running
issue
open
as
we
kind
of
work
through
it
cool.
So
then
the
last
thing
is
something
that's
rich
added
to
the
agenda
or
you
know
it's
the
comments
of
the
issue
and
I've
popped
in
the
agenda.
I
dropped
a
link
into
the.
A
Zoom
chat
there
and
now
I
will
actually
open
it
up
myself
again.
You
want
to
give
us
some
context.
D
Rich
yeah,
so
this
is
a
tsc
charter,
a
node.js
technical
steering
committee
charter
change,
which
needs
to
be
approved
by
this
body
because,
as
the
nature
of
charter
changes
to
the
new
js
tech
and
steering
committee-
and
the
purpose
of
this
change
is
we
have
we
have.
We
have
a
set
of
criteria
by
which
people
are
supposedly
automatically
removed
from
the
tsc.
D
If
they
don't
do
any
of
three
things
within
a
three
month
period,
don't
attend
any
meetings,
don't
participate
in
any
votes
and
don't
participate
in
any
tsc
discussions,
and
it's
that
last
one.
That's
really
problematic,
because
that
just
makes
it
absolutely
impossible
to
automate
and
impossible
to
do
by
to
do
manually
for
that
matter,
and
we
we've
had
people
not
currently,
I
don't
think
but,
but
you
know
we
have
had
stretches
where
people
did
not
participate
for
two
years
before
we
removed
them.
D
I
would
like
to
avoid
that
it
makes
it
makes
getting
to
quorum
and
con
concluding
votes
problematic
and
just
anyway,
so
this
change
tries
to
make
things
a
little
more
automatable
by
reducing
the
criteria
to
attending
a
meeting
within
a
three-month
period
and
participating
or
or
participating
in
a
boat
within
a
three-month
period.
D
If
you
do
either
of
those
things,
then
you
are
a-okay
to
stay
on
the
tsc,
at
least
unless
tsc
chooses
to
remove
you,
but
we
never
do
that,
though
we're
really
bad
at
it,
and
so
I
would
love
to
automate
this.
D
I've
introduced
some
automation
to
do
this
for
collaborators
in
node,
and
I
think
it's
working
really
well,
and
I
would
like
to
do
this
for
the
tsc
as
well
and
I'll
add
as
an
additional
note
that
I
noticed
that
the
cpc
team
in
the
opengs
foundation
repository
has
something
like
36
members
or
something
like
that.
I
have
never
seen
that
many
people
on
the
cpcc
meetings.
D
I
don't
wonder
if
maybe
something
like
this
might
benefit
this
this
body.
I'm
not
sure,
though,
might
not
work
that
way
anyway,
so
I
don't
know
how
to
anyway.
I
don't
know
what
the
process
is
for
getting
this
approved
by
the
cpc,
but
please
approve
this.
Thank
you.
B
A
Yeah
yeah
great
yeah,
and
I
I'm
curious
as
to
how
it
works.
You
know
I
hope
everything
works
well
in
the
automation
and
it's
certainly
something
we
can
consider
on
our
side.
Here
too.
A
D
And
offhand
does
anybody
know
what
a
majority
of
the
voting.
D
A
A
E
E
D
I
You
can
just
you
can
merge
that
in
two
weeks
and
nobody
else
did
rich.
B
Also,
we
can
send
an
email
to
the,
and
this
would
be
a
task
for
dawson.
I
assume
email,
the
board
for
visibility
and.
D
C
E
C
I
I
I
I
guess
in
the
the
vein
of
node
and
charter
stuff,
I
probably
should
have
brought
this
up
earlier,
but
we've
officially
sunset
com,
common
node.
I
I
I
don't
think
there's
a
de-chartering
process,
which
is,
I
think,
fine,
but
wanted
to
give
that
heads
up
as
well.
E
I
I
realized
I
didn't
make
an
announcement
thing
about
that
and
that
probably
would
have
been
fitting
yeah.
But
yeah
and
michael
said
that
he
there's
there
will
be
probably
substantial
changes
that
do
come
as
a
result
of
that
and
that'll
be
something
that
we
do
have
to
get
word
approval
on
most
likely
so
yeah
yeah.
A
I
I
I
am
gonna,
do
the
opposite.
I
didn't
work.
I
A
G
Do
quickly
if
we
can
just
roll
back
to
the
issue
beforehand,
the
dojo
coc
I
actually
went
through
the
whole
thing
and
because
dojo
is
actually
now
leveraging
the
opengs's
coc
directly.
G
A
Yeah,
did
you
do
that
toby?
Did
you
thank
dylan,
I'm
going
to
do
that
now.
Okay,
great,
thank
you
in
advance.
Go
ahead.
B
And
so
I
I
wanted
to
pop
back
to
the
earlier.
We
were
talking
about
the
working
group
and
regular
meeting
schedule
and
we
updated
the
next
working
session
on
october.
19Th
would
be
canceled
due
to
the
conflict
with
the
conference
and
likely
low
attendance,
and
that
would
move
our
next
working
meeting
to
november
2nd
as
tech
strategy.
That
is
a
smack
on
the
same
day
as
our
in-person
board
meeting,
which
will
be
on
pacific
time.
I'm
thinking
that
will
probably
also
be
a
conflict.
Maybe.
E
B
Okay,
you're
right
apologies.
I
had
it
in
my
mind.
It
was
the
second
forgive
me
we'll
then
then
never
mind,
then
I'll
zip,
my
mouth,
but
it
is
that
time
of
year
where
we
do
start
to
look
ahead
to
like
potential
conflicts
due
to
holidays
and
stuff.
B
So
let
me
just
ask,
after
the
november
tuesday
november
23
regular
meeting,
which
often
is
low
attendance,
because
that's
just
prior
to
us,
thanksgiving
holiday
and
the
december
28
working
group
meeting,
which
is
smack
between
the
new
year
and
and
winter
holidays,
summer
holidays,
depending
where
you
are
in
the
world
that
a
lot
of
people
take
off
so
should
we
preemptively
cancel
the
28th.
C
I
will
update,
I
did
remember
one
quick
announcement.
We
have
three
new
board
members,
oh,
which
is
pretty
amazing.
We
had-
I
don't
know,
michael
if
you
want
to
give
an
update,
I'm
happy
to
give
an
update
or
sarah,
but
we
had.
We
have
a
new
platinum
director
from
microsoft.
Shane
boyer
welcome
shane
gareth,
who
many
of
you
know
from
the
node.js
days
who
served
on
the
node.js
board,
and
the
openjs
board
has
moved
on
to
a
different
role
at
microsoft
and
passed
the
torch
to
shane.
C
C
So
dan
is
now
the
gold
director,
and
then
we
had
an
end-user
director
election
and
alex
liu
from
netflix
was
when
that
seat
ran
unopposed,
welcome,
alex
who
replaced
g
a
friend,
guillerm
hermetto,
who
left
netflix
so
lots
of
moving
around
in
the
industry
inside
and
outside
companies.
C
A
A
Cool
yep,
I
want
to
double
back
to
something
we
talked
about
earlier,
I'm
just
kidding.
I
don't
have
anything
else.
We
just
keep
doubling
back,
which
is
fun.
Eight
minutes
left
anything
else.
We
want
to
talk
about
or.
B
We
talked
about
this
briefly
in
the
standards
working
group
meeting
earlier
this
week,
but
but
google
have
launched
a
program
called
sos.dev
for
rewarding
folks
who
are
fixing
you
know
security
issues
and
bringing
critical
open
source
projects
back.
You
know
kind
of
up
to
more
modern
security
practices.
So
sos.dev
looks
like
a
great
little
rewards
program,
check
it
out
and
think
about
whether
your
project
could
benefit
from
that.
So.
E
A
Cool
and
just
double
doubling
back,
I
am
actually
doubling
back.
I'm
closing
tabs
as
we're
talking
and
stuff
looks
like
jordan
does
have
a
comment
on
that:
ci
automation,
ad
link,
checking
that's
already
been.