I’ve approved that email so it has landed to the devel-announce list now too. Here is where I am at with the current policy, and what I would like to see as next/final steps:
- The policy has not changed drastically from what had initially been proposed. As far as I can tell, there is no brand new subject matter introduced the latest revision form the original. Rather, the current proposal has been enhanced to include as much feedback as possible from the original. So to me, there is no need to completely restart the process. Instead, we are continuing on in the current process and making sure that there is clarity on what is being proposed to be voted on.
- I understood from our meeting last week that we were delaying the decision to vote by one week as there was still a lot of discussion happening on the thread, and what the exact policy that we would have to take a vote on was not very clear. At least to me it wasn’t. Our Policy Change Policy only states that a minimum of two weeks must be given for feedback, not that we can only allow two weeks for feedback. In this instance, more time was and is absolutely needed. And I think we are the better for it with the latest version of the policy!
So, with this latest revision now published, I feel we have reached a place where there is a satisfactory* policy proposed, which has come from several revisions to the original from the feedback received. This is community collaboration at work, and while the topic itself is a pretty divisive one, its been great to see the different points of views being stated, and heard, and formed into a policy the project can at least start with regarding AI.
My suggestion for the councils next steps:
Firstly, thank you @churchyard for announcing the current policy version to the lists, to you @jasonbrooks for updating the ticket with the current version and @bookwar for updating this thread with them too. This is exactly the clarity we needed to proceed with this process.
A current version of the policy is now announce, and I would recommend that we (council), continue to monitor the discussion, and plan to vote in the ticket before our next council meeting on Wednesday, 22 October 2025.
We can follow FESCo’s pattern of a -1 vote in the ticket will automatically trigger that the proposal be discussed in the meeting. However, if no -1s are received in the ticket, we will do a vote tally as part of the meeting and can announce any decisions and assign any action items as the result.
*I understand this is not a satisfactory proposal felt by absolutely everyone. However, this one seems to meet a decent middle ground, and I agree with @blc sentiment that the policy currently proposed is ‘good enough’ for now. Personally, I would prefer that the Fedora Project have something in place regarding AI contributions that could help folks understand where and what is an appropriate use of AI in the project than have nothing at all. I fully expect we will need to propose further revisions to any policy we ratify on the subject in the (likely near) future, but until we start with something, we ultimately have nothing