8000 Requirement to publish formal objections should include a timeline · Issue #735 · w3c/process · GitHub
[go: up one dir, main page]

Skip to content

Requirement to publish formal objections should include a timeline #735

@jyasskin

Description

@jyasskin

https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-04#registering-objections says

A record of each Formal Objection against a decision regarding a publicly-available document must be made publicly available

It would be good to describe when the record must be made public. This ambiguity caused a problem with the formal objections to the DID recommendation, when @tantek posted Mozilla's objection publicly, while we left Google's responses only member-visible. The Team decided to make the record public much later than I'd expected, which meant that @tantek and Mozilla took more of the blame than they should have.

This doesn't need to be fixed for Process 2023.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Closed: AcceptedThe issue has been addressed, though not necessarily based on the initial suggestionFO/CouncilIssues related to the W3C Council and Formal Objection Handling

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0