Talk:SUL finalisation

Community discussion of hierarchy for who has priority for a username
Where is it? If it doesn't already exist, why hasn't this already been done? This can be done now before the software is written, the scripts run, and the usernames changed. Risker (talk) 02:55, 26 June 2014 (UTC)
 * You're one year late to the party: m:Talk:Single User Login finalisation announcement. There is m:Talk:Global rename policy in some activity now (you probably saw messages on local wikis by stewards). --Nemo 05:36, 26 June 2014 (UTC)
 * Okay - so show me the hierarchy. Risker (talk) 07:42, 26 June 2014 (UTC)
 * You asked a discussion, I linked it. Precedences for global accounts have already been set in 2008, see m:Help:Unified login. --Nemo 07:47, 26 June 2014 (UTC)
 * So in other words, no, there hasn't actually been a discussion with the community specific to the hierarchy of which of multiple accounts will get custody of a username that has actually come to any resolution. Nemo, you know this is what I wanted to know; it would have been okay to simply say "Risker, there is no hierarchy agreed to by the community, or even discussed or proposed to the community".  We both know that the software that will run through and change usernames to create SUL accounts needs to be programmed according to the hierarchy.  We both also know what happens when Engineering, in solving a technical problem, creates a social problen directly involving tens of thousands of users - in this case, potentially on every project, not just the noisy ones. Usernames are a big deal, and this is a serious editor retention issue.  This needs to be resolved. This is what they have their community liaisons for, to lead these kinds of discussions and obtain this kind of consensus.  Risker (talk) 08:01, 26 June 2014 (UTC)
 * Nope. The hierarchy exists, this doesn't mean it wasn't discussed on the talks I linked. --Nemo 08:13, 26 June 2014 (UTC)
 * Nemo, do you know what the hierarchy is? If so, please publish it or link to it.  Risker (talk) 15:14, 26 June 2014 (UTC)
 * Hello both! Jumping in quickly - the Community Liaisons have a planning meeting early next week to begin discussing the communications plan surrounding this project. There will be hierarchy with clashing usernames, which we will be discussing with the community soon. We have a lot of work to do surrounding this change, and I admit I don't currently know all of the ins and outs of it, but I trust that I'll learn with your help :). Risker, absolutely, usernames are a big deal and something that we need to handle as sensitively as possible. More information coming soon. Rdicerb (WMF) (talk) 18:11, 26 June 2014 (UTC)
 * Hello . I think the most useful suggestion I could give you at this point is to follow the lead of the Legal and Community Advocacy team in the manner in which they have handled large-scale discussions of global policies (terms of use, privacy policy, etc); they've got some pretty good practices, and there's no reason to re-invent the wheel. I know it is possible to run a script to identify how many users/which users have conflicting usernames now, although as I recall the last time it was run there were over 100K users involved.  From that list, it should be possible to run another script that will cross-reference to the "home wikis" of the users.  That can give you a list of wikis that you want to target with your messages/invitations to participate. In fact, gathering as much info as possible about the users who have conflicts and being able to present that information in the discussion will be useful, provided that it comes with a caveat that the number of users involved is fluid.  Things to consider reporting: how many users on various projects are affected; how many by user category (steward, checkuser, oversighter, bureaucrat, other permissions - there are a whole pile of them, autoconfirmed, editor, etc); number of editors affected in various strata of activity/inactivity (e.g., highly active, active in past year, inactive in past year, inactive in past 5 years, inactive more than 5 years, etc); your team can probably come up with a few other ways of slicing and dicing the affected users.  Ensure invitations go to every bureaucrat noticeboard/renaming noticeboard on every project. And so on. Risker (talk) 05:29, 29 June 2014 (UTC)

Don't fail to update the English Wikipedia
It should not have to be my or anyone else outside your team's job to have to update en:Wikipedia:Unified login/Finalisation with the latest status of your project, such as this new commitment to setting a date for finalisation by the end of September. —  Scott  •  talk  22:17, 17 July 2014 (UTC)
 * Good point, duplication is very bad. Fixed: . --Nemo 22:41, 17 July 2014 (UTC)

