Skip to content

feat(trg-11): add Generative AI usage guidelines - #1569

Open
mgarciaLKS wants to merge 3 commits into
mainfrom
feat/trg-11-generative-ai
Open

feat(trg-11): add Generative AI usage guidelines#1569
mgarciaLKS wants to merge 3 commits into
mainfrom
feat/trg-11-generative-ai

Conversation

@mgarciaLKS

Copy link
Copy Markdown
Contributor

Add TRG 11 - Generative AI with two sub-TRGs:

  • TRG 11.01: Generative AI Usage Guidelines (disclosure requirements, CC0-1.0 + Apache-2.0 dual licensing, Assisted-by commit footer, file header template, committer responsibilities)
  • TRG 11.02: AI_POLICY.md Requirements (what repositories must include, full AI_POLICY.md template with quality requirements and restrictions)

Register TRG 11 in sidebars.js for website navigation.

Based on Eclipse Foundation Generative AI Usage Guidelines: https://www.eclipse.org/projects/handbook/#genai

Assisted-by: GitHub Copilot (Claude Sonnet 4.6)

Description

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

Add TRG 11 - Generative AI with two sub-TRGs:
- TRG 11.01: Generative AI Usage Guidelines (disclosure requirements,
  CC0-1.0 + Apache-2.0 dual licensing, Assisted-by commit footer,
  file header template, committer responsibilities)
- TRG 11.02: AI_POLICY.md Requirements (what repositories must include,
  full AI_POLICY.md template with quality requirements and restrictions)

Register TRG 11 in sidebars.js for website navigation.

Based on Eclipse Foundation Generative AI Usage Guidelines:
https://www.eclipse.org/projects/handbook/#genai

Assisted-by: GitHub Copilot (Claude Sonnet 4.6)
- Add language specifier (text/markdown) to all fenced code blocks
  in trg-11-01.md and trg-11-02.md (MD040)
- Add blank lines around fenced code block inside list item
  in trg-11-02.md (MD031)
…sion

The markdown template block contained an inner ```text fence that
was prematurely closing the outer ```markdown fence (MD031/MD040 at
line 101). Switching to a 4-backtick outer fence prevents the inner
3-backtick fences from closing it.
@matbmoser

Copy link
Copy Markdown
Contributor

Great contribution @mgarciaLKS !!! I will review it.

# License for the specific language governing permissions and limitations
# under the License.
#
# AI Disclosure: This file was [minimally | largely | entirely] AI-generated.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Isn't this section redundant to the assisted-by clause. I think, we need more than just a new TRG, e.g. We have the statement:

# This program and the accompanying materials are made available under the
# terms of the Apache License, Version 2.0 which is available at
# https://www.apache.org/licenses/LICENSE-2.0.

above, which could be extended to state, that for AI generated stuff, the CC0-1.0 applies. But we should also include this into the other main files, where we state Apache-2.0 and CC-BY-4.0 as project licenses. Then the AI-Generated-By section becomes obsolete.

One problem is, that it is difficult to tell, which license applies to which part of the file, as a reader cannot distinguish between human and ai creation. The options entirely and potentially also largely suggest, that the file is completely under CC0-1.0, whereas minimally suggest mainly Apache-2.0.

Since we run into devils kitchen, I suggest, that we do not exceed the requirements from the Eclipse Foundation and do not get creative at this stage.

################################################################################
# Eclipse Tractus-X - <Repository Name>
#
# Copyright (c) 2026 Contributors to the Eclipse Foundation

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please not "Contributors to the Eclipse Foundation" in examples. Just use

Suggested change
# Copyright (c) 2026 Contributors to the Eclipse Foundation
# Copyright (c) 2026 <Intellectual property owner of content>

or something similar

5. **Restrictions** — any content types or areas where AI assistance is discouraged or prohibited (e.g., cryptographic implementations, security-sensitive code).
6. **Review process** — how AI-generated contributions are reviewed and what the merge criteria are.

### Template

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We should decide on two fixed versions of the file, one for usage with AI and one without AI, I doubt, that it brings much benefit to let everyone formulate a file on themselves.

@github-project-automation github-project-automation Bot moved this from Inbox to Todo in Tractus-X Webpage Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

3 participants