Clarify Final Comment Period status in the core/README#1979
Conversation
There was a problem hiding this comment.
Pull request overview
Clarifies the CAP lifecycle wording in core/README.md by making the Final Comment Period (FCP) explicitly indicate its intended disposition (Acceptance vs Rejection), reducing ambiguity in CAP statuses across the spec docs.
Changes:
- Replaces the ambiguous “FCP: [Acceptance/Rejection]” terminology with “Final Comment Period: [Acceptance/Rejection]” and clarifies the transition outcomes.
- Updates the CAP-0085 entry in
core/README.mdto use the new explicit FCP disposition. - Synchronizes CAP-0085’s preamble
Statusfield with the README index entry.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| core/README.md | Clarifies workflow/status terminology and updates CAP-0085’s indexed status to include intended FCP disposition. |
| core/cap-0085.md | Updates the CAP preamble Status to match the README’s explicit “Final Comment Period: Acceptance” status. |
| - After a week of an Final Comment Period (FCP) where any major concerns that have not been | ||
| previously addressed can be brought up, the CAP will head to its final disposition. | ||
| ### Final Comment Period: [Acceptance/Rejection] -> Accepted or Rejected | ||
| - After a week in Final Comment Period, any major concerns that have not been previously |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
I would just replace it with "Final Comment Period" as this is how we've been using in the past and how it's referenced in the document anyways |
Removed the disposition from the FCP status. Those will now have to be inferred from the discussion thread. |
anupsdf
changed the title
what
Clarify Final Comment Period: Acceptance or Rejection in the core/README.
why
To remove ambiguity around the status of CAPs.