►
From YouTube: A month in PL EngRes IPFS Development and how you can be involved - @biglep - Project & Community
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Thanks
a
lot
for
joining
this
talk,
you
just
want
to
dig
into
what
a
month
of
development
looks
like
for
the
ipfs
team
within
protocol
labs
engineering,
research
group.
So
thanks
for
letting
me
have
the
chance
to
talk-
and
hopefully
this
gives
a
little
bit
of
insight
into
what
we've
been
up
to
and
maybe
how
you
can
get
involved,
or
at
least
what
to
expect
from
us.
So
a
little
about
me,
I'm
steve
lefke
go
by
big
lap
on
on
github.
Some
people
have
asked
that
is
a
nickname
acquired
in
high
school.
A
I
had
a
10
inch
growth
spurt
near
the
end
of
high
school.
I
was
a
late
bloomer,
and
so
it
has
stuck
so
that
that's
where
that
comes
from
on
the
team,
I'm
on
kind
of
the
group,
that's
less
focused
on
file
coin.
This
is
projects
like
itfs,
the
p2p
and
ipld,
and
get
to
be
an
engineering
manager
on
that
team,
and
so
a
lot
of
that
is
just
being
an
encourager
and
wingman
to
the
amazing
people.
A
We
have
and
empowering
our
engineers
to
do
as
much
and
as
awesome
software
development
as
they
can
quick
fun
fact.
I
was
going
to
talk
with
some
people
about
this
at
dinner.
The
other
day
best
purchase
of
the
year
was
a
tandem
bike.
I
was
able
to
get
my
two
two
kids
on
that,
so
they
love
biking
with
me
now,
which
is
great
and
that's
the
preferred
way
to
get
to
school.
So
that's
what
I'll
say.
There's
a
little
thing.
A
I
live
in
seattle,
but
was
born
in
canada,
my
view
of
the
promised
land,
and
so
when
the
olympics
are
on.
We
bleed
maple
leafs.
So
anyway,
as
as
to
this
talk,
I
really
just
want
to
give
visibility
into
what
the
team
is
up
to,
as
I
said,
and
how
we
function,
you
know
if
you
go
through
the
ipfs
or
sorry
I
should
say:
yeah
ipfs,
github
archives,
there's
like
great
docs
in
the
past
of
like
how
the
team
operates,
the
working
groups
etc.
A
We're
trying
to
get
back
to
some
of
that.
So
this
talk
is
you
know
to
step
in
that
direction
and
partly
just
using
as
a
forcing
function
for
myself
and
the
rest
of
the
team
to
document
a
bunch
of
things
that
just
hadn't
been
documented.
So,
thanks
for
letting
me
do
that
in
terms
of
the
team
itself
on
the
go
and
kubo
side,
you've
probably
seen
a
lot
of
those
folks
they're
they're
here
and
have
been
presenting
dean
gus
antonio
and
dropo.
A
You
know
lydle
wears
many
hats,
certainly
on
the
go
side,
but
also
helping
steward
a
lot
of
our.
You
know
gui
tools,
but
getting
some
of
that
passed
off
to
russell
and
henrik
or
hectius
also
helps
with
that
and,
of
course,
there's
alex
taking
brain
who
carries
a
lot
on
the
javascript
and
currently
that
that's
that's
the
team
of
wonderful
folks
in
terms
of
what
we
do.
A
We,
we
spend
a
lot
of
our
time,
attempting
to
empower
others
to
develop
their
own
ipfs,
implementations
and
applications,
and
certainly
then,
as
part
of
that,
we
maintain
our
own
implementations
like
kubo
and
js-type
pfs,
so
that
the
advice
that
we're
giving
or
our
judgments
in
design
decisions
can
really
be
grounded
and
then
also
test
it
out.
So
that's
that's
not
going
to
change.
That's
that's
important,
some
things
that
define
us.
A
A
Some
of
our
values-
and
these
are
definitely
still
in
progress
in
actualizing
them.
You
know
what
lydell
talked
about
earlier
in
terms
of
being
specs.
First,
like
we're,
throwing
all
of
our
weight
behind
that,
and
we
hope
that
the
rest
of
community
will
as
well.
You
know
we
do
get
asked
a
lot
of
questions
in
different
places
working
on
this,
but
really
trying
to
respond
more
with
urls
than
more
text
blobs,
so
that
things
can
scale
and
be
more
reusable.
A
I'll
dig
into
this
a
little
bit
more,
but
this
is
kind
of
what
the
team's
monthly
rhythm
looks
like.
So
the
items
on
the
top
kind
of
happen,
weekly
items
in
the
second
row
kind
of
happen,
bi-weekly
and
there's
some
monthly
stuff
as
well.
So
specifically,
what
those
things
are.
We've
got
various
levels
of
thinking
that
happens
across
the
team,
so
the
the
stewards
team
of
ipfs,
the
p2p
and
ipld.
A
We
do
gather
synchronously
once
a
week,
some
of
that's
just
dealing
with
some
logistics,
but
it's
also
our
chance
to
talk
about
things
that
are
affecting
the
whole
stack.
The
kubo
team
specifically
does
do
stand-ups
twice
a
week.
Well,
we
have
we're
fortunate
to
get
to
the
ips.
Partridge
is
fortunate
to
meet
with
juan
once
every
two
weeks
and
that's
partly
a
chance
for
us
to
bring
things
to
him,
but
also
you
know
juan
is
getting
to
talk
with
different
folks
and
be
exposed
to
different
people.
A
That's
a
chance
to
get
input
from
him
or
to
get
a
digest
of
things.
He's
seeing
one
effort
that
we're
particularly
excited
about
that
has
been
going
on
the
last
few
months
is
the
implementers
think
this
happens
every
two
weeks.
It's
intended
for
a
lot
of
folks
in
this
audience
of
anyone
who's
doing
an
ipfs
implementation
where
we
get
to
talk
about
cross-cutting
concerns,
get
questions
answered
and
you
know
and
come
together.
So
you
know.
Certainly
avengers
group
has
been
there,
but
iro
has
been
there.
A
You
know
dag
host
and
elastic
provider.
They've
folks
they've
been
there
and
again
anyone
else.
Just
wanting
to
do
an
iphone
implementation.
We'd
love
to
have
you
show
up
again:
it's
not
the
place
to
come,
get
general
ipfs
help,
but
if
you
want
to
talk
about
spec
things
etc,
a
good
place
to
come,
and
also
you
know,
outer
core
team,
which
is
doing
an
amazing
job
engaging
with
the
community
collabs.
We
do
get
to
sync
up
with
them
and
get
a
you
know.
A
You
know
see
if
there
are
key
things
that
we
can
help
work
on
together
in
terms
of
reporting
out
like
a
lot
of
the
andreas
teams,
we
do
have
a
weekly
sit
rep.
Basically
our
status
report.
That's
all
public,
it's
kind
of
broken
down
by
different
work
tracks
in
terms
of
what
happened
last
week
and
what's
happening
next
week
and
some
of
what's
coming
and
as
part
of
benj
rez,
there
is
a
monthly
public
all
hands
that
people
can
engage
in
you
know
fridays,
for
us
is
really
kind
of
like
github
day.
A
In
terms
of
looking.
You
know
triaging
all
the
js
ipfs
issues
and
kubo
issues
that
come
in
you
know,
monday
through
thursday,
is
primarily
worked.
Sorry,
we
primarily
focus
on
some
of
our
own.
You
know
initiatives
that
we
think
are
really
important
for
driving
forward,
but
after
triaging
we
spend
a
lot
of
the
rest
of
the
day
trying
to
land
community
prs
or
giving
feedback
and
getting
the
ball
back
into
focus
court.
A
I
want
to
call
out
the
ecosystem
dashboard
tool.
I
don't
know
how
many
folks
are
aware
of
it.
I
believe
it
was
a
protocol
lab
sponsored
project
some
number
of
years
ago.
You
know
andrew
nesbitt's,
the
main
maintainer
about
it
for
it,
but
it's
a
very
useful
tool
for
us.
It's
public
for
anyone
to
use
things
that
we
really
like
about.
It
is
that
you've
got
very
hackable
urls
to
get
different
views
on
issues
and
pr's,
and
it's
got
really
great
metadata
for
us
on
hey.
A
Is
this
issue
or
sort
of
pull
request
coming
from
one
of
our
key
collaborators
or
not,
so
that
we
can
at
least
make
sure
we're
prioritizing
our
time
on
folks
that
are
deeply
invested
in
the
community,
so
others
again
feel
free
to
use
that
tool
just
wanted
to
pass
it
on
in
terms
of
the
release
process
of
the
group
for
those
who
are
paying
attention,
the
kubo
0.13
release
was
a
big
one.
The
amount
of
braking
changes,
slash
new
features
that
came
out.
A
Slash
number
of
lib
p2p
upgrades
that
we
did
while
doing
that
release
was
massive
and
it
was
just
like
too
much
we
kind
of
hit
a
breaking
point
and
in
the
team
retrospective.
I
was
like
okay,
that
that's
gotta
stop,
but
we
at
least
need
to
experiment
with
something
different,
so
we're
we're
moving
towards.
Are
we
attempting
on
a
five-week
release
cadence
if
there's
basically,
four
weeks
of
active
development?
One
week
of
things
sitting
in
our
c
before
it
before
it
gets
shipped
out,
that's
that
whole
process
is
documented.
A
We
leverage
infrastructure
providers
like
like
protocol
labs
infrastructure
to
try
things
out
in
production
and
it'll,
make
things
more
predictable
from
them
for
them
on
when
this
is
coming
and
the
scope
of
changes
that
are
involved
in
that
deployment
in
terms
of
like
variables
to
the
schedule.
Obviously,
you
know
our
team
does
spend
a
lot
of
time
talking
with
collaborators,
and
we
love
that.
That's
a
you
know.
A
I
think
one
of
the
ways
that
we
can
really
provide
impact
and
that
that
comes
in
ad
hoc
ways,
so
there's
no
no
qualms
with
that,
but
that
certainly
adds
variables
to
the
schedule
where
things
get
a
little
more
fun
is
when
there
are
security
events,
regardless
of
where
it
happens
in
the
stack
whether
ipld
or
lib
p2p.
We
generally
have
to
get
involved
either
sometimes
doing
the
fixing
or
at
least
in
the
disclosing,
because
it
does
end
up
impacting
folks
like
ipfs
operators
that
have
software
and
production.
A
A
So
we
just
to
want
to
let
folks
know
we
are
working
on
getting
a
different
domain
for
the
ipfs.eo
website
and
docs
so
that,
even
though
ipves.oh
is
tarnished
or
has
a
bit
of
a
mark
against
it
because
of
the
gateway
and
some
of
the
content
that
can
be
disclosed
on
that
we
want
to
at
least
you
know,
reduce
the
blast
radius
so
that
that
happens
again.
Our
activist
project
website
and
docs
can
still
stay
online.
So
that's
in
progress.
You
know.
A
Lidl
has
been
trying
to
figure
out
how
to
make
that
move
forward.
You
know
I
expect
by
the
end
of
the
year,
we
will
have
that
fully
done
as
a
lot
of
just
comes
down
to
finding
the
right
domain
name
talk
to
lytle.
If
you
want
to
know
more
of
the
history
on
that
one
banana
for
the
overall
project
for
all
of
ipves.
A
So
cool
in
terms
of
where
to
find
us
chat
wise,
you
know,
most
of
the
team
is
in
file
coin
slack,
but
we
have
all
that
bridge
to
ipfs
matrix
and
discord,
particularly
in
terms
of
the
high
signal
channels
for
our
team.
It's
the
itfs
implementers
channel.
I
know
some
are
engaged
in
the
private
ipfest
operators
channel.
That
has
been
discussed,
and
you
know
just
in
general,
really
trying
to
redirect
dms
into
some
more
of
these
public
forms
to
help
help
us
scale.
A
The
active
work
of
the
team
is
all
on
github
project
board
and
we've
found
like
the
new
beta
boards,
which
aren't
so
new
anymore
like
have
enough
features
that
we
don't
need
custom
extensions
or
to
be
using
other
tools.
We
can
keep
it
all
within
github,
pioch
from
the
developer
productivity
team
will
be
speaking
after
me.
You
know
he's
even
done
some
nice
things
for
us
where
we
get
custom
status.
Feel
like
the
nice
thing
about
the
project
boards
is,
you
can
add
custom
fields
and
we
have
things
like
anytime.
A
You
move
a
card
around.
We
record
this
the
date
of
when
that
state
change
occurred
and
that
allows
us
to
do
queries
like
only
show
things
that
were
updated
in
the
last
week
and
things
of
that
nature,
so
those
have
worked
well
for
us.
You
know
we
do
check
in
on
this.
Every
tuesday,
thursday
and
part
of
that
goal,
beyond
coordinating
with
the
team,
is
to
hopefully
get
an
eye
in
on.
How
can
we
limit
some
of
our
work
in
progress
again
still
still
in
progress
there?
You
know
how
this
is
used.
A
Just
you
know
to
close
things
out
in
terms
of
where
to
improve
for
the
group,
because
by
no
means
perfect
here
one
is
just
giving
visibility
on
like
hey.
What's
coming
next
for
the
team
and
what
things
can
you
expect
in
kubo,
because
there's
a
lot
people
that
people
ask
just
being
more
public
about
that
and
publishing
it
is,
you
know
a
key
element
for
us,
so
that'll
be
happening
this
quarter,
you
know.
Similarly,
you
know
I
don't
we
don't
use
metrics
the
best
for
for
our
prioritization.
A
You
know
we
have
lots
of
different
metrics
on
different
things.
It's
a
pretty
wide
surface
area
from
open
source
engagement
to
how
things
are
performing
in
production,
to
adoption,
etc,
and
I
think
we
have
a
good
area
to
grow
in
terms
of
bringing
that
into
a
unified
view
and
again,
really
making
sure
that's
informing
in
a
more
practical
way
how
we,
how
we
prioritizing
what
we
take
on
next
and
in.
In
addition,
you
know
there
are
great
developer,
advocates,
etc.
We
have
touch
points
and
connections
with
them.
I
just
want
to.
A
I
think
we
can
pull
that
even
tighter
to
make
sure
we
are
really
enumerating
what
our
top
issues
and
what
our
responses
and
plans
are
for
them.
So
those
are
those
are
some
of
the
things
you
know
I've.
I
know
we're
probably
time
crunched
here,
I'm
coming
into
my
time,
but
I
would
certainly
for
myself
welcome
any
feedback
if
there's
ways
that
our
team
can
better
work
with
you
or
if
you
have
ways
that
would
be
better
to
engage.
Please
talk
with
me
or
others
on
the
team.
We'd
love
to
hear
it
again.