- name: mgccli
- description: Magalu Cloud command line interface
- snapcraft: we can’t provide the yaml, because we use Goreleaser to publish snaps: goreleaser_internal.yaml
- upstream: Github - MagaluCloud/magalu
- aliases:
- alias1: mgc
- reasoning: our application is a CLI, and our other packages and documentation already use commands starting with “mgc.” Therefore, I kindly ask for the approval of the alias “mgccli.mgc” for “mgc.”
To the best of my knowledge, there is no existing snap alias already granted or a well-known Linux application conflicting with the aliases requested here.
Hello @geffersonFerraz! There is already a snap named mgc, so this alias can not be granted.
-1 from me - The alias is already taken.
Is the mgc snap above in a brand store? From the global store perspective, it looks like it’s in private at best - would it be best to reconsider from the POV that the alias is being denied by something that most people can’t prove exists?
Hypothetically, if mgc is infact unused, would it not be preferable to transfer it over to someone who has a purpose for it?
I understand the intention in not granting aliases where it can cause confusion, but there is no mgc snap for anyone other than the admin staff or the single account/brand to be confused with, and avoiding 3 letter package names in order to prefer aliases is generally a good practise, which mgccli is.
1 Like
Hey folks,
I can confirm that there is a private snap in the global store called mgc. However, there is no revision available for it.
In this case, I think we should revoke the mgc snap before granting the alias if it is reasonable. @store @alexmurray how do we typically mediate this situation?
Thanks
From what I can see the user who registered the mgc snap (@mgclabs) did so a while ago and so this does look to be abandoned. As such it seems reasonable to consider removing it from the store, particularly as there are no snaps published to the snap name. @store can you please advise if this is possible? Thanks.
