SUL finalisation

From MediaWiki.org
Jump to: navigation, search

SUL finalisation would unify user accounts across all Wikimedia wikis.

Status[edit | edit source]

2014-07-monthly:

In July, the SUL finalisation team began work on completing the necessary feature work to support the SUL finalisation.

To help users with local-only accounts that are going to be forcibly renamed due to the SUL finalisation, the team is working on a form that lets those users request a rename. These requests will be forwarded onto the stewards to handle. The SUL team is currently in consultation with the stewards about how they would like this tool to work. When this consultation is wrapped up, the team will begin design and implementation.

To help users get globally renamed without having to request renames on potentially hundreds of wikis, the team implemented and deployed GlobalRenameUser, a tool which renames users globally. As the tool is designed to work post-finalisation, it only performs renames where the current name is global, and the requested name is totally untaken (no global account and no local accounts exist with that name).

To help users who get renamed by the finalisation and, despite our best efforts to reach out to them, did not get the chance to request a rename before the finalisation, the team is working on a feature to let users log in with their old credentials. The feature will display an interstitial when they log in, informing them that they logged in with old credentials and that they need to use new ones. We are also considering a persistent banner for those users, so that they definitely know they need to use their new credentials. An early beta version of this feature is complete, and now needs design and product refinements to be completed.

To help users who get renamed by the finalisation and, as a result, have several accounts that were previously local-only turned into separate global accounts, the team is working on a tool to merge global accounts. We chose to merge accounts as it was the easiest way to satisfy the use case without causing further local-global account clashes that would cause us to have to perform a second finalisation. The tool is in its preliminary stages.

The team also globalised some accounts that were not globalised but had no clashes. These accounts were either created in this local-only form due to bugs, or are accounts from before CentralAuth was deployed where the user never globalised. As these accounts had no clashes, there were no repercussions to globalising these accounts, so we did this immediately.

At present, no date has been chosen for the finalisation. The team plans to have the necessary engineering work done by the end of the quarter (end of September 2014), and have a date chosen by then.

Next month the team plans to continue work on these features.

History[edit | edit source]

Originally, Wikimedia wikis operated completely independently from each other, with separate user accounts and passwords for each wiki. CentralAuth was created to let users log in with the same credentials across multiple wikis, but as the wikis operated independently for years there were thousands of clashing accounts, i.e. cases where different people had registered the same name on different wikis. These clashes prevent those affected from logging in with the same name across all wikis.

Project Goal[edit | edit source]

The goal of the SUL finalisation is to forcibly rename any clashing user accounts so that every single user has their own single unified login across all Wikimedia sites.

Project Duration[edit | edit source]

TODO: Fill this out

Backlog[edit | edit source]

Necessary prior code/ops steps[edit | edit source]

Desirable prior code/ops steps[edit | edit source]

  • N Not done: Write & deploy global user merging so two global users can be merged together
    • What to do when two clashing local instances under the global accounts?
    • Next steps:
      • Legoktm - implement based on Dan's specifications
  • N Not done: Write & deploy a tool for local ‘losing’ users to check a proposed new account name (check against clashing global and local users, and also against the global user account name rules) and request it be done.
    • This needs to integrate with Stewards current rename workflow
    • Depends on Global Rename tool
    • Next steps:
      • DGarry (WMF) - Requirements and UX input

Project pages[edit | edit source]

See also[edit | edit source]