Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] AI_POLICY.md document template
I don't know specifically where Maria Teresa got her inspiration for the template that she's generated.

We started this work based on an observation that AI_POLICY.md documents in various forms are popping up in all kinds of GitHub repositories. AFAICT it's not a standard yet, nor have I seen any specific discussion regarding making it a standard. Things continue to evolve.

If you (or anybody else in the council) has observed something different, then we should explore that.

Here're a couple of examples:

https://github.com/eclipse-collections/eclipse-collections/blob/master/AI_POLICY.md
https://github.com/apache/fory/blob/main/AI_POLICY.md

HTH,

Wayne

On Mon, 17 Aug 2026 at 16:08, Jay Jay Billings via eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx> wrote:
Wayne,

Thanks very much for sharing. I look forward to digging deeper into this.

Quick question: Can you point to an example of a project that has an AI_POLICY.md document? I've never seen that kind of document. Instead, I usually see the AI policy in README.md.

Jay

On Mon, Aug 17, 2026 at 3:18 PM Wayne Beaton via eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx> wrote:
Greetings Eclipse Technical Advisory Council!

We've observed a trend of creating an AI_POLICY document in repository roots to provide contributors with guidelines regarding the project's values with regard to the use of AI in the contribution process. I've mentioned this document in a few of our committer office hours sessions and in the Use of Artificial Intelligence by Eclipse Committers and Contributors committer training video.

The EMO team has been working on a template for a project-specific AI_POLICY.md file. We're tracking that work in this issue. Your feedback is requested.

Note that this is intended as a template for a project-specific policy; this is specifically not intended as the policy for all Eclipse projects. Nonetheless, this will likely be regarded as a recommendation by some, so we should be sensitive to that.

We considered the opportunity for multiple templates but decided to start with what the team feels is the most common configuration.

Thanks in advance.

Wayne

--

Wayne Beaton (he/him)

Head of Open Source Projects | Eclipse Foundation

_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council


--
Jay Jay Billings, Ph.D.
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council


--

Wayne Beaton (he/him)

Head of Open Source Projects | Eclipse Foundation

Back to the top