Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Question: is the plugin registry still accepting community submissions?

Aperta
  • Qualcosa non va?
#71 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
25/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Ambito
documentation

Direzione di ricerca

Read CONTRIBUTING.md and GOVERNANCE.md, then review the status of PRs #69 and #70 alongside the other stalled pull requests. Clarify whether community submissions are accepted, what review latency and contributor actions are expected, and update the relevant process documentation if the current guidance is insufficient.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Question: is the plugin registry still accepting community submissions?

This is a process question, not a re-pitch. I have two PRs open (#69, #70) that have received no review, and I noticed the review queue looks stalled generally rather than specific to my submissions.

What I'm seeing:

  • Last commit to main: 2026-09-21 (#48).
  • No review on #69 or #70, both open since 2026-10-02.
  • Other open PRs with substantial discussion and no review: #62 (11 comments), #57 (4), #41 (38).

What I'd like to know:

  1. Is community Plugin submission still being accepted, or is review paused while the registry is reorganised?
  2. If it's active, roughly what should a contributor expect in review latency? CONTRIBUTING.md describes what review covers but names no reviewer or target, and GOVERNANCE.md notes the project "may introduce additional reviewer and maintainer roles as contribution volume grows" — so I can't tell whether review is expected to be staffed or best-effort.
  3. If my two PRs are fine as they are, no reply is needed — I just don't want them to sit indefinitely if something is expected from the contributor (a rebase onto main, a different manifest shape, splitting the Skill and the MCP server into two PRs, and so on).

For context on my two PRs, both are small and self-contained, and each ships its own verification evidence in the description:

  • #69 — four project Skills packaged for the registry. Includes a copyable example, expected result, requirements, and network/data sections.
  • #70 — a dependency-free stdio MCP server plus a Skill for static security triage of an Omarchy checkout. Passes npm run validate (OK plugin BoozeLee/omarchy-audit, 29 hosted Plugins validated). It's a triage tool, not a security fix, and isn't aimed at any bounty.

If the answer is that the queue is simply backed up, I'm happy to wait. I just didn't want to assume the repo was dormant by design versus by circumstance.

Thanks for reading.

Lingua principale
JavaScript
Stelle
19
Fork
17
Merge medio
1g 20h
PR unite (30g)
14

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di MiniMax-AI/MiniMax-Code-Plugins

Tutte le issue di MiniMax-AI/MiniMax-Code-Plugins

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.