►
From YouTube: EOSIO+ Meeting, January 20th, 2022
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).
C
E
Well,
I
was
thinking
that
that
I
should
do
that,
but
I
I'm
totally
happy
with
the
with
circulating
this
role
to
to
everybody,
so
we
could
go
move
on
with
that.
A
Can
can
I
make
a
suggestion?
I
I
read
what
you
said
romney
and
I
I
don't
want
to
disagree
with
that,
but
I
think
there's
a
certain
efficiency
if,
if
as
long
as
it
works
with
just
having
the
continuity
of
of
some
of
you
know
like,
I
don't
want
to
have
to
know.
Oh
my
gosh.
This
is
my
week
to
to
do
this
and
stuff
like
that.
It
really
is
going
to
be
better
if
one
person
does
it.
A
I
think
that
I
I
would
propose
kirsten
for
a
couple
of
reasons
number
one,
even
though
he
was
working
for
telos.
He
is
not
a
long
time
fellows
guy
and
you
know
in
the
same
way
that
I
am
and
and
as
you'll
see
in
working
with
him,
as
you
already
probably
have.
He
is
very,
he
is
very
consensus.
Building
guy,
he
is
very
on
he's
very
great
focus,
and
I
I
don't
think
I
you
know
yes
he's
from
telos,
but
I
don't
think
that
he's
gonna
be,
I
think,
he's
more
aligned.
A
He
could
be
more
aligned
to
logic
and
fairness
here
than
anyone
jane
and
he's
also
quite
good
at
it.
I
mean
he's
like
he's.
If
you
I
don't
know
how
long
you
guys
have
been
meeting
with
that
but
yeah
I
I
think
I
I
think
if
we
can
find
somebody,
can
we
audition
this.
You
know
of
of
of
kirsten
doing
it
for
a
couple
times
and
then
reassess
whether
things
are
going
efficiently,
because
I
think
if
it
does,
then
it's
ultimately
more
efficient
anyway.
That's
my
thought.
All.
D
Right,
well,
I'm
always
for
brutal
efficiency.
My
my
rebuttal
here
is
simply
that,
first
of
all,
I
think
that
we
should
be
taking
this
into.
B
Our
own
hands:
it's
not.
D
Necessarily
about
who,
specifically,
is
gonna,
be
doing
it.
It's
about
us
doing
it
together,
and
I
think
that
a
rotating
chair
encourages
that
secondarily.
D
B
Is
temporary
he's
a
loan
asset
from
telos.
D
And
we
haven't
decided
how
long
we're
gonna
be
running
this
group.
But
if
this
group
runs
for
one
in
a
few
months,
more
than
long
longer
than
kirsten's
tenure.
B
Then
we
need
a
solution
and
if
that
solution
is
us
taking
it
upon
ourselves
to
rotate
the
chair,
then
I.
D
So
whatever
the
group
decides,
that's
those
are
my
thoughts.
A
Sure
in
in
in
rebuttal,
I
would
say
that
he's
you
know
his
his
tenure
with
us
can't
you
know
is,
can
be
flexible.
Also,
we
don't
need
to
find
out.
We
don't
need
to
find
today
or
tomorrow,
a
solution,
that's
going
to
work
for
the
ongoing
lifetime
of
the
project.
We
need
to
find
something.
That's
going
to
work
for
this,
this
phase,
yeah
and-
and
I
I
just
I
do
think
with
as
busy
as
we
are.
A
D
A
F
A
F
I
think
if,
if
the
to
step
up,
then
they
should
definitely
be
vocal
and
the
group
could
be
open
to
it.
I
know
I'm
in
the
same
boat
as
justin
like
I.
I
don't
want
to
take
that
responsibility,
because
I
don't
think
I
would
do
it
justice
but
yeah
having
that
flexibility
is
good
and
having
something
that
we
can
default
to
is
also
really
good,
so
that
for
the
app
to
keep
us
on
track.
G
Yeah
we
and
we
invited
christian
exactly
for
that
role
to
be
a
dedicated
project
manager
so,
and
it
is
good
to
have
that
in
one
hand,
because
someone
follows
through
and
and
keeps
an
eye
on
everything
and
on
a
process.
So
it's
it's
good
to
have
a
dedicated
person
for
rotating.
I
don't
I
don't
know
I'm
bad
at
leading
the
meetings
and
and
taking
notes,
and
many
of
us
are
as
well
so.
E
Yep
yeah,
so
so
then,
then,
I'm
fine
with
that
I've
been
assigned
to
it.
I
like
to
do
it
so
so
we
have
this
this
initial
time
frame
that
we
discussed
and
agreed
to.
If
we
find
out
that
this
takes
longer,
then
obviously
we
we
tell
us
we
need
to
reassess
that
if
I
can
manage
this
with
all
the
other
tasks
that
we're
doing,
but
but
I'm
happy
to
do
this
as
long
as
required
and-
and
we
agree
on
the
tell
site,
to
dedicate
my
resources
to
this.
A
I
I
think,
that's
great
and
if
I
can,
if
I
can
offer
this,
I
have
a
new
employee
coming
on
in
two
weeks
or
maybe
a
little
bit
less
who's
who
50
of
her
job
is
going
to
be
to
sit
in
meetings
like
this
and
take
notes
and
distribute
them
to
everybody.
A
And
so
I
I
would
be
happy
to
to
make
this
meeting
one
of
her
regular
meetings,
and
so
we
would
so
that
it.
It
takes
the
job
of
being
essentially
the
secretary
of
the
meeting
out
of
the
hands
of
the
of
the
chair,
which
I
hopefully
makes
it
easier
actually.
Hopefully
that
makes
it
easier
either
way
we
do
it.
So
just
something
to
think
about.
If
you
guys
want
me
to
follow
through
with
that,
when
she
comes
on
sure.
E
Okay,
thanks
for
that
douglas
so
question
one,
we
did
record
the
last
meeting,
should
we
disc
should
we
also
record
this
meeting.
E
Oh
okay,
excellent
thanks
can
can
somebody
make
me
host
so
I
can
share
my
screen.
E
So,
as
you
might
have
seen
next
to
all
the
horse,
discussions
on
you
probably
want
to
cut
this
out
rami
yeah.
E
We
had
a
lot
of
discussions
about
the
name
in
the
channel,
so
it's
probably
ended
up
with
with
you,
having
not
seen
the
the
minutes
from
from
last
meeting,
which
I
try
to
put
into
a
mind
map,
because
it
was
kind
of
distracting
and
and
obviously
a
little
bit
unstructured,
because
it
was
was
kind
of
a
new
setup.
So
I
tried
to
do
this
in
in
this
kind
of
format.
E
Don't
worry
I'll
be
zooming
in
in
a
second,
so
what
I'll
try
to
do
is
I
try
to
have
the
main
topics
in
each
branch
here
and
then
we
can.
We
can
work
through
those
branches,
any
type
of
decision
or
thing
that
we
want
to
move
to
the
next
meeting
or
we
need
to
decide
on
or
like
have
work
in
progress.
They
will
be
flagged
with
a
little
little
post-it
note
here
on
this
board.
I
will
circulate
the
board
to
all
attendees,
so
you
you'll
have
right
access.
E
You
can
always
jump
in
here,
make
comments
at
add
post-its
and
be
in
a
position
to
to
kind
of
update
this
and
amend
this
if
this
is
required
from
your
site.
So
we
have
like
a
working
document
that
everybody
can
jump
in,
so
this
is
a
mirror
board.
I
don't
know
if
all
of
you
are
familiar
with
this,
the
cool
thing
that
we
have
in
this
mirror
board
and
I've
been
testing
this
with
justine.
E
The
adjustment
is
that
we
have
kind
of
a
voting
function
that
we
can
utilize
so
so
we
can
basically
have
a
vote
started
for
everybody.
That's
joining
that
that
mirror
board,
and
I
can.
You
can
then
have
like
one
vote
and
you
just
click
here
and
just
vote
for
for
whatever
you
want
to
vote
for
and
then,
if
we
end
the
session,
then
we
basically
have
the
results
and
and
it's
an
anonymous
wall
vote,
so
we
see
how
everybody
voted.
E
That's
gonna
be
far
easier
than
than
having
raising
hands
nodding
heads
without
having
cameras
on
so
from
that
perspective,
I
think
this
would
be
a
good
interim
way
for
voting
in
this.
So
if
everybody's
okay,
then
I
will,
I
will
circulate
the
mirror
link
and
we
can
go
on
from
there
to
work
in
this
board.
E
Yeah,
I
will
circulate
the
link
after
the
meeting.
So
then
everybody's
got
this
okay.
I
just
wanted
to
be
sure
that
that
we're
going
to
use
this
so
good.
Then
we
had
some
topics
from
from
last
meeting.
Let
me
zoom
in
here.
Can
everybody
read
this?
Okay.
I
Okay,
not
at
all
yeah
yep.
I
K
You
might
have
to
share
your
screen
if
you
have
an
extra
monitor
if
it's
on
that
monitor,
if
you're,
just
sharing
a
window
and
you're
zooming
in
it
might
not
have
appeared
on
the
third
screen.
E
Okay,
there
you
go
okay,
now
we're
good
excellent
good,
so
we
had
this
hold
on.
We
had
this
voting
discussions
rami.
You
raised
the
point
in
the
chat
today
that
your
opinion
was
that
one
vote
per
chain
would
not
necessarily
be
what
we
should
be
looking
at.
So
we
we
did
this
decision
in
the
last
meeting,
so
I
would
I
was
just.
E
I
would
just
like
to
follow
up
if
everybody
agrees
that
we
we
keep
this
for
now
as
an
interim
solution,
but
we
will
be
voting
on
a
more
broader
range
of
participants
that
are
having
votes
in
this
meeting
at
a
later
point
of
time.
So
if
that's
fine
for
you,
then.
D
Just
to
be
clear,
like
I
was
just
voicing
some
thoughts
that
I've
had
since
last
week,
simply.
E
E
D
We
would
be
missing
out
on
some
important
opinions
along
the
way
and
that
in
the
future,
when
we
start
deciding
what
a
real
government
solutions
should
look
like
that,
one
chain.
E
Yeah
we
still
have
like
aaron
in
in
these
calls
to
to
kind
of
build
opinions
and
give
his
his
experience,
which
is
awesome
into
this
round.
So
so
I
I
trust
that
that
the
representatives
of
the
change
will
will
follow
those
recommendations,
but
obviously
you're
right.
We,
we
might
even
think
about
having
like
different
voting
assignments,
so
specific
things
that
that
we
may
think
of.
D
E
D
I
Okay,
so
kirsten
just
for
what's
on
the
screen
right
now,
I
believe
we
have
eight
or
nine
chains
represented
in
this
call,
but
I
only
see
five
on
screen.
I
don't
know.
E
Though
that
that
was
what
I
could
take
from
from
the
participants
list,
because
I
was
not
hundred
percent
sure
who
is
really
participating
right
now,
so
we
can,
we
can
just
amend.
I
I
Yeah,
eva
yeah,
that's
what
I
was
thinking
of
ux
exactly
yeah
and
I
believe
that
encompasses
everybody.
A
Ones
that
you
know,
I
don't
know
if
they're,
one
being
bullish
and
the
other
being
being
mythical
games,
both
are
they're
both
running
big.
J
I
hope
this
is
only
public
chains
for
now.
Okay,.
B
I
Great
message:
well,
that's
what
I
was
I
was
imagining
was
that
whoever
represents,
for
example,
telos.
You
will
have
your
own
internal
process
as
to
who
gets
sent
to
this
group.
I
don't
think
it
should
be
this
group
that
decides
who
telos
decides
to
center
represent
telos,
for
example,
right.
B
And
then
the
the
person
that
we
send.
I
would
hope
that
these
decisions
are
not
like
hey.
We
need
to
decide
on
this
and
by
the
end
of
the
call
the
decisions
made
like
we
could.
We
should
have
like
at
least
a
week
of
time
to
go
solicit
feedback
from
our
stakeholders,
our
dapps,
whoever.
However,
we
make
our
decision
process,
so
the
representative
doesn't
actually
have
the
executive.
D
B
The
grand
mass
example
I
would
love
to
have
you
know
aaron
and
his
team
contribute
to
what
our
vote
is,
even
if
they
don't
represent
here
as
a
specific
chain
and
have
their
own
vote
right
and
that
kind
of,
if
we
all
do
a
good
job
of
soliciting
input
from
our
stakeholders
on
our
chains.
B
I
One
part
of
it
is
also
who
attends
these
meetings
right
so
yeah.
I
think
I
had
the
discussion
with
aaron
and
he
was
saying
why
should
he
even
attend
these
meetings?
Why
is
he
different
than
everybody
else,
and
then
who
decides?
I
guess
attendance
to
these
meetings?
Who
decides
which
chain
can
be
represented?
I
think,
like
obviously
kirsten
just
put
a
star
beside
eva,
should
there
be
a
star
beside
ultra
because
of
their
particularities?
I
know
remy
brought
those
up
last
week
as
well.
I
All
of
that,
I
think,
is,
is
kind
of
at
some
point.
Whoever's
here
right
now
is
going
to
make
a
decision
that
can
be
modified
in
the
future,
but
without
making
that
decision
now
we
just
turn
in
circles,
as
we
did
last
week
as
we
did
earlier
in
this
call
talking
about
kirsten,
which
is,
though,
at
some
point.
We
just
need
to
move
forward,
and
you
know
I
think
one
another
with
mitigating
risks
like
we
accept
that.
Maybe
this
is
not
the
ideal
solution
for
now,
but
the
alternative
is
just
doing
nothing.
B
Yeah,
I
mean
one
solution
for
that
I
think
is,
and
we
probably
should
this
is
another
decision
to
make.
But
if
these
meetings
are
made
public
or
a
summary
of
them
and
the
upcoming
decisions
are
made
public
and
they're
done
on
a
schedule
that
people
know
where
to
learn
what
decisions
are
being
made,
then
a
team
that
we're
not
really
in
talks
with
for
via
any
chain,
but
they
are
watching
these
things.
Almost
like
political
shenanigans.
B
You
you
see
that
there's
something
coming
up
on
the
ballot,
because
you
can
see
what's
going
on
publicly
and
then
you
go
to
your
local
representative
and
say
hey.
I
know
this
is
coming
up.
You
may
not
have
any
idea
how
important
it
is,
but
here's
who
I
am
and
here's
how
important
it
is.
Please
consider
my
you
know
so
like
if
the
public
can
know
what's
being
voted
on.
They
can
go
to
their
particular
chain
or
chains,
because
maybe
they're
on
many
of
our
networks
and
say
hey.
B
E
E
Sometimes
there
are
possibly
new
people
joining
in
like
douglas
today,
so
we
are
at
this
point.
We
are
not
gonna,
discuss
this
over
and
over
again.
I
just
wanted
to
go
through
this,
because
I
I
think
it
is
important
that
that
we
are
all
having
the
same
understanding
and
we
have
the
agreement
for
now
that
this
is
the
schedule
we
want
to.
We
want
to
run
on
now
with
the
with
the
knowledge
that
we
might
want
to
reassess
at
a
specific
point
of
time.
E
So,
but
I
would
I
would
just
move
on
from
here
the
I
made
a
two-star
one
for
non-open
source
and
we
have
eva
with
non-public,
which
is
not
a
judgment.
It's
just
an
information
here
in
in
that,
so
the
the
task
I
would
like
to
give
give
all
trains
now
is:
please
get
back
to
your
chains
and
decide
who's
gonna
be
the
voting
representative
in
this.
E
When
we
do
the
voting,
so
this
good-
if
we
have
this
for
next
meeting,
so
please
pass
this
person
to
me
and
then
I
can.
I
can
add
it
here
so
so
we
know
who's.
Who
is
the
voting
representative?
E
We
discussed
the
some
points
which
are
open,
which
is
voting
weight
where
we
we
did
have
some
some
slight
escalation
last
week
when
we
said
well,
why
shouldn't
the
big
trains
have
more
votes
than
small
trains,
so
I
think
we
we
postponed
this
and
said
well
for
now
one
chain,
one
vote
to
have
like
a
simple.
E
Like
a
proposal
process
so
who
proposes
like
a
new
chain
to
join
in
and
what
we
did
discussed
yes
last
time
was
that
non-trained
members
can
be
can
be
voted
in
by
a
simple
majority
by
all
trains.
So
if
somebody
decides
or
would
like
to
forward
aaron
as
an
example
to
this
group,
then
we
have
a
simple
vote
and
say
yeah.
We
would
like
to
do
this
and
simple
majority,
and
then
this
new
person
or
organization
can
join
in
while
not
having
a
vote
unless
they
are
a
new
chain.
D
H
That
this
group
would
be
you
know,
voting
on,
because
I
guess
the
scope
of
what
we're
voting
on
might
influence
a
selected
and
and
b
what
you
know
what
this
voting
pro
it
might.
It
might
impact
the
voting
process
like,
for
example,
if
all
we're
voting
on
is
within
what
how
we're
spending
the
budget
within
this
group
and
the
recommendation
we're
posing
to
the
network.
H
It's
pretty
small
scope.
We
don't
have
to
worry
about
things
like
you
know
the
risk
of
a
moral
hazard,
for
example,
if
if
our
scope
was
larger,
where
this
group
is
responsible,
for
example,
of
defining
the
road
map
for
all
of
eosio.
H
E
In
fact
they
have
to
when
we
wouldn't
vote
on
something
we
discussed
today,
then
this
this
wouldn't
be
possible
because,
obviously,
if
you
want
to
vote
on
something,
that's
gonna
cost
like
100k,
then
you
would
have
to
have
like
a
community
vote
or
ask
some
people
inside
your
organization
to
to
approve
that.
Then,
obviously,
we
cannot
vote
for
this
today,
but
we
can
vote
for
this
most
likely
next
week,
when
this
representative
had
has
had
a
chance
to
discuss
this
and
and
have
a
chain
based
approval
on
on.
E
If
they,
if
the
money
should
be
spent
or
not,
we
we
could
discuss
having
like
a
split
of
voting
representatives
based
on
topics.
So
if
we
need
to
discuss
budget,
we
pull
in
person
a
and
if
we
want
to
discuss
like
a
general
feature
or
requirement,
we
push
in
person
b,
but
I
personally
think
that's
gonna,
that's
gonna,
be
too
diffused.
We're
gonna
have
too
many
people
on
this
call
circulating
and-
and
I
would
rather
propose
to
have
one
person.
E
H
E
We,
we
all
say:
okay,
we
can
all
vote
for
this.
We
have
the
authorization
to
do
that.
A
Can
I
mention,
I
think,
that
the
process
that
we're
discussing
is
going
to
definitely
increase
the
time
right.
Let's
we
think
about
something
and
then
and
then
the
next
week
we
do
research
on
what
the
budget
is
likely
to
be,
and
then
the
next
week
we
you
know,
decide
if
we
have
enough
information
to
vote
or
not
and
then
the
next
week
we
put
it
to
our
vote.
H
Which
is
a
part
of
why,
knowing
the
scope
of
what
we're
voting
on
the
larger
the
scope,
the
more
rigorous
and
long
it's
going
to
take,
and
if
we're,
if
we're
agreeing
now
like
hey,
this
is
actually
a
pretty
small
school.
It's
just
you
know
we
got
this
250
000
budget
from
the
enf
we've.
This
is
our
mandate.
Yes,
we're
just
we're
just
operating
within
that
very
small
scope
of
a
mandate.
We
can
move
pretty
quick.
A
Right
right,
I
think
so
I
think
that
is
so
looking
at
scope
is
important
and
also,
though,
looking
at
the
phase
that
we
are
at
in
in
the
development
of
of
this
in
the
life
cycle
of
this
organization.
So
for
you
know
in
you
know
a
year
from
now,
maybe
it's
great,
maybe
maybe
that's
maybe
we
need
even
longer
before
we
vote
on.
Maybe
you
know
major
things
right
now.
My
concern
I've
expressed
to
some
people
is
that
you
know
slow
progress
here
is
you
know
it
does
not
help
the
overall.
A
You
know
investor
narrative,
at
the
very
least
for
for
the
eosio
you
know,
communities
and-
and
I
think
we're
in
a
phase
where
we
need
to
where
we
need
to
accelerate
our
our
speed
of
of
decision
making.
You
know
not
slow
it
down
later
on.
We
would
try.
You
know
the
the
situation
would
be
opposite
so
so
I
you
know,
let's
look
in
figuring
out
these
governmental
processes.
A
Exactly
for
the
current
reality
totally,
my
my
view
is-
and
some
of
this
is
expressed
in
how
we
do
things
on
telos
and
it
has
its
positives
and
negatives.
But
my
view
is:
we
need
to
move
quickly.
We
need
to
be
open
and
receptive
to
people
saying
hey.
I
think
you
moved
a
little
too
quickly
on
this
and
we
should
do.
A
We
should
make
a
change
or
conditions
have
changed,
or
it's
not
working
out
the
way
we
want
or
expected,
and-
and
you
know
we
should
be
open
to
re-evaluation,
but
overall
we
should
try
to
move
quickly,
because
the
analysis,
paralysis
is
very
real
and
the
the
opportunity
cost
of
that
time
is
probably
more
precious
to
us
than
than
the
risk
of
making
a
temporary
bad
decision
like
on
on
total.
A
I
think
if
we
move
quickly,
you
know
not
dumb,
but
not
in
a
dumb
way,
but
if
we
move
quickly
and
and
and
make
sure
that
we're
monitoring
things
that
might
not
be
going,
you
know,
according
to
plan
and
making
course
corrections.
I
think
overall,
that
will
be
faster
and
better
than
constantly.
A
You
know
talking
every
last
thing
to
death
and,
and
you
know
I'm
trying
the
poster
child
of-
and
you
know
I
think
we'll
get
more
done
that
way,
and
so
I'm
going
to
stop
talking.
E
Yeah,
it
makes
sense
so
so
one
thing
is
that
that
I
will
obviously
pass
out
agendas
like
in
a
timely
manner,
so
you
have
like
one
two
three
days
to
to
kind
of
discuss
that
internally.
So
if
we
want
to
put
something
up
for
vote
or
something
comes
up
in
on
telegram
in
the
groups
or
on
discord
where,
where
we
have
a
topic
where
we
say
okay,
this
needs
to
be
discussed
next
week.
E
Then
I'll
put
it
on
the
agenda,
circulate
that
and-
and
you
have
a
chance
to
pre-align
with
your
with
your
chains
and
then
we
can
decide
like
large
or
or
e,
which
can
can
be
done
in
here.
So
like.
Obviously,
if
we
have
like
the
technical
representatives
here-
and
we
have
the
topic
for
the
meeting
is
on
to
specific
thing
in
github,
then
you
obviously
he
pulled
your
devs
into
the
into
the
call
and
say
well
what
is
best
best
practice
on
all
the
chains?
E
How
do
you
organize
this,
and
then
we
can
do
this
decision
here?
But
if
we're
talking
about
a
budget
like
one
million
dollars
and
everybody's
got
gotta
do
a
share,
then
obviously
you
wanna-
you
wanna,
have
like
one
week
time
to
to
kind
of
discuss
that,
but
it
shouldn't
be
here
to
to
paralyze
us.
It
should
just
be
there
that,
like
I
have
to
vote
now,
but
I
really
don't
know
if
I
can
decide
this
myself
bring
you
in
a
bad
position,
and
that
was
the
point
that
was
raised.
E
So
if
we
are
doing
it
this
way,
I
think
we'll
all
be
fine
kind
of
just
drop
this
off
the
agenda
to
make
the
decision
next
week
and
not
move
forward,
but
a
fair,
very,
very
good
and
fair
comment.
E
Okay,
so
all
agree
with
that:
definitely
yep,
that's
good
good,
good!
So
yeah
we
had
the
discussion
about
additional
members
and
how
to
add
those
yeah.
We
we
had
this
like
grey,
miss
and
clarion
that
always
say
can
be
voted
into
group.
Basically,
we
decided
last
week
that
we
want
to
do
this
on
this
point
here.
E
D
D
K
Suggestions
how
we
could
involve
them
in
these
processes?
I
think
you're,
specifically
speaking,
of
on
the
eos
network.
So
I
don't
know
I'm
not
familiar
with
every
network
here,
but
as
far
as
you
mentioned,
the
asian
block
producers.
K
I
think
we
do
a
pretty
good
job
at
communicating
as
dnf
with
the
asian
markets
as
far
as
translations
and
text
formats.
So
if
we,
if
we
start
having
meeting
minutes
and
things
like
that,
obviously
they're
not
gonna
be
able
to
watch
these
whole
calls
and
we're
not
gonna
subtitle
them.
But
if
kirsten's
providing
documentation,
meeting
minutes
things
like
that
that
are
in
text
form,
we
could
make
sure
from
the
nf
standpoint
that
those
get
translated
and
distributed
as
as
needed.
G
The
questions
that
we
need
to
we
want
to
ask
those
extended
communities,
and
then
we
find
the
representatives
of
them,
including
asia,
also
latin
america,
or
of
special
biggest
dubs
on
the
network
at
the
moment,
we're
still
making
baby
steps
and
understanding
what
we're
actually
doing
here
and
what
what
the
goal
is.
So
I
mean
inviting
more
people
is
no
problem
as
soon
as
we
know
what
we
want
to
ask
them
or
what
what
we
want
to
tell
them
at
the
moment.
We
still
don't
have
that
yeah.
K
So
I
do
have
one
other
thing
I
would
like
to
add.
So
as
far
as
representatives
and
they've
been
on
a
lot
of
they're
in
the
groups-
and
just
I
don't
see
anyone
on
the
call
today,
but
the
clarion
team,
so
I
just
want
to
share
something
that
mike
who's
been
on.
The
previous
calls
from
clarion
he
shared
with
me.
K
It's
an
idea
from
the
clarion
team
is
any
team
within
any
of
our
chains,
who
would
like
to
participate
in
like
core
eos
io
development
that
they
want
to
discuss,
building
a
program,
so
it'll
be
an
opportunity
to
I'm
reading
this.
You
know
an
opportunity
to
one
train
up
the
community
broadly
on
what
it
takes
to
write
core
code
to
give
feedback
to
the
developers
on,
and
I'm
jacking
this
up,
trying
to
read
it.
K
Basically,
they
want
to
set
up
a
program
where
it
allows
anyone
who
wants
to
contribute
to
core
code
to
basically
have
an
onboarding
program.
This
type
of
thing
from
the
clarion
team,
where
they'll
have
one-on-one
calls
with
these
teams
and
face-to-face
kind
of
interactions
to
kind
of
onboard
any
other
team
within
the
eos
io
ecosystem,
who
wants
to
be
kind
of
core
contributors
to
to
the
nodeos
and
core
level
protocol
code.
K
So
I
haven't
seen
anyone
else
kind
of
step
up
to
that
clarion's
kind
of
doing
their
own
thing
right
now,
with
with
cnf
and
the
mando
upgrade
for
eos
seo
specific,
but
as
we
start
defining
what
the
up,
what
the
features
are
that
we
could
all
agree
on
like
things
like
faster
finality
things
like
that,
if
there's
specific
things
that
a
team
from
for
example,
talos
wanted
to
take
on,
but
they
needed
kind
of
a
fast
track,
onboarding
to
get
up
to
speed
on
certain
aspects
of
eosio.
K
G
That
was
definitely
demanded.
I
know
that
wax
and
proton
are
hiring
c
plus
plus
engineers,
without
blockchain
experience,
just
senior
c,
plus
plus
and
mid
level
super
space
engineers.
So
there
will
be
demand,
of
course,
for
training.
F
I
will
expand
upon
that
and
say
that
that
maybe
should
be
a
function
of
this
organization
and
then
one
branch
of
that
function
can
be
core
development
as
you're
describing
it,
but
core
development
far
expands
the
capabilities
of
clarion.
At
this
point,.
K
F
And
that's
why
I
said
maybe
this
needs
to
be
elevated,
to
be
a
function
of
this
group
at
some
point,
because
when,
if
we're
talking
about
mobile
app
development
or
we're
talking
about
web
application
development,
which
also
falls
within
the
core
of
this
platform,
there
will
be
other
teams
that
will
need
to
be
able
to
facilitate
that
same
service
for
those
same
teams
and
help
bring
people
into
the
fold.
So
I
think
it's
a
great
idea
and
I
think
that
they
are
definitely
someone
who
can
contribute
to
that.
K
Definitely
I
agree
100.
I
think
we
just
got
to
look
at
it
from
where
we're
at
today
and
where
we
plan
to
be
and
where
we're
at
today
is
they're
pretty
much
the
elders
of
the
code
so
early
on.
They
I
agree
with
you.
They
can't
be
the
only
ones.
That's
the
whole
point
of
this
group
is.
We
need
multiple
teams
working
on
core
developments,
there's
no
single
point
of
failure
ever
and
no
single
reliance
on
any
one
team.
I
I
was
just
letting
everyone
know
that
this
offer
is
out
there
and
I'll.
K
Have
him
formulate
the
text
into
the
group
chat.
I'm
not
sure
why
they
didn't
do
that.
Initially,
he
was
just
trying
to
get
my
feedback
and
I
said
I'd
get
feedback
from
the
call
just
to
be
clear.
This
is
something
that
they're
looking
to.
D
Publish
widely
or
are
they.
K
As
far
as
what
getting
new
developers
on
board
so
they're
just
looking,
they,
I
think,
they're
in
the
same
boat
as
all
of
us.
They
don't
wanna,
be
the
only
core
developers.
D
K
E
Yeah,
okay,
I've
added
this
to
this
branch
here
that
I
basically
just
edited
this
to
like
core
development
requirements,
management
and
documentation,
and
then
we
have
like
the
development
units
and
core
development,
and
I
added
this
kind
of
training
and
onboarding
team
for
new
development
units.
So
that's
the
the
proposal
of
clarion.
E
So
so
we
can
we
have
this
here
and
and
can
discuss
that
at
the
right
point
of
time.
Right
now
we
don't
even
know
where
we
want
to
store
the
documents
and
how
the
the
how
the
requirements
engineering
should
be
working
in
which
tools
and
so
on.
So
it's
obviously
a
very
important
point
to
have
these
onboarding
and
training,
especially
if
there
are
new
developments
core
developments,
they
they
obviously
need
to
be
rolled
out
either
to
the
chains
and
and
also
to
new
developers
coming
on
board.
E
So
it's
very
valid
point
good
good.
So
this
one
here
then
we
move
on
from
here.
I
just
wanted
to
erase
this
and
say
if
you
are
thinking
that
some
critic
really
critical
units
or
people
are
missing
on
this
call,
then
please
move
that
forward,
but
I
do
agree
that
obviously
the
group
is
already
big.
So
if
we
add
another
resource
here
on
other
people
right
now,
we
might
not
get
forward
into
any
direction
so
be
kind
of
cautious
in
whom
you
would
like
to
propose.
E
E
Okay,
then
we
did
have
all
the
funding
discussions.
So
a
question
that
that
I
would
like
to
raise
here
again
is:
do
we
have
like
the
requirement
to
have
a
legal
entity
that
is
kind
of
taking
the
responsibility
for
all
the
invoices
invoicing
process
and
budgeting
or
how?
How
do
we
move
that
forward,
because
obviously,
the
tfs
or
telos
foundation,
which
is
a
legal
entity,
has
has
offered
to
do
kind
of
these
invoicing
processes?
G
Well,
this
construct
will
start
spending
money
and
paying
to
contractors
and,
and
then
question
is
who
is
paying
to
contract?
What
kind
of
organization
is
spending
this
money?
So
I
think
the
hotels
foundation
could
take
this
role.
It's
just
accounting
right,
there's,
nothing!
Nothing!
Special!
It's
just
basically
correct!
So.
I
Basically,
what
I
understood
was
the
telos
foundation
is
raising
its
hand
to
be
the
accounting
firm,
essentially
or
the
accounting
branch
for
this
group
until
such
a
time
that
perhaps
this
group
in
the
future
decides
that
it
needs
its
own
entity
to
do
its
own
thing.
But
in
the
meantime
that
would
fast
track
the
process
instead
of
instead
of
creating
a
new
entity
that
we
don't
even
need
know
what
the
purpose
will
be.
I
Yet
we
just
use
the
tile
foundation,
which
has
raised
its
hand
as
the
accounting
firm,
essentially
or
the
accounting
branch
for
this
group,
and
I
would
be
okay
with
that,
and
so
the
idea
would
be
that
the
enf,
which
is
also
an
entity,
would
would
enter
into
a
contract
in
a
way
with
with
the
telo
foundation
to
appoint
the
funds
to
them,
and
then
the
telus
foundation
would
create
a
permission
structure
that
would
encompass
the.
I
I
guess
the
voting
members
of
this
group
within
a
permission
set
on
chain,
but
they
would
effectively
be
the
one
doing
the
paperwork
really
this.
It's
the
administrative
function
of
them.
Whenever
we
decide
to
hire
a
contractor
or
we
decide
to
assign
a
contract
telos
foundation,
is
the
one
essentially
doing
the
paperwork
for
it.
A
Yeah,
that
sounds
like
it
makes
sense,
also
adding
to
the
efficiency
there
if
there
has
to
be
an
on-chain
vote
of
that,
we
have
like
a
mobile
app
that
you
know
is
already
set
up
to
do
that.
So.
I
D
I
I
I
fully
agree
that
we
are
in
a
state
right
now,
where
the
level
of
risk
that
we
should
be
taking
and-
and
I'm
not
saying
willy-nilly,
like
you
said
same
thing,
you
know
it's
not
it's
not
it's
not
taking
risk
without
mitigating
potential
issues,
but
we
should
be
airing
on
the
side
of
moving
more
rapidly
more
frequently
than
on
trying
to
get
something
perfect
from
the
outset,
eventually,
not
doing
anything,
and
I
think
that
appointing
the
funds
to
the
telos
foundation,
which
would
still
be
on
eos.
I
A
A
We
should
use
that
this
when
you
guys
start
using
it
you'll
see
how
efficient
it
is,
and
it's
actually
we
can
do
things
that
that
you
may
not
even
be
considering
right
now,
because
it
also
has
vote
based
document
amendment
and-
and
you
know,
clause
by
clause
and
so
there's
a
lot
of
there's
a
lot
of
tools
there.
So
I
I
would
just
so.
I
would
suggest
that
we
that
we
make
whatever
on-chain
group
we
need
for
for
you
and
then
we
can
never
just
download
the
app
and
it'll
be.
I
A
A
Votes
can
be
sure,
so,
there's
all
kinds
of
votes
and
just
be
very,
I
would
be
very
pleased
to
walk
anybody
here
wants
to
see
through
it,
but
yeah
you
can
set,
you
can
like
some
votes
can
be,
can
be
one
account
one
vote.
Some
votes
could
be
could
be
you
know,
based
on
on
how
many
tokens
you
have.
A
Obviously
this
would
not
be
a
standard
economic
thing,
but
it
might
be
something
where
you
know
we
decided
one
one
distribution,
yeah,
yeah
and
and
then
we
can
also
do
and
then
we
can
also
do
you
know,
there's
it's
fully
fully,
modifiable
and
and
on
a
per
ballot
basis.
So
yeah
you
do
all
that.
I
I'd
like.
I
To
get
a,
I
guess
pick
you
up
on
your
offer
of
getting
a
tour
of
the
application.
That'd
be
awesome.
Yeah.
E
A
Think
we
should
do
it
offline
sometime
where
people
can
opt
in
or
not
and
not
use
our
very
rare.
You
know
precious
time
here
to
do
that.
A
G
I
use
it
actually
recently,
and
I
mean
it's
not
so
much
difficult
as
soon
as
we
have
a
subject
to
autumn
setting
up
voting
a
ballot
and
start
watching.
It
is
not
a
big
deal,
yeah,
okay,
so
we
just
need
to
yeah.
We
need
to
concentrate
on
on
essence
on
the
subject.
Actually,
what
we
are
deciding
about
how
to
decide
is
is
totally
a
technical
task
that
is
yeah.
It's
solved.
I
Sorry
kirsten
just
to
go
back,
there
was
no,
we
didn't
take
a
vote
on
whether
or
not
the
others
agreed
that
essentially
telos
foundation,
be
the
accountant
responsible.
Is
there
anybody
who
objects
to
this?
We
don't
have
a
voting
mechanism
right
now,
but
those
on
the
call
is
there.
Anybody
who
objects
to
that.
I
G
I
G
I
I
A
I
I'm
pretty
sure
your
your
reputation
is
worth
more
than
250
000.
So
that's
not
a
concern
of
mine.
I
Account
is
there
I'm
going
back
going
back
to
what
you
said
doug
earlier
like
breaking
this
in
550
000.
It
just
makes
no
sense.
It's
we
move
it
along
forward
faster.
It
also
shows
commitment
and
it's
just
more
efficient.
Okay,
you
don't
have
to
convince
me.
I
was
just.
I
was
just
trying
to
remove
a
possible
objection.
E
Okay,
we
got
this,
then
the
our
favorite
topic,
and
I
I
basically
we
decided
like
we're
gonna.
E
D
G
E
It
so
we
we
just
basically,
we
decided
last
week
that
we
we
would
go
forward
in
having
a
professional
agency
coming
on
board,
to
bring
up
three
proposals
for
names,
because
basically
everybody
that
mandela
or
most
of
the
people
agreed
that.
E
Yeah,
that's
good
start
anyway.
So
basically
we
agreed
mandel
would
not
be
the
right
name.
Then,
following
telegram
there
were
notes
like
yeah.
We
shouldn't
do
that,
but
I
have
an
idea
and
another
one
came
up
and
said:
oh
you
know
it's
so
much
effort.
I
would
rather
still
use
mandel
and
others
said
well.
We
want
to
use
my
proper
marketing
agency
to
do
this
for
now.
So
really,
what
is
the
decision?
Now?
E
We
wanted
to
discuss
this
meeting
if
anybody
else
would
also
like
to
have
that
task,
so
so
we
could
decide
who
would
actually
do
it
or
or
do
we
have
any
kind
of
other
agreement
because
I'm
now
lost
because
while
we
discussed
that
we
would
be,
we
would
be
having
an
agency
doing
that.
The
telegram
chat
told
a
different
language.
So
can
we
agree
on
how
to
go
forward
now,
so
anybody
that
objects
to
use
not
to
use
mandel.
G
I
would
suggest
that
we
I
mean
we
develop
mandel
as
useful
distribution
as
a
branch
of
usio.
At
some
point
in
time
we
we
come
to
the
to
good,
naming
and
rebrand
use.
Io
mandel
could
actually
stay
as
a
branch
of
of
usio,
whatever
it
will
be
called
in
in
the
future.
Then
we
are,
I
mean
it.
Then
it
doesn't
block
us
from
from
moving
forward
and
clarion
team
can
start
developing
under
mandel
name
as
name
right.
The
core
software
could
be
rebranded
later.
A
A
Work
right,
my
experience
is
that
that
even
bad
names
tend
to
stick
and
the
more
you
use
them,
and
that's
often
why
people
pick
code
names
that
just
have
no
chance
of
ever.
You
know
being
done
at
at
good
block.
We
used
jrr
token
names
right,
so
there's
no
way
we
were
going
to
call
you
know
something
bomber,
that's
so
we
didn't
get
fall
in
love
with
this
effort
with
the
name.
A
I
think
that
mandel
thing
personally
I
I
just
think
it's
unusable
for
a
lot
of
reasons,
and
but
I
think,
as
more
people
hear
about
it,
the
more
the
more
ingrained
it
becomes
and
that's
always
a
danger,
and
I
think
if
you
just
call
it
like
something
like,
like
you
know,
white,
you
know
gray.
What
is
something
that
something
that's
innocuous
and
no
one
would
ever
think
would
be
the
the
you
know
the
name,
then
it
it.
A
It
leaves
it
open
for
for
a
proper
name
to
come
in
later
without
without
people
going
yeah,
but
I
kind
of
got
used
to
hearing
mandel.
You
know,
that's
my
opinion,
I'll
leave
it
at.
I
Circles
yeah
for
now
three
calls
in
a
row.
We
we
did
decide
on
a
way
forward.
The
way
forward-
and
I
don't
want
to
rehash
this
again-
is
that
justin
took
on
the
responsibility
of
going
to
branding
agencies
and,
if
other
people
want
to
help
him
out
or
if
other
people
want
to
suggest
other
branding
agencies
feel
free,
but
he's
going
to
go
to
branding
agencies
and
in
roughly
two
months,
get
back
to
this
group
with
proposals
and
it
will
not
be
mandel.
Mandel
is
not
the
name.
I
I
We
will
have
a
recommendation
from
justin
based
off
of
professionals,
alongside
logos,
alongside
perhaps
the
domains
being
already
secured,
alongside
with
that
name
or
with
those
proposed
names,
and
then
this
group,
and
or
whatever
this
group
ends
up
becoming
in
two
months,
and
what
that
process
looks
like
in
two
months
would
then
vote
on
one
of
those
proposals
as
to
what
eos
io
will
become
in
the
future.
It
will
not
be
mandel.
A
I
If,
if
mandela
is
a
placeholder
name
for
business,
needs
for
business
need
purposes
for
eos
the
chain
itself,
that
the
network
that
runs
the
eos
token,
and
so
in
the
media
and
in
general
for
now
like
in
the
ethereum,
it's
they
just
did
the
so
it
does
not
change
the
underlying
code.
The
fork
of
the
code
itself
that
now
is
remains
the
same
as
it
is
with
eosio
everywhere.
So
it
addresses
the
concerns
that
aaron
brought
up
last
week,
but
the
name
that
we
publish
in,
for
example,
coindesk
cointelegraph.
I
I
Doug
as
well,
though,
that
the
longer
we
do
this,
the
more
ingrained
that
name
becomes,
which
is
why
part
of
the
exercise
last
week
was
to
also
determine
a
time
frame
that
justin
would
come
back
to
the
group
and
that
time
frame
that
was
deemed
adequate
was
the
end
of
march,
so
roughly
two
earlier
if
possible.
But
that
seemed
to
be
a
an
appropriate
time
frame
for
him
to
come
back.
A
E
E
Yeah,
do
this
great
so
that
that
means
that,
as
we
did
this,
we
may
give
the
agency
the
name
chain
base
as
kind
of
proposal.
But
it's
not
going
to
be
the.
A
Yeah,
I
think
it
does
seem
like
we're
revisiting
issues
that
that
that
have
been
solved
enough.
We
have
to
get
our
own
as
a
group
we
have
to.
We
have
to
set
up
our
own
ability
just
to
know
when
to
stop
like
to
note
like
to
me.
It
seems
like
everything's
stan
handled,
and
we
don't
need
to
talk
about
this
for
another
couple
months
and
you
know
maybe
until
justin
comes
back
with
something
you
know.
A
I
Also
need
to
be
comfortable
that
whatever
justin
is
working
on
the
rest
of
the
group
probably
will
not
be
privy
to
the
proposed.
He
might,
you
know,
go
through
10
or
15
names
before
he
actually
proposes
in
two
months.
We
cannot
bring
them
up
because
they're
considerations
for
asic
securing
assets
we.
This
is
not
something
that
we
should
be
talking
on.
A
public
call
ongoing
until
there's
something
concrete
to
present
where
assets
have
been
secured
and
there's
a
vision
behind
them.
E
At
the
very
point,
absolute
valid
point
that
shouldn't
have
been
on
this
board,
so
so
my
excuse
for
that,
so
we
we
have
this
decision
now.
So
it's
not
gonna,
be
that
name
anyway,
good
that
I
mentioned
the
other
name
in
the
call.
So
it's
not
gonna
be
evaluated
anyway.
So
then,
just
just
to
to
because
I
don't
wanna
have
like
bad
feelings
and
say
wow
well,
telus
is
doing
all
the
inverses.
E
We're
thinking
about
using
telos,
decide
voter
for
voting
and
now
justin
is
is
being
tasked
to
define
the
name
so
eosnf
obviously
opted
out
from
this
naming
process
is
any
other
chain.
Does
any
other
chain
want
to
take
up
the
task
in
finding
the
name,
because
I
don't
want
to
have
like
in
two
meetings.
Anybody
come
back
and
say
hey.
This
is
too
much
tell
us
here.
I
I
don't
want
this,
so
so
I'm
asking
this
question
explicitly,
because
I
want
to
assure
that
everybody's
really
fine
with
that
decision.
N
No,
I
appreciate
that
justin's
doing
it,
but
I
I
mean
that's
awesome
so,
but
I
don't
object
at
all.
E
Okay,
then
then
this
is
fine,
then
we
will
move
on
doing
this.
E
Okay,
so
with
all
the
other
tasks,
obviously
that
are
related
to
this,
like
social
urls,
logo,
development
and
anything-
that's
obviously
related
to
this
one.
So
we
did
have
the
discussion
last
week
about
the
effort
in
re,
doing
the
name,
changes
on
the
github
repositories
and
sorry,
I
don't
recall
who
wanted
who
took
the
task
to
to
check
with
the
with
the
programmers.
If
there
is
a
possible
script
that
can
really
make
this
far
easier.
Do
we
have
any
kind
of
update
on
this.
I
E
Excellent
okay,
so
then,
at
that
point
we
can
talk
about
all
those
things
same
about
content
creation.
I
did
create
a
branch
here
for
all
the
tasks
that
are
relying
on
that,
but
this
can
obviously
only
start
the
moment
that
we
do
have
that
name.
The
question
I
have
now
is:
if
we
are,
if
mandel
is
being
used
here,
are
we
doing
anything
to
to
kind
of
start
migrate,
content
from
the
existing
ersio
or
or
mandel
sites?
If
existing
start
or
do
we,
we
have
a
name
and
start?
A
Well,
is
it
that's,
that
is
a
post-chain
name,
that's
definitely
not
gonna
be
used,
and
so
I
I
it
seems
like
that's,
not
really
the
business
of
this
committee,
because
this
is
this-
is
based
around
developing
the
eosio
pro
recall.
So
that
would
be
a
decision
that
that
eos
would
make
right.
You
don't
care
what
I
think
about
what
you
know
or
or
rami,
or
anybody
else.
That's
decision
for
them.
E
It
seems
to
me
we
we
still
probably
need
a
website
or
all
those
social.
Well,
you
obviously
we
don't
need,
I
know
so,
but
like
a
website
or
content
being
generated
this
new
entity,
let's
get
this.
I
I
think
the
idea
is,
for
example,
rami
is,
is
the
one
recording
the
call
and
he
did
last
week
and
he
shared
on
his
socials,
and
then
we
can
all
you
know
either
retweet
or
reshare
from
our
individual
socials
and
once
in
the
future,
that
becomes
more
formalized
that
all
right
we're
getting
on
these
calls
more
frequently.
There
is
an
entity
forming
there's
a
process.
There
are
things
being
discussed
that
are
worthwhile,
that's
that
in
the
future.
E
Okay,
so
we
just
leave
the
branch
for
now
and
have
it
as
a
that's
all
right.
Then
we
have
three
streams
over
here
that
we
didn't
discuss
last
time
so
so
I
think
it
would
make
sense
to
move
from
top
to
bottom,
so
I
took
took
from
the
from
the
various
chats
and
discussions
that
we
still
have
the,
as
is
analyst
analysis
and
deviation
analysis
for
eosio2021
to
the
chains.
That's
open.
I
recall
that
rami.
You
mentioned
that
this
is
in
progress
for
ultra,
because
obviously
no
longer
open
sourced.
E
Okay
for
the
other
chains,
because
I
don't
have
access
to
those
documents
right
now,
is
there
any
kind
of
do
you
already
have
these
kind
of
analysis
done
and
if
so,
could
you
forward
those
to
me.
N
Yeah
for
fia,
we
don't
have
this
and
I
started
it's
going
to
be
out
on
github
like
to
help
kirsten.
Thank
you,
but
it's
still,
it's
still
just
kind
of
a
framework
right
now,
I'm
trying
to
get
some
time
for
my
developers
to
really
flesh
it
out
at
a
code
level.
I
think,
would
be
the
most
helpful.
E
Would
you
be
kind
enough
to
him
to
if.
I
I
In
order
to
do
the
third
party
analysis
of
what
is
being
proposed
by
clarion
team
to
see
whether
or
not
there
are
gaps
and
how
or
that
he's
involved
in
which
I
believe
wags,
proton
and
theo,
if
I'm
not
mistaken
or
something
of
the
store
and
so
stan
himself,
is
going
to
literally
be
doing
the
work
yeah
of
doing
so
less
relevant
for
sam
to
send
it
himself
essentially
exactly.
I
And
I
might
screw
this
up,
but
2.1
will
become
2.3
and
2.0
becomes
3.0
and
he's
going
to
be
doing.
The
third
party
audit
revision,
slash
gap,
analysis
with
the
change
that
he's
involved.
I
Somebody's
maybe
correct
me,
I
believe
it
was
wax
telos,
theo
and
proton,
but
I'm
I'm
not
certain
on
that.
So
maybe
somebody
can
can
correct
if
that's
not
the
case.
I
That
function,
but
yes,
there
would
be
no
gap.
Analysis
in
that
sense
and
the
one
thing
that
essentially
could
have
potentially
created
more
issues
was
contract
pays,
but
it
was
announced
last
week.
I
believe
that
contract
pays
will
likely
not
find
itself
in
that
release,
because
there
are
vulnerabilities
that
were
found
with
no
remediation.
L
I
The
in
2.0
2.1.
I
The
one
that
we're
really
missing
is
is
ultra
the
harder
change
so
much.
We
don't
have
the
information
and
no
so
he
that
review.
E
So
then,
last
time
that
there
are
this
documentation
and
requirements
and
so
on
so
is
there
any
all
of
those
docu
we
stored
centrally?
E
I'm
sorry
which
documents
are
we
talking
about
right
now,
it's
like
like
requirements,
documents
or
sculpt
documents,
that's
being
worked
on.
E
We,
it's
probably
different,
a
different
type,
maybe.
I
Ramy
was
talking
about
the
working
groups
like
api
plus,
which
I'm
not
sure
would
be
relevant
for
this.
Unless
ramy,
do
you
recall.
D
E
Perhaps
yeah
question
I
haven't,
I
can't
tell
you
so
just
picked
this
up
last
time,
so
the
kind
of
documentation
that
would
be
required
so,
like
these
gap
analysis
as
an
example.
Where
would
we
put
those
do
we
have
any
central
storage
or
a
server
that
we
can
utilize
to
put
those
documents
on
that
everybody's
gonna.
I
I
Right
now,
as
I
said,
the
the
fork
or
the
someone's
it's
a
clone
of
the
eos
io
repository
that
was
under
block
one's
repo,
has
been
cloned
or
moved
over
under
enf's
repo
again
temporarily.
Until
this
group,
I
guess,
comes
up
with
an
entity
or
name,
and
then
that
would
again
be
cloned
over
reported
over
whatever
that
one
would
be
okay
other
than
the
github
repo.
I
don't
know
what
other
documentation
there
is
or
needs
to
be
at
this
particular
time.
E
Okay,
good
so
for
the
other
chains
that
we
have
on
the
list,
because
we
have
all
of
those
years.
Obviously
we
don't
have
to
do
this.
How
what
about
war,
eva
ux
in
regard
of
the
gap
analysis.
I
So
orr
was
on
this
call
earlier
they
did
drop,
but
I
think
deck
was
on
early
on.
So
maybe
we
can
make
a
note
to
confirm
with
deck
whether
or
not
there's
something
to
do
there
and
eva
is
in
the
channel.
But
eva
is
a
is
a
application
that
runs
their
own
chain.
So
perhaps
we
can
also
reach
out
to
them
in
the
group,
but
I.
O
Yeah
I
I
do
have
like
a
few
the
list
of
all
of
our
changes.
I
can
just
forward
that
to
christine
and
it's
it's
quite
quite
simple.
It's
only
like
three
or
four
things
and
kirsten
that's
for.
I
E
Okay,
so
yeah
don't
have
to
forward
anything
because
it's
it's
existing
code
anyway.
Okay,
so
then,
we've
got
this
any
any
further
comments
on
this
yeah.
I
Well,
just
in
general,
because
we're
opening
it
up-
let's
say
we
we're
putting
eva,
for
example,
on
this
list.
If
eva
makes
it
on
this
list,
then
I
think
the
list
grows
significantly.
There
are
other
a
lot
of
other
applications
that
are
in
the
same
boat.
I
So
just
that
is
a
discussion
that
we'll
need
to
have
at
some
point
is,
is
who
can?
Who
is
even
on
the
list?
Because
if
we
add
eva
we're
clearly
missing
a
lot
more,
maybe.
E
A
A
Were
talking
about
right,
if
something
we
make
decisions,
we
move
on
with
them.
If
we
don't
necessarily
feel
like,
we
have
to
waste
a
lot
of
time,
anticipating
every
possible
problem,
we
just
accept
as
a
methodology
that
there
may
be
problems
in
the
future
and
when
they
arise,
then
we
deal
with
them
and
I
think,
if
that's
the
methodology
we're
going
to
follow,
then
let's
just
stick
with
them
being
on
the
list
and
if,
in
the
future
somebody
has
a
problem
with
it,
we
can
say
yeah.
We
can
okay,
great,
that's
a
good
question.
A
E
Okay,
great
so
then,
the
last
branches
that
we
had
here,
obviously
core
development
requirements,
management
and
documentation.
E
Oh,
if
a
point
where
we,
this
is
we'll
obviously
start
to
experience
from
those,
because
we
need
to
move
on
to
align
the
the
version.
So
so
it's
supporting
everybody
in
the
same
way.
As
far
as
I
understood,
that's,
not
correct,
then
we
need
to
define
tools
and
ownership.
So
if
we
are
going
into
a
requirements
pro,
where
do
we
want
to
host
all
this
information?
E
So
we
could
obviously
have
a
join
github
setup,
which
is
good
for
programmers,
but
in
some
cases
it's
not
so
transparent
for
any
other
type
of
person
that
might
be
interested
in
what
we're
doing
a
jira
conference
setup
that
could
be
linked
to
github,
which
is
what
we're
just
building
so
question
is
jira
is
obviously
a
professional
tool,
so
who's
going
to
manage
this
and
all
we
could
have
set
up
like
we
did,
would
do
this
now
or
like
trello.
Or
what
have
you
so
question
is?
E
Is
here
best
practice
pains
which
tools
you
are
using?
Obviously,
everybody
uses
github.
So
that's
fine,
but
for
the
other
tools
like
requirements,
management
which
tools
are,
would
you
proposal
a
proposal
prefer
to
start
this.
E
Okay,
so.
I
I
E
Well,
it
could
be,
it
could
be
both.
Obviously
it's
harder
to
open
up
the
jira
setup
for
the
or
the
entire
public.
That's
probably
a
trello
board
is
far
easier
to
do
that,
but
we,
my
my
main
main
question,
would
be
which
tool
do
we
want
to
use
to
efficiently
manage
the
requirements
that
this
group
is
setting
up
and
defining?
E
I
As
the
somewhat
appointed
de
facto
chair
and
secretariat
for
this
group,
I
I
would
turn
it
to
you.
What
would
you
like
to
use.
E
Well,
you
know
we
had
this
discussion
just
recently
internally
with
with
a
development
partner
that
just
didn't
want
to
use
gyro.
E
So
I
I
marks
in
that
telegram
chat,
so
I
personally
would
recommend
using
gyro
it's
a
it's
a
complex
tool,
but
it's
a
complex
software,
so
having
gyro
then
use
confluence
for
the
documentation,
part
and
link
it
to
github.
I
think
that
is
the
perfect
setup
to
to
make
this
in
a
professional
way,
and
is
it
a
free
to
use
tool?
I
E
It's
it's!
It's
not
it's
not
costing
a
fortune.
It's
just
that
this
border
of
10
is
is
reached
pretty
soon,
but
I
personally
think
using
gyro.
Would
it's
a
professional
tool
and
everybody
most
of
us
would
probably
know
how
to
work
with
it,
and
it's
gonna
enable
us
to
really
maintain
that
project
with
all
the
sub
projects
in
a
decent
way.
E
L
Poses
well,
I'm
just
gonna
leave
a
comment
that
if
there's
a
non-profit
entity
that
ever
gets
formed,
you
can
use
gear
for
free.
That's
what
we
use
for
freo
protocol.
It's
you
know.
We
have
an
unlimited
number
of
users,
essentially,
so
we're
not
limited
by
that.
We
run
our
entire
worker
proposal
system
through
jira
and
use
confluence
extensively.
So
I'd
be
happy
to
give
a
few
minute
demonstration
on
one
of
these
calls,
if
that's
helpful-
and
I
got
there's
some
videos
out
there
of
how
we
use
it
as
well.
D
I
So
is
there
anybody
who
opposes
them?
I
guess
the
proposal
of
using.
F
I
N
So
yeah,
if
that's
a
good
question,
because
the
one
thing
that
is
somewhat
difficult
with
maintaining
documentation
or
influence
piece
of
that
is,
can
you
try
and
send
those
links
out?
I
feel
like
you,
have
to
go
and
have
a
log
in,
so
it's
not
a
great
system
for
public
but
you're
right.
If
it's
just
this
group,
I
think
it's
definitely
doable
within
that.
That
framework
is
very
large.
It's
actually
somewhat
difficult
to
find
documents
on
there
as
it
would
be
within
any
huge
kind
of
repository,
but
it's
manageable.
I
do.
I
N
I
K
E
H
I
Again,
is
it's
a
placeholder
simply
for
efficiency
purpose,
but
I
would
imagine
that
this
group
will
create
one
or
or
the
current
one
will
be
ported
over
to
the
ultimate
one
whenever
that
comes
about
that'll,
probably
yes,
there's
the
current
the
there's,
the
current
enf
one,
which
was
created
just
for
this
purpose.
Literally,
that's
the
only
thing.
That's
in
it.
F
Yeah
and
the
github
itself
will
probably
need
to
be
a
part
of
the
branding
process
where
assets
are
like
domains
are
collected.
The
github
username
will
probably
also
need
to
be
part
of
that
equation,
and
github
does
also
have
free
for
not
for
profit.
If
that's
the
direction.
This
goes,
I
mean
we
have
plus
two
two
services
that
can
be
at
massive
discounts
at
this
point.
If
that
was
the
organizational
structure.
I
And
on
that,
on
that
front,
the
enf
is
a
non-for-profit,
and
so
should
this
group
determine
that
setting
up
a
not-for-profit
would
be
the
way
to
go.
The
enf
can
also
essentially
help
coordinate
that,
if
but
not
opposed
to
anybody
else
doing
it
just
think
that
that's
something
we
can
help
with
as
well.
E
I
Gonna
be
this:
I
don't
envision
that
in
the
future.
No,
so
right
now
as
a
placeholder,
the
enf
owns
the
repo
but
the
highest.
The
min
rights
are
given
to
clarion
team
because
they're
the
ones
doing
the
actual
work
in
the
future.
I
would
imagine
that
whatever
name
this
group
takes
on
and
whatever
eosio
turns
into,
there
would
be
a
governance
structure
around
that,
and
that
would
be
you
know
that
would
follow
along
who
can
who
owns
the
github
repo
and
what
that's
called
and,
if
there's
a
permission,
set
et
cetera,
et
cetera.
I
So
right
now,
it's
basically
a
again
just
a
placeholder
so
that
we
can
try
not
to
read
the
chat
just
a
placeholder,
so
that
so
that
we
have
something
in
place
as
we
are
doing,
the
the
current
fork.
Essentially
yeah.
E
Well,
we
we
had
the
same
kind
of
discussions
earlier,
because
you
know
we
have
to
do
a
new
blog
explorer.
Unfortunately,
and
somebody
put
that
name
into
that
chat-
that
was
kind
kind
of
interesting
reaction
so
anyway,
so
we
have
this.
So
if
that's
the
case,
is
there
any
object,
because
we
also
need
an
owner
for
the
gyro
and
confluence
setup
is?
Is
that
a
possibility?
Because
I'm
also
looking
at
this
training
and
onboarding
team
on
on
side
of
clarion?
E
Can
they
also
take
the
ownership
of
the
gyro
and
all
the
setups?
For
this.
F
F
I
Could
it
be,
could
it
be
that
kirsten
is
the
one
that
owns
it
for
now,
seeing
as
he's
the
one
that's
going
to
be
inputting
information
at
the
in
the
beginning,
anyways.
I
F
That
I
potentially
can
offer
someone
in
the
future.
I
have
somebody
starting
in
about
two
weeks
that
is
very
fluent
in
jira
operations,
but
that's.
I
Not
now,
and
as
I
mentioned,
a
few
calls
back
as
well-
I
should
be
finding
out
this
friday
so
tomorrow,
ideally
whether
or
not
the
person
that
I
that
the
enf
is
hiring
to
essentially
manage
all
of
our
working
groups,
including
this
one,
whether
or
not
they'd
be
joining.
And
if
that's
the
case,
then
that's
a
resource
that
we'd
be
willing
to
share
with
this
group,
obviously,
and
and
that
person
could
also
you
know,
take
care
of
that
and
it's
somebody
that
you
all
know
or
that,
I'm
pretty
sure
you
all
know.
I
Organization,
yeah
just
placeholders,
and
we
can
even
mark
it
as
such.
We
can
even
I
agree
with
what
ramy
had
said
before,
like
if
we
have
the
at
the
front
and
center
that
all
of
this
is
temporary,
but
we
need
to
do
something.
Otherwise
we
do
nothing
and
we
just
keep
that
in
the
back
of
our
mind
and
it's
front
and
center.
I
E
Okay,
so
I
erased
the
question
anyway
in
in
the
chat,
because,
if,
if
they
own
the
github
right
now,
then-
and
and
they
set
up
the
gyro
they
because
the
enf
owns
the
github
just
to.
I
H
I
I
E
Yes
and
I
I'll
be
happy
to
set
up
the
basics
and
based
on
that,
but
you
need
to
set
up
like
web
hooks
between
between
github
and
con
jira
and
confluence,
and
you
need
to
put
in
some
automation
rules
so,
like
issues
are
synchronized
back
and
forth
between
github.
So
if
you
enter
a
new
issue
in
gyra,
it
will
automatically
be
populated
in
github
and
vice
versa.
So
we
can
set
this
up
and
then
we
have
those
both
too
closely
connected.
E
So
we
anything
that
we
do
in
gyro
or
github
is
gonna,
be
replicated,
and
then
it's
accessible
to
everybody.
So
this
is
probably
why
programmers
don't
like
it,
because
somebody
puts
in
a
gyro
ticket
they
end
up
with
having
an
issue
in
in
github
that
they
need
to
work
with,
but.
I
F
Not
opposed,
but
do
have
a
technical
concern
with
how
those
integrations
work
and
the
future
of
the
repository
is
the
enf
going
to
want
to
maintain
that
repository
moving
forward
or
a
instance
of
it,
because
if
we
integrate
jira
and
github
together,
for
example,
it's
going
to
start
generating
a
lot
of
contextual
content
between
those
two
things
and
as
this
organization
as
the
eos
io
work
group.
If
it
turns
into
an
organization
that
then
takes
you'd,
have
to
translate.
K
H
F
I
F
I
Yeah,
so
I've
got
I've
got
a
proposal
so,
and
I
just
need
clarification
on
one
point:
whether
or
not
it's
even
possible.
So
when
you
transfer
ownership,
can
you
also
rename
of
a
github
repo?
Yes,.
I
Create
a
new
jira
that
would
be
owned
by
the
enf
in
partnership
with
kirsten
who'll,
be
helping
out
in
the
future.
Whatever
this
becomes
all
right,
when,
when
we
finally
settle
on
horse,
then
the
github
repo
will
be
renamed
the
horse,
the
jira
everything
we
won't
lose.
All
of
that
connection
that
will
have
built
built
over
months
at
that
time.
I
F
E
E
So
would
you
would
you
envision
that
we
need
to
have
like
a
transparency
layer
that
everybody
could
at
any
time
have
access
to
this?
To
these
like
gyro
requirements,
I
mean,
if
we
synchronize
them
to
the
github,
then
they
would
be
kind
of
available,
because
then
every
ticket
that
is
being
raised
in
confluence
or
in
indira
sorry
will
be
automatically
synchronized
to
github.
So
so
then
the
community
could
look
into
that.
Who
else
would
look
at
code
as
if
not
a
programmer,
so
a
question?
I
Alternatively,
as
well,
because
we're
recording
these
calls
and
posting
these
calls,
we
would
be
talking
about
whatever
we
did
do
in
jira
or
consulates
against.
It
would
be
mirrored
in
github.
I'm
not
sure,
that's
so
much
of
an
issue,
but
also
don't
see
it's
not
that
there's
an
issue
to
making
it
public
it
can
be
public
is
that
function
even
available
is
more
so.
My
question.
F
I
And
realistically,
very
few
people
will
go
and
check
it
like
it's
somewhat
irrelevant,
but
so
I
don't
think
there's
a
privacy
issue
as
much
as
whether
or
not
the
function's
available
and
then
either
way.
These
are.
These
calls
are
recorded,
made
public.
The
work
is
going
to
be
public
anyways.
I'm
I'm
not
even
convinced
that
there's
going
to
be
anything
in
there
for
for
a
period
of
time,
regardless.
E
Yeah,
okay,
excellent:
I
I
will
research
this
everyone
access
and
and
give
that
information
into
the
into
the
room
next
time.
So
so
we
have
this.
I
totally
agree.
I
haven't
looked
at
the
post
from
romney.
I
don't
know
how
many
people
actually
looked
at
the
video.
E
There
is
a
decent
interest,
then,
so
that's
that's
good,
so
I
will
research
this
okay.
Thank.
K
You
kirsten
for
the
github
integration
into
jira,
that's
totally
out
of
my
wheelhouse,
and
I
can't
really
make
a
commitment
for
the
clarion
team.
So
if
I
added
you
to
the
same
admin
level
as
like
todd
fleming,
for
example,
would
you
be
able
to
set
up
all
of
the
web
hooks
and
things
like
that.
E
Yeah,
I
should
be
able
to
do
that
and
if,
if,
if
I'm
not
not
in
that
position,
I
know
somebody
who
can
help
us
with
this.
Okay.
E
Good,
so
I
would
propose
to
have
the
assignment
of
development
units
and
core
development
moved
to
the
next
meeting,
because
it's
already
30
minutes
to
to
10
and
on
my
watch,
so
I
would
propose
to
move
this
to
the
next
meeting
for
discussion.
I
also
think
that
this
is
like
a
bigger
topic
that
that
will
take
some
time
to
discuss
same
is
for
like
voting
on
new
requirements
as
well
as
budget
and
cost
sharing.
So
these
three
topics
I
would
like
to
move
to
the
next
meeting.
E
So
same
applies
for
blue
paper,
which
is
obviously
also
related
to
requirements
in
general.
So
I
would
move
that
to
the
next
meeting.
E
Is
there
anything
from
anybody
here
that
needs
to
be
covered
for
today
or
should
be
covered
in
the
next
meeting?.
I
I
think
if
you,
if
you
could
like
randomly
suggested,
perhaps
share
an
agenda
of
the
meeting
prior
to
the
meeting,
maybe
two
or
three
days
before
we
already
have
most
of
the
items
that
you
just
laid
out.
That
would
be
great.
Otherwise
I
just
really
want
to
thank
you
for
leading
this
meegan
very,
very,
very
well
organized
the
my
report
that
you
have
so
that
we
can
follow
along
is
is
great,
so
just
a
big
thank
you
from
from
me,
anyways.
E
I
agree
thanks
great,
thank
you
so
much.
Then
then
I
will
post
the
pdf
of
this,
the
mirrorboard
back
to
the
telegram
chat.
So
everybody
has
that
next
to
the
to
the
video
that
that
is,
gonna
be
published,
and
I
will
issue
the
mural
link
to
everybody
on
the
invite
so
feel
free
to
forward
that
that
email
to
anybody
that
is
from
europe
perspective,
should
have
this
link
and
should
have
access
to
the
mirror
board.
So
I
will
forward
this
latest
tomorrow
morning.