Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 02 2018 09:26
    @Arachnid banned @johnny_musk_twitter
  • Jun 06 2018 10:22
    @Arachnid banned @ethsupport1
  • Oct 21 2017 19:12
    @Arachnid banned @Musk11
  • Jun 05 2016 10:37
    @chriseth banned @adamskee
Micah Zoltu
@MicahZoltu
We have no requirement for RFC 2119 right? If an author doesn't want to use it, they don't have to?
Micah Zoltu
@MicahZoltu
Also, what is our stance on people who use the sections incorrectly and don't want to change that? e.g., putting motivation stuff in the abstract or abstract stuff in the specification? Do we just offer the best advice we can and merge to Last Call/Final anyway, or do we require them to get some editor to agree with them that their stuff is in the right section?
(if the latter, I have an EIP for you all to review that I think doesn't have stuff in the right sections)
Greg Colvin
@gcolvin
I think we should pretty much treat the sections as advisory. If the proposal is clear as written I don’t want to fight with an author — it could be a lot of work to rewrite it and keep it clear. If it’s really just a little cut-and-paste that might be different, but laying out a whole policy in advance doesn’t seem worth the trouble.
Micah Zoltu
@MicahZoltu
:thumbsup:
In this case, the author simply disagrees with me on what content is appropriate for what sections, I don't think it is an issue of difficulty of the change. :smile:
If someone other than me wants to review this move to Last Call that would likely be appreciated by the author. :smiley: ethereum/EIPs#2832
Greg Colvin
@gcolvin
I’ll get to when I can - traveling now - thanks
Micah Zoltu
@MicahZoltu
@lightclient Would be cool if the automated EIP spellchecker left suggestion comments (the ones that let you one-click apply) on so the author doesn't have to go through and manually fix them all.
Micah Zoltu
@MicahZoltu
Any editors get a chance to check out ethereum/EIPs#2832 for moving into Last Call? Its review end period continues to approach...
Greg Colvin
@gcolvin
Hi @MicahZoltu still at lodge with no WiFi and almost no 4G. Skimmed comments on #2832, not sure why you can't move it and deal with any remaining issues in Last Call. I haven't bandwidth for more, Sorry.
Micah Zoltu
@MicahZoltu
My issue is that the author thinks the sections have a different purpose than I do and they have no intention of resolving it. I am not a dictator, nor want to be one, so I won't fight against any editor merging as last call, but I personally don't think it is using the sections correctly for an EIP so I don't feel comfortable merging it to Last Call myself.
James Hancock
@MadeofTin
The sections are not defined or clarified well. I remember writing my first one and thinking. “So you are asking me to say the same thing 3 times? I don’t get it 🤷‍♀️”
No problem not merging it if you don’t feel comfortable. 👌
If all the editors don’t feel comfortable then that is on them.
Micah Zoltu
@MicahZoltu
Yeah, I agree the sections aren't terribly clear, which is why I try really hard to coach authors through the section meanings and help them move things around into the proper sections.
  • Simple Summary: One-liner "what is this".
  • Abstract: What this EIP does (human readable).
  • Motivation: Why this EIP exists.
  • Specification: Technical (almost computer readable).
  • Rationale: Why specific decisions were made.
Sometimes I run into an author that simply disagrees with me on the section purposes and thinks the Abstract should contain "why", in which case I leave it to other editors to merge. :smile:
Micah Zoltu
@MicahZoltu
Does anyone know what the cause of the CI error that @poojaranjan is running into with ethereum/EIPs#2809 is?
Jekyll Feed: Generating feed for posts

Liquid Exception: Liquid error (/home/travis/build/ethereum/EIPs/_includes/eiptable.html line 11): comparison of Array with Array failed included in all.html
lightclient
@lightclient
I'm not certain, but it may be due to this: https://github.com/ethereum/EIPs/pull/2809/files#r466508384
Pooja Ranjan
@poojaranjan
It worked, thank you @lightclient :)
lightclient
@lightclient
woot!
Pooja Ranjan
@poojaranjan
I'm not sure where this proposal will go but happy to learn one of the basic requirements to get the bot ✔️ and have a strong feeling that a session on EIP tips could be useful for many others like me. Thank you @MicahZoltu for bringing it here.
Greg Colvin
@gcolvin
@MicahZoltu briefly found bandwidth here in the woods. My take is that so long as the Summary and Abstract are clear and a person with relevant skills can implement the RIP from the Spec I'm happy.
Later..
lightclient
@lightclient
I've opened a draft PR to swap in eipv as the new eip validator in travis. Since eipv is more strict than the existing validator, a lot of cleanup was necessary (trailing whitespaces, weird newlines, etc). Please take a look at it and share your feedback! Since this PR touches so many EIPs, I'm not sure what the best way to proceed is w.r.t. merging this. ethereum/EIPs#2860
eipv is still not feature complete, but it AFAICT it covers all cases that current validator coves + more. To see (and request) additional validations, please see the eipv repo: https://github.com/lightclient/eipv
Micah Zoltu
@MicahZoltu
@gcolvin Next time you have internet, you should merge that PR if you are OK with its formatting. :smile:
Pooja Ranjan
@poojaranjan
EIPIP meeting 14
Date: Wednesday, Aug 12, 2020, at 15:00 UTC
Agenda: ethereum-cat-herders/EIPIP#26
Greg Colvin
@gcolvin
@MicahZoltu We decided that we are on vacation ;)
Micah Zoltu
@MicahZoltu
:laughing:
Pooja Ranjan
@poojaranjan
EIPIP meeting 14
Date: Today, Aug 12, 2020, at 15:00 UTC (~4.5 hrs from now)
Agenda: ethereum-cat-herders/EIPIP#26
Join Zoom Meeting
https://us02web.zoom.us/j/82004604182?pwd=UzBZOWdQQUE0WmZvWENEOG5jL2dZQT09
Meeting ID: 820 0460 4182
Passcode: 136915
Pooja Ranjan
@poojaranjan
I have got a few questions about Standard track EIPs other than core.
I'm curious to understand who/how their next status is decided. Given, they follow the same process as EIP, I suspect status is decided by the same process and EIP authors change the status.
Other than the GitHub issue and Eth Magician does it get discussed anywhere else?
Do we know a big amount of open PRs at EIP repo are for ERCs and other Standard track EIPs? If these are addressed many PRs can be closed.
The current stats. for ERC suggests Accepted =14, Last Call = 3, Draft = 100. 2/3 Last call period already ended in 2019.
Is there anything that Cat Herders can help with?
Micah Zoltu
@MicahZoltu
@poojaranjan Non-core EIPs can move into Last Call at the author's request, after an editor verifies it is well formed and sufficiently descriptive.
Once we have the new statuses like Withdrawn/Abandoned we can go through and clear out all of the DRAFTs that have been sitting forever.
Probably wouldn't hurt to make a pass through the Last Call EIPs and check with the authors to see if they are ready to move forward.
lightclient
@lightclient
is there a reason to not mark eips as abandoned today? it's recognized as a status in eip-1
Micah Zoltu
@MicahZoltu
Oh, is only Withdrawn missing?
lightclient
@lightclient
yes
Micah Zoltu
@MicahZoltu
Someone probably should then.
lightclient
@lightclient
abandoned is also supported by eipv so i don't think anything is blocking that from happening
Pooja Ranjan
@poojaranjan
@MicahZoltu thanks for clarifying.

Probably wouldn't hurt to make a pass through the Last Call EIPs and check with the authors to see if they are ready to move forward.

I am already in touch with one, will try to contact the rest two.