Conflicting Composer package name

Dear Frank,

I am a developer for Mantis Bug Tracker (https://mantisbt.org), a popular open-source issue tracker written in PHP.

While we don't actually distribute MantisBT via Packagist today, we do make use of Composer for our dependencies, and our software has been declared in our composer.json as mantisbt/mantisbt since 2017.

I never realized until today that we had never actually registered it on Packagist... Only to find that you had actually registered the mantisbt name for your own binary tree library.

It's worth noting that There are several packages which are in fact MantisBT plugins, that mistakenly depend on yours because of this (see https://packagist.org/packages/mantisbt/mantisbt/dependents).

Given that mantisbt is a well-established brand name for our project since 2000, I was hoping that you would be willing to consider publishing your library under a different name, e.g. `drmantis84/mantisbt^ or whatever, so we could actually claim the mantisbt vendor name, which we feel rightfully belongs to us. Since there are only about 50 installations (most of which are likely to be a consequence of the above-mentioned MantisBT plugins declaring a dependency on mantisbt/mantisbt), hopefully this wouldn't cause too much inconvenience.

Looking forward to hearing from you.