►
From YouTube: 2021-11-9-CPC Meeting
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
B
Super
quick
there's
an
openjs
world
programming
committee
meeting
this
thursday
sign
the
public
calendar
we'd
love
to
have
you
feel
free
to
pop
in.
If
you
want
to
get
involved
in
planning
the
event.
B
A
D
Just
one
quick
update,
we're
updating
the
node.js
certification
to
v16
long
term
support
going
from
14
to
16.,
and
we
have
a
blog
that'll
go
out
today.
We're
just
doing
some
final
testing.
A
A
If
not,
then
we
can
move
on
to
the
next
topic,
which
is
any
updates
from
the
board
meeting.
I'm
just
trying
to
think.
If
anything
comes
comes
up.
I
think
the
the
main
thing
that
comes
to
mind
with
me
is:
we
had
a
good
discussion
about
some
of
the
technical
strategy
work
that
we've
been
working
on
jory
put
together
a
nice
summary
of
that
and
the
board
seemed
quite
supportive
of
helping
them.
A
D
Just
that
we
spent
some
time
looking
at
budget
for
next
year,
we're
doing
well,
many
foundations
are,
you
know,
have
struggled
just
a
tiny
bit
during
the
pandemic,
but
we've
held
pretty
strong
and
just
a
little
bit
over
flat.
So
that's
was
really,
I
think,
good
news
for
us,
given
all
the
challenges
of
the
pandemic,
so
we're
in
a
good
spot.
B
A
C
Trying
to
take
a
look,
I
was
supposed
to
do
work
and
let's
say
that
the
last
two
weeks
have
been
a
bit
complicated,
and
so
I
haven't.
A
Okay,
so
no
update
on
that
one.
The
next
one
is
clarify
requirements
around
coc
violation.
D
I
have
I
have
an
update,
just
sort
of
more
broadly
about
code
of
conduct
and
and
then
where
we
are
with
sort
of
our
inventory.
So
I'll
talk
about
the
inventory
later,
I
did
go
through
all
of
our
projects
to
take
a
look
at
that
and
pretty
good
spot
there.
We
can
talk
about
it,
but
last
week
was
the
linux
foundation
open
source
member
summit
for
lf
members,
and
I
attended.
D
There
were
two
breakout
sessions
on
code
of
conduct
that
were
a
packed
house,
which
was
pretty
amazing,
and
there
was
sort
of
a
separate
kind
of
ad
hoc
working
group
that
got
together
to
talk
to
sort
of
follow
up
on
that.
D
So
I
believe
those
sessions
are
public
ones
by
joanna
lee
who's,
an
attorney
who's
who's,
one
of
our
attorneys
as
well
she's,
fantastic,
it's
an
area
specialty
and
the
other
was
ava
black
who's
on
the
kubernetes
code
of
conduct
committee
and
at
microsoft.
So
I'll
find
those
links
and
we
can
put
them
in
the
notes.
But
I
learned
a
lot
and
if
I
was
sort
of
looking
at
what
we're
looking
at
as
having
some
of
those
core
requirements,
toby
has
a
checklist
in
the
issue.
D
I
think
those
are
really
good
and
I
I
think,
and
I'm
not
quite
sure,
that
we
have
sort
of
codified
those.
It's
not
entirely,
I'm
not
entirely
sure
and
I
think
the
the
biggest
one
that
is
in
toby's
list.
That's,
maybe
not
in
our
policy,
is
to
to
err
on
the
side
of
transparency
and
to
always
list
who
is
on
that
code
of
conduct
committee.
D
D
D
So
this
group
is
looking
at
creating
sort
of
more
kind
of
what's
the
line
when
you
escalate
to
an
attorney
into
an
area
where
you
are
better
counseled
and
protected
in
that
escalation
process.
D
D
So
how
do
we
get
that
training
in
place?
How
can
the
linux
foundation
support
that
fund
that
as
well
and
again,
if
there
is
new
work
around
a
new
code
of
conduct?
Where
should
that
be
hosted,
probably
not
at
the
linux
foundation,
because
it
impacts
people
who
work
across
foundations
from
apache
eclipse
and
everywhere
else?
So
this
group
wants
it
to
be
broad
and
then
just
making
sure
that
there
are
diverse
voices
on
on
these
on
these
projects.
D
So
if
that's
something
you're
interested
in
participating
in,
I
can
plug
it
into
that
that
group.
So
that
is
just
work,
that's
sort
of
spinning
up,
okay
quickly.
I
did
an
inventory
and
if
I
sort
of
take
a
look,
we
have
38
projects
really
only
five
do
not
have
their
code
of
conduct
listed
on
their
website
or
their
or
their
github
repo
that
I
found.
So
I
don't
want
to
call
anybody
out
because
it
could
be
buried
and
I
didn't
find
it,
but
we'll
work
with
those
folks.
D
D
If
you
don't
have
a
process,
then
do
you
really
have
a
code
of
conduct
and
things
like
that,
so
one
of
the
things
I
think
we
need
to
do
is
just
make
sure
that
we're
really
solid
on
what
our
process,
what
the
process
is
who's
who's
on
these
committees
and
what
guidance
can
we
give
and
what
templates
can
we
give
to
these
projects?
I
think
some
of
some
of
the
projects
who
have
more
work
to
do
we're,
probably
still
in
that
onboarding
process
from
the
js
foundation
to
openjs
foundation.
D
A
My
quick
question
would
be:
is
there
any
way
that
that,
like
the
you
know,
having
gone
through
the
process
of
sort
of
looking
at
them,
where
we
could
automate
any
of
that,
so
that
you
know
it's
a
regular
scan
that
says
yeah?
Okay,
we've
got
things
in
place
that
it
I
mean
that
may
be
hard,
but
I
thought
I'd
ask
they're.
D
Often
buried
you
know
those
code
of
conducts.
I
love
it
when
it's
right
in
the
you
know
the
top
right
hand
of
the
github
reaper,
where
you
usually
have
your
license,
love
it
when
it's
there
super
easy
to
find.
Sometimes
it's
buried
in
the
contributing
section.
C
Yeah
no
comment
you
know
just
like
we
said,
like
no
process
do.
We
have
really
have
a
code
of
conduct
like
if,
if
the
link
is
buried
somewhere,
I'm
like
do,
we
really
have
a
god
of
conduct.
I
think
those
are
important.
It's
not
just
like
cosmetic
right
when
you
actually
like,
when
there's
a
crisis
being
able
to
find
this
easily
as
like.
C
It
should
be
like
so
I
think
at
some
point,
so
maybe
having
some
recommendations
around
this
would
be
useful,
but
yeah
thanks
for
sharing
this
and
thanks
for
reporting
from
the
the
the
the
linux
foundation
summit.
I
think
this
was
really
useful
information
to
happen.
It's
great
to
know
that
there's
like
ongoing
work
in
this
space.
D
Yeah
automating,
I
think,
putting
together
some
best
practices
for
them
to
adopt.
You
know
I
love
it
when
they
have
it
on
their
website,
as
well
as
their
github
repo
again,
so
I
I
have
several
notes
for
each
I.
I
don't
think
it
can
be
something.
A
Because
I
do
wonder
like
how
big
an
ask
is
it
to
say
we
want?
You
know
you
we
could
say
like
you
need
to
have
a
file
name
this
in
your
repo
right.
Like
I
don't
know,
I
guess
that's
for
the
discussion
of
the
expect.
Like
the
in
that
issue
there
we
can
flesh
out
what
the
ask
the
the
ask
beyond
what
we've
already
asked
would
be.
D
If
somebody's
stressed
and
wanting
to
file
a
report
so
and
then
again,
I
think
you
know
if,
if
we
all
agree
that
this
should
be
again
having
names,
I
think
it's
really
great,
because
if
you're
reporting
and
you're
reporting,
you
don't
know
who
this
list
is
going
to
the
person
who
you're
you're
reporting
a
complaint
against
may
be
in
that
group,
and
you
don't
know
it.
So,
how
is
that
handled?
C
Toby
yeah,
and
just
to
to
your
point,
michael,
I
think
more
than
actually
trying
to
automate
the
thing
making
sure
that
it's
part
of
the
onboarding
process
that,
like
whatever
process
we
want
for
this,
is
actually
implemented.
There
would
be
already
like
a
really
huge
first
step
that
well
I
don't
I
mean
we
have
just
a
requirement
for
having
one,
but
I
think
like
having
a
requirement
for
the
process
like
a
larger
package.
C
D
Yeah
documentation
was,
is,
I
think,
lacking
not
just
for
us.
I
think,
but
I
heard
that
across
at
the
linux
foundation
meeting
that
we
had
folks
that
were
all
just
really
missing
documentation
and
hopefully
that
would
become
sort
of
a
best
practices
that
we
could
adopt,
we're
just
not
there
yet.
So
I'm
happy
to
draft
something
up
with
your
all's
help.
D
A
D
I
did
I
came
up
with
some
options.
We
use
pinnacle
branding
for
our
swag.
Essentially,
they
have
great
negotiated
rates
for
content
and,
most
importantly,
shipping,
which
is
huge
right
as
well
for
especially
what
we're
looking
at
I
you
know
we
worked
just
as
a
team
and
we
had
sort
of
our
three
favorites
and
and
then
pinnacles
looking
for
some
other
suggestions,
but
you
know
backing
up.
I
think
we
we
need
to
think
about
budget.
D
We
love
the
power
bricks,
those
are
always
popular
water
bottles
and
fleece,
blankets.
Those
seem
to
be
sort
of
the
more
popular
ones.
Those
range
in
the
10
to
20
dollar
range
and
pinnacles,
going
back
to
find
us
a
really
good
quality.
I
didn't
want
this
to
be
like
crap
that
you,
you
know,
that's
like
broadly
handed
it
out.
That's
you
know.
D
I
want
it
to
be
a
high
quality
for
thank
you
gift,
so
they're,
coming
back
with
some
recommendations
for
that,
if
you
ever
have
any
other
favorite
swag,
let
us
know
and
there's
you
know,
there's
sort
of
two
ways
you
can
do
it.
You
could
give
somebody
a
thank
you,
one.
Okay,
we
could.
We
could
set
up
a
store,
an
openjs
foundation
store
with
their
product.
You
could
get
give
them
a
free
gift
certificate
for
that
particular
item.
D
They
could
click
it,
it
would
get
drop
shipped
to
them
or
we
can
just
notify
pinnacle
hey.
We
want
to
recognize
these
five
people
this
month
or
this
quarter.
We
could
send
those
names
to
pinnacle
and
they
would
drop
ship
it.
So
it
could
be
something
that
we
can
control.
It
could
be
something
that
the
recipient
controls.
D
D
So
I
had
in
my
mind
if
we
were
going
to
buy
in
bulk
to
buy
like
500
of
something
and
say
you
bought
500
of
something
and
it's
you
know
10
to
15
a
piece
you
need
to
add
10
to
that
at
least
or
12
to
20
for
that
for
international
shipping.
So
I
would
think
we
would
need
about
10
000
to
kick
off
the
thank
you
program,
but
I
think
the
nice
thing
is
once
we
set
up
the
store
as
well.
D
D
D
D
Yep
so
yeah
pinnacle
shared
with
me
that
that
old
store
link
and
so
she's
doing
an
inventory
of
all
the
node
product.
There's
a
few
random
javascript
products
as
well.
A
D
D
D
I
think
what
we
would
want
to
do
is
maybe
establish
a
partnership
with
the
one
or
two
entities
to
make
it
meaningful.
Probably.
E
Something
to
consider
as
well
that
may
be
much
more
difficult
is
the
best
github
swag
I've
ever
seen
is
skyline.github.com
where
it
takes
your
contribution.
D
E
And
lets
you
3d
print
an
example
of
it
seen
here,
and
so
that's
unique
to
me
and
I
like
I
can
do
one
for
each
year
and
so
on.
So
I
wonder
if
there's
something
around
like
to
be
explored
around
like
customized
swag,
that
highlights
an
individual's
contributions
to
foundation
projects.
D
Yeah
and
that's
code
specific,
which
is
one
unique
issue,
I
think
for
us
yeah.
I
think
for
us.
E
D
So
we
could,
if
you
have
like,
we
could
change
it
up
and
make
it
like
this,
the
superstar
mvps
and
make
it
more
special
yeah
I
mean
joey
and
I
were
looking
at
and
I
had
suggested,
maybe
some
like
glass
bricks.
You
know
or
something
like
that
to
really
recognize
those
special
people.
We
could
definitely
do
something
like
that
or
more
custom.
D
So
I
guess
it's
it's
it's
kind
of
it's
recognition,
but
I
think
if
it's
also
to
encourage
them
to
do
more
right
so.
A
D
C
A
Because,
okay,
thanks
for
that
update,
so
then
the
last
one
on
the
agenda,
which
is
provide
implementation
guidance
for
the
dcocla.
A
B
So
what
we,
what
we
can
update
is
that
on
the
dco
probot
app,
there
have
been
a
lot
of
conversations
across
multiple
projects
within
the
lf,
and
there
is
increasing
appetite
now
to
potentially
have
lfit.
Take
take
that
project
on
so
for
a
minute.
I
thought
it
was
dead
in
the
water,
but
I
will
say
that
I
think
that
after
particularly
some
folks
in
hyperledger
and
some
other
bigger
projects
were
like
no,
this
is
really
important
to
us.
B
A
Okay,
well,
that's
a
good
update
to
hear
that
that's
looking
up,
so
that
would
be
definitely
good,
so
that
takes
us
to
the
end
of
the
agenda
and
we
have
three
minutes
left.
Is
there
anything
else
that
we
should
talk
about
before
we
close
out
for
today.
B
If,
with
our
final
three
minutes,
let
me
just
say
one
of
the
things
in
the
open
js
world
like
programming
group
right
now
that
we're
talking
a
lot
about
is
you
know
who,
should
we
potentially
be
telling
in
advance?
Hey
there's,
you
know
our
event
is
june
the
week
of
june
6.
we'd
love
for
you
to
either
a
consider.
You
know
submitting
a
cfp.
Obviously,
the
cfp
will
be
open
in
the
new
year
or
b.
B
You
know
these
are
folks
that
we'd
love
to
potentially
think
about
for
keynotes,
so
and
at
this
point
in
time,
if
you've
seen
and
presentations
from
folks,
particularly
those
that
we
don't
see
all
the
time,
I
would
love
to
get
your
your
feedback
on
who,
you
think
would
be
great
for
our
either
our
js
keynote
day
or
the
shared
keynote
day.
We'd
love
to
love
to
know
what
you
think.