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

[template] TRs produced by the WG will operate strictly under the W3C Process #461

Closed
csarven opened this issue Oct 13, 2023 · 3 comments
Closed
Assignees

Comments

@csarven
Copy link
Member

csarven commented Oct 13, 2023

Introduce text to indicate that TRs produced by the WG will operate strictly under the W3C Process.

Yes, it goes without saying that, but as such clarification is requested in #459 , it should hold true for any charter.

If such text is deemed necessary, the text can be used towards resolving issue 459. If unnecessary, the issue can be closed without changes.

@plehegar
Copy link
Member

plehegar commented Oct 19, 2023

[[
Introduce text to indicate that TRs produced by the WG will operate strictly under the W3C Process.
]]

All Working Groups operate under the W3C Process. So I'm not sure what you're looking for.

@csarven
Copy link
Member Author

csarven commented Oct 19, 2023

Right. Am aware.

The question back to you is whether there is a need to say that in a charter (template). See linked issue 459.

@plehegar plehegar changed the title TRs produced by the WG will operate strictly under the W3C Process [template] TRs produced by the WG will operate strictly under the W3C Process Oct 19, 2023
@svgeesus
Copy link
Contributor

Putting this in the charter template paves the way for some group to say"we follow the W3C process except we ..." which would get flagged at charter review before it went to the AC. So would be a bad thing to do.

If unnecessary, the issue can be closed without changes.

Closing

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

3 participants