FreeBSD Status Report Fourth Quarter 2024

Here is the fourth and last 2024 status report, with 44 entries.

It shows: 2024 has been a tremendously successful and busy year. Usually, one would expect the final months in a year to be less busy, with people leaving for holidays and New Years celebration. We still managed to deliver and see great progress on so many things!

Collecting and compiling this report took longer than planned, but it was worth the wait.

Thank you to the whole community for your amazing work and an especially big thanks to those who contributed updates to this report!

Enjoy the read!

Chris Moerz, on behalf of the Status Team.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

A rendered version of this report is available here: https://www.freebsd.org/status/report-2024-10-2024-12/

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Table of Contents

• FreeBSD Team Reports
□ FreeBSD Core Team
□ FreeBSD Foundation
□ FreeBSD Release Engineering Team
□ Cluster Administration Team
□ Continuous Integration
□ Ports Collection
□ Bugmeister Team
□ New srcmgr team
• Projects
□ Infrastructure Modernization
□ Laptop Support and Usability Improvements Project
□ Security engineering at the FreeBSD Foundation
□ Security Audits
□ Framework Laptop support
• Userland
□ PkgBase-motivated improvements to pkg
□ Progress on the FreeBSD installer
• Kernel
□ Audio Stack Improvements
□ mac_do(4), setcred(2), mdo(1)
□ Suspend/Resume Improvements
□ umb(4) driver for MBIM USB 4G/5G modems
□ LinuxKPI 802.11 Wireless Update
□ Wireless Update
□ Syzkaller Improvement on FreeBSD
• Architectures
□ Pinephone Pro Support
• Cloud
□ FreeBSD on Microsoft HyperV and Azure
□ OpenStack on FreeBSD
□ Containers and FreeBSD: Cloud Native Buildpacks
□ FreeBSD on EC2
• Documentation
□ Documentation Engineering Team
• Ports
□ Ports Collection Accessibility - Colors Low Vision
□ Containers and FreeBSD: AppJail, Director, OCI and more
□ Improving Common Lisp Infrastructure in FreeBSD Ports
□ FreeBSD Erlang Ecosystem Ports update
□ Improve OpenJDK on FreeBSD
□ Xfce on FreeBSD
□ LXQt on FreeBSD
□ GCC on FreeBSD
□ Tor-Browser
□ Greenbone Vulnerability Management Community Edition
□ Wazuh on FreeBSD
□ A bhyve management GUI written in Freepascal/Lazarus
□ BSD-USER 4 LINUX
• Third Party Projects
□ Laptop and Desktop Work Group (LDWG)
□ Containers and FreeBSD: Pot, Potluck and Potman

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD Team Reports

Entries from the various official and semi-official teams, as found in the Administration Page.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD Core Team

Contact: FreeBSD Core Team <[email protected]>

The FreeBSD Core Team is the governing body of FreeBSD.

Following up with the FreeBSD Foundation

Core had a video conference with the FreeBSD Foundation on 2024-12-12 to follow-up on their in-person meeting held in Dublin during EuroBSDCon. Core and the Foundation continue discussing how to improve the collaboration and how to support developers and contributors:

• The next round of community survey

• Identifying projects where core would like help from the Foundation

• Work on the technical roadmap with the Foundation

Work in Progress

Core is currently working on the following items:

• Policy on generative AI created code and documentation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD Foundation

Links:
FreeBSD Foundation URL: https://freebsdfoundation.org/
Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://freebsdfoundation.org/donate/
Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/
FreeBSD Journal URL: https://freebsdfoundation.org/journal/
Foundation Events URL: https://freebsdfoundation.org/our-work/events/

Contact: Deb Goodkin <[email protected]>

The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to advancing FreeBSD through technical and non-technical support. Funded entirely by donations, the Foundation supports software development, infrastructure, security, and collaboration efforts; organizes events and developer summits; provides educational resources; and represents the FreeBSD Project in legal matters. The following report covers just some of the ways we supported FreeBSD in Q4.

