Thanks for filing. What's the main objective here? (Depending on the answer, the possible implementations vary radically.)

(In reply to Bryan Davis from comment #0)

As a user who is going to be forcibly renamed
I would like the opportunity to choose a new name that I like
So that I'm not stuck with OLDNAME~wiki as my new name.

As a user who is going to be forcibly renamed
I would like to request a new name [...]
So I do not lose access to my account.

These two don't require using the home wiki. Reducing the need of bug 47918 (where "All such users will be in the case B") could.

Maybe this is actually a bug about creating a special page, given the dependency on bug 68889?

As there is the potential for a requested name to be in conflict with one or more local "titleblacklist"s, is it possible to check the name against the system-wide (even post the application), and not any wiki where it is in conflict? If too hard would it be possible for there be a capacity for it to run a check from the page.

Unless of course, the name change tool will be able to ignore any local rules, and to push through.

(In reply to Nemo from comment #1)

Thanks for filing. What's the main objective here? (Depending on the answer,
the possible implementations vary radically.)

(In reply to Bryan Davis from comment #0)

As a user who is going to be forcibly renamed
I would like the opportunity to choose a new name that I like
So that I'm not stuck with OLDNAME~wiki as my new name.

As a user who is going to be forcibly renamed
I would like to request a new name [...]
So I do not lose access to my account.

These two don't require using the home wiki. Reducing the need of bug 47918
(where "All such users will be in the case B") could.

Maybe this is actually a bug about creating a special page, given the
dependency on bug 68889?

I forgot to add the link to Brandon's design page which may clarify some things. Basically I'm going to be working on creating a new special page that will populate a new global table of rename requests. These requests will be processed by stewards to rename the local wiki account and promote it from a local account to a global one. Every account that we can get converted this way will be one less account that needs to be forcibly renamed.

The intent is to make this special page available prior to the forced rename implementation, hence the home wiki requirement. We will have many users who do not have an account on meta where renames are currently requested. By making the form for this available on each wiki we will be able to authenticate the existing user and keep track of who has asked for a rename in a reliable manner. We will use this to enforce that each account only has a single rename request pending at any given time.

The initial scope of this work will be to facilitate the SUL finalization process, but we are hoping that this will become the de facto method of requesting global account renames in the future.

(In reply to billinghurst from comment #2)

As there is the potential for a requested name to be in conflict with one or
more local "titleblacklist"s, is it possible to check the name against the
system-wide (even post the application), and not any wiki where it is in
conflict? If too hard would it be possible for there be a capacity for it to
run a check from the page.

Unless of course, the name change tool will be able to ignore any local
rules, and to push through.

I am planning to incorporate the checks that are done for a global account creation request as much as possible. I'm not sure what can or should be done in addition to that. Functionally I don't see this as being any different that a new account creation as far as naming restrictions are concerned.

Change 156488 had a related patch set uploaded by BryanDavis:
[WIP] Request a global account rename

https://gerrit.wikimedia.org/r/156488

Change 156488 merged by jenkins-bot:
Request a global account rename

https://gerrit.wikimedia.org/r/156488