Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Pluginkit: Let a plugin run on more than one host

Open
  • Is something wrong?
#15 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
go
Domain
backend

Research direction

Start with the pluginkit package, which holds Plugin, Migrator, Seeder, RouteProvider and PublicPathProvider, and with the host-side sdk package that each plugin currently imports. The issue asks for a decision first: what a plugin may request from a host, and how a host declares what it offers. Done means that design is agreed in the thread, not that code is written; a newcomer should wait for maintainers to settle it.

Written by the indexing model from the issue text.

Description

A plugin written for one host cannot run on another, even when it needs nothing that host owns. This blocks a shared plugin pool and any marketplace built on one.

Current state: pluginkit carries the lifecycle only, and Plugin, Migrator, Seeder, RouteProvider and PublicPathProvider are already host agnostic. Everything else a plugin reaches for comes from its own host's sdk package, and that single import ties the plugin to that host for good.

Proposal: settle what a plugin may ask a host for, and how a host declares what it offers. A plugin needing only the lifecycle, its own schema and its own routes should compile against pluginkit alone.

Trigger: the first plugin wanted on both hosts, or the marketplace design.

Dominant language
Go
Stars
69
Forks
3
Avg merge
9h 11m
Merged PRs (30d)
38

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gopherium/framework

All issues in gopherium/framework

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.