[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. @Lydia_Pintscher Looks like we wont get further input. - Tasks to consider above are mostly unchanged (obviously there are others, less related to Wikidata). Maybe the common point is that these are all additions or updates to configuration variables or language

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Lydia_Pintscher added a comment. We need to distinguish tickets that are additions of language codes and other language-related tickets. They are not the same and do not follow the same processes etc. This ticket was only about standardizing turn-around times for the addition of new language

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. @Lydia_Pintscher on some of the open points: - what's your view on the triage of tickets? Do you want to do it? Are the various boards/statuses fine with you? There was some debate about it at T168295#7165601

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. If we knew what problem you are trying to solve and the time this may take, we could help you address it. There seem to be aspects that are understood differently by Wikibase developers and the Wikidata community compared to langcom, so the langcom review can ap

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Amire80 added a comment. In T284276#7160323 , @Esc3300 wrote: > In T284276#7160314 , @Amire80 wrote: > >> Emails //from Phabricator// are not very efficient. > > If you want to p

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. In T284276#7160314 , @Amire80 wrote: > Emails //from Phabricator// are not very efficient. If you want to participate in a phabricator based process at some point you need to adopt its use. Personally, I thi

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Amire80 added a comment. In T284276#7160307 , @Esc3300 wrote: > I don't think any WMF process can rely on Telegram or other third party tools. Email is generic enough if you don't want Telegram, which is totally understandable

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. > It certainly happens that things get missed, and it's not good. [..], I'm easy to find on email and Telegram, and a lot of people use this successfully. Personally, I'm happy with the current process as re-designed by the language committee not too long ago. Th

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Amire80 added a comment. In T284276#7160260 , @Esc3300 wrote: > I suppose you refer to the timeframe for langco review of proposed new codes. Can you please stop writing "langco"? It's really weird. It's "Language committee", and i

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. Let's see what Amire80 suggests how we could improve the process as seen for "Alsatian". TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331,

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Mbch331 added a comment. In T284276#7160260 , @Esc3300 wrote: > > The consensus on Wikidata is that langco review isn't needed If @Lydia_Pintscher and her team don't agree with this, then I can make patches, but they won

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. I suppose you refer to the timeframe for langco review of proposed new codes. I don't think it's entirely new. It is already used for language codes on Wikidata for some time, given the lack of response and sometimes entirely incomprehensible arguments we had during

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Amire80 added a comment. This was already mentioned in T284151 as if it's the new rule, but it isn't. Please don't do this. It doesn't create a good impression. It comes back to the questions of what are the basic criteria of Language committe

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Amire80 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Amire80 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Mbch331 added a comment. In T284276#7148337 , @Esc3300 wrote: > Well, test is after deployment (i.e. ensure it actually works). Ideally this is done by the person who requested the new code. There is also a test done by WMDE after t

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. Well, test is after deployment (i.e. ensure it actually works). Ideally this is done by the person who requested the new code. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreference

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Mbch331 added a comment. In T284276#7148299 , @Esc3300 wrote: >> Which steps can run parallel ? > > I think there are two possibilities: > > - steps that can't technically done in parallel > - steps that can technically be done

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. > Which steps can run parallel ? I think there are two possibilities: - steps that can't technically done in parallel - steps that can technically be done in parallel For the later, there may be reasons to do them before or after some step. Obviously,

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Mbch331 added a comment. > Which steps can run parallel ? Actually none. It doesn't make sense to start coding before there's approval. If a ticket doesn't get approval by langcom, you've coded something that's never going to be used. You can't review a code change, without the coding

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. In T284276#7139740 , @Lydia_Pintscher wrote: > In the case of new language codes no coding is involved. It's just adding it to a list, which @Mbch331 does, and then someone from the dev-team just reviews, like a

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Lydia_Pintscher added a comment. In T284276#7138007 , @Esc3300 wrote: > I think primarily all maintenance, development, and code review is done by WMF/WMDE, at least per Jimmy Wales' plan, but maybe we should also consider the hypothesi

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. Sounds reasonable. The process seems more "predictable" since the two of you take care of it. I suppose we agree that Wikidata's needs are very different from Incubator's. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricato

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

jhsoby added a comment. I agree this is a good idea, I have to admit that we (langcom) are often a bottleneck in this – more often than I would like. So what if we say something like, if nobody hears from Langcom within 2 weeks of a request being posted, a request can be assumed to be ok? Wh

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. @Amire80 @jhsoby what's your view on this? TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, E

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. In T284276#7133853 , @Mbch331 wrote: > In T284276#7133623 , @Esc3300 wrote: > >> I noticed that the quickest step usually is Mbc331 . >> >> - As creation

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Mbch331 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Mbch331 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Mbch331 added a comment. In T284276#7133623 , @Esc3300 wrote: > I noticed that the quickest step usually is Mbc331 . > > - As creation of these codes is a basic Wikidata maintenance step, I suppose we should also plan for when Mbc331

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 added a comment. I noticed that the quickest step usually is Mbc331 . - As creation of these codes is a basic Wikidata maintenance step, I suppose we should also plan for when Mbc331 isn't available and it has to be done by WMDE. - For code review, I added a few open ones I

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 updated the task description. TASK DETAIL https://phabricator.wikimedia.org/T284276 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Esc3300 Cc: Mahir256, Mbch331, Amire80, jhsoby, Lydia_Pintscher, Aklapper, Esc3300, Invadibot, maantietaja, Ak

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Lydia_Pintscher added a comment. Yeah as @Mbch331 said, no review needed from my side. If he submits the patch as usual ( ❤ ) it'll be reviewed in less than a week except for some very unusual circumstances. It then goes out within a week with the next deployment train unless it's halted for

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Mbch331 added a comment. Coding done by volunteer -> 1 week after langcom approval (should be shorter, but depends on when the volunteer (usually mee) has time). (Doesn't matter which of the three it is.) Coding done by WMDE: Don't know if they want to spend "expensive" paid resources when

[Wikidata-bugs] [Maniphest] T284276: define standard turn-around times for language code additions for Wikidata

Esc3300 created this task. Esc3300 added projects: Wikidata, Language codes. Restricted Application added a subscriber: Aklapper. TASK DESCRIPTION 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: