►
From YouTube: W18 Community stewards: YT descirptions, Roadmap and timelines, Paramms party and more!
Description
Timecodes:
00:00 - Temperature check
11:24 - Spotlight
18:20 - Blogpost
23:38 - Paramms party
27:10 - Roadmap and timelines!
31:49 - Onboarding journey!
40:30 - Call to action!
45:12 - YT descirptions
🙏 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/
A
B
Yeah,
thank
you.
Yeah
you're,
going
to
mute
sorry
about
that
yeah.
One
of
the
things
I've
been
just
noticing
is
the
the
you
know.
I
don't
know
all
the
all
the
action
that's
going
over
the
praise
system
or
the
source
cred
that
we
have
to
implement.
That
seems
to
be
something
that
a
lot
of
people
is
aware
of.
So
I'd
like
to
launch
that
committee
and
and
start
working
into
that
direction.
B
Do
some
testing
with
source
credits
see
how
results
come
out
and
how
we
can
end
up
with
whatever
we
decide
as
a
community
as
as
one
system
or
one
way
to
distribute
whatever
we
decide
to
distribute.
So
I
I
that's,
that's
something
that
I
I
see
many
people
is
concerned
about
and
I'd
like
to
start
getting
into
that
I'll
pass
it
to
a.
C
A
C
Well,
I
feel
a
lot
of
excitement
because
of
where
we
are
and
yeah.
I
I
I
think
that
we're
almost
like
in
a
in
a
point
where,
like
a
lot
of
issues
like
may
arise,
but
like
we're
already,
like
so
close,
that
I
just
feel
like
that
people
are
excited
in
in
general,
I'm
I
am
excited
for
for
the
next,
the
next
weeks
and
yeah
yeah.
C
E
Thanks
david
nate,
you
should
try
on
the
settings
on
the
discord
and
maybe
you
have
a
new
device
connected
or
something
yeah
just
play
with
it.
For
the
temperature
check
yeah.
We
finally
have
four
feet
more
fierce
monitoring
on
the
other.
It
was
livi
and
it's
so
cool
like
it's
moving.
It's
awesome
and
another
thing
I
mean
it's
not
dc
related
but
like
celeste
is
working
pretty
good
and
yeah.
I
mean
somehow
it's
related,
so
yeah
and
it's
fun
I'll
pass
it
to
griff.
F
Yeah
celeste
is
is
working
well.
The
one
hype
community
is
have
has
made
like
a
leap
which
is
really
cool
to
see
the
parameters
stuff
is
we
have
like
a
new
contributor,
his
name
is
noggin
and
he
came
out
of
he's,
got
like
a
whale
like
vomiting,
rainbows,
great
great
icon,
and
he's
he's
he's
like
hot
to
try
he's
like.
F
I
want
to
work
on
things
and
he's
doing
everything
right
he's
coming
in
taking
easy
issues
supporting
vitor
and
those
guys,
and
I
feel
like
we're
going
to
get
a
lot
more
and
we
have
christopher
and
now
and
the
other,
like
contributors
on
the
dev
side,
starting
to
come
in
and
creep
in,
and
it's
really
cool
to
see
the
engagement
and
the
excitement
on
their
side
of
just
like.
I
want
to
help
you
know,
and
then
there's
also
jugged
us
in
that
last
call
being
like.
F
Oh
hey
by
the
way,
I'm
a
designer,
oh
really,
okay,
cool
yeah.
I
want
to
do
this.
You
know
it
was
like.
I
think
that
was
the
first
time
I
heard
that
manu
and
his
designer
bailed
and
within
just
a
few
seconds.
Basically
of
the
announcement:
oh
okay,
here's
another
designer.
We
have
a
lot
of
resources
at
our
fingertips,
I'll
pass
it
to.
H
I
think
it's
working
now
yeah,
sorry
about
that.
I
appreciate
your
patience
yeah.
I
think
the
community
is
doing
well.
From
my
perspective,
I
think
a
lot
of
people
are
really
kind
of
nuzzling
themselves
into
new
roles.
I
think
truly,
congratulations.
Man,
you're
doing
a
great
job
with
the
calm
stuff.
I
really
appreciate
you
taking
that
on
the
seo
is
really
interesting
and
we're
getting
that
all
together
and
making
sure
that
we
have
access
to
everything.
I
know
that's.
J
I
have
been
learning
in
these
past
months
and
it
was
super
interesting
that
we
were
talking
with
asante
city
about
proof
of
humanity,
and
I
asked
him
that
if
he
had
done
like
simulations
for
for
his
token-
because
this
is
like
an
insight
that
that
I
have
had
from
token
engineering-
and
he
said
like
yes-
we
once
had
one-
and
we
saw
that,
even
though
that
we
are
giving
like
the
same
amount
to
everyone.
It
can
cause
monopolies
and
it
tends
to
monopolies
so
yeah.
J
It's
it's
so
nice
to
see
how,
like
the
application
of
the
token
engineering
into
a
token
project,
can
like
signal
these
these
points
and
that
there
is
still
much
to
do
to
improve
and
to
like
make
a
more
like
resilient,
all
our
tokenized
systems.
So
I
am
super
excited
about
this
and
yeah.
I
think
that
I've
been
like
a
little
bit
distracted,
but
I
I
think
that
everything
is
going
great.
A
Cool
happy
to
hear
that
okay,
excellent
cool,
oh
mine,
so
I
also
want
to
say
I
really
like
the
you
know
the
what's
the
right
word
for
it:
the
collaboration
on
the
mvv.
I
thought
that
it
was
a
really
great
team
community
collaboration
and
that
how
you
know
the
one
of
the
the
things
I
thought
about
was
like.
A
Oh,
this
is
this
is
like
collective
intelligence
like
what
we're
ending
up
with
is
going
to
be
better
than
any
one
person
could
write
alone
because
we're
writing
them
all
together
and
then
I
think
onboarding's
becoming
a
lot
stronger,
and
I
really
appreciate
that.
Actually,
knowing
that
people
are
coming
in
and
they're,
not
we
don't
lose
track
of
them.
You
know
we.
A
I
think
we
still
have
a
lot
of
way
to
go,
but
at
least
we
now
know
where,
like
we
can,
we
can
look
at
them
every
week
and
check
in
on
them
every
week
and
make
sure
that
they're
finding
the
right
path
or
help
them
find
a
better
path
if
they
haven't
found
it
by
themselves,
and
then
I
think
comes
I'm
actually
really
impressed
with
how
comms
is
you
know.
Mitch
is
a
monster,
he's
he's
putting
a
lot
of
stuff
out
the
seo
project
and
the
hatcher
campaign
project
got
a
lot
of
momentum.
A
A
F
K
F
A
Okay,
cool
yeah,
it
was
originally
under
the
hatcher
outreach
team
with
eduardo
and
it
was
an
issue
that
was
assigned
to
him
week
two
week,
but
it's
you
know.
It
was
also
he's
having
a
hard
time
picking
the
projects
too.
So
we
thought
maybe
we
can
bring
it
into
this
tec
steward.
So
we
could
have
like
a
group
think
about
it
weekly,
but
it
would
be
great
if
some
one
person
owned
it
too
and
I
don't
know
yeah,
I
don't
know
who
the
the
person
is,
who
can
own
it.
H
A
Originally,
it
was
projects
that
would
then
would
use
the
spotlight
to
share
their
project
because
they
were
going
to
request
funding
from
the
tec.
So
it
was
projects,
but
the
entire
project
sort
of
didn't
have
enough
momentum
to
have
a
lot
of
you
know,
flux
around
talking
to
a
lot
of
projects
and
getting
you
know,
speaking
to
a
lot
of
people
and
putting
figuring
out
who
could
present
and
who
could
propose.
So
maybe
now
that
proposals
is
getting
a
little
more
momentum,
maybe
it
can.
It
can
be
that
I
don't
know
it
like.
A
A
Okay,
olivia
and
griff,
I
just
wanna
originally,
that
was
the
scope
like
people
that
were
proposing,
but
can
we
have
it
be
more
like?
Well,
you
just
have
a
cool
project
in
the
tec
that
we're
spotlighting.
I
mean
in
the
te
that
we're
spotlighting
and
when
we
have
proposals
that
will
propose,
they
definitely
get
the
priority.
F
F
D
D
Token
engineering
narrative-
maybe
we
could
start
shaping
this
more
into
the
the
proposals
working
group
and
start
like
feeling
those
buckets
and
bringing
attention
to
each
one
of
those
and
having
them
organized.
So
people
really
understand
like
oh,
what
is
a
te
project
that
deals
with
education?
What
is
a
tea
project
that
is
building
open
source
tooling.
A
A
F
F
A
Yeah,
so
cool
all
right
and
now
nate
will
take
what
nate
will
be
there
to
be
like
hey,
so
you
don't
have
to
scramble
last
minute,
he'll
remind
you
a
few
days
beforehand,
too
cool
and
any
ideas.
Maybe
we
coordinate
with
any
ideas
as
we're
as
I'm
reaching
out
to
hatcher's
a
lot
of
them
have
their
own
projects,
yeah,
okay,
all
right
cool.
So
the
next
thing
on
the
agenda
is
also
the
new
blog
post
will
be
next
week.
A
A
I
A
Okay
cool:
is
it
an
interesting
idea,
yes
or
no,
to
include
something
around
our
soft
commitments
and
our
number
of
hatcheries
committed
hatchers?
Do
we
want
to
start
having
like
a
little
progress
to
hatch
section,
I'm
leaning
towards
no,
but
I'm
putting
the
idea
out
there
anyway?
Actually,
as
I'm
saying
it,
I'm
thinking
it's
not
a
great
idea,
but
I'm
gonna,
I'm
gonna,
see
if
anyone
thinks
it's
a
better
idea
than
I
do.
A
A
A
F
So
I
don't
know
exactly
but
how
to
say
that,
but
everything's
working
right
now,
like
rage,
quits
work,
everything's
working
as
expected
on
the
contracts,
so
they're
they're,
basically
done
and
the
review
is,
is-
was
just
waiting
on
a
few
last
tests
and
basically
done
so
by
next
week
for
sure
it
will
be
like
100
done.
There
won't
be
any
more
any
more
people
looking
at
them
and
we'll
just
be
able
to
start
playing.
F
F
K
A
F
F
It
didn't
work
right,
so
the
first
qa
was
was
done
by
jake
and
lauren
and
the
pram
team
and
were
we
were
all
too
inside
and
that
was
we
made
enough
improvements
didn't
and
then
we
and
then
we
tested
again
with
nate
and
craig
and
it
it
was
still
very
confusing.
And
then
we
tried
to
make
some
improvements
and
then
we
tested
it
with
tam
and
the
crew
on
sunday
and
oh,
my
gosh
still
a
lot
of
improvements,
so
we're
making
major
changes.
F
We're
getting
rid
of
the
cultural
build
tribute,
we're
shortening
the
text,
we're
we're
going
wild
with
it
right
so
it'll
be
a
complete
it'll,
be
like
a
very
new
dashboard
tomorrow
and
hopefully
it
will
pass
qa
this
time
and
with
this
new
dashboard
and
then
we'll
have
more
regular
parties.
But
I
would
love
it
if
the
stewards
would
be
down
to
come
to
the
pram
party.
F
B
F
One
on
the
one
on
friday
will
probably
be
pending.
I
I
I
locked
in
the
spot,
but
it's
pending
success
on
tomorrow,
that,
like
people
aren't
just
like
throwing
their
hands
up
like
this,
doesn't
make
any
sense.
You
know.
So,
as
long
as
as
long
as
we
succeed
tomorrow,
then
the
one
on
friday
is
scheduled
as
well.
I
can't
remember
the
time
what's
the
time
time
for
that.
A
A
I
want
to
talk
a
little
bit
about
our
road
map
and
timelines,
because
you
know,
as
griff
mentioned
last
week,
our
commons
upgrade
will
certainly
be
delayed
and,
as
we've
been
talking
about
these
hat
param
voting
periods,
we're
saying
we
need
more
time,
so
we've
elongated
the
period
for
the
the
hatch
params,
and
so
that
pushes
things
a
little
bit
and
I've
updated.
There's
a
few
things
right,
like
our
roadmap
here,
is
getting
quite
long,
so
I've
truncated
it
just
to
make
it
more
visible
and
easier
to
see.
A
What's
going
on,
I
still
need
to
run
through
this
with
with
griff
with
jake
who's,
not
on
today
around
these,
these
specific
ones
that
I
moved
around
based
on
what
our
new
timing
was,
and
some
of
the
timing
comes
from
looking
at
the
so
I
want
nobody
to
judge
this
by
its
old
format,
but
timing
wise
it's
these
are.
These
are
not
official
dates.
I
want
to
say
these
are
like
our
top
our
target
dates
just
so
that
we
have
something
that
we
can
work
towards.
A
A
So
in
terms
of
communication,
we'll
have
this
available
more
widely
as
well
on
our
community
calendar
tomorrow.
Our
community
agenda
tomorrow,
but
for
all
of
us
to
sort
of
be
in
the
same
terms
of
the
hatch,
isn't
going
to
be
the
beginning
of.
May
it's
rather
going
to
be
the
end
of
may,
and
does
anyone
want
to
ask
any
questions
around
the
hatch
timelines?
Because
now
is
the
best
time
to
do
it.
H
Yeah
I
was
going
to
ask
just
in
terms:
do
you
have
a
document
for
that
already?
Just
so
like
the
comms,
and
I
know
chewie's
working
on
a
timeline
for
the
actual
distribution
of
preparing
people
for
the
hatch,
so
I
you
know
we
can
include,
like
things
like
parameter,
voting
and
stuff
like
that
as
well.
Yeah.
F
So
we
want
to
be
very
careful
with
these
timelines.
As
tim
said,
it's
like
hey
things
can
be
delayed,
so
it's
like
man,
expectation
management
from
comms.
You
know
where
it's
like.
Okay,
we
have
these
internal
dates
that
are,
for
our
purposes
of
organizing
and
making
sure
that,
like
we're
doing
this,
but
we're
not
definitely
not
going
to
tweet
them
or
something
I
just
want
to
make
sure
that's
clear.
You
know,
but
but
yeah
it's
it's
our
best
target
and
if
one
thing
gets
delayed,
it's
a
cascade
effect
right.
It
moves
everything
back.
A
And
to
that
nate
in
the
it's
in
the
mirror
board
it's
in
this.
You
know
the
road
map
and
timelines
mirror
board
so
for
coms
purposes.
We
should
be
working
towards
these
dates.
You
know
definitely,
but
without
announcing
the
dates
specifically
announcing
a
sprint
or
maybe
even
a
week
can
be
reasonable,
but
definitely
not
a
a
hard
date.
Unless
there's
something
like
you
know,
the
mvv
wrote
vote
is
going
to
take
place
in
the
soft
gov
call.
H
C
H
A
I
I
A
One
thing
I
I
want
to
say
is:
we
did
an
onboard
which
we
did.
A
katie
probably
also
presented
this.
This
guide
to
use
while
we're
on
boarding,
and
we
gave
it
a
trial
run
yesterday
in
an
onboarding
session
with
kate,
katie,
myself,
chewie
and
eden,
who
you
know
it's
very
it's
one
of
these
interesting
moments
like
you're
doing
you're
like
okay,
we're
going
to
follow
this
guideline
right
out
the
window.
A
I
So
you
know,
we've
we've
been
talking
about
this
a
little
bit
and
I
already
shared
the
the
onboarding
journey
message
that
would
be
great
to
share
anytime.
You
come
across
a
new
contributor,
so
same
idea,
but
then
this
is
the
next
step
for
actual
onboarding,
and
so
it
covers
those
same
questions
that
tam
added,
I
guess
maybe
a
short
while
ago,
into
the
new
contributor
excel
spreadsheet.
I
So
you
know
how
did
you
find
out
about
the
tec?
What
are
your
interests
and
background?
What
questions
do
you
have
about
the
tdc
yeah
so
doing
this
with
aiden
yesterday
was
super
interesting
because
it
was
obvious
right
away
that
we
didn't
need.
I
mean
he
know
he
knew
a
lot
already,
so
we
could
skip
that
or
or
like
we
said,
just
kind
of
walk
around
it
in
whatever
organic
way
made
sense,
and
so
then,
let's
see,
can
we
can
we
see?
Can
you
see
my
no?
I
can't
see
them
either.
I
I
I
went
ahead
of
myself.
All
right,
like
I
said,
am
I
so
when
I'm
doing
when
I
present
like
this
live,
my
computer
gets
a
little
a
little
bit
slow.
So
it's
it's
chugging
along
here
so
on
this
particular
site,
get
to
know
us
each
one
of
these
is
has
some
speaker
nodes
with
some
links
which
can
obviously
be
updated,
so
obviously
the
first
one,
the
mvp
we
want
to
put
in
the
actual
mvv
in
there
and
then
we
can
go
over
it.
I
C
I
The
more
I
don't
know,
technical
stuff
we've
got
sharing
the
road
map
and
then,
of
course,
the
10
working
groups
going
over
those
one
by
one
and
then,
depending
on
the
nature
of
the
the
onboarding.
We
can
talk
about
the
the
tech,
hatch,
raising
funds,
funding
projects,
and
you
know
the
hatch
process.
Those
are
probably
reserved
more
for
a
higher
level
or
different
type
of
contributor.
I
Then,
finally,
once
that
all
comes
together,
you
can
talk
to
the
new
contributor
about
what
they
can
do
next
so
usual
stuff.
We
want
to
send
them
to
the
community
call
they
want
to
send
them
to
the
ama,
possibly
the
hatcher
ama
and
again
it
may
be
the
case
that
you
they've
already
been
there
and
that's
how
they
got,
how
they
found
or
how
they
got
onboarded
in
the
first
place.
So
whatever
works
there
share
the
tec
calendar
and
then
maybe
more.
A
Cool
thank
you
for
thank
you,
and
I'm
also
just
going
to
share
that.
Like
the
you
know,
it's
nice
that
this
process
is
getting
a
lot
stronger
and
I
think
to
the
work
that
katie's
doing
it
and
you
know
interviewing
all
the
stewards
for
how
like
this
collective
intelligence
like
how
can
we
make
it
better,
but
we're
also
starting
to
figure
out.
A
Okay,
now
we're
starting
to
capture
people
like
this
is
aidan,
who
was
on
boarded
on
the
20th
by
chewie
and
katie,
and
I
and
how
he
found
out
about
us
what
his
skills
or
interests
are.
You
know
where
is
he
so
he's
super
knowledgeable,
he's
very
well
connected
and
then,
like
what
our
recommendations
were,
you
know
he's
he's
sort
of
like
you
just
need
to
aim
him
somewhere,
so
he
aimed
to
make
it
book
you
know
suggested.
Maybe
he
could
be
interested
in
like
looking
talking
to
the
hatch
outreach.
A
Maybe
he
could
be
very
interesting
for
a
project
since
he's
extremely
well
connected
in
a
bunch
of
different
projects
comes.
Certainly,
he
seems
like
an
am
like
he's
a
bull
horn.
You
know
he
seems
like
an
app
amplification
machine,
so
the
idea
is
like,
maybe
in
the
stewards
meetings
we
can
have
a
look
at
who
we
have
available
or
when
there's
a
community
steward.
That
has
a
need.
We
can
go
back
and
just
be
like.
Oh
there's
there's
some
people
in
our
community
who
have
that
those
skill
sets.
So
we
can
start
to.
A
I
don't
think
I'm
gonna
say
deploy
people,
but
it
means
like
to
really
engage
people
and
activate
them
in
the
tc
thanks.
So
much
for
that
katie.
It's
really
great.
The
next
thing
is
the
call
to
action.
So
in
the
comms
call
there
was
on
the
agenda
asking
the
stewards
to
use
the
c
d
repository,
so
I
will
pass
to
chewie
or
marco
or
whichever
one
of
you
wanna
wanna,
give
the
call
to
action
to
the
stewards.
C
E
A
C
C
C
A
A
Cool
okay:
the
next
thing
is
mitch
and
marco
working
group
for
summaries
working
group
summaries
for
youtube.
So
this
is
something
that
was
an
idea
that
iv
had
to
you
know.
Since
we
have
all
of
these
videos
on
youtube,
it
would
be
great.
You
know.
Each
working
group
has
our
working
group
videos
and
our
working
group
channel
and
right
now,
they're
empty.
A
Basically,
the
the
call
to
action
from
the
stewards
is
to
have
a
look
at
the
working
groups,
but
also,
maybe
for
us
to
think
strategically
about.
You
know
what
we
should
have
on
each
video
should
we
have
more
information
about
the
tec
link
to
our
discord,
how
they
can
join
as
well
as
a
little
paragraph
about
each
working
group
so
yeah.
I
think
some
of
these
are
probably
a
little
outdated
too.
So
just
a
reminder
that
some
of
us
can
you
know
you
know-
and
I
wouldn't
say
refresh
our
manifest.
A
We
end
up
it's
a
quarter
right.
If
we
were
updating
our
manifesto,
I
feel
like
we'd
be
doing
it
all
the
time,
but
just
the
thinking
is
that,
like
okay,
I
probably
want
to
go
back
and
if
this
is
going
to
be
on
every
youtube
video
on
for
the
work
for
the
community
stewards
working
group,
I
would
like
this
to
be
a
little
tighter
and
cleaner
and
have
a
call
to
action
that
brings
people
into
the
tec
when
they
find
our
video
online
so
yeah.
A
So
I
I
actually
think
maybe
the
next
steps
is-
and
I
don't
know
if
we
could
ask
comms
to
do
this-
is
to
come
up
with
a
strategy
for
what
kind
of
information
should
be
in
the
in
that
in
everybody's
youtube.
Video.
If
we're
gonna,
you
know,
go
through
putting
the
information
in
there
and
then
for
the
working
groups
to
review
what
they
want
to
have
shared
with
the
what
they
want
to
have
shared
with.
You
know
the
2.3
billion
youtube
users.
C
A
A
For
each
video,
but
it
could
be
something
very
generic
like
you
know,
this
is
this
working
group
and
to
find
out
more
about
the
tec
and
here's
our
discord
channel,
and
you
know
something
like
that.
So
yeah
I,
I
guess
the
question
really
is
like:
does
every
steward
want
to
take
that
on
to
do
it,
or
maybe
we
can
ask
comms
if
they
can,
you
know
shape.
You
know
the
generic
thing
that
goes
for
everyone,
like
the
calls
to
action
and
how
to
find
more
about
the
tec
and
then
each
of
our
stewards.
A
Maybe
we
pull
this
into
a
next.
The
next
sprint
can
work
on.
You
know
the
the
the
comments
that
you
want
on
the
working
group
on
your
working
groups,
or
maybe
we
have
some-
I
don't
know
like.
Maybe
we
have
something
pretty
templated
or
I
don't.
Every
working
group
can
just
write
their
own
paragraph
and
share
it
so
that
it
can
be
updated
to
youtube.
Maybe
that's
a
nice
way
to
do
it.
A
E
Yeah,
the
there
are
some
links
that
just
provide,
and
then
we
just
updated
like
the
one
from
the
discord
and
so
on.
But
I'm
wondering
like
should
the
lead
that
they
think
we
have
in
the
past
like
like
especially
the
thing
that
just
drafted
and
add
this
or
you
want
to
have
the
thing
that
just
drafted
and
this
on
top
of
that.
A
A
I
think
the
first
way
works
since
it's
actually
a
little
piece
of
little
piece
of
work,
but
we
could
do
it
either
way.
Actually,
if
it
ends
up
taking
time
and
not
being
something
fast,
then
it's
probably
best
for
it
to
be
assigned
to
each
steward,
but
then
it
will
definitely
be
like
something
that
we
pull
into
the
next
sprint.
So
we
would
expect
it
not
to
get
done,
which
probably
there's
no
rush
to
do
it.
I
think
it's
better
that
we
do
it
really
well
you're
cool
all
right.
E
E
I
mean
I
like
a
little
introduction
on
the
like
this
thing.
That
mitch
was
doing.
I
think
it's
cool
like,
for
example,
we
would
have
a
little
explanation
of
the
working
group
and
then
the
time
codes
and
then
the
thank
you
and
that
stuff
that
just
made
you
know
so
maybe,
but
I
feel
like
this
is
too
long
like,
for
example,
parameters
like
I
would
make
something.
You
know
three
four
lines
and
then
yeah
something
generic
and
yeah
to
engage
and
then
add
the
ceo
stuff.
I
think
that's
really
important.
A
A
So
the
last
thing
is,
you
know
we're
looking
at
the
ice
looking
at
the
issues
template-
and
I
don't
know
if
everyone
else
does
the
same
thing,
but
let
me
go
back
into
our
distribution.
It
was
a
template
that
we
pulled
from
from
common
stack,
which
I
think
was
really
useful
when
it
was
first
first
created,
but
I
don't
know
that
we're
actually
using
the
issue
template
anymore.
A
A
You
know
one
of
the
things
that
we're
doing
is
like
one
person,
one
issue,
one
issue,
one
assignee
so
it'd
be
nice
to
have
like
who
else
should
be
aware,
like
you
know,
just
a
list
of
all
the
people
who
should
be
aware
which
we've
been
using
as
reviewers
for
now
but
other
than
reviewers.
It's
other
like
it's
also
other
people
that
are
participating
actively
in
this
issue.
So
maybe
it's
advice
process.
A
You
know
the
definition
of
done
like
success
criteria
like
how
do
we
know
this
issue
is
done.
You
know
like
sometimes
we
get
to
the
end
of
a
sprint
and
we're
like,
but
is
it
done?
But
you
know
and
it's
like,
should
we
close
it?
Yet,
and
that
way
we
could
in
the
beginning
plan
what
the
expected
outcome
is
and
then,
if
we
pivot,
we
could
always
update
our
definition
of
dones,
but
at
least
we'll
have
a
clear
idea
of
what
it
is.
A
So
I
really
like
the
idea
of
having
like
hey
who's,
the
advice
process
on
this
who's.
It.
What's
the
definition
of
done
and
maybe
getting
rid
of
you
know
something,
maybe
I
you
know
I
haven't
put
a
lot
of
thinking
into
this
yet,
but
the
idea
is
like
it's
a
good
opportunity
for
us
just
to
to
clear
out
the
cobwebs
and
and
try
to
make
it
a
more
easier
template
to
follow.
A
D
D
A
Yeah
thanks
for
bringing
that
up,
because
I
do
that
a
lot
actually,
so
I
needed
to
hear
that,
and
I
think
you're
right
it'd
be
great
to
see
that
maybe
durgados
has
volunteered
to
do
some
designs
for
the
hatch
process.
Maybe
maybe
he
can
have
like
a
visualization
of
ostrom's
principles
and
all
of
the
tec
working
groups
and
how
it
is
really.
We
are
really
applied
everywhere.
I
I
F
D
F
I
think
everyone
here
knows
how
to
vote,
but
I
think
it'd
be,
I
think,
it'd
be
great
if
there's
like,
if
you
feel
like
you,
have
some
overall
thoughts
about
all
of
them
holistically
to
make
comments
in
this
post
and
if
you
have
thoughts
on
individual
issues,
make
comments
in
the
github
issue.
This
is
what
we
want
to
do
for
the
rams
when
we
start
voting
on
prams,
have
a
forum
post
where
people
can
talk
about
the
params
in
general
and
then
have
the
each
issue.
They
talk
about
the
params
individually.