Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Ground truth: numcrux transfer/donation (governance decision)

Abierto
  • ¿Algo no está bien?
#987 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
kotlin, python, pytorch
Área
data, machine-learning

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Kotlin
Estrellas
52
Forks
15
Merge medio
1 d 15 h
PR fusionados (30 d)
36

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de SKaiNET-developers/SKaiNET

Todos los issues de SKaiNET-developers/SKaiNET

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.