Question: is the plugin registry still accepting community submissions?
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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:
- Is community Plugin submission still being accepted, or is review paused while the registry is reorganised?
- If it's active, roughly what should a contributor expect in review latency?
CONTRIBUTING.mddescribes what review covers but names no reviewer or target, andGOVERNANCE.mdnotes 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. - 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.
- 主要语言
- JavaScript
- 星标
- 19
- 派生
- 17
- 平均合并
- 1 天 20 小时
- 30 天内合并 PR
- 14
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
MiniMax-AI/MiniMax-Code-Plugins 的其他 Issue
-
难度 5/5 一周以上 新手友好度 25/100
MiniMax-AI/MiniMax-Code-Plugins#47 ·
维护者通常 1 天内回复
查看 MiniMax-AI/MiniMax-Code-Plugins 的全部 Issue
相似的 Issue
-
macOS
难度 2/5 1-3 小时 新手友好度 76/100
beyondcode/herd-community#1761 ·
-
content good first issue hacktoberfest
难度 2/5 1-3 小时 新手友好度 74/100
vieanderes/understory#19 ·
-
automated issue report
难度 2/5 1-3 小时 新手友好度 68/100
lirantal/discoprint#37 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
tauri-apps/tauri#16219 ·
维护者通常 2 天内回复
-
agentic-workflows
难度 1/5 1 小时以内 新手友好度 90/100
githubnext/gh-aw-cao#16599 ·
维护者通常 1 天内回复