►
From YouTube: EIPIP Meeting #11
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
Now,
let's
start
I'm
James
Hancock.
This
is
e
IP
IP
meeting
11
with
agenda
on
the
cat,
herders
github
we
are
small
today,
so
we
will
we're
going
to
review,
go
over
stuff,
keep
and
perhaps
have
a
short
meeting,
but
thank
you
all
who
came
the
we'll
just
start
at
these
there's
something
particularly
you
all
want
to
go
over
since
we're
small
enough.
We
I
think
we
are.
We
can
be
flexible
about
what
to
talk
about.
First,
there's
anything
that
comes
to
mind.
B
A
C
Sometimes,
there's
things
on
the
agenda
which
we
don't
get
to
as
more
and
more
items
are
to
the
agenda.
I
think
you're,
add
below
to
future
agendas
and
we
might
lose
items
so
I
think
it's
a
good
way
to
organize
feature,
talking
points
that
we
table
to
future
meetings,
or
sometimes
the
average
and
items
that
say
we
want
to
focus
on
decision
making,
but
we're
also
introducing
stuff
around
onboarding
me.
C
B
Yeah
I
kind
of
like
the
idea
too
sometimes
back.
We
have
used
it
for
you
know
creating
the
post-modern
for
Constantine
ole
and
they
can't
her
this
itself.
I'm
gonna
share
the
link
in
the
chat
here
so
yeah.
This
is
like
a
good
way
to
keep
track
of
it,
like
whatever
agenda
that
we
are
trying
to
discuss
here
and
if
any
decisions
are
make
and
how
we
are
going
to
implement
that
it
would
be
a
good
way
to
keep
track
of
it.
B
Yeah
I
think
it
should
be
like
when
we
look
into
these
VIP
AP
Depot.
There
is
a
section
for
project
which
is
empty
at
this
point
of
time.
I'm
gonna
share
the
link
here
again,
so
there
we
can
kind
of
sort
planned
project,
automate,
workflow
and
everything
is
there,
so
might
have
to
take
what
we
want
to
put
where
or
how
we
would
want
to
address
this.
B
So
I
think
up
till
now,
guitars
that
how
we
have
been
managing
is
like
we
had
this
initial
document
of
e
IP
IP,
where
we
gathered
some
idea,
how
we
are
going
to
do
that
and
the
it
sends
a
report
that
came
up
after
the
AP
AP
survey.
So
that
was
another
reference
point,
and
now
we
have
to
collect
the
main
ideas
from
there
and
add
them
as
tasks,
and
then
we
can
keep
measuring
how
the
progress
I
mean.
B
A
Else
is
nice
with
github
project
boards
is,
you
can
tie
the
project.
I
actually
have
started
using
the
project.
They
get
hub
project
board
for
managing
the
hard
for
coordination.
Stuff
I
have
one
that
I've
thought
about
just
making
public,
but
I
wanted
to
make
sure
I
work.
It
works
well
before
I.
Did
that
just
to
keep
keep
track
of
this
stuff
that
I'm
doing
and
something
that's
nice
using
the
github
project
board.
Is
you
can
tie
issues
you
can
connect
an
issue
to
it
to
a
tile
or
whatever
you
call
them
right.
B
A
D
A
Let's
just
go
backwards
because
I
think
the
some
food
puja
you
copied
a
comment
from
Kidder
about
separation
of
the
IP
and
Harford
coordination
and
I'll,
just
read
it
out.
Here
I
am-
and
this
is
from
Yoakam
Bruin.
I
am
super
concerned
that
in
har
fork,
Medes
drafted
e
eyed
peas
get
accepted,
see
the
VLSC
IP
I'm
also
concerned.
Why
it's
not
a
requirement
that
accepted
hard
for
GIPS
have
state
test
PRS
in
the
etherium
to
test
repository.
A
A
The
one,
the
definition
of
what
is
accepted
is
is
changing
like
if
we
go
over
the
new,
the
new
statuses
that
are
being
proposed
accept
it
is
it
even
in
there,
and
the
reason
is
that
the
the
accepted
status
will
be
part
of
the
network
upgrade
process
and
that
will
be
done
separately
and
this
big.
We
are
at
the
stage
and
defining
the
process.
So
a
little
bit
of
high-level
where
we
are
currently
with
that
is
we
have
the
IPS
go
through
EFI
and
then
when
and
then
through
EFI.
A
A
It's
a
good
concern
and
something
that
we're
actively
thinking
about
what,
when
it's.
Actually
it's
been
easier
to
process
this,
since
we've
started
separating
the
IP
process
and
the
hard
for
coordination
process,
because
we
can
be
stricter
on
things
like
this
exactly
is
it
and
and
have
a
better
process
for
each
one,
so
that
I've
been
personally
excited
about
and
I'd
like
to
move
forward
with
getting
the
new
statuses
up
at
at
TTIP,
one
which
I?
Don't?
Did
you
guys
talk
about
that
last
week
about.
B
No,
not
really.
That
was
like
skipped
in
your
absence.
We
thought
it's
better
like
hard
work
coordinator
should
be
sufficient
in
the
same
context.
I
have
a
question
here.
I
mean
it's
just
for
my
general
understand
me
like
when
we
mention
that
a
IP
has
to
be
EFI
and
then
goes
for
implementation
and
then
goes
for.
You
know
acceptance
in
the
upgrade
meta
meta.
So
my
question
is
in
regards
to
EAP
two
zero,
four
six
and
twos
five.
B
Six
five,
so
I
understand
that
two
five
six
five
recently
have
entered
into
EFI
and
that
we
are
considering
in
Berlin
dashboard
for
even
for
you
know
the
next
upgrade,
although,
although
it
is
not
very
much
confirmed
that
it
is
going
or
not
going
depending
upon
how
the
problem
goes
ahead,
so
for
EAP
to
zero
for
sex,
where
do
we
see
that?
Is
it
under
efi
or
considered
for
because
I
remember
some
discussion
considering
it
for
the
Berlin
upgrade,
but
I
do
not
I'm,
not
sure
Oh?
What
is
the
state
of
it?
A
A
So
it's
it's
understandable,
but
the
status
should
be
an
EFI,
and
it's
also
still
not
it's
still
possible
to
get
in
Berlin,
because
the
reason
VIPs
get
into
hard
Forex
is
because
they're
ready
to
go
in
when
hard
work
happens
or
when
a
network
upgrade
happens,
and
so
as
that
one
is
ready,
then
it
can
be
moved
which
there
are
still.
There
are
still
some
outstanding
stuff
to
figure
out.
What's:
okay,
I
know
and
it'll
will
go
on
Yolo
before
I.
Think
any
of
that
has
even
decided
there.
There
is.
A
There
are
some
things
that
need
to
be
tested
before
we
could
even
say
it
should
go.
We
should
think
about
it
going
in
Berlin
first
and
it's
easier
to
test
those
having
them
on
Yolo,
because
then
we
can
test
them
with
three
different
clients
I've.
So
that's
why
it's
a
little
bit
in
a
weird
place
compared
to
other
AI
pees.
Some
me
I.
A
Some
Mei
peas,
you
you
have
it's
pretty
straightforward
if
or
how
to
do
it,
and
then
we
kind
of
move
forward
on
implementations
this
one,
because
it's
touching
gas
costs
it
involves
repricing
gas
things
which
then
means
we
need
to
make
things
like.
For
example,
we
need
to
make
sure
that
all
contracts
are
still
safe
on
the
network
and
that's
just
something
someone
has
to
go
through
which
that
step
is
easier.
A
B
A
A
A
B
A
D
E
B
F
A
A
A
A
Yeah
I
wanted
to
dress
like
clients
comments,
so
he
mentions
their
github
allows
a
special
type
of
contributor
with
triage
permissions,
meaning
they
don't
have
write
access,
but
can
label
issues
in
PRS.
This
is,
and
this
could
be
a
good
on-ramp
for
contributors
to
become
editors
and
wouldn't
minimize.
The
time
needs
to
keep
through
PRS.
This
is
great
it.
This
would
be
a
great
thing
to
do
at
Humber.
Send
support
that
I'm
would
say.
Had
someone
agree
and
help
on
getting
that?
I
am
NOT
very
github
literate
to
be
totally
honest
and.
B
A
Of
these
things,
is
this
a
matter
of
actually
knowing
how
to
do
it
and
having
someone
who
knows
how
to
do
it?
Do
it
so
I
very
much
appreciate
help
on
this
and
3e.
It
would
be
good
to
agree
on
specific
naming
conventions
for
e
IPS
and
official
documents
these
different
formats.
This
is
correct
and
should
be
updated
on
a
IP
one.
A
B
I
remember
an
incidence
when
I
submitted
appeal
for
a
specific
EAP
which
was
already
existing,
and
then
one
of
the
editors
edited.
My
IP
number,
like
I,
forgot
to
mention
the
hyphen
between
like
say,
for
example,
it's
a
IP
one,
so
I
chose
the
third
one
EAB
space
one
and
he
corrected
it.
Mentioning
that
I
know
it
needs
to
be
EIT
one.
So
if
they
consider
that
as
a
baseline,
I
I
think
that
can
that
needs
to
be
mentioned
in
EAP
one
and
that
can
be
followed.
Yeah.
E
Do
we
is
there
any
progress
on
that,
because
I
feel
like
there's
a
few
people
in
this
face
would
be
perfect
for
that,
and
certainly
you
know,
we
have
some
experience
with
doing
emergency
columns
and
then
the
risk
evaluation.
That's
a
I
I.
Don't
know
that
this
that
this
little
note
is
is
small
and
I.
Think
the
what
is
room.
What
is
involved
in
creating
that
is
very,
very
large
and
I
think
it
would
be
better
to
put
that
up
for
opinion
in
the
each
security
job.
E
A
B
For
that,
like
we
have
created
this
emergency
come
processed
document,
sometimes
back
during
the
constantin
on
the
postmortem.
Only
so
it
suggests
that
we
should
be
having
a
list
of
key
audiences.
Those
are
going
to
be.
You
know,
emergency,
constant
members
and
we're
trying
to
create
this
list
and,
like
generally,
we
use
this
kind
of
list
at
the
time
of
upgrade
or
hard
work
to
communicate
with
our
key
stakeholders.
B
Let
them
know
what's
going
on
on
it's
something:
urgent
comes
up,
so
that's
that's
it
and
the
other
thing
was
like
we
have
came
up
with
a
list
of
you
know,
preferred
channels
of
communication,
but
it's
important
that
we
should
be
reaching
people
more
people
and
like
quicker
as
quickly
as
possible.
So
this
is
the
preferred
appropriate
channels
that
we
suggested
we
should
be
using
and
forever
yeah.
E
Makes
sense
just
quickly
looking
at
those
it,
certainly
the
having
like
understanding
the
list
of
who
to
contact
I
mean
you
know
this
is
public,
so
I,
don't
you
know
that
it
would
have
to
be
a
trusted
group
of
people
to
do
that,
but
I
I
feel
like
if
this
is,
if
there's
a
little
bit
more
direction
in
this
document,
that
it
that
that
team
could
be
could
be
formed.
I,
don't
know
it's
it's
really.
E
B
E
E
It's
really
needed
is
the
people
to
be
able
to
execute
on
the
thing
that
when
it,
when
it's
needed
and
to
have
the
professionalism
to
you,
know,
work
together
and
say
the
right
things
and
I
think
that
could
be
honestly
coordinated
through
a
little
telegram
job.
That's
like
that's
limited
in
how
many
people
are
in
it.
So.
B
E
That
makes
sense.
Emergency
comms
is
something
that
I
have
some
experience
and
so
I'd
be
happy
to
help,
but
I
mean
I'd
still
I
think
I'd
still
want
to
hang
back
a
little
bit
as
I,
slowly
unpack
and
understand
more
the
processes,
I'm
not
ready
to
just
jump
in
and-
and
you
know,
start
saying-
here's
solutions
because
I
don't
think
that
would
be
that
that
would
actually
be
very
that
wouldn't
be
good
good
of
me.
You
know,
there's
there's
a
lot
of
stuff
that
has
already
been
built
out.
A
B
A
E
On
it
maybe
I
mean
maybe
this
is
for
yeah
they'll
be
that'd,
be
amazing,
I
think
a
checklist
and
people
to
execute
on
it
would
be
good.
I
think
wouldn't
be
a
very
hard
thing
to
organize.
Maybe
its
think
to
talk
about
on
the
next
di
P
call.
It
would
more
detail
I'm
taking
up
too
much
time
here,
but
the
that
I
just
wanted
to
bring
that
up.
As
as
that
is
definitely
an
area
that
I
feel
like
in
I
can
help
right
away.
Cool
I
think.
G
Personally,
I
agree:
I
feel
like
the
processes
that
are
there
work
for
when
things
are
going
well,
but
even
right
now,
with
Hudson,
James
and
being
away
I'm
sure
James.
You
are
kind
of
left
to
do
a
lot
of
things
that
maybe
you
aren't
used
to
be
doing
so
having
processes
where
those
of
us
that
are
used.
G
A
E
You
know,
but
I'm
I
certainly
feel
confident
in
providing
feedback
and
and
also
help
sort
of
coordinate
a
team
together
when
we're
ready
and
and
work
on
on,
like
when
goes
down
but
at,
but
at
the
moment
I'm
I,
just
I,
don't
have
enough
of
the
pieces
and
I
think
them.
The
biggest
need
is
to
prioritize.
It.
Have
a
checklist,
go
through
the
checklist
and
and
get
the
and
get
a
list
of
contacts
every
like
everything
else.
A
The
what
are
people's
thoughts
on
increasing
the
strictness
of
the
IP
validator,
it
seems
like
the
quality
of
the
IPS,
could
be
improved
quite
a
bit.
It
checks
a
curb
before
merging
and
he
started
on
a
New,
Year's,
Eve
elevator,
and
he
plans
to
make
it
stricter
than
the
existing
validator
and
more
robust
and
I
have
been
asking
for
this
for
a
long
time.
I
don't
want
to
jump
ahead
of
everybody,
but
I'm
very
excited.
A
A
A
G
A
B
A
Then
the
last
one,
how
can
we
funnel
people
working
on
some
similar
AI
piece
together,
for
example,
EAP
549,
is
related
1x
and
if
two
witnesses,
these
groups
may
I
not
be
at
the
stage
where
they're
ready
to
pursue
any
IP.
But
it
looks
like
this
would
end
up
being
superseded
by
the
eventually
you
might
be
from
these
groups.
A
A
A
A
B
So
if
we
have
to
look
into
the
postmortem,
we
just
gave
a
look
to
the
constant
in
pool
that
we
did
earlier.
That
was
in
a
form
of
project,
but
in
one
of
the
previous
EAP
IP
meeting,
we
decided
that
these
kind
of
information
should
be
made
public
in
a
form
of
EIA.
We
can
save.
It
is
unlike
an
informational
unity
which
is
like
very
easy
and
accessible
for
people
rather
than
finding
it
in
some
particular
github
repository
in
some
project
section.
So
this
is
a
draft
that
we
have
created
for
the
previous.
B
The
mutilation
upgrade
and
we
have
tried
to
provide
as
much
as
information
as
possible,
starting
from
the
upgrade
summary
section
like
what
date
time
block
number
and
who
owned
that
particular
blog.
They
details
from
there
right
from
there
be
included
the
EIP
listed,
the
EAP,
those
were
included,
but
formulation.
It
was
just
the
only
one
for
that
pushing
up
the
difficulty
BOM
phone.
So
we
used
that-
and
this
is
the
sequence
of
events
that
took
place
the
decision-making
beti
so
that
people
can
go
and
refer
it's.
B
It's
just
a
thought
is
to
make
everything
accessible
for
community
later
on,
to
read
and
if
we
come
up
with
some
good
practices
that
we
would
want
to
continue
in
future,
some
corrective
actions
like
the
rubric
that
we
discussed
the
other
time
about
like
how
we
can
prevent
anything,
miss
happening.
Or
what
will
the
issue
is?
We
can't
be
phased
in.
How
what
were
that
possible
suggestions
to
that
are.
D
B
B
B
If
anything
is
messing
up,
the
two
questions
I
have
in
mind:
I'll
just
mention
it
so
that
if
you
are
giving
it
to
look
or
maybe
think
about
it,
the
discussion
to
a
section
here,
what
we
did
is
like
we
refer
to
the
post,
magician,
post
and
James
created
formulation
a
bit.
We
did
not
create
any
specific,
yet
magician
post
to
just
list
the
mutilation,
because
I'm
not
sure
if
there
is
much
more
discussion
needed
on
effect
is
we
can
just
combine
both
of
them.
B
So
that
was
one
and
the
other
thing
was
at
the
end
of
this
document.
We
have
also
listed
the
resources.
This
is
not
a
typical
format
of
any
EIP.
Do
we
need
to
have
it
if
it
is
fine
to
keep
it
because
I
I
think
I
have
mentioned
on
the
links
here
already,
then
we
will
keep
it.
Otherwise,
we
might
want
to
remove
it
and,
yes,
please
feel
free
to
share
your
thoughts
about
this
there's
one
more
thing
like
we
have
this
template.
This
is
the
general
template
for
future
post-mortem
of
grade.
B
G
Anyone
has
any
question
on
the
second
point
you
made
about
the
resources
just
on
specifically
accessibility
readings
as
someone
who
does
have
a
hard
time,
sometimes
navigating
through
some
of
these,
the
ip's
I
do
think
it's
helpful
to
have
the
resources
sort
for,
like
future
post
mortems,
if
not
didn't,
become
something
that
was
normal.
I
think
it
could
be
helpful
that
for
people
that
aren't
as
used
to
know,
what's
going
on
in
the
community,
I'm
gonna
go
to
kind
of
figure
out
more
information
there.
That
can
also
be
in
the
blog
post
as
well.
G
F
G
B
So
I
have
added
the
blog
post
here
somewhere,
like
okay.
This
was
published
by
the
catalyst
okay,
I
think
I
missed
one
published
by
the
ETM
foundation.
I
may
have
to
add
that
blog
post
as
one
so
we
try
to
provide
as
much
link
as
possible
to
get
into
the
real
conversation
and
feel
like
we
have
not
made
up
anything.
Everything
is
coming
up
from
the
discussion,
so
yeah
I
will
add
those
at
the
bottom
as
well.
G
B
B
So
one
a
new
thing
that
we
are
trying
to
do
here
is
like
putting
this
suggestive
corrective
action
in
the
form
of
problem
and
suggestions,
like
one
of
the
comments
that
was
received
by
one
of
the
client
developers
like
the
testing
window
planned
for
this
particular
upgrade
was
too
short.
Maybe
because,
like
you
know,
we
did
the
Istanbul
in
December
and
January,
it
was
there
so
yeah.
Certainly
we
did
not
have
testing
window
and
maybe
because
of
that
some
calculate
miscalculation.
B
The
Rothstein
had
to
be
delayed
for
a
very,
very
long
time
like
it
came
up
after
10
days
or
11
days
after
the
main
it,
and
we
should
not
I
mean
we
should
avoid
mainly
to
upgrade
before
test
night.
So
does
anybody
has
any
comment
on
this
particular
format?
The
problem
and
suggestion
are,
it
looks
fine,
or
can
we
put
it
in
some
other
form?
I
think
it
looks
fine.
A
A
A
B
B
B
A
A
Ten
three
future
meetings
discuss
on
board
II
I
on
board
eg
IP
editors,
which
we
did.
We
talked
about
a
little
bit
today
with
having
the
the
permissions
for
you
can
have
provisions
for
triaging
and
things
which
we
can
have
be
more
open
for.
Individuals
and
10.4
have
use
of
labels
for
PRS,
TEI,
PS
and
then
10.5
waiting
on
James
to
complete
the
complete
compiled
discussion
item.
B
A
A
C
So
I
think
that's
good.
One
thing
I
wanted
I
brought
up
in
the
previous
meeting
was
a
feedback
from
our
time.
Was
that
there's
less
scrutiny
moving
from
one
status
to
another,
and
that
could
be
because
we
haven't
defined
how
to
move
from
once
that
assume
the
other.
So
it
could
probably
included
with
the
statuses
we
can
define
how
to
move
from
one,
how
to
how
to
progress
within
the
statuses
or
like
specified
that
it
makes
sense.
Yeah.
A
C
How
is
I
guess
more
specifically
how
you
moved
from
one
place
to
the
other
also,
we
should
start
defining
statuses
for
the
heart
forward
coordination,
and
we
should
also
include
how
to
move
from
one
status,
the
other,
where
that,
as
well
kind
of
mirroring
the
Yaquis.
A
C
This
project
management
step
so
there
would
be-
or
this
is
just
my
initial
thoughts
because
they
get
feedback
but
eligible
for
inclusion-
is
for
consideration.
Then
implementation,
then
testing,
then
final
decision,
then
deployment
and
then
through
any
of
these
process.
Any
of
these
steps,
where
you
go
from
one
to
the
other,
there's
always
the
chance
to
motion
to
rejection.
So
say
you
go
to
test,
then
you
can
go
to
rejection.
You
know
implementation.
You
find
something
that
just
the
EAP
pick
something
impossible
or
just
messes
something
up
deeply.
A
I
like
having
the
flow
that
way
and
having
each
having
each
step
have
its
own
as
my
part
of
that,
what
we've
run
into
historically
is
accepted.
Me
I
think
the
definition
of
accepted
it's
kind
of
clear
in
the
IP
one,
but
the
community
understanding,
and
even
sometimes
the
core
developer,
understanding
of
what
that
it
means
it
was
totally
different.
So
having
the
you
go
through
the
process
and
at
any
point
it
can
be
rejected.
A
It's
a
good
way
of
kind
of
managing
those
expectations,
and
we
should
show
that
visually
when
we're
defining
the
process.
I
like
I,
like
that
quite
a
bit,
the
I'll
work
on
before
I'll
work
on
doing
a
document
or
a
PR
for
the
status
is
the
epi
one.
So
I'll
feel
more
confident
moving
into
you're
right
that
it's
time
to
start
more
defining
the
network
upgrade
process.
I
would
just
feel
more
comfortable
if
we
had
some
more
resolution
on
the
standardization
process
before
I
start
shifting
mental
gears
into
that
something,
that's
something.
A
B
One
of
the
action
items
mentioned
are
not
absent
action
item.
It's
just
a
part
of
decision
like
you
know,
there
should
be
a
particular
place
to
collect
all
this
kind
of.
You
know,
definitions
that
we
are
planning
to
which
one
is
it,
adding
a
mandatory
terminology
section
for
EAP
so
like
we
are
discussing
for
putting
these
statuses
and
destroyed
any
IP
you
want
and
it's
something
that
we
should
consider
for
a
IPS
in
general
as
well
like
if
something
new
is
coming
up.
C
I
think
we
mentioned
this
in
the
previous
meeting.
I
had
suggested
different
standards
like
different
senator
organizations.
They
have
a
section
for
terminology,
it
might
be
good
if
we
simplified
just
something
like
save
definitions
as
having
it
mandatory.
There
may
be
ApS
that
don't
really
introduce
new
terms
and
then
having
global
terms
that
require
for
each
API,
I,
don't
think
is
necessary,
but
some
VIPs
may
introduce
new
terminology
that
would
facilitate
clarifying
to
the
reader.
Be
okay,
I
think
it's
definitely.
It
brings
some
value
having
a
definition.
Second
yeah.
B
I'm
not
too
sure
like
how
much
value
would
it
add
like
if
we
can,
if
it
is
not
something
that
is
going
to
be
common
in
most
of
the
EIP
s,
we
can
probably
go
ahead
and
explain
that
term
in
one
of
the
summary
summary
section
or
somewhere
else
in
the
EAP
itself,
but
adding
this
as
a
you
know
mandatory
section
for
every
IP
and
that
is
I'm,
not
sure
Oh.
What
are
you
it
doesn't
harm
to
have
something
additional
as
well
so.
C
B
Right
that
is,
that
is
me
dude,
like
I'm
in
for
EAP.
One
I
understand
this
part
like
this
section
is
a
mandatory
for
EAP
one
but
again
EAP
one
is
not
a
mental
EAP,
it's
a
kind
of
documentation
that
provides
the
guidelines.
So
for
that
having
this
session,
it
makes
a
lot
of
sense,
but
making
it
mandatory.
I
was
not
sure,
but
if
it
is
an
optional
yeah
perfectly
fine,
yeah.
D
B
A
A
B
A
B
B
B
C
B
Okay,
but
yeah
I
will
I
will
look
into
it
like
who
has
the
access,
maybe
Hudson
or
somebody
else
should
have
I'm,
not
sure
of
that.
But
yes,
I
would
be
happy
to
you
know,
discuss
and
if
we
can
work
out,
I
mean
I'm,
not
sure.
If
you
have
any
idea
James
does
it
work
out
with
the
help
of
pull
requests?