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

CIP-0020 | Adjust preamble and structure w.r.t CIP-0001 #410

Closed
Tracked by #389
KtorZ opened this issue Dec 8, 2022 · 4 comments · Fixed by #647
Closed
Tracked by #389

CIP-0020 | Adjust preamble and structure w.r.t CIP-0001 #410

KtorZ opened this issue Dec 8, 2022 · 4 comments · Fixed by #647
Assignees

Comments

@KtorZ
Copy link
Member

KtorZ commented Dec 8, 2022

Partially done in #394. Only the Path to Active is missing from there as well as renaming the "Motivation" and "Rationale" to their question-like format. But preamble and other sections have been updated accordingly.

@KtorZ KtorZ self-assigned this Dec 8, 2022
@rphair
Copy link
Collaborator

rphair commented Dec 8, 2022

OK, when I was re-reading this I was wondering how in general to assign Path to Active for proposals already Active for a while... will be following this one 🤓

@KtorZ
Copy link
Member Author

KtorZ commented Dec 8, 2022

🤷 , I think the general strategy is mostly about (a) trying to remember why we turned it into active (meeting minutes help remembering here) and (b) capturing this honestly in a few bullet points.

@rphair
Copy link
Collaborator

rphair commented Dec 8, 2022

thanks @KtorZ & I'll infer what might already have been stated or obvious, but is counter-intuitive for me... that all merged proposals (unless maybe deliberately declared Inactive?) must have a Path to Active that describes both the acceptance criteria (even if already accepted) & the implementation plan (even if already implemented).

@rphair
Copy link
Collaborator

rphair commented Dec 20, 2023

Fixed by #647.

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 a pull request may close this issue.

2 participants