The github username is “MonolithProjects”, so the backend is defaulting to thinking that should be the namespace. In old galaxy, namespace names were managled and lowercased and substituted with underscores to try to conform to collection namespace requirements. That is probably why you were able to end up with a “monolithprojects” namespace. In the new galaxy, we have removed all the magic munging of namespaces and are adhering to exactly what the users are specifying with their import commands and in the content itself for predictability and consistency.
If you want to keep your github user as “MonolithProjects” but have your roles use “monolithprojects”, you’d need to add a “namespace” key in the meta/main.yml for all your roles that specifies “monolithprojects” as the true namespace. At import time, the backend code will use this namespace key as the source of truth …
After updating the source for all your roles on github, you should next delete all the roles in the “wrong” namespace via curl by their role id …
https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/community/userguide/#http-client
You can’t permanently delete the “MonolithProjects” namespace as that will get auto created every time you login to the UI, but it doesn’t have to contain any roles.