►
From YouTube: 2021-09-14-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
Okay,
welcome
to
the
cpc
meeting
for
september
14
2021.
We
will
follow
the
agenda
that
was
in
the
issue
tagged
in
the
repository,
which
was
issue.
797.
first
thing:
does
anybody
have
any
public
announcements
they'd
like
to
share.
B
A
bit
of
a
quiet
week
this
week,
but
we
do
have
the
programming
committee
meeting
on
thursday
and
also
a
selection
of
folks
from
the
standards
working
group
are
chatting
with
w3c
for
their
ac
office
hours
today.
If
there's
anything
interesting,
you
wanted
to
know
or
discuss
with
our
colleagues
at
the
w3c.
That's
coming
up
later
today
at
four
o'clock
eastern.
So
that's
that's
it.
I
usually
have
a
long
list
of
things,
and
I
don't
today
so
I'm
sorry.
I.
C
Have
one
thing
quick
thing
this
friday?
I
should
get
the
time
right.
I
will
be
honored
to
be
a
guest
on
the
wonderful
show
in
the
open
that
ibm
host
with
joe
seppy
and
lucas,
so
that
is,
I
should
have
this
memorized
and
it's.
E
I'll
just
add
too,
I
don't
know
much
of
an
announcement
but
posted
in
slack
channels,
travis
ci
security
issue,
if
you're
using
it
still,
I
know
they
they
burned
a
lot
of
the
community,
but
if
you're
still
using
it
rotate
your
keys
and
yeah
be
safe.
A
A
Sounds
good.
I
do
remember
there
was
something
that
was
in
some
of
the
notes.
One
of
the
meetings
I
didn't
miss
that
was
going
to
go
to
the
board
for
a
vote.
I
don't
think
we've
quite
had
that
happen.
Yet
so,
hopefully
we
can
get
that
in
for
next
week.
G
Sure,
hello,
everyone
there
is
a
quick
announcement
native
script.
8.1
was
just
released
yesterday.
It
was
an
exciting
update
for
everyone
involved
on
the
team
and
it's
nice
to
expand
into
kind
of
official
workspace
development,
which
has
been
the
javascript
community
for
a
long
time,
but
particular
things
with
the
cli
had
constrained
it
in
certain
ways.
So
8.1
sort
of
removes
those
restrictions
on
that
line
thursday.
G
A
E
A
H
E
E
Yeah
I
started,
I
started
a
document
in
the
repository
to
just
collect
them
and
that
we
could
check
on
every
now
and
again
until
we,
you
know,
have
something
more
automated
in
place.
A
Okay,
I
mean,
I
think
that
could
be
the
perfectly
good
solution
where
we
look
at
that
each
week
in
the
in
the
the
repo
versus.
Not
you
know
if,
if,
if
we
don't
have,
can
think
of
what
an
automation
helps,
I'm
just
saying
I,
I
don't
think
we
necessarily
have
to
say
automation's
the
end
goal
in
this
case,
but
so
it's
good
to
see
some
progress
on
that
one.
In
that
front,
the
next
one
is
794,
create
dates
and
reminders.
E
And
so
I
think,
there's
one
question
related
to
this.
If
I
remember
correctly
is,
should
we
capture
the
dates
to
remember
in
an
issue
or
in
a
document
in
the
repository
I'm
open
to
either,
I
think
that's
one
question
toby
and
I
were
going
back
and
forth.
H
I
mean
we
shouldn't
be
spending
a
lot
of
time
on
this.
Frankly,
oh
I
I
think
just
folks
should
have
a
look
at
both
solutions
and
figure
out
like
what
works
for
them
and
then
pick
one
I
don't
think
either
joe.
Would
I
really
care
so
essentially
whoever
is
going
to
handle
the
meeting?
Michael,
maybe
that's
you,
and
so
maybe
you
should
just
decide
whatever
feels
easier.
E
Hitting
well
that's
automatic,
but
yeah,
so
I
guess
the
question
is
we
could
just
update
the
templates
to
have
something
sort
of
like
we
check
in
on
the
working
session,
stuff
and
and
and
point
to
the
dock,
or
we
have
an
issue
that
has
an
agenda
label.
Personally
I
I
like
that.
The
document
at
the
top
level,
the
repo
and
we
can
edit
it
as
we
see,
fit
and
organize
it
as
we
see
fit.
But
again
I
I
agree
with
you
toby.
F
A
E
E
Worked
just
really
quickly,
and
maybe
I
don't
know
why
I'm
directing
this
to
toby.
But
can
you
create
a
quick
issue
to
just
say
add
the
reminder
for
dates
document
to
the
meeting.
H
Yeah,
I
think
we
had
a
bunch
of
agreements
as
what
what
the
next
steps
were.
There
was
one
small
issues
that
that
one
small
issue
that
came
up
as
I
was
trying
to
start
on
working
on
the
pull
request
for
that
was.
There
is
a
requirement
for
using
a
mailing
list
to
be
able
to
report
code
of
conduct
violations,
but
there
is
no
requirement
for
clarifying
who
was
on
the
receiving
end
of
that
mailing
list,
and
this
felt
like
something
that
was
awkward.
H
If
you
were
about
to
report
something
that
had
happened
to
you
not
being
aware
of
like
who
you're
reporting
that
to
could
feel
really
scary.
And
so
I
was
wondering
if
people
have
thoughts
about
how
we
should
move
forward
with
that.
H
To
give
a
bit
of
context
to
folks
who
are
not
clear
was
what
this
issue
is.
This
issue
is
about
adding
a
minimum
set
of
requirements
to
make
sure
that
there
is
a
found
across
a
different
projects,
agreement
as
to
the
basics
of
how
to
handle
a
coc
evaluation
or
delegated
to
the
cpc.
If
our
project
doesn't
want
to
handle
it
itself,.
A
J
As
long
as
the
requirement
isn't,
I
think
to
that
we
use
absolutely
real
names,
but
that
they
are
identifying.
I
don't
know
github,
usernames
or
anything
to
to
basically
identify
the
person
rather
than
revealing
private
information
that
a
person
might
not,
who,
at
the
receiving
end,
might
not
want
to
share.
A
A
B
B
Multiple
patterns
that
a
project
could
choose
and
there's
certainly
some
projects
that
and
like
dojo,
is
one
I
think,
there's
only
one
or
two
people
and
they're
like
hey,
it's
dylan
and
nick
there
you
go
and
that's
that's
fine.
As
long
as
somebody
knows
who's
getting
it.
H
So,
just
for
clarity's
sake
are
requiring
the
recipients
of
that
email
to
be
known,
as
is
what
the
agreement
is
about.
People
agree
with
that.
H
G
J
C
A
Okay,
so
the
next
issue
is
number
782,
which
is
simplify
coc
page.
A
Okay,
okay,
so
waiting
on
birds,
so
yeah,
hopefully
we'll
cover
that
off
this
week
or
next
week.
Sorry,
when
the
board
meet
takes
place,
next
one
is
reminders
for
long-term
events.
This
is
758.
H
This
is
probably
the
issue
that
we
have
there
to
be
reminded
to
be
reminded
about
long-term
events.
It
feels
like
we
can
close
this.
H
Oh
or
rather,
let's
have
the
pull
request
close.
Let's
have
795
close
it.
Okay,
so
we'll
say
this
should
be
closed.
H
E
Because
it
may
be
good
enough
to
land,
and
then
we
just
you
know,
modify
it
as
we
go.
H
E
A
F
H
E
H
No,
no
I'm
sorry.
What
I
meant
is
what
we
had
discussed
joe
is:
if
this
is
a
document
in
the
cpc
repository
and
you
want
to
update
it,
because
we
have
like
something
that
we
have
to
you
know
like
something
to
add
during
a
meeting
right
like
we
can't
we
want,
we
don't
want
to
have
to
wait
on
the
two-week
requirements
to
merge
a
full
request.
A
Right
but
it's
not
a
it's.
Basically
pro
requests
do
not
change
charter
or
governance.
Cpc
can
be
merged
in
the
repository
following
condition,
so
no
objections,
two
approvals
by
cpc
members
72
hours.
So
it's
not
quite
two
weeks.
I
agree
we
could
add
in
another
section
into
that
merging
prs,
which
is
basically
like
for
this
file.
A
There
are
no
requirements
or
something
if
we
wanted
or
one
approval-
or
I
don't
know
what
right
but
but
I
don't
know,
we
need
to
wait
to
land
it
to
do
that,
because
we
can
separately
have
a
pr
that.
E
F
No
worries-
and
I
hope
that
I'm
not
should
would
it
make
sense
to
also
add
these
things
to
the
calendar.
B
F
Why
not?
I
don't
know
if
I
who
has
rights
to
that
calendar,
I
don't
want
to
just
throw
a
work
on
people's
plates.
If
I
can
add
it,
let
me
know,
if
not
then
sorry.
B
Staff,
joe
any
you
know,
lots
of
lots
of
us
so
once
this
lands
we
can
get
get
them
all
added
as
recurring
events.
So
awesome
thanks.
A
A
Okay,
the
next
one
create
proposals
for
the
community
fund,
756.
C
Yeah
I'll
give
you
all
a
quick
update.
If
you
see
at
the
very
end
of
the
document
we
have,
we
had
a
plan
for
the
node.js
lyft
scholarship,
that's
going
out
at
the
end
of
the
week,
lots
of
great
things,
doing
a
blog
and
a
direct
mail
piece.
Some
social
and
some
press
outreach.
So
that's
exciting
to
get
that
launched,
and
I
think
the
only
other
piece
on
that
I
need
from
you
all
is
a
volunteer
or
two
to
help
me
review.
C
The
applications
that
come
in
michael's
been
a
great
set
of
eyes
on
this.
Already,
I
don't
know
if
you
want,
if
you're
interested
in
continuing
or
any
of
you
or
folks,
from
your
projects.
If
they'd
like
to
help
review
those
that
come
in
so
once
it
goes
live
we
give
it
30
days
to
come
in
and
we'll
do
some
marketing
throughout
that
time
and
then
30
days
out,
we'll
review.
C
B
C
Probably
a
couple
of
hours,
we
have
some
estimate
based
on
the
number
of
applications
that
come
in
from
the
linux
foundation.
That's
broader!
C
What
we
do
is
give
it
sort
of
a
one
run
through
because
sometimes
applications
that
come
in
that
are
incomplete
or
like
one
words,
so
we
sort
of
pair
those
back
and
create
a
shorter
list
so
probably
similar
to
what
you
would
find.
If
you
have
experience
working
on
the
program
committee
going
through
and
reading
some
of
those,
but
we
tried
to
we
created
some
little
limits
and
have
concise
answers.
A
Okay,
okay,
so
I
guess-
and
I
don't
know
if
we
there
was
some
discussion
in
one
of
the
last
working
sessions
right.
So
I
don't
know
if
it's
worth.
C
C
Yep
that
we
would
give
an
update.
Last
week
we
had
a
working
session
on
how
to
spend
the
remaining
because
again
we're
only
using
a
portion
of
the
funds
that
were
set
aside
so
jorie.
Do
you
want
to
give
a
recap-
and
I
think
next
steps
might
even
be
to
carry
on
the
conversation
as
well.
B
Yeah,
so
we
had,
unfortunately
not
the
the
greatest
turnout
that
we
were
hoping
for,
and
so
we
kind
of
recapped
the
areas
that
we
were
imagining
the
community
fund
would
be
deployed
to.
Obviously
we
have
the
the
lyft
scholarships.
B
We
have
the
the
travel
program
as
well,
which
is,
is
quite
active,
so
these
these
are
systems
that
we've
already
kind
of
developed,
a
muscle
to
deliver
on,
and
there's
a
couple,
though,
that
we
were
excited
about
that
we
don't
have
the
muscle
for
delivery
on
yet,
and
I
think
the
group
spent
the
most
time
kind
of
thinking
and
contemplating
what
a
like
a
thank
you
program
could
look
like,
so
this
would
be
a
function
where
project
maintainers
could
send
tokens
of
gratitude
somehow
to
contributors
or
people
who
are
supporting
their
project
in
a
meaningful
way,
say
they,
you
know,
helped
close
a
a
feature
or
they
they
helped
do
some
training
or
support,
or
you
know
whatever
the
case
may
be
it's
up
to
the
project.
B
Frankly,
so
we
we
talked
about
different
ways
that
we
could
kind
of
deliver
that
if
we
perhaps
scoped
a
a
package
that
the
foundation
kind
of
get
puts
together
with
like
a
t-shirt
and
a
thank
you
card
and
some
stickers
or
something
like
that
and
or
whether
there's
something
more
customizable
for
the
project.
Maintainers
say
sending
people
like
an
american
express
gift
card
for
25,
for
example.
So
these
are
different
things
that
we
we
discussed
and
the
action
item
there
was
we're
going
to
go.
B
Take
a
look
at
the
the
kind
of
the
cost
and
the
packaging
that
we
we
know
can
be
provided
by
a
third
party.
So
there's
third
party
services
do
these
sorts
of
things
and
that's
probably
the
way
to
go
here.
That
was
maybe
the
biggest
the
other
areas
where
we
thought
maintainers
might
want
to
maybe
spend
some
time
is
or
or
have
something
is,
for
example,
just
more
ad
hoc,
and
we
don't
really
have
a
muscle
for
that.
Yet
either
we
were
kind
of
debating
about
like
what
kinds
of
things.
B
What
kind
of
parameters
we
might
want
to
kind
of
put
on
an
ad
hoc
request
so
that
we
can
either
make
sure
that
it
kind
of
fits
within
the
goals
of
the
community
fund?
Or,
frankly,
you
know
it's
not
something
that
we
might
already
be
funding
out
of
a
different
account
accounting
account
because,
for
example,
the
the
foundation
supports
a
wide
variety
of
infrastructure
costs
for
projects.
B
So
if
our
project
says,
can
I
have
some
money
for
infrastructure
that
may
very
well
fit
very
well
in
our
our
current
budget
so
and
that
kind
of
recaps.
The
conversation
on
the
community
fund,
specifically
but
again
I'll
note
that
it
wasn't
inclusive
of
everybody
who
may
care
to
think
about
this
stuff,
and
so
we're
gonna
continue.
A
G
If,
if
I
may,
I
think
that's
a
great
idea,
you
know
tipping
is
something
I
think
in
open
source
people
do
enjoy
doing.
G
You
know,
even
if
it's
99
cents
1.99
something
like
that
youtube
live
streams,
obviously
taking
contributions
to
comment
and
have
a
comment
show
up
in
in
the
stream
there
and
people
do
that
a
lot
for
anyone
that
live
streams
for
an
hour
on
any
topic
that
they
are
interested
in
and
it
is
a
good
way,
I
think,
to
probably
get
some
open
source
projects,
some
some
support-
and
perhaps
maybe
there
is
some
way
to
answer
questions
in
that
realm
too,
where
someone
really
needs
a
direct
answer,
but
perhaps
you
know
github
issue
reporting
or
the
forums
on
any
particular
project
is
not
answering,
but
maybe
someone
you
know
would
love
to
contribute
something
to
get
a
direct
answer.
G
Perhaps
I
don't
know
the
best
way
to
roll
something
out
like
that
other
than
integrate
it
into
some
process
that
either
is
through
openjs,
directly
or
individually
through
projects,
there's
probably
a
number
of
creative
ways.
You
could
go
about
doing
that,
but
I
think
that
would
be
interesting.
I
think
I
know
I
would
have
contributed
to
open
source
projects
to
get
some
more
involved
discussions
or
inquiry.
K
I
I
you
know
having
come
in
about
30
seconds
ago.
I
already
have
opinions
on
this
topic
yeah.
I
I
get
concerned
about
enabling
individual
contribution.
I
think
it's
masking
sustainable
funding
for
open
source
projects
in
a
way
that's
unsustainable
and
putting
the
onus
on
individuals
in
a
way
that
creates
a
somewhat
toxic
relationship
that
gets
out
of
the
people
who
are
actually
benefiting
most
from
it.
K
The
people
who
are
making
millions
off
of
open
source
work
not
having
to
do
anything
and
showing
that
on
individuals
who
are,
you
know
getting
employed
by
those
people
or
those
companies,
so
yeah,
I,
I
am
very
critical
of
you-
know
whether
it's
something
like
github
sponsors
or
open,
collective
and
individual
contributions.
K
A
Projects
could
say
thank
you
to
somebody
who
not
not
it's
not
like
hey
you
did
this
here's.
You
know
here's
a
return.
It
would
be
like
exceptional
cases
where
somebody
said
hey.
Somebody
really
stepped
up.
Thank
you
for
doing.
Thank
you
for
doing
that
and
it
could
be
through
something
more
than
just
like
the
words.
Thank
you.
G
Perhaps
I
threw
that
off
tourney
by
saying
kind
of
asking
for
a
immediate
need.
Yeah,
I
think
that's
more
the
better
line
to
go
what
michael's
talking
about,
I
think
you're
more,
a
tip
gesture
that
makes
sense.
K
Yeah
sorry,
I
I
heard
that,
and
that
is
something
I
am
very
concerned
about
when
it
comes
to
open
source
funding.
So
I
wanted
to
make
sure
I
raised
that
if
that's
what
we
were
talking
about,
so
apologies
for
really.
A
Yeah,
this
really
shouldn't
be
anything
about
funding.
This
is
more
just
like
hey
the
ability
for
a
project
to
to
give
a
special
thanks
to
some
people
who
have,
you
know
have
done
something
I
I
I
personally
find
that,
like.
I
quite
like
that
with
the
ability
to
do
that
within
a
company-
and
this
is
something
that
you
know
the
opengs
could
help
enable
for
projects
if
they
think
that,
if
we
think
that's
going
to
be
useful
and
beneficial.
K
E
G
E
Just
say
real
quickly:
one
idea
that
we,
tossed
around
too
was
maybe
having
a
list
of
organizations.
You
know
girls
who
code
or
what
have
you
and
you
could
like
have
a
small
amount
that
they
would
donate
in
your
name
kind
of
thing.
It's
another
idea.
G
C
G
C
Our
badge
vendor
to
do
something
like
that.
I
believe.
B
Yeah
we
could,
we
could
do
badging
we
we
could
also
do
like
in
terms
of
if
there's
a
way,
you
want
to
empower
the
community
to
suggest
people
who
need
to
be
appreciated
or
knowledge.
Perhaps
there's
a
like
a
form
that
then
the
tsc
reviews
and
says.
Oh
you
know
we
got
these
suggestions
that
we
should
honor
michael
and
sarah
jordan.
B
H
Yeah
I
just
wanted
to
like,
I
think
the
thank
you
aspect
is
great.
I
think
that's
valuable.
I
think
we
have
to
be
worried,
as
tyrion
mentioned,
about
tipping
for
a
number
of
reasons,
also
because
it's
a
very
north
american
thing,
it
has
a
also
a
kind
of
a
problematic
history
and
it's
it
feels
really
weird
to
your
appearance.
H
For
example
like
it's,
it's
a
weird
practice
for
us
here,
and
so
you
know,
let's
just
be
careful
like
let's
be
careful
about
how
this
is
like
talked
about,
and
lastly
also
I
think
another
thing
that's
important,
which
is
why
I
really
like
this
idea
of
being
being
able
to
donate
this,
that
money
to
other
organizations
instead.
Is
it's
also
not
just
like
ship
junk
to
people
all
the
time?
Like
the
conferences?
Do
this
it's
bad?
Can
we
stop
doing
that?
H
A
I
think
that
was
part
of
the
reason
we
said
like.
Let
the
recipient
choose
what's
meaningful
for
them
right,
and
so,
if
that's
a
donation
to
a
charity
grade,
if
that's
some
swag
okay,
but
if
it's
a
small
amount
of
money
whatever
like
try
and
figure
out
a
good
set
of
those.
Now
I
should
let
it
go
to.
J
Yeah,
I
think
we're
like
overthinking
this.
I
mean
honestly
from
my
point
of
view,
having
once
received
flag
for
doing
a
contribution
to
an
open
source
client
thing
that
someone
else
that
that
a
corporate
entity
did.
I
thought
that
was
really
cool,
and
I
thought
really
there,
this
flag
itself
didn't
matter.
It
was
the
sense
of
them
wanting
to.
Thank
me
and
me
first
of
all
not
expecting
anything
like
that
and
being
able
to
offer
something
like
that
to
contribute
to
projects.
J
Exceptional
ones
in
particular
would
be
really
cool
and
yeah.
It's
not
meant
to
be
something
that
anyone
does
for
the
money.
It's
meant
to
be
something
that
you
know.
We
just
do
to
someone
that
isn't
expecting
to
get
anything
for
what
they've
done,
but
we
just
want
to
thank
them
right.
It's
a
surprise.
A
J
J
Having
an
option
to
get
you
know,
so
you
know
we
said
we
could
send
you
a
small
bunch
of
swag
or
you
know
you
could
say
we
could
do
a
small
contribution
to
do
one
or
two
of
these,
these
nice
things
that
you
know
which
what
do
you
want
and
then
go
with
that.
A
B
Right
so,
and
I
think
the
last
bucket
of
a
possibility
for
the
community
fund,
I'm
just
going
to
keep
reframing
this
as
possibility,
we
haven't
taken
a
full
decision
on
any
of
this
is-
and
this
is
something
I
know
some
projects
are
doing-
they're
trying
to
think
about
ways
that
they
can
support
local
meetups,
where
a
meetup
may
have
a
javascript,
meetup
and
they're
talking
about
webdriver.
B
The
webdriver
project
might
like
to
send
that
meet
up
some
stickers
or
some
pizza,
or
you
know,
do
something,
and-
and
so
we
want
to
maybe
think
about
make
operationalizing
a
process
where
they
can
say
hey
the
the
meet
up
in
berlin
is
doing.
This
would
like
to
send
them
a
fifty
dollar
hundred
dollars
for
pizza
or
whatever.
Can
we
do
that
through
the
community
fund,
as
opposed
to
having
to
run
our
own
system?
A
H
Oh
yeah,
sorry
that
was
me.
I
was
looking
at
code
of
conduct
for
the
pr
we
talked
about
earlier
and
I
bumped
into
an
issue
with
that
form.
Hadn't
been
working
for
like
over
a
year
and
it
still
isn't
working,
and
so
that
probably
needs
to
be
fixed,
and
I
don't
know
why
I
reported
it
here
rather
than
the
dojo
thing,
because
I
was
in
a
hurry.
Essentially.
B
K
I
believe
I've
also
I've
I've
raised
this
in
the
past
as
well.
I
I,
I
think,
dylan
got
all
right.
I
think
dylan
at
one
point,
I'm
not
sure
what
the
status
of
it
was.
A
B
So
this
is
the
link
that
they
use
to
have
people
notify
of
a
report,
and
that
is
used
in
a
couple
of
places,
one
of
which
is
our
list
of
where
to
report
issues
for
each
project.
B
C
H
B
So
we
don't
have
any
update
on
this
and
other
than
to
just
say
it's
been
just
to
recap
again
really
quickly.
B
The
question
on
the
table
for
us
is
whether
the
linux
foundation
should
perhaps
consider
bringing
the
probot
dco
app
under
its
purview
for-
and
I
should
not
say
under
its
purview,
but
should
become
code
owners
effectively
for
that
application,
and
so
that
we
can
help
manage
and
maintain
the
feature
that
we
would
be
adding
with
the
pr
that
brian
submitted.
B
We
have
been
a
bit
busy
with
the
easy
cla
hot
swap
over,
as
well
as
just
it's
kind
of
a
busy
time
of
year,
right
now
across
all
of
the
the
projects
as
we
prepare
for
and
the
2022
budget
and
member
renewal
cycle.
So
I'm
not
sure
that
this
is
something
that's
getting
the
strategic
visibility
at
the
moment.
It's
really
needed
in
order
to
take
this
decision,
but
it's
not
it's
not
forgotten.
It
is
still
very
much
here.
B
A
E
Yeah,
I
think
so,
although
toby
did
have
an
idea
to
double
back
and
see
if
the
at-large,
you
know
interacting
more
with
that
large
projects
was
what's
happening,
so
I
don't
mind
keeping
this
on
the
list.
I
feel
like
we're.
B
B
B
Would
I
personally
maybe
prefer
to
keep
it
the
issue
open
and
maybe
tag
it
with
like
a
backlog
or
something
so
that
it's?
We
know
that
it's
not
this,
this
urgent
thing,
but
I
think
that
makes
more
sense
than
putting
it
elsewhere
in
my
two
cents,
but
it
doesn't.
B
Well,
just
and
maybe
also
for
the
record
that
it
sounds
like
what
we've
asked
or
what
we
we
are
asking
is
not
for
this
to
become
the
remit
of
openjs
foundation,
but
for
this
to
become
the
remit
of
lfit,
which
makes
it
not
really
our
decision.
But
it
does
impact
us
because
it's
something
that
we
want
implemented
because
it
will
benefit
our
foundation.
B
So
you
know
that's,
maybe
an
important
distinction,
because
the
community
here
has
decided
it's
not
really
something
that
we
can
take
on.
But
it's
something
that
the
community
felt
the
lf
should
consider
taking
on.
A
Yeah,
I
think
it
came
up.
Sorry
go
ahead.
Terry,
go
ahead,
michael!
I
I
think
it
came
up
because
it
you
know
it
was
mentioned
that
many
projects
depend
on
many
of
the
linux
foundation.
Projects
depend
on
this
dco
bot
and
this
this
pattern,
and
so
that
seemed
like
a
natural
question.
It's
like
okay,
if
it's
important-
and
this
isn't
obviously
an
important
issue
across
the
foundation-
could
could
we
get
some
support
on
it?
A
K
Yeah
that
makes
sense
is,
is
there
some
kind
of
like
you
know,
timeline
of
expectation
of
hearing
back
from
them.
B
I
mean
I
would
probably
suppose
that
we
would
have
maybe
more
time
and
ability
to
move
this
forward
by
like
mid-october,
just
because
of
all
the
things
that
are
going
on
and
robin's
nodding.
So
that
seems
yeah.
C
I
know
that
team
has
some
milestones
that
they're
hitting
for
mid-october
actually
from
a
timing
perspective
I
just
came
off
and
now
left
calls.
So
that
sounds
reasonable
and
I
know
brian
has
invested
a
lot
of
time
and
coding
and
thought
around
this.
So
we
do
want
to
move
it
forward.
So.
K
I'm
glad
to
I'm
glad
to
hear
that,
and
would
it
be
possible
like
just
to
note
that
in
the
issue
that
like
that's
a
potential
like
not
not
a
commitment
but
like
you
know
the
estimated
time
that
we've
we've
kind
of
shared
in
the
cpc
just
so
we
can
kind
of
keep
note,
because
I
think
we're
it's
good
to
document
that
stuff
as
it
comes
up
yep
cool,
perfect.
Thank
you.
B
B
You
know
as
and
feature
complete,
maybe
as
we
would
like
them
to
be,
and
so
the
issue
with
implementation,
the
provide
implementation
guidance
for
dcocla
is
sort
of
morphed
into
something.
That's
a
lot
more
specific,
which
is
hey.
We
want
xyz
feature
added
to
to
this
bot.
You
know
how?
B
How
can
we
make
that
happen,
because
we
think
that
will
make
dco
a
more
attractive
choice
for
projects
so
that
that's
it's
sort
of
interesting,
because
every
time
we
hit
this
issue,
we
have
to
do
some
restating
of
the
context
and
all
of
that
it's
a
lot
more.
You
know
detailed.
Maybe
it's
worth
kind
of
revising.
A
It's
it's
fairly
closely
tied,
though,
because
the
dco
recommendation-
and
there
was
discussion
that
basically
was
the
recommendation
to
use
the
dco,
as
is
there-
were
several
projects
that
expressed
concerns,
so
the
recommended
guidance
was
going
to
be
to
do
it
in
the
way
that
the
pr
allows
you
to
do
it.
But
of
course
you
can't
make
that
recommendation
until
you've
got
the
tool
that
lets
you
do
it
that
way,
right.
B
Right,
yeah
and-
and
that's
that's
just
a
little
bit
of
a
catch-22
I
think.
A
B
One
thing
I
wanted
to
just
bring
up
is
you
know
we
we've
had
the
working
sessions
on
our
off
weeks
from
our
regular
sessions
and
we're
noticing
that
we
don't
get
as
much
attendance.
At
least
we
didn't
as
much
as
we
wanted
in
august,
that's
probably
due
to
a
lot
of
last
minute
travel
and
people
being
out
of
office
and
all
of
that
sort
of
thing.
B
But
we're
going
to
you
know,
start
taking
some
different
sort
of
tax
to
help
make
sure
you're
all
aware
of
like
the
topics
that
we're
covering
in
the
working
session,
so
that
if
it's
something
that
interests
you
and
you
do
want
to
participate
and
weigh
in
and
that
you
at
least
know
what
it
is
that
we're
talking
about,
so
that
you
can
put
it
on
your
calendar
for
real
and
make
time
make
time
to
come.
And
so
to
that
end.
B
Last
week,
as
we
said,
we
reported
on
the
we
talked
about
the
community
fund.
The
next
meeting
for
working
meeting
is
skep
for
september
21st.
We've
currently
penciled
that
as
a
coc
working
meeting,
but
we
also
have
a
couple
of
other
topics
which
may
be
more
more
pressing.
My
recommendation
might
be
to
do
the
easy,
cla
demo
and
discussion
for
project
maintainers
on
the
21st,
because
that
is
suddenly
something
that
we
have
had
to
turn
on
for
everybody,
so
everybody
who
has
opted
into
into
that
as
an
option.
B
So
that
is
september.
G
I
just
had
a
closing
thought
on
the
openjs
world:
is
there
a
banner
or
a
common
banner
that
all
projects
could
share
to
put
up
because
it,
I
know,
with
the
travel
being
it's
much
in
advance,
we'd
love
to
put
the
word
out
about
that?
Are
there
limitations
to
the
venue?
Are
you
trying
to
keep
the
attendance
below
you
know?
Is
it
okay
that
should
all
projects
put
a
banner
up
and
and
we
could
help
create
such
a
banner-
that's
consistent?
I
thought
that
would
be
nice.
C
That's
great:
we
had
banners
created
for
2021
and
we'll
have
them
for
2022
shortly.
Okay,
great
yeah
and
we'll
have
more
information
to
share,
but
we're
following
the
linux
foundation,
where
vaccines
are
mandated,
masks
are
mandated
as
well
so
and
we're
looking
at
co-locating
with
some
other
entities
next
year
as
well,
because
we
have
a
great
space
of
the
hyatt.
So.
C
That's
okay!
It's
all!
Coming
together
and
and
as
jerry
mentioned,
we
have
our
program
committee
meetings.
So
if
you
or
anyone
else
is
interested
we'd
love
to
have
you
on
board
how
we
structure
it
to
who
will
speak.
B
And
how
you
would
like
to
see
you
know
your
project
engage
with
it.
You
know
and
we
have
we're
providing
community
spaces
in
the
past.
We've
done
like
project
office
hour
desks
where
projects
can
sort
of
arrange
to
have
people
there
to
just
talk
to
people
in
the
exhibition
hall
about
you
know
things
that
are
going
on
or
do
a
lightning
talk
about.
You
know
the
latest
news
from
the
project.
We
we
want
this
to
be
the
project's
event.
B
You
know
so,
whatever
kind
of
thing
you
might
think
of,
I'm
sure
there's
a
way
to
to
do
it
so
sending
it
rep
from
your
project
to
to
the
programming
committee
would
be
super
rad,
so
we
can
make
sure
we
we
get
that.
C
We
meet
on
thursdays,
it's
on
the
public
calendar,
it's
every
other
week.
I
believe
it.
I
can't
remember
if
it's
eight
or
nine
my
time,
pacific,
but
yeah
and
also
you
know
we
have
the
event
which
are
two
days
and
then
the
two
days
following
are
collab
summits
for
projects.
C
C
E
And
just
to
double
back
on
your
question
jory,
I
think
easy
cla
makes
sense
for
for
next
time,
but
I'm
open.
B
Any
issues
swapping
easy,
cla
and
cfc
working
group
meeting
or
working
session
we've
got
stuff
happening
for
both,
but
I
just
think
it.
The
easy
cla
issue
is
more
pressing
because
it's
there
be
bugs
yeah
and
we
want
to
solve
them
with
our
can
of
objection
here.
Cool.
Thank
you
I'll
swatch.
Those
thank
you.
A
Hey
any
other
issues,
people
want
to
bring
up
before
we
close
out.