►
From YouTube: IPFS in Web Browsers 2019-Q2 OKRs
Description
@autonome give a quick update on 2019-Q2 OKRs for the IPFS in Web Browsers working group!
https://docs.google.com/spreadsheets/d/1YSeyWqXh3ImanRrTkYQHHkCofiORn68bYqM_KTLBlsA/edit#gid=1681757723
https://github.com/ipfs/in-web-browsers
A
Never
see
right
now
it
was
a
jump
that
I,
oh
hey,
you're,
here,
welcome,
let's
get
started:
I
am
Dietrich
Ayala
and
I'm,
a
member
of
the
web
browsers
working
group
to
my
PFS
project
and
today
I'm
going
to
talk
to
you
for
a
couple
of
minutes
about
the
priorities
that
we
have
for
q2
2009
team,
starting.
Our
immediate
priority
is
to
support
ipfs
camp
and
events
happening
in
june
and
barcelona,
where
a
bunch
of
people
are
going
to
come
and
learn
about
how
to
sell,
adopt
and
accelerate
ipfs.
A
We
need
to
figure
out
what
we're
gonna
teach
them.
So
there
are
core
courses,
and
this
working
group
has
taken
on
what
are
the
core
courses,
which
is
about
developing
apps
for
ipfs,
so
introduction
to
how
to
develop
and
ship
web
and
other
applications?
Well,
the
tooling,
workflow,
etc.
We've
also
adopted
a
second
course,
which
is
an
elective
course,
so
some
people
can
take
a
little
deeper
into
the
workflow
and
intricacies
of
building
websites
and
publishing
them
ipfs.
A
That
second,
okay,
are
for.
The
group
is
in
support
of
an
annual
2019
priority,
which
is
building
package
managers
with
ipfs
and
encouraging
package
manager.
Adoption
of
my
PFS
for
distribution,
the
p0
for
the
group
in
this
area
of
work,
is
to
reduce
IPS
resolve
times
so
right
now,
my
penis
can
take
from
what
I
hear
up
to
four
minutes,
sometimes
to
resolve
and
I
taught
a
demo
today,
slowly
taking
a
minute
or
so
so
things
are
getting
better.
A
But
the
goal
for
the
work
that
this
team
is
doing
and
in
conjunction
with
some
of
the
other
working
groups
that
are
also
working
on
improving
IPS,
is
to
reduce
result
time
down
to
10
seconds
or
less
in
browser
contexts.
We
also
have
an
another
lower
priority
goal:
to
do
a
little
bit
of
experimentation
with
web-based.
A
Module
loaders
like
I'm
packaged,
but
that
is
the
primary
goal,
is
to
support
the
IPS
performance
work
which
all
support
not
only
the
package,
vanity
Bowl,
but
a
bunch
of
other
projects
as
well.
The
third
objective
is
one
that's
kind
of
ongoing
for
this
group,
which
is
to
reduce
surprises
for
web
developers,
so
we
reworked
the
language
on
this
objective,
a
bit
at
the
Lisbon
planning
session
last
week
to
encompass
kind
of
what
to
just
better
describe
what
the
actual
goal
there
is
to
support
adoption
by
web
developers.
A
We
know
how
many
peas
zeroes
this
quarter
for
this
trading
instead
for
supporting
package
manager
and
my
PFS
camp
worked,
but
some
of
the
things
are
around
getting
ipfs
GSM
I've
asked
people
to
work
in
ways
that
web
developers
would
expected
to
with
the
tools
and
frameworks
that
they're
using
things
like
view,
things
like
module
resolution
and
the
fourth
objective
is
another
new
one.
So
this
is
the
companion
I
profess
companion
can
support
archiving
of
web
content.
A
The
longer
term
goal
from
a
user
first
facing
perspective
is
around
some
primary
use,
cases
that
that
people
want
to
do
and
can
do
with
ipfs
in
the
browser
and
saving
and
archiving
of
content
that
they
experienced
and
seeing
the
browser
sharing
that
same
content,
and
it
was
also
publishing
new
content.
So
those
are
the
three
primary
use
cases
we
identified
from
a
user
facing
standpoint
tasks
that
people
want
to
do
when
they
have
access
to
a
I
profess,
capable
browser.
A
The
next
objective
is
also
an
ongoing
one
for
this
working
group,
which
is
the
browser,
is
our
browser.
Vendors
are
integrating
ipfs
and
shipping
it.
The
immediate
priority
from
me
as
being
new
to
the
group
is
to
again
do
it
a
little
bit
of
work
to
articulate
what
the
overarching
strategy
is
there
and
how
we're
gonna,
how
we're
gonna
get
there?
What
why
do
we
want
browsers
to
integrate
that
give
us?
How
do
we
want
that
to
happen?
A
The
final
objective
for
the
group
is
also
a
not
a
p0
crazy
high
priority,
but
an
ongoing
bit
of
work
around
identifying
alternative
environments
that
are
web.
Like
use
web
standards
use
web
web
stack
technologies,
but
maybe
aren't
a
browser
per
se,
so
we
have
a
p1
where
we
want
to
be
able
to
identify
what
needs
do.
What
changes
need
to
be
able
to
make?
We
need
to
make
NGS
I
profess,
to
be
able
to
work
in
electron,
apps,
better
and
better
support.
A
Desktop
app
developers
are
using
that
web
platform
stack
be
able
to
build
applications.
So
that's
it
for
q2.
It's
a
lot.
We
did
a
rough
estimation
of
p0
work
and
that
should
fit
into
the
time
that
we
have
for
sure,
and
then
some
of
the
some
of
this
is
also
around.
It
is
about
product
brought
more
broadly
figuring
out
what
we
need
to
do
as
a
working
group
with
the
broader
objective
envision.