►
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).
B
A
C
Very
good,
very
good
cool,
so
we
are
live
thanks.
Everybody
for
joining
another
episode
of
the
openjs
foundation's
cross
project
council
meeting
today
is
the
last
tuesday
of
march
in
the
year
2021
we're
working
off
of
issue
737.
C
I
see
another
attendee
waiting,
oh
I
will,
unless
maybe
he
was
already
promoted,
because
I
saw
him
on
the
list.
Yeah
thanks
everybody
for
joining,
don't
forget
to
add
your
name
to
the
the
doc
which
I
will
paste
in
there
and
help
take
notes.
We've
got
a
small
crew
today,
hustle
through
the
agenda
and
then
see
what
happens
from
there.
B
We've
got
a
few
so
tomorrow,
as
an
fyi,
this
will
be
super
fun.
The
web
driver,
io
team
is
gonna,
do
one
of
our
not.
We
cannot
q
a
sessions.
We
can't
call
it
ama,
because
amas
are
this
trademark
term,
apparently
ama.
So
is
that
true,
that's
true.
Reddit
has
a
trademark
on
on
on
ama
or
ask
me
anything.
So
we
have
a
q,
a
session
we've
rebranded
q,
a
session
and
with
the
web
driver.
I
o
team
they've
got
some
exciting
announcements.
B
That's
tomorrow,
wednesday
at
9,
00
a.m,
pacific
and
so
we'd
love
for
you
to
join
in,
listen
and
ask
questions,
and
that
kind
of
thing
other
exciting
announcements.
We
want
to
say
congratulations
to
nvm
on
their
latest
release,
good
job,
jordan,
and
then
we
also
announced
some
exciting
discounts
on
the
new
node
training
and
certifications.
B
Well,
they're,
not
new,
but
there's
some
new
features
to
that
platform
and
celebrate
we're.
We've
got
some
pretty
deep
discounts
on
the
certification,
training,
materials
and
tests,
and
you
know
check
that
out.
If
you
are
so
down.
C
Yeah
and
to
add
that
they're
they're
they
have
a
bunch
of
free
tickets
to
the
environment,
to
kind
of
try
it
out
and
get
used
to
it
before
you
actually
do
your
training,
which
I
think
was
learning
from
people's
experience.
You
know
their
suggestions
so
definitely
check
that
out.
B
Yep,
let's
see
other
sort
of
general
stuff,
we're
really
plowing
forward
on
our
plan
to
announce
openjs
world
speakers
really
soon,
and
so
that
should
happen
sometime
next
week.
B
We're
really
excited
about
the
talks
we
have
so
far
and
so
just
remind
her
to
register
for
the
event,
if
you
haven't
already
that's
on
june
2nd
and
I
feel
like
there
was
something
else
we
had
a
book
club
and
the
book
club
was
really
fun
and
I'm
always
saying
that,
because
there
were
people
that
said
they
were
going
to
come
to
book
club
and
they
didn't
make
it
and
I'm
not
saying
who
that
is,
but
I'm
looking
at
you
in
my
zoom
chat,
we'd
love
to
do
that
again.
D
A
B
B
We're
looking
for
the
next
book
is
like
kind
of
the
the
thing
and
we're
sort
of
chatting
about
that
sorry,
jokes
today,
so
that's
all
the
announcements.
I
have
the
end.
C
Well,
I
dropped
a
link
to
the
no
jazz
tweet
about
the
certifications
and
stuff
too.
If
anybody
wants
to
help
promote
it
or
just
find
out
more
information,
it's
a
tweetbread,
so
the
other
few
links
in
there
for
oh,
no,
that's
not
the
tweet
thread,
that's
a
different
one,
but
that's
still,
I
think
the
right
tweet
right,
yeah
yeah
about
the
trainings.
C
I
guess
I
will
say,
because
I
just
confused
myself
that
there
is
the
node
survey
is
happening.
I
think
it's
still
happening.
I
think
it's
still,
you
know
open.
So
you
know
the
first
10
years
were
pretty
good
and
we're
looking
for
the
next
10
years
and
and
there's
a
group
of
us
who
are
trying
to
plot
that
out
figure
out
what's
important
and
stakeholders
and-
and
you
know,
constituencies
priorities
things
like
that.
C
So
if
anybody
has,
you
know
any
input
on
that
any
thoughts
about
that
feel
free
to
take
the
survey
here
in
this
group
or
anybody
watching
live
check
it
out.
C
So
that's
another
announcement
cool
with
that
we
can
jump
into
the
agenda.
I
suppose
is:
was
there
any
sorry
that
was
a
bad
page?
Reload
was
there?
Is
there
anything
from
the
board?
I
mean,
I
guess,
there's
nobody
here
from
the
board,
but
I
don't
know
if
there
was
a
meeting
last
week.
B
There
was,
there
was
a
meeting
on
friday.
Obviously
our
our
two
cpc
board
director
reps
are
not
present
today,
so
we'll
have
to
get
an
update
from
them
next
time.
C
Sounds
good
all
right
cool,
so
if
we
are
to
jump
into
the
agenda,
the
first
issue
is
actually
from
the
summit.
Repo
issue
306.
I
think
that
this
was
maybe
talked
about
a
couple
of
weeks
ago,
and
I
actually
I
commented
here,
but
I
wasn't
in
that
meeting.
So
I
don't
know
the
conversation,
but
I
grabbed
from
the
notes
to
drop
it
in
there
because
we
were
talking
about
it
in
the
the
node.js,
tooling
meeting
joy,
you
ran
it
last
time.
C
Did
you
do
you
have
anything
to
share
on
that
front?.
B
Yeah
so,
and
our
last
meeting
and
after
the
discussion
with
the
group
present,
you
know
it
became
pretty
clear.
There
was
consensus
for
us
to
not
plan
on
running
any
kind
of
conjoined
event
with
the
june
2nd,
open,
js
world
and
instead
sort
of
keep
the
conversation
open
for
potentially
doing
something
else
in
the
fall.
B
There
are
a
couple
of
like
lf
events
that
are
more
gener
general,
like
open
source
summit,
north
america,
and
that
kind
of
thing
that
are
that
are
are
still
on
for
in
person,
and
there
was
a
conversation
about
whether
that's
something
we
might
want
to
arrange
like
a
meet
up
there.
If
there
were
going
to
be
a
chunk
of
folks
who
would
be
planning
to
attend
one
of
those
events
but
effectively.
B
I
think
our
group
agreed
last
week
without
necessarily
memorializing.
G
B
Anywhere
that
we
wouldn't
do
it
with
openjs
world
on
june,
2nd
so
not
sure
what
we
need
to
do
to
sort
of
update
this
ticket.
Probably
just
maybe
comment
as
such
that
we're
we're
keeping
the
option
open
for
something
in
the
fall
that
could
be
in
person,
but
but.
C
Yeah
yeah
yeah,
we
can.
We
can
comment
on
the
issue
and
just
maybe
keep
it
in
mind
and
the
tooling
group
we
were
thinking.
We
might
do
something
in
the
fall,
but
I
don't
know
if
we
were
thinking
in
person
or
or
just
online,
and
I
I
wonder.
I
think
that
the
collab
summit
is
a
great
thing.
C
The
in-person
ones
were
really
effective,
the
virtual
ones,
perhaps
less
so,
but
maybe
that
just
presents
an
opportunity
to
figure
out
different
ways
to
approach
it
and
I'm
even
wondering
if
it
should
just
be
more.
You
know
focused
one-day
things
with
each
group.
You
know,
like
the
tooling
group
could
just
you
know,
plan
their
own
dang
summit
online
for
now,
and
you
know,
spend
a
day
working
stuff,
but
anyway
it's
something
I'm
thinking
about,
but
I
don't
really
have
any
actions
or
direction
either.
B
Could
be
an
interesting
thing
for
just
putting
this
in
our
in
a
future
pocket
like
an
interesting
discussion
to
have
at
one
of
our
working
group
sessions
like
if
we
were
to
take
a
topic
of
let's
reimagine
collab
summits
in
a
post
covered
world?
What
does
that
look
like
that
could
be
interesting?
Yeah.
C
I
agree,
I
agree
cool.
I
had
another
thought,
but
I
think
I
just
lost
it,
so
it
doesn't
matter
cool
all
right.
Well,
we'll
just
kind
of
leave
that
where
it
is
for
now
and
at
some
point
we
could
take
the
agenda
label
of
it,
but
something
to
think
about
next
on
today's
agenda,
private
slack
channel
for
node.js
build
team
machine
management
closed
since
answered.
Well,
no,
a
closing
since
answered
was
not
actually
closed.
So
I
will
close.
C
This
issue
looks
like
everything
is
sorted
here,
so
that
seems
fine
cool
closing
that
issue
moving
on.
This
is
actually
the
thing
that
I
was
thinking
about
and
then
lost
it
travel
fund
allocation
for
2021..
A
That,
last
time,
okay,
what
michael
shared
with
us
was
this
had
been
brought
to
the
attention
of
the
board
that
had
to
do
further
discussing
about
it
and
come
back
to
us.
Okay,
I'll,
come
back
with
some
movement
around
it.
C
Yeah
yeah,
okay,
the
gist
is
that
the
travel
fund
was
diminished.
I
don't
want
to
say
I
don't
want
to
be
hyperbolic
a
lot
and
the
thinking
is
that
traveling
by.
A
Say
drastic,
but
I
don't
want
to
be.
There
was
two
comments
that
were
made
one
by
me,
suggesting
that
the
money
saved
that
way
should
be
reinvested
in
other
related
efforts,
such
as
diversity
and
inclusion,
which
are
tightly
related
to
this
fund,
and
I
think
tyranny
brought
up
the
fact
that
many
people
had
complained
that
in
the
rest
of
the
world,
people
were
actually
traveling
now
or
were
able
to,
and
so
it
felt
very
american
or
well
western
centric
to
have
that.
C
Perception,
yeah,
and
also
who
knows
we're
not
even
halfway
through
the
year,
things
are
generally
improving.
Will
there
be
more
travel
in
the
second
half
of
the
year?
You
know
what
I
mean
it
depends
on
what
continent
you.
A
G
Yeah
for
what
is
worth
at
microsoft,
we
still
have
no
trouble,
no
participation
in
online
events
worldwide.
G
Yes,
that's
so
of
kind
of
respect
of
how
things
are
going
in
other
countries,
so
we
don't
want
to
start
doing
things
in
the
u.s
if
things
improve,
if
in
other
countries
are
nothing
doing
okay,
I
think
so
we
are
in
a
you
know,
travel
situation
for
now.
B
A
C
Cool
well,
we
will
defer
this
issue
till
next
time
and
see
if
there's
any
sort
of
updates.
C
Moving
on
the
this
is
issue
711.
This
is
renaming
master
branches.
I
think
that
the
rename
has
largely
happened
and,
if
I
remember
correctly,
scrolling
down
suggestion
to
email
folks,
I'm
pretty
sure
I
saw
that
email
go
out,
confirm
that,
for
me,
jewelry.
C
Great
so
do
we
think
I
mean
I
guess
we
can
check
off
the
standard
commission
communication
channels,
encourage
other
folks
possibly
create
a
dedicated
place,
which
I
think
we
decided
would
just
be
the
infra
channel
and
eventually
address
issues
uncovered
by
projects
implementing
this
change,
which
I
think
is,
if
you
say
eventually,
then
maybe
that
just
needs
to
be
a
new
issue.
If,
if
things
come
up
or
you
know,
multiple
things
does
that
seem
fair?
We
can
check
all
the
boxes
on
this
issue
description
and
then
call
this
done.
A
Yeah,
I
think
so
I'm
wondering
if
how
to
handle
issues
like
this,
we
would
sort
of
want
to
have
a
look-
and
you
know
maybe
like
three
month
or
quarter
or
like
something
to
just
check
that
we
can
actually
really
close
this
and
there's
like
no
pending
issues
and
then,
like
the
you
know,
pounding
from
I
I
don't.
I
don't
really
know
how
to
handle
this.
B
C
And
that's
why
I
stopped
using
ruby.
That's
a
good
question.
What
I've
seen
in
the
node
space
is
that
a
lot
of
projects
have
have
switched,
but
some
haven't
and
that's
because
of
infrastructure
and
whatnot.
So
yeah.
A
I
don't
know:
do
we
have
a
list
of
the
orgs
of
every
openjs
foundation
project,
someone,
okay,.
C
C
Great
michael
has.
H
B
Who
has-
and
you
know
you
know
if
there's
chance,
somebody's
stuck
on
something
or
you
know
whatever
right.
A
That's
a
the
fact
that
you
bring
that
up.
Jordan
makes
me
think
that
this
is
does
it.
Would
it
feel
like
this.
A
A
A
No
it
just
like
just
the
way
you
brought
it
up
felt,
oh
this.
This
can
feel
that
way,
and
I
actually
do
do
want
to
take
a
step
back.
If
I
think
that
feedback
is
valuable
and
important,
and
I
do
want
to
step
back
and
doing
like
a
fun
three-hour
script
exercise
that
potentially
has
human
downsides
feels
like
a
different
project.
Certainly,
so
I
think
this
is
an.
H
Important
point:
well,
I
more
think
that
the
the
thing
that's
useful
is
making
sure
every
foundation
project
maintainer
is
aware
of
the
desire
for
the
shift,
if
necessary,
is
informed
of
the
reasons
why
it's
important
and
if
their
reasons
for
pushback
are
non-pragmatic
or
technical
in
nature,
then
to
avoid
potential
turbulence
around
those
topics.
It's
probably
worth
arranging
private
discussions
to
educate
those
maintainers
we're
unrelated
to
whether
they
actually
make
the
change
or
not.
But
once
someone
is
informed
and
philosophically
aligned.
H
A
At
least
it's
very
clearly
and
well
articulated,
and
I
think
it's
important
to
hear
that.
Thank
you.
C
It
looks
like
node,
you
know,
I
need
to
go
through
this
whole
issue,
but
it
looks
like
you
know.
There
are
some
issues
and
also
some
folks
who
are
just
not
into
it,
but
I,
but
I
went
there
partially
toby
because
michael
wrote,
a
script
that
will
go
through
all
the
repos
in
an
org
and
you
know
check
the
branches.
So
I
thought
if
you
were
gonna,
write,
something
that
might
be
either
useful
or
it
might
already
be
written
depending
on
how
far
you're
going
so.
C
The
last
thing
I
posted
was
michael's
comment,
which
has
the
the
script
in
it.
C
Cool
all
right
so
we'll
leave
this
one
for
now.
I
will
close
this
our
issue,
though,
and
or
or
do
we
think
we
should
leave
this
open
for
now?
I
I'm
I'm
torn.
I
think.
B
Other
additional
steps
to
take
right
at
this
moment,
and
I
I
think
we
could
possibly
close
it
and
find
other
things
to
support.
D
C
Oops,
like
commented,
without
closing
there,
we
go
cool
so
that
one's
closed
next
up
is
a
issue
699.
This
is
the
dni
improving
diversity
and
inclusion
issue.
I'm
not
sure
what
we
have
for
updates
on
this
toby.
Do
you
have
any
thoughts,
jory.
B
Well,
I
can
speak
to
a
very
specific
sub-sub-component
of
this
project,
which
is
that
the
the
last
couple
of
working
group
meetings
now
for
the
cpc
we've
tackled
a
specific
set
of
changes
that
we
want
to
propose
to
the
cpc
for
the
code
of
conduct
and
handling
code
of
conduct
reports,
and
that
task
is
currently
with
sarah
divi
and
myself
to
memorialize
some
of
the
working
groups,
consensus
agreement
in
a
in
their
working
session
on
what
the
proposal
should
look
like
that's
in
review.
B
It
should
go
to
the
coc
working
group
team.
Those
folks
have
been
brainstorming
on
this
this
week,
we'll
have
a
follow-up
meeting
to
discuss
and
then
bring
that
to
a
cpc
for
for
discussion
and
hopeful
ratification
so
that
yeah.
C
Yeah,
I'm
sorry
to
interrupt
you.
I
think
that
we've
been
doing
two
separate
things
in
the
working
sessions
and
I
can
see
how
the
code
of
conduct
and
moderation
work
sort
of
could
apply
to
the
dni
effort,
but
I've
been
thinking
about
them
differently.
So
I
don't
I
mean
separately.
I
should
say
thank
you
for
that
update,
but
there
is.
A
Yes,
I
will
take
the
action
item
to
organize
a
meeting
with
folks
that
were
interested
in
order
to
discuss
the
survey
that
we
want
to
do
and
see
how
to
move
forward
with
that.
A
We've
discussed
a
number
of
different
options
around
this
and
are,
while
still
looking
at
like
different
options
and
on
as
a
second
as
a
second
part
to
that.
I'm
also
going
to
organize
a
meeting
with
folks
at
the
w3c
who
are
interested
about
this
issue
too,
and
looking
at
also
working
on
a
survey
to
see
how
we
can
synergize
this
this.
These,
you
know
two
organizations
wanting
essentially
to
do
the
same
work.
C
Great,
thank
you
so.
C
Sorry,
please,
I
was
just
gonna
say
we'll
we'll
do
we'll
we'll
try
to
pull
a
meeting
together.
That's
a
non-working
session
meeting,
just
sort
of
yeah,
we'll
figure
out
a
time
to
get
together.
A
Okay,
I'll
set
that
up
and
share
it
in
slack.
C
Cool,
thank
you
toby.
Thank
you,
jory,
or,
should
I
say
jory,
I
see
your
exclamation
point.
Sorry
cool
last
issue
on
the
agenda
is
the
this
dcocla
stuff
jory?
I
don't
know
if
this
was
talked
about
last
week
or
if
there's
any
sort
of
update
here
I
know
we
were
kind
of
waiting
on
something.
B
It
was
so
just
to-
and
I
think
brian
updated
the
issue
with
the
latest
so
as
an
fyi
brian
warner
has
been
working
with
the
pro
bot
dco
folks
to
implement
some
changes
and
some
features
to
probot
dcl
that
will
work
more
fluidly
with
our
systems
and
they've
been
making
some
progress
but
running
into
little
minor
issues
here
and
there
that's
slowing
things
down.
B
Obviously,
the
pro
bots
dco
team
is
it's
an
open
source
project
and
they're
all
they
all
have
other
jobs
and
that
sort
of
thing
so
there's
no
timetable
exactly,
but
we
we
are
making
progress
and
hope
to
have
hope
to
have
it
soon
enough.
As
a
reminder,
our
projects
are
able
to
use
whatever
dco
or
cla
tool.
They
they
use
dto
or
cla
if
they
like,
or
nothing
and
there's
a
couple
options
for
each.
So
these
are
just
options:
cool
cool
cool.
C
Great,
that
concludes
our
agenda.
Doesn't
it?
I
guess
the
one
thing
that
we
should
address
is
next
week's
working
session.
I
don't
know
if
we
are
doing
coc
stuff.
There,
moderation,
jory,
you've,
got
comments.
B
Yes,
I
have
comments.
I
have
thoughts,
so
you
know,
I
think,
it'd
be
great
if
we
could
maybe
plan
a
couple
of
weeks
of
working
group
meetings
out
in
in
a
bit
of
an
advance,
because
we've
got
so
many
different
things
we
want
to
make
progress
on.
We
have
a
tech
strategy,
work
that
I
think
would
be
dope.
We've
got
jslandia
stuff
that
would
be
dope.
We've
got
obviously
the
dei
and
the
coc
stuff.
B
C
That
makes
sense.
So
what
do
you
have
a
sense
of
what
we
should
work
on
next
and
are
you
it
sounds
to
me
like
you're,
saying
we
should
plan
to
kind
of
alternates,
not
the
right
word,
but
just
have
action
items
out
of
each
one
and
then
can
kind
of
rotate
them
more
and
have
progress
come
through
yeah.
B
Yeah
and-
and
I
think
it'd
be
cool
like
so.
We
know
because
we're
good
at
calendars.
B
And
we're
so
not
good
at
calendars,
but
we
know
that,
like
you
know
the
on
on
on
the
sixth,
so
that's
next
week
and
on
the
20th
you
know
we
can.
We
can
kind
of
pick
a
couple
of
topics
for
say
april.
May
you
know
before
let's
work
on
text
strategy,
let's
work
on
on
the
april
6
meeting
or
let's
work
on.
C
Yeah
so
one
thought
that's
coming
to
mind
and
anybody
feel
the
interject
if
they
have
something
they
want
to
add
here,
but
maybe
we
should
have
an
issue
for
each
of
these,
like
we
have
for
the
the
dni
one
and
if
we,
if,
if
we
have
some
work,
that
a
small
group
can
go
and
do
they
could
report
it
back
to
this
to
the
cpc
meeting,
because
you
know
like
today,
we
would
probably
have
a
good
20
minutes
left
over.
C
That
could
be
a
good
chunk
of
time
for
an
update
on
on
any
of
that
sort
of
work.
So
we
can
have
a
meeting
focus
on
it
figure
out
what
the
action
items
are.
People
can
go
off
and
do
them,
and
then
we
could
report
back
to
the
cpc
meeting
on
any
progress
there.
If
we
wanted.
C
So
I
mean
that
makes
sense
to
me
jory
and
everyone.
What
do
we
wanna
pick
something
to
pick
up
next
or
do
we
think
that
we
need
to
touch
on
something
that
we're
already
working
on
for
next
week?.
I
I
don't
want
to
over
engineer
well,
I
was
going
to
say
that
I
think
jslandia
hasn't
been
discussed
in
a
while
and
it
might
be
good
to
talk
about
it
and
I'll
lose
it.
I
don't
want
to
over
engineer
it,
but
maybe
having
a
rotation
would
be
good
kind
of
like
what
jory
said,
or
maybe
these
things
need
to
spin
off
into
their
own
working
groups,
and
we
can,
I
don't
know
now,
I'm
over
engineering
again.
I
was
just
going
to
nominate
jsyllabia.
C
So
I
agree
with
you
on
both
of
those
I
think
jslandia
would
be
good
for
next
week,
partially
thinking
about
the
upcoming
events
and
just
making
sure
that
we're
ahead
of
the
game
and
can
you
know
maximize
any
sort
of
promotion,
but
also
fun.
You
know
we
can
have
fun
with
it
and
do
fun
things
and
whatnot.
I
I
do
think
that
maybe
some
of
these
things
would
not
be
bad
to
have
its
own
meeting
like
toby
had
mentioned
earlier.
C
You
know
the
the
dei
work,
maybe
that
just
kind
of
has
its
own
meeting
and
we
sort
of
work
through
that
with
that
cadence.
Those
are
my
two
thoughts.
B
I'd
be
down
for
doing
js
landing
next
week,
because
well,
one
of
the
kind
of
foundation
to
do's
is
a
mvp
of
like
the
passports
and
and
I'm
confident.
We
will
have
something
to
show
you
next
week
and
we
can
brainstorm
on
that
and
cool.
It
sounds
fun.
B
C
Great,
do
we
also
want
to
plan
for
the
the
working
session
beyond
that.
B
B
So,
just
because
this
this
is
sort
of
like
a
like.
What's
the
word
I
want
to
use,
this
is
a
hangover
discussion,
but
that
sounds
like
it's
been
drinking
a
lot
and
that's
not
the
case.
B
I
know
I
apologize
so
a
carryover
conversation
that
I
think
we've
been
having
since
off
and
on
since
before
the
merger,
which
is
like
you
know.
How
do
we
think
about
telling
the
story
of
like
the
technologies
in
our
foundation?
How
do
we
think
about
like
catering
to
or
and
describing,
and
perhaps
the
types
of
projects
that
are
going
to
be
a
great
fit
for
the
foundation?
B
That
kind
of
thing,
and
it's
always
one
that
we
kind
of
hit
when
we
get
a
new
project
application
and
we
kind
of
go?
Oh
well,
this
you
know,
we've
got
this
rubric,
but
there's
also
an
element
of
like
feeling
to
it,
and
I
think
it'd
be
great
to
maybe
define
that
a
little
bit
further.
That's
something
that
I
know
robin
would.
B
C
C
Yeah
yeah,
I
mean
obviously
save
that
thought
for
later
joe,
okay,
okay,
I
I
mean
I'm
game.
I
I
this
makes
sense
to
me
and
I
think
it
kind
of
raises
some
questions
for
me,
cool.
Do
you.
C
A
Yeah,
if,
if
I
may,
and
if
you're
in
the
calendar
and
issue
space,
I
actually
think
that
what
we
have
for
amp
that
I
don't
know
where
it
comes
from.
I
wonder
if
it
doesn't
come
from
here.
Actually
works
really
well
like
one
issue
with
all
of
the
meetings
that
we're
going
to
have
planned
and
the
topics
that
are
going
to
be
discussed.
B
A
C
I'm
glad
that
you
know
that
they
pay
you
jory.
C
So
thank
you,
but
also
I'm
glad
about
that.
Let
me
know
how
I
can
help
to
you
know.
Consider
me
a
resource.
You
know
where
to
find
me
got
it
cool.
So
that's
like
two
working
sessions.
We're
thinking
about
is
that
good
enough
for
now
and
the
dei
stuff
will
spin
off
into
a
separate
meeting
its
own
meeting
and
then
we'll
just
see
in
terms
of
this,
the
coc
and
moderation
work
we'll
we'll
wait
for
more
progress
there
and
then
go
from
there.
B
Hello,
that
sounds
good.
C
Sorry,
paris,
you
joined
right
as
we
were,
reaching
the
end
of
our
business.
B
Cool,
no,
I
can't
think
of
anything.
C
It's
okay,
we
should
one
thing
that
comes
to
mind
is
like
incubating.
You
know.
I
know
we
have
a
couple
of
projects
there
right.
Do
we.
B
Do
yeah
divya
and
I
are
going
to
talk
to
one
of
our
incubating
projects
native
script
next
week
they
have
a
bunch
of
cool
stuff,
coming
up
that
they're
going
to
be
announcing
and
so
they've
been
busy
busy,
but
that's
a
hot
potato
and
then
other
stuff.
That's
just
you
know,
heads
up
and
fyi.
The
standards
working
group
has,
after
talking
to
a
whole
bunch
of
projects
and
evaluating
all
of
the
options.
B
At
our
last
meeting,
we
elected
to
focus
on
two
strategies:
the
first
one
being
the
educational
resources
and
curation
for
people
who
are
hoping
to
onboard
into
what
mike
champion
is
coined
standards,
culture
which
I
think
is
like
mwah,
it's
a
great
term.
B
B
So
we're
also
going
to
be
brainstorming
how
to
tackle
that
process
and
if
you're
interested
in
that
join
us.
C
Cool
I'm
reminded
of
a
potential
calendar
conflict
for
next
week
is
that
right.
B
Yes,
it
looks
like
we
do,
have
a
conflict
for
the
standards
working
group
and
the
cpc
working
meeting.
So
we
will
we.
D
C
I
I've
turned
on
the
video
and
kept
the
mic
yeah.
I
can
see
michael
isn't
here
today,
so
what
I
can
share
is
we
had
our
board
meeting
last
week.
I
thought
there
was
a
lot
of
really
interesting
stuff
shared
by
rachel
around
growth,
with
our
newsletter
growth
of
the
newsletter.
I
Exciting
news
other
board
related.
I
don't
think
there's
any
other
board
related
news
that
we
haven't
shared
here.
Just
the
summit
approaching
and
planning
for
the
summit,
and
things
like
that.
I
C
Great
and
then
I
don't
know
if
there's
any
takeaways
from
anything
regarding
the
travel
fund,
I
know
we
kind
of
touched
on
it
briefly
before
you,
you,
you
got
here,
but
there's
anything
to
share
there.
Let
me
know.
I
C
E
We
have
a
webinar
or
a
q,
a
tomorrow
with
web
driver
and
node
certification
and
training
big
sale.
Those
were
the
three
things
that
I
had.
C
Great
yeah,
that's
what
we
talked
about
earlier,
good
good,
great,
all
right!
Well,
I
can
give
everybody
everybody
back,
10
minutes
if,
if
they'd
like,
and
we
can
call
it
a
wrap.