Notifications
I would be interested to know how affected users will be notified. For example, I have a local account in around 100 wikis and use a different username in 10 wikis, and there is another person who uses the same username as me in those 10 wikis. The issue is that this second person is active, but responds neither to messages on his talkpage nor to emails (he has no email in his preferences but has a valid email on his user page). Thus my questions are the following: This is a very important change (as all edits are attributed to usernames, thus attribution of all article edits and talk page comments should change) and this is significantly different to regular user rename process (as in most projects only inactive accounts could be usurped), thus I believe users should be adequately informed of the process and be aware of the outcome — NickK (talk) 22:25, 25 August 2014 (UTC)
 * What will be the notification policy — will users receive emails and messages on talk pages for each accounts, will users receive one message or email per group of accounts or will there just be some CentralNotice message?
 * Will lists of concerned accounts be available somewhere — for example, for local communities may be in better position to reach and help affected but active and experienced users?
 * Will users receive information whether their account will be renamed in case of clash or other accounts will be renamed?
 * What will be done with renamed users? Will there be any disambiguation for both concerned users (they will not have access to their talk page anymore and their login will change) and other users (who may still find links on discussion pages to the page already belonging to a different person and still try to send an email to a concerned user but contact a different person instead)
 * You might get a faster reply if you ask at m:Talk:Single User Login finalisation announcement instead. I would also recommend you to go to Special:MergeAccount and merge your account. That way, it will be easier to see where the user name belongs to you (those accounts will be attached to SUL) and where it belongs to someone else (those accounts will remain local).
 * I'm not sure exactly what the developers are planning, but it seems that users will be notified in some way. --Stefan2 (talk) 14:20, 26 August 2014 (UTC)
 * Thanks for the pointer, Stefan2. It also helps others that will come to that page and ask the same questions - we'll have a nice FAQ soon.
 * NickK, to the points:
 * The plan is to notify accounts that are not attached, all accounts, individually and not as a group. There's no real good way to parse which person owns which account on which wiki, and also it is imperative that every account is told individually. There can be no opportunity for "No one told me!" in this significant process.
 * A list of accounts per-wiki to post for the community's help is a wonderful idea. If feasible, I'll see what I can do to make this happen. Any and all help is sought and appreciated.
 * Yes.
 * Like the current process, all edits in page histories will have their attribution changed to point to the correct account. Old signatures is tricky - I think a nice solution would be if a WMF or volunteer developer would write a tool that a renamed user could run through their brand-new global.js on Meta that would crawl through the wikis and replace old signatures. We'll see how that goes.
 * In summary, proper communication of information is what will make this whole thing work and it is a dedicated process. Most of this work will pick up in October once the engineering is finished and the timeline is more clear. Hope this helps. Keegan (WMF) (talk) 19:38, 26 August 2014 (UTC)
 * Stefan2: thanks for advicing this, but I do not know whether it will be easier to ask accounts to be usurped or deal with merging two global accounts one by one (i.e. I will definitely have to attach local accounts once I have freed global ones).
 * Keegan (WMF): thanks for your reply. I guess it will make sense to, one hand, notify affected users (it would be better if one would be able to send one message per user only, for example, by checking emails, matching passwords or checking pairs of interwikis, as receiving dozens of mails, one per account, will be annoying), on the other hand, notify local communities (that would be particularly interested in selecting users with high contributions and/or any advanced rights, as hardly anyone will try to track users with 1 or 2 edits) — NickK (talk) 22:04, 26 August 2014 (UTC)
 * I don't imagine sending multiple emails. If there are email matches, that's an easy step to eliminate. Accounts will probably still get multiple brief messages on their wiki talk pages as well. Keegan (WMF) (talk) 22:49, 26 August 2014 (UTC)
 * But talk messages trigger enotiftalk :); and many users pay more attention to talk page messages than to emails so it's not a trivial decision to skip either of the two for users with email set. --Nemo 10:46, 4 September 2014 (UTC)
 * About the last question, is there going to be something like 61074, or is that abandoned? --Stefan2 (talk) 22:15, 26 August 2014 (UTC)
 * the ability to login with old credentials is essential to this process. It's not this particular patch, though. You can find the current one under review here. Keegan (WMF) (talk) 23:04, 26 August 2014 (UTC)

Wrong wiki?
If I am not mistaken, this does not affect any of the millions of other users of the Media Wiki software, and does not belong on this page at all. Where this does belong is on Metawiki, the cross wiki page for all of the Wikipedia projects. Anyone can download and install the Mediawiki software on their website, and no one using those sites will ever be able to use a SUL account on those, in my understanding. I would suggest deleting this page and importing it to Wikimedia (leaving only a redirect). Apteva (talk) 18:51, 22 September 2014 (UTC)
 * Hi, this page is in this wiki due to the coding/engineering tasks involved. Your objection is understandable, but it comes about 4-5 years too late, see Category:WMF Projects. If you believe the page confusing there are probably ways to improve that: as for the title, "SUL" is a nickname used only on Wikimedia projects, isn't it? The extension is called CentralAuth. --Nemo 19:57, 22 September 2014 (UTC)
 * I have no problem if someone wants to create a page here called "CentralAuth implementation", but this statement, "Resolve any remaining clashing user names, so that in the future every user may have a single username to log in with on all wikis" has absolutely no relevance to MediaWiki, and is only referring to the Wikimedia projects. I have no reason to be referred to a MediaWiki page for an issue that only affects the Wikimedia projects. So the only part of this page that is relevant to MediaWiki is the implementation of CentralAuth - which is something that can be used by any assortment of wikis. Apteva (talk) 20:25, 22 September 2014 (UTC)
 * Better? --Nemo 20:44, 22 September 2014 (UTC)
 * Much better, but the issues of how to unify user names on the Wikipedia projects does not belong here, but on Meta wiki. Only the software issues of doing that belong here, not the user issues. Apteva (talk) 21:10, 22 September 2014 (UTC)
 * The main announcement pages and user-help pages, are already at meta: Single User Login finalisation announcement (which has 7 talkpage archives) and m:Help:Unified login. This page is indeed, primarily for the software issues (although most of the Stewards and Bureaucrats who are involved, are also technically knowledgeable, hence there is a lot of overlap). HTH. :) Quiddity (WMF) (talk) 01:30, 23 September 2014 (UTC)
 * The finalisation announcement page is a bit strange place for discussion about the finalisation as a whole. Bever (talk) 03:55, 5 October 2014 (UTC)

