EIPIP Meeting 79
poojaranjan opened this issue · 8 comments
Date and Time
Apr 19, 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
- ethereum/EIPs#6894
- ethereum/EIPs#6840
- dependency bot
- ethereum/EIPs#6897
- ethereum/EIPs#6905
- ethereum/EIPs#6904
- ethereum/EIPs#6903
- ethereum/EIPs#6902
- ethereum/EIPs#6556 - A bug? EIP status not updated on eips.ethereum.org
2. Discussion continued from earlier meetings
- Yellow Paper
3. EIPW bot Issues
4. EIPs Insight - Monthly EIPs status reporting.
5. EIP Editing Office Hour
6. Review action items from earlier meetings
- Prev. meeting Summary
Next meeting - May 03, 2023?
okay i regret moving to renovate can we please move to a quieter dependency bot
Propose to add ethereum/EIPs#6897 to agenda
Propose to add ethereum/EIPs#6900 to agenda
Yellow Paper
EIPIP meeting is to discuss Ethereum process change/improvement.
PR-6900 is marked for Author's review. It seems like a new proposal. Probably not a good fit for this meeting, unless you think it is process related.
If you've any questions related to the merge of the PR, please share them on the EthCatHerders Discord or join EIP Editing Office Hour.
Having said that, this is an open meeting, and you're welcome to join the meeting.
@poojaranjan I understand, thank you for sharing the additional resources.
Summary
1.
a. PR-6894 - Proposer will address the last comments added by the EIP editor
b. PR-6840 - Generally, editors seem fine with the proposal. Someone can create a Pull Request to propose this change.
c. dependency bot - @SamWilsn will create an Issue to indicate @Pandapip1 to reduce the notification pings.
d. Allow BIPs as an external source. PR-#6897 - @xinbenlv will create a PR to edit it.
e. EIP-3651, 3860, 3855, 4895 - Move to Final - We should wait for author's approval
f. EIP-5507 A bug - @SamWilsn will look into it.
2.
Yellow Paper - @SamWilsn will connect @xinbenlv with the right people to get the required permissions to maintain Yellow Paper.
Closing in favor of #229