Deb Goodkin here. On behalf of the Foundation, I want to start out by saying thank you to this amazing community! Your financial contributions have allowed us to step up and take on some significant projects, including large, multi-phase software development work, greater security improvements, and important infrastructure improvements that will continue through 2025. We also increased our FreeBSD advocacy efforts over many different technical and social media platforms, including creating more content to promote and advocate for FreeBSD. You’ll find more information about all of this work below. For a more
in-depth look at our efforts in 2024, be sure to check out the year-end blog posts and my year-end reflections in the advocacy section below.

We are hiring! Check out our jobs page here for our Solutions Specialist and Technical Marketing Manager job postings. Plus, we are looking for part-time technical writers and will be opening up another position soon, so keep an eye on this page https://freebsdfoundation.org/open-positions/.

We are still finalizing our 2024 fundraising numbers, but at this writing, we have raised around $1,324,000. You might be thinking, why do not we have a final tally now that it is 2025? First, we have not yet received all the checks postmarked 2024 . We are also waiting on a few payments from invoices issued last year. We will have a final report in the next quarterly status report.

Thank you to the individuals and organizations that made a financial contribution in Q4! We received 325 donations from individuals totaling $120,841 and six financial contributions from organizations totaling $326,000. We also received a grant from the Silicon Valley Community Fund.

I would also like to send a shoutout to the anonymous donor who wanted us to help get Framework laptops into developers' hands. Pietro Cerutti has been coordinating that effort, and we are close to finalizing the process with Framework so developers can place their orders directly with them.

We also funded almost $5,000 worth of AV equipment for the BSDCon AV team to minimize the amount of equipment needed to rent at each of the two main BSD conferences.

Now, back to our financials. We will be publishing 2024 financial documents and reports in Q1. Our updated Q1-Q3 2024 Financial reports will be published by the end of January and will better match the budget format. The Final 2024 financial reports will be published in early Q2. Going forward, our budget and financial reports will provide more details on how funding is allocated to the major software development projects. For example, we will include how much was spent on the laptop project each quarter. We are working with our accountant to improve our accounting systems to be more transparent on how we spend our money.

We are excited about the opportunities for FreeBSD in 2025 and beyond, and are growing our team to help support the work needed to take advantage of these opportunities. However, we need your help to sustain this. Our investments will only carry on this work for a year or two at most. If your company is invested in the long-term sustainability of FreeBSD, please consider giving a financial contribution so we can ensure it stays the secure, reliable, and innovative platform you depend on. Not sure how to go about asking? Please reach out. We can help you navigate the process.

Please go here to make a donation: https://freebsdfoundation.org/donate/. To find out more about our Partnership Program, go here: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/.

Advocacy

During the 4th quarter of 2024, we continued to raise awareness, advocate for the project, showcase users, while also providing educational content to the FreeBSD community. Here are some highlights of those efforts.

• Sponsored and helped to organize the Fall 2024 FreeBSD Summit which took
place November 7-8, 2024 in San Jose, CA. Check out the event recap. Videos
are available on the FreeBSD YouTube channel.

• Updated the community on two of the new releases:

□ FreeBSD 13.4: What’s new, and how did we get here?

□ FreeBSD 14.2: What’s new, and how did we get here?

• Published the NYI Case Study

• Shared the FreeBSD Foundation 2024 Report on the Security Audit of the
Capsicum and bhyve subsystems. Learn more in the Security Audit.

• Created a series of year end retrospectives on the work we did in 2024.

□ Your Impact on FreeBSD: 2024 Milestones and What’s Next

□ 2024: A Year of Advocacy and Growth for the FreeBSD Foundation

□ Celebrating 2024’s Collaborative Achievements at the FreeBSD Foundation

□ FreeBSD Foundation: A Year of Sponsored Development in 2024

□ Reflecting on a Successful 2024

• Published additional blogs including:

□ Why Your Open Source Project Should Prioritize Security: Lessons from
FreeBSD’s Proactive Approach

□ Why FreeBSD Should Be the Foundation for Your Security Product

□ Celebrating FreeBSD Day with Tara Stella: A Journey from Linux to
FreeBSD

□ Advancing Cloud Native Containers on FreeBSD: Podman Testing Highlights

