Hi! Not quite sure what is the conversation here, but if you need my input, please do tell (preferrably in english - or point me to the essential bits and can try machine-translate it)
Hi there @jonas, the subject of the conversation was about an issue we have for the gcli command line application.
That application is built as a
-
Linux binaries (amd64 + arm64), as well as Debian
.debpackage files. -
MacOS binary plus
homebrewequivalent of a package.
And for both Debian and Homebrew it seems the gcli name is already taken by other official packages.
So this post is about two things:
-
Coming up with a new name for the
gcliapplication, that would be unique and not conflict with existing packages inDebianandHomebrew. -
A request for help in properly registering the new name in both
DebianandHomebrewpackage repositories so that this issue doesn’t occur again.
And I am hoping you could help with that last point, specifically for Debian 
Debian is not a registry.
Securing a namespace (i.e. name of package, command, etc.) involves maintaining a package.
I already maintain far too many packages in Debian, so I will not volunteer for new ones here (and in fact, I would prefer if someone closer to this mostly french-spanish tool would take over maintaining silkaj as well). What I can offer is to help guide you or others willing to step in themselves and take on the work and responsibility of maintaining the project as an official package in Debian.
dcli is available in debian and homebrew.
I’m volunteer to package and maintain both.
I can take over maintaining silkaj too.
dcli name is fine for me.
Nice! Please do reach out as a Debian bugreport, so that we can have a public track record of the handover 
I’m wondering, more specifically for Gcli (soon to be “dcli” I guess), is it possible to have more than one maintainer for a Debian package?
I don’t have the knowledge yet but would be interested in learning how it works as a “backup” maintainer.
Yes, I’ll do it.
BTW I would like to be mentored by @Pini to become maintainer.
Should I mention it in the bug report ?
Yes, Debian packages can be maintained either by a single person or by a team.
What I suggest to file as a bugreport is the takeover of maintainership for silkaj.
Becoming a maintainer is a prerequisite for taking over, and does not involve bugreports (bugreports are tied to packages, not to contributors).
Just regarding the name gcli, we could actually call the Debian package duniter-gcli to avoid conflicts and keep gcli as the CLI name. I think this is common practice.
It’s possible, isn’t it?
The probability that a user will install two different gcli tools on their system is extremely low, negligible in my opinion.
But I’m fine with dcli.
It is possible to mark the package as conflicting with another, so apt will refuse to have both installed simultaneously. But if I were a user who wanted both, I would find the situation quite annoying and ridiculous.
This situation will never happen
Réflexions intéressantes pour le nommage d’un projet logiciel.