Skip to content

Notify the AC when an AB or TAG member is removed. #1023

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.

Sign up for GitHub

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

Jump to bottom
Merged
fantasai merged 1 commit into from
Apr 22, 2025
Merged

Notify the AC when an AB or TAG member is removed. #1023

fantasai merged 1 commit into from
Apr 22, 2025

Conversation

@fantasai
Copy link
Contributor

@fantasai fantasai commented Apr 11, 2025 •
edited by pr-preview bot
Loading

Addresses #888 (comment) Related to #882.

Preview | Diff

@fantasai fantasai added the Agenda+ Recommends to the Chairs that this issue or pull request be discussed at the next meeting label Apr 15, 2025
tantek
tantek approved these changes Apr 15, 2025
View reviewed changes
Copy link
Contributor

@tantek tantek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM. Why the "5 days" in particular? Is that similar to other notification requirements elsewhere? 5 calendar days? 5 business days? Excluding holidays in what countries? Could be tighter, or perhaps simplify to "one week"? "Two weeks" also seems reasonable. Up to editor discretion.

@fantasai
Copy link
Contributor Author

fantasai commented Apr 15, 2025 •
edited
Loading

@tantek To be honest, I just picked a random period that was short but long enough to allow for crafting an appropriate message. Figured I'll get some input on the time period from the CG. :) I'd be fine with one week.

@fantasai fantasai force-pushed the removal-notification branch from ea972db to 71cfc71 Compare April 15, 2025 22:47
@frivoal frivoal mentioned this pull request Apr 22, 2025
Merged
@fantasai fantasai merged commit 12eef64 into w3c:main Apr 22, 2025
2 checks passed
@fantasai fantasai deleted the removal-notification branch April 22, 2025 04:02
@frivoal frivoal added this to the Process 2024/2025 milestone Apr 22, 2025
@frivoal frivoal added Topic: AB/TAG discipline and removed Agenda+ Recommends to the Chairs that this issue or pull request be discussed at the next meeting labels May 2, 2025
@frivoal frivoal modified the milestones: AB/TAG discipline, Deferred Jun 18, 2025
@frivoal frivoal modified the milestones: Deferred, Process 2024/2025 Sep 25, 2025
@frivoal
Copy link
Collaborator

frivoal commented Oct 6, 2025

As discussed in #882 (comment), a dedicated topic branch was created for this issue and related ones: ab-tag-discipline
Although this PR had previously been merged into the main branch, this has been reverted (prior to publication of Process 2025). See ab-tag-discipline, and related issues or PRs for more on that topic.

@frivoal frivoal added the Closed: Reverted PR Used for pull requests that were merged, but got reverted (during the same Process cycle) label Oct 6, 2025
@frivoal frivoal modified the milestones: Deferred, Process 2024/2025 Oct 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@frivoal frivoal frivoal approved these changes

@plehegar plehegar plehegar approved these changes

+3 more reviewers

@tantek tantek tantek approved these changes

@cwilso cwilso cwilso approved these changes

@TallTed TallTed TallTed approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

Closed: Reverted PR Used for pull requests that were merged, but got reverted (during the same Process cycle) Topic: AB/TAG discipline

Projects

None yet

Milestone

Process 2024/2025

Development

Successfully merging this pull request may close these issues.

6 participants

@fantasai @frivoal @tantek @cwilso @plehegar @TallTed