[continued from previous message]

The Foundation continues to work on improving overall laptop support, and Framework laptops are one of the target platforms for the Laptop Support and Usability Project.

In March, some FreeBSD developers visited Framework’s Taipei office again to test FreeBSD on pre-release Framework products, the Framework Desktop and Framework Laptop 12. The results of these tests will be used to help shape FreeBSD’s development plans, and the FreeBSD support status will be updated in
document after further verification.

Sheng-Yi is using the laptop provided by Framework Computer to add more device support, e.g. hwpstate: add CPPC support for pstate driver on AMD.

Sponsor: The FreeBSD Foundation for Li-Wen and Sheng-Yi’s work
Sponsor: Framework Computer Inc for Daniel’s work, hardware and space support

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

Hackathon 202503 Tokyo, Japan

Links:
Hackathon/202503 Wiki Page URL: https://wiki.freebsd.org/Hackathon/202503 FreeBSD Hackathon Wiki Page URL: https://wiki.freebsd.org/Hackathon

Before the AsiaBSDCon-Lite 2025 event, some members of the community gathered and held a hackathon in Tokyo.

Thanks to Christoff Visser and Internet Initiative Japan Inc. who sponsored the venue.

The work done or progressed in the hackathon

Sheng-Yi Hung

• ipheth(4): The iPhone tethering uses NCM on newer iOS, modified ipheth(4)
to supporting it. Patch: https://reviews.freebsd.org/D49431

• Sccahe for FreeBSD base: the FreeBSD base supports ccache to cache the
build result. For cross machine build, we need a distributed cache
mechanism — that is — sccache. In Hackathon, the patch for adding sccache
support is created: https://reviews.freebsd.org/D49417

Kristof Provost

Wrote a test case for bsnmpd’s snmp_pf module. This revealed that the BEGEMOT-PF-MIB.txt MIB file could not be parsed by bsnmpwalk, which was also fixed. Commits: 712309a64512, c849f5333260 and 36586800803d

Aymeric Wibo

• Got writing to config space of USB4 routers working and successive reads on
AMD USB4 controllers.

• First steps to suspending USB4 routers.

• Put up a bunch of preliminary patches regarding the USB4 stuff.

• Tried passing through USB4 devices to Linux guest to suspend them (did not
work).

Mark Johnston

• Worked on various syzkaller reports, e.g.: fe7fe3b175b6

• Looked for races in pf after getting some vague bug reports from the
OPNsense developers and, with Gleb and Kristof, found and fixed a rare race
which could cause a use-after-free: 8efd2acf07bc

Philip Paeps

• Fixed the libtrue website — we now have libtrue.so :-)

• Worked on clusteradm technical debt

• Good progress on our LDAP update

• Updated a couple of internal machines

Li-Wen Hsu

• Project’s Git infrastructure improvements, including system updating,
maintenance scripts and git hooks fixes

• Plan the cluster goals and roadmap for 2025 and longer with Philip Paeps

Sponsor: Christoff Visser and Internet Initiative Japan Inc. for the venue

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

Sylve — A Unified System Management Platform for FreeBSD

Links:
GitHub URL: https://github.com/AlchemillaHQ/Sylve
CI URL: https://sylve-ci.alchemilla.io
Discord URL: https://discord.gg/bJB826JvXK

Contact: Hayzam Sherif <hayzam@alchemilla.io>

Sylve is a modern, unified system management platform for FreeBSD, inspired by Proxmox. It intends to provide an integrated web interface for managing virtual machines (via Bhyve), Jails, ZFS storage, networking, and firewalling. The backend is implemented in Go, while the frontend uses SvelteKit with Tailwind CSS and ShadCN UI components.

The project emphasizes a minimal system footprint, currently requiring only sysutils/smartmontools and sysutils/tmux as runtime dependencies.

Sylve addresses a key gap in the FreeBSD ecosystem: a user-friendly, full-featured web interface for system management. By unifying virtualization, storage, and network management, it aims to lower the barrier for users and administrators deploying FreeBSD in complex environments.

We started working on the project since February and have made significant progress across several areas:

• PAM-Based Authentication: Integrated support for FreeBSD’s native PAM
system, with optional fallback to local authentication.

