{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidqnpgwwbknvt33naze5bkzpacvipeqi4igjpfgsc4rwbellfsn64",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mooshxkdchv2"
  },
  "path": "/t/c-inf-soft-sparsity-engine-maths-and-code-from-1972/176964#post_3",
  "publishedAt": "2026-06-20T01:23:02.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "(click for more details)"
  ],
  "textContent": "Hmm… I’m not the right person to judge the math, but if the question is where to publish what in and around Hugging Face, my rough map would be something like this:\n\n* * *\n\n**Very short version:** for historical maths + Fortran code, I would probably use **GitHub as the primary home**.\n\nThen:\n\n  * **GitHub** — code, notes, examples, license, citation file, releases\n  * **Zenodo / DOI** — stable citable archive\n  * **HF Dataset repo** — sample inputs/outputs, reproduced results, benchmark files, toy matrices, reproducibility package\n  * **HF Space** — interactive demo people can try in the browser\n  * **HF Model repo + Model Card** — only if there is a model-like artifact, such as weights, adapter weights, tokenizer/config files, or a reusable ML component\n  * **HF Storage Bucket** — large mutable files, logs, checkpoints, intermediate artifacts, not the main explanation page\n\n\n\nSo for this case, my default route would be:\n\n  1. **GitHub first**\n  2. Add **CITATION.cff** , license, examples, and release notes\n  3. Archive a release with **Zenodo** or another DOI path\n  4. Optionally add an **HF Dataset repo** for reproducibility files\n  5. Optionally add an **HF Space** if there is a small runnable demo\n  6. Use an **HF Model repo** only if the work becomes something model-like or loadable in an ML workflow\n\n\n\nOptional extra notes below, only in case they help.\n\nMore detailed map (click for more details) Why I would separate the homes (click for more details) Possible GitHub layout (click for more details) Possible README sections (click for more details) Possible one-line notes to prevent confusion (click for more details) Possible low-friction roadmap (click for more details)",
  "title": "C-inf soft sparsity engine maths and code from 1972"
}