EIPIP Meeting 76

[poojaranjan]

Date and Time

Mar 08, 2023 at 14:00 UTC

Location

Zoom: TBA in the Discord #eip-editing channel

YouTube Live Stream/Recording: https://www.youtube.com/playlist?list=PL4cwHXAawZxpLrRIkDlBjDUUrGgF91pQw

Agenda

1. Discuss Open Issues/PRs, and other topics

• Interim Editor for EIP number assignment Ref & PR
• Full Spell Check Ref: Discussion
• Only check sibling headers for sameness ethereum/EIPs#6643

2. Discussion continued from earlier meetings

• Website: Rewrite index with filters ethereum/EIPs#6483
• Website: more rss feeds ethereum/EIPs#6579
• Discuss policy to add a champion or co-author to an EIP
• Moving away from Jekyll
• Update EIP-712: Fix eth_signTypedData definition ethereum/EIPs#5457
• Website: Migrate to vitepress ethereum/EIPs#6518

3. EIPW bot Issues

• Special case markdown-rel-links to help when linking to eips.ethereum.org ethereum/eipw#5

4. EIPs Insight - Monthly EIPs status reporting.

• EIPsInsight.com
• Hackmd

5. EIP Editing Office Hour

• Agenda Meeting 13

6. Review action items from earlier meetings

Prev. meeting

Next meeting - Mar 22, 2023?

[abcoathup]

I believe EIP #s should be assigned quickly to reduce friction to the EIP process. (In my day job I include EIP/ERCs so want to use the appropriate #).

Until it can be automated or numbers are sold, then I offer my services as an EIP or ERC editor to help assign numbers quickly.

I am keen to avoid any perceived number gaming by ERC authors. As an ERC author I had an ERC number changed due to number lunging (ethereum/EIPs#4888 (comment)), so have a strong appreciation for perceived value of numbers and transparency of the number assigning process.
See: ethereum/EIPs#5294 (comment)

I visit the EIP repo most week days, but work in the Australian time zone so wouldn't want to attend EIPIP meetings at their current time.

---

Alternatively, I'd like to see a more optimistic approach to EIP/ERC # assignment. That authors can use the earliest PR # for their EIP/ERC unless there is number gaming and this is quickly resolved.

---

Recent queries I have had on EIP/ERC #s.
ethereum/EIPs#6538 (comment)
ethereum/EIPs#6506 (comment)

[Pandapip1]

I hope we can get the migration to vuepress done before the next EIPIP meeting, but if the PR is still open, it should be discussed during the meeting.

I also opened ethereum/EIPs#6575 in response to @abcoathup's comment. I am +1 to adding him as an editor.

[poojaranjan]

@Pandapip1

I hope we can get the migration to vuepress done before the next EIPIP meeting, but if the PR is still open, it should be discussed during the meeting.

Please share the PR link, if not merged.

[poojaranjan]

Summary

1. Discuss Open Issues/PRs, and other topics

a. Interim Editor for EIP number assignment
A bot for the allocation of EIP numbers is in progress. @SamWilsn and @lightclients think it would add value if the proposer considers reviewing EIP/ERC and not just the EIP# allocation. @abcoathup may let editors know about extending the contribution.

b. Full Spell Check
@JEAlfonsoP has a proposal to add words to Code Spell Check. In the meantime, @Pandapip1 may add words if anyone will make a PR with new words.

c. ethereum/EIPs#6643
Approved & Merged.

2. Discussion continued from earlier meetings

a. ethereum/EIPs#6483
The proposer needs to keep "all" in order to maintain google SEO.

b. ethereum/EIPs#6579
@poojaranjan will check with EF team for the use of 3rd party email services to send out RSS feed. Also, check if proposer @fulldecent is open to using any other 3rd party email services.

c. Discuss policy to add a champion or co-author to an EIP
(skipped)

d. Moving away from Jekyll
under consideration

e. ethereum/EIPs#5457
Merged

f. ethereum/EIPs#6518
Requires more discussion

3. EIPW bot Issues

a. ethereum/eipw#5
@JEAlfonsoP working with @SamWilsn, made a PR

Peer reviewing

Add more reviewers to the list. Reach out to Sam Wilson if interested in peer reviewing.

[fulldecent]

Address file name at 4693f759ab3e92b0c11912909a1d84701a2ac39a in https://github.com/ethereum/EIPs/pull/6483/commits

[xinbenlv]

Hi @poojaranjan could we include this issue next time: ethereum/EIPs#5682 ?
FYI: @kdenhartog, @chaals

[poojaranjan]

Hi @poojaranjan could we include this issue next time: ethereum/EIPs#5682 ? FYI: @kdenhartog, @chaals

Added!

[poojaranjan]

Closing in favor of #219