From bb7f5ce4532d00f50b09e2b7c0dd1d51b86dfe85 Mon Sep 17 00:00:00 2001 From: Denis Chevalier Date: Tue, 11 Aug 2026 01:07:27 +0200 Subject: Add CODE-OF-CONDUCT.md --- CODE-OF-CONDUCT.md | 81 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+) create mode 100644 CODE-OF-CONDUCT.md (limited to 'CODE-OF-CONDUCT.md') diff --git a/CODE-OF-CONDUCT.md b/CODE-OF-CONDUCT.md new file mode 100644 index 0000000..4163341 --- /dev/null +++ b/CODE-OF-CONDUCT.md @@ -0,0 +1,81 @@ +# Code of Conduct + +The **SAME Analog Modular Ecosystem** is a metrology-grade engineering project. +We exist to build precise, open, and mathematically verifiable hardware +architectures. + +We prioritize technical truth, physical accuracy, and engineering excellence +above consensus-seeking or politeness. This Code of Conduct outlines the +boundaries of participation in this repository. + +## 1. Technical Debate & The Standard of Rigor + +We encourage fierce, direct, and uncompromising technical debate. + +* **Thick Skin Required:** If your proposed circuit topology has a flaw, if + your math is wrong, or if your code breaks an assertion metrology check, + expect to be told so directly, bluntly, and without sugarcoating. +* **Critique the Engineering, Not the Person:** Vigorous critique of designs, + mathematics, schematics, and Typst code is standard operating procedure. + Calling a flawed technical design "terrible" or "broken" is valid technical + feedback. Personal insults, ad hominem attacks, and identity-based + disparagement are not. +* **Meritocracy of Evidence:** Arguments are settled by physics, mathematical + proof, datasheets, and compiled assertions — not by reputation, authority, or + emotional appeal. + +## 2. Hard Boundaries (Zero Tolerance) + +While technical debate can be rough, the following two boundaries are absolute. +Violation of either will result in immediate moderation action. + +### A. Strictly No Off-Topic Discussion + +This repository is exclusively for the engineering, metrology, software tooling, +and specification of the SAME Analog Modular Ecosystem. + +* **Keep it strictly about SAME:** Discussions regarding national politics, + culture wars, social commentary, or unrelated tech drama are **strictly + prohibited**. +* **Zero Warning Cleanup:** Any pull request, issue, or discussion thread that + strays into non-SAME topics will be locked and deleted immediately without + debate. + +### B. No Discrimination or Hate Speech + +Discrimination, bigotry, and targeted harassment will not be tolerated under any +circumstances. + +* **Zero Tolerance:** Hate speech, slur usage, or discrimination based on race, + ethnicity, gender identity, sexual orientation, religion, disability, or + nationality is strictly banned. +* **Immediate Action:** Attacks on an individual's personal identity (as opposed + to their technical work) will result in an immediate and permanent ban from + the organization. + +### C. A Non-Negotiable Copyleft Identity + +The SAME project is fundamentally built on strong copyleft principles to +guarantee open access, repairability, and technological sovereignty forever. + +* **The Licenses are Settled:** The project's [licensing model](LICENSE.md) is + non-negotiable. +* **No Re-licensing Debates:** Issues, pull requests, or forum threads + questioning the copyleft identity, arguing for permissive licenses (MIT, + Apache, BSD, etc.), or re-opening licensing debates will be closed immediately + without discussion. + +## 3. Scope & Enforcement + +This Code of Conduct applies to all spaces managed by the SAME project (git +repository, issue trackers, pull requests, and official communication channels). + +Project maintainers reserve the right to: + +1. Instantly delete off-topic or non-engineering discussions. +2. Permanently ban participants who violate the anti-discrimination policy. +3. Reject contributions that rely on unverified claims rather than physical or + mathematical proof. + +If you observe a violation of the hard boundaries (hate speech or harassment), + report it directly to [Denis Chevalier](mailto:perso@denischevalier.fr). -- cgit