►
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
We
do
have
announcements.
I
will
make
those
on
behalf
of
jory
this
morning.
Tuesdays,
of
course,
are
our
favorite
days
because
we
get
to
see
you
all
so
much
after
the
cpc
meeting
today.
Actually
at
11
a.m.
Pacific.
We
have
our
standards
working
group
meeting,
there's
a
standards
workspace
in
our
slack
channel.
If
you
want
more
information
at
12
noon,
pacific
we
have
our
open,
js
foundation,
marketing
committee
meeting
again.
Those
are
all
on
youtube
as
well.
B
So
if
you
want
to
take
a
look
or
participate
and
at
1
pm
pacific
is
our
open,
js
world
2021
program
committee
meeting
and
particularly
for
our
project
reps,
we
really
love
to
have
a
representative
on
that
program
committee.
As
we
start
thinking
through
tracks,
see
you
know
issuing
cfps
for
early
next
year
and
planning
for
our
2021
virtual
event,
which
is
going
to
be
in
early
june.
A
Is
that
I'm
sorry
to
jump
in
here
that
last
minute
you
talked
about
the
program
planning
committee.
A
B
A
B
Yeah,
it's
typically
not
public.
We
take
project
reps
and
folks
from
the
marketing
committee,
but
if
someone
is
interested
in
participating
contact
me
and
I'm
sure
we
could
use
your
help.
Okay,.
B
B
B
Yeah
and
we're
not
just
we're,
in
addition
to
content,
we're
thinking
through
how
we
even
structure
the
event
next
year
is
that
one
day,
two
day,
three
days
last
week,
we
had
our
last
this
year.
I
guess
it
was.
We
had
a
whole
week
so
we're
just
trying
to
work
out
what
we're
going
to
do
and
looking
through
a
lot
of
experiences
from
the
other
tech
conferences
that
have
been
happening
so
pulling
data
to
make
those
decisions.
A
Excellent
another
announcement,
michael.
D
C
That's
our
next
major
and
14.x
goes
to
ltx
next
next
week.
So
lots
of
excitement
this
week
and
next,
yes
for
sure.
A
Lots
of
excitement
great.
Let
me
drop
this
link
in
here
for
toby.
Thank
you
for
joining
my
friend
cool.
Getting
into
the
agenda
then.
A
First
on
the
list
here
is
develop
a
growth
plan
template
this
is
an
issue,
and
is
this
the
pull
request
related
to
it
right
trying
to
pop
around
here
nope.
This
is
the
kind
of
top
level
issue
592.,
but
don't
we
have
a
growth
plan
template?
Am
I
crazy.
E
Toby
yeah,
there
is
one,
I'm
sorry
it
just
turns
out.
My
camera
is
not
working.
I
have
to
log
out
and
log
back
into
zoom
yeah.
There
is
a
growth
plan,
a
port
quest
somewhere,
I'm
not
exactly
sure
where
I'm
actually
not
on
top
of
things,
for
the
cpc
at
all
this
week.
E
C
E
E
And
I
I
have
a
thing:
that's
in
a
tab
on
my
browser
somewhere,
that's
been
sitting
there
for,
like
probably
over
a
week,
if
I
haven't
lost
it
in
the
meantime
that
tried
to
address
this.
I
will
get
back
to
it
shortly
and
also
I
don't
think
it
has.
I
don't
it
has
to
land
in
the
other
repository
as
my
feeling,
but
I
might
be
confusing
this
with
another
one
so
regardless
I
know
I
have
work
to
do
that.
A
All
right
cool,
I
I
added
a
couple
of
related
issues,
so
maybe
that
will
kind
of
show
up
properly.
I'm
not
sure
I
did
that
right.
Yeah
looks
like
I
did
cool
great
all
right.
Well,
we'll
we'll
move
that
along
in
the
coming
days
or
whatnot
thanks
toby,
I
guess
relatedly,
the
oh!
No,
that's
that's
copied
and
pasted
okay
cool
next
on
the
agenda.
Here
is
the
work
in
progress
proposal
to
remove
the
growth
stage.
A
Any
I
guess,
toby,
this
is
kind
of
on
your
plate
too.
You
want
to
give
us
an
update
or
anything
here.
A
A
C
Unless
somebody
wanted
to
champion
it
separately,
which
I
don't
think
we
we
had
anybody
saying
oh
yeah
yeah.
We
need
to
do
that.
So
I'm
just
thinking
like
you
know
the
the
review
like
the
develop
annual
review
process
for
projects-
that's
maybe
the
one
we
could
leave
on
with
a
reference
to
the
different
ones
that
we
need
to
look
at,
or
I
don't
know
just
just
thinking,
because
we
seem
to
talk
about
them
each
week
but
say
the
same
thing.
A
Yeah,
I'm
not
even
sure,
like,
I
think,
removing
the
growth
phase
doesn't
necessarily
need
to
be
dependent
on
any
sort
of
growth
plan,
because
I
feel,
like
growth
plan
templates,
you
know
different
projects
could
have
different
ideas
of
what
a
growth
plan
might
be.
I
think
just
the
idea
of
two
project
phases
rather
than
the
third
with
growth
there
I
think,
could
be
standalone.
I
don't
know
what
other
people
think.
E
I
would
agree
with
you
joe
actually
on
this
point,
though
I
also
get
michael's
point,
which
is
oh,
it's
pointless
to
have
these
things
show
up
every
week
to
just
discuss
them
again.
If
there's
no
progress
made
and
I
apologize
for
the
no
progress
made.
E
But
I
also
think
that
we
have
to
acknowledge
that
folks
have
like
a
whole
bunch
of
things
going
on
and
can't
necessarily
like
have
updates
on
a
weekly
basis,
and
maybe
we
could
have
something
to
say:
hey
can
you
can
we
raise
those
back
like
in
a
month
or
so?
We
have
sort
of
like
a
slow
or
sort
of
like
cycle
to
make
sure
we
don't
lose
track
of
stuff,
but,
like
maybe
have
like
an
in-progress
thing
or
I
don't
know
some
kind
of
label
that
would
help
this.
F
G
One
thing
we've
done
over
in
node
in
the
tsc
is
we
have
what
we
call
strategic
initiatives
that
have
champions
and
then
in
every
meeting
we
do
an
update
on
the
strategic
initiatives,
but
it's
not
necessarily
expected
that
we're
going
to
have
a
full
discussion
on
them.
In
fact,
it's
the
opposite.
G
It's
expected
that
it
will
just
be
kind
of
like
an
update
and
sometimes
that
update
even
just
happens
in
text
in
the
issue,
so
it
might
be
like
to
borrow
some
work
terms
like
we
have
epics
kind
of
which
are
like
these
really
big
initiatives
that
we
are
doing.
That
like
are
ongoing
and
it
might
be
reasonable
to
kind
of
you
know,
switch
the
discussion
where,
like
it
might
still
be
like
we
could
just
do
a
review
of
like
all
these
epics
that
are
in
flight
and,
like
separately,
build
an
agenda.
C
A
H
Sorry,
I've
lost
a
bit
of
track
on
this
one,
but
did
we
have
something
in
progress
regarding
actually
reaching
out
to
the
projects
that
are
currently
in
growth
stage
about
how
they
feel
about
things
related
to
this.
E
C
I
think
that's
the
way
I
remember
it
is
that,
like
it
was
like
yeah.
That's
that's
interesting,
but
you
know
toby's
was
like
well,
I
only
got
so
much
time,
so
the
thing
you're
actually
moving
forward
is
putting
to
helping
to
put
together
growth
plans
for
amp,
and
I
think,
along
with
chris
for
moca
right
and
that
was
kind
of
the
next
step
once
you've
gotten
through
that,
then
maybe
looping
back
to
look
at
the
removing
the
stage
or
not
made
sense
might
be
something
you
were
going
to
pick
up.
E
E
I
agree
that
emily's
suggestion
to
get
input
from
growth
projects
could
be
interesting,
but
I
think
we've
sort
of
like
discussed
that
sorely
already
and
we're
sort
of
not
really
inclined
to
see
this
sort
of
like
great
evaluation
thing
too
much.
That
was
my
understanding
from
previous
discussions.
C
A
Yeah
and
I
think
if
we
position
it
as
do
you
have
any
objections
to
this,
something
that
we've
discussed
a
bunch
at
the
cpc.
You
know
this
is
what
we're
looking
at
doing.
Are
there
any
objections
from
you
on
the
project,
rather
than
opening
it
up
for
more
discussion,
necessarily
which
I'm
I'm
happy
for
input,
I'm
just
saying
framing
is
sometimes.
A
Sorry,
if
it's
noisy
over
here,
I've
got
I've
got
a
puppy
thanks
for
your
help.
My
also
he's
gone.
Okay,
all
right,
so
I've
got
a
couple
of
notes
here
to
to
look
at
a
couple
of
these
things
and
maybe
I'll
ping
jory
about
you
know
some
sort
of
a
message
out
to
growth
projects,
and
you
know
I'll
look
at
trying
to
create
some
sort
of
epic
issue.
If
that's
the
way,
we
want
to
track
this
and
a
number
of
other
things.
A
Frankly,
we
should
make
sure
don't
kind
of
fall
by
the
wayside
I'll
try
to
work
on
that
this
week,
I'll
show
the
puppy
near
the
end.
I
don't
want
to
derail
too
much
cool
anything
else
on
this
issue
before
we
move
on
to
next
items,.
A
Next
up
is
again
issue
649.
Should
we
have
a
lightweight
mechanism
to
spin
off
ad
hoc
meetings?
I
feel
like
a
ding
dong.
When
I
see
these
things
I
know
we've
talked
about
a
bunch
and
I'm
not
sure
what
the
status
is
exactly,
but
I
think
we
we
we've
landed
on
doing
some
working
sessions
right
and
for
potentially
at
some
point,
creating
a
template
to
help
people
if
they
wanted
to
spin
off
a
working
group
meeting.
Is
that
accurate.
F
I
think
we
decided,
I
think,
from
what
I
remember
and
someone
told
me
if
I'm
wrong.
I
think
the
decision
was
to
start
with
the
working
sessions.
I
think
we
kind
of
got
hijacked
because
I
think
we
started
talking
about
the
working
sessions
in
this
meeting
and
I
don't
remember
if
we
came
to
a
resolution
about
the
ad
hoc,
okay.
B
B
E
If
we
all,
you
know,
if
there
was
a
process
to
run
this
because
it
actually
takes
time,
but
I
think
yeah,
I
think
you're
all
right
that
we
ended
up
saying:
let's
try
to
have
more
work
sessions
during
those
weekly
calls
and
see
if
we
still
need
those
ad
hoc
meetings
in
the
future.
E
So
I
think
there
was
this
tension.
Sorry
joe,
I
think
it
was
this
tension
between
wanting
to
run
more
of
those
meanings
in
the
as
working
sessions
in
the
weeklies
and
also
some
people
were
like.
Well,
I'm
not
really
interested
in
that
topic.
Why
do
I
have
to
sit
through
those
and
I
think,
like
we
didn't
really
resolve
that
tension.
A
I
think
it's
if
it's,
you
know,
if
we're
using
the
overflow
time
of
the
meeting,
once
we
get
through
the
agenda,
then
people
can
drop
if
they
want
right.
I
don't
think
that's
too
much
of
an
impact.
Is
that
correct.
A
E
A
I
was
going
to
say
I'm,
I'm
writing
up.
This
comment
saying
you
know,
for
one
consensus
is
to
use
cpc
meeting
time
beyond
agenda
to
do
some
working
session
work.
Another
idea
is
to
create
a
working
session
meeting
template
that
would
provide
info
on
the
following
link
to
doodle
calendar
scheduling,
zoom
link
from
openjs
account,
hack,
md
or
google
doc
link.
Is
there
anything
else
that
we
think
would
be
useful
in
a
template
like
this.
E
I
think
that's
a
good
start.
Okay,
all
right,
so
concrete
outcomes
do
we
want
some
do
we
want
actually
to
create
that
template
and
have
it
somewhere
in
the
repository,
like
is
like,
is
a
pull
request.
A
concrete
outcome
of
this.
E
Can
someone
that
is
familiar
with
the
tools
actually
volunteered
to
do
this?
I
mean
I'm
pointing
the
fingers
that
brian
warner,
who
is
that
who
has
already
too
much
on
his
plate?
I
know
that
oh,
a
jury
who
isn't
there
so
yeah,
but
I
I
think
it
would
be
easier
if
it
was
someone
who
actually
knew
which
tool,
rather
than
actually
have
someone
go
ask
for
this
stuff.
A
E
E
D
Is
the
question
about
adding
zoom
links
and
things
like
that,
so
that
people
have
them
available
to
use.
G
D
And
things
yeah
absolutely
happy
to
help
coordinate
on
this,
and
it
definitely
does
make
sense
to
have
a
central
calendar
for
all
of
this,
so
that
we
don't
have
collisions
so
easy.
And
yes.
A
D
Yep,
okay,
that
would
be
great
yeah
and
then
I
think
we
could,
if
we
could
just
all
agree
that
whatever
meeting
is
on
the
calendar,
is
the
one
that
has
the
primary
rights
to
the
zoom
link.
You
know
for
so
that,
for
example,
ad
hoc
meetings
don't
displace
scheduled
ones.
That
sort
of
thing
that's
probably
about
it.
A
Cool
all
right.
Well,
great,
that's
progress!
So
yeah
toby!
If
you
want
to
just
drop
a
meeting
template
in
there
and
to
I
don't
think
we
have
anything
yet
write.
Any
issue
templates
doesn't
look
like.
Oh
wait,
hang
on
pull
request
templates,
but
that's
it
workflows,
but
the
github
directories
there
so
drop
it
in
there.
E
Yes,
that's
good
yeah,
I
hadn't
thought
of
that
makes
sense.
Absolutely.
A
Cool
cool
cool,
great,
all,
right
cool,
that's
some
progress
there
and
I
put
some
notes
in
the
issue
itself,
so
we
know
excellent.
Next
up,
I'm
gonna
ask
robin
if
she's
got
any
examples
of
successful
applications
that
she
can
share
with
us.
B
Yes,
I
just
dropped
in
a
comment,
work
on
adding
the
other
three,
but
we
offlined
and
we
all
decided
yeah.
We
need
to
have
a
more
uniform
way,
a
more
discoverable
way
of
filling
these
out
and
sharing
them
with
the
world.
So
we're
creating
a
web
form
to
do
that.
So.
A
Cool
excellent.
Thank
you
this
next
one
is
issue.
632
provide
implementation
guidance
for
dcocla
brian
has
experimented
with
some
implementations
of
this
any
thing
new
from
you,
brian.
D
This
is
my
week
to
get
it
done,
so
I
think
I
think
a
week
ago
I
said,
give
me
two
weeks,
so
things
are
blocked.
Things
have
unblocked,
so
I'm
hoping
that's
something
we
can
review
by
the
next
meeting.
A
Great
great
great
and-
and
I
I
meant
to
comment
earlier
too,
when
toby
was
talking
about
like
things
that
are
kind
of
in
progress
and
there's
not
much
of
an
update.
There's
no
like
just
saying
it's
in
progress
or
next
week,
or
whatever
is
always
fine.
I
know
we
all
have
lots
going
on,
so
never
any
guilt
or
anything
like
that
cool
next
on
the
list
is
issue
592,
develop
annual
review
process
for
projects
I
mean,
I
think
this
is
kind
of
related
to
what
we're
talking
about
earlier.
A
We
have
some
stuff
happening,
I'm
not
sure
if
there's
too
much
to
talk
about
on
this
issue,
anybody
have
anything
they
want
to
add
or
share,
or
anything.
A
If
not,
then
we
will
continue
on
and
if
I
am
able
to
look
at
kind
of
an
overarching
epic
around
this
sort
of
work.
I
will
you
know,
look
at
that
issue
pull
anything
needed
from
there
and
you
know
determine
whether
it
needs
to
be
closed.
Or
what
have
you
excuse
me.
A
A
Let
me
actually,
I
wrote
this
down
somewhere,
I
think
in
our
slack
I
pinged
kind
of
what
I
synthesized
as
the
the
takeaways
from
our
conversation
and
that
consensus
was
remove
the
term
staging
two
phases
incubating
so
in
terms
of
the
proposal
process
incubating
and
ready
for
review.
Slash
approval
as
many
pr's
as
you'd,
like
through
the
incubating
process,
essentially
providing
snapshots
pr
to
move
artifacts
into
place,
is
the
ready
for
approval
phase
and
a
desire
for
a
definition
of
done.
A
So
does
anyone
want
to
open
up
that
file
and
drive
kind
of
implementation
of
these
ideas
or
move
it
forward
in
that
regard,.
C
A
F
A
A
I
think
it's
fine,
because
the
definition
there
makes
sense
can
you
increase
your
font,
michael
for
those
of
us
following
along.
I
Quick
question:
is
there
any
restriction
on
who
can
be
a
champion.
A
So,
typically,
in
typically
in
node,
the
champion
was
usually
a
member
of
the
committee.
That
is,
you
know,
in
charge
of
the
initiative.
So,
like
you
know,
community
committee
or
the
tsc,
but
that's
a
good
question.
I
mean
I
think
so
where's
the
wording
that
we're
looking
at
here.
Oh.
I
I'm
looking
at
line
11,
they
have
a
short
name
and
identified
champion
just
like
if
someone's
looking
at
this.
If
someone
says
I
want
a
proposal,
I
want
to
make
a
proposal
and
then
they
pull
up
this
document.
Then,
like
the
the
question
they
might
one
question
they
might
have
is
who
can
be
the
champion?
I.
I
A
No,
I
think
it's
I'm
glad
you
brought
it
up
to
me
personally.
I
think
anybody
should
be
able
to
suggest
something,
but
maybe
we
can
change
the
language
there
to
say
you
know
a
champion
should
be
identified
early
in
the
process
or
something.
I
The
way
we
generally
do
it
is
that,
like
anyone
in
the
world
can
submit
a
like,
create
a
proposal,
an
author
one,
but
for
the
sake
of
having
every
single
person's
random
idea
being
like
not
being
considered
a
stage
zero
proposal,
the
like
sort
of
implicit
undocumented
convention
is
that
you
have
to
have
the
author
has
to
either
be
a
delegate
or
has
to
have
a
champion
who's
a
delegate
or
has
to
be
on
a
proposal
agenda
like,
in
other
words
like
there
has
to
have
been
a
step
taken
towards
presenting
it,
and
you
know
it's
it's
fine
to
like
presenting
it
at
a
meeting
requires
that
it
has
a
champion.
I
I
It's
just
like
it's
like
like,
in
other
words,
I
think
it's
useful
to
put
a
very
low
friction
gate
to
prevent
any
random
idea
from
consuming
all
of
our
energy
and
time.
C
I
B
I
B
Yeah,
I
would
expect
that
you
know
all
are
welcome
to
come
to
our
cpc
meetings
and
present
their
idea,
and
you
know,
but
you're
right
I
mean
having
that
first
lens
through
a
pr
makes
sense
as
well
yeah
but
having
but
having
the
ability
to
know
somebody
to
champion
at
the
beginning.
I
think
is
too
restrictive.
So.
H
I
All
right:
well,
I
mean
the
the
language
that
github
uses
when
it's
not
a
draft
is
ready
for
review,
and
that
actually
seems
appropriate
here.
Right
is
that
anyone
can
open
a
pr.
It
is
marked
ready
for
review
when
they
have
located
a
champion,
which
they
don't
need
to
do
in
advance
of
opening
the
pr
and
anyone.
Anyone
with
write
access
on
the
repo
can
flip
the
pr
you
know
put
back
and
forth
between
those
statuses,
so
it
doesn't
matter
if
they
open
it
with
the
correct
status.
I
In
the
first
place,
we
can
just
kind
of
set
it
to
draft
as
needed,
or
set
it
to
ready
for
review.
When
someone
wants
to.
You
know
champion
it
that
that
that
seems
to
me,
like
a
really
nice
balance
between
what
robin's
talking
about,
which
is
like
allowing
anyone
to
submit
a
pr
and
removing
the
the
necessity
of
knowing
the
right
people
in
advance,
but
also
like
provides
some
ability
for
us
not
to
get
inundated
with
things
that
we
all
need
to
pay
attention
to
immediately.
A
So
essentially,
we
have
an
incubating
proposal,
but
we
should
have
some
sort
of
asterisk
here.
Some
sort
of
note
that
if
you
are
not
a
cpc
member
one
needs
to
be
identified
as
a
champion
and
that
shouldn't
prevent
you
from
opening
a
pr.
But
please
make
it
correct
that
makes
sense
to
me.
I
C
I
H
That's
the
reason
why
I
suggested
cpc
member
is
that
if
somebody
comes
in
who
cares
enough
to
put
in
a
request
a
proposal
for
anything
and
does
not
immediately
get
a
champion,
we
can
then
easily
tell
them.
Oh,
you
know
you
could
also
become
a
member
of
the
cpc.
Just
you
know
actively
participate,
and
then
you
can
champion
this
yourself.
C
Right,
but
I
I'm
even
like
thinking,
though,
that,
like
sometimes
introducing
a
cpc
member
who
may
not
have
as
much
time
to
participate,
can
slow
things
down
and
kind
of
get
in
the
way
versus
helping.
Like
you
know,
we
should
make
sure
that
if
somebody
needs
help,
they
get
the
help,
but
by
forcing
them
to
be
like
there
to
be
a
cpc
person,
you
can
actually,
you
know,
be
a
drag
versus
help.
H
A
Yeah-
and
I'm
also
like
one
of
the
things
that's
sort
of
guiding
me
in
this
discussion
is
like
the
more
we
can
simplify
this.
I
think
the
better
you
know.
C
C
I
A
I
think
maybe
getting
rid
of
the
term
champion,
but
we
should
maybe
have
some
language
that
says.
If
you
propose
something
you
know,
I
you
need
to
be
able
and
willing
to
kind
of
help.
Work
through
that
process
is
that
accurate.
C
Yeah,
I
think
I
mean
the
the
existing
wording
is
not
terrible.
It's
like
what
I've
modified
a
little
bit,
but
it
could
be
like
before
landing.
It
needs
to
have
an
identified
champion.
This
could
be
anybody
who
would
be
pushing
the
proposal
to
its
conclusion
yeah.
So
you
can
open
a
pr
that
says:
hey.
You
should
do
this,
but
before
we
actually
say
this
is
an
incubating
proposal,
you
know
somebody's
identified
as
the
person
who's
actually
going
to
move
it
forward.
H
That
does
set
up
a
a
consideration
in
if,
if
we
do
allow
proposals
to
be
coming
in
with
champions
effectively
outside
our
relatively
small
community,
then
what
if
that
champion
just
goes
silent?
I
think
we
ought
to
have
language
somewhere.
That
has
some
number
of
weeks
or
months
of
inactivity
being
a
being
followed
by
effectively
dropping
a
proposal
due
to
an
activity.
A
Sure
we
can,
we
can
add
a
little
language.
I
think
around
that
you
know
just
perhaps
it's
like
sort
of
after
these
details.
Just
a
couple
of
notes.
You
know:
stale
stale
proposals
will
be
closed.
Those
kinds
of
things
just
a
heads
up.
We
have
12
minutes
and
I
think
you
know
we've
got
some
concrete
thoughts
here
that
I
think
we
can
have
in
a
pr.
A
A
So
two
phases
incubating
and
ready
for
review,
slash
approval
and
I
guess
we
should
just
be
ready
for
approval
and
is
it?
Is
it
clear
in
your
text
there,
michael
that
approval
is
like
cpc
and
potentially
board
review
right?
Let
me
see.
A
Okay,
next
item
on
the
list
here
is
that
the
incubating
proposal
process
can
have
as
many
prs
as
desired
each
essentially
providing
something
like
a
snapshot.
C
A
C
Make
sense?
Okay,
so
this
is
tasty
sure
yeah.
A
A
Sorry,
the
next
one
is
the
the
ready
for
review
or
approval
phase.
Is
you
know,
moving
the
files
into
place
right?
Okay,
I
think
again
that
could
just
go
at
the
end.
A
We
can
kind
of
work
the
wording
in
the
pr
itself.
A
I
don't
know
if
we
need
stage
three
complete
right.
No,
I
just
hadn't
deleted
that
yet
yeah
yeah
and
I'm
don't
mind
me
michael
I'm
kind
of
talking
out
loud
as
you
as
you're
right.
We
have
nine
minutes.
I
think
we
could
the
idea
of
a
definition
of
done
or
checklist
of
sorts.
Maybe
we
can
iterate
that
idea
in
the
pull
request.
A
I
mean,
I
guess.
If
we
have
time
we
can
talk
about
it
more
now,
but
that's
the
last
bullet
on
the
list
that
I
had.
A
I
think
sarah,
maybe
jordan.
I
can't
remember
who
had
mentioned
that
thought
in
the
last
meeting
the
definition
of
done
idea.
A
Either
way:
well,
we
can.
We
can
I'm
not
sure
what
that
would
would
look
like
in
in
a
generic
sort
of
way.
A
But
it's
something
we
can
we
can
think
about.
I
guess.
H
Is
there
a
need
for
for
us
to
have
a
stage
or
something
sort
of
after
after
a
proposal
is
accepted,
but
before
for
the
actual
implementation
of
whatever
that
proposal
is
about
before
it's?
Actually,
you
know
up
and
running
and
done.
Some
proposals
certainly
would
be
just
a
decision,
and
then
you
know
that
it's
been
decided.
H
H
C
I'm
more
like
once
it's
landed,
it
should
be
done
like
and
hopefully
the
landing
of
it
can
can
like
move.
So,
for
example,
for
the
collaboration
network,
there
were
changes
to
the
the
the
governance,
so
you
know
those
those
were
done
at
the
same
time.
C
A
Yeah,
I
think,
and
I
think,
like
sarah's
work
on
the
supporter
program,
you
know
there's
a
lot,
that's
kind
of
going
into
that,
including
you
know,
design
and
assets
and
stuff.
So
that's
all
kind
of
still
a
part
of
the
process.
I
think,
but
I
could
see
how
some
of
that
even
would
be.
You
know,
could
potentially
be
well
that's
phase.
Two
we've
landed
this
now,
let's
you
know
continue
implementing
it,
but
you
know
the
work
will
still
need
to
go
on.
A
The
other
thought
I
had
is
are:
how
are
we
capturing
like
essentially
approved
proposals?
Do
we
do
we
capture
those
and
keep
them
in
a
directory
that
you
know
to
kind
of
show
the
things
that
have
gone
through
the
process
or
is
that
something
we
care
about?.
F
Yeah,
I
think
that's
important,
I
think.
Well,
I
I
think
it's
helpful
for
people
to
see
what's
made
it
through.
C
Right,
so
I
think,
though
we
can
just
like
there
was
a
directory
where
we
had
the
different
stages.
If
we
just
have
like
an
approved
directory
and
your
pr
will
move
some
of
the
artifacts
out
of
that
out
of
the
proposal
into
the
main
place,
but
the
the
sort
of
outline
the
first
outline
that
says
what
it
is,
could
still
end
up
there
in
the
approved
section.
C
D
C
J
A
Yes,
we
may
want
to
even
as
a
follow-on
pr
or
maybe
even
a
pre.
You
know
before
landing
the
work
that
you're
doing.
I
mean
I
guess
it
doesn't
matter,
but
I'm
looking
at
the
way
the
proposals
directory
is
currently
set
up
and
there
is
stage
zero
stage.
One
stage
two
so
we
may
want
to.
A
So
if
you
think
of
it,
when
you
commit
this,
you
could
just
add
a
note
to
say:
take
a
look
at
the
directory
structure
in
the
proposals
directory
to
align
with
this
work.
C
C
A
F
F
A
I
think
he's
got
some
shepherd
in
him
too,
because
he
bites
his
sister's
ankles
and
tries
to
like
kind
of
hurt
her
and
you
know
yeah
exactly
you
guys.
I'm
talking
about
you
great
all,
right,
cool,
well,
good
work,
everybody
good
meeting.
I
appreciate
everybody's
time
and
energy
and
I
look
forward
to
doing
it
again
soon.