►
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
Great
looks
like
we
are:
live
thanks:
everyone
for
joining
another
episode
of
the
cross
project
councils.
Sorry,
the
open
days,
foundations,
cross
project
council
meeting
today
is
the
second
of
february.
A
I'm
just
dropping
some
links,
I'll
do
my
usual
hi
friends
in
the
chat
and
so
yeah.
Thanks
for
joining.
Do
we
want
to
start
with
any
announcements.
A
B
Oh
announcements,
so
a
reminder
to
everyone
here
we
are
really
excited
to
get
as
many.
You
know,
folks
in
the
community
submitting
cfps
for
openjs
world
as
possible,
that's
going
to
be
a
remote
like
virtual
event
and
so
in
in
june,
and
we've
got
a
great
programming
team
together.
We've
got
some
awesome
keynotes
that
we've
announced
as
well
we're
going
to
be
doing
some
more
like
content
and
storytelling
around
some
of
the
stuff.
B
You
will
expect
to
see
in
the
program,
but
if
anybody
is
interested
in
submitting
a
talk,
we
are
doing
an
ama
tomorrow.
If
you
are
interested
in
getting
involved
in
reviewing
the
the
cfps,
maybe
you're
not
ready
to
submit
a
talk
yet,
but
you
want
to
help
curate
the
program.
B
We
would
love
to
have
you
if
you
want
to
get
involved
in
the
programming
committee's
work.
That's
also
something
that
we
would
love
to
invite
you
to
come.
Do
so.
That's
we're
really
pushing
on
that
and
we
think
it's
going
to
be
an
awesome
event
and
you
know
come
get
involved,
is
my
message
there
and
I
don't
remember
what
time
our
ama
is
in
the
but
it's
tomorrow
and
I
will
we'll
be
there.
B
I
think
another
one
to
share
is
we're
starting
our
newsletter
out
to
all
of
our
js
landia
participants,
so
javascript
landia
is
going
really
well.
We've
been
really
excited
about
the
interest
and
the
support
for
that
program
and
so
we're
starting
our
badges
and
conversations
and
that
sort
of
thing
with
that
community
now.
So,
if
it's
something
you
want
to
get
involved
with,
that's
another
space,
we'd
love
to
have
love
to
have
folks
from
the
community
hanging
out,
and
I
need
to
go
to
my
list.
F
B
I
don't
know
what
the
latest
is,
because
there's
a
somewhat
of
a
at
the
moment,
there's
currently
a
manual
step,
but
it's
like
150
160
people.
It
was
200
a
week
and
a
half
ago,
oh
wow,
see
I'm
way
off.
G
It's
the
auto
join
process
is
automated,
but
before
we
take
that
those
names
and
put
them
on
the
website,
we
just
give
it
a
a
really
a
quick
preview.
So
we
do
update
the
website
weekly,
even
though
your
joining
process
is
immediate.
B
Cool,
oh
another
thing:
this
is
the
last
little
thing
we
started
a
book
club
in
the
slack
workspace
if
you
want
to
come,
be
a
book
nerd
with
us
join
hash
book
dash
club
and
come
geek
out.
D
B
It
seems
like
we're
focused
on
largely
non-fiction
that
has
to
do
with
open
source
javascript
standards
programming.
You
know,
tech
culture
like
that
kind
of
vein,
and
people
are
just
sort
of
talking
about
different,
like
owen
buckley
shared
that
he
read
like
linus
torvald's
autobiography,
and
so
that's
fascinating.
You
know.
D
A
We're
gonna
start
reading
snow
crash
here
at
home.
My
young
son
maybe
skip
any
parts
that
need
to
be
skipped
but
generally
get
into
that
anyway.
Put
that
on
the
book
club
list
cool
anything
else,
any
other
announcements
or
anything
from
the
board
or
whatnot.
D
G
Wait
an
expedition,
a
road
road
show
just
to
get
some
feedback
from
the
projects
their
tscs
and
to
share
some
sort
of
updates
that
you
all
have
been
doing.
The
cpc
and
then
kind
of
half
of
it
is
also
getting
feedback
from
the
standards
working
group.
The
standards
working
group
had
a
strategic
planning
session
and
really
wanted
some
specific
feedback
from
the
projects.
E
G
Yeah
we've
reached
jerry
reached
out
to
the
amp
folks.
G
Of
the
a
lot
of
the
larger
projects
so
far
that
are
they
start
tomorrow,
I
think
happening
over
the
next
couple
of
weeks
and
then
we'll
start
cascading
as
well,
but
yeah.
A
I
can
announce
that
we
have
a
new
dog
he's,
a
puppy
chihuahua
and
I
have
a
puppy
lab
in
here
too.
So
I
keep
muting
because
they
keep
wrestling
and
making
crazy
noises.
H
A
He's
pretty
chill
so
far,
we'll
see
so
I'll
do
my
best
to
run
the
meeting
and
manage
puppies
cool.
So
speaking
of
we'll
get
into
the
agenda,
the
first
issue
is.
A
Master,
I'm
gonna
try
to
click
into
this
yeah
you
wanna
watch.
Let's
see
who
opened
this
toby.
Do
you
wanna
give
us
some
comment
or
update
or
anything.
E
I
mean
updates
no,
no.
This
just
came
up
because
this
came
up
in
amp
recently
that
we
wanted
to
make
sure
that
all
of
the
amp
project
was
rid
of
using
master
instead
of
main
github
has
now
made
that
way
easier.
You
can
in
the
settings,
essentially
change.
It's
a
it's
a
one,
setting
thing
that
just
like
re.
I
can't
find
the
words
basically.
J
F
E
But
what
it
doesn't
do,
however,
is
fix
all
of
the
infra
that
rely
that
assumes
master
as
the
main
branch
which
some
infra
does
and
some
doesn't.
It
depends
right,
yeah,.
D
F
Won't
update
links
that
are
like,
even
though
it
will
redirect
them.
In
most
cases,
it
won't
update
links
that
are
hard-coded
to
have
master
in
them.
But
if
you
change
them
to
have
capital
head,
then
it
will
no
longer
care
what
the
default
branch
name
is,
and
so
that
could
be
landed
prior
to
the
change
and
should
be
okay.
It's
it's
only
when
infrared
explicitly
needs
a
branch
name
and
is
not
using
it
directly
in
the
git
cli
that
you
can't
use
head
and
then
that's
trickier.
F
You
have
to
like
kind
of
coordinate
it
with
the
the
tool
with
github's
tool,
so.
E
Yeah
so
anyway,
the
point
was
just
to
say
that
we
should
do
this
at
the
cpc
level,
because
it's
fairly
straightforward
to
do
then
we
should
do
this
at
the
organization
level
for
openjs
would
be
my
belief
and
then
we
should
also
see
if
there's
how
we
can
help
the
projects
do
that.
D
Yeah,
I
think
specifically
for
the
like
our
projects.
I
don't
think
there's
that
much
activity
that
it
would
really
be
a
major
impact.
I
I
did
it
for
one
of
the
ones
in
the
node
project.
Node
on
api
last
week
haven't
heard
any
complaints,
yet
so
I'd
be
tempted
to
just
like
do
it
and
then
fix
things
up,
because
I
don't
think
there'll
be
a
severe
impact
for
us
and
it's
probably
good
to
just
do
it.
F
I
think
for
everything
under
our
org
it
we
should
yeah
like
it's
just
click
a
button,
and
it's
fine
exactly
and
I
think
for
projects.
The
challenge
is
that
anyone
who
doesn't
like
there's
two
challenges,
one
is
that
it
creates
a
timeline
entry
on
every
pr
when
it
retargets
them.
So
people
get
actively
notified
that
we're
renaming
it
so
on
a
large
project
like
node.
F
That
would
attract
a
lot
of
trollish
behavior,
that's
what
it
will
do
and
then
the
other
side
is
that
if
it
didn't
notify,
then
you
would
have
no
way
of
knowing
you
need
to
update
your
local
branches,
and
even
the
notification
isn't
very
clear
about
how
to
do
that.
So
anyone
who
is
in
the
middle
of
a
pull
request
is
going
to
potentially
be
confused
and
need
to
switch
their
branch
around.
It's
all
like
relatively
straightforward,
but
github
doesn't
like
surface
exactly
what
would
be
needed
to
make
it
a
non-problem.
F
F
D
D
The
node
project
has
been
talking
about
making
that
move
and
has
been
moving
over
a
bunch.
You
know
bit
by
bit,
so
I
think
that's
well
underway
the
node
one,
as
you
say,
may
be
the
last
one,
though
just
once
once
once
we're
comfortable
having
switched
everything
over
and
figure,
there's
we've
found
the
gotchas
and
stuff.
E
D
E
The
amp
perspective,
like
every
rapper,
except
the
main
one,
has
moved
and
the
main
one
is
to
to
move
this
quarter.
But
it
is
a
really
I
mean
a
significant
infra
work
to
get
to
get
that
done
and
to
make
sure
that
everything
continues
to
work
in
the
cicd
pipelines.
E
Yeah,
that
would
be
great,
I
think
communicating
about
this
would
be
great.
I
think
if
there
are
lessons
learned
that
can
be
shared
broadly
or
shared
inside
of
the
org.
I
think
that's
also
useful,
and
you
know
it's
a
really
small
thing
when
you
think
about
it,
but
it
is
also
a
sign
of
actually
caring
about
these
issues,
and
so
I
think
it's
also
worth
doing.
For
that
reason.
D
F
Is
that
the
only
thing
that
I
would
recommend
doing
first
is
just
quickly
grepping
through
each
repo
and
seeing
if
there's
any
occurrence
of
the
word
master.
If
there
are
none,
then
github's
new
flow
means
that
there's
no
technical
barriers,
just
click
the
switch
right
and
it's
fine.
And
if
there
are
some,
you
can
probably
update
them
all
to
be
head
and
then,
after
that's
landed,
just
click
the
switch
and
it's
fine
right
and.
F
D
Actually
has
to
you
know,
maybe
block
off
a
couple
hours
versus
somebody
could
say:
oh
I'll,
take
10
minutes
and
I'll
rename
them
all.
So
if
we
think
we
should
I'm
just
saying
if
we
actually
want
to
make
it
happen,
it
happens
sooner
than
later.
I'd
personally,
I
think
be
comfortable
that
we
just
renamed
them,
because
the
downside,
I
don't
know
that
it's
going
to
be
that
big,
even
if
we
miss
things
right
right
and
separately
in
terms
of
like
references
to
master
those
should
redirect
anyway
right
yeah,
that's
true!
So.
F
D
E
D
K
D
I
think
the
read
well,
the
redirect
should
fix
that.
I
think
when
we
do
them
later,
it's
to
me
that
would
fall
under
the
typo.
The
other
kind
of
thing,
where
we
just
give
them
a
notification,
because
there's
no
there's
no
substantive
change
there.
So
I,
if
we
rename,
if
we
rename
the
main
branch,
it's
now
a
typo
that
it's
pointing
to
the
wrong.
A
Cool
yeah,
I
dropped
a
a
link
to
a
hackmd
file
if
we
want
to
like
start
to
capture
some
suggestions,
some
tips,
some
things
to
be
worried
about,
and
efforts
to
get
a
blog
post
together.
A
Cool
so
yeah
michael,
were
you
gonna
just
go
in
and
rename
them
or.
D
Like
I'll
go
rename
a
few
basically,
what
I
would
say
is:
if
anybody
has
a
few
minutes,
just
go
in
and
rename
a
couple
and
all
you
know
I'll
do
the
same,
and
if
we
all
do
that,
we'll
have
them
all
done
by
next
week.
Right.
L
D
E
All
right,
sorry,
do
we
have
anyone,
that's
going
to
be
leading
the
blog
post.
If
you
want
to
do
this,
rachel
is
that
is,
does
that
fall
on
you
by
default
or,
like
I
I
don't
know
just
I
mean
I
think
it's
useful.
So
I
think
if
we
want
to
do
it,
we
should
say
so
and
if
we
don't,
we
shouldn't
have
a
draft
like.
C
I
think
I
mean
I
think
it's
really
helpful
content,
especially
for
other
folks
who
are
trying
to
figure
out
how
to
do.
This
sounds
like
it's
a
really
easy
thing,
so
I
think
my
recommendation
would
be
for
us
to
kind
of
capture
like
robin
said:
tips,
tricks
things
to
look
out
for
and
just
kind
of
create.
C
This
helpful
thing
like
this
is
easy
to
do,
and
this
is
how
we
did
it
and
I'm
happy
to
ping
this
group
to
say:
okay,
how
did
y'all
do
it
and
then
I
can
kind
of
glean
some
of
that
and
help
you
know
shape
the
you
know
shape
the
blog.
Is
that
helpful.
C
G
And
again
it
doesn't
have
to
be
pretty
what
joe,
with
the
hacker
document
just
start,
throwing
mud
on
the
wall
and
we
can
make
it
pretty
yeah.
Absolutely.
A
Sorry,
all
right
cool
great
great
great,
so
I
think
we
got
ways
to
move
forward
on
that
and
that's
awesome.
Moving
on
next
on
the
list
is
the
primary
cpc
director
election.
A
A
I've
got
some
interest
expressed
to
me
so
I've
I've
got
that
I
can
you
know.
Maybe
we
can
make
this
kind
of
a
last
call,
and
tomorrow
morning
I
will,
you
know,
drop
the
names
in
this
issue
and
then
request
quiet,
request,
candidate
statements
and
we
can
move
on
from
there.
There's
the
lab
too.
A
A
And
then
this
one
just
keeps
running
across
my
desk
yeah.
So
last
call
we'll
say
you
know
midnight
or
the
morning
or
whatever
reach
out
to
me
or
or
dory.
If
you
prefer
and
we'll
you
know,
announce
the
names
tomorrow
and
yeah,
like
I
said,
ask
for
candidate
statements
and
then
I
think
we're
just
going
to
have
the
vote
open
for
a
week
and
then
go
from
there.
L
A
Does
anybody
have
any
objection
to,
I
guess
for
one,
the
amount
of
people
and
for
two
should
we
just
get
it
started.
I
H
H
A
So
yeah
we
had
talked
about
you
know
making
like
one
last
call
today
stop
playing
with
that,
because
I
had
only
had
one
but
then
someone
else
reached
out
so
now
I
have
two,
so
you
know
I'm
fine
with
whatever
we
want
to
do.
We
did
say
we
would
open
it
up
today,
so
is.
Are
the
two
candidates
diverse.
C
A
No
all
right,
so,
let's
open
it
now
I
can
post
in
the
in
the
issue
after
the
meeting
the
candidates,
but
I'll
share
with
you
both
with
you
all
now
be
careful
that
the
two
candidates
are
toby
and
sarah.
I
A
For
sure,
okay,
absolutely
great
okay,
so
I
I
will
post
the
names
and
a
request
for
candidate
statements
after
the
meeting
and
we'll
move
forward,
teddy
quiet
cool
great,
so
that
answers
that
I
was
actually
stressed
out
about
that-
and
now
I
feel
great
next
up-
is
improving
diversity
and
inclusion
at
the
open.js
foundation.
A
We
had
a
working
session
on
this
last
week.
I
expect
that
we
will
do
it
again
this
week,
if
I'm
not
mistaken,
but
would
toby
or
jory
anyone
like
to
add
any
comment
here.
E
I'm
sort
of
blanking
on
this-
to
be
very
honest,
I
I
think
was
we're
due
to
speak
next
week
again.
G
G
G
You
know-
and
I
think
the
summary
is-
we
made
great
progress
last
year-
a
lot
from
the
bottoms
up
from
the
community.
So
thank
you,
but
we
still
haven't
reached
the
initial
goals
that
we
set
out
as
at
the
foundation
that
at
least
you
know,
we
have
that
we
report
out
to
our
board
of
directors.
So
still
a
lot
of
work
to
do.
But
yeah
we
made
a
lot
of
great
progress.
A
Yeah
we
made
a
lot
of
great
progress
and
last
week
on
the
working
session,
we
had
a
really
good
working
session,
a
lot
of
good
ideas
and
conversation
and
thoughts,
and
you
know
I
I
felt
like
it
was
the
beginning
of
the
beginning,
and
so
you
know
I
look
forward
to
working
more
on
this
and
you
know
I
know
I
thought
we
had
discussed,
that
we
would
do
it
again
next
working
session.
So
I
I
you
know
we
can
kind
of.
A
E
A
Yeah,
I
don't
see
why
I
wouldn't
be,
but
yeah,
I'm
not
sure
where
they
are
exactly.
A
No,
actually,
they
are
in
the
they're
in
they
are
in
the
the
working
session
meeting
issue.
So
that's
maybe
confusing-
and
this
is
one
of
the
things
that
I'm
hoping
to
kind
of
work
out
is
like
how
do
we
manage
these
sorts
of?
You
know
working
sessions
and
issues
and
stuff,
but
here's
the
actual
issue
for
the
working
session,
and
that
has
a
link
to
the
notes.
A
Yeah,
please
please,
and
I
guess
I
should
create
an
issue
for
next
week's
working
session
and
do
the
same
kind
of
thing.
B
Let
me
try
and
make
that
session
a
little
bit
more
focused.
I
I
think
we
covered
a
lot
of
ground
about.
You
know
sort
of
the
state
of
the
universe
on
this
topic
for
our
projects,
and
I
I
think
I
was
really
struggling
during
the
the
call
to
identify,
like
the
like
an
example
of
a
core
problem
to
sort
of
kind
of
reason
about,
and
so
I'd
love
to
maybe
brainstorm
what
some
of
those
are
yeah.
So
we
can,
if
we
can
do
that.
A
Yeah,
I
agree
and
that's
what
I
kind
of
mean
like
it
felt
like
the
beginning
of
the
beginning,
like
we
were
really
kind
of
putting
a
lot
of
thoughts
and
ideas
out
there
that
you
know
be
good
to
kind
of
focus
in
on
some
stuff.
A
Is
that
something
we
should
just
plan
to
do
at
the
beginning
of
the
meeting
and
work
through
at
the
meeting
or
jory?
Are
you
thinking
we
should?
You
know,
start
to
kind
of
figure
out
what
some
of
those
things
are
before
the
meeting.
B
B
G
A
And
I
think
another
thing
too,
that
we
talked
about
was
like
defining
what
we
even
mean
by
diversity.
You
know,
so
I
think
getting
something
like
that
in
place
would
be
a
great
thing
to
have
before
we
even
really
get
into
some
of
the
other
things.
A
All
right
great,
so
those
are
some
things
to
think
about,
and
we
can
you
know,
flesh
it
out
further
in
in
the
meeting
if
anybody
wants
to
talk
beforehand
or
slack
or
whatever
feel
free
to
reach
out
to
me
quiet
all
right.
Moving
on
the
next
issue
is
673
google
summer
of
code,
2021
brian's.
Not
here
I
don't
know
if
there's
much
to
talk
about
on
this
one
right
now.
B
I
he
and
I
kind
of
briefly
talked
about
this,
but
that
this
will
be
any
project.
That's
interested
in
requesting
a
and
working
with
the
google
summer
code
program
it'd
be
great
to
start
working
on
that
plan.
Now
it's
been
something
that
the
last
couple
of
years
has
snuck
up
on
us,
and
so
we
haven't
really
been
able
to
give
projects
the
kind
of
heads
up.
So
that's
one
thing
to
be
mindful
of
today.
A
Great,
thank
you
cool,
so
moving
on
the
next
item
is
remove
the
growth
stage.
This
is
pull
request.
650.
toby.
Do
you
have
any
updates
or
thoughts
on
this?
I
know
that
there's
this
pull
request,
as
well
as
the
work
in
the
project
status,
repo,
so.
E
If
my,
if
my
I'm
recording
correctly,
I
had
to
check,
was
the
amp
tsc
that
they
were
okay
was
removing
the
growth
stage.
They
were
so
I
updated
the
issue
with
this.
The
pull
request
in
the
the
project
status
representation,
I
think,
is
ready
to
be
landed,
and
I
think
that
this
pull
request
in
the
cpc
wrapper
is
also
ready.
E
It
might
be
that
we
need
to
do
a
double
check
to
see
if
there
are
reference
to
growth
projects
elsewhere,
that
we
need
to
update,
I'm
not
sure
that
that
was
done.
A
Thank
you.
Sorry.
I
keep
having
puppy
issues
great
yeah,
so
so
we
just
go
through
and
figure
that
out.
If
there's
any
references
and
then
we
think
we
can
land,
these
can.
B
The
only
other
place,
I'm
aware
of
reference
to
growth
stage
projects
are
in
the
project
status
repo
and
on
the
on
the
openjs
website
and
beyond
that,
it's
possible
that
growth
projects
have
referenced
themselves
in
such
a
way
on
their
own.
You
know
materials,
but.
K
K
A
B
So
the
next
issue
on
our
agenda
is
issue
632,
which
is
provide
implementation
guidance
for
the
dco,
slash
cla.
This.
B
This
is
also
brian
brian,
had
some
very
promising
updates.
As
you
may
recall,
brian
was
working
on
some
patches
to
the
dco
bot
that
we
wanted
to
see,
and
I
think
that
that
actually
has
been
successful
or
very
nearly
successful,
and
so
we
should
be
having
a
lot
more
to
say
on
this
issue
in
the
next
few
weeks.
For
those
who
may
want
to
use
the
dcf.
B
So
that's
not
much,
but
it's
it's
just
a
report
to
remind
everyone.
We,
like
the
dco
bot.
We
wanted
to
see
some
changes
for
our
projects.
We
think
that
those
are
basically
in
and
we
should
have
stuff
to
share
with
everybody
in
a
few
weeks.
A
Thanks
jory,
I
can
jump
back
in,
as
I
think
we
really
only
have
one
more
issue
here:
the
update,
the
onboarding
checklist
templates.
It's
a
pull
request
from
the
project
status,
repo.
This
toby
you
opened
four
weeks
ago.
B
D
D
E
Yeah,
no,
I
think
I
already
added
the
changes
to
some
of
the
new
on
boarding
entries
manually,
so
I'm
kind
of
surprised
that
that
was
not
merged
before
I
did.
That
apologies,
you
know.
A
Good
enough
cool,
it's
merged,
jory
you've
got
an
old
pull
request
open
here
for
documentation.
You
know
if
you're
really
wanting
to
merge
stuff.
B
Well,
I
do,
but
that
is
not.
I
need
to
go
back
to
that
and
really
pick
up
where
I
left
off.
I
kind
of
got
the
first
couple
of
checklist
items
documented,
but
we
were
still
kind
of
tweaking
some
of
the
required
like
some
of
the
requirements
of
the
checklist.
B
So
I
decided
I
better
wait,
but
anyway,
the
goal
of
that
eventual
pr
which
is
sort
of.
I
guess
now.
I'm
admitting
this
isn't
a
best
practice,
because
it'll
be
a
big
pr,
as
opposed
to
a
little
one
is
to
provide
more
clarification
for
projects
that
are
going
through
onboarding
about
like
what
it
each
step
means
and
like
what
needs
to
be
done
and
what
we're
looking
for
and
that
kind
of
thing.
So.
B
A
All
right
that
kind
of
wraps
things
up
and
I
don't
know,
does
anybody
have
anything
else
they
want
to
get
into
in
the
last
eight.
A
Minutes
I
could
give
that
time
back
to
you
all
and,
and
we
could
divvy
up
some
repos
and
go
switch
from
master
to
maine.
Since
you
have.
D
B
Think
the
last
thing
you
know
to
end
on
here
is
like
for
the
rest
of
the
week.
You
know
there's
some
stuff
happening
wednesday,
thursday
and
friday
wednesday.
We
have
the
ama,
so
you
know
help
with
that
and
and
sharing
that
out
thursday
is
our
program
committee
meeting
for
openjs
world
and
then
friday
and
we're
pulling
the
javascript
landia
working
group
back
together
to
work
on
the
next
phase
of
projects
for
jslandia.
B
So
any
extra
time
you
may
have
this
week
for
openjs
foundation.
Programs,
we've
got
it.
You
know,
we've
got
lots
of
things
to
do
so.
Come
join.
A
Cool
all
right:
well,
let's,
let's
call
it
a
wrap.
I
appreciate
everybody
taking
the
time
I'll
go
get
the
election
started
as
well,
so
maybe
jory
you
and
I
can
chat
real
quickly
after
the
meeting
to
to
get
that
moving
and
that's
good
cool.
All
right.