►
From YouTube: EIP editors apprenticeship meeting 17
Description
Agenda: https://github.com/ethereum-cat-herders/EIPIP/issues/135
A
All
right,
so
we
are
waiting
for
light
line
right.
Let
me
quickly
ping
him
and
in
the
meanwhile
I'll
also
share
the
agenda.
Here
I
have
kind
of
listed
some
of
the
pull
requests
that
may
need
some
attention
from
our
end,
I
know
some.
You
have
responded
to
a
lot
of
pull
requests,
but
still,
if
we
can
close
it
faster,
that
would
be
good.
B
I
do
apologize
for
having
been
a
lot
less
active
recently
I've
kind
of
lost
my
free
time
on
my
sundays
for
now,
which
is
like
what
I
was
doing
most
of
my
work
there.
So
I
am
hoping
to
rethink
that
at
some
point,
but
in
the
meantime
it's
been
like
really
reduced
capacity.
For
me.
A
A
A
All
right,
while
we
are
waiting
for
light
line,
jan,
if
you
would
like
to
go
ahead
and
sorry,
is
it
gen
l?
Yes,
so
jen?
If
you
would
like
to
briefly
introduce
yourself
to
the
group.
C
Yeah
sure
I
gosh
I've,
I'm
from
australia,
it's
about
11
00
p.m.
Right
now,
over
here
I
have
about
20
years
of
tech
experience
and
very
interested
in
web
3
really
excited
about
what
you
guys
doing
in
on
the
ethereum
and
would
like
to
get
involved
with
the
eip
and
erc
editing
process.
A
Nice
to
have
you
on
this
collagen:
did
you
by
any
chance
get
in
touch
with
any
of
the
present
contributors
of
ethereum,
or
how
did
you
get
to
know
about
this
meeting
yeah
through
tim
baker,.
C
Yes,
I
believe
yeah
he's
part
of
the
group
and
yeah
he's
heavily
involved
with
all
of
this
with
merch
etc.
So
I
came
to
him.
D
Do
you
have
hello,
hey
man,
yes,
so
do
either
of
you
have
like
contributor
permissions
on
the
eips
repository.
D
Like
like
being
able
to
merge,
prs
and
override
the
bot,
I
do
okay.
Do
you
need
that?
I
maybe
I
think
so.
5035
I
think,
was
superseded
by
a
different
pr,
so
I
think
we
can
close
it,
but
yeah
anyways.
We
can.
We
can
talk
about
that
when
we
get
to
it.
A
That
is
my
question
as
well
like
what
is
this
pr
all
about?
If
you
can,
maybe
let
us
know
and
is
it
auto
created
by
bot
or
something
yeah.
E
It's
auto
created
there's
this
gem
called
nokogiri.
I
think
it's
yeah,
some
xml
html
thing.
It's
running
the
ci.
I
think
it.
I
think
what
this
gem
does.
Is
it
lets
you
go
through
your
html,
that's
generated
for
like
the
eeps.ethereum.org
website
and
make
sure
all
the
links
work,
and
so
I
guess
the
dependabot
just
makes
prs
to
update
things.
E
Let's
see
which
part
so
this
isn't
even
a
bot.
This
is,
I
think,
it's
just
a
script
that
runs
and.
D
E
D
E
F
E
Just
like,
I
think,
historically,
it
just
sits
there
for
a
really
long
time.
E
The
last
one
I
remember
is
that
micah
and
I
were
like
yeah
it's
okay,
if
it
merges,
but
like
neither
of
us,
wanted
to
make
sure
that
it
didn't
break
anything.
I
don't
remember,
I
think,
eventually
just
got
merged
and
I
guess
it
didn't
break
anything,
but.
E
D
Nothing
happens.
I
haven't
ever
tried.
Actually
it
just
doesn't
ping
me,
so
I
assume
I'm
not
an
approver
on
it.
Oh,
it
doesn't
ping
me
either.
E
So
I'm
not
really
sure
anyways,
I
don't
know
we'll
just
close,
it
don't
open
another
one,
two
months
and
then
we
can
have.
Hopefully
somebody
emerges
who's
in
charge
of
the
ci
twitter
fix
on
terminatedbracket681.
F
To
god
yep
there,
it
is
right
there.
E
E
F
E
D
Oh,
this
is
the
one
that
I
think
there's
another
pr,
that's
related
to
it.
I
think,
or
is
that
the
previous.
A
F
A
A
F
E
E
E
A
E
A
E
A
Is
not
so
I
met
with
this
author
and
I
had
this
question
so.
B
A
F
E
I
mean
this
isn't
100
foolproof,
because
some
pathological
person
could
open
a
pr
that
doesn't
somehow
have
any
mention
of
the
eip
number.
But
if
you
search
like
the
number
this
one
4907
and
then
you
click
issues
that
will
list
everything
related
to
that
eep,
so
it
was
long,
I
guess
even
with
the
bot.
The
bot
is
also
showing
up
here,
looks
like
like
it
says
right
here
4907.,
so
this
should
be
a
pretty
good
way
to
pull
up
everything
related
to
that
number.
In
the
pull
request.
E
E
E
E
D
Was
this
the
one
where
I
yeah,
I
included
their
their
implementation.
B
D
Were
the
the
spell
checker
is
checking
the
json
file,
which
has
like
not
words
in
it,
and
there
was
an
actual
typo
somewhere.
F
D
E
E
E
E
D
F
D
And
then,
if
you
do
zed
equals
on
a
word,
it
gives
you
the
suggestions
to
apply.
F
E
F
E
F
F
F
A
Matt,
if
I
can,
if
I
can
maybe
interrupt
for
a
moment.
A
Have
one
more
new
hoping
to
be
an
editor?
She
is
jen
l,
and
this
is
her
first
meeting.
So
if
I
know
now,
we
are
starting
on
new
proposals
like
the
new
draft
proposal,
so
it
will
be
a
good
walk
through
for
her,
but
I
would
like
to
invite
her
to
maybe
say
any
question
that
she
may
have
so
far.
C
Yeah
hi
everyone
yeah,
my
full
name
is
jen
jennifer,
ellerton
yeah,
so
I've
just
been
thrown
into
this,
and
I'm
just
coming
into
this.
For
the
first
time,
I've
had
a
look
at
I've,
looked
at
the
ripper
on
on
github
and
I've
created
a
fork
and
that's
about
it.
That's
about
all
I've
done
so
I'm
interested
to
find
out
like.
Can
you
give
me
a
little
bit
of
context
about
what
we're
doing
and
these
meetings?
C
I
guess
this
is
how
you
catch
up
with
everybody
or
I'm
just
coming
in
with
with
no
no
context
no
background
at
all,
so
hoping
you
can
throw
some
like
into
it.
Sure.
E
C
We're
doing
basically
at
the
moment
is
me
more
of
an
enthusiast,
and
I
imagine
that
that
my
contribution
would
be
more
in
terms
of
this.
In
terms
of
editing
would
be
you
know
more
grammatical
and
and
and
just
looking
at
the
layouts
and
so
forth,
but
I'm
really
looking
to
you
guys
for
any
input
on
how
to
get
started
in
that.
E
Nice
well
welcome.
Thank
you
this.
E
The
grammatical
checks
make
sure
that
things
like
you
know,
read
clearly
that
the
idea
is
being
conveyed
that
the
structure
of
everything
is
correct.
That
they're,
following
all
of
the
guidelines,
that's
listed
in
each
one,
so
that
tends
to
be
like
the
majority
of
the
work
that
we
do.
Obviously
you
know
if
there's
time
things
that,
like
we
can
clearly
see,
are
going
to
be
like
really
important
proposals,
maybe
we'll
spend
more
time
on
them
and
make
sure
that
they're
like
very
robust.
E
Maybe
we
actually,
you
know
if
we're
reading
an
eep
and
we
have
an
idea
about
it
on
a
more
technical
level.
We
might
mention
that,
but
the
main
goal
of
this
is
just
to
have
a
coherent
directory
of
proposals
to
improve
ethereum.
So
yeah,
that's
that's
what
we
that's.
What
we've
been
doing
on
this
call
for
the
last
bit
is
just
going
through
those
types
of
things,
so
people
can
sort
of
see
what
the
decisions
that
editors
make
yeah.
I
don't
know
sam.
If
you
were
wanting
to
say
something
too.
D
A
A
Have
started
adding
some
of
the
proposals
which
sometimes
get
slips
through
the
graphs,
and
we
are
trying
to
pay
extra
attention
to
proposals
which
are
long
pending.
The
goal
is
that
the
eap
repository
should
not
have
much
of
open
pull
requests
and
people
who
are
submitting
their
pull
request
should
get
proper
attention.
A
So
I'm
sharing
the
link
to
the
agenda.
I
don't
know
if
you
missed
it
earlier.
They
generally
have
this
meeting
once
in
two
week,
and
here
we
are
trying
to
address
to
all
these
full
requests,
which
needs
editor's
attention.
A
So
so
far
in
the
meeting
since
morning,
we
have
looked
into
some
of
the
ambiguous
proposals.
Ambiguous
is
a
tag
that
is
added
by
bot.
We
run
couple
of
eap
bots
and
some
of
these
status
change
requests
which
we're
pending
for
a
while
and
now.
I
think
matt
will
proceed
with
the
list
of
new
proposals
which
have
been
submitted
in
draft.
C
E
Sure
yeah,
so
oh
alex
berry,
zazi
reviewed
this,
so
most
of
the
stuff
we
were
just
doing
was
more
like
just
things
that
have
already
been
reviewed
and
read,
and
we
were
just
making
sure
they
follow
rules
to
move
to
different
stages
and
sort
out
like
why
are
these
not
getting
merged?
And
now?
This
is
something
that
I
haven't
read
before,
and
so
this
is
definitely
the
most
time
consuming
thing.
E
E
We
can
also.
This
is
an
important
thing.
We
can
look
down
here
to
see
if
there's
like
immediately
something
failing
in
travis
ci.
This
does
a
bunch
of
checks
for
us,
so
things
like
spelling
link
checking.
So
we
can
just
click
on
that
and
then
open
up
the
travis
ci
to
see
like
where
it's
failing.
So
we
immediately
see
like
they've
misspelled
compatibility.
E
That's
that's
the
only
thing
that's
causing
it
to
error,
so
we
can
just
like
go
back
there
right
now
and
figure
out
where
that
is
and
just
add
a
change
here,
compatibility
okay,
so
that
will
fix
ci.
And
so
then
we
can
sort
of
start
looking
at
this
to
make
sure
like
first
it
is
structured
correctly.
So
I
just
kind
of
do
a
quick
look
over
this.
These
all
look
good
principle.
E
Token,
that's
a
title
that
I
don't
really
know
what
it
means,
but
it
seems
okay,
so
we
won't
say
anything
about
that
and
then
I'm
just
like
looking
at
the
structure
of
the
still
so
we've
got.
This
is
something
the
bot
doesn't
do
yet,
but
we
should
have
it
do
is
like
we
don't
want
to
make
sure
that
all
of
the
eep
one
sections
are
in
order.
So
the
first
one
is
abstract.
E
They
have
that
motivation
specification,
and
these
are
all
on
the
second
level
of
the
markdown
titles,
and
so
everything
underneath
that
should
be.
You
know
three
four,
just
basic
stuff,
like
they
didn't
capitalize,
a
title
that
should
be
capitalized.
E
I
don't
know
why
they
didn't.
Oh,
these
are
functions.
Maybe
that's
why
they
didn't
okay,
these
are
functions.
Let's
make
these
code
blocks,
so
it's
clear.
E
Sometimes
you
have
to
balance
between
like
going
through
and
making
the
changes
them
yourself
or
like
suggesting
them
yourself,
or
just
like
mentioning,
like
hey
you're,
making
an
error
like
this
over
and
over
again,
you
should
fix
it
and
then
like.
Let
them
come
back
so
because
there's
only
a
handful
of
these,
I
think
I
can
just
do
them,
but
there's
four
then
I
would
have
liked.
C
Is
there
a
template
for
the
headings
that
it
should
follow?
It
was
in
the
handbook,
I'm
not
sure.
E
E
For
the
header,
and
then
it
has
all
the
sections
abstract
and
it
kind
of
explains
like
what
are
all
these
sections.
So
this
is
the
main
interaction
that
people
have
with
like
what
an
eep
should
look
like,
and
so
it
only
defines
like
what
should
be
at
the
second
level
here,
like
abstract
motivation
like
I
was
looking
for,
it
doesn't
say
like
we're
under
specification
right
now
in
this
in
this
one,
and
so
it
doesn't
say
like
what
should
the
like.
E
Okay,
so
we
did
that
we
looked
at
the
specification
next
up
rationale:
that's
their
backwards,
compatibility
reference,
implementation,
security
considerations;
they
got
all
that
okay,
so
the
structure
is
good.
Let's,
like
take
a
look
at
the
actual
text,.
E
An
extension
the
rc20
token,
so
if
it's
an
extension,
it
needs
to
require
it,
so
it
does
require
prc20
and
then
it
requires
26
12,
which
I
think
is
permit.
E
This
kind
of
in-depth
review,
and
especially
some
of
them,
are
just
like
they
need
a
lot
of
work
like
this
is
a
pretty
well
written
one
as
far
as
I
can
tell
it
so
it
can
like
you
know,
you
can
kind
of
nudge
them
in
directions,
and
I
think
that
will
help
a
lot,
but
other
other
ones
are
very
difficult
to
even
like
read,
because
maybe
they're
not
written
by
a
native
english
speaker
and
so
to
like,
actually
get
it
to
like
a
very
coherent
deep
is
like
a
lot
of
work
for
you
as
an
editor
to
do.
E
There's
only
been
a
few
times
where,
after
several
rounds
of
revisions
like
we
still
weren't
able
to
get
to
a
place
that
was
comfortable
merging,
and
so
at
that
point
you
just
kind
of
just
say
like
this.
Is
this
the
grammar
of
this
needs
to
be
improved
to
be
merged,
so
it's
just
like
depends
on
how
much
time
you're
willing
to
like
put
into
a
certain.
C
Yeah,
that
makes
sense,
so
the
focus
is
on
the
grammar
initially
and
and
hopefully
that
we
can
all
get
to
a
point
where,
where
it's
readable
by
everybody,
but
I
think
most
of
them
would
be
in
quite
quite
a
good
state.
I
imagine
sorry,
I
imagine
most
of
them
would
be
at
quite
a
good
state.
To
begin
with
is
that
right.
E
D
Yeah,
I
think
the
the
default
first
pass
is
is
mostly
like
making
sure
they
have
the
right,
headers
and
and
the
right
preamble
and
then
grammar
and
spelling
and
then
technical
content
is
like
the
last
thing
you
look
at.
E
E
A
Is
a
section
for
style,
guide
and
eip1.
E
A
A
F
E
That's
a
good
piece
of
feedback,
so
this
is
something
that's
like
hard
like.
Even
I
like,
I
just
don't
really
interact
with
the
application
layer
enough
to
match
all
these
eips
together
and
so
alex
was
fortunately
able
to
like
point
out
that
this
eep
is
like
really
similar
to
another
eep
4626,
and
so
that's
something
that
it's
not
a
requirement
for
doing
editing
like.
E
I
don't
think
it's
like
reasonable
to
expect
that
we
can
always
you
know,
sort
these
things
out,
but
I
think
that's
like
the
ideal
world
is
that
if
we
see
proposals
that
are
similar,
we
try
and
connect.
Those
authors
like
4626
is
already
final,
and
so
we
can't
like
really
update
it,
and
so
we
should
just
like
make
sure
that
this
eep
that
we're
reviewing
right
now
is
adding.
E
B
Though,
to
be
honest,
if
you
do
erc
editing
for
a
while
focus
like
I
know,
you
also
have
the
corey
eyepiece
that
you're
doing
but
like
I
know
for
me
just
by
like
having
put
in
consistent
effort
on
the
ercs
for
a
while.
You
get
a
pretty
good
idea
of
all
the
usual
suspects.
E
E
B
E
E
E
F
A
A
Of
maybe
information
here
when
we
come
across
similar
proposals
just
like
in
this
case
exec
has
highlighted.
If,
at
all,
the
author
is
trying
to
document
it
for
some
new
feature
or
some
new
change.
There
are
high
chances
that
the
proposal,
which
is
already
similar
and
is
available
as
a
standard,
may
be
added
as
a
required
section.
E
F
F
A
F
E
You
are
wait.
League
has
one
for
8
31.
A
D
D
Of
them
here,
there's
the
eth
call
one
that
I
think
it's
key
or
chi,
that
put
it
put
up
and
there's
this
one,
which
is
completely
different.
Oh
this
one's
different,
okay
yeah,
because
there's
there's
three
that
are
like
in
flight
right
now
that
I'm
remember,
there's
this
one:
there's
the
wallet,
connect,
url
and
then
there's
the
eth
call
url,
and
I
really
feel
like
we
need
to
put
all
of
these
into
one
url
standard,
because
it's
ridiculous.
D
E
Is
the
screen
that
you
had?
Oh,
this
is
the
author.
I
was
looking
to
see
what
this
author
of
this
eep
is
doing
because
I
was
like
it
would
be
great
if
some
of
these
authors
worked
together
on
the
different
ones,
and
I
was
like
who
is
this
person
and
I
just
pulled
up
their
github
and
they
have
committed
every.
E
E
Yeah
I
gotta
bounce
off
as
well
I'll
finish
reviewing
this.
I
don't
know.
I
mean
this
is
just
like
one
of
those
things
again
every
once
in
a
while
comes
up
where
it
would
be
really
nice
just
say:
hey,
there's
a
working
group,
that's
working
on
urls
like
we're
gonna.
Let
them
decide
what
eeps
go
in
related
to
urls
right
now,.
A
All
right,
thank
you,
matt.
I
know
we
could
not
cover
most
of
the
proposals
like
new
proposals,
so
if
anyone
gets
a
chance,
I
know
some
of
them.
Proposals
have
already
received
comments
from
sam
and
there
is
this
new
guy
panda
pip.
He
is
also
trying
to
leave
some
comments
and
review
all
these
proposals
so
yeah.
If,
if
we
get
a
chance,
maybe
we'll
try
to
bring
it
up
in
the
next
meeting,
but
in
the
meanwhile,
if
any
of
those
can
be
addressed
will
be
great
to
have.
A
Thank
you,
everyone
for
joining
us,
so
just
for
information
jen
there
is
another
meeting
eip
ip
which
happens
on
wednesday
alternate
wednesday.
That
is
where
we
discuss
the
rest
of
the
issues
related
to
eips.
I
mean
that
is
again
around
the
ap.
So
if
you
are
interested,
you
can
join.