-
Notifications
You must be signed in to change notification settings - Fork 319
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
Update older CIPs for revised CIP-0001 #389
Comments
@KtorZ before we get too far into this list, can we reformat the items in the outline above from e.g. :
to
Otherwise the email notifications for all these new PRs and issues will be hard to tell apart, with the distinguishing element so deep into the title. They'll still collate as currently above but will require a wider screen to view. There could also be some historical benefit to using the same format that we use for all our other issues & PRs... rather than having them all stand out as parts of a once-off editing process. If you and @crptmppt @SebastienGllmt agree I can easily script that change... as could you, but I'm ready, willing & motivated to do it right now 😎 |
Done! |
@KtorZ noting also re: resolution at CIP meeting today that we are currently obligated to mark previously merged RSS |
@Ryun1 @KtorZ with the new versioning clarification proposed in #563 I think we might also have to add version treatment to the outline of things to do here... at the very least, to consider adding it (although this could depend on consensus with authors & other proponents, which might not be possible). |
@KtorZ @Ryun1 @Crypto2099 my Catalyst Fund 10 project has been approved, with filing PRs for all of these as the Q4 2023 milestone. 😬 I've added it to the CIP meeting agenda today so we can talk about how the editorial process would best proceed for these. 😇 |
FYI as of now, I've created issues for all the CIP remediations above & linked each one of the unresolved issues to one of 41 new PRs which we can work on refining, approving & merging some time soon in the New Year. 🎉 |
* double check CIP-0001 compliance as per #389 * spelled NA instead of standard N/A
Great work on this @rphair 💪 Im sure it will feel very satisfying to press the |
Thanks for the great backup & insight... you guys are awesome 🤩 |
* add explicit versioning subsection * /pulls URI syntax error was also in the CPS template * Ledger process link didn't reflect CIP-0084 merge * template: canonical URL for pull requests Co-authored-by: Ryan Williams <44342099+Ryun1@users.noreply.github.com> * missing shorthand Markdown link * fix editing error in last commit * add license template lines to CIP template * optional sections, including more flexible yet more specific Versioning * forgot to include Versioning internal link * last change forgot placeholder for optional sections * grammar error: wrong preposition * Path to Active implementation complete with #389 --------- Co-authored-by: Ryan Williams <44342099+Ryun1@users.noreply.github.com>
) * status updates missed in Remediation effort #389 * post meeting status changes themselves
The CIP-0001's rework has been merged. In this rework, we've changed the preamble header structure and renamed some of the sections. Thus, for the sake of consistency, we'll need to update past CIPs to reflect this new structure. This issue is meant to help organizing the work around that. For each CIP, we need to:
Authors
to an actual bullet-point list (one name per line, starting with-
)type
)Discussions
field with a list (same as authors) of links to past discussions. At the very least, this should contain a link to the original PR (git log
comes in handy to figure this out).Category
,Implementors
...).README.md
if there is a status change for this CIP in the table.In terms of process; here below is a list of all (currently) merged CIPs; Each item can be converted into issue and assigned to one person. Thus, if you intend to help, make an issue out of one of the point, assign it to you and make a follow-up PR with the changes. Once all CIPs have been updated, we should be able to repair the website build.
The text was updated successfully, but these errors were encountered: