|
| 1 | +<!-- SPDX-License-Identifier: MPL-2.0 --> |
| 2 | +<!-- SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell --> |
| 3 | + |
| 4 | +# Contributing to technical-notes |
| 5 | + |
| 6 | +Thanks for your interest. This repository follows the Hyperpolymath estate |
| 7 | +standards defined in [hyperpolymath/standards](https://github.com/hyperpolymath/standards). |
| 8 | + |
| 9 | +## Licence |
| 10 | + |
| 11 | +This project is licensed under **MPL-2.0**. By contributing you agree that |
| 12 | +your contributions are licensed under the same terms. Every source file |
| 13 | +carries an `SPDX-License-Identifier` header; keep it when editing, and add |
| 14 | +one to any new file. |
| 15 | + |
| 16 | +## Development environment |
| 17 | + |
| 18 | +A pinned dev shell is provided: |
| 19 | + |
| 20 | +```sh |
| 21 | +nix develop # toolchain: git |
| 22 | +``` |
| 23 | + |
| 24 | +Estate policy is Guix primary / Nix fallback; this repo currently ships the |
| 25 | +Nix fallback. A `guix.scm` is welcome if you prefer the primary tier. |
| 26 | + |
| 27 | +## Language policy |
| 28 | + |
| 29 | +The estate restricts which languages may be used. In particular Python, Go, |
| 30 | +TypeScript, ReScript, V-lang, Java/Kotlin, Swift and Makefiles are **not** |
| 31 | +accepted in new code; AffineScript, Rust/SPARK, Zig, Deno, Gleam, Elixir, |
| 32 | +Haskell, Idris2, Agda, Julia and OCaml are. CI enforces this, so check the |
| 33 | +policy in `hyperpolymath/standards` before introducing a new language. |
| 34 | + |
| 35 | +## Documentation format |
| 36 | + |
| 37 | +Docs are AsciiDoc (`.adoc`) by default, including `README.adoc`. The |
| 38 | +GitHub-required community-health files stay Markdown: `SECURITY.md`, |
| 39 | +`CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, `CHANGELOG.md`. Do not add a `.md` |
| 40 | +duplicate of a doc that already exists as `.adoc`. |
| 41 | + |
| 42 | +## Pull requests |
| 43 | + |
| 44 | +1. Branch from `main` — do not push to `main` directly; branch protection |
| 45 | + requires review and passing checks. |
| 46 | +2. Keep the change focused, and explain *why* in the PR body. |
| 47 | +3. Make sure governance CI is green. It checks documentation presence, |
| 48 | + packaging policy, secrets, licence consistency and workflow security. |
| 49 | +4. Security issues: follow `SECURITY.md` — report privately, never in a |
| 50 | + public issue. |
0 commit comments