From 5f7f5fd3f3ce52c79f06dcf83af43c06eaf500ec Mon Sep 17 00:00:00 2001 From: Arman Bilge Date: Thu, 26 Feb 2026 08:07:47 -0800 Subject: [PATCH 1/3] Add GSoC AI policy --- src/gsoc/ai.md | 22 ++++++++++++++++++++++ src/gsoc/gsoc.template.html | 1 + 2 files changed, 23 insertions(+) create mode 100644 src/gsoc/ai.md diff --git a/src/gsoc/ai.md b/src/gsoc/ai.md new file mode 100644 index 00000000..f8e13ad8 --- /dev/null +++ b/src/gsoc/ai.md @@ -0,0 +1,22 @@ +{% + laika.title: GSoC AI Policy + ai-tab.class: bulma-is-active +%} + +# Typelevel GSoC AI Policy + +Our AI policy is based on the following ideas. + +* **Respect maintainer time.** Our maintainers and GSoC mentors are volunteers who invest many hours reviewing open source contributions to ensure that Typelevel projects have high-quality, maintainable codebases. Please respect their time by submitting your best work. + +* **GSoC is about learning first, delivering second.** We prefer that you take your time and ask for help when contributing to our projects, rather than using AI to quickly write code that may work, but you do not understand. Our midterm and final evaluations of your work will consider how you grew as an open source contributor, in addition to what you created. + +* **AI has become a part of the contemporary developers's toolkit.** We do not want to blanket ban the use of AI. We recognize its value when used thoughtfully and want to support you in learning when and how to use AI effectively. + +With these principles in mind, to contribute to Typelevel as part of GSoC we ask you to follow these rules. + +1. **Demonstrate ownership of your code**, no matter how you wrote it. This means understanding how it works and being capable of explaining that and also creating and performing tests to confirm that it works correctly, both for yourself and for your collaborators. It is okay to ask for help! + +2. ***Never* use AI to generate descriptions for PRs or issues.** Similarly, please do not use AI to write your GSoC proposal or other communications such as email and Discord messages. The purpose of writing in these contexts is to organize your thoughts and directly communicate your ideas, not to craft a "polished" document. However, you may use AI to translate between English and another (natural) language. + +3. **Always communicate when you have used AI** to write code, typically in your PR description. It is also helpful to explain where and how you used it, such as by including any prompts. diff --git a/src/gsoc/gsoc.template.html b/src/gsoc/gsoc.template.html index 4c84c9df..c02ead31 100644 --- a/src/gsoc/gsoc.template.html +++ b/src/gsoc/gsoc.template.html @@ -5,5 +5,6 @@

Google Summer of Code

  • Welcome
  • Ideas
  • Events
    • +
  • AI Policy
    • From 77bd39fc135813650a9c9c0964495a593af86799 Mon Sep 17 00:00:00 2001 From: Arman Bilge Date: Thu, 26 Feb 2026 08:09:54 -0800 Subject: [PATCH 2/3] Fix typo --- src/gsoc/ai.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gsoc/ai.md b/src/gsoc/ai.md index f8e13ad8..3601d64f 100644 --- a/src/gsoc/ai.md +++ b/src/gsoc/ai.md @@ -11,7 +11,7 @@ Our AI policy is based on the following ideas. * **GSoC is about learning first, delivering second.** We prefer that you take your time and ask for help when contributing to our projects, rather than using AI to quickly write code that may work, but you do not understand. Our midterm and final evaluations of your work will consider how you grew as an open source contributor, in addition to what you created. -* **AI has become a part of the contemporary developers's toolkit.** We do not want to blanket ban the use of AI. We recognize its value when used thoughtfully and want to support you in learning when and how to use AI effectively. +* **AI has become a part of the contemporary developer's toolkit.** We do not want to blanket ban the use of AI. We recognize its value when used thoughtfully and want to support you in learning when and how to use AI effectively. With these principles in mind, to contribute to Typelevel as part of GSoC we ask you to follow these rules. From f4c9f81e9392a8b2de24b503541e6e26a4495410 Mon Sep 17 00:00:00 2001 From: Arman Bilge Date: Thu, 26 Feb 2026 08:27:37 -0800 Subject: [PATCH 3/3] Improve "ownership" rule Co-authored-by: Justin du Coeur, AKA Mark Waks --- src/gsoc/ai.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gsoc/ai.md b/src/gsoc/ai.md index 3601d64f..9a98d0ed 100644 --- a/src/gsoc/ai.md +++ b/src/gsoc/ai.md @@ -15,7 +15,7 @@ Our AI policy is based on the following ideas. With these principles in mind, to contribute to Typelevel as part of GSoC we ask you to follow these rules. -1. **Demonstrate ownership of your code**, no matter how you wrote it. This means understanding how it works and being capable of explaining that and also creating and performing tests to confirm that it works correctly, both for yourself and for your collaborators. It is okay to ask for help! +1. **Demonstrate ownership of your code**, no matter how you wrote it. This means understanding why it is appropriate to Typelevel's needs and how it works, being capable of explaining that, and also creating and performing tests to confirm that it works correctly, both for yourself and for your collaborators. It is okay to ask for help! 2. ***Never* use AI to generate descriptions for PRs or issues.** Similarly, please do not use AI to write your GSoC proposal or other communications such as email and Discord messages. The purpose of writing in these contexts is to organize your thoughts and directly communicate your ideas, not to craft a "polished" document. However, you may use AI to translate between English and another (natural) language.