Overhaul of the plugin maintenance/system
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
调研方向
从 channel.json 以及 plugin-channel/plugins/.json 和 updated-plugins/**/.json 下的插件元数据开始，然后比较所链接的 release 和 repository 布局。完整的结果应定义所列 repository 的所有权模型、版本/tag 引用、artifact 链接以及未来的 hash 字段；该 issue 未指出实现入口或测试。
由索引模型根据 Issue 内容生成。
描述
Description
This is a topic which spans over multiple repositories:
- plugin-channel
- updated-plugins
- micro
- all dedicated plugin repositories (present inside micro-editor)
- 3rd-party channels etc.
Current situation:
We have a lot of plugins which are currently "maintained" inside one single "large" updated-plugins repository, which are somehow old forks or the last "actual" state. On top of that we have plugin-channel which point to plugins inside updated-plugins or the upstream locations.
Both repositories have in common that they store the binary artifacts of every tracked version in one release...
- https://github.com/micro-editor/plugin-channel/releases/tag/plugins
- https://github.com/micro-editor/updated-plugins/releases/tag/v1.0.0
...so they are uploaded manually...for each plugin.
The traceability is actually an absolute pain.
Right now there is no authentication check available for any plugin.
channel.json points to...
- https://github.com/micro-editor/plugin-channel/tree/master/plugins/*.json
- https://github.com/micro-editor/updated-plugins/tree/master/**/*.json
...which point to "internal" as well as external resources.
Target situation:
Each plugin shall be tracked within one single repository, whether it's one of micro-editor or a third party.
Each version of each plugin must be tracked with its version number AND tag fitting together. Based on the tags GitHub will already create "snapshots" of the actual repository content, archive them to a zip and tar.gz, which then can be linked as artifact (actually no need to track further manually uploaded binaries/artifacts).
The *.json's pointing to the concrete files/versions should include (for future) revisions an entry for the hash of the file, to provide at least some sort of authenticity.
Unfortunately GitHub's tag snapshots don't generate a SHA256 on its own.
We need a plan where the master *.json is tracked and which location it shall point to.
I think we can agree, that the micro team can't maintain every possible plugin, but the question is, if it shall curate the plugins and point to fixed releases?
- 主要语言
- Go
- 星标
- 29.8k
- 派生
- 1.4k
- 平均合并
- 1 天 12 小时
- 30 天内合并 PR
- 2
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
micro-editor/micro 的其他 Issue
-
feature syntax
难度 2/5 1-3 小时 新手友好度 72/100
micro-editor/micro#4289 ·
维护者通常 3 天内回复
-
Also bind alt-click for multi-cursors可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭feature
难度 2/5 1-3 小时 新手友好度 68/100
micro-editor/micro#4260 ·
维护者通常 3 天内回复
-
XML syntax highlighting breaks if empty tag contains whitespace before close可能已有人在做 @justadityaraj 于 59 天前认领。 未关闭bug syntax
难度 2/5 1-3 小时 新手友好度 68/100
micro-editor/micro#4213 · 1 条评论 ·
维护者通常 3 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
micro-editor/micro#3553 · 5 条评论 ·
维护者通常 3 天内回复
-
syntax
难度 2/5 1-3 小时 新手友好度 64/100
micro-editor/micro#2969 · 3 条评论 · 1 个 reaction ·
维护者通常 3 天内回复
查看 micro-editor/micro 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
-
[Bug] K8s reconcile still resets explicit 0 to defaults for response_api, memory and flow state可能已有人在做 @Bevisy 今天认领。 未关闭needs-acceptance
难度 2/5 1-3 小时 新手友好度 87/100
vllm-project/semantic-router#5998 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
devantler-tech/ksail#8256 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
desktop v3 windows
难度 2/5 1-3 小时 新手友好度 75/100
esengine/DeepSeek-Reasonix#15016 · 1 条评论 ·
维护者通常 1 天内回复