What should I do with admin_delegation?

13 months ago, I wrote admin_delegation and put it in my sandbox. It does basically the same thing, in a different way (it even directly accesses the user table instead of proper API functions).

The primary differences are that it

1. Adds account administration links to the users' view page under an Account Administration heading instead of in a Roles tab.
2. Allows the delegation of the account status (active/blocked).
3. Assigning of delegated permissions are on their own page instead of in the core Permissions list.
4. Users do not see the Account Administration heading on their own view page.

I wrote it for a site that has 80 modules, 30 content types, and 30 roles, so putting the role delegation on a separate permissions page was intentional because the core permissions grid was becoming incredibly large. I also called it admin delegation because I can see it growing into other delegated permissions (like status, email update, password reset). Combined with User Read-Only, that would mean users can be blocked from updating their own email unless they contact a user moderator, for example.

Just tried your module... It seems well thought out. It looks like it could supersede Role Delegation!

Some of Role Delegation's issues would apply to admin_delegation as well, such as #341165: Module should use user_save instead of directly accessing drupal database (drupal6 patch).

A drawback that comes to mind: Since your module inserts its functionality into the standard user view page, it won't be accessible when that page is overridden (with Content Profile, for example). Because of this, it might be a good idea to provide the functionality in a separate tab.