Skip to content

docs(contributing): retire mandatory DCO sign-off #418

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
masarray merged 1 commit into from
Sep 26, 2026
Merged

docs(contributing): retire mandatory DCO sign-off #418

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/pull_request_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ For UI changes, include:
- [ ] No proprietary source, documentation wording, tests, UI, screenshots, or restricted engineering material was copied.
- [ ] Third-party components and licenses are identified.
- [ ] Public license, commercial-license, and trademark wording remains accurate.
- [ ] Commits include the required DCO sign-off.
- [ ] I have read and affirmatively agree to the [Contributor License Agreement](../CONTRIBUTOR-LICENSE-AGREEMENT.md) for this contribution, and I have the rights and any required authorization to submit it.

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 26, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use a working CLA URL in generated PR bodies

When this template is used to create a pull request, the Markdown is rendered at /masarray/arsas/pull/<number>, where ../CONTRIBUTOR-LICENSE-AGREEMENT.md resolves to /masarray/arsas/CONTRIBUTOR-LICENSE-AGREEMENT.md rather than the repository file under /blob/<branch>/. The agreement checkbox therefore sends contributors to a missing page precisely when they need to review the now-required CLA; use a repository-root URL containing /blob/main/ (or a full permanent URL) instead. This matters because the repository explicitly makes the PR template part of its validation workflow.

AGENTS.md reference: AGENTS.md:L227-L227

Useful? React with 👍 / 👎.


## Independent implementation and provenance

Expand Down
10 changes: 3 additions & 7 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ A pull request should:
- use synthetic, public-domain, or contributor-owned test data;
- update public documentation when behavior, maturity, safety, or claim boundaries change;
- preserve the GPL community license and separate commercial-licensing wording;
- include a signed-off commit as required by the project DCO.
- document contribution authorship, origin, and required third-party rights; a DCO commit sign-off is not required.

For UI changes, include the tested Windows scaling level, resolution, keyboard workflow, and any accessibility impact. For protocol, reporting, GOOSE, SMV, file-transfer, SCL, or control changes, state whether validation used unit tests, deterministic fixtures, loopback, simulator, or an authorized laboratory IED.

Expand All @@ -72,16 +72,12 @@ For UI changes, include the tested Windows scaling level, resolution, keyboard w
The current public project is distributed under `GPL-3.0-or-later` and maintains a separate commercial-licensing path. Before merge, contributors must:

- read and affirmatively agree to [CONTRIBUTOR-LICENSE-AGREEMENT.md](CONTRIBUTOR-LICENSE-AGREEMENT.md);
- sign off every commit under [DCO.txt](DCO.txt);
- retain accurate Git authorship and document contribution provenance in the pull request;
- have the legal right and any required employer authorization to contribute;
- avoid confidential, proprietary, restricted, customer-owned, or security-sensitive material;
- identify any third-party component and its license before introducing it.

Example sign-off:

```text
Signed-off-by: Contributor Name <contributor@example.com>
```
ARSAS does not request or require DCO `Signed-off-by` trailers on new commits. [DCO.txt](DCO.txt) and sign-offs in existing Git history are retained as historical records, not active merge requirements. CLA agreement and source/provenance review remain required.

## Clean-room and data provenance

Expand Down
2 changes: 1 addition & 1 deletion docs/LICENSING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ ArIED links directly to ARIEC61850. A distributed combined build must use mutual

## Contributions and branding

New contributions require DCO sign-off and agreement to [CONTRIBUTOR-LICENSE-AGREEMENT.md](../CONTRIBUTOR-LICENSE-AGREEMENT.md). Branding is governed separately by [TRADEMARK.md](../TRADEMARK.md).
New contributions require affirmative agreement to [CONTRIBUTOR-LICENSE-AGREEMENT.md](../CONTRIBUTOR-LICENSE-AGREEMENT.md), accurate authorship and provenance, and review of any third-party rights. DCO commit sign-off is not required for new contributions; existing sign-offs remain part of Git history. Branding is governed separately by [TRADEMARK.md](../TRADEMARK.md).

## Ownership boundary

Expand Down
Loading