Introducing The ASF’s New Logo Read Now

Board history: Responsible AI

ASF Oak Leaf Icon

Responsible AI

What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.

These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.

Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.

[raw] the published minutes, which are the record. [main index]

Appointments

Date Action Decided by
2026-07-22 Appointed Jeff Genender the board, by resolution

Decisions

Date Decision Item Outcome
2026-07-15 Create the Responsible AI Executive Committee special order not approved
2026-06-17 Create the Responsible AI Executive Committee special order tabled
2026-04-15 Responsible AI Initiative discussion discussed

Reports

2026-10-21 — Jeff Genender

* Survey for AI usage completed and results completed.
* LLMAO is passing traffic from ASVS scans and other pipelines on Gofannon
  along with coding agents including Claude Code, Grok Build, pi, and Copilot.
  Projects onboarded include Spark, Airflow, Solr, Sourcelume, Sling,
  Fineract, and Groovy.
* Refractory (RAI platform) with Memory design docs and work plan drafted and
  distributed.
* Presented on a panel covering "AI Policy for Open Source" at the Open Source
  Congress, leading to discussions with other foundations about adopting and
  contributing to the RAI platform.
* Public fork of Gofannon set up for regular upstream updates back to AI
  Alliance pulled from our maintenance fork
  (at https://github.com/apache/tooling-gofannon-fork)
* RAI Hackathon at Community Over Code for setting up LLMAO occurred
  on Oct 12 -
  Signed up Apache Sling, Apache Solr, Apache Sourcelume,
  Apache Spark, and others for using our hosted LLMs.
* RAI Roundtable at Community Over Code occurred on Oct 12 - Successful
  Roundtable with standing-room attendance. Great discussion with the panel
  and special thanks to Professor Tim Storer for attending and contributing.
* Blog post explaining items RAI has completed so far at
  https://news.apache.org/foundation/entry/what-the-asf-responsible-ai-initiative-has-built-so-far
* Request for budget for platform development and operation entered in Special
  Order 7-B Increase Staffing Budget
* Working with Fundraising regarding
    1. current RAI-related in-kind contributions
    2. vetting proposed a Targeted Donation of an AI cybersecurity
       code review platform, and a Targeted cash donation to benefit a
       named Apache project
    3. a possible AI tool entering the Incubator
* Spoke to VP of Legal and will introduce him to the proposed legal firm for
  pro-bono work once the law firm approves us via their pro-bono Board.

2026-09-16 — Jeff Genender

**Description**

The ASF Responsible AI Initiative (RAI) is a program to support the open
source technologies that underpin modern artificial intelligence, and to help
Apache communities adopt AI in a way that is open, transparent, and aligned
with the ASF's values. The initiative is grounded in the ASF's guidelines for
the responsible use of AI — human oversight, licensing integrity, security,
and documentation — core principles rooted in the Foundation's longstanding
philosophy of community over code.

To fulfill its charter, the RAI is undertaking efforts to facilitate:

  1. Access to AI models and tooling
  2. Ecosystem support for Projects
  3. Community engagement and outreach

**Status**

- Auto-deployment of cloud GPU instances is progressing well. This capability
  is being integrated into our system to manage donated credits, budgeted
  token allocations, and inference services for Foundation communities.
- Consulted with the Treasurer on accounting processes and completed Ramp
  setup in accordance with the approved budget.
- Met with two candidate sponsors to explore potential donations that would
  expand access to additional AI tools.
- Met with RAI backers to align on future donated services.
- Began developing a set of Best Practice recommendations.
- Submitted candidate logos to Marketing & Publicity (M&P) to finalize the RAI
  logo and ensure brand-usage compliance.
- Sourcelume has been successfully bootstrapped with initial infrastructure
  (email lists, website, and repositories) and will now handle its own
  reporting going forward. We are supportive of their progress and will
  continue to assist as needed.
- Organizing a RAI Hackathon and Birds-of-a-Feather (BOF) panel for Community
  Over Code Glasgow.
- Drafting the RAI work plan for the Refractory Platform Project. The
  Refractory is an internal holistic Project to specify a managed AI platform
  providing governance, metering, and budgeting for donated funds, compute
  time, and inference tokens. Describes the tooling and services to enable
  projects to take advantage of self-serve security scans and other workloads,
  and to have access to models and agents.
- Distributed a survey on AI usage to Project Management Committees (PMCs).
- Completed security scans across more than 230 repositories, resulting in
  CVEs and other hardening measures that are already complete or underway
https://news.apache.org/foundation/entry/security-scanning-at-foundation-scale
- Created a public email list at [email protected]
- Currently speaking to a law firm based out of DC that specializes in
  technical/IP law on a pro bono basis to review agreements, best practices,
  as well as other areas of legal interest.

**Upcoming**

Will be gathering the survey information to detemine project needs with AI and
begin forming information for AI usage and provide the begining of planning to
support the needs as well as solidifying Best Practices.

2026-08-19 — Jeff Genender

# Responsible AI Initiative Board Reports

## Report 1: August 2026

**Description**

The ASF Responsible AI Initiative (RAI) is a program to support the open
source technologies that underpin modern artificial intelligence, and to help
Apache communities adopt AI in a way that is open, transparent, and aligned
with the ASF's values. The initiative is grounded in the ASF's guidelines for
the responsible use of AI — human oversight, licensing integrity, security,
and documentation — core principles rooted in the Foundation's longstanding
philosophy of community over code.

To fulfill its charter, the RAI is undertaking efforts to facilitate:

1. Access to AI models and tooling
2. Ecosystem support for Projects
3. Community engagement and outreach

**Status**

Status on the above activities includes supporting the Security Scanning &
Triage collaboration between the ASF Security team and the Tooling team. More
than 75 PMCs have enlisted: some delays from one of our frontier model donors
are now resolved and initial scans are underway.

I participated on calls with Infrastructure, Tooling, and Fundraising to
coordinate targeted donations, prioritize token usage, and connect with
Initiative backers.

We are planning to conduct a survey of PMCs and operations teams on their use
of AI to have a better idea on the state of AI activity and tooling within the
ASF. We are touching base with the folks on Apache Magpie and coordinating
various projects-in-development, including Low-Rank Adaptation (LoRA) adapters
and a dynamic routing layer, a TLP proposal being prepared for Apache
Sourcelume — an AI training data provenance infrastructure, as well as a
proposal preparing to be submitted to the Apache Incubator or for new Project
(TBD).

Initial work has begun on LLMAO (LLM for Apache.Org), a Foundation-wide way
for committers, projects, and communities to reach sanctioned inference and
related AI capabilities without every PMC holding its own provider keys. The
goal is one governed chokepoint for attribution, budgets, and policy for work
in an AI-capable ASF. This project is to provide gateway access through
LiteLLM to hosted models including frontier and cloud (local) implementations.

We have opened the floor for ideas regarding budget, and worked on
infrastructure for RAI: our initial site is up at https://rai.apache.org/ . We
plan to add a new logo for RAI and are narrowing down to a handful of options.

We had a discussion with the Community Over Code/Asia panelists to review
messaging, and shared a new graph of our email counts that shows the source of
our pull requests (49% from unknown authors: possibly bots; need to look into
this).

As we're just officially getting started (our second week!) we welcome Member
feedback and ideas at `[email protected]` and at `#rai-discuss` on Slack.

We have currently put together an initial budget, in coordination with Tooling
and Infra to obtain some initial numbers primarily for hosting private LLMs
and token acquisition. The budget also includes travel for the VP to
Glasgow/CoC surrounding events with potential for one or more presentations,
Q&A, panel, BoF, and hackathon. The budget request is for $83,500.00 for the
current fiscal year. A resolution to approve the budget will be submitted to
the Board for consideration.

**Upcoming**

We aim to share results as we develop our tooling and processes. We are
planning to attend Community Over Code in Glasgow, and look forward to sharing
our progress with the greater community.

**Work items**

From our proposal for RAI, we have begun our initial work items:

1. Assess foundation-wide the current state of AI activity and tooling
2. Prioritize AI resources PMCs would like the Foundation to provide
3. Assemble a situation report with gap analysis
4. Prepare a strategy within 60 days
5. Maintain a rolling 60-day roadmap and plan
6. Construct budget updates for the Board's consideration
7. Collaborate with existing teams on policy

We are assembling estimates for potential work streams to support budget
plans. And we will be coordinating with existing teams this month to assess
any policy needs.

Subscribe to ASF Plus One, Our Monthly Newsletter

Subscribe Now