Fork `basement`? As `baseplate`?

turion:

• You can optionally apply for a global/public name without your namespace prefix, but you have to pledge maintainership and have fever privileges, e.g. hackage trustees are allowed to give control over that name to someone else if they believe that the other person will be a better maintainer for the community

I personally would never apply for global/public name in that case.

Why would I trust someone else to know better than me who is a good maintainer for the package/library I wrote?

This policy is in very stark contrast to e.g. what the CLC does for core libraries: although it can appoint new maintainers, it generally only does so when the current maintainer is not contactable or has quit.

I don’t think you’ll find a whole lot of passionate package authors who would agree to your proposed deal.

You could do it another way and say global/public names are just symlinks maintained by a committee or something. But at that point, I’d rather not upload my packages to hackage anymore. If they decide to put one of my packages into global namespace with my name on it, then change it in a couple of years to something worse, this could indeed damage my own reputation as a maintainer.