Skip to content

Fix inconsistent naming in RFCs and update the status of some RFCs#447

Open
zhangsoledad wants to merge 1 commit into
nervosnetwork:masterfrom
zhangsoledad:zhangsoledad/fix-inconsistent
Open

Fix inconsistent naming in RFCs and update the status of some RFCs#447
zhangsoledad wants to merge 1 commit into
nervosnetwork:masterfrom
zhangsoledad:zhangsoledad/fix-inconsistent

Conversation

@zhangsoledad

Copy link
Copy Markdown
Member

This PR unifies the naming conventions across multiple RFCs, ensuring consistency in RFCs. Additionally, it updates the status of several RFCs to reflect their latest status.

@zhangsoledad zhangsoledad requested review from a team and xxuejie as code owners March 12, 2025 15:27
@zhangsoledad zhangsoledad requested a review from doitian March 12, 2025 15:27
@XuJiandong

XuJiandong commented Mar 13, 2025

Copy link
Copy Markdown
Contributor

In older documents or other sources, some references still use outdated naming conventions.
Can we provide a mapping table, such as:

Edition CKB2023 → CKB Edition Meepo (on 2024/??)

@zhangsoledad

Copy link
Copy Markdown
Member Author

In older documents or other sources, some references still use outdated naming conventions. Can we provide a mapping table, such as:

Edition CKB2023 → CKB Edition Meepo (on 2024/??)

https://github.com/nervosnetwork/rfcs/blob/5a0e339bcbd88f6ca283cd57a13b1c808503313f/rfcs/0053-ckb-hardfork/0053-ckb-hardfork.md#historical-editions @XuJiandong

@xxuejie

xxuejie commented Mar 19, 2025

Copy link
Copy Markdown
Contributor

Just being curious: why do we name it as CKB Edition Meepo, I feel that CKB Meepo Edition is more like proper English grammar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants