More explicitly allow removal of AB/TAG members for violation of the Code of Conduct #1048
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
…Code of Conduct This wording has two goals: 1. Make it clear that members can be removed for Code of Conduct violations. 2. Make it clear that minor transgressions are not enough to cause removal. Relates to w3c#882
nigelmegitt
reviewed
May 14, 2025
index.bs
Outdated
Comment on lines
1334
to
1337
| or if they are violating policies or other standards of behavior | ||
| (such as applicable laws or the <a href="https://www.w3.org/policies/code-of-conduct/#Reporting">Code of Conduct</a>) | ||
| in a way that significantly impacts the safety or integrity | ||
| of W3C or its community. |
Contributor
There was a problem hiding this comment.
This is interesting. It sidesteps the issue of how a potential CoC violation should be handled, which reflects the concerns described previously. However, to do that, it adds a new condition "a way that significantly impacts the safety or integrity of W3C or its community", which is likely to be a subjective metric, and is seemingly to be assessed by the individual's peers in their group.
I'm not sure how I feel about that, and welcome the views of others. I'm certainly not instantly comfortable with it.
frivoal
commented
Sep 25, 2025
Collaborator
Author
|
Merging into the ab-tag-discipline branch, as decided on the 2025-09-24 Process CG call. That branch itself is not being merged into main, and does not represent consensus, merely work in progress. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
This wording has two goals:
Relates to #882
This is split from #1036, to facilitate discussion of the various independent aspects of that PR. See https://github.com/w3c/process/pull/1036/files#r2064384283 for prior discussion on this particular aspect.
This PRs is against the ab-tag-discipline topic branch (source, preview), not the main branch, meaning we can iterate and accept individual pieces, and still have a chance at the end to judge the combined result before we decide whether to merge it.
Preview | Diff