Recommended namespacing of gadget snaps?

We are looking to create separate model assertions for public clouds, to support ubuntu-core in these environments. This will require separate gadgets for each, in particular to handle separate bootloader configuration.

These will be published to the snap store as public snaps.

Is there any guidance about how these should be named? E.g. would gadget snaps named ‘ec2’, ‘azure’, ‘gce’ be appropriate and accepted, or should these use some common prefix to avoid namespace squatting in the store?

We are currently simply using the device names (pi3, dragonboard, nanopi-air, nanopi-neo, etc) so the attempt sounds in line with the current naming scheme …