aziascreations/PB-MessagePack
1
0
Fork 0
mirror of https://github.com/aziascreations/PB-MessagePack.git synced 2026-11-03 17:01:24 +01:00
Code Issues Packages Releases Activity

Fixed typos in AI policy, Updated gitignore

Browse Source
This commit is contained in:
Herwin Bozet (NibblePoker)
2026-11-03 16:52:04 +01:00
parent 9facb66ee8
commit ea38a45cf3
2 changed files with 21 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitignore
+8
View File
@@ -6,6 +6,7 @@
*.dll *.dll
*.exe *.exe
*.cfg *.cfg
Build/
# Binary blobs # Binary blobs
*.bin *.bin
@@ -19,5 +20,12 @@ Trash/
*.zip *.zip
/spec* /spec*
# Performance tests
PerfTests/Results/
PerfTests/**/bin/
PerfTests/**/obj/
PerfTests/**/__pycache__/
# Security test suite # Security test suite
# Kept private as it is more than 3GB
SecurityTests/ SecurityTests/
ai-policy.md
+13 -15
View File
@@ -3,7 +3,7 @@
## Summary ## Summary
Usage of AI tools is authorized in this project. Usage of AI tools is authorized in this project.
**However, you are accountable for all produced code and must ensure you properly validated it before commiting !** **However, you are accountable for all produced code and must ensure you properly validated it before committing !**
## Scope ## Scope
@@ -14,14 +14,14 @@ This policy covers all contributions to this repository: source code, tests, doc
- Generating, refactoring, or explaining code with any AI tool. - Generating, refactoring, or explaining code with any AI tool.
- Writing tests and PR descriptions. - Writing tests and PR descriptions.
* *Make extra sure you review those in depth !* * *Make extra sure you review those in depth !*
- Openning pull requests, as long as a human reviews the result before merge. - Opening pull requests, as long as a human reviews the result before merge.
- Debugging, code review assistance, and research. - Debugging, code review assistance, and research.
## What should be avoided when possible ## What should be avoided when possible
- Writting every bit of documentation with AI. - Writing every bit of documentation with AI.
- Using AI to write commit messages. - Using AI to write commit messages.
* *Keep it human and clean as possible* * *Keep it as human and clean as possible*
## What isn't allowed ## What isn't allowed
@@ -37,7 +37,7 @@ AI output should be treated as a draft.
Before a change is merged, the submitting **human** must: Before a change is merged, the submitting **human** must:
1. **Read it.** Every changed line, not a skim. 1. **Read it.** Every changed line, not a skim.
2. **Understand it.** You can explain what it does and why, without the AI. 2. **Understand it.** You can explain what it does and why, without the AI.
3. **Verify it.** Build and test it, make sure you don't break it, and update what need to be. 3. **Verify it.** Build and test it, make sure you don't break it, and update what needs to be.
4. **Own it.** You would defend it in review exactly as if you had typed it yourself. 4. **Own it.** You would defend it in review exactly as if you had typed it yourself.
If you cannot do all four, the change is not ready. If you cannot do all four, the change is not ready.
@@ -48,17 +48,17 @@ If you cannot do all four, the change is not ready.
- An AI review alone does not count as an approval. - An AI review alone does not count as an approval.
## Licensign & accountability ## Licensing & accountability
**The human submitter is the author.** **The human submitter is the author.**
* You will be fully responsible for any security or licensing issue. * You will be fully responsible for any security or licensing issue.
* If required, you must be able to provide the prompts that led to your code. * If required, you must be able to provide the prompts that led to your code.
* We will **agressively** discard contributions when licensing issues arise and you can't do that. * We will **aggressively** discard contributions when licensing issues arise and you can't do that.
## Restrictions ## Restrictions
- **Secrets and sensitive data:** never paste credentials, keys, personal data, or confidential customer data into AI tools that are not approved for that data. - **Secrets and sensitive data:** never paste credentials, keys, personal data, or confidential customer data into AI tools that are not approved for that data.
- **Licensing:** do not accept output that reproduces third-party code with an incompatible licence. If a suggestion looks copied, treat it as copied. - **Licensing:** do not accept output that reproduces third-party code with an incompatible license. If a suggestion looks copied, treat it as copied.
## Disclosure ## Disclosure
@@ -72,20 +72,18 @@ Co-Authored-By: {AI's name} <{AI's email}>
## Enforcement ## Enforcement
- Changes that violate this policy will be reverted. - Changes that violate this policy will be reverted.
- Repeated violations will result in blank refusal of any further contributions. - Repeated violations will result in blanket refusal of any further contributions.
## Authors's note ## Author's note
I hate having to write to kind of shit to *moral sermon*, but the current landscape of software development is evolving fast, and I can't be fucked to deal with bullshit drama around the usage of AI. I hate having to write this kind of *moral sermon* shit, but the current landscape of software development is evolving fast, and I can't be fucked to deal with bullshit drama around the usage of AI.
If you don't like it, fine, go away and make you own. \ If you don't like it, fine, go away and make your own. \
If you like it, feel free to burn some tokens around the bonfire with us. If you like it, feel free to burn some tokens around the bonfire with us.
## Changes to This Policy ## Changes to This Policy
<!-- TODO: owner/contact -->
This policy is maintained by **Herwin Bozet (NibblePoker)**. \ This policy is maintained by **Herwin Bozet (NibblePoker)**. \
Feel free to propose changes via a pull request. Feel free to propose changes via a pull request.
_Last updated: 2026-11-02_ _Last updated: 2026-11-03_