Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGES.rst
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,7 @@ Documentation
- Added recognition of NLnet Foundation for its funding and Open Collective for donations to the documentation footer. :issue:`1214`
- Documented ``vText`` properties according to :rfc:`5545#section-3.3.11`. :issue:`742`
- Convert docstrings in :mod:`icalendar.caselessdict` to Google Style format with ``Parameters``, ``Returns``, ``Raises``, and ``Example`` sections as appropriate. :issue:`1072`
- Revise AI policy, per NLnet advice. See discussion under `pycal.org issue #24 <https://github.com/pycalendar/pycal.org/issues/24>`_.


7.0.3 (2026-03-03)
Expand Down
21 changes: 16 additions & 5 deletions docs/contribute/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -70,28 +70,39 @@ Artificial intelligence policy
We want to protect the joy, goodwill, and volunteer time of the maintainers and contributors of icalendar.
As such, we take a strong stance against artificial intelligence (AI) abuse.

Contributors to icalendar must follow icalendar's AI policy as described in this section.
Contributors to icalendar must follow icalendar's AI policy as described in this section and its subsections.


.. _responsible-ai-use:

Responsible AI use
``````````````````

You may responsibly use AI as a tool to draft a pull request.
That means you must comply with :ref:`pull-request-requirements` and follow icalendar's `Code of Conduct <https://github.com/collective/icalendar/blob/main/CODE_OF_CONDUCT.md>`_.
It also means that you must take responsibility for the output, including reviewing and validating the output for accuracy and ensuring it resolves an issue.
You shall be held accountable for your AI-generated content.

If you use AI in your work:

- You must take responsibility for the output, including reviewing and validating the output for accuracy and ensuring it resolves an issue.
Comment thread
stevepiercy marked this conversation as resolved.
- You must disclose the AI's terms of use.
Comment thread
stevepiercy marked this conversation as resolved.
Outdated
- You must ensure that outputs are not reconstructed from copyrighted sources.
Comment thread
stevepiercy marked this conversation as resolved.
Outdated
Comment thread
stevepiercy marked this conversation as resolved.
Outdated
- You are expected to understand and be able to explain design and code decisions.
Comment thread
stevepiercy marked this conversation as resolved.
- You must distinguish git commits that add generated code and include the used model and prompts in your commit message.
Comment thread
stevepiercy marked this conversation as resolved.
Outdated
- You must disclose that you used AI in your change log entry.
- You shall be held accountable for your AI-generated content.


AI abuse
````````

You may not abuse AI to generate a pull request that is disruptive to the icalendar community.
Examples of such abuse include the following actions.
You may not abuse AI to generate a pull request that is disruptive to the icalendar community or does not adhere to :ref:`responsible-ai-use` described in the previous subsection.
Examples of such abuse and irresponsible use include the following actions.

- You claim no responsibility for the output of AI generated content.
- Your pull request demonstrates no understanding or thought whatsoever to solve an issue.
- Your pull request plagiarizes copyrighted or other material to which you have no legal claim.
- You ignore or don't respond to feedback.
- The GitHub account is itself an AI agent.


Report suspected violations
Expand Down