►
From YouTube: CA/VCA Working Group Meeting
Description
Topics Included: DeWork, Github and Consenz, and integration of the communications tools.
A
A
Is
that
whichever
working
group
each
working
group
below,
if
you
once
you
go
to
role
selection,
if
you
haven't
gone
to
role
selection,
excuse
me,
you
won't
see
the
working
groups,
but
the
working
groups
below.
A
I
guess,
I'm
up
for
debate
to
see
how
how
the
community
would
like
for
them
to
be
moderated
with
so
many
working
groups.
There
should
be
somebody
who
can
actually
that
has
privileges
for
privileges,
to
change
the
channels
or
create
channels
as
needed,
delete
channels
as
they
or
archive
them,
as
they
go
as
they're
no
longer
used.
So
that's
one
question
to
the
community
to
this
group.
A
The
other
question
is:
are
there?
Are
there
any
channels
for
those
people
have
been
here?
Are
there
any
channels
that
are
missing
that
you
would
like
to
see
that
would
help
the
flow
of
information
and
help
yeah
or
with
the
organization
of
it?
What
I
don't
want,
those
like
for
every
and
it
would
make
it
what
I
don't
want,
I'm
sure
nobody
else
wants.
I
mean
it's,
not
my
server's
community
server,
I'm
trying
to
make
it
efficient,
but
what
I
I
wouldn't
want
to
see
is
like
channels
for
each
issue
that
there
is.
A
A
C
A
Right,
I
think
they're,
if
I'm
not
mistaken,
like
I
haven't
used
threads
a
whole
lot.
I
think
it's
24
hours
of
inactivity.
I
think
it.
B
So
maybe
maybe
for
the
benefit
of
the
recording
and
people
who
will
watch
it
later.
We
can
just
frame
a
little
bit,
because
this
is
a
continuation
of
the
discussion
that
we've
been
having
and
a
working
group
that
is
forming
around
creating
communications,
streamlining
and
project
workflow
that
integrates
together
so
that
all
of
us
who
are
working
on
different
things
related
to
this
ca.
B
Community
advisor
group
have
a
way
to
to
talk
and
to
discuss
and
to
maybe
even
hold
unsync
kind
of
conversations,
but
that
those
solutions
and
ideas
are
collected
and
moved
forward
in
a
way
that
helps
us
to
solve,
solve
issues
and
challenges
and
also
create
new
things
that
will
help
the
community
moving
forward.
B
And
ultimately,
the
goal
is
that
we
also
build
a
github
repository
that
could
actually
manage
the
workflow
and
that
we
onboard
different
tools
that
all
work
together
so
that
there's
a
syncing
and
a
sort
of
centralization,
which
is
always
a
tough
word
in
catalyst,
but
a
centralization
of
the
information
and
progress
for
us
to
be
able
to
work.
So
as
so.
B
This
is
like
the
first
actual
meeting
that
we've
held
in
in
the
hub
and
we're
just
trying
it
out
and-
and
today
hopefully,
we
can
look
at
some
of
the
different,
the
different
tools
that
are
being
tested
and
considered,
and
certainly
everyone
on
this
call
will
be
have
a
lot
of
insight,
because
each
of
you
is
either
probably
use
these
or
has
familiarity
with
them
and
we're
trying
to
create
something.
B
Then
that
also
will
let
us
develop
the
repository
with
some
governance
framework
so
that
we
are
there's
a
there's,
a
respect
for
the
community
having
it's
the
community
legitimizing
what's
being
created,
and
so
that
there's
a
lot
of
input
on
making
sure
that
we
do
this
in
a
way
that
is
allows
us
to
be
as
decentralized
and
transparent.
B
As
possible
and
then
ultimately,
the
hope
is
from
the
building
of
these
of
these
different
workspaces
that,
as
groups
form
to
work
on
things,
they
will
have
a
little
bit
of
a
circle
format
with
someone
who's
championing
that
group
so
scott's.
A
good
example
of
that
with
this
group
and
that
those
discussions
can
happen
and
take
place.
B
B
There
is
an
archiving
aspect
so
that
we
are
able
to
look
back
and
see
how
things
were
addressed
or
why
we
made
a
decision
or
didn't
make
it
so
that
we
avoid
this
whole
groundhog
day
kind
of
perpetual
discussing
of
issues
that,
and
also
specifically
for
for
new
people
coming
in
as
well,
because
the
people
who
come
in
we
start
to
notice
the
same
problems
within
the
ecosystem,
and
there
should
be
a
sense
of
that.
B
Those
things
have
been
identified
and
addressed,
and
if
they
haven't
that
that
person
then
could
take
on
a
little
bit
of
ownership
and
start
to
start
to
find
a
way
to
contribute
meaningfully.
So
that's
maybe
the
framing
here.
I
know
it's
a
special
benefit
that
we
have
aaron
here
today
to
talk
to
us
about
consents.
B
So
we
want
to
take
a
little
bit
of
a
look
at
that
as
an
alternative
to
to
how
google
docs
are
formed,
and
that
will
probably
be
a
welcome
conversation
for
many
people
here
and
then
scott
has
done
a
lot
of
work
this
week,
understanding
d
work.
So
we're
going
to
look
at
that
tool
and
beyond
that,
it's
really
a
space
for
us
to
just
give
feedback
and
insight
for
the
for
the
development
of
something
that
can
really
serve
and
consider
everyone.
C
I
was
wondering
if
I
could
raise
just
something
as
as
a
participant
of
the
discord
servers
for
some
time
yeah
out
of
the
original
idea,
and
I
think
the
the
main
inverted
commas
discord
server
has
got
into
a
bit
of
a
mess,
because
it's
trying
to
be
too
many
things
to
too
many
people.
C
So
just
I'm
wondering
how
how
if
there's
a
thinking
on
how
we
can
maintain
that
cas,
aren't
just
congealing
in
this
server,
for
instance,
whereas
we
want
the
cross
pollination
across
groups
and
and
that
sort
of
stuff,
so
just
I'll
just
bring
that
into
the
space.
Now,
while
it's
also
forming
and
and
just
so,
you
can
think
about
that
that
that
this
was
decided
way
back.
But
it
the
mess
has
happened,
and
I
think
it's
got
value.
But
there
is
that
little
element
there
that
that
needs
to
be
considered.
Mm-Hmm.
A
I
just
want
to
say:
do
you
think?
Maybe
I
mean
we
could
I've?
A
A
You
know,
as
far
as
like
now
we're
asking
ca's
and
bca's
questions,
but
now
then
we
start
when
we
start
having
more
areas
that
are
more
proposer
specific
and
then
it
just
keeps
explaining
kind
of
like
what
you
were
saying
and
then
you're
kind
of
just
repeating
the
the
same
problems
that
happened
on
the
other.
B
A
So
what
about
what
about
integration
or
interlinking
or
like
making
you
know
just
putting
a
link
hey
if
you
want
to
speak
to
ca,
you
know
if
you
want
to
speak
to
see
a
community
go
here.
I
mean
I
I
don't
know
yeah,
I'm
definitely
open
to
any.
So.
C
I
I
guess
it
depends
on
the
purpose
of
the
server
right
like
if
it's,
if
it's
a
breakout
server
where
people
can
engage
with
ca
issues
and
reach
out
to
the
ca
representative
and
discuss
specific
ca
stuff
and
then
the
community
server
kind
of
stays
as
that
hub
of
activity
where,
where
we
try
to
focus
the
questions
and
the
the
more
general
participation,
that
kind
of
seems
like
a
possibility.
But
yeah
I
mean
each
server
is
going
to
have
its
own
life
and
its
own
way.
C
But
I
can
understand
why
this
has
been
made,
because
that
I
would
I've
stopped
participating.
Even
though
I'm
admitting
the
server
it's
it
just
got
too
too
bulky
to
keep
your
head
around
it
all
the
time
so
yeah.
I
guess
it's
just
a
point,
rather
than
a
it's
a
point
of
note
that
I'd
like
to
bring
up
in
the
early
stage
just
to
keep
in
mind
that
that
we
don't
want
to
silo
out
things.
A
Yeah
the
there
is-
and
I
know
this
might
sound
like
minimal,
but
you
know
like
each
server.
I
think
you
all
have
an
announcements
channel
on
there,
but
like
even
even
little
things
like
that
to
where
you
can
follow
another
server
with
their
announcements
and
just
kind
of
like
letting
people
know
that
there
are
other
servers
out
there
that
are
kind
of
focused
on
the
various
categories.
A
I
mean
I'm
not
running
the
entire
circle
or
catalyst,
but
I
mean
my
vision
would
be
like
each
representative
has
their
own
discord
server
and
then
all
those
discord
servers
communicate
with
you
with
each
other,
through
announcements
and
following
each
server
and
then
there's
links
and
stuff
but
yeah.
It's
it's
definitely
an
issue.
C
Yeah-
and
I
mean
we
have-
they
said-
50
000-
I
think
members
on
ideas
scale
and
then
we
have
about
170
participants
in
the
last
town
hall,
so
the
town
hall
kind
of
represents
the
current
active
body
of
people.
I
feel
right
that
that's
like
a
good
measure
of
how
many
people
are
actively
involved
with
the
community.
C
B
B
Originally,
just
the
thinking
about
this
was:
how
do
we?
How
do
we
manage
project
workflow
and
how
do
we?
How
do
we
make
sure
that
we're
we're
collecting
everything
and
having
it
in
this?
In
the
same
place?
The
communications
part
of
that
is
part
of
it,
but
I
guess
one
part
of
our
vision
was
that
the,
for
example,
let's
say
we
just
had
the
lottery
details
come
out
at
the
end,
the
ca
rewards
explanation
and
that
started
a
whole
collection
of
of
telegram
conversation.
B
This
is
where
this
is
being
talked
about,
and
here's
a
lot
of
like
backstory
and
here's
a
lot
of
thinking
so
that
someone
could
come
up
to
speed
and
so
that
we're
not
losing
any
of
the
of
that
of
that
material
and
that
if
it
would
come
to
a
place
of
needing
a
group
to
work
on
it,
things
like
yesterday's
after
town
hall
and
those
kind
of
official
discussions
could
also
live
in
in
the
same
place
like
the
repository
ultimately,
and
so
the
discussion
could
find
itself
in
in
more
of
the
same
place.
C
I
mean
I
kind
of
I
kind
of
see
this
as
being
like
the
place
for
the
cc
rep
to
sit
like
you're
you're,
currently
here
and
when's
your
terms
over
the
new
if
they
want
to
the
new
cc
rep
and
sit
in
here,
and
because
it's
hard
to
monitor
all
the
other
noise.
That's
happening
on
on
the
other
channels.
I
think
right,
like
even
this
telegram
chat,
doesn't
always
discuss
ca
issues
right.
C
It's
a
broad
discussion
about
catalyst
as
a
whole
generally
and
that's
the
most
active
point
of
general
discussion.
I
find
right,
whereas
the
proposals
can
be
a
whole
range
of
experiences
from
new
to
experienced,
but
the
cas
are
always
the
active
members.
I
find-
and
I
think
that's
kind
of
how
iog
envisioned
stuff
and
that's
why
the
ca
monica's
given
because
they're
more
than
just
the
assessors
participants
so
yeah,
I
think
it.
C
It
does
have
great
value
this
space
and
I
think
the
discussion
that
we're
previously
having
in
in
the
other
channel
for
fund
eight
improvements
would
would
be
better
suited
on
this
channel
right
right,
but
but
then
because
and
then
maybe
onboarding
whoever's
takes
on
on
boarding
in
this
channel
monitors
what's
happening
on
the
other
channel
and
says.
Look
if
you
want
to
find
more
specific
ca
discussion
head
over
to
this
server
exactly.
B
B
D
C
C
There's
no
issue
there,
but
if
everyone
just
does
that,
then
we're
going
to
have
this
massively
siloing.
So
just
encouraging
heading
out-
and
I
guess
like
that.
That
would
be
like
announcements
and
say:
look
it's
we
were
running,
we've
got
a
tool
actually
for
it.
We
didn't
launch
it
this
fund,
but
it's
a
a
proposal,
feedback
tool
right
where
it
encourages
the
community
to
actually
go
through
and
make
comments,
and
it
actually
tracks
the
comments
on
the
idea
scale
and
in
previous
two
funds.
C
We've
actually
run
that
in
conjunction
with
iog
to
because
we
weren't
there
wasn't
enough
participation
on
on
proposal.
Discussion
comment
comments,
so
that
could
be
highly
encouraged
in
this
server
for
the
active
participants
and
we
could
launch
that
tool
each
fund
and
and
this
server
could
be
responsible
for
like
let's
go,
we've
got
a
week.
Let's
and
you
know,
make
a
game
of
it
or
whatever
they
choose
to
whatever
this
group
decides
to
do.
This
would
be
the
place.
I
think.
A
A
A
I
think
you
can
pull
in
telegram
comments
as
well
in
here
yeah.
You
can.
A
C
C
I
also,
I
guess,
I'm
also
partly
here
because
of
the
fact
that
the
kadano
catalyst
with
the
dot
st
at
the
end
site
is
there
and
it's
not
being
as
updated
or
curated
by
myself
as
much
as
I'd
like
it
to
be,
and
it's
sort
of
something
that
I'd
like
to
get
a
lot
more
participation
in
even
to
the
point
where
I'm
not
doing
it,
because
I'd
like
to
do
other
things.
C
I'd
like
so
that's
part
of
the
conversation
I
was
going
to
have
with
scott
and
we
might
still
just
keep
that
form
for
monday,
but
I
did
want
to
bring
that
into
the
space
that
says
that
there
is
a
community
site
available.
It
does
have
some
funding
available
as
well.
So
it's
it's
and
I'm
working
on
various
ways
to
incentivize
participation
with
that
site
through
through
a
bounty
system.
D
C
Knowledge
about
github,
pull
requests
and
to
write
markdown
and
then
there's
some
weird
viewpress
stuff
that
you'd
have
to
get
your
head
around.
But
someone
could
show
you
and
if
you've
got
some
technical
knowledge
you
could
you
could
find
you
could
work
around
that.
But
we
are.
C
We
would
like
to
change
it
to
a
wiki
structure
and
I'd
like
to
discuss
that.
I
guess
whether
people
think
that's
a
good
idea
or
not
because
then
you
could
just
like
wikis
in
theory,
can
just
be
a
lot
easier,
updated
by
community.
But
I'm
not
sure
if
I've
hijacked
the
discussion
here
or
not.
B
A
Yeah
yeah,
I
was
going
to
mention
phil,
if
you
like,
I
mean
put
like
a
call
to
arms
to
see
who
would
be
interested
in
or
maybe
I
can
make
an
announcement
here
like
the
people
who
are
interested.
Maybe
they
can
be
like
assigned
a
particular
section
of
the
of
the
server
or
something
of
that
nature.
I
mean.
C
I
even
just
one
person,
that's
happy
to
trawl
through
it
and
has
the
skills
to
do
it.
There's
funds
to
pay
them
to
to
just
go
and
update
all
the
bits
to
cool
you
know
as
they
come
up
to
date.
Just
it's
probably
a
couple
hours
a
week
like
two
hours
a
week,
probably
just
to
keep
it
up
to
date,
but
it's
just
something
I
don't
have
time
to
do
myself.
So,
but
let's
talk
about
that
monday,
scott.
B
A
F
For
me,
it
was
great
even
just
listening
for
you,
because
the
real
real
life
issues
that
you
stumble
upon
this
is
these
are
the
problems
that
we
wish
to
provide
some
kind
of
solution.
Some
complimentary
platforms
that
can
answer
those
needs
that
the
discord
and
google
doc
and
github
does
not.
So
I
hope
you
can
er
can
integrate
into
your
work
as
well
and
just
for
for
framing
the
platform.
We
are
just
started
to
build
it.
F
We
have
been
funded
in
part
seven,
and
I
hope
that
later
this
year
we
will
launch
some
mvp
and
we
can
invite
you
to
start
using
it,
but
I
I
it
may
be
premature,
but
I
wish
to
show
you
some
very
basic
demo
just
for
you
for
you
to
know
what
we
are
working
on
for
you
not
to
work
on
parallel
or
something
something
too
similar
and
not
waste
too
much
energy,
but
also
I
I
maybe
also
because
we
have.
F
We
have
a
specific
proposal,
some
modest
budgeted
proposal
for
the
ca
challenge
and-
and
maybe
also
it's
an
opportunity
for
us
for
you
to
look
at
it
and
see
if
it
works.
You're
voting,
and
so
I
can
share
the
screen
just
start
demo.
A
F
F
I
I
assume
so
you
can
see
here
some
kind
of
dow
that
I
invent
for
this
for
this
demonstration
and
they
decided
to
to
establish
a
console,
and
I
took
some
ideas
like
from
from
the
circle
from
the
catalyst
circle
definition
document
and
put
it
here
just
for
er
for
the
example.
So
you
can
see
this
is
this
is
the
agreement
you
can
see
here
you
can
be.
It
can
be
part
of
many
many
groups,
many
dows
or
many
communities.
F
There
are
channels,
there
are
different
agreements,
different
documents
in
different
stages,
and
this
is
a
document
that
what
we,
what
we
are
seeing
now
in
this
document
in
this
draft,
are
sections
that
are
already
being
discussed
and
approved
in
in
these
pages.
What
you
see,
those
of
the
agreement
in
the
current
in
the
in
the
current
times,
like
a
snapshot
of
the
agreement
of
the
community
at
the
at
the
present
time.
Now,
if
I
will
go
for
this
section,
is
that
suggests
that
electric
member
will
serve
three
weeks
term.
A
F
Okay,
so
I
can
browse
and
to
see
first.
First
of
all,
you
can
see
the
the
comment
section.
This.
The
comment
is
a
tribute
to
the
section
itself
and
if
I
will
go
to
the
suggestion,
I
will
see
the
this
user.
This
member
suggests
to
change
weeks
from
weeks
to
month.
That's
all.
I
can
change
the
view
to
form
a
more
convenient
viewpoint
and
I
would
can
vote
as
a
first
step
and
we
encourage
voting
in
this
platform,
because
voting
is
a
way
to
express
opinion
without
creating
noise.
F
You
can
use
the
the
the
output
of
this
action
and
integrate
it
into
the
creation
of
the
algorithm
argument.
Agreement.
Excuse
me,
without
adding
more
noise
that
needed
more
eyes
on
it.
So
every
time
a
a
user
vote
for
this
bar
is
getting
larger
and
if
it
will
reach
this
point,
then
the
status
of
this
will
change
from
suggestion
into
the
current
version.
So
you
can
see
now,
let's
say
more
user
has
been
joined.
The
the
conversation
joined
the
process.
Now
I
will
and
we
add
the
last
vote,
the
last
pro
vote.
F
It
became
the
conversion
and
when
I
will
go
back
to
the
back
to
the
agreement
to
the
document,
I
will
see
that
the
weeks
has
been
changed
from
weeks
to
month.
F
So
we
will
of
course,
will
add
some
more
versions
pages,
so
you
can
track
the
different
changes
that
the
document
has
been
been
through,
but
at
any
any
point
in
time
here
you
can
see
the
activity,
the
activity
page,
you
can
vote
from
the
activity
page.
You
can
go
see
the
the
document,
the
whole
document
process
you
can
vote
from
here
as
well.
You
can
see
other
sections
and
the
main
point
is
that
we
can
we
can
discuss.
We
can
express
our
opinion.
F
Our
proposal
is
to
create
joint
drafting
guidelines
for
the
ca
it
can
be
made
together
and
create
a
library
of
agreements.
So
so
a
document
like
this,
like
this
roblox
that,
as
far
as
I
know,
you're
you're
still
using
it
is
it
relevant.
This
document.
F
You
know
so
so
imagine
a
a
document
at
least
like
this
in
some
kind
of
library
designs,
that
you
can
choose
different
agreement
according
to
different
classification
and
go
and
and
follow
the
process
of
building
this
agreement
in
very
focused
and
docume
well
documented
manner.
So
you
can
see
the
different
a
a
point
of
view
of
the
participant.
F
So
this
is
the
demo
and
again
it
I
I
I
I'm
sorry
that
I
cannot
invite
you
to
join
the
experiment
right
now,
but
I
hope
very
hopes
that
every
month
we
can
can
begin
really
testing
it
in
live
version.
C
Yeah,
that's
right
and,
and
that's
why
I've
I've
approached
like
when
aaron
first
talked
about
this
a
few
funds
ago.
It
made
so
much
sense
that
this
needs
to
exist
and
it's
going
to
add
like
as
he
develops
it,
it's
going
to
add
so
much
usability
to
the
process.
C
For
for
me,
the
the
current
user
interface,
I
think
aaron's
mentioned
as
well
that
doesn't
quite
work
for
for
usability
of
the
platform,
but
the
the
functionality
is
definitely
there
and
with
some
usability
improvements,
I
think
it
can
easily
be
usability
usable
soon.
I
think
I
hope.
F
Yeah
exactly
this
is
why
our
proposal
is
on
the
ci
challenge
is
made
to
engage
the
community
in
the
design
process,
because
this
is
the
time
now
we
are
starting
the
design.
You
see
the
very
rough
sketches,
so
we
wish
we
planned
to
do
some
co-design
sessions.
It's
a
format
that
means
from
the
social
design
academy
has
been
building
also
funded
in
farm
five.
I
think
so.
F
This
is
this
part
of
what
we
are
trying
to
do
and
and,
as
I
said,
just
listening
for
to
the
start
of
your
conversation
for
me,
it
brought
some
insight.
It
needed
to
be
integrated
into
the
design
of
the
platform
and
to
do
it
in
a
very
structured
way
can
to
make
sure
that
the
platform,
the
the
mvp
version
will
be
the
most
useful
for
for
your
for
the
ca
use
cases
and
and
for
other
parts
of
the
community.
C
I'd
also
add
in
there
that
I
I
did
some
experimentation
with
github
being
the
central
space,
but
it
I
feel
that
it
has
technological
hurdles
that,
if
you're,
if
you're
completely
it
has
two
hurdles,
one
that
you
have
to
authenticate
into
github
and
if
it's
the
only
thing
you're
using
github,
for
it
seems
heavy-handed
because
of
the
the
large.
C
It's
very
heavy
to
ask
people
to
do
pull,
requests
and
stuff
that
aren't
in
the
technological
space,
and
that's
a
platform
like
this
will
ease.
People
will
allow
engagement
a
lot
higher.
I
feel
because
it's
it's
more
wiki-esque,
let's
say
where
you're
going
in
it's
natural
to
edit
something
and
then
all
it's
doing
is
adding
a
layer
over
the
top
that
it
says
once
you've
done
your
edit
or
your
suggestion.
C
B
So
let
me
ask
like
just
like
comprehension,
questions
to
make
sure
I
have
it.
So
if
we
were
to
put
so
like,
let's
use
the
ca
assessment
guide
right
now,
that's
a
document,
that's
owned.
We
all
make
comments
on
it,
but
ultimately
you
would
have
a
group
that
looks
at
that
document,
both
from
a
document
formation
standpoint
and
from
a
governance.
Standpoint
of
we
are
agreeing
that
these
are
the
I
don't
want
to
use
like
heavy
language.
B
This
is
this
is
we
agree,
is
the
best
practice
and
we
could
all
we
could
all
contribute
to
that,
but
you
also
could
do
things
like
develop
like
create
consensus
on
like
the
from
the
circle
perspective,
you
could
do
the
decision
making
about
election
to
your
example
about
election
standards
and
have
people
come
in
and
vote
on
it
from
a
decision-making
standpoint
rather
than
a
document
creation
standpoint.
F
This
can
be
another
use
case,
and,
and
there
is
some
kind
of
flexibility
in
in
the
platform
there-
there
will
be
a
kind
of
flexibility
between
on
the
spectrum
of
decentralization,
because
this
decentralization
is
a
spectrum-
let's
admit
it:
it's
not
binary
center,
centralized
or
decentralized,
and
this
voting
mechanism
in
consensus
can
we
can
adjust
it
for
the
different
needs
of
different
communities
in
different
groups.
It
is
it's
legitimacy
for
some
group
to
decide
that
it
needed
to
be
more
professional.
F
It
needed
more
reputation
or
something
existed.
It
want
to
be
more
more
centralized
and
more
controlled,
so
they
still
can
get
the
the
the
voting
input
and
the
other
comment
from
the
community
and
different
improvement
suggestions
to
the
document,
but
still
there
is
more
influence
by
the
some
group
or
or
the
or
some
admin
in
the
voting
system,
as
long
as
it
is
completely
transparent.
I
think
this
kind
of
flexibility
is
good
for
for
the
community
and
just
to
keep
it
transparent
and
fair,
and
it
can
be
a
very
versatile
tool
for
different.
C
User
bases
right
so
the
circle
could
have
permission
to
edit
it
or
they
could
assign
permission
to
just
editors,
but
then
the
community
can
vote
on
it
or
they
can
make
a
document
that
the
community
makes
a
document.
But
only
the
circle
could
vote
on
it
like
you
can
you
can
start
to
play
with
all
sorts
of
different
mechanisms
of
assigning
levels
of
usability,
so
some
documents,
like
the
ca
document,
could
just
be
open
to
everyone,
but
maybe
in
the
future
will
have
to
be
closed
because
you
get
randoms
coming
in
from
outside.
C
You
you
eventually,
you
can
authenticate
with
a
did
and
ensure
that
someone
is
a
ca
before
they
can
edit
it
that
sort
of
stuff
right.
But
but
it's
got
this
amazing
dynamic,
not
now,
and
maybe
not
in
the
first
iteration,
but
in
future
iterations.
It
can
easily
expand
out
to
just
be
this
amazing
consensus
writing
document
with
various
inputs
and
outputs
and
and
yeah
and
a
mix
of
of
whatever
it
is,
depending
on
what
document
you're
trying
to
write
and
and
who
you
want
to
vote
on
it.
B
We
would
create
documents
related
to
certain
initiatives
and
then
they
could
be
talked
about
it.
So
I'm
just
trying
to
think
about
flow
of
information.
Maybe
we
we
all
recognize,
there's
an
issue
we
need
to.
You
know
talk
about
how
to
make
pancakes
and
then
the
conversation
comes
in
here
we
got
a
group
together,
we're
all
talking
about
how
to
make
pancakes.
Then
we
decide
we
need
to
write
the
instructions
and
the
best
way
to
make
pancakes,
and
we
go
to
consensus
to
do
that.
B
Then
we
all
vote
on
whether
or
not
that's
the
best
thing
and
simultaneously
we
have
the
github
repository
where
that
document
is
linked
to
and
anything
else
related
to.
That
also
is
in
it.
Where
is
there
a
redundancy
here
as
far
as
the
project
workflow
and
I'm
work,
I'm
looking
to
everyone
else
in
the
group
to
like
help
me
sort
of
like
work
through
how
things
are
being
set
up
so
that
we
can
get
a
sense
of
like
how
we
can.
B
I
think
this
is
a
fantastic
project.
I
personally
think
it
should
be
well
supported
and
also
you
know,
really
thinking
about
how
we
we're
trying
to
make
things
as
streamlined
as
possible,
so
how
we,
how
we
have
it
sort
of
interface.
I
don't.
A
I
don't
I
mean
I
think
it'll
work
perfect
honestly
with
the
I
haven't,
showed
it
yet,
and
I
don't
know
how
many
people
are
familiar
with
it
with
the
dwork
platform.
I
think
it'd
be
great,
because
you
can
bring
that
platform.
You
can
determine
what
are
the
pressing
issues
within
the
community,
for
instance
like
bca
requirements
that
there's
and
then
like
those
issues
can
be
can
be
brought
forward
discussed.
A
A
Issue
and
then
once
there's
some
sort
of
consensus
on
my
from
what
from
what
aaron
presented
so
once
there's
a
consensus
on
like
how
do
we
approach
it?
What
documents,
then
we
bring
that
in
to
whoever
the
champion?
Is
they
bring
that
document
that
needs
to
be
remodeled
into
aaron's
platform
into
consensus,
and
then
the
I'm
assuming
didn't
really
see,
but
there
can
be
edits
or
comments
made
on
it
and
adjustments
made
to
that
document.
A
Then
the
finalization
is
done
and
then
voted
on,
not
not
done,
but
it's
voted
on
to
determine
whether
or
not
how
much
broad
support
there
is
for
it.
A
F
Yeah
integration
with
integration
with
other
platforms
is
part
of
our
roadmap.
It
won't
be
in
the
mvp,
but
it
is
a
part
of
our
plan
and
we
think
github
it
should
be.
It
doesn't
think
that
it's
not
the
thing
that
I
thought
about
it
before
this
meeting
and
I
understand
that
some
kind
of
an
api
integration
or
or
other
a
bridge,
a
content
bridge
between
consensus
and
github
can
be
very
useful
as
well.
F
Our
main
focus
until
now
was
was
on
the
social
media
platform,
how
we
can
cultivate
discussions
that
now
are
not
structured
in
different.
This
discord,
servers
in
intel
group
and
other
platform
and
and
take
the
the
relevant
knowledge
from
there
to
the
structured
and
focus
the
discussion
and
consent.
F
We
can
do
it
manually
manually
or
at
least
for
the
minimum
viable
product
we
can
put
some
moderators
or
or
some
kind
of
investors
in
different
channels
to
identify
the
the
places
where,
where
participant
in
the
the
discussion
raise
solutions
that
can
be
then
finalized
using
constants
and
and
migrate
them
into
the
platform,
but
also
to
create
some
kind
of
automation
for
that
some
bots
or
other
tools.
That
can
be
useful
for
this
and
github.
F
I
assume
I'm
not
completely
sure
about
it,
but
I
I
assume
that
there
is
some
api
or
other
tooling
that
can
be
used
to
create
this
cross-platform's
content
management
and
then
and
then
we
we
need
to
design
and
exactly
like
nadia
asked
before,
to
avoid
redundancy
to
identify
exactly
what
what
are
the
benefits
that
gita
brings,
that
other
platform
does
not
and
then
to
be
very
focused
on
how
we
can
create
this.
A
cross-platform
content
management.
A
I
think,
and
I
think
what
phil
said
too,
I
don't
want
to
discount
what
phil
said
about
github
github
is
a
technical
challenge
for
many
people
and
that-
and
I
think
the
part
with
github
I
understand
its
capabilities.
I
probably
don't
understand
its
full
capabilities,
but
I
think
it's
a
great
place
is
to
have
like,
as
like,
a
reference
for
open
issues
and
closed
issues,
and
then
anybody
in
the
community
they
don't
have
to
be
technically
savvy
to
just
look
at
github
and
look
at
the
issues
that
are
open
or
closed
that
have
been
accomplished.
A
But
again
I
haven't
I
mean
I
love
aaron.
I
love
your
platform,
I
think
it's
great,
especially
like
the
the
voting
part
on
it.
I
think
that
probably
that
pushes
it
that
pushes
it
above
all
others
and
I,
as
far
as
what
I'm
not
working
on
the
github
side,
I'm
kind
of
working
on
the
the
integrations-
I
guess
with.
A
Obviously
my
integrations
are
with
discords,
where
discord
can
be
a
notification
and
hopefully
in
the
future,
you
can
actually
submit
issues
through
through
discord
to
the
various
platforms.
Of
course,
I
don't
know
the
the
integration
technicalities
on
that
the
scope
of
the
the
process
that
involves,
but
I
mean
yeah
if
you're
asking,
I
think
aaron's
platform
will
work
as
part
as
part
of
the
the
workflow
and
and
the
integrations
I
mean
yeah.
I
think
it's
I
think
it's
beautiful.
A
F
Because
slack
does
integrate
very,
very
beautifully
with
github
and
with
google
doc.
So
every
new
comment
comment:
when
you
pull
request,
every
new
comment
on
an
issue
is
notified.
You
can
pop
notification
in
the
slack
channel,
but
it's
slack
is
more.
It's
a
closed
system.
I
think
compared
to
discord.
So
I'm
not
sure
it's
suitable
for
this
purpose.
C
Yeah
more
of
the
community
used
discord.
I
actually
did
attempt
to
to
start
a
slack
way
back
like
a
year
and
a
bit
ago
as
well.
I
did
not
get
the
same
traction
and
then
just
decided
to
send
everyone
to
discord,
because
it
was
a
better
platform.
C
I
think
slack's
good
for
for
the
people
who
are
in
the
dev
community,
as
well
or
in
the
corporate
community,
that
that
seems
to
be
the
the
use
case
of
slack
more
than
discord,
whereas
discord
seems
to
be
based
on
gamer
community
which
are
more
loose
form
and
and
now
building
community
based
tooling,
and
I
feel
like
that's
just
where
the
communities
are
falling
at
the
moment.
B
It
would
be
interesting
for
you
as
you
develop,
but
I'm
sure
that,
because
you
have
this
because
you
have
this
great
governance
component
built
in
and
I
think
there
would
be
openness,
I'm
speaking
out
of
turn,
I
have
no
idea,
but
my
my
gut
level
is
that
it
would
be
an
interesting
thing
to
have
that
conversation
with
with
the
circle
and
stuff
circle,
because
you
know,
certainly,
if
you're
going
to
have
an
integrate.
That's
a
great
that's
a
great
use
case
to
try
and
you're
a
catalyst
project.
B
So
so
it
would
be
cool
to
see
it's
probably
it's
well
used
with
for
the
circle
like
it's
a
it's
a
everyone's
on
there
and
using
it.
So
it
would
certainly
be
something
where
it's
not
too
large
of
a
too
large
of
a
group.
It's
a
nice
size
to
test
with
and
yeah
and
there's
the
github
integration
and
the
google
docs
integration
right
now,
with
slack
in
that
group
as
well.
So
you
could.
C
I'm
sorry
I'm
going
to
have
to
jump
off
in
about
a
minute
or
two
to
get
ready
for
another
meeting
or
I'll
hang
around
just
a
little
bit
and
then
I'll
just
disappear
quietly.
I
think.
A
I'd
like
to
I
guess,
maybe
I
can
show
the
dwork
platform
and
maybe
see
see
how
that
integrates
with
with
where
erin's
would
would
fit
into
that.
I
mean,
I
know
it
fits
it's
just
seeing
the
flow
of
the
information
software
by
no
means
am
I
an
expert.
I've
just
used
this
platform
for
a
few
days
set
up
a
few
things
and
executed
a
few
tests.
B
Well,
you
pull
while
you
pull
that
up
I'll,
just
say
aaron.
I
think
you
know
this
group.
Certainly
we
can
pop
into
your
proposal
and
do
the
feedback
and
and
all
that
supportive
stuff
and
if
it
helps
to
have
us
test
drive.
I
think
that
it
seems
like
there's
consensus
among
us
that
we
might
be
a
good
might
be
a
good
like
guinea,
pig
kind
of
a
group
as
you
start
to
roll
these
features
out.
A
Yeah,
okay,
so
this
is
the
dework
platform.
It
looks
looks
very
similar
to
some
of
the
other
workboards
that
were
being
used
by
other
teams.
I
think
one
time
circle
used
trello,
so
it's
just
similar
similar
issue
tracking
discussion
review.
What
makes
it
interesting,
though,
is
there
is
there
are
integrations
with
with
github
and
discord,
and
so
any
issue
created
any
issue
created
here.
So
you
just
click
the
plus
create
your
issue.
A
And
then
obviously
put
in
your
description
here,
whatever
the
issue
is
and
over
here,
you
can
set
it
as
a
community
suggestion
to
do
in
process.
Obviously,
all
the
various
steps
involved.
You
create
your
own
custom
tags,
there's
a
bunch
of
things
you
can
do
set
due
dates,
assign
the
number
of
hours
and
if
there
is
a
reward,
not
yet
because
there's
not
a
lot
of
cardano
organizations
using
the
platform,
so
there's
no
cardano
wallet
tie-in,
but
in
the
future
you
will
be
able
to
pay
through
this.
This
actual
platform
and.
A
So
moving
from
there,
you
know
what
my
apologies,
I
didn't.
A
Y'all
are
unable
to
see
it,
but
I
will
I'll
show
my
screen
on
here.
Real
quick.
A
A
A
Obviously,
stewards
are
the
ones
that
can
actually
move
these
issues
across
the
board
to
their
various
to
the
various
stages,
and
I
mean
that's
there's
more
to
it,
but
I
don't
want
to
waste,
not
waste,
but
I
don't
want
to
take
up
more
time.
I
really
wasn't
expecting
to
give
a
complete,
thorough
presentation
on
it
today,
but
any
comments,
so
any
any
any
comments
that
are
made.
A
Anything
that
is
done
with
these
with
with
any
of
these
individual
issues
will
populate
onto
github,
and
the
good
thing
about
github
is,
if
I
mean
y'all,
know
this
already,
but
I'll
stop
sharing
the
screen.
I'm
sorry,
let
me
go
back
to
that
platform.
One
more
thing
so
in
here
here:
here's
what
I'm
envisioning
similar
to
what
some
of
what
like
aaron,
was
discussing
with
issues
being
brought
forward
so
right
now
this
is
kind
of
generic
in
a
test,
so
you
can
create
a
project
and
and
call
it
whatever
you
like.
A
So
if
you
put,
I
don't
know
vca
guidebook
issues
and.
A
A
A
It
can
be,
but,
like
the
major
issues
can
go
here,
in
which
case
they
can
be
discussed,
and
so
I'll
go
back
to
the
ca
hub
over
here.
You
also
have
the
community
can
come
in
and
they
can
also
vote
here
to
show
importance
of
the
community
how
how
important
it
is
to
the
community
and
those
people
involved.
A
A
So,
like
issues
will
start
with
with
d
work
and
then
you
can
get
a
consensus
on
what's
important
and
then
the
important
area
issues
are
taken
to
aaron's
platform
and
then
that's
where
everything
is
hammered
out.
Details
are
hashed
out
and
then
like
define
the
finality
of
it
that
that's
kind
of
how
I'm
seeing
it
really
without
knowing
aaron's
detailing
platform
based
upon
what
was
shown
so
and
that's
it.
I
guess
I'm
open
to
comments,
see
if
there's
anything
I
might
have
missed
or
maybe,
if
there's
disagreements
with
the
process.
B
So,
let's
can
we,
let's
do
like
a
let's
just
walk
through
like
a
real
life
scenario,
so
this
the
let's
use
this
great
example
a
current
example
of
the
guidebook
needing
updates,
based
on
what
things
have
changed
for
fund
8
from
fund
7.,
so
that
how
we
did
that
here
was
we
talked
about.
We
talked
we
talk
and
talk
and
talk
in
the
answer,
town
hall,
so
we
have
all
the
after
town
hall
meetings.
B
First
of
all,
we
notice
that
there's
an
issue
because
things
have
changed
right.
So
now
we
have
to
talk
about
it.
We
get
together
in
the
after
town
hall.
We
all
have
a
conversation.
We
take
notes
on
it.
We
have
the
recording,
then
we
say:
okay
on
the
outs
of
town
hall,
we
say:
okay
by
thursday,
we're
gonna
get
together.
We're
gonna
get
in
the
discord
thread
right
now.
That's
how
it
is
we
all
get
in
there.
We
talk
about
it.
We
get
onto
the
document
itself.
We
all
add
comments.
B
We
comment
on
our
comments
on
our
comments
and
then
within
those
comments
we
make
decisions
on
the
comments,
which
is
what
aaron's
tool
would
really
completely
solve,
because
it
was
really
painful
and
then
we
then
that
document
so
then,
with
the
group
comes
together,
who's
working
on
it,
so
a
centralized
case
starts
for
it,
meaning
in
the
future.
B
We
will
want
to
look
back
at
the
previous
once
those
comments
are
accepted.
We
won't
understand
why
those
decisions
were
made
because
those
comments
don't
exist
anymore
and
although
we
talked
about
it
in
the
after
town
hall,
all
that
knowledge
is
lost,
then,
when
it
comes
to
edit
the
the
guidebook
next
time
we
sort
of
start
from
scratch,
based
on
the
based
on
the
what
the
reality
of
that
situation
is
at
that
time,
but
not
necessarily
with
the
same
people
who
edit
it
previously.
B
B
So
that's
how
that's
how
it
currently
went
and
there's
not
a
lot
there's,
not
an
archiving
of
why
those
decisions
were
made
and
there's
a
lot
of
thinking
around
some
of
those
decisions,
even
though
you
would
never
understand
that
when
you
read
the
guy,
the
guy's
just
going
to
be
like
a
nice
easy
thing,
you
don't
know
why
this
was
linked
externally,
why
it
was
chosen
that
this
goes
in
here.
What
the
data
was
that
informed,
how
we
made
those
decisions
and
that's
really
a
problem?
B
B
H
H
Do
you
have
do
you
have
a
history
for
the
changes
on
the
main
document.
F
Okay,
you
can
browse
between
different
versions
and
you
can
dive
in
into
every
version
and
to
see
the
discussions
have
been
happening
to
see
the
logic
and
the
reasoning
for
the
specific
change
to
be
applied,
and
also
to
see,
if
some,
some
numbers
of
of
a
supporter,
objective
objections
to
know
how
much
consensus
this
this
change
really
came
came
with
is
some
changes
that
can
could
be
fully
full
consensus,
and
some
of
them
would
be
just
on
the
a
matter
of
one
one
vote
to
to
make
the
decision,
and
then
you
can
reappeal
them
if
we
did
so.
F
B
It
really
does
it
solves
the
problem
of
the
edit
and
the
tracking
of
the
history
in
that
document.
So,
however
period,
that's
it
that's
a
solution
for
that
issue.
The
other
thing
is
what
were
this?
What
were
the
discussions
that
led
up
to
this-
and
I
noticed
this
tremendously
like
yesterday
in
that
vca
call,
there
was
a
gentleman
who
was
brand
new.
B
That
makes
a
lot
of
sense
that
that
does
solve
the
problem
that
you're
as
you're
thinking
about
it.
But
actually
what
has
contributed
to
this
problem
are
these
things
over
here
and
so
in
back
to
the
guide
case,
you
want
to
have
context
around
those
decisions
as
well.
Why
did
we
bother
to
put
the
length
issue
in
there
because
we
got
infiltrated
with
a
tremendous
number
of
short,
like
inadequate
assessments
that
and
nonsensical
ones,
and
so
you
need
to
in
fund
seven.
B
But
if
there's
no
record
of
that,
then
you,
you
might
not
even
know
why
that
was
decided
to
be
put
there
or
how
the
criteria
was
set
so
outside
of
the
actual
changes
to
the
document
and
the
reasons
for
those
decisions
having
a
record
of
people's
ins,
people's
yay
or
nay
is.
This
is
what
the
issue
was,
and
this
is
how
it
was
solved,
and
I
think
for
me,
that
is
where
the
github
situation
comes,
because
we
need
a
place
for
the
timestamp
recordings
of
those
times.
B
We
need
a
place
for
you
know
that
that
kind
and
those
kind
of
things
to
be
to
be
saved
in
one
place,
so
that
the
people
who
come
and
fund
10
aren't
like
what
the
heck
about
this
so
scott.
A
B
A
Do
if
it's
big
enough,
if
it's
a
big
enough
issue
like
I
guess,
that's
the
one
metric
to
determine
like
what
makes
an
issue
you
know
just
discussing
you
know,
I
don't
like
the
way
this
works,
so
I
think
if
we
can
define
what
actually
makes
an
issue
like.
Is
it
the
number
of
feedback?
But
here
would
be
my
suggestion
honestly,
is
that
you
can
have
the
discussion
like
there
there's
people
that
discuss
it
on
telegram,
and
so
somebody
determines
yes,
we
need
to.
A
We
need
to
show
the
we
need
to
to
create
an
issue
for
this,
and
then
you
come
in
here.
You
create
your
issue,
your
suggestion,
and
so
I'm
not
going
to
create
a
new
one,
but
I'll
go
back
to
the
video
demo.
So
this
is
the
issue.
Okay
and
then
you
go
go
to
discord
thread.
A
A
A
B
So
all
so
this
this
hash
here
for
these
dwork
issues
is
only
things
that
have.
It
is
only
populated
pretty
much
by
the
creation
of
the
issue
and
then,
once
you
click
on
it.
Now
we
can
talk
about
a
comment
on
the
right
and
those
things.
It's
a
two
directional
thing.
So
those
do
those
comments.
Then
we
comment
on
tests
of
all
tests.
A
Yeah
the
comments
don't
go
into
d-work.
This
is
the
d-work
is
just
like
a
kanban.
I
think
that's
what's
called
kanban
board
to
where
it
just
you
put
the
issues
in
there,
you
show
where
they're
at
you
can
put
conversations
in
there,
but
typically
what
I've
seen
from
the
use
of
it
is
that
it's
the
conversations
happen
outside
of
d-word
d-work
is
where
you
track
the
progress
and
track
the
issues.
A
So
with
the
integration
of
discord,
these
are
the
threads
that
that
phil
was
talking
about,
instead
of
it
being
just
a
run
through
all
the
way
through
here.
Just
conversations
about
various
things,
you
have
threads
off
to
the
side
and
you
can
click
it'll.
You
work
automatically,
creates
a
thread
right
here,
and
so
you
can
see
the
different
threads
on
it,
but
on
the
right
hand,
side
is
where
the
community
can
can
discuss
about
it
and
then,
if
there's
something,
that's
something
that's
resolved
or
a
team
decides
that
they
want
to
take
it
over.
A
A
A
However,
that's
this
is
a
suggestion,
there's
a
consensus
that
it
needs
to
be
done
and
that's
the
to-do
list
and
then
I
think
the
in
progress
or
maybe
somewhere
before.
That
is
where
aaron's
platform
would
come
in
and
it's
worked
on
for
the
in
progress
and
then
the
in
review
would
also
be
aaron's
platform,
since
he
has
the
cool
voting
tool
and
then
it
just
comes
over
here
and
then
like
for
this
one.
A
You
just
go
in
and
put
that
that
it's
done
and
obviously
within
here
you
can
add-
you
can
add
various
like
in
subtask.
I
guess
you
can
add
stuff
or
in
the
description
you
can
put
where
the
file
is
located.
What
pla?
You
know
the
a
link
to
it
and
when
you
click
done,
then
it's
done
it
closes
and
actually
it
also
updates
to
get
the
the
github
issue
and
it
closes
the
github
issue
as
well.
So
the
github
is
no
longer
open
for
comment.
B
So
back
to
the
get
back
to
the
guidebook
situation,
then
we
create
this
tip.
So
we
say:
oh
it's
definitely
an
issue
like
let's
pretend
fixed
mirror
board
is,
is
fix
the
guidebook,
so
we
open
it
up
and
then
under
description.
That's
where
we
would
post
maybe
a
link
to
the
document
that
we've
created
and
consents
that
people
can
now
start
yeah
yeah.
A
F
I
I
can
imagine
a
situation
where
some
some
ca
identifies.
F
A
problem
but
dca
does
does
not
necessarily
really
acquaint
it
with
the
guideline
document,
so
the
the
work
can
be
some
kind
of
of
a
place
to
put
those
issues.
Those
problems
in
in
the
first
is
the
first
step,
but
someone
some
other
ca
or
some
other
member
of
the
community.
That
knows
better.
The
guidance
can
can
link
between
the
two
say.
Okay,
this
problem.
We
can
solve
it
by
changes,
but
change
this
section
in
this
paragraph
in
in
the
document,
so
the
linkage
could
be
by
some
again.
F
I
think
I'm
thinking
about
culture
of
of
the
commentation,
because
I
have
my
own
experience
of
starting
the
developing
in
in
a
closed
system
and
then
opening
it
up,
and
I
realized
open
source
coding
demand
some
kind
of
very,
very
specific,
specific
documentation,
and
maybe
this
process
should
be
also
in
in
in
a
sense
documented
from
from
the
problem
sensing
to
the
to
the
solution
to
the
implementing
of
the
solution.
So
the
direct
the
work
I
see
is
a
as
a
place
for
roles
to
get
this.
F
B
That
makes
a
lot
of
sense
and
then,
when
people
come
in
to,
if
people
come
in
to
dework
here
you
can
see
everything
so
right
now
we
have
the
vca
improvements.
We
have
to
make
some
decisions
on
the
vca
improvements.
We
have
the
guidebook,
that's
being
updated.
That's
just
a
that's
like
a
group
issue,
but
it's
more
of
like
a
functional
thing,
whereas
we
also
have
like
the
community
this
this
group,
particularly
working
on
how
do
we
build
this
communications
and
workflow
process.
B
So
that's
something
that
would
be
like
have
a
lot
of
different
things
in
there
and
then
then
we
have
a
group
working
on.
How
do
we
educate
and
onboard
people?
How
do
we
recruit
people
and
maintain
them
so
you'd
be
able
to
see
the
whole
spectrum
of
that
there
and
then,
when
you
go
to
consent,
you
would
see
actually
what
did
this?
How
the
decision
making
this
is
like
giving
you
an
overview
and
then
the
consents
would
give
you
the
actual
place
where
the
work
is
being
done
and
collaboration
is
happening
and
voting
is
happening.
A
And
yeah
exactly-
and
this
just
want
to
show
one
more
thing
on
this
like
for
all
the
boards
that
are
open,
that
these
three
boards
you
can
go
to
combine
boards
and
it'll
show
every
every
process.
That's
either
going
that's
being
worked
on
going
through
closed,
so
it's
yeah
anyway,
there's
a
way
to
get
a
broad
overall
view
of
it.
You
got
a
lot.
H
H
Board
for
every
issue
that
we
have,
this
will
be
way
more
clear
to
view
and
understand
yeah,
otherwise,.
H
If
we
have
too
many
issues
in
the
same
board,
it
won't
be
easy
to
navigate
in.
B
B
A
No,
here's!
Here's
how
here's
actually
what
you
can
do
it
that
way
or
like?
I
was
just
using
that
as
an
example,
you
can
put.
B
B
A
B
Okay,
so
under
that,
then
would
be
ilia
let's,
if
we
did
this,
like
actual
reality,
function
functionality.
This
is
like
the
group
allison's
working
on
and
they're.
Solving
like
this
is
actually
a
great
example
of
here
is
where
the
guidebook
update
would
go,
but
also
that
group's
working
on
how
do
we?
How
do
we
recruit
more
cas?
That's
like
a
task
or
an
initiative,
and
then
another
thing
they're
working
on
is
like:
how
do
we?
What
kind
of
a
do
we
want
like
a
credentialing
and
an
onboarding?
G
A
Yeah,
I
think
that's
the
best.
I
think
that's
the
best
method
you
can
have
like
a
general.
You
can
have
like
a
general
group
like
a
general
ca
group,
maybe
or
something
I
don't
want
to
say
miscellaneous,
because
I
think
that's
overused,
but
you
know
just
like
a
general
group
like
people
that
want
to
express
their
frustration
to
nadia
or
something
like
that.
Let's
make
that
yeah.
Let's
see.
H
B
I
A
No
there's
there's
going
to
be
a
champion
as
to
use
nadia's
terminology
again,
there's
going
to
be-
or
in
this
case,
for,
for
instance,
this
one
when
you
do
an
invite,
you
can
invite
contributors
and
contributors
can
only
find
a
mistake,
and
I
tested
it
briefly
with
sim.
They
can
create
suggestions,
but
they
can't
make
any
of
the
critical
assignments,
and
I
don't
believe
that
they
can.
A
I
don't
believe
that
they
can
move
it
from
the
status
from
to
do
done,
whatever
have
you,
but
they
can
come
in
and
create
suggestions,
which
is
great.
I
think
it's
great,
but
here
is
where
the
stewards
you
would
invite
the
stewards
and
they
would
have
to
be
identified
and
those
would
be
the
ones
who
are
responsible
for
updating
the
board
and
moving
and
changing
statuses
and
moving
these
issues
across
the
board.
A
So
yeah
that
would
that's
part
of
and
there's
another
tool
too
called
role,
gating,
which
I
haven't
had
much
success
with
testing
it
with
sim.
But
the
doing
the
contributor
invite
is
perfectly
fine
with
the
role
game.
What
the
discord
role
game
will
do
is
like.
If
you
have
a
role
in
discord,
it
gives
you
certain
permissions
on
in
d
work,
but
yeah
and
back
to
your
original
question.
Ilia
is
that
yeah,
I
think
like
nadia
was
saying
like
recruit
and
retrain
would
have
one
all.
The
working
groups
would
have.
H
And
does
the
d-work
platform
archive
everything
that
has
been
done.
A
Yeah
and
go
straight
to
github
and
there's
also,
I
don't
know
where
it's
at
I'll
have
to
look
again
to
find
it,
but
there's
also
a
method
to
to
actually
download
everything
to
a
csv
for
a
particular
project,
and
so
it
presents
it
to
you.
Obviously
in
csv
format,
but
I
don't
have.
I
don't
have
github
open.
I
don't
have
github
set
up
on
this
particular
laptop
and
I
think
that's
the
biggest
hold
up
for
launching
right
now.
A
That's
the
biggest
hold
up
for
launching
dwork
is,
I
don't
know
what
we
need
a
discord.
I
mean
a
github
account
and
repo
for
each
working
group
and
I
think
that
would
be
beneficial
as
far
as
archiving
going
back
and
researching,
because
people
can
even
go
to
github
and
put
comments
in
and
those
comments
will
populate
back
to
discord.
F
I
need
to
live
now.
It
was
fascinating.
Thank
you,
nadia
for
inviting
me
and
we'll
be
in
touch
as
we
progress
as
we
create
more
progress
in
the
design
process.
I
wouldn't
be
in
touch
with
you,
because
your
feedback,
you
you
will
use
case-
are
the
most
important
thing
for
us
to
create
the
best
platform,
and
I
will
update
you
as
I
go.
Thank.
B
I
think
the
only
last
thing
to
say
is
that
we
need
to
figure
out
so
for
to
your
point
there
about
github
the
hold
up
on
github
is
we're
looking
to
create
a
repository
that
also
incorporates
government's
framework
and
is
and
is
legitimized
by
the
community,
so
that
that
is
something
we're
working
on
as
a
proposal
so
that
we
can
actually
have
it.
You
know
we
can't,
so
we
can
actually
have
it,
go
through
the
right
channel
and
and
be
legitimized
so.
A
Is
there
a
way
to
at
least
I
mean
I
don't
know?
Is
there
a
way
to
at
least
set
up
an
account
and
then
somebody
just
create?
They
only
have
to
put
anything
in
it.
Just
create
repost
and
excuse
me
for
those
working
groups
in
here
I
mean
until
then,
discord
is
just
discord,
nothing,
there's
no
it'll
it'll.
It
it'll
lose
a
lot
of
its
potential.
I
guess
that's
what
I'm
getting
at
well.
B
Should
we
do
it
to
just
test
the
whole
thing?
Should
we
create
one
just
as
a
maybe
not
a
permanent
but
a
temporary
solution?
So
we
can
test
the
inner
workings
of
everything,
because
I
do
think
it's
important
that
we
go
through
the
right
go
through
the
right
avenue
to
have
the
github
like
broadly
interconnected,
with
the
different
places
that
it
should
be
interconnected
and
also
from
a
governance
perspective.
Have
those
elements
built
in
which
we're
still
sort
of
figuring
out
exactly
what
they
are.
B
A
My
I
guess
my
issue
with
that
is
going
to
be
the
fragmentation,
then
of
the
the
repositories
like
if
people
actually
come
here
before
that
proposal
is,
is
actually
created
before
that
proposal
is
actually
funded
or
voted.
For
I
mean
you,
don't
even
know
if
it's
going
to
be
voted
in,
and
so,
if
there's
work,
if
the
platform
is
used
before
that,
then
all
that
information
gets
fragmented
from
whatever
the
official,
whatever
that
may
be,
is
set
up.
B
H
A
As
far
as
using
github
but
github
is
I
mean
github?
Is
it's
open
source
and
it's
I
mean
it's.
It's
yeah.
I
understand
that
things
need
to
be
tracked
as
far
as
you
know,
on
blockchain
and
recorded,
and
I
don't
know
how
much
you've
looked
into
actually
storing
the
information
on
blockchain,
but
it
gets
it's
super
expensive
to
do
that
and
yeah.
I
understand
I.
A
B
B
A
Yeah
well,
we
need,
but
what
we
do
need
also
is
integration
and
that's
going
to
be
the
issue,
or
else
we're
going
to
have
redundant
work
being
performed
yeah.
So
until
we
get
that
point-
and
I
don't
know
if
it'll
be
a
year
or
not
or
or
longer
but
yeah-
I
I
understand
your
concerns
ilia
as
far
as
that
goes,
but
the
tools
we
have
right
now
are
in
front
of
us,
and
that
seems
to
be
an
issue.
A
B
And
I
just-
and
I
just
said
a
year,
but
I
mean
if
this
works
well
and
it
solves
these
issues,
we
should
use
it
as
long
as
it
works
well
and
and
and
serves
us
right.
So
if
we
get
this
thing
put
together
here-
and
you
know
it
takes
us
out
as
far
as
we
need
to
go,
but
just
like
it's
happening
constantly
all
the
time
news
like
consensus
is
a
great
example
of
new
things
that
will
develop.
That
will
help
us
to
do
things
even
better.
B
So
at
this
point,
github
is
a
is
a
it's
the
open
source
component.
It
really
does
serve
the
need
it's
well
utilized
across
the
catalyst
community,
so
it
can
it's
easily
replicable.
So
that's
the
other
thing
we
wanted
to
create
here
is
something
that
is
replicable
for
other
groups,
and
that
means
we
have
to
really
think
these
things
through
in
the
beginning.
So
so
I
think
it's
on
me
here.
B
I
need
to
go
back
and
you
know
jeremy's
offered
to
advise
us
on
the
governance
component,
so
I'll
see
if
I
can
ping
him
today,
it's
just
a
it's
a
wild
time
for
everyone
with
the
proposals
to
be
doing
something.
That's,
but
we
are
going
to
create
a
proposal
here
as
well.
So
maybe
jeremy
will
give
us
some
feedback.
We
can
talk
to
stephen
and
vanessa.
We
can
sort
of
figure
out
what
it
is
that
we
need
to
make
this
proposal
complete
and
put
that
up,
and
then
at
least
we'll
have.
B
We
need
to
get
an
understanding
of
the
vision
of
how
github
needs
to
be
set
up
with
its
workflow,
so
that
so
that
we
create
governance
and
also
operational.
A
And
I
I
guess-
and
I
I
concur
100
with
that
github
is
to
set
up
an
account,
takes
absolutely
no
time
to
create.
I
don't
know
how
many,
how
many
working
groups
we
have
in
here
six
working
groups.
A
It
takes
no
time
to
set
up
six
repo.
None,
I
mean
it'll,
take
you
20
minutes
at
max,
but
I
think
the
biggest
issue
is
finding
out
where
it's
going
to
be
who's,
going
to
set
it
up
and
who's
responsible
for
the
keys,
because
in
order
to
do
this,
integration,
I'm
mistaken
there'll
have
to
be
some
sort
of
admin
rights.
A
It's
just
I
mean
just
to
make
the
link
and
that's
it,
but
in
the
meantime,
like
you
said
I
guess
I
can,
I
can
set
up.
Another
github
account
make
it
temporary,
but
I
don't
know
how
that
migration
would
be
from
whatever
is
worked
on
now
until
there's,
eventually,
a
final
official
github.
B
Okay,
so
we
need
to
have
this
solved
within
a
week
really
these
the
answers
to
these
questions.
We
might
not
have
the
github
in
a
week,
but
we
need
to
have
answers
solved
and
like
a
clear
path
of
what
we're
going
to
do.
So
I
will
take
that
from
here
scott
you
have
done
so
much
and
putting
this
together,
I
give
you
like.
B
A
Yeah,
it's
yeah
and
that's
it
yeah.
It's
just
getting
the
github
just
open
the
account
create
repost,
that's
it!
You
don't
have
to
do
anything
more
and
those
repos
don't
won't
interfere.
They
won't
interfere
with
with
anybody
else.
What
they're
working
on
any
of
the
framework
or
anything
it's
just
another
repo
on
the
github.
H
What
I'm
thinking
is
that
the
the
key
for
the
github,
the
password
and
everything
should
be
hold
by
the
by
the
representative
and
when
the
representative
changes
then.
A
I
A
B
And-
and
the
communication
needs
to
be
like
to
both
both
ways-
right
two-way
street,
because
one
of
the
functions
of
this
outside
of
the
community
working
on
things
together
is
when
we
have
issues
that
we
need
outside
involvement
on,
we
have
to
be
able
to
kick
those
into
in
those
directions,
and
so
this
the
github,
has
to
integrate.
Also
with
with
circle
stuff,
it
has
to
integrate.
B
All
directions
in
all
in
all
directions,
so
we
need,
we
need
to
really
think
about
how
we're
putting
it
together
and
what
it
affects
as
we
go,
but
we
did
not
also
not
overthink
it.
So
I
I
don't
think
it's
a
super
complicated
thing.
You
know,
I
think
that
you
know
that
we're
working
on
the
treasury
for
the
ca
treasury,
you
have
to
say
things,
you
can't
just
say:
we'll,
have
a
pot
of
money
and
we'll
distribute
it
as
needed.
B
We
need
to
say,
like
there
will
be
this
person
and
that
person
will
hold
the
keys
to
it
and
in
order
to
request
the
funds
from
it.
This
needs
to
happen
and
then,
as
the
funds
are
distributed,
these
three
things
need
to
be
chronicled
and
it
has
this
criteria
there
has
to
be.
There
has
to
be
governance
around
some
of
the
stuff.
B
So
that's
that's
really
that
and
we
need
to
get
that.
Get
that
straightened
out.
I
don't
think
it's
a
huge
job,
but
I
do
think
it's
one
that
if
we
skip
we'll,
we
won't
have
as
solid
as
a
product.
B
Okay,
so
I
will
take
that
as
a
marching
order.
Do
you
want
to
talk
about
like
recurring
meeting
time,
so
we
don't
have
to
like
yeah
all
this
stuff
happening.
A
Perfect
yeah,
thank
you
for
bringing
that
up.
So
here's
what
my
solution.
It's
not
a
solution,
but
it's!
I
guess
my
idea
is
to
create
another
when
to
meet
and
create
another
win
to
meet.
Send
that
out
to
like
put
an
announcement
here
in
discord.
A
A
You
know
where
that,
where
the,
where
the
the
the
most
available
hours
are
and
then
those
will
be
the
meetings
and
we'll
have
one
on
I'm
guessing
like
on
a
a
monday
or
tuesday
and
then
one
like
on
a
thursday,
but
one
will
be
in
the
morning
and
one
will
be
in
the
evening,
so
it
should
overlap,
and
it
should
also
be
like
if
there's
something
to
happen
between
the
beginning
of
the
week
and
the
latter
part
of
the
week.
Then
that
can
also
be
brought
up.
A
A
No,
they
will
be
the
same
problems
and
then
it'll,
it'll
kind
of
be
like
an
overlap,
it'll
kind
of
be
like
maybe
it'll
kind
of
be
like
a
if
there
are
still
existing
issues.
My
guess
is
that
they
would
be
brought
up
again
in
the
next
meeting
and
then
there'd
be
a
recap
from
the
previous
meeting.
As
far
as
what
was
discussed,
but
you
know
also
there'll
be
videos
where
people
can
catch
up
on
information
as
well
yeah.
You
know
we're
kind
of
still
just
playing
kind
of
feeling
it
out
and
playing
around.
H
A
A
A
I
think
I
think
nadia
has
permissions
and
I
think
same
has
permissions
to
record,
but
there
needs
to
be
some.
If
we're
going
to
do
video
recordings,
there
needs
to
be
somebody
here
to
handle
that
as
well
and.
B
But
you
know
what
we
could
I
mean
we
could
have.
We
could
open
it
for
people
to
to
come
and
because
we're
we're
interrelated
with
a
lot
of
things.
So
I
think
why
don't
we
send
this
out
scott
and
see
if
maybe
there's
a
time
that
really
does
well
for
everyone,
and
we
don't
need
to
do
multiple
ones
so,
we'll
see.
A
Yeah
yeah,
of
course,
of
course,
yeah
absolutely
and
and
maybe
and
all
this
is
entirely
up
to
you
I
mean.
Maybe
maybe
this
should
be
done
offline.
I
don't
know,
but
maybe
people
can
cut
like
if
you
have
something
you
want
to
announce
to
the
to
the
cas
or
vcas.
You
know
you
can
have
like
a
weekly
event.
I
don't
know
or
like
a
bi-weekly
event,
that
is
on
a
specific
day
and
time.
A
G
B
You
know
it's
only
been
in
existence
for
a
week
or
two
like
really
actually
working
on
things,
and
you
know
it's.
It's
grown
a
lot,
so
you
know
a
lot
has
been
accomplished.
So
I
think
we
can.
Let's
just
start
with
seeing
what
consensus
is
as
far
as
timing,
and
then
you
know
scott,
maybe
you
and
I
and
anyone
who
wants
to
weigh
in
maybe
we
put
together
something
like
a
weekly
like
half
hour,
check-in
kind
of
a
thing
or
we
figure
out
an
unsync
meeting.