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

CRD may be followed by a Proposed Recommendation #450

Closed
plehegar opened this issue Sep 4, 2020 · 6 comments
Closed

CRD may be followed by a Proposed Recommendation #450

plehegar opened this issue Sep 4, 2020 · 6 comments
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Type: Editorial improvements
Milestone

Comments

@plehegar
Copy link
Member

plehegar commented Sep 4, 2020

[[
A Candidate Recommendation Draft is published on the W3C’s Technical Reports page [TR] to integrate changes from the previous Candidate Recommendation Snapshot that the Working Group intends to include in a subsequent Candidate Recommendation Snapshot.
]]
https://www.w3.org/2020/Process-20200915/#candidate-recommendation-draft

However, one can go directly from CRD to Proposed Recommendation if no substantive changes were made since the most recent snapshot. So, it's not necessirely included in a subsequent CRS.

How about:
[[
A Candidate Recommendation Draft is published on the W3C’s Technical Reports page [TR] to integrate changes from the previous Candidate Recommendation Snapshot that the Working Group intends to include in a subsequent update.
]]

cc @dontcallmedom

@frivoal
Copy link
Collaborator

frivoal commented Sep 7, 2020

I'm a little unsure. On the one hand, you're right, CRD->PR is possible in this case. On the other hand, it seems to me that the current text is clearer about the general intent, by naming what kind of update we're talking about, and it just so happens that we have an exception that allows you to skip CRS and go straight to PR if you've only made editorial changes. Should we go for clarity of intent, or for precision? Or should we find yet another wording that gives us both?

While we're on that, I'm not sure that "subsquent update" is quite the right word anyway. A new CR(S) would be an update, but is PR really an update?

@fantasai
Copy link
Collaborator

fantasai commented Sep 8, 2020

  • Let's remove “on the W3C’s Technical Reports page [TR]”, that will at least shorten the sentence.
  • Agree with @frivoal’s concerns about “update” being a bit too vague. We could write out ”Candidate Recommendation Snapshot or Proposed Recommendation” in full (especially after deleting that other bit ;) or just accept the slight inaccuracy.

@plehegar
Copy link
Member Author

plehegar commented Sep 8, 2020

well, PR is an update since it has a new date at the minimum. Spelling it out while we're trying to make the SOTD the SOTD shorter backward to me.

@fantasai
Copy link
Collaborator

fantasai commented Sep 9, 2020

@plehegar I mean, I'd be OK with dropping the entire “that the Working Group intends to include in a subsequent Candidate Recommendation Snapshot” phrase. But a CRD is also an “update” so the phrase is a bit nonsensical if we just replace “Candidate Recommendation Snapshot” with “update” here.

@plehegar plehegar changed the title CRD may be following by a Proposed Recommendation CRD may be followed by a Proposed Recommendation Sep 9, 2020
@fantasai
Copy link
Collaborator

fantasai commented Sep 9, 2020

Proposed wording: “A Candidate Recommendation Draft is published to solicit review of intended changes from the previous Candidate Recommendation Snapshot.”

plehegar added a commit to w3c/tr-design that referenced this issue Sep 10, 2020
tabatkins pushed a commit to tabatkins/tr-design that referenced this issue Sep 23, 2020
@frivoal frivoal added this to the Deferred milestone Jan 11, 2023
@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Apr 19, 2024
frivoal added a commit to frivoal/w3process that referenced this issue May 21, 2024
By focusing on what the changes in a CDR are from rather than what
they're aimed at, we can both make the sentence simpler and avoid making
undesired implications about the impossibility to transition from CRD to PR.

This addresses w3c#450
@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed #873.

The full IRC log of that discussion <plh> Topic: #873
<plh> Github: https://github.com//issues/450
<plh> Florian: it seems it's possible to move from CRD to PR if you don't make substantive changes. but the definition of CRD claims that it was only to prepare a CRS
<plh> .... the PR makes things clearer
<plh> Plh: +1
<plh> Resolved: Let's merge #873

frivoal added a commit that referenced this issue May 22, 2024
By focusing on what the changes in a CDR are from rather than what
they're aimed at, we can both make the sentence simpler and avoid making
undesired implications about the impossibility to transition from CRD to PR.

This addresses #450

Co-authored-by: Dominique Hazael-Massieux <dom@w3.org>
@frivoal frivoal modified the milestones: Deferred, Process 2024 May 22, 2024
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion and removed Agenda+ Marks issues that are ready for discussion on the call labels May 22, 2024
@frivoal frivoal closed this as completed May 22, 2024
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 Type: Editorial improvements
Projects
None yet
Development

No branches or pull requests

4 participants