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

Abandoning Charter Refinement should require Team to agree #982

Open
fantasai opened this issue Jan 22, 2025 · 2 comments
Open

Abandoning Charter Refinement should require Team to agree #982

fantasai opened this issue Jan 22, 2025 · 2 comments
Labels
Agenda+ Marks issues that are ready for discussion on the call Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion

Comments

@fantasai
Copy link
Collaborator

The current draft requires only a Chair Decision from a facilitator to abandon efforts on a new charter. During internal review at Apple, it was asked if this decision shouldn't also consider the Team's position.

Suggestion: Require both a chair (chartering facilitator) decision and a Team decision in order to abandon the chartering effort.

@fantasai fantasai added this to the Process 2024/2025 milestone Jan 22, 2025
@fantasai fantasai changed the title Abandoning Charter Refinement should require Team Decision Abandoning Charter Refinement should require Team to agree Jan 22, 2025
@frivoal
Copy link
Collaborator

frivoal commented Jan 22, 2025

Basically I agree. In terms of how to describe it, I'm not 100% sure about whether to require a double decision as you suggest, or to make it a proposal by the facilitator + a decision by the Team. But then again, maybe this is a distinction without a difference.

@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed Requiring Team to assent to abandoning charter review, and agreed to the following:

  • RESOLVED: Draft a PR for this issue
The full IRC log of that discussion <fantasai> Subtopic: Requiring Team to assent to abandoning charter review
<fantasai> florian: Issue from Apple. Currently the facilitator can decide to give up unilaterally.
<fantasai> ... Perhaps they give up too early
<fantasai> ... so the proposal is that both the chartering facilitator and the Team need to agree to give up
<fantasai> ... if the Team thinks effort should continue, then effort shoudl continue
<plh> q+
<fantasai> ... potentially with a different facilitator
<fantasai> plh: Can't Team decide anyway?
<plh> "A group decision or Team Decision to initiate AC Review of the charter draft, subject to Team verification that the expectations of charter refinement are fulfilled.'
<fantasai> florian: If we have a charter draft, and the group doesn't want to take it to the AC, then Team can decide unilaterally
<fantasai> ... but the facilitator can decide to *give up* unilaterally
<fantasai> s/can/can still/
<fantasai> plh: Ah
<fantasai> florian: I agree with the feedback, unsure about wording
<fantasai> plh: The Team can pick a different facilitator if the facilitator gives up
<fantasai> florian: If they decide to give up trying personally, sure. But if they decide the effort overall should stop...
<fantasai> plh: OK
<fantasai> ... though we could restart the effort in any case
<fantasai> florian: Yes, but more messy
<fantasai> florian: One way to say this is that both the facilitator and the Team need to decide to give up
<fantasai> ... other option is that facilitator proposes and Team confirms
<fantasai> plh: I don't feel strongly
<fantasai> TallTed: Inclined towards Florian's structure: decision by facilitator and concurrance by the Team
<fantasai> ... appealing the decision, I don't think the intent is to force the facilitator who is resigning to continue with it
<fantasai> ... so that is not a decision that is subject to objection
<fantasai> florian: Not a question about they can resign. Question is if they decide to disband the group.
<fantasai> ... Is it two decisions, or a proposal and a decision?
<fantasai> [confusion]
<fantasai> florian: The facilitator isn't just saying taht they can't do it personally, but that the task is not worth continuing, let's stop trying.
<fantasai> plh: Can already object to a decision to abandon the proposal
<fantasai> ... what's important is that it's a decision and can appeal it
<fantasai> florian: Let's agree on the goal, and then I'll try to make a PR
<fantasai> RESOLVED: Draft a PR for this issue
<fantasai> github: https://github.com//issues/982

frivoal added a commit to frivoal/w3process that referenced this issue Jan 23, 2025
@frivoal frivoal added Agenda+ Marks issues that are ready for discussion on the call Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Agenda+ Marks issues that are ready for discussion on the call Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion
Projects
None yet
Development

No branches or pull requests

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy