Remove references to unrelated personal projects from OpenDKG policies

.github/ISSUE_TEMPLATE/membership-agreement.yml

@@ -11,12 +11,12 @@ body:
         **Only applications filed in [OpenDKG/.github](https://github.com/OpenDKG/.github/issues/new?template=membership-agreement.yml) are processed.** This template can also be visible as an organization default in other repositories; do not file there.
 
         **Read these pinned documents before checking any boxes:**
-        - [Contributor Agreement v1.0](https://github.com/OpenDKG/.github/blob/2e429d904db1059a678085792ad44f1d732d7ea1/CONTRIBUTOR_AGREEMENT.md)
-        - [Governance v1.0](https://github.com/OpenDKG/.github/blob/2e429d904db1059a678085792ad44f1d732d7ea1/GOVERNANCE.md)
-        - [Contribution guidelines v1.0](https://github.com/OpenDKG/.github/blob/2e429d904db1059a678085792ad44f1d732d7ea1/CONTRIBUTING.md)
-        - [Developer Certificate of Origin](https://github.com/OpenDKG/.github/blob/2e429d904db1059a678085792ad44f1d732d7ea1/DCO.md)
+        - [Contributor Agreement v1.0](https://github.com/OpenDKG/.github/blob/d56279b4f3c25dd8f9e68699d61be23a0c7a6b07/CONTRIBUTOR_AGREEMENT.md)
+        - [Governance v1.0](https://github.com/OpenDKG/.github/blob/d56279b4f3c25dd8f9e68699d61be23a0c7a6b07/GOVERNANCE.md)
+        - [Contribution guidelines v1.0](https://github.com/OpenDKG/.github/blob/d56279b4f3c25dd8f9e68699d61be23a0c7a6b07/CONTRIBUTING.md)
+        - [Developer Certificate of Origin](https://github.com/OpenDKG/.github/blob/d56279b4f3c25dd8f9e68699d61be23a0c7a6b07/DCO.md)
 
-        **Exact agreement revision:** `2e429d904db1059a678085792ad44f1d732d7ea1`. The forms refer to this specific version, not to future changes. NetPetra is excluded from all coverage.
+        **Exact agreement revision:** `d56279b4f3c25dd8f9e68699d61be23a0c7a6b07`. The forms refer to this specific version, not to future changes.
 
         These terms are a **proposal until the three original equal cofounders each personally adopt them**. Do not use this form to grant membership until adoption is confirmed. Filing this public issue is not an automatic invitation, a qualified electronic signature, or proof of civil identity.
 
@@ -44,14 +44,14 @@ body:
     attributes:
       label: "Contributor Agreement v1.0 — explicit acceptance"
       options:
-        - label: "I have read and affirmatively accept OpenDKG Contributor Agreement v1.0 at commit 2e429d904db1059a678085792ad44f1d732d7ea1 for my authorized contributions to present and future Covered Repositories. NetPetra is excluded. I understand that existing valid outbound open-source licenses remain effective if I leave."
+        - label: "I have read and affirmatively accept OpenDKG Contributor Agreement v1.0 at commit d56279b4f3c25dd8f9e68699d61be23a0c7a6b07 for my authorized contributions to present and future Covered Repositories. I understand that existing valid outbound open-source licenses remain effective if I leave."
           required: true
   - type: checkboxes
     id: governance-v1
     attributes:
       label: "Governance v1.0 — explicit acceptance"
       options:
-        - label: "I have read and accept OpenDKG Governance v1.0 at commit 2e429d904db1059a678085792ad44f1d732d7ea1 for my requested role, including contribution review, decision-making, access control, and departure."
+        - label: "I have read and accept OpenDKG Governance v1.0 at commit d56279b4f3c25dd8f9e68699d61be23a0c7a6b07 for my requested role, including contribution review, decision-making, access control, and departure."
           required: true
   - type: checkboxes
     id: contributing-dco-v1

.github/PULL_REQUEST_TEMPLATE.md

@@ -13,4 +13,4 @@
 
 **Prior acceptance issue or CLA Assistant confirmation (if available):** <!-- Link to a public record; never include private identity data. -->
 
-> **Note:** This checklist is not a legal signature or an automatic enforcement mechanism. The repository's CLA/DCO status checks and maintainer reviews determine merge eligibility. NetPetra is explicitly excluded from OpenDKG policies.
+> **Note:** This checklist is not a legal signature or an automatic enforcement mechanism. The repository's CLA/DCO status checks and maintainer reviews determine merge eligibility.

CLA_SETUP.md

@@ -11,8 +11,8 @@ The [CLA Assistant service](https://cla-assistant.io/) can prompt an external pu
 ## Configuration by a GitHub organization owner
 
 1. First have **all three equal original cofounders**, including current technical owner `@a-51-50`, personally confirm acceptance (outside members can comment before joining) and complete the **unanimous founding adoption** of the proposed [Contributor Agreement](CONTRIBUTOR_AGREEMENT.md) and [Governance](GOVERNANCE.md).
-2. Prepare the complete, unchanged effective **Contributor Agreement v1.0** as a public GitHub Gist linked to the adopted exact revision. Do not silently rewrite substantive terms. The reference OpenDKG agreement revision in this initial package is `2e429d904db1059a678085792ad44f1d732d7ea1`; if it changes before adoption, pin and review the actual adopted revision instead.
-3. Sign in at **https://cla-assistant.io/** with an authorized GitHub account. Link OpenDKG or each of its covered repositories to that Gist, and approve the requested GitHub authorization/installation as required by the service. Install/use it only for **OpenDKG covered repositories**, not NetPetra.
+2. Prepare the complete, unchanged effective **Contributor Agreement v1.0** as a public GitHub Gist linked to the adopted exact revision. Do not silently rewrite substantive terms. The reference OpenDKG agreement revision in this initial package is `d56279b4f3c25dd8f9e68699d61be23a0c7a6b07`; if it changes before adoption, pin and review the actual adopted revision instead.
+3. Sign in at **https://cla-assistant.io/** with an authorized GitHub account. Link OpenDKG or each of its covered repositories to that Gist, and approve the requested GitHub authorization/installation as required by the service. Install/use it only for **OpenDKG covered repositories**.
 4. Open a harmless test PR from a **different GitHub account that has not signed**. Check that the service requests explicit agreement and posts the expected pending/failing status. Sign once, verify it changes to success and that the recorded version matches the approved text. Confirm it does not silently exempt authors who should sign.
 5. In each covered repository, configure **Settings → Rules → Rulesets** (or Branch protection) to **require the CLA check** before merging into the protected branch. Select the actual check name shown by your test PR, not a guessed name. Require at least one independent review and restrict bypass permissions. GitHub Free supports branch protection for public repositories; review plan limitations for private repos.
 6. Repeat or automate repository **enrollment** for every existing and subsequently created OpenDKG project. A central `.github` repository alone **does not enforce CLA checks in other repositories**. Check each repository after setup.

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing to OpenDKG projects
 
-Welcome to OpenDKG. These contribution guidelines are the **organization default** for repositories owned by **[OpenDKG](https://github.com/OpenDKG)** now or created later, **excluding NetPetra**. A project may have additional documented requirements, and the repository's own `LICENSE` determines its outbound software license.
+Welcome to OpenDKG. These contribution guidelines are the **organization default** for repositories owned by **[OpenDKG](https://github.com/OpenDKG)** now or created later. A project may have additional documented requirements, and the repository's own `LICENSE` determines its outbound software license.
 
 **Default software license: Apache-2.0.** Each project must contain its **own** license file. Policies and the license in `OpenDKG/.github` do not automatically add a license to other repositories.
 
@@ -11,7 +11,7 @@ Read our [Contributor Agreement](https://github.com/OpenDKG/.github/blob/main/CO
 ## Before your first contribution
 
 1. Check the specific repository's `LICENSE`, `README`, third-party notices, and any special rules. If its license differs from Apache-2.0, obtain explicit permission to submit under the stated license.
-2. Explicitly accept the **current Contributor Agreement version** through an attributed GitHub acknowledgment referring to its exact commit SHA. One valid acceptance is intended to cover subsequent authorized contributions to current and future OpenDKG repositories, except NetPetra, until a material policy revision needs new acceptance. Acceptance is **not** automatic from joining an organization.
+2. Explicitly accept the **current Contributor Agreement version** through an attributed GitHub acknowledgment referring to its exact commit SHA. One valid acceptance is intended to cover subsequent authorized contributions to current and future OpenDKG repositories, until a material policy revision needs new acceptance. Acceptance is **not** automatic from joining an organization.
 3. Use a stable GitHub account/pseudonym and an email you control; check that any employer, client or coauthor rights have been cleared.
 4. Sign off each commit with the Developer Certificate of Origin: `git commit -s -m "Your change"`. This is separate from, and **does not replace**, the agreement acceptance. Use GPG/SSH signing additionally if your repository enforces verified cryptographic commits.
 5. Submit a PR; wait for independent maintainer review, required checks and licensing/provenance verification.

CONTRIBUTOR_AGREEMENT.md

@@ -10,8 +10,6 @@
 
 A **Covered Repository** is a repository *owned by the `OpenDKG` GitHub organization* when a contribution is intentionally submitted for inclusion, whether the repository exists now or is created in the future. This agreement is intended to govern contributions to **all current and future Covered Repositories** after a contributor's valid acceptance, without needing a new project-specific agreement for each new repository.
 
-**Express exclusion: NetPetra.** The NetPetra software/project and any repository principally dedicated to it are excluded, even if later transferred to the OpenDKG organization. Inclusion would require a separate, explicit written decision by the maintainers and permission from affected contributors; it is **not** automatic.
-
 The agreement does not govern repositories outside OpenDKG ownership, personal forks, outside employers' code, or material already licensed under other terms merely because it is subsequently copied or transferred into a Covered Repository. Transferring an existing repository to OpenDKG does not retroactively license its history. Each such repository requires an ownership, provenance and license review before inclusion.
 
 ## 2. Who is granting rights
@@ -51,7 +49,7 @@ Before their first contribution under this policy, the contributor must post an
 
 **Acceptance statement (copy and complete with actual values):**
 
-> I, the GitHub account signing this comment, affirmatively accept **OpenDKG Contributor Agreement v1.0**, at the exact revision linked in this comment, for my authorized contributions to **all current and future Covered Repositories owned by OpenDKG**, excluding **NetPetra**. I understand that valid outbound licenses I grant on accepted contributions cannot be revoked solely because I leave the team. I retain ownership of my original work. My previously submitted work is included **only** if I list the relevant commits or PRs here. Covered earlier work: **none / links**. Agreement revision (commit SHA): **[paste commit]**.
+> I, the GitHub account signing this comment, affirmatively accept **OpenDKG Contributor Agreement v1.0**, at the exact revision linked in this comment, for my authorized contributions to **all current and future Covered Repositories owned by OpenDKG**. I understand that valid outbound licenses I grant on accepted contributions cannot be revoked solely because I leave the team. I retain ownership of my original work. My previously submitted work is included **only** if I list the relevant commits or PRs here. Covered earlier work: **none / links**. Agreement revision (commit SHA): **[paste commit]**.
 
 A DCO `Signed-off-by` trailer is **not** acceptance of this separate agreement. Acceptance of a materially revised agreement requires a new explicit acknowledgment; changed terms cannot retroactively replace prior public licenses. The three original equal cofounders must each personally accept this agreement and record adoption of `GOVERNANCE.md` before the three-person council claims its collective rules are in force. Founding status is not decided by the order of GitHub invitations.
 

DCO.md

@@ -1,6 +1,6 @@
 # Developer Certificate of Origin (DCO)
 
-**For contributions to OpenDKG covered repositories (NetPetra excluded).** The following is the **verbatim Developer's Certificate of Origin 1.1** published by the Linux Foundation at https://developercertificate.org/. The DCO records a contributor's certification of their right to submit work; it is **not itself a copyright assignment, a standalone software license, or acceptance of `CONTRIBUTOR_AGREEMENT.md`**.
+**For contributions to OpenDKG covered repositories.** The following is the **verbatim Developer's Certificate of Origin 1.1** published by the Linux Foundation at https://developercertificate.org/. The DCO records a contributor's certification of their right to submit work; it is **not itself a copyright assignment, a standalone software license, or acceptance of `CONTRIBUTOR_AGREEMENT.md`**.
 
 ## Official DCO 1.1 text (unaltered)
 

FOUNDER_ONBOARDING.md

@@ -12,13 +12,11 @@ OpenDKG is intended as a project **cofounded from the outset by three equal indi
 
 These are **three equal founding seats**. Who created the GitHub account first does not confer additional votes, project copyright, founders' ownership rights, or permanent control. The other original cofounders are not ordinary later-stage applicants merely because their GitHub invitations have not yet been sent. However, **do not claim that anyone is contractually bound until they personally accept** the relevant agreement.
 
-**Exact proposed Governance and Contributor Agreement revision for acceptance:** `2e429d904db1059a678085792ad44f1d732d7ea1`. The underlying documents remain v1.0 proposals and were clarified before any of the three original cofounders had accepted. An outdated revision is not adequate consent to this clarified version.
-
-**NetPetra is explicitly excluded**, even if it later moves into OpenDKG.
+**Exact proposed Governance and Contributor Agreement revision for acceptance:** `d56279b4f3c25dd8f9e68699d61be23a0c7a6b07`. The underlying documents remain v1.0 proposals and were clarified before any of the three original cofounders had accepted. An outdated revision is not adequate consent to this clarified version.
 
 ## How each of the three accepts (including the initial technical Owner)
 
-1. Read [Contributor Agreement v1.0 at the pinned revision](https://github.com/OpenDKG/.github/blob/2e429d904db1059a678085792ad44f1d732d7ea1/CONTRIBUTOR_AGREEMENT.md) and [Governance v1.0 at the same revision](https://github.com/OpenDKG/.github/blob/2e429d904db1059a678085792ad44f1d732d7ea1/GOVERNANCE.md).
+1. Read [Contributor Agreement v1.0 at the pinned revision](https://github.com/OpenDKG/.github/blob/d56279b4f3c25dd8f9e68699d61be23a0c7a6b07/CONTRIBUTOR_AGREEMENT.md) and [Governance v1.0 at the same revision](https://github.com/OpenDKG/.github/blob/d56279b4f3c25dd8f9e68699d61be23a0c7a6b07/GOVERNANCE.md).
 2. Each of the original three individually opens [founding acceptance Issue #3](https://github.com/OpenDKG/.github/issues/3) **from their own GitHub account**. You can comment **without being an organization member** because the repository is public.
 3. Each personally posts the declaration provided in Issue #3 after actually reading the documents. No owner, agent or bot may post acceptance for another person. A GitHub comment is evidence of an attributable public action, not verified civil identity or a qualified electronic signature.
 4. The current GitHub Owner checks that exactly three **different original-cofounder accounts** submitted explicit acceptance of the **same pinned revision**. Record three comment permalinks in the issue and only then mark the full founding council as formed. If the text changes substantially, collect agreement to the final version again.

GOVERNANCE.md

@@ -1,7 +1,7 @@
 # OpenDKG Governance
 
 **Version:** 1.0 — proposed for adoption  
-**Scope:** OpenDKG GitHub organization and its current and future organization-owned projects, **excluding NetPetra**.
+**Scope:** OpenDKG GitHub organization and its current and future organization-owned projects.
 
 > OpenDKG is presently treated here as an **informal collaboration of individuals**, not a registered company, employer, partnership, or separate legal person. This document sets voluntary operating rules; it does not determine ownership of a personal domain, trademark, bank account, wallet, signing certificate or other asset. It cannot override GitHub's technical permissions or applicable law.
 
@@ -48,7 +48,6 @@ With two remaining active maintainers, require both for official releases and ir
 ## 3. Projects and license rules
 
 - **Coverage:** All repositories owned by `github.com/OpenDKG` now or in the future, subject to a repository-specific written exception.
-- **Permanent named exclusion:** **NetPetra** remains out of scope even if subsequently moved to this organization, until a separately documented agreement expressly includes it and rights-holders consent as needed.
 - **Default outbound software license:** Apache License 2.0; place an actual `LICENSE` in **each** repository. `OpenDKG/.github/LICENSE` does not license other repositories.
 - If a repository uses another license, disclose it clearly **before** accepting contributions and obtain contributor approval for that repository's license. Existing third-party/copyleft or previously licensed material is not automatically relicensed by organizational policy.
 - A newly transferred repository requires a provenance and governance review; this policy cannot retroactively bind its former contributors.