work in progress
User story:
As a Wikidata architect interested in adding a new language code,
I want a process that lets me know in advance if a new language code will be accepted or not
to not waste time.
As a Wikidata developer,
I want a more failproof process
to not make errors (see e.g. T273627).
Problem:
Our current processes around adding new language codes sometimes lead to inconsistent and hard-to-predict results. Also, the implementation can be inconsistent in some cases. This can be a frustrating experience for all parties involved and lead to subpar results.
Also: we have seem to have some bad config T284808: Add a configuration variable that allows disabling language codes for labels, descriptions, and aliases
Examples:
Solution:
Make processes clearer and easier. Ideally one could predict the outcome of a request even before sending it in.
Also, we need a process that helps to vet the changes to avoid back-and-forth decisions or problematic outcomes (e.g. removing code with existing Lexemes)
Related:
- T284276: define standard turn-around times for language code additions for Wikidata and T284808: Add a configuration variable that allows disabling language codes for labels, descriptions, and aliases
- https://www.wikidata.org/wiki/Help:Monolingual_text_languages
- https://www.wikidata.org/wiki/User:Lea_Lacroix_(WMDE)/List_of_lists_of_languages
- Language codes Phabricator project and workboard