►
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
Welcome
everyone
to
our
cpc
meeting
this
fine
tuesday
november,
the
17th.
We
are
getting
started
a
little
bit
late,
because
we
just
enjoyed
a
interesting
presentation
from
someone
at
the
lf
cool
stuff.
Coming,
let's
start
with
some
announcements,
any
announcements.
A
Yeah
a
couple
they're
not
like
super
exciting,
but
you
know:
okay,
cool,
so
I'll
go
with
the
ones
that
I
have
and
if
you
remember
one
then
just
pipe
up
so
and
today
we
we
canceled
the
standards
team
meeting
that
is
ordinarily
at
two
o'clock
today,
but
on
december
1st,
which
would
be
the
next
day
for
the
standards
meeting.
We're
gonna
have
a
prolonged
session
on
strategic
planning
and
sort
of
visioning
for
2021.
So
if
you're
interested
in
that,
please
definitely
make
sure
to
note
your
calendar
for
the
december
1st
standards
meeting.
A
Also
later
today
we
have
the
marketing
committee
meeting,
which
is
also
super
fun,
we're
actually
doing
some
really
cool
stuff,
one
of
which
is
we
submitted
a
panel
to
south
by
and
so
we
would
love
your
votes.
If
you
could
go
and
vote
for
our
panel
at
south
by
southwest
that'd
be
pretty
cool.
A
Let's
see
what
else
I
feel
like
there
was
oh
and
then
we've
got
a
fun
meeting
planned
for
friday
for
those
of
us
who
have
been
interested
in
pushing
forward
on
the
individual
supporter
program
and
there's
like
we're
pretty
close
to
some
pretty
cool
stuff.
So
if
you
have
time
on
friday
and
would
like
to
join,
please
reach
out
and
slack
what
else
am
I
missing
this
week.
A
Nothing,
maybe
everything,
that's
all
I
can
recall,
but
if
we
think
of
something
else,
we'll
we'll
we'll
just
go.
Aha,
let's
go
to
our
next
agenda
topic,
which
is
board
meeting
updates,
which
is
not
bored
b-o-r-e-d
but
like
bored
as
in
fun.
C
A
All
right,
let's
quick,
board,
meeting
all
right,
then
we
move
to
our
normal
agenda
topics,
and
these
are
the
issues
that
are
tagged
with
the
cross
project
council
agenda
tag
on
our
github
repo.
A
A
Joe
has
a
proposal
for
kind
of
a
cadence
for
rotating
through
some
different
time
zones
and
there's
a
number
of
thumbs
up
on
that
issue.
But
no
further
comment.
So
I'm
curious,
you
know,
if
anybody's
had
time
to
reflect
on
that
or
propose
something
slightly
different
or
any
concerns
or
what
we
might
need
to
do
to
maybe
make
that
vision
and
dream
a
reality.
D
Some
thoughts
that
I
was
having
this
morning
is
to
give
folks
some
time
to
kind
of
be
aware
of
this
change.
Maybe
we
do
it
two
weeks
from
today
we
start
that
cadence,
unless
someone
objects
or
has
a
better
idea-
and
that
gives
us
you
know
next
week's
2pm,
meeting
or
later
meeting.
However,
you
phrase
it
and
then
the
following
week
we
would
kind
of
start
the
sort
of
two
weeks
in
a
row.
D
At
the
same
time,
you
know
first
meeting
be
an
official
meeting
second
meeting
being
kind
of
an
optional
working
meeting
and
then
just
sort
of
get
into
that
cadence.
That
was
my
thought.
A
Probably
a
good
idea
to
give
people
a
heads
up,
and
I
think
also
and
maybe
kind
of
timing,
that
for
near-ish,
like
the
holidays,
where
meeting
cadences
are
going
to
be
a
little
bit
wonky
anyway,
as
lots
of
folks
may
be
out
of
office
for
holiday
or
you
know,
and
we're
nearing
the
beginning
of
the
year.
That
makes
sense
to
me.
A
D
A
A
Robin
or
brian,
can
you
one
of
you
promote
a
geary
portfolio.
I've
lost
my
privileges
for
promoting
people.
A
Cool
exciting
stuff,
so
sounds
good.
We'll
we'll
give
ourselves
another
two
weeks
on
this
old
cadence
and
commence
with
a
new
one.
That
would
time
it
out
for
approximately
beginning
in
december
and
sounds
good.
A
All
right.
Tell
your
friends
we're
changing
our
meeting
time.
Moving
on
to
number
679.
We
actually
don't
have
this
ready
for
you
today
this
it
was
a
review
individual
supporter
program
designs.
We
are
just
getting
some
polish,
some
more
polish,
but
you're
gonna
love
it.
I
promise,
and
if
you
really,
if
you
really
are
itching
to
see
it,
which
you
should
be,
you
should
come
to
the
meeting
on
friday
and
then
you'll
definitely
get
to
see
it.
F
A
All
right,
so
there
we
go
number
658,
which
is
develop
growth,
print
growth
plan.
I
can
speak
now
template
and
then
I'm
kind
of
connected.
We
have
issues
650
and
647,
which
are
all
related
to
changes
around
the
growth
plan
and
the
growth
stage.
A
One
of
the
is
it
okay
to
would
y'all
be
comfortable
sort
of
treating
those
together
as
an
agenda
item,
as
opposed
to
trying
to
break
them
down.
C
A
Okay
cool,
so
one
of
the
action
items
that
was
a
result
of
last
week's
meeting
was
to
reach
out
to
growth
stage
maintainers
and
ask
for
you
know
their
thoughts
and
feedback
and
input.
A
We
had
two
folks
who
weren't
already
actively
involved
in
the
conversation
way
in
and
both
indicated
that
they
have
really
no
problem
with
the
idea
of
dropping
this
as
a
like
formal
stage
and
moving
it
more
into
something
that
was
more
like
a
tag,
or
you
know
something
like
that,
so
I
don't
they
seem
to
find
the
utility
in
it
and
didn't
really
have
any
concerns.
A
So
I
think
to
that
end
on
the
for
the
for
the
growth
stage,
projects
themselves,
they're
comfortable
and
a
few
of
them
added
a
few
comments
to
the
issue
so
reporting
on
that
that
action
item.
So
with
that
feedback
and
with
that
sort
of,
like
you,
know,
tacit
support
of
growth
plan
projects
to
kind
of
experiment
here
I
think
the
next
question
is
you
know
what
do
we?
C
A
I
think
some
of
them
are
interested
in
and
you
know
I
don't
want
to
put
words
in
anyone's
mouth,
so
I'm
not
going
to
identify
anybody,
but
I
think
there's
at
least
one
who
would
be
interested
in
seeing
if
they
can
qualify
for
impact.
Actually
at
this
point,
so
I
think
there's
a
process
that
we
need
to
go
through
for
figuring
out
whether
they're
going
to
be
an
at-large
or
an
impact.
E
G
C
Like
we
could
close
this
out
by
saying
you
know
basically,
if
you're
in
growth,
you're
going
to
go
to
at
large
with
a
growth
plan
optionally,
you
know
if
people
still
want
to
do
that
and
then
you
know
applying
to
be
promoted.
I
think
we
have
an
existing
process
right
that
somebody
just
needs
to
start.
D
A
I
think
that
makes
sense,
because
I
think
so
there
were.
There
are
a
couple
of
the
growth
stage
projects
that
actually
didn't
necessarily
intend
to
advance
to
impact
that
that
wasn't
a
goal,
and
so
you
know,
I
think
that
just
saying,
okay,
we're
all
these
are
all
at
large
now
and
we'll
go
through
a
process
of
of
applying
the
growth.
C
A
And
you
know,
speaking
personally,
I've
never
particularly
cared
for
that.
Like
graduated
versus
you
know
incubating
language,
I
think
it
just
doesn't
make
it
clear.
You
know
that
that
these
are
part
like
that
they
are
part
of
the
foundation.
Regardless
of
what
you
know
stage
they're
in.
I
think
that
was
always
a
challenge
we
had
with
the
js
foundation
back
when
we
had
grad,
we
had
graduated
projects
so
yeah,
I'm.
C
Just
I'm
just
thinking
like
there
is
in
me,
at
least
in
my
mind
the
fact
that,
like
currently
impact-
and
I
think
probably
the
same
goes
for
cncf-
is
like
projects
who
have
reached
the
state
where
they've
got
a
broad
contributor
base.
They've
got
open
governance,
it's
you
know,
that's
that's
still
important
versus
you
know.
We've
joined
and
well
we're
we're
still
a
one
person.
You
know
the
fdl
or
something
like
that
right,
because
we
can
have
all
those
different
kinds
of
projects,
but
that's
kind
of
the
main.
C
G
Yeah,
I
think
that's
right.
I
mean
really
the
the
stages
that
we
have
in
our
life
cycle
here.
They
they
are
communicating
a
different
thing
than
the
stages
in
the
cncf
life
cycle,
because
the
cncf
life
cycle
once
you're
in
you're,
basically
in
and
here
we
are
using
our
stages
to
communicate
the
once
you're
in
the
maturity
or
the
the
aspirations
or
the
the
general
needs
of
the
project,
which
is
just
you
know,
it's
it's.
A
different
dimension
is
all
and
yeah.
C
F
F
C
C
G
A
Yeah,
so
I
think
I
I
I
think
the
purpose
of
growth
plans
for
us
is
really
more.
I
think
twofold
one
is
in
the
case
that
the
project
really
does
want
to
meet
that
impact
level
that
we've
defined,
and
the
second
is
the
project,
has
some
specifically
scoped
needs
or
objectives
or
wishes
that
it
is,
you
know,
needing
of
extra
resources
or
like
focused
mentorship,
or
something
like
that,
which
is
not
ordinarily
part
of
what
they're
they're
getting
as
an
at-large
project.
A
So
I
think
if
we
can
find
a
template
or
a
you
know,
a
structure
that
that
kind
of
accommodates
that
need
which
could
be
time
bound
and
scoped.
That
would
be
great.
C
So
I
guess
your
original
question
is:
what's
our
next
step,
I
mean,
I
guess
our
next
step
could
be
to
move
like.
Basically,
you
know
pr
out
that
stage
and
move
all
the
existing
growth
stages
to
at
large
and
then,
along
with,
maybe
adding
like
a
growth
plan
for
relevant
ones.
D
Yeah
doing
that
work
and
you
know
merging
the
pr
to
make
the
changes
and
then
maybe
jory
like
a
follow-up
email
to
the
project.
Saying
we've
successfully
done
this
and
you
know
everybody's
at
large
and
we
have
this
concept
of
a
growth
plan
and,
if
you're
interested
in
moving
from
at
large,
to
impact,
let's
figure
that
out
together
and
work
through
this
growth
plan
process.
C
That
that's
yeah
I
like
that
in
terms
of
the,
if
you're
interested
here's
the
template,
that
we
put
together
for
a
growth
plan,
and
you
know
so,
if
you
create
one,
then
you
can
yeah
make
it
make
it
a
not
a,
not
a
pull.
D
But
a
push
right,
yeah
and
also,
I
think,
to
celebrate
the
the
change.
I
think
it's
you
know
we're
we're,
making
progress
and
some
of
the
things
we
designed
in
the
bootstrap
process,
we're
in
a
vacuum
and
so
we're
we're
improving
things
so
frame
it
that
way,
but
also
inviting
these
projects
to
be
involved,
like
you
know,
we're
trying
to
figure
out
how
to
help
you.
We've
got
this
concept
of
a
growth
plan
instead
of
a
growth
stage,
and
so,
let's,
let's
work
on
it
together.
D
E
A
So,
okay,
well,
I'm
happy
to
follow
back
up
with
those
projects
and
just
say
you
know:
give
them
like
the
heads
up
that
this
is.
This
is
what
will
happen
and
get
their
input
start
getting
their
input
on.
What
that
plan
document
can
look
like,
and
I
believe
that's
already-
there's
a
template
or
draft
yeah,
and
so
we
can
start
just
collaborating
on
that
template
on
the
pr.
A
D
A
D
So
before
we
move
on
just
in
I'm
looking
at
the
pull
request,
650,
which
is
still
in
draft
mode-
and
you
know
we
don't
have
approvals
on
this.
D
Anyway,
I'm
trying
to
think
through
like
what
the
actual
moving
on
for
this
is
the
next
steps,
sorry,
which
one
is
that
650
pull
request,
650.
D
A
And
christian
broman
also
added
some
as
well
recently,
so
it
looks
like
we
still.
You
know,
have
dialogue
on
this
and
and
it's
toby's
pr,
so
maybe
once
they
are
available
to
respond
to
some
of
these
comments
or
and
maybe
open
up
the
the
draft
for
other
editors,
we
can,
we
can
incorporate
and
get
this
puppy
moving.
D
A
D
Yes,
that,
okay
and
then
so
I
have
an
issue
related
to
that
which
doesn't
seem
like
things
are
linked,
but
I
think
we
can
close
issue
675
my
issue
as
well
as
miles's
issue
right,
because
I
think
we've
landed
everything.
A
This
is
great,
go
go
team
yeah,
so
thank
you
joe
miles
and
michael
for
for
that
work.
Number
632
is
the
next
of
our
remaining
issues.
This
is
and
provide
implementation
guidance
for
dco
and
cla.
This
has
been
a
ongoing
work
in
progress
that
that
toby
and
brian
have
been
leading.
I
don't
know
that
there's
been
an
update
on
the
issue
itself
since
september
brian.
Do
you
know
any
update
on
this.
G
Yeah,
so
I
I've
got
a
working
draft
here.
I
would
like
to
get
one
or
two
other
sets
of
eyes
of
attorneys
on
it,
just
to
make
sure
that
I'm
positioning
things
correctly
here,
but
yeah,
hopefully
in
the
next
day
or
two.
G
It's
been
a
long
work
in
progress,
but
it's
coming
so
no
just
get
some
eyes
on
it
and
we'll
be
good
to
go
great.
A
Thank
you,
brian
that'll
be
very
helpful,
and
this
is
just
going
to
be
a
great
resource
to
our
community
for
ensuring
that
they've
got
their
their
systems
wired
up
and
what
they're
doing
so.
G
Yeah
and
part
of
the
key
thing
here
too,
is
that,
for
I
know,
we've
talked
about
this,
but
it
probably
bears
repeating
in
prior
versions
of
the
foundation.
This
wasn't
a
choice
like
you
either
had
to
use
dco
or
you
were
required
to
use
a
cla
one
of
the
big
changes
for
the
open.js
foundation.
Is
we
left
that
optional?
So
it's
up
to
each
one
of
the
projects
to
make
their
decision
based
upon
the
project
community
which
one
they
need.
So
that's.
G
The
the
goal
of
this
guidance
is
to
provide
at
least
a
basic
framework
for
understanding.
You
know
the
implications
of
making
one
decision
or
another.
It's
not
meant
to
be
legal
guidance.
However,
it
is
basically
here
are
the
different
things
that
you
would
need
to
consider
from
a
from
a
practical
perspective,
if
you're
choosing
one
or
the
other.
A
All
right
that
takes
us
to
our
last
a
topic
which
is
number
653,
moved
supporter
program
to
stage
three
joe
added
to
agenda.
D
Yeah
I
threw
this
on
there
just
because
I
was
going
through
the
simplifying
the
proposal
process,
work
and
talked
with
michael
this
morning
and
he
merged
in
his
pr-
and
I
just
was
curious
because
this
one's
been
there
for
a
bit
and
I
pinged
sarah.
She
was
only
available
the
first
half,
but
I
wasn't
able
to
join
this
meeting,
but
it
would
be
great
to
land
this,
but
I
don't
know
if
we're
waiting
for
the
creative
review
or
you
know,
we've
got
the
other
simplified
proposal
process
stuff
in
alignment.
D
Yeah
I
haven't
looked
since
your
merge,
what
that
looks
like,
but
but
yeah.
However,
we
would
need
to
get
that
there
so
anyway,
at
a
minimum.
I
wanted
to
raise
this.
As
you
know,
this
would
be
another
great
thing
to
kind
of
get
landed.
D
Not
really
consider
completes,
I
think,
there's
this
will
be
a
journey
pun
intended,
but
you
know
having
this
pr
land
would,
I
think,
be
great.
I
feel
like
it's
real.
A
D
Yeah-
and
I
I
did
you
know
in
the
slack
conversation
where
she
was
looking
for
the
meeting
link
this
morning
or
just
you
know,
half
hour
ago,
I
erased
it
to
her
that
you
know
that
I
was
hoping
to
discuss
this.
So
it's
on
her
radar
at
least.
D
Do
we
sorry
to
kind
of
jump
around
here,
but
do
we
need
any
private
time
today.
A
I
mean
we
kind
of
took
most
of
it
at
the
beginning
for
that
session,
and
there
there
was
an
email
that
I
sent
to
the
private
list,
which
is
exciting
and
you
should
read
it
if
you
haven't,
but
that's
certainly
not
necessarily
something
we
need
to
take
meeting
time
to
discuss
because
we're
we're
just
use
the
asynchronous
communication
channels
for
that.
But
I
suspect
we'll
take
some
time
next
week
to
discuss
that.