An open source policy is more than a set of organizational rules. It shapes how people contribute to and maintain a project. Contributors need to understand it. Maintainers need to apply it consistently. Community members need opportunities to question it. And projects need to be willing to change it when experience shows that something isn't working. Organizations need to understand the expectations and requirements of the open source projects they depend on. This helps developers contribute code that upstream communities can legally and comfortably accept .
The first blog post in this series discussed community governance. Good governance turns shared community values into practical ground rules without trying to forecast every new coding assistant or possible use of a rapidly changing technology. An AI policy touches more than the people writing code, so a useful policy has to account for many perspectives and create a process in which community disagreement can make the policy better.
A 2026 study by Wenhao Yang, Runzhi He, and Minghui Zhou examined publicly available generative AI (gen AI) governance materials associated with 67 highly visible open source projects. The researchers found that the concerns around AI that communities are dealing with go far beyond the question of whether to permit AI-generated code. They also include accountability, verification, review capacity, provenance, and project infrastructure. The research identifies 3 broad governance orientations, summarized in Table 1.
Potential AI governance orientations in open source projects The researchers emphasize that these are different ways of framing the governance problem, rather than rigid categories. Projects can combine elements of more than 1 approach. Red Hat's Open Source and AI Program Office (OSAIPO) created AI Contribution Policy: A Practical Guide to help communities translate these governance questions into practical policy decisions. The guide takesthe boundary-and-accountability approach.
