notes: docs/contributor/contributing

This data as json

path title type status classification words body
docs/contributor/contributing Contributing to KSKB: proposals, corrections, comments, attribution reference v0.1.1 — 2026-10-21: the licenses set (ADR 0004); was: v0.1 — the path as designed; opens to outside contributors when the curator decides (phase 6) partner 533 # Contributing to KSKB > Contributor set. KSKB is one person's curated record of the KERI Suite and its community, and it improves fastest when the people who build the suite correct it. This page is the whole agreement: what a contribution is, how it travels, and how it is credited. ## What is welcome - A correction: a version, a date, a name, an attribution, a quotation that is not exact. - A missing resource: a site, repository, paper, course, or event that belongs in the register. - A note on a specification, an implementation, a meeting, or an event, written in the community's terms with its evidence labeled. - A comment on a note: what is wrong, what is missing, what has changed. What is not: marketing copy, a company's description of itself as fact, anything about a person beyond their public role, and anything Mark cannot verify against a source you name. ## How it travels 1. **Open an issue or a pull request on the export repository** (`kerisuite-kb`, the shared repository for the core group, once it is shared with you; `ks-corpus` is the private export that ADE's tools read). A pull request may touch only `inbound/`; a guard blocks anything else, because the repository is rebuilt from the vault and an edit elsewhere would be destroyed on the next sync. 2. **Name the file in `inbound/<your-name>/YYYY-MM-DD-<what>.md`** with a header: target (the file it corrects or the folder it adds to), change (one sentence), sources (URLs or documents), and what you could not verify. 3. **Mark reviews it against the governing documents** (the specifications, the synthesis, the register) and applies what survives to the vault, with a dated line saying what changed and who proposed it. A merge on the export repository means received, not adopted. 4. **The next sync carries the result.** Your inbound file stays in the repository as the record of the proposal. ## Attribution A contribution that lands is credited in the note it changed ("corrected 2026-10-02 on a proposal by <name>") and in the register's note field for a new resource. The vault's history keeps the proposal file. No contributor is quoted or named beyond what they wrote in the proposal. ## Corrections to the record A correction replaces the wrong statement and leaves a dated trace: "was: v1.1; corrected to v1.0 on 2026-09-15 against the ToIP approval record." A note is never silently rewritten, and a superseded claim is not deleted from a transcript; the note that cites it is corrected. ## Comments Until the site exists, a comment is an issue on the export repository or a message to Mark. Comments are not published; what they change is. ## What you agree to By contributing you license your text under the same terms as the repository, set on 21 October 2026 ([[300-Research/310-KERISuite/decisions/0004-2026-10-21-licenses-and-no-lock-in|ADR 0004]]): the Apache License 2.0 for code and the Creative Commons Attribution 4.0 license (CC BY 4.0) for text, Apache 2.0 being the license of the community's own repositories and CC BY 4.0 the content license Trust over IP's working groups list. You confirm it is yours to give, and you accept that Mark edits it into the record's voice.

Links from other tables