CLDR-18927 site: update /process.md #5251
Open
+27
−18
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
- incorporate updates for non-TC org voting
|
✨ 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.
| | **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 (However, their vetting work is 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 (However, their vetting work is 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 (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 / 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 (However, their vetting work is 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 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 | | |
Contributor
There was a problem hiding this comment.
Suggested change
| | *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 | | | |
| | *TC Organization Manager* | 6 | - 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 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 (However, their vetting work is 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 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 | | |
Contributor
There was a problem hiding this comment.
Suggested change
| | *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 | | | |
| | *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 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. | | | ||
| | *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 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 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 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. | | |
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 email addresses <br>- Cannot manage other users | | |
| - Some specific items have an even higher threshold. See approvalRequirement elements in [coverageLevels.xml](https://unicode.org/repos/cldr/trunk/common/supplemental/coverageLevels.xml) for details. | ||
| 1. *Established* locales are currently found in [coverageLevels.xml], with `approvalRequirement[@votes="8"]` | ||
| - Some specific items have an even higher threshold. See approvalRequirement elements in [coverageLevels.xml] for details. | ||
| 2. If the oldStatus is better than the new draft status, then no change is made. Otherwise, the optimal value and its draft status are made part of the new release. |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. If the oldStatus is better than the new draft status, then no change is made. Otherwise, the optimal value and its draft status are made part of the new release. | |
| 2. If the `oldStatus` is better than the new draft status, then no change is made. Otherwise, the optimal value and its draft status are made part of the new release. |
| ## Data- Resolution | ||
|
|
||
| After the contribution of collecting and vetting data, the data needs to be refined free of errors for the release: | ||
| After theontribution 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 theontribution 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 to be curated to be free of errors for the release: |
| This process can be fine-tuned by the Technical Committee as needed, to resolve any problems that turn up. A committee decision can also override any of the above process for any specific values. | ||
|
|
||
| For more information see the key links in [CLDR Survey Tool](https://st.unicode.org) (especially the Vetting Phase). | ||
| For more information see the key links in the [Information Hub](/translation) (especially the Vetting Phase). |
Contributor
There was a problem hiding this comment.
Suggested change
| For more information see the key links in the [Information Hub](/translation) (especially the Vetting Phase). | |
| For more information, see the key links in the [Information Hub](/translation) (especially the Vetting Phase). |
| - Linguistically-sensitive data should always go through the survey tool. Examples include: | ||
| - names of months, territories, number formats, changing ASCII apostrophe to U+02BC modifier letter apostrophe or U+02BB modifier letter turned comma, or U+02BD modifier letter reversed comma, adding/removing normal exemplar characters. | ||
| - The TC committee can authorize bulk submissions of new data directly (CVS), with all new data marked draft="unconfirmed" (or other status decided by the committee), but only where the data passes the CheckCLDR console tests. | ||
| - The TC committee can authorize bulk submissions of new data directly, with all new data marked draft="unconfirmed" (or other status decided by the committee), but only where the data passes the CheckCLDR console tests. |
Contributor
There was a problem hiding this comment.
Suggested change
| - The TC committee can authorize bulk submissions of new data directly, with all new data marked draft="unconfirmed" (or other status decided by the committee), but only where the data passes the CheckCLDR console tests. | |
| - The TC committee can authorize bulk submissions of new data directly, with all new data marked `draft="unconfirmed"` (or other status decided by the committee), but only where the data passes the CheckCLDR console tests. |
| ## Meetings and Communication | ||
|
|
||
| The currently-scheduled meetings are listed on the [Unicode Calendar](https://www.unicode.org/timesens/calendar.html). Meetings are held by phone, every week at 8:00 AM Pacific Time (-08:00 GMT in winter, -07:00 GMT in summer). Additional meeting is scheduled every other Mondays depending on the need and people's availability. | ||
| The currently-scheduled meetings are listed on the [Unicode Calendar](https://www.unicode.org/timesens/calendar.html). Meetings are held by phone, weekly. Additional meeting is scheduled every other Mondays depending on the need and people's availability. |
Contributor
There was a problem hiding this comment.
Suggested change
| The currently-scheduled meetings are listed on the [Unicode Calendar](https://www.unicode.org/timesens/calendar.html). Meetings are held by phone, weekly. Additional meeting is scheduled every other Mondays depending on the need and people's availability. | |
| The currently-scheduled meetings are listed on the [Unicode Calendar](https://www.unicode.org/timesens/calendar.html). Meetings are held by phone and Google Meet, weekly. Additional meetings are scheduled depending on the need and participants' availability. |
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