►
Description
Timecodes:
00:00 - Agenda
00:32 - Reward Board
01:51 - Praise backend
08:38 - Sourcecred bot
10:37 - Praise data
17:50 - Paused/finished Reward system process and rules of praise
🙏 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
That
format
is
so
so
focusing
on
what
you
have
been
doing
for
the
last
few
days
and
and
what
you
will
be
focusing
on
the
days
ahead
and
if
there's
anything
blocking
your
progress,
and
I
know
to
start
with
that.
If
we
we
get
started
that
the
first
item,
the
rewards
committee
mateo,
is
on
vacation,
so
he
won't
be
able
to
report
anything
there.
A
I
know
that
he
has
asked
started
by
asking
a
few
people
to
join
the
committee
and
that's
it,
but
I
think
maybe
it's
a
good
idea
to
support
matteo
and
libby.
I
think
you
and
me
should
talk
about
maybe
supporting
him
while
he's
gone
and
all
making
sure
that
things
move
forward
there.
B
A
Yeah
but
let's,
let's
have
a
separate
discussion
about
needs
to
be
done
about
that.
B
B
A
And
then
praise
back
end
and
nagan.
Would
you
like
to
and
talk
a
bit
about
what
you
have
been
doing.
C
Yeah
sure
it's
been
a
bit,
I
don't
have
that
much
to
say
because
well
we
had
this
these
issues
with
with
the
dashboard.
We
took
a
lot
of
time
and
then
I've
been
struggling
with
the
java,
basically
with
the
java
discord
apis
up
to
the
point
that
that
I
just
my
last
point
was
to
say
it
edited
in
python.
I
have
the
best
basic
bot
in
python,
and
now
I
don't
know,
maybe
just
try
to
translate
it
or
or
see.
C
Maybe
I
should
talk
to
rudolph
and
if
we
can
have
two
little
python
bots
running
in
the
server
to
feed
the
data
to
the
to
the
database,
maybe
that's
easier,
because
I
think
that
could
help
us
to
also
use
the
already
existing
bots
and
just
modify
them.
So
they
they
sent
us
store
the
data
somewhere
else
I
don't
know
but
but
yeah.
So
that's
been.
It's
basically.
A
It
would
be
nice,
I
think,
to
to
upgrade
the
bots
to
to
use
this
the
slash
command
discord.
Wouldn't
it.
A
So
some
some
some
work
needs
to
be
done.
I
I
know,
and
when
it
comes
to
hosting
the
the
python
bots,
what
what
is
needed
to
to
host
those
bots
do
they
could
they
live
on
the
same
server
as
the
the
back
end
in
general,
I.
C
Think,
yes,
they
don't
need
any
kind
of
special
resources,
just
an
endpoint
from
which
they
communicate.
So,
yes,
like
the
the
way
that
that
the
project
is
back
in
the
structure
right
now
with
what
google
did
is,
they
are
separate.
So
if
there
is
his
backend
and
then
this
telegram,
client
and
java
client,
which
has
its
own
build
file
and
everything
separated.
A
Yeah,
so
so
by
all
means
check
check
with
him
that
and-
and
I
agree
we
can-
if
we
can
save
a
lot
of
time
by
by
using
the
the
existing
bots
that
then,
of
course,
that
is
something
we
could
consider
unless
we,
the
the
the
the
bottom,
the
work
of
rewriting
them
is
quite
small,
and
we
know
that
we,
you
know,
there's
an
another
advantage
of
making
the
the
new
bots
more
integrated,
with
the
the
new
back
end.
Of
course,
so
it
could
save
us
more
time
later
on.
A
But
but
could
you
make
an
assessment
together
with
him
if
it's
which
way
a
route
to
choose,
if
we
can
keep
the
old
bots
and
modify
for
the
new
backend
or
if
we
make
new
bots.
A
Cool
and
rudolph
is
not
here
because
he
is,
he
is
at
his
day
job.
But
what
can
I
say
for
him
about
the
back
end
in
general?
That
is
that
the
the
data
model
is
set,
I
think,
and
he
has
begun
implementing
it.
So
he
has
implemented
like
a
few
of
the
endpoints
these
last
few
days,
for
instance
the
listing
stuff
concerning
praise
periods
and
also
some
some
more
work
on
the
authentication
layer
and
like
user,
the
the
user
stuff
like
listing
users,
etc.
A
So
that's
that's
really,
nice
that
that
the
things
are
happening
there
and
I
expect
the
the
the
rest
of
the
endpoints
that
he
will
develop
them
quite
quickly
now
that
we
have
set
the
data
model
etc,
and
he
does
not
express
any
blockers.
I
think
the
the
blockers
he
has
expressed
is
the
it
has
been
about
the
the
data
model
like
the
the
need
to
we
need
to
set
the
data
model
before
I
build
a
develop
the
the
endpoints.
A
Otherwise,
I
have
to
rewrite
everything
when
we
decide
on
the
data
model,
and
now
I
think
we
have
set
that
so
moving
on
to
a
front
end.
A
So
what
I
know
about
his
work,
that
is,
that
he
has
in
he
has
a
time
he
has
time
that
he
can
focus
on
on
front
and
work
the
coming
days.
He
had
said
he.
I
don't
think
he
has
seen
so
much
progress
so
far,
but
I
don't
think
he
has
any
any
blockers
or
the
blockers
would
be
me
then.
A
A
I've
been
working
a
little
bit
the
last
few
days
with
integrating
with
the
the
the
new
endpoints
that
rudolph
has
made,
and
I've
done
some
work
with
them,
also
for
the
front-end
authentication
layer
of
making
sure
that
if
your
session
token
becomes
invalid,
you
get
redirected
to
the
login
page
to
log
in
again
etc.
Those
kind
of
basic
scaffolding,
structural
stuff,
and
the
same
with
me
as
with
rudolph.
A
I
expect
the
work
move
to
move
forward
quite
quickly
when
we
once
we
have
the
the
foundation
of
the
set
and-
and
I
don't
have
any
any
blockers
there-
I
think
we
have
yeah.
The
data
model
is
quite
set,
and
we
have
also
discussed
this
about
the
duplicate,
praise
and
and
all
that
kind
of
stuff.
We
discussed
last
time.
A
For
reasons
I
don't
do
not
know,
and
I
don't
I
know
that
he
has
not
had
yeah,
he
has
begun
doing
work
on
the
meeting
tracker
bot,
but
that
is
all
I
know
for
now.
I
cannot
speak
more
for
him.
A
End
of
the
list,
I
can
mention
that
we
would
have
spent
a
long
time
if,
if
everyone
would
have
been
here,
of
course,
maybe
we
will
consider
moving
this
meeting
to
a
time
that
better
suits
everyone
I'll
see.
But
but
it's
it's
difficult
when
everyone
is
in
different
time
zones.
A
I
can
just
mention
what
some
stuff
that
that
is
up
ahead.
That
needs
to
be
done
and
one
of
the
work
streams
that
needs
to
be
started
is
the
is
the
work
of
taking
care
of
the
data
that
comes
out
of
the
the
phrase
system
and
the
source
credit
system
and
the
the
last
step.
That
is,
the
distribution
and
the
analysis,
steps
and
it
seems
like
it
could
work
doing
this
in
a
jupiter
notebook
format
like
I
proposed
in
on
the
chat
or
like
last
week.
A
A
So
just
a
a
short
rewind
to
fresh
up
our
minds
about
this,
the
the
the
source
cred
the
system
and
the
the
phrase
system.
They
are
output,
data,
the
the
phrase
system,
outputs,
quantified,
yeah,
the
quantified
price
data
and
the
source
credit
system,
outputs,
the
the
grain
calculated
data
for
the
price
data.
We
do
this
manual
validation,
which
I
believe
will
be
a
google
spreadsheet
exercise
for
this
first
version
and
and
then
later
on.
A
We
will
hope
to
include
it
in
into
the
price
system
and
then
comes
the
step
that
I
believe
will
continue
lie
outside
of
of
the
prey
system,
because
it's
a
it's
a
combination
of
data
from
source
credit
and
praise.
It's
not
a
like
a
phrase,
only
functionality
so
that
there
we
merge
the
those
two
data
streams
into
one
and
calculate
the
token
distribution
and
also
when
the
token
have
been
distributed.
We
do
saw
some
analysis
and-
and
we
would
like
to
be
able
to
write
some
some
report
or
the
rewards
committee.
A
They
should
be
able
to
write
some
comments
about
this
phrase
period
and
my
idea
is
to
package
all
this
into
a
jupyter
notebook.
A
python
notebook
with
four
four
tabs,
basically
and
and
the
benefit
of
doing
it.
That
way,
would
be
that
we
can
take
this
jupyter
notebook
and
then
we
can
copy
it
for
for
next
next
phrase
period
and
reuse.
It
and
also
modify
it
slightly
for
next
time,
and
then
we
can
store
store
those
nodes
notebooks
in
a
in
a
github
repository
and
have
have
full
history.
A
So
you
can
easily
move
back
and
in
the
best
of
words,
we
would
also
like
build
a
really
simple
website
where
you
can
have
like
a
list
of
praise
periods
and
you
just
click
one
of
the
older
place
periods,
and
that
opens
up
the
the
old
jupiter
notebook
where
you
can
see
like
all
the
details,
how
the
how
the
the
the
praise
data
was
being
converted
into
tc
tokens
and
the
analysis
and
the
comments
from
the
rewards
committee
etc.
A
So,
basically,
for
one
notebook,
four
tabs,
the
first
one
is
the
the
price
input
data,
the
quantified,
the
data.
The
second
one
is
the
source
credit
input
data
with
the
grain
information.
A
The
third
one
is
where
the
actual
tec
token
distribution
is
being
calculated
and
and
how
this
looks
in
detail.
We'll
see
you
know
it's
it's
a
formula,
it's
an
algorithm
that
turns
quantified
based
data
into
tec
tokens.
So
that's
a
mathematical
formula
somehow
and-
and
I
think
it
would
be
good
to
showcase
that
whatever
parameters
is
deciding
how
this
distribution
looks.
A
We
want
to
visualize
that,
and
we
also
want
to
make
the
actual
token
distribution,
and
we
want
there
to
be
a
button
at
the
bottom
saying
you
know,
export
dsv
data
and
that
data
you
can
feed
into
the
the
the
dow
that
makes
the
the
actual
payments
and
the
fourth
one
would
be
used
after
the
the
distribution
is
done,
and
that
is
the
analysis
step
so
that,
like
automated
analysis
of
you
know
both
the
the
the
two
input
streams,
as
well
as
the
the
final
token
distributions
and
and
what
metrics
and
the
visualizations
we
would
like
to
have
there,
I
don't
know,
I
think,
has
a
good
idea
who
everyone
that
was
involved
in
the
praise.
A
Magedon
aftermath-
and
you
know
coming
up
like
these-
are
good,
interesting
metrics-
that
we
would
like
to
measure
when
we
do
a
quantification
that
that
kind
of
stuff
would
be
on
this
screen
for
every
praise
period,
as
well
as
some
some
kind
of
explanatory
text
from
the
reward
committee
yeah
to
sum
things
up.
A
So
that
is
my
idea
about
that
last
step
and
that
that
could
be
treated
as
like
a
separate
work
stream,
because
we
can,
we
cannot
quite
easily
define
how
will
the
output
of
the
prey
system
look,
even
even
though
it's
not
finished
so
so
this
this
thing
can
run
in
parallel
with
everything
else,
any
any
spontaneous
feedback
on
this.
B
A
Yeah,
I
also
saw
that
there
is,
I
think,
there's
a
like
a
csv
data
importer
plug-in
for
jupyter
notebook.
So
you
can
include
that
my
hopes
are
that
we
on
this
github
repository
and
we
have
one
folder
for
each
place
period
and
within
that
folder
we
have
like
two
inputs,
csv
files
that-
and
we
can
use
them
for
for
what
you
mentioned,
of
course,
to
include
them
in
a
web
page
as
long
as
they
are
accessible
on
github.
We
can
use
them
as
easily
as
if
they
were
in
the
github
guest.
B
Yeah
and
for
the
matrix,
I
think
we
don't
have
like
the
best
idea
on
them
yet,
but
it's
something
we'll
be
looking
into
in
the
research
group.
A
Yeah
and
the
big
advantage
here
would
be
like
if
we
start
with
a
notebook
with
with
quite
simple
metrics,
then
we
copy
it
for
for
the
next
price
period,
and
then
we
add
something
that
we,
you
know
figured
out
that
that
period.
We
wouldn't
need
this
as
well,
and
then
it
can.
You
know
it
can
slowly
evolve
over
time,
but
we
can
always
move
back.
So
it
becomes
a
really
a
tool
for
for
transparency
and
traceability
and
see
who
did
what
and
when
yeah.
A
And
I
also
could
mention
that
we-
I
talked
to
mitchell
and
livy
before
this
and
and
sort
of
concluded
that
the
the
reward
system
process
and
the
rules
of
pace
and
quantification.
Those
two
work
streams
are
not
necessarily
done
done,
but
at
least
they
are
they're
on
hold
for
for
now
that
there
is
no
more
work
being
done.
Currently,
maybe
we'll
reopen
them
later
on.
A
A
No
but
but
I'd
say
we're,
we
are
seeing
seeing
good
progress
and
and
griff
said
like
give
it
a
meeting
with
grief
just
recently
like
the
all
resources,
everyone
is
quite
squeezed
just
now.
Everyone
has
a
lot
to
do,
and
so
and
hopefully
in
like
a
week
or
ten
days
time,
there
will
be
more
space
in
everyone's
calendar
and
I
think
things
will
move
even
even
faster
when
the
comments
become
as
upgrade
parameters.
Dashboard
is,
is
done,
etc.
A
A
Yeah,
so
thank
you
all
for
this
and
and
see
it
and
take
care.