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 (https://github.com/ethereum/EIPs/pull/4888#issuecomment-1064757848), so have a strong appreciation for perceived value of numbers and transparency of the number assigning process. See: https://github.com/ethereum/EIPs/issues/5294#issuecomment-1189733761

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. https://github.com/ethereum/EIPs/pull/6538#issuecomment-1442658463 https://github.com/ethereum/EIPs/pull/6506#issuecomment-1432288507

Pandapip1 commented 1 year ago

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 https://github.com/ethereum/EIPs/pull/6575 in response to @abcoathup's comment. I am +1 to adding him as an editor.

poojaranjan commented 1 year ago

@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 commented 1 year ago

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. https://github.com/ethereum/EIPs/pull/6643 Approved & Merged.

2. Discussion continued from earlier meetings

a. https://github.com/ethereum/EIPs/pull/6483 The proposer needs to keep "all" in order to maintain google SEO.

b. https://github.com/ethereum/EIPs/pull/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. https://github.com/ethereum/EIPs/pull/5457 Merged

f. https://github.com/ethereum/EIPs/pull/6518 Requires more discussion

3. EIPW bot Issues

a. https://github.com/ethereum/eipw/issues/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 commented 1 year ago

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

xinbenlv commented 1 year ago

Hi @poojaranjan could we include this issue next time: https://github.com/ethereum/EIPs/issues/5682 ? FYI: @kdenhartog, @chaals

poojaranjan commented 1 year ago

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

Added!

poojaranjan commented 1 year ago

Closing in favor of #219

ethcatherders / EIPIP

EIPIP Meeting 76 #217

Date and Time

Location

Agenda

1. Discuss Open Issues/PRs, and other topics

2. Discussion continued from earlier meetings

3. EIPW bot Issues

4. EIPs Insight - Monthly EIPs status reporting.

5. EIP Editing Office Hour

6. Review action items from earlier meetings

Summary

1. Discuss Open Issues/PRs, and other topics

2. Discussion continued from earlier meetings

3. EIPW bot Issues

Peer reviewing