►
Description
Timecodes:
00:00 - Intentions and distractions
03:12 - Transparency blogpost
03:55 - Content distribution board
26:38 - Website CMS
32:54 - Hatch video
36:21 - Manu updates
37:10 - TEC Bi weekly blog
39 - Spotlight for community call
42:05 - Hatch DAO being his own product!
🙏 Thank you for watching! Hit 👍 and subscribe 🚩 to support this work
🌱Join the Community🌱
on Discord https://discord.gg/uM4ZWDjNfK
or say hello on Telegram https://t.me/tecommons
Join the conversation https://forum.tecommons.org/
Follow us on Twitter: https://twitter.com/tecmns
Learn more http://tecommons.org/
Check out our Glossary: https://token-engineering-commons.gitbook.io/tec-handbook/glossary
E
A
F
G
G
A
Thank
you
very
much,
juan
yeah
good
at
you,
man,
transparency,
working,
good,
blog
post.
We
did
mentioned
that
couple
of
times
in
our
working
in
our
intercoms
channel,
please
whoever
can
open
that
link.
Go
through
that
if
you
can
review
it,
add
your
comments,
notes,
suggestions
whatever
so
that
it
can
be
published
this
week.
Yeah!
A
That's
for
that
part!
Nate
thanks
a
lot
for
sharing
the
link.
Let
me
just
check
it.
First,
there's
a
bunch
of
stuff
to
read
there.
So
maybe
we
don't
want
to
go
through
that
document
right
now,
so
I
think
everybody
else
should
just
read
it
later
on
nate.
Do
you
want
to
go
through
the
3d
board
that
we
did
or
how
do
we
want
to
approach.
E
So
one
of
the
big
issues
that
we
wanted
to
address
was
the
kind
of
creating
a
central
location
for
the
content
distribution
strategy.
So
access
to
this
process
could
be
you
know,
obtained
by
anyone
within
the
community,
so
they're
really
we're
gonna
utilize,
the
zenhub
workspace
board,
and
so
we're
gonna
have
a,
I
believe
in
the
the
content
distribution
process,
repo
we're
gonna
have
a
board
and
the
board's
gonna
have
seven
stages.
The
first
stage
is
going
to
be
the
content,
ideas
and
requests,
and
so
this
is.
E
This
concept
is
kind
of
like.
Instead
of
having
this
kind
of
a
signer
assignee
relationship
between
content
creators
and
content
requesters,
we
have
just
working
groups
or
members
of
the
community
who
identify
needs
within
their
working
groups
and
say
hey.
We
need
this
type
of
content
created
on
behalf
of
that
working
group
and
we
can
post
it
within
the
ideas
and
requests.
E
If
content
creator
is
done
with
the
document,
they
can
switch
within
the
issue,
a
request
for
editing
and
the
editing
we
were
wanting
to
separate
into
two
sections.
I
know
marco
and
I
discussed
this
kind
of
difficult
to
decide
who
is
going
to
be
editors
and
who
is
not
going
to
be
editors
but
instead
of
decide
defining
roles
with
among
community
members.
I'd
rather
see
it
be
open
to
anyone
and
have
you
know
a
real
focus
on
acknowledging
the
working
group
that
that
particular
content
piece
was
geared
for.
E
So
if
it's
something
that
is,
you
know
technically
related,
we
want
the
working
group.
That's
you
know.
If
it's
on
parameters,
we
want
the
parameter
working
group
members
to
actually
be
the
ones
to
be
looking
at
the
constant
review
aspect
of
it
making
sure
for
quality.
You
know
messaging
and
and
value,
and
then
once
the
content
review
process
is
done,
it
will
go
to
a
copy
editing
process
where
we
have
anybody.
E
This
pipeline,
there's
going
to
be
a
lot
of
you
know
permissions
that
need
to
be
worked
out
and
and
and
processes
that
need
to
be
established.
That
are
small,
but
can
be
done.
You
know
transparently,
but
it
it
really
does
require
community
feedback
on
how
this
is
going
to
be
implemented
and
whether
we
commit
ourselves
to
actually
putting
this
into
practice,
because
I
do
think
that
once
we
put
it
into
practice,
we're
going
to
have
a
very
you
know:
it'll
become
more
efficient
and
more
streamlined.
E
A
Well,
one
major
thing
is:
first,
we
we're,
probably
gonna
need
the
person
who
will
be
pm'ing,
this
kind
of
distribution
process
for
starters,
nate
volunteered
to
do
that
for
now,
but
like
in
the
future,
we
want
to
have
a
dedicated
person,
so
we
we
definitely
need
to
figure
out
how
we
want
to
how
we
can
scale
our
people
here.
That's
that's
really
important
and
then
the
second
thing
where
we're
gonna
be
needing
assistance
from
from
from
you
guys
or
from
everybody.
A
A
So,
like
that's
the
approved
sage,
so
you
know
expect
someone
to
just
mention
you
ping,
you
you
take
a
look,
and
maybe
say
yes,
that's
fine,
it's
good
or
not,
or
we
discuss
in
our
weekly
course
something
like
that.
Then,
on
the
writing
stage,
that's
fine
and
then
also
the
writer
author
of
this
piece
could
be.
It
doesn't
have
to
be
a
written
piece.
It
can
be
a
video,
it
can
be
a
blog
post,
it
can
be
whatever
they
can
basically
suggest
who
they
want
this
to
review.
A
So,
for
example,
it
could
be
a
technic,
maybe
a
technical
issue
that
they
think
the
best
person
to
review
is
someone
from
the
some
token
engineer.
Maybe
or
you
know
they
can
review,
and
they
can
mention
those
people
as
reviewers,
similarly
to
what
we
do
in
the
coordination
repo
as
well.
So
whenever
you
get
tagged,
it
would
be
nice
to
respond
to
that.
A
You
don't
have
to
it's,
that's
you,
but
but
yeah
would
be
nice
or
then,
if
you
think,
like
someone
else,
should
also
review
that
you
can
also
mention
them
as
well.
So
like
this
is
that's
the
second
step
where
broader
involvement
from
the
group
is
needed
and
then,
like
that's
the
editing
stage.
Final
edits
is
done
by
the
author.
Pre-Published
checklist
is
something
that
we
need
to
first
establish
it's
something
to
be
defined.
A
Now
I
call
this
column
ready
for
ivy
just
so
because,
like
iv
is
already
doing
that,
but
it's
not
not
an
intention
to
put
it
on
ivy,
but
just
to
to
show
you
that
we
need
one
person
who
will
then
be
responsible
for
taking
that
piece
and
then
setting
up
this
further
through
the
distribution
funnel.
So
you
know
creating
tweets,
creating,
maybe
twitter
threads
publishing
on
on
medium
scheduling,
everything
putting
it
in
the
calendar
and
what
what
what
so
on
and
so
forth.
A
So
that's
like
a
second
person
we
need
for
for
the
content,
distribution
so
and
yeah,
and
after
it's
it's
scheduled
that
that
means
it's
in
our
calendar.
It
will
go
out
eventually,
whenever
it's
scheduled
and
once
it's
done,
it
will
be
just
published
and
that's
basically
it
so
yeah.
That's
roughly
the
plan,
and
maybe
we
just
go
around.
I
don't
know
maybe
a
minute
or
two
everybody's
feedback
who
wants
to
go
first.
A
H
I
I
think
it's
I
think
it's
really
nice
to
have
a
dedicated
stream
and
like
right
now
you
know
all
the
other
working
groups
are.
I
I
think
this
is
inspiring
to
other
working
groups
too,
to
start
having
your
own
dedicated
stream
of
process.
I
feel
like
a
couple
groups
kind
of
do
it.
You
guys
are
nailing
it
down
and
really
making
the
flow
work
for
you,
and
you
know
what's
most
important-
is
that
we
have
a
good
starting
point
and
then
we
will
discover
more
improvements
along
the
way.
B
Okay,
I
like
it
the
only
thing
I
will
try
to
understand
it's
the
tone.
The
tone
section
like
how
do
we
have
a
thin
tone
in
text
or
in
the
pieces
of
our
code
are
going
to
be
published,
so
I
mean
we
need
to.
I
mean
everyone
as
a
writer
have
their
own
tone
and
their
own
way
of
expressing,
but
it
would
be
nice
that
the
articles
are
sort
of
aligned
all
day
or
at
least,
if
it's
related
to
the
same
topic
that
we
have
online
in
the
tone.
E
But
as
time
goes
on,
we'll
we'll
see
that
you
know,
as
we
scale
we'll
have
members
who
are
really
dedicated
to
actual
content
creation
and
that
you
know
we'll
have
you
know
a
handful
of
writers
who
are
very
good
at
creating
a
a
solid
voice
for
the
community
and
will
probably
be
relied
upon
for
the
most
part,
but
that
that's
in
the
future.
And
so
I,
I
think,
that's
a
short
tune
problem.
A
Yeah
great
great
comment
from
eduardo
and
and
guys,
if
you
spot
anything
else
that
is
missing
and
as
and
also
as
griff
said,
we're
gonna
be
refining
this
and
finding
some
things
for
improvement
along
the
way.
This
is
like
really
for
the
starters,
but
like
ton
of
boys,
or
something
like
that.
Maybe
we
should
have
guidelines
or
something
like
that
written
up
front
and
also,
like
you
know,
tag
like
all
already
somewhere
like
linked,
always
visible
when
creating
a
new
issue
or
idea
or
always
pinned
at
the
top.
A
So
it's
visible
for
everyone
before
you
start.
Please
read
this
or
something
like
that
and
then
secondly,
it
can
go
into
pre-published
checklists
as
well
so
for
for
whoever
is,
like
you
know,
doing
a
check
before
it's
going
to
pre-publishing
or
even
the
author
can
do
that
we'll
we'll
decide
on
that.
They
just
go
to
the
checklist
and
check
that
say
cool.
That's
fine!
I'm
moving
forward!
B
A
So
for
now,
as
far
as
I
understand,
we
do
have
kind
of
like
a
distribution,
not
a
process
but
like
where,
where
the
content
pieces
are
going
out
and
where
they
need
to
be
published
until
until
we
actually
kick
off
this
for
real.
I
think
we
should
like
just
publish
these
pieces
that
we
have
right
now.
So
it's
like
not
not
blocking
anything
and
then
like.
The
next
thing
that
goes
in
here
goes
to
this
life
cycle
and-
and
we
take
it
for,
like
start
fresh.
C
C
There
are
certain
things
that
we
need
to
respect,
because
it's
important
for
either
legal
reasons
or
just
you
know,
making
sure
we
have
a
cohesive
message
and
I
think
that's
some
something
that's
really
important
in
the
style
guide
and
then
I
would
say
everyone's
gonna
have
their
own
voice
anyway,
but
then
there's
probably
gonna
be
like
one
thing
that
comes
from
like
te
commons,
you
know
that's
like
group
efforts
which
will
sort
of
have
to
have
more
of
a
a
different
perspective.
Maybe
like
that.
C
It's
like
the
official
t,
like
the
official
things
that
are
posted
and
then
it's
like
all
all
the
people
who
are
contributing,
who
are
posting
information
and
sharing
information
too,
and
I
think
that
having
different
voices
is
actually
really
neat.
So
I
think
that's
that's
going
to
be
good
too.
I
didn't
have
a
chance
to
read
the
document,
I'm
just
seeing
it
now
for
the
first
time
so
I'll
be
able
to
give
more
feedback
when
I
look
at
it,
but
really
great
start
so
far
and
I'll
pass
to
craig.
If
we're
passing.
I
I
I
But
what
I'm
gleaning
from
the
conversation
is
that
yeah
content
distribution
there's
going
to
be
a
life
cycle
starting
sort
of
soon
once
we
get
this
next
round
of
docs
out,
so
I
think
that's
great
I'm
behind.
I
just
need
to
catch
up,
and
I
so
later
today,
hopefully
I'm
not
sure
who
has
not
gone
so
somebody
else
can
take
it.
D
A
So
the
first
person
we're
looking
for
is
pm,
who
will
be
managing
this
board
and
then
the
second
person
is
the
distributor
who
will
be
taking
on
the
the
finished
pieces
or
whatever
content.
There
is
doing
a
pre-publishing
checklist
and
scheduling
the
distribution
nate,
and
I
talked
about
the
distribution
person
since
ivy's
already
doing
that
and
managing
our
twitter
schedule
to
ask
her
if
she
might
have
time.
If
not,
then
we
might
just
need
another
person
for
that.
Okay,.
D
C
A
D
G
I
just
saw
this
document
today,
but
I
am
reading
it
and
I
love
the
purpose
because
it
says
the
the
intention
behind
this
is
to
not
create
a
signal,
a
significance
within
pc,
but
to
simply
state
our
content
needs
based
on
a
set
of
external
and
internal
communication
goals.
I
think
that,
like
summarize,
very
well
a
great
idea,
and
it
can
also
like
foster
collaboration
between
people
that
can
take
some
of
the
content
needs
and
help
producing
that
content
for
the
different
working
groups.
So
I
think
it's
a
really
great.
F
E
I
just
wanted
to
add
that
I
do
think
it's
very
important
like
because
every
time
we
create
a
new
process
and
even
if
it's
especially
when
it's
really
effective,
that
when
we
have
new
members
coming
to
the
the
community,
that
these
processes
need
to
be
integrated
within
the
onboarding
processes
and
making
sure
that
you
know
the
people
who
are
doing
onboarding
are
able
to
go
through
this
process
and
teach
people.
This
is
how
you
go
through
this.
A
Yeah-
and
I
just
want
to
add
to
that-
also
that
one
of
the
things
that
they
suggested
during
the
onboarding-
we
might
even
ask
people
like
you
know
if
they're,
if
they
want
to
write
something.
You
know
why
not.
You
know
tell
us
why
you're
here
and
what
excites
you
most
and
do
want
to
write
something
for
us.
It
doesn't
have
to
be
mandatory,
but
yeah
during
the
onboarding.
A
We
might
also
want
to
do
that,
and
also
one
of
the
things
since
publishing
or
actually
submitting
ideas
and
requests
for
new
content
requires
a
person
to
have
a
github
account.
We
might
want
to
ask
that
person
during
the
onboarding.
Do
they
have
a
github
account
or
something
just
to
make
sure
they
they
do.
A
C
A
Yeah,
that
was
my
conditional
idea
when
we,
when
we
migrated
the
new
discord
server,
to
have
this
kind
of
like
part
of
the
onboarding
flow,
where
we
can
try
kind
of
to
map
that
person
to
see
where,
where
they
are
with
a
couple
of
questions
or
whatever
the
automated
or
something
like
that.
So
we
we
get
their
interest.
A
So
we
can
then
like
guide
them
through
the
dedicated
working
group
or
you
know
whatever,
but
this
we're
gonna
transition
now
into
the
second
agenda
topic,
which
is
we're
migrating
a
new
website
old
website
from
wordpress
to
network,
and
we're
going
to
be
updating
that.
I
think
that
goes
along
with
what
we're
talking
right
now,
because
we're
going
to
create
a
new
dedicated
set
page
for
joining
the
tec
community.
A
We
have
a
plenty
of
room
there
to
talk
about
whatever
we
want
and
maybe
on
board
people
properly.
That's
number
one
thing,
and
then
the
second
thing
is
also
on
the
discord
as
a
first
channel
that
will
be
joining,
we
might
have
just
a
a
list
of
useful
links
and
resources
for
people
when
they
first
time
join.
So
they
know
I.
This
is
the
forum
here.
You
can
read
more
about
parameters
like
here.
A
You
can
read
more
working
groups
here,
you
can
read
about
whatever
interests
you
and
now
go
ahead
and
explore,
and
also
nate,
and
I
were
discussing
about
having
like
a
central
place.
Currently
we
have
git
book
now
for
for
all
the
resources
and
stuff,
so
either
it's
it's
gonna
be
git
book
or
we
might
even
have
a
section
on
our
website
with,
like
all
the
resources
that
we're
going
to
be
updating
updating
throughout
the
time
right.
A
So
it
could
be
something,
for
example,
if
you're
looking
for
something
you
don't
being
a
person
hey.
Where
can
I
find
this?
No,
you
just
go
to
that
one
single
page
and
you
know
exactly
we're.
Gonna
find
that
thing
there
right
beat
the
wiki
beat
the
kit
book
or
you
know
whatever
we're
gonna
be
using,
but
I
think
it's
important
that
we
have
that
as
well.
C
A
It's
not
an
archive
for
me.
It's
like,
I
think
it's
more
information
like
and
also
where
do
I
submit
content
to
be
published
or
how
can
I
contribute
to
you
know
writing
or
where
do
I
submit
there
or
where
can
I
find
this
information,
or
where
can
I
find
the
logo
of
the
tc,
for
example,
because,
like
you
know,
I
share
that
couple
of
times.
I
pinned
that
right,
but
if
we
just
have
like
you
know
one
place,
for
example,
the
forms
that
you
know
graviton
group
is
using.
A
Yeah
exactly
so
it
kind
of
it
is.
I
think
it
is
already
a
git
book,
so
either
we
it
is,
it
will
be
there
and
it
will
maintain
it
there
or
we
will
have
maybe
another
page
on
our
website
that
is
publicly
available
and
maybe
for
other
stuff
that
are
just
for
us
internally.
Maybe
we
can
have
a
pass
protected
page
where
you
can
just
access
some
something.
A
C
C
A
A
No
worries
no
worries:
anyways
yeah
anyway,
christopher
is
working
on
a
website,
migration
and
we're.
Finally,
gonna
have
a
custom
front
end.
I'm
super
happy
about
it,
because
we
can
make
everything
nice
responsive
and
we
have
the
freedom
to
do
whatever
we
want.
So
for
that
we
created
a
new,
separate
repo,
which
is
called
tc
web
and
everything
that
is
related
to
reporting
bugs
suggestions
upgrades
whatever
needs
requirements.
A
You
can
create
an
issue
there
or
you
can
create
an
issue
in
the
coordination
and
I'm
gonna
paste
that
issue
there
or
whatever
works
for
you
no
worries,
but
we
just
wanna
have
a
separate
repo
for
that
to
keep
it
clean
and
yeah.
I
think
that's
it
for
that
for
the
website
and
also
like
in
the
future,
we
plan
to
upgrade
and
update
the
website
with
more
content.
A
I'm
also
thinking
about
maybe
a
dedicated
session
section
for
the
working
groups,
just
to
give
a
brief
overview,
what
they
are
a
quick
introduction
and
links
to
join
them
in
the
discord
or
forum,
or
something
like
that
we'll
see.
These
are
the
future
updates
for
the
website.
If
you
have
any
suggestions,
please
go
ahead
and
create
an
issue.
A
Website
all
right,
nope
next
up
next
up,
I'm
just
gonna
skip
these
two
agenda
items
and
just
remind
you
again
for
the
transparency
working
group
blog
post,
that
needs
to
review
and
wants
to
go
live
this
week.
So
please,
if
you
can
take
a
look
read
it
leave
your
comment
there
or
something
so
that
they
can
distribute
it
this
week,
what
else
yeah
current
content
pieces
and
distributions
what
we
have
on
the
zenhub
board?
Maybe
just
a
you
know,
quick
update
from
edu,
I
think
eduardo.
A
B
That
at
right
now
there
is
a
mixed
opinion
about
the
the
that
post.
For
me,
it's
ready,
at
least
for
the
forum
tim
mentioned-
the
fact
that
it
needs
to
still
be
reviewed,
grief
added
some
comments
on
it
past
time.
So
if
there
is
no
other
comment
further,
besides
the
grief
and
time
comments,
I
will,
I
will
have
it
tomorrow
and
then
there
is
this.
B
B
D
B
B
A
A
Onboarding
video,
he.
I
also
talked
with
him
or
chatted
with
him
last
week,
so
he
is
very,
very
confident
that
he
will
be
delivering
that
within
the
sprint.
That's
the
recent
update
that
we
got.
I
haven't
seen
any
drafts
yet,
but
you
know
if
manu
said
he's
going
to
deliver,
then
he's
going
to
deliver.
So
that's
for
that
part
and
then
the
last
thing
yeah
tec,
bi-weekly
blog
post
craig,
is
on
vacation
for
the
next
two
weeks.
A
H
C
Cool
a
quick
fill
in
on
the
process,
so
during
the
tec
community
stewards
call,
we
propose
a
list
of
subjects,
topics
that
are
eligible
for
the
blog
post
and
we
prioritize
them
and
then
basically
you
can
just
use
that
list
and
talk.
You
know,
take
the
top
priorities
and
expand.
You
know
write
a
little
blurb
about
each
each
one
and
I'll
send
you.
You
have
the
examples
of
the
last
blog
posts
that
craig
and
jessica
have
been
doing
so.
C
A
A
F
H
H
A
And
yeah,
and
also
like
jake,
has
an
open
issue
to
to
actually
record
a
video
walkthrough
of
the
hatch.
You
know
choosing
the
parameters
so
like
if
that
can
be
done
on
that
same
call,
and
we
just
record
that-
and
we
like
cut
it
out
later
on
into
like
a
just
that
part
of
the
video
where
he
does
the
walkthrough
then
like
we,
we
have.
We
close
two
issues
at
once.
A
H
B
Sorry
on
that
matter,
because
sorry
on
that
matter,
because
of
the
I
mean
the
looking
for
the
speaker
every
week
goes
all
on
the
line
of
the
proposals
and
from
hatch
outreach.
We
will
need
more
help
from
comms
looking
for
projects,
I
have
a
list
that
we
will
tackle
from
from
bitcoin,
but
it
will
be
nice
if
we
prepare
some
kind
of
content,
eventually
down
the
line
to
incentivize
people
to
propose
to
the
dac
in
the
forum.
B
A
H
H
H
Have
that
approach
or
have
that
mindset
with
with
hatchers
with
with
our
comms,
when
we
start
talking
about
the
hatch
in
phase
one
that
we,
you
know
say
like
yeah,
we're
gonna
start
out
through
through
this
really
cool
method,
where
we,
where
we
become
a
doubt,
the
intention
of
that
dao
is
to
upgrade.
But,
like
you
know,
hey
this,
this
dow
thing
is
something
that
the
whole
world
can
reuse.
It's
gonna
be
a
complete
product
in
itself
and
yeah.
I
just
that
framing
is
what
I'm
really.
H
Yeah,
it
could
be
its
own
post.
I
mean
that's,
that's
that's
a
great
idea.
The
other
thing
is
just
when
we
talk
about
it.
I
feel
like
we
often
like
relegate
it
to
just
like
phase
one,
and
when
we
speak
about
it,
we
should
be
like
dude
we're
starting
out
as
the
coolest
dow
ever
you
know
like
this.
This
thing
is
wild.
H
Like
the
way
we
do
impact
hours
like
we
always
we
barely
even
talk
about
the
impact,
our
stuff,
you
know,
but
it's
so
cool,
aligning
the
incentive
of
the
team
that
made
it
happen
with
the
stakeholders
with
the
people,
adding
financial
and
that
interplay
is
I've,
never
seen
any
project
do
that.
You
know
and
yeah
we're
really
cool
we're
using
toku.
H
I
I
mean
the
community
design
approach
like
we're
just
about
to
really
launch
this
thing,
and
so,
if
we
just
talk
about
it
as
like
phase
one,
then
no
one's
really
going
to
be
excited
about
participating.
But
if
we
talk
about
it
as
like
whoa
look
at
this
new
way
to
do
dao's.
This
is
the
way
to
do
dallas
for
from
here
to
eternity
you
shouldn't.
Do
it
any
other
way?
This
is
butter.
This
is
like
better
than
sliced
bread.
You
know
this
is.
This
is
delicious.
We
we
want
to
be
in
this
yeah.
H
No
because
the
legal
side
of
it
is
that's,
what's
well,
that's,
what's
kind
of
the
dicey,
that's
why
we
need
this
with
swiss
membership.
However,
if
it's
a
blockchain
for
good
down,
they
want
to
use
our
legal
strategy
that
is
plug
and
play
as
well,
but
like
in
some
ways,
it's
easier
to
start
things
as
a
source
credow,
and
that,
like
I,
wouldn't
I
wouldn't
say
that
our
legal
strategy
is
the
best
all
right.
Okay,
our
legal
strategy,
for
what
we
want
to
do
is
the
best
but
like
because
these
hashtags
are
are
closed.
H
They
have
like
more
weird
legal
thing
issues,
but
that
being
said,
everyone
who
puts
money
in
instantly
loses
money,
so
it's
not
an
investment
which
is
pretty
cool.
That's
what
makes
molok
dao
so
great.
Is
that
like,
and
everyone
who
puts
money
in
on
the
legal
side
like
they
don't
have
to
worry
about
it
because,
like
they
know,
they're
going
to
lose
money,
but
yeah.
A
I
had
just
more
questions.
I
took
notes
for
what
you
were
saying:
productizing,
the
hatch
dial.
Does
that
mean,
for
example,
we
should
have
like
a
dedicated
page,
where
we
talk
about
just
a
hatch
style,
with
links
and
resources
for
people
to
grab
the
code
and
stereo
kickstart
their
own
now
with
our
with
our
product.