Finalisation, when?
I'm pretty excited about the prospect of SUL, and I was wondering when I will be able to have my global watchlist? --LT910001 (talk) 00:04, 28 October 2014 (UTC)
 * When I just reviewed the list with contributions of Bevers, I got the impression that the six conflicting accounts with my name have less contributions than before. Is this a result of the finalisation project, or is my memory misleading me? Bever (talk) 09:33, 18 December 2014 (UTC)
 * Deletions and other events can reduce the visible edits of a user, but the editcount field is not necessarily updated. To run the finalisation scripts, most information in the databases has been verified and updated, so it's possible that the editcounts of those users were updated and decreased. Now they are closer to the truth. --Nemo 06:24, 28 March 2015 (UTC)

Format of new names
I would like to ask attention for the comments which have been made half a year ago about the format of the new names of users who are forcibly renamed. User Wnt criticized this format even in May 2013 on Meta, but there has not been a real answer. See also meta:Talk:Single User Login finalisation announcement.
 * The tilde is an awkward choice, some people may have difficulties with typing this. For example, when followed by an n or a vowel, the tilde is places above the character (ñ, ã, õ) instead of before it, on many computers. Also the suffixes are rather long. Therefore I support Wnt's proposal to use a hyphen instead, I think there will be little cases where this would result in a new conflict.
 * Also for Wikipedia names, the suffix could be shortened to -en or -enw or -enwp instead of ~enwiki, which is not very informative anyway, aren't all WikiMedia sites wikis? Bever (talk) 11:32, 15 March 2015 (UTC)
 * Yeah, again that choice was probably made thinking nobody would actually need to type the username on login. I hope this will prove correct...
 * The "enwiki" format for IDs is a historical thing, the databases have been called like that since the time MediaWiki was born. --Nemo 06:24, 28 March 2015 (UTC)

Password safety
There is the idea that a user who is forcibly renamed, can still log on with his/her old user name and password. At least once, so that the user has an easier transfer to the new situation. But what happens when both users have the same password (12345, for example)? I think the idea is hazardous. Bever (talk) 11:38, 15 March 2015 (UTC)
 * Practically speaking, the risk might be minimal because most conflicting accounts never cross, for instance a French-speaking user who only ever visits French wikis and an Italian-speaking user who only ever visits Italian wikis. So in most cases the login attempts will come from the correct user.
 * As for intentional "attacks", we can't do anything about them when the user chooses a weak password. In your example, the local account could already have been "stolen" by any user with the same name on another wiki by entering that password on Special:MergeAccount. So in the end the "institutional" answer is probably that accounts with weak passwords can't be protected. --Nemo 06:24, 28 March 2015 (UTC)

Why no redirect?
Why are user pages and talk pages moved without redirect? (Example: en:User talk:Lupi.) It is confusing even for an experienced editor who sees a redlink in a forcibly user's signature, and it must be even more confusing for less experienced editors, who won't know how to talk with such a user. At the very least, a softlink like "This page has been moved to User talk:Lupi~enwiki" would address that problem. SebastianHelm (talk) 17:23, 31 December 2015 (UTC)
 * Because the user page would now be used by the global "Lupi" account, so the redirect would be misleading. The move/deletion log snippet should provide that softlink. Legoktm (talk) 00:32, 2 January 2016 (UTC)

Chinese Remainder and its construction
“Eva Lou Billingsley Russell”, also affectionately known as ``Grandma Rap'', 82 of Birmingham, was the founder and owner of Fraternal Cafe in downtown Birmingham for more than 20 years. She was a Civil Rights activist most noted for feeding the local as well as attending to the national civil rights movement for many years. Mrs. Russell operated feeding programs for the homeless and poor, and years afterwards she was remembered for its humanity in surely troubled communities. Grandma rap spent considerable time encouraging young people to get in on education and to stay away from drugs. Many times this message was rapped to the children. It is not uncommon to pick up a magazine and find one of her poems or to hear a child reciting one of her poems in a church or at a school throughout the city. She is the author of the book “Golden Threads” --A Collection of Poems About Her Black Family. Eva Lou Billingsley Russell is very active at Saint Joseph Baptist Church where she has been a member for a number of years. Most recently, she was a deaconess, Chair of the Pastor's Aide Board, and worked with the Missionary Society, Homeless Committee, Willing Workers and served in numerous other capacities of leadership throughout her membership at the church; including Vice President of the St. Joseph Day Care Center, Youth Supervisor and Chair of the Deaconess Board. Shiloh Baptist Church and others as disciplined for Christ Ida Avant Russell agree in this manner; and a Portrait in our History.

Shiloh is a founding Baptist as well as church institution with a great history. Around since the turn of the 20th century it like some other Sacramento Churches was a cornerstone to Azusa and its principal seized waterways.

Necessary prior code/ops steps

 * ✅ : ACTION: ?? to run the pass0 script to clean up data; updated stats review
 * ✅: PG's AccountAudit extension deployed and $wgCentralAuthAutoMigrate enabled on 2013-05-10 (allows gradual automatic merging by users on login).
 * ✅ by Legoktm, September 2014: also create a global account upon login when all local accounts belong to the user.
 * : ACTION: ?? to run the migrateAccount script for non-conflicting users, in order:
 * ✅ Merge 10k users who only exist on one wiki, and are not attached
 * ✅ Merge 18k incorrectly unattached users and 3k LUGM
 * ✅ Iterate over all unattached accounts with email and, where all accounts for a username have the same (confirmed) email, merge them all.
 * Send emails to make 50k global accounts claim all their local unattached accounts (gives 28 days time)
 * Email the (up to) 3.3M unattached, email unconfirmed accounts (sendConfirmAndMigrateEmail.php)
 * [Timing depends on how many] Automatically create some more global accounts (migrateAccount.php --auto)
 * Figure out other cases which need no manual intervention
 * Next steps (parallel):
 * Hoo? – Review lego's patch for 4
 * Depends on stats DB ✅
 * ✅ : Finalize the global rename user tool and get deployed
 * Note that renamed users MUST have their cookie invalidated.
 * Next step:
 * ✅ Legoktm, CSteipp, Hoo man - Merge https://gerrit.wikimedia.org/r/#/c/92468/ and test on beta
 * ✅ CSteipp, Hoo man, Legoktm - deploy on cluster and test. Planned for July 9th.
 * ✅ We need the ability to re-run metrics like these
 * Setup DB for tracking unattached user in the cluster
 * Ops: rt #7775
 * CSteipp? - Scripts to synchronize user tables
 * ✅ : Add sufficient unit tests to CentralAuth to prevent regressions
 * Plenty more could be added, but we should get notification of major breakage now.
 * ✅ : Run pass0 again, to ensure localnames and globalnames are accurate
 * Legoktm - See updates at 67350.
 * : Write & deploy new code for auto-login-to-alternate account.
 * ("You logged in as 'Foo' but your username has been automatically changed to 'Foo~Barwiki' - please use this in future")
 * Started as - Abandoned
 * ✅ Patch by bd808 to handle most cases:
 * ✅ Core hook and hook implementation by CSteipp to handle case where winner later renames, so no global account conflicting with the looser's old name exsits
 * Notification page once you login with your old name
 * : Write & deploy clashing-user-rename-and-globalise script.
 * Note that a single user with multiple local accounts that clash with a global account need to be renamed to a single global account named after the “home wiki” per the same code that Special:MergeAccount uses
 * Note that a single user with multiple local accounts that clash with a global account need to be renamed to a single global account named after the “home wiki” per the same code that Special:MergeAccount uses

Desirable prior code/ops steps

 * : 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?
 * ✅ Deploy UserMerge extension to all wikis
 * ✅ Update extensions to be compatible - bug 67758
 * ✅ Fix major bugs in Ex:UserMerge
 * ✅ Enable UserMerge for all wikis in beta, test
 * Next steps:
 * Legoktm - quash bugs found during testing in beta
 * ✅ CSteipp - Merge global merge, disabled by config
 * : 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.
 * ✅ bug 68886 Request global account rename from home wiki before forced SUL name change
 * bug 68924 Create special page to manage global rename request queue
 * Depends on Global Rename tool
 * Next steps:
 * Bd808 is working on patches

Project pages

 * /Global account merge


 * Global rename
 * older implementation (historical, outdated)
 * User documentation for tool


 * SUL Audit:
 * February 2013
 * March 2013
 * April 2013
 * May 2013
 * July 2014
 * September 2014