►
Description
🙏 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
Nation
points
in
every
working
group
they
can
achieve
that
like,
for
example,
sample
can
still
have
clarity,
doesn't
change
anything,
but
it
doesn't
matter
that
for
the
rest
of
the
communities
on
the
working
groups,
I
feel
we
have
this
level
of
awareness.
I
think
the
center
hub
is
not
what
is
wrong.
It's
just
the
way.
It's
structured,
it's
not
even
wrong.
It's
just
the
way
that
it's
structured.
A
It's
not
very
efficient
because
the
awareness
on
the
awareness
gets
gated
to
the
people
who
attend
this
school
and
is
gated
to
usually
the
stewards,
no
one
else.
So
we
don't.
We
don't
actually
have
awareness
and
there
is
no
coordination
between
working
groups,
because
only
people
who
knows
what's
going
on
in
the
store.
So
I
feel
like
for
me
for
me.
I
will
suggest
like
hey.
If
you
are
receiving
compensation
for
any
role
on
dc,
you
should
join
this
call
and
it's
a
sort
of
a
mandatory
kind
of
thing.
B
B
You
know
like
here's,
five
different
epics,
we
all
choose
what
epic
to
swarm
to,
and
so,
if
you're
in
communitas,
you
say,
okay,
how
can
I
help
achieve
that?
Epic,
and
then
you
can
have
your
own
community
toss
working
group
like
issues
that
you
work
on,
but
they're
not
necessary
to
achieve
for
that
that
series,
but
I
think,
having
a
collective
understanding
of
like
the
direction
we're
of
where
we're
heading
as
a
community.
A
Yeah,
I
think
that
simplicity,
for
example,
I
found
that
when
I
put
the
new
proposal
for
the
next
term
for
communitas,
I
create
an
epic
that
match
that
funding
proposal.
A
So
that's
the
direction
where
I'm
going
and
I
feel
like
we
should
scale
that
kind
of
process
for
for,
like
you
remember
when
we're
doing
the
token
or
we're
doing
the
design
and
so
on.
There
were
this
critical
labeled
issues
that
made
very
simple
to
understood
that
all
need
to
stop,
but
this
because
this
is
priority.
A
So
for
me
this
seasonal
system,
whatever
you
want
to
call
this
amount
of
time
that
they,
everyone
is
focused
on
one
or
two
things-
should
be
a
separate
board
or
should
be
just
a
column
separated
from
the
rest
and
a
column
that
says
this
season
or
something
along
those
lines
and
in
that
season,
we'll
keep
track
of
all
the
align
issues
that
needs
to
be
focused
and
prioritized
the
same
way
we
were
using
for
the
token
design
back
in
the
day.
A
It's
just
that
this
will
be
more
on
the
mvv
or
more
of
a
season
or
whatever
happens
now.
Yeah.
B
And
so
you
think
we
should
stick
with
the
individual
issues
within
those
in
hub.
A
I
think
they
one
of
the
very
few
things
that
I
think
are
really
helpful
and
they
are
tiring,
maybe,
but
I
feel
they're
really
helpful.
It's
the
practice.
The
common
practice
of,
if
you
wanna,
be
accountable,
just
create
an
issue
for
the
tasks
that
you
that
you
say
you
were
gonna.
Do
that
simple?
That
simple
ask.
I
feel
it's
the
minimum
that
we
can
ask
for
anyone
receiving
funds
from
the
dc.
A
It's
really
simple,
and
maybe
it's
unbearable
in
the
sense
of
how
many
things
there
is
on
the
board,
but
that
that
that
action-
or
maybe
it's
not
a
single
but
action
of
just
keeping
this
common
place
where
everyone
knows
that
they
have
to
put
their
issues
in
order
to
be
transparent
and
compensated.
That's
a
very
simple
ask
that
I
feel
we
should
keep
okay.
C
D
C
A
But
that's
because,
after
the
launch
of
the
token
or
the
process
we
sort
of
since
the
technical
team
stopped
sort
of
using
github
in
in
that
recurring
base,
we
just
sort
of
dropped
the
ball
on
that,
but
not
because
I
think
it's
just
that.
It's
just
that
we
dropped
the
ball
because
there
was
no.
There
was
no
race,
there
was
no
goal
for
or
is
horizon
where
we
were
all
aiming
to
so,
but
I
think
it's
just
some
it's
just
a
time.
It's
just
a
call
for
redo
a
little
bit
the
board.
A
I,
for
example,
I
don't
know,
for
example,
if
I
delete
all
the
boards
that
will
affect
their
reward
system
or
source
cred.
I
don't
know
if
someone
scored
is
taking
information
from
github
to
I
don't
know,
I'm
just
an
example
like
for
me.
I
would
just
probably
create
a
very
simple,
very
simple
minded
board.
Parallel
to
this
one
or
a
new
one.
I
don't
know,
but.
A
Yeah,
I
think
at
at
some
point
there
could
be
coordination
that
it's
external
or
internal,
and
maybe
there
are
things
that
we
can
coordinate
internally
onsen
hub
and
then
we
can
just
simplify
it
on
a
very
simple,
open,
21
notion.
The
thing
about
using
cenhop
at
the
moment
is
that
we
rely
on
giving
people
access
to
github
and
then
that's
the
barrier
entry
that
not
everyone
have
access
to
github
so
for
them
to
edit
the
issue
you
need
to
have
access
to
github
and
or
at
least
be
named
on
that
issue.
A
I
remember,
for
example,
jean
for
the
longest
time
he
couldn't
do
anything
because
he
really,
and
it
always
happens,
but
most
of
most
of
the
people
doesn't
know
we
just
dropped
the
ball.
A
lot
of
the
newcomers
doesn't
know
that
we
track
things
on
github
or
send
sunhop.
So
for
me,
it's
just
like
hey,
let's
simplify
it.
Let's
take
out
some
of
this
gating
thing
and
just
do
a
free
notion,
kind
of
thing
and
just
put
all
the
things
in
notion
and
just
simple
goal:
driven
board.
B
Yeah
I
mean,
and
so
one
of
the
things
that
I'm
like
I
get
confused
about
is
like
you
know,
if
I'm,
if
I'm
a
contributor
within
you
know,
community
toss,
do
I
really
you
know
what
is
the
benefit
of
knowing
what's
going
on
in
gravity?
You
know
like
we
want
to
have
this
kind
of
complete
information
about
the
entire
thing,
but
I
think
that's
what
stewards
and
you
know
the
leaders
of
the
commons
are
responsible
for-
is
that
distributing
that
information
across
working
groups?
B
A
Challenge
that,
if
we
are
in
a
in
a
commons
that
aspire
to
use
the
model
of
talking
engineering,
only
focused
on
one
aspect
of
talking
engineering
could
be
omega,
it
could
be
communitas
or
could
be
sample
one.
It
won't
be
in
in
consonance
with
the
spirit
of
attack
engineering
system
that
needs
to
have
different
layers.
A
So
if
we
were,
for
example,
this
is
this
example,
that
is
that
I
came
from
the
mistake
and
then
it
was
corrected.
Enos
dao
is
not
a
dao
anymore,
it's
a
funding
layer
because
they
figured
out
that
they
didn't
need
a
dao.
Actually,
this
is
not
a
social
space;
they
don't
need
contributors,
they
don't
need
any
of
that.
They
just
need
projects
works
on
ens,
so
they
deleted
the
enso
in
concept
and
now
it's
a
funding
layer
and
that's
it
so
they
simplify
it
to
a
way
that
it's
easier
to
articulate.
A
So
in
that
case,
for
example,
I
will
say
if
I
work
in
the
enes
funding
layer,
I
don't
need
to
know
what's
going
on
the
foundation,
I
don't
need
to
know
what's
going
on,
because
that
system
is
it's
focused
on
development.
It's
a
technical
system
very
focused,
no
need
to
have
overlap
of
all
the
layers,
because
there
is
no
other
layers,
only
the
governance
layer,
but
here
is
not
the
case.
We
are
talking
engineering
system
and
I
feel
that
having
only
one
side
of
the
coin
will
be,
you
will
be
missing
yeah.
B
I
agree,
and
I
guess
just
how
do
we
remove
that
kind
of
barrier
from
individuals.
E
A
Were
we
were
having
a
sounding
board
session
regarding
what
to
do
with
the
board?
If
we
need
to
release
it
the
same
way
we
have
revisited
the
community
call.
The
orientation
condole
is
calling
we
needed
to
revisit
the
process
of
retrospective
and
then
nade
was
suggesting
two
different
things,
and
then
we
were
just
back
and
forth.
E
E
So
I
love
to
do
something
else
and
just
to
have
this
print
like
what
should
happen
really
is
each
working
group
does
their
own
planning
and
then
you
know
that
that
just
happens
as
a
cycle
and
then
the
sprint
planning
is
for,
like
the
commons
sprint
plan
and
not
for
every
working
group
that
you
know
maybe
isn't
necessarily
like
they
have
their
own
sprint
planning
or
their
own
van,
like
their
own
project
management,
their
own.
You
know
management
in
their
working
groups,
but
I
think
having
everyone
do
it
on
the
spread
board.
B
Concern
he
had
was
like
the
accessibility
to
things
like
this
in
hub
board
and
that's
what
kind
of
prevented
people
from
participating
for
a
lot
of
it.
But
I
don't
edit,
you
probably
sorry,
you,
you
explain.
Yeah.
A
So
I
challenged
that
idea
that
I
do
believe
that,
like
I
do
believe
that
everyone,
every
working
group
should
have
their
own
system
if
they
want
to
organize
themselves,
but
I
see
so
much
positive
and
having
this
common
space
and
common
ground
for
everyone
to
be
aware
of.
A
What's
going
on
in
a
detailed
way-
and
I
was
suggesting
that,
rather
than
having
the
stewards
sort
of
only
on
this
conversation
be
more
of
a
contributors
call
kind
of
format
and
that
for
people
who
are
trying
to
for
people
who
are
receiving
compensation
that
this
should
be
a
must
to
be
kind
of
space
because
it
helps
people
for
me.
A
It's
again
is
this
idea
of
talking
engineering
and
the
layers,
and
this
perception
that,
if
you're
working
only
on
your
area
without
any
kind
of
awareness
of
what
surrounds
you
you're,
not
of
talking
engineering,
you're
done
you're,
not
doing
a
talk,
engineering
approach,
it
doesn't
mean
you
need
to
be
involved
in
all
the
layers.
It
just
means
that
you
could
be.
You
could
be
helped
by
having
awareness
about
the
other
things
around.
You.
E
I
bristle
at
making
anything
mandatory
for
compensation
because
timing
time
zones
all
of
this
can
be
blockers
well.
First
of
all,
I
just
I,
I
think,
making
a
two
hour.
Meeting
mandatory
to
receive
compensation
is
probably
too
heavy-handed,
but
also
practically
speaking,
not
achievable.
E
I
think
it's
difficult
enough
for
people
to
find
an
hour
a
week
that
works
for
everyone.
You
know
even
an
hour
a
month
that
might
work
for
all
contributors,
but
I
think
also,
I
know
I'm
I
feel
really
strongly
here
it's
and
what
you,
what
you
said
about
having
it
be
more
open,
not
more
open
but
more,
like,
I
think,
all
of
the
the
sprint
plannings
should
be
open,
but
they're
not
going
to
be
effective
if
they
are
not
focused
on
specific
streams
of
work.
E
You
know
it's
a
project,
not
12
different
projects,
so
I
think
that
they
should
be
more
focused
on
specific
pieces
of
work
and
it's
super
helpful
to
have
a
review
across
all
of
the
different
streams
of
work.
E
E
You
know
at
the
side,
like
you
know,
maybe
especially
a
working
group
like
omega
or
gravity
or
labs.
You
know
that
are
like
okay.
We,
we
don't
need
to
essentially
know
exactly
what
they're
doing
or
require
mert
or
you
know
ygg
or
you
know,
to
or
wonky
even
to
be
in
these.
These
sprint
planning
calls,
but
everyone
is
welcome
to
join
something
like
that.
A
Right
so
holy
hell,
so
I
was
my
suggestion.
There
it's
impossible
to
have
a
two
hours
call
for
everyone,
but
it
would
be
different
if,
for
example,
we
encourage
that
working
groups
will
have
this
this.
This
coordination
layer
within
their
calls
within
the
coordination
calls.
So
the
last
10
minutes
of
all
working
groups
do
do
this
and
they
do
a
checking
on
this
and
then
only
they
focused
or
most
relevant
according
to
the
season.
A
Issues
or
or
planning
comes
retrospective.
So
the
contributor
who
is
working
on
something
relevant
to
that
season
comes
retrospective,
update,
shares
and
so
on.
So
it
will
be
a
focused
only
retrospective
and
then
we'll
leave
the
rest
of
the
of
the
coordination
of
the
working
groups
to
the
working
groups
within
their
weekly
sync.
A
So
we
will
have
this
time
only
for
focused
season
theme,
whatever
you
want
to
call
actions
and
contributors
who
are
working
on
that
have
aware
of
what
other
working
groups
are
doing
on
the
same
topic
or
the
same
subject
or
on
the
same
season.
So
you
will
have
at
least
these
people
focused.
A
So
if
we
have
like
a
more
objective
driven,
I
was
using
the
example
of
when
we
were
doing
the
token,
and
then
we
had
this
label
was
named
critical
and
the
critical
layer
will
help
us
to
focus
on
which
things
were
priority,
and
it
would
even
give
more
time
to
grave
to
explain-
and
you
know,
with
respect
so
doing
something
very
similar
to
have
this
mission-driven
or
objective-driven
smaller
systems
or
sprints.
A
Whatever,
whatever
system
we
found
is
better
and
then
only
the
critical,
let's
say
critical
for
that
objective
issues
or
or
tasks
comes
to
these
meetings
and
shared,
and
we
we
also
decentralized
from
the
stewards
but
the
contributors
who
are
working
on
these
issues
from
those
critical
things.
So,
if
I
think
now
regarding,
for
example,
12th
rune,
it
would
mean
sampo,
it
would
mean
maybe
someone
from
comes
or
someone
from
commuters
who
is
engaging
with
other
communities
to
let
them
know
about
this,
or
you
know
like
having
this.
A
These
two
people
will
be
the
only
ones
speaking
on
this
meeting,
because
those
are
the
objectives
of
this
print,
let's
say
sample
and
the
12
rule
group.
So
everyone
will
have
awareness
of
this
and
something
along
those
lines
and
we
keep
the
coordination
for
every
working
group
within
the
working
group
not
on
this
call
necessarily.
B
No,
I
just
you
know,
I
think,
that
being
able
to
even
have
that
coordination
be
extended
like
escalated
to
the
community
within
sprint.
Planning,
I
think,
is
a
really
interesting
concept
where
we
say:
okay,
you
know
if
it's
important,
if
it's
critical,
if
it's
something
that
needs
to
get
done
quickly
package
it
into
an
epic,
submit
it
for
the
community,
sprint
planning
call
and
make
your
case
for
it.
Why?
This
is
important?
B
Why
the
community
should
help
you
and
developing
this
very
very
quickly
and
get
get
everybody
on
board
in
terms
of
like
whether
it
should
be
prioritized
or
not,
because
I
think
that
if
you
have
working
groups
submitting
those
those
those
issues
that
we're
going
to
vote
on
or
decide
what
we're
going
to
focus
on
for
that
sprint,
I
think
it
it
kind
of
solves
that
challenge
and
allows
us
to
kind
of
have
this
conversation
of
prioritization
so
like
when
we
get
to
sprint
planning.
F
Yeah
sam,
I
just
saw
your
comment
that
that's
what
tokenlock
does
and
we
chatted
a
little
bit
about
it,
because
nate
brought
this
idea
in
the
stewards
console
and
it
sounded
like
awesome
that
we
can
have
this
coordinated
prioritization
and
then
I
thought
we
could
just
start
using
tokenlog,
because
we
have
the
issues
already.
Then
the
community
could
vote
on
what
is
a
priority
for
the
tc.
E
I
am
not
yeah.
I
think
these
are
good
ideas
to
experiment
with,
in
my
experience,
having
many
steps
in
a
process
is
not
necessarily
the
fastest
way.
So
I
think
this
is
a
really
great
idea.
Maybe
we
I
mean
it,
you
know
I
could
see
if
we
need
to
do
something
quickly
like
okay,
this
friend,
we
need
to
finish
this
one
important
thing
it
actually
being
slowed
down
by
saying:
okay,
we
have
to
now
present
it
to
the
community.
Wait
for
feedback
incorporate
the
feedback.
E
So
I'm
not.
I
think
that
there's
some
I
mean,
I
guess
it's
like
where,
where
we're
zooming
in
right,
like
what
are
the
big
priorities
to
focus
on,
I
think,
is
a
community
decision.
The
execution,
maybe
is
not
necessarily
as
interesting
to
the
community
or
even
the
best
use
of
anyone's
time.
If
we
try
to
engage
the
community
on
how
to
execute.
A
So
I
will
suggest
that
we
keep
this
total
log
decision
for
high
level
kind
of
objectives.
So,
for
example,
we
can
have
this
same
format
that
most
organizations
have
in
the
dials
like
every
six
month
period
of
times
you
have
a
new
system
and
then
you
re-evaluate,
reassess
and
reframe
your
objective.
So
every
six
months,
every
three
months,
we
can
have
this
same
token
log
mutation
only
for
these
times,
so
for
for
at
least
the
proposition
of
what
will
be
the
next
objective.
A
The
community
doesn't
need
to
vote
on
every
part
of
the
execution
just
in
a
general
idea,
high
level
concept,
and
then,
if
the
community
decides
that
this
one
or
that
one
is
the
one
that
will
gonna
work
for
the
next
six
months.
Maybe
that's
you
know,
sort
of
worth
technical,
but
I
don't
think
having
token
loan
for
every
every
sprint,
for
example,
will
be
helpful.
I
think
that's
a
little
bit
too
much.
F
I
like
that
idea
and
to
have
a
six
months
focus
or
maybe
even
four
months.
A
Yeah
and
I
feel
like
now
with
the
12
rune
group
sample
strategy,
we
are
from
different
aspects
of
finding
this
rhythm
that
could
be
helpful
to
explore
and
to
also
help
us
to
reassess
our
own
priorities,
like
you
know,
like
an
in-place
self-checking
that
I
feel
we
have
missing,
because
we
I
feel
at
a
certain
level,
we
are
discoordinated.
A
So,
for
example,
let's
say
communities
do
the
cell
checking
in
august,
but
then
stewards,
though,
do
the
self
checking
on
september,
and
that
brings
on
coordination
awareness
level,
because
we
are
not
on
the
same
sort
of
page
and
we
are
mismatched
timings.
So
if,
if
with
this
conversation,
for
example,
about
the
stewards
change
will
happen,
we
will
reassess
or
retalk
about
this.
At
the
same
time,
the
rest
of
these
changes
will
happen.
A
It
could
be
really
interesting.
I
feel
like
to
have
this
overview
and
overlap
and
sort
of
overlap
of
feedback
and
changes
and
puts
and
something
place,
a
mechanism
that
could
keep
us
on
track
and
and
with
the
cards
on
the
table.
If
that
makes
any
sense.
B
So
I
guess
my
question
is:
is
if
we,
if
we
finally
come
to
consensus
on
what
to
do
about
this
sprint
planning,
how
do
we
actually
implement
it?
You
know
what
one
of
the
ones
that
like.
I
think
this
is
the
time
period
where
we
actually
attempt
to
implement
it
like.
I
think
we
should
do
it
as
quickly
as
possible.
In
terms
of
you
know,
while
people
are
on
vacation
and
things
are,
you
know
they
can
come
back
to
an
organized
type
of
sprint,
planning
situation
and
kind
of
go.
B
A
F
No
yeah,
I
think
this
would
actually
be
a
good
snapshot
vote,
because
we
haven't
had
the
chance
to
involve
the
community
on
deciding
how
the
stewardship
happens
in
a
in
a
very
direct
way,
and
this
could
be
something
that
we
engage
like
that.
We
bring
people
into
this
discussion
because
I
think
a
lot
of
people
would
have
something
to
say.
F
You
know
on
the
direction
of
the
tc
and
then
bringing
stewards
more
in
this
role
of
like
what
is
what
are
the
waters
we're
in
and
how
are
we
like
stewarding
the
direction
to
where
the
collective
is
coming
so
help?
Stakeholders
have
an
understanding
of
where
we
at
where
we're
trying
to
go
and
then
have
advice
process,
but
bring
it
maybe
two
options:
a
few
options
to,
or
or
just
reiterate,
in
snapshot.
E
B
Yeah
so
it'll
require
kind
of
an
order
of
approval
in
terms
of
how
we
go
about
it,
because
if
you
know
I
I
don't
know,
I
think,
out
of
all
of
those
things,
the
the
structure
of
stewardship
might
be
the
most
contested
or
most
challenged
type
of
alteration.
But
I
don't
know
I.
I
can't
really
pick
up
on
community
sentiment
on
that
subject.
Right
now,.
A
I
will
say
bluntly
that
there
is
no
community
sentiment
on
stewardship.
That's
it
it's.
I
don't
think
there
is
an
attachment
to
the
figure.
I
think
it's
it's
valuable
from
the
community
perspective,
but
I
don't
think
there's
an
attachment
to
that.
I
want
to
welcome
just
gideon
and
juanka
to
the
call,
and
we
are
debating
a
little
bit
about
retrospective,
so
you're
welcome
to
join
the
conversation.
D
Yeah,
sorry
to
be
late,
folks,
just
missed
it.
B
No
worries
it's
friday,
just
talking
about
sprint
planning,
so
I
mean
we
do
have
enough
people
here
to
talk
about
it,
but
I'm
not
sure
if
we
go
back
or
we
just
trust
everybody
to
update
their
issues
right
now.
Should
we
go
ahead
and
go
through
it.
F
C
C
I
was
just
going
to
say,
like
I
really
like
the
idea
of
you
know
having
this
talking
lock
thing,
so
we
can
so
token
holders
can
signally
what
the
things
they
want
to
get
built
and
then
we
could
use
the
sprint
planning
just
to
you
know
see
who
will
lead
any
like
all
those
epics
who
would
be
like
the
best
person
and
with
someone?
That's
of
course
like
willing
to
do
it
like
they
might.
B
And
I
just
want
to
say
I
like
the
idea
of
voting,
but
I
don't
think
that
it
is
feasible
in
terms
of
you
know
the
people
who
are
going
to
be
voting
are
they
going
to
be
be
the
people
that
are
in
the
room
at
that
sprint
planning,
and
so
that
could
be
everybody.
It
could
be
nobody,
and
so
I
don't
know
if
having
you
know
this
holdings
within
a
single
meeting
to
decide
what
we
do
is
the
right.
B
F
C
E
I
think
a
great
idea
for
it
would
be
for
whoever
it
wants
to
really
quarterback
or
like
champion
this,
to
write
down
something
that
we
could
then
evaluate,
because
one
of
the
like,
even
maybe
go
through
the
exercise
of
like
what
kinds
of
things
are
being
voted
on,
because
the
purpose
of
token
log
was
really
to
allow
token
holders
to
add
features
to
products.
E
So
software
development
new
features
to
development
products
we're
using
github
as
coordination,
so
we're
not
building
features
for
the
community,
we're
coordinating
our
work
streams
to
be
effective
and
the
people
who
know
best
how
to
best
coordinate
their
work
stream
are
the
people
in
that
work
stream
and
not
necessarily
the
community.
So
there
may
be
some
other
kind
of
repository
that
we
have
where
we
allow
the
community
to
vote
on
certain
things
that
make
sense.
But
I
don't
know
I,
but
I
don't
think
for
a
coordination
repository.
E
F
Thanks
for
it,
sorry
just
something
quick
yep
thanks
for
articulating
that
way,
tim
cause.
I
think
what
we
are
missing
is
you
said:
oh
people
in
the
work
streams
know
what's
best
for
that
work
stream,
but
maybe
what
we're
missing
is
the
signal
from
the
community
of
what
is
desirable.
Even
for
that
works
worth
work
stream,
or
what
work
streams
are
not
there
or,
like.
F
D
A
D
I
do
think
it's
hard
for
people
outside
of
like
a
a
work
group.
That's
very
close
to
I
mean
we've
actually
seen
this
in
praise
too,
like
I
think,
sometimes
it's
difficult
for
people
who
are
not
close
to
the
work
to
actually
accurately
quantify
work,
and
I
think
it's
the
same
thing
when
it
comes
to
evaluating
which
particular
strategy
or
path
to
go
down.
D
Context
really
does
matter.
But
having
said
said
that
libby,
I
I
I
wanna
also,
I
mean
I
love
the
fact
that
these
two,
you
tam
and
libby-
you
both
brought
these
things
up
because
it
I
feel
strongly
about
this.
I
think
we
do.
I
don't
know
if
we
need
voting
on
these
kinds
of
issues,
but
I
think
we
definitely
need
some
type
of
sense
making.
You
know
like
some
almost
like
it's
like
a
sensor.
D
You
know
it's
like
ways
of
listening
to
the
desires
of
the
stakeholders,
like
the
builders
who
are
building
stuff,
but
even
more
broadly,
the
people
we
need
to
attract
like
the
the
future
users
of
the
services,
we're
gonna
be
building.
We
we
really
need
some
listening
devices
for
for
being
able
to
pick
up
on.
What's
of
value
to
people
and
I'd
love
to
see
us
just,
you
know
maybe
iterate
on
some
simple
versions
of
that.
I
think
that
would
take
us
a
long.
B
Way-
and
I
just
want
to
make
one
last
comment
with
with,
in
terms
of
of
this-
the
purpose
of
doing
things
like
in
this
manner-
it's
not
so
much
for
me,
as
you
know,
to
prioritize
certain
issues
over
others.
I
think
the
real
value
here
is
is
collectively
deciding
how
to
get
something
done
within
the
community.
B
The
first
thing
we
could
decide
on
is
is
which
one
are
we
going
to
focus
on
for
that
sprint
planning,
and
then
we
discuss
as
a
group
as
a
community
as
working
groups,
how
we
can
contribute
to
executing
on
that
goal
of
executing
on
that
initiative,
and
so
what
can
my
working
group
do
to
contribute
to
this
effort?
What
can
I
as
an
individual,
contribute
to
this
effort
and
and
and
kind
of
mapping
out
what
tasks
need
to
be
done
for
that
test?
B
For
that
to
happen,
and
so
I
think
that
the
collaborative
nature
of
trying
to
get
working
groups
working
with
each
other
instead
of
being
isolated
and
saying,
I
have
my
issues,
they
have
their
issues
and
even
though
I'm
aware
of
it,
I'm
not
really
doing
anything
to
contribute
or
help
or
support.
Even
though
most
of
the
tasks
that
we
have
within
zenhub
right
now
require
involvement
of
multiple
working
groups.
It
requires
in
the
the
approval
of
multiple
people
within
different
working
groups,
and
you
know
we.
B
We
assume
that
you're
just
going
to
take
care
of
that
on
your
own
and
a
lot
of
times.
I
think
a
lot
of
people
have
obstacles
in
terms
of
achieving
that,
and
so
I
think
the
sprint
planning
could
be
really
beneficial
to
getting
every
all
the
working
groups
and
all
the
individuals
within
those
working
groups
and
working
streams
to
coordinate
on
one
one
initiative.
E
I
mean
like
that's
the
that's
the
intention
right,
so
everyone
is
aware
of
the
interdependencies
between
the
working
groups.
That's
why
we
started
using
scrum,
but
it's
it's
I.
What
I
would
say
is
we
have
outgrown
it
with
the
size
that
we
are,
and
you
know
the
and
and
I
and
so
there
maybe
it
has
to
be
some
way
to
either
move
things
separately.
E
But
maybe
the
common
scrum
is
doesn't
have
every
single
working
group
in
it
necessarily
and
then
sort
of
pulling
in
eduardo's
recommendations
around
having
you
know
the
season.
You
know
maybe
it's
like
these
are,
and
maybe
our
seasons
are
quarters
and
we
look
at
every
quarter
for
what
the
goal
is
for
that
quarter
and
then
there's
working
groups
who
may
or
may
not
have
things
to
contribute
to
that.
But
then
the
commons
scrum
focuses
just
on
that
objective.
E
One
focuses
on
that
objective
for
that
quarter
and
that's
really
what
the
scrum
is
about,
so
so
it
achieves
like
the
focus
without
making
it
without
with
it,
with
respect
to
sort
of
scalability
limitations
of
coordination.
Efforts
for
this.
D
I
really
like
that
direction.
I
think
it's
what
I
like
about,
that
is
having
some
longer
time
frames
within
which
we
set
some
priorities
right,
like
bi-weekly,
I
think
it's
too
short
and
I
think
sometimes
it's
just
human
nature.
You
know
to
be
in
a
meeting
and
think
that
one
thing
is
important
in
a
given
moment
and
then
you
know
you
get
out
of
the
meeting
and
a
week
goes
by
and
you're
like.
D
D
B
Yeah,
so
I
I
guess
is
the
is
there
I
don't
know
can
may
know
this,
but
is?
Is
there
a
kind
of
a
method
for
that
like
where
we
have
this
kind
of
sprint
planning
on
a
larger
scale
in
the
seasons
and
then
having
these
small
touch
periods
in
between.
E
E
I
mean
so
for
the
sprint
planning
when
we're
it
depends
on
the
type
of
work.
That's
happening
right,
some
pieces
of
work,
some
types
of
work
like
research,
for
example,
you
go
month
or
two
months,
the
dynamics
around
what
you're
doing
don't
shift
and
change,
and
you
don't
have
to
react
coordination.
The
software
development.
E
The
idea
is
really,
you
can
show
pieces
to
the
client
right,
so
the
original,
the
origin
of
scrum's,
agile
development
and
the
idea
was
being
agile
like
being
able
to
show
the
clients
pieces
of
software
deliver
things,
and
then
you
know
under
then
do
this.
You
know
introspection
to
see
what
went
right
when
well
and
be
able
to
adapt
each
sprint.
E
So
it's
part
of
the
angel
agile
framework
and
for
what
we're
do.
What
we're
using
it
for
for
the
stewardship
and
for
work
streams
in
the
tec
is
really
just
coordination.
So
what
we
plan
for
this
sprint
is
might
change
next
week
when
there's
some
new
thing.
That
happened
some
new
piece
of
information.
We
have
that
now
we
need
to
adapt
what
we,
what
our
plan
was.
E
So
the
purpose
of
scrum
is
to
be,
you
know,
adaptable,
introspective
and
transparent.
Those
are
like
the
three
pillars
of
scrum,
so
I
think
what
what
piece
we
are
missing
is
like.
Well,
what
are
our
goals
for
the
quarter?
You
know
and
okrs
or
objectives
and
key
results.
Like
that's
one
method
we
can
use
to
say:
okay,
every
quarter
will
come
together
and
have
a
you
know,
agree
on
what
our
objectives
are
and
how
we
measure
them,
and
then
we
can
use
our
sprint
planning
to
support
that
those
goals.
E
A
I
agree
with
that
assessment.
I
feel
like
having
common
the
commons
focused
retrospective
and
spring
planning
will
be
way
more
helpful
and
then
leaving
the
micromanagement
of
each
individual
working
group
or
even
taser
are
not
relevant
necessarily
for
the
objective
of
the
commons
being
managed
by
their
own
working
groups
in
their
own
work
streams,
but
that
for
me
it.
A
It
should
come
also
with
this
very
clearly
out
of
method
for
working
groups
to
understand
how
they
can
take
advantage
of
this,
because
I
feel
this
methodology
really
worked
for
us
when
we
launched
the
token
and
all
that
process,
but
it
sort
of
we
dropped
a
little
bit
the
ball
with
that.
So
I
felt
it
became
more
of
a
cultural
routineary
thing
to
do
rather
than
an
effective,
necessarily
process.
A
So
so
yeah.
A
Does
anyone
have
any
other
comment
regarding
this
five
four,
three.
B
I
guess
I
have
to
ask
about
the
access
thing
again.
If
you
know,
if
we're
the
only
ones,
you
know
the
stewards
in
particular,
who
are
going
to
be
participating
in
this
actual
organizing
the
planning
stuff
and
we
kind
of
leave
the
contributors
outside
of
it.
B
E
Yeah,
I
think
that's
a
great
question.
Let
me
try
to
answer
this
actually
because
I
agree
with
you
and
the
purpose
of
using
github
and
using
zenhub
and
making
it
open.
So
anyone
can
open
an
issue
was
exactly
to
allow
people
to
open
issues
if
they
saw
work
that
they
needed
that
they
wanted
to
do
and
that
that
works
sometimes
but
mostly
doesn't.
Work
is
maybe
something
that
we
could
look
at
how
to
fix
that
particular
thing.
E
But
I
don't
think
this
model
is
closed.
I
don't
think
it's
closed
access.
I
think
this
model
remains
open
access.
It's
just
how
do
the
real
question
is?
How
do
we
get
contributors
to
you
know,
put
forth
their
ideas
in
the
sprint
board?
Maybe
they're
shy
to
open
an
issue
in
this
in
this
print
board?
Maybe
they
there
should
be
a
forum
where
we
can't
form
like
a
space
where
we
can
take
contributors,
ideas
and
help
them
put
them.
In
this
I
mean-
maybe
it
happens
in
a
working
group.
E
B
I
think
most
of
the
part
is
like
you
know,
knowledge.
You
know
most
people
come
in
and
they
want
to
participate
but
they're
afraid
to
put
it
on
the
board,
because
they're
not
extra
their
time
capacity
to
contribute
to
that
effort.
They
just
know
that
it
needs
to
be
done
and
so,
like
a
lot
of
issues
that
we
do
have
are
kind
of
aspirational.
B
Almost
not
really,
you
know
tangible
in
terms
of
that
two-week
spread
period,
and
so
a
lot
of
people
hesitate
on
even
putting
it
up
there
and
it's
like
you
know,
do
we
have
this
kind
of
sprint
board?
That's
just
filled
with
issues
that
are
kind
of
like
this
is
what
we'd
like
to
do,
rather
than
this
is
exactly
what
we're
going
to
be
doing
these
next
two
weeks.
B
I
think
that's
really
hard
to
to
to
have
people
participate
in
understanding,
because
we
do
it
from
an
individual
perspective,
but
not
from
a
working
group
perspective,
and
so
I
think,
if
you
had
like
two
or
three
people
who
were
like
yeah,
let's
do
this.
I
think
it
would
work
a
lot
he's
a
lot
better.
B
Knowing
that
you
have
support
to
execute
on
that,
that
particular
issue-
I
think
I
don't
know
I
I
just
I-
I
look
at
the
the
sprint
board
now
and
I
see
you
know
the
same
five
or
six
people
who
actively
participate
in
in
in
creating
issues
and
going
about
it,
and
it
doesn't
mean
that
work
is
not
being
done
in
the
background
by
other
contributors
for
other
issues,
they're
just
not
being
put
on
the
spread
board,
you
know,
and
so
how
do
we
convey
from
the
work
that's
being
done
in
the
working
groups,
especially
if
we're
moving
away
from
like
working
group
stewards
to
to
be
conveyed
into
the
overall
community
planning.
D
I
I
I
guess
I'm
so
if
I
understand
correctly,
what's
being
because
it
seems
like
there's
a
few
ideas
that
are
floating
around
here,
but
if
I'm
understanding
correctly
there's
one
idea
which
is
like
let's,
let's
keep
more
of
the
kind
of
coordination
within
working
groups
within
working
groups
and
focus
this
the
kind
of
the
commons
level
coordination
on
a
slightly
different
sprint
process
that
we're
still
defining
and
then
we're
talking
about,
possibly
also
then
having
some
kind
of
longer
term
set
of
goals
that
drive
that
process.
D
And
then
I
I
think,
I'm
I'm
also
detecting
something
nate
that
is
within
what
you're
saying
too,
which
is
I've
noticed
this
too,
like
zen
hub,
not
that
accessible
right,
like
most
people,
don't
really
know
how
to
do
that
when
they
come
in
the
first
time,
it's
pretty
overwhelming,
and
I
think,
rather
than
trying
to
train
the
community
on
how
to
use
zenhub,
that
we
that
there
may
be
some
simpler,
like
sense-making
things
right
like,
for
example,
you
know
polis,
we,
we
we
use
polis
with
with
some
interesting
effect
like
it,
actually
seemed
to
be
kind
of
a
good
listening
device,
and
maybe
there's
a
way
for
us
to
you
know
once
a
quarter
basically
put
out
some
type
of
pull
where
we
we
see
that
you
know
the
steward
seed.
D
The
pole
with
like
here
are
all
the
things
that
we,
we
think
are
interesting
and
important
right
now,
but,
as
you
know,
like
the
way
that
polis
works
you
can
get,
you
know
you
can
get
actual
people
weighing
in
on
the
stuff
that's
been
put
in
there,
but
then
they
can
add
stuff
to
it
right
and
it's
a
pretty
simple
user
interface,
and
my
guess
is
that
most
of
the
community
doesn't
really
want
to
get,
doesn't
really
want
to
get
that
sucked
into
the
nitty-gritty
of
the
decision-making
process.
D
They
would
probably
like
more
to
just
kind
of
weigh
in
on
the
high-level
like
directional
piece
and
be
able
to
give
their
advice
and
give
their
perspective.
That's.
F
I
wonder
if
it
would
be
interesting
for
us
to
invert
the
process
of
accountability,
somehow
that
people
don't
tell
in
advance
what
they're
going
to
do,
but
that
they
report
after
they
did
something
that
they
did
that
something,
and
then
we
would
have
some
type
of
documented,
like
database
of
everything
that
was
done
and
then
maybe
there
can
be
some
type
of
I
don't
know,
rewards
on
top
of
it
or
I
don't
know.
A
I
will
say
that
I
will
say
that
decent
hub,
as
we
were
talking,
the
cine
hub
and
github,
has
presented
sort
of
a
barrier
for
fox.
I
think
that
also
send
hub
at
the
state
that
it
is
currently
it's
a
lot
of
information.
A
A
lot
of
information
to
visualize
and
people
gets
lost
so
before
before
when
it
was
only
1798
on
this
call,
we
talked
about
like
simplifying
to
maybe
do
another
board
that
has
only
the
commons
focused
objective
system
or
having
a
notion
board,
because
the
advantage
of
notion
is
that
you
can
easily
make
it
open
or
you
know,
low
barrier.
I
don't
have
to
give
you
access
to
github,
then
teach
you
how
to
use
send
hub
so
something
that
could
be
something
else,
but
something
that
could
provide.
A
This
will
be
really
helpful,
but
I
do
feel-
and
I
strongly
feel
that
we
will
certain
level
of
not
commitment,
but
at
least
accountability,
format
or
process,
that
everyone
can
follow
and
understand
so
like.
While
we
mentioned
like
having
this
issue
after
you
finished
or
having
that
posted
before
it
doesn't
matter.
If
it's
for
me
it
doesn't,
I
don't
think
it
changes
much.
It
changes
small
much,
but
I
think
it's
helpful
to
make
sure
that
we
don't
lose
this
practice
of
keeping
track
of
things.
A
Just
quickly
on
that,
no
there
will
be
things,
for
example,
consensus
library,
or
that
will
take
more
time
as
time
mentioned.
There
are
things
that
research
that
will
take
way
more
time
or
maybe
less
time
than
the
commons
sort
of
focus
and
that
could
be
beneficial
for
the
ecosystem
or,
for
example,
twitter.
Something
that
you
know
happens
every
week
doesn't
necessarily
will
will
see
the
big
scheme
of
the
comments,
but
necessarily
will
be
it's
a
different
work
stream
like
if
you
have
to
research
design,
something
for
twitter
and
so
on.
A
These
are
working
that
still
happens
and
will
still
happen,
but
that
doesn't
mean
that
they
are.
They
have
the
same
kind
of
alignment
with
the
comments,
not
in
the
sense
of
they
have
a
value
alignment
they
have
all
of
this,
but
they
they
will
have
different
rhythm.
Let's
say.
C
A
C
F
B
I
feel
like
we
still
are
kind
of
in
different,
realms
and
thinking
in
terms
of
like
how
best
to
move
forward
with
sprint
planning.
But
I
don't
know
I
I
would
like.
B
I
would
like
to
have
something
in
the
works
for
this
sprint
regarding
this
topic,
but
I'm
not
exactly
sure
how
what
form
that
will
take
yeah
go
ahead.
Tim.
E
B
E
But
I
think
we
can.
We
can
say
that's
something
that
nate
and
I
should
take
on
and
rather
than
you
know,
ten
people
or
how
many
people
are
in
this
call
like
four
or
five
rather
than
seven
people
working
independently
trying
to
do
the
same
thing.
Maybe
we
can
sort
of
consolidate
all
of
it
and
make
that
something,
a
task
that
you
and
I
make
a
proposal
for.
E
I
think
kepler
should
be.
You
should.
B
I'm
done
with
that
and
yeah.
So
so
do
we
want
to
just
do
like
a
forum
post
once
we
have
the
steward
stuff
idea
of
what's
going
to
happen.
There.
E
B
A
Those
anyone
feels
anything
against
or
feedback
or
anything
they
want
to
comment
regarding
this
idea,
just
before
anything,
five,
four,
three
two:
I
wanna.
G
G
Good
results,
because
we've
gotten
to
this
point,
so
I
think,
like
the
cen
hub,
I
I
I
understand
the
complexity
of
like
having
multiple
pages
and
multiple
platforms,
but
I
I
still
believe
that
zenhub
could
help
us
progress
more,
and
I
think
that
the
coordination
it's
not
only
like
thinking
on
the
platform,
but
thinking
also
on
the
availability
and
the
the
presence
and
the
closeness
that
we
have
as
a
group,
and
I
think
that
not
only
thinking
about
the
platforms
but
thinking
also
about
the
closeness
in
the
group.
G
It's
something
that
would
be
very
interesting
because
sometimes
I
feel
that
we
have
been
growing
a
little
bit
distance
between
the
working
groups
and
it's
not
only
the
platforms.
G
And
if
we
see
that
that,
in
the
following
weeks,
we
are
going
to
have
less
participation
from
more
from
some
people,
we
should
prepare
for
that
and
do
what
we
can
before
and
yeah
try
to
try
to
give
a
step
up.
Even
if
we
have
to
make
an
extraordinary
meeting
just
to
gather
up
and
and
feel
close
together
up
steroids
get
together
or
something.
I
don't
know.
B
B
E
C
F
C
E
E
The
other
thing
is:
maybe
we
talk
about
our
working
groups
in
conversation,
discussion
format,
so
skip
the
board
planning
itself
or
we
do
the
board
planning
itself
or
we
just
have
a
conversation
around
our
working
groups
and
whether
we
have
any
needs
from
other
yeah
wonka.
I
feel
the
same.
Actually
most
of
my
issues
are
the
same
too.
So
maybe
I'll
pass
it
around
would
be
passed
to
libya
to
kick
us
off
of
those
of
the
best
use
of
this
time.
Now.
F
Yeah
and
for
me,
I
I
feel
like
my
work-
is
a
little
bit
on
that
realm.
That
gideon
was
talking
about.
That
is
hard
to
have
specific
issues,
for
it
seems
that
there's
something
a
little
more
long-term
evolving,
because
I
think
there's
this
cultural
shift
happening
and
it
feels
like.
I
have
to
do
to
understand
things.
First,
I
don't
know
and
then
there's
things
emerging
out
of
the
softcup
meetings
and
I
was
just
making
a
survey
now
thinking
about,
like
tc
stakeholders
signal
what
are
some
questions
that
we
could
ask
to
the
community.
A
Yeah,
I
wouldn't
do
this
compounding.
I
think
the
conversation
today
has
weighed
enough
into
how
this
needs
to
be
sort
of
redo.
So
I
will
just
follow
this
general
consent
on
anyone
who
has
a
priority
or
want
to
express
a
priority
for
this
next
week
to
express
it
and-
and
we
can
sort
of
build
based
on
that,
and
I
will
pass
it
on
to
getting.
D
Thanks,
I
do
yeah,
I
I
feel
like
you
know,
we
do
like
pretty
intensive
project
planning
in
sampo,
so
it
does
feel
like
kind
of
duplicated.
I
mean
it
feels
a
little
bit,
I'm
to
be
honest.
It
feels
a
little
bit
like
make
work
to
to
kind
of
like
surface
it
up
here
again
and
track
it
here
too.
But
having
said
that,
I
still
like.
D
I
think
that
there's
like
a
super
valuable
role
for
doing
inter-working
group
coordination
like
that's
that
doesn't
go
away
right
like
so,
so
I
I
think
I
would
say
like
for
this
call
like
yeah.
Let's
for
me
skip
the
the
detailed
sprint
planning,
but
I
think
it's
useful
to
kind
of
look
at
like,
for
instance,
if
you
were
to
ask
me
like
over
the
next
two
months.
What
do
you
see
coming
from
the
sample
work?
Where
you
know
I
could
really
use
some
help
from
other
working
groups.
I
can
tell
you
like
boom.
D
You
know
there
are
definitely
some
things
right,
and
I
bet
that
each
of
us
probably
have
some
similar
perspectives,
so
yeah
I'll
pass
it
to
zeptomus.
C
Yeah,
for
me,
I
mean
I
actually
think
like
we
should
skip
the
details.
I
strongly
feel
like
you
know.
We
mostly
have
some
issues
with
closing
issues
like
we,
you
know
people
most
people's
living,
so
yeah.
I
really
think
we
should
keep
like
I
I
on
this
call.
I
was
keep
thinking
like
how
we
you
know,
like
even
change
like
you
know
like
we
should
even
think
like
are
working
groups
serving
the
common
or
are
it
delaying
like?
C
There's
many
questions,
so
I
I
really
really
really
agree
with
libby
and
nate
were
talking
about,
like
you
know,
having
issues
voting
on
them,
so
the
token
holders
are
deciding
what's
to
get
done
and
then
using
our
resources,
which
is
the
people
to
get
those
issues
done
something
around
those
lives.
I
just
thinking,
but
I
don't
have
a
process
but
yeah.
I
think
we
could
keep
talking
about
future.
B
Yeah,
so
I
think
one
of
the
things
that's
especially
within
the
sample
working
group
and
throttle
through
and
policy
group
right
now,
I
think,
is
a
good
example
of
like
why
we
need
to
cross
working
group.
You
know
coordination,
and
you
know
we
have
a
lot
of
issues
where,
like
I
want
to
go
through
the
process
of
ratifying
this
policy
document,
I
want
to
go
through
the
process
of
putting
this
the
investment
strategy
up
to
a
vote,
and
this
is
some
something
that
soft
gov
could
definitely
help
help
with.
B
And
so
I
think
that
that's
a
really
interesting
issue
and
something
that
we
could
bring
to
the
front
because
it'd
be
like
you
know,
we
come
to
this
print
planning
and
say
hey.
I
want
this
is
what
I
need
right
now.
I
I
have
this
this
initiative
that
I'm
trying
to
accomplish,
but
I
do
need
help
with
other
working
groups.
I
do
need
help.
You
know
presenting
this
in
a
way
on
on
snapshot.
I
do
need
help
presenting
this
in
a
way
on
our
town
voting
and
what
is
the
process
for
that?
B
What
do
I
need
to
go
through
to
get
that
done
and
having
somebody
there
to
actually
pick
up
that
piece
and
execute
on
it
would
be
really
helpful,
and
so
I
think
that
that's
a
huge
aspect
right
now
for
for
what
we
need
in
the
the
treasury
policy
and
the
treasury
formation
stuff
after
we
go
through
this
week
of
advice
process
on
the
forum,
and
I
introduced
the
first
investment
strategy,
and
so
I
guess
figuring
out
a
way
to
use
the
sprint
planning
for
that
purpose.
For
that
cross.
B
You
know,
dependency
purpose
where
I'm
like
hey.
How
can
you
guys
help
me
out
with
this,
I
think,
would
go
a
long
way
to
being
more
efficient,
more
productive
as
a
community
in
helping
out
with
these
initiatives.
So
as
of
right
now
yeah.
I
think
that
I
would
like
to
add
that
as
a
kind
of
an
issue
and
see
where
we
can
all
pitch
in
but
yeah
I'll
pass
it
over
to
wonka.
G
Thanks
nate
well
in
gravity,
we
are
now
with
25
neogravitons,
and
some
of
the
things
that
I
am
seeing
is
that
okay,
we
now
have
a
lot
of
people
that
that
is
trained
and
some
of
them
willing
to
actually
mediate
cases.
But
right
now
I've
seen
a
decrease
on
the
number
of
cases.
G
So
normally
we
were
having
like
around
one
or
two
cases
per
month,
but
this
past
month
things
have
gone
slowly
too.
G
So
I
think
it
would
be
good
to
be
able
to
to
outreach
other
communities
to
receive
more
cases,
to
have
like
more
dynamic
on
this
motor
of
people
taking
cases
to
provide
the
service
that
we
want
to
provide,
and
I
also
think
that
something
that
I
think
that
could
be
worked
on
is
like
how
can
we
offer
tc
services
as
a
bundle,
but
also
the
individual
services
from
the
working
groups
to
tailor
the
needs
of
of
possible
clients?
G
Maybe
there's
a
client
that
would
like
all
of
the
dc
services,
maybe
there's
a
client
that
would
like,
like
only
sample
guidance
or
like
stewardship
guidance
or
onboarding,
and
of
boarding,
guidance
or
soft
guidance.
I
think
that
we
all
have
developed
products
that
it
would
be
really
cool
to
be
able
to
offer
and
to
to
to
have
defined,
as
as
as
each
group
an
individual
service,
but
also
the
tc
as
a
bundle.
I
think
yeah
that
that
conversation
once
started,
but
we
can't
retake
it
and.
G
I
think
that
we,
we
are
really
good
with
our
educational,
offering.
I
really
liked
the
third
graviton
training,
and
I
know
that
now
we
have
new
topics
to
add
to
the
to
another
graviton
training,
but
it's
always
like.
We
don't
only
want
to
be
an
educational
offering,
but
also
to
provide
a
service,
and
now
we
we
need
more
cases.
G
We
need
more
people
actively
engaging
with
with
the
type
firm
and
and
asking
for
support
in
in
in
conflicts,
I
mean
I
haven't,
received
an
input
in
the
type
form
for
like
two
weeks
and
it
I
think
it's
the
longest
time
that
I
haven't
received
an
input
in
the
type
form
for
a
long
time.
E
And
so
I
guess
I'm
the
last
one
to
go
so
about
the.
E
Coordination
layers
and
sprint
planning
and
what
we
do
about
it
I'd
say:
if
we
look
at
any
for
designing
any
system,
I
think
we
start
from
what
our
goals
are
and
what
our
requirements
are
and
then
from
the
requirements
we
could
sort
of
build
a
system.
E
I
think
scrum
was
a
choice
that
we
made
because
of
the
transparency,
introspection
and
adaptation,
it's
very
agile
and
it
provides
a
lot
of
the
values
that
tc
holds
here,
but
I
think
you
know
maybe
what
we've
been
missing
all
this
time
is
a
suggestion
box
to
make
it
easier
for
suggestions
about
what
we
can
do
in
in
our
sprint
planning.
E
I
think
community
participation
is
that
a
requirement
is
it
a
nice
to
have?
You
know,
like
the
you
know,
raising
partic
like
working
group
participation.
Is
that
a
requirement
like
what
what
are
all
of
our
requirements
and
then
we
can
actually
design
the
system
that
meets
those
requirements
rather
than
taking.
You
know,
designing
different
things
without
knowing
what
our
requirements
are.
First
and
then
you
know,
I'm
not
necessarily
tied
to
zenhub
or
even
github,
but
I
think
that
the
scrum
framework
has
indeed
been
very
advantageous
in
what
it
provides.
E
I
think,
if
just
out
of
this
conversation
and
all
the
different
perspectives,
the
two
things
that
would
enhance
it
would
be
quarterly
okrs
or
even
biannual
okrs.
So
what
are
our
goals
for
that
six
month
period
and
some
way
to
facilitate
communities,
suggestions
and
whether
that
makes
it
onto
the
sprint
board
or
not?
E
Who
knows
but
just
a
way
for
the
you
know,
I
guess
I'm
very
sensitive
to
this
idea
that
contributors
feel
that
they
don't
really
have
access
to
participate
in
this
in
contributing
work
to
a
work
stream,
and
if
it's
zen
hub,
that's
blocking
that.
Maybe
we
need
something
else.
You
know
yeah,
I
guess
the
like.
The
long
and
short
of
it
is.
I
think
it's
also
really
tied
to
the
stewardship
transformation,
and
you
know
having
common
stewards
and
working
group,
stewards
and
advisory
team.
I
think,
is
really
important
in
that
coordination.
E
Layer
too,
because
the
coordination
layers
not
just
like
what
tools
we
use,
but
the
cadence
for
our
meetings
and
what
each
of
these
groups
responsibilities
are,
and
that's
going
to
be.
That's
going
to
involve
the
kinds
of
meetings
of
coordination
meetings
that
they
would
attend
and
yeah.
I
think
I
look
forward
to
taking
a
crappiness
with
me.
B
E
B
Whether
we
should
go
one
by
one
through
each
of
these
issues
or
just
have
each
speech
steward
or
if
you
have
an
issue
open
right
now
on
this
call
like
go
through
them
and
see
if
it's
necessary,
if
not
close
them
and
we'll
clean
it
up
a
little
bit.
E
E
I
don't
think
that
if
we
spend
all
our
time
going
one
through
one
through
the
issues
and
closing
them,
it
would
feel
as
productive
to
us.
I
think
that
the
discussion
that
came
out
of
this
was
super
valuable
honestly
and
unless
there's
an
overwhelming,
I
mean
it
seemed
to
be
pretty
consensus.
E
I'd
say
we
just
pop
the
sprint
is
on
pause.
You
know
this
two-week
period.
I
think
everyone
knows
what
they're
doing
the
working
groups
are
doing
their
coordinations,
mostly
in
the
working
groups,
and
that
we
can
pick
this
up
and
then
we
can
pick
this
up
in
a
future
sprint
and
or
have
a
proposal
for
how
to
change
coordination
before
the
next
one,
which
seems
really
tight
to
do.
Actually.
E
Okay,
maybe
like
what
is
it
called
a
quick
fire?
What
are
you
looking
forward
to
most
this
weekend
before
we
hop
off
the
call,
unless
there's
anything
else,
anybody
wants
to
share.
G
So
I
think
that
there's
a
lot
of
value
that
we
can
continue
like
voicing
it
and
making
it
loud
so
that
the
things
that
we
did
for
ourselves
we
can,
we
can
support
others,
do
them,
because
sometimes
it's
difficult
to
continue
doing
in
the
same
community,
because
sometimes
what
we
did
was
done,
and
sometimes
each
thing
has
its
momentum
and
maybe
yeah.
That's
why?
G
I
think
that
some
of
the
working
groups
could
benefit
from
from
trying
to
to
see
how
can
they
apply
their
their
their
developed
string
of
work
in
in
other
in
other
community
thinking
that
yeah
that
maybe
it's
it's
something
that
we
can
iterate
on
and
like
a
continuous
thing
that
we
can
always
do
in
the
tc?
E
E
I
don't
exactly
share
that
perspective,
but
I
also
think
that
I
think
a
working
group
that
feels
that
they
have
something
to
share
with
other
douses
definitely
would
be
encouraged
to
develop.
That
kind
of
practice,
like
like
gravity,
did,
I
think,
gravity
set
a
good
example
of
that.
Actually.
E
Okay
nate:
will
you
share
what
you're
looking
forward
to
most
this
weekend.
B
Yeah
sure
I'm
going
to
hang
out
at
first
fridays
with
this
little
guy
tonight,
which
is
gonna,
be
great.
It's
like
an
art
festival
here
in
oakland.
It
happens
every
first
friday
and
yeah.
We're
just
gonna,
go
check
out
some
artwork
and
hang
out
until
he
passes
out
and
then
this
weekend
we're
just
gonna
hang
as
well.
So
good
he's
he's
grown
a
lot
and
it's
a
lot
of
fun
him
starting
to
move
around
more,
but
yeah
it'll
be
cool
and
I'll
pass
it
over
to
gideon.
D
Thanks
nate
so
cool
to
see
kepler
there.
I
just
love
that
age
man.
I
miss
it
also
just
an
appreciation
to
the
two
of
you.
I
I
am
so
glad
that
you're
digging
into
this,
like
I,
I
feel
like
there's.
C
D
A
bunch
of
stuff
that,
like
we're
changing-
and
I
love
the
fact
that
you
two
are
so
focused
on
trying
to
make
sure
that,
like
we're,
we're
coordinating
in
the
right
way
as
an
organization
right.
Thank
you.
I'm
looking
forward
to
a
walk
tonight
with
cj
my
wife.
We
we
we
do
this
pretty
regularly,
but
it's
just
like
perfect
weather
today
here
in
seattle.
So
I'm
really
looking
forward
to
that.
I
will
pass
to
zepty.
C
Thank
gideon,
I'm
also
going
on
a
vlog
actually
in
half
an
hour
I'll
go
with
sam,
a
place
that
is
called
la
punta
luc
yeah,
it's
a
pretty
lovely
place
here
in
the
village.
It's
like
you're,
getting
to
the
car
to
the
mountain,
and
it's
like
one
hour
one
hour
and
a
half
work
yeah.
It
is
great
and
yeah.
C
One
thing:
I'm
really
looking
forward
is
getting
the
audit
finished
this
weekend.
It's
needed
I'll,
pass
it
to
nate.
G
Thanks
nate
yeah
I've
been
taking
it
slow
this
week,
so
I
will
continue
taking
it
slow
this
weekend.
G
I
maybe
will
go
out
some
sometime
in
the
night
a
little
bit
but
like
stay
in
my
house,
chilling,
taking
benefit
and
and
the
best
of
these
slow
times,
because
after
the
calm
comes
the
storm-
and
I
know
that
at
some
point
we
will
be
full
of
work
as
we
will,
as
as
as
we
were,
and
full
of
coordination
and
life
as
we
were
and
yeah
just
hanging
out
with
with
danny
and
chilling,
maybe
playing
some
video
games.
F
E
Everyone's
walking
actually
so
I
think
this
weekend
I'll
find
a
nice
walk
to
take
too.
The
kids
have
a
lot
of
plans,
so
I
feel
like
we're
doing
a
lot
of
hanging
out
with
their
friends.