Page MenuHomePhabricator

Notifications DB should be centralized across Wikimedia wikis
Open, MediumPublic

Description

I suggest we centralize the translators database for all wikis that use Translate and TranslationNotifications. This may necessitate giving translators more fine-grained control over what types of pages (by wiki / by topic) they're willing to translate, but is preferable over having to build a translators database for each site that might require translations.

See Also:
T37306: Global (to a wiki farm or family) message delivery (thoughts)

Details

Reference
bz39073

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 12:59 AM
bzimport set Reference to bz39073.
bzimport added a subscriber: Unknown Object (MLST).
Eloquence created this task.Aug 6 2012, 5:07 PM

I agree in principle.

Implementation-wise, currently the "translators database" is, in fact, just a bunch of additional user preferences. Having global preferences is supposed to solve this.

Creating another global database seems a bit of an overkill, especially considering that CentralAuth is a bit of a hack. Do we have any other global storage except the basic login data in CentralAuth?

Identity, messaging, affiliation. :)

CCing E2 team so this can be looked at in the context of the overall notifications work.

In the meanwhile several wikis have enabled TranslationNotifications and built their own subscriptions...

Cf. bug 35306 comment 15.

Nikerabbit raised the priority of this task from Low to Medium.Jun 7 2016, 8:56 AM
Nikerabbit updated the task description. (Show Details)
Nikerabbit removed a subscriber: wikibugs-l-list.