Change Details

To better manage people's expectations, maybe we should try to come up with good estimates about how long it should take to add new language codes: Tasks to consider: * code for monolingual strings * code for lexemes * changes in labels for existing codes Assumptions: * request is complete with samples * simple code addition * basic criteria of Language committee fulfilled (whatever they may be) Steps to consider and estimates: [ ] help users create/complete their request: can be on [[https://www.wikidata.org/wiki/Wikidata:Project_chat|Project Chat]], [[https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team|Contact_the_development_team]], #Wikidata status //incoming// or //needs discussion or investigation// [ ] Language committee review: TBD (or two weeks without a response). Use "Due Date" feature to set end date. [ ] ~~Lydia review~~ [ ] coding done by volunteer: (estimate if Mbch331 available) within a week: using #Wikidata status //ready to go// [ ] coding done by WMDE: TBD: using #Wikidata status //consider for next sprint// [ ] code review by WMDE: (estimate) within a week: use tags #Wikidata-Campsite-Iteration-∞ status //peer review// and #Wikidata status //in progress// [ ] code deployment: (estimate) within a week [ ] test deployment [ ] (re)-triage of tickets on #Language_codes #Wikidata #Wikidata-Campsite-Iteration-∞ : done by Language codes project members or developers: usually weekly. See T284856 for steps Which steps can run parallel ? Current ranges vary from 1 week to x months even for trivial additions

To better manage people's expectations, maybe we should try to come up with good estimates about how long it should take to add new language codes: Tasks to consider: * code for monolingual strings * code for lexemes * changes in labels for existing codes (language name in English or other languages, not autonym) Assumptions: * request is complete with samples * simple code addition * basic criteria of Language committee fulfilled (whatever they may be) Steps to consider and estimates: [ ] help users create/complete their request: can be on [[https://www.wikidata.org/wiki/Wikidata:Project_chat|Project Chat]], [[https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team|Contact_the_development_team]], #Wikidata status //incoming// or //needs discussion or investigation// [ ] Language committee review: TBD (or two weeks without a response) [ ] ~~Lydia review~~ [ ] coding done by volunteer: (estimate if Mbch331 available) within a week: using #Wikidata status //ready to go// [ ] coding done by WMDE: TBD: using #Wikidata status //consider for next sprint// [ ] code review by WMDE: (estimate) within a week: use tags #Wikidata-Campsite-Iteration-∞ status //peer review// and #Wikidata status //in progress// [ ] code deployment: (estimate) within a week [ ] test deployment [ ] (re)-triage of tickets on #Language_codes #Wikidata #Wikidata-Campsite-Iteration-∞ : done by Language codes project members or developers: usually weekly. See T284856 for steps Which steps can run parallel ? Current ranges vary from 1 week to x months even for trivial additions

To better manage people's expectations, maybe we should try to come up with good estimates about how long it should take to add new language codes: Tasks to consider: * code for monolingual strings * code for lexemes * changes in labels for existing codes (language name in English or other languages, not autonym) Assumptions: * request is complete with samples * simple code addition * basic criteria of Language committee fulfilled (whatever they may be) Steps to consider and estimates: [ ] help users create/complete their request: can be on [[https://www.wikidata.org/wiki/Wikidata:Project_chat|Project Chat]], [[https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team|Contact_the_development_team]], #Wikidata status //incoming// or //needs discussion or investigation// [ ] Language committee review: TBD (or two weeks without a response). Use "Due Date" feature to set end date. [ ] ~~Lydia review~~ [ ] coding done by volunteer: (estimate if Mbch331 available) within a week: using #Wikidata status //ready to go// [ ] coding done by WMDE: TBD: using #Wikidata status //consider for next sprint// [ ] code review by WMDE: (estimate) within a week: use tags #Wikidata-Campsite-Iteration-∞ status //peer review// and #Wikidata status //in progress// [ ] code deployment: (estimate) within a week [ ] test deployment [ ] (re)-triage of tickets on #Language_codes #Wikidata #Wikidata-Campsite-Iteration-∞ : done by Language codes project members or developers: usually weekly. See T284856 for steps Which steps can run parallel ? Current ranges vary from 1 week to x months even for trivial additions