• Participated in the following contributed articles, interviews and
podcasts:

□ All Things Open Blog: Prioritizing Security: Lessons from FreeBSD’s
Proactive Approach

□ FreeBSD Foundation Releases Bhyve and Capsicum Security Audit Funded by
Alpha-Omega Project

□ Why We Use FreeBSD Over Linux: A CTO’s Perspective

• Published the October 2024, November 2024, and December 2024 FreeBSD
Foundation Newsletters.

• Released the September/October 2024 issue of the FreeBSD Journal with HTML
versions of the articles.

OS Improvements

During the fourth quarter of 2024, 382 src, 135 ports, and 17 doc tree commits identified The FreeBSD Foundation as a sponsor.

The Foundation and its investment partners supported four major projects:

• Konstantin Belousov continued work on an AMD IOMMU driver for FreeBSD, a
project jointly funded by AMD and the Foundation. This effort aims to
enhance support for large-core AMD systems and other scenarios requiring
interrupt remapping. The driver was pushed to the src tree in early
November and continues to undergo testing and refinement.

• Alpha-Omega and the Foundation have been jointly funding a project to
improve FreeBSD security. For the latest updates, refer to the Security
Engineering at the FreeBSD Foundation entry for the latest updates.

• A project to improve FreeBSD laptop usability began this quarter. For
details, refer to the Laptop Support and Usability Improvements Project
report entry.

• Work commissioned by the Sovereign Tech Agency to modernize FreeBSD’s
infrastructure continued this quarter. The goal of this work is to help
achieve and sustain a manageable bug backlog. As part of this effort, The
Foundation worked with Bitergia to analyze and assess open Bugzilla bugs.
Muhammad Moinur Rahman finished porting Grimoirelab and deploying Grimoire
in the FreeBSD cluster.

Other projects:

• Alfonso S. Siciliano provided a FreeBSD Accessibility Project update.

• Aymeric Wibo began implementing suspend-to-idle and S0ix sleep support.

• Bjoern A. Zeeb shared a LinuxKPI 802.11 Wireless Update.

• Chih-Hsin Chang continued work to improve OpenStack on FreeBSD.

• Christos Margiolis shared an update on work to improve the FreeBSD audio
stack.

• Harald Eilersten began working on a project to improve OpenJDK on FreeBSD.

• Isaac Freund worked on PkgBase-motivated improvements to pkg.

• Jian-Lin Li began a project to improve Syzkaller on FreeBSD.

• Joseph Mingrone spent time on a personal project to improve Common Lisp
support in the ports tree.

• Olivier Certner submitted a report entry describing the work he completed
with Baptiste Daroussin to allow controlled process credentials transitions
using the MAC framework.

• Pierre Pronchery returned to working on a umb(4) driver for MBIM USB 4G/5G
modems and he shared an update on work to improve the FreeBSD Installer.

• Tom Jones started porting the iwx WiFi driver from OpenBSD (via Haiku).

Other members of the Foundation’s development team contributed to FreeBSD development efforts. For example:

• Mitchell Horne worked with community contributor Julien Cassette to add a
RISC-V Allwinner D1 clock and reset driver.

• Chuck Tuffli, John Baldwin, and Pierre Pronchery fixed a few bhyve issues:

□ bounds checks in hda_codec

□ out-of-bounds read in NVMe log page

□ infinite loop in queue processing

□ buffer overflow in pci_vtcon_control_send

□ robustness of TRIM handling.

• In the ports tree, Muhammad Moinur Rahman converted USE_OCAML and USE_JAVA
to the USES framework.

• Ed Maste squashed a couple of makefs(8) bugs related to creating ISO9660
filesystems via the cd9660(4) driver:

□ cd9660 filename buffer maximum length

□ cd9660 duplicate directory names.

Continuous Integration and Workflow Improvement

As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to improving the Project’s continuous integration system and test infrastructure.

Legal/FreeBSD IP

The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise.

Go to https://freebsdfoundation.org to find more about how we support FreeBSD and how we can help you!

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD Release Engineering Team

Links:
FreeBSD 14.2-RELEASE announcement URL: https://www.freebsd.org/releases/14.2R/announce/
FreeBSD 13.5-RELEASE schedule URL: https://www.freebsd.org/releases/13.5R/schedule/
FreeBSD releases URL: https://download.freebsd.org/releases/ISO-IMAGES/
FreeBSD development snapshots URL: https://download.freebsd.org/snapshots/ISO-IMAGES/

Contact: FreeBSD Release Engineering Team, <[email protected]>

The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.

The Team managed 14.2-RELEASE, leading to the official RELEASE build and announcement in December. Planning has started for the upcoming 13.5-RELEASE cycle, which is expected to be the final release from the legacy stable/13 branch; as such it will include updates to "contrib" code and some bug fixes, but is not expected to have any significant new features.

In addition to previously shipped release artifacts (ISO and memory stick images, VM images, cloud offerings, etc.) the Team is now also providing OCI compatible container images.

The Release Engineering Team continued providing weekly development snapshot builds for the main, stable/14, and stable/13 branches.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Cluster Administration Team

Links:
Cluster Administration Team members URL: https://www.freebsd.org/administration/#t-clusteradm

Contact: Cluster Administration Team <[email protected]>

FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronize its distributed work and communications.

In this quarter, the team has worked on the following:

• Regular support for FreeBSD.org user accounts.

• Regular disk and parts support (and replacement) for all physical hosts and
mirrors.

• Cluster software refresh.

• Moving more cluster services to Chicago.

• Supporting the Grimoirelab dashboard effort.

Cluster software refresh

Except for the package builders and developer-facing ("dogfood") machines, the FreeBSD cluster mostly tracks stable/X branches.

At the time of this writing, there are 131 physical machines in the cluster. We have 54 machines on current, 61 on stable/14 and 14 on stable/13. Work continues to upgrade the remaining stable/13 machines to stable/14. The stable/ 12 machines have been slated for decommissioning for a while; they do not run production workloads. The remaining machines are slated for upgrading or decommissioning in the near future.

Of the 297 jails in the cluster, 222 are now on stable/14.

12.x: Regular 2, Jails 7
13.x: Regular 14, Jails 59
14.x: Regular 61, Jails 222

15.x: Regular 54, Jails 9

Total: Regular 131, Jails 297
Total installations: 428
Running -RELEASE|{-p*}: 0
Total geographic sites: 15

Moving cluster services to Chicago

Earlier this year, we started building up our new site in Chicago. This quarter, we began decommissioning older machines in New Jersey and moving services to the newer machines in Chicago. Our long-term goal is for Chicago to become our primary location. This work will take several more months to complete.

FreeBSD Official Mirrors Overview

Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Sweden, Taiwan, United Kingdom (full mirror site), United States of America — California, Chicago, New Jersey (primary
site), and Washington.

Our mirror site in Taiwan is experiencing an extended outage. We hope to have it back online during the first quarter of 2025.

Also during the first quarter of 2025, we expect a second mirror site in California, generously hosted by Sonic.

The hardware and network connection have been generously provided by:

• Cloud and SDN Laboratory at BroadBand Tower, Inc

• Department of Computer Science, National Yang Ming Chiao Tung University

• Equinix

• Internet Association of Australia

• Internet Systems Consortium

• INX-ZA

• KDDI Web Communications Inc

• Malaysian Research & Education Network

• MetaPeer

• New York Internet

• NIC.br

• Teleservice Skåne AB

• Your.Org

New official mirrors are always welcome. We have noted the benefits of hosting single mirrors at Internet Exchange Points globally, as evidenced by our existing mirrors in Australia, Brazil, and South Africa. If you are affiliated with or know of any organizations willing to sponsor a single mirror server, please contact us. We are particularly interested in locations on the United States West Coast and throughout Europe.

See generic mirrored layout for full mirror site specs and tiny-mirror for a single mirror site.

Sponsors: The FreeBSD Foundation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Continuous Integration

