►
From YouTube: Aries-vcx Meeting
Description
Aries-vcx Meeting
A
B
B
Well,
I
know
that
Miro
is
not
joining
today,
but
let's
give
it
a
minute
or
two
see
if
perhaps
not
an
iron
or
both
can
I
join.
B
B
So
yeah
welcome,
George
to
and
anybody
who's
listening
somewhere
else
to
Harry's
vcx
Community
call
it's
September
21st
2023,
and
this
is
our
hyperledger
and
Anti-Trust
policy
notice,
which
is
in
effect
starting
meeting
discussion.
B
A
B
Right,
okay,
so
in
that
case
some
Community
updates.
B
So
well
this
this
has
been
here
kind
of
permanently
put
as
a
reminder:
I
still
haven't
managed
to
stop
by
there
and
time
off
on
Monday,
so
I
couldn't,
but
that
was
I
was
yesterday
attending
the
Aries
War
group
call,
and
so,
and
so
two
points
were
well
not
necessarily
touched
on.
I
didn't
get
to
speak
about
the
issue,
credential
stuff,
but
I
think
the
the
guys
are
aware
of
that.
B
B
Both
of
those
are
kind
of
questionable,
so
I'm
raising
questions
here
as
to
whether
it
is
a
real
necessary
if
somebody
is
actually
using
it,
and
what
do
we
do
in
in
a
V3
versions
if
this
can
be
somewhat
considered
as
we
shape
the
next
version
of
the
community,
as
we
should
the
next
version
of
edition's
credential
protocol,
which
will
be
definitely
coming
with
the
adjustments
needed
for
the
conv2
and
I
kind
of
also
touched
on
I,
saw
this
as
a
payments
kind
of
decorator
in
the
the
issue,
Credence
will
be
two
I
think
it
makes
the
protocol
heavier
than
it
have
to
be,
and
can
be.
B
This
kind
of
stuff
can
also
be
decoupled.
So
also
also
left
the
point
here,
I'm
curious.
What
what
kind
of
discussion
is
gonna
spread
out
of
this
so
yeah
we'll
see.
Perhaps
this
might
be
also
the
better
medium
to
discuss
the
issue
than
raising
it
on
a
call
and
that
on
a
wardrobe
call
and
then
I
have
five
to
ten
minutes
to
discuss
about
it.
B
I
guess
this
way
people
can
pretty
body
make
up
their
mind
and
and
next
next
week
we
can
have
more
more
effective,
more
efficient
discussion
on
the
call,
then
also
there
is
a
spec
for
did
tier
4,
which
is
apparently
nearing
completion.
B
But
yeah
I
was
asking
on
a
call
for
like
how
long
is
this
gonna
be
open
for
a
modifications?
Is
it
usually
it's
easier
to
find
out
it's
easier
to
find
out
things
you
don't
like
about
rfcs
once
you
actually
start
to
implement
them,
so
I
was
asking
like
how
how
long
can
this
stay
open
for
modifications?
So
we
don't
have
to
create
a
did
peer
version.
Five.
B
If
we
run
into
some
breaking
tweaks,
you
would
like
to
do
and
basically
there's
no
rush.
I
was
told
that
there
is
no
not
necessarily
Rush
with
merging
this,
and
we
are
welcome
to
you
know,
leave
leave
feedback
on
this,
but
yeah
so
I
I
kind
of
like
to
comment
here
that
we'll
be
starting
implementing
this
just
so
that
they
are
aware
of
it
and
hopefully
waiting
for
us
to
provide
some
feedback.
B
If
we,
if
it
turns
out
that
we
have
any
I,
think
nevertheless,
I
think
it
would
be
good
if
we
start
working
on
this
rather
sooner
the
later
I
think
early
October
early
October
should
be
the
latest.
We
should
start
looking
into
this.
B
And
yeah
I
don't
know,
I
saw
that
the
discussion
last
kind
of
community
happening
wise.
So
the
the
issue
you
George
created
a
while
ago
I
know
it
seems
a
little
bit
stale.
The
last
comment
was
two
weeks
ago:
do
you
know
if
there's
I
know
any
any
devote
further
developments
of
this?
So
Andy
was
talking
about
some
releases
here.
Do
you
know
if
anything
came
out.
B
Right,
okay,
well,
we'll
see,
I
haven't
checked
the
repos
if
there's
possibly
any
releases,
so
it
might
be
something
I
would
missed.
I
guess
just
just
want
to
keep
track
of
this,
so
I
think
we
can
keep
it
here
until
these
things
become
resolved,
yeah
and
then
and
then
well
before
I
move
on
to
mentorship
updates,
there's
a
new
and
then
you
do
does
any
of
you
any
any
kind
of
Community
updates
or
attended
any
any
any
calls
to
report
on
by
a
chance.
B
No
I
guess
10
minutes.
No,
so
that's
fine!
Let's
move
on
to
mentorship
updates,
so
we
we
also
have
nine
to
join
the
call
eventually
and
welcome
on
okay.
So
we
can
start
with
a
mediator,
so
it
it
came.
It
happened
to
be
that
usually
coming
coming
report
as
to
to
about
your
status.
So
you
have
any
news
and
progress
updates
for
us
this
week.
C
Okay,
so
last
time
I
think
I
had
demoed
this.
That
is
this
is
the
mediator
displaying
an
out-of-band
in
white,
so
this
is
currently
implemented
for
the
mediator
part.
Then
this
past
week,
I
was
working
on
the
client
side
of
the
mediator
that
is
making
a
connection
using
this
out
of
pen.
Invite
last
time
I.
Think
I
had
also
demoed
the
web
UI
for
making
a
client
request.
C
So
George
mentioned
last
time
about
if
I
had
tried
to
do
a
CLI
and
I
had
mentioned
that
it's
a
bit,
not
very
ergonomic,
so
I
did
think
about
it,
though,
later
again,
when
George
mentioned
and
I
thought,
okay,
a
CLI
is
not
very
ergonomic,
but
a
toi
could
kind
of
be
possible
for
Aries,
so
I
went
ahead
and
experimented
with
this
Library
called
cursive
and
I
have
something
right
now.
So
this,
for
example,
you
can
see
this
is
the
toi
that
I
created
for
the
Aries
mediator
client.
C
So
you
get
a
list
of
endpoints.
Just
like
you'd
have
endpoints
for
the
web
UI.
You
can
have
a
list
of
them
here
and
then
you
can
use
your
mouse
to
select
it
and
you
get
this
nice
display
box
where
you
can
manually
copy
paste.
So,
for
example,
I'm
now
here
copying
the
OB
invite
from
the
web
page
and
pasting
it
here.
C
So
it
works
fine
and
you
can
try
to
connect
so
right
now
it's
showing
a
404,
because
the
mediator
side
of
receiving
the
connection
request
isn't
implemented
yet,
but,
as
you
can
see,
you
can
kind
of
have
a
terminal
UI
for
the
client,
also
yes
and
yeah.
So
right
now,
I'm
working
on
the
mediator
side
of
accepting
the
connection
and
sending
back
a
response
and
I
hope
that
by
maybe
next
week,
I'll
have
the
connection
part
holy
setup.
B
Thank
you.
Thank
you.
That's
very
cool.
Looking
forward
to
see
you
know
making
connections
through
this.
This
you,
this
UI
and
like
fetching
checking
for
the
messages,
can
be
actually
really
really
cool
demo
to
show
the
ones
we
have
ones
like
the
whole
did
come.
Kind
of
interface
is
integrated
here
and
I
would
be
able
to
click
on
buttons,
like
fetch
messages
and
see
all
the
messages
and
from
whom
they've
been
sent.
C
B
It's
gonna
be
really
cool
for,
like
demo
purposes
and
yeah
actually
actually
like
I
would
like
to,
and
this
applies
for
the
both
projects
both
for
the
mediator
and
the
UEFI
wrapper
it'll,
be
I,
think
nice
to
make
a
small
demo,
and
some
of
the
Aries
or
group
calls
just
to
show
what
we
are
up
to
and
what
are
the
outputs
of
the
the
mentorship
which
we
are
running
and
I
think
this
will
be
like
really
beautiful
demo
for
the
for
that
purpose.
To
actually
show
them
like.
B
B
Yeah
and
then
so,
moving
on
to
the
good
job
again
and
I
think
not
just
like
briefly
I
guess
like
going
forward.
Perhaps
next
week
we
might
have
the
collection
completed.
Do
you
think,
like
I
know
established
it
com
connection.
B
B
A
Yeah
yeah
I
am
I,
I'll
suggest
something
new
and
then
it'll
end
up
in
another
PR.
So
maybe
it's
my
fault
for
not
waiting
until
the
first
one's
done
before
recommending
other
things.
But
it's
it's
going
well
the
project,
the
connection
implementation
is
done.
I
think
swapnils
addressed
my
final
comment
now,
but
then
we
were
earlier
this
week
we
were
having
a
look
at
how
we
can
refactor
the
app
a
little
bit
to
make
it
more
readable
and
understandable
to
people
who
look
at
it.
A
A
Then
we
did
some
script
optimizations
as
well,
so
yeah
it
should
be
easier
for
you
know
someone
like
you
or
just
a
random
Android
developer,
to
try
spin
up
the
project
themselves
with
the
simplest
script
yeah
and
in
the
meantime,
swapno's
been
looking
at
the
issue.
Credential
V1
protocol
and
that's
the
next
task.
B
Cool
cool:
when
do
you?
Do
you
think
that
we
would
I
mean
there's
not
necessarily
any
Rush
with
doing
this,
but
I
was
just
thinking
about
doing
some
demo,
like
you
know
dedicating.
C
D
B
Much
space
of
a
single
Aries
for
a
group
call,
but
do
you
think
they're
that
the
that
the
app
is
like
nearing
a
stage
where
there
will
be
something
demoable,
I
guess
maybe
the
the
connections
working
and
the
and
issue
issuance
protocol
and
being
implemented?
I
guess
that's
something
that
will
be.
You
know
the
the
mobile.
A
B
Guess
yeah
yeah,
I,
guess
I!
Guess
we
the
board
and
demo
it
multiple
times
so
I
guess
it's
better
to
make
sure
that
things
are
right
further
than
the
rush
quickly
to
show
what
has
been
done.
B
Right
so
yeah
that
in
mind,
yeah,
no,
no,
no
rifle
that
just
I
guess,
but
let's
keep
it
in
mind
that,
like
eventually
I
want
to
show
this
to
like
wider
community,
so
we
should
have.
We
should
have
I
mean
for
for
none.
We
can.
We
can
and
I
wouldn't
do
live.
Demos
rather
just
like
do.
B
I
know
one
two
minute
recording
of
of
the
of
the
things
of
those
things,
but
for
Fernand
that
can
be
the
the
terminal,
UI
kind
of
demonstration
and
and
yeah,
maybe
from
the
app
it
can
be
just
recording
of
like
connect
scanning
QR
code
and
then
getting
some
credential
from
there
and
and
here
also
along
with
that
I
think,
once
we
like
show
it
to
the
world.
B
We
should
also
make
sure
to
have
a
some
nice
nice
readings
about
it,
but
we
still
have
what
month
and
a
half
till
the
end
of
mentorship.
Is
that
right?
Something
like
that.
So
yeah
should
be
enough
time,
all
right
so
going
through
our
usual
Parts
overview.
So
it's
not
much
to
start
this
week.
I
think
we
had
the
lint
fixes
it's
yet
to
be
merged,
but
I
consider
it
as
to
be
done.
The
CI
looks
like
it's
gonna
pass
my
approval
on
it.
B
So
I
know.
If
you
guys
wanted
to
have
a
look
at
it.
It's
a
it's
a
huge
Delta
but
yeah
that
should
be
pretty
much
ready.
B
I
got
lost
there.
We
are,
then
there
was
further
integration
test,
refactoring
them
that
done
my
mirror.
I,
don't
think
I'm
gonna
explicitly
go
into
details,
it
was
refactoring
and
then
similarly
some
dependency
cleanups
from
myself.
There
are
some
dependencies
which
are
not
necessary.
B
D
Assume
in
particular
to
George
if
he
wants
to
have
another
look
over
it
or
yeah.
The
description
pretty
much
said
that
the
like
bigger
crates
like
rsbcx
series,
CX,
core
and
Libby
CX,
are
gonna
be
handled
in
separate
PRS,
which
they
were,
but
the
PRS
were
based
on
this
one
and
I
saw
that
you
merged
the
vcx
core
one,
so
I
merged
the
other
one
too.
So
they're
now
part
of
this,
which
makes
it
bigger
I
guess,
but
just
just
as
an
FYI.
D
B
Yeah
yeah
apologies
I,
actually
didn't
notice
that
it
was
based
on
this
one.
So
it's
it's
my
mistake,
I
I
would
I
would
generally
also
like
actually
prefer
that
approaches
while
having
them
merge
separately.
So
if,
if
you
are
fine
with
that,
we
could
perhaps
you
could
horse
push
into
this
PR
the
original
pre-emerge
version,
and
then
we
create
those
PR.
So
we
can
merge
them
into
main
or.
B
Well,
it's
I
guess
it's
still
out
there,
I
guess:
restorable.
B
D
Yeah
I
don't
know
anymore
honestly,
but
yeah
like
I
said
when
I
started
emerge
this
one
I
just
merged
the
other.
One
I
thought
that
you
just
wanted
to
have
one
bigger
PR,
but
I
think
we
can
just
leave
it
as
it
is
right
now.
The
the
Aries
vcx
and
rsvcx
core
PRS
were
approved
by
both
you
and
Mira.
D
So
I
guess
that's
fine,
and
this
one
will
basically
incorporate
this.
So
I'll
do
live
vcx
in
a
separate
one
and
one
more.
It's
gonna
still
gonna
be
based
on
this,
but
we're
gonna
merge
them
into
main
separately
I
I
guess
the
levy
CX
is
the
most
Troublesome
one
anyway,
when
it
comes
down
to
lens.
So.
B
Yeah!
Sorry
about
that
again.
D
We
could
probably
restore
things
but
I
I
think
that's
just
wasted
effort
right
now
going
through
commits
and
I'm,
not
sure
exactly
like
I
know
there
was
some
modifications
done
before
I
had
to
rebase
some
stuff
I,
don't
think
it's
gonna,
be
all
that
straightforward
and
I
I,
really
don't
wanna.
B
Yeah
I
I,
I
I,
don't
know
what
was
the
discussion
between
you,
bogana
and
George.
It
seems
like
you
had
some
communication
about
this,
which
I
kind
of
didn't
realize.
George
are
you?
Are
you
fine
with,
despite
what
happened
and
that
we
actually
got
it
merged
you
find
with
going
forward
and
merging
this
yeah.
A
No,
that's
okay,
yeah
I
bugged
into
just
explained
the
incremental
approach
to
me
before,
but
yeah.
It's.
B
A
B
Yeah
George:
do
you
want
to
a
leave
review
for
for
this
one.
A
Yeah
I've
already
looked
at
the
the
dot
Rus
format
file
and
you
know
it
didn't
didn't
scare
me
or
anything
so
I
guess
I'll,
just
yeah
do
a
review
and
prove
it.
B
B
Well,
parked
parked
tasks
at
the
Diddy
exchange
for
a
while
I
think
we
should
burst
at
least
implemented
it
before
and
then
sync
it
up
with
those
changes.
And
then
perhaps
we
can
actually
merge
to
The
Exchange,
PR
and
similar
for
the
demo.
B
I
was
actually
working
on
this
further
after
I
got
the
reviews
from
you
guys.
I
have
an
address
everything.
There
are
still
comments
from
George
I
need
to
address,
but
I
did
address
kind
of
bigger
impact.
Higher
impact
request
from
from
Bogdan,
so
I
have
removed
actually
the
HTTP
messaging
from
here.
B
So
the
all
the
messaging
now
happens
happening
through
the
npsc
channels
and
it's
it's
a
bit
simpler,
I
know:
I,
guess:
I
will
Mark
you
for
read
review,
but
I'll
I'll
yet
want
to
finish
up
those
spending
comments
and
there
will
be
ready
for
the
new
review.
B
Now
I
think,
essentially
what
this
is
becoming
a
little
by
little
is
kind
of
integration
test
for
connections,
but
yeah
I
I
think
that
this
could
be
a
kind
of
a
good
pattern
for
those.
B
But
let
me
let
me
know
what
you
guys
think:
I'll
I'll
ping,
you
on
studies
ready
so
I'll
just
move
on
for
now
in
progress,
yeah
still
kind
of
preparing
for
the
vdr
tools
and
on
credit
removal
and
obviously
from
George
side,
a
V2,
slash,
presentation,
protocols,
drafting
I,
don't
think
we
have
planned
anything
new
right
now
other
than
what
we're
already
doing,
and
that
brings
us
to
the
end
of
the
discussion
and
any
other
ones.
You
guys
have
to
bring
up.
A
Yeah
so
today,
for
me
was
mostly
looking
at
the
message
structs
for
the
V2
issuance
protocol
and
there's
a
draw
PR
up
for
that,
but
I'm
not
entirely
sure
if
I've
done
the
right
thing,
because
I
don't
think
there
is
a
comparison
to
look
at
in
the
messages
crate
where
there's
sort
of
different
versions
for
the
same
message,
but
yeah
yeah,
Bogan,
you've
seen
my
private
message
this.
A
B
Right,
let
me
just
quickly
skim
skim
through
this
and.
C
B
Did
you
have
something
to
did
you
want
to
say
something?
You
were
unmuted
for
a
while.
C
This
is
unmarked
message,
so
this
wallet
has
this
unpacked
message
that
takes
in
an
encrypted
message
and
gives
out
a
vector
so
initially
when
using
that
in
the
client
implementation
of
Aries
I
had
some
confusion
of
what
this
Vector
actually
is
and
I
did
take
a
look
at
the
Aries
demo
that
you
have
on
GitHub
right
now
and
like
there,
I
saw
that
you
have
this
Private
Structure
called
unpack,
where
you
have
message
sender,
very
key
and
recipient
key
as
the
three
different
properties
of
that
structure,
and
then
your
deserializing
that
Vector
that
unpack
message
returns
into
that.
B
B
C
It's
a
very
opaque
long
Vector
like
we
don't
know
what
things
it
contains.
I
did,
in
fact
like
take
a
look
like
going
down
the
rabbit
hole
by
I
mean
by
seeing
the
implementation
of
Indie
wallet
and
then
from
there
going
into
ariesvcx
core
signing
dot,
RS
and
then
deeper
and
deeper
and
I
ended
up
at
vdr
tools
where
the
actual
structure
is
defined.
The
unpack
message
so
like
since
video
tools
is
I,
guess
a
optional
dependency.
A
Yep
yeah
big
agreed
from
me
I,
think
I
think
the
base
wallet
should
just
return.
The
struck
swapnil
had
this
same
problem
last
week
and
was
confused
by
the
Vector
of
u8
because
it
is
confusing.
D
Well,
the
problem
actually
goes
way
deeper
than
that.
It's
right
now,
I'm,
not
sure
how
willing
or
home
worth
it
would
be
to
change
vdr
tools,
but
it's
a
whole
mess
of
serializing
and
this
realizing
some
jws
or
jwe
I.
Don't
remember
structures
and.
D
Yeah,
the
vector
of
of
bytes
was
basically
I,
guess
a
representation
of
that
so
like
a
serialization
of
that
gwe
structure,
which
I
guess
Patrick
replicated
in
the
in
the
in
the
demo.
With
that
unpacked
message.
A
B
D
B
Yeah
I
would
suspect
the
dust
car
might
be
better
in
the
in
terms
of
efficiency.
Also,
I
haven't
looked
at
the
code,
necessarily
just
assuming,
based
on
the
fact
that
it's
like
refactored
component
but
yeah
I
mean
the
the
least
we
can
do
at
least
for
Nan
and
newcomers.
Swapnil
new.
C
B
Else,
I
guess
it's
to
to
just
tweak
those
apis
on
all
Aries
vcx
level,
the
stuff
we
provide
and
return
something
more
reasonable,
despite
the
fact
that
maybe
the
underlying
vdr
tools
followed
implementation
is
not
not
ideal.
B
So
yeah
thank
you
now
and
I
will
we'll
get
that
addressed
or
if
you
would
like
to
you,
can
actually
take
that
issue
and
try
to
try
to
address
it
yourself
and
quick
review
or
PR,
but
you
should.
You
should
primarily
focus
on
the
on
the
connections.
But
if
you
like
to
take
this
as
a
side
quest
so
to
speak,
then
you
are
free
to
do
so.
C
Yeah
sure
I
mean
I.
I
was
doing
this
anyway,
like
this
morning,
I
was
kind
of
digging
down
this
hole,
trying
to
understand
what
it
is
so
now
that
I
have
I
think
I
can
make
a
PR
changing
the
structure,
so
one
question
I
would
have
if
I
do.
This
is,
should
I
return,
a
different
structure
in
the
base,
wallet,
trade
or
should
I
just
add
the
documentation
regarding
what
the
structure
looks
like
of
the
vector.
B
Now,
it's
probably
lean
towards
just
returning
the
some
some
sort
of
struct
because
yeah
we
always
whenever
we
unpack
message.
We
want
to
actually
work
with
the
data
and
and
usually
we
don't
work
it
with
work
with
it.
I
don't
I,
don't
think
there
is
a
case
where
we
work
within
in
in
such
an
op-back
way.
B
Typically,
when
we
unpack
it,
we
want
to
inspect
what
the
actual
message
is
and
what
what
the
send,
what
the
sender
work
is
stuff
like
that,
so
because
in
some
some
space
some
I
can
imagine
that
there
would
be
scenarios
where
you
actually
want
to
get
just
a
raw
kind
of
data
as
a
UA,
Vector
UA,
then
then
just
pass
it
somewhere
else,
but
I
don't
think
we
have
such
a
case
now
and
it
is
more
confusing
than
it
has
to
be.
So
you
can
create
news
track.
I!
B
Well,
yeah
I
guess
something
like
that.
You
also
have
to
possibly
change
lots
of
random
places
in
code.
I
I,
don't
know
if
many,
but.
C
C
Okay,
okay,
I'll,
take
a
look
sometime
in
the
evening
today.
Maybe
all.
B
B
Okay,
guys
anything
else.
A
If
there's
nothing
else
from
anyone
just
on
the
Aries
RFC
issue,
you
raised
I'm,
not
sure
if
you
saw
my
reply
but
I
think
the
presentation.
Protocol
V2
is
a
very
similar
story,
but.
B
A
They
do
draw
attention
to
the
fact
that
it's
an
array,
so
you
can
sort
of
see
the
quote
there
and
I'm
having
a
hard
time
understanding
what
they're
trying
to
say
with
this
here
I
think
they're,
trying
to
say
that
you
can
attach
you
know
five
different
presentation
requests
in
different
formats
and
then
the
holder
or
the
proof
is
only
meant
to
reply
to
one
of
them
that
they
can
reply
to.
But
I
don't
know.
If
that's
that's
what
they're
trying
to
say.
B
In
addition
is
that
this
correct
place
I'm
reading
here-
oh
yeah,
the
in
addition,
the
egg
and
problem
informations-
are
about
that
yeah
yeah
are
the
messages
that
include
ethics,
attachments
may
use
any
form
of
embedded
attachment
in
the
examples
below
the
forms
of
attachments
are
arbitrary.
The
attach
array
is
to
be
used
to
enable
single
presentation
to
be
the
requested
delivered
in
in
different
verifiable
presentation
formats.
D
D
Right
and
I
I
guess
it's
fairly
straightforward,
which
would
make
more
sense.
I
would
make
it
less
stupid,
honestly
that,
okay,
they
allow
you
to
have
an
array
of
whatever
attachments,
because
you
can
have
an
array
of
formats
and
it
essentially
allows
you
to
send
the
send
the
same
message:
the
same
attachment
but
encoded
in
different
formats,
so
that
the
counterpart
you
can
choose
whichever
they
want.
D
I
guess
that
that
makes
more
sense,
rather
than
the
ability
of
sending
multiple
like
unrelated
attachments,
presentations
or
proposals
or
whatever.
In
the
same
in
the
same
message.
B
Yeah
yeah,
that
that
makes
sense,
I
think
that
that's
how
I
understood
it
as
well
I'm
just
wondering
if
it's,
if
it's
some
sort
of
different,
what
kind
of
form
I'm
just
wondering
what
kind
of
formats
there
there
can
be
I
know,
there's
a
I'm
wondering
if
it
refers
to
like
kind
of
formats
of
in
general,
because
I
know,
there's
like
three
I
heard
that
there's
three
different
ways:
how
to
work
with
attachments
or
informat
them
or
I'm
wondering
if
it
really
refers
to
the
some
sort
of
format
of
the
presentation
itself.
B
A
B
When
you're
requesting
a
presentation
you
performance
contains
entry
for
each
because
presentation
attach
array
entry
from
the
attachment
registry
below
oh
okay,
I
see.
B
B
Yeah
well,
let's
see
what
what
comes
out
of
this
and
what's.
B
Community
members
thinking
and
if
this
being
actually
used,
that's
that's
what
I
wonder
about
the
most.
B
Let's,
let's
I,
guess
I'm,
just
looking
at
the
list
of
to-do's
here
I
know:
I
crossed
the
Olympics
since
we
are
getting
addressed
now
next
next
week,
I'll
delete
it
just
look
at
this
report.
Reorg
Point
here
wondering:
if
shall
we?
If
we
shall
start
doing
some
sort
of
you
know,
murdered
not
necessarily
merge
these
projects
but
create
some
sub
some
root
directories
and
and
score
a
bunch
of
crates
in
there,
for
example,
the
did
come
like
did
and
did
resolver
related
stuff
I.
B
Okay,
then
perhaps
we
can,
we
can
go
through
it
through
chat
because
you
don't
chat
or
or
maybe
next
week,.
B
Stuff,
like
that,
so
you
know:
let's,
let's
try
to
discuss
that
then
get
a
bit
simplified
here.
So
lots
of
directories
very
overwhelming
for
some
some
new
newcomers
I
think,
okay,
guys
I
think
that's
it
is
that
it.