►
From YouTube: Giveth livestream - GIV meeting on July 19, 2021
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
it's
it
looks
like
it's
just
the
three
of
us
at
the
moment,
so
the
team
must
be
a
little
busy
in
paris.
So
we
can.
We
can
run
through
the
agenda
and
I
think
probably
make
it
like
briefer
than
usual
and
maybe
on
our
like
in
the
channel.
I'll
just
share
the
notes
and
post
what
priorities
we
kind
of
initially
talk
about,
but
I
want
to
make
sure,
obviously
that
we
get
input
from
the
rest
of
the
team
as
well
before
we
like
100,
lock
it
in.
B
C
A
Sounds
good
okay,
so
I
will
skip
the
centering
just
in
effort
of
time,
but
for
check-in.
How
are
you
feeling
right
now
what's
your
goal
for
today
and
how
would
you
like
to
use
our
time
together
on
this
call?
I
can
get
us
started.
A
I
just
did
some
kundalini
yoga,
so
I'm
feeling
very
centered
my
goal
for
today
being.
A
For
the
team
to
set
priorities
for
this
sprint,
I
I
think
just
for
us
to
initially
talk
through
what
we
feel
are
some
good
priorities
to
suggest
to
the
greater
give
team
in
the
tokenomics
channel
and
yeah.
We
can
just
review
the
remaining
things
potentially
rolling
over
from
sprint
11
and
what
potential
like
new
things,
we'd
like
to
focus
on
and
I'll
pass
it
to
lauren.
B
Hey
guys,
I'm
feeling
good
yeah,
I'm
eager
to
like
kind
of
focus
and
get
some
work
and
so
kind
of
yeah.
I
guess
I
mean
we
could
quickly
review
what
we
talked
about
yesterday
and
I
don't
know
if
there's
any
other
outstanding
things
that
we
need
to
talk
about,
but
I
really
feel
like
almost
like.
We
could
make
this
call
like
10
minutes,
and
that
would
be
like
my
ideal
goal,
but
yeah
I'm
here
for
whatever
time
we
need
and
I'll
pass
it
to
done.
C
Yeah,
I
I
feel
good
as
well.
I
dig
into
that
node
in
the
morning
and
I
I
was
really
interested
in
that
the
technology
and
as
we
had
a
meeting
on
give
screen
planning
yesterday,
as
lauren
also
stated
today,
we
can
just
go
through
the
main
points
and
what
features
are
going
to
be
next
launched
and
yeah?
That's
it.
A
Awesome
thanks.
You
guys
and
yeah
yesterday
was
closing
out
sprint,
11
and
reviewing
where
we're
at
with
things,
so
we
are
all
aligned
there.
The
intention
of
this
call
is
to
determine
our
priorities
for
sprint
12
and
what
we're
going
to
focus
on
for
this
next
week.
A
So
if
you
would
like
to
follow
along
on
the
ocean
agenda,
I
posted
a
link
to
it
in
the
scheduling
channel
as
well
as
the
give
token
tokenomics
channel.
I,
the
initial
intention
was
to
set
priorities
and
then
get
clear
on
action,
items
and
owners
of
each
task,
but
I
think
we'll
probably
just
use
the
time
to
initially
set
some
priorities
and
we
won't
assign
owners
or
clear
actions
yet
because
we
need
to
run
it
by
the
rest
of
the
team.
A
A
So
that
is
the
design
stuff
getting
the
governance
proposal
around
liquidity
mining
parameters
approved
through
a
vote
continuing
to
push
gardens
and
hoping
for
them
to
redeploy
rinkeby
with
the
new
settings,
resolving
the
dynamic
issuance
rate
tension,
and
that
is
all
so
for
sprint.
12
priorities.
A
I
am
recommending
that
we
obviously
continue
with
the
things
that
we
discussed
yesterday
that
are
rolling
over
from
sprint
11,
with
the
addition
of
continuing
to
onboard
donna
onto
the
team
and
making
sure
that
she
feels
comfortable
and
and
well
resourced.
And
then
I
added
a
bullet
here.
A
Enhancing
communication
with
dap
node
developers
yeah
just
seeing
like
the
the
best
ways
that
we
can
like
integrate
the
the
people
that
are
working
on
the
tech
into
yeah,
our
sprints
and
not
necessarily
having
them
in
each
meeting,
but
like
how
we
can
have
clear
communication
with
them,
at
least
from
donna
and
I's
role.
Standpoint
lauren.
Do
you
feel
that
there
are
any
other
additional
things
you'd
like
to
see
us
focus
on
over
the
next
two
weeks?.
B
I
think
did
you
mention
the
design,
because
I
kind
of
just
I
think
one
of
my
my
personal
priority
for
the
next
two
weeks
is
like
to
support
and
to
kind
of
just
keep
pushing
the
finishing
out
of
the
design
like
for
gift
facts
and
they
give
drop
and
stuff.
We
talked
about
it
yesterday,
but
I
didn't
hear
you
mention
it
just
now.
A
Yeah,
I
I
have
that
at
the
top
of
the
list,
from
what
we're
rolling
over
as
what
we
didn't
like
fully
complete
from
the
last
sprint
yeah.
So
like
continuing
the
the
feedback
on
marco
various
considerations
of
the
the
give
backs
and
give
drop
design
stuff.
Is
he
gonna
have
like
separate
design
files
that
he's
creating
around
give
stream,
or
is
that
just
kind
of
like
an
element
integrated
into
like
the
give
drop.
B
D
B
Yeah,
but
I
don't
think
anything
else
like
I
mean
what
you
said
about
dapnode
like
communicating
in
cancer
communication
with
daphne
developers.
I
think
like
also
another
priority
for
me.
This
week
is
like
to
just
try
to
support
dap
note,
as
they
kind
of
like
going
through
this,
like
clearing
up
things
around
the
air
drop
and
like
like.
B
We
were
talking
about
like
keeping
the
vibes
high
and
stuff,
and
then
I
think,
just
like
all
the
lessons
learned
that
come
into
that
like
things
that
I'm
realizing,
I'm
realizing
some
things
like
people
are
having
trouble
claiming
on
their
phones
and
that's
something
that
they
didn't
think
to
test
that,
like
we
probably
wouldn't,
have
thought
to
test
too
and
other
things
like
this,
I
think,
are
great
lessons
learned
from
dap
notes.
So
yeah
just
kind
of
like
watching
that,
like.
A
How
we
can
support
that
in
the
in
the
community,
you
know
with
like
onboarding
and
resolving
tensions
and
keeping
the
vibe
side,
but
also
even
like
you
know.
Maybe
we
talk
about
this
in
communications
like
public
relations,
either
like
how
can
we
support
them?
I
mean
I
know
I
went
through
and
did
some
social
media,
but
yeah.
A
It's
like
brainstorming,
other
ways
that
we
can
support
them
as
like
a
partner
and
also
look
to
maybe
even
have
like
plans
in
place
for
if
this
something
like
this
were
to
happen
with
us
like
just
discussing
in
advance
like
how
might
we
handle
something
like
that
like
what
would
be
our
plan
of
action
could
be
cool
to
kind
of
get
the
ball
rolling.
C
Okay,
well,
I
think
I
went
through
the
the
introduction
to
that
node
and
I
think
it
was
really
cool
and
but
I
think
we
need
a
more
like
easy
to
read
easy
to
read
guide.
It's
not
that
easy
to
read.
It's
just
text
we
can
have
like
flowchart,
which
is
more
like
in
a
snapshot.
C
A
Think
yeah,
as
far
as
like
the
documentation
stuff
like
if
someone
is
newly
coming
to
the
top
node
website
and
looking
to
understand
what
it
is
and
and
how
to
onboard.
Is
that
the
the
copy,
the
content
that
you're
talking
about
donna.
B
Lauren,
isn't
that
what
you
and
mitch
have
been
working
on
documentation
yeah?
We
do
have
some
documentation,
that's
like
ready
to
go
up
for
daphna,
but
it
is
like
mostly
text-based
donna
was
talking.
I
think,
like
more
that
she
would
like
to
see
like
kind
of
like
more
visuals
and
things.
C
B
B
If
you
want
to
create
like
like
animations
or
designs
like
you
have
to
involve
more
people
and
yeah,
and
it
takes
like
longer
to
explain
things
and
then,
when
things
are
a
little
bit
more
technical
than
I
don't
know,
yeah
it's
just
kind
of
more
in
the
interest
of
time
that
they
they
don't
have
a
lot
of
animations
but
yeah
with
with
giveth
we're
we're
working
on
like
the
give
drop
designs
right
now
and
marcus's.
Marco
is
trying
to
come
up
with
like
good
ways
of
visually
representing
everything.
B
So
we're
gonna
have
a
combination
of
both,
but
I
think
the
documentation
is
still
necessary
and
and
useful
to
have
in
text.
It's
not
like
really
there
for
people
who
are
just
like.
Oh,
like
I
don't
know,
it's
not
really
there
for
just
like
easily
consumable
it's
for
people
who
kind
of
like
want
to
more
dive
deep
into
the
details
of
things,
but
I
think
there's
value
in
merit
having
both.
A
Dapnode
is
a
is,
you
know,
we're
we're
working
on
give
us
dapnote
is
like
a
partner
or
a
sister
organization
in
a
sense,
and
sometimes
we
will
like
there's
a
few
people
on
the
team
that
kind
of
cross
over
and
work
on,
both
both
organizations,
but
I
think
for
this
sprint,
I
I
imagine
that
we
would
want
to
like
focus
our
resources,
mostly
on
on
how
we
can
create
or
adapt
or
or
learn
from
what
dap
note
has
done
and
create
like
more
visual
documentation
for
giveth,
for
example,
I
mean
in
a
lot
of
the
documentation
we've
been
creating
on
the
comms
team
forgiveth,
I
wouldn't
say
it's
super
visual
like
we
use
memes
and
stuff,
but
I
guess
when
we
sometimes
use
like
screenshots
of
like
a
flow
when
we're
describing
a
certain
element,
I
think
that's
an
easy
way
of
doing
it.
C
Yeah
and
I
have
a
question:
what
forest?
What
do
you
mean
by
enhancing
communication?
With
that
note
developers
I
mean,
where
is
the
problem.
A
That's
what
I
was
sharing
with
you
on
our
one-on-one
call
when
I
was
expressing
like
with
graffia
just
that
at
in
the
pm
role
like
I
personally,
when
we
had
like
edu
and
a
couple
different
developers
like
griff,
was
kind
of
the
go-between
with
them,
and
I
wasn't
communicating
with
them
directly
and
so.
That
bullet
is
just
suggesting
that,
like
discussing
a
plan
where,
as
you're
onboarding,
you
can
be
in
more
direct
communication
with
them.
A
A
Clear
deliverables
for
marco,
so
that
he
like
really
understands
all
the
different
like
design
pieces,
we're
working
on.
And
then,
if
there
are
any
questions
or
like
whenever.
A
A
Through
some
of
these
concepts
or
give.
A
Together
on
a
call,
we
can
absolutely
do
that,
but
I
think,
having.
A
For
him
yeah
and
then
supporting
deafnote
and
pr
and
community
support
and
taking
a
look
at
our
documentation
and
their
documentation
and
yeah
as
you're
going
through.
Definitely
besides
just
testing,
like
all
of
that
feedback
that
you
have
donna
for
sure.
A
Okay,
well,
I
feel
like
yeah.
We
don't
really
need
a
whole
lot
more
time
than
that.
I
can
and
just
put
those.