7
31
Fork
You've already forked blackmagic
23

Add the Zig's NoAI policy to our Code of Conduct. #2268

Merged
freyjadomville merged 1 commit from add-no-ai-to-coc into main 2026年06月16日 13:11:51 +02:00
Owner
Copy link

Detailed description

This is a proposal for adding the Zig programming language version of the NoAI section to our Code of Conduct. This text aligns very much with our view on AI/LLM use. We wanted to be more explicit about how we develop Black Magic Debug going forward.

Your checklist for this pull request

Closing issues

<!-- Filling this template is mandatory --> ## Detailed description This is a proposal for adding the Zig programming language version of the NoAI section to our Code of Conduct. This text aligns very much with our view on AI/LLM use. We wanted to be more explicit about how we develop Black Magic Debug going forward. <!-- Explain the **details** for making this change. * Is a new feature implemented? * What existing problem(s) does the pull request solve? * How does the pull request solve these problems? Please provide enough information so that others can review your pull request. Information embedded in the description part of the commits doesn't count. --> ## Your checklist for this pull request * [x] I've read the [Code of Conduct](https://codeberg.org/blackmagic-debug/blackmagic/src/CODE_OF_CONDUCT.md) * [x] I've read the [guidelines for contributing](https://codeberg.org/blackmagic-debug/blackmagic/src/CONTRIBUTING.md) to this repository * [x] It builds for hardware native (see [Building the firmware](https://codeberg.org/blackmagic-debug/blackmagic?tab=readme-ov-file#building-the-firmware)) * [x] It builds as BMDA (see [Building the BMDA](https://codeberg.org/blackmagic-debug/blackmagic?tab=readme-ov-file#building-black-magic-debug-app)) * [x] I've tested it to the best of my ability * [x] My commit messages provide a useful short description of what the commits do ## Closing issues <!-- put "fixes #XXXX" here to auto-close the issue(s) that your PR fixes (if any). -->
Add the Zig's NoAI policy to our Code of Conduct.
Some checks failed
ci/woodpecker/pr/build-firmware/5 Pipeline was successful
ci/woodpecker/pr/build-firmware/4 Pipeline was successful
ci/woodpecker/pr/build-firmware/1 Pipeline was successful
ci/woodpecker/pr/build-firmware/2 Pipeline was successful
ci/woodpecker/pr/build-firmware/3 Pipeline was successful
ci/woodpecker/pr/build-firmware/6 Pipeline was successful
ci/woodpecker/pr/build-firmware/7 Pipeline was successful
ci/woodpecker/pr/build-firmware/8 Pipeline failed
ci/woodpecker/pr/build-firmware/10 Pipeline was successful
ci/woodpecker/pr/build-firmware/9 Pipeline was successful
ci/woodpecker/pr/build-firmware/11 Pipeline was successful
ci/woodpecker/pr/build-firmware/13 Pipeline failed
ci/woodpecker/pr/build-firmware/12 Pipeline was successful
ci/woodpecker/pr/build-firmware/15 Pipeline was successful
ci/woodpecker/pr/build-firmware/14 Pipeline was successful
ci/woodpecker/pr/build-firmware/16 Pipeline was successful
ci/woodpecker/pr/build-linux/1 Pipeline was successful
ci/woodpecker/pr/build-firmware/18 Pipeline was successful
ci/woodpecker/pr/build-firmware/17 Pipeline was successful
ci/woodpecker/pr/build-firmware/19 Pipeline was successful
ci/woodpecker/pr/build-firmware/20 Pipeline was successful
ci/woodpecker/pr/build-linux/2 Pipeline was successful
ci/woodpecker/pr/build-windows Pipeline was successful
ci/woodpecker/pr/lint Pipeline was successful
d2a63f250e
dragonmux requested changes 2026年06月14日 04:50:10 +02:00
Dismissed
dragonmux left a comment
Copy link

