Governance/AI_USAGE.md
Konstantin Pastbin 67a3af5d6c Amend and add Members-approved and supporting docs
Co-authored-by: Penn Mackintosh <[email protected]>
Signed-off-by: Konstantin Pastbin <[email protected]>
2026-10-14 13:00:30 +07:00

4.2 KiB

AI usage in the CoMaps project

This document describes if and how artificial intelligence can be used in the CoMaps project by contributors, including agreements for how to use it in a transparent and responsible way. This agreement is applicable to all projects hosted under the umbrella of the CoMaps organisation.

All contributors are expected to be aware of this agreement and to apply it in their contributions. Contributions that do not honor these agreements will not be accepted and admins will close corresponding pull requests and issues.

Definitions & Motivations

Note

This does not necessarily reflect the official or commonly used definitions.

Software and services that heavily rely on large language model technology to generate their outcomes are referred to as Artificial Intelligence (AI). Examples of products that fit this definition: GitHub Copilot, ChatGPT, Claude Sonnet, DeepSeek, Llama and Gemini.

There's a distinction between general and narrow AI, all the aforementioned examples fall under general AI as they were not trained to execute a specific well-defined task. Narrow AI is trained to be used for specific well-defined tasks where the problem space is known in advance.

Vibe coding is the practice where AI creates a code change (feature, bug fix, tests, refactor) with a human that describes what needs to be implemented.

AI agents are AIs that are configured to perform interactions or make changes with little to no human supervision.

"AI agents" and "vibe coding" typically result in the "authors" of code not having expertise in the changes they aim to contribute, thus not able to answer questions about which trade-offs were made and why. If authors were only minimally involved in how code was generated, they can't be accountable for AI's output, which is harmful to the long-term sustainability of open source projects like CoMaps.

Agreement

  1. If content was made with the help of AI, you must convey that this is the case. This includes content that you authored but was motivated by a suggestion of AI.
  2. If at any point you used AI's work in your contribution you should make an effort to verify that you can submit this under the license of the repository.
  3. The accountability of using AI in a contribution lies with the person that makes that contribution.
  4. All communication, that includes: commit messages, pull request messages, documentation, code comments and issues (and comments on issues/pull requests), that is intended to be read by people to understand your thoughts and work must not have been generated with AI. We exclude machine translation and tooling that helps with grammar and spelling check.
  5. Using general AI for review is forbidden. Changes have to be approved by a human reviewer.
  6. It is not allowed to use AI in an autonomous-looking way to contribute in CoMaps (i.e. solely using 'agent mode' or 'vibe coding'). To ensure the long-term maintainability and sustainability of the project, we require authors to have read and understand the code they submit themselves.

Note

Where CoMaps tries to cherry-pick open source commits from upstream projects (e.g. Organic Maps), this agreement only applies to original/new contributions made to CoMaps and not those cherry-picks. Instead, cherry-picks continue to be reviewed and tested by multiple contributors, thus minimizing the outlined sustainability issues.

License

This agreement has been adapted from the AI Agreement that the Forgejo project has passed in late 2025 and which is licensed under a Creative Commons CC BY 4.0 license.

We thank the Forgejo project and its contributors for their thorough discussions on this and for allowing us to benefit from them. We thus release our adapted version under the same CC BY 4.0 license for others to similarly benefit from our work.


This is a Members-approved document, all amendments (except non-substantive changes, e.g. typo fixes) must be approved by a regular Members vote as per the Constitution.