ObliviOS Developer portal Project site

Home / Decisions / ADR-264

Settle the open choices before the flip and prepare the four repositories.

Accepted, recorded 18 November 2026.

Decision
ADR-264
Date
2026-11-18
Status
AcceptedAccepted (owner, 2026-11-18: yes for the contact, \"do what is smartest and best\" for the code of conduct, \"I do not think so\" for the legal notice, \"go ahead\" for the export position, and \"do what you can right away\" for the rest).
Mentions
ADR-261

1Decision

Settle the open choices before the flip and prepare the four repositories. (1) The Gmail address stays the security contact (O-6); no forwarding address is set up.

(2) A short code of conduct and one Markdown issue template (with a contact link to the Security page of the site) are added to all four repositories, and a CONTRIBUTING.md to manifest and docs; the docs files come from tools/docs/community/ through build-public-docs.py, the code repositories carry copies. (3) No legal notice on the sites (B-4).

(4) The export-control position of the published cryptographic source (B-5) is assessed by the agent, with its sources and limits in the licensing review. (5) The four READMEs open with the logo (a picture element that names the light and dark lockup of oblivios.org) and a link to the site. (6) The GitHub settings of R-3 are applied: description, homepage https://oblivios.org, five topics, wiki and projects off, Dependabot alerts on.

2Why and evidence

A reader who finds a problem needs one place to say so, one rule for how to behave, and one contact; the contact already works. The code of conduct is the shortest text that states what the maintainer will do. The export position is a risk that the owner can accept only when it is written down with its sources.

Rejected: a security@oblivios.org forwarder (it needs mail records and a received test message before it is trusted); the Contributor Covenant text (it needs attribution and says more than this project can run); YAML issue forms (a Markdown template needs no schema); private vulnerability reporting (a third channel beside the issue and the e-mail of ADR-261); a legal notice (no source was found that says Dutch law requires one for this site, but none was searched for [assumption]).

3Consequences

Done and read on 2026-11-18: platform c1ff1d7, services 1110f95 and manifest 0cfaafa (each the second of two commits) hold the files and the READMEs; R-3 read back with gh api for all four repositories; the external links of the READMEs and the site checked (19, nine answer, nine are the private repositories, one is a 403 to a script); the US rule read in the eCFR, the Wassenaar and EU text only through search snippets.

Not done: a rendering of the READMEs on GitHub (the repositories are private); a received test message at the contact; whether Dutch law requires a legal notice; the export position of the object code of the three prebuilt files, the full text of EU Annex I and a read by counsel or the Dutch authority; the terms of Anthropic for the logo.

4Review when

A lawyer or the authority finds a control that applies; a contributor asks to send pull requests; the owner wants a forwarding address or a legal notice.

Read from docs/governance/decision-log.md, entry ADR-264.