• Disk Management: Users can view and manage physical disks and partitions
through the web UI, with SMART-based health monitoring included.

• Frontend Infrastructure: Continued development of reusable UI components
and layout structure, with a responsive and accessible design.

The project remains under active development and is not yet production-ready.

Planned tasks for the upcoming quarter include:

• ZFS Management: Implementing full support for creating and managing ZFS
pools and datasets via the web interface.

• Virtual Machine Management: Continuing the Bhyve integration to support VM
creation, monitoring, and control.

• Basic Network and Firewalling: Providing web-based interfaces for NAT, port
forwarding, and firewall rule configuration.

Contributions, testing, and feedback are very welcome. If you are interested in contributing, consider helping with:

• UI testing and accessibility feedback

• Bug reports and feature requests via GitHub

Sponsor: FreeBSD Foundation and Alchemilla (development and infrastructure support)

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

Userland

Changes affecting the base system and programs in it.

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

Jail metadata feature

Links:
The main commit URL: https://cgit.freebsd.org/src/commit/?id=30e6e008bc06385a66756bebb41676f4f9017eca

Contact: Igor Ostapenko <igoro@FreeBSD.org>
Contact: Dave Cottlehuber <dch@FreeBSD.org>

The meta and env new parameters of jail(8) have been introduced. Each one is an arbitrary string associated with a jail. It can be set upon jail creation or added/modified later:

# jail -cm ... meta="tag1=value1 tag2=value2" env="configuration"

The values are not inherited from the parent jail. A parent jail can read both metadata parameters, while a child jail can read only env via the newly added security.jail.env sysctl.

The maximum size of meta or env per jail is controlled by the global security.jail.meta_maxbufsize sysctl. Decreasing it does not alter the existing meta information.

Each metadata buffer can optionally be handled as a set of key=value\n strings:

# jail -cm ... meta="$(echo k1=v1; echo k2=v2)" env.1=one
# jls meta.k2 env.1 meta.k1

While meta.k1="" or meta.k1= resets the value to an empty string, the meta.k1 without the equal sign removes the given key. The flua’s libjail has been updated respectively to support the key-based handling.

Sponsor: SkunkWerks GmbH

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

Kernel

Updates to kernel subsystems/features, driver support, filesystems, and more.

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

Audio Stack Improvements

Contact: Christos Margiolis <christos@FreeBSD.org>

I have been working on the audio stack since 2024Q1. Below is a list of the previous status reports:

• 2024Q1

• 2024Q2

• 2024Q3

• 2024Q4

Important work since last report:

• Large refactor in sound(4)'s format conversion framework: 433e270f341c.
Further simplifications and refactors in the rest of the processing chain.

• Implemented AFMT_FLOAT support.

• More out-of-the-box laptop support, especially Framework models.

• Virtual channels are now allocated on-demand: 02d4eeabfd73

• Re-implementing /dev/dsp as a virtual/router device: D49216. Apart from the
standalone benefits of this change, it will also help us improve automatic
sound redirection in snd_hda(4).

• More sound(4) cleanups, fixes and improvements.

• New virtual_oss release: https://github.com/freebsd/virtual_oss/releases/tag/v1.3.2

• Got my audio-related BSDCan 2025 talk proposal accepted.

• Put porting SOF to FreeBSD on the backburner for now. See here for an
explanation.

• In contact with potential GSOC students interested in porting virtual_oss
to base.

Future work includes:

• Finish currently open tasks.

• More bug fixes, support, optimizations and general improvements, in all
areas of the sound stack.

• Get back to audio(8)

• Implement a generic MIDI layer, similar to pcm/, and improve/modernize the
MIDI codebase in general.

You can also follow the development process in freebsd-multimedia@, where I post regular reports.

Sponsor: The FreeBSD Foundation

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

DRM drivers

Links:
Update to Linux 6.7 DRM drivers URL: https://github.com/freebsd/drm-kmod/pull/332
Update to Linux 6.8 DRM drivers URL: https://github.com/freebsd/drm-kmod/pull/344

Contact: Jean-Sébastien Pédron <dumbbell@FreeBSD.org>

DRM drivers are kernel drivers for integrated and discrete GPUs. They are maintained in the Linux kernel and we port them to FreeBSD. As of this report, we take the AMD and Intel DRM drivers only (NVIDIA FreeBSD drivers are proprietary and provided by NVIDIA themselves).

