👋 New contributors: start here
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 20/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 冷清
- 技术栈
- kotlin
调研方向
This pinned issue is a contributor guide, not an implementation task. Read the linked getting-started guide and issue taxonomy to understand the DARC and SKEEP workflows; use the linked issue searches to find a specific open sub-issue with a file to copy and a Gradle task to run. Done means claiming and completing that sub-issue, rather than changing this guide.
由索引模型根据 Issue 内容生成。
描述
Welcome! This issue stays pinned so the first thing you see is how to find something you can actually do.
Two workflows, one sentence each
- DARC (Document / Assess / Research / Code) drives one feature — an operator, a metric, a kernel. A feature is one parent issue (
trackingdarc) plus small, skill-labelled sub-issues you can claim on their own. - SKEEP records one architectural decision — public API, DSL, storage, runtime/compiler integration, compatibility — as a numbered proposal under
docs/modules/skeep/, coordinated through askeeptracking issue.
Find a task (every one names the file to copy from and the exact Gradle task to run):
- 🟣 All open good first issues
- ⏱️ Under an hour · a few hours
- 🧠 By what you already know, no SKaiNET knowledge assumed: Kotlin · PyTorch / NumPy, no Kotlin · Android · iOS · JS / Wasm · Kotlin/Native · writing docs
- 🗺️ The big picture: open DARC features · open SKEEP proposals
Claim it: comment on the sub-issue; a maintainer assigns it. Branch from develop, keep the PR to that one sub-issue, link it with Closes #NNN.
Read more: Getting started as a contributor · Issue taxonomy (labels & title prefixes) · Worked example: F1Score via DARC · a live example feature: #1222
Questions? Ask right here in the comments.
- 主要语言
- 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
-
bugbane/qf good first issue
难度 2/5 1-3 小时 新手友好度 64/100
osservatorionessuno/bugbane#173 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
Bayern feature:Application ready web
难度 2/5 1-3 小时 新手友好度 67/100
digitalfabrik/entitlementcard#3176 ·
维护者通常 7 天内回复
-
bug need-device
难度 2/5 1-3 小时 新手友好度 64/100
ramesh130/superplayer#495 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
maxrave-dev/SimpMusic#2649 ·
维护者通常 2 天内回复