Hi, > Just to be clear, personally, I agree with the both original and the > current cmdtest maintainers that this issue has been caused by the other > upstream, and the other upstream's collaboration on a resolution has > been poor.
I'd like to point out that no one in the current Yarn development team was there when the project name was coined. Myself only joined it in 2017, far too late to have any weight in its naming (2015 / 2016). By this time changing the binary name was already quite difficult (we actually experimented with it by also shipping a `yarnpkg` binary through npm, but noone in our community really used it; and we couldn't remove `yarn` by fear of breaking a lot of CIs - as a package manager, Yarn is often one of the entry points to JavaScript, and keeping it stable is very important ...). > I agree with the original maintainer that this namespace takeover attempt > feels like bullying. "Mine is bigger than yours" is not a good argument for > anything in Debian. I can't speak on behalf of the former Yarn team, but I can assure you that the current one had no intent to bully anyone. We're all open-source maintainers, and I'm sure you can resonate if I tell you that our only goal is to make things as smooth as possible for our users - even people who want to use both Yarn and cmdtest! My understanding was that these binary conflict situations, although impractical for everyone, sometimes happen, and my hope was that we could find a solution together. I initially contacted Lars in 2019 and was given reasons to think that a renaming would be possible, but our exchange was short and I failed to see how much frustration you had with this situation - which I can understand. Best regards, Maël
