-
Notifications
You must be signed in to change notification settings - Fork 243
Update timeline.yaml #1637
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
base: master
Are you sure you want to change the base?
Update timeline.yaml #1637
Conversation
Update to current milestones
✅ Deploy Preview for ethereumclassic ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@copilot can you fix this PR, so that it builds preoprly? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the Ethereum Classic timeline to include current milestones and events. It adds new historical events and enhances existing entries with more detailed attribution information.
- Adds
__dateTextfields to existing timeline entries for better attribution - Includes new milestone events from 2024-2025 including team wind-downs, upgrades, and anniversary celebrations
- Expands the timeline with additional historical context and recent developments
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
realcodywburns
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
add more events review icons review colors review accuracy
| __icon: cubes | ||
| __link: https://coinmarketcap.com/community/articles/688a1da31c29df0fa3641d03/ | ||
| text: Ethereum Classic turns 10. Explore the untold story of the original Ethereum chain that upheld immutability, preserved Proof-of-Work, and now powers the smart contract layer for PoW assets. | ||
| roadToOlympia: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need TWO Olympia plugs in the timeline.
Requesting the removal of the CMC article item, especially as it's editorialized title is misleading.
| __icon: handHoldingUsd | ||
| __link: https://x.com/ETCGrantsDao/status/1973818014786347151 | ||
| text: As core developers organize the path to long-term protocol-level funding through Olympia, Bitmain steps in as a stopgap to help fund core client development while the community finalizes implementation details. | ||
| olympiaDay: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As explained in #1649 (comment)
I do not think its appropriate to be describing a Draft ECIP in these terms.
the ECIP authors judge the Olympia suite (1111–1114) sufficiently polished to begin implementation
This is just false as anyone who's been on the calls would be able to testify.
I don't understand why this kind of language is being pushed and approved @realcodywburns
We need to be careful about maintaining neutrality on these community channels and not be seen to be pushing a particular bias on one side of the debate.
Update to current milestones