►
From YouTube: 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
A
Do
we
have
any
any
announcements
folks
want
to
share
from
their
projects
this
week
or
from
the
foundation
robin's
nodding.
B
Let's
go,
I
have
a
great
announcement.
We
have
the
joy
of
welcoming
alex
robinson
to
the
team
she's,
our
new
head
of
marketing
and
communication
alex.
You
want
to
give
a
quick.
C
Intro
yeah
thanks
robin
yeah,
so
my
first
day
was
last
week
last
wednesday
december
1st
and
I'm
very
excited
to
be
here
still
getting
to
know
the
project
and
everybody
that's
involved
with
it.
I
was
previously
at
synopsis
doing
marketing
communications
there
for
several
years,
so
I'm
really
happy
to
be
here.
I'm
excited
to
be
part
of
you
know
the
linux
foundation
and
also
just
open
source
helping
to
expand
our
projects.
C
B
A
A
We
do
have
a
programming
committee
meeting
this
this
thursday
for
those
in
interested
in
getting
involved
in
open,
js
world
planning,
which
is
really
coming
along
in
an
exciting
way.
So
join
us
thursday,
if
you
can
for
that.
So
those
are
some
upcoming
community
meetings
and
things
to
to
attend
to
if
you're
interested.
A
A
All
right
board
meeting
updates
mr
dawson.
D
B
Is
today
the
last
day
for
the
certification,
it
is
the
last
day
for
the
certification
cyber
monday
offer
it
the
lf
extended
it
an
extra
day.
It
was
supposed
to
end
yesterday,
so
I
put
out
a
quick
notice
yesterday
and
just
the
other
thing
we're
still
on
track
with
our
event
in
june
and
austin,
a
lot
of
questions
coming
in
with
the
new
variant
and
things
like
that,
but
we're
still
monitoring
the
situation,
but
still
moving
ahead
as
planned.
A
D
We
have
the
right
licenses
in
you
know
when
we
create
the
repo
and
do
we
continue
to
make
sure
that,
like
we
don't
add
stuff
in
there-
and
I
suspect
this
is
a
problem
that,
like
any
project
that
has
more
than
a
few
repos,
is
going
to
have
an
issue,
and
so
it
seemed
to
me
like
a
common
thing
that,
like
I
don't
know
if
the
linux
foundation
already
has
some
tools
to
help
with,
but
it
seemed
like
it
was
worth
bringing
up
to
see
if
there's
like
a
common
solution,
certainly
in
terms
of
like
helping
our
projects,
I
think
it
would
be
useful
for
us
to
have
a
standard
solution
that,
like
could
scan
and
give
us.
D
A
So
speak
to
like
the
lf
tooling,
there
is
a
license
check
component
to
the
new
security
platform
that
they
they
released.
I
think
we
do
need
to
get
projects
who
are
interested
and
set
up
so
that
the
lf
bot
can
go
go.
Do
that
it's
the
way
it
works
is
through
adding
a
adding
a
bot.
Everything
adds
a
blob
these
days
to
your
org,
so
that
that
it
will
check
and
and
scan
those.
So
we
can
certainly
do
do
that.
A
I
know
the
js
foundation
had
several
projects
on
fossa
for
a
while,
but
I'm
not
sure
how
you
know
how
how
many
people
are
still
using
that.
So
that's
another
one
that
that
foss
also
works
with
many
lf
projects.
That's
one
we
could
probably
also
bring
in
two.
So
those
are
two
that
I'm
I'm
aware
of
right
now.
F
Mean
I
I
I
don't
think
I've
particularly
talked
about
this
publicly,
but
I'm
relatively
against
fossa.
I
don't
think
that
information
should
be
behind
a
corporation
and
like
that
tooling
should
be
available,
and
I
I
would
hope
that
we
would
go
with
tooling.
That
is
either
from
lf
or
external
community
stuff,
rather
than
kind
of
being
a
you
know,
I
I
would
prefer
node
not
like
you
know
in
the
case
of
node,
or
you
know
the
case
of
electron.
I
would
prefer
us
not
to
you
know,
give
them.
F
You
know
our
logo
to
promote
their
product
in,
because
we're
getting
licensing
information
from
them
that
does
not
link
should
not
be
paid
so
yeah.
That's
you
know,
at
least
from
the
projects
I
I
participate
in.
I
would
definitely
push
against
fossa
for
that
reasoning.
F
A
So
the
lfx
security
platform
is
not
not
part
of.
Oh,
it's
not
part
of
open
ssf.
It's
there's
it
they're
working
on
things
in
collaboration
with
the
openssf,
but
it
is
in
fact
separate.
There's
an
additional
tool
that
I
just
that
is
a
project
in
the
linux
foundation
called
the
open
source
review
tool
kit,
which
I
popped
into
the
the
chat
for
us
I'll
pop
it
into
the
notes
as
well.
A
It's
more
of
an
open
source
like
licensed
policy
compliance
tool,
application
for
for
for
companies
mostly,
but
I
could
see
that
also
being
potentially
and
useful
and
it's
it
is
open
source.
A
A
D
I
I
don't
mind
the
here's
several.
I
guess
you
know
if
the
lfx
is
building
something.
I
assume
it's
because
there's
not
something
easy
to
use
across
this
use
case
or.
G
G
I'd
have
to
track
it
down,
but
I
think
that
the
the
thing
that
we
as
the
foundation
should
be
providing,
I
hope
for
users
is
here,
is
one
or
more
easy
ways
to
figure
out
what
the
actionable
things
are
for
you
on
your
project
and
why
and
whatever
that
means
like
that's
where
we
can
figure
out
and
debate
the
implementation
details
but
like
like
as
it
relates
to
does
your
project
have
a
license
and
is
it
a
license
that
most
companies
are
cool
with
and
like?
G
What
are
the
reasons
why
the
license
you
have
is
unadvisable
and
so
on
and
so
forth?
Right
like
we
need
something
that
that's
easy,
not
like,
both
for
I'm
a
company,
and
I
want
to
evaluate
my
internal
stuff
and
and
the
things
I'm
using
and
also
I'm
an
open
source
maintainer.
G
I
want
to
evaluate
the
things
I
make
and
also
I'm
an
open
source
consumer.
I
want
to
evaluate
the
things
I'm
about
to
use
and
I
don't
believe,
there's
a
good
solution
for
perhaps
all
of
those
things
or
all
of
those
groups
at
the
moment,
but
certainly.
D
D
D
We
forgot
to
do
this
over
here,
or
do
we
forgot
to
do
this
over
there
right
and
so
whatever
you
know,
whatever
the
easiest
way
to
do
that,
if
it's
like
you
know
a
bot
that
gets
added
to
every
every
you
know
to
a
repo
as
it
gets
created
or
whatever
that
doesn't
sound
too
hard,
so
I'd
say
like
if
you
can
put
some
information
on
a
few
of
those
into
the
issue
like
you
know.
D
D
A
Yeah
and
if
shobi
has
their
hand
raised,
and
I
will
I'll
send
you
guys
in
chat
a
link
to
the
tool
as
it
is
now,
but
toby
go
right
ahead.
H
Yeah,
I
must
admit
that
I
wasn't
paying
100
attention
to
the
conversation.
So
if
I'm
repeating
a
point,
please
just
wave
your
hand
and
I'll
shut
up.
I
was
wondering
if
there
was,
we
had
discussed
separation
between
actually
figuring
out
what
the
licenses
in
the
repo
is
versus.
D
I'd
agree
like
the
dependencies,
especially
dependencies
that
aren't
in
the
repo
I'm
not
as
worried
about
right,
like
that's
the
next
layer
of
like.
Are
you
depending
on
compatible
things?
The
first
part
is
just
like:
what's
in
our
repo
does
do
have
we
have
we
said,
there's
a
license
because,
like
I
come
across
ones
where
it's
like?
Oh,
we
didn't
even
add
a
license
file.
Right
so
did
we
add
a
license,
sometimes
we're
transferring
ones
and
they
come
with
a
license.
So
it's
like
okay,
so
it's
like.
Do
we
have
one?
D
Does
it
meet
what
we
said
we
should
have
and
then,
if
it
has
any
extra
smarts
to
try
and
search
within
that
repo
to
say
like?
Is
there
anything
outside
of
that
because
sometimes,
like
you
end
up
with
hey
we're
mit
but
somewhere
buried
down
in
in
something
you've
pulled
in,
it's
got
something
else
like.
D
D
It's
still
a
concern
like
they're.
It
part
of
what
made
me
think
about
this
again
is
there
was
like
a
pr
that
was
like
hey.
Let's
add
this
in
and
I'm
like
wait
a
sec
there's
a
reference
to
gpl
in
here.
Is
that
okay,
you
know
so
even
in
other
repos.
I
think
it's.
If
I
wouldn't.
I
wouldn't
make
that
a
blocker,
but
like
that's
sort
of
like
the
nice
to
have
the
very
first
thing
is
just
like
hey
did
we
have
do
we
have
a
license?
Do
we
is
it?
D
A
Yeah,
that
makes
sense,
and-
and
I
I
like
kind
of
the
focus
on
like
solve,
solve
sort
of
the
top
level
problem
and
then
kind
of
drill
down
into
the
more
tricky
nuance
problems
which
are
you
know,
licenses
and
package
dependencies
and
that
sort
of
thing.
H
Yeah,
do
we
have
in
open
gsf
projects
the
ability
to
have
to
know
all
of
the
orgs
and
all
the
projects
like?
Do
we
have
like
links
to
all
of
those
somewhere.
A
Yeah,
I
don't
know
if
we
have
them
like
super
accessible.
Like
I
mean
we
certainly
do
have
staff.
I
don't
know
if
we
can,
because.
H
H
Orgs
that
oil
aleph
sorry
open,
gsf
members
and
the
list
of
that
than
actually
writing
a
script
that
iterates
through
that
api
and
gets
the
licensing
for
all
of
the
repositories.
So
we
can.
What
I'm
saying
is
the
first
thing
is
really
easy
to
answer.
If
we
have
all
of
that
information,
and
so
maybe
we
should
start
there
and
see
what
that
looks
like.
A
Yep
yeah,
we
can
do
that
there's
we
have
have
access
to
yeah.
To
do
that.
I
think
that's
a
good
idea.
H
F
H
B
D
To
toby's
point,
I
think
it
would
be
really
handy
somewhere
if
we
had
like
a
jason
file
that
actually
had
all
the
repos,
because
that
would
be
a
very
easily
parsable
thing
and
then,
as
we
brought
in
a
new
project,
it
would
be
like.
Okay,
here's
the
org,
you
part
of
it
is
like
you,
pr
in
your
org
or
something
to
there,
not
maybe
not
the
repos,
because
those
could
change
a
fair
amount.
But
like
here's,
the
orgs
that
you
that
are
listed
for
each
of
the
projects.
D
D
D
But
so
I'd
start
with
the
public
ones.
Just
from
this
ease.
F
I
Okay,
implicitly,
thereby
creating
an
api
for
getting
all
of
the
repositories
of
the
openjs
foundation,
is
actually
not
a
bad
idea
by
itself
either.
A
Yeah,
I
think,
there's
a
there's,
probably
a
couple
ways:
we
can
automate
that
we
could
use
landscape
for
that.
We
could
there's
a
couple.
I
think
a
couple
options.
It
sounds
like
actions
on
this
particular
issue
for
today,
let's
go
see
per
chance
if
the
lf
well,
first
off,
let's
make
sure
the
lfx,
like
security
platform,
actually
potentially
solves
the
the
problem.
If
so,
that's
a
super
easy
fix.
If
not,
we
will
look
into
something
else.
A
We
will
also
create
a
a
space
to
record,
either
through
automation
or
potentially
temporarily
through
manual
pr,
a
list
of
all
of
the
repos,
so
that
or
organization.
Sorry,
so
that
some
enterprising
script
kid
can
write
something
for
us
to
pull
or
check
repos
in
those
orgs
and
we
will
also
go.
I
can
do
a
quick
review
too,
of
all
of
the
from
the
other
lfpms.
If
there's
favored
license
review
tools
beyond
these
that
I've
shared
today
cause
I'm
sure.
I
A
So
most
of
the-
I
think
not
not
just
most,
I
think
all
of
the
projects
at
this
point
have
added
there's
a
an
account
that
is
held
by
openjs
staff
for
the
purposes
of
redundancy
and
occasional
support,
if
they're,
using
a
tool
like
the
easy
cla
and
that
that
user
account
has
is
a
member
of
the
orgs.
So
what
I
would
have
done,
or
was
thinking
about
here,
was
saying.
Okay,
let
me
go
query.
A
This
user
account,
which
orgs
is
it
does
it
belong
to?
It,
belongs
to
you,
know,
jquery
and
node
and
dojo,
and
that
kind
of
thing
and
it
would
be
able
to
so
that's
that's
one
way
and
most
of
the
projects
do
elect
to
add
the
account
to
their
orgs
when
they
onboard.
A
All
righty
cool
good
discussion.
I
like
that.
I
like
it
a
lot
because
you
know
it
really
does
segway
too
and
and
and
sorry
support.
Other
conversations
we're
having
around
like
just
being
more
apparent
about
what
tools
and
benefits
and
things
we
have
for
projects.
So
great
all
right.
Next
issue,
number
789
is
start
listing
documents
maintained
by
the
cpc.
A
A
A
Yep,
this
is
kind
of
related
to
some
other
questions
and
feedback.
We've
gotten
about
just
the
fact
that
we've
added
a
lot
of
documentation
to
our
cpc
repository
and
it's
getting
a
bit
hard
to
read
and
find
so,
I
think,
just
general,
a
general
pr
to
help
clean
up
would
probably
be
welcomed
by
the
community.
If
somebody
wanted
to
do
some
digital
filing
for
us,
you
know
that'd
be
great.
That
was
one
of
my
first
jobs
was
filing
like
after
school.
A
I'd
go
to
this
office
and
file
paperwork
so
anyway,
if
you
want
to
do
that,
but
with
github
markdown
files
that'd
be
great.
D
A
That's
true,
you
know
I
I'll
be
candid
and
say
I'm
not
gonna
be
picky.
If
somebody
has
a
particular,
you
know
vision
for
how
might
be
more
readable,
more
consumable
for
the
community.
A
It's
certainly
going
to
be
better
than
what
it
is
now.
So
you
know
suggestions,
warmly
welcomed.
If
you
feel
you
know,
you
have
a
vision
for
how
to
organize
it,
then,
if
not,
I
could
make
something
up,
but.
H
A
So
I
think
we've
had
a
couple
of
actually
ben
from
jason.
Schema
was
one
who
brought
brought
it
up
a
couple
of
few
other
people
too
yeah.
So.
H
A
Had
a
strong
like
you
know,
it
should
look
like
this
instead,
just
more
that,
like
hey,
you
know,
thanks
for
the
link,
I
find
it
hard
to
find
things
here
and
I'm
too,
which
I
say
you
are
not
wrong.
It
is
hard
to
find
things
here.
So
you
know,
I
guess
that's
that's.
Maybe
another
call
like
call
for
input
requested
if
there's
any
like
strong
ideas
for
how
to
organize
it.
A
A
One
thing
that
michael
dawson
and
I
had
come
up
with
last
week
was:
maybe
we
should
pull
some
of
like
the
travel
fund
and
some
of
those
things
related
to
that
type
of
activity.
So
those
who
are
looking
for
information
about
how
to
take
take
advantage
of
the
travel
or
the
scholarship
or
sponsorship
sort
of
policies
that
we
have.
Maybe
that
goes
out
into
its
own
separate
repository,
called
community
fund,
and
we
start
to
kind
of
think
about
these
bigger
programs
having
their
own.
A
D
Yeah,
I
think
that
was
the
working
session
last
week,
where
we
sort
of
looked
at
a
little
bit
with
the
structure
but
yeah.
I
think
I
think
it
might
be
easier
to
have
multiple
starting
points
where
it's
like
I'm
interested
in
the
community
fund.
Okay,
here's
all
the
stuff
related
to
that
versus
a
whole
bunch
of
things
at
the
top
level
of
the
cpc
repo.
H
Yeah
it
feels
like
we
need
an
entry
point
and
yeah,
maybe
to
read
me
as
that
entry
point,
that's
sort
of
what
it
was.
That's
the
assumption
I
made
when
I
was
adding
stuff
to
it.
Maybe
we
could
also
imagine
having
the
readme
or
part
of
the
readme
or
something
of
that
nature
on
the
website
itself
and
then
use
that
as
an
entry
point
to
the
different
points.
I
don't
know
it's
worth
thinking
about
it
because
it
is
kind
of
messy.
I
do
agree.
D
A
And
yeah,
I
think,
it'd
be
it'd,
be
great.
To
also
add
this
to
the
site.
We
could
probably
very
easily
create
a
info
page
on
the
openjs
website
that
helps
people
just
get
a
quick
little
glimpse
of
what
each
program
is
and
then
drops
them
more
directly
into
the
documentation.
For
that.
So
I
think
that's
a
great
suggestion.
This
feels
like
we're
getting
ready
to
do
some
like
spring
cleaning
on
our
repos
and
I'm
like
weirdly
excited
about
that
so
yeah
I
mean.
B
Doesn't
say,
I
don't
think
we
need
to
boil
the
ocean
when
I
was
doing
an
auditive
code
of
conduct.
Some
were
so
obviously
easy
to
find
and
some
I
had
to
click
three
places
and
try
to
be
intuitive,
but
maybe
we
just
start
by
doing
instead
of
trying
to
organize
clean
your
entire
bedroom
at
once.
Let's
start
with
the
books
and
then
start
with
this
and
the
toys
just
do
it
little
by
little.
A
Well,
that's
that's
exactly
how
I
clean
my
house
is
it's
like
real
the
ocean
style,
so
you.
B
Yeah
exactly
so,
maybe
if
we
start
with
the
community
fund-
and
we
start
with
the
you
know-
the
code
of
conduct
make
that
easy
to
find
and
then
just
sort
of
piecemeal
the
organization.
Instead
of
trying
to
re.
A
A
I
think
that's
fair,
there's
a
second
kind
of
stepping
a
little
further
into
sort
of
the
topics
of
the
working
session,
which
is
last
two
sessions
that
we've
done
have
been
the
community
fund
and
then
previously
the
the
tech
strategy,
and,
I
think,
there's
also
a
desire
which
was
shared
with
you
all
as
well.
To
pull
some
of
the
tech
strategy
conversation
pieces
into
a
separate
repository
as
well,
and
that
might
help
quite
a
bit.
D
H
I
mean
I
don't
want
to
drag
this
conversation
on
too
much.
Could
we
maybe
like
two
things
one
can
we
could?
H
We
have
a
workshop
session
on
this
thing
to
figure
out
how
we
want
to
organize
stuff,
and
the
second
thing
I
do
want
to
say
is:
you
know,
there's
this
huge
tension
in
the
in
computing
between
model
repos
and
like
yeah,
to
put
it
like
very
sort
of
very
broadly
moderates
and
sort
of
micro
services,
and
we
want
to
watch
out
not
to
move
from
like
having
everything
in
the
same
place,
which
has
issues
to
have
like
a
whole
bunch
of
representation.
H
It's
actually
just
hard
to
find
the
stuff
just
because
there's
it
can
be
like
so
many
different
places,
and
we
might
want
to
do
a
tiny
bit
of
information
architecture
here,
just
like
figure
out
like
the
four
five
six,
like
big
cases
that
people
have
to
come
see.
What's
you
know
what
the
cpc
does
like
join?
I
don't
know
like
upgrade,
be
a
like
the
elections
and,
like
you
know,
the
two
or
three
other
things,
and
maybe
sort
of
like
have
a
landing
page
for
those.
H
A
I
think
that's
a
fair
point
and
toby.
I
hadn't
really
thought
about
that
and
I
do
feel
like
something
like
the
community
fund,
where
you
know
that's,
there's
some
complex
steps
involved,
potentially
with
like
how
you
get
approval
to
attend
a
thing
or
how
you
get
exp,
how
you
how
you
leverage
that
and
and
we're
talking
about,
also
the
community's
ability
to
direct
funds
to
certain
things
that
probably
does
deserve
its
own
repo.
But
to
your
point.
E
H
I
mean
essentially,
I
I
heard
sort
of
you
jerry
say
I
boiled
the
ocean
and
I
cleaned
up,
and
I
heard
robin
say
I
start
by
one
place
and
I
kind
of
like
spent
my
life
alternating
between
one
or
the
other
and,
like
you
know,
there's
some.
There
was
room
in
the
middle
which
would
like
yeah
a
calmer
thing
to
do.
I
think
that
was
my
point.
B
A
Yeah,
let's,
let's
do
a
working
session
in
the
new
year.
I
guess
about
housekeeping
in
a
way
and
we'll
put
that
on
on
the
agenda.
The
next
item
is
well.
I
guess
we
we
I've
completed
an
item.
They
create
proposals
for
community
fund.
Michael,
do
you
want
to
summarize
kind
of
our
progress
from
the
meeting
last
week.
D
D
How
do
we
sort
of
break
this
down
in
terms
of
you
know
again,
if
we
had
say
a
separate
repo
for
it?
What
would
that
repo
look
like,
and
you
know
we
kind
of,
were
you
know
looking
at
the
beginning
where
it's
like
okay
about
the
community
fund?
Well,
it's
broken
down
into
these
different
categories,
so
travel
scholarships.
D
D
D
D
For
each
of
those,
though
you
know
they
they
might
have
come,
and
they
there
were
common,
think
questions
that
needed
to
be
answered
like
eligibility
criteria,
how
you
know
the
guesstimate
of
how
much
we
were
putting
into
that
bucket,
how
you
would
apply
and
who
would
the
approvers
would
be
so
we
could
see
then
breaking
it
down
based
on
on
that
and
then
you
know
recur.
D
D
A
Oh,
are
you
one
of
our
standards?
Wonks
and
you
want
to
you
know,
take
it
take
advantage
of
the
fund
to
go
to
a
meeting.
Here's
here's!
How
are
you
a
node
collaborator?
Here's?
How
are
you
looking
for
other
kinds
of
support?
So
I
think
one
of
those
goals
is
just
like
better
memorializing
the
process
that
we
have
in
a
consumable
way.
A
A
So
that's
where
we
got
last
week
at
that
working
session
and-
and
I
think
one
of
the
other
things
we'll
do
is
close-
the
issue-
that
kind
of
sparked
this
discussion,
close
close
756
in
favor
of
creating
separate
issues
to
document
the
these
specific
programs.
And
that's
that's
that's
where
we're
at
with
that.
A
Cool
all
right,
the
next
topic
in
our
agenda
today
is
number
seven
or
632
around
the
the
dc
ocla.
I
think
I
gave
a
brief
update
on
this
last
week
about
the
that
probot
dco,
being
something
we're
going
to
that
the
lfit
is
going
to
be
bringing
in
don't
have
any
further
update
beyond
that.
A
But
there
are
some
some
actions.
I
would
maybe
propose
that
we
remove
the
cpc
agenda
label
from
this
one
for
a
while,
because
we're
no
doubt
going
to
get
internally
at
the
lfa
notification
when
this
is
ready-
or
this
has
been
brought
further
into
the
house,
but
then
we
can
stop
looking
at
it
longingly
every
week.
E
A
Okay
cool
all
right?
Well,
I
will
remove
the
remove
this
label
from
that
for
now,
and
we
can
add
the
other.
A
Cool
all
right
so
next
week,
working
session
is
on
tech
strategy.
It
is
the
last
meeting
of
the
year
wow.
So
that's
the
14th
we'll
be
continuing
that
conversation.
A
If
you're
interested
in
joining,
we
hope
to
see
you
there
that
will
build
on
documentation,
work
that
we've
started
in
in
previous
working
group
meetings
and
build
on
some
of
the
stuff
that
michael
and
I
sent
around
to
you
all
so
join
us.
If
you
like,
we
have
a
new
issue
open
for
the
2022
cpc
meeting
schedule,
which
is
issue
816
and
it's
pinned
to
the
top
of
the
repo.
A
So
if
you
want
to
go,
take
a
look
at
you
know
at
that
and
start
to
think
about
working
sessions
to
propose
throughout
the
year
there
please
feel
free.
Well,
it
also
is
very
helpful
in
my
mind,
to
go
ahead
and
pre
pre-cancel
things,
for
example,
that
we
know
will
be
conflicts
with
the
event
or
a
holiday,
or
things
like
that,
so
that
that
issue
is
open
for
us,
so
we'll
do
a
spring
cleaning
working
session
at
let's.
A
Let's
do
that
our
first
working
meeting
of
the
year-
and
that
will
be
that
any
other
suggestions
for
working
group
working
meetings.
B
At
the
this
time,
no,
I
was
thinking
about
some
of
the
swag
and
the
store
proposals
we
have.
I
don't
think
we
need
a
meeting
on
that.
I
think
what
I'll
do
is,
send
it
via
email
and
get
your
all
input
that
way.
What
do
you
like?
What
you
don't
like,
but
essentially
we
can
set
up
a
store,
is
an
easy
way
to
implement
a
thank
you
program
or
a
way
to
support
community
meetups
and
things
like
that
around
the
world.
D
B
On
the
on
the
non-profits
for
contributing,
we
don't,
although
our
dei
working
group,
sonal
and
sarah
chips
and
I
had
a
short
list
of
organizations
we
like
so
maybe
that's
a
good
starting
place.
D
Yeah,
I
just
you
know
for
me:
I
think
the
the
more
we
can
make
it
less
about
I
you
know
I
got
something
and
that
something
cost
fifty
dollars
to
ship,
and
you
know
the
the
thank
you
and
and
something
of
value
going
somewhere
good
that
the
better
so
just
want
to
make
sure
we
have
those
options.
That's
all.
E
A
All
right
that
kind
of
pulls
us
to
the
end
of
our
agent.
Is
there
any
other
business
today,
any
any
anything
anybody
wants
to
raise
before
we
conclude
okay?
Well,
if
I
don't
see
you
again
this
year,
thank
you.
It's
been
a
pleasure
great
work
this
year.