Ground truth: numcrux transfer/donation (governance decision)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 领域
- data, machine-learning
调研方向
Start by reading the linked parent issue #984, then review CONTRACT.md and skainet-test-groundtruth/build.gradle.kts for the stated technical preconditions. The issue is done when the owners decide whether to transfer the corpus, what happens to gradienttracer and licensing, and whether CI should use a numcrux-hosted corpus; it does not specify an implementation task.
由索引模型根据 Issue 内容生成。
描述
Sub-issue of #984.
skainet-ground-truth's actual Python content is already framework-agnostic — it
imports only torch and gradienttracer, zero SKaiNET/Kotlin coupling. The "SKaiNET"
branding is only in the repo name and README framing, not the code, matching
numcrux's own stated mission ("a public, neutral,
versioned reference-data commons... framework-agnostic and language-agnostic... will
start with the existing numerical test suite from SKaiNET").
skainet-test-groundtruth/build.gradle.kts's fixture-source path is now overridable
(-PgroundTruthSourceDir, defaults to the sibling-checkout convenience it always had),
and CONTRACT.md documents the GGUF tensor-naming/metadata conventions explicitly — so
SKaiNET's consumer no longer needs to change if/when the underlying fixtures move to a
numcrux-owned repo. That was the technical precondition; this issue is the remaining
non-technical one.
Open questions (for whoever owns this decision)
- Does
skainet-ground-truth's content get donated/transferred to thenumcruxorg
outright, or doesnumcruxstart a fresh corpus andskainet-ground-truthstays as
SKaiNET's own (possibly narrower, possibly diverging) fixture set? - If transferred: does
gradienttracer(the execution/serialization engine) move too,
or stay underSKaiNET-developersas infrastructure numcrux depends on? - License/attribution framing for a neutral commons vs. a SKaiNET-branded repo.
- Whether SKaiNET's CI (
.github/workflows/ground-truth.yml) should point at the
numcrux-hosted corpus once one exists, via-PgroundTruthSourceDir, or continue
usingskainet-ground-truthas a curated subset.
Not blocking anything today — filed so the decision has a home when it's ready to be
made, and so the "near future" framing from the original ask has a concrete place to
land.
- 主要语言
- Kotlin
- 星标
- 52
- 派生
- 15
- 平均合并
- 1 天 15 小时
- 30 天内合并 PR
- 36
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
SKaiNET-developers/SKaiNET 的其他 Issue
-
coding good first issue size:xs skill:kotlin-core sub-issue
难度 2/5 1-3 小时 新手友好度 88/100
SKaiNET-developers/SKaiNET#1323 ·
维护者通常 1 天内回复
-
coding good first issue platform size:xs skill:js sub-issue
难度 2/5 1-3 小时 新手友好度 72/100
SKaiNET-developers/SKaiNET#1232 ·
维护者通常 1 天内回复
-
skeep tracking
难度 5/5 一周以上 新手友好度 15/100
SKaiNET-developers/SKaiNET#1331 ·
维护者通常 1 天内回复
-
assessment size:s skill:review sub-issue
难度 4/5 1-2 天 新手友好度 18/100
SKaiNET-developers/SKaiNET#1330 ·
维护者通常 1 天内回复
-
documentation good first issue size:s skill:docs sub-issue
难度 3/5 1-2 天 新手友好度 78/100
SKaiNET-developers/SKaiNET#1329 ·
维护者通常 1 天内回复
查看 SKaiNET-developers/SKaiNET 的全部 Issue
相似的 Issue
-
bug need-device
难度 2/5 1-3 小时 新手友好度 64/100
ramesh130/superplayer#495 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
maxrave-dev/SimpMusic#2649 ·
维护者通常 2 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 66/100
PimpinPumpkin/Vela#778 ·
维护者通常 1 天内回复
-
M1 manhwa list未关闭Bug Domain changed
难度 2/5 1-3 小时 新手友好度 62/100
keiyoushi/extensions-source#19882 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 3 天内回复