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

Generalize FO-handling #276

Closed
frivoal opened this issue May 20, 2019 · 2 comments
Closed

Generalize FO-handling #276

frivoal opened this issue May 20, 2019 · 2 comments
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
Milestone

Comments

@frivoal
Copy link
Collaborator

frivoal commented May 20, 2019

The section about handing Formal Objections is invoked not just for Formal Objections, but also for Group Decision Appeals, Chair Decision Appeals, and Member Submission Appeals. Some editorial rephrasing is probably needed to make it clear how it applies in all cases.

We need at least some better terminology, and maybe some other tweaks.

See https://www.w3.org/Consortium/Process/Drafts/director-free/#addressing-fo

@dwsinger
Copy link
Contributor

  1. Make a section "W3C Council" after the AB and TAG are defined, and move this sentence in there.

Together with the [=CEO=} and the members of the TAG, members of the Advisory Board hear and adjudicate on Submission Appeals, Chair Decision Appeals, Group Decision Appeals, and Formal Objections. These are Council Questions.

  1. Keep 3.3.2 as specific to FOs, but terminate it by saying that FOs are Council Questions and resolved by Council decisions.

  2. add a new section Council Decisions, which takes the rest of what is 3.3.2, and makes it general. Start with "The Team considers the Formal objection, researches the question, " but change to "The Team considers the Question, researches it, …"

I think the other edits then follow. For recusal, it has to be the person who made the original decision, or the person who called it into question (e.g., they filed the formal objection).

@frivoal frivoal modified the milestones: Deferred, Director-free Mar 11, 2020
@plehegar plehegar changed the title [director-free] Generalize FO-handling Generalize FO-handling Jun 30, 2020
@frivoal frivoal added Director-free: FO/Council Issues realted to the W3C Council and Formal Objection Handling and removed director-free labels Jul 1, 2020
@frivoal frivoal modified the milestones: Director-free, Deferred Jul 1, 2020
@dwsinger dwsinger added the Director-free (all) All issues & pull request related to director-free. See also the topic-branch label Jul 26, 2021
@frivoal frivoal modified the milestones: Deferred, Process 2023 Nov 9, 2022
@frivoal frivoal added the Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion label Nov 9, 2022
@frivoal
Copy link
Collaborator Author

frivoal commented Nov 9, 2022

This was resolved as part of merging the director-free branch

@frivoal frivoal closed this as completed Nov 9, 2022
@frivoal frivoal added Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice and removed Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice labels Mar 2, 2023
fantasai added a commit that referenced this issue May 11, 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

No branches or pull requests

2 participants