← Back to issue list

init-plugin command for new plugin creation

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1629910
Type
issue
State
open
Author
~jaymell
Labels
new-plugin plugin
Created
Updated
Closed

Current evaluation

Feature proposal for an 'init-plugin' command to scaffold new snapcraft plugins; opened ~10 years ago by an external contributor, zero comments, no PR submitted, no maintainer engagement, and it predates the current parts-based plugin architecture.

Suggested action: close stale

Reason: Last activity was 3618 days ago with zero comments; the author promised a PR from a fork branch (jaymell/snapcraft InitPlugin) that never materialized, and the proposal targets the pre-rewrite plugin system while the repo now shows a parts/extensions-based architecture. Inactive for ~10 years and no longer applicable to the modern codebase, so it should be closed as stale rather than triaged as new work.

Impact: 25 Quick Win: 15.0 Staleness: 95 Complexity: 40 Confidence: 55 Support Request: 10

Issue body

Hi, I wanted to open this to track progress for an "init-plugin" command. The idea for this came from feedback received when filing bug 1624798: https://bugs.launchpad.net/snapcraft/+bug/1624798/comments/1. I've done some initial work on a branch for this (https://github.com/jaymell/snapcraft/tree/InitPlugin) and would like to submit a PR once it's further along. The main goal would just be to: 1) create proper dir structure and plugin sub-class based on plugin name provided 2) provide hook-ins to existing documentation for plugins / some other helpful guidance I'd be glad to hear anyone's thoughts on this. Thanks!

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 25
Quick Win: 15.0
Staleness: 95
Complexity: 40
Confidence: 55
Support Request: 10
close stale Feature proposal for an 'init-plugin' command to scaffold new snapcraft plugins; opened ~10 years ago by an external contributor, zero comments, no PR submitted, no maintainer engagement, and it predates the current parts-based plugin architecture.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 25
Confidence: 90
Support Request: 10
close stale Feature request to add an 'init-plugin' CLI command for scaffolding new plugins. Unanswered for nearly 10 years with no maintainer engagement.
qwen/qwen3.6-35b-a3b
Staleness: 100
Complexity: 40
Confidence: 95
Support Request: 5
close stale Proposal for an init-plugin command to scaffold new Snapcraft plugins. Unaddressed for nearly 10 years with no maintainer response or follow-up PR.
qwen3.6-35b-a3b-mtp-q6
Staleness: 100
Complexity: 30
Confidence: 90
Support Request: 10
close stale Request to add an init-plugin CLI command that scaffolds directory structure and plugin subclasses for new plugins. Untriaged, inactive for nearly a decade, no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 40
Confidence: 92
Support Request: 10
close stale Proposes an init-plugin command to scaffold new plugin directories, subclasses, and documentation hooks. Author has a working branch and seeks feedback before submitting a PR. Currently under discussion, awaiting community review.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.