►
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
All
right,
so
it
looks
like
it's
starting.
I
will
capture
this
link
and
we
will
get
rolling,
actually
I'll,
throw
a
comment
in
here.
My
friends
feel
free
to
ask
any
questions
great,
so
welcome
everyone
to
another
episode
of
the
cross
project
council
meeting
as
part
of
the
open
js
foundation
today
is
the
15th
of
february
in
the
year.
2022.
A
C
B
Yay
we
had
an
election
and
also
alex
liu
was
re-elected
as
our
end-user
and
dan
cousino
was
re-elected
as
our
goal
director
and
so
we'll
be
putting
out
a
blog
today,
kind
of
just
reintroducing
you
to
our
board
of
directors
and
introducing
folks
to
jordan,
who
are
not
on
calls
with
us
every
other
day,
like
jordan
often
is
so.
B
Yep,
what
else
newswise
we
have
extended
rcfps
for
openjs
world
to
next
friday
february
25th,
but
if
you're
watching
this
we'll
let
you
know
that
we
give
folks
a
little
bit
of
a
grace
period
on
that
weekend,
just
because
time
zones
are
so
wacky
around
the
world.
So
we're
saying
the
25th,
but
it
kind
of
if
it
rolls
in
on
the
weekend
we're
good
with
that
because
monday
morning,
we'll
be
having
our
program
committee.
Take
a
look
at
those
great
yeah,
great
and
then
also
in
case
you
missed
it.
B
We
had
a
nice
bit
of
news
from
our
member
joint
who
also
shawn
johnson's
on
our
board
of
directors
and
joint
joint
has
contributed
the
node.js
trademarks
to
the
openjs
foundation,
and
I
know
this
is
something
that
the
community
has
been
working
on
for
many
years.
So
we're
super
grateful
for
all
of
that.
A
I
don't,
but
I
will
ask
anything.
I
know
you
know
obviously
there's
board
news
there,
but
anything
else
with
upcoming
meetings
or
any
anything
that
we
should
be
aware
of.
B
A
Great
openjsf.org
collaborate,
great
cool,
all
right.
Well
with
that,
we
will
move
things
along
and
I'm
looking
for
my
page
with
the
agenda
for
folks
who
joined
the
call
after
I
shared
this
here
is
the
meeting
notes.
Please
add
yourself
and
note:
takers
are
greatly
appreciated.
A
So
if
we
get
into
the
agenda,
the
first
item
on
the
list
here
is
the
issue.
Excuse
me:
826
focus
on
javascript
security
at
openjs
we
had
a
good
meeting
a
working
session.
What
was
it
last
week?
I
can't
remember
time
really
flies
and
you
want
to
get
anyone
want
to
give
the
update.
I
see
robin
you
added
some
action
items
from
that.
That's
fresh
in
your
mind.
You
want
to
share
with
folks.
B
B
I
think
we
all
do
open
source
well
and
we
need
to
encourage
more
folks
from
the
security
community.
I
think
that's
fair,
to
say
to
build
kind
of
a
a
culture
of
security
around
open
source
and
share
best
practices
we
talked
about.
Are
there
some
requirements
that
we
need
to
set?
There's
talks
at
the
linux
foundation,
perhaps
through
the
leadership
at
openssf.
B
Are
there
some
minimum
requirements
that
projects
should
consider?
We
did
talk
about
the
work
the
open
ssf
is
doing
and
just
wanted
to.
Let
you
all
know
that
we
are
having
conversations
with
those
and
we'll
look
be
looking
to
get
some
more
support
from
those
organizations
who
support
that,
but
I
think
the
conversation
was
just
so
rich.
I
know
I
learned
a
lot
and
we
had
some
takeaways
that
one
one
was
easy.
We
were
going
to
set
up
a
slack
channel
on
security.
A
B
Maybe
that's
just
like
for
us
to
start
sharing
information
and
news,
and
things
like
that.
That's
important,
I
know,
there's
a
lot
happening
in
the
world
and
then
there
was
again
such
a
good
conversation.
It
felt
a
little
that
an
hour.
It
wasn't
enough,
so
we
needed
a
follow-up
conversation
with
that.
Our
cpc
working
sessions
are
kind
of
booked
out
topic-wise.
We
thought
we
needed
maybe
kind
of
an
off-calendar
working
session,
an
idea.
A
Yeah
I
was
looking
at
the
calendar
and
it's
not
actually
that
far
booked
out.
In
fact,
I
think
next
week
is
the
only
week.
That's
has
something
and
it's
listed
as
repo
cleanup.
A
So
I
wonder
if
we
should,
you
know,
push
off
the
repo
cleanup
work
and
instead
get
back
to
security
for
for
next
week,
start
to
think
through.
You
know
what
are
what
are
some
things
we
could
start
doing
what.
A
Be
the
same
as
this
week,
so
it'll
be
noon
next
week.
A
Yeah
npm
folks
would
be
great
too
so
yeah
and
I've
talked
to
lauren
a
little
bit
in
gms,
and
you
know
they're
interested
in
doing
more,
so
I
can
reach
out
to
them
again
and
see
if
they
can
join,
but
I
guess
the
question
remains:
should
we
should
we
do
that
for
next
week?
What
will
the
folks
think.
A
I'm
into
it,
I
think
you
know
we
can
maybe
make
an
issue
for
repo
cleanup
and
yeah
trailer
bits.
Folks
as
well
rich
would
be
good,
although
they'll
charge
us
for
attending.
Maybe
we
can
make
it.
A
I
don't
know
if
there's
an
issue
for
the
repo
cleanup,
but
maybe
we
can
make
an
issue
for
that,
and
people
could
put
in
there
what
they
think
needs
to
happen,
and
maybe
that
could
happen
async
even
until
we,
you
know,
I'm
sure
we'll
always
have
stuff
to
do
in
the
working
sessions,
but
I
could
try
to
get
some
repo
cleanup
happening.
If
there
are
specific
things
we
want
to
be
doing.
B
Come
on
and
then
I
think
we
talked
about
a
collab
space.
I
think
we
know
that
if
you're
going
to
have
a
successful
collab
space,
you
need
a
couple
of
champions
who
drive
it.
So
that
may
you
know,
be
you
know
a
result
of
some
of
these
meetings,
but
just
through
that
out
there.
A
Yeah,
I
agree.
I
think
it
would
be
a
good
thing
to
do,
but
maybe
we'll
just
let
that
come
naturally,
as
we
kind
of
keep
working
on
it
champions
and
what
the
scope
of
that
collab
space
would
look.
A
Out
all
right
cool,
so
I
will
update
the
meeting
issue
to
push
off
the
repo
cleanup
for
a
week
I'll
see
if
there's
an
issue
for
repo
cleanup
and
create
one
if
there
isn't
and
we'll
put
security
on
the
list
for
next
week,
cool.
A
That's
that
getting
back
to
it.
The
next
item
on
the
agenda
is
issue
821,
google,
summer
of
code.
Brian,
do
you
want
to
comment
on
this?
I
know.
There's
there's
great.
Your
description
here
is
is
good,
so
people
can
read
that
and
it
looks
like
maybe
rich
shared
it
with
the
tsc
a
little
while
ago.
I
don't
know
if
there's
any
comments
there,
but
let's,
let's
talk
about
this.
E
Sure
so
just
I
had
opened
that
open
edition
of
the
repo.
In
case
we
wanted
to
file
an
application
on
behalf
of
open.js
foundation.
I
haven't
seen
any
activity
on
that.
We
should
go
check
it
because
I've
looked
at
it
in
last
week
or
so,
but
the
deadline
for
that
is
coming
up.
E
I
believe
it's
early
next
week.
So
if
we
do,
if
there
are
any
projects
that
would
like
to
make
use
of
this,
then
we
should
probably
get
on
this
fairly
quickly.
A
Any
feedback
or
anything,
rich
or
michael,
has
gone
invisible.
I
can't
see
him
in
his
chair
anymore.
F
Yeah,
I
think
google
summer
of
code
has
not
always
been
a
great
fit
for
node
for
various
reasons,
and
I
honestly
can't
recall
what
those
reasons
are:
it's
nothing
about
the
program.
It's
just
I
I
forget,
but
it
never.
We
always
every
year
we
talk
about
it
and
we
don't
participate.
F
I
probably
should
come
with
more
concrete
information
than
that
and
it's
probably
you
know.
Obviously
it's
been
great
for
a
lot
of
other
projects
and
I'm
sure
there
are
other
projects
in
the
openjs
foundation
that
would
benefit
from
it
tremendously.
So
I'm
totally
supportive.
I
just
don't
know
that
node
is
necessarily
the
right
place.
F
G
Yeah,
for
what
it's
worth
electron
has
a
a
new.
I
guess:
collaborator
from
postman
who's
been
driving
getting
electron
involved
in
this
and
been
helping
basically
be
doing
all
the
work
to
get
us
there.
So,
ideally,
we're
gonna
have
a
couple
people
who
set
up
for
it
as
mentors
we're
providing
the
list,
but
a
list
of
potential
topics
that
we
can
pull
someone
for,
we're
hoping
to
get
it
out.
The
deadline
is
thurs
or
is
monday,
which
is
a
holiday.
G
So
ideally
you
have
to
get
it
out
by
friday,
like
the
application
or
whatever.
So
that's
coming,
but
you
know
we're
we're
we're
planning
on
doing
it.
Ideally,
we
make
it.
We
might
not
make
that
deadline,
but
we'll
see.
E
E
Okay,
great
yeah,
that's
and,
and
just
in
case
it
was
missed
in
the
the
context
here.
Absolutely
no
I'm
sorry,
I
was
just
gonna
say
projects
that
would
like
to
to
apply
on
their
own.
We
absolutely
encourage
that
this
is
more
just
if
anybody
needs
help
wants
to
do
it.
On
the
you
know,
on
the
foundation
have
the
foundation
handle
this,
then
we're
happy
to
do
that
as
well.
So
that's
I
it's
great
to
hear
that
electrons
going
through
and
doing
this
cool.
G
Yeah,
I
appreciate
that
and
I
might
have
the
person
from
postman
reach
out
to
you
daniel
so.
A
I
you
know
the
website
redesign
stuff
always
comes
to
mind,
but
there's
just
not
someone
to
really
drive
that.
So
I
don't
think
that
that
and
we've
talked
about
a
little
bit
with
the
with
a
couple
of
the
folks
working
on
that.
I
don't
think,
there's
really
a
mentor
to
be
able
to
drive
that.
But
I
do
wonder
about
the
tooling
group.
We
have
a
few
things
we
want
to
be
doing
so
I'll.
A
We
have
a
meeting
on
friday,
so
I
will
talk
to
them
about
it
to
the
node.js
tool
group
and
see
if
we
can
take
advantage
of
this
program.
A
Nope,
okay:
I
will
make
a
quick
note
over
in
here
and
and
then
I'll
move
on
to
the
next
agenda
item.
A
Where
am
I
all
right?
So
next
item
on
the
agenda
is
add,
dates
and
reminders
the
bi-weekly
cpc
meeting
template.
I
actually
wanted
to
do
this
before
this
meeting,
because
I
think
there
are
some
key
things
that
are
not
being
tracked,
that
we
need
to
be
tracking
like
elections,
so
I'm
going
to
try
and
work
on
this
this
afternoon,
so
number
one.
A
I
get
dates
into
these
files
or
this
file,
and
also
so
that
I
know
if
we
have
elections
coming
up,
which
I
think
we
do
so
I
I
should
figure
that
out
and
get
ahead
of
it.
A
Work
on
that-
and
I
don't
know
what
else
there
is
to
say
about
it
at
the
moment,
so
I
will
move
on
next
issue
is
8
15.
This
is
the
license,
check,
support
and
tooling.
A
I
don't
know
if
there's
much
more,
that
we
want
to
talk
about
about
this
or
or
what
we
think
needs
to
happen
here
for
this
particular
issue.
Michael,
you
opened
it.
I
know
we've
had
a
lot
of
good
conversation
here,
but
what,
if
anybody
got
my
thoughts
about
this?
I.
C
C
A
Well,
what's
what's
the
ask,
though,
is
it?
Is
it
building
out
the
tool
that
jordan
has
or
is
it
like,
lfx
tooling,
that
we're
interested
in.
C
C
It's
it's
it's
like
is
the
the
the
linux
foundation
team
going
to
take
ownership
of
providing
a
solution
to
projects
of
some
sort,
and
I'm
not
going
to
tell
them
then
hey.
Do
it
like
this,
or
do
it
like
that
right?
You
know
it's
like
are:
are
they
interested?
Do
they
have
cycles?
Do
they
agree?
This
is
a
good
cross
project
cross.
You
know,
project
service
to
provide
and
if
so
great,
then
we
can
help
sort
of
support
them
in
that
effort
right.
C
B
I
think
what
I
heard
from
shubra
even
before
and
afters
yes,
they
could
make
it
happen.
Bandwidth
is
we
I
never
know
they
could
have
a
backlog.
I
would
say
three
months.
Maybe
I
guess
the
question
is
jordan?
Do
you
think
that
yours
could
be
you
think
you
could
work
with
schubert
on
something
or
do
you
think
that
they're
too
different
or
no.
H
The
yeah
I
mean
the
primary
driver
for
me
is
that
most
tools
for
repo
management
are
built
with
the
limited,
overly
limited
view
of
within
a
single
org
or
within
a
single
user
account,
and
I
have
like
eight
orgs,
and
so
I
need
something
that
uses
my
github
account
and
checks
everything,
and
so
that's
what
I
built
so
yeah
I
mean
the
the
actual.
Once
you
have
a
list
of
repos.
C
G
C
C
You
know,
and
my
point
was:
it
would
be
very
useful
to
have
a
tool
that
not
doesn't
check
your
dependency
licenses
but
just
says
in
our
repo,
like
we've
got
100
repos
125
repos
in
the
note
org
today,
the
the
tool
would
confirm
they
all
use
a
license,
which
is
a
which
is
approved
under
our
our
you
know:
open
js
foundation,
governance
or
no,
this
one's
missing
a
license,
or
this
one
has
a
different
license.
But
okay
yeah,
we
know
that's
that
that's
approved
by
the
board.
C
G
I
mean
at
the
very
least,
npm
has
also
built
this
dashboard
already,
with
their
status
board
thing
like
you,
can
see
the
full
list
of
licenses.
In
addition,.
A
That's,
I
think,
perhaps
repo
specific,
but
I
I
want
to
let
emily
speak
and
then
we
can
dig
back.
Is
it
just
me
or
does
this
sound
an
awful
lot
like
a
google
summer
code.
A
That's
a
great
point
emily.
So,
let's
put
a
pin
in
that,
but
yeah.
I
think
what
what
what
you
had
shared
their
tyranny.
The
the
status
board
is
that's
repo,
specific
right
where
I
think
michael
and
was
looking
for
like
cross-org
kind
of
stuff.
I.
G
Mean
you
could
just
put
multiple
orgs
in
it
like
it's,
not
it's
not
a
or
you
could
have
multiple
status
boards
in,
like
you
know
a
different
for
it
is,
it
is
repos
sure,
but
like
you're,
the
org
doesn't
have
a
license.
The
repos
in
the
org
does
it's
that
that
detail
is
irrelevant
to
this
specifically.
H
Yeah,
I
mean,
I
think
I
think
that
any
dashboard
like
this,
including
npms,
theoretically,
should
work
just
fine
and
the
main
reason
that
I
didn't
use
any
of
those
is
because
every
single
one
of
them's
list
of
repos
is
a
single
org
or
a
hard-coded
list
of
works,
and
I
wanted
a
tool
that
discovers
based.
On
my
github
token,
all
the
repos
that
I
can
manage,
which
is
across
multiple
orgs
and
also
users
and
user
owned
repos
tend
to
be
ignored
whenever
github
does
adds
features.
H
So
this
this
status
board
seems
great,
and
it
very
well
might
work
well.
Also
interesting.
C
C
H
B
It
makes
sense
to
have
it
in
the
lfx
dashboard
because
that's
exactly
what
they
want
us
to
get
requests
from
the
projects
from
the
communities
and
have
that
you
know
have
that
one
view.
So
why
don't
we
I
can
follow
up
with
schubert.
I
have
him
assign
an
engineer
again,
it's
just
not
as
maybe
as
fast.
You
know.
It
may
take
a
little
bit
longer
depending
on
what
other
stuff
they
have
on
the
pipeline.
A
Tierney
has
their
hand
up,
but
I'll
just
say
real
quickly.
You
know:
can
we
combine
those
two
thoughts
with
the
lfx
shubra
and
the
google
summer
of
code
just
put
that
out
there
but
tierney?
You
had
a
comment.
G
On
that,
specifically,
I
don't.
I
don't
know
if
that
worked,
because
lfx
is
an
open
source
as
far
as
I'm
aware,
but
like
I,
I
guess
I
I'd
be
fine
with
delegating
to
this
to
lfx.
I
just
want
a
commitment
from
them
that
it'll
be
done
like
that's,
that's
the
big
thing.
G
I
know
that
they
get
a
lot
of
requests
and
are
very
eager
to
do
things,
so
I
I
want
to
make
sure
that,
like
this
is
something
that
actually
gets
done
and
if
it's
not
like
telling
us,
no
we're
not
gonna
do
this
is
totally
fine.
Just
I
don't
want
like
a
maybe
halfway
commitment
in
it
to
stretch
on
forever.
C
Yeah,
I
think
I,
like
I,
don't
mind
somebody
saying
hey
yes,
but
three
months
is
when
we'll
start,
but
I
agree
like
it's:
we
we
want
the
yeah
we're
we.
You
know.
We
think
this.
We
we
think
this
is.
This
is
an
important
thing.
It's
something
we
should
provide
we're
going
to
do
it,
but
yeah.
We
can't
get
it
until
two
or
three
months,
but
yeah
timeline,
oh
so,
like
maybe
maybe,
or
maybe
not
yeah
yeah.
A
And
I
wonder,
I
don't
know
how
lfx
is
built
and
you
know
I
hear
your
your
comment:
tyranny
about
not
being
open
source.
I
wonder
if
we
could
use
google
summer
of
code
and
jordan's
tool
to
to
flesh
it
out.
This
is
what
we're
looking
for
and
then
you
know
that
would
at
least
fill
the
gap
for
now
and
then
lfx
can
incorporate
that
same
functionality
as
they
seem
to.
C
C
B
C
E
E
E
Yeah,
I
I
think
really
our
two.
Our
two
off-the-shelf
options.
Right
now
are
what
jordan
created
and
then
the
second
one
would
be.
If
we
wanted
to
really
you
know,
do
some
serious
license
scanning
linux
foundation
can
also
do
physology
scans
and
interpret
them,
and
that
that's,
I
think
that
may
be
not
meeting
the
need
that
jordan
is
describing
here
of
automatically
discovering
things.
E
C
Yeah,
I'm
kind
of
back
to
like
it's
something
I
I
think
would
be
good,
but
I
don't
know
that,
like
I'm
gonna
have
time
to
to
make
that
my
top
priority
to
go
and
look
at
a
tool,
and
so
I
I
was
raising
it
as
like.
Hey
everybody
has
this
problem?
Can
somebody
can
we
get
some
help
to
help
solve
it
like
in
that
context?
C
I'd
almost
rather
wait
for
something
which
will
be
like
hey
here's
our
way
that
we
do
it
across
the
projects
rather
than
putting
together
something
that's
specific
to
us
right,
because
I
don't
have
the
time
to
do
that
so
come.
It
comes
back
to
I
think,
tierney's
like
if
there's
going
to
be
a
yeah.
This
is
important.
It's
going
to
be
something
we
want
to
do
sort
of
standardize.
We
think
we
can
add
value
across
projects.
I'd
prefer
to
wait
than
to
couple
something
together
now
on
our
own.
If
you
know
what
I.
A
Mean
yeah,
it
seems
to
me,
like
the
path
forward,
is
to
see
if,
if
lfx
of
schubrun
team
can
put
it
on
their
calendar
and
give
us
a
date
that
they
think
they
can
hit,
and
then
you
know
see
how
that
goes
and
in
the
meantime,
if
somebody
does
have
cycles
and
wants
to
flush
it
out
in
a
tool,
then
cool,
but
knowing
myself
and
others
availability,
it
would
be
great
if
lfx
could
could
manage
it.
C
I
also
kind
of
see
it
as
like.
This
is
a
first
simple
example
of
the
kind
of
things
like
we've
got
some
guidance
at
the
open
gs
level.
This
is
the
first
simple
one
which
I
know
of
that.
Like
I've
been
like,
okay,
well,
we've
got
all
these
repos
are
we
are
we
keeping
on
top
of
as
well,
but
there's
going
to
be
other.
There
is
already
others
that
we've
talked
about
like
if
we
say
on
the
security
front
that
everybody
should
have
a
security.md
right.
A
C
A
All
right:
well,
we've
we've
kind
of
talked
about
this
for
a
while.
Should
we
comment
on
the
issue
that
that
you
know
see
if
schubert
can
can
give
us
an
estimate
on
on
that,
okay,
cool
and
then
we'll
just
see
how
that
progresses.
B
A
Great,
thank
you
too.
Robin
next
issue
is
786.
This
is
an
issue
toby
created
a
while
ago,
clarify
requirements
around
coc
violation.
I
know
toby,
you
you've
got
a
draft
pr
open,
which
is
830
yeah,
and
we.
I
Did
some
work
last
week
too,
all
of
us
which
I
have
notes
for
which
I
haven't
shared
yet,
and
I
apologize.
Let
me
let
me
turn
those
notes
into
something
that
maybe
I
add
to
that
issue
or
do
a
separate
doc
and
share
in
the
next
cpc
meeting.
If
that's
fine
with
you
all
sure,.
I
A
I
Soon,
cool,
if
folks
really
want
an
update
now
I
can
take
like
10
minutes
to
go.
Look
at
my
notes
and
figure
it
out,
and
then
we
can
go
get
back
to
this
issue
at
the
end
of
the
call,
if
you're
fine
waiting
for
two
weeks
I'd
it's
up
to
you.
A
We
only
have
one
more
issue
on
the
agenda,
so,
okay,
so
I'll
dig
in
while
you
do
that
issue,
okay,
we'll
see
in
a
minute.
A
So
the
next
item
on
the
agenda
is
issue.
756
create
proposals
for
the
community
fund.
This
is
a
you
know,
a
long-standing
issue.
My
last
comment
from
28
days
ago,
is
to
check
out
the
repo
and
to
further
flesh
that
out,
I
see
rich.
You
is
rich
still
on
the
call.
No
okay
rich.
Maybe
you
have
a
input.
Michael
rich
mentioned
this
at
the
tsc
on
the
26th
of
january.
I
don't
know
if
there's
any.
C
I
don't
remember
any
feedback
or
anything
like
that,
but
he
you
know
he
did
mention
that
hey.
This
is
going
on.
If
you,
if
you're
interested
this
is
this
is
where
you
can
get
involved.
Yeah.
B
I
think
one
of
the
one
of
the
takeaways
we've
had
at
one
point
on
this
issue
is
that
it's
pretty
broad
and
maybe
we
need
individual
issues,
there's
one
issue
in
particular
the
thank
you
program
that
we've
sort
of
done
a
little
bit
of
work
on,
but
then
we
had
our
standards
working
group
meeting
said
last
week
two
weeks
ago,
and
we
were
talking
through
some
programming
and
we
thought
a.
B
B
Similar
cncf
has
the
chopwood
gary
water
awards
community
awards,
so
I
wanted
to
sort
of
open
it
up
with
you
all
and
think
about.
This
is
something
we
would
like
to
do
in
the
cpc.
A
Yeah,
I
think
a
thank
you
program
would
be
fantastic.
I
shared
a
link
to
this
thing
that
just
went
out
recently
the
oss.love
by
netlify,
which
I
think
is
really
very
nice.
C
B
B
With
swag
upper,
you
know
with
swag
options,
and
I
think
that
that's
more
of
the
do
we,
you
know,
push
push
that
to
the
projects
and
then
they
thank
people
and
then
I'm
also
asking
do
we
also
want
to,
from
at
a
foundation
level,
give
some
community
awards
at
the
open,
js
world
conference
something
a
little
more
public.
You
know.
C
Yeah
that
sounds
like
you
know,
a
good
idea
under
the
thank
you
like
it
could
be
another
another
section
of
like
we
do.
Thank
you.
We
do
thank
yous
by
giving
the
projects
a
bill
to
do
this
and
then
once
a
year
at
our
at
our
conference.
We
also
do
this.
Here's
how
you
nominate
whatever
and
okay.
A
We,
you
know
a
thought
that
pops
in
my
head
is:
should
we
use
a
working
session
to
work
on
a
thank
you
program,
especially
since
open
jazz
world
is
not
that
far
away.
C
I
think
we've
spent
a
lot
of
time
talking
about
it.
I
think
don't
we
don't
like
that.
I
think
what
would
be
really
good
is
the
written
down
like
we.
We
have
that
structure
now
in
the
repo
I
think
the
most
effective.
So
I
could
see
us
having
a
working
session,
but
I
I
thinking
we
should
have
like
a
concrete
proposal
of
what
the
words
would
look
like
there
or
use
that
working
session
to
put
it
together,
yeah.
B
So
the
beautiful
thing
about
the
linux
foundation
family
is,
we
share
all
of
our
great
programs,
so
I
I'm
sure
I
can
on
the
awards
in
particular
and
the
nominations
and
whatnot.
I
can
pull
some
drafts
a
draft
together
for
us
to
review
swag
programs
separately
and
then
we
can
use
maybe
the
working
session
just
to
think
about
yeah.
C
C
If
we
look
at
the
one
we
have
for
travel
fund,
we've
got
the
sections
like
you
know
the
who
you
know,
we've
got
reinvert
how
you're
reimbursed
we
have
applications
in
terms
of
collaborator
applications
how
to
apply,
and
actually
we
even
have
like
for
the
standard
participation
we
have
section
so,
but
if,
like
a
pr
that
put
it
in
there,
that
would,
I
think,
make
it
really
concrete
and
at
the
end
of
that
session
we
might
be
able
to
say
yeah,
let's
prove
and
land
it
right
and
tweak
it,
and.
A
Yeah,
I
think
that's
great
and
robin
if
you
want
to
you,
know
powwow
before
you
know
before
our
next
meeting,
so
we
can
try
to
aim
for
having
a
prn
for
some
some
bones
of
the
thank
you
program
or
details,
and
with
that
in
mind,
the
schedule
the
working
session
schedule
would
be
next
week
would
be
security
and
then
two
weeks
after
that
would
be
thank
you
program,
community
fund,
which
gives
us
three
weeks
to
kind
of
really
put
something
together
to
chew
on
in
that
working
session.
A
I
Great
okay,
I'm
ready
to
fill
you
in
on
the
previous
issue.
I
If
you
want
sounds
good,
let's
do
it,
okay,
so
it
was
786,
so
we
had
done
some
work
a
while
back
now
in
one
of
our
regular
sessions
like
today's,
and
notably
tierney,
had
suggested
a
bunch
of
additions
to
the
code
of
conduct,
the
additional
document
that
goes
with
the
code
of
connect,
which
is
the
foundation
code
of
connect
requirements.md,
which
I'm
linking
to
here,
and
so
we
had
sort
of
come
up
with
a
list
of
what
we
wanted
in
there,
and
so
when
I
started
to
work
on
the
poll
request.
I
Finally,
not
that
long
ago,
I
actually
noticed
that
most
of
it
was
actually
in
that
document,
except
sort
of
like
the
requirements
were
very
much
embedded
in
sort
of
the
pros
and
we're
kind
of
like
hard
to
make
out.
So
what
I'm
proposing
to
do
is
turn
more
of
that
document
here
into
sort
of
like
a
list
of
requirements
to
make
it
sort
of
like
clear.
I
What's
expected
and
not
have
you
know
you
have
sort
of
like
things
where
it's
sort
of
like
implied
that
you
need
the
mailing
list
and
then
et
cetera,
et
cetera
right,
so
that
was
sort
of
like
the
first
part
of
our
conversation,
and
then
we
dug
into
things
that
we
hadn't
discussed
yet,
but
thoughts
were,
would
be
useful
to
add
sort
of
to
this
document
and
elsewhere.
I
The
first
thing
was
that
our
events
are
actually
under
the
linux
foundation,
events
code
of
conduct
and
not
on
the
other
code
of
conduct,
and
so
it
felt
useful
to
actually
add
this
in
the
code
of
conduct
itself.
I
Another
thing
that
we
suggested
and
thought
that
would
bring
to
the
cpc
for
discussion
was
that
we
now
that
we
have
a
footer
with
the
trademark
policy,
the
cookie
policy,
the
privacy
policy,
that's
sort
of
like
a
template
that
projects
can
just
like
pull
in
and
stick
at
the
bottom
of
the
website.
It
felt
kind
of
logical
to
add
the
code
of
conduct
directly
from
there.
So
that
was
a
suggestion
that
was
made
during
that
call.
I
Was
some
sort
of
like,
like
a
really
short,
eventually
like
a
short,
a
piece
of
text
around
it
that
we
could
share
what
we
could
discuss
once
once
since
in
the
polar
class?
I
We
also
discussed
merging
the
cpc
panel
and
the
escalation
panel,
because,
right
now
we
have
the
cpc
is
supposed
to
handle
certain
cases
and
then
we're
supposed
to
have
like
a
cocp
which
sort
of
code
of
comic
panel
is
supposed
to
handle.
Other
things,
it's
kind
of
like
unclear,
which
is
responsible
for
what
it
feels
like
a
lot
of
like
red
tape,
for
something
that
could
be
simpler.
I
So
we
wanted
to
sort
of
like
simplify
that
and
have,
instead
of
like
a
large
number
of
people,
three
or
four
people
max
and
actually
have
those
people
named,
because
one
of
the
things
we
wanted
to
have
as
a
requirements
for
projects
was
for
people.
That
would
be
responding
to
a
cpc
violation
to
be
named
so
that,
if,
like
the
person,
that's
responsible
for
the
violation
is
also
in
the
in
the
panel
you're
aware
of
it
up
front
and
that
doesn't
come
as
like
an
additional
surprise
and
already
difficult
situation.
I
So
you
know
that
was
the
first
step
was
actually
like
getting
our
house
in
order
before
asking
projects
to
do
so,
and
then
the
last
bit
was
the
linking
the
code
of
conduct
more
visibly
from
the
open,
jsf.from
opengsf.org,
because
it
was
sort
of
like
an
embed
in
a
sub
menu
somewhere
and
brian
just
did
that
right
away
after
the
call
last
week,
and
so
it's
now
at
the
bottom,
along
with,
like
the
other
important
policies
that
we
have
so
that's
kind
of
what
we
discussed
last
week
and
the
next
steps
are
for
me
to
actually
finish
the
pr
and
then
pull
all
of
those
suggestions
in
the
same
pr.
I
A
It
was,
but
I
look
forward
to
those
updates
and
you
know
feeling
like
that's
in
a
better
place
and
I
agree
yes,
cool
any
comments,
questions
thoughts,
anything.
A
No
right
on
well,
we
are
at
time
not
a
time
where
or
at
the
end
of
our
agenda.
We
already
talked
about
the
working
sessions
that
are
upcoming,
which
is
at
the
end
of
the
agenda
and
to
check
on
dates,
which
I
will
work
on
that
soon
too,
I
already
updated
the
meeting
issue
that
has
the
schedule
for
working
sessions.
So
that's
up
to
date.
C
A
Yeah,
let's
call
it
a
wrap
and
stick
around
if
you
want
to
talk
about
anything
and
we'll
go
from
there,
cool
ending
the
stream
thanks,
everybody
for
watching
see.