Add fork folders, other minor changes #913
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To improve our usage of the
pmrepository, and declutterexecution-specs, I propose we begin using fork-specific folders to track things like mainnet readiness checklists, devnet specs, and more. When a fork has gone live, we can migrate its folder from the top level one to/Archive.The
pmrepository is already well-known, and this would create an easy place to point people to when they want to track a specific fork. Additionally, the "specs" we've been using inexecution-specsto track EIPs considered/included in network upgrades currently contain client implementation status information, which feels out of scope.We can easily add this information to mainnet readiness checklists instead. As an example, I've pulled the (out of date) table from
cancun.mdand added it to/Dencun/4844-readiness-checklist.md.Discussion about the right way to handle the network upgrade specs is out of scope for this PR 😄