add support for the "contact" field in snapcraft
Metadata
Current evaluation
PR #1447 was closed unmerged after inactivity; maintainers deferred contact-field support pending store metadata discussions and suggested reopening or redoing it.
Resolution: closed stale
Reason: PR #1447 never received review or CI validation. In the final maintainer comment on 2017-12-14, @sergiusens said contact was still under discussion and the PR could be reopened or redone once settled.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This allows a snapcraft.yaml to have a new "contact" field. This is part of a wider meta-data improvement, outlined in https://forum.snapcraft.io/t/development-sprint-june-26th-2017/415/48. The idea is that the metadata is part of snapcraft.yaml and that snapcraft pushes the metadata via some new store API to the store. The idea is that the metadata can be changed on the store side (e.g. to add new translations without having to push a new snap revision) but to still make it transparent for people who do not use the web-ui. A conflict mechanism is also planned.
This PR is one (important) first step because right now the other metadata (summary, description) can already be part of snapcraft.yaml but `contact` is currently not supported.
LP: #1624829 (partly)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | PR #1447 was closed unmerged after inactivity; maintainers deferred contact-field support pending store metadata discussions and suggested reopening or redoing it. | |
| stealth/space-bunny-alpha | — | closed stale | Contact-field support was deferred and PR #1447 closed unmerged after inactivity; @sergiusens said it could be reopened or redone after store metadata discussions concluded. | |
| qwen/qwen3.6-35b-a3b | — | — | Support for the contact field was deferred and the pull request closed. Maintainers cited pending store API and metadata discussions, asking the author to wait until the feature is finalized before reopening or resubmitting. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without merging. Implementation was deferred pending forum discussions and finalization of the new store API. Maintainers requested the PR be reopened or resubmitted once the contact field requirements are settled. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #692 Use the new snapcraft mailing list as contact info | snapcraft | closed | PR #692 updated copyright contact info to the new snapcraft mailing list but was closed unmerged after bot pings went unanswered; the same change landed via merged PR #702 (commit 41a544d20). | |
| #2164 add support for the "website" field in snapcraft | snapcraft | closed | PR #2164 was closed unmerged because snapd and review tools lacked website support and the proposed code did not work; passthrough was recommended. Later metadata-link support landed in snapcraft#4275 (de56fe6a1). |