FreeBSD Status Report
Report Entry
FreeBSD Core Team
Contact: FreeBSD Core Team <core@FreeBSD.org>
The FreeBSD Core Team is the governing body of FreeBSD.
Completed items
We completed the following items:
Handover from the previous Core Team
The handover from core.13 was completed: mail aliases, the LDAP group, and the Phabricator group now contain only core.14 members.
Core liaisons
-
FreeBSD Foundation: bapt@ (with most of core@ participating in monthly Foundation meetings)
-
secteam: kevans@
-
clusteradm: adrian@
-
srcmgr: imp@
-
portmgr: adamw@, olivier@
-
doceng: hrs@
-
re: hrs@
Public meeting minutes
We reached consensus to publish our public meeting minutes, which were previously only sent to the developers mailing list.
FreeBSD Developer AI survey
bapt@ created a survey for FreeBSD developers on the use of AI and LLMs. He presented the results to core@, and a summary was shared with developers. 140 developers responded.
-
Policy: 88% want the Project to adopt a policy, either a formal, written policy (49%) or light guidance and best practices (39%). 6% said that AI should be explicitly discouraged, and 3% that the existing contribution rules are sufficient.
-
AI-assisted code: 35% said it must be disclosed, 25% that it must be reviewed more strictly than human code, 22% that it should be treated like any other contribution, and 16% that it should be rejected outright.
-
Safeguards: mandatory human review (78%) and mandatory disclosure (69%) were requested most often, followed by provenance or licensing documentation (47%) and mandatory testing (39%).
-
Disclosure: 84% want AI use disclosed, either always (48%) or when its involvement is significant (36%). 79% want AI-assisted commits marked in the commit log, and 56% prefer a tag that names the tool.
-
Concerns: the main concerns about quality are correctness and subtle bugs (39%), licensing and provenance (26%), and maintainability (21%). 75% are somewhat or very concerned about copyright and licensing.
-
Principles: accountability, meaning that a human remains responsible (91%), and transparency (78%) were selected most often, and preserving code quality was the top-ranked goal for a policy.
-
Other uses: 65% would allow AI-generated documentation with human review. 54% would allow AI tools on Project infrastructure, most of them with restrictions, and 29% would not.
Community survey committee
The FreeBSD Foundation asked for a core representative on the committee for the upcoming user survey. jrm@ volunteered.
Ports repository freeze and history rewrite
On 2026-07-20, a 150 MB binary file was mistakenly committed to the ports tree. The commit broke mirroring to GitHub, which rejects files larger than 100 MB, and added a file of questionable licensing to the repository history. On 2026-07-21, core@ decided to freeze the ports repository to limit the number of commits that would need to be rewritten, and worked out a plan with clusteradm@, portmgr@, and the Git administrators. kevans@ published a signed statement on 2026-07-22 to explain the freeze and to make clear that the ports tree had not been compromised. The offending commits were removed by rewriting the history of the main branch, and package builds from the old hashes were stopped. New server-side hooks now guard against a recurrence.
EU Cyber Resilience Act (CRA) statement
The FreeBSD Foundation asked core@ to recognize it as an open source steward. We settled on a statement of support, which was published on the announce and developers mailing lists.
Releases
We reviewed the draft announcement for 14.5-RELEASE and the proposed schedule for 15.2-RELEASE.
Developer and contributor conflicts
We dealt with conflicts between developers and external contributors. Decisions were communicated to the parties involved.
Commit bit policy
jrm@ committed a clarification of the commit bit policy.
Correspondence
We handled correspondence on a number of topics, including the current and future AI policy work and the impact of increased AI/bot-driven scraping on FreeBSD infrastructure.
Work in progress
Core secretary role
We are defining the scope of a funded secretary role, which may serve the whole project rather than only core@. Examples from other non-profits and FreeBSD working groups are being used as a reference. There is rough consensus to move the role towards a project management assistant. A proposal was shared with the FreeBSD Foundation and feedback is pending.
AI policy
imp@ created an AI working group made up of people with diverse opinions on the topic. The working group will use the developer survey results as input for a policy on the use of AI/LLMs. The kickoff meeting of the group will be held on October 7. Final reports are expected in Q4.
Bylaws and core terms
We are continuing the previous Core Team’s work on staggered terms. We consider ourselves a transitional Core Team and plan to invoke the bylaws' staggering provision, with the change taking effect in 2027. Before the 2027 election, we will designate which members step down after one year and which serve a full two-year term; the vacated seats will be filled in that election.
Regularizing policy
Efforts are underway to modernize and centralize the FreeBSD Project’s policy documentation, which is currently inconsistent, poorly visible, and reliant on unwritten "tribal knowledge." imp@ is working to consolidate existing guidelines, resolve policy contradictions between project groups, and formally record long-standing traditions. Additionally, this initiative will identify gaps where new, formal policies are needed to ensure smooth, efficient operations. We hope to have this wrapped up by the end of Q1 2027.
Liaison expectations
We are documenting the responsibilities of each liaison role and will publish the document once it is complete.
Workflow organization
We are evaluating tooling to track our tasks, documents, and correspondence. We began using a CryptPad instance set up by bapt@ and clusteradm@.
Policy on reasonable content for Project spaces
We discussed writing down the Project norms for what content is reasonable for Project spaces, such as the wiki and repository metadata. Over the years, we have developed a tradition of avoiding politics, religion, and other contentious issues unrelated to the Project, and need to write it down and bring it in line with open source norms.
portmgr structure
We are discussing the structure of portmgr@ and how to revamp the team.
Cluster administration planning
adrian@ and some clusteradm@ members are preparing a budget, prioritizing work, improving documentation and processes, and planning to recruit new team members in 2027.
Returning developers
srcmgr@ has a new policy for returning developers, which asks for some recent work or plans before access is restored, and portmgr@ has something similar. We are discussing whether it makes sense for these policies to be aligned across teams.
Privacy requests
core@ received a GDPR erasure request covering mailing list posts from more than twenty years ago. Removing content from public mailing list archives is not practical, especially for archives the Project does not control. The Project has a privacy policy, which should be extended to cover mailing lists, Bugzilla, and other services. We communicated this to the person requesting the removal.
Core and FreeBSD Foundation meetings
Monthly meetings are scheduled through December 2026.
Bay Area Vendor Summit in November
We are planning a short introduction and update followed by a question and answer session.
Last modified on: October 8, 2026 by Joseph Mingrone