Links:
FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org
FreeBSD CI Tinderbox view URL: https://tinderbox.freebsd.org
FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org
Hosted CI wiki URL: https://wiki.FreeBSD.org/HostedCI
3rd Party Software CI URL: https://wiki.FreeBSD.org/3rdPartySoftwareCI
Tickets related to freebsd-testing@ URL: https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals
FreeBSD CI Repository URL: https://github.com/freebsd/freebsd-ci
dev-ci Mailing List URL: https://lists.FreeBSD.org/subscription/dev-ci

Contact: Jenkins Admin <[email protected]>
Contact: Li-Wen Hsu <[email protected]>
Contact: freebsd-testing Mailing List
Contact: IRC #freebsd-ci channel on EFNet

In the fourth quarter of 2024, we worked with the project contributors and developers to address their testing requirements. Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD.

Important completed tasks:

• Update main and stable/14 build environment to 14.2-RELEASE

• Update stable/13 build environment to 13.4-RELEASE

• Fixed an old but not revealed bug about pw(1) usage in jail setup.

Work in progress tasks:

• Designing and implementing pre-commit CI building and testing and pull/
merge-request based system (to support the workflow working group)

□ Improving the src/tests/ci work to support running test suites

☆ Merging CI: Add full test support

□ Merging Pre-commit CI with CIRRUS-CI

• Designing and implementing use of CI cluster to build release artifacts as
release engineering does, starting with snapshot builds

• Simplifying CI/test environment setting up for contributors and developers

• Setting up the CI stage environment and putting the experimental jobs on it

• Redesigning the hardware test lab and adding more hardware for testing

Open or queued tasks:

• Collecting and sorting CI tasks and ideas

• Setting up public network access for the VM guest running tests

• Implementing use of bare-metal hardware to run test suites

• Adding drm ports building tests against -CURRENT

• Helping more software get FreeBSD support in its CI pipeline (Wiki pages:
3rdPartySoftwareCI, HostedCI)

• Working with hosted CI providers to have better FreeBSD support

Please see freebsd-testing@ related tickets for more WIP information, and do not hesitate to join the effort!

Sponsor: The FreeBSD Foundation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Ports Collection

Links:
About FreeBSD Ports URL:https://www.FreeBSD.org/ports/
Contributing to Ports URL: https://docs.freebsd.org/en/articles/contributing/#ports-contributing
Ports Management Team URL: https://www.freebsd.org/portmgr/
Ports Tarball URL: http://ftp.freebsd.org/pub/FreeBSD/ports/ports/

Contact: Tobias C. Berner <[email protected]>
Contact: FreeBSD Ports Management Team <[email protected]>

The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. Below is what happened in the last quarter.

In the last quarter, we welcomed Xavier Beaudouin (kiwi@) as a new ports committer.

According to INDEX, there are currently 36,332 (down from 36,504) ports in the Ports Collection. There are currently about 3,368 (down from 3,379) open ports PRs, of which 809 are unassigned.

The last quarter saw 10,640 commits (down from 11,594) by 155 committers (one less) on the main branch and 733 commits (down from 832) by 61 committers (down from 78) on the 2024Q4 branch.

The number of ports also decreased (down from 36,504).

The most active committers to main were:

• 3867 [email protected]

• 1156 [email protected]

• 368 [email protected]

• 361 [email protected]

• 273 [email protected]

• 247 [email protected]

• 209 [email protected]

• 206 [email protected]

• 201 [email protected]

• 157 [email protected]

A lot has happened in the ports tree in the last three months, an excerpt of the major software upgrades are:

• Default version of Lazarus switched to 3.6.0

• Default version of PHP switched to 8.3

• Chromium 131.0.6778.204

• Electron 33.3.0

• Firefox 134.0

• Firefox-esr 128.6.0

• KDE Frameworks 6.9.0

• KDE Plasma 6.2.4

• Qt6 6.8.1

• Python 3.9.21

• Python 3.10.16

• Python 3.11.11

• Ruby 3.2.6

• Ruby 3.3.6

• Rust 1.83.0

• SDL 2.30.10

• SDL 3.1.6

• Sway 1.10

Three new USES were introduced:

• cl to provide support for Common Lisp ports.

• java to provide support for Java.

• sbrk to handle ports requiring sbrk()

During the last quarter, pkgmgr@ ran 14 exp-runs to test various ports upgrades and changes to bsd.port.mk.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Bugmeister Team

Links:
FreeBSD Bugzilla URL: https://wiki.freebsd.org/Bugzilla

Contact: Bugmeister <[email protected]>

In this quarter we came even closer to steady-state; we are dealing with incoming PRs more quickly these days. For reference:

https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html&days=90

The overall number of PRs came down from slightly over 11,600 to right at 11,000. This was due to work from several people to go over entire groups of PRs (see below).

Mark Linimon attended several video calls with various src committers. They are doing some experimentation to learn what kind of effort is sustainable. The most recent effort was to evaluate the latest incoming src PRs; you will note that many of them from the past few weeks have been marked as requesting feedback.

Bugmeister folks also did some passes through the database to clean up metadata:

• reassigned bugs away from committers who had had their commit bits safekept
over the last year.

• cleaned up bugs for Product: Base System Status: In Progress. A number of
these were not being actively worked on. The count is down to 184.

□ In particular, Mark Linimon believes "assigned to mailing list" means
"it is not really In Progress". Perhaps it has been discussed, but we
do not really have a state for that. (We can make an argument that that
itself is a bug.)

□ We are now down to only a handful of the above, from "too many". The
concept is to make sure In Progress has some real meaning.

• evaluated PRs for mfc-stableN. In particular, any having mfc-stable12 had
that flag cleared.

□ The concept is to make sure these metadata have some real meaning as
well: e.g. "a commit has been made and should be evaluated for MFCs".

□ There are now a much smaller number of these.

• closed numerous PRs as "Overcome By Events":

□ (old version) + (contains the string "boot")

□ (old version) + (contains the strings "alpha" or "beta")

• evaluated "PR shows a commit" (possibly via Phabricator)" and "there was no
trailing discussion".

□ In a few cases of the above we simply assigned them and made sure that
mfc-stable[13|14] was set, if it seemed appropriate.

□ This does leave many that have a commit and then have trailing
discussion. I think we will need more volunteers to go through those.

• removed many of the 'patch' keywords from PRs. In the optimal case these
should now be imputed by metadata in each attachment. In a few cases where
patches are submitted inline instead of as an attachment, the keyword
stays. There may be a few of these left over from the GNATS conversion. The
use of inline patches should be discouraged, as automation has no way to
detect them. Thanks to our triagers, especially Alexander Ziaee.

There were various discussions about bug futures that came up in various video chats. One is that there is a (supported) successor to Phabricator, which itself is now no longer developed. Multiple groups will need to coordinate to evaluate it.

Jan Bramkamp has volunteered to help with the task "automate harvesting PRs and evaluating whether they still apply". Mark Linimon to collaborate.

Clusteradm@ helped us fend off yet another crawler site. While that was ongoing, bugzilla was nearly unusable due to timeouts, as were other services hosted on the same machine (wiki and cgit among others).

We also welcomed our newest Triage member, Lexi (aka 'ivy' on Discord).

Finally, glebius was added to bugmeister@ alias as core.13 liaison.

See also: https://wiki.freebsd.org/Bugzilla/SearchQueries

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

New srcmgr team

Contact: srcmgr <[email protected]>

A new source management team has been ratified by core@ to handle management of the FreeBSD src tree, akin to portmgr@ and doceng@ for the ports and docs trees, respectively. The initial members are Ed Maste, Mark Johnston, John Baldwin, and Warner Losh. srcmgr@ is currently focused on finding ways to make src developers more productive, and to try and manage the large numbers of bug reports and pull requests that we receive. The team meets every two weeks to discuss src-related issues and spend time triaging bug reports and pull requests. Meeting minutes are available on GitHub. The srcmgr@ team has a charter and is working on developing and documenting policies to help manage the src tree.

In December, srcmgr@ ran an online bug-busting session, attended by 15 developers. We spent time going through recent bug reports, plus a list of older ones with patches. The team plans to host monthly sessions of this type, and aims to open them to a wider audience in the future.

The team plans to develop a lurker program similar to portmgr@'s in the first half of 2025.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Projects

Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects.


[continued in next message]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)