CLDR-18927 site: update /process.md #5251
Open
+28
−20
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
|
✨ This commit deployed to https://c518f5e1.cldr.pages.dev Changed Pages in the last commit: |
stenshamn
requested changes
Jan 4, 2026
Contributor
stenshamn
left a comment
stenshamn
left a comment
There was a problem hiding this comment.
Some suggested changes to clean up consistency in the bullet points and and a typo fix or two for your consideration.
Member
Author
|
Thanks @stenshamn good suggestions. I've got merge conflicts and probably some broken links still, but let's try to move this forward. |
Member
Author
- incorporate updates for non-TC org voting (cherry picked from commit a381832)
Co-authored-by: Fredrik Stenshamn <[email protected]> (cherry picked from commit f186cf6)
srl295
force-pushed
the
srl295/cldr-18927/document-vote-resolution-rules
branch
from
f186cf6 to
6c138d0
Compare
|
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
|
✨ This commit deployed to https://ad7d90c0.cldr.pages.dev Changed Pages in the last commit: |
AEApple
requested changes
Jan 14, 2026
| | *TC Organization Managers* | 6 | - Manage users in their organization <br>- Can vet and submit data for all locales (However, their vetting work is only done to correct issues.) <br>- Can see the email addresses for all vetters in their organization | | | ||
| | *Organization Managers* | 4 | -Manage users in their organization <br>- Can vet and submit data for all locales (However, their vetting work is only done to correct issues.) <br>- Can see the email addresses for all vetters in their organization | | | ||
| | *TC Organization Vetter* | 6 | - Can vet and submit data for a particular set of locales. <br>- Can see the email addresses for submitted data in their locales. <br>- Cannot manage other users. | | | ||
| | *Organization Manager* | 4 | -Manage users in their organization <br>- Can vet and submit data for all locales (only done to correct issues) <br>- Can see the email addresses for all vetters in their organization | | |
Contributor
There was a problem hiding this comment.
Suggested change
| | *Organization Manager* | 4 | -Manage users in their organization <br>- Can vet and submit data for all locales (only done to correct issues) <br>- Can see the email addresses for all vetters in their organization | | | |
| | *Organization Manager* | 4 | - Manage users in their organization <br>- Can vet and submit data for all locales (only done to correct issues) <br>- Can see the email addresses for all vetters in their organization | | |
| | *Guest Vetter* | 1 | - Can vet and submit data for a particular set of locales <br>- Cannot see email addresses. <br>- Cannot manage other users. | | | ||
| | *Locked Vetter* | 0 | - If a user is locked or removed, then their vote is considered a zero weight. | | | ||
| | *Guest Vetter* | 1 | - Can vet and submit data for a particular set of locales <br>- Cannot see email addresses <br>- Cannot manage other users | | | ||
| | *Locked/Removed Vetter* | 0 | - When a user is locked or removed during a vetting cycle, their vote is considered a zero weight and is no longer counted. | | |
Contributor
There was a problem hiding this comment.
I thought we don't remove vetter accounts, only lock them?
Member
There was a problem hiding this comment.
Right, we should delete /Removed and "or removed"
Contributor
|
Looks great, feel free to discard my feedback and fix in a follow-up PR if it is easier. |
stenshamn
requested changes
Jan 14, 2026
| | **Vetter Level** | **Number of Votes** | **Description** | | | ||
| |---|---|---|:---:| | ||
| | *TC Member* | 50 / 6 or 4 | - Manage users in their organization <br>- Can vet and submit data for all locales (However, their vetting work is only done to correct issues.) <br>- Can see the email addresses for all vetters in their organization <br>- Only uses a 50 vote for items agreed to by the CLDR technical Committee <br>- TC members may have a 6 or 4 regular vote depending on how actively their organization participates in the TC | | | ||
| | *TC Member* | 50 | - Manage users in their organization <br>- Can vet and submit data for all locales (only done to correct issues) <br>- Can see the email addresses for all vetters in their organization <br>- High level vote must be used by agreement with the CLDR Technical Committee, otherwise the voting level of their organization's vetters should be used. | | |
Contributor
There was a problem hiding this comment.
Suggested change
| | *TC Member* | 50 | - Manage users in their organization <br>- Can vet and submit data for all locales (only done to correct issues) <br>- Can see the email addresses for all vetters in their organization <br>- High level vote must be used by agreement with the CLDR Technical Committee, otherwise the voting level of their organization's vetters should be used. | | | |
| | *TC Member* | 50 | - Manage users in their organization <br>- Can vet and submit data for all locales (high level votes are only used to correct issues with CLDR Technical Committee's approval - otherwise the voting level of their organization is used) <br>- Can see the email addresses for all vetters in their organization | | |
Member
There was a problem hiding this comment.
(high level votes are only used to correct issues with CLDR Technical Committee's approval - otherwise the voting level of their organization is used)
the "is used" sounds a bit like that is automatic somehow. I think better would be:
otherwise they must use the voting level of their organization's vetters
Contributor
There was a problem hiding this comment.
Sounds so authoritative :-)
I'm not in love with my current wording, but I think it is softer and describes expected practice.
| | *Organization Managers* | 4 | -Manage users in their organization <br>- Can vet and submit data for all locales (However, their vetting work is only done to correct issues.) <br>- Can see the email addresses for all vetters in their organization | | | ||
| | *TC Organization Vetter* | 6 | - Can vet and submit data for a particular set of locales. <br>- Can see the email addresses for submitted data in their locales. <br>- Cannot manage other users. | | | ||
| | *Organization Manager* | 4 | -Manage users in their organization <br>- Can vet and submit data for all locales (only done to correct issues) <br>- Can see the email addresses for all vetters in their organization | | | ||
| | *TC Organization Vetter* | 6 | - Can vet and submit data for a particular set of locales <br>- Can see the email addresses for submitted data in their locales <br>- Cannot manage other users | | |
Contributor
There was a problem hiding this comment.
Suggested change
| | *TC Organization Vetter* | 6 | - Can vet and submit data for a particular set of locales <br>- Can see the email addresses for submitted data in their locales <br>- Cannot manage other users | | | |
| | *TC Organization Vetter* | 6 | - Can vet and submit data for a particular set of locales <br>- Can see the email addresses for vetters that submitted data in their locales <br>- Cannot manage other users | | |
| | *Organization Vetter* | 4 | - Can vet and submit data for a particular set of locales <br>- Can see the email addresses for submitted data in their locales. <br>- Cannot manage other users. | | | ||
| | *Guest Vetter* | 1 | - Can vet and submit data for a particular set of locales <br>- Cannot see email addresses. <br>- Cannot manage other users. | | | ||
| | *Locked Vetter* | 0 | - If a user is locked or removed, then their vote is considered a zero weight. | | | ||
| | *Guest Vetter* | 1 | - Can vet and submit data for a particular set of locales <br>- Cannot see email addresses <br>- Cannot manage other users | | |
Contributor
There was a problem hiding this comment.
Suggested change
| | *Guest Vetter* | 1 | - Can vet and submit data for a particular set of locales <br>- Cannot see email addresses <br>- Cannot manage other users | | | |
| | *Guest Vetter* | 1 | - Can vet and submit data for a particular set of locales <br>- Cannot see others' email addresses <br>- Cannot manage other users | | |
| - The liaison/associate member him/herself gets TC status in order to manage users, but gets a Guest status in terms of voting, unless the committee approves a higher level. | ||
| - Users who are not affiliated with any [CLDR organization] are normally assigned as Guest, but the committee can assign a different level. | ||
| - Unicode TC members (full/institutional/supporting) can create new user accounts at the TC, Manager, Vetter, or Guest level. | ||
| - Vetters of TC Organizations that are fully engaged in the CLDR Technical Committee are given the higher vote level of a *TC Organization Vetter* to reflect their level of expertise and coordination in the working of CLDR and the survey tool as compared to the normal *Organization Vetter* level. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Vetters of TC Organizations that are fully engaged in the CLDR Technical Committee are given the higher vote level of a *TC Organization Vetter* to reflect their level of expertise and coordination in the working of CLDR and the survey tool as compared to the normal *Organization Vetter* level. | |
| - Vetters of TC Organizations that are fully engaged in the CLDR Technical Committee are given the higher vote level of a *TC Organization Vetter* to reflect their level of expertise and coordination in the workings of CLDR and the survey tool as compared to the regular *Organization Vetter* level. |
| - Users who are not affiliated with any [CLDR organization] are normally assigned as Guest, but the committee can assign a different level. | ||
| - Unicode TC members (full/institutional/supporting) can create new user accounts at the TC, Manager, Vetter, or Guest level. | ||
| - Vetters of TC Organizations that are fully engaged in the CLDR Technical Committee are given the higher vote level of a *TC Organization Vetter* to reflect their level of expertise and coordination in the working of CLDR and the survey tool as compared to the normal *Organization Vetter* level. | ||
| - Other organizations, including liaison or associate members, can create user accounts at the Manager, Vetter, or Guest level only. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Other organizations, including liaison or associate members, can create user accounts at the Manager, Vetter, or Guest level only. | |
| - Other organizations, including liaison or associate members, can create user accounts at the Manager, Vetter, or Guest level. |
| - If the users within an organization vote for different values, a user with a higher voting level will overrule a vote at a lower voting level. | ||
| - For "TC Organizations" (see above), a later vote at the same level will override an earlier vote: "latest wins" | ||
| - For all other organizations, a value with more users voting for it will win over a value with fewer users voting for it. | ||
| - If there's still a tie, the tie will be broken arbitrarily by comparing the text lexically. |
Contributor
There was a problem hiding this comment.
Don't we also prioritize the legacy value in case of a tie, to avoid churn?
| ### Optimal Field Value | ||
|
|
||
| For each release, there is one optimal field value determined by the following: | ||
| For each release, there is one optimal (or, "winning") field value determined by the following process: |
Contributor
There was a problem hiding this comment.
Suggested change
| For each release, there is one optimal (or, "winning") field value determined by the following process: | |
| For each release, there is one optimal (or "winning") field value determined by the following process: |
| ## Data- Resolution | ||
|
|
||
| After the contribution of collecting and vetting data, the data needs to be refined free of errors for the release: | ||
| After the contribution of collecting and vetting data, the data needs to be curated to be free of errors for the release: |
Contributor
There was a problem hiding this comment.
Suggested change
| After the contribution of collecting and vetting data, the data needs to be curated to be free of errors for the release: | |
| After the contribution of collecting and vetting data, the data needs goes through a curation stage to ensure it is free of errors for the release: |
|
|
||
| It is difficult to develop a formulation that provides for stability, yet allows people to make needed changes. The CLDR committee welcomes suggestions for tuning this mechanism. Such suggestions can be made by [filing a ticket]. | ||
|
|
||
| ## Data- Resolution |
Contributor
There was a problem hiding this comment.
Suggested change
| ## Data- Resolution | |
| ## Data Resolution |
| - If data has a formal problem, it can be fixed directly (in GitHub) without going through the above process. Examples include: | ||
| - syntactic problems in pattern, extra trailing spaces, inconsistent decimals, mechanical sweeps to change attributes, translatable characters not quoted in patterns, changing ' (punctuation mark) to curly apostrophe or s-cedilla to s-comma-below, removing disallowed exemplar characters (non-letter, number, mark, uppercase when there is a lowercase). | ||
| - These are changed in-place, without changing the draft status. | ||
| - Linguistically-sensitive data should always go through the survey tool. Examples include: |
Contributor
There was a problem hiding this comment.
Suggested change
| - Linguistically-sensitive data should always go through the survey tool. Examples include: | |
| - Linguistically sensitive data should always go through the survey tool. Examples include: |
stenshamn
requested changes
Jan 15, 2026
| | *Guest Vetter* | 1 | - Can vet and submit data for a particular set of locales <br>- Cannot see email addresses. <br>- Cannot manage other users. | | | ||
| | *Locked Vetter* | 0 | - If a user is locked or removed, then their vote is considered a zero weight. | | | ||
| | *Guest Vetter* | 1 | - Can vet and submit data for a particular set of locales <br>- Cannot see email addresses <br>- Cannot manage other users | | | ||
| | *Locked/Removed Vetter* | 0 | - When a user is locked or removed during a vetting cycle, their vote is considered a zero weight and is no longer counted. | | |
Contributor
There was a problem hiding this comment.
Suggested change
| | *Locked/Removed Vetter* | 0 | - When a user is locked or removed during a vetting cycle, their vote is considered a zero weight and is no longer counted. | | | |
| | *Locked Vetter* | 0 | - When a user is locked during a vetting cycle, their vote is considered a zero weight and is no longer counted. | | |
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.
CLDR-18927
ALLOW_MANY_COMMITS=true