Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epic: post-merge content updates #7075

Closed
59 tasks done
jmcook1186 opened this issue Jul 15, 2022 · 7 comments
Closed
59 tasks done

Epic: post-merge content updates #7075

jmcook1186 opened this issue Jul 15, 2022 · 7 comments
Assignees
Labels
epic 💪 This issue is an epic on our product roadmap feature ✨ This is enhancing something existing or creating something new

Comments

@jmcook1186
Copy link
Contributor

jmcook1186 commented Jul 15, 2022

Epic Description

The Merge is almost upon us. Ethereum.org has recently been updated to ensure that the content is up-to-date and correct for the final months of pre-merge Ethereum (#6281). Now, as part of our Q3 roadmap (#7166) we will create a branch of ethereum.org with content appropriate for post-merge Ethereum, with the intention to merge this branch in once The Merge is complete.

Involves

  • Scoping out what content changes, additions, or subtractions are required related to the Merge upgrade (done, tracked in Excel sheet)
  • Preparing appropriate content changes,
  • Coordinating with external contributors to ensure accuracy
  • Timing releases appropriately to provide the community with accurate information about the Merge during and immediately after transition

Goals

  • Ensure references to proof-of-work are updated to either be historical references, or removed
  • Update developer documentation to ensure all fundamentals are accurately represented under the proof-of-stake model
  • Update /upgrade/merge and to be reflective of past tense and latest information
  • Update /energy-consumption page with updated latest information

Checkpoints

Page Audit Spreadsheet

The following pages have been identified as requiring post-merge adjustments (tick off when PR merge to post-merge branch):

@jmcook1186 jmcook1186 added the feature ✨ This is enhancing something existing or creating something new label Jul 15, 2022
@samajammin samajammin added the epic 💪 This issue is an epic on our product roadmap label Jul 28, 2022
@samajammin
Copy link
Member

samajammin commented Sep 16, 2022

FYI @jmcook1186 @wackerow updated the issue description to include the /upgrades/merge/issuance/ page.

I think(?) once that's done, we can close this issue out?

@wackerow
Copy link
Member

wackerow commented Sep 16, 2022

Sounds good. A community member also reported that the Ethereum Vision page also still notes "Too much energy" as one of the problems facing Ethereum today:
image

I think we should update this. Few options include:

  1. Change the title to be more broadly the issues that are being addressed, and update the description for that third card to be more of a reflection
  2. Remove this card
  3. Replace the card with a new issue that challenges the scalability of Ethereum

Open to suggestions

@samajammin
Copy link
Member

A community member also reported that the Ethereum Vision page also still notes "Too much energy" as one of the problems facing Ethereum today:

Yes great point!

I'm open to any ideas. I like the idea of (1), to change the section title (maybe something like "Problems being addressed"). Then in each card description, we could link to resources on how the problem is being tackled:

  • Clogged network: mention roll-up centric roadmap & link to L2 page?
  • Disk space: linking to sharding / research resources on state expiry?
  • Energy consumption: mention this is largely solved, link to Merge/PoS page?

@chomusuke-works
Copy link

A community member also reported that the Ethereum Vision page also still notes "Too much energy" as one of the problems facing Ethereum today:

i also like solution (1), maybe alongside adding a green frame to the tile and a "solved since the Merge" text going with it?

@wackerow
Copy link
Member

Just noting that #7931 was intended to be a quick patch while planning a new approach here.

I may push back on approach 1 in the form of linking out to solutions, since the user is then more likely to leave the page when there is more to engage with below to explain more and then links out to the upgrades pages.

Would personally advocate for 3 and list another problem instead.. maybe privacy, censorship-resistance, or mev? Open to ideas. Note that we already have a callout lower in the page about the energy reduction and low-carbon output of Ethereum now.

@samajammin
Copy link
Member

Hey @jmcook1186 @wackerow - is this complete? Can this be closed out?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic 💪 This issue is an epic on our product roadmap feature ✨ This is enhancing something existing or creating something new
Projects
None yet
Development

No branches or pull requests

5 participants