Figure out `maintainer` vs. `contact` in debcraft.yaml fields
Metadata
Current evaluation
Determines if debcraft.yaml maintainer and craft contact fields are duplicative or distinct. Requires a decision on field mapping and artifact inclusion. Open 209 days, zero comments, awaiting triage and assignment.
Suggested action: needs triage
Reason: The issue is unlabelled and has zero comments, indicating it has not been formally triaged or prioritized despite being opened by a maintainer. It represents an open design decision that requires assessment to determine if it is still relevant or actionable.
Staleness:
70
Complexity:
20
Confidence:
90
Support Request:
0
Issue body
Currently debcraft requires a `maintainer` field that corresponds to the control file's maintainer field, but the generic craft project has a `contact` field that serves a similar role and we had discussions about using that field. We should decide whether these fields are duplicative or serve different purposes, and if the latter, how to include the contact field in the resulting artifact.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| 2026-06-17 03:19:41.308239+00:00 | qwen3.6-35b-a3b-mtp-q6 |
Staleness:
70
Complexity:
20
Confidence:
90
Support Request:
0
|
needs triage | Determines if debcraft.yaml maintainer and craft contact fields are duplicative or distinct. Requires a decision on field mapping and artifact inclusion. Open 209 days, zero comments, awaiting triage and assignment. |
| 2026-06-17 03:17:11.792521+00:00 | pending | — | — | — |