►
From YouTube: Community Development: CDIPs Final Report
Description
Tim Black walks through Community Development Initiative Proposals (CDIPs) recap and shares successes and takeaways from the program.
Community Projects: https://community-development.makerdao.com/en/funding/community-projects
A
All
right,
so
here
we
are
in
community
development,
talking
about
c-dips
sort
of
a
final
report.
We
were
in
this
call
just
a
little
bit
before
saying
that
this
is
part
of
our
archiving
efforts,
so
hopefully
we'll
put
this
up
on
youtube
and
I'll.
Add
it
to
the
github
issue
to
explain
this
whole
journey
we've
been
through,
and
so
as
a
refresher
for
most
people.
Here
you
know,
but
for
other
folks
randomly
on
the
youtubes
hello,
I'm
tim
one
of
the
folks
in
community
development.
A
It
was
meant
to
be
a
flexible
tool
and
it
was
a
way
to
introduce
a
new
initiative
or
expand
the
scope
of
existing
initiatives
within
community
development,
and
they
worked
well
as
a
catch-all
for
projects
that
aren't
quite
at
the
scale
of
grants,
which
was
a
much
more
robust
process
which,
as
of
monday,
we
announced
that
that
program
is
now
sunset
and
they
also
worked
really
well
for
people
who
didn't
have
a
lot
of
time
to
commit,
but
had
a
pretty
good
plan.
To
just
put
these
milestones
up
in
this
format.
A
Documentation
will
be
on
our
github
issue,
but
they're
also
here
within
this
presentation,
for
the
simple
doc
template
the
way
we
make
decisions
about
them.
What
to
expect
for
the
different
stages
and
then
the
pages
within
our
community
development
portal
about
cdips
at
a
high
level
what
they
did
and
what
they
didn't
do
is
right.
Here
they
were
there
to
scope,
small
projects
from
beginning
to
end
with
just
a
nice
light
structure
or
break
up
a
large
project.
A
As
I
mentioned
into
more
digestible,
time-bound
chunks,
the
heuristic
was
about
5k,
as
the
upper
budget
before
it
seemed
to
be.
People's
ideas
are
a
little
bit
too
ambitious
and
should
be
in
the
grants
framework,
but
we
were
pretty
flexible
with
that.
We
iterated
a
lot
and
we'll
get
into
those
highlights
as
we
go
now.
A
What
c-dips
were
not
supposed
to
do
was
fund
existing
projects
or
fun
finished
work
or
serve
as
a
money
tree
so
yeah,
that's
not
our
jam,
so
some
highlights,
which
are
always
the
fun
part,
the
stats
we
actually
evaluated,
41,
total
c
dips.
We
completed
28
of
them.
There
are
two
that
are
still
running:
the
lattem
die
action
groups
and
kevin
is
working
on
a
set
of
merchant
pages
or
a
qr
code
generator.
A
We
ended
up
pausing,
archiving
voiding
or
replacing,
or
stopping
basically
11
of
them.
We
had
28
people
who
proposed
cdips
and
eight
people
who
proposed
themselves
as
advisors,
although
it
ended
up
being
about
five
who
really
were
like
the
full-time
advisor
people
we'll
get
into
those
roles,
as
we
continue
the
average
time
to
complete
these
was
two
months.
I
thought
it
was
longer
last
time
I
did
the
data,
but
it
ended
up
being
two
our
average
time
to
approve.
A
One
of
these
is
about
three
weeks
and
the
program
lifetime
ran
for
a
year
and
there
were
four
extensions:
the
transparency
dashboard,
the
badges
on
the
maker
file
forum,
the
latim
die
action
groups
aforementioned
and
the
marketing
team
used
a
bunch
of
c
dips
to
scope
together,
a
large
launch
for
our
community
portal
and
so
more
more
cool
stuff
or
some
impact.
Some
delivery
highlights
again
41
things
can't
progress
in
one
slide,
but
we
had
292
badge
redemptions.
We
had
a
demo
day,
which
is
on
our
youtube
channel.
A
You
can
find
that
for
all
of
the
cool
stuff
that
we
were
building
at
the
same
time,
lisa
one
of
our
contributors,
who
is
not
here
at
the
moment,
but
could
come
back
at
any
time,
did
an
amazing
presentation
about
user
personas
and
some
research
for
our
community
portal.
Kevin's
directory
page,
the
voices
of
the
dow
podcast
launched,
there's,
there's
all
sorts
of
magical
things.
We
did
the
funds,
I
know.
Probably
some
of
us
are
giggling
to
ourselves,
but
running
the
numbers,
93k
or
so
was
requested
and
about
70k
was
dispersed.
A
Most
of
the
thing
is
that
people
were
pretty
ambitious,
so
a
lot
of
ideas
started
as
an
initiative
and
that
just
kept
growing
because
we
have
some
smart
folks,
so
I'd
like
to
put
a
spotlight
on
the
lattam
die
action
groups
for
a
second
because
they've,
you
know
they
were
above
that
5k
heuristic
cap
and
they've
done
a
few
of
these
now.
So
some
stats
on
these
guys
is
that
they
operate
in
three
countries:
brazil,
colombia
and
venezuela.
They
have
seven
unique
contributors.
64
pieces
of
content
have
been
produced.
A
They
have
twitter
followers
of
almost
1
500
telegram.
Members
of
almost
1
500.
they've
started
growing.
A
p2p
marketplace
for
low
fee
die,
transfers
using
x,
die,
die
and
little
hacking
on
the
exchange
that
shall
be
not
named,
which
is
like
really
cool
and
their
memes
are
fire,
so
shout
out
to
the
latdam
die
action
groups
and
their
advisor
david
for
basically
hacking
the
c
dip
framework
and
doing
something
really
really
cool
making
making
maker
dell
global
good
job.
A
Guys
more
examples,
of
course
we
have
our
chief
happiness
officer,
st
bourbon,
who
proposed
the
swag
squad
and
has
actually
been
sending
out.
I
think
bespoke
welcome
packages
to
pretty
much
everyone
which
is
super
cool.
You
can
find
his
c
dip
as
like
with
all
of
these
on
our
cdf
issue.
There's
actually
just
a
tag
for
it.
A
I
don't
remember
another
thing:
scott
did
was
he
paired
with
josie
and
nas
and
aaron,
and
many
other
people
to
basically
get
our
badges
as
a
working
prototype
on
the
forum
which,
as
nas
sort
of
shared
the
later
vision
for
this
started,
to
enable
like
an
actual
reputation
system
for
people
who
act
in
governance,
which
is
pretty
cool,
exciting
to
see
where
those
go?
So
I
really
like
to
look
at
c
dips.
It's
basically
the
story
right.
Originally,
it
was
like
just
a
loose
process
framework.
A
To
just
add
a
plan
to
an
idea,
so
it's
not
just
like.
I
want
to
do
a
crazy
thing.
It
just
became.
I
want
to
do
a
thing:
here's
a
plan,
here's
a
budget.
They
grew
into
this
story
line
which
shout
out
to
amy,
for
that
mention
because
I
felt
like
that
was
best
framing
of
just
community
members
who
were
trying
these
new
growth
experiments
right
and
each
one
was
different
and
they
came
in
from
a
different
angle
and
they
brought
new
skills
and
new
ideas
to
comdab,
which
is
like
super
cool.
A
A
So
with
revisions
comes
lessons
and
with
running
a
program
for
a
year,
you're
not
going
to
do
it
perfectly.
I
think
maybe
I
tinkered
too
much,
but
we
learned
a
ton
which
is
super
valuable
first,
one,
as
I'm
sure
everyone's
kind
of
noticing
is
that
settlement
by
committee
is
difficult.
When
you
have
five
or
six
opinions,
it's
like
really
tough
to
get
alignment,
but
it's
a
valuable
thing
to
do.
A
Another
thing
is,
we
could
have,
but
we
didn't
announce
to
the
governance
group
or
sort
of
telegraph
for
new
ideas
would
have
maybe
been
a
better
thing
to
have
done
like
a
a
monthly
here's,
the
cdip's
update
or
produced
something
on
the
forum
that
was
more
like
hey.
We
want
your
ideas
too
you're
part
of
our
community.
On
that
note,
another
thing,
probably
more.
My
fault
than
anybody
else
is
that
the
advisor
roll
these
swimming
lanes-
we
just
showed
you,
the
yellow
in
the
middle.
A
You
can
see
shuffled
back
and
forth
between
the
two
other
swimming
lanes,
and
so,
as
a
result,
they
by
accident,
started
playing
telephone
all
the
time.
It
would
go
to
someone
with
an
idea
and
try
and
frame
and
form.
It
then
go
to
the
committee
to
talk
to
them,
and
then
they
would
take
things
back
when
realistically,
we
could
have
just
opened
up
a
little
bit
more
and
had
maybe
a
better
cadence
on
that.
But
again
we
learned
that
over
time.
A
You
know
on
that
note:
cdips
are
for
ideas
right,
so
they
needed
space
for
iteration.
I
think
about
a
month
or
two
ago,
someone
had
great
feedback
about
just
opening
up
15
minutes
in
our
weekly
sink
to
free
up
ideas
before
they
become
a
seed
epper
before
they
become
a
grant
or
before
they
go
and
join
another
team,
and
it
would
have
been
nice
to
have
designed
for
that
in
the
beginning.
A
But
again
it's
one
of
those
lessons
you
learn
so
anything
where
you
have
a
chance
to
meet
with
folks
who
are
going
to
approve
or
vote
or
decide
on
whatever
your
idea
is
before
it
goes
through.
That
process
would
have
been
helpful
and
so
lesson
learned,
which
is
super
cool.
The
other
thing
that's
tough,
as
I
mentioned.
I
see
this
in
the
dow
as
well.
Is
that
framing
something
for
its
value
is
really
really
difficult
for
humans.
A
So
it's
pretty
difficult
to
say:
I'm
gonna
do
thing.
Price
tag
x
and
very
often
folks
would
be
like
I'm
gonna.
Do
thing
milestones.
Xyz
me,
the
person
with
price
tag
y
and
so
pretty
often
folks
would
just
sort
of
default
to
contracting
hourly
rates
and
that's
just
sort
of
the
name
of
the
game.
It's
kind
of
really
hard
to
get
into
that
mindset,
but
that's
another
lesson
that
we
learned,
and
so
why
am
I
talking
about
lessons?
Why
am
I
going
through
this
program?
A
Well
part
of
it's
a
recap,
but
the
other
thing
is
that
I
think
these
are
some
good
recommendations
for
the
dow
and
then
I'll
end
with
sort
of
a
little
bit
of
a
vision
check,
hopefully
to
inspire
someone
as
they
go
from
there.
So
the
key
is
to
frame
problems
and
then
just
sort
of
decide
right.
So
if
you
look
at
these
as
micro
grants,
they're
kind
of
small
in
the
grand
scheme
of
things
so
look
at
them
as
a
solvable
problem
for
the
dow
make
sure
the
milestones
fit.
A
A
We
would
like
ask
more
questions
and
then
an
advisor
would
go
back
to
someone
with
an
idea
and
then
we
would
evaluate
it
again
and
there
could
have
just
been
a
like
faster,
tighter
feedback
loop,
and
then
that
would
mean
that
you
could
take
more
bets
on
people
which
would
be
super
cool.
Also,
some
process
improvements
would
be
nice.
Picking
one
platform
to
update
statuses
and
decisions
would
be
cool.
Github
does
work
for
this,
but
again
that
would
have
been
another
telegraphing
thing
that
would
have
been
super
nice.
A
A
I
think
this
is
already
kind
of
happening
in
the
dow
anyway,
which
is
like
really
cool
to
see.
Is
that
everybody's
opening
up
their
ideas
or
their
core
units
and
they're
presenting
these
things,
so
that
there's
like
an
open
process,
but
one
suggestion
here
is
just
an
accountability,
buddy.
Basically
someone
who
reminds
you
to
update
everybody
on
what
you're
doing
so
you
don't
disappear
into
a
corner.
A
I
mentioned
earlier.
Also
an
open
idea
review
would
be
cool
again.
This
is
another
thing
where
the
forums
is
a
natural
choice,
or
you
could
do
these
public
calls
where
you
are
bringing
something
to
the
dow
you
want
to
solve
it
through
this
granting
format,
then
you
can
just
take
people's
ideas
and
then
that
allows
you
to
speed
up
the
feedback
and
get
some
mvps
out
there.
Also,
I
definitely
over
documented.
The
heck
out
of
this
less
documentation
is
always
good.
A
Keep
things
simple,
sorry
y'all,
my
other
suggestion
to
the
dow
would
be
to
just
maybe
change
the
name.
Micro
grants
or
grant
to
hire
or
mini
mips
are
all
suggested.
I
like
mini
mips,
so
let's
roll
with
that,
I
think
that
c-dips
could
evolve
and
become
a
very
useful
thing
right,
like
the
original
vision
for
them
was
that
they
would
become
a
robust
public
good.
A
They
would
seed
small
iterative
improvements.
Large
impacts,
essentially
punching
above
their
weight
class
mini
mips,
could
serve
as
like
a
project
tool
before
people
do
like
robust
committee,
things
like
core
units
or
creating
huge
projects
that
could,
at
least
like
prove
their
metal
kind
of
like
an
alternative
resume.
If
you
really
think
about
it
or
mini
mips,
could
set
an
example
for
the
broader
ecosystem
right
as
an
earning
opportunity
for
participants.
It's
a
way
to
get
out
of
that
sort
of
traditional
crypto
sort
of
pre.
A
The
other
thing
is
that,
if
you
step
up
to
create
a
hopefully
possibly
future
mini
mip,
it
would
become
a
visible
achievement,
something
that
builds
reputation
I
mean
heck.
We
could
even
make
a
badge
for
it,
but
that's
those
are
the
lessons
we
did.
That's
the
program
recap
and
that's
the
story
of
c
dips,
and
I
hope
that
someone
finds
his
utility
out
of
it
and
does
something
cool
thanks.