Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Ground truth: numcrux transfer/donation (governance decision)

Aperta
  • Qualcosa non va?
#987 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
kotlin, python, pytorch
Ambito
data, machine-learning

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

question sub-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 the numcrux org
    outright, or does numcrux start a fresh corpus and skainet-ground-truth stays as
    SKaiNET's own (possibly narrower, possibly diverging) fixture set?
  • If transferred: does gradienttracer (the execution/serialization engine) move too,
    or stay under SKaiNET-developers as 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
    using skainet-ground-truth as 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.

Lingua principale
Kotlin
Stelle
52
Fork
15
Merge medio
1g 15h
PR unite (30g)
36

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di SKaiNET-developers/SKaiNET

Tutte le issue di SKaiNET-developers/SKaiNET

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.