►
Description
Timecodes:
00:00 - Intentions and updates
02:20 - Zenhub Board
03:10 - Reward process description
19:12 - Praise rules
22:46 - Sourcecred Bots
40:03 - Backend
43:15 - Frontend
🙏 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
A
So
it's
a
good
good
time
to
do
a
a
stand
up
and
so
and
then
for
next
week,
will
be
more
of
a
review
and
a
planning
for
the
for
the
upcoming
two
weeks.
A
But
before
we
start
that,
I
can
just
give
you
a
short
status
up
update
for
the
the
the
project
and
as
when
it
comes
to
the
people
involved.
I
I
had
a
discussion
with
stryker
today
and
we
agreed
that
he
will
not
take
on
the
role
as
a
lead,
front-end
developer,
but
take
a
more
of
a
junior
role
supporting
the
developer.
A
So
that
means
that
we
are
one
person
short
so
taking
on
on
that
role
for
the
coming
week.
I
will
take
on
that
role
and
then
hopefully
we
can
get
pedro
or
someone
working
at
the
commons
config
dashboard
to
to
step
into
that,
so
that
that
is
a
general
plan
and
not
to
try
to
recruit
someone
completely
new
but
instead
hold
out
until
we
get
some
of
the
old
stars
to
jump
on
board.
A
Yeah,
I'm
super
happy.
Now
we
have
a.
We
have
a
functioning
back
end
and
functioning
front
end
and
the
authentication
layer
in
of
the
front
end
and
the
back
end
is
synchronized
and
they
speak
to
each
other
and
so
we're
beginning
to
establish
a
structure
for
the
praise
piece
of
the
reward
system.
That
works,
which
is
super
great,
to
have
that
in
place.
A
But
for
the
so,
let's
begin
the
the
stand-up
part-
and
I
think
we'll
who
who
would
the
questions
to
to
consider
is
what
what
have
you
been
doing
the
last
few
days.
What
are
you
planning
to
do
in
the
days
ahead
and
are
there
and
is
there
anything
blocking
your
progress,
and
I
will
share
my
screen
and
I
will
bring
up
the
sunhub
board
as
we
speak,
and
I
will
try
to
fill
in
any
like
missing
issues
that
are
identified
so
so
after
this
meeting,
the
the
board
is
somewhat
updated.
A
Who
who
would
like
to
go
first?
I
I
put
everyone
here
in
an
order,
but
it
doesn't
necessarily
have
to
be
that
order.
Did
someone
want
to
go
first.
B
Yeah,
I
can
take
it
first,
so
we
posted
up
the
rewards
process
description,
the
forum,
that's
up
we're
getting
advice
process,
and
the
next
step
for
me
is
to
just
clean
up
the
roadmap
and
then
publish
that
under
the
same
post
and
discuss
any
parts
of
that.
Maybe
that
need
to
be
modified
or
adjust
based
on
feedback.
B
A
B
I
mean
once
we
have
that
down.
Hopefully
I
can
be
of
use
making
copy
or
just
helping
on
the
front
end.
Somehow.
A
Selecting
the
rewards
committee
setting
the
the
initial
parameters,
but
I
guess
my
plan
was
to
re-read
the
process
description
before
the
meeting,
but
it
didn't
find
time,
but
maybe
it's
a
rewards
committee
that
said
that
proposes
the
initial
you
know
we
need
to
make
into
reality
all
the
stuff.
With
that
we
outline
in
the
process
the
rest
of
the
steps
sort
of.
B
D
A
D
D
What
we
already
have
changing
the
name
and
then
having
more
of
a
process
to
select
who's
going
to
be
there,
but
then,
since
you've
been
looking
into
the
source,
cred
parameters
for
so
long,
I
think
you
have
an
understanding
of
like
how
how
we
could
set
that
up
how
we
could
what
we
need.
What
types
of
expertise
we
need
in
that
group.
C
Perfect
yeah
do
I
have
access
to
the
mirror
board
christopher?
Can
you
send
to
me
please,
I
think
I
don't
have
access
to
it.
C
I'll
leave
you
sure
I
can.
I
can
take
it.
My
availability
this
month
is
going
to
be
a
kind
of
partial
by
the
end
of
the
month.
I
want
to
take
a
break,
but
I
can
still
attend
to
some
meetings,
so
I
already
let
christopher
know
about
it,
but
yeah
I'll
take
it
for
sure.
I
think
that
with
all
of
these
months
handling
source
credits,
just
where
that
I
take
it
for
sure.
A
So
setting
up
the
rewards
committee
would
be
not
like
we
that
we
vote
on
the
individuals
that
are
a
part
of
it,
but
more
that
we
have
a.
We
make
a
proposal
that
this
is
the
rewards
committee.
It's
it's.
It's
headed
by
mateo
and
these
are
the
other
people
involved.
So
we'll
just
make
a
a
forum
proposal
for
that
as
well
or
does
it
have
to
be
another
kind
of
vote?
The
forum
is
enough.
C
C
D
A
C
A
And
one
one
part
of
this,
this
work
stream,
I
I'd
say,
is
also.
A
A
dry
run,
a
place,
quantification
dry
run,
isn't
it
maybe
it
isn't.
If
we
have
it's
it's
so
similar
to
the
old
system,
so
maybe
we
don't
have
to
try
it
out
before
we
do
it
for
real
other
than.
Of
course,
we
do
like
technical
testing
of
the
the
actual
system
that
it
works,
etc.
D
A
Yeah
yeah
and
the
committee
that
there's
also
some
some
sort
of
parameters
for
praise
like
how
long
is
the
praise
period?
How
much
of
the
budget
do
we
allocate
towards
praise
so
and
the
rewards
committee?
Of
course
it
will
manage
all
those
parameters
as
well.
A
Nice
is
there
anything
else
we
need
to
do
before
the
the
praise
quant.
We
we
I
I
guess
we
need
to
get
the
the
praise
process
description,
also
to
have
some
sort
of
a
more
permanent
location
than
the
forum
shouldn't.
It
be
end
up
in
a
git
book
somewhere
also.
A
Yeah,
maybe
rules
for
yeah,
maybe
the
process
description
is
it's
fine
that
it
only
lives
on
the
forum,
because
it's
a
thing
that
is
valid
and
interesting
up
to
the
point
of
where
we
start
the
whole
thing.
And
then
it's.
B
Yeah,
I
think
just
because,
like
what
I
put
it
up,
I
don't
know
how
long
we
want
to
leave
it
for
advice
process
on
there
and
if
we
want
to
add
it
to
the
existing
git
book.
I
imagine
instead
of
making
a
new
one.
A
You
know
the
the
the
the
the
praise
process
description
that
when
we
describe
how,
how
does
the
the
tec
reward
system
work?
I
I
that
description
would
it
would
be
nice
to
have
that
description
easily
findable
in
the
future,
with
the
something
similar
to
the
to
the
the
graphic
similar
to
this
graphic
and
describe
like
this
is
how
the
the
reward
system
works.
So
it's
basically
the
the
forum
post
without
the
the
roadmap
up
to
the
first
quant.
B
B
A
D
From
octopus,
I
sent
him
some
questions
mostly
about
how
I
remember
him
talking
once
that
links
were
very
bad
for
the
like.
They
made
the
data
dirty
and-
and
there
was
something
about
emojis
too,
but
then
I
don't
know
if
we
can
work
on
a
way
to
include
emojis
because
it
feels
like
they
are
a
big
part
of
the
language.
Also.
C
D
Just
waiting
to
see
if
emojis
are
really
bad
or
not,
and
if
we
can
continue
with
them
and
then,
if
we
can't,
maybe
we
could
do
something
like
aloisios
was
mentioning
of
like
having
the
reactions
with
the
emojis,
and
that
could
be
a
fun
part.
A
No,
I
I
was
thinking
if
we
we
haven't,
decided
how
we
we
should
handle
duplicate,
duplicate,
praise,
a
praise
for
the
same
contribution,
how
the
algorithm
will
value
that
and
one
option
would
be
to
allow
for
emojis
or
to
represent
the
similar.
The
the
same
thing
like
two
praise
referring
to
the
same
contribution
would
be
the
same
thing
as
one
praise
with
two
emojis.
D
The
solution
rich
and
I
found
for
this
was
to
make
in
the
quantification
one
per
like
all
of
the
contributions
of
one
person
are
one
next
to
each
other.
So
the
person
who
is
quantifying
can
have
an
idea
of
what
is
the
total
amount
of
their
contributions,
because
the
problem
with
deleting
or
just
like
counting
one
of
the
praises
is
that
I
think
there
are
some
signals
and
in
there
that
we
couldn't
ignore.
For
example,
what
if,
like
10
people,
praised
someone
for
the
same
thing.
C
A
D
Have
higher
reach-
or
something
like
that,
so
I
think
if
they
are
all
close
to
each
other
and
there
are
little
differences
in
how
each
person
thinks
something
was
important
to
praise
someone.
Then
the
quantifier
will
see
all
that
in
perspective.
C
C
Also
think
that
I
don't
I'm
not
sure
how
many
people
will
read
the
praise
when
they're
not
involved.
So
I
just
adding
an
an
extra
reaction.
Maybe
not
may
not
be
realistic,
because
people
just
want
to
prefer
to
write
their
praise
out
and
continue
instead
of
scroll
up
and
search
for
the
praise
that
somebody
got
and
then
add
their
reaction
to
that.
A
Absolutely
so,
but
the
now,
let's
see
it
felt
like
we
moved
on
from
from
mitch
to
libya
a
little
bit.
So
you
said
that
you
were
planning
to
write
a
forum
post
about
the
the
rules
for
praise.
D
Yeah
I'm
on
on
the
way.
I
think
I
can
finish
soon
in
between
calls
and
it's
mostly
I'm
following
a
little
bit
what
you
posted
in
the
issue,
because
you
asked
a
lot
of
good
questions.
So
I'm
trying
to
answer
all
of
them,
so
yeah
differentiating
subjective
from
objective
contributions
and
giving
a
little
bit
more
of
context
because
I
feel
like
it
gets
kind
of
too
abstract.
Sometimes
when
we
say
subjective
so.
C
D
To
put
some
examples
and
examples
of
objective
contributions
to
and
then
the
objective
contributions
part
is
what
we're
gonna
work
with
the
committee
to
pick
the
source
credit
parameters.
So
the
more
we
have
this
differentiation
and
we
see
how
far
risk
grad
can
grab
contributions.
C
D
Then
how
does
the
quantification
work
work?
We
already
worked
on
that
with
I'm
in
the
forum
post
that
meech
posted
so
I'll
just
put
some
of
that
information
here
in
the
praise
categories.
D
D
D
C
A
Cool
thanks,
I'm
constantly
constantly
getting
lost
in
this
sun
hub
board
world
try
to
find
all
the
issues.
While
we
talk
who
would
like
to
go
next,
we
have
yyv
for
the
bots
and
we
have.
I
can
speak
about
the
front
end
and
if
nagan
has
anything
to
say
about
the
back
end,
please
do
that.
Otherwise
I
can
say
something
that
I've
heard
from
from
rudolph.
E
D
E
Tried
out
the
meeting
what
the
bridger
bought
virtually
so
it's
it's
a
good
solution
that
we
could
use
with
a
little
bit
of
changes.
E
E
It
gives
you
the
people
that
attended
the
meeting,
however,
like
it
returns
an
embed
instead
of
a
text
instead
of
a
text
message.
So
the
issue
with
that
is,
I
don't
know
if
source
grid
handles
embeds
because,
like
embed
is
a
insert,
is
a
different
object
in
itself.
E
We
make
our
own
bot
means.
That's
like
a
fork
of
the
reserve
button
with
slight
changes,
and
it
goes
through
a
channel
called
gift
props,
or
something
like
that.
That's
that
has
source
credit
set
up
in
a
way
where,
like
people
mentioned
in
the
messages,
get
the
cred.
E
Yeah
yeah,
so
yeah,
that's
for
automatic
meeting
tracking.
I
don't
know
if
sesh
would
be
a
good
option
because,
like
we
are
making
about
to
pass
things
out
of
it
might
as
well
just
make
our
own
bot
to
track
the
same
and
for
the
twitter
I
looked
into
twitter
and
you
know
I
don't
exactly
know
what
we
are
specifically
looking
for.
E
E
I
think
we
can
track
that
and
have
that
sent
to
discord
in
the
source
grid
channel
and
people
can
react
to
it
to
give
it
great,
but
like
I'm
not
sure
if
this
would
be
a
good
solution,
because
then
it
will
expand
the
entire
subscription,
so
people
won't
even
be
able
to
see
it.
So
I
don't
know
if
we
can
allocate
credit
that
way,
but,
like
an
interesting
thing,
we
could
look
into.
Is
this
thing
called
orbit?
E
Like
it's,
it's
it's
like
a
plat.
It's
like
a
the.
E
Tracking
software,
it's
for
many
platforms.
We
could
just
use
the
twitter
plugin
and
you
could
just
like
have
who
interacted
the
most
with
our
twitter
this
this
month
or
this
week,
and
we
could
have
that
data
pulled
into
source
credit.
I'm
not
exactly
sure
how
we
link
source
grid
with
that,
but
that
can
also
be
like
an
interesting
metric.
Instead
of
you
know
like
manually
tracking
it
and
then
having
people
allocate
credit
to
it.
A
Yeah
and
then
going
forward
here,
we
we
need
to
make
some.
We
need
to
decide
on
on
which
route
to
take,
and
I
guess
by
by
the
you-
are
the
best
best
informed
when
it
comes
to
the
the
bots
to
to
to
choose
which
way
to
go.
Basically.
E
So
for
the
calls,
I
think
our
best
way
would
be
like
before
I'll
the
reservoir,
and
we
have
it
set
up
so
that
it
can
work
with
the
source
grid
in
our
discord
and
for
for
the
twitter,
I'm
really
unsure,
because
it's
it's
slightly
vague.
We
don't
have
any,
like
definition,
for
how
we
allocate
credit
to
things
on
twitter
like
what
has
value
is
it
relate
to
it?
Is
it
people's
getting
likes?
Is
it
them.
E
With
us,
what's
what
exactly
is
the
dynamic
between
you
know
what
we
count
as
adding
value
and
what
we
don't
count
as
adding
value.
C
Yeah,
I
think
that
twitter
has
the
same
problem
as
discord
that
it
can
be
easily
gained
by
anyone.
So
I
I
don't
know
if
we
have
value
adding
it
to
source
credit,
maybe
we
can
make
it
something
separate
and
consider
limiting
what
an
interaction
is
maybe
per
day
or
something
whatever
you
did
with
our
accounts
or
hashtags
in
a
day
counts
as
one
fixed
interaction,
because,
let's
say
if
one
person
creates
an
account
and
gives
likes
to
all
of
the
tweets
retweet
them.
C
I
don't
know
whatever
happens,
that
can
be
easily
game,
and
maybe
I
would
say
that
if
you
do
one
interaction
in
a
day
that
counts
as
a
fixed
interaction
and
that's
it
so
whatever
people
does
even
if
they
do
like
some
attack
or
whatever
it's
not
attack,
because
it
even
is
convenient
to
us
that
people
are
using
a
lot
of
interaction.
A
lot
we
don't
give
more
than
a
fixed
number
on
on
a
reward,
and
that
can
be
completely
separate
of
a
source
thread.
I
don't
know
if
you
agree
with
that
guys.
E
E
Yeah,
so
I
had
a
question
is
like:
do
we
need
the
twitter
part
to
be
in
source
grid,
or
could
we
maybe
just
roll
this
into
sausage
into
place
and
like
have
a
fixed
price
that
we
could
give
for
it?
Maybe
something
like
that.
A
No,
I
think
we
have
to
make
the
distinction
that
that
phrase
that
does
not
we
don't
want
to
import
the
the
the
kind
of
auto
quantify
that
the
data
that
we
can
ought
to
quantify
that
don't
bring
that
into
praise,
because
then
the
phrase
becomes
something
else.
E
What
if
we
like,
do
something
like
we
bucket
types
of
interactions,
so
we
have
like
a
few
pockets
for
likes
of
your
pockets,
for
we
have
one
bucket
for
two
likes.
We
have
a
one
bucket
for
retweeting
and
we
have
one
pocket
for
interacting
with
us
and
one
bucket
for
mentioning
us
and
like
if,
if
you
fill
anything
in
that
one
bucket,
it
counts
as
some
fixed
number
of
grid
yeah.
C
E
C
E
E
And
I
think
we
should
probably
make
our
own,
but
I
don't
know
if
there's
a
part
out
there
that
tracks
specific
metrics
there
could
be.
But
if
you,
if
you
want
just
one
like
like
in
interaction
relative
interaction
number,
then
we
could
use
some
service
like
orbit
that
just
tracks
everything
happening
on
your
twitter
and
like
allocate
some
percentage
of
like
interaction
points
that
each
person
had.
Actually
let
me
just
share
my
screen
and
show
you
what
orbit
shows.
C
C
A
This
way,
and
thus
does
orbit,
has
an
api
yeah
yeah.
It
has
an
api.
So
basically,
if
we
use
orbit,
we
can
write
a
quite
a
simple
bot
that
just
fetches
these
activity,
numbers
and
and
somehow
re
reposts
them
into
a
discord
in
in
a
in
a
way
that
source
crit
can
use.
E
E
E
Instead
of
like
posting
this
to
discord
and
then
having
people
react
to
it,.
A
Yeah,
no,
that
that
seemed
like
the
the
of
course,
the
most
straightforward
thing
that,
because
if
we
have
that
smart
system
already
doing
sort
of
the
analysis
for
us
and
doing
the
weighing
of
different
kind
of
interactions
etc-
and
we
get
just
one
number
so
just
take
that
number
and
move
it
into
source
credit
each
month.
That
sounds
like
a
smooth
way
forward:
yeah
if
it's
easy
to
build
a
a
a
a
plug-in
for
a
source
grid,
but
that
could
be
fun
to
investigate.
C
B
E
B
E
Yeah,
I
think
we
can
fetch
data
by
weekly.
Let
me
see
if
that's
something
we
could
do
just
pretty
much
tracks
anything
happening
with
your
twitter
account,
so,
instead
of
having
our
bot
keeping
track
of
everything
on
twitter
might
as
well.
Let
them
have
to
do
this
because
I
don't
know
if
what
would
be
the
like
kind
of
hosting,
we
need
to
keep
track
of
everything
on
twitter.
A
If
we
do
it
on
a
recurring
basis,
then
then,
and
we
have
an
automatic
bot
and
it's
not,
then
then
it
might
be
as
well
that
it
feeds
the
source
credit
every
day,
because
then
we
don't
run
the
risk
of
you
know,
depending
on
how
we
set
the
price
or
the
the
how
we
set
the
periods
we
we
could
miss
if
we
do
it
just
month
by
month.
If
we
set
the
date
wrong,
then
we
will
miss
what
one
completes
months
of
data.
If
we
just
move
the
price
period
date
back
and
forth.
A
A
Can
I
put
that
as
an
issue
on
your
assigned
to
you,
then,
to
take
that
further
and
see
if
it's
doable.
E
All
right
all
right,
but
I
think
we
should
maybe
de-prioritize
with
at
the
moment
I'm
thinking
of
focusing
first
on
the
call
system.
E
So
so
first,
we
can
maybe
get
that
done
and
after
that,
whenever
I
have
time
we
could
work
on
it
and
if
anyone
else
wants
to
work
on
it
with
me,
they
are
sure-
and
I
think
we
need
someone
who
has
access
to
our
twitter
account
so
that
we
can
give
access
to
orbit
so
that
it
can
like
analyze
that
data.
A
Yep
no,
but
but
then
we
will
set
that
as
a
in
the
in
the
product
backlog
and
and
this
meeting
tracker
bought
in
in
the
yeah
in
progress
or
in
the
sprint
practice.
For
now.
C
A
C
No,
I
haven't
talked
to
him.
I've
been
I've
been
busy
with
the
with
the
dashboard
stuff
that
I
think
you're,
probably
more
up
to
date.
I'm
still
on
the
point
of
getting
it
to
run.
I've
been
playing
around
a
bit
at
this
week
with
some
easy
bots
for
the
for
the
telegram
and
discord
phrase
thing,
and
I
wanted
to
get
things
running
and
start
with
the
unit
tests,
because
I
think
there
may
be
a
bit
more
priority,
but
I
haven't
talked
to
rudolph
since
our
meeting.
So
maybe
you
are
more
up
to
date.
There.
A
Yeah
and
let
me
see
what.
A
C
A
My
my
intention
at
least,
was
to
assign
an
issue
to
you
that
said
unit
tests
for
the
authentication
layer,
because.
A
The
first
main
piece
and
the
so
the
main,
the
first
piece
of
the
back
end
is
the
authentication
layer.
The
next
piece
will
be
the
praise
periods.
A
So,
and
I
can
say
a
few
words
about
the
status
of
the
the
back
end
yeah,
like
I
mentioned
in
the
beginning,
rudolph
has
yeah
the
authentication.
I
I
don't
know
if
it's
completely
done.
It
needs
this
unit
testing
and
a
little
bit
more
refactoring,
but
it's
almost
done
and
it's
one
of
the,
I
would
say
one
of
the
most
technically
advanced
components
of
this
whole
thing.
The
rest
of
the
system
is
mostly
filling
forms
and
filling
the
database
with
information.
A
And
so
that's
great
what
else
has
been
happening
in
the
backend
world?
Yeah
rudolph
not
notified
me
about
other
kinds
of
stuff
like
attack
vectors
that
we
need
to
think
about.
So
so
let's
identify
some
some
issues
there,
like
denial
of
service
attacks
and
and
now
we're
building
the
the
praise
system
so
that
every
time
a
new
address
logs
in
a
user
account
is
created
and,
of
course,
one
easy
way
to
crash.
A
The
system
would
be
to
just
register
lots
of
new
user
accounts,
so
we'll
do
some
some
sort
of
rate
limiting
there.
What
else
has
he
been
up
to.
E
I
had
a
question:
what
kind
of
auth
are
we
using
on
our
website
on
the
web
portal
for
logging?
In
so
sorry?
What
kind
of
what
kind
of
auth
are
we
using
for
logging
in
if
it's
like
json
web
tokens,
we
could
probably
like
set
some
parameters
for
like
outdating
them,
or
something
like
that,
so
we
have
like
create
limiting
built-in
if
we
like
use
those.
A
A
So
those
tokens
have
an
expiry
date
and
etc.
I
don't
know
how
they
can
be
used
to
to
counter
like
dns
attacks,
etc.
E
A
Yeah,
I
think
that
that
was
that's
his
plan
to
sort
of
do
some,
that
kind
of
limiting
somehow
and
then
for
the
front.
End
yeah
good,
good
news
that
rudolph
just
before
this
meeting
got
managed
to
connect
the
connect
the
front
end
with
a
back
end,
basically
because
there's
a
fair
amount
of
authentication
and
magic
that
needs
to
happen
for
this
metamask
login
to
work
smoothly
as
well.
So
for
the
front
end.
A
That
is
also
one
of
the
most
technical
pieces
of
the
whole
thing
is
to
you
know,
log
in
using
metamask
and
that
that
flow
should
be
like
really
intuitive
and
and
work
really
well,
so
you
get
redirected
to
the
right
page
after
you
have
logged
in
and
you're
saving
that
token
for
the
login
token
for
for
later,
so
you
don't
have
to
log
in
again
just
because
you
close
the
tab
and
and
go
back
that
kind
of
usability
stuff.
A
A
Steps
for
for
the
front-end
development
is
to
to
start
with
the
first
page
or
the
the
dashboard
skeleton
and
some
of
the
graphical
building
blocks
that
we
can
reuse
for
for
the
rest
of
the
rest
of
the
process,
as
well
as
beginning
working
on
the
the
quantification
periods
and
that
those
two
or
three
screens,
where
you
can
view
the
the
upcoming
phrase
periods
or
or,
and
you
can
as
an
administrator,
you
can
create
new
periods,
give
those
periods
a
name
and
then
end
the
date
and
also
assign
quantifiers
to
those
periods,
which
means
that
we
also
in
in
hand
in
hand
with
this.
A
We
will
need
to
to
add
the
functionality
for
the
quantifier
pool,
because
you're
to
be
able
to
assign
quantifiers.
There
needs
to
be
a
quantify
pool,
and
for
that
there
is
a
small
algorithm
that
we
need.
We
need
to
figure
out
like
a
minimum
minimum
quantifier
pool
amount
of
people.
A
Let's
say
if
we
want
each
price
to
be
quantified
by
three
people
and
we
have
x
x,
amount
x,
number
of
praise
and
we
don't
want,
and
we
want
each
quantifier
not
to
have
more
praise
or
quantify
praise
for
more
than
10
people.
A
Then
we
can
make
a
calculation
saying
yeah.
If
we
have
100
praise
divided
over
10
people,
then
we
need
this
amount
of
people
in
the
quantify
pool
to
be
able
to
assign
each
one.
A
An
amount
of
tasks
that
is
good
so
then
the
question
would
be.
If
we
have
too
few,
if
too
few
quantifiers
in
the
pool,
then
it
would
warn
and
say,
like
yeah,
the
the
tool
of
quantifier
is
too
small:
either
recruit
more
people
and
or
or
or
ignore
this
warning
and
and
assign.
You
know
a
thousand
praise
to
these
two
poor
bastards
that
are
in
in
the
pool,
but
you
yeah,
we
at
least
inform
you
that
it's
you're
breaking
the
algorithm.
A
So
that
I
would
say
is,
is
the
plan
for
for
the
coming
week
when,
when
it
comes
to
the
front-end
break,
hopefully
we
will
have
that
functionality
done
by
end
of
next
week.
Let's
see.
E
I
had
a
question:
how
do
we
encourage
people
to
become
quantifiers?
Do
they
give
them
extra
praise
or
extra
skill
points,
or
something
like
that.
E
Sorry,
how
do
we,
how
do
we
like
expand
the
quantifier
pool
like
do
we
incentivize
them
in
some
way,
like,
for
example,
like
on
a
celeste,
you
have
the
you
have
honeys
taking,
so
you
get
some
amount
of
money
back
so
like?
Is
there
some
incentive
link
to
it,
or
do
we
like
give
them
more?
Please,
or
something
like
that?.
A
No,
they
they
get
to
a
part
of
the
a
piece
of
the
cut
of
the
the
the
total
payments.
So
so,
when
the
when
the
tokens
are
distributed
and
allocations
are
being
calculated,
the
most
the
biggest
chunk
goes
to
the
contributors.
Of
course,
a
little
piece
goes
to
the
the
quantifiers
and
and
the
the
smallest
piece
goes
to
the
reward
system.
Committee
and
and
those
percentages
would
be
voted
on
by
the
community
and
initially
set
by
the
rewards
system
committee
and
then
can
be
voted
on
by
the
community.
E
Okay,
something
related
to
that,
that's
can
be
an
attack
right
vector
is
like
would
having
a
chunk
of.
The
final
rewards,
make
the
quantifiers,
if
they're
bad
actors
until
they
go
into
the
system
and
increase
the
try
to
increase
the
amount
of
tokens
that
we
are
going
to
mint
or
like
the
amount
of
hours
that
are
allocated
to
people
or
is
that
fixed,
like
you,
have
these
many
hours
to
use
this.
B
A
And
also
the
tac
funding
pool
is
controlled
by
a
separate
entity,
which
is,
I
don't
remember
the.
E
A
The
rewards
dao
requests
funds
from
the
tec
funding
pool
by
the
the
reward
system
committee
request
funds
for
the
rewards
dao,
but
the
the
the
payment
of
that
fund.
The
payment
of
those
fund
is,
is
approved
by
the
tc
yeah.
E
Okay,
didn't
understand
that
fully
because,
like
how
are
we
going
to
frame
the
quantification
process
because
earlier
what
used
to
be
happened
was
like?
I
think
you
just
decided,
like
the
three
quantifiers
decided
on
for
how
many
hours
we're
gonna
mint
this
period
and
then
the
distribution
got
created.
E
B
D
D
Well,
like
every
two
weeks,
maybe
override
every
period
of
like
a
month
or
another,
and
I
think
the
reward
committee
should
should
propose
different
numbers
for
that.
Maybe.
C
I
I
just
wanted
to
say,
like
I
really
like
how
it
was
in
the
past,
like
the
quantifiers
were
saying:
okay,
the
value
created
this
period.
This
was
like
800
hours
and
then
we
distribute
regarding
of
that
and
yeah.
We
just
like
like
yeah,
we
need
like.
If
the
committee
is
there,
they
they
need
to
be
useful,
and
I
think
it's
useful
for
these
subjective
things
like
maybe
this.
You
know,
maybe
it's
christmas
and
no
one's
working
and
the
reward
shouldn't.
You
know,
then
little
contributions
could
get
a
lot
of
reward.
C
E
Spotify,
like
make
the
number
like
the
total
amount
of
hours
that
would
be
distributed,
a
function
of
like
the
number
of
people
engaged
in
that
in
that
period
of
praise,
and
then
we
like
add
some
small,
really
small
amount
on
top
of
that,
that's
decided
on
by
the
quantifiers
or
the
rewards.
So
like
that's
subjective,
but
like
we
have
a
base
for
what's
being
minted,
proportional
to
the
number
of
like
members
in
that
pool.
That's
where
we
can
like
scale
up.
If
we
get,
we
get
like
a
lot
of
members.
B
A
And-
and
it's
really
worth
pointing
out
that
the
these
parameters
are,
of
course
modifiable
over
time,
and
so
so
what
what
we
are
proposing
now
for
before,
before
the
first
quant.
Of
course,
we
will
have
a
a
set
up
for
for
the
that
first
round
and
then
for
for
each
round
the
community
can
get
involved
and
override
or
signal
their
their
intentions
and
that
their
how
they
would
like
to
see
it
being
done
and
the
hopes
are
by
doing
qualifications
on
on
a
steady,
bi-weekly
basis,
with
more
focus
on
transparency.
A
Is
that
to
have
a
continuous,
the
discussion
about
all
the
parameters
and
and
the
distributions
and
the
budgets
etc.
So
we
we
get
more
more
buy-in
or
everyone
respects
the
distribution
more
and-
and
we
have
increased
transparency.
D
I
think
it's
a
really
good
idea,
though,
to
have
what
viva
v
suggested
some
type
of
formula
that
we
always
understand
how
many
people
are
in
and
more
or
less
how
much
they
would
receive
even
for
impact
hours.
We
had
it
wasn't
like
the
the
quant
the
amount
for
each
praise,
but
for
each
impact
hour
that
we
didn't
want
each
impact
hour
to
be
valuable.
Less
than
10
die,
for
example,
and
I
think
we
should
keep
some
type
of
layer
in
there.
E
Yeah,
that
sounds
great,
maybe
like
moving
forward
after
we've
like
made
the
initial
version,
then
we
can
have
these
conversations
and
you
know
like
decide
on
the
formula.
According
to
the
data
like
what
would
work
best.
A
Oh,
but
we
couldn't
you
post
post
a
comment
to
the
reward
system,
the
process
description
on
on
the
forum.
So
we
don't
don't
forget-
and
I
also
agree
and
and
like
have
having
a
fixed
budget
every
every
period
where
the
the
amount
of
contributions
may
vary
widely.
That
makes
a
quite
an
uncertain,
uncertain
situation,
so
so
it
feels
sort
of
logical
or
reasonable
that
if
we
for
a
period
we
have
a
really
small
amount
of
contributions,
then
the
the
amount
that
we
also
distribute
is
less
and
and
vice
versa.
A
So
we
are
at
the
top
of
the
hour.
I
need
to
go
downstairs
and
cook
dinner
for
my
family.
Thank
you
all
for
for
coming.