git: 6b006b34bf - main - status/report-2022-01-2022-03: Add report
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 09 Jun 2022 20:25:59 UTC
The branch main has been updated by salvadore (ports committer):
URL: https://cgit.FreeBSD.org/doc/commit/?id=6b006b34bf9bf198e037cebc430a34cbf635bdb3
commit 6b006b34bf9bf198e037cebc430a34cbf635bdb3
Author: Lorenzo Salvadore <salvadore@FreeBSD.org>
AuthorDate: 2022-06-03 21:37:41 +0000
Commit: Lorenzo Salvadore <salvadore@FreeBSD.org>
CommitDate: 2022-06-09 20:25:49 +0000
status/report-2022-01-2022-03: Add report
Reviewed by: grahamperrin,
Pau Amma <pauamma@gundo.com>
Approved by: gerald (mentor), debdrup (status blanket)
Differential Revision: https://reviews.freebsd.org/D35402
---
website/content/en/status/_index.adoc | 6 +-
.../en/status/report-2022-01-2022-03/_index.adoc | 142 +++++++++++++++
.../report-2022-01-2022-03/accessibility.adoc | 20 +++
.../report-2022-01-2022-03/boot-performance.adoc | 38 ++++
.../en/status/report-2022-01-2022-03/ci.adoc | 53 ++++++
.../status/report-2022-01-2022-03/clusteradm.adoc | 49 ++++++
.../en/status/report-2022-01-2022-03/doceng.adoc | 100 +++++++++++
.../en/status/report-2022-01-2022-03/dpaa2.adoc | 39 +++++
.../en/status/report-2022-01-2022-03/ena.adoc | 26 +++
.../en/status/report-2022-01-2022-03/fpart.adoc | 38 ++++
.../report-2022-01-2022-03/freebsd-foundation.adoc | 193 +++++++++++++++++++++
.../en/status/report-2022-01-2022-03/gcc.adoc | 28 +++
.../en/status/report-2022-01-2022-03/gunion.adoc | 23 +++
.../status/report-2022-01-2022-03/hellosystem.adoc | 28 +++
.../en/status/report-2022-01-2022-03/intro.adoc | 11 ++
.../en/status/report-2022-01-2022-03/iwlwifi.adoc | 26 +++
.../en/status/report-2022-01-2022-03/kde.adoc | 49 ++++++
.../en/status/report-2022-01-2022-03/ocf-wg.adoc | 17 ++
.../en/status/report-2022-01-2022-03/office.adoc | 25 +++
.../status/report-2022-01-2022-03/portconfig.adoc | 24 +++
.../en/status/report-2022-01-2022-03/portmgr.adoc | 51 ++++++
.../en/status/report-2022-01-2022-03/pot.adoc | 23 +++
.../en/status/report-2022-01-2022-03/releng.adoc | 21 +++
.../en/status/report-2022-01-2022-03/rtw88.adoc | 24 +++
.../en/status/report-2022-01-2022-03/wifibox.adoc | 50 ++++++
website/data/en/news/news.toml | 5 +
26 files changed, 1108 insertions(+), 1 deletion(-)
diff --git a/website/content/en/status/_index.adoc b/website/content/en/status/_index.adoc
index a13ad654cc..2c66dfee07 100644
--- a/website/content/en/status/_index.adoc
+++ b/website/content/en/status/_index.adoc
@@ -5,7 +5,7 @@ sidenav: about
= FreeBSD Status Reports
-== Next Quarterly Status Report submissions (January - March) due: March 31st, 2022
+== Next Quarterly Status Report submissions (April - June) due: June 30th, 2022
Submit your entries as Pull Requests from your fork of link:https://github.com/freebsd/freebsd-quarterly[FreeBSD Status Report GitHub repo] or submit them via e-mail to quarterly-submissions@FreeBSD.org, using the link:https://github.com/freebsd/freebsd-quarterly/blob/master/report-sample.adoc[report-sample.adoc template].
@@ -21,6 +21,10 @@ Periodically, special status reports are prepared and published. One of those ar
These status reports may be reproduced in whole or in part, as long as the source is clearly identified and appropriate credit given.
+== 2022
+
+* link:report-2022-01-2022-03/[January, 2022 - March, 2022]
+
== 2021
* link:report-2021-10-2021-12/[October, 2021 - December, 2021]
diff --git a/website/content/en/status/report-2022-01-2022-03/_index.adoc b/website/content/en/status/report-2022-01-2022-03/_index.adoc
new file mode 100644
index 0000000000..40e43c766f
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/_index.adoc
@@ -0,0 +1,142 @@
+---
+title: "FreeBSD Quarterly Status Report First Quarter 2022"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2022-01-2022-03
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+Entries from the various official and semi-official teams, as found in the
+link:../../administration/[Administration Page].
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+Projects that span multiple categories, from the kernel and userspace to the
+Ports Collection or external projects.
+
+include::{reports-path}/accessibility.adoc[]
+
+'''
+
+include::{reports-path}/boot-performance.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+Updates to kernel subsystems/features, driver support, filesystems, and more.
+
+include::{reports-path}/ena.adoc[]
+
+'''
+
+include::{reports-path}/gunion.adoc[]
+
+'''
+
+include::{reports-path}/rtw88.adoc[]
+
+'''
+
+include::{reports-path}/iwlwifi.adoc[]
+
+'''
+
+include::{reports-path}/ocf-wg.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+Noteworthy changes in the documentation tree, man-pages, or new external
+books/documents.
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+Changes affecting the Ports Collection, whether sweeping changes that touch most
+of the tree, or individual ports themselves.
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/office.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/portconfig.adoc[]
+
+'''
+
+include::{reports-path}/wifibox.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+Many projects build upon FreeBSD or incorporate components of FreeBSD into their
+project. As these projects may be of interest to the broader FreeBSD community,
+we sometimes include brief updates submitted by these projects in our quarterly
+report. The FreeBSD project makes no representation as to the accuracy or
+veracity of any claims in these submissions.
+
+include::{reports-path}/hellosystem.adoc[]
+
+'''
+
+include::{reports-path}/pot.adoc[]
+
+'''
+
+include::{reports-path}/fpart.adoc[]
diff --git a/website/content/en/status/report-2022-01-2022-03/accessibility.adoc b/website/content/en/status/report-2022-01-2022-03/accessibility.adoc
new file mode 100644
index 0000000000..f91908d2c8
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/accessibility.adoc
@@ -0,0 +1,20 @@
+=== FreeBSD Accessibility
+
+Links: +
+link:https://wiki.freebsd.org/Accessibility[Accessibility wiki page] URL: link:https://wiki.freebsd.org/Accessibility[https://wiki.freebsd.org/Accessibility] +
+link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html[List introduction, goals, audience, and ground rules] URL: link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html[link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html] +
+
+Contact: Pau Amma <pauamma@gundo.com> +
+Contact: FreeBSD accessibility discussions <freebsd-accessibility@freebsd.org>
+
+Over the past several months, I've started putting together tools and resources to help make the FreeBSD ecosystem (more) accessible to people with disabilities:
+
+* a link:https://lists.freebsd.org/subscription/freebsd-accessibility[mailing list]
+* a link:https://wiki.freebsd.org/Accessibility[set of wiki pages] including link:https://wiki.freebsd.org/Accessibility/Resources[resources] and a link:https://wiki.freebsd.org/Accessibility/Wishlist[categorized wish list]
+* tooling including a link:https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=accessibility&list_id=471790&resolution=---[searchable accessibility Bugzilla keyword] and an link:https://reviews.freebsd.org/project/profile/87/[accessibility Phabricator group]
+
+I need all the help I can get with:
+
+* specifying, designing, implementing, and testing the items on the wishlist
+* adding to the wishlist in areas were have little or no experience or for things I missed
+* moving beyond software and documentation to processes and culture
diff --git a/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc b/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc
new file mode 100644
index 0000000000..3d0503f1cc
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc
@@ -0,0 +1,38 @@
+=== Boot Performance Improvements
+
+Links: +
+link:https://wiki.freebsd.org/BootTime[Wiki page] URL: link:https://wiki.freebsd.org/BootTime[https://wiki.freebsd.org/BootTime] +
+link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html[OS boot time comparison] URL: link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html[https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html]
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+Colin Percival is coordinating an effort to speed up the FreeBSD boot process.
+For benchmarking purposes, he is primarily using an EC2 c5.xlarge instance as a
+reference platform and is measuring the time between when the virtual machine
+enters the EC2 "running" state and when it is possible to SSH into the instance.
+
+This work started in 2017, and as of the end of December 2021 the FreeBSD boot
+time was reduced from approximately 30 seconds to approximately 10 seconds.
+During 2022Q1, further improvements have shaved more time off the boot process,
+taking it down to roughly 8 seconds.
+
+Two major issues remain outstanding:
+
+. The first time an EC2 instance boots, dhclient takes about 2 seconds longer
+than normal to get an IPv4 address. The cause of this is unknown and requires
+investigation.
+
+. IPv6 configuration includes two one-second-long sleep(1) invocations, one
+from /etc/rc.d/netif and the other from /etc/rc.d/rtsold. It might be possible
+to simply remove these; but care is needed to avoid progressing too far in the
+boot process before IPv6 addresses are configured. Input from IPv6 experts
+is required here.
+
+Issues are listed on the wiki page as they are identified; the wiki page also
+has instructions for performing profiling. Users are encouraged to profile
+the boot process on their own systems, in case they experience delays which
+don't show up on the system Colin is using for testing.
+
+This work is supported by Colin's FreeBSD/EC2 Patreon.
+
+Sponsor: https://www.patreon.com/cperciva
diff --git a/website/content/en/status/report-2022-01-2022-03/ci.adoc b/website/content/en/status/report-2022-01-2022-03/ci.adoc
new file mode 100644
index 0000000000..78afdb4e4a
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/ci.adoc
@@ -0,0 +1,53 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[https://ci.FreeBSD.org] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[https://artifact.ci.FreeBSD.org] +
+link:https://wiki.freebsd.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.freebsd.org/Jenkins[https://wiki.freebsd.org/Jenkins] +
+link:https://wiki.freebsd.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.freebsd.org/HostedCI[https://wiki.freebsd.org/HostedCI] +
+link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.freebsd.org/3rdPartySoftwareCI[https://wiki.freebsd.org/3rdPartySoftwareCI] +
+link:https://preview.tinyurl.com/y9maauwg[Tickets related to freebsd-testing@] URL: link:https://preview.tinyurl.com/y9maauwg[https://preview.tinyurl.com/y9maauwg] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[https://github.com/freebsd/freebsd-ci]+
+link:https://lists.freebsd.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.freebsd.org/subscription/dev-ci[https://lists.freebsd.org/subscription/dev-ci]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[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 link:https://artifact.ci.FreeBSD.org[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 first quarter of 2022, we continued working with the contributors and developers in the project to fulfil their testing needs and also keep collaborating with external projects and companies to improve their products and FreeBSD.
+
+Important changes:
+
+* link:https://ci.freebsd.org/job/FreeBSD-main-amd64-dtrace_test/[DTrace tests] are running with KASAN now.
+* Fixed and resumed the powerpc64le test jobs.
+
+Retired jobs:
+
+* The jobs of main branch on mips* were removed.
+
+Work in progress and open tasks:
+
+* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does
+* Collecting and sorting CI tasks and ideas link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[here]
+* Testing and merging pull requests in link:https://github.com/freebsd/freebsd-ci/pulls[the FreeBSD-ci repo]
+* Reducing the procedures of CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Setting up public network access for the VM guest running tests
+* Implementing using 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
+* Improving maturity of the hardware lab and adding more hardware under test
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.freebsd.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://preview.tinyurl.com/y9maauwg[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-01-2022-03/clusteradm.adoc b/website/content/en/status/report-2022-01-2022-03/clusteradm.adoc
new file mode 100644
index 0000000000..c78e7c0543
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/clusteradm.adoc
@@ -0,0 +1,49 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[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:
+
+* Improved web service performance and security
+** Moved some critical services to newer machines
+** Swept all services to ensure the support of TLS v1.2 and v1.3 and disable v1 and v1.1
+** Enabled dual-stack certificates for the primary FreeBSD web services. +
+ ECDSA and RSA certificates, preferring ECDSA, discussed with secteam@, benefit the project in favor of security and performance matter.
+* Infrastructure improvements at primary site
+** Evicted some very old hardware
+** Moved cluster internal services to newer hardware
+*** Build host
+*** Parts of LDAP, kerberos, DNS and NTP
+* Installed an additional aarch64 package builder
+** ampere3.nyi.freebsd.org
+** Identical specs to ampere[12].nyi.freebsd.org
+* Moved ftp0.nyi.freebsd.org to an aarch64 machine.
+* Main distributed mirror site, download.freebsd.org, enhancements
+** Updated link:https://download.freebsd.org/doc/[offline documentation] (PDF and HTML) in the mirrors. +
+ The old directory `/doc` is now on link:http://ftp-archive.freebsd.org/mirror/FreeBSD-Archive/old-docs/[ftp-archive]; it contains files prior to the Hugo/Asciidoctor migration.
+** Moved ports INDEX files to distributed mirror, download.freebsd.org
+** Removed `/ftp` from the canonical URLs of files on download.freebsd.org. +
+ Old URLs are still valid.
+* Cleanup of Handbook/Mirrors section +
+ Much stale information; now there is more info about the official mirrors and locations. Former official mirrors are now named 'Community mirrors'.
+* Ongoing day to day cluster administration
+** Cluster refresh
+** Replacing failed disks
+** Babysitting pkgsync
+
+Work in progress:
+
+* Improve the package building infrastructure
+* Review the service jails and service administrators operation
+* Set up powerpc pkgbuilder/ref/universal machines
+* Search for more providers that can fit the requirements for a link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] or a link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny mirror]
+* Work with doceng@ to improve https://www.freebsd.org and https://docs.freebsd.org
+* Improve the web service architecture
+* Improve the cluster backup plan
+* Improve the log analysis system
+* Set up Australia mirror
+* Hardware refresh
diff --git a/website/content/en/status/report-2022-01-2022-03/doceng.adoc b/website/content/en/status/report-2022-01-2022-03/doceng.adoc
new file mode 100644
index 0000000000..cc74e6d63a
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/doceng.adoc
@@ -0,0 +1,100 @@
+////
+Quarter: 1st quarter of 2022
+Prepared by: dbaio
+Reviewed by: carlavilla
+Last edit: $Date: 2022-04-09 09:51:36 -0300 (Sat, 09 Apr 2022) $
+Version: $Id: doceng-2022-1st-quarter-status-report.adoc 221 2022-04-09 12:51:36Z dbaio $
+////
+
+=== Documentation Engineering Team
+
+Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] +
+Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] +
+Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team]
+
+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 link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+No new documentation commit bit was granted during the last quarter, and only one commit bit was safe kept.
+
+Several tasks were completed related to the doc tree during the last quarter:
+
+* Fix some issues in the translation workflow with PO files and Weblate related to the po4a program.
++
+More info link:https://lists.freebsd.org/archives/freebsd-translators/2022-February/000029.html[here].
+
+* Update link:https://download.freebsd.org/doc/[offline documentation (PDF and HTML)].
++
+The old directory /doc is now on link:http://ftp-archive.freebsd.org/mirror/FreeBSD-Archive/old-docs/[ftp-archive]; it contains files prior to the Hugo/Asciidoctor migration.
+
+* Remove Google Analytics from documentation and website.
+
+* Add last modified information to the documentation and website pages.
+
+* Tag FreeBSD docset for 13.1-RELEASE.
+
+* Add the first Indonesian translation to the doc tree.
+
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance]
+
+The translation workflow with Weblate is more mature at this point.
+Several issues were fixed between PO files and po4a program.
+
+We welcome everyone to try our Weblate instance to translate a few documents.
+
+The first Indonesian translation was added to the FreeBSD project.
+We thank Azrael JD for the contribution, and we are looking forward to seeing more Indonesian translations.
+
+===== Q1 2022 Status
+
+* 12 languages (1 new language)
+* 142 registered users
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)
+* Chinese (Traditional) (zh-tw)
+* Dutch (nl)
+* French (fr)
+* German (de)
+* Indonesian (id) - Added
+* Italian (it)
+* Norwegian (nb-no)
+* Persian (fa-ir)
+* Portuguese (pt-br)
+* Spanish (es)
+* Turkish (tr)
+
+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.
+
+
+==== FreeBSD Website Revamp - WebApps working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components.
+FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21.
+The work will be divided into four phases:
+
+. Redesign of the Documentation Portal
++
+Create a new design, responsive and with global search. (_Complete_)
+
+. Redesign of the Manual Pages on web
++
+Scripts to generate the HTML pages using mandoc. (_Work in progress_)
+
+. Redesign of the Ports page on web
++
+Ports scripts to create an applications portal. (_Work in progress_)
+
+. Redesign of the FreeBSD main website
++
+New design, responsive and dark theme. (_Not started_)
diff --git a/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc b/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc
new file mode 100644
index 0000000000..3ccc689b10
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc
@@ -0,0 +1,39 @@
+== NXP DPAA2 support
+
+Links +
+link:https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[Development] URL: https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2] +
+
+Contact: Dmitry Salychev <dsl@mcusim.org> +
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+Some of the NXP SoCs (LX2160A, LS1088A) are shipped with
+link:https://www.nxp.com/design/qoriq-developer-resources/second-generation-data-path-acceleration-architecture-dpaa2:DPAA2[DPAA2],
+the second generation of the data path acceleration architecture. It allows to
+dynamically configure and wire packet processing "objects" (like DPNI for a
+network interface, DPMAC for media access controller, etc.) together to form a
+network-on-a-chip.
+
+link:https://solidrun.atlassian.net/wiki/spaces/developer/pages/197494288/HoneyComb+LX2+ClearFog+CX+LX2+Quick+Start+Guide[Honeycomb LX2],
+as one of the powerful ARM64 boards from SolidRun, is also built around NXP
+LX2160A and lacks on-board GbE support in FreeBSD. These drivers are about to
+change it.
+
+It's still work in progress and a rough implementation of the drivers for some
+DPAA2 objects is available at the moment. A new network interface (dpni) can be
+used on Honeycomb for testing.
+
+TODO:
+
+* Update dpaa2_mc_fdt driver for the link:https://www.crowdsupply.com/traverse-technologies/ten64[Traverse Ten64] board
+
+* Review and fix DPAA2 resources allocation to support as many DPNIs as possible
+
+* Free driver resources properly
+
+* Implement CPU affinity for DPIOs and DPNIs
+
+* Implement cached memory-backed software portals
+
+* Profile and mitigate bottlenecks
+
+Sponsor: Bare Enthusiasm :)
diff --git a/website/content/en/status/report-2022-01-2022-03/ena.adoc b/website/content/en/status/report-2022-01-2022-03/ena.adoc
new file mode 100644
index 0000000000..4f2edefd50
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/ena.adoc
@@ -0,0 +1,26 @@
+=== ENA FreeBSD Driver Update
+
+Links: +
+link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README[ENA README] URL: link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README[https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README]
+
+Contact: Michal Krawczyk <mk@semihalf.com> +
+Contact: Dawid Gorecki <dgr@semihalf.com> +
+Contact: Marcin Wojtas <mw@semihalf.com>
+
+ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS).
+The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used.
+
+Completed since the last update:
+
+* Add IPv6 layer 4 checksum offload support to the driver
+* Add NUMA awareness to the driver when the RSS kernel option is enabled
+* Rework validation of the Tx request ID
+* Change lifetime of the driver's timer service
+* Avoid reset triggering when the device is unresponsive
+
+Work in progress:
+
+* Prototype the driver port to the iflib framework
+* Tests of the incoming ENA driver release (v2.5.0)
+
+Sponsor: Amazon.com Inc
diff --git a/website/content/en/status/report-2022-01-2022-03/fpart.adoc b/website/content/en/status/report-2022-01-2022-03/fpart.adoc
new file mode 100644
index 0000000000..ecd0a060ff
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/fpart.adoc
@@ -0,0 +1,38 @@
+=== Fpart and fpsync
+
+Links: +
+link:https://www.fpart.org[Project site and documentation] URL: link:https://www.fpart.org[https://www.fpart.org] +
+link:https://github.com/martymac/fpart[Development] URL: link:https://github.com/martymac/fpart[https://github.com/martymac/fpart] +
+link:https://www.freshports.org/sysutils/fpart[Port] URL: link:https://www.freshports.org/sysutils/fpart[https://www.freshports.org/sysutils/fpart]
+
+Contact: Ganael Laplanche <martymac@FreeBSD.org>
+
+==== What is fpart ?
+
+Fpart is a *filesystem partitioner*. It helps you sort file trees and pack them into bags ("partitions").
+
+It uses FreeBSD's fts(3) implementation (GNU/Linux builds can also use it as an option), which makes it crawl filesystems very fast.
+
+A hook facility is provided to trigger actions on the partitions produced.
+
+==== What is fpsync ?
+
+Fpsync is a companion script that uses fpart under the hood to parallelize rsync(1) or cpio(1) jobs, making it a simple but powerful data migration tool. Those jobs can be run either locally or remotely (using SSH). Fpsync is link:https://www.fpart.org/links/[often used by researchers and cloud providers] where lots of data need to be moved and clusters are available to speed up transfers.
+
+==== Q1 2022 Status
+
+Both tools continued to evolve and saw several bugs fixed; see the link:https://www.fpart.org/changelog/[changelog].
+
+Also, a user reported a major bug regarding our fts(3) implementation, which ignores readdir(3) errors. I have reported the bug in our Bugzilla:
+
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262038[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262038]
+
+It should be merged soon (hopefully).
+
+Last but not least, fpart has been link:https://sill.etalab.gouv.fr/fr/software?id=229[referenced in the French Government's 'SILL'].
+
+==== Contributing
+
+If you are interested in contributing, have a look at the link:https://github.com/martymac/fpart/blob/master/TODO[TODO list].
+
+Any contribution is welcome, more especially in the field of unit testing.
diff --git a/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc b/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc
new file mode 100644
index 0000000000..71be9af883
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc
@@ -0,0 +1,193 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://www.FreeBSDfoundation.org[FreeBSD Foundation] URL: link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://FreeBSDFoundation.org/blog/technology-roadmap/] +
+link:https://www.FreeBSDfoundation.org/donate/[Donate] URL: link:https://www.FreeBSDfoundation.org/donate/[https://www.FreeBSDFoundation.org/donate/] +
+link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program[https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program] +
+link:https://www.FreeBSDfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDFoundation.org/journal/] +
+link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[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.
+
+Here are some highlights from the Foundation for the first quarter of
+2022.
+
+==== Fundraising Efforts
+
+As promised, we updated our fundraising meter for 2022. So far, we’ve
+raised over $84,000 towards our 2022 goal of $1,400,000. We’d like to
+thank our individual and corporate donors for supporting our efforts
+this year. We’d also like to give a big shout out to our Gold Sponsor,
+Facebook, Silver Sponsors, VMware and Tarsnap, and the companies that
+provide free hosting for the Project: Bytemark, 365 Data Centers, NYI,
+NextArray, Sentex Data Communications, and the Computer Science
+Department at NCTU.
+
+You can find out how we spent your donations by reading about what we
+supported in Q1, in this report, and our Spring Newsletter.
+
+If you haven’t made a donation this year, please consider making a donation
+now at https://freebsdfoundation.org/donate/.
+
+We also have a Partnership Program for larger commercial donors. You can
+find out more at
+https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/
+
+==== OS Improvements
+
+During the first quarter of 2022, 372 src, 41 ports, and 16 doc tree
+commits were made that identified The FreeBSD Foundation as a sponsor.
+# This represents 16, 0.4, and 5% of the total number of commits in each repository.
+
+You can read about Foundation-sponsored projects in individual quarterly report
+entries:
+
+* Crypto changes for WireGuard
+* Intel Wireless driver support
+
+Here is a small sample of other base system improvements from Foundation
+developers this quarter that do not have separate report entries.
+
+==== riscv: Add support for enabling SV48 mode
+
+SV48 is intended for systems for which a 39-bit virtual address space is
+insufficient. This change increases the size of the user map from 256GB
+to 128TB. The kernel map is left unchanged for now.
+
+For now SV48 mode is left disabled by default, but can be enabled with a
+tunable. Note that extant hardware does not implement SV48, but QEMU
+does.
+
+* In pmap_bootstrap(), allocate a L0 page and attempt to enable SV48
+ mode. If the write to SATP doesn't take, the kernel continues to run
+ in SV39 mode.
+* Define VM_MAX_USER_ADDRESS to refer to the SV48 limit. In SV39 mode,
+ the region [VM_MAX_USER_ADDRESS_SV39, VM_MAX_USER_ADDRESS_SV48] is not
+ mappable.
+
+==== Add v3 support to CTF tools
+
+CTF, the Compact C Type Format, is a representation of type information
+most often contained within ELF binaries. This type information is
+helpful for probing tools like DTrace. Recent work by Mark Johnston
+allows different Dtrace providers like the FBT (Function Boundary
+Tracing) provider to work with version 3 of CTF.
+
+==== FreeBSD on the Framework Laptop
+
+Two Foundation staff members, Ed Maste and Mark Johnston, as well as a few developers and community members now each have access to Framework laptops, which are designed to make hardware upgrades, repairs, and customizations straightforward for the average user. The goal of this work is to ensure that the experience running FreeBSD on the laptops matches the stability that FreeBSD users expect.
+
+Recent improvements and fixes include:
+
+* Making audio switch appropriately between speakers and the headphone jack when headphones are plugged in or unplugged
+* Fixing bug 259230, which would cause a Framework laptop to reboot or power off when the touchpad was used.
+* Adding the Tempo Semiconductor 92HD95B HDA codec ID
+* Temporarily fixing stalled usb enumeration, bluetooth, and S3 resume. The temporary fix is to avoid attaching to several newer Intel controllers, which require firmware to be loaded, which is different from that implemented by ng_ubt_intel and iwmbtfw, so they are not usable yet.
+* Avoiding a 16 second boot delay, by probing the TSC frequency earlier. This lets us use the TSC to implement early DELAY, limiting the use of the sometimes-unreliable 8254 PIT.
+
+You can follow news about FreeBSD work on the Framework laptop at: https://wiki.freebsd.org/Laptops/Framework_Laptop.
+
+==== 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.
+
+==== Supporting FreeBSD Infrastructure
+
+The Foundation provides hardware and support for the Project. At the
+time of writing, the server that will become the new Australian mirror
+has arrived in Australia, has a fresh FreeBSD install and will shortly
+join the cluster.
+
+==== FreeBSD Advocacy and Education
+
+Much of our effort is dedicated to Project advocacy. This may involve
+highlighting interesting FreeBSD work, producing literature, 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 virtual events and began planning the June 2022
+Developer Summit.
+
+Check out some of the advocacy and education work we did last quarter:
+
+* Committed to hosting a FreeBSD Workshop at SCALE 19x and serve as a Media Sponsor - July 28-31, 2022 in Los Angeles, CA
+
+* Participated in the FLOSS Weekly Podcast - January 5, 2022
+ https://twit.tv/shows/floss-weekly/episodes/662
+
+* Sent out the 2021 Impact Report showcasing how we supported the Project last year.
+ https://freebsdfoundation.org/blog/2021-freebsd-foundation-impact-report/
+
+* Hosted a stand at FOSDEM 2022 - Videos from the stand can be found at: https://youtube.com/playlist?list=PLugwS7L7NMXxwqIRg1PlhgzhNRi1eVdRQ
+
+* Participated in the Open Source Voices Podcast - Episode to be aired in late April [note from status report team: the episode has indeed be aired and is now available at https://www.opensourcevoices.org/29; unfortunately, there is and will be no transcript.]
+
+* Began planning the June 2022 FreeBSD Developers Summit taking place virtually, June 16-17, 2022 https://wiki.freebsd.org/DevSummit/202206
+
+* Held a new FreeBSD Friday - How to Track FreeBSD Using Git Pt. 2
+ https://youtu.be/Fe-dJrDMK_0
+
+* Presented at the St. Louis Unix User Group on March 9, 2022
+ https://ow.ly/1QXn50Ivj75
+
+* Served as Admins and were accepted as a mentoring organization for the 2022 Google Summer of Code
+
+* Held an Office Hours session on Google Summer of Code.
+ https://youtu.be/x-4U1xurmBE
+
+* Hosted a booth at the virtual Open Source 101 conference on March 29, 2022
+
+* New blog posts:
+
+** link:https://freebsdfoundation.org/blog/raid-z-expansion-feature-for-zfs/[RAID-Z Expansion Feature for ZFS In the Home Stretch]
+** link:https://freebsdfoundation.org/blog/whats-ahead-for-freebsd-and-the-foundation-in-2022/[What's Ahead for FreeBSD and the Foundation in 2022]
+** link:https://freebsdfoundation.org/blog/work-with-freebsd-in-google-summer-of-code/[Work with FreeBSD in Google Summer of Code]
+
+* New How-To Guide: link:https://freebsdfoundation.org/freebsd-project/resources/introduction-to-freebsd-jails/[An Introduction to FreeBSD Jails]
+
+* New FreeBSD Journal Article: link:https://freebsdfoundation.org/wp-content/uploads/2022/04/Contributing-to-FreeBSD-Ports-with-Git.pdf[Contributing to FreeBSD ports with Git]
+
+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 link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org]
+to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2022-01-2022-03/gcc.adoc b/website/content/en/status/report-2022-01-2022-03/gcc.adoc
new file mode 100644
index 0000000000..003d15a7bb
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/gcc.adoc
@@ -0,0 +1,28 @@
+=== lang/gcc* ports need some love and attention
+
+Links: +
+link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[https://gcc.gnu.org/gcc-11/]
+
+Contact: toolchain@FreeBSD.org +
+Contact: Gerald Pfeifer <gerald@pfeifer.com>
+
+After about two decades of maintaining FreeBSD's lang/gcc* ports, the time came to hand over the baton and mostly step back.
+Alas the baton essentially dropped to the floor, despite multiple calls for help.
+
+Here are a few specific tasks looking for help:
+
+ * Upgrade GCC_DEFAULT in Mk/bsd.default-versions.mk from 10 to 11,
+ including fixing the (luckily minor) fall out of an -exp run:
+ link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378]
+
+ * Three changes to work through with upstream GCC (requires src
+ expertise, not ports):
+
+ ** upstreaming lang/gcc11/patch-gets-no-more
+ ** upstreaming lang/gcc11/patch-arm-unwind-cxx-support
+ ** link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874]
+
+ * We have removed the unmaintained lang/gcc9-devel and lang/gcc10-devel
+ ports, alas kept lang/gcc11-devel and lang/gcc12-devel which would be
+ good to see if not weekly, then somewhat regular updates.
diff --git a/website/content/en/status/report-2022-01-2022-03/gunion.adoc b/website/content/en/status/report-2022-01-2022-03/gunion.adoc
new file mode 100644
index 0000000000..b0058476c7
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/gunion.adoc
@@ -0,0 +1,23 @@
+=== A New GEOM Facility, gunion
+
+Contact: Marshall Kirk McKusick <mckusick@mckusick.com>
+
+The gunion facility is used to track changes to a read-only disk on a writable disk.
+Logically, a writable disk is placed over a read-only disk.
+Write requests are intercepted and stored on the writable disk.
+Read requests are first checked to see if they have been written on the top (writable disk) and if found are returned.
+If they have not been written on the top disk, then they are read from the lower disk.
+
+The gunion facility can be especially useful if you have a large disk with a corrupted filesystem that you are unsure of how to repair.
+You can use gunion to place another disk over the corrupted disk and then attempt to repair the filesystem.
+If the repair fails, you can revert all the changes in the upper disk and be back to the unchanged state of the lower disk thus allowing you to try another approach to repairing it.
+If the repair is successful you can commit all the writes recorded on the top disk to the lower disk.
+
+Another use of the gunion facility is to try out upgrades to your system.
+Place the upper disk over the disk holding your filesystem that is to be upgraded and then run the upgrade on it.
+If it works, commit it; if it fails, revert the upgrade.
+
+The gunion(8) utility is used to create and manage an instance of a gunion. Further details and usage examples can be found in the gunion(8) manual page.
+At this time, gunion(8) is available only in 14.0.
+
+Sponsor: Netflix
diff --git a/website/content/en/status/report-2022-01-2022-03/hellosystem.adoc b/website/content/en/status/report-2022-01-2022-03/hellosystem.adoc
new file mode 100644
index 0000000000..07ba012ddd
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/hellosystem.adoc
@@ -0,0 +1,28 @@
+=== helloSystem
+
+Links: +
+link:https://hellosystem.github.io/docs/[Documentation] URL: link:https://hellosystem.github.io/[https://hellosystem.github.io/]
+
+Contact: Simon Peter <probono@puredarwin.org> +
+Contact: `\#helloSystem` on `irc.libera.chat`, mirrored to link:https://matrix.to/#/%23helloSystem:matrix.org?via=matrix.org[`#helloSystem:matrix.org` on Matrix]
+
+==== What is helloSystem?
+
+helloSystem is FreeBSD preconfigured as a desktop operating system with a focus on simplicity, elegance, and usability.
+Its design follows the “Less, but better” philosophy.
+
+==== Q1 2022 Status
+
+* Version 0.8.0 of helloSystem is under development and test
+** helloSystem 0.8.0 will be based on FreeBSD 13.1-RELEASE
+** Experimental Live ISOs using FreeBSD 13.1-BETA3 are available
+** Initial support for running Linux AppImage files using an optional Debian runtime
+** Initial support for the AppImage format in the user interface
+** Improved reliability and performance of mounted archives by using fuse-archive
+** Various bugfixes
+
+Installable experimental Live ISO images are available at https://github.com/helloSystem/ISO/releases/tag/experimental-13.1.
+
+==== Contributing
+
+link:https://github.com/helloSystem/hello/blob/master/CONTRIBUTING.md[The project appreciates contributions in various areas].
diff --git a/website/content/en/status/report-2022-01-2022-03/intro.adoc b/website/content/en/status/report-2022-01-2022-03/intro.adoc
new file mode 100644
index 0000000000..a24df1bff6
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/intro.adoc
@@ -0,0 +1,11 @@
+As things are yet again settling into a new normal, it's once again time for a status report for the FreeBSD Project.
+
+You may have noticed that this report is also a little on the late side, and it's with regret that it's taken this long to get to it - however, thanks to a few kind souls who've stepped up to the plate, in addition to the folks on the team who do things quietly in the background, future reports should hopefully be more on time.
+
+So let's get some introductions in order, as yours truly is delighted to accept a hand from Pau Amma who already has been helping with reviews for a while, Lorenzo Salvadore who is stepping up to get some tooling in place to make it less of a chore to make the reports, as well as Sergio Carlavilla who is stepping up to help with all the work that can't be easily automated.
+
+This report covers a very diverse set of topics including but not limited to accessibility, system boot speed-up, an implementation of GEOM union, changes to the WiFi situation, and many other things.
+
+We hope you'll enjoy reading it!
+
+Daniel Ebdrup Jensen, on behalf of the status report team.
diff --git a/website/content/en/status/report-2022-01-2022-03/iwlwifi.adoc b/website/content/en/status/report-2022-01-2022-03/iwlwifi.adoc
new file mode 100644
index 0000000000..f1f9990407
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/iwlwifi.adoc
@@ -0,0 +1,26 @@
+=== Intel Wireless driver support and LinuxKPI 802.11 compatibility layer
+
+Links: +
+link:https://wiki.freebsd.org/WiFi/Iwlwifi[iwlwifi status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Iwlwifi[https://wiki.freebsd.org/WiFi/Iwlwifi]
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+The Intel Wireless driver update project aims to bring support for newer chipsets along with mac80211 LinuxKPI compat code.
+The dual-licensed Intel driver code was ported in the past for the iwm(4) native driver; using the LinuxKPI compat framework allows us to use the driver directly and gives support to all the latest chipsets, with only minor local modifications.
+Some of the changes made while porting the driver to FreeBSD were kindly incorporated into the upstream Linux driver already.
+
+During the first quarter work continued with about 70 commits.
+Updating the driver and firmware reduced differences to the Linux version and gave us bugfixes and improvements.
+Changes to the LinuxKPI 802.11 compatibility layer were made to avoid firmware crashes and possible panics for users along with other improvements.
+
+Auto-loading support for LinuxKPI PCI drivers was comitted.
+This means that iwlwifi(4) will now load automatically during boot if a supported card is detected without any user interactions.
+Considering the current state of the driver and the next release a decision was made that iwm(4) supported chipsets will continue to attach to iwm(4) for now and only newer and otherwise unsupported chipsets will use the iwlwifi(4) driver.
+This is likely going to change in CURRENT as soon as iwlwifi(4) provides better support than iwm(4).
+
+The code was merged to the stable/13 branch and the current state will be shipped with the upcoming 13.1-RELEASE.
+
+In addition to The FreeBSD Foundation thanks need to go to all users who have been testing and reporting back or are patiently waiting for the next update.
+For the latest state of the development, please follow the freebsd-wireless mailing list.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-01-2022-03/kde.adoc b/website/content/en/status/report-2022-01-2022-03/kde.adoc
new file mode 100644
index 0000000000..8c88b635d1
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/kde.adoc
@@ -0,0 +1,49 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] +
+link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
*** 339 LINES SKIPPED ***