Skip to content

Require documentation of how FOs get resolved #953

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

Merged
merged 1 commit into from
Dec 23, 2024
Merged

Conversation

frivoal
Copy link
Collaborator

@frivoal frivoal commented Dec 6, 2024

See #870


Preview | Diff

@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Dec 6, 2024
@frivoal frivoal added this to the Process 2024/2025 milestone Dec 6, 2024
Copy link
Member

@plehegar plehegar left a comment

Choose a reason for hiding this comment

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

Sine all Formal Objections must be made public, isn't that saying the resolution must be public?

@frivoal
Copy link
Collaborator Author

frivoal commented Dec 10, 2024

Since all Formal Objections must be made public, isn't that saying the resolution must be public?

Yes, it's saying that. But to me, it's also saying that you should make the announcement not just with the same confidentiality, but also with the same visibility. E.g.: If the FO is announced on a well-read mailing list, the resolution needs to be announced there too. Putting it on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard.” [1] doesn't count, even if the cabinet is not designated as confidential.

[1] in case this example looks a bit over the top to anyone, it's a quote from a novel: https://www.goodreads.com/quotes/40705-but-the-plans-were-on-display-on-display-i-eventually

@plehegar
Copy link
Member

Unless there is new information by December 20, this pull request will get merged.

@vivienlacourba vivienlacourba changed the title Require documentation of hwo FOs get resolved Require documentation of how FOs get resolved Dec 13, 2024
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion and removed Agenda+ Marks issues that are ready for discussion on the call labels Dec 23, 2024
@frivoal frivoal merged commit 624237d into w3c:main Dec 23, 2024
2 checks passed
@frivoal frivoal deleted the fo-record branch December 23, 2024 02:18
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants