Validate maintainer names
Metadata
Current evaluation
Feature request to validate the maintainer, original-maintainer, and uploaders fields as RFC822 Name <email> format in debcraft. Open 285 days with no labels, comments, or activity; no evidence of a fix or related work.
Suggested action: needs triage
Reason: The issue has no labels, no comments, no assignee, and no maintainer acknowledgement in 285 days, showing no sign of triage. It is a legitimate, well-scoped validation task (RFC822 parsing of three metadata fields), and there is no evidence it was implemented elsewhere or is no longer applicable, so closing as stale is not justified. Confidence is moderate because I could not inspect the current debcraft source to confirm whether validation already exists.
Impact:
30
Quick Win:
19.5
Staleness:
70
Complexity:
35
Confidence:
60
Support Request:
5
Issue body
We need to validate that the `maintainer`, `original-maintainer` and `uploaders` fields contain valid RFC822 `Name <email@address>` fields.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
19.5
Staleness:
70
Complexity:
35
Confidence:
60
Support Request:
5
|
needs triage | Feature request to validate the maintainer, original-maintainer, and uploaders fields as RFC822 Name <email> format in debcraft. Open 285 days with no labels, comments, or activity; no evidence of a fix or related work. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
80
Complexity:
10
Confidence:
90
Support Request:
0
|
needs triage | Request to validate maintainer, original-maintainer, and uploaders fields for RFC822 Name <email> format compliance. Currently inactive with zero comments or labels for 244 days. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
35
Confidence:
80
Support Request:
10
|
needs triage | Request to add validation for maintainer, original-maintainer, and uploaders fields to ensure they follow RFC822 Name <email> format. Currently open with no maintainer response or comments after 231 days. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
65
Complexity:
30
Confidence:
80
Support Request:
10
|
needs triage | Add validation to ensure maintainer, original-maintainer, and uploaders fields conform to RFC822 Name <email@address> format. Open for 209 days with no comments, awaiting triage and assignment. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #40 Figure out `maintainer` vs. `contact` in debcraft.yaml fields | debcraft | open | Open design question on whether debcraft.yaml's required maintainer field overlaps with the generic craft contact field, and how contact should map into the built artifact. No labels, comments, or maintainer response in 285 days; code still has a TODO comment (contact -> Maintainer) in project.py. |