►
From YouTube: EIP Editing Office Hour 16
Description
Agenda: https://github.com/ethereum-cat-herders/EIPIP/issues/228
B
Welcome
to
EIP
editing
office
hour
meeting
17.
Thank
you,
authors
for
joining
us
and
thank
you,
Sam
Wilson,
for
joining
us
and
helping
out
these
authors
to
review
these
proposals.
I
have
shared
a
link
to
the
agenda
in
chat.
If
you
would
like
to
go
ahead
and
share
your
screen,
the
first
one
for
review
here
is
PR
number
6808
and
the
same
team
has
6809.
So
we
can
start
from
there.
C
D
C
F
C
Yep
exactly
so
it'd
become
like
it
gets
an
EIP
number
and
I
I
like
as
much
as
any
of
this
process
is
formalized.
That's
the
this
is
the
first
step
of
it
yeah,
okay
and
then,
whenever
you
guys
are
ready,
you
can
open
a
pull
request
to
move
it
to
review
and
that's
generally
once
you're
fairly
confident
there
aren't
going
to
be
any
more
substantial
changes
and,
if
you're,
confident
now
you
could
do
that
tomorrow.
If
you
want,
or
or
later
today,
yeah
okay.
C
Okay,
yeah
so
I'll
just
give
this
a
read
just
one
thing
to
point
out
and
and
I
I'm
trying
to
do
this.
For
everybody
who
comes
to
these
meetings
once
you
go
to
final,
there
are
no
changes
permitted
so
make
sure
you
have
everything
in
order
before
you
make
the
pull
request
to
go
into
last
call.
D
G
C
So
as
long
as
everything
is
like
small
changes
like
that,
I'll
just
commit
them
when
I'm
done
reviewing
Congress
return,
false
good.
C
Generally,
we
don't
use
horizontal
rules,
not
a
huge
issue
at
all,
secure
good,
good.
D
F
Yeah,
the
major
changes
in
these
sections
were
just
the
removal
of
some
of
the
footnotes,
so
it
wasn't
so
repetitive
for
the
reader
to
easily
digest
the
information
that
is
there.
C
D
Okay,
kpg
20
good
good.
C
Yeah
I
think
that's
that's
perfect.
So
I
will
do
this.
C
Oh,
could
you
check
the
allow
edits
from
maintainers
option
on
the
pull
request,
so
I
can
just
commit
these
for
you
or.
F
That
up
and
that
will
most
probably
have
the
same
changes
they
just
have.
C
D
D
D
C
Yeah
this
just
to
confirm
this
is
the
correct
interface
for
this
heading.
D
C
Right
so
I
will
just
leave
these
like
this
and
we
can
come
back
to
those
in
a
bit.
B
H
Yes,
so
my
question
is
basically
just
around
yeah,
this
sort
of
review
for
format,
sort
of
content,
expectations
and
yeah
like
we're
still
expecting
it
to
stay
in
the
draft
stage
for
a
little
bit,
we're
working
with
community
members
and
revising
it,
but
yeah
just
sort
of
a
general
review
of
the
proposal
sort
of
what
we
like
right
now.
Okay,.
C
Yeah,
so
how
familiar
are
you
with
the
EIP
process.
H
I've
sort
of
tracked
the
guides
and
sort
of
walkthroughs
on
youth
magicians
and
can't
hurt
us
I've
tried
to
follow
the
best
I
can
but
that's
sort
of
the
extent.
Okay
yeah.
C
That's
perfect,
so
just
like
the
the
quick
overview,
this
is
almost
an
entirely
author
driven
process.
So
at
each
stage
we'll
expect
you
to
open
a
pull
request
to
move
it
to
the
next
status
whenever
you're,
ready,
I.
H
Okay,
yep
sounds
good
cool
yeah,
it's
sort
of
a
wide
reaching
proposal,
so
there's
been
some
discussion
on
youth
magicians
Forum,
so
we're
sort
of
expecting
to
go
through
a
couple
rounds
of
drafts
before
making
that
move
perfect.
C
C
It's
the
what's
the
common
Mark
way
of
doing
that:
I
think
it's
an
exclamation
mark.
C
C
Good
good
motivation,
no,
no
rationale
mixed
up
in
there.
G
D
H
I
think
it
was
just
to
sort
of
make
it
easier
to
like
skim
past
it
and
stay
on
the
text
portion
of
it,
but
we
can
definitely
like
adjust
it
to
fit
whatever
sort
of
style
expectations.
There
are
yeah.
H
H
Also
for
I
guess
it's
relatively
large,
like
interface
code
blocks
like
this,
would
you
recommend
moving
it
to
just
be
like
a
linked
asset
or
to
keep
it
in
the
proposal
itself?.
C
That's
a
good
question,
and
it's
mostly
up
to
to
you
guys
the
authors
I
it
like
my
personal
view
is
that
if,
if
you
can't
really
understand
the
Eep
and
you'd
be
referring
to
the
the
asset
like
often
while
you're
reading,
that
it's
probably
better
to
have
it
in
line,
but
if
it's
really
big
or
something
along
those
lines
and
yeah,
it
makes
sense
to
have
it
as
an
asset.
So
your
call.
E
D
B
H
C
Admonitions,
that's
what
they're
called
at
least
in
the
the
GitHub
vocabulary.
C
Yeah
I
think,
if
you
just
use
like
a
quote
and
the
emoji
for
a
warning
or
a
light
bulb
that
would
also
work
yeah.
That
looks
good
good.
What
is
this?
This
is
a
an
example.
C
H
Yeah,
it's
the
intention
sort
of
an
explanatory
component
for
a
like
coding
practice
that
isn't
commonly
done
yeah,
that's
generally,
but
without
like
necessitating
as
part
of
the
spec,
because
you
know
you
can
implement
it
in
non-solidity
in
many
other
ways.
So
yeah
yeah.
C
G
C
Otherwise,
I
think
that's
really
well
done.
B
So
the
next
one
here
we
have
is
for
last
call
pull
request.
Number
is
6672.
B
D
G
D
D
D
C
B
Right
so
the
next
one
is
PR
number
is
six
nine
double
six
and
the
EAP
is
double
five.
Seven,
zero
moving
to
last
call
yeah.
D
B
D
C
D
C
Can
somebody
with
a
better
font,
open
this
Eep
and
tell
me
what
this
character
is,
because
mine
is
not
rendering
it.
B
E
B
B
G
C
We
allow
W3
standards,
yet
we
do
not.
D
D
D
B
D
C
D
D
D
D
C
D
D
D
D
C
All
right,
that's
pretty
reasonable.
D
D
D
D
D
D
D
D
C
All
right
and
there
we
go
I-
have
to
hop
off
to
get
ready
for
my
next
meeting.
Thanks
everybody
for
coming
out
and
yeah
talk
to
you
in
two
weeks.
B
A
Yes,
can
you
hear
me
yes,.
A
Yeah
hi
everyone.
This
is
Victor
and
one
of
the
EIP
editors,
and
some
of
you
might
know
that
we're
starting
an
all
ERC
Dev
call
a
regularly
meeting,
intend
to
let
view
the
community
so
that
ERC
authors
developers,
my
contract
and
the
app
adapts
can
kind
of
help
each
other
meet
up
and
and
learn
from
each
other
things
like,
and
we
want
to
make
and
make
it
easier
for
people
to
do
Tech
and
code
peer
review
and
to
kind
of
promote
their
ercs
for
more
adoptions.
A
The
general
idea
is
that
the
more
that
we
can
learn
from
each
other
and
then
pass
the
knowledge
and
information
around,
we
will
be
able
to
kind
of
Advocate
better
for
open
standardization,
and
this
is
just
like
all
core
devs.
This
is
a
place
for
developers
who
are
interested
in
ERC
ref,
ERC
erc's.
A
So
if
you're
interested
hop
on
this
thread
and
then
we'll
be
pulling
the
convenience
the
improving
the
interest
in
the
time
slot.
So
if
you
can
kindly
in
this
form,
that
would
be
great
and
then
I
know
that
you
won't
be
have
access
to
this
chat
message
later
on.
I'll
also
put
it
in
the
Discord
channel
of
VIP
editors
in
the
ethereum
cap,
herders
thanks
everyone
and
look
forward
to
meet
you
Puja.
Thank
you
very
much
for
the
time.