Since eips.ethereum.org doesn’t have linking to headings, here’s a github link: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1.md#eip-work-flow
Scroll down to "Work in progress (WIP)” and check out the entire paragaph.
Oh, and if you hover over the heading, and click on the link icon, it will generate you a link to that header.
Hovering over “EIP Work Flow” doesn’t do anything on Firefox.
Well, I have been away from the internet and missed a lot here. I will share my thoughts in brief.
For the community members who don't regularly use Github any EIP that is not on http://eips.ethereum.org/ doesn't exist. They don't understand what a pull request means and that technically being a PR or merged as Draft are not different. Pointing them to a PR that requires a lot of background knowledge about Github and general CS is more than confusing, it is a barrier to entry.
On #2025 I have requested comments multiple times on this channel and have received none. A lack of comments shows a lack of opposition to being merged. If I have to wait for someone to make a comment I may have to wait for ever.
What does it mean to be technically sound. The idea of Block Rewards is technically sound. I am not sure what is confusing about the specification. Either way rather than debate what it means to be Technically sound or not, I suggest we remove that language from EIP-1.
100 messages since yesterday, so my opinions are based on a quick skim, sorry.
@Arachnid says, "Virgil is working on an alternate EIP process that brings in an external standards company to manage the process.”
This sounds like a terrible idea, unless the outsider is little but a clerk. But then I can’t see needing a whole company. I believe Hudson the @Souptacular is on salary, and overloaded with responsibilities. Perhaps the EF can hire him an asstiant?
@MadeofTin says, "For the community members who don't regularly use Github any EIP that is not on http://eips.ethereum.org/ doesn't exist."
Yes, this is pain. https://github.com/ethereum/EIPs/issues can be a good place for proposals that are ready to discuss, (at the author's option) but not to write up in the full form of a draft. The number that is assigned is from the same series as the PR numbers, so can serve as the EIP number, and stay the same if a PR is made. Discussions can be sent to the Magicians if desired. And Github now maintains a history of edits to the issue. So a working copy of a proposal can be maintained with simple source control, and a simple editor. And abandoned proposals only clutter the Issue space, not the PR space.
And I thought we agreed long ago, and reaffirmed after the lost funds hassle, that Draft PRs only needed to meet the form of a PR. Thus the auto-merger. And I don’t think we should require an implementation to get to Final, though in Last Call it might be called out as needed for a particular PR.
And all this may be irrelevant if I’ve misunderstood. And now I need to get back to earning a living. I’ll check in later. Thanks.