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 position wrt to other processes #58

Closed
wants to merge 1 commit into from
Closed

Conversation

pchampin
Copy link
Collaborator

Copy link
Member

@csarven csarven left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Of course it goes without saying when a deliverable (a CG's work item) is taken as a WG's ED or FPWD, and following REC, NOTE, REGISTRY.. requirements.

I would suggest to not introduce this text in the PR unless charter-drafts makes a similar recommendation that proposed charters should clarify the process that was used to produce the deliverables from an incubation phase ( https://www.w3.org/Guide/standards-track/ ) and that WG will use the W3C Process going forward. That's clearly not the case with the other charter proposals, so not sure why it needs to be called out for the Solid WG charter.

We are already in the process of updating the CG's EDs (and TRs) to not mention Solid Process (and thereby BDFL..), and probably cut CG-DRAFT/FINAL (as latest TR) any way.

I would not object to introducing this text if you (W3C Team) still wants to go ahead with it, but would you (W3C Team) at least consider removing this text once we (CG) update the TRs/EDs of the referenced deliverables to not mention Solid Process?

@melvincarvalho
Copy link
Member

It’s prudent to maintain separation here; the dynamic nature and certain ambiguities within the CG charter, contrasted with the stability of the W3C process, warrant it.

Copy link
Member

@acoburn acoburn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good clarification given the current state of CG input documents. I probably wouldn't include the phrase "It goes without saying", since the text is literally saying just that.

@pchampin
Copy link
Collaborator Author

@csarven I would in general agree with your suggestion to not include this text, but some reviewers expressed concerns about that, hence this PR. I would keep the text even after the draft is updated and does not mention the Solid process.

@acoburn I included the text "It goes without saying" precisely to make it clear that we are not trying to introduce anything new or exceptional compared to other WGs. I would welcome suggestions for another wording, but I think we must emphasize the fact that this is "business as usual".

@csarven
Copy link
Member

csarven commented Oct 20, 2023

@pchampin
Copy link
Collaborator Author

I got multiple feedback, including from W3C staff, discouraging us to include this text in the charter, following the same rationale as @csarven above. Even more than the fact that "it goes without saying", the concern was that including it in one charter may give the impression that other charters may opt out of the W3C process.

I'm therefore closing this PR without merging it. The corresponding text will be instead included in the response sent to the AC reviewers with the new version of the charter, when finalized.

@pchampin pchampin closed this Oct 26, 2023
@pchampin pchampin added the ac-review PR addressing the issues/objections raised during AC review label Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ac-review PR addressing the issues/objections raised during AC review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants