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

Clarify changes allowed during CR->REC transition #919

Closed
fantasai opened this issue Sep 19, 2024 · 3 comments
Closed

Clarify changes allowed during CR->REC transition #919

fantasai opened this issue Sep 19, 2024 · 3 comments
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion

Comments

@fantasai
Copy link
Collaborator

Filing this to make sure we review the text about dropping PR to ensure that the document published as REC corresponds precisely to the document reviewed during the patent exclusion period and AC formal review.

@nigelmegitt
Copy link
Contributor

There must be some expected and permitted minor differences, so it would be good to be clear about what they are. I'm thinking of things that you may or may not consider to be part of the document:

  • The SOTD must change to reflect the status change from CR to REC
  • The document title must change
  • ... not sure what else?

Is there scope for requiring specific markup on the AC Review CR, so that the final SOTD text will be visible to reviewers but in a "proposed for Rec" or "for review" styled block, I wonder? I'm not sure if that's a Process question or not.

@fantasai
Copy link
Collaborator Author

fantasai commented Oct 8, 2024

Currently we only restrict to "must not contain substantive changes" from the PR, so probably we can just preserve that qualification. https://www.w3.org/policies/process/#transition-rec

frivoal added a commit to frivoal/w3process that referenced this issue Oct 8, 2024
Ensure the Recommendation published after AC Review corresponds
to the text submitted to AC Review and the Patent Exlusion Opportunity.

See w3c#919
@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Oct 8, 2024
@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed Close review loopholes from dropping Proposed REC, and agreed to the following:

  • RESOLVED: Accept this PR with Florian's final wording tweak
The full IRC log of that discussion <fantasai> Subtopic: Close review loopholes from dropping Proposed REC
<fantasai> github: https://github.com//issues/919
<fantasai> https://github.com//pull/927
<fantasai> PROPOSED: Accept this PR with Florian's final wording tweak
<fantasai> RESOLVED: Accept this PR with Florian's final wording tweak

@css-meeting-bot css-meeting-bot removed the Agenda+ Marks issues that are ready for discussion on the call label Oct 9, 2024
frivoal added a commit to frivoal/w3process that referenced this issue Oct 9, 2024
Ensure the Recommendation published after AC Review corresponds
to the text submitted to AC Review and the Patent Exlusion Opportunity.

See w3c#919
@frivoal frivoal added the Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion label Oct 9, 2024
@frivoal frivoal added this to the Process 2024/2025 milestone Oct 9, 2024
@frivoal frivoal closed this as completed Oct 9, 2024
frivoal added a commit that referenced this issue Oct 9, 2024
Ensure the Recommendation published after AC Review corresponds
to the text submitted to AC Review and the Patent Exlusion Opportunity.

See #919
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion
Projects
None yet
Development

No branches or pull requests

4 participants