Greetings, The overall issue was identified a *very* long time ago... and I suspect succinct and precise memories from then might be a little difficult to come by without some digging. That being said, as noted the decision to change was due to the state of the [trade|word]mark space. For Open Source projects, it is important to avoid conflicting with marks which are already held. In general, to have a mark, such as a trademark or a wordmark, you are required to "protect and defend" your marks to keep your marks. If you search[0] for marks for the word "quantum", you will see there are many many instances of use of the mark already. I don't know what the OpenStack Technical Committee will decide in regards to releasing the package name, but you may also want to reconsider your naming by first doing some trade/wordmark searches to ensure your project name is not going to be problematic as time goes on. Good luck! -Julia [0]: https://tmsearch.uspto.gov/search/search-information On Tue, May 13, 2025 at 12:14 PM Sean Mooney <smooney@redhat.com> wrote:
On 13/05/2025 20:03, Jay Faulkner wrote:
Just for historical knowledge...
OpenStack Neutron, the OpenStack project for networking, used to be called Quantum. This project still exists and is extremely active -- and is why we still hold this name. I don't work on Neutron much so I'll let them (and or TC/foundation reps) reply as to how they'd feel about it.
```
I am the creator and maintainer of the programming language "qb" (qb · PyPI <https://pypi.org/project/qb/>, qb <https://lschreiber.eu/qb/>) and I wanted to implement a package manager similar to how Maven, Cargo or Poetry works. I picked the name "quantum" for this program and noticed that this name was already in use on pypi for a package developed by you.
```
more historical context neutron was renamed form quantum due to trademark and copyright reasons so calling the package manager for your new language quantum may hit the same legal issues.
Thanks, JayF