Skip to content

CIP-0001, CIP-9999, README & templates: periodic update #1044

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

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

rphair
Copy link
Collaborator

@rphair rphair commented Jun 11, 2025

A more-or-less annual update to fix/clarify these issues that came up over the last year or so (since #924):

  • Don't include commits from previously submitted PR's... submit your new PR from a branch that's been rebased on main (as described here)
  • Don't do "force push": with reason explained here to someone who hadn't done it before, preemptively (in terms of usability of commit history)
  • Don't put backticks in CIP titles (we had to remove them here)
  • Add Consensus and Network categories to CIP and CPS templates (pointed out here)
  • Ensure the ordering in the templates match the orderings in CIP 1 & -1 AND the prevailing document order (as explained here): with the more taxonomically significant term Category appearing before Status everywhere (not adjusting other CPS documents "out of sync" since field ordering is not agreed to really matter)
    • It would be even more important for Category to generally precede Status especially since contemporary discussions for different processes to be followed for different processes (e.g. Ledger especially) might lead to different possible Status per Category (see @WhatisRT discussion point here - cc @yHSJ)
  • Migrated existing "notes" to GitHub Alerts (now that they are supported) from things like lightbulb icons within ordinary blockquotes.
  • Updated front page so lists of CIPs & CPSs appear with
    • most currently discussed actively reviewed proposals appearing first
    • least recently discussed flagged "not progressing" proposals appearing first
  • For categories, changed "registered" to "editorially accepted" (since there is no central means of "registering" anything as there might have been during the formerly organisational process of "enlistment")

This is intended to provide a more current baseline in anticipation of further updates from one or more of these issues:


(new front README) - (new CIP-0001) - (new CIP-9999)

@rphair rphair self-assigned this Jun 11, 2025
@rphair rphair added Update Adds content or significantly reworks an existing proposal Category: Meta Proposals belonging to the 'Meta' category. State: Triage Applied to new PR afer editor cleanup on GitHub, pending CIP meeting introduction. labels Jun 11, 2025
@rphair rphair requested a review from Ryun1 June 11, 2025 16:00
@rphair
Copy link
Collaborator Author

rphair commented Jun 26, 2025

@Ryun1 @Crypto2099 I talked a bit about these changes at yesterday's CIP meeting & the community observers could also see the importance of merging these diverse particulars before specific CIP process issues will likely be reviewed in the weeks ahead: so we should merge this (after modifying if necessary) before that period. 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Meta Proposals belonging to the 'Meta' category. State: Triage Applied to new PR afer editor cleanup on GitHub, pending CIP meeting introduction. Update Adds content or significantly reworks an existing proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants