Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Ground truth: numcrux transfer/donation (governance decision)

Ouverte
  • Quelque chose ne va pas ?
#987 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Calme
Stack technique
kotlin, python, pytorch
Domaine
data, machine-learning

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Kotlin
Étoiles
52
Forks
15
Merge moyen
1 j 2 h
PR mergées (30 j)
63

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de SKaiNET-developers/SKaiNET

Toutes les issues de SKaiNET-developers/SKaiNET

Issues similaires

Plus d'issues Kotlin

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.