Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[gemma3n] Split into its own family module + conformance (postponed)

未关闭
#377 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
冷清
技术栈
kotlin

调研方向

Read #346 for the module split template and #374 for the Gemma sweep that leaves Gemma 3n untouched. The issue names llm-inference/gemma, Gemma3nIngestion, and the kgemma CLI as the current code and consumer; begin by tracing that consumer and the Gemma3n* runtime, loader, and cache. Done means the family is split into the named modules, the DSL or hand-rolled runtime approach is decided, packed loading works, and the maturity gate passes.

由索引模型根据 Issue 内容生成。

描述

Postponed marker (like qwen's #352 lane) — descoped from the llama+gemma conformance release by decision.

Gemma 3n is effectively its own family living inside llm-inference/gemma: hand-rolled Gemma3nRuntime/Gemma3nAttentionBackend/Gemma3nKvCache (never touches gemmaNetwork()), own loaders, AltUp/ActivationSparsity ops — ~2000 LOC with exactly one external consumer (Gemma3nIngestion → kgemma CLI). Its engine delegation still has the defect fixed for gemma4: Gemma3nWeightLoader forces token_embd → GEMMA_DEQUANTIZE_ALL and Gemma3nLoadConfig dequantizes the whole model because the hand-rolled runtime can't consume packed tensors. Maturity gate: 0/5.

When picked up:

  • Move Gemma3n* + AltUp + ActivationSparsity + the gemma-module AttentionBackend into llm-inference/gemma3n (+ llm-runtime/kgemma3n facade), per the #346 template — mechanical, one consumer
  • Decide DSL migration vs documented Option-B hand-rolled runtime (AltUp/PLE/sparsity are the DSL-expressibility question)
  • Packed loading (kill the dense-FP32-everything default)
  • Maturity gate (golden parity, model-gated smoke, entry-point parity)

Refs: #346, #374 (the gemma sweep that leaves 3n untouched).

主要语言
Kotlin
星标
8
派生
3
平均合并
1 天 16 小时
30 天内合并 PR
48

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

SKaiNET-developers/SKaiNET-transformers 的其他 Issue

查看 SKaiNET-developers/SKaiNET-transformers 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。