►
From YouTube: IPFS All Hands 🙌🏽 📞 Apr 30, 2018
Description
Introducing Mike Goelzer as Product Manager for libp2p and announcing IPFS Summit in Berlin July 2018!
B
Yeah,
thank
you,
and
so
this
is
the
ipfs
all
homes
today
into
the
30th
of
April.
It's
cyclical
where
I
am
up
at
least
so.
We
have
a
note-taker,
we
have
sort
of
the
recording
and
if
you
have
something
that
you
want
to
bring
up,
don't
forget
it
at
it
in
the
agenda.
Otherwise
we
will
not
give
you
so.
The
first
thing
we
will
do
is
that
Matt
is
gonna,
introduce
us
to
someone
new,
ok,.
A
C
Sure,
hello,
everyone,
it's
nice
to
meet
you
all
right,
so
basically,
I
came
to
PL
from
docker
the
container
company
and
basically,
what
I
did
there
was
so
I've
been
doing
open
source
product
management
for
a
long
time
now,
I
at
docker
I
was
a
product
manager
for
what
we
called
docker
core.
It
means
something
a
little
bit
different
from
the
way
PL
uses
that
it
just
basically
referred
to
our
open
source.
C
It
just
all
sort
of
all
of
our
open
source,
and
so
the
main
projects
I
worked
on
were
the
clustering
for
the
docker
engine.
So
docker.
If
you're
not
familiar,
it's
a
it's
a
container
engine,
it's
like
lightweight
virtual
machine
system
and
it
became
very
popular
around
like
2014,
because
it
makes
it
very
easy
to
run
to
sort
of
run,
can
containerized
applications.
But
then
what
we
started
to
discover
was
that
as
people
were
using
it,
they
really
want
to
use
it
on
multiple
machines
and
not
just
in
machines
operating
independently.
C
One
of
them
was
a
product
that
I
built
and
launched
with
a
really
great
engineering
team
at
docker
called
docker
swarm,
and
this
is
a
sub
functionality
that
we
just
built
into
the
docker
engine
so
that
you
could
just
cluster
docker
different
docker
hosts.
You
know
the
different
Linux
boxes,
running
docker,
you
cluster
them
together
very
easily,
and
we
did
a
lot
around
sort
of
make
it
secure
out
of
the
box
like
really
strong
security,
easy
to
use
good
good
overlay.
C
Networking,
which
is
kind
of
makes
it
look
like
all
all
the
machines
are
on
the
same
sort
of
the
VPN.
So
so
we
built
that,
and
then
we
also
did
I
also
worked
a
lot
on
our
kubernetes
strategy,
because
a
lot
of
our
users
wanted
to
use
kubernetes
to
cluster
their
or
their
doctor
engines
together.
So
those
are
sort
of
the
two
main
things
I
work
on
a
docker
and
it
was
a
great
experience.
You
know
I
started
there
in
2018
it
was
a
really
small
company.
C
It
was
like
you
know,
kind
of
I,
don't
want
to
say
chaotic,
because
that
has
a
negative
connotation,
but
you
know
is
like
typical
kind
of
startup,
like
a
million
things
going
on
and
I
try
to
help
them
to
bring
some
order
to
that
and
and
help
us
execute
on
the
things
that
like
really
mattered
and
that's
actually
kind
of
what
I'm
hoping
to
do.
Unlit
p2p
I'll
talk
more
about
that
in
a
minute.
But
yet
that's
basically
my
recent
background
I
mean
big
picture.
I've
been
writing
software
and
managing
software
teams.
C
Since
I
was
in
my
early
20s
actually,
but
since
I
was
19
actually
I've
started
companies,
I've
done
I've
started
a
couple.
Companies
one
was
a
wait
way
way
back
in
the
early
2000s
and
then
another
one
was
a
contract
software
development
shop
that
I
ran
for
a
while
and
so
I
have.
You
know
a
lot
of
experience
in
engineering
management,
product
management.
Obviously,
everyone
a
huge
amount
of
code,
I
love,
low-level
stuff,
I
love
getting
into
the
Linux
kernel,
I,
actually
really
love
the
the
Windows
kernel
too,
which
is
weird
but
I'm.
C
Being
honest
here,
I
think
it's
very
well
designed
it's
a
it's
kind
of.
They
took
a
lot
of
the
best
ideas
from
VMs,
which
is
a
really
ancient
operating
system,
and
you
can,
even
today
you
can
still
see
those
reflected
in
the
design
of
the
Windows
kernel
but
yeah.
So
so
that's
me
I'm
a
product
manager
but
I'm
really,
technically
you
know
engineering
focused
kind
of
guy
I
love
to
get
actually
get
into
the
code,
and
so
that's
you
know
that's
sort
of
what
I'm
that's
kind
of
what
I'm
about.
Is
that
a
helpful
introduction.
C
Yeah,
so
let
me
see
if
I
can
share
my
screen
if
so,
just
I'll,
preface
it
like
this
right
now
live
p2p
is
basically
an
upstream
for
for
ipfs
like
it's
primarily
that
that's
how
we
we
it's
not
really
its
own
project,
it's
sort
of
like
when
we
need
to
do
something
in
ipfs
we
and,
and
it
touches
lit
p2p.
Then
people
open
PRS
against
one
of
the
live
p2p
repost.
Well,
what
I
want
to
do
is
turn
lib
p2p
into
a
real
first
class
project
and
I.
To
me.
C
C
Okay,
hopefully
now
you
can
see
a
Google
spreadsheet,
just
give
me
a
thumbs
up
if
you're,
seeing
it
yeah-
okay,
great
okay.
So
what
I
try
to
do
as
a
starting
point
is
calm
up
with
some
okrs
that
I
want
to
propose
to
this
group
and
then
I'm
gonna,
ask
for
your
feedback,
but
basically
I
think
there's
four
main
goals
on
lid
p2p.
The
first
one
is
turning
it
into
a
dedicated,
creating
a
dedicated
working
group,
and
this
is
what
I'm
saying
about
turning
into
a
first-class
project.
C
Like
you
know,
we
we
set
up
like
a
real
working
group
with
an
unknown
group
of
people
who
want
to
be
members
of
that
working
group
and
then
I
have
some
other
ideas
about,
and
this
I'm
going
to
ask
for
feedback
on
this
in
a
moment.
But
you
know
I
have
some
other
ideas
about
how
we
should
kind
of
structure
things
in
terms
of
should
we
do,
like
wit,
some
kind
of
weekly
call.
C
Should
we
have
some
kind
of
what
I'm
thinking
is
some
kind
of
meta
repo
that
would
track
issues
across
all
of
the
different
implement
language,
implementations,
Olympia
piece
of
some
sort
of
master
place,
or
we
can
go
and
see
everything?
That's
that's
a
github
issue
in
any
of
the
repos
and
you
know,
have
a
roadmap
document,
so
it's
just
stuff
like
that,
so
the
first
best,
the
first
of
all
setting
up
working
group.
C
C
What
I
would
call
the
product
management
goal
like
basically
just
go
out
and
talk
to
people
who
want
to
use
limb,
p2p,
get
get
some
information
from
them
and
like
about
what
their
needs
are
or,
if
they're,
if
they're,
trying
and
failing
to
use
it
in
their
project,
figure
out,
why
they're
failing
and
what
do
we
need
to
do
to
to
fix
it?
The
third
main
goal,
the
one
that's
labeled,
three-
basically
that's
about
promoting
lib
p2p,
so
I
have
this
theory.
C
Yeah,
maybe
I'm
wrong,
but
I
have
a
theory
that
there
are
a
lot
of
people
who
want
to
build
decentralized
applications
and
they're
gonna.
In
the
absence
of
knowledge
about
of
lib
PDP's
existence
and
knowledge
of
its
quality,
and
so
on,
they're,
just
going
to
reinvent
the
wheel,
they're
just
gonna
completely
build
rebuild
their
own
peer-to-peer
primitives.
So
what
I
want
to
do
is
kind
of
promote
lib
p2p
in
the
sense
of
like
put
out
more
information
about
it.
C
You
know
every
every
talk
that
anyone
does
about
lid
p2p,
that's
publicly
posted
I
think
we
should
a
great
those
into
some,
like
you
know,
like
a
like.
The
lid
p2p
website
have
some
good
tutorials
for
developers
who
just
just
want
to
understand
how
to
use
lid
p2p
and
then
the
fourth
excuse
me.
The
fourth
goal
is
a
set
of
this
is
like
the
features
goal,
so
these
are
kind
of
high
priority
features
for
Lib
p2p
right
now.
Some
of
these
are
being
tracked
in
so
like
the
the
Jas
ipfs
team.
C
C
You
know
like
improve
memory
usage,
that's
kind
of
broad
I
could
have
company
encompass
multiple,
you
have
issues,
so
that's
what
I'm
trying
to
do
in
the
in
the
number
four
goal
and
yeah.
So
this
is
kind
of
the
idea
I
have
about
what
what
the
goals
of
lid
p2p
should
be.
Maybe
I
can
make
this
larger
and
it
all
fits
yeah.
So,
okay,
so
that
so
that's
those
are
basically
my
ideas.
C
C
C
C
C
The
second
thing
I
wanted
to
ask
is
what
how
do
people
feel
about
doing
a
like
a
some
kind
of
a
weekly
I?
Don't
want
to
call
it
a
meeting
because
everybody
hates
meetings,
but
what
I'm
thinking
is
either
a
weekly
sync
on
IRC
or
we
could
do
a
weekly
call
like
this.
If
people
prefer
this
kind
of
format,
I,
don't
know
what
folks
participate
in
that
or
what?
What
are
your
thoughts
on
that.
D
C
E
I
would
like
to
do
a
second
Brendan.
Invite
weekly
goes.
You
know
like
the
way
things
are.
Moving
and
little
people
I
mean
they're,
big
chunks
of
work
that
need
to
happen,
and
you
know,
like
I,
don't
know
how
to
like
tightly
mounting
it
with
a
weekly
meeting.
It's
gonna
help
probably
better
start
quickly
and.
E
C
C
C
C
There's
also
this.
Well.
Maybe
this
is
something
we'll
talk
about
in
the
first
meeting.
I
want
to
set
up
some
kind
of
meta
repo
that
or
yet
it
doesn't
even
have
maybe
repos
not
the
right
word.
I
want
to
set
up
some
kind
of
location
the
tracks
across
all
of
the
different
lit
p2p
implemented,
because
there's
multiple
implementations
and
then
many
of
them
like
the
NGO
and
Jas,
have
multiple
repos
and
there's
like
issues
in
those
repos.
So
we
have
a
lot
of
information
and
there's
issues
in
the
main
ipfs
repo.
C
So
we
have
a
lot
of
limb.
P2P
related
issues
spread
across
a
large
number
of
places
and
I
want
to
try
to
aggregate
those
somewhere.
I've
heard
some
votes
for
waffle,
I've
heard
some
votes
for
Zen
hub
I'm,
personally
kind
of
tool
agnostic,
but
I'd
like
to
get
something
like
that
set
up.
I
think
would
just
be
helpful
to
have
a
global
view
of
the
project.
Yeah,
okay,
but
I
think
that
the
specific
details
of
how
we
do
that
is
something
I
think
we
could
discuss
in
the
first.
C
The
last
thing
is,
and
and
again
I
might
I'm
thinking
it
might
be
better
to
push
this
to
the
sink
chat
with
just
the
people
who
are
interested
but
I'd,
like
some
feedback
on
what
I
put
there
and
number
four
as
some
of
those
future
goals
like.
Is
that
really
capturing
the
most
important
things
is
it
like?
Is
it
missing
things?
C
C
C
C
Yeah
yeah
no
I
I
see
what
you
mean
yeah.
It's
tough,
because
there's
different
types
of
issues
like
some
issues,
are
kind
of
big
picture.
Like
the
you
know,
design
proposal,
but
some
issues
are
like
very
specific
to
to
to
a
particular
repo.
So
there
is
a
case
for
putting
issues
in
in
in
a
repo
and
yeah
yeah,
but
but
I
hear
you
I
think
it's
a
good
point.
C
A
Yeah
more
excitement,
so
some
of
you
already
know
about
this.
We
are
now
ready
to
announce
that
in
early
July
we
will
be
hosting
a
live,
Peter
Peter.
Sorry,
an
ipfs
summit
which
will
be
three
days
followed
by
a
live
peter
peace
summit,
which
will
be
one
day,
and
these
will
be
in
berlin,
probably
in
the
second
week
of
July
the
goal
of
these
so
Matt,
oh
yeah,
you.
A
A
I
were
aiming
for
these,
as
I
said
the
second
week
of
July
in
Berlin,
and
these
are
meant
to
be
focused
working
meetings
where
all
of
the
attendees
are
active
contributors
to
IPO,
ipfs
or
people
who
are
very
actively
building
stuff
on
ipfs.
So
it's
it's
a
working
meeting
with
a
high
amount
of
context
required
for
the
participants,
and
that
will
be
a
precursor
to
ipfs
comp
which
we're
aiming
to
do
in
November
in
Lisbon.
K
A
The
Lib
Peter
peace
summit,
the
main
thing
to
know
about
the
summit-
is
that
it's
invitation
only
so
you
have
to
ask
to
be
invited
because
we
are
requiring
you
have
to.
You
have
to
be
actively
involved
in
order
to
attend.
You
have
to
be
actively
contributing
or
either
either
contributing
code
directly
to
the
code
bases
or
contributing
in
the
form
of
using
this.
This
using
the
software
really
proactively
and
contributing
in
the
conversations
that
are
steering
our
strategy
and
our
decisions
about
how
to
how
to
navigate
the
future
for
these
these
projects.
A
So
what
we
will
be
doing
with,
like
one
rule
of
thumb
for
right
now,
if
you
aren't
on,
if
you're
reflected
on
any
of
the
okay,
are
spreadsheets
you're
going
to
be
welcome
at
this
summit.
So
for
that's,
the
majority
of
the
people
who
are
in
these
balls
have
have
asked
at
least
1k
are
somewhere
on
those
sheets,
but
for
everyone
else,
we're
going
to
be
creating
on
will
have
a
rubric
for
like
the
people
who
are
automatically
included.
A
So,
for
example,
if
you're
contributing
code
to
the
code
base,
you're
automatically
welcome,
but
we're
also
going
to
create
a
public
IP
FS
users
registry,
that
will
let
people
register
their
themselves
and
their
projects
as
users
of
ipfs
and
tell
the
world
about
your
project.
But
we
will
also
use
that
as
part
of
the
rubric
for
deciding
who's
who
is
able
to
attend
the
summit.
A
A
A
So
it's
going
to
be
like
a
working
meeting,
so
in
the
lead
up.
The
main
thing
that
europa
doing
is
proposing
sessions
which
will
will
solicit
proposals
over
the
coming
weeks
for
people
proposing
sessions
that
they
want
how
to
have
or
presentations
that
they
want
to
have.
In
the
first
day,
people
are
going
to
give
lightning
talks
about
the
projects
that
they've
been
about
the
various
projects
that
they've
been
working
on,
so
those
would
be
like
rapid-fire
updates
on
all
the
different
projects.
A
So,
if
you've
been
working
on
specific
projects,
you'll
be
giving
a
lightning
talk,
but
then
it's
also
the
all.
These
working
groups
will
be
meeting
and
they
will
be
having
face-to-face
meetings
where
they're
planning
the
next
three
to
six
to
twelve
months
of
their
work,
and
so
the
main
preparation
that
you
can
do
there
is
getting
involved
in
the
working
groups
and
getting
involved
in
the
planning
so
that
you,
you
have
as
much
planning
done
in
advance
asynchronously
before
you
arrive,
so
you
can
make
the
most
of
the
time
when
you're
face
to
face.
A
So
that's
yeah.
So
they
answer
your
question.
It's
if
you've
been
doing
work
that
should
be
giving
an
update,
be
like
prepare
to
give
a
lightning
talk
if
there's
sessions
you
want
us
to
have
at
the
meeting,
be
what
you
should
propose
their
sessions
when
we
float
requests
for
proposals
for
sessions
which
you
might
end
up
running,
if
you
proposed
it
and
then
also
be
prepared
to
be
doing
working
meetings
with
the
working
groups
so
get
involved
with
the
working
groups.
A
The
other
thing
to
flag
is
that
the
lib
p2p
someone's
gonna
be
a
lot
smaller
than
the
ipfs
one
so
where
there
are
a
lot
of
people
who
totally
belong
at
an
IP
FS
working
summit
who
just
aren't
actively
involved
in
the
p2p.
And
so
we
will
narrow
down
the
the
group
so
that
further
for
the
lib
p2p
meeting,
so
that
that
meeting
can
stay
focused
and
not
not
have
a
lot
of
people
who
are
kind
of
interested
and
they
care,
but
aren't
actively
involved
in
the
implementation
decisions.
A
And,
if
that's
all,
then
that
was
the
announcement
of
people.
We're
really
excited
to
be
doing
this.
This
will
be
the
first
time
of
having
a
majority
of
ipfs
contributors
and
users,
a
majority
of
contributors
and
a
critical
mass
of
contributors
all
physically
in
the
same
place,
together
the
closest
we've
gotten
to
that
so
far
was
2016.
We
had
a
workshop
in
Lisbon,
but
that
was
actually
sort
of.
It
was
actually
a
pretty
small
subset
of
the
ipfs
users
out
there.
Even
then,
so
this
is
really
exciting
to
get
everyone
together.
L
L
It
really
clearly
communicated
both
of
those
things
to
make
it
really
clear
that
a
repo
is
is
dead,
and
you
should
go
find
information
about
that
stuff
where
else
or
understand
that
that
tool
or
library
is
no
longer
supported,
no
longer
actively
used.
So
it's
mostly
right
now
focused
on
things
are
like
naming
and
what
we
need
to
make
sure
a
labels
on
and
that
kind
of
stuff.
L
L
Then
the
other
one
I
mentioned
in
there
is
that
there's
a
PR
for
kind
of
a
standardized
licensing
policy,
because
in
a
similar
sense,
there's
a
lot
of
different
ways
that
all
the
various
repos
are
licensed
and
a
for
sanity's
sake.
It
should
be
a
little
bit
more
standardized,
but
especially
for
people
who
are
making
use
of
them.
It
should
be
standardized
and
clear
things
that
are
ipfs
relations
to
a
certain
way.
So
there's
a
PR.
Please
check
that
out.
H
I
am
oh
yeah.
We
have
a
release
candidate
out
for
a
4:15,
not
rc1,
go
try
it.
Probably
it's
looking
pretty
clean.
So
far,
there's
not
too
much
to
do
here,
probably
just
going
to
shift
that
in
a
couple
days
officially
and
then
move
on
to
oh
six.
Oh
four,
sixteen
which
is
going
to
be
pretty
big
release
because
we're
gonna
be
trying
to
get
some
pretty
significant.
Limpy
tupiri
factors
in
or
rather
I
should
say.
Steven
is
going
to
be
trying
to
get
some
really
important.
H
Lupita
period
factors
in
it's
gonna
be
great
beyond
we
have
a
bunch
of
other
updates
that
have
been
waiting
to
go
through
for
a
while
some
stuff.
In
the
go
data
store
package,
that's
gonna
make
cluster
more
performant
and
some
other
fun
stuff.
That
just
generally
makes
things
nicer,
anything
specific
Steven.
You
wanted
to
bring
up
cool.
B
H
H
B
H
H
E
We
don't
put
enough
values
on
the
DHD
so
that
all
the
resolutions
for
IB
NS,
which
are
trying
to
resolve
to
collect
at
least
16
nodes,
16
values
before
making
a
determination
for
the
best
record
for
timing
out.
So
that
was
the
tipping
point
that
led
down
a
rabbit
hole
and
after
some
you
know
like
work
with
Jeremy
over
the
weekend.
E
So
we've
finally
found
the
smoking
gun
so
we're
at
a
crawler,
and
it
seems
that
61%
of
our
PhDs
and
vegetable
and
drink
she
have
lots
of
dial
data
and
we're
still
working
the
crawler
to
collect
poor
data.
But
the
thing
is
that
this
imagery
Israel
would
be
pushing
forward
for
integrated
relays
into
or
network
infrastructure.
So
that's
the
heads
up
that
I
want
to
bring
up,
so
the
people
are
aware
that
we
have
this
really
big
issue.
And
if
you
share
ideas
on
how
to
approach
it
and
want
to
contribute
just
speak
out
a.
A
E
No,
it
means
these
are
nodes,
we
cannot
dial,
so
these
are
regular
dates,
the
nodes
which
are
reported
by
other
days.
You
know
to
connect
to
that
and
we
cannot
tell
them
so
they're
unreachable,
so
there
are
active
in
the
DHT,
and
you
know,
like
your
notes
that
are
connected
to
them.
Are
posting
values
to
them?
But
anybody
else
who
is
doing
a
resolution
cannot
actually
reach
them.
J
J
E
So
it's
a
little
more
complicated
by
that.
So
first
of
all,
two
can
be
multiple
records
on
the
Dec
in
different
places
and
there
could
be
records
published
by
multiple
entities
that
possess
the
same
the
same
key.
So
what
we
want
to
do
is
that
we
want
to
be
able
to
retrieve
the
best
record,
which
is
the
latest
record
that
it's
been
published
and
on
the
same
time
we
want
to
defend
against
the
clips
attacked.
E
E
It
seemed
like
a
good
value
right
and
we're
publishing
we're
pushing
220
doubts,
let's
rate
from
16,
that's
80%
quorum,
that's
pretty
pretty
hard
to
fake,
but
turns
out
that
if
you
cannot
connect
to
60%
of
those
you're
not
going
to
get
this
quorum
and
simply
going
to
timeout
everywhere
and
have
abysmal,
slow,
IP
NS.
As
a
result.
I
E
This
so
this
was
a
fair
hypothesis.
I
was
formulating
because
we
had
seen
some
increase
in
issues
from
Chinese
users,
so
the
browser
signs
early
signs
for
adoption
there,
but
I
haven't
confirmed
this
hypothesis.
I
haven't
done
a
full
analysis,
but
I
mean
all
the
notion
of
singer
either
ripe
or
so
there
they're
not
genomic.
A
big
note.
B
A
A
Let's
get
sign
out
from
at
least
three
of
the
working
group
captains
as
a
signal
that
is
ready
for
like
a
final
review
in
a
March.
So
if
you
are
a
working
group
captain,
please
read
both
of
those
RFC's
and
comment.
The
first
one
seems
pretty
much
ready
to
merge.
The
second
one
definitely
read
it
and
give
comments.
We
we
come
it's
passable,
but
we
can
probably
make
it
better.
A
The
one
key
thing
to
pay
attention
to
is
that
it's
making
this
distinction
between
teams
and
working
groups
and
so
pay
attention
to
that
team's
being
a
focused
team
of
three
to
ten
people.
That's
trying
to
be
a
small
focus
team
that
has
people
focusing
full-time
on
building
a
product
or
a
service
versus
working
groups
who
exists
as
a
like.
They
provide
supports
multiple
teams
or
provide
a
way
from
multiple
teams
to
coordinate
with
each
other,
and
so
this
is
different
from
the
way
we've
used.
A
A
K
Cool,
so
one
of
the
things
that
we've
these
last
week
was
actually
creating
a
protocol
to
a
fleet
meant
a
nurse
for
the
GP
fest
module
microsystem,
like
people
have
been
reporting
like
we're.
Having
trouble
just
like
getting
things
merged,
editing
is
reviewed
because,
after
all,
there
was
a
huge
one
like
me
to
review
everything
and
to
release
all
the
dependencies
and,
although
well
I,
just
try
to
everyone's
on
time
like
the
realities.
K
I
just
cannot
and
there's
a
lot
of
people
excited
too
tribute
with
that
time
and
attention
in
rigor
to
make
sure
that
the
packages
are
always
up-to-date
and
released
and
merged
and
evolves
always
little
edit
features,
and
so
with
that,
we
we
first
like
created
an
issue
like
I
posted,
both
links
area
for
the
issues.
Just
like
raising
the
problem.
Just
like
saying
that
we
are
going
to
move
forward
this
and
then
we
updated
the
GS
codes
contributing
guidelines.
K
But
again
they
go
all
continues
to
be
empowering
and
encouraging
more
people
to
like
take
ownership
over
certain
parts
of
the
project
and
just
I
also
recognize,
because
a
lot
of
people
were
already
doing
at
work.
So
it's
better
just
like
to
have
a
way
to
give
the
positions
to
give
the
publish
access
to
do
to
give
that
authority.
K
K
Be
tough,
like
you,
don't
have
to
like
bring
extra
cooling
to
ask
for
the
future,
and
so
as
we
go
through
all
these
packages,
which
are
a
lot
and
like,
as
we
add,
the
wind
maintainer
Rimi,
we
are
also
setting,
like
the
write
permission,
giving
the
write,
publish
access
like
and
yeah
like
this
reading
the
ownership,
so
people
like
seem
to
be
very
excited
like
there
was
a
lot
of
positive
feedback
on
the
PR
itself.
If
people
have
comments
now,
questions
comes
up.
It's
also
welcome.
K
B
Any
any
questions
alright,
so
this
was
or
not
agenda
point
then,
which
one
time
demo
that
has
been
pre-recorded
from
Alan
about
IP
le
explorers
CLI
tools.
So
there
is
a
there
is
a
YouTube
video
you
can
check
out
or
how
the
tour
is
working.
There
is
a
link
to
the
github
repo
and
probably,
if
you
try
out
the
tool,
you
will
have
lots
of
ideas
what
it
should
do,
what
I
shouldn't
do
and
then
you
can
go
to
github
issues
and
write
your
thoughts
there.
B
K
Being
what
week
on
that
note,
we
actually
don't
have
ten
more
minutes
like
want
the
issue
to
reduce
the
meeting
time
from
60
to
30,
since
we
kind
of
like
still
on
at
1:00
I
just
went
ahead
and
reduce
it
to
45.
So
we
are
now
two
minutes
above
the
meeting
like
if
you
check
the
calendar,
it
was
updated
as
well
at
school
register,
be
better
all.