Harmonize the affiliation constraints for the AB and TAG#1167
Open
frivoal wants to merge 1 commit into
Open
Conversation
As there is no clear ongoing reason to justify the difference of treatment between the AB and TAG when affiliation changes cause two or more participants to share the same affiliation, harmonize the rules for the two groups, by aligning on the more lenient one in terms of duration (the TAG's) while keeping details from the more specific one (the AB's) in terms of backstop. Addresses w3c#817
frivoal
added
Needs Review
Agenda+
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As discussed in #817, since there is no clear ongoing reason to justify the difference of treatment between the AB and TAG when affiliation changes cause two or more participants to share the same affiliation, this PR proposes to harmonize the rules for the two groups, by aligning on the more lenient one in terms of duration (the TAG's) while keeping details from the more specific one (the AB's) in terms of backstop.
Note: I have also switched the responsibility for running (if necessary) the verifiable random selection procedure from the Chair to the Team, as this is a purely administrative yet fiddly step, whose timing would now be tied to the election, which is already run by the Team. So that seemed simpler. We can of course switch back if there's a preference to that effect.
Preview | Diff