►
Description
In the Stewards Working Group the Community Stewards come together to coordinate workstreams, share experiences and reflect on what is going well and what can be done better in order to achieve the mission of the TEC and best serve our community.
Find us on the #stewards channel on our Discord!
We gather every Wednesday at 7pm CET.
Steward: Tam
Timecodes:
00:00 - Temperature check
13:09 - Spotlight
14:52 - Gitcoin Grant
16:02 - Comunitas WG
24:55 - Twitter
25:37 - Community Survey
27:17 - Ostrom's principles
29:23 - Proposals
56:23 - Topics for the blog
🙏 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/
B
Thank
you
tim
thank
you
check
quite
excited
for
the
humidity
community,
that's
working
group,
so
that's
like
driving
my
boat.
If
you
wanna
rocking
my
boat,
as
you
may
saying,
I
don't
remember
the
expression.
Besides
that
I
don't
know.
I
feel
that
this
I
thought
I
I
felt
certain
confusion
when,
in
the
in
the
community
stewards
on
telegram
channel,
there
was
small
discussions
about
the
public
governance
and
the
choosing
the
things
for
giving
permission
or
not
to
people,
so
that,
for
me,
was
a
little
bit
like
tricky.
B
I
felt
we
were
like
caught
in
a
loophole
for
some
reason,
and
I
felt
that
this.
That
is
something
that
we
have
sort
of.
Maybe
I
felt
underrated
and
it
would
be
nice
to
sort
of
give
a
little
bit
of
relevance
about
this
poly
governance
decision
making
and
how
it
will
come
down
the
line
in
in
the
near
future.
C
D
Thanks
yeah,
actually,
on
that
topic
I
think
we
are.
We
are
reaching
a
really
interesting
level
of
complexity
with
with
our
governance,
and
that
was
the
whole
softcup
call
about.
That's
that's
what
it
was
about
yesterday,
just
trying
to
understand
how
do
we
take
the
decisions
that
we
need
to
take
and
I
feel
like
it's
a
very
mature
point,
because
we
have
many
many
tools
and
we
have
many
educated
people
in
how
to
go
about
this
decision.
So
it's
been
like
very
fruitful
conversations
and
yeah.
D
E
F
Thanks
chris
yeah,
I
feel
I
I
feel
that
we're
also
like
in
in
familiar
grounds.
Let's
say
like
we,
we
have
definitely
dealt
with
higher
temperatures
and
yeah.
I
feel
that,
right
now,
it's
it's
really
good.
It's
really
good
ground
for
asking
like
where
this
is
going.
How
are
we
gonna
improve
it,
based
on
our
experience
and
and
yeah?
It
makes
me
feel
confident
and.
A
G
Hello,
chewie,
hello,
everyone
well.
My
temperature
check
today
has
been
like
a
very
important
day
because,
like
we
were
trying
to
reschedule
our
return
to
colombia,
but
like
it
seems
that
we
we
are
going
to
travel
tomorrow
and
yeah,
I'm
happy
about
it,
but
at
the
same
time
I
was
also
ready
to
stay
more
days
but
well
yeah.
H
Thanks
wonka
yeah
well,
like
I
told
suga
chewie
nedu
on
the
ama
on
the
welcome
call,
I'm
exploring
the
like
a
a
proposal
or
or
just
like
a
system
for
diagramming,
I
kind
of
want
to
pick
up
where
github
and
senhob
and
and
make
it
more
granular.
I
think
it's
it's
it's
not
a
tc
problem,
but
a
dow
problem,
and
really
is
it's
it's
it's
the
same
vein
of
the
forum
post
from
anne
marie,
say:
okay,
how
do
we
make
it
people
on
board
easier?
H
They
just
it's
sort
of
like
a
plug
and
play
framework
and
yeah.
I
was
thinking
of
like
making
a
version
of
uml
and
that
would
be
compatible
with
you
know
the
issues
and
the
the
business
processes
that
go
in
inside
a
dial.
So
this
is
something
that
I
talk
with
chewy.
I
see
it
as
something
between
comms
and
transparency,
maybe
related
with
the
communities
working
group,
which
is
a
new
working
group
that
is
being
assembled.
H
So
I
don't
know,
I
think,
there's
a
void
and-
and
I
want
to
feel
it
so
I'm
just
exploring
it
I'd-
be
interested
in
talking
with
tom
or
chris
later
about
this,
but
yeah.
That's
something
that
I'm
I'm
exploring
and
I'm
I'm
very
excited
about.
Hopefully
I
can
contribute
with
that
later
on.
I
don't
overthink
it
too
much.
I
just
know:
there's
a
void.
It's
been
stated
several
times
explicitly
by
members.
I've
encountered
myself
and
I
just
trying
to
find
the
right
solution
for
it.
I
I
F
C
I
C
Thanks
yeah,
so
that's
on
the
radar
and
also
I'll
just
I
just
wanted
to
add
thanks
to
all
of
you
for
adding
to
the
stewards
working
groups
contributor
wish
list,
so
that's
pretty
much
complete
now.
So
I'm
excited
to
be
able
to
share
that
and
later
I
think,
to
talk
about
communitas
a
bit
back
to
you
to
tim
thanks.
A
So
it
feels
like
it
just
feels
like
we
have
really
good
momentum
and
I'd
like
us
to
to
key.
I
mean
everyone
here
would
like
us
to
keep
it.
Of
course,
I'm
really
interested
in
chatting
with
manu
and
hearing
more
about
what
it
is
that
you
were
talking
about
and
what
void
as
well.
So
maybe
we
can
spend
some
time
later
this
week,
doing
that,
and
I
guess
I'll
say
yeah,
you
know
I
feel
a
little
bit
like
we,
and
this
is
my
own
responsibility.
A
I
think
like
we're
still
getting
the
like.
Okay,
critical
to
commons,
upgrade
together
on
the
mirror
board
and
I'd
really
like
by
you
know
the
mid
to
end
of
the
sprint,
we're
probably
in
the
middle
of
the
sprint,
now
to
actually
have
it
in
a
form
that
is
shareable
with
everyone.
Most
importantly
hatchers,
but
ourselves
as
well
about
my
time
and
I'll
pass
to
santi.
Welcome
santi.
A
J
Okay,
I'm
I'm
really
excited
to
see
how
tui
mon
manu,
nate
and
and
and
the
comms
group
our
community
group
are-
are
starting
to
launch
this.
I,
I
really
think
it's
a
great
it's
a
great
idea,
and-
and
it's
also,
as
you
mentioned,
the
result
of
the
growth
that
we
are
having
if
we
were
not
having
growth,
we
probably
would
have
would
have
not
thought
of
of
creating
a
a
working
group
dealing
with
with
the
community,
although
it's
always
important.
J
A
Nope,
that's
it
cool,
so
I
want
to
share
that.
You
know
the
last
few
times
we've
had
this.
This
weekly
stewards
call
we've
really
run
out
of
time
before
we
really
got
to
talk
about
some
group
updates
or
even
check
the
board.
So
I've
been
trying
to
figure
out
how
we
can
make
this
make
time
for
all
of
the
stewards
and
active
community
members
to
really
get
together
and
talk
about
issues
that
need
our
attention
that
need
discussion.
A
That
needs
some
sort
of
multiple
perspectives,
but
that
we
benefit
from
doing
it
in
real
time
like
this
versus
in
the
forum
or
discord
or
telegram
and
still
being
able
to
do
coordination-
and
I
thought
one
thing
we
could
do-
is
sort
of
tease
apart
a
weekly
coordination
which
still
has
to
happen
to
keep
us
moving
forward
and
having
a
council
where
we're
not
doing
any
coordination.
But
what
we
are
doing
is
collaborating
on
solutions
and
problem
solving
and
future
planning,
and
so
I
thought
every
other
thursday.
A
We
have
a
sprint
retrospective
and
the
thursday
that
we
don't
have
a
sprint
retrospective.
We
could
hold
a
stewards
council,
and
that
would
be
for
specifically
what
kinds
of
you
know
what's
on
our
docket
to
discuss
this
week
or
this
sprint,
so
that
we
can
spend
some
time
talking
about
it
by
a
show
of
hands,
or
at
least
a
show
of
yays
or
nays.
I
don't
know
how
to
do
this
one.
I
can't
see
anyone
can
can
people
just
let
me
know
if
they
agree.
A
A
There
will
be
a
separate
agenda
for
the
council
and
I
welcome
anyone
to
go
into
it
and
add
into
the
agenda
and
also
just
email
me
or
whatever
message
me
if
you
think
that
there's
something
that
we
need
to
discuss
it'll
be
one
hour
for
focus
discussion,
so
I
think
that'll
help
a
lot
cool
spotlight
for
tomorrow.
How
are
we
doing?
Oh
nate
is
not
here
so
who
to
ask:
let's
see
if
there's
something
in
our
spreadsheet.
A
A
E
B
A
Anyone
anyone
go
to
the
mentions
and
just
see
who
needs
their
attention
on
something.
Is
this
just
your
friendly
weekly
reminder
that
github
notifications
exist
and
it's
a
really
nice
way
to
answer
questions
when
people
have
questions
specifically
for
you.
This
mentioned
here
is
like
amazing.
You
can
also
see
like
if
you're
participating
in
something
what's
going
on
with
it,
but
I
like
I,
I
go
here
first.
This
is
my
my
go-to
space,
all
right
that
was
just
a
friendly
reminder:
bitcoin
grants
around
11.
craig
cannot
join
us.
A
He
is
officially
on
jury
duty,
but
he
did
volunteer
to
do
a
tec,
genera,
general
or
generic
bitcoin
grant.
I
thought
it
was
worth
taking
this
moment,
because
a
lot
of
our
stewards
and
active
community
members
have
other
projects
that
they're
working
on
so
the
for
one
one
point
is
to
say:
hey
if
there's
something
that
you're
working
on
now
is
a
good
time
to
put
your
grant
together.
A
The
second
thing
I
wanted
to
ask-
and
I
think
I
I
did
ask
in
the
in
the
issue
itself
that
that's
raised
for
this
was-
is
there
anything
we
need
to
change,
because
all
of
our
grants
previously
had
been
before
the
hatch,
and
there
might
be
something
that
we'll
want
to
change,
because
now
we've
hatched-
and
I
don't
know
whether
it's
the
wording
or
the
ask,
or
what
have
you?
Maybe
we
need
to
have
something
more
specific.
A
C
Cool
thanks
a
lot
tam,
so
yeah
we,
as
you
know,
I've
been
working
a
lot
in
orientation
and
finally,
we've
come
to
the
moment
where
we
think
we've
got
a
great
idea
for
a
new
working
group
that
incorporates
not
only
orientation
but
notably
what
we've
been
calling
community
building.
So
we've
called
it
communitas
and
tam.
C
So
if
you
have
a
look
at
the
the
definition
we
put
it
up
there.
So
communitas
is
a
latin
term
commonly
referring
either
to
an
unstructured
community
in
which
people
are
equal
or
to
the
very
spirit
of
community
community
communitas
refers
to
an
unstructured
state
in
which
all
members
of
a
community
are
equal,
allowing
them
to
share
common
experience,
usually
through
a
rite
of
passage,
and
of
course,
that
is
what
we
think
sort
of
embodies.
C
The
spirit
of
what
we're
doing
through
both
helping
folks
enter
the
tec
and
navigate
as
new
contributors
new
members,
but
also
to
support
members
already
in
the
tec
and
to
just
foster
nurture
build
that
community.
So
if
you
have
a
look
at
the
working
group,
you'll
see
that
we
are
interested
in
in,
and
I
want
to
look
at
the
areas
that
are
on
our
radar.
So
we've
included
some
the
main
again.
The
main
idea
is
orientation
and
community
building.
C
C
Any
all
of
the
projects,
outreach
tec
services
and
this
kind
of
thing-
and
so
edo
has
been
working
with
me
closely
on
this,
and
so
has
anna
marie
we've
also
had
support
from,
of
course,
vi
and
from
nick,
and
also
I
haven't,
and
also
a
bit
nate
was
was
sort
of
jumping
in
previously
with
some
orientation
stuff.
But
I
have
yet
to
sort
of
sync
with
everybody,
but
we're
just
trying
to
mostly
for
now
it's
been
me
and
edo
and
anna
marie.
C
B
Thank
you.
No,
I
think
it
pretty
much
corral.
Part
of
the
interest
of
this
is
also
having
processes
improved
when
talking
about
pathways
for
new
people
pathways
for
proposals
pathways
for
contributors
there
by
by
ib,
is
also
helping
us
building
a
bug
that
will
be
sort
of
a
welcoming
bot.
We
also
are
proposing
the
tc
lounge
to
be
changed.
B
B
A
B
A
A
Actually
so
I'd
like
to
share
that
with
everyone
else,
and
that
it's
that
nobody
has
actually
figured
this
out.
A
lot
of
the
problems
that
I
share,
that
we
are
like.
Here's
here
are
some
of
the
issues
that
we're
having
in
coordination
or
other
things,
and
maybe
we
could
get
some
insight
there
because
of
you
know,
work
in
other
dials
as
well
and
sharing
information
with
other
dows
and
one
of
the
things
that
came
up
when
I
was
speaking
about.
You
know
we
have
a
lot
of
initiatives
that
are
coming
up.
A
You
know
the
way
even
communitas
formed
was
there
was
an
orientation
initiative
and
there's
this
initiative,
or
you
know,
source
cred
initiative
or
hatcher
outreach
initiative.
There's
a
lot
of
these
initiatives,
but
there's
no
place
for
these
initiatives
to
really
coordinate
anywhere
yet
and
one
of
the
ideas
which
might
actually
work
nicely
with
communitas,
either
underneath
communitas
or
parallel.
Is
this
an
idea
of
having
an
incubator
for
working
groups?
So
it
could
be
an
initiatives,
working
group
or
an
incubator,
but
the
idea
would
be
like
the
same
as
a
startup
incubator.
A
You
know
you
have
a
group
of
people
who
have
an
idea
and
you
get
together
and
have
this
like
the
operational
support
to
sort
of
see
if
it
can
launch
or
not
and
the
id
and
something
like
if
enough.
If
there's
a
group
of
people
who
have
an
idea
that
they
want
to
look
at
something
and
investigate
how
something
can
be
improved
there
there's
you
know
a
weekly
there's,
the
same
sort
of
rhythm
that
we
have
you
know
so
there's
this
weekly
place
for
them
to
do
it
and
focus
just
on
initiatives
within
the
tec.
A
All
right.
I
also
wanted
to
share
in
case
anyone
doesn't
know
david
dyor
shared
a
really
nice
post
on
the
forum
about
how
he
can
help
make
twitter
our
twitter
even
better,
and
one
of
the
things
that
we
spoke
about
was
or
that
I
shared
with.
I
think,
with
chewie,
and
with
david
too,
is
like
be
great
if
he
meets
all
of
the
stewards.
So
if
we
could
make
some
time
for
him,
you
know
if
everyone
can
like
make
an
hour
for
him
in
the
next.
A
D
Yeah
yeah,
so
we
we
put
put
up
this
cultural,
build
survey,
it's
a
common
stock
initiative,
but
it's
been
supported
by
griff
and
I
and
tim
and
nate
and
katie
and
kelsey
also
joined
us
recently.
So
we're
doing
a
yeah
case
study
of
the
cultural
build
and
of
the
tc
so
far,
so
it
would
be
really
really
great
to
listen
to
all
of
the
stewards.
D
I
think
everyone
here
has
really
great
perspectives
about
our
our
culture
and
what
works
and
what
doesn't
and
from
a
very
individual
standpoint,
just
wanting
to
hear
everyone-
and
this
will
help
us
to
move
forward
after
the
the
case
studies
to
build
a
guide
cultural
handbook
that
will
serve
as
a
guide
for
multiple
thousands
in
the
community
sharing
like
our
best
practices
for
self-managed
organization
like
like
we
are
so
please
take
a
minute
to
to
fill
it
up.
Thanks,
tim,
okay,.
A
D
D
So
there's
still
a
lack
of
clarity
on
how
far
should
we
go
with
advice
process
like
when
is
advice,
process
a
step
before
another
decision
or
when
is
that
enough,
and
I
think
that
would
be
a
good
question
to
start
asking
ourselves
whenever
we
receive
a
lot
of
feedback
from
a
proposal
like
maybe
that's
enough.
Maybe
it
doesn't
need
to
go
to
another
round
of
voting
and
another
with
another
tour
platform.
D
So
then,
from
the
top
decisions
that
we
have
to
make
now
the
reward
systems.
I
was
wondering
if
this
needs
to
be
voted
on
like
I
feel
like
the
advice
process
has
been
complementing
the
the
proposal
and
that
there
is
a
lot
of
like
minds.
Thinking
about
it
and-
and
I
don't
know
if
we
have
like
anything
else-
that
we
could
do
instead
like
if
this
proposal
would
be
voted
and
not
approved.
D
Then
what
and
but
I
I
didn't
receive
any
signal
in
the
forum
so
far-
that
that
this
is
not
a
good
direction.
So
I
just
wanted
to
check
if
someone
is
opposed
to
this
proposal
not
being
voted
on,
but
just
passing
through
advice
process
and
also
an
update
that
christopher
joined
us,
and
he
is
incredibly
amazing.
D
It
was
so
good
to
have
this
talk
to
him
and
he
mapped
out
the
process
that
was
laid
out
already,
and
then
we
changed
a
little
bit
this
map
together
and
looking
into
what
needs
to
be
done,
and
now
next
steps
is
going
to
be
finding
all
of
the
people
to
work
on
it
and
then
moving
forward
have
a
little
road
map
so
yeah.
If
anyone
has
a
strong
opinion
about
like
no,
this
should
be
voted
on.
E
B
E
E
D
Oh,
but
there
are
two
different
things:
one
is
like
bringing
tokens
to
this
dao
and
one
is
like
the
process
as
a
whole
like
not
like
bringing
funds
into
the
reward
systems.
Doubt
is
as
if
we
had
approved
everything
that
we're
doing
and
moving
forward
with
it
and
then
asking
for
funds
to
be
distributed.
E
Yeah-
and
I
I
agree
completely
the
I
about
like
separating
the
the
concerns
like-
is
this:
the
right
proposal.
Do
I
have
quorum
like
hey
guys,
hi
hello?
Is
this
a
good
way
to
go?
Does
anyone
see
any
problems,
give
us
feedback
right
totally,
but
then
also
for
you
doing.
The
initial
buy
into
the
bonding
curve
will
also
be
like
more
of
a
formal
ratification
of
the
dow
saying.
This
is
also
a
good
idea.
E
D
Well,
I
think
this
is
important
for
all
of
us
and
I
see
that,
like
not,
everybody
was
in
sofkav
yesterday,
so
I
just
wanted
to
give
a
quick
update
on
on
all
of
them
like
eduardo
was
saying
like
oh,
but
it
feels
like
we're
not
bringing
this
forth
with
the
importance
that
it
has
just
wanted
to
that.
Everybody
knows
that
we're
working
on
this
and
some
of
the
the
progress
that
we
have
made
and
then
can
you
go
back
quickly.
There,
tim,
okay,
so
the
governance
give
back.
D
Huanka
gave
a
good
idea
that
the
the
yes
or
no
vote
will
already
have
the
solution
embedded
in
it.
So
it's
like
yes
for
the
solution
or
no
for
the
solution,
and
that
is
the
only
solution
that
is
presented
because
it
was
given
through
advice,
process
by
the
commons
forum
team
and
and
then
that's
how
we
could
move
forward
with
it,
because
a
problem
that
if
we
don't
present
a
solution
and
just
make
a
yes
or
no
people,
could
vote
yes
for
a
certain
decision
or
no
for
another
decision.
D
A
G
In
in
the
monday
common
swarm
call,
there
was
like
a
solution
that
was
proposed
and
was
more
or
less
like,
like
well
seen
by
by
the
common
swarm,
and
I
think
that
eases
and
clears
up
the
discussion
around
the
technical
solution.
So
that
way
that
the
vote,
like
only
refers
to
the
75
percent
governance,
give
back.
A
I
just
want
to
say
something
that
what
in
this
okay,
embedding
the
solution
in
the
vote
here
are
some
possible
risks.
If
there
is
a
solution
and
then
the
community
approves
the
vote,
yes,
but
also
we
sort
of
like
hard
code
a
solution
in,
should
there
then
be
any
problems
with
the
solution?
While
we
technically
build
it,
then
we
don't
have
an
option
to
still
honor
what
we've
agreed
is
necessary.
G
Is
that
there
needs
to
be
time
to
build
and
to
implement
the
the
solution
so
like.
What
I
am
proposing
is
that
in
the
boat,
we
respect
the
technical
solution
that
the
common
swarm
chooses
and
yeah.
We
respect
the
common
storm
solution
and
and
yeah
we.
We
only
refer
to
it
as
for
yes
or
no,
so
that
we
can
give
time
for
the
implementation.
Yes,.
A
Yeah,
so
I
think
we're
agreeing
so
we
don't
say
the
solution.
We
say
this
is
just
a
yes
or
no
vote
and
we
acknowledge
that
common
swarm
will
then
determine
the
best
way
to
implement
it.
Yes,
I
I
couldn't
agree
more
because
we
don't
know
what
challenges
they're
going
to
face
when
they
try
to
build
it
and
they
might
need
to
abandon
one
method
and
try
another
one.
So
the
community
should
probably
not
vote
on
the
solution,
but
just
the
spirit
of
whether
or
not
to
restrict
the
people
yay.
G
A
Okay,
I
see
no,
I
just
wonder
I
mean
if
that's
the
timing,
okay,
I
think
it
could
even
be
earlier.
I
don't
know
that,
but
I
guess
what
is
what
is
the?
What
are
you
hoping
to?
What
are
you
hoping
for
in
the
next?
It's
less
than
10
days
like
in
the
next
nine
days,
it's
just
to
set
up
the
vote,
and
then
let
people
know
that
they
should
be
voting
in
it.
Okay,.
D
We
just
need
to
think
about
the
promotion
to
do
around
that
and
how
how
that's
happening
with
you,
guys
that
are
like
in
the
forefront
of
it
that
are
going
to
talk
to
the
people
with
the
addresses
and
stuff
like
that.
So
I
think
it's
more
a
matter
of
coordination
and
I
don't
think
he
needs
to
go
to
snapshot.
I
mean
this
was
just
a
test
vote.
D
A
A
There's
there
was
no
proposal
in
here,
there's
nothing
to
be
voted
on.
It
was
more
like
hey
here's,
something
that's
possible
community
brainstorm
on
some
ideas
that
we
can
that
we
can
then
implement
and
to
be
honest,
we
can't
even
vote
a
rank
vote
right
now,
because
there
is
technical
feasibility
discussions
that
need
to
happen
for
some
of
them
there's
interest
to
gauge
for
others
of
them.
So
I
yeah.
A
A
Yeah
well,
things
like
some
of
some
of
the
possible
options
have
to
have
some
feasibility
studies
or
some
feasibility
study
to
look
at.
You
know
the
the
agave
one,
the
the
secondary
markets
like
how,
and
when
can
we
do
it
not
not
within
endow
ourselves
but
like
if
we're
connecting
with
another
partner?
A
So
some
of
the
some
of
the
ideas
were
like
it
was
really
just
like
hey
here
are
some
ideas?
Can
someone
who
wants
to
champion
them
flesh
them
out
a
little
bit
and
then
bring
back
more
comprehensive
proposal
that
then
can
be
voted
on,
but
in
the
form
it
is
now
it's
too
immature
to
vote
on
it,
because
it
could
just
be
nothing.
It
could
but
yeah.
So
yeah.
It's
interesting
like
this.
This
I
I
had.
I
tried
I've
been
trying
to
separate
calling
this
a
proposal
because,
technically
it's
not
it's
just
like
brainstorm
requests.
A
A
D
A
Yeah-
and
there
was
a
there-
was
a
discussion
on
it:
zepty
chewie
mitch,
myself
griff
spoke
with
them
and
they
you
know,
as
they
were
hashing
out
like
feasibility.
There
was.
They
were
sort
of
starting
to
zero
in
on
what
was
feasible
and
what
wasn't
so.
I
think
it's
gonna
end
up
being
a
valid
proposal,
but
there's
a
lot
of
like
it
might
have
turned
out
that
conversation
didn't
lead
anymore.
D
No
and
then
just
that
the
covenant,
I
know
it
doesn't
need
to
be
proposed
to
the
hatched
out,
but
since
we
put
it
under
the
the
only
way
to
change
the
covenant
is
through
the
tao
tao
voting
after.
I
think
it
makes
sense
to
submit
to
the
hatch
down
just
to
like
set
precedent
of
submitting
it
to
adult
voting
to
for
anything
to
change.
A
D
E
Does
we're
discovering,
if
it's
technically
feasible,
about
turning
the
common
pool
funds
into
a
a
agave
or
whatever,
but
that
doesn't
necessarily
relate
to
the
should
we
buy
into
the
bonding
curve
initialize
the
bonding
curve,
so
there
were
kind
of
two
conversations
going
on
there
and
actually
buying
into
the
bonding
curve.
I
don't
know
it
was
really
that
ended
up
just
being
like
hey.
Do
you
want
to
be
our
partner?
Should
we
do
a
token
exchange?
E
A
Yeah
exactly
and
then
there's
also
sort
of
like
well.
What
does
it
actually
mean
if
we're
holding
their
toe
governance,
tokens
and
they're
holding
our
governance
tokens,
so
it
ended
up
being
you
know,
really
more
than
just
technical
feasibility,
but
like
is
this
actually
something
we
would
want
to
pursue
so
say,
there's
a
little
more
thought
that
needs
to
sort
of
go
in
it
before
somebody
before
the
community
could
vote
on
it,
because
right
now,
there's
not
actually
enough
information
to
vote
on.
I
Yeah
next
week
after
softcove,
I
think
we're
going
to
do
a
debate
and
yeah.
I
think
we
could
prepare
like
some
questions
and
then
maybe
do
a
round,
and
you
know
like
actually
like
the
the
money.
That's
in
the
common
pool,
it's
from
every
one
of
us
right
like
and
the
idea
would
be
like
everyone
says.
Oh
if
that
money
was
yours,
what
would
you
do
and
then
gather
like
the
whole
collective?
What
what
everyone
single?
Maybe
someone
is
like?
I
Oh
I'm,
very
conservative,
I
don't
want
to
do
anything
and
I
just
want
to
get
my
die
and
fund
the
tc
and
you
know
get
the
value
from
creating
projects,
and
maybe
someone
is
like.
Oh,
but
maybe
let's
put
some
money
here.
Let's
you
know
and
yeah
gather
the
information
what
every
every
single
person
would
do
and
yeah.
I
think,
then
we
could
have
a
good
collective
decision.
H
A
I
Some
questions
and
then
it
would
be
easy,
like
I
put
it
one
hour
in
the
calendar,
but
actually
it
depends
on
the
quorum
might
be
longer
might
be
shorter,
like
the
idea
is
like
also
like,
I
don't
know
we're
talking
we're
enjoying
our
time
like.
Let's
not
close,
oh
it's
time.
Let's
leave
right,
let's
yeah.
E
Sorry,
my
computer
was
going
really
slow,
prams
yeah,
we're
just
pushing
you
know,
simple
same
old
were
mostly
through
conviction.
Voting.
There
were
some
technical
challenges.
What
do
you
know
it's
complicated,
but
yeah?
I
think
I
think
we're
looking
pretty
good
for
october
1st
as
a
actually
being
able
to
start
voting
on
it.
The
main
modules
should
be
done
on
the
15th
is
the
target
date
that
that
were
that,
we're
looking
and
then
we'll
just
have
the
we'll
have
to
still
add
the
issue
thing.
The
git
github
issue
thing.
E
I
saw
some
conversations
in
the
stewards
chat
and
they
want
to
bring
it
because
it
fell
out
of
context.
But
it's
worth
saying
the
reason
that
we're
using
a
bot
to
make
issues
in
in
for
github
is
that
it's
like
with
the
bot
we
can
make
the
issue
and
then
edit
the
issue
and
make
it
really
long,
but
with
before
the
way
we
were
doing
it
for
the
hatch,
we
couldn't
make
a
long
issue,
so
we
just
wanted.
We
needed
more
characters
for
this
one.
E
The
run-ups
for
the
run-offs,
they
won't
be
for
sure,
yeah.
We
had
a
discussion
around
that
and
we
settled
on
adding
the
names.
I
can't
remember
the
details
honestly
and
then
common
swarm.
We
had
an
amazing
session
with
brett.
He
took
it
upon
himself
to
review
the
hatch
as
well,
which
is
really
really
nice,
at
least
for
future
comments,
and
he
found
a
couple
bugs
in
the
hatch,
nothing
major
but
but
like
you
know,
he
really
is
the
best
person
in
the
world
to
review
this.
E
You
know
he
just
knows
all
the
random
things
that
happened
to
er,
that
or
were
found
in
all
the
previous
aragon,
dao
audits
and
deployments,
and
little
things
like.
Oh,
there
was
an
escape
hatch
that
if
someone
would
have
called
it,
you
know
like
that
should
have
been
turned
off.
You
know
and
there
weren't
any
issues
that
really
could
have
happened
in
the
hatch,
but
very
very
likely
that
without
that
review,
future
groups
that
were
trying
to
deploy
the
hatch
would
have
could
have
been
vulnerable
to
issues.
E
E
As
far
as
any
found,
all
sorts
of
nice
improvements
to
make
the
code
clearer
and-
and
you
know,
prevent
mis
prevent
mis
configurations
really
like
of
deployments
and
make
it
a
lot
safer.
But
honestly
there
was
there
were
not
very
many
issues
found
so
and
that
that
report,
it
we'll
probably
publish
it
as
a
report
if
brett
allows
us
to,
but
the
stuff
is
on
our
github
other
than
that
yeah
stem
and
the
guys
are
just
working
on
the
evm,
crispr
and
sem
is
really
hot.
A
F
E
Yeah,
I
think,
actually
craig
wrote
it
in
the
bitcoin
grant,
there's
graviton
training,
there's
te
academy
and
labs
lots
of
education
opportunities
and
then
we're
going
to
have
collaborative
economics
on
top
of
it,
which
really
is
another.
You
know,
educational
opportunity,
we're
practically
yeah
lots
of
stuff
to
learn.