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

Fix up inconsistencies in the confidentiality of FOs and Council Reports #720

Merged
merged 1 commit into from
Mar 22, 2023

Conversation

frivoal
Copy link
Collaborator

@frivoal frivoal commented Mar 21, 2023

See #717


πŸ’₯ Error: 400 Bad Request πŸ’₯

PR Preview failed to build. (Last tried on Mar 22, 2023, 3:15 PM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 CSS Spec Preprocessor - CSS Spec Preprocessor is the web service used to build Bikeshed specs.

πŸ”— Related URL

Error running preprocessor, returned code: 2.
FATAL ERROR: LINE 26: The document's metadata block should be the first thing in the document. Please move this block to the top.
 ✘  Did not generate, due to fatal errors

If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.

@frivoal frivoal added Needs Review Director-free: FO/Council Issues realted to the W3C Council and Formal Objection Handling labels Mar 21, 2023
@frivoal frivoal added this to the Process 2023 milestone Mar 21, 2023
@frivoal frivoal self-assigned this Mar 21, 2023
@frivoal frivoal changed the title Fix up inconsistencies in the Confidentiality of FOs and Council Reports Fix up inconsistencies in the confidentiality of FOs and Council Reports Mar 21, 2023
@@ -2548,8 +2550,15 @@ Council Decision Report</h5>
indexing all completed [=Council Reports=].
If a Council decision is later overturned by an [=AC Appeal=],
this <em class=rfc2119>must</em> also be mentioned.
[=Council Reports=] <em class=rfc2119>must</em> have the same level of confidentiality
as the [=Formal Objection=].
[=Council Reports=] <em class=rfc2119>must</em> be no more confidential
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't there a problem here that the report might cite material that is confidential, and then the report cannot be less confidential than the material it cites/includes?

Copy link
Contributor

Choose a reason for hiding this comment

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

This concept of more confidential or less confidential being on a linear scale only works if some assumptions are true. I think of it as a venn diagram where each circle is a group of people who have access. If one circle is inside another, more vs less works, but if they only partially intersect, or don't intersect at all, it doesn't work.

For example, if the Team can see Team confidential stuff, and some of the Council can see AB-confidential stuff, and some TAG-confidential stuff, then the circles are unlikely to nest nicely. It also depends on which of those groups have visibility of the FO.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@dwsinger: yes, but depending on what needs saying, a report might not need to cite such confidential material, and in such cases, could be more public.

@nigelmegitt I was working off the team-only / member-visible / public confidenciality scale, which is indeed nesting. But there might be edge (or not so edge) cases where that isn't quite as neat, and I don't think it's that essential, so maybe "same level" is simpler.

Copy link
Contributor

Choose a reason for hiding this comment

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

There's also the ambiguity that "more confidential" could mean "less visible to the same people" (e.g. redacted) or "visible to fewer people"

@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion and removed Needs Review labels Mar 22, 2023
@frivoal frivoal force-pushed the council-report-confidentiality branch from 750c7dc to f974dd4 Compare March 22, 2023 15:15
@frivoal frivoal merged commit 40b6742 into w3c:main Mar 22, 2023
@frivoal frivoal deleted the council-report-confidentiality branch March 22, 2023 15:19
@frivoal frivoal added the Director-free (all) All issues & pull request related to director-free. See also the topic-branch label Mar 22, 2023
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 Director-free (all) All issues & pull request related to director-free. See also the topic-branch Director-free: FO/Council Issues realted to the W3C Council and Formal Objection Handling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants