Adding one more parameter project name to the snapcraft init command

Metadata

Project: snapcraft (launchpad)
Number: #1672578
Type: issue
State: open
Author: ~liu-xiao-guo
Labels: —
Created: 2017-03-14 12:56 AM UTC
Updated: 2017-03-14 12:56 AM UTC
Closed: —

Current evaluation

Feature request to add a project name argument to 'snapcraft init' so the generated snapcraft.yaml template is pre-filled with the name. No maintainer response, no labels, no activity in ~9.5 years.

Suggested action: needs triage

Reason: The issue is a well-formed feature request (add a positional project-name argument to the init command so the template's name/summary/description fields are pre-populated) but shows zero maintainer engagement: no labels, no comments, no assignee, and last activity 3458 days ago. It has never been triaged, so needs_triage is the correct default. The request is small in scope (a CLI argument plus template substitution in the init command) and low impact — a convenience improvement, not a bug — so impact is low. Staleness is high given the ~9.5-year inactivity, but the underlying convenience need is still plausible in modern snapcraft, so it is not clearly obsolete enough to close as stale without first checking whether the init command already accepts a name argument.

Impact: 20 Quick Win: 15.0 Staleness: 95 Complexity: 25 Confidence: 70 Support Request: 30

Issue body

So far, snapcraft init works well in most of the cases. However, it would be best to have the following kind of format: $ snapcraft init project_name so that, the template is like: ==================================================== name: project_name # you probably want to 'snapcraft register <name>' version: '0.1' # just for humans, typically '1.2+git' or '1.3.2' summary: This is balabal project_name description: | This is a template project for project_name grade: devel # must be 'stable' to release into candidate/stable channels confinement: devmode # use 'strict' once you have the right plugs and slots parts: my-part: # See 'snapcraft plugins' plugin: nil =================================================== A developer does not need to change the template much to start to work on the new project straight away. Now, every time, I have to change the strings in the template thought it is not a big effort. Thanks & best regards, XiaoGuo

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 07:49 AM UTC	qwen/qwen3.8-27b	Impact: 20 Quick Win: 15.0 Staleness: 95 Complexity: 25 Confidence: 70 Support Request: 30	needs triage	Feature request to add a project name argument to 'snapcraft init' so the generated snapcraft.yaml template is pre-filled with the name. No maintainer response, no labels, no activity in ~9.5 years.
2026-07-23 02:07 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 98 Complexity: 15 Confidence: 95 Support Request: 10	close stale	Feature request to add a project name argument to snapcraft init for pre-filling templates. Open for over nine years with zero comments or maintainer engagement.
2026-07-22 12:19 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 98 Complexity: 20 Confidence: 95 Support Request: 10	close stale	Feature request to add a project name argument to snapcraft init for pre-filling templates. Unlabeled, zero maintainer interaction, and inactive for over 9 years.
2026-07-09 08:59 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 98 Complexity: 15 Confidence: 85 Support Request: 10	close stale	Feature request to add a project name argument to snapcraft init for pre-filling templates. Unanswered for ~9 years with zero maintainer interaction.
2026-06-20 11:42 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 98 Complexity: 15 Confidence: 90 Support Request: 0	close stale	Request adding a project name argument to snapcraft init to auto-populate template fields, reducing manual editing. Open for over nine years with zero comments, awaiting triage and assignment.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.