8000 Proposed Recommendations aren't useful in the same way other maturity stages are · Issue #861 · w3c/process · GitHub
[go: up one dir, main page]

Skip to content

Proposed Recommendations aren't useful in the same way other maturity stages are #861

@frivoal

Description

@frivoal

Unlike (FP)WD, CR(S or D), and RECs, Proposed Recommendations aren't long-lived stages on the Recommendation track.

They only exist for the purpose of supporting an AC Review about the transition from CR to REC. The Process explicitly disallows making substantive changes to Proposed RECs, and you need to cycle through more CRs (or WDs) if you want to change things.

It seems to me that we could do away with Proposed RECs, while keeping the associated AC Review. It would just apply to a CR instead of a PR. We'd still have an "AC Review to propose advancement to Recommendation", and it would still apply to a CR that has satisfied all the criteria for advancement, but we wouldn't need a distinct publication.

We have done similar things before:

  • Registries go directly from Candidate Registry to Registry and there's no "Proposed Registry"
  • Notes get elevated to Statement without going through a specially named publication to which the AC Review applies (and they still have a bunch of criteria to fulfill).
  • We used to have a special kind of Working Draft distinctly identified as Last Call Working Draft about which WGs needed to demonstrate wide review, before advancing to CR or going back to regular Working Drafts. We've keep the wide review requirement, but discontinued the transitional LCWD stage.

This would allow us:

Also, while I suppose we could deal with these two independently, I think it would make sense to also look into a similar merger of candidate ammendments with proposed amendments. This could be part of the simplification of .3.11.5. Incorporating Candidate Amendments requested in issues like #590, #589, or #700

Metadata

Metadata

Assignees

No one assigned

    Labels

    Closed: AcceptedThe issue has been addressed, though not necessarily based on the initial suggestionTopic: Simplifications

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0