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

Requirements for advancement to Recommendation #496

Closed
plehegar opened this issue Jan 25, 2021 · 2 comments · Fixed by w3c/transitions#309
Closed

Requirements for advancement to Recommendation #496

plehegar opened this issue Jan 25, 2021 · 2 comments · Fixed by w3c/transitions#309
Labels
Closed: Retracted Closed by the person who opened the issue, no longer requesting anything be done. Type: Editorial improvements
Milestone

Comments

@plehegar
Copy link
Member

For transitioning to Recommendation, the Process points to the requirements for advancement. The first item in the list of requirements is "must record the group’s decision to request advancement." Since no substantive are made to move to Proposed Recommendation, is it required to record a new Group decision to move to Recommendation or is the group decision to move to Proposed Recommendation enough?

@nigelmegitt
Copy link
Contributor

Good shout @plehegar this has always been an odd thing when we've been wanting to transition to Rec.

One possible solution is to define a "document owner" for the document which is the WG at WD and CR stages, but then transfers to the Director at PR. Then it's the document owner who must record the decision to advance.

This may pave the way for a nice change for specs that are developed in a CG and then transferred to a WG, in that the document owner would change, and it would be clear who owns it.

@frivoal
Copy link
Collaborator

frivoal commented Jan 26, 2021

Since the only purpose of going to PR is to go to REC, I think a group decision to request PR is also a group decision to (attempt to) go to REC. Maybe we can clarify in the Process if there's any doubt, but I don't think this should cause any problem in practice.

@frivoal frivoal added the Closed: Retracted Closed by the person who opened the issue, no longer requesting anything be done. label Mar 2, 2023
@frivoal frivoal added this to the Process 2023 milestone Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Retracted Closed by the person who opened the issue, no longer requesting anything be done. Type: Editorial improvements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants