Skip to content

Charters should be explicit about a group intents to publish Recommendations or simply publishing CR Snapshots #275

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

Closed
plehegar opened this issue Aug 28, 2020 · 12 comments
Assignees

Comments

@plehegar
Copy link
Member

Though Process 2020 allows a Working Group to publish as they wish as long as the document is on the REC-track (modulo update/transition requests), a Group may choose not to publish a Recommendation (see also w3c/process#443). It would be good to indicate the Group intend in the charter if known.

@swickr
Copy link
Contributor

swickr commented Aug 28, 2020

You're referring to a Group that intends that the end state is a series of CR Snapshots. As in #274, I agree this should also be explicit in the charter.

@svgeesus svgeesus self-assigned this Nov 8, 2020
@svgeesus
Copy link
Contributor

So https://www.w3.org/2020/Process-20200915/#transition-pr is about stronger emphasis on getting to Rec, to ensure HR happens and issues are addressed; it also touches on what it means for a spec to be "maintained".

Putting optional boilerplate in a charter that says "we expect to hang around in CR forever" seems to encourage an anti-pattern therefore; unless the wording focuses more on "how will you demonstrate the CR is maintained and not abandoned".

@svgeesus
Copy link
Contributor

svgeesus commented Dec 8, 2020

Discussed on 8 Dec 2020 strat call; unless the AC is requesting this, it seems premature to add this to the charter. The inclination was to close this with no change.

@svgeesus svgeesus removed the Agenda+ label Dec 8, 2020
@plehegar
Copy link
Member Author

plehegar commented Dec 9, 2020

So, we don't make the participants intent in the charter if they have one? I understand the worry about encouraging folks not to get to REC but saying nothing in the charter if the intent is known doesn't help imho.

@samuelweiler
Copy link
Member

samuelweiler commented Feb 19, 2021

I think #343 resolves most of this, but perhaps we should also take out the "expected completion" line in the deliverables list?

@wseltzer
Copy link
Member

WebAppSec used: the Working Group intends to publish the latest state of their work as Candidate Recommendation (with Snapshots). The group will advance documents to Recommendation when they are sufficiently mature, with no explicit milestones.
w3c/webappsec#581

@svgeesus
Copy link
Contributor

Add the WebAppSec wording (if approved following AC review) to the template as one option.

@plehegar
Copy link
Member Author

cc @dontcallmedom

@dontcallmedom
Copy link
Member

I am unconvinced the text about CR Snapshots and Rec when mature adds anything - this is exactly what any WG is expected to do.

@nigelmegitt
Copy link
Contributor

I am unconvinced the text about CR Snapshots and Rec when mature adds anything - this is exactly what any WG is expected to do.

If the suggestion is that some WGs expect not to advance to Rec when sufficiently mature, then I would agree that a) that should be discouraged and b) it should be explicitly stated. But I'd much prefer that WGs are expected to advance to Rec when adequately mature.

@plehegar
Copy link
Member Author

At this point, we've been sending charters to the AC with the intent of the Working Group. Is there anything else that needs to be fixed?

@plehegar
Copy link
Member Author

plehegar commented Sep 7, 2023

closing this for now. feel free to re-open if you believe this is still an issue.

@plehegar plehegar closed this as completed Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants