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] Removal of the words "all known" in the current charter template #435

Closed
plehegar opened this issue Sep 7, 2023 · 3 comments · Fixed by #440
Closed

[template] Removal of the words "all known" in the current charter template #435

plehegar opened this issue Sep 7, 2023 · 3 comments · Fixed by #440

Comments

@plehegar
Copy link
Member

plehegar commented Sep 7, 2023

[[
I have a concern (objection) about the removal of the words "all known" in the current charter template, made in #415 .

The original phrasing, which I would prefer to continue use, was:

Each specification should contain sections detailing all known security and privacy implications for implementers, Web authors, and end users.

As I describe in the PATCG charter issue where this change was proposed, I believe that this is a step in the wrong direction, I don't believe the concern of disruption to WGs through "weaponisation" of that requirement to be well founded, and we shouldn't be loosening the requirements on WGs to document privacy considerations, even with strong horizontal review in place, as we have.
]]
From @chrisn #416 (comment)

@samuelweiler
Copy link
Member

For the historical context, see: #415

My summary: #415 was merged without consensus. I'm not sure whether it's better to revert #415 while we sort out a consensus or not.

@chrisn
Copy link
Member

chrisn commented Sep 15, 2023

I would prefer us to do that, as I'm seeing charters coming through for AC review with that change included, and I don't want to be objecting to everything.

@samuelweiler
Copy link
Member

Per strategy team discussion 19 September 2023, rolling back the change in 415.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants