FreeBSD Status Report Fourth Quarter 2022

The New Year has started and here is the last status report of 2022, including 34 reports. You will also notice that for the first time a new category has been introduced: the Cloud category. As FreeBSD keeps up to date with the latest technologies in IT, projects dealing with the cloud make steady improvements, and thus it has been judged that they deserve their own category in the status reports.

The new category is not the only change about status reports. Indeed, the status team is revisiting its own workflow to become more efficient. If you are a report submitter, please ensure to read carefully the report authored by the status team as well as the next Call for Reports emails to keep up with the most recent changes.

Have a nice read.

Lorenzo Salvadore, on behalf of the status team.

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

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

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

Table of Contents

• FreeBSD Team Reports
□ FreeBSD Core Team
□ FreeBSD Foundation
□ FreeBSD Release Engineering Team
□ Cluster Administration Team
□ Continuous Integration
□ Ports Collection
□ Status reports: New workflow
• Projects
□ Console screen reader infrastructure
□ Vessel - Integrated Application Containers for FreeBSD
□ Enable the NFS server to run in a vnet prison
□ Pytest support for the FreeBSD testing framework
• Userland
□ Base System OpenSSH Update
• Kernel
□ Enabling Snapshots on Filesystems Using Journaled Soft Updates
□ Wireless updates
□ Netlink on FreeBSD
□ Adding basic CTF support to ddb
• Architectures
□ CheriBSD 22.12 release
□ FreeBSD/riscv64 Improvements
□ go on FreeBSD riscv64
□ FreeBSD/ARM64 on Xen
• Cloud
□ FreeBSD on Microsoft HyperV and Azure
□ FreeBSD as a Tier 1 cloud-init Platform
□ OpenStack on FreeBSD
• Documentation
□ Documentation Engineering Team
□ FreeBSD Presentations and Papers
• Ports
□ FreshPorts - help wanted
□ PortsDB: Program that imports the ports tree into an SQLite database
□ KDE on FreeBSD
□ Xfce on FreeBSD
□ Pantheon desktop on FreeBSD
□ Budgie desktop on FreeBSD
□ GCC on FreeBSD
□ Another milestone for biology ports
• Third Party Projects
□ 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 <core@FreeBSD.org>

The FreeBSD Core Team is the governing body of FreeBSD.

Items

Core Team Charter

A delegation of the current core team is working together with some members of the previous Core Team to draft a core team charter. There was a face-to-face meeting in the US on December 3 - 4 to discuss the new charter. The delegation will present to the rest of the core team and discuss the details in the first quarter of 2023. The same delegation also had a meeting with the FreeBSD Foundation board on December 5th to discuss the collaboration details.

Experimental Matrix IM solution

The core team is working on evaluating Matrix as an instant messaging tool for the project. This will make the project’s communication channels less dependant
on third parties. The service will be made available to the FreeBSD community to test and evaluate its validity at a later date.

Committer’s Guide

Deprecate BSD-2-Clause-FreeBSD and use BSD-2-Clause. For more information please refer to the commit.

Commit bits

• Core approved the src commit bit for Zhenlei Huang (zlei@)

• Core approved the src commit bit for Corvin Köhne (corvink@)

• Core approved the src commit bit for Sumit Saxon (ssaxena@)

• Core approved the restore of the source commit bit for Paweł Jakub Dawidek
(pjd@).

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

FreeBSD Foundation

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

Contact: Deb Goodkin <deb@FreeBSDFoundation.org>

The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits. We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts. We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity.

Fundraising Efforts

Thank you to everyone who made a financial contribution in 2022! We’re still tallying up the totals and will have final numbers soon. Unfortunately, we did not meet our fundraising goal, which reinforced our need of having someone who can focus on encouraging organizations to invest in FreeBSD. We will bring someone on board soon to help with that effort.

In this Quarterly Status report you’ll read about many of the areas we funded in Q4 to improve FreeBSD and advocate for the Project (the two main areas we spend money on). Check out reports on the internally and externally funded projects like Openstack on FreeBSD, Enabling Snapshots on Filesystems Using Journaled Soft Updates, FreeBSD as a Tier 1 cloud-init Platform, and FreeBSD/ riscv64 Improvements. In addition, we provided tons of community engagement and education opportunities virtually and in-person!

If you want to help us continue our efforts, please consider making a donation towards our 2023 fundraising campaign! https://www.freebsdfoundation.org/donate/

We also have a Partnership Program for larger commercial donors. You can read about it at https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/.

OS Improvements

During the last quarter of 2022, 218 src, 45 ports, and 12 doc tree commits identified the Foundation as a sponsor. Work was committed under Foundation sponsorship to repositories outside of FreeBSD as well, e.g., to the cloud-init project. Some of this sponsored work is described in separate report entries:

• FreeBSD as a Tier 1 cloud-init Platform

• OpenStack on FreeBSD project update

• Wireless Report

• Enabling Snapshots on Filesystems Using Journaled Soft Updates

Other Foundation work in the src tree included:

• a variety of additions and fixes from Konstantin Belousov including commits
to the virtual memory system (e.g., ec201dd, cd08669, and d537d1f), and
file systems (e.g., 37aea26, 83aff0f, 860399e, and 4d903a1)

• work from Andrew Turner on arm64 such as an implementation of per-superpage
locks and the addition of support for an array of hwresets

• more RISC-V improvements from Mitchell Horne, including improvements to
parsing of ISA property strings, optimizations to memory allocation, and
various documentation additions and improvements

• follow-up commits to Mark Johnston’s work to add ZFS Support to makefs(8)
(e.g., work to easily provide ZFS-based VM and cloud images and automation
for better defaults from Li-Wen Hsu)

• a variety of work from Ed Maste, including an ssh update and a switch to
LLVM objdump.

Continuous Integration and Quality Assurance

The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project. You can read about the latest activity for that work in a separate report entry.

FreeBSD Advocacy and Education

Much of our effort is dedicated to Project advocacy. This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations. The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier. Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables.

The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. These events can be BSD-related, open source, or technology events geared towards underrepresented groups. We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. This all helps provide a healthy ecosystem. We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. We are continuing to attend events both in person and virtual as well as planning the November Vendor Summit. In addition to attending and planning virtual events, we are continually working on new training initiatives and updating our selection of how-to guides to facilitate getting more folks to try out FreeBSD.

Check out some of the advocacy and education work we did last quarter:

• Sponsored the OpenZFS Developer Summit, October 24-25, 2022 in San
Francisco, CA

• Sponsored All Things Open, October 30-November 2, 2022 in Raleigh, NC

• Sponsored and helped organize the November 2022 FreeBSD Vendor Summit.
Videos from the Summit are available.

• Held a new FreeBSD Friday: An Introduction to FreeBSD Services by Drew
Gurkowski

• Published the Fall and Winter Newsletter updates

• New Blog Posts

□ Meet the 2022 FreeBSD Google Summer of Code Students: Koichi Imai

□ Meet the 2022 FreeBSD Google Summer of Code Students: Bojan Novković

□ Keeping FreeBSD Secure: Learn the Whys and Hows with the FreeBSD Sec
Team

□ The FreeBSD Journal is still Free!

□ EuroBSDCon 2022 Trip Report: Muhammad Moinur Rahman

□ EuroBSDCon 2022 Trip Report: Patrick McEvoy

□ Fall Foundation Software Development Update

□ Invest in FreeBSD

□ 2022 in Review: Advocacy

□ Foundation Sponsors Update to WireGuard Kernel Port for FreeBSD

□ 2022 in Review: Fundraising Update

□ 2022 in Review: Software Development

□ 2022 in Review: Continuous Integration and Quality Assurance Update

• FreeBSD in the news:

□ Ampere: Getting Cloud-Native with FreeBSD on OCI Ampere A1 with
Terraform

□ FreeBSD is Well Supported on 4th Gen AMD EPYC™ Processors

• For a quick review of all the Foundation efforts in 2022, check out our
2022 Thank You Video.

We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. As we mentioned previously, the FreeBSD Journal is now a free publication. Find out more and access the latest issues at https://www.freebsdfoundation.org/journal/.

You can find out more about events we attended and upcoming events at https://www.freebsdfoundation.org/news-and-events/.

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://www.freebsdfoundation.org to find more about how we support FreeBSD and how we can help you!

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

FreeBSD Release Engineering Team

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

Contact: FreeBSD Release Engineering Team <re@FreeBSD.org>

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.

During the fourth quarter of 2022, the Release Engineering Team completed work on the 12.4-RELEASE cycle. This is the final release from the stable/12 branch. During the release cycle, only one BETA build and two RC (release candidate) builds were needed; overall the release cycle went very smoothly and the release took place on December 5th.

During the fourth quarter of 2022, the Release Engineering Team continued providing weekly development snapshot builds for the main, stable/13, and stable/12 branches.

In the first quarter of 2023, the Release Engineering Team will start work on the upcoming 13.2-RELEASE.

Sponsors:
Rubicon Communications, LLC ("Netgate")
The FreeBSD Foundation

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

Cluster Administration Team

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

Contact: Cluster Administration Team <clusteradm@FreeBSD.org>

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

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

• Regular cluster-wide software upgrades
Two full upgrades to fix and prevent some impacting issues
(FreeBSD-EN-22:25.tcp and FreeBSD-EN-22:28.heimdal).

• Regular support for FreeBSD.org user accounts

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

• Site audit at our primary site

□ Inventory of spares and other miscellanea occupying space in our
cabinets.

□ Inventory of PDUs/power outlet usage and identifying faulty PSUs.

• Identify and fix major DNS issue impacting the project
The primary DNS servers hosted on HE.net suffered outages for a few days,
and new DNS servers were deployed worldwide. We thank our sponsor Metapeer
for providing anycast infrastructure.

• Deploy a new mirror in Frankfurt, Germany
A replacement for our mirror in Amsterdam (site decommissioned). Former and
new mirror hosted and sponsored by Equinix.

• Reuse parts of three broken CI machines
No replacements for these at this moment, awaiting a cluster refresh soon.

• Work with the PowerPC team to improve the PowerPC cluster machines

□ Parts like mainboard, NVMe and Power 9 CPU bought through the FreeBSD
Foundation.

□ Former package builder fixed, and re-deployed as powerpc and powerpc64
package builder.

□ Former devref machine reinstalled as a new powerpc64le package builder.

□ The cluster has now only these two PowerPC machines in operation.

• Several rounds to free up disk space usage in the cluster machines

• Setup of an experimental search engine for the mailing lists:
https://lists.freebsd.org/search

• Fix a bug in the mailing lists archiver, which resulted in some broken
links
All mailing lists archives have been regenerated.

Work in progress:

• Large-scale network upgrade at our primary site
New Juniper switches arrived at our primary site to replace the former
ones. We thank Juniper for the donation.

• Replace old servers in our primary site and a few mirrors
Besides the broken CI servers, we have a few old servers with broken disks
and faulty PSUs. This task is in conjunction with the FreeBSD Foundation
and donors/sponsors.

• Create a new database for the mailing list search engine to allow searching
for mail in the archives from mailman’s time

FreeBSD Official Mirrors Overview:

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

The hardware and network connection have been generously provided by:

• Bytemark Hosting

• 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

• Your.org

The Frankfurt single server mirror is now the primary Europe mirror in bandwidth and usage.

We are still looking for an additional full mirror site (five servers) in Europe to replace old servers in the United Kingdom full mirror site.

We see a good pattern in having single mirrors in Internet Exchange Points worldwide (Australia, Brazil, and South Africa); if you know or work for some of them that could sponsor a single mirror server, please get in touch. United States (West Coast) and Europe (anywhere) are preferable places.

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

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

Continuous Integration

Links:
FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org
FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org
FreeBSD Jenkins wiki URL: https://wiki.FreeBSD.org/Jenkins
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://preview.tinyurl.com/y9maauwg 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 <jenkins-admin@FreeBSD.org>
Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
Contact: freebsd-testing Mailing List
Contact: IRC #freebsd-ci channel on EFNet

The FreeBSD CI team maintains the continuous integration system of the FreeBSD project. The CI system checks the committed changes can be successfully built, then performs various tests and analysis over the newly built results. The artifacts from those builds are archived in the artifact server for further testing and debugging needs. The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the code or adjust test infrastructure.

During the fourth quarter of 2022, we continued working with the contributors and developers in the project to fulfill their testing needs and also keep collaborating with external projects and companies to improve their products and FreeBSD.

Important completed tasks:

• FreeBSD-main-amd64-gcc9_build now sends failing reports to the committers
whose commits may be related.

• FreeBSD-main-amd64-gcc12_build has been added.

• FreeBSD-main-powerpc64-images now also builds bootable APM disk image for
Apple G5 baremetal and QEMU -M mac99 (by alfredo@)

Work in progress tasks:

• Designing and implementing pre-commit CI building and testing (to support
the workflow working group)

• Designing and implementing use of CI cluster to build release artifacts as
release engineering does

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

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

• Organizing the scripts in freebsd-ci repository to prepare for merging to
src repository

• Improving 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

• Planning to run ztest tests

• Adding more external toolchain related jobs

• 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 don’t
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
FreeBSD Ports Monitoring URL: http://portsmon.freebsd.org/
Ports Management Team URL: https://www.freebsd.org/portmgr/
Ports Tarball URL: http://ftp.freebsd.org/pub/FreeBSD/ports/ports/

Contact: René Ladan <portmgr-secretary@FreeBSD.org>
Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>

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

Currently we have just over 31,000 ports in the Ports Tree. There are currently close to 2900 open ports PRs of which almost 800 are unassigned. The last quarter saw 8194 commits by 159 committers on the main branch and 657 commits by 53 committers on the 2022Q4 branch. Compared to the quarter before, this means a small increase in the number of available ports but also in the number of open PRs and a decreasing number of commits made.

On the personnel front, we welcomed Ronald Klop (ronald@) and said goodbye to bar@ and bhughes@. We welcomed pizzamig@ as a new official member after a successful lurking period. We also welcomed three new lurkers: bofh@, ler@, and ygy@.

Portmgr split itself up into portmgr and pkgmgr. The new pkgmgr team, currently consisting of antoine@ and bdrewery@, is responsible for building packages and maintaining the package building cluster.

Four new USES were introduced:

• llvm to canonicalize ports dependencies on LLVM

• luajit to select a LuaJIT runtime

• octave to help ports depend on Octave and Octave-Forge

• tex to define dependencies on TeX and its various components.

The following default versions were bumped:

• Firebird to 3.0

• GCC to 12

• Lazarus to 2.2.4

• Lua to 5.4

• PHP to 8.1

• Samba to 4.13

• Varnish to 6

• LuaJIT is new and set at "luajit-openresty" for PowerPC64 and
"luajit-devel" for all other architectures.

Three new features were introduced, PIE, RELRO, and BIND_NOW. Each port can opt out of them by setting the <feature>_UNSAFE variable. Users can activate or deactivate them globally by setting WITH_<feature> or WITHOUT_<feature>.

The following major ports were updated to new versions:

• Chromium 108.0.5359.124

• Electron 18.3.11, 19.0.15, and 21.2.0

• Firefox 108.0.1

• Firefox-ESR 102.6.0

• gcc 12

• KDE Plasma 5.24.7, Frameworks 5.101.0, Applications 22.12.0

• Qt 5.15.7 and 6.4.1

• Rust 1.66.0

• SDL 2.26.1

• Sway 1.8

• wlroots 0.16.1

• Wine 7.0.1.

The exp-run reports are available again. During the last quarter, antoine@ ran 38 exp-runs to:

• test port updates

• change default versions

• identify use of IPPROTO_DIVERT in ports

• support PF_DIVERT in Python for FreeBSD 14.

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

Status reports: New workflow

Links:
FreeBSD status reports URL: https://www.freebsd.org/status/
Status reports GitHub repository URL: https://github.com/freebsd/freebsd-quarterly

Contact: <status@FreeBSD.org>

Goals of the new workflow

This quarter the status team has been discussing with doceng@ some improvements to its workflow. In particular, the team is attempting to merge its GitHub repository into the FreeBSD doc/ repository.

