Page MenuHomePhabricator

Save translations in Draft namespace where it is available
Closed, ResolvedPublic

Description

Context
The draft namespace provides place for work-in-progress content.

Unfortunately, the draft namespace is not available in al Wikipedias, so it can be used only when it is available.

Narrative
As a user, I can create translations in a common place, so that they do not depend on my user and duplications are reduced.

Acceptance Criteria

  1. For wikis with draft namespace enabled, in-progress translations are saved in the draft namespace.
  2. For wikis with draft namespace enabled, anonymous users can create and publish translations.
  3. For wikis without draft namespace support, translations will use the user namespace as usual.
  4. The change should be transparent to the different CX processes:
    1. Processes that get translations across different wikis, should be aware of the possible locations.
    2. For wikis with draft namespace, a decision is made on what to do with the existing translations under the username space (deprecate, migrate, integrate...).

Event Timeline

Arrbee raised the priority of this task from to Needs Triage.
Arrbee updated the task description. (Show Details)
Arrbee added a project: ContentTranslation.

Depending on the collaboration model supported for translations, the draft namespace may be a viable option or not (e.g., how to deal with two users translating the same article from different source languages into the same target one?).

The model described at T86151 (where several users can work on independent translations about the same topic) doe not seem to fit in the draft namespace idea (of one draft per topic).

Depending on the collaboration model supported for translations, the draft namespace may be a viable option or not.
The model described at T86151 (where several users can work on independent translations about the same topic) doe not seem to fit in the draft namespace idea (of one draft per topic).

santhosh claimed this task.
santhosh subscribed.

Since we have a feature to save the translations in progress, the need to save translations is already addressed. As Pau said, collaboration on translation is a big feature and need to be discussed and designed.

We also have a configurable target namespace option now. If a community want the translations to be published in Draft namespace instead of Main namespace, wgContentTranslationTargetNamespace can be cofigured to do so.

Considering the above two facts, I dont see anything else to address for this bug. Closing.