From cc3033289aee24a621dc3b22266036f1c803c57b Mon Sep 17 00:00:00 2001 From: etiennebacher Date: Mon, 18 May 2026 16:40:04 +0100 Subject: [PATCH 1/3] init --- AI_policy.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 AI_policy.md diff --git a/AI_policy.md b/AI_policy.md new file mode 100644 index 0000000..63d71a9 --- /dev/null +++ b/AI_policy.md @@ -0,0 +1,16 @@ + +### Github + +We accept contributions generated by AI as long as they comply with the following criteria: + +1. The contributor must specify which parts of the code have been generated by AI. +1. The contributor must declare that they have reviewed all code generated by AI and that this code passes the test suite locally. +1. AI can be used to generate code but all other parts of the contributing process (including the process of opening a PR and communicating with the maintainers) must be done by a human. +1. All user-facing parts of a contribution (e.g., documenting a new function argument, adding a vignette, editing the changelog) must be done by a human. +1. If you wish to include context from an interaction with AI in your comments, it must be in a quote block (e.g., using >) and disclosed as such. It must be accompanied by human commentary explaining the relevance and implications of the context. Do not share long snippets. + +Not following these rules may lead to a PR being closed. + +### Zulip + +AI-generated messages are forbidden on Zulip. \ No newline at end of file From e97e8495310c19d155da6c65bc21f87db20b7a8a Mon Sep 17 00:00:00 2001 From: etiennebacher Date: Tue, 2 Jun 2026 14:56:10 +0100 Subject: [PATCH 2/3] add preamble --- AI_policy.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/AI_policy.md b/AI_policy.md index 63d71a9..4d0a797 100644 --- a/AI_policy.md +++ b/AI_policy.md @@ -1,3 +1,6 @@ +Palaeoverse is a community-driven initiative advancing open science in palaeontology through shared tools, training, and resources. The human aspect of this project is therefore important to us, which explains why we wrote the document you are currently reading. The objective of this community is also to enable researchers at every career stage to learn and develop new skills. + +Still, we acknowledge the potential usefulness and growing prevalence of AI, but wish to see it used only where reasonable and appropriate. The objective of this policy is to provide some guidelines regarding AI usage on our various platforms, such as Github and Zulip. ### Github From 71a2ea84baebe1c8011db9507657e9e883041cfb Mon Sep 17 00:00:00 2001 From: etiennebacher Date: Tue, 2 Jun 2026 15:37:33 +0100 Subject: [PATCH 3/3] big revamp --- AI_policy.md | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/AI_policy.md b/AI_policy.md index 4d0a797..fad2584 100644 --- a/AI_policy.md +++ b/AI_policy.md @@ -1,19 +1,21 @@ -Palaeoverse is a community-driven initiative advancing open science in palaeontology through shared tools, training, and resources. The human aspect of this project is therefore important to us, which explains why we wrote the document you are currently reading. The objective of this community is also to enable researchers at every career stage to learn and develop new skills. +Palaeoverse is a community-driven initiative advancing open science in palaeontology through shared tools, training, and resources. The objective of this community is also to enable researchers at every career stage to learn and develop new skills. The human aspect of this project is therefore important to us, which is the reason why we wrote this document. -Still, we acknowledge the potential usefulness and growing prevalence of AI, but wish to see it used only where reasonable and appropriate. The objective of this policy is to provide some guidelines regarding AI usage on our various platforms, such as Github and Zulip. +Still, we acknowledge the potential usefulness and growing prevalence of AI, but wish to see it used only where reasonable and appropriate. The objective of this policy is to provide some guidelines regarding AI usage on our various platforms, such as Github and Zulip. This policy is adapted from **XXX**. -### Github +### AI for communication -We accept contributions generated by AI as long as they comply with the following criteria: +Do not post AI-generated messages, i.e., Zulip messages, Github issues, pull requests description, and other messages must be written by humans. It's fine to use whatever tools you like for help with spelling, grammar, or translation. -1. The contributor must specify which parts of the code have been generated by AI. -1. The contributor must declare that they have reviewed all code generated by AI and that this code passes the test suite locally. -1. AI can be used to generate code but all other parts of the contributing process (including the process of opening a PR and communicating with the maintainers) must be done by a human. -1. All user-facing parts of a contribution (e.g., documenting a new function argument, adding a vignette, editing the changelog) must be done by a human. -1. If you wish to include context from an interaction with AI in your comments, it must be in a quote block (e.g., using >) and disclosed as such. It must be accompanied by human commentary explaining the relevance and implications of the context. Do not share long snippets. +Quoting an LLM answer is usually less helpful than linking to relevant primary sources, like source code, reference documentation, or web standards. If you do need to quote an LLM answer in a conversation, put the answer in a quote block, to distinguish LLM output from your own thoughts. -Not following these rules may lead to a PR being closed. +### AI for coding -### Zulip +You can use any tools that help you understand the codebase and write good code, including AI tools. If you used AI to generate code, you must disclose it in the PR description. Additionally, you always need to understand and explain the changes you're proposing to make, whether or not you used an LLM as part of your process to produce them. The answer to "Why is X an improvement?" should never be "I'm not sure. The AI did it.". -AI-generated messages are forbidden on Zulip. \ No newline at end of file +Do not submit an AI-generated PR you haven't personally understood and tested, as this wastes maintainers' time. + +Changes in documentation (e.g., documenting a new function argument, adding a vignette, editing the changelog) can be based on LLM output, but it remains your responsibility to read through the whole thing and make sure that it makes sense to you and represents your ideas concisely. A good rule of thumb is that if you can't make yourself carefully read some LLM output that you generated, nobody else wants to read it either. + +### Rule violations + +Violating these rules may lead to message deletions or pull requests being closed, and repeated offences may lead to temporary or permanent bans. \ No newline at end of file