►
From YouTube: ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 October 15, 2018
Description
A
It's
really
nice
to
see
you
all
note
taker
is
Jacob.
He's
already
put
his
name
down.
That's
fabulous
called
put
your
name
on
your
attendees
list.
If
you
haven't
already
and
weekly
updates
showing
so
I
might
as
well
start
do
full.
So
last
week
was
the
protocol
lab
week,
and
it
was
the
awesome
I.
Just
put
a
couple
of
links
to
talks.
I
gave
that
whilst
there
in
case
you
were
interested
I
today
released
JSI,
BFS
API
version
25
and
that
has
got
a
fix.
A
A
So
what
else
I
created
a
release
issue
for
Jess
IVFs
0.33?
The
next
release
will
have
the
new
web
UI,
stuff,
hooray
and
so
there's
gonna
be
fun.
I
talked
to
Holly
this
morning
and
he
is
cool
to
get
that
in
as
soon
as
possible.
So
so,
let's
do
that.
It's
gonna
be
right:
I'm
not
currently
blocked
in
anything
I
am
currently
or
this
week.
I
am
hoping
to
finally
complete
my
CID
base
work
if
other
stuff
doesn't
get
in
the
way.
C
C
That's
like,
after,
like
four
gigs
or
something
it
was
crushing,
can
you
make
sure
to
follow
up
with
them
just
give
them
a
ping
saying:
okay,
like
it's
now
fixed,
also
really
exciting,
that
is
so
Jessica's
getting
the
first,
the
new
web
UI
nice
and
it's
just
people
skating
first,
the
race
duty
to
stuff.
If
you
finish
it
this
week,
well,
I
guess
he
does
still
to
get
released
right.
A
A
B
So
it
was
lab
week
or
last
week
we
made
good
progress
with
Lupita
P
on
our
roadmap,
so
we're
gonna
work
on
a
little
bit
more
and
get
that
published
in
some
stuff
came
up
couple
questions
on
private
networks,
so
I
did
that
on
the
plane.
Ride.
There's
now
a
probably
Network
example,
but
I've
got
a
pull
request
open
to
and
solicit
a
couple
community
members
for
feedback
on
that
that
we're
having
a
hard
time
with
it,
also
working
on
support
for
the
elliptic
curve
keys.
C
D
A
B
So
the
example
shows
how
to
run
two
nodes
that
have
the
same
swarm
key
and
then
there's
like
a
task
in
there,
where
you
can
go
in
and
comment
out,
the
like
one
of
the
swarm
keys
and
changes
so
that
the
nodes
are
running
different,
swarm
keys
and
watch
them
fail
to
connect.
So
this
example
is
how
to
do
that.
Running.
Jsi
BFS,
without,
like
we've,
got
a
change
request
open
in
ipfs
repo
that
we
haven't
really
touched.
B
That's
actually
like
adding
the
ability
to
auto,
detect
and
pull
that
for
JSI
BFS,
but
we
don't
technically
don't
need
any
of
those
changes.
It
just
works
right
now.
A
B
So
that
just
came
up,
there
was
a
issue
about
a
month
ago,
where
somebody
was
looking
for
the
example
and
then
it
came
up
like
it
was
really
Saturday
or
something
where
somebody
was
having
issues
getting
it
running
on
how
and
then
this
addresses
that
in
the
I
don't
know
if
there's
a
GS
ipfs
issue,
I
haven't
seen
that,
but
I
can
take
a
quick
look
and
link
over
that
example.
Cool.
E
So
I
was
also
the
lab
week
and
I
would
say
that
grafting
finally
has
a
design,
so
the
spec
needs
to
be
written,
which
will
be
my
task
I,
which
also
we
didn't
ask
of
the
next
week.
Starting
with
it
then
yeah
we
for
the
lab
week,
I
started
my
phosphor
G
talk,
I
just
need
to
upload
it
just
to
cut
off
my
start,
the
recording,
yeah
and
then
I
yeah
head
also
conversation
with
Ellen.
Today
about
so
darks
Libra
is
changing
api's
and
is
a
way
we
could
change.
F
During
that
time,
I
did
some
minor
requests
to
a
year
about
the
experimental
world
and
a
couple
of
minor
other
things,
and
don't
really
remember,
but
okay,
so
for
the
next
week,
I
will
finally
finish
the
Shanghai
ads
review.
That
Alan
gave
me
and
now
so
I
will
start
making
bundles
smaller
in
meantime,
I'll
continue
doing
their
tests
as
these
take
a
long
time.
I've
in
between
I
have
time
to
do
other
stuff
like
making
the
experimental
real
default
and
on
those
smaller
I
also
would
like
to
show
you
guys
something.
F
F
So
for
the
bundles,
one
of
the
things
that
I'll
be
using
to
show
up
like
progress
and
stuff
would
be
this
tool
bundle
phobia.
As
you
can
see
here,
you
can
track
the
size
of
a
time
as
we
improve
the
size
of
each
of
our
packages.
We
can
use
this
to
to
keep
track
of
the
progress
and
also
I'll
use
another
tool
called
size
limits
that
will
be
configured
in
each
ripple.
That
will
give
the
developers
or
the
maintenance
feedback
about
the
size.
F
F
This
is
basically
the
list
of
all
the
runs.
You
get
a
nice
view
of
the
pipeline.
You
can
retry
each
of
the
steps,
not
all
not
the
not
only
the
state
of
the
complete
stage,
but
each
of
the
steps
you
can
also
do
whatever
we
want.
Basically,
we
can,
as
we
configure
that
pipeline
with
this
file,
we
can
do
stuff
like
checking
out
by
cloning
and
checking
out
all
the
repos
running.
F
The
tests
like
with
a
link
to
this
is
specially
important
for
the
ipfs,
so
we
can
like
test
if
we
don't
break
other
packages
or
other
vehicles.
When
we
do
some
some
kind
of
change,
we
can
do
also
scheduled
pipelines.
That
would
be
useful
for
the
might
be
military
tests
to
run
it
like
weekly
or
daily
or
whatever,
so
it's
pretty
configurable
and
it
works
pretty
well.
This
is
connected
to
the
github
repos
directly.
They
basically
set
up
hooks
and
when
everything
gets
pushed,
they
run
the
pipeline
on
it
live
on
it
lab.
F
A
F
Basically,
this
the
experimental
watching
what
it
does
it's
it's.
The
setup
is
a
little
bit
a
little
bit
simpler
and
the
updates
bubble
and
web
pack
with
new
conflicts
for
each
to
make
the
bundle
smaller
to
make
the
translation
a
a
little
bit
better,
not
by
much
but
just
a
little
bit
and
it's
basically
it.
C
Two
questions
so
the
first
one
on
the
bundle
side
is
pretty
cool
it'll,
be
great
if
it
isn't
required
us
to
girl
to
that
service.
Every
time
it'll
be
great
like
if
there
is
a
CI
hook
that
just
tells
of
every
four
requests.
What
is
it
change?
There's
nothing
necessary
to
make
request
file
if
the
bundle
increases
just
like
something
that
we
can
keep
track
on.
It
keeps
reminding
us
on
the
EITI
super
interesting,
like
I
I've
been
like
longtime
fan
of
people
have
and
how
they
set
up
stuff.
C
Sorry
I
was
just
asking
everyone
to
give
me
and
so
yeah
so
yeah
give
up,
see
I
love
to
see
if
there
is
issues
open
about
like
deaths,
that
the
that
plan
and
I
just
like
to
get
everyone's
feelings
about
it.
Everyone's
perspective,
no
more
than
killing
there
is
perspective,
but
it
but
yeah
like
thank
you
for
like
just
coming
up
with
that
and
and
developing
a
proof
of
concept
right
now.
I
don't
have
any
technical
observations
other
than
well
nice
looks
cool,
so
Helen.
A
Yeah
just
kind
of
two
things
quickly:
the
but
the
web
UI
is
using
a
service
that
does
do
a
get
hook
for
bundle
size
and
it
keeps
it
to
a
specific
particular
level.
And
if
you
go
over
that,
then
it
will.
It
will
kind
of
flag
it
up.
So
we
could
use
that
and
then
secondly,
a
question
for
the
Hugo.
If
we,
if
with
the
get
lab
stuff,
would
we
also
have
to
remove
or
lock
code
to
get
lab,
or
can
we
run
it
like
as
a
separate
CI
service.
F
So
the
demo
just
did
I
didn't
put
any
cold
on
the
cloud.
It's
all
all
connected
to
the
IP
FST
CTL,
in
a
specific
branch
that
I'm
using
to
test
out
all
this
stuff.
So
the
workflow
would
continue
to
be
exactly
the
same
with
one
exception.
Instead
of
going
to
Jenkins
page
we'll
go
to
the
get
labs,
CI
page,
nothing
more.
When.
G
A
I'd
love
to
see
that
I
think
that
we're
at
cool
any
other
questions
for
Hugo.
C
The
vision
of
my
PFS
and
I
give
some
tangent
chill
like
some
reality,
but
milestones
like
something
that
we
can
I
understand
what
we
need
to
do
in
order
to
reach
what
is
the
vision,
and
so
me
and
Molly
are
working
on
that
document.
Our
hopes
is
to
have
a
version
by
the
end
of
this
week
that
we
can
send
to
you
all
for
you
to
pull
requests
against
and
so
like
it's
more
Yuri
into
the
oxy.
C
The
all
of
these
artifacts
will
be
public
for
the
internet
profess
community.
We
are
just
like
getting
the
first
versions
over
a
Google
Doc,
because
the
the
experience
of
like
anything
there
is
like
fessor
buttock,
wants
to
feel
that
is
ready
to
share.
We
were
just
like
do
a
request
on
a
repo
cultural
map
and
welcome
everyone
in
and
so
yeah.
That
is
like
my
core
focus
right
now.
My
secondary
focus
is
I'm
spending
some
time
with
a
girl
team,
and
so
they
are
now
also
figuring
out
their
own
priorities.
C
E
C
Data
set
etc,
to
like
kind
of
like
dictates
whether
we
don't
like
the
performance
improvements.
If
we
need
to
get
ready
and
then
also
like
there
is
a
big
conversation,
and
it
is
something
that,
like
we
also
need
to
have
a
conversation
about,
is
to
make
sure
that
the
maturity
and
the
stability
of
the
project
gets
proven
by
benchmarks
and
tested
and
so
like.
When
we
say
we
can
trust
for
a
one
terabyte
file.
It
should
not
just
be
like
someone
tried
on
their
machine
one
time.
C
It
should
be
something
that
is
repeatable
and
something
that
will
give
confidence
to
all
of
our
users,
that
the
machine
is
ready
and
so
and
also
like,
even
like
an
a
byproduct
of
that
is.
When
you
create
those
testing
our
messes
and
benchmark,
you
suddenly
open
the
door
to
all
of
the
networking
peer
to
peer
performance
experts
to
have
a
playground
for
them
to
like
test
their
ideas
and
test
their
expertise
and
really
I.
C
Take
part
on
the
project
right
now,
just
hard
for
people
that
are
experienced
on
like
markets
to
come
to
beat,
swap
and
like
help
us
I
figure
out.
What
is
the
best
strategy
for
get
swap
or
for
DHT
or
etc,
and
so
getting
a
bunch
of
benchmark
and
I
know
that
this
team
is
working
on
the
monetary
test
that
so
that's
going
to
be
great?
C
Getting
those
things
finalized
this
quarter
will
be
like
will
yield
a
ton
of
returns
for
next
year,
because
then
we
can
open
the
the
playground
for
everyone
else
so
and
I
could
part
of
this
conversation
is
also
like
lovely
optical
team
to
have
better
coordination
in
a
way
that
it
is
inclusive
of
other
teams.
So
that's
if
of
course,
I
can
like
communicate,
needs
that
the
Jazz
team
can
like
understand.
D
C
D
A
Yeah
I
mean
the
guy.
The
guy
PFS
team
kind
of
communication
is
already
so
much
better,
like
I'm
already
I
already
get
like
pings
from
Steven
when
he
feels
there's
something
that
I
should
know
about.
Like
oh
I,
guess
issues
and
that's
just
like.
Even
if
it's
just
ping
me,
then
the
nuts
that
it's
just
a
big
step
in
the
right
direction.
So
I'm
super
happy
with
that.
So
yeah
I'm,
seeing
all
this
good
stuff
gonna
start
to
pay
off
at
least
so.
A
Rad
very
excited
and
yeah,
like
I,
totally
agree
on
the
benchmark
stuff
and
having
I
think
having
that
just
like
that
bundle.
Phobia
thing
where
you
can
have
like
a
this
version.
Was
this
slow
playground
where
you
can
kind
of
see
what
what
what
differences
you're
actually
making
each
version
would
be.
Yeah
super
useful,
so
yeah
totally
aligned
on
that
and
absolutely
hoping
to
make
progress
on
on
that
front.
This
quarter
well
we're
totally
on
time,
so
we
should
get
off
this
call.
Does
anyone
have
any
final
thoughts,
or
can
we
just
go
all
right?