We usually port them one Linux version at a time. This allows us to ship updates more often and it eases porting and debugging because we have a smaller delta compared to a bigger jump skipping several versions.

This quarter, we ported DRM drivers from Linux 6.7 and 6.8. This effort did not hit the Ports tree yet because several patches to the FreeBSD kernel (the linuxkpi compatibility layer specifically) are still being reviewed and improved.

So far, the feedback was good for GPUs that were already supported by previous versions of the drivers. For newer GPUs, especially Intel ones, panics and display corruptions were reported. At this point, it is difficult to say if we just miss fixes from Linux that were published in a later version, or if these issues are actual bugs on FreeBSD.

These updates target the FreeBSD 15-CURRENT development branch for now. Once kernel patches are accepted and the DRM drivers updates merged, we will evaluate if/how we can backport the kernel patches to earlier release branches (namely 14-STABLE).

If you want to try them, you will find instructions to build and install a kernel with the non-committed changes, the drivers and the firmwares, in the pull requests’ descriptions.

The next steps are:

1. Finish the polishing of kernel patches and commit them

2. Review and merge the DRM drivers updates

3. Evaluate a backport of the kernel patches to release branches to allow to
use these updates on older versions of FreeBSD.

This work is kindly sponsored by the FreeBSD Foundation as part of the Laptop and Desktop Project.

Sponsor: The FreeBSD Foundation

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

Suspend/Resume Improvement

Links:
Blog URL: https://obiw.ac/s0ix/
FOSDEM talk on S0ix URL: https://youtu.be/mBxj_EkAzV0
Working Repository URL: https://github.com/obiwac/freebsd-s0ix
Tip of the S0ix + AMD SMU stack URL: https://reviews.freebsd.org/D48721
USB4 suspend stack URL: https://reviews.freebsd.org/D49453

Contact: obiwac <obiwac@FreeBSD.org>

Suspend-to-idle and support for S0ix sleep is in the process of being added to FreeBSD.

This will allow modern Intel and AMD laptops (e.g. AMD and newer Intel Framework laptops), some of which do not support ACPI S3 sleep, to enter low power states to increase battery life.

Suspending and resuming is working on the Framework 13 AMD Ryzen 7040 series, though the deepest S0ix state (S0i3), necessary for significant power savings, cannot yet be entered on AMD systems. The major blocker for this at the moment is being able to suspend all the USB4 routers correctly, without which the power management firmware will refuse to enter S0i3. USB4 suspend support in FreeBSD is necessary as the BIOS wakes them up and runs a pre-OS connection manager for USB4 to work before an OS loads with its own connection manager, so they start off in an awake state.

Work has been picked up from the initial USB4 driver Scott Long started writing, but it is not yet at a stage where the routers are being fully suspended.

An amdsmu driver was written to read last suspend statistics and sleep-state residency counters (which were unavailable in the ACPI _LPI objects). The SMU is a small coprocessor on AMD CPUs which runs the power management firmware and is ultimately what decides to enter S0i3 or not. These statistics can tell us if the system entered S0i3 during the last suspend, how much time it took to enter, and which proportion of suspended time was spent in S0i3.

Sponsor: The FreeBSD Foundation

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

Syzkaller Improvement for WiFi on FreeBSD

Links:
google/syzkaller URL: https://github.com/google/syzkaller
work repository URL: https://github.com/estarriol43/syzkaller/tree/freebsd/frame-injection-v2

Contact: Jian-Lin Li <ljianlin99@gmail.com>
Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>

Syzkaller is an operating system kernel fuzzer that can look for vulnerabilities in the kernel.

This project aims to improve the support of Syzkaller on FreeBSD. Based on the existing WiFi fuzzer designed for Linux, we drafted a WiFi fuzzer for FreeBSD. We planned to use wtap(4), a virtual wifi interface for testing, in order to support WiFi fuzzing.

Some of the design details include:

• Initialize wtap devices in Syzkaller before WiFi fuzzing

• Inject 802.11 frames via the existing ioctl interface provided by wtap

• Inject 802.11 frames via the Netlink interface, which is not supported by
FreeBSD for now

We have developed a WiFi fuzzer using existing ioctl interface provided by wtap. One can check out the result in this branch.

We hope to introduce Netlink interface, which is adopted by the Syzkaller to inject 802.11 frames into Linux kernel, to FreeBSD to improve the compatibilities between Linux and FreeBSD.

Sponsor: The FreeBSD Foundation

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

LinuxKPI 802.11 Wireless Update

Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
Contact: The FreeBSD wireless mailing list <wireless@FreeBSD.org>

With multiple wireless projects ongoing, this report focuses on the efforts using permissively licensed Linux wireless drivers mostly unmodified on FreeBSD. The currently supported drivers are iwlwifi(4), rtw88(4), and rtw89(4) .

The rtw88(4) driver was made to work (associate) again (Bugzilla PR#283142). In addition, thanks to the massive help debugging and testing by the community, the cause for leaking memory got resolved (Bugzilla PR#283903).

Tunables to selectively control HT and VHT support in rtw88(4), and rtw89(4) were added. HW crypto offload was enabled by default for CCMP. It turns out that a lot of users are still using TKIP. Work is in on the way to support this and will hopefully land early in Q2.

HT (11n) and VHT (11ac) support are now also compiled in by default for the LinuxKPI based drivers. The drivers and entire framework changes were merged from main to stable/14 so both branches have the same level of support.

People installing firmware using fwget(8) will get HT and VHT automatically enabled for iwlwifi(4) 2200 (mostly AX200), AX210, and BE200 chipset generations. Older iwlwifi(4) chipset generations, rtw88(4), and rtw89(4) will need extra work in LinuxKPI or the driver to provide working support.

It was announced that iwlwififw(4) will follow rtw88(4), and rtw89(4) firmware and be removed from the base system in April 2025 for both main and stable/14 in favor of the ports based solution and fwget(8) support (Announcement).

Sponsor: The FreeBSD Foundation

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

Wireless Update

Contact: Tom Jones <thj@FreeBSD.org>
Contact: The FreeBSD wireless mailing list <wireless@FreeBSD.org>

At the end of 2024 Future Crew LLC provided the source for their iwx port from OpenBSD. I opted to merge the two drivers together using the Future Crew driver as a base and importing my modifications.

I worked on this driver, tidying up and removing a lot of development code and expanding support for more devices. iwx in FreeBSD should now attach to any device supported by OpenBSD. Firmware is available thanks to bz@ in the net/ wifi-firmware-iwlwifi-kmod package.

iwx landed in FreeBSD on the final day of the quarter. iwx probes with a lower priority than iwlwifi to avoid breaking deployed configurations.

iwx supports legacy, HT and VHT rates and some users have reported significant throughputs in test. There remain many issues around rate selection and development is continuing.

Sponsor: The FreeBSD Foundation

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

Architectures

Updating platform-specific features and bringing in support for new hardware platforms.

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

Pinephone Pro Support

Links:
Repository on Codeberg URL: https://codeberg.org/Honeyguide/freebsd-pinephonepro

Contact: Toby Kurien <toby@tobykurien.com>

The project to port FreeBSD over to the Pinephone Pro is progressing. The aim of this project is to step by step support components of the Pinephone Pro in FreeBSD so that the device one day might be usable as a highly mobile FreeBSD device. In this quarter, console output to the screen was enabled, using EFI framebuffer support. This requires using a specific version of U-boot that sets up the EFI framebuffer, which FreeBSD’s kernel is then able to use for output while booting up. While this comes with limitations (like no hardware acceleration), it is a big step forward in making FreeBSD usable on the PinePhone Pro. To make it easier to try the current code changes out, a script was added to the repository to create a flashable image for booting from an SD card. This script downloads and patches a FreeBSD CURRENT mini-memstick image with the custom device tree and kernel. The resulting image can then be copied to an SD card using dd and booted up on the phone. See the repo for details.

Work on enabling the USB port was started but has stalled and help is needed, particularly from someone who understands the USB subsystem and can help move this forward. Currently, some USB controllers are detected by FreeBSD but no USB devices are visible, e.g. the internally connected modem. Help is also needed to port the WiFi driver from Linux, which would be the same driver needed for Raspberry Pi 3b+/4/5 (Broadcom 43455 wifi module connected via SDIO). Anyone wanting to assist can contact me by e-mail.

See the post on the FreeBSD Forum for more: https://forums.freebsd.org/threads/porting-freebsd-to-pinephone-pro-help-needed.95948/

Sponsor: Honeyguide Group

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

Cloud

Updating cloud-specific features and bringing in support for new cloud platforms.

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

FreeBSD on Microsoft HyperV and Azure

Links:
Microsoft Azure article on FreeBSD wiki URL: https://wiki.freebsd.org/MicrosoftAzure
Microsoft HyperV article on FreeBSD wiki URL: https://wiki.freebsd.org/HyperV

Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> Contact: freebsd-cloud Mailing List
Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> Contact: Wei Hu <whu@FreeBSD.org>, <weh@microsoft.com>
Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com>
Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>

In this quarter, we have published the 13.5-RELEASE on Azure Marketplace.

Wei Hu continues bug fixing for FreeBSD MANA NIC device.

Work in progress tasks:

• Automating the image publishing process and merging to src/release/.

• Making the process of publishing to Azure Marketplace more smoothly.

• Support FreeBSD in Azure VM utilities.

Open tasks:

• Update FreeBSD-related doc at Microsoft Learn

• Update sysutils/azure-agent to the latest version

• Upstream local modifications of Azure agent

• Port Linux Virtual Machine Extensions for Azure

• Adding FreeBSD support in Azure Pipelines

□ https://github.com/microsoft/azure-pipelines-agent/pull/3266

□ Building and publishing snapshot builds to Azure community gallery.

Sponsor: Microsoft for people in Microsoft, and for resources for the rest Sponsor: The FreeBSD Foundation for everything else

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

Containers and FreeBSD: Cloud Native Buildpacks

Links:
Cloud Native Buildpacks (CNBs) URL: https://buildpacks.io/
GitHub Buildpacks repository URL: https://github.com/buildpacks/pack

Contact: Robert Gogolok <gogolok@gmail.com>

Cloud Native Buildpacks (CNBs) transform application source code into container images. Those images can run on any cloud. With buildpacks, organizations can concentrate the knowledge of container build best practices within a specialized team, instead of having application developers across the organization individually maintain their own Dockerfiles.

My goal for this quarter was to enable building the tool pack on FreeBSD.

With the following changes, it is now possible to compile pack on FreeBSD:

• Remove obsolete // +build lines #2337

• Use unix build constraint #2339

• Support FreeBSD build phase #2357

The next steps are:

• Provide missing FreeBSD functionality to lifecycle and pack.

• Further investigate FreeBSD as a build target in lifecycle.

• Provide lifecycle and/or pack via FreeBSD ports.

• Investigate the idea of FreeBSD buildpacks for some popular languages,
similar to paketo buildpacks.

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

FreeBSD on EC2

Links:
EC2 Boot performance over time URL: https://www.daemonology.net/freebsd-ec2-boot-performance/

Contact: Colin Percival <cperciva@FreeBSD.org>

FreeBSD is available on both amd64 (Intel and AMD) and arm64 (Graviton) EC2 instances.

In the past quarter, considerable effort has gone into making "hot unplug" (e.g. detaching EBS volumes) work correctly, with several different fixes required on different instance types. This is expected to be fully functional in the upcoming FreeBSD 14.3.

Sponsor: Amazon
Sponsor: https://www.patreon.com/cperciva

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

Documentation

Noteworthy changes in the documentation tree, manual pages, or new external books/documents.

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

Documentation Engineering Team

Links:
FreeBSD Documentation Project URL: https://www.freebsd.org/docproj/url
FreeBSD Documentation Project Primer for New Contributors URL: https://docs.freebsd.org/en/books/fdp-primer/url
Documentation Engineering Team URL: https://www.freebsd.org/administration/#t-docengurl

Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>

The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see FreeBSD Doceng Team Charter.

Document changes

Handbook

• The Filesystems chapter has been reworked.

• The information about official mirrors have been updated.

• Multiple examples have been updated including vnet, jails, git, etc.

Porter’s Handbook

The following USES were documented:

• ansible

• angr

• apache

• azurepy

• electronfix

• elixir

• emacs

• fpc

• jpeg

• kodi

• lazarus

• mlt

• mpi

• ocaml

• trigger

• waf

New variables were documented for USES=samba:

• SAMBA_TALLOC_PORT,

• SAMBA_TDB_PORT

• SAMBA_TEVENT_PORT

Website

• Manual pages for NetBSD 10.1 have been added.

• Manual pages for Rocky Linux 8.10, 9.4 and 9.5 have been added.

• Manual pages for FreeBSD 13.5 have been added.

• Pages for OpenSolaris 2010.03 have been added.

FreeBSD Translations on Weblate

Links:
Translate FreeBSD on Weblate URL: https://wiki.freebsd.org/Doc/Translation/Weblateurl
FreeBSD Weblate Instance URL: https://translate-dev.freebsd.org/url

Q3 2024 Status

• 18 team languages

• 246 registered users

7 new translators joined Weblate:

• Squirrel-hue (ES, ES_CL)

• Javier Faig (ES)

• Сергей (RU)

• Renan Birck Pinheiro (PT)

• Davi Rodrigues (PT)

• laiis akibo

• Raoul Taddei (FR_FR)

Languages

• Chinese (Simplified) (zh-cn) (progress: 7%)

• Chinese (Traditional) (zh-tw) (progress: 3%)

• Dutch (nl) (progress: 1%)

• French (fr) (progress: 1%)

• German (de) (progress: 1%)

• Greek (el) (progress: 1%)

• Indonesian (id) (progress: 1%)

• Italian (it) (progress: 4%)

• Korean (ko) (progress: 30%)

• Norwegian (nb-no) (progress: 1%)

• Persian (fa-ir) (progress: 2%)

• Polish (progress: 2%)

• Portuguese (progress: 0%)

• Portuguese (pt-br) (progress: 23%)

• Spanish (es) (progress: 36%)

• Turkish (tr) (progress: 2%)

We want to thank everyone that contributed, translating or reviewing documents.

And please, help promote this effort on your local user group, we always need more volunteers.

Packages maintained by DocEng

During this quarter the following work was done in packages maintained by doceng@:

• www/gohugo: updated to 0.145.0

Open issues

There are no open PRs assigned to doceng@.

During this quarter the following PR was closed:

• 276923 www/gohugo link error under poudriere

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

FreeBSD Wiki

Links:
FreeBSD wiki front page URL: https://wiki.freebsd.org/FrontPage

Contact: Mark Linimon <linimon@FreeBSD.org>
Contact: Wiki admin <wiki-admin@FreeBSD.org>

The wiki team needs new blood.

Since the last status report (2024Q3) forward progress has stalled. We have given out several dozen new accounts but most of the changes by these new authors have been to individual pages, not to the overall structure.

Mark Linimon still thinks the wiki could be a great resource if people were willing to put time into it. But right now, there are more complaints about stale data than there are new contributors and new ideas.

It is fair to say that right now, the wiki is on autopilot.

Previous plans that have stalled

Preliminary work was being done on updating the wiki software itself. Earlier, we were looking at switching implementations because MoinMoin development seemed to have stalled, leaving us with an unwanted hanging python2 dependency. However, MoinMoin now claims that they are nearing a 2.0 release. We have not yet tried an install of their latest beta version to test compatibility.

Specific short-term requests for help

If anyone knows about MoinMoin markup, contact Mark.

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

Vision Accessibility — Accessibility Handbook

Link:
Project Repository URL: https://gitlab.com/alfix/freebsd-accessibility

Contact: FreeBSD Accessibility mailing list <freebsd-accessibility@FreeBSD.org> Contact: Alfonso Sabato Siciliano <asiciliano@FreeBSD.org>

The FreeBSD Foundation is supporting a series of projects to enhance accessibility for users with visual impairments.

FreeBSD offers several assistive technologies, thanks to the dedicated work of contributors and committers. An ongoing effort focuses on listing and documenting these accessibility features in a new handbook. Currently, the project centers on documenting features for blind, low-vision, and colorblind users, covering both PORTS and BASE system functionalities. For example: ports for screen magnification, screen readers (which aid users who cannot see the screen), as well as tools for adjusting colors in desktop environments. Additionally, accessibility features available in the BASE system to enhance visibility are also being documented with examples and tips: such as the

[continued in next message]

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