Page MenuHomePhabricator

Allow different users to translate the same topic independently
Open, NormalPublic

Subscribers
Tokens
"Grey Medal" token, awarded by Liuxinyu970226."Like" token, awarded by Framawiki."Barnstar" token, awarded by geraki."Piece of Eight" token, awarded by Sunpriat."Grey Medal" token, awarded by RandomDSdevel.
Assigned To
None
Authored By
Pginer-WMF, Jan 8 2015

Description

Currently, two different users cannot start a translation for the same topic across the same languages.
This means that a user is not allowed to translate an article X if another user has started a translation draft before. This is problematic since we are making users unable to create content.

Allowing users to start translations about the same article also brings some challenges to avoid effort duplication. So we can:

  1. When creating an article, show a warning in the "new translation dialog" indicating that another user started a draft with an option to view it. (T214380)
  2. If the user views the other person draft (through 1) or accesses it by guessing the URL, the user will get a message about the draft author and options to either create a new draft based on the current content, or start a translation from scratch (check "View other persons draft" mockup of the design notes).
  3. When editing an article and another user starts a draft, a warning will be shown on top in the usual way warnings are shown in the translation editor (providing access to the other person draft).

Specific work for the different parts will be captured in sub-tickets.

Important disclaimer
This is not about collaborative editing. We are not proposing multiple uses to work at the same time on the same draft. We are proposing multiple users to be able to work on independent drafts on the same topic. Supporting the former brings lots of other complications.

Design details

Scenarios supported
T214416: Update the data model to allow translations by different users for the same topic and languages

New translation warning
T214380: Communicate that other users started this translation on the "new translation" dialog

Warning while editing your translation draft
T214411: Communicate other translations were started for this topic when editing your translation

Viewing other persons translation draft
T214409: Display in-progress translations

Related Objects

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
Arrbee raised the priority of this task from Normal to High.Feb 2 2015, 8:10 AM
Arrbee lowered the priority of this task from High to Normal.Feb 2 2015, 9:30 AM
Arrbee added a subscriber: Arrbee.
Nirzar added a subscriber: Nirzar.Mar 23 2015, 5:40 PM
Arrbee moved this task from Long term to CX5 on the ContentTranslation board.Apr 20 2015, 6:06 AM

I have no idea how this can block a feature like lists of articles to translate. Handling editing by multiple people inside CX is feature creep and should be avoided, moreover the issues with attribution etc. etc. are going to be esiziali/fatal.

To let someone else continue the translation, the user should simply publish the translation to a wiki page. If conversion from wikitext to the aligned structure CX uses is not possible, that could be stored for a while and retrieved when the page is reimported into CX by another user.

have no idea how this can block a feature like lists of articles to translate.

@Nemo_bis I can try to clarify this:

  • As it is noted in the "important disclaimer" section, this does not imply two people working on the same content (although I understand someone can infer it because is one possible way to solve the problem). Currently content translation does not allow you to translate an article if someone is working on it (in theory people can block articles to be translated just by starting a new translation, something I think we need to solve). What this task proposes is to inform you that someone else is working on the same thing but let you to do a new translation about the same article (taking into account aspects such as warning in case the content gets published by the other user among others).
  • In practice we had no reported issues of people having problems because of the above. However, it is a very important area to look carefully when doing changes that may direct multiple users to translate the same articles in a short period of time (which I think T96147 qualifies). So although it may not be a functional dependency, it is something we need to look close as we start working on a feature such as lists.
Amire80 moved this task from CX5 to CX6 on the ContentTranslation board.Jul 2 2015, 4:32 PM

An issue related to this was reported here.

Another issue relate to this was reported here.

Sunpriat rescinded a token.
Sunpriat added a subscriber: Sunpriat.
Amire80 moved this task from CX6 to Bugs on the ContentTranslation board.Oct 2 2015, 2:46 PM

One more issue related to this was reported here: a user unable to pick a topic to translate during a campaign.

