Allow adding snaps that you are a collaborator for

[evandandrea]

In user testing Blake tried to add the maas snap to build.snapcraft.io, which is owned by the maas LP user. Blake is a collaborator on this snap, but it told him that he didn't have permission to add it.

[cjwatson]

Do you have the exact error message? Do you know at exactly which stage it failed?

[bartaz]

My guess would be that name registration failed (if name is owned by maas user and was attempted to be added by other user), as that's the first point where we do any permissions checks with the store.

Unless it was a problem with some GH permissions (only GH admins can add repos).

[cjwatson]

Those were also my guesses, but it would save much time going down blind alleys to have the exact error message, which would disambiguate.

[evandandrea]

Yes, sorry. It was a failure in the name registration box. I don't recall the exact message, but I believe it was "Sorry, that name is already taken"

[Saviq]

Here's a screenshot of the message I got in the exact same situation for mir-kiosk-apps

[adglkh]

Same here.
We're in a transition towards migrating some snaps build from launchpad to build.snapcraft.io.
I am a collaborator of easy-openvpn project.
When I added the repo and clicked "Register name", error pop-ups.

This issue probably will be going to be a major setback for developers who use build.snapcraft.io to build & publish snap into a store, especially for a large project which has a bunch of developers to contribute.
I didn't stumble upon by this issue on launchpad when building&publishing snap on it as a collaborator.

[bartaz]

Duplicate of #799