Here are the reasons for such a change:

• having two independent repositories requires spending some time to make
sure that both are in sync, which is being done manually. See for example
commits such as
https://github.com/freebsd/freebsd-quarterly/commit/4b8255e604dd0513e841aa8f3dce7741e78b999c,
which are not immediately clear
in their commit messages about what is being done unless more time is
invested to copy commit messages properly;

• the FreeSD doc/ repository is self-hosted, while the status repository is
hosted on GitHub. Since the contents of the self-hosted repository are
mirrored, nothing is being lost in visibility with the repository merging.

Some inconsistencies about the name of the team have also been found: the team has been referred to as "quarterly", "quarterly status team", "status", "status team", "monthly" etc. So this issue is also being addressed.

Please note that we are still working on these changes and that they might not be completed within the next quarter. The status team will take care to keep all information about report submissions up to date so that you always know how to submit your reports.

Team naming

Since "quarterly" might refer to quarterly reports but also to quarterly branches, using "quarterly" only could cause some confusion in some contexts. "quarterly-status" is likely a bad idea as well, as the frequency of reports publication might need to change in the future. Thus just "status" has been chosen: this is correct as quarterly status reports contain information about the status of the development of FreeBSD, it is frequency-agnostic and consistent with its FreeBSD website section.

The following email addresses have been created:

• the main contact address for the status team is now <status@FreeBSD.org>.
Mails sent to quarterly@FreeBSD.org will still reach the team, but you are
encouraged to use the new address;

• the email address for the status report submissions is now <
status-submissions@FreeBSD.org>. Mails sent to
quarterly-submissions@FreeBSD.org will still reach the team, but you are
encouraged to use the new address;

• the quarterly-calls mailing list has been renamed to status-calls. If you
were already subscribed to quarterly-calls, you do not need to resubscribe.

Report submission

Three different ways to submit reports will be provided:

• submitting a review on Phabricator. A new Phabricator group called "status"
has been created. If you would like to give a hand to the team by reviewing
reports we suggest you add yourself to the group 'watchers';

• submitting a pull request at https://github.com/freebsd/freebsd-doc/pulls;

• sending an email to status-submissions@FreeBSD.org.

Reviewing processes will proceed as they usually do on each of these channels.

Other changes

• The repository merging will require reworking some of the existing tools to
better integrate with the existent structure of the FreeBSD doc/
repository.

• The status reports GitHub repository will be archived once the new workflow
implementation is completed.

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

Projects

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

Console screen reader infrastructure

Links:
console speaker daemon URL: https://reviews.freebsd.org/D35776
kernel support for console screen reader URL: https://reviews.freebsd.org/D35754
base system accessibility wishlist URL: https://wiki.freebsd.org/Accessibility/Wishlist/Base

Contact: Hans Petter Selasky <hps@selasky.org>
Contact: FreeBSD accessibility discussions <freebsd-accessibility@freebsd.org>

This project aims at providing a very basic screen reader usable in console mode (without a GUI) for FreeBSD. This is an important first step for system administrators using speech to access computers, who previously would have needed a second computer running a terminal emulator to install or configure a FreeBSD server or character-based desktop computer.

The third and fourth quarters of 2022 saw basic design and some feature testing which looks promising, and a detailed call for testing with installation procedure posted.

This project needs help with the following:

• Code reviewing

• Usability testing

• Integrating with the FreeBSD installer.

Sponsor: NVIDIA Networking (for the kernel development part)

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

Vessel - Integrated Application Containers for FreeBSD

Links:
Vessel URL: https://github.com/ssteidl/vessel

Contact: Shane Steidley <ssgriffonuser@gmail.com>

What is Vessel?

The goal of vessel is to expose the many powerful features of FreeBSD to application developers. Vessel accomplishes this goal by:

• Providing a "Docker-like" interface familiar to most application developers
for building, running, publishing and pulling container images.

• Tightly integrating with FreeBSD system level interfaces (kqueue process
tracing, signal handling, devd.seqpacket, rctl, cpuset) to manage running
jails.


[continued in next message]

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