►
From YouTube: TEC Sprint 1 Kickoff
Description
Timecodes:
00:00 - Intentions and distractions
09:28 - Agenda
21:36 - Gravity
40:34 - Soft Gov
01:04 :19 - Onboarding
01:29:00 - Comms
01:46:50 - Legal
01:50:50 - Paramms
01:53:54 - Transparency
01:54:56 - Closing and mindfulness
🙏 Thank you for watching! Hit 👍 and subscribe 🚩 to support this work
🌱Join the Community🌱
on Discord https://discord.gg/DDr5kYU
or say hello on Telegram http://t.me/CommonsStack
Join the conversation https://forum.tecommons.org/
Follow us on Twitter: http://twitter.com/CommonsStack
Learn more http://tecommons.org/
A
Sorry
I
was
distracted
by
needing
to
go
to
the
bathroom
and
eight
hours
of
calls,
sorry
for
being
late
and
then,
but
as
far
as
intentions,
just
to
like
sink
on
the
plan
for
the
next
two
weeks.
It
doesn't
have
to
be
so
intense,
but
the
my
intention
is
that
we
only
put
things
on
the
board
in
the
next
two
weeks
that
we
promise
to
finish
and
then
and
we
hold
each
other
accountable
for
it
and
then
yeah,
and
then
we
have
a
good
time.
A
B
The
idea
that
we
have
in
in
gravity
is
to
start
the
the
training
this
year
as
soon
as
possible
and
to
have
like
consent
on
the
topics
and
on
the
on
the
yeah.
On
the
plan
of
study
that
we're
going
to
have,
I
want
to
translate
into
the
the
workflow
and
I
don't
have
any
instructions
I
am
just
have
have
had
lunch,
so
I'm
fine
and
yeah.
We
still
be
in
this
call,
so
I
will
pass
it
to
santi.
C
An
opacity
to
sam
or
zapdimov,
or
both
of
them
yeah,
you
take
it
hello,
everyone
when
my
computer
was
not
working,
that's
my
main
distraction,
so
I'm
here,
hopefully
we
have
a
good
connection
here
and
I
actually
quite
distracted
lately,
but
I
mean
this
is
what
it
is,
but
I'm
I'm
going
to
be
quite
focused
on
this.
Internship
asked
me
to
come
to
this
specific
one.
So
I
want
to
be
here
and
see
everything
is
going
in
the
rest
of
the
groups
and
we
can
work.
C
Our
issues
on
github,
like
I
we
were,
we
didn't
have
it
until
today
we
I
we
were
also
thinking
to
make
it
them
on
the
next
transparency
working.
But
it's
awesome.
We
pressure
that
and
yeah.
We
have
an
epic,
I
think
we
can
share
and,
I
think
yeah
I
would
love
to
have
some
feedback
from
the
whole
community
and
I'll
pass
it
to.
D
E
E
You
know
that
opportunity
to
really
know
where
everyone
is-
and
this
is
really
helpful,
moving
forward
in
case
people
have
their
own
individual
blocks.
So
having
this
kind
of
big
open
communication
is
really
cool,
so
we
have
much
more
directed
direction,
distractions.
Well,
both
my
kids
are
inside
and
so
that
positive
you
know,
outlook.
I
don't
have
to
worry
about
monkeys
taking
them
away,
I'm
I'm
watching
sim
eat
and
I'm
getting
hungry
so
other
than
that.
No
I'm
really
excited
about
this.
I'm
gonna
pass
it
to
eduardo.
F
G
G
Much
needed
to
a
lot
of
the
stuff
is
new
in
fairness,
from
like
a
few
meetings,
so
I'm
gonna
use
this
time
to
try
to
get
caught
up
on
the
board,
and
so
everybody
can
see
and
other
distractions.
I
am
making
some
food
and
some
tea.
So
if
anyone
wants
to
come
over
for
lunch,
I
made
a
huge
pot
of
butternut
squash
soup
and
I
will
pass
to.
G
C
Otherwise,
I'm
here
basically
because
I
don't
want
the
trusted
seat
from
the
computer
side
to
be
a
boardwalk
for
anybody,
so
I
want
this
listen
and
take
notes
and
just
kill
you
guys
out
and
mark
down
any
issue
that
near
to
that.
So
I
can.
I
can
support
you
and
I'll
pass
it
to.
I
gotta
hear
a
little
bit
later.
I
don't
know.
D
My
intentions,
for
this
call
are,
are
to
organize
all
our
work
and
I'm
really
excited
because
it's
the
first
time
for
for
the
common
stack
people
that
we
are
separating
common
stack
and
tc
issues
into
two
different
sprints,
and
that
was
like
wow.
I
I
feel
like
even
like
my
brain
feels
so
happy
about
it.
It
feels
really
good
and
distractions.
I
really
have
to
go
to
the
bathroom,
so
I
I
might
have
to
do
that
in
a
minute.
C
H
H
Okay,
I'll
go
and
craig,
if
you
hear
us
just
jump
in
my
intentions,
are
to
have
a
really
strong
kickoff
for
the
first
tec.
Sprint,
I'm
really
excited
about
it
as
well.
I'm
really
looking
forward
also
to
you
know
the
the
ideas
and
the
work
that
everyone
has
put
in
to
the
the
workboard
so
far,
so
I
think
I
think
it's
I'm
really
looking
forward
to
that
and
distractions.
H
H
So
I
think
everyone
has
seen
this
document
multiple
times,
because
I
have
sent
it
multiple
times
and
and
to
everyone
individually
and
group
channels,
but
welcome
to
the
tec
sprint
one
kickoff
we
are
gonna
get
started
with
the
same
type
of
sprint
that
we've
been
doing
with
commons
stack
for
last
two
sprints.
It
seems
to
be
working
well,
and
this
is
really
the
first
time
that
each
of
the
stewards
is
going
to
manage
control
their
own
workload
across
the
sprints.
H
H
H
So
I
want
to
make
sure
I
guess
there's
a
few
things.
I
want
to
do
a
little
bit
of
housekeeping
before
we
kick
this
off
and
that's
to
make
sure
that
our
key
dates
for
the
sprint
for
the
scrum
light
framework
is,
is
doable
that
there's
not
any
major
blockers
or
any
reason
we
change
it.
If
there
is,
we
could
take
it
offline
and
organize
async,
but
as
it's
proposed
we
will
basically
be
having
meetings.
The
this
sync
meeting
would
happen.
H
H
H
Maybe
noticed
your
calendar
entries
have
agenda
links
on
them
now
I
really
encourage
everyone
to
use
the
agendas
for
us
for
our
own,
knowing
what
we're
going
to
do
on
our
in
on
in
each
session,
but
also
for
community
members
who
want
to
decide
whether
or
not
they
should
join.
That
call
for
you
know
if
they
can
have
a
look
at
the
agenda,
they
can
sort
of
make
that
decision.
Maybe
you'll
bring
more
people
in.
H
You'll
basically
have
an
inbox
here
and
then,
when
you
go
to
this
sorry,
when
you
go
to
mentioned,
you
will
see
everything
that
has
that
somebody
has
tagged
you
in.
So,
if
there's
a
comment
or
an
issue
that
you've
been
tagged
in,
it
will
be
in
here
and
you
can
go
through
them.
I've
sort
of
added
this
to
my
daily
routine.
So
I
check
it
in
the
morning
to
see
if
there's
anything
I
need
to
respond
to.
H
H
Are
we
on
target
from
where
we
thought
we
will
be,
and
that's
really
so,
you
can
come
back
as
you're
planning
as
you're
as
you're
doing
your
planning
and
then
the
one
thing
I
want
to
say
before
we
start
in
our
board
is
this:
is
you
know
sprint
sprint?
Planning
is
really
a
working
session.
You
know
it's
not
it's!
It's
our
goal
is
to
know
what,
where
each
work
stream
will
be
doing
over
the
course
of
the
next
two
weeks.
H
H
So
I've
sent
messages
to
everyone
to
to.
If
you
have
time
between
monday
and
today,
to
have
looked
at
your
work
stream
and
tagged
any
issues
that
you
have
with
nick
sprint,
those
are
the
ones
we'll
start
looking
at
first,
what
else
do
I
want
to
say
about
that?
Nothing
really.
So
I
maybe
think
that
the
way
that
we
can
do
this
is
by
each
working
group.
H
H
H
Oh
okay,
the
te
community
call
is
essentially
what
we
do.
You
know
how,
in
in
common
stack,
we
have
a
review,
call,
that's
special,
that
we
record
not
special,
but
that's
a
demo
that
we
record.
Essentially
that's
our
in
te
commons.
That's
that's!
The
community
call
where
we
demo
everything
that
we've
done
the
la
that
week.
So
we'll
just
have
two
reviews.
Instead
of
one
review
for
each
sprint
and
then
every
other
week
we'll
have
a
thursday
retrospective
and
then
24
hours
later
the
sprint
planning
for
the
next
sprint.
G
But
it's
still
a
little
confused
for
some
reason,
so
you're
saying
the
regular
stewards
calls
will
continue
on
wednes,
like
every
other
wednesday,
we'll
have
a
normal
call
and
the
other
like
the
second
wednesday,
is
going
to
be
this
and
then
the
alternating
retro
will
be
every.
There
will
be
every
two
weeks.
H
D
H
Yeah
I
hear
that
jessica.
It
comes
out
to
three
meetings.
I
mean
three
hours
over
two
weeks
and
I
think
that
the
results
of
us
empowering
the
te
stewards
to
control
their
own
work-
sprint
work
group
work,
sprints,
probably
will
will
be
rewarding.
I
think
I
think
that
you
know
an
extra
three
hours.
Every
two
weeks
may
prove
to
be
quite
quite
a
good
deal,
but
I
I
agree.
H
A
G
G
So
I'm
happy
to
table
this
discussion
for
the
next
regular
stewards
call
to
help
to
like
manage
that
flow,
because
yeah
I'm
starting
to
drop
out
of
like
going
to
some
of
the
calls
but
yeah
we
can
table
that
discussion
for
another
time
and
focus
on
the
sprint
I'm
open
to
like
giving
this
a
go.
I'm
I
know
it's
going
to
be
really
helpful
and
we've
kind
of
lacked
this
and
said
we
needed
it.
So
I'll
just
bring
up
the
like
meeting
tracking
or
internal
comms
discussion
for
the
next
meeting.
G
H
Okay,
so
I
think
we
maybe
start
with-
I
don't
know
what
the
right
order
to
start
with
is,
but
I'm
looking
at
juan
carlos,
since
I
know
that
this
is
probably
one
of
the
least
hairier
ones,
so
juan
carlos.
If
we
look
at
it
is
still
called
conflict
management,
and
do
you
want
to
talk
about
what
issues
or
what
the
workload
looks
like
for
the
conflict
management
working
group
for
this
next,
like
what
your
goals
are
for
these
next
two
weeks
for
the
sprint.
B
So
it
will
take
the
two
last
weeks
of
january
and
february
and
it
will
end
in
in
march,
but
I
I
have
already
started
this
study
plan
and
I
have
shared
it
with
libyan
grip,
but
I
am
going
to
share
it
in
the
in
the
in
the
steroids
chat,
because
for
me,
it's
really
important
to
have
the
the
everyone's
review
and
to
see,
if
you
like,
agree
on
on
what.
How
are
the
the
the
topics
divided?
H
H
H
The
way
that
these
pipelines
will
we
move
through
the
pipelines
is
this
is
all
of
the
issues
are
essentially
our
roadmap
and
what
are
what
tec
com?
What
tec
coordination
is
delivering,
what
it
is
and
what
it
is
delivering
any
new
issues
automatically
fall
into
the
new
issues
pipeline,
and
then
we
move
them
to
the
product
backlog
and
then
and
before
the
sprint,
as
part
of
the
sprint
planning.
Every
tec
steward
will
tag
their
issues
with
new
sprint,
we'll
review
those
issues
and
move
them
into
the
sprint's
backlog.
H
At
the
end
of
this
session,
we'll
take
everything
in
the
sprint
backlog
and
we'll
assign
it
to
a
milestone
so
that
you
can
always
search
by
a
milestone.
To
see
milestone
is
another
word
for
sprint.
Milestone
is
the
zen
hub
word
for
sprint,
so
when
I
say
milestone,
it's
really
interchangeable
with
sprint,
so
you
can
see
which
sprint
the
workload
is
scheduled
for
when
you're
working
on
that
particular
issue.
You
would
just
move
it
to
in
progress.
H
H
H
There
is
and
olivia
raised
this
on
the
group
channel
earlier
today
around
the
terms
and
conditions,
and
I
think
maybe
it's
a
good
point
for
us
to
also
discuss
that
now,
since
it
affects
actually
all
of
the
groups,
and
but
I
just
want
to
see,
is
this:
is
there
anything
else
that
you
want
to
bring
into
the
sprint
backlog
for
this
sprint?
Because
or
not
because
this
is
certainly
enough.
A
lot
of
work.
B
H
D
B
B
H
Better
well,
the
the
purpose
of
this
sprint
planning
session
is
for
all
of
us
to
know
what
everyone
is
working
on.
So
we
could
actually
just
take
the
time
now
to
if
there
is
stuff
that
you're
that's
in
progress
now,
we'll
move
it
to
the
sprint
backlog
and
we'll
just
put
everything
in
the
sprint
backlog,
and
then
you
can
move
it
in
progress
over
the
course
of
the
next
days.
A
D
D
So
and
then
I
assigned
the
epic
for
the
three
of
us
santi
and
I
so
that
would
be
like.
Oh,
we
will
overlook
all
of
them,
but
then
one
one
question
I
had
was
do
we
need
three
issues
for
each
each
section
or
they
are
somehow
interconnected
and
I
feel
like
at
least
the
gravity
and
soft
gov
are
connected.
I
don't
think
there
needs
to
be
two
separate
ones
and
then
for
the
legal
part
I
was
imagining.
D
A
The
the
general
strategy
with
these
epics
is
our
issues
is
that
each
issue
represents
one
person
max
and
two
weeks
of
work
max,
and
so
what
I
would
say
is
that
each
of
these
documents
need
to
be
reviewed
by
all
by
all
three
of
you,
and
so
it's
kind
of
like
when
that
issue
goes
to
closed,
then
you
can
say
you've
reviewed
it.
It's
done
you
know
like,
and
then
that
document,
when
all
three
of
those
issues
is
closed,
is
like
done
right
that
that's
my
idea
on
it.
G
I
feel
like
we're
in
this
place,
where
we're
still
exploring
this
balance
and
it's
improving
in
some
ways.
But
then
it's
getting
a
little
cuckoo
another
like
a
little
messy
in
other
ways.
So
maybe
part
of
this
process
is
to
like
align
around
how
we
want
to
use
this
system
to
like
improve
the
work
and
not
having
like,
I
think
we're
just.
We
all
have
different
ideas
about
what
we're
supposed
to
be
doing
like
a
little
bit.
G
H
Yeah
yeah,
so
it's
two
things
I
would
love.
You
know
it's.
We
we're
getting
at
the
point
with
our
third
sprint,
with
common
stock,
where
it's
really
we're
in
the
flow
now.
So
I'd
love
for
us
to
give
this
a
go,
the
same
methodology
and
in
two
weeks
do
our
retro
see
what
worked,
what
didn't
work
and
improve
for
the
next
sprint
and
continue
that
way,
without
maybe
putting
too
much
emphasis
on
analysis
right
now
at
this
moment
as
we're
getting
started
for
this
particular
issue,
I
looked
it.
H
As
you
know,
it
looks
like
there's
a
lot
of
issues.
It's
actually
super
fast
to
do,
but
what
it
is
is
like
also
every
it's
a
touch
point
between
terms
and
conditions,
which
is
crucial
and
the
the
crucial
work,
the
crucial
work
groups
that
need
to
touch
it.
You
know
like
for
each
of
these
different
channels
that
we
have.
H
There
will
be
one
terms
and
conditions
file
and
there's
three
departments
that
need
to
sign
off
on
it,
and
this
is
just
that
sign
off,
sign
off,
sign
up
and
it's
easy
because
it
can
go
into
we
could
select.
You
know
you
know
three
channels
and
all
of
the
work
streams
can
go
into
one
sprint
and
we
can
get
done
with
that
tnc
that
one
tnc
very
quickly.
H
I
don't
know
if
that
fully
addressed
your
your
comments,
jessica,
but
I'd
I'd.
I
think
I
think
we,
I
think,
having
a
conversation
around
how
we
you
know
pm
overhead
right
now
might
not
be
the
best
moment
for
us
to
do
it.
I
think
maybe
we
can
have
it
in
the
retrospective
after
we've,
planned
this
sprint
and
gone
through
the
one.
The
exercise
with
this
new
team
of
tc
stewards
does.
H
D
Can
I
just
have
a
last
comment,
so
I
understand
what
you
guys
thought
now.
I
think
there
was
just
a
lack
of
like
maybe
it
wasn't
explained
in
the
titles
and
then
I
got
confused.
I
was
like.
Oh,
are
we
doing
like
three
different
whole
processes,
but
then
now
I
get
it
that
is
just
reviewing.
So
maybe
it
could
be
helpful
to
have
like
the
issues
that
each
one
is
working
on
assigned
to
each
person
like
that,
each
topic
of
the
code
of
conduct
and
then
having
just
one
issue
to
be
like
leave.
D
H
You
know
many
ways
to
skin
a
cat
there's
if
we
do
it
that
way,
it's
sort
of
like
the
one
issue
just
is
kind
of
never
getting
done.
You
know
here's
like
if
santi
can
work
on.
You
know,
github
and
tec,
hatch
and
soft
gov
is
working
on
a
different
tc.
This.
This
allows
for
a
lot
of
agility
and
a
lot
of
flexibility
for
each
working
group
to
work
together
on
one
tc
or
work
on
different
parts
of
another
one
and
still
move
like
move
forward
with
like
get
the
get
it
finished.
H
B
Yes,
on
the
call
we
had
yesterday
on
softgov,
we
started
hacking
on
the
document
and
I
think
I'm
going
to
be
working
on
this
document
these
days
and
like
I
made
the
the
first
part
on
the
on
gravity,
but
I
have
to
review
all
the
other
sections
and
I
also
like
thought
of
a
different
order
of
the
on.
How
is
the
information
presented?
B
A
Hatch,
legal
santi
and
I
have
already
started
that
and
we're
going
to
like
probably
be
the
one
ones
who
start
that
and
different
ones
of
these
have
are
going
to
be
started
by
different
working
groups
and
then
so,
if
you
want
to
start
it
and
like
try
to
get
it
done
because
seriously,
this
is
not
something
if
it's
like
just
sitting
there
on
the
sprint
board
forever.
It'll
never
get
done
and
we'll
just
never.
A
B
B
A
B
H
H
D
H
D
D
D
H
D
C
C
All
we
have
to
do
is
you
know,
decide
the
the
parameters
we
want
to
start
with
and
probably
run
with
those
parameters
for
a
few
weeks
before
the
hatch
to
see
how
the
outcome
looks
like,
but
the
other
options,
the
other
reward
systems
that
we
may
want
to
try
as
going
still
going
on
with
praise
and
maybe
adding
others
that
other
other
you
know
contributors
may
want
to
put
on
the
table.
I
don't
know
about
those.
You
have
a
brighter
brother
picture
on
those,
but
I
definitely
have
no
problem.
H
If
I
can,
I
think
of
it,
as
this
is
two
actually
issues
and
one
is
sort
of
led
by
santi,
which
is
the
source
cred
option
and
implementation,
and
the
other
is
really
libya
liberate
system
holistically
are
those
sort
of
the
two
issues,
and
can
I
just
break
it
into
two
issues
and
libya.
You're
you'll
run
with
holistic
praise
and
more
very
high
level.
What
we
want
to
do
and
santi's
running
with
the
source,
cred
implementation
and
investigation-
is
that
okay,
yes,.
H
H
G
I
would
suggest
this
has
been
a
discussion
for
a
while.
I
guess,
like
a
discussion,
was
a
brainstorming
session
around
what
the
praise
system
could
look
like
post-hatch
and
maybe
the
starting
of
a
document
to
document
those
ideas
of
what
that
would
look
like
that
seems
doable
in
the
sprint.
I
don't
know
the
priority,
but
maybe.
D
D
G
H
G
Maybe
it's
synthesized
this
feedback
into
a
document
like
this
is
really
hard
to
look
at.
So
maybe
like
a
document,
that's
synthesizing
this
like
for
me,
it's
pretty
straightforward.
It's
like
we
would
have
to
whatever
group
wants
to
work
on
managing
the
praise
would
have
to
submit
a
proposal
for
like
x
amount
of
dire
dollars
per
month
to
use
towards
this
system,
and
then
they'd
have
to
write
up
the
proposal
of
how
they
would
dish
it
out,
but
maybe
synthesizing
some
of
this
feedback.
It
would
be
a
next
step.
D
H
D
H
H
C
We
are
working
on
on
the
hatch
terms
and
conditions,
the
not
not
in
the
yeah
and
the
hatch
and
the
one
yeah,
the
hatch.
We
already
have
the
joining
those
and
conditions
we
publish
that
on
the
forum
post
and
those
are
the
institutes
and
the
the
terms
that
are
on
the
onboarding
app
we
have
to
go
over
the
rest.
I
haven't
done
anything
on
all
those
that
were
added
a
couple
of
days
ago.
C
I
just
saw
them
as
nice
king's
presence
when
I
opened
up
my
mail,
so
I
we
can
go
over
all
of
them
and
see
if
anyone's,
if
anyone's
working
on
them
and
and
and
if
we
can
deal
with
all
of
them.
I
I
I
just
have
to
go
over
them
and
and
figure
out.
I
I
haven't
been
working
on
many
of
those,
but
I
don't
know
if
anyone
else
is,
as
juan
carlos
said,
that
the
telegram
and
the
github
are
are
being
worked
on.
So
I
have
no
problem
on
reviewing
them.
C
C
A
Yeah
there's
the
the
dandelion
voting
and
the
hatch
one.
I
think
those
are
the
two
that
we've
well.
We
already
started
the
hatch
one
in
like
the
last
legal
session
of
last
year,
where
we're
going
through
that,
so
that
I
feel
like
that
one's
sort
of
a
good
one
to
be
in
the
backlog,
because
we
could
probably
get
it
done
and
then,
if
we
want
to
start
the
dandelion
voting
one,
this
that's
cool,
but
I
doubt
I
doubt
we
would
get
to
it
finishing.
A
C
A
What
I
would
say
is
both
bonding
curve
and
conviction.
Building
probably
shouldn't
be,
they
would
be
a
distraction.
This
sprint
we
have
an
extra
month
and
a
half,
probably
from
the
hatch
date
to
do
those
finalize
those
you
know
so
like
yeah.
The
most
important
are
probably
the
social
media
terms
and
conditions,
because
I
mean
they're
not
necessarily
critical
to
hatch
but
they're,
very
nice
to
have,
and
literally
the
augmented
bonding
curve
and
the
conviction.
D
D
Yeah,
but
the
way
we're
separating
them
is
that
there
are
three
different
buckets
for
forum
proposals
and
the
ones
for
cv.
They
would
arrive
in
the
forum,
but
they
would
go
to
conviction
voting
so
like
I
understand
it's
not
urgent,
but
I
just
feel
like
it
would
be
clean
if
we
had
it
already
now
that
people
are
submitting
to
the
forum
that
will
go
there,
but
I'll
I'll.
Keep
that
in
the
in
the
in
the
backlog
of
this
print,
then.
A
I
think
there's
like
the
terms
and
conditions
people
see
in
the
forum,
which
I
guess
that
forum
proposals
needs
to
be
broken
up
into
three
different
terms
and
condition
issues
because
the
three
different
deliverables,
but
basically
the
what
do
you
tell
the
people
who
are
proposing
in
the
form
and
then
there's?
What
do
we
actually
put
in
the
check
box
of
the
conviction
voting
website?
You
know
when
they
go
to
click,
make
this
proposal
there's
going
to
be
something
there
and
we'll
probably
have
some
last
minute
things
that
we
have
to
add.
D
A
C
A
C
A
A
D
H
D
H
Thinking
work:
okay
for
the
purpose
of
now.
It's
something
that
I
think
is
probably
not
going
to
be
in
this
sprint,
so
maybe
we
just
put
it
in
our
backlog
and
in
our
one
of
our
future
sprinting
sessions.
We
come
back
to
that
unless
I
don't
think
there's
an
urgent
reason
for
that
to
be
in
this
sprint.
Is
that
correct
general
agreement?
Okay,
okay,
cool!
H
D
G
Yeah
I
can
make
a
I
can
ask
marco's
bandwidth
is
super
low,
so
I
often
do
graphic
design
that
never
gets
on
the
github
board
or
scene,
but
I
do
graphic
design
a
lot.
So
I'm
trying
to
synthesize
this
process
so
that
everybody
here
can.
I
mean
I
sent
the
template
that
I
use,
I
believe,
but
I'll
send
it
again,
so
everybody
can
make
their
own
can.
H
D
H
F
H
So
we're
looking
at
the
the
tec
coordination
workspace
in
zenhub
and
it
has
a
list
of
all
of
the
the
issues
that
are
labeled,
onboarding
and
next
sprout
and
if
you
haven't
had
a
chance
to
label
all
the
issues
that
you
want
in
the
next
sprint.
Let
me
know
and
I'll
take
this
off,
but
generally
things
go
a
lot
faster
if
they
are
labeled
next
sprint,
so
we
can
really
filter
the
the
the
prioritized
list
for
each
working
group
and
the
question
is
what
in
in
what
what
is
like?
H
F
F
F
Yeah,
okay,
yeah
yeah,
because
there
was
no.
There
was
no
issue
for
what
we're
doing
now,
which
is
basically
that's
why
I
created
another
one
and
I
deleted
it
and
I
closed
it
because
I
thought
it
was
wrong,
which
was
basically
the
what
we
are
doing
now,
which
is
getting
stuff
commitments
and
an
onboarding
hatcher's
onboarding
archers
that
we
are
sort
of
close
to
us.
So
I
created
an
issue
for
that
and
I
closed
it
thinking
it
was
the
same.
Clearly
it
wasn't
so,
basically
we
are
doing
that.
F
F
F
H
F
A
G
F
E
H
F
I
don't
know
if
it
works
for
you,
but
I
will.
I
don't
know
if
it's
possible
to
do
but
like
I
will
just
probably
have
two
permanent
issues
which
are
onboarding,
hatcher's,
onboarding
and
every
every
sprint
we
just
change
or
edit
the
content.
We
check
the
ones
that
has
been
filled
or
finished
and
then
we
can
keep
sort
of
tracked
through
time.
F
F
H
H
F
Okay,
well,
this
is
print
in
particular,
it's
to
try
to
see
if
we
can
get.
I
don't
know
if
it
would
possible
to
have
the
this
section
of
systack
tokens
jessica.
Do
you
remember
this
section
of
the
welcome
to
the
tec
forum
post?
That
is
not
complete
because
we
are
still
waiting
for
legal.
I
don't
know
jessica
if
you
have
any
update
on
that
or.
G
Oh
you
just
what's
next
steps
for
the
welcome
to
tc
section
yeah,
I
think
probably
you
and
I
have
a
few
things
to
go
over.
So
maybe
we
just
do
30
minutes
and
we
do
that
like
disclaimer
thing
and
we
do
just
like.
I
wanted
to
ask
you
to
put
some
more
linking
in
some
of
the
posts,
so
I'll
explain
that
and
yeah
just
revisit
this
and
see
where
else
we
can
link
and
now
fill
in.
I
went
today
and
filled
in
about
the
what
we
fund
proposals
but
yeah.
G
F
There
is
also
a
recurring
issue
that
I
will
do
time,
which
is
keeping
the
forum
update
every
sprint,
because,
basically,
what's
what's
happening
is
that
we
need
like
every
spring.
We
need
today
with
legal.
If
something
changed,
I
need
to
go
to
the
forum
every
spring.
We
need
to
check
if
the
proposals
are
there
like
or
like
the
corrections
that
we
need
to
do
so.
F
I
will
also
add
the
one
that
the
forum
should
be
also
dated
and
constantly
checked
if
it's
up
to
date
to
this
the
latest
sprint
or
to
the
next
sprint.
However,
you
want
to
call
it
so
that
will
be
also
a
recurring
one
that
I
will
do,
but
for
now
it's
just
to
sort
of
what
jessica
just
mentioned.
Also,
it's
like
a
little
a
lot
of
small
tasks
that
are
not
worth
it
to
create
an
issue
for
them,
but
they
are
not
meant
to
be
blocked.
F
H
H
G
G
It's
going
to
take
a
couple
of
hours
and
then
specifically
for
that
video.
It
is
an
epic.
I
would
like
to
include
it
in
this
sprint,
maybe
to
start
to
draft
a
little
more
solid
idea.
Like
we've
gotten,
some
I've
got
collected
some
brainstorming
and
I
would
like
to
start
to
sketch
out
a
video.
I
had
a
seminar
discussed
yesterday,
so
maybe
in
this
sprint
we
can
I'd
like
to
start
a
brainstorming
document
to
start
to
synthesize
the
feedback
and
drop
the
sketch
out.
G
H
F
H
F
F
No,
I
meant
that
this
is.
This
is
part
of
the
of
conversations
that
we
have
regarding
tracking
the
list
from
craig
or
or
any
kind
of
the
trusted
seed
list,
so
it
all
is.
There
is
a
bunch
of
issues
that
that
tackle
the
same
thing
that
we
have
just
for
one,
for
whatever
reason
created
more
than
once,
so
I
will
close
that
track.
F
H
H
G
F
This
is
a
peculiar
one,
because
we
have
had
this
conversation
with
in
the
last
call
time,
if
you
don't
recall,
if
you
recall,
regarding
when
we
asked
when
we
do
the
the
onboarding
of
the
hatcheries
of
the
list
from
from
grief,
and
then
we
asked
about
what
were
the
requirements
and
their,
I
mean
the
requirements.
Besides
the
legal
of
signing
up
the
association
and
because
of
justice
kind
of
stuff,
there
were
no
more.
I
don't
know
if
there
is
other
aspects
or
requirements
that
we
have
missed.
A
F
A
C
Maybe
maybe
yeah
right,
maybe
I
was
saying
yes
with
my
head
watching
me:
maybe
we
can
create
another
one.
I
consider
that
this
will
be
finished
once
we
have
that
voting
and
we
close
that
voting,
but
maybe
we
could
add
another
one
which
will
be
actually
publishing
them
to
everyone.
So
everyone
is
aware
where
to
figure
out,
what's
the
requirements
to
become
a
hatcher,
and
that
would
be
something
beyond
legal
and
for
a
forum
and
or
communications.
C
G
And
just
two
things
on
that,
I
think
it
number
one
speaks
to
how
important
it
is
to
be
clear
in
the
naming
of
the
issues
and
also
the
descriptions,
because
I
think
that
is
what
adds
sometimes
the
confusion
and
having
like
many
many
issues
is
what
is
this
thing?
This
was
actually
a
legal
working
group
issue
about
determining
what
other
requirements
and
yeah
there's
a
separate
issue
of
publishing
a
content
piece
which
I
have
planned,
which
is
not
on
the
board.
G
Yet
post
vote
is
like
well,
we
have
to
decide,
you
know
we
can
do
one
post
on
the
vote,
what
happened
or
we
can
make
that
the
establishing
the
requirements.
I
agree
with
griff
that
until
there's
a
call
to
action
might
be
kind
of
silly,
but
we
can
definitely
draft
it.
Griff
actually
already
pretty
much.
Did
the
draft
so
yeah
separate
issue
and
we
can
put
it
on
comms
board,
but
yeah.
It
will
be
a
combined
legal
and
comms
effort.
H
Cool,
so
I
changed
the
wording
to
draft
very
good
point
jess.
I
totally
agree
the
more
the
more
clear,
the
naming
and
the
the
description
inside
the
body
of
the
issue.
The
the
faster
a
lot
of
this
goes
faster.
A
lot
of
this
goes
the
clearer.
A
lot
of
this
is
the
higher
visibility
everyone
has
into
all
of
the
work
streams.
H
G
H
G
G
C
H
H
F
F
F
H
G
Yeah,
that
sounds
good.
There
are
two
issues.
One
issue
is
actually
setting
up
the
crm
and
like
the
subscription
and
choosing
the
platform,
and
then
this,
the
other
one,
is
actually
organizing
and
figuring
out
what
emails
and
how
to
kind
of
manage
that
information,
because
there's
some
legal
ties
to
it
so
yeah
these.
G
F
F
C
H
G
Yeah,
I
went
through
all
of
the
ones
that
are
on
the
board
and
then
I
need
to
add
all
the
new
ones
and
a
lot
of
them
actually
apply
to
this
sprint.
Since
the
common
stack
tec
comes
narratives
meeting
the
other
day
so
but
yeah
we
can
start
with
those.
I
I
there's
a
people
and
a
lot
of
them
are
epics
that
need
to
be
try
our
best.
G
G
So
I
think
there
needs
to
be
two
separate
issues,
but
we
were
kind
of
laughing
like
I'm
doing
the
tldr
of
the
tl,
dr
that's
more
like
that
any
community
can
come
and
be
like.
Oh-
and
this
is
like
the
index
of
the
library
of
the
parameters
and
then
jake
is
working
on
more
for
the
devs
to
be
able
to
come
and
like
go
to
github
and
like
find
the
contracts,
and
is
that
right,
jake.
E
Yeah
we
need
a
tldr
of
the
because,
for
instance,
the
full
spec
for
aragon
is
massive,
and
we
needed
to
make
something
like
that.
Just
for
the
tec,
for
the
hatch
and
me
and
griff
are
working
on
that,
but
we're
what
I
came
up
with
is
actually
going
to
work
better
for
as
far
as
the
full
spent,
so
the
tl
dr
itself,
as
in
what
jessica
originally
wanted,
and
what
that
is.
E
G
I
would
say
tamara
for
the
purpose
of
this.
We
can
leave
that
leave
that
issue,
as
is
you
can
assign
it
to
me.
My
plan
is
to
bullet
point
it
out
and
then
get
help
from
jake,
and
maybe
we
can
also
get.
I
don't
know
what
could
be
interested
because
he's
documenting
this
for
other
dows
and
such
but
anyway,
you
can
leave
it
as
is,
but
it's
not
for
the
sprint.
We
can
push
it
to
the
next
sprint.
A
A
G
And
maybe
atta
would
be
interested
to
help
on
this,
because
I
see
it
as
like.
This
is
a
super,
huge
value
that
you
guys
have
created
for
other
doubts
like
it's
like
a
library
of
parameters.
I
talked
to
a
few
dolls
about
it
and
they
were
like
oh
yeah.
I
want
to
see
this
so
yeah.
We
can
leave
it
for
another
spring.
G
I
would
also
ask
you
know
this
is
a
creative
process
that
can't
be.
You
know
sam
and
I
talked
about
this
yesterday,
so
I
I'm
asking
for
some
feedback
and
I'm
going
to
go
through
a
process
with
durgados
and
I'm
going
to
go
through
yeah
we're
revisiting
this
and
it
kind
of
ties
in
a
bit
as
well
with
like
revisiting
the
mission
and
the
vision
with
livia,
so
yeah.
G
D
H
Maybe
I
propose
because
it
is
actually
it's
one
issue
in
a
epic
itself,
and
maybe
we
what
we
do
is
we.
We
know
that
you're
it's
in
progress
right,
so
maybe
we
add
it
to
our
sprint
backlog
and
then,
in
our
working
session
we
can
separate
the
pieces
that
are
part
of
this
sprint
and
other
sprints
does.
G
For
that,
I
do
think
it
is
important
to
have
a
visual
representation
and
definitely
did
awesome
work
in
having
that
diagram.
So
I
was
just
asking
for
some
feedback
from
griff
and
santi
and
jeff
as
well
as
to
what
we
think
is
the
most
helpful,
and
maybe
also
this
would
be
great
to
have
for
the
how
to
become
a
hatcher
so
that
people
can
not
only
read
the
steps
but
see
like
step
or
the
launching
part.
One
is
like
mondale
watching
part.
G
Two
is
this,
so
I
was
just
asking
for
some
feedback
on
what
we
think
the
best
representation
is
so
that
I
have
a
meeting
with
marco
next
week,
a
design
meeting.
So
then
I
can
bring
it
up
with
him
and
see
what
his
bandwidth
is
and
get
it
like
at
least
a
bit
in
his
flow.
But
I
I
would,
I
guess,
try
to
get
feedback
before
next
week
would
be
great
if
santi
and
griffey
have
some
ideas-
and
I
asked
in
the
issue
there
for
feedback
so
that
we
can
take
the
next
step.
C
C
G
Awesome,
okay,
so
maybe
maybe
I'll
hold
off
with
marco,
like
I
won't
give
it
to
him
next
week.
So
maybe
this
sprint
we
just
like
yeah,
we
might
need
there's
two
or
like
we
may
have
iteration
one
which
is
like
sandy
or
sam.
You
guys
draw
it
and
we
can
use
it
for
the
how
to
become
a
hatchery
publishing
thing
and
then
we
could
pass
it
to
marco
if
we
want
something
more
fancy
or
whatever
and
we
could
have.
I
think
we're
going
to
have
a
couple
of
versions
of
this.
Maybe.
H
Cool,
so
it
definitely
sounds
like
not
something
for
this
sprint,
but
sort
of
collaboration
with
the
work
that
sam
is
doing
and
even
in
the
next
sprint,
it'll
be
ready
to
sort
of
release
on
the
public
tec
email
newsletter,
outbound
hatching
this
looks
like
a
bigger.
This
is
an
epic,
oh!
No,
this
is
not
an
epic,
it's
part
of
an
epic.
Oh,
it
is
an
epic
yeah
with
no
nothing.
Oh
here
organize
all
our
tc
member
emails.
H
G
G
C
B
C
C
H
H
G
A
But
it's
basically
neurons
downward
tweak
where
which,
with
the
common
stack,
has
done
a
couple,
or
at
least
once
I
feel
like
we
did
it
twice
and
yeah
we've.
The
the
deadline
is
that
when
we
have
a
one
slide
by
tomorrow,
although
you
know
neuron-
and
I
are
bloody
buddy,
if
it
doesn't
happen
tomorrow-
we'll
be
able
to
sneak
in
there,
but
it
would
be
polite
to
get
it
to
him
tomorrow
and
I
actually
did
not
read.
I
didn't
really
put
these.
A
A
H
A
No,
it's
just
a
it's
a
gathering
place
for
people
who
are
like.
I
want
to
join
it.
What
dials
are
there
and
so
then
you
the
way
they
did
it
last
time
was
that
they
have
like
a
two-hour
call
for
everyone
to
talk
about
their
slide
and
then
each
and
then
say
when
they're
going
to
have
their
like
onboarding
call
so
like
so
someone
can
go
to
this
two-hour
meeting
and
see
20
dollars
present
back
to
back-to-back
and
see
which
ones
they
want
to
join
and
then
go
to
their
individual
sessions.
G
Okay,
may
I'll
have
a
look
at
the
requirements,
and
maybe
I
will
look
at
maybe
if,
if
jake
since
you're
the
design
other
design
guy,
you
can
help
me
make
something
flashy
I
can
do
the
content
and
then
olivia
we
can
discuss,
or
maybe
dan,
maybe
dan.
Whoever
has
time
I
I'm
happy
to
participate
and
present
or
dan
if
you
want
to
present
since
you're
doing
a
lot
of
community
management
you're.
A
C
A
H
G
Basically,
the
main
other
projects
that
are
ongoing
in
epics
are
the
new
tec
discord,
which
I
also
need
to
break
down
into
some
issues.
A
lot
of
issues.
That's
a
huge
project.
I
need
to
also
determine
the
timeline
of
when
we're
going
to
launch
that
and
then
yes,
all
of
the
pieces
from
the
mirror
board,
all
the
things
that
were
developed
there.
G
We
can
put
at
least
on
the
backlog,
and
there
are
a
few
of
them
that
I
may
tackle
this
sprint
like
there's
going
to
be
a
piece
after
the
legal
vote
which
is
kind
of
like
we
called
it
prep
for
becoming
a
hatcher.
So
it's
not
the
full
how
to
become
a
hatchery
and
go
to
the
dap.
It's
going
to
be
like
a
prep
like
hey
everybody
voted.
Yes,
we
as
tc
blah
blah
blah
are
gonna
use
the
common
stack
and
then
maybe
I'm
gonna
work
on
one
one
or
two
other
pieces.
G
H
Okay,
cool
excellent
yeah
that
works.
This
is
our
first
sprint
we're
it's
not
going
to
be
perfect.
It
like
slowly
refined
over
time.
So
let's
be
super
flexible.
Okay,
so
then
jess.
If
it's
okay,
we're
gonna
move
on
from
communicating
I'd
say
what
we
have
left
is
transparency,
legal,
sem
garden
swarm,
which
we've
moved
all
of
the
garden
swamp
issues
that
were
here
to
the
garden
swarm,
which
we
we
talked
about
today,
which
I
think
is
the
more
natural
place
to
to
review
it
in
our
weeklies.
H
I
was
hoping
that
maybe
we
could
still
have
you
give
an
update
on
today's
call,
but
we're
the
last
10
minutes
so
maybe
in
the
next
stuart
sink.
If
you
would
join
us
again,
because
zap
only
has
to
do
this
now,
so
it's
easy
to
bring
you
in
and
we
get
we
can
have
you
give
an
update
to
afterwards
there
and
then
santi.
I
think,
is
there
anything
you
want
to
discuss
about
what
legal
wants
to
do
these
next
two
weeks,
I
know
you're
working.
C
H
D
C
C
C
C
C
H
C
D
E
E
That
spec
and
get
that
finished
up
that's
evolved
into
something
new
that
I
have
some
new
issues
that
are
going
to
go
into
that
as
well:
they're,
fine,
where
they
are
in
the
new
issues,
the
tech
hatched
out
params
decision
making
process
print
two,
because
it's
gonna
coin
spec
and
we're
gonna
have
all
of
that.
We
have
to
get
that
done
in
the
next
two
weeks
regardless.
So
that's
really
my
only
big
issues
right
now,
because
I
have
to
dedicate
everything
towards
everything
else.
E
H
E
C
Okay,
yeah
the
today
morning,
we're
gonna
be
with
yeah
building
that,
because
we
didn't
have
anything
before
and
there
is
like
two
things
like,
for
example,
we
have
some
bad
habits
from
behind.
Before,
like
we
were
like
working
in
the
shadows
and
we
were
doing
the
work,
but
we
we
didn't
have
like
something
organized
and
our
epic
right
now
is
to
establish
the
system,
but
it's
not
for
the
next
sprint,
because
it,
I
think
it
it
will
going
to
take
more
time
right.
B
C
Epic,
and
for
this
spring
we
would,
we
will
going
to
try
to
establish
a
system
for
recording.
The
calls
like
like
our
priority
right
now,
is
like
if,
for
example,
if
I'm
not
able
to
be
on
a
call
or
ivy
or
anyone
like
it,
creates
something.
That's
easy
for
anyone
to
record
a
call
and
yeah
just
have
a
system.
So
everyone
know.
B
So
I
would
really
like
appreciate
if
we
can
like
make
the
the
calendar
the
most
like
clear
possible,
so
that
I
can
like
program
a
new
schedule
for
the
gravity
call,
and
also
because
this
gravity
call.
After
like
the
21
of
january,
we
are
going
to
start
the
gravity
training
and
I
would
like
it
to
be
like
a
very
open
space
for
everyone
and
that
that
our
call
doesn't
conflict
with
with
anything.
B
H
Okay,
okay,
yeah:
we
need
a
new
gravity
timeslot,
there's
one
thing
that
we
usually
do
with
these
processes,
which
is
choose
a
sprint
goal
like
a
rallying
cry
that
get
behind.
I
would
like
to
open
up
the
discussion
to
suggestions
for
to
for
this
sprint.
This
first
sprint
sprint
goal.
If
anyone
has
a
suggestion,
please
now
say
what
your
suggestion
could
be.
What
should
we
all
like?
What
should
our?
What
is
our
focus
for
this
sprint
goal
and
or
just
our
our
rallying
cry.
H
C
My
my
suggestion
is
that
we
coordinate
much
better
after
this
first
spring.
I
think
we're
gonna
we're
gonna,
better
understand
each
other.
We're
gonna,
probably
better
use
the
tool
that
we
have,
which
is
awesome,
but
I
I'm
the
first
one
to
to
say
that
I've
I
haven't
been
using
it
as
much
as
probably
I
need
to,
and
and
probably
make
these
meetings
much.
You
know
smoother
and
faster
and
easier
to
follow.
H
H
Cool
okay,
thank
you,
everyone
and
thank
you
for
that
parting
wisdom.
Assante.
I
think
I
think
you
know
the
you're
right,
the
more
the
more
we
do,
this
the
more
familiar
and
it
feels
comfortable,
and
then
we
see
that
things
just
become
easier
to
in
terms
of
like
knowing
what
what
other
groups
are
working
on
and
syncing
together
on
our
workloads
every
two
weeks,
and
we
just
constantly
refreshing
our
priorities
against
everything.
New
that's
come
up
since
the
last
time
we
we've,
you
know,
prioritized
our
work,
all
right,
awesome!
H
H
G
B
B
B
B
And
now
we
are
going
to
jump
to
the
word.
I
love
you.
That
is
one
of
my
favorites
and
I
really
love
to
say
to
all
of
you.
I
love
you
because
you
have
brought
many
like
a
lot
of
light
to
my
life
and
I
hope
I
can
also
bring
light
to
your
lives
as
well,
and
I
love
you
because
you
spend
like
a
lot
of
time
with
me
hearing
me
and
listening
to
me
and
making
my
ideas
better,
and
I
hope
also
that
you
can
do
everything.