►
From YouTube: EIPIP meeting 45
Description
Agenda: https://github.com/ethereum-cat-herders/EIPIP/issues/95
A
The
first
item
listed
there
is
a
general
consensus
for
closing
recent
most
discussion
to
issues
I
understand
we
were
discussing
it
in
the
last
call
like
how
do
we
manage
the
long
list
of
open
issues
and
how
to
point
people
for
the
right
place
to
start
the
discussion
to
link
for
any
new
proposal?
A
I
suppose
we
have
updated
the
eip1
with
a
strong
recommendation
actually
to
start
the
discussion
thread
at
fellowship
of
ethereum
magician,
but
still
we
are
receiving
some
of
the
new
issues
where
this
particular
section
is
being
used
as
a
discussion
link
for
new
proposals.
I
understand
a
few
meetings
ago.
We
decided-
and
there
was
a
bot
which
was
updated
to
generate
message
for
new
issues,
saying
that
if
this
is
related
to
proposal
discussion,
please
create
a
fem
thread
and
close
this
issue.
A
Micah.
I
see
your
comment
that
that
message
was
supposed
to
be
for
the
new
contributor
only.
A
B
I
mean,
I
guess
the
question
I
have
is:
what
do
we
want
to
actually
use
the
issues
for,
and
maybe
this
is
a
discussion
that
will
need
a
bigger
quorum
than
just
you
and
I
to
hash
out.
But
what's
what
is
your
initial
thoughts
on?
What
are
the
appropriate
types
of
issues.
A
What
kind
of
help
they
are
looking
for
and
if
something
sucks,
maybe
I'm
hoping
to
use
that
particular
section
to
be
a
point
where
people
come
up
with
their
issues
and
that
issues
could
be
discussed
here
in
this
eipip
meeting
in
future
to
help
out
and
maybe
streamline
more
processes.
Around
eips
and
network
upgrades.
A
Correct
yeah,
because
that
is
an
eap
github,
so
it
should
be
mostly
for
editors
discussion
here.
A
All
right
yeah,
this
is
not
something
that
has
been
added
to
eip1
yet,
but
I
think
it
would
make
sense
if
we
are
in
agreement
or
maybe
we
I
can
start
with
creating
an
issue
in
this
issue-
section
saying
that
how
about
we
start
using
this
issue
shepsen
for
different
purposes.
I
mean
I'm
not
discussing
at
this
point
like
whether
or
not
we
should
close
the
earlier
issues
which
were
created
for
that.
That
may
require
a
separate
discussion,
but
at
least
this
new.
A
B
A
I
know
today.
It
is
all
on
you,
because
we
have
only
one
editor
in
the
meeting,
sorry
about
putting
you
on
the
spot,
for
this
okay.
So
the
next
item
I
have
added
here
is
an
appropriate
placeholder
for
the
active,
eap
validator.
A
So
I
see
this
pull
request,
which
has
recently
updated
the
readme
of
the
eip
repo,
which
is
good
like
we
should
not
be
having
the
old
ruby
one
and
we
should
be
redirecting
to
the
right
one,
but
I
was
wondering,
like
this
points
towards
an
individual's
github
repository,
which
I
think
would
not
be
a
good
practice.
I
understand
like.
A
Currently
he
is
he's
a
great
contributor
and
we
would
like
to
keep
it
that
way,
but
it
would
be
nice
to
have
a
placeholder
for
this
eipv
so
that
in
future
we
can
also
get
pull
requests
and
updates
from
community
as
well
as
it
would
be
easier
for
us
to
maintain,
rather
than
keeping
it
individuals.
B
A
B
I
don't
know
what
the
process
is:
I've
never
looked
into
moving
a
repo.
My
guess
is
that
they
just
need
to
create
a
new
repository
named.
I
don't
know
eipv
or
whatever
they
want.
You
want
to
name
it,
and
then
they
would
just
clone
like
clients
repository
into
that
essentially.
A
Okay,
maybe
I'll
talk
to
maybe
jamie
or
someone
from
the
ops
team
and
try
to
get
this
new
repository
created.
A
A
Moving
on
to
the
next
item,
it's
about
an
incidence
which
was
reported
for
pull,
request;
four,
four:
seven,
eight,
four,
four,
seven,
nine
and
then
four
four,
eight
four
and
four
four,
eight
five.
So
the
thing
is,
I
can't
find
eap,
seven,
two
two
in
any
of
the
repo,
I
mean
sorry,
the
atm
repo,
but
my
understanding
is
all
these
merges
are
associated
with
that.
I
I
saw
that
there
were
some
comments,
reverted,
but
I
was
wondering
yeah.
Why
did
it
happen?
In
the
first
place?
It.
B
Was
a
it
was
a
bug
in
the
auto
merger,
it
accidentally
auto
merged
something
that
shouldn't
have
it's
all.
The
user
created
a
new
apip
with
a
number
they
gave
themselves.
They
didn't
realize
that
they
weren't
supposed
to
and
the
auto
merge
bot
just
said
sure
and
emerged.
It
alita
very
quickly
fixed
that
so
it
shouldn't
happen
again
and
the
eip
has
been
moved
to
an
appropriate
location.
A
B
Yes,
I
believe
the
problem
was:
is
the
initial
pr
got
auto
merged
and
then
the
user
was
then
able
to
edit
their
eip
because
they
now
had
eip
722.
and
then
I
think,
alex
finally
got
in
contact
with
the
user
and
moved
it
to
the
right
location.
So
it
didn't
exist
anymore.
So
if
you
looked
after
the
fact
it
wasn't
there.
A
A
The
next
item
listed
here
is
eip's
insight.
That's
a
monthly
reporting
on
eips.
So
for
the
month
of
november,
we
have
three
new
proposals
introduced
as
as
draft
we
have
three
eips,
those
are
moved
to
stagnant
and
three
resurrected
from
stagnant
two
to
back
to
review
and
one
is
moved
to
draft
from
stagnant.
A
Two
proposals
will
move
to
last
call,
but
I
suppose
the
review
period
is
already
ended,
and
now
there
are
a
pull
request
in
the
repository
to
move
it
to
the
final
status,
and
there
was
one
eip
which
was
withdrawn
by
the
author.
A
Some
of
the
noticeable
updates
for
this
month
for
eip1,
where
we
have
updated
the
eip
process,
the
process
image
for
stagnant
status,
and
there
is
now
description
for
preamble
fields
to
eip1
change
in
the
field
review
period
end.
It
has
now
been
updated
to
last
call
deadline
and
the
updated
field
has
been
removed
from
the
template
couple
of
other
updates.
The
one
is
running
the
rule
for
the
discussion
to
urls.
A
So
that's
on
the
eip
inside
side.
The
next
item
listed
here
is
a
eip,
editor's
apprenticeship
meeting.
We
could
not
conduct
the
second
meeting
this
week,
but
I
have
seen
quite
a
few
interest
from
community
and
they
have
started
contributing
from
like
on
different
proposals.
B
A
Would
like
to
say
yeah,
it
is,
and
I
also
talked
to
a
couple
of
people
individually,
and
they
said
that,
like
we
can
see
some
of
the
inputs,
the
comments
on
the
repo
itself,
but
there
are
people
who
are
also
working
in
the
back
end
connecting
with
authors.
There
is
this
guy
who
is
talking
to
richard,
because
richard
is
trying
to
pull
his
proposal
back
and
it's
nice
to
see.
People
are
trying
to
engage
themselves.
C
I
suppose
we
will
get
one
sorry
yeah.
What
do
we
think
is
the
right
next
step
to
keep
these
people
engaged
like?
C
How
do
we
ideally
eventually
convert
a
couple
of
them
to
eip
editors
like
what
do
we
want
to
see
or
like
yeah,
I'm
curious,
you
know
how,
because
because
I
think
we
we
want
like
people
to
like
you
know
proactively
do
stuff
and
whatnot,
but
once
they
are
doing
it,
how
do
we
like
encourage
them
and
and
get
that
keep
them
engaged
so
that
yeah
they
stick
around?
Ideally,.
A
D
Yeah
thanks
from
my
point
of
view,
I
just
contributed
my
my
in
my
first
two
bounties
and
I
just
learning
everything
and
having
a
look
around,
and
I
think
what
you
do
brilliantly
is
all
the
documentation.
It's
it's
really
good
to
to
get
the
foot
in,
and
I
think
you're
a
strong
community
and
that's
the
base
for
for
for
a
good,
onboarding
I'll.
I
report
back
when
I've
got
more
information
from
my
point
of
view.
If
that
helps.
C
Yeah
100,
and
if
there's
things
you
know,
you
think
are
confusing
or
it
can
be
done
better
or
like
yeah.
That
are
just
like
friction
points.
If
you
can
share
those.
That's
that's
really
valuable
yeah,
because
it's
it's
the
first
time
that
we
have
like
kind
of
a
cohort
of
interesting
people
interested
people
yeah,
and
I
think
we
want
to
make
sure
that
we
we
don't
lose
people
because,
like
we
just
have
a
bad
process
or
whatever
sure
yeah
we'll
do
yeah
awesome
thanks.
A
So
we
have
planned
the
next
meeting
on
december
7th,
as
I
mentioned
earlier,
I
hope
to
see
more
people
or
people
coming
with
the
sharing
their
experience
for
the
past
two
three
weeks
and
if
they
have
any
new
questions.
A
A
All
right
that
was
it
and
we
are
almost
at
the
last
item
that
is
listed
on
the
agenda
for
today
the
review
action
item.
Unfortunately,
we
do
not
have
the
notes
for
it.
I
was
informed
that
it
will
be
up
later
today,
sorry
for
the
delay
guys,
but
I
have
a
point
listed
it
out.
What
were
the
action
items
from
the
last
meeting,
so
I
made
a
poll
request
to
update
the
web
link
to
text
removed
from
bibliography
from
eib1.
A
I
see
it
has
been
approved
by
one
of
the
editor,
but
it
might
require
address
like
one
more
approval
from
the
there's
two
editors
to
be
merged.
B
A
Okay
and
the
couple
of
other
pull
requests
are
one
to
update
the
discussion
to
place
and
status
cases,
and
I
think
it
has
been
merged
already
yeah.
There
was
one
action
item
on
me
to
create
an
issue
where
we
can
start
looking
into
adding
labels
to
prs.
I
have
shared
the
eip
bot
github
repository
with
a
few
people
in
the
community,
like
the
new
contributors,
whom
we
are
interacting
and
I'm
looking
forward
to
get
some
input,
get
some
update
and
help
from
these
people.
A
I
know
stefan
is
one
of
those
I
shared
the
aip
github
repository,
so
we
may
be
expecting
some
help
in
future.
I
know
alita
left
some
comment.
Unfortunately,
she
is
not
here
for
this
meeting.
She
is
traveling,
but
she
left
some
questions
and
concerns
that
she
has
about
this
sharing
responsibility
or
transitioning
responsibility.
A
As
of
now,
I
do
not
have
any
one
single
person
in
my
mind
like
who
can
be
like
taking
over
completely,
but
if
you
do
not
get
anyone,
I'm
hoping
to
make
it
decentralized
like
making
these
chats
bounty
based
and
get
it
done.
But
for
sure
we
will
be
having
people
around
to
take
care
of
ech
engineering.
Chess.
A
That's
all
from
the
item
listed,
I
know
tim,
you,
you
missed
the
discussion
on
the
first
item
when
we
were
discussing
about
the
discussion,
two
link
for
general
issues,
so
I'm
I'm
hoping
they're
like.
Maybe
we
can
create
an
issue
or
pull
request
and
tag
you
and
and
rest
of
the
ap
editors
and
have
the
discussion
over
there
yeah.
That's
all
anyone,
yeah
yeah,
please
anyone
wants
to
bring
anything
up.
A
Yeah,
that's
all
right!
Yeah!
I
mean
it's
on
her
comfort
level
like
of
what
whatever
she
wants
to
do.
Like
any
thing
I
mean,
generally,
we
try
to
label
them
and
out,
and
I
don't
think
there
are
a
lot
of
issues
so
when
it's
like,
when
there
will
be
a
lot
of
issues,
then
that
can
be
priority
based.
But
that's
okay
good
to
know.
A
All
right
folks,
thank
you
for
joining
in
the
one
major
change
that
I'm
hoping
to
get
it
done
in
future
is
about
like
whatever
the
issues
and
challenges
people
are
facing.
That
needs
to
be
added
somewhere
from
where
we
can
start
getting
data,
because
it's
random
and
I
have
to
search
on
all
the
discord
and
the
issues
and
github's
repository.
A
So
I'm
hoping
to
make
the
eip
github
repository
issue
section
is
the
section
where
anything
that
you
want
to
be
discussed
or
brought
into
attention
offer
the
eip
editors
can
be
listed
and
we
can
take
it
out
and
start
discussing
in
this
eipab
meeting.
So
folks,
if
you
are
listening-
and
if
you
have
questions
comment-
concerns
anything
either
show
up
on
our
discord
channel
or
add
it
there
in
the
issue
section
we'll
try
to
bring
it
up
in
this
meeting.
A
Thank
you.
Everyone
for
joining
us
today.
I
hope
to
see
you
in
next
two
weeks
have
a
good
rest
of
the
day.