Amend "need to re-join" guidance to align with practice #391
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
The need for current group participants to re-join a group once a new charter is approved is triggered by a change of scope. The guidebook also mentioned the list of deliverables, but we do not ask participants to re-join when new new in-scope deliverables are added.
plehegar
approved these changes
Jan 16, 2026
TallTed
reviewed
Jan 16, 2026
| 1. A w3.org URI to the proposed charter (not a github.io URI). This charter is public, and must not be altered, during the AC review. | ||
| 2. The list of significant changes to a revised charter (per ["Advisory Committee Review of a Working Group or Interest Group Charter"](https://www.w3.org/policies/process/#CharterReview) of the Process Document). It is useful to include a diff between the current and proposed charters (you may wish to use the [HTML diff tool](https://services.w3.org/htmldiff)). | ||
| 3. In case of renewal of an existing charter, whether the group scope has changed. I.e., are there any new deliverables with licensing obligations under the W3C Patent Policy? The current group participants would need to re-join the group once the revised charter is approved. | ||
| 3. In case of renewal of an existing charter, whether the current group participants would need to re-join the group once the revised charter is approved. Group participants would need to re-join if the scope changes. |
Member
There was a problem hiding this comment.
Suggested change
| 3. In case of renewal of an existing charter, whether the current group participants would need to re-join the group once the revised charter is approved. Group participants would need to re-join if the scope changes. | |
| 3. When renewing an existing charter, whether the current group participants would need to re-join the group once the revised charter is approved. Group participants would need to re-join if the scope changes. |
TallTed
reviewed
Jan 16, 2026
| - If applicable, the rationale for approving the group despite objections, or despite the fact it did not receive reviews [from at least 5% of the Membership](#review_threshold). | ||
| In case a charter has new deliverables in-scope, it is useful to include a notice that a 45-day grace period is granted to existing participants of the group under the previous charter, who will then need to re-join the group. | ||
| In case the scope of a charter changed, it is useful to include a notice that a 45-day grace period is granted to existing participants of the group under the previous charter, who will then need to re-join the group. |
Member
There was a problem hiding this comment.
Suggested change
| In case the scope of a charter changed, it is useful to include a notice that a 45-day grace period is granted to existing participants of the group under the previous charter, who will then need to re-join the group. | |
| When the scope of a charter changes, it is useful to include a notice that a 45-day grace period is granted to existing participants of the group under the previous charter, who will then need to re-join the group. |
TallTed
reviewed
Jan 16, 2026
| In case the scope of a charter changed, it is useful to include a notice that a 45-day grace period is granted to existing participants of the group under the previous charter, who will then need to re-join the group. | ||
| In case the new charter doesn't have new deliverables involving new patent commitment, it is useful to clarify that existing participants under the previous charter will not be required to leave/re-join the group. | ||
| In case the scope of a charter did not change, it is useful to clarify that existing participants under the previous charter will not be required to leave/re-join the group. |
Member
There was a problem hiding this comment.
Suggested change
| In case the scope of a charter did not change, it is useful to clarify that existing participants under the previous charter will not be required to leave/re-join the group. | |
| When the scope of a charter does not change, it is useful to clarify that existing participants under the previous charter will not be required to leave/re-join the group. |
TallTed
reviewed
Jan 16, 2026
| Staff Contacts should look at [how to setup a new group](../tools/new-group.md) once the call for participation is out. | ||
|
|
||
| **Note:** When we recharter a work group and the charter scope has changed, we enter the CFP into the Group DB, which triggers messages to the group participants that they must rejoin. If the new charter doesn't have new deliverables involving new patent commitment, do not register the new CFP. | ||
| **Note:** When we recharter a work group and the charter scope has changed, we enter the CFP into the Group DB, which triggers messages to the group participants that they must re-join. If the scope did not change in the new charter, do not register the new CFP. |
Member
There was a problem hiding this comment.
Suggested change
| **Note:** When we recharter a work group and the charter scope has changed, we enter the CFP into the Group DB, which triggers messages to the group participants that they must re-join. If the scope did not change in the new charter, do not register the new CFP. | |
| **Note:** When we recharter a work group and the charter scope has changed, we enter the CFP into the Group DB, which triggers messages to the group participants that they must re-join. If the scope did not change in the new charter, we do not register a new CFP. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The need for current group participants to re-join a group once a new charter is approved is triggered by a change of scope. The guidebook also mentioned the list of deliverables, but we do not ask participants to re-join when new new in-scope deliverables are added.