►
From YouTube: EOS MANDEL Meeting #6 (March 16th 2022)
Description
All EOS Mandel Meetings : https://github.com/EOS-Nation/mandel/issues/37
#eos #mandel
Everything EOS is the official media channel of the EOS Network Foundation (ENF). The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.
// EOS Network Foundation //
https://eosn.foundation
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosn.foundation
#EOS #EOSIO #ENF
A
All
right
welcome
everybody.
This
is
the
sixth
mandel
weekly
check-in.
It
is
march
the
16th
welcome
everybody
we'll
continue
as
we
do
going
through
the
stuff
we've
got
in
progress.
We've
got
some
checking
in
to
do
on
the
mandel
code.
We
can
check
in
on
how
we're
doing
on
getting
vps
registered
on
jungle.
I
don't
have
much
to
share
in
terms
of
updates
for
this
survey.
I'm
not
sure
if
randall
is
on
the
line.
Maybe
he's
got
some
to
share
some
documentation
there
in
progress.
A
B
On
the
agenda,
so
why
don't
we
get
right
into
it?
So
dan
confirmed
over
since
last
call
that
his
team
will
be
releasing
what
we'll
call
3.0.5
or
3.05
sorry
3.05,
and
that
essentially
should
be
reviewed
and
merged
either
by
the
end
of
this
week
or
early
next
week,
and
that's
what
we
are
yeah,
no
second
dot.
So
just
3.05,
okay
or
that's
what
it's
being
called
that
we
can
adjust
later
on
what
it
does
have.
B
However,
the
block
logs,
whatever
block
split
logs,
as
well
as
the
list
of
issues
that
are
still
pending
that
are,
if
I
believe,
merged
in
2.21.x
or
whatever,
on
the
block,
one
repo,
basically
that
that
whole
list
that
stan
is
compiled
right.
That
will
not
be
in
three
point:
zero
point,
three
point:
zero
five,
and
so
when
the
engineer's
on
r
and
start
that
will
be
one
of
the
first.
If
not
the
first
thing
that
they'll
tackle
will
be
finishing,
the
merging
of
the
block
logs
and
those
issues
so
that
we
then
create
3.1.
B
C
B
B
B
To
to
adjust
that
so,
basically
over
the
coming
month
or
two,
let's
continue
adding
the
issues
within
reason,
of
course,
but
especially
if
they're
already
in
2.1
or
2.2.x
whatever,
then
we
can
port
them
to
3.1.
We'll
have
the
time
to
be
able
to
do
so
likely
that
will
also
impact
the
testnet
strategy.
Where
I
would
guess
now,
the
idea
would
be
to
go
from
2.0,
which
I
believe
is
currently
running
to
3.0
to
3.05
or
maybe
even
skip
3.05,
but
get
depending
on
the
amount
of
time
and
then
just
go
straight
to
3.1.
D
E
Yeah,
okay,
so
a
little
bit
of
a
little
bit
of
color
here.
So
the
the
there's
two
things
here
so
there's
we
might
call
it
the
nuclear
option,
that's
in
two
one,
which
is
that
it
just
sets
a
timer,
basically
that,
but
we
don't
see
anything
on
a
connection,
it
severs
it
and
restarts
it.
So
that's
kind
of
okay,
let's
just
make
sure
no
matter
what
that
you
know
if
you
get
in
quote-unquote
coma,
we
get
out
of
there
now
that
was
put
into
one
since
that
was
put
in.
E
I
believe
I
I
reproduced
the
exact
issue
that
michael
was
seeing
and
fixed
it,
and
that-
and
I
I
have
to
double
check
this,
which
I'll
do
personally,
I
believe
that
was
actually
merged
yesterday
or
day
before
into
a
mandel
maine,
because
it
was
fixed
in
2.0
x,
which
was
just
merged
into
to
man
domain.
E
C
E
E
B
Of
them
kevin
mentioned
has
already
been
merged,
either
yesterday
or
this
morning,
and
so
that
would
already
be
in
because
that
comes
from
2.0.
Everything
else
would
go
if,
as
long
as
as
long
as
it
is
properly
logged,
then
they
would
be
able
to
emerge
in
3.1
great,
which
does
give
us
time
so
again.
Those
dates
when
the
engineers
start
will
be
april,
6th
and
april
11th.
A
B
Yes-
and
that
was
already
done-
and
essentially
now
it's
being
reviewed
and
merged
and
which
should
happen
either
by
the
end
of
this
week
or
early
next
week,
and
then
once
that's
done,
then
fractally
teams
is
done
with
their
part
done
with
their
part.
Sorry,
if
there
are
issues
with
the
work
that
they've
done
then
a
stand,
for
example,
please
keep
reviewing,
they
will
continue,
maintaining
the
work
that
they've
done,
but
they
will
no
longer
add
functionality
into
it
or
continue
merging
new
functions.
So
it.
A
I'm
sure
matthews
matthew
is
going
to
be
testing
on
the
diffuse
stuff
as
soon
as
it's
available,
I'm
sure-
and
so
maybe
we
can
talk
about
that
next,
the
anything
else
to
add
on
this
topic
before
we,
maybe
we
can
revisit
the
testing
strategy.
A
A
B
B
A
F
G
Look
I'm
from
the
phone
now
there's
no
branch,
at
least
in
the
manual
repo
there's
no
tag,
no.
A
We
can
add
a
dot
later
if
we
need
to
yeah.
Okay,
we're
I
haven't
stan,
have
you
registered
on
jungle
yet
and
do
we
have
anyone
from
us.
B
A
C
The
record
I
work
with
costa
rica
all
the
time
I
work
with
costa
rica
all
the
time
they
are
aware
of.
What's
going
on,
they
were
registered.
I
think
they
had
some
server
issues
and
they're
spinning
it
back
up
and
getting
going,
and
I'm
relaying
cliff
notes
of
we're
on
2.0.13
and
then
go
into
whatever
version
we
decided
to
at
the
time.
So
I
don't
know
whether
they're
on
the
call-
and
I
know
they
aren't
on
telegram
as
much
but
I'll
be
happy
to
relay
like
say
I
talk
to
them
all
the
time.
Great
appreciate.
B
That
yeah
and
daniel
it
is
el
mato
in.
C
B
A
Great,
thank
you
we'll
reach
out,
okay
and
so
we're
on
track
to
get
these
other
three
go
on.
Anyone
else
on
the
line
here,
who's
got
a
bp.
They
can
register
on
jungle
as
well.
Do
you.
B
B
A
Okay,
anything
to
add
on
text-
and
I
can
give
a
quick
update
on
kylin
loudmouth-
has
committed
to
they're
going
to
be
re-enabling
their
faucet.
I
don't
know
the
current
status,
whether
that's
happened
yet
or
not,
but
I
did
receive
a
confirmation
for
their
team
that
they're
happy
to
re-enable
that
for
us.
B
A
H
A
A
H
A
We
can
let's
check
in
offline
you
and
me
denny
and
I'll
check,
follow
up
again
with
kailyn
on
on
or
with
flaumau
and
what
their
status
is.
Maybe
they're
already
almost
done
so
yeah
might
not
be
necessary.
What
else
we
got
any
progress
to
report
stan
on
any
of
the
materials
right
either
around
the
survey
or
the
developer,
documentation.
A
A
B
So
those
are
issues
just
to
confirm
because
the
issues
you
opened
were
also
issues
from
not
issues
with
that
repo
itself
or
with
the
code
itself.
It
was
issues
from
hey.
You
didn't
add
this.
You
didn't
add
this,
but
from
the
code
that
was
written
or
the
code
that
was
merged,
did
you
find
any
issues
and
were
those
addressed
or
are
those
being
addressed?
Yes,
yes,
there's
one
one
issue
that
since.
F
F
F
A
A
All
right
last
week
we
talked
about
the
mono
repo,
I
don't
think,
there's
probably
anything
to
discuss.
Today
we
put
out
a
call
to
action
to
the
community.
I
think
anyone
has
to
add
on
this
topic.
Perhaps
you
you
weren't
able
to
attend
last
week
and
you
have
some
feedback,
some
ideas
on
how
we
can
get
engagement
from
the
community
to
participate
in
here.
A
Okay,
didn't
think
so,
and
that's
those
are
really
all
the
items
that
that
I
had
in
mind
to
discuss
today.
Is
there
anything
else?
Okay,
in
that
case,
we'll
we'll
give
you
all
back
the
rest
of
the
time
and
see
you
in
a
week
thanks
everybody
and
one
clear
thing.
I
just
want
to
thank
stephen
ford.
His
peer
reviews,
they've
been
very
helpful,
appreciated
his
time
there.