Kulga A split extension would be useful
Seconded. Once you've finished writing that extension, you can test it by splitting this discussion off! 😉
christophermancini I think a user list at a minimum is important to be in the admin section of core.
It doesn't absolutely have to be in the core. I agree that it will be important to include some sort of user list as part of the default installation; but it could be done as a bundled extension. (And, at the risk of repeating myself, if we're going to make a user list available, why not put it in the user interface and add the user management functionality there, as has already been done with the user profile page?)
The fact that the user list page would be the ideal location for a Add User function may lead us to think that the user list should be in the core. But if I'm correctly understanding how extensions work, it would be entirely possible for your Add User extension to add that function to a page created by a User List extension.
But that would present a difficulty. The Add User extension would then be dependent on the User List extension, so anyone who wanted to replace the default User List extension with a third-party user list would not be able to take advantage of your Add User extension.
I suspect the best solution may end up being a hybrid. For example, we could add a "user list page" to the core; this would provide a space that extensions can populate with content, plus a route (e.g. example.com/u/ without any UID or username, as I suggested above) to that space. The actual user list would be added to this page by a bundled extension, which could be replaced by a better third-party extension, as @Kulga suggests.
Other functionality, such as the Add User feature, could be added by other extensions ... which would not need to be dependent on the bundled User List extension.
