►
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
Cool
all
right:
well,
thanks
everybody
for
joining
another
episode
of
the
openjs
foundation's
cross
project
council
meeting
today
is
the
17th
of
august
and
we'll
get
right
into
things.
Yeah,
don't
forget
to
add
yourself
to
the
the
meeting
notes
and
if
anybody
helps
with
meeting
notes,
that's
always
greatly
appreciated
you
get
a
little
something
extra
with
the
holiday
gifts
and
whatnot.
What
am
I
looking
for
here?
Oh
yeah,
the
recording
yeah.
So
do
we
have
any
announcements
or
anything
before
we
get
into
our
agenda.
B
After
today's
cpc
meeting,
we
have
a
marketing
committee
meeting
for
those
who
want
to
hop
on
and
help
us
think
generally
about
marketing
and
rachel
could
probably
dive
into
the
agenda.
I
work
we're
also
excitedly
kind
of
thinking
about
the
open,
js
world
event.
B
That's
a
that's
a
topic
that
we'll
cover
in
both
the
marketing
call
and
in
our
bi-weekly
programming
committee,
calls
so
again
for
those
who
are
interested
in
helping
with
the
event
specifically
join
us
for
those
calls
or
if
you
want
to
help
kind
of
promote
either
case
studies
or
not
amas,
because
we
don't
call
it
that
anymore,
things
of
that
sort
and
then
on
the
marketing
side
that
that
meeting
is
later
rachel.
Do
you
have
anything
you
want
to
add
on
that
front?
B
One
other
quick
request
from
openjsf
ops
if
your
project
is
still
using
the
js
foundation,
cla
infrastructure
and
you're
interested
in
moving
over
to
the
in
keeping
your
your
cla.
And
you
want
to
move
over
to
the
easy
cla
system.
And
please
let
me
know
you
can
slack
me
or
whatever
we're
trying
to
programmatically
roll
that
out,
because
we're
certainly
running
into
issues
with
that
bot,
the
old
jsf
bot.
So
let
me
know
if
you're
interested
in
that.
B
B
And
jory
book
club
thursday
book
club
book
club-
oh
thank
you
yeah,
so
book
club
is-
is
this
thursday
at
3
p.m?
If
you're
interested
in
dialing
in
you,
obviously
don't
have
to
have
read
the
book,
I
mean
that's
part
of
the
joy
of
a
book
club
is
that,
like
maybe
20,
have
actually
read
the
book,
there's
some
great,
like
youtube
summaries
of
the
books.
B
If
you
want
to
go,
watch
those,
but
we're
talking
about
a
book
called
how
to
do
nothing
which
speaks
to
me
and
my
inner
sloth
and
then
also
a
book
called
braiding
sweetgrass,
which
is
a
very
interesting
book
by
an
ecological
scientist
that
has
a
lot
of
like
tran,
useful
translations
to
like
open
source
and
sustainability
and
so
really
excited
about
talking
about
those
books.
So
join
us
on
thursday.
If
you
would
like.
A
A
Node.Js
had
some
security
releases
right,
that's
a
that's
a
good
thing.
If
you're
using
node
check
that
out
cool,
if
there's
nothing
else,
we
can
get
into
the
agenda.
A
The
first
item
is
pull
quest.
789
and
toby
started
this.
A
It's
a
work
in
progress,
so
I
think
if
anybody
else
wants
to
add
stuff
in
there,
we
can
certainly
merge
this
and
continue
to
to
work
on
it,
but
I
think
it
would
be
great
if
anybody
wanted
to
throw
some
more
in
there
that
they
can,
if
they
have
a
moment
anything
else
on
this
toby.
Do
you
want
to
comment
or
anything.
D
D
So
that's
why
I
opened
it
that
you
know
that
way
it
it's
it's
a
bit.
Essentially
the
issue
was
we
don't
really
know
what
the
cpc
is
working
on
and
there's
well
more
clearly
like
there's
a
there's,
a
lot
of
policy
documents
in
the
root
of
the
cpc
directory,
and
this
is
not
obvious
to
newcomers
or
people
that
are
doing
stuff,
and
so
can
we
have
a
list
of
those
somewhere,
and
so
I
started
working
on
those
and
I'm
doing
such
a
list
they're
not
sort
of
super
easy
to
categorize
right.
D
A
A
Okay,
great,
thank
you
for
that
effort.
A
Cool
moving
on
the
next
item
is
issue
786.
This
is
clarify
requirements
around
coc
violation.
E
D
And
just
for
context,
I
think
this
was
a
follow-up
from
a
conversation
we
had
two
weeks
ago
where
we
wanted
to
open
such
an
issue,
which
is
why
I
opened
it
yeah.
So
maybe
I
should
put
make
that
clear
in
the
issue.
A
Sure
sure
that
makes
sense.
I
think
this
also
perhaps
relates
to
the
another
agenda
item
around.
You
know
contact
information
around
code
of
conduct
stuff
right,
so
I
don't
know
if
we
want
to
link
those
issues.
B
So
I
think
one
easy
one
is
that
they
that
we
require
them
to
add.
As
you
know,
particularly
for
the
new
projects
that
we
onboard,
we
can
go
back
and
retroactively,
get
this
for
the
old
projects,
their
their
reporting
method.
You
know
if
it's
a
a
form
that
they
maintain
or
some
other
list
that
they
maintain,
because
they
have
the
community
support
to
do
so,
and
that's
obviously
something
that
projects
can
can
choose
or
if
they
wish
also
to
delegate
that
to
our
cross
project
group.
That's
fine,
but
they
need
to.
A
So
reporting
method
you
mentioned,
I'm
not
sure
if
I
missed
any
other
bullet
points
from
that,
but
toby
also
mentions
you
know:
privacy,
probably
retention,
right
and
privacy.
A
I'm
just
trying
to
take
a
couple
of
notes
here
that
I
can
add
to
this
issue
any
any
anything
else.
B
I
think
yeah
escalation,
but
also
one
thing
that
would
be
great
for
the
future,
not
necessarily
from
day
one
but
would
be
some
kind
of
just
baseline
training
that
you
know
we
can
say:
hey
everybody
who's
on
the
lists
for
reporting
for
any
of
our
projects
has
taken.
B
You
know
some
session
that
we've
designated
as
a
baseline.
B
Yeah
as
a
requirement
for
I
mean
again
I'm
hence
saying
for
the
future,
because
we've
got
a
lot
of
people
who
are
yeah
currently
helpful
in
serving
these
roles
today
that
we
don't
want
to
bump
out,
but
you
know,
say
over
some
period
of
time
the
next
year
we
get
folks
all
taking
the
same
session
that'd
be
useful.
I
think.
C
As
a
extension
to
that,
do
you
expect
that
everyone
will
like
or
each
project
will
you
know
if
there's
something
a
project
disagrees
with
in
that
session
about
how
something
should
be
handled
should
do?
Will
the
projects
be
expected
to
precisely
uphold
whatever
is
taught
in
that
session?.
C
Okay,
no,
I
just
I
I
I
want
to
I.
I
largely
bring
that
up
for
the
case
where
I've
done
trainings
like
this
and
they
are,
they
have
been
misinformed
and
they
have
been
harmful.
C
Also
didn't
the
found:
doesn't
the
foundation
still
I.
I
would
hope
that
this
we
didn't
lose
this.
The
node
foundation
paid
a
lot
of
money
for
some
training
that
tracy
heinz
helped
get
set
up,
and
then
we
in
in
perpetuity
had
like
rights
to
that
training.
This
was
for
the
node
moderation
team.
Do
we
it
was
like
conflict
resolution.
I
think,
do
we
still
have
that.
F
I'm
not
aware,
I
have
not
heard
of
it,
but
I
I
think
I
know
who
I
can
where
I
can
find
out
and
get
it
from
yeah.
C
If,
if
we
do
still
have
access
to
that,
making
that
available
to
all
foundation
projects,
and
because
that
was
the
scope
of
it
was
have
anyone
be
able
to
take,
have
access
to
it?
I
think
we
paid,
like
you,
know
five
figures
for
it
and
then
like
three
hundred
dollars
or
something
to
retain
it
per
permanently.
C
That'd
be
nice.
If
we,
if
we
could
figure
that
out
and
resurface
that
yeah.
A
Yeah,
I
remember
that
too
toby,
you
had
your
hand
up
first,
I
think.
G
Okay,
hopefully
I'll
make
you
think
of
it.
I
wanted
to
say
it
sounds
like
there's
a
real
opportunity
to
like
if
we
think
about
the
foundation's
role
here
as
a
central
org.
G
I
wonder
if,
as
we
talk
about
the
individual
coc
groups
of
the
projects,
if
we
could
ask
for
some
either
transparency
or
provide
some
transparency
up
or
down,
because
it
seems
like
the
there's,
a
real
opportunity
to
have
very
different,
like
the
code
of
conduct
can
be
standard,
but
the
decisions
made
by
the
projects
could
be
very
different,
and
maybe
that's
fine
with
us,
like,
maybe
we're
not
here
to
dictate.
You
know
we
should
be
kicked
out.
We
should
the
the
net
foundation
recently
ran
into.
G
I
don't
know
if
anyone
saw
this
an
issue
where
they
have
a
new
central
code
of
conduct
group
and
they
have
made
the
call
that,
if
a
group,
if
someone
is
removed
from
one
project
in
the
foundation,
they're
removed
from
every
project
permanently
in
perpetuity
associated
with
the
foundation
now
those
are,
I
think
that
is
in
I'm
opinionless,
like
I'm,
not
saying
that
this
is
something
that
we
should
do,
however,
and
maybe
we're
trying
to
maybe
I'm
trying
to
solve
future
problems.
G
That
haven't
happened
yet,
but
this
seems
like
as
essential
or
an
opportunity
to
provide
guidance
here,
which
is
what
we're
talking
about,
but
also
maybe
I
don't
know
if
there's
a
world
where
we
provide
some
st
some
transparency
or
ask
for
transparency
codes,
so
we
can
standardize
decision
making
is
really
the
problem
of
trying
to
solve
where
like,
if,
if
we
consider
something
a
coc
violation,
but
the
project
doesn't
what
does
that
look
like.
B
Just
I
want
to
respond
to
sarah
really
quick,
because
because
because
she's
ring
something
up,
which
is
a
great
point,
but
it's
also
in
sort
of
it,
it
relates
to
a
decision
that
this
group
specifically
made,
which
was
not
to
to
standardize
that
process,
because
projects
like
node
would
rather
have
that
agency
and
assurance
that
a
decision
or
an
issue
made
by
another
coc
moderation
group
did
not
affect
their
project,
and
so
there
was
a
desire
for
more
autonomy
over
uniformity
from
the
projects
on
that
particular
thing.
B
A
D
Yeah,
so
that
was
the
third
point
I
was
going
to
bring
up
to
the
thanks,
for
I
remember
vividly
this
conversation
in
montreal
and
some
people
were
very
keen
on
making
sure
that
we
didn't
cross
the
line
here,
and
I
think
this
is
something
we
want
to
be
careful
about
yeah
and
the
last
conversation
we
had,
and
this
is
going
back
to
the
list
you
were
making
joe
clearly
suggested
that
every
project
should
have
an
sort
of
a
dedicated
mailing
list
of
at
which
to
email,
a
code
of
conduct,
violation
rather
than
personal
emails,
and
if
we
go
down
that
route,
I'd
like
to
add
to
that
that
an
sort
of
like
a
following
problem
related
to
that
is,
if
you
don't
know,
who's
the
recipient
of
your
email
and
it's
potentially
the
person
that
you
actually
want
to
file
something
against.
D
That
can
be
problematic
too,
so
maybe
having
some
guidance
around.
That
would
be
useful
too.
And
lastly,
I
wanted
to
point
out
that
I've
actually
taken
two,
I
think
of
the
linux
foundation
courses
to
assess
them
on
diversity
and
inclusion,
and
the
second
one
in
particular.
I
thought
was
quite
good
and,
frankly,
surprisingly,
up
to
date
in
terms
of
the
kinds
of
questions
that
people
that
care
about
these
issues
are
aware
today,
so
I
actually
recommend
the
second
one.
D
I
think
it's
the
diversity
and
inclusion
of
102
and
it's
free
and
if
you
all
want
to
go,
have
a
look
at
it
like
I.
It
was
a
good
course
and
I'm
usually
very
critical
of
stuff
in
general,
so
I
mean
this,
so
it's
like
it
was
good.
The
first
one
wasn't
as
good.
A
Great,
thank
you
emily.
You
had
your
hand
up.
You
took
it
down
you
good
yeah,
I'm
good.
The
point
I
would
have
made
was
covered
by
others.
Okay,
and
I
know,
there's
a
couple
of
comments
in
the
chat.
I
don't
know
if
tierney
or
rich
or
jory
anyone
wants
to
open
it
up
to
the
group
or
anything.
C
A
So
is
this
specifically
around
the
autonomy
versus.
B
Yeah,
so
I
I
think
the
more
useful
kind
of
step
there
might
be
for
for
node
and
electron
in
any
of
the
projects,
amp,
etc,
to
kind
of
have
the
conversation
with
their
groups
about
what
concerns
they
would
have
if
we
did
adopt
a
more
uniform
approach,
and
you
know
because
there's
obviously
differences
of
opinion
even
within
projects.
So
I.
C
I
you
know
this
has
been
the
discussion
for
years,
so
I
might
have
been
representing
comcom
at
some
point,
but
I've
never
been
in
I've
been
in
the
cbc
as
a
regular
member
for
node,
but
not
ever
as
a
voting
member
one
of
the
primary
concerns
that
electron
has-
and
this
was
something
that
we
started
raising
when
we
were
doing
onboarding-
is
a
situation
in
which
you
know
how
things
are
previously
worded.
C
Basically,
people
like
could
escalate
a
coc
decision
to
the
cpc
and
or
whatever
mechanism
the
cpc
creates,
and
that
could
then
like
there's
a
there.
It
was
written
in
a
way
in
which
a
decision
could
be
made
that
overrode
the
project's
decision
to
ban
someone
or
block
someone
which
to
me
is
completely
unacceptable.
That
mechanism
should
never
exist.
C
If
a
project
decides
to
block
someone,
they
should
be
blocked
and
that's
the
end
of
story
so
yeah
that
that
was
largely
where
my
my
concern
was
previously
in
the
inverse
situation,
where,
like
the
foundation,
is
providing
basically
a
block
list
which
I
know
we've
talked
about,
has
repercussions
that
I'm
you
know
I'm
not
addressing
right
now.
I
I
think
that's
fine.
I
think
projects
should
be
able
to
choose
to
opt
into
that,
but
I'm
also
not.
C
I
don't
have
a
hard
decision
about
that
there
there
is,
you
know
the
problem
of
well.
If
someone
who's
a
maintainer
comes
and
is
shitty
in
my
project
and
then
everyone's
enforced
on
the
block
list,
they
get
blocked
from
their
own
project.
What
what's
that
situation,
because,
like
I've,
I've
had
maintainers
who
I've
blocked
personally
and
I
believe,
there's
been
action
taken
against
maintainers
in
the
past
as
well.
So
that's
a
very
hard
situation
that
I,
I
honestly
don't
know.
C
If
we
have
the
time
and
energy
to
solve
so
yeah,
that's
it.
A
All
right
well
all
good
points,
and
I
think
things
to
you
know
further
consider,
but
maybe
we
should
time
box.
This
maybe
put
some
of
these
notes
into
that
issue,
in
particular
some
of
the
ideas
that
we
may
expect
from
from
projects,
and
we
can
discuss
it
further
on
the
issue
or
or
further
in
a
cpc
meeting
or
you
know,
maybe
even
a
working
session.
D
Yeah,
I
just
think
that
there's
like
a
broad
conversation
that
we
can
have,
but
also
there
could
be
some
minimum
requirements
that
we
could
probably
all
agree
to
early
on
and
that
we
probably
should
focus
on
those
first
and
then,
if
we
want
to
have
a
broader
conversation,
have
that
separately
in
like
a
work
shop
session.
D
Whatever
it
is,
I
don't
think
we
need
to
solve
the
mvp
the
minimum
one
today,
but
I
think
that's
what
we
should
focus
on
in
this
issue,
at
least
because
that
was
what
the
requirement
was
and
what
the
issue
was
opened
for.
A
Okay,
I
think
that
makes
sense.
Can
I
ask
you
toby
to
grab
that
little
bit
from
the
notes
and
maybe
just
drop
kind
of
what
you
said
into
the
issue
I'll?
Do
that
right
now?
Okay,
thank
you
all
right,
great
moving
on.
A
Let
me
see
get
back
to
where
I
am
here
kickoff
election
process
for
secondary
cpc
director
this
I
was
looking
at
earlier,
so
yeah.
This
is
the
second
meeting.
So
thinking
about
the
timeline,
we
opened
it
up
a
meeting
ago.
A
This
meeting,
I
think
we
would
say
at
the
end
of
today
we
would
close
nominations
and
then
open
up
the
election
process,
and
I
can
say
that
I
have
more
than
one
person
who
has
reached
out
to
me.
A
So
you
know
an
election
is
forthcoming,
so
I
guess
this
is
maybe
an
opportunity
to
remind
folks
if
they
are
interested
in
this
secondary
cpc
director
role
to
reach
out
to
me-
and
let
me
know-
and
at
the
end
of
the
day
today
or
first
thing
tomorrow
morning
I
can
announce
the
nominees
and
we
can
move
forward.
A
Then
the
election
will
be
open
for
two
weeks.
Closing
you
know
at
the
next
the
end
of
the
next
cpc
meeting
day,
I
think,
is
august
31st.
According
to
the
issue
checking
my
notes,
yep,
which
I
think
is
actually
perfect
in
terms
of
timing.
I
think
michael
opened
this
up
right
on
time.
A
So
great
anything
else
on
this
one
from
folks.
A
If
not,
I
will
move
it
along.
I
guess
I
will
ask,
should
we
do
any
sort
of
you
know
last
pings
anywhere
and
slack
and
an
email
anything
I
mean
we're
talking
about.
You
know
before
tomorrow
morning,
so
not
a
lot
of
time,
but
does
anybody
have
any
thoughts
around
that
we're
live
on
youtube?
I
know
everybody
watches
that.
A
Okay,
would
anyone
like
to
just
drop
that
in
there
real
quickly.
A
Great.
Thank
you.
Next
item
is
a
pull
request.
782.
This
is
maybe
the
one
we
were
kind
of
referencing
before
toby
opened.
This.
Thank
you
again
closes
a
couple.
Issues
and
and
kind
of
adds
clarifies
some
of
the
reporting
destinations.
I
don't
know
what
the
word
is.
I'm
looking
for
toby.
Do
you
want
to
comment,
or
anybody
have
any
comments
on
this
pull
request.
D
So
I
just
want
to
share
that.
I
mean
mention
that
this
needs
board
approval,
because
it
changes
the
charter
to
clarify
the
role
of
the
cpc.
A
Okay,
let's
add
that
label
your
I've
added
it
great.
Thank
you
excellent.
So
that's
I
don't
know.
Let
me
look
at
zoom
here,
sarah's
already
gone
yeah
all
right!
Well
I
mean
maybe
robin
you
can
take
it
to
the
board
or
we
can
mention
it.
A
Excellent,
thank
you
wow.
How
did
emily
get
sideways?
Oh
there?
He
goes
that
was
weird
cool,
so
yeah
I
mean
I
encourage
folks
to
take
a
look
at
this.
I
think
it
makes
sense
it
sort
of
goes
a
little
bit
long
with
the
previous
conversation.
We
had,
but
definitely
take
a
look
and
see
if
you
have
any
thoughts
cool
moving
on
this
is
issue
772.
A
This
is
the
cpc
chairperson
election.
It
looks
like
this
is
closable
and
I
will
continue
doing
this
thing
that
I'm
doing
any
objections.
I
don't
know
if
that
I
don't
know
if
you
can
object
now,
but
it
doesn't.
A
Cool
happy
to
happy
to
do
it
and
I'm
hoping
that
I
have
even
more
time
to
do
it
been
busy
lately,
but
anyway
great.
Thank
you.
Where
did
it
go?
Actually,
let
me
just
close
it.
I'm
gonna
just
say
thanks,
y'all
cool
moving
on
this
is
issue
761.
A
toby.
This
is
build
stronger
ties
between
at
large
maintainers
and
their
cpc
reps
looks
like
maybe
I
think
your
last
comment.
Toby
has
some
good
ideas
there
and
we
just
need
to
kind
of
act
on
them,
at
least
as
an
initial
first
step.
D
I
did
this
to
myself.
I
guess
yeah,
I
think
the
I
we
wanted
to
do
like
again,
like
a
really
small
first
step
to
actually
get
something
done
because
we're
like
already
you
know
halfway
through
the
year
or
more,
and
the
idea
was
just
to
create
a
slack
channel
to
have
at
large
maintainers
and
the
the
representatives
have
a
communication
channel.
This
was
sort
of
like
the
direction
in
which
I
was
suggesting.
D
We
we
could
start
just
want
to
make
sure
that
people
were
okay
with
this
and
have
the
folks
representing
at
large
maintainers
joined
us,
and
if
we
could
actually
invite
those
people
on
the
maintainers
into
that
channel,
I
don't.
I
don't
know
if
we
actually
have
enough
information
to
do
that,
and
that
was
it
really.
A
Cool
just
invited
you
toby
and
we
can
go
from
there.
That's
wonderful,
please
invite
me
as
well
roger
that.
D
And
I
guess,
michael
too.
A
Yeah,
okay,
I
think
I
think
we
did
that
correctly
great
I'll,
invite
them
as
well
great
all
right
cool.
So
that's
a
start.
Those
folks
are
invited
and
then
yeah
george,
if
you
can
maybe
ping
project
maintainers
and
let
them
know
about
it
and
we
can
start
kind
of
having
some
stuff
happen
there
and
you
know,
grow
this
effort
from
there.
A
I
will
ask:
do
we
keep
this
issue
open?
Do
we
close
it
until
we
I
mean
maybe
once
jory
invites
folks
we
can
close
it
and
and
then
open
subsequent
issues
from
there.
Does
that
make
sense?
A
Okay,
great
all,
right,
excellent!
Moving
on
the
next
one
is
issue
758,
there's!
No,
as
far
as
I
know,
there's
no
progress
on
this,
and
I
say
that
because
it's
something
that
I
wanted
to
work
on,
but
have
not
been
able
to
yet
this
is
reminder
for
reminders
for
long-term
events.
In
essence,
some
like
github
actions
that
would
create
issues
for
things
like
elections
and
whatnot.
So
I
think
we're
using
this
this
issue
to
drop
in
things.
That
would
be
good
for
this
sort
of
you
know
tooling.
A
So
definitely,
if
you
think
of
anything,
that's
not
here
drop
it
in,
and
if
anybody
wants
to
work
on
this,
that
would
be
great.
But
beyond
that
I
will
I'll
try
to
get
to
it
as
soon
as
I
can
cool
anything
else.
On
this
I
know
tierney,
you
had
mentioned
something
in
some.
I
think
slack
messages
that
were
was
perhaps
related,
but
I
don't
know
if
it
said.
C
A
Recall
left
hand,
it
was
code,
spaces
and
and
gists.
Oh
yeah,.
C
A
Cool
well,
I
will
still
look
at
this
stuff
as
soon
as
I
can
moving
on
the
create
proposal
for
our
proposals
for
the
community
fund.
This
is
issue
756.
robin
dropped.
The
comments
in
less
than
a
day
ago,
with
a
doc
around
the
lyft
scholarships
for
node.js
training
and
certification.
A
F
Yep
no
problem,
it
really
sort
of
details.
What
we've
been
talking
about
frames,
how
we
would
describe
the
lift
scholarship-
and
there
is
rachel-
has
a
much
more
detailed
document,
for
example,
on
how
this
will
be
rolled
out
we'd
like
to
launch
it
september,
6th,
leave
it
open
for
30
days
and
then,
depending
on
the
number
we
get
in
it
could
be
like
two
to
four
weeks
to
review
all
of
those
and
make
an
award.
F
A
Great
thank
you
to
all
of
you
for
putting
that
together.
It's
a
short
read.
If
anybody
you
know
it's
like
less
than
a
page,
so
I
encourage
folks
to
take
a
peek
at
it
and
comment
if
you
have
any
questions
or
thoughts
or
whatnot.
A
Cool
and
then
finally,
on
the
list
is
the
dco
thing
that
we
mentioned
earlier.
Jory.
Do
you
wanna
chime
in
on
this?
This
is
issue.
632
provide
implementation,
guidance
for
dco
cla.
B
Yeah,
so
I'm
just
chiming
in
on
behalf
of
brian
and
to
to
update
everybody
so
probot
dco
is
the
bot
that
we
have
been
working
on
with
the
probot
team
for
quite
some
time
to
make
the
changes
necessary
to
make
it
easier
for
people
of
all
skill
levels
to
easily
sign
or
agree
to
the
dco,
and
we
have
submitted
those
changes.
We're
waiting
for
someone
from
the
probot
dco
team
to
agree
to
merge
it
in,
unfortunately,
they're.
B
Also
looking
at
they're
looking
for
someone
to
take
on
ownership
of
that
bot,
so
they're
they're,
reticent
to
accept
our
code
because
they're
not
going
to
they're,
not
planning
to
maintain
it,
and
so
the
question
to
us
has
been.
Would
we
the
foundation
like
to
take
on
that
responsibility?
B
And
if
so,
are
there
perhaps
people
in
our
work
that
would
be
willing
to
help
co-maintain
it,
because
that's
not
something
that
say
brian,
for
example,
could
do
alone.
So
that's
kind
of
where
we're
we're
at
in
this
sort
of
like
dance,
I
suppose
we're
a
little
stuck,
but
that's
the
situation
on
the
on
the
dco
bot.
B
As
far
as
the
cla
goes.
We
do
encourage
projects
that
are
currently
using
the
js
foundation,
cla
assistant
bot,
to
migrate
to
ezcla
and
we're
working
on
documentation
and
easy
process
for
migration
for
projects
like
webpack
at
the
moment-
and
I
know
some
others
have
raised
their
hand
to
say
we
want
to
move
too,
and
hopefully
that
can
happen
fairly
quickly.
B
Once
once
we
have
everybody
kind
of
aware
of
what
that
process
will
look
like,
so
that
there's
no
surprises,
but
in
any
case,
if
you're
interested
and
ready
to
move
to
the
open,
js
foundation,
cla,
let
us
know
and
we'll
work
with
you
to
get
eccla
turned
on.
D
Do
we
have
a
good
sense
of
like
how
much
the
project
is
used
elsewhere
and
what
what
does
the
maintaining
requirement
is?
Oh,
okay!
Well,
okay!
Well
that
answers
my
question
like
if
this
isn't?
No,
if
this
isn't
like
a
large
project
that
is
very
much
used
like
in
lots
of
different
areas,
then
we
probably
it's
a
different
conversation
than
if,
like
we're,
you
know,
would
be
like
the
only
one
still
using
that
thing.
A
Yeah,
if
it's
used
a
lot,
and
particularly
outside
of
our
sort
of
ecosystem
community,
you
know,
however,
we
define
that
specifically,
but
you
know,
is
it
something
the
linux
foundation
should
consider
you
know
or.
I
F
D
C
Yeah,
so
I
wouldn't
call
it
a
large
project,
but
it's
a
non-trivial
project
like
it's,
not
it's
not
at
the
scale
of
something
like
you
know,
electron
or
node
or
amp,
or
something
like
that.
But
it's
a
project
that
has
users
and
has
like
is
a
responsibility,
and
I
I
agree
with
toby
that
I
don't
think
we're
in
a
spot
where
we
can
say
we're
gonna
take
that
on
now,
if
people
step
up
and
to
maintain
it
and
want
to
bring
it
into
the
foundation,
I'm
fine
with
that.
D
However,
we
should
try
to
figure
out
how
to
solve
our
problem
of
getting
the
thing
that
we
care
about
merged
in,
and
we
could
focus
on
figuring
out
how
to
help
doing
just
that.
C
B
This
this
is
just
the
dco,
and
here
is
just
is
it
for
those
who
want
to
follow
along
with
the
old
the
long
conversation?
That's
that's
brian's
original
pr
from
quite
some
time
ago,
which
includes
you
know.
Basically,
the
name
dc
is
a
great
bot
and
the
change.
The
change
we
want
to
see
is
one
which
would
make
it
easier
for
us
to
do
remediation,
commits
and
and
make
that
again
something
that's
more
accessible
to
folks
who
aren't
as
experienced
with
get
and
may
run
into.
C
C
C
Yeah
I
I
agree,
and
I
also
think
that
this
is
a
reasonable
ask
for
the
linux
foundation
to
take
on,
if
that's
something
that
you'd
be
willing
to
do
that,
you
could
talk
to
because,
like
yeah,
the
dc,
isn't
the
dco
like
maintained
by
the
linux
foundation
or
something
or
it
comes
from
linux.
Right.
B
C
D
A
And
I
see
gregor's
comment
is
pretty
early
on
in
the
process.
Here,
changes
look
good
to
me
overall,
I'm
just
concerned
that
it
adds
quite
some
complexity.
I'm
worried
that
about
the
maintenance
of
the
app
as
you
use
the
app
at
the
linux
foundation,
I
wonder
if
you
or
someone
else
from
your
teams
could
help
out
maintaining
dco
and
especially
the
advanced
features
added
by
this.
B
Pr
so
I
mean
this
is
something
we
can
follow
up
with.
You
know
internally
and
see
if
there
is
capacity
at
the
lf
writ
large
to
support,
maybe
by
you
know,
but
that's
that's
a
that's
a
different
question
than
is
this
community
interested
in
in
maintaining
the
project
and
so
either
way,
though,
like
those
are.
C
C
A
A
Let
me
double
check
the
agenda
yeah
last
issue,
although
next
week
we're
supporting
the
nebraska
projects
in
the
working
session,
let
me
just
touch
on
that
real
quickly.
B
You
know:
small
projects
with
big
impact
on
the
ecosystem.
F
B
That's
that
comes
specifically
out
of
an
extension
of
our
conversation
around
like
technical
strategy
and
supporting
projects
of
varying
shapes
and
sizes
at
the
foundation,
so
that
for
the
next
call
we're
going
to
talk
about
like
the
smaller
projects.
Specifically,
I
will
create
an
agenda
and
post
an
issue
for
this
meeting.
B
B
It
sounds
like
we
could
obviously
do
another
session
on
working
session
on
the
code
of
conduct
or
do
a
working
session
on
the
the
the
community
fund
seemed
like
great
topics,
but
that's.
A
B
Okay,
so
text
strategy,
anything
else.
B
We
could
do
one
specifically
for
parties
interested
in
in
the
easy
cla
just
as
an
informative,
like
kind
of.
A
A
We
have
seven
minutes
left.
Did
we
want
to
double
back
on
any
of
those
things
or
the
dco
further?
I
I
see
your
comment
there
tierney
asking
gregor,
if
you
know
co-owners
code
owners
for
those
specific
features,
you
can
see
what
he
says.
C
Yeah
I
mean
if
it's,
if
it's
like
you
know
this
100
lines
of
code
or
whatever
that
he's
asking
for
support
on.
I
think
that's
a
reasonable
request,
like
I,
I
think
most
of
the
projects
here
would
also
request
that
if
it's
like
a
feature,
that's
kind
of
outside
of
the
scope
but
still
is
accepted,
I
think
that
that's
a
reasonable
request
and
I
think
that
if
we
want
this
merged,
we
should
be
willing
to
do
that.
So
I
like
yeah.
C
C
I
think
if
we
are
making
this
request,
we
should
be
willing
to
put
someone
forward
to
do
it,
so,
whether
that's
finding
someone
in
the
cpc
or
a
member
project
or
whatever,
but
finding
someone
to
that's
willing
to
maintain
this
is
probably
something
we
should
do.
If
we,
if
we're
asking
for
it,
yeah.
A
I
agree
tierney,
would
you
mind
kind
of
just
summarizing
that
very
briefly
in
in
our
issue
and
and
and
just
when
we
come
back
to
what
we
know
yeah
and
we
can
see
what
gregor
says
in
the
meantime.
A
All
right
yeah,
I
guess
we'll
we'll
just
call
it
then
I
appreciate
everybody
showing
up
and
doing
the
work
here
and
and
in
between
meetings.
So
thank
you.
Everybody
appreciate
it.
A
B
Adios
you
wanna,
cancel
us
on
youtube.