snapcraft and the store disagree on what to call developer namespaces
Metadata
Current evaluation
Superseded. Snapcraft no longer prompts for or manages developer namespaces, rendering the terminology mismatch obsolete. The secondary 2FA UX concern was split into a separate bug report.
Suggested action: —
No scores available.
Issue body
"""
$ snapcraft login
Enter your Ubuntu One SSO credentials.
Email: <email address hidden>
Password:
We strongly recommend enabling multi-factor authentication: https://help.ubuntu.com/community/SSO/FAQs/2FA
You need to set a username. It will appear in the developer field alongside the other details for your snap. Please visit https://myapps.developer.ubuntu.com/dev/account/ and login again.
Login failed.
"""
Assuming the role of a new user, I set a username when I created my account. It's ev+test. The thing you want me to do the store calls something entirely different (and equally confusing):
"""
The Developer namespace will be appended to all your package names to help avoid name collisions across the store.
The namespace is required only when uploading a package for Phone or Snappy; however, it cannot be removed once set and cannot be changed while you have active packages.
Developer namespace
[_________________]
Enter a value consisting of lower-case letters, numbers or hyphens. Hyphens can not occur at the start or end of the chosen value.
"""
Can we please sync these up so they use the same language?
I'd also suggest not showing the 2FA suggestion unless there's a successful login. Saying "login failed" is a bit redundant given that you just instructed them to login again. That might be better at the start of the paragraph, if present at all.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Superseded. Snapcraft no longer prompts for or manages developer namespaces, rendering the terminology mismatch obsolete. The secondary 2FA UX concern was split into a separate bug report. | |
| qwen/qwen3.6-35b-a3b | — | — | Superseded. Snapcraft no longer manages or allows users to set developer namespaces, making the terminology mismatch obsolete. The secondary 2FA feedback was tracked separately. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Inconsistent terminology between snapcraft CLI and Ubuntu Developer Store regarding developer namespaces, with a UX suggestion for 2FA messaging. Unaddressed for over nine years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Reports terminology mismatch between snapcraft CLI and Ubuntu Store for developer namespaces. Suggests aligning language and adjusting 2FA prompt placement. No maintainer response in over 9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Report requests terminology alignment between snapcraft CLI and Ubuntu Store for developer namespaces, plus a minor UX fix for login error messaging. Unaddressed for over nine years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Inconsistent terminology between snapcraft CLI and Ubuntu Store regarding developer namespaces. Requests aligning the language and improving 2FA message flow. Open, untriaged, and awaiting review. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1886223 snapcraft recommends bad naming standards | snapcraft (launchpad) | open | Reports that the snapcraft register CLI prompt implied third parties couldn't publish snaps and suggested username suffixes, contradicting store naming docs. No maintainer response; the referenced register command/prompt no longer exists in current snapcraft. |