Only the one change we can see to suggest, otherwise this looks good to us and we'd be happy to merge it and promulgate it to the other project repos.

Only the one change we can see to suggest, otherwise this looks good to us and we'd be happy to merge it and promulgate it to the other project repos.
@ -128,3 +146,4 @@ For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at
https://www.contributor-covenant.org/translations.
We incorporated the AI policy from the Zig [language CoC](https://ziglang.org/code-of-conduct/#strict-no-llm-no-ai-policy)

We suggest including the word Zig in the link text as it's the "Zig lanuage", not the "Zig language" (if you catch the way we see that separating the words and how that seems odd.)

We suggest including the word `Zig` in the link text as it's the "`Zig lanuage`", not the "Zig `language`" (if you catch the way we see that separating the words and how that seems odd.)
Author
Owner
Copy link

Good point. Corrected that.

Good point. Corrected that.
esden marked this conversation as resolved
esden force-pushed add-no-ai-to-coc from d2a63f250e
Some checks failed
ci/woodpecker/pr/build-firmware/5 Pipeline was successful
ci/woodpecker/pr/build-firmware/4 Pipeline was successful
ci/woodpecker/pr/build-firmware/1 Pipeline was successful
ci/woodpecker/pr/build-firmware/2 Pipeline was successful
ci/woodpecker/pr/build-firmware/3 Pipeline was successful
ci/woodpecker/pr/build-firmware/6 Pipeline was successful
ci/woodpecker/pr/build-firmware/7 Pipeline was successful
ci/woodpecker/pr/build-firmware/8 Pipeline failed
ci/woodpecker/pr/build-firmware/10 Pipeline was successful
ci/woodpecker/pr/build-firmware/9 Pipeline was successful
ci/woodpecker/pr/build-firmware/11 Pipeline was successful
ci/woodpecker/pr/build-firmware/13 Pipeline failed
ci/woodpecker/pr/build-firmware/12 Pipeline was successful
ci/woodpecker/pr/build-firmware/15 Pipeline was successful
ci/woodpecker/pr/build-firmware/14 Pipeline was successful
ci/woodpecker/pr/build-firmware/16 Pipeline was successful
ci/woodpecker/pr/build-linux/1 Pipeline was successful
ci/woodpecker/pr/build-firmware/18 Pipeline was successful
ci/woodpecker/pr/build-firmware/17 Pipeline was successful
ci/woodpecker/pr/build-firmware/19 Pipeline was successful
ci/woodpecker/pr/build-firmware/20 Pipeline was successful
ci/woodpecker/pr/build-linux/2 Pipeline was successful
ci/woodpecker/pr/build-windows Pipeline was successful
ci/woodpecker/pr/lint Pipeline was successful
to e3e42dd496
Some checks failed
ci/woodpecker/pr/build-firmware/15 Pipeline was successful
ci/woodpecker/pr/build-firmware/19 Pipeline was successful
ci/woodpecker/pr/build-linux/1 Pipeline was successful
ci/woodpecker/pr/build-firmware/20 Pipeline was successful
ci/woodpecker/pr/build-linux/2 Pipeline was successful
ci/woodpecker/pr/build-windows Pipeline was successful
ci/woodpecker/pr/lint Pipeline was successful
ci/woodpecker/push/build-firmware/2 Pipeline was successful
ci/woodpecker/push/build-firmware/5 Pipeline was successful
ci/woodpecker/push/build-firmware/8 Pipeline failed
ci/woodpecker/push/build-firmware/4 Pipeline was successful
ci/woodpecker/push/build-firmware/6 Pipeline was successful
ci/woodpecker/push/build-firmware/1 Pipeline was successful
ci/woodpecker/push/build-firmware/7 Pipeline was successful
ci/woodpecker/push/build-firmware/3 Pipeline was successful
ci/woodpecker/push/build-firmware/13 Pipeline failed
ci/woodpecker/push/build-firmware/11 Pipeline was successful
ci/woodpecker/push/build-firmware/16 Pipeline was successful
ci/woodpecker/push/build-firmware/14 Pipeline was successful
ci/woodpecker/push/build-firmware/9 Pipeline was successful
ci/woodpecker/push/build-firmware/10 Pipeline was successful
ci/woodpecker/push/build-firmware/12 Pipeline was successful
ci/woodpecker/push/build-firmware/15 Pipeline was successful
ci/woodpecker/push/build-linux/1 Pipeline was successful
ci/woodpecker/push/build-linux/2 Pipeline was successful
ci/woodpecker/push/build-firmware/19 Pipeline was successful
ci/woodpecker/push/build-firmware/20 Pipeline was successful
ci/woodpecker/push/build-firmware/18 Pipeline was successful
ci/woodpecker/push/build-windows Pipeline was successful
ci/woodpecker/push/build-firmware/17 Pipeline was successful
2026年06月14日 21:09:17 +02:00
Compare
Author
Owner
Copy link

@northernpaws @freyjadomville Do we need to clarify anything beyond the current wording?

Do we need to define what is considered AI/LLM here? Because it is not text <-> speech for example, which is used for accessibility and does not fall under these rules. The rule about translation is there because it is important to know what translator tool is used to know it's quirks and how it might or might not misinterpret the content. Posting pre-translated texts removes this context.

@northernpaws @freyjadomville Do we need to clarify anything beyond the current wording? Do we need to define what is considered AI/LLM here? Because it is not text <-> speech for example, which is used for accessibility and does not fall under these rules. The rule about translation is there because it is important to know what translator tool is used to know it's quirks and how it might or might not misinterpret the content. Posting pre-translated texts removes this context.
esden changed title from (削除) WIP: Add the Zig's NoAI policy to our Code of Conduct. (削除ここまで) to Add the Zig's NoAI policy to our Code of Conduct. 2026年06月14日 21:15:18 +02:00
dragonmux left a comment
Copy link

All looks good from our perspective, so approving pending their reviews.

All looks good from our perspective, so approving pending their reviews.
northernpaws left a comment
Copy link

Looks good to me! I'm comfortable that the current wording is explicit enough that it's referring to LLMs and not other machine learning-based applications like speech-based accessibility aids.

Looks good to me! I'm comfortable that the current wording is explicit enough that it's referring to LLMs and not other machine learning-based applications like speech-based accessibility aids.

Likewise, looks good to me. Shipping it.

Likewise, looks good to me. Shipping it.
Sign in to join this conversation.
Labels
Clear labels
BMD App
Black Magic Debug App (aka. PC hosted) (not firmware)
BMP Firmware
Black Magic Probe Firmware (not PC hosted software)
Bug
Confirmed bug
Build system
Build system
Can't reproduce
Maintainers can't reproduce this problem
CI
Continuous Integration System
Contribution wanted
User contributions welcome
Documentation
Project documentation
Draft
Work in progress draft
Duplicate
This issue or pull request already exists
Enhancement
General project improvement
Feedback wanted
Requires additional submitter feedback
Foreign Host Board
Non Native hardware to runing Black Magic firmware on
GDB
Issue/PR related to GDB
Good first issue
Good for newcommers
HwIssue Mitigation
Solving or mitigating a Hardware issue in Software
Information Needed
Maintainers need more information
NativeHardware
Official Black Magic Debug Hardware
New Host Board
New hardware to run Black Magic firmware on
New Target
New debug target
Off Topic
Something that does not involve the project in any way
Potential Bug
A potential, unconfirmed or very special circumstance bug
Regression
Bug caused by a regression
User Interest Needed
More user interest required before consideration
User Testing Needed
Looking for user testing reports
Won't fix
Outside of the project scope or works as intended
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
blackmagic-debug/blackmagic!2268
Reference in a new issue
blackmagic-debug/blackmagic
No description provided.
Delete branch "add-no-ai-to-coc"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?