Nemo_bis removed a subscriber: Nemo_bis.Jan 18 2016, 2:30 PM

This comment illustrates a user having trouble to find an article not already being translated by someone else.

He7d3r added a subscriber: He7d3r.May 27 2016, 7:25 PM
santhosh updated the task description. (Show Details)Sep 2 2016, 3:58 AM
Framawiki added a subscriber: Framawiki.

Hi, two news reports : on my talk page about one of mine translation draft, and on MW site Talk:Content translation.

This issue was reported in this comment.

Nnvu added a subscriber: Nnvu.Jan 8 2018, 7:42 PM
Strainu added a subscriber: Strainu.EditedMar 22 2018, 8:11 PM

And one more. I seem to remember a brief period when creating your own translation was possible? Was that an experiment or do I just remember wrong? Currently there is no way to do this as far as I can see

Arrbee moved this task from Bugs to Enhancements on the ContentTranslation board.Jun 22 2018, 1:40 PM
1997kB added a subscriber: 1997kB.Dec 22 2018, 3:29 PM
1997kB added a comment.EditedDec 22 2018, 3:34 PM

Another issue in which the user is same but forgot the password of old account.

Nick added a subscriber: Nick.Dec 22 2018, 4:32 PM

Why is the tool breaking one of our most important, long standing and cherished policies, namely https://en.wikipedia.org/wiki/Wikipedia:Ownership_of_content, and allowing the first mover to take over some level of ownership and control of an article in translation.

Also, the tool is abysmal, it does nothing but churn out error after error. I've no idea why it's enabled in Beta Features, because it looks like it's barely into Alpha let alone out and into Beta.

Why is the tool breaking one of our most important, long standing and cherished policies, namely https://en.wikipedia.org/wiki/Wikipedia:Ownership_of_content, and allowing the first mover to take over some level of ownership and control of an article in translation.

This is a limitation of the current data model that we plan to resolve. This ticket captures a proposal for doing so.

Also, the tool is abysmal, it does nothing but churn out error after error. I've no idea why it's enabled in Beta Features, because it looks like it's barely into Alpha let alone out and into Beta.

Content is very different from wiki to wiki. The tool has been very useful for many users on different wikis while others have experienced different issues on some articles on different wikis. We are working on a new version of the tool that is intended to provide a more solid editing experience. Since we cannot test all combinations of article × source language × destination language individually, it is very useful to hear about specific examples of the issues. Feel free to report any issue with the new version (the old one will be deprecated soon) in the project talk page or here in Phabricator.

Strainu added a comment.EditedDec 25 2018, 11:08 AM

the old one will be deprecated soon

We've been hearing that for at least 2 years, during which the tech ambassadors had to do the tech support that the team refused to do.

Do you at least plan to test bugs filed against v1 on v2, so we don't have to report the same issues again?

the old one will be deprecated soon

We've been hearing that for at least 2 years, during which the tech ambassadors had to do the tech support that the team refused to do.

As mentioned in T204817#4842893, the new version is being used for 45% of the translations. As new improvements are made we have been exposing the new version more prominently, and we plan to make it the default during next January. The new version replaces the editing surface used in version 1 (the browser default editing surface) with the Visual Editor one (more apt to deal with wikitext), which required to significatively refactor the different tools that manipulated the editing surface. So it has been a significant change and we wanted to expose the new version gradually.

Do you at least plan to test bugs filed against v1 on v2, so we don't have to report the same issues again?

Yes. We are already doing so. We have a process to review reported issues where we either (a) check that they are resolved with the new version, or (b) confirm that the issue still affects the new version. Recently we have been reviewing tickets related to references and templates which were the focus of the recent improvements in the new version, but we'll be covering other areas.

Pginer-WMF updated the task description. (Show Details)Jan 22 2019, 1:14 PM
Pginer-WMF updated the task description. (Show Details)Jan 22 2019, 4:33 PM
Pginer-WMF updated the task description. (Show Details)Jan 25 2019, 10:57 AM