►
Description
Special Guests:
Community Development Demo Day!
15 mins Portal ( Rejon and Tim Black)
10 mins Badges ( scottrepreneur )
10 mins CDIPs ( Tim Black )
10 mins Community Marketing/Messaging ( mkrtomalpha )
Maker is a Decentralized Autonomous Organization(DAO) that manages the Maker Protocol on the Ethereum blockchain.
This video is a weekly community call that covers all Technical Milestones, Online Events, Partnerships, New Hires, Highlights from the Community, Real-Life Events, and more. Every now and then we even have a guest.
Maker Relay Ep 16
https://forum.makerdao.com/t/maker-relay-ep-16
If you're curious to learn more about MakerDAO explore some of the resources below:
Awesome-MakerDAO Resource Repository: https://awesome.makerdao.com/
Technical Documentation: https://docs.makerdao.com/
Community Portal: https://community-development.makerdao.com/
Governance Forum: https://forum.makerdao.com/
Website: https://makerdao.com
Twitter: https://twitter.com/makerdao
Reddit: https://www.reddit.com/r/MakerDAO/
Chat: https://chat.makerdao.com/home
A
Hey
everybody
welcome
to
october
13th,
make
your
dial
community
call.
My
name
is
david
utrobin
and
welcome.
Welcome
to
the
call
happy
tuesday.
I
hope
everybody
who
is
watching
or
here
live
with
us
or
watching
on
the
youtube
recording
wishing
you
guys
a
fine
day
today
is
gonna,
be
a
fun
one.
We've
just
spent
the
last
15
minutes
or
last
hour
playing
around
with
crowdcast
realizing
how
weird
it
is,
but
this
one
is
going
to
be
good.
A
So,
typically,
if
you're
new,
this
call
is
used
for
kind
of
covering
what
the
latest
events
that
are
happening
in
maker
dow.
Are
we
typically
go
through
the
maker
relay
if
we
don't
have
any
special
guests
or
special
functions
planned,
but
today
we
have
a
special
function,
and
so
and
so
just
to
give
a
little
bit
of
context
myself,
david
utrobin,
I
work
in
something
called
the
community
development
department
at
the
maker
foundation
and
the
community
development
department
actually
works
to
help
bridge.
A
You
know
people
in
the
community,
like
freelancers
individuals,
like
everybody
from
designers,
coders
to
content
writers,
you
name
it.
We
try
to
bridge
these
individuals
with
becoming
active
in
the
in
the
actual
maker
dial
community
in
the
protocol
right.
We
want
them
to
create
educational
materials.
A
We
want
them
to
become
a
part
of
the
community
to
like
have
impact,
and
also
to
do
something
that
they're
that
they're,
enjoying
and
loving
so
like
our
job
is
really
to
kind
of
bridge
bridge
people
to
understand
what
what
they
can
do
in
our
community
and
so
for
the
last
I'd
say
since
really
like
january
tim
black
who's.
One
of
one
of
these
really
awesome
awesome
awesome
community
members.
A
So
with
that
being
said,
I
guess,
I
guess
really
quickly.
I'm
gonna
run
through
the
agenda.
The
first
guest
that
we
have
on
is
rayjan
and
tim
and
they
have
been
working
on
the
redesigned
community
development
portal
and,
if
you
don't
know
about
it,
well,
you
might
remember
the
old
community
development
portal,
which
was
kind
of
a
git,
bookc
and
very
flat,
and
very
very
unidimensional,
so
to
speak.
A
B
Okay,
okay
I'll
start,
considering
we're
sharing
the
same
presentation
and
I'll
just
do
a
very
brief
intro,
hello,
everyone,
I'm
tim
black
I've
been
in
crypto
well
as
a
hobbyist
or
enthusiast
since
2013
and
then
professionally
since
2018.
I
joined
makers
community
last
year,
actually
because
I
was
looking
to
pick
up
some
work
and
I
just
dm'd
david
and
at
that
time.
That
was
the
only
way
to
do
it
and
now,
as
he
so
illustriously
explained,
we
have
c
dips
and
grants
and
all
sorts
of
wonderful
things.
B
Amy
has
taken
over
from
rich
our
former
head
of
community
development
and
we're
in
a
bit
of
a
flux,
so
we're
always
looking
for
new
talent
and
one
of
the
ways
to
do
that
is
through
our
portal,
which
rajan
is
sharing.
The
screen
here
with
me
as
well,
is
our
lead
developer
alongside
shea
fitzgerald,
our
lead
designer
and
we're
just
basically
going
to
do
a
little
presentation
about
what
we
created
for
everybody.
B
B
How
do
we
put
it
all
together
and
then
rajan
will
take
over
the
technology,
stack
the
philosophy
of
how
it's
built
some
of
the
design
and
then
give
you
that
as
the
ultimate
payoff,
and
so
we
call
this
a
portal,
but
you
really
want
to
think
of
the
community
dash
development
site
as
a
hub
for
hosting
programs,
and
it's
all
community
generated
resources
right,
so
that
improves
the
management,
onboarding
and
growth
of
maker
dow
as
a
whole
right.
So
you
can
think
of
the
portal
as
like
your
interface
to
community
development
as
a
function.
B
Our
docs.makerdale.com
are
like
spectacular.
So
that's
not
our
focus
in
the
portal,
but
ideally
it's
folks
who
are
also
familiar
with
maker,
dow
and
looking
for
canonical
specific
answers
about
maker,
doubt
or
ways
to
engage,
and
so
the
objective
for
the
portal
always-
and
it
was
a
two-year-old
ticket
in
github-
was
to
make
a
platform
that's
more
friendly
for
contributors
for
content
creators
and
for
ultimately
developers
to
collaborate
and
easily
engage.
The
other
thing
is
that,
since
maker
dow
is
a
global
protocol,
it
works
everywhere.
You
can't
turn
it
off.
B
B
And
so,
when
we
first
embarked
on
this
project,
it
was
a
content.
First
approach
to
putting
this
thing
together,
and
so
right
here
is
a
site
map
put
together
by
ryan
cordell.
Now
at
the
ethereum
foundation,
who
was
one
of
our
contributors?
Who
did
a
c-dip
as
david
mentioned,
so
he
took
all
of
those
markdown
files
and
mapped
them
into
a
much
more
realistic
reading
of
everything
that
was
there.
And
now
we
have
these
simple
headers
right,
learn,
contribute
and
funding.
B
All
of
our
pages
were
asking
something
of
the
reader
and
we've
reconfigured
everything
to
fall
under
these
action.
Verbs
right
so
learn
gives
you
explanations
of
foundational
maker
concepts
and
then
hubs
you
out
to
further
reading.
That
might
be
some
other
resource
like
the
bitcoin
white
paper
or
the
ethereum
yellow
paper
right
or
it
might
just
be
something
in
doc's
dot,
maker,
dow
or
the
blog
contribute
gives
you
guides
on
best
practices
as
a
community
development.
Member,
which
remember,
is
all
of
you.
Everybody
can
be
part
of
the
maker
dial
community
right.
B
Funding
is
also
guides
on
the
process
for
applying
for
meetups,
for
example,
which
david
runs
for
c-dips,
which
we
talked
about
and
I'll
do
a
presentation
about
later
for
larger
grants
and
then
for
hackathons
as
well,
and
when
we
say
community
we
really
do
mean
community.
This
is
entirely
built
by
community
members.
These
are
community
generated
resources
right.
It
was
made
100
through
grants
right.
That's
how
community
development
runs,
whether
they're
small
or
whether
they're
large
right
so
our
content
team
development
team
design,
team.
C
Sweet
awesome
so
hello,
everybody,
I'm
raija.
I
was
the
lead
developer
and
architect
for
the
development
execution
for
our
new
portal,
whether
that
be
2.0.
If
you're
new
here
that'll
be
the
1.0
for
you,
I'm
known
around
these
parts
as
the
mad
scientist
maximum
crash
and
what
that
mad
scientist
moniker
means
is.
C
B
C
C
B
C
However,
the
next
problem
that
we
had
was
with
translations,
not
as
large
as
an
issue.
However,
when
it
comes
to
considering
more
complicated
languages,
especially
languages
that
read
right
to
left,
including
those
in
these
kinds
of
services,
is
way
more
difficult.
Just
because
they're
not
thought
about
from
the
jump.
C
There
are
also
major
blockers
on
creating
more
complex
components,
so
videos
touts
buttons
kind
of
anything
that
a
content
creator
would
have
liked
to
provide
to
a
video
is
kind
of
well
to
a
article
or
to
a
page
is
kind
of
locked
off
behind,
whatever
these
services
can
provide,
or
they
would
have
to
find
a
very
specialized
developer
to
solve
this
problem,
the
list
kind
of
goes
on
from
there.
If
you
use
these
other
kind
of
technologies,
however,
the
objectives
were
pretty
clear
from
the
jump.
C
The
second
is
that
the
maker
dial
community
is
global.
We
can't
just
keep
thinking
with
a
us
based
mindset
with
how
we
develop
these
things.
Instead,
we
need
to
solve
for
localization
accessibility
out
the
gate.
That
way,
it's
not.
It's
not
a
nice
to
have
it's
not
a
sprinkle
on
top.
It
is
a
core
piece,
a
core
feature
of
this
product.
The
next
is
that
the
content
directory
or
whatever
will
contain
all
of
our
content
for
the
site.
It
has
to
be
decoupled
from
the
logic
that
makes
the
site
work.
C
C
The
next
is
that
the
new
framework
must
have
more,
must
support
more
advanced
components.
That
way,
there's
not
really
any
limitations
on
what
we
could
execute
from
a
technological
standpoint.
So
if
a
content
creator
or
somebody
in
the
community
says
oh,
I
would
really
love
a
component
that
did
this
developers
have
more
opportunities
to
say
yes
and
explore
those
options
without
having
to
look
down
the
rabbit
hole
of
these
existing
services
to
see
if
they
should
have
to
hack
together
a
solution
that
would
take
more
time
and
cost.
C
Essentially,
a
lot
more
money
to
build
and
transferring
of
the
legacy
content
should
be
a
breeze.
We
have
to
keep
in
mind
that
we
still
have
hundreds
of
existing
pages,
that
a
lot
of
people
really
rely
on
to
do
the
work
they
do
every
day,
so
ensuring
that
we
could
wrap
all
of
these
up
in
a
nice
package.
C
Is
a
big
ask.
So
this
is
you
know
when
we
talk
about
it,
it's
easy
to
talk
about
it's
easy
to
use,
but
it'll
be
extremely
difficult
to
execute,
there's
not
really
a
free
ish,
modern
day
content
platform
or
any
really
content
management
system
or
cms.
That
really
supports
this.
At
least
that
I
could
find
if
you
do
find
one.
Let
me
know
I
would
love
to
talk
with
them,
but
this
is
like
a
dream:
cms
right
somebody.
C
So
that
way,
anybody
that's
new
to
the
community,
whether
they
be
more
technically
versed
or
whether
they're
completely
new
to
crypto
and
they're.
Here,
just
getting
started
getting
their
feet
wet
in
our
community,
they
should
still
be
able
to
contribute
we're
also
talking
about
low
friction
for
creating
new
content,
adding
new
features
making
the
site
look.
However,
you
want,
if
shay
or
another
designer
comes
in
and
says
I
think
we
could
make
a
component
that
looks
like
this
or
bring
some
flair
to
this
area.
C
We
also
wanted
to
make
sure
that
the
content
was
as
portable
as
possible.
I
keep
talking
about
legacy
content,
but
essentially
we
don't
want
to
get
locked
into
any
system
that
we
end
up,
creating
with
the
content
that
way
if
one
day
somebody
says,
oh,
some
of
the
tools
that
we're
using
some
of
the
frameworks
we're
using,
aren't
really
hidden
for
us.
We,
but
we
want
to
save
the
content.
Everybody
works
so
hard
on
this.
You
should
be
able
to
just
take
that
and
migrate
it
without
any
concerns.
C
So
the
stack
that
we
use
to
to
make
this
dream
a
reality.
We
have
github
kind
of
as
a
base
of
operations.
This
is
the
place
where
all
of
our
conversations
where
our
history
will
happen.
Where
issues
will
pop
up?
This
is
the
space
in
which
the
community
collaboration
from
a
technical
standpoint
starts
for
the
rest
of
our
stack,
though
internally
we
are
using.
Gatsby
has
fantastically
expandable
build
pipelines.
Graphql
is
built
in
through
the
use
of
sift
tons
of
plugins.
C
We
are
also
leveraging
lunar.js
internally
part
of
our
build
pipeline
with
gatsby,
as
it's
a
really
fantastic
static
search
index
builder,
where
it
can
run
through
our
entire
content
directory
and
then
have
that
available
on
as
search
on
our
site
without
having
to
touch
anything
like
algolia
or
any
other
search
engines.
And
then
I
also
built
a
custom
translation
module
inspired
by
i18
next
in
a
couple
of
my
old
previous
projects
in
hopes
of
building
something
that
works
really
well
with
our
flexible
content
stack.
C
So
the
things
that
this
stack
solves
for
is
the
directory
interfacing
through
gatsby's
graphql
api.
This
means
that
developers
who
are
working
more
closely
to
site
code
and
not
content,
get
to
touch
or
tap
into
some
of
the
front
matter
variables
that
are
provided
through
markdown
files.
So
if
we
wanted
something
more
customizable
by
content
creators,
we
can
build
more
features
into
their
markdown
files.
C
Github
also
is
going
to
serve
as
our
source
of
truth.
It's
it's
kind
of
where
everything
will
start
and
where
everything
will
end.
So
there's
a
clear
path
or
pipeline
for
how
things
will
work.
We
also
built
a
number
of
actions
that
make
it
easy
for
this
community
to
collaborate
and
communicate
on
any
new
work
that
is
coming
in.
C
Why
maintains
a
design
bridge
of
communication
between
the
foundation
and
the
community?
Essentially
because
die
ui
is
built
internally
and
leveraged
throughout
our
community.
It
essentially
creates
a
consistent
means
of
colors
and
themes
and
icons
from
which
other
maker,
dial,
community
projects
or
c
diffs
may
essentially
bridge
off
of,
and
the
portal
happens
to
be
one
of
the
largest
to
use
it
today
and
then
mdx.
I've
already
gushed
about
it,
but
it
allows
us
to
leave
markdown
with
reactant.
C
If
you're
a
react
developer,
you
can
only
imagine
the
I
guess,
the
possibilities
that
come
from
that,
because
this
is
where
we
get
to
expand
upon
the
bigger
ass
for
different
kinds
of
components
and
where
we
can
interweave
buttons
and
markdown,
which
isn't
something
that's
entirely
possible,
and
it
also
means
that
our
content
editors,
whose
previous
experience
is
writing
in
hack
md
for
get
books.
They
don't
have
to
learn
a
new
language.
They
don't
have
to
change
how
they
work.
C
C
There
is
a
conflict
in
the
architecture
and
the
philosophy
of
its
execution.
You
would
think
typically,
a
ui
engineer
would
be
the
one
to
handle
all
the
designs
and
handle
all
the
content.
They
would
take
them
and
integrate
them
into
the
site,
except
the
way
that
this
is
developed
or
architected.
It's
no.
No,
I'm
not
writing
a
website.
You're
writing
a
website.
C
However,
there's
definitely
some
bells
ringing
and
some
folks
heads
about
this
gatsby
is
not
forever.
Nor
is
mdx
right.
We
there's
a
big
issue
with
locking
our
content
into
very
specific
frameworks
where
we
don't
want
to
say:
okay,
everybody's
using
ndx,
everybody
has
reacted
to
markdown.
What
does
that?
Look
like
for
migrations?
C
Essentially,
there's
gonna
be
a
little
bit
of
nitpicking
with
having
to
remove
things
if
they
do
go
back
to
a
markdown
specific
system.
However,
that
would
just
be
as
simple
as
writing.
A
regex
find
a
lookup
for
anything
that
contains
any
greater
than
or
less
than
brackets,
with
a
slash
at
the
end.
So
what
that
really
means
is
you
know
the
minimum
requirements
for
these
for
these
architectural
design
decisions
is
that
markdown
format
for
all
of
the
content
content
can
be
rendered
in
a
non-react
environment.
C
What
you
see
is
what
you
get
and
we
don't
go
any
further
than
that.
We
don't
keep
any
secrets
with
our
with
our
content
creators.
They
are
in
complete
control
of
everything,
and
you
know
this
is
also
a
somewhat
frictionless
workspace
where,
but
you
know,
working
with
open
tech,
open
source
technologies
is
always
a
gamble.
You
know
I
took
a
big
chance
with
mdx.
C
C
The
more
a
content
creator
will
want
out
of
our
mdx
system,
the
more
of
a
front-end
developer.
They
become
essentially
the
more
writing.
Content
is
the
same
as
writing
code
for
our
site,
which
essentially
means
knowledge,
is
power.
The
more
of
a
react
background
you
have
of
leveraging
the
tools
we
create
or
creating
your
own
tools
for
this
portal
essentially
makes
you
just
like
myself
a
top
level
tools
developer
in
the
portal.
If
somebody
has
an
idea,
if
somebody
wants
to
connect
to
an
api,
somebody
wants
some
kind
of
form.
C
Somebody
wants
a
wizard.
Somebody
wants
a
carousel
as
long
as
you
have
the
knowledge
to
execute
your
idea,
you
essentially
have
all
the
power
to
make
it
a
reality.
In
our
system,
however,
that
doesn't
mean
we
lock
out
anybody
who's,
not
as
technically
versed.
That
doesn't
mean
if
you
don't
know,
react,
you're,
not
welcome
here,
it's
more
so
like
we
use
react
more
so
as
a
means
of
creating
a
space
for
conversations
between
our
content
creators
and
our
developers.
C
So
you
could
say
this
project
is
a
little
bit
auto
magical
because
it
builds
a
lot
of
things
for
us.
It
has
this
wonderful
build
pipeline
out
of
gatsby.
It
handles
all
the
header
through
the
front
matter
and
handles
on
the
side
nav
automatically,
and
you
know
that
comes
at
a
cost
right,
there's
nothing
is
free,
as
you
may
say,
so,
the
lift
has
to
go
somewhere.
While
this
project
may
seem
like
a
miracle
built
on
wheels
because
it's
breathing,
it's
live
it's
out
there.
C
C
I
would
say
you
could
almost
say
it's
a
there's,
a
culture
to
working
in
this
portal
or
working
with
this
portal
we're
reading
this
portal.
So
there's
a
lot
more
to
cover.
I
could
talk
about
this
for
hours
and
hours,
but
you
can
find
most
of
my
in-depth
writings
and
the
pull
requests
on
our
repo
I've
written
about
230,
pull
requests
that
are
about
three
paragraphs
long,
you
could
say
I've
written
the
great
expectations
by
charles
dickens
by
now.
C
However,
I've
also
written
a
ton
of
other
stuff
and
I
hope
to
expand
more
so
about
this
later.
As
I
start
to
take
this
project,
and
hopefully
in
the
next
couple
of
weeks,
make
it
open
source
for
other
folks
to
have
a
starter
with.
So,
if
you're
around
our
community,
if
you're
new
to
our
community,
please
stay
tuned,
I
will
definitely
be
dropping
that
by
the
end
of
this
month.
But
with
that,
thank
you
for
listening.
A
Sweet
thank
you
so
so
so
much
rajon
that
was
really
fascinating.
So,
like
I'm,
not
a
developer
and
and
the
way
that
you
explain
things,
it's
kind
of
it
kind
of
I
kind
of
see
it
like.
It
really
is
a
secret
on-ramp,
because
when
I've
been
playing
with
mdx,
it's
like
oh,
like
slowly,
the
you
know
things
are
clicking
in
my
head.
Like
okay,
now
I
kind
of
understand,
like
the
general
like
workarounds,
for
almost
any
language
in
code.
A
It's
you
kind
of
get
the
basics
you
kind
of
get
those
first
principles
and
yeah,
it's
really
cool.
It's.
It's
also
pretty
comfortable
to
work
with
there's
like
a
cheat
sheet
in
there.
So,
like
you,
can
see
like
the
really
easy
ways
to
add
the
different
react
components
inside
of
mdx
itself
and
so
yeah
man.
Thank
you.
You've
been
a
total
total
total
legend.
A
Yeah,
of
course,
and
so
with
that
I'm
gonna,
let
you
go
and
and
so
next
we
had
the
forum
badges
program
which
actually
unfortunately
aaron
couldn't
make
it.
But
aaron
did
record.
Oh
scott
is
here
yeah
cool,
so
I'm
gonna,
assuming
scott,
is
ready.
I'm
happy
to
give
it
over
to
scott.
I'm
gonna
invite
you
just
to
the
screen,
scott
and
and
yeah,
and
we
could
talk
a
bit
about
it,
because
the
forum
badges
are
really
really
cool.
A
A
That
means
their
opinion
should
be,
like.
You
know,
considered
like
a
little
bit
more
seriously
than
the
person
that
has
almost
so.
It
gives
a
level
of
like
credentials
to
the
community,
which
I
really
find
gives
an
overall,
better
level
of
depth.
So
with
with
that,
I'm
gonna
give
it
over
to
scott.
What's
up
man,
how
you
doing
how's.
A
A
D
D
D
D
E
A
E
D
And
then
yeah
the
forum,
integration
leverages
the
service,
that's
identifying
those
participants,
and
so
then
you
can
go
into
your
settings
inside
of
the
forum
and
there's
a
little
there's
a
little
import
badges
button
here
at
the
bottom,
where
you
sign
a
message
that
sends
your
username
just
to
the
backend
service.
That
looks
like
the
badges
that
you
can
get
and
then
it
will
ping
the
the
forum
and
let
you
know,
I've
already
cleaned
all
these
badges.
D
A
Nice,
so
I
know
a
lot
of
the
questions
around
this
project
have
been
with
regards
to
like
not
letting
out
your
ethereum
address
to
the
public
or
like
being
able
to.
Basically,
you
know,
claim
your
badges
have
them
associated
with
your
forum
account,
but
not
give
away
the
address
you
used
to
sign
the
message
to
redeem
them.
Is
there
any
like?
Can
you
talk
a
little
bit
more
about
kind
of
the
privacy
stuff
in
mind
that
you
and.
D
A
D
A
All
right,
it's
sweet
yeah!
No,
no!
It's
good!
I
I
was
I
was
helping
your
bandwidth.
I
was
like
I
also
closed
my
video,
so
cool
anyway.
Yeah.
That's
that's
really
really
fascinating
man.
If,
if
anybody
here
is
a
regular
user
of
the
forums,
I
highly
suggest
you
check
out
check
out
that
functionality,
because
it
is
really
really
really
fun
to
have
a
bunch
of
badges.
A
Next
to
your
name,
when
you
comment
it's
like
makes,
you
feel
like
a
bit
of
a
boss,
but
I'm
I'm
being
facetious,
of
course,
but
but
yeah
cool,
so
if,
by
the
way
throughout
this
demo
day
feel
free,
anybody
in
the
chat
feel
free
to
ask
questions,
feel
free
to
give
comments.
I'm
happy
to
relay
them
to
to
anybody
who's,
presenting
on
your
behalf
and
so
so
yeah,
but
yeah
with
that
scott.
A
I
think
I
think
that
more
or
less
covers
badges
right,
yeah
cool,
all
right,
so
the
next
so
I'm
gonna,
oh
actually,
akiba,
has
a
question:
what,
if
I'm
an
active
forum
user,
but
not
an
active
blockchain
user?
Oh
thing,
then
you
got
no
skin
in
the
game.
Baby!
Sorry
yeah!
You'll
get
that
cred.
You
don't
get
that
cred.
A
Shots
fired
yeah,
exactly
exactly
oh
man,
all
right
cool
so
could
be
maker
whale
badges,
but
none.
Currently
it's
a
call
for
yeah.
Well,
exactly
right,
like
so.
If
you're
on
the
forum
and
and
you're
very
active
and
you
haven't
redeemed
badges
like,
I
guess,
people
like
certain
people
won't
ever
redeem
badges
just
for
privacy
reasons
and
like
whatever
and
like
I'm
sure
people
in
our
community
will
respect
that.
But
if
you
are
an
active
contributor
and
you
do
have
some
level
of
like
on,
you
know,
verified
credentials
like
hey.
A
A
B
Hello,
it
me
again
how's
everyone
doing,
I'm
actually
glad
we're
running
out
of
time,
because
there's
another
presentation
I
have
to
give
we'll
do
that
later,
because
after
this
tom
will
come
on
and
talk
about
how
we're
going
to
talk
about
all
these
things
in
general.
But
right
now,
I'm
just
going
to
share
my
screen
and
do
a
really
brief
proposal
or
sorry,
a
presentation
on
what
c
dips
are
right.
Name
tpd!
I
guess
because
they're
in
progress.
So
let
me
share
my
screen
with
this.
B
All
right
so
cdips
we're
gonna
talk
about
what
the
what
when
and
how
to
use
them
and
basically
what
they
are
we're
going
to
talk
about
where
we
are
now.
We've
been
working
on
this
process
for
about
six
months
and
we're
going
to
basically
overview
who
they're
for
this
actually
was
a
presentation
that
would
talk
about
development
grants,
but
I
decided
to
turn
that
off
because
it's
going
to
get
confusing.
So
we
can
just
ignore
that
part.
So
I'm
sure
you're
all
wondering
what
this
acronym
means.
B
It's
a
community
development
initiative
proposal
as
opposed
to
improvement,
because
you
know
why
not
be
just
different
than
everybody
else,
since
everything
is
mips
and
yips
and
anything
whatever
it
rhymes.
Who
cares,
you
can
basically
think
of
a
c-dip
as
a
micro
grant
for
ideas
right.
So
cdubs
are
a
robust
and
lightweight
framing
tool.
They
make
your
life
easier
when
you
have
an
idea,
and
so
there's
for
mostly
small
tightly
scoped
projects
right.
B
There
are
some
heuristics
around
this,
but
the
the
the
thought
or
the
the
program
is
essentially
set
up
to
be
like.
I
have
an
idea
and
I
need
some
money
to
make.
It
really
happen
and
here's
the
milestones
for
doing
it
and
here's
how
it
comes
in.
It's
really
just
a
document
framework
right,
the
heuristics
for
funding
a
cdip
or
getting
them
going
or
around
a
budget
of
5k
or
less
should
take.
Maybe
two
and
a
half
months.
Most
people
in
our
maker
down
community
are
part-timers
right.
B
They
have
other
full-time
jobs,
they
have
other
things
they
do
so,
hopefully
they
can
rope
in
a
couple
of
friends,
maybe
two
or
three
people
scope
down
on
a
couple
of
milestones
and
sort
of
hammer
it
out,
badges
turned
out
to
actually
be
four
cdips
and
two
teams,
so
they're,
flexible,
they're,
just
heuristics
one
person
can
do
one
project
or
ten
people
could
do
something
that
takes
six
months
and
they
just
do
it
two
hours
a
week,
it's
very,
very
flexible.
That's
the
whole
point.
B
C-Dips
are
broken
down
into
this
document
framework
with
roles
inside
of
it
right,
and
so,
if
you
have
an
idea-
and
you
want
funding
to
deliver
that
idea,
then
that
makes
you
a
contributor
if
you
like
that
idea,
and
you
want
the
responsibility
to
help
frame
check
in
update
the
rest
of
the
team.
We
have
a
wednesday
sync
where
we
talk
about
cdips.
B
If
you
want
to
support
that
team,
if
you
want
to
solve
problems,
help
scope
next
steps
and
just
be
the
person
to
check
in
and
make
sure
the
project's
on
track,
that
we
call
those
people
advisors
and
then,
if
you
are
like
amy
david
myself
and
juan
and
you
control
the
budget
and
want
to
see
an
idea
succeed,
then
that
makes
you
an
approver.
Our
hope
is
to
grow.
The
scope
of
these
roles.
B
And
so,
when
someone
has
an
idea,
when
do
you
want
to
use
a
c-dip?
It's
when
it's
sort
of
specific
and
it's
kind
of
a
measurable
idea
right,
it's
sort
of
quick
and
clear.
The
timeline
is
obvious
about
how
long
it
should
take
there
isn't
too
much
research
up
front.
We
had
someone
ambitiously
come
in
and
say
they
wanted
to
build
an
org
chart
tool
which
was
massively
awesome,
but
it
turned
out
to
be
like
a
huge
scope
and
it
just
kept
expanding,
so
it
didn't
actually
fit
in
a
c
dip.
B
Ideally,
if
you're
going
to
execute
on
your
idea,
the
skills
required
are
in
your
wheelhouse,
it's
something
you
feel
pretty
capable
of
doing,
and
ideally
your
idea
aligns
with
the
com
dev
mission
for
now
right.
Community
development,
but
c-dips
are
built
to
be
scalable,
and
hopefully
we
can
expand
this
out
as
part
of
a
micro
granting
program
for
program
for
the
whole
community
or
see
where
it
goes.
Remember
it's
only
six
months
old,
so
it's
pretty
straightforward.
You
just
fill
out
the
cdip.
It's
a
github
issue
template
it's
also
a
document
framework.
B
It's
going
to
be
pinned
to
the
top
of
community
development,
it's
just
a
google
doc.
You
make
a
copy.
You
fill
out
all
the
questions
in
bold
and
then
you
find
someone
to
help.
You
usher
you
through
the
process.
It's
super
open
open-ended.
The
project
planning
is
basically
built
into
it.
So,
as
you
fill
in
this
dock,
it
takes
maybe
five
ten
minutes
or
something
like
that.
Some
people
have
taken
a
lot
longer.
B
There
are
just
three
stages:
there
is
submission,
execution
and
completion,
and
so
that
gives
you
a
full
end-to-end
experience
of
going
from
an
idea
to
presenting
it
on
a
demo
day
like
this
or
putting
it
into
a
wednesday
call
when
community
development
comes
together.
I
also
went
pretty
granular
in
this
process.
B
You
basically
have
whatever
you're
doing
on
your
project
in
one
screen
and
then
you've
got
like
a
map
that
you
can
go
back
and
refer
to
anytime.
You
need
it,
and
so
these
links
here
take
you
to
a
google
doc.
They
take
you
to
that
visual
guide
that
I
mentioned,
which
is
a
figma,
and
then
it
also
takes
you
to
another
google
doc
about
what
to
expect,
and
so
we've
broken
down
this
whole
process
into
a
pretty
straightforward
thing,
because
it
is
straightforward.
B
E
A
B
We've
we've
talked
about
them
ad
nauseum.
I
expect
to
talk
about
them
for
the
next
year.
The
long-term
plans
is
actually
to
basically
automate
these
and
turn
them
into
a
community
tool,
and
so
ideally
it
would
be
the
kind
of
thing
that
we
can
start
embedding
in
different
places.
People
can
use
them
in
different
ways,
and
it's
like
using
some
github
actions
and
other
stuff
like
that.
B
It
just
it's
the
kind
of
thing
that
people
feel
excited
about
in
the
space
they
come
in
they're
like
oh,
I
got
a
c
dip
and
then
I'm
going
to
apply
for
a
grant.
Now
I'm
going
to
go
and
join
this
team.
You
know
it's
the
kind
of
thing
that
just
really
falls
in
line
with
what
community
development
does,
which
is
just
like
incubate
talent,
make
a
talent,
flywheel
and
ship
them
out
wherever
they
go.
So
that's
how.
A
B
A
You
use
the
use
the
form
to
really
lay
out
your
idea
and
actually
in
completing
the
form
it
helps.
You
clarify
your
idea,
because
a
lot
of
people
have
ideas,
but
they're
not
really
like
fleshed
out
and
drawn
out
to
the
point
where
you
could
receive
funding
from
somebody
who's
offering
it
right
and
so,
like
yeah
tim
you've
done
an
absolutely
fantastic
job
like
putting
this
together
over
the
last,
like
basically
six
to
eight
months
and
yeah.
A
We're
I'm
excited
to
see
where
it
goes
and
continues
to
go
and
where
it's
going
to
be
applied,
because
it's
not
just
here
in
community
development
like
this,
can
be
actually
adopted
and
like
slightly
rebranded,
to
be
to
be
a
proposal
tool
pretty
much
in
any
of
the
maker
dao
like
domain
teams
and
and
really
even
outside
of
maker
dial.
But
that's
a
whole
different
story.
B
B
The
real
key
is
that
it's
like
small
enough
for
you
to
really
nail
it,
that's
kind
of
how
it
goes,
and
so,
if
you
need,
you
know
10k
for
a
budget
of
like
seven
people
operating
on
a
team,
but
the
whole
thing
is
heavily
coordinated
and
it
really
makes
a
lot
of
sense
down
to
like
the
calendar
invites
that
that
sounds
pretty
good.
You
know,
and
again
this
is
a
young
program
right,
sometimes
you
know
david
or
I
have
to
serve
as
an
advisor
and
an
approver
which
gets
weird,
sometimes
right.
B
So
that's
why
we're
hoping
to
scale
it
up
and
have
more
people?
We've
got
some
buy-in
from
the
maker
foundation
themselves.
They
have
community
leads.
One
of
them
is
doing
indonesian
translations
right.
So
it's
a
very
young
program
and
we're
trying
to
just
like
get
the
opportunity
to
like
remove
the
clunkiness
and
get
rid
of
some
of
the
friction.
And
so
some
of
that
is,
like
a
you
know,
getting
a
c
dip
for
like
2,
15k
and
amy.
Being
like
that's
a
grant
and
we'll
be
like.
B
A
Right
right
exactly
and
also
like
for
smaller
c
dips,
like
even
so
that's
what's
in
the
same
smaller
c
dips
like
require
a
little
bit
less
like
accountability
right
when
you're
giving
a
lot
more
money.
There's
just
a
lot
more
detail
required.
There's
a
lot
more
follow-up
required.
There's
a
lot
more
kind
of
checks
required
just
to
make
sure
that
you
know
the
person
who
is
being
granted.
A
This
money
is
responsible
and
actually
fulfilling
on
the
idea
right
and
so,
and
so
yeah
c
dips
are
a
really
good
kind
of
lower
end
granting
tool.
Basically,
like
like
some
said
in
the
presentation:
it's
it's
up
to
around
5k
past
5k,
it
might
6k
okay,
it
still
might
be
a
relatively
small
idea.
It
might
fit
into
the
scope
when
you
start
getting
into
like
the
higher
numbers
you
should
already
be
considering
like
all
right.
Is
this
maybe
a
more
serious
like
software
project?
A
Is
this
like,
maybe
a
more
serious
like
like
what
is
this
you
know
like?
Should
I
am
I
applying
for
the
right
funding
here
right?
Should
I
go
to
the
development
grants,
for
example,
but
yeah
totally
man
totally
so
yeah?
If
you
guys
have
questions
about
it,
feel
free
to
okay,
bye,
bye,
feel
free
to
to
ask
us
about
it
in
the
community
development
chat,
and
so
with
that
I
believe.
Let's
we
have
about
10
minutes
left.
A
You
should
be
able
to
come
on,
and
so
tom
is
going
to
talk
a
bit
about
the
govcoms
working
group
or,
generally
speaking,
like
community
marketing,
slash
messaging,
I
believe,
yeah.
Sorry
govcoms
is
like
a
slightly
separate
thing,
but
yeah
I
see
maker
is
connecting
and
yeah
there.
You
are
what's
up.
What's
up
tom.
E
I'm
I'm
tom
and
one
of
the
community
development
peoples,
and
I
specifically
am
a
part
of
the
messaging
team
and
I'm
going
to
give
you
a
rundown
of
what
messaging
is
and
what
it
means
and
how
it
ties
back
to
all
that
all
those
dope
projects
that
came
before
it's
going
to
keep
it
simple.
And
so
let
me
go
ahead
and
share
my
screen.
A
E
Cool,
let
me
start
at
slide
number
one
cool.
Well,
like
I
said
it's
the
community
messaging
team.
It's
basically
a
marketing
function
for
community
development.
What
a
little
bit
of
background
is
we
kept
coming
out
with
these
c
dips
and
then
every
single
one
we'd
be
like
well.
How
do
we
just
solve
discoverability
on
this?
So
like
everything
we
created,
we
kind
of
wanted
to
figure
out.
E
We
needed
like
a
mini
marketing
function
for,
and
that
meant
that
every
project,
no
matter
who
was
working
on
it,
had
to
like
become
their
own
marketing
team.
So
I
have
a
background
in
marketing
and
sort
of
a
few
other
people
who
are
on
this.
Like
little
team,
we
developed
and
so
kind
of
the
idea
was
born
out
of
this
hey.
E
If
we
create
a
blueprint,
if
we
create
a
framework
for
getting
the
for
the
market
for
marketing
for
each
project
for
in
general,
then
there
can
be
a
team
who
gets
a
message
out
about
the
project
instead
of
having
each
each
project.
Try
to
do
it.
So
this
team
currently
is
anna
myself,
jerry
and
tim,
and
let's
move
on
all
right.
Just
real
quick
gonna
go
through
this
agenda.
You
can
tell
I
sold
tim's
template
here.
What.
E
E
And
okay,
so
like
what
is
the
messaging
team?
Computer
community
comdem
has
a
lot
of
projects
and
it's
our
responsibility
to
get
a
message
out.
We
get
the
message
out
messaging
team.
We
get
messages
out.
So,
for
example,
you
have
the
badges
program.
Super
dope,
you'll
stumble
across
it
when
you
go
on
the
forums
or
if
you
talk
to
someone
or
if,
like
you,
know
someone,
but
maybe
how
do
we
get
that
out
to
a
broader
audience?
How
do
we
make
sure
everyone
in
the
maker
community
knows
about
it?
E
E
How
to
tell
people
about
that?
What
do
we
actually
do?
Yeah,
like
seo
site
maintenance,
improving
the
messages
on
the
site,
twitter,
post
blog
posts,
write
a
post
forum
posts,
post
rocket,
chat,
pr
articles,
outreach
to
media
press
kits
videos,
specific
projects
like
marketing
campaigns
like
we
have
this
cool
thing
called
humans
of
maker,
dao,
you're,
saying
like?
Why
haven't
I
seen
it
yet?
Well,
because
we're
pretty
new
and
we're
still
getting
the
framework
together.
E
That
said,
we
have
done
a
few
things
so
far,
cdip11
that
was
us
building
framework,
so
we're
utilizing
the
cdip
model
here.
So
the
tim
was
just
talking
about
seed
of
27.
We
did
a
go
to
market
strategy
for
the
portal,
we'll
be
rolling
out
soon.
You
should
be
seeing
that
c-dip
26
humans
make
your
dao.
E
That
is
this
other
marketing
project.
I
was
talking
about
not
fully
rolled
out
either,
but
these
things
are
all
dope.
I
promise
you're
gonna
be
super
psyched
when
you
see
it
in
the
wild
lots
more
planned
for
sure.
Here's
like
some
of
the
stuff
we
have
going
on.
We
have
a
maker
governance
with
like
a
little
arm
of
the
messaging
team
and
it's
the
maker
messaging
team
and
the
so
we
got
like
you
know.
Just
like
that's
one
example.
E
There
we
have
a
content
calendar
which
you
can
see
in
the
background.
That's
how
we
sort
of
like
organizing
our
workflow.
We
got
a
marketing
plan
below
that.
I'm
super
excited
to
look
at.
I
know,
but
just
kind
of
want
to
show
off
some
of
the
stuff
we're
doing
in
the
background
and
then
we're
also
utilizing
a
new
decision-making
framework
that
calm
down
has
been
working
on
in
general.
E
So
it's
kind
of
like
a
decision-making
framework
for
dao
and
we've
been
utilizing
that
to
move
forward
with
our
overall
marketing
plan
and
to
hopefully
create
some
com
dev
own
channels,
just
to
better
better,
be
able
to
get
the
word
out
and
then,
as
you
can
see,
we
have
like
grammarly
and
notes
making
the
screenshot
just
look
dope
and
then
a
little
ending
slide
here.
So
we
can
stop
after
this,
but
you
know
how
we
can
achieve
our
goals.
E
Just
yeah,
this
little
cool
blip
here
about
content,
marketing
content
marketing
is
a
strategic
approach,
focused
on
creating
distributing
valuable,
relevant
and
consistent
content
to
attract
and
retain
a
clearly
defined
audience.
Yes,
very
true,
and
I
could
go
into
this
whole
thing
on
like
a
marketing
presentation
and
funnels
and
stuff,
but
hey.
I
just
really
actually
want
to
keep
this
like
super
simple,
because
sometimes
people
are
confused
on
what
we
do,
because
we
haven't
put
out
much
yet,
but,
like
yeah
messaging
team
gets
the
message
out,
did
you
do
a
cdip?
B
A
The
things
that
we're
doing
it's
communicating
about
them
like
we
have.
You
know
we
have
how
many
different
projects-
and
you
know,
there's
all
this
noise
in
the
space.
It
really
is
an
art
to
communicate
effectively
about
each
one
of
them
in
a
way
that,
and
that
not
only
explains
what
we're
doing,
but
also
like
really
gets
people
excited
about
what
we're
doing
and
gets
people
to
be.
Like
hey
like,
I
want
to
also
like
do
that
and
so
and
so
yeah
tom.
E
A
B
A
Oh
no,
okay
and
then
I
guess
for
the
for
the
last,
like
two
minutes
here,
I'm
gonna,
I
guess
tim-
do
you
wanna
come
on
and
do
like
a
little
outro
with
me
and
talk
about
what
we
might
do
with
the
govcoms
with
the
govcoms
bit
all
right
cool,
because
I
know
governance
communications
is
a
really
really
cool
working
group
that
has
been
that
has
been
around
for
a
little
bit
and
I
definitely
don't
want
to.
I
want
it
to
be
mentioned
a
little
bit.
B
Yeah,
it's
a
good
transition
from
tom,
so
you
can
think
of
the
messaging
team
as
sort
of
the
umbrella
in
which
there
are
different
initiatives
to
be
messaged
about
one
of
those
is
the
problem
space
of
governance,
communications,
I'm
sure
everyone
has
seen
the
relay
at
least
a
little
bit.
Hopefully,
if
you
haven't
check
out
maker
relay
it's
a
tag
on
the
forum,
it's
also
in
the
updates
category.
It
should
be
there
all
the
time,
but
it's
basically.
B
As
you
know,
that's
what
sort
of
domain
teams
eventually
do
and
so
considering
maker
relay
is
an
experiment
we're
conducting
a
few
more.
We
just
want
to
sort
of
make
it
known
to
governance
that
we
want
to
sort
of
start
to
experiment
with
speaking
on
their
behalf
and
speaking
to
governance,
but
it's
a
hairy
problem
and
I
have
a
presentation
about
it.
So
we'll
talk
about
another
at
another
time.
A
Right
on,
thank
you
so
much
tim
and
with
that
it's
1
p.m.
Happy
tuesday,
everybody!
Well,
it's
1
p.m!
For
me,
it's
it's
the
top
of
the
hour
for
many
of
you,
and
so
with
that.
I
hope
you
all
have
a
really
fantastic
tuesday
and
we
will
see
you
next
tuesday
or
in
the
chat
or
in
the
forum,
but
yeah
hope
you
enjoyed
this.
We
definitely
did
so
take
care.