Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Question: is the plugin registry still accepting community submissions?

Ouverte
  • Quelque chose ne va pas ?
#71 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
1/5
Temps estimé
Moins d'une heure
Accessibilité débutants
25/100
Type d'issue
Documentation
Clarté
À clarifier
Activité
Active
Domaine
documentation

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
JavaScript
Étoiles
19
Forks
17
Merge moyen
1 j 20 h
PR mergées (30 j)
14

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de MiniMax-AI/MiniMax-Code-Plugins

Toutes les issues de MiniMax-AI/MiniMax-Code-Plugins

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.