Better define major/minor charter changes #1042
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
frivoal
added
the
Agenda+
See PSIG discussion at https://lists.w3.org/Archives/Member/member-psig/2025AprJun/0005.html and later. As approved by PSIG in the May 12 call Co-authored-by: fantasai <fantasai.bugs@inkedblade.net> Co-authored-by: Anna Weinberg <anna_m_weinberg@apple.com> Co-authored-by: Jill Schmidt <jill_schmidt@apple.com> Co-authored-by: Michael Sirtori <michael.j.sirtori@intel.com>
nigelmegitt
suggested changes
May 13, 2025
plehegar
requested changes
May 14, 2025
|
The Revising W3C Process CG just discussed
The full IRC log of that discussion<fantasai> Subtopic: Better define major/minor charter changes (from PSIG)<fantasai> github: https://github.com//pull/1042 <fantasai> florian: This came to PSIG's attention because we reshuffled the text in this area. The existing text is not new, but it moved and was tweaked a bit so that got their attention <plh> plh: we don't make minor changes to scope. At best, a minor change in the deliverable section is to fix a broken link. <fantasai> florian: the focus from their point of view is making sure that at least changes in scope, changes that increase scope especially, including some type of adding deliverables would go through review due to patent implications <fantasai> plh: In practice, the only changes we make that way are to change Team Contacts, Chairs, or end date of charter <fantasai> ... in the PR, when we change the chair, some people would consider that substantive <fantasai> ... and would not be incorrect; however the Process doesn't say we need to have an AC review because substantive. <fantasai> ... Chairs are selected by the Team. <fantasai> ... We put that info in the charter, but if a chair needs to change for whatever reason, we don't want that to go through AC Review <fantasai> ... and not necessarily consensus of the WG (though should consult with the group) <fantasai> cwilso: Not sure that's true in practice. How do you determine what the group wants if you don't ask? <fantasai> plh: Change seems to say that it require consensus of the group. <fantasai> florian: First, changing chairs was previously and is still a minor change. <fantasai> ... PSIG clarifies other changes. <fantasai> ... Consensus is a should requirement, not must. <fantasai> ... Also I don't think PSIG would mind if you put chair along with Team Contact as not needing group consensus. <fantasai> plh: Changing chairs would be seen as substantive <TallTed> Depends on the outgoing and incoming chairs... <fantasai> fantasai: substantive != minor, a change could be both substantive and minor. <fantasai> ... In any case, the Team always has the option to go through AC Review. The minor changes process is only an option. <fantasai> plh: We never did an AC Review for changing the chair <fantasai> florian: Old Process, Team is allowed but not required to AC Review for change of chair. <fantasai> ... Proposed prose recommends, but does not require, consensus of group for changes. <fantasai> cwilso: If necessary people can formally object to the Team decision. <fantasai> ... It's a little weird to change during the review period <fantasai> florian: Wrt change or expansion of scope... [quotes text] <fantasai> ... We don't say explicitly that reducing scope is a minor change, but we do say that increasing scope is not. <fantasai> ... From PSIG's point of view, from patent point of view, no risk to portfolio to reduce scope. <fantasai> ... They don't take a position on whether decreasing needs review. <fantasai> plh: If it was me, any change to scope is major change. We have never done that. <fantasai> florian: So aligned with Chris that any change should be not minor. <fantasai> plh: Right. We shouldn't change scope of charter at all. <fantasai> florian: I can live with that <fantasai> fantasai: I suspect PSIG would be fine <fantasai> florian: what's the process? <fantasai> fantasai: We gave AB a heads up on this topic. We should make any changes we think need to happen. And then go back to PSIG/AB with the result. <fantasai> florian: OK, so let's switch to any change in scope <fantasai> RESOLVED: Adopt #1042 with switch to "any change in scope" |
css-meeting-bot
removed
the
Agenda+
frivoal
added
the
Closed: Accepted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refine the definition/usage of the concept of minor changes to a charter.
See PSIG discussion at https://lists.w3.org/Archives/Member/member-psig/2025AprJun/0005